close 614413 thank you Roger,
thanks for heads-up. I am unable to keep up with debian-devel, so thank you for the summary. This is a good news :). Closing the bug. Ondrej On Thu, Mar 17, 2011 at 13:09, Roger Leigh <[email protected]> wrote: > On Thu, Mar 17, 2011 at 11:56:59AM +0100, Ondřej Surý wrote: >> tags 614413 +wontfix >> thank you >> >> Hi, >> >> just to reconfirm our position - I'm here with Sean and Raphael. (And >> BTW: Roger, very good work on that report, we just don't agree with >> the conclusion ;)). > > Hi Ondřej, > > That's fine. I don't know if you saw the discussion on -devel and > -policy, but I have since revised this opinion in light of the > discussion, and this isn't a bug at all. Feel free to close it > entirely :) > > We subsequently adjusted the apt resolver to behave in the same way > as the internal resolver; that is, it prunes all alternatives and > only considers the first one, making it perfectly acceptable to use > alternatives. (The behaviour is configurable; aptitude considers all > alternatives by default, so the alternatives can be used when building > e.g. experimental and backports, but won't be used for unstable.) > > The only known difference now is that internal would skip the first > alternative if any of the alternatives were already installed. apt > will still require the first to be present. This difference will > only be seen if building in a dirty build environment, and nowadays > we use clean chroot snapshots so it won't be seen in practice. > > > Regards, > Roger > > -- > .''`. Roger Leigh > : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ > `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ > `- GPG Public Key: 0x25BFB848 Please GPG sign your mail. > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAk2B+foACgkQVcFcaSW/uEjdQACg8rW7qNsbtCQQ5S/EpVgqVgxM > 66oAoO9/evKem4Ob/PC5BHPFklD82/MJ > =WTYw > -----END PGP SIGNATURE----- > > -- Ondřej Surý <[email protected]> http://blog.rfc1925.org/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
