On Wed, May 20, 2009 at 09:50:27AM +0300, Andrei Popescu wrote: > On Mon,18.May.09, 16:28:55, Barclay, Daniel wrote: > > Michael M. Moore wrote: > > ... > > > mcu...@drifter:~$ cat /etc/apt/apt.conf > > > APT::Default-Release "stable"; > > > APT::Cache-Limit 33554432; > > > > At some time in the past, APT::Default-Release worked only with the > > status-based > > release names (stable, testing, etc.) but didn't work (and didn't report any > > error message) when given release code names (e.g., lenny, sid, etc.) > > > > Has that been fixed yet? > > Short answer: No. Long answer: see #97564, #254716, #423234 and #509471. > > > If not, how can one avoid having aptitude try to upgrade you to a newly > > release version (before you more directly choose to)? > > I'd be interested in a solution as well.
Are you talking aptitude bug: 514930 It has interesting comment > This bug of aptitude ignoring priority of packages appears to be the > same as bug #473296 . It is fixed in experimental only... Osamu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
