Re: Difficulty downgrading a mistakenly installed non-stable package
On Fri 24 Apr 2015 at 12:37:36 -0400, Kynn Jones wrote: I try to keep my system as close to 100% stable as possible. In spite of this, a version of libp11-kit0 that is ahead of stable somehow snuck into my system: $ apt-cache policy libp11-kit0 libp11-kit0: Installed: 0.20.7-1~bpo70+1 Candidate: 0.20.7-1~bpo70+1 Version table: *** 0.20.7-1~bpo70+1 0 100 /var/lib/dpkg/status 0.12-3 0 500 http://debian.csail.mit.edu/debian/ stable/main amd64 Packages 500 http://ftp.us.debian.org/debian/ stable/main amd64 Packages libp11-kit0 wasn't installed by mistake and didn't sneak onto your system uninvited. Backports will pull in packages and versions of packages which are not in a stable release. Bug makes interesting reading; especially when it contains In my opinion it's very good when backports is default in sources.list. My opinion is that I don't want to push ticking time bombs into the hands of our users. And that's exactly what defaulting to enabling backports was. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150424175030.go22...@copernicus.demon.co.uk
Re: Difficulty downgrading a mistakenly installed non-stable package
Kynn Jones wrote: $ apt-cache policy libp11-kit0 libp11-kit0: Installed: 0.20.7-1~bpo70+1 Candidate: 0.20.7-1~bpo70+1 Version table: *** 0.20.7-1~bpo70+1 0 100 /var/lib/dpkg/status 0.12-3 0 500 http://debian.csail.mit.edu/debian/ stable/main amd64 Packages 500 http://ftp.us.debian.org/debian/ stable/main amd64 Packages ... How can I downgrade this libp11-kit0? The usual way is to specify the explicit version number. apt-get install libp11-kit0=0.12-3 Upgrading is automatic but downgrading requires an explicit version. Bob signature.asc Description: Digital signature
Re: Difficulty downgrading a mistakenly installed non-stable package
On Fri 24 Apr 2015 at 18:50:30 +0100, Brian wrote: Bug makes interesting reading; especially when it contains #764982 in case anyone was wondering, :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/24042015185527.7a08296f2...@desktop.copernicus.demon.co.uk
Re: Difficulty downgrading a mistakenly installed non-stable package
Kynn Jones wrote: I try to keep my system as close to 100% stable as possible. In spite of this, a version of libp11-kit0 that is ahead of stable somehow snuck into my system: $ apt-cache policy libp11-kit0 libp11-kit0: Installed: 0.20.7-1~bpo70+1 Candidate: 0.20.7-1~bpo70+1 Version table: *** 0.20.7-1~bpo70+1 0 100 /var/lib/dpkg/status 0.12-3 0 500 http://debian.csail.mit.edu/debian/ stable/main amd64 Packages 500 http://ftp.us.debian.org/debian/ stable/main amd64 Packages I went back and looked at your previous messages to the list. I see this from you previously: As part of a work-related requirement, I need to install ia32-libs on my (mostly stable) Debian laptop. Unfortunately, it turns out that ia32-libs conflicts, indirectly, with *the one lone package* that I have explicitly installed from a Debian release other than stable, namely emacs24-lucid from wheezy-backports. The immediate cause of the conflict is the package libp11-kit0, but the full dependency chain goes like this: emacs24-lucid depends on libgnutls-deb0-28 (= 3.3.0) depends on libp11-kit0 (= 0.20.7) There you go! It wasn't somehow. It was installed as an explicit installation by you when you installed it from backports. Everything makes perfect sense. Before downgrading it you would need to remove the emacs24-lucid backport that you installed that pulled it in first. Along with the other dependencies too. On the other hand you say you want emacs24-lucid from backports. In which case that means you also want libp11-kit0 from backports to supply the dependency for it too. Seems reasonable to me. Keep it! :-) Bob signature.asc Description: Digital signature
Re: Difficulty downgrading a mistakenly installed non-stable package
On Fri, Apr 24, 2015 at 1:50 PM, Brian a...@cityscape.co.uk wrote: On Fri 24 Apr 2015 at 12:37:36 -0400, Kynn Jones wrote: I try to keep my system as close to 100% stable as possible. In spite of this, a version of libp11-kit0 that is ahead of stable somehow snuck into my system: $ apt-cache policy libp11-kit0 libp11-kit0: Installed: 0.20.7-1~bpo70+1 Candidate: 0.20.7-1~bpo70+1 Version table: *** 0.20.7-1~bpo70+1 0 100 /var/lib/dpkg/status 0.12-3 0 500 http://debian.csail.mit.edu/debian/ stable/main amd64 Packages 500 http://ftp.us.debian.org/debian/ stable/main amd64 Packages libp11-kit0 wasn't installed by mistake and didn't sneak onto your system uninvited. Backports will pull in packages and versions of packages which are not in a stable release. You're right, that's exactly what happened! (The reason I thought otherwise is that I misinterpreted some of `aptitude`'s output. I won't bore you with the details.) Searching for libp11-kit0 in /var/log/aptitude.1.gz I found the line [UPGRADE] libp11-kit0:amd64 0.12-3 - 0.20.7-1~bpo70+1 just a couple of lines below the line [INSTALL] emacs24-lucid:amd64 Sure enough, emacs24-lucid is one of only two packages (the other one being emacs24-el) that I've installed from outside of stable, and both come from wheezy-backports. Thanks for your comments. And @Bob, thanks also for your suggestion. The output I got when I tried it included the lines The following packages have unmet dependencies: libgnutls-deb0-28 : Depends: libp11-kit0 (= 0.20.7) but 0.12-3 is to be installed. The following actions will resolve these dependencies: Remove the following packages: 1) emacs24-lucid 2) libgnutls-deb0-28 ...and seeing `emacs24-lucid` there was what set me on the Road to Enlightenment. ;) kj -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAFvQaj7Dm1DRywMvtHP5KpYRLWE=oM=+-h30+3kw2amuu53...@mail.gmail.com
