I just failed to reproduce this bug with apt 0.6.9, so I suspect it was caused by some missing or partially retrieved Release files.
On 01 Jan 2004, Matt Zimmerman <[EMAIL PROTECTED]> wrote: > On Fri, Jan 02, 2004 at 01:10:09AM +0100, Philipp Weis wrote: > > > I have been able to resolve my pinning problem by replacing sarge with > > testing and woody with stable. > > > > Nevertheless, some strangeness remains. If the releases have to be referred > > to by their generic name, why did the last pin on unstable not work? And > > I'm sure this preferences file worked with the 0.5 version of apt. > > > > Please let me know if I could help you with any further information. > > Yes, I inadvertently changed the semantics. This will be fixed in 0.6.10, > to be uploaded shortly. Are you sure this was standard behaviour in 0.5? The sample preferences files in the documentation (man apt_preferences) use the suite name instead of the codename. I just verified it on one of my machines running apt 0.5.14 from testing: it definitely uses the suite name instead, codenames do not work there. Thanks for your great work with apt 0.6! -- Philipp Weis [EMAIL PROTECTED] Freiburg, Germany http://pweis.com/
