Bug#885238: rumor: please migrate to guile-2.2

Source: rumor Severity: normal I'd like to remove guile-2.0 before the buster release, so please migrate to guile-2.2 when you can. 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

Re: Processed: Re: RM: emacs23 -- ROM; replaced by emacs24

, mipsel, powerpc, s390x, sparc emacs23-nox | 23.4+1-4.1+b1 | amd64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x, sparc Maintainer: Rob Browning --- Reason --- -- Checking reverse

Bug#745991: Bug#760986: RM: guile-1.8 -- ROM; replaced by guile-2.0

t; 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

Bug#746010: rumor: please migrate to guile-2.0

Package: rumor I'm planning to have guile-1.8 removed from unstable before the freeze; please migrate to guile-2.0 as soon as possible. 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

Bug#745991: beast: please migrate to guile-2.0

Package: beast Version: 0.7.8-1 I'm planning to have guile-1.8 removed before the freeze; please migrate to guile-2.0 as soon as possible. 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-

Please upgrade your package to guile-2.0 as soon as possible

guile-1.8-dev xchat-guile: guile-1.8-dev 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 ___ pkg-mul

Re: Proposed new requirements for emacsen add-on packages

uot;new-style" packages, then that may be the right thing to do for now, since the alternative appears to be a much bigger overhaul -- an overhaul that I suspect in the end may well require even more substantial changes to all add-on packages. Many thanks for helping me think this through. --

Re: Proposed new requirements for emacsen add-on packages

Rob Browning writes: > However, to demonstrate why I'm beginning to think the current approach > may be unworkable, consider the case where no emacsen-related packages > are installed and someone runs this: > > apt-get install emacs24 add-on-depending-on-add-on-1 add-

Re: Proposed new requirements for emacsen add-on packages

acs-install-standard.sh > > but while highly desirable this is something different from the > original problem this thread is about. Agreed, and there are a number of ways we might manage something like that, which might or might not involve the code going directly into emacsen-common -- i.e.

Re: Proposed new requirements for emacsen add-on packages

hat we required before, since emacsen-common is vastly smaller than any of the flavors. Ideally, the dependency requirement, assuming we decide that it's necessary, will turn out to be a temporary addition -- until we figure out how to remove it again (perhaps with triggers, or some other approach).

Proposed new requirements for emacsen add-on packages

-common >= 2.0.8. Thoughts? Strong objections? (And for whatever it's worth, I've been posting some relevant bits to debian-emac...@lists.debian.org lately, but I imagined that many/most of you aren't subscribed.) Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org