* Rob Browning ([email protected]) [141002 18:59]:
> Daniel Schepler <[email protected]> writes:
>
> > Well, I was actually just pulling it into my bootstrapping process as a
> > build
> > dependency of swig2.0 and autogen.
>
> OK, I've filed migration bugs against both. I'm guessing that perhaps
> once they migrate, you can migrate?
I'm not sure if this will actually happen in time for jessie, because looking
at the current packages in testing using guile-1.8:
anubis: anubis [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel
powerpc s390x]
not yet updated, no explizit patch
dico: dico-module-guile [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386
mips mipsel powerpc s390x]
FTBFS on three arches since the update, bug just filed
drgeo: drgeo [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel
powerpc s390x]
Bug closed by package still depends on guile-1.8
gnubik: gnubik [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel
powerpc s390x]
waiting for migration (3 of 5 days)
guile-cairo: guile-cairo [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386
mips mipsel powerpc s390x]
guile-cairo-dev [amd64 armel armhf i386 kfreebsd-amd64
kfreebsd-i386 mips mipsel powerpc s390x]
FTBFS on two arches since the update, because guile-snarf depends on gcc-4.8
without an package dependency
(at least on armhf / armel), bug just filed
guile-lib: guile-library
Still depends on guile-1.8 in spite of the NMU
lilypond: lilypond [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips
mipsel powerpc s390x]
waiting on upstream
mailutils: mailutils-guile
not fixed
trackballs: trackballs [amd64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386
mips mipsel powerpc s390x]
nothing yet
Especially as the freeze is in about a month, I don't think this will
be acomplished unless someone is pushing really hard right now. So I
think it would be helpful to fix the guile-1.8-bug now. Of course,
individual packages could still migrate to guile-2.0 as they consider
fit, until the freeze date.
Andi
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
