On Thu, May 22, 2014 at 11:43:39AM -0500, Rob Browning wrote: > Agustin Martin <agmar...@debian.org> writes: > > > One question here, does the dependency really needs to be this tight? I > > mean, would emacsen-common (>= 2.0.5) be enough? That is the emacsen-common > > version in unstable and would help a lot with use of newer add-on packages > > in stable. > > Let me make sure I understand -- what's the case you're thinking about > here? > > Is it someone running stable/testing (or similar) who wants to > > apt-get install -t testing newer-add-on > > but doesn't want that to pull in a new emacsen-commmon, or something > else?
My first thought was about possible incompatibilities of new emacsen-common with old stuff in stable. But thinking more in depth, I'd expect sid emacsen-common to install smoothly in stable and work at least as well (and with most of the known problems with not well adapted add-ons) as stable emacsen-common. If that is the case, my original question is mostly philosophical, nothing to worry about too much. Simply installing emacsen-common along with the new add-on would satisfy dependencies and fix the problem. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
