Luca Falavigna <dktrkr...@debian.org> writes:
> These are the reverse dependencies to be fixed before removing this
> package:
Right -- I was hoping to try to reach a decision this week with respect
to jessie.
Here's what I hope is a reasonably accurate summary of the situation.
As a general comment, people on #guile (including one of the upstream
Guile maintainers) have said that at this point, they would prefer that
we remove packages from jessie that support Guile 2.0 upstream, but
still depend on 1.8 in Debian (though we might or might not keep them in
unstable). This was mentioned in particular, with respect to g-wrap,
guile-cairo, and guile-gnome-platform.
As an overall summary:
- There are a few packages that we might want to remove from jessie
for now (but they're likely to return later if/when they have an
active maintainer -- guile-cairo, etc.[1]).
- There's at least one package that has an active maintainer, and is
actively being ported upstream, but that probably won't be ready for
jessie (lilypond).
- There are a number of packages that are more or less unmaintained,
or may otherwise be unsuitable for continued inclusion in Debian.
- Guile 1.8 is no longer maintained upstream, and hasn't been since
2010.
[1] Though apparently g-wrap, guile-cairo, and guile-gnome-platform may
be easy to NMU for 2.0 -- if I get enough time *immediately*, I
might try to help there. Anyone else interested should talk to Mark
(cc'ed above).
In the end, the question is whether or not, on balance, we're better off
with or without guile-1.8 in jessie.
> anubis
No response wrt 2.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745989
Last non-NMU: 2009-09
> beast
No response wrt 2.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745991
Last non-NMU: 2013-02
> drgeo
Some response from the maintainer in May, but nothing since:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707903
Last non-NMU appears to be 2012-05
I've also been told that drgeo no longer uses Guile upstream.
> freetalk
No response wrt 2.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745997
Last non-NMU: 2012-06
> g-wrap [1]
Only response wrt 2.0 is a mention of an upload that's been in
experimental for two years, but no response from the maintainer:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761210
Last non-experimental upload: 2012-05
> guile-cairo [1]
Looks like this may just be waiting on a testing transition, which may
have been blocked by a (now fixed) problem with guile-2.0 on arm*. If
so, it should just need a rebuild on arm*.
Though #guile warned that this NMU may or may not play nice with the
current guile-gnome-platform (below), depending on exactly how the NMU
was handled,
> guile-gnome-platform [1]
No response wrt 2.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761211
Last non-NMU: 2012-06
> gwave
This may be dependent on the guile-cairo update.
> lilypond
Upgrade to 2.0 won't be ready upstream in time for jessie, so removing
guile-1.8 would imply removing lilypond.
> texmacs
Last information was that upstream doesn't support 2.0 yet
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731787
but texmacs may also not be currently suitable for Debian for other
reasons?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711383
> trackballs
No response wrt 2.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746011
Last non-NMU: 2007-12
> swig2.0
I'm probably just missing something obvious, but I'm not sure why this
is still listed -- 2.0.12-1 appears to be in testing, and it is supposed
to have migrated to guile-2.0. Looking in the control file I also don't
see any obvious guile-1.8 deps...
> graphviz
Hmm, "dak ... -s testing -Rn guile-1.8" doesn't list it, but maybe "-s
testing" isn't working right? In any case, I imagine it's the swig dep
above.
> guile-1.8-non-dfsg/non-free
Should be removed iff guile-1.8 is.
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
