Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
wheezy backports updates
wheezy backports updates
I just added backports to a minimal blackbox wheezy install
and I see 4 updates
gettext-base
libusb-1.0
libgeoip
libasprintf
Is it normal for backports to automatically update stable or
could it be related to the new point release due shortly?
and I see 4 updates
gettext-base
libusb-1.0
libgeoip
libasprintf
Is it normal for backports to automatically update stable or
could it be related to the new point release due shortly?
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: wheezy backports updates
What does 'apt-cache policy' say for them?
AdrianTM wrote:There's no hacker in my grandma...
Re: wheezy backports updates
$ apt-cache policy gettext-base libusb-1.0-0 libgeoip1 libasprintf0c2
gettext-base:
Installed: 0.18.1.1-10
Candidate: 0.18.3-1~bpo7+1
Version table:
0.18.3-1~bpo7+1 0
100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages
*** 0.18.1.1-10 0
100 /var/lib/dpkg/status
0.18.1.1-9 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
libusb-1.0-0:
Installed: 2:1.0.12-2
Candidate: 2:1.0.17-1~bpo70+1
Version table:
2:1.0.17-1~bpo70+1 0
100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages
*** 2:1.0.12-2 0
100 /var/lib/dpkg/status
2:1.0.11-1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
libgeoip1:
Installed: 1.4.8+dfsg-4
Candidate: 1.5.0-3~bpo70+1
Version table:
1.5.0-3~bpo70+1 0
100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages
*** 1.4.8+dfsg-4 0
100 /var/lib/dpkg/status
1.4.8+dfsg-3 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
libasprintf0c2:
Installed: 0.18.1.1-10
Candidate: 0.18.3-1~bpo7+1
Version table:
0.18.3-1~bpo7+1 0
100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages
*** 0.18.1.1-10 0
100 /var/lib/dpkg/status
0.18.1.1-9 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
$
aptitude preselected them for upgrade as soon as I added backports and updated the package cache.
I suppose I already answered my own question now.
But I still don't understand why aptitude does that occasionally,
selects certain packages automatically for install immediate after updating the package cache while in the ncurses interface.
I'll understand it one day, hopefully...
gettext-base:
Installed: 0.18.1.1-10
Candidate: 0.18.3-1~bpo7+1
Version table:
0.18.3-1~bpo7+1 0
100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages
*** 0.18.1.1-10 0
100 /var/lib/dpkg/status
0.18.1.1-9 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
libusb-1.0-0:
Installed: 2:1.0.12-2
Candidate: 2:1.0.17-1~bpo70+1
Version table:
2:1.0.17-1~bpo70+1 0
100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages
*** 2:1.0.12-2 0
100 /var/lib/dpkg/status
2:1.0.11-1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
libgeoip1:
Installed: 1.4.8+dfsg-4
Candidate: 1.5.0-3~bpo70+1
Version table:
1.5.0-3~bpo70+1 0
100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages
*** 1.4.8+dfsg-4 0
100 /var/lib/dpkg/status
1.4.8+dfsg-3 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
libasprintf0c2:
Installed: 0.18.1.1-10
Candidate: 0.18.3-1~bpo7+1
Version table:
0.18.3-1~bpo7+1 0
100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages
*** 0.18.1.1-10 0
100 /var/lib/dpkg/status
0.18.1.1-9 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
$
aptitude preselected them for upgrade as soon as I added backports and updated the package cache.
I suppose I already answered my own question now.
But I still don't understand why aptitude does that occasionally,
selects certain packages automatically for install immediate after updating the package cache while in the ncurses interface.
I'll understand it one day, hopefully...
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
- dilberts_left_nut
- Administrator
- Posts: 5346
- Joined: 2009-10-05 07:54
- Location: enzed
- Has thanked: 13 times
- Been thanked: 66 times
Re: wheezy backports updates
If you look in the options (in the ncurses interface menu) there is a "Automatically upgrade installed packages" - although it is off by default.
AdrianTM wrote:There's no hacker in my grandma...
Re: wheezy backports updates
I so rarely change any defaults, I even firgot about the options in the menu ...
I only use CTRL T b with any regularity.
Every once in a while I'll add priority to
The default grouping method for package views
especially when downgrading and I want to purge everything except essential and important.
Edit: adding priority is another option I don't understand completely as well.
I've been able to make it persistent a few times, but it usually reverts to default after exiting.
hotkey G
and you know the old routine about version behavior ... sheeshh
I'm still looking for the install automagically after update option, to double check that it is not enabled ...
and see if there are other options I've ever changed that might effect how the ncurses screens behave.
thanks for the kind reminder
editedit: --\ Miscellaneous are both default [ ]
double checking the config files too
but I'm gonna have to find out where they are first...
I only use CTRL T b with any regularity.
Every once in a while I'll add priority to
The default grouping method for package views
especially when downgrading and I want to purge everything except essential and important.
Edit: adding priority is another option I don't understand completely as well.
I've been able to make it persistent a few times, but it usually reverts to default after exiting.
hotkey G
and you know the old routine about version behavior ... sheeshh
I'm still looking for the install automagically after update option, to double check that it is not enabled ...
and see if there are other options I've ever changed that might effect how the ncurses screens behave.
thanks for the kind reminder
editedit: --\ Miscellaneous are both default [ ]
double checking the config files too
but I'm gonna have to find out where they are first...
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
Re: wheezy backports updates
update
the list is up to 11 now ( )
just keepin my eye on it_||_
the new ones
$ apt-cache policy linux-image-3.2.0-4-686-pae base-files libc6 multiarch-support locales tzdata gettext-base openssl
linux-image-3.2.0-4-686-pae:
Installed: 3.2.51-1
Candidate: 3.2.54-2
Version table:
3.2.54-2 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 3.2.51-1 0
100 /var/lib/dpkg/status
3.2.46-1+deb7u1 0
500 http://security.debian.org/ wheezy/updates/main i386 Packages
base-files:
Installed: 7.1wheezy3
Candidate: 7.1wheezy4
Version table:
7.1wheezy4 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 7.1wheezy3 0
100 /var/lib/dpkg/status
libc-bin:
Installed: 2.13-38
Candidate: 2.13-38+deb7u1
Version table:
2.13-38+deb7u1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 2.13-38 0
100 /var/lib/dpkg/status
libc6:
Installed: 2.13-38
Candidate: 2.13-38+deb7u1
Version table:
2.13-38+deb7u1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 2.13-38 0
100 /var/lib/dpkg/status
multiarch-support:
Installed: 2.13-38
Candidate: 2.13-38+deb7u1
Version table:
2.13-38+deb7u1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 2.13-38 0
100 /var/lib/dpkg/status
locales:
Installed: 2.13-38
Candidate: 2.13-38+deb7u1
Version table:
2.13-38+deb7u1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 2.13-38 0
100 /var/lib/dpkg/status
tzdata:
Installed: 2013h-0wheezy1
Candidate: 2013i-0wheezy1
Version table:
2013i-0wheezy1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 2013h-0wheezy1 0
100 /var/lib/dpkg/status
gettext-base:
Installed: 0.18.1.1-10
Candidate: 0.18.3-1~bpo7+1
Version table:
0.18.3-1~bpo7+1 0
100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages
*** 0.18.1.1-10 0
100 /var/lib/dpkg/status
0.18.1.1-9 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
openssl:
Installed: 1.0.1e-2+deb7u3
Candidate: 1.0.1e-2+deb7u4
Version table:
1.0.1e-2+deb7u4 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 1.0.1e-2+deb7u3 0
500 http://security.debian.org/ wheezy/updates/main i386 Packages
100 /var/lib/dpkg/status
$
the list is up to 11 now ( )
just keepin my eye on it_||_
the new ones
$ apt-cache policy linux-image-3.2.0-4-686-pae base-files libc6 multiarch-support locales tzdata gettext-base openssl
linux-image-3.2.0-4-686-pae:
Installed: 3.2.51-1
Candidate: 3.2.54-2
Version table:
3.2.54-2 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 3.2.51-1 0
100 /var/lib/dpkg/status
3.2.46-1+deb7u1 0
500 http://security.debian.org/ wheezy/updates/main i386 Packages
base-files:
Installed: 7.1wheezy3
Candidate: 7.1wheezy4
Version table:
7.1wheezy4 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 7.1wheezy3 0
100 /var/lib/dpkg/status
libc-bin:
Installed: 2.13-38
Candidate: 2.13-38+deb7u1
Version table:
2.13-38+deb7u1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 2.13-38 0
100 /var/lib/dpkg/status
libc6:
Installed: 2.13-38
Candidate: 2.13-38+deb7u1
Version table:
2.13-38+deb7u1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 2.13-38 0
100 /var/lib/dpkg/status
multiarch-support:
Installed: 2.13-38
Candidate: 2.13-38+deb7u1
Version table:
2.13-38+deb7u1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 2.13-38 0
100 /var/lib/dpkg/status
locales:
Installed: 2.13-38
Candidate: 2.13-38+deb7u1
Version table:
2.13-38+deb7u1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 2.13-38 0
100 /var/lib/dpkg/status
tzdata:
Installed: 2013h-0wheezy1
Candidate: 2013i-0wheezy1
Version table:
2013i-0wheezy1 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 2013h-0wheezy1 0
100 /var/lib/dpkg/status
gettext-base:
Installed: 0.18.1.1-10
Candidate: 0.18.3-1~bpo7+1
Version table:
0.18.3-1~bpo7+1 0
100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages
*** 0.18.1.1-10 0
100 /var/lib/dpkg/status
0.18.1.1-9 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
openssl:
Installed: 1.0.1e-2+deb7u3
Candidate: 1.0.1e-2+deb7u4
Version table:
1.0.1e-2+deb7u4 0
500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
*** 1.0.1e-2+deb7u3 0
500 http://security.debian.org/ wheezy/updates/main i386 Packages
100 /var/lib/dpkg/status
$
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
-
- Posts: 107
- Joined: 2014-01-25 21:27
Re: wheezy backports updates
I don't understand. Backports are suppose to be deactivated by default. Are you saying this has changed?
Re: wheezy backports updates
nawziggybopbopdoo wrote:I don't understand. Backports are suppose to be deactivated by default. Are you saying this has changed?
sorry it's not real clear, mostly cause I don't understand some of aptitudes intermittent behavior yet.
But there are two things happening here AFAICT
there are some packages being updated for the new point release scheduled in another week or so - if I understand correctly
And the reason for the OP is that aptitudes ncurses menu sometimes automagically pre schedules packages for upgrade directly after update.
And me being kinda new to backports and seeing this happen after I added backports - see OP and my second post - I was confused a bit.
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
Re: wheezy backports updates
You currently have the 0.18.1.1-10 version of gettext-base installed. It's a version that's not in any of the repos (that's why only /var/lib/dpkg/status is shown for it).llivv wrote:Code: Select all
gettext-base: Installed: 0.18.1.1-10 Candidate: 0.18.3-1~bpo7+1 Version table: 0.18.3-1~bpo7+1 0 100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages *** 0.18.1.1-10 0 100 /var/lib/dpkg/status 0.18.1.1-9 0 500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
I'm pretty sure if you would downgrade gettext-base to the 0.18.1.1-9 wheezy version, that you'll no longer see the wheezy-backports version offered as a upgrade.
Re: wheezy backports updates
Thanks for digging that up for me.kmathern wrote:You currently have the 0.18.1.1-10 version of gettext-base installed. It's a version that's not in any of the repos (that's why only /var/lib/dpkg/status is shown for it).llivv wrote:Code: Select all
gettext-base: Installed: 0.18.1.1-10 Candidate: 0.18.3-1~bpo7+1 Version table: 0.18.3-1~bpo7+1 0 100 http://mirrors.kernel.org/debian/ wheezy-backports/main i386 Packages *** 0.18.1.1-10 0 100 /var/lib/dpkg/status 0.18.1.1-9 0 500 http://mirrors.kernel.org/debian/ wheezy/main i386 Packages
I'm pretty sure if you would downgrade gettext-base to the 0.18.1.1-9 wheezy version, that you'll no longer see the wheezy-backports version offered as a upgrade.
I thought I did a through downgrade of this install from a two year old sid to wheezy,
rather then do the 400+ upgrades to current sid and for practice.
But it looks like I missed a few things, which explains the behavior, at least to me in theory.
Edit: I think aptitudes auto selection of the 4 initial backports packages happened twice. iirc
They are no longer being auto selected after updating the cache.
I will definitely get gettext straightened out asap and double check for others I may have missed...
thanks again k mathern
edit 2:
looks like I missed 57 packages
/var/log/aptitude
Code: Select all
Aptitude 0.6.8.2: log report
Sat, Feb 8 2014 18:05:53 -0500
IMPORTANT: this log only lists intended actions; actions which fail due to
dpkg problems may not be completed.
Will install 59 packages, and remove 24 packages.
54.7 MB of disk space will be freed
===============================================================================
[REMOVE, NOT USED] libsigsegv2:i386
[REMOVE, NOT USED] libxtables9:i386
[REMOVE, NOT USED] python-six:i386
[HOLD, DEPENDENCIES] multiarch-support:i386
[INSTALL, DEPENDENCIES] libebml3:i386
[INSTALL, DEPENDENCIES] libmatroska5:i386
[DOWNGRADE] acpid:i386 1:2.0.17-2 -> 1:2.0.16-1+deb7u1
[DOWNGRADE] cpp-4.4:i386 4.4.7-3 -> 4.4.7-2
[DOWNGRADE] debianutils:i386 4.3.4 -> 4.3.2
[DOWNGRADE] dialog:i386 1.1-20120215-3 -> 1.1-20120215-2
[DOWNGRADE] diffutils:i386 1:3.2-7 -> 1:3.2-6
[DOWNGRADE] ffmpeg:i386 6:0.8.10-1 -> 6:0.8.9-1
[DOWNGRADE] findutils:i386 4.4.2-5 -> 4.4.2-4
[DOWNGRADE] gcc-4.4-base:i386 4.4.7-3 -> 4.4.7-2
[DOWNGRADE] gettext-base:i386 0.18.1.1-10 -> 0.18.1.1-9
[DOWNGRADE] grep:i386 2.14-1 -> 2.12-2
[DOWNGRADE] hostname:i386 3.12 -> 3.11
[DOWNGRADE] hsetroot:i386 1.0.2-2 -> 1.0.2-1
[DOWNGRADE] iptables:i386 1.4.16.3-4 -> 1.4.14-3.1
[DOWNGRADE] javascript-common:i386 8 -> 7
[DOWNGRADE] libasprintf0c2:i386 0.18.1.1-10 -> 0.18.1.1-9
[DOWNGRADE] libcdparanoia0:i386 3.10.2+debian-11 -> 3.10.2+debian-10.1
[DOWNGRADE] libclass-isa-perl:i386 0.36-5 -> 0.36-3
[DOWNGRADE] libcurl3-gnutls:i386 7.28.0-3 -> 7.26.0-1+wheezy8
[DOWNGRADE] libdvdnav4:i386 4.2.0+20121016-1 -> 4.2.0+20120524-2
[DOWNGRADE] libdvdread4:i386 4.2.0+20121016-1 -> 4.2.0+20120521-2
[DOWNGRADE] libenca0:i386 1.14-2 -> 1.13-4
[DOWNGRADE] libgeoip1:i386 1.4.8+dfsg-4 -> 1.4.8+dfsg-3
[DOWNGRADE] libgsf-1-114:i386 1.14.25-1 -> 1.14.21-2.1
[DOWNGRADE] libgsf-1-common:i386 1.14.25-1 -> 1.14.21-2.1
[DOWNGRADE] libjasper1:i386 1.900.1-14 -> 1.900.1-13
[DOWNGRADE] libkeyutils1:i386 1.5.5-4 -> 1.5.5-3
[DOWNGRADE] libltdl7:i386 2.4.2-1.2 -> 2.4.2-1.1
[DOWNGRADE] libnspr4:i386 2:4.9.4-1 -> 2:4.9.2-1+deb7u1
[DOWNGRADE] libnspr4-0d:i386 2:4.9.4-1 -> 2:4.9.2-1+deb7u1
[DOWNGRADE] liboath0:i386 1.12.6-1 -> 1.12.4-1
[DOWNGRADE] libpam-oath:i386 1.12.6-1 -> 1.12.4-1
[DOWNGRADE] libpcre3:i386 1:8.31-1 -> 1:8.30-5
[DOWNGRADE] libpipeline1:i386 1.2.2-1 -> 1.2.1-1
[DOWNGRADE] libpng12-0:i386 1.2.49-3 -> 1.2.49-1
[DOWNGRADE] libprocps0:i386 1:3.3.4-2 -> 1:3.3.3-3
[DOWNGRADE] libsqlite3-0:i386 3.7.15-1 -> 3.7.13-1+deb7u1
[DOWNGRADE] libusb-0.1-4:i386 2:0.1.12-23+nmu1 -> 2:0.1.12-20+nmu1
[DOWNGRADE] libusb-1.0-0:i386 2:1.0.12-2 -> 2:1.0.11-1
[DOWNGRADE] locate:i386 4.4.2-5 -> 4.4.2-4
[DOWNGRADE] logrotate:i386 3.8.3-3 -> 3.8.1-4
[DOWNGRADE] lsb-base:i386 4.1+Debian9 -> 4.1+Debian8+deb7u1
[DOWNGRADE] lsb-release:i386 4.1+Debian9 -> 4.1+Debian8+deb7u1
[DOWNGRADE] m4:i386 1.4.16-4 -> 1.4.16-3
[DOWNGRADE] man-db:i386 2.6.3-3 -> 2.6.2-1
[DOWNGRADE] mime-support:i386 3.52-2 -> 3.52-1
[DOWNGRADE] mkvtoolnix:i386 5.9.0-1 -> 5.6.0-1
[DOWNGRADE] procps:i386 1:3.3.4-2 -> 1:3.3.3-3
[DOWNGRADE] psmisc:i386 22.20-1 -> 22.19-1+deb7u1
[DOWNGRADE] python-debian:i386 0.1.21+nmu2 -> 0.1.21
[DOWNGRADE] python-simplejson:i386 2.6.2-1 -> 2.5.2-1
[DOWNGRADE] quota:i386 4.01-2 -> 4.00-4+deb7u1
[DOWNGRADE] traceroute:i386 1:2.0.19-1 -> 1:2.0.18-3
[DOWNGRADE] vbetool:i386 1.1-3 -> 1.1-2
[DOWNGRADE] wget:i386 1.14-1 -> 1.13.4-3+deb7u1
[DOWNGRADE] xbitmaps:i386 1.1.1-2 -> 1.1.1-1
[DOWNGRADE] xfsdump:i386 3.1.1 -> 3.0.6
[DOWNGRADE] xfsprogs:i386 3.1.9 -> 3.1.7+b1
[HOLD] base-files:i386
[HOLD] libc-bin:i386
[HOLD] libc6:i386
[HOLD] libssl1.0.0:i386
[HOLD] linux-image-3.2.0-4-686-pae:i386
[HOLD] locales:i386
[HOLD] openssl:i386
[HOLD] tzdata:i386
[REMOVE] cpp-4.3:i386
[REMOVE] cpp-4.5:i386
[REMOVE] debconf-english:i386
[REMOVE] defoma:i386
[REMOVE] gcc-4.3-base:i386
[REMOVE] gcc-4.5-base:i386
[REMOVE] gs-common:i386
[REMOVE] libblas3:i386
[REMOVE] libblas3gf:i386
[REMOVE] libdb4.8:i386
[REMOVE] libgmp3c2:i386
[REMOVE] liblzma2:i386
[REMOVE] libssl0.9.8:i386
[REMOVE] netcat:i386
[REMOVE] psfontmgr:i386
[REMOVE] python-gobject-2:i386
[REMOVE] python-gtk2:i386
[REMOVE] python2.5:i386
[REMOVE] python2.5-minimal:i386
[REMOVE] x-ttcidfont-conf:i386
[REMOVE] xpdf-common:i386
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.