On Fri, Oct 11, 2002 at 05:05:56PM -0600, Shawn Willden wrote: > My file/print/web/e-mail/everything server is running Woody, and I'd like to > mostly keep it that way. However, there are a few packages I'd like to pull > from Sarge, and possibly even Sid. > > I've read through the docs that say how to do this, and they make perfect > sense, but the approach described doesn't seem to actually work. > > As I understand it, I should be able to just add the appropriate lines to > sources.list so that I have access to the newer packages. That works, and > apt-get and aptitutude both want to upgrade my system like crazy. To prevent > this, I should be able to just put the line: > > Apt::Default-Release "woody"; I don't find this as a valid configuration directive in /usr/share/doc/apt/examples/configure-index.gz. > > in a file in /etc/apt/apt.conf.d (I put it in '71local'). > > But "apt-get upgrade" and "aptitude upgrade" (my preference) still want to > upgrade my system like crazy. > > So, I went the next step and put the following in /etc/apt/preferences: > > Package: * > Pin: release v=3.0*,a=stable > > But, *still* "apt-get upgrade" and "aptitude upgrade" want to upgrade some > packages, though not many. In fact, the packages it wants to upgrade are: > > automake1.6 > ethereal > ethereal-common > libfam0 > libpng2 > libssl0.9.6 > openssl > python > python2.1 (Held back due to unsatisfied dependencies) > courier-imap-ssl (Held back due to unsatisfied dependencies) > courier-pop-ssl (Held back due to unsatisfied dependencies) > courier-ssl (Held back due to unsatisfied dependencies) A number of these have had security upgrades. The courier packages are probably held back because they depend on newer versions of openssl and libssl0.9.6. If you have woody, sarge, and sid in your sources.list and are using aptitude, highlight the name of the upgradeable package, press enter, and scroll to bottom of displayed information to see which of the available version the upgrade will install. Since automake1.6 is in testing, do you still have testing and sid lines in your sources.list? If you still do and want to keep them, you could make your /etc/apt/preferences something like: Package: * Pin: release a=testing Pin-Priority: 90 Package: * Pin: release a=unstable Pin-Priority: 60 Package: * Pin: release a=stable Pin-Priority: 990 You could try downloading automake1.5 deb and installing it with dpkg. > > But I would rather stick with the stable versions of all of these. Actually, > the only packages I want to pull from Sarge are a few that aren't in Woody at > all. Pulling any files from Sarge may require you to upgrade key files like libc6. Youmay want to consider downloading source package from Sarge and then compiling rather than installing binary deb from Sarge. > > So, questions: Why doesn't setting the default release work like I expect it > to? And why does pinning the Woody packages still leave a few to get > upgraded? I've even tried setting the pin priority to 1001, which should > force packages to *downgrade* to satisfy the pinning (not what I want, > really, if I choose to explicitly upgrade a package, I don't want it > downgraded again), but that doesn't change the behavior either. > > Suggestions? Am I missing something obvious? > > Thanks, > > Shawn. > > -- Jerome
Attachment:
pgpmQ9aD0ooYF.pgp
Description: PGP signature