Hi all,
I've been running Sarge for a while now and have avoided pinning for a long time, but am now seriously considering pinning Firefox and probably also Inkscape from testing. I like this idea better than backports for somewhat intangible reasons. Since I've never pinned, I'm proceeding carefully; I want to keep my system as close to stable as possible after installing these two packages, and I am hoping they don't have too many dependencies. I've added testing sources to sources.list and created a preferences file (as described at
dastrike's wiki) that looks like this:
Code:
# cat preferences
Package: *
Pin: release a=stable
Pin-Priority: 700
Package: *
Pin: release a=testing
Pin-Priority: 600
Now, after modifying sources.list I ran "apt-get update", and everything looks fine. But when I then simulate an upgrade (without first installing any packages), it seems that APT wants to update one of my libraries to a version from testing:
Code:
# apt-get upgrade -s
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages have been kept back:
acroread acroread-plugins
The following packages will be upgraded:
libpixman1
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
This does make some sense -- "apt-cache show" says that the candidate is from testing. If it already exists on my system, then I got it either from stable or, more likely, from nerim-marillat (now debian-multimedia.org). The question is, how can I know whether I should let it be updated?
I have some concerns about whether this will even work as desired. "#apt-get -s install firefox" shows several library depends, so I tried instead:
Code:
# apt-get -s -t testing install firefox
Reading Package Lists... Done
Building Dependency Tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
firefox: Depends: libgtk2.0-0 (>= 2.8.0) but 2.6.4-3.1 is to be installed
Depends: libxinerama1 but it is not going to be installed
E: Broken packages
I'm not sure how to proceed from there.
Can anyone speak from experience? Would it actually be easier to install Firefox 1.5 from a backport than to pin from testing?
