bugtracker@slideomania.com wrote: > Hi list, > > recently I was trying to install a package from lenny on etch, that has no > backport available (yet; request has been filed). I was > configuring /etc/apt/apt-conf and /etc/apt/preferences as I saw fit, but > learned "the hard way" that it's seemingly not possible to pin releases by > their relase name (etch, lenny), but only with stable, testing, unstable. [snip] > I'd guess the only way to assure a non-upgrade to lenny once it will be > declared stable, would be something like 'APT::Default-Release "oldstable";' > in /etc/apt/apt.conf - if that worked at all, just a guess for a somewhat > practical workaround... > > Long story short, why is it not possible to pin by release name? Searching for > this returns lots of web pages that show examples with pinning by release > name, and I'm wondering why they all propose something that doesn't work at > all... > > I hope somebody can enlighten me on this topic a bit. Why: because it wasn't implemented properly before. APT 0.8.x, which supposedly will be in Debian Squeeze will have this feature most probably. How to work around: release versions. Just use "4.0*", and apt should not upgrade to Lenny when it becomes stable. FYI: this is already documented in Lenny's APT in apt_preferences(5). Regards, -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com Ukrainian C++ Developer, Debian Maintainer, APT contributor
Attachment:
signature.asc
Description: OpenPGP digital signature