Bug#599523: [update-manager-gnome] wants to downgrade packages without any notice
user release.debian@packages.debian.org usertag 599523 squeeze-can-defer tag 599523 squeeze-ignore kthxbye On Fri, Oct 8, 2010 at 14:01:19 +0200, Zoran Dzelajlija wrote: Package: update-manager-gnome Version: 0.200.4-1 Severity: serious --- Please enter the report below this line. --- update-manager wants to downgrade a package I explicitely installed from experimental without any special notice. This downgrade would break functionality on my machine. apt and aptitude don't try to do anything similar, nor suggest it be done. Seems to be some kind of weird apt behaviour with experimental. I don't consider this a blocker for squeeze, tagging as such. Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#599523: [update-manager-gnome] wants to downgrade packages without any notice
Processing commands for cont...@bugs.debian.org: user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was jcris...@debian.org). usertag 599523 squeeze-can-defer Bug#599523: [update-manager-gnome] wants to downgrade packages without any notice There were no usertags set. Usertags are now: squeeze-can-defer. tag 599523 squeeze-ignore Bug #599523 [update-manager-gnome] [update-manager-gnome] wants to downgrade packages without any notice Added tag(s) squeeze-ignore. kthxbye Stopping processing here. Please contact me if you need assistance. -- 599523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599523: [update-manager-gnome] wants to downgrade packages without any notice
Hi, On 10/21/2010 11:25 PM, Zoran Dželajlija wrote: Candidate is 7.7.1-4, NOT your wanted 7.8.2-2. Indeed, but a downgrade must not be attempted at priority 700 or even 990. The relevant passage from apt_preferences(5) seem to be: I know that part of apt_preferences(5) and your assumtion sounds correct. But! ;) I've just installed a plain Squeeze in a VM, added experimental to the sources and ran apt-get update apt-get -t experimental install libgl1-mesa-dri. The followed apt-get upgrade told me 0 packages to upgrade (expected behaviour). But then I applied your preferences file, and even apt-get wants to downgrade libgl1-mesa-dri now. Even when I lower the priorities of libgl to 500 on all suites, apt still tries to downgrade it. Since the newer package was explicitely installed manually, and the highest pinned, target release package does _not_ exceed 1000, I believe a downgrade _must not_ be attempted at all. Both apt-get and aptitude binaries interpret the situation in this manner and don't try to downgrade, as opposed to update-manager. As written above, MY apt does a downgrade, aptitude doesnt. UpdateManager uses APT's python bindings and never does stuff itself, so if any, this bug is to be searched in apt. Digging through src:apt bugs, I found this one: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543966 Exactly your behaviour (and yes, as soon I pin libgl/testing to 100, it downgrades). I'd say this one is a duplicate of the above, the bug is in apt, not in UM. HOw about merging after raising the priority at apt to serious? Sure, attaching outputs of apt-cache policy and cat /etc/apt/preferences /etc/apt/preferences.d/*. My preferences probably are somewhat broken according to apt-cache policy libgl-mesa-dri. They don't do what I expected them to -- that is, make the latest libgl1-mesa-dri from either testing, unstable or experimental the prefered candidate. However I don't see a way how they could enable a downgrade. To reach that, it should be enough to have Package: libgl1-mesa-dri Pin: release a=experimental Pin-Priority: 500 Then all suites would have prio 500 (If you drop your handpinning to 300,700 etc) and get always the latest package available. Regards Evgeni -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599523: [update-manager-gnome] wants to downgrade packages without any notice
Hi, Quoting Evgeni Golov (evg...@debian.org): Hi Zoran, I fear your problem is your pinning. I believe the problem is update-manager does not behave like apt-preferences(5) says APT (or presumably any package manager) should. Some reasoning below. $ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 7.8.2-2 Candidate: 7.7.1-4 Package pin: 7.7.1-4 Version table: *** 7.8.2-2 990 200 http://debian.iskon.hr/debian/ experimental/main i386 Packages 100 /var/lib/dpkg/status 7.7.1-4 990 700 http://debian.iskon.hr/debian/ testing/main i386 Packages 300 http://debian.iskon.hr/debian/ unstable/main i386 Packages 7.0.3-7 990 400 http://debian.iskon.hr/debian/ stable/main i386 Packages Candidate is 7.7.1-4, NOT your wanted 7.8.2-2. Indeed, but a downgrade must not be attempted at priority 700 or even 990. The relevant passage from apt_preferences(5) seem to be: [cut] If the target release has been specified then APT uses the following algorithm to set the priorities of the versions of a package. Assign: priority 1 to the versions coming from archives which in their Release files are marked as NotAutomatic: yes like the debian experimental archive. priority 100 to the version that is already installed (if any). priority 500 to the versions that are not installed and do not belong to the target release. priority 990 to the versions that are not installed and belong to the target release. APT then applies the following rules, listed in order of precedence, to determine which version of a package to install. - Never downgrade unless the priority of an available version exceeds 1000. (Downgrading is installing a less recent version of a package in place of a more recent version. Note that none of APT's default priorities exceeds 1000; such high priorities can only be set in the preferences file. Note also that downgrading a package can be risky.) - Install the highest priority version. - If two or more versions have the same priority, install the most recent one (that is, the one with the higher version number). - If two or more versions have the same priority and version number but either the packages differ in some of their metadata or the --reinstall option is given, install the uninstalled one. [cut] Since the newer package was explicitely installed manually, and the highest pinned, target release package does _not_ exceed 1000, I believe a downgrade _must not_ be attempted at all. Both apt-get and aptitude binaries interpret the situation in this manner and don't try to downgrade, as opposed to update-manager. In addition to fixing this behavior, I strongly suggest update-manager should warn when a downgrade is attempted or proposed _even_ when the true conditions for a downgrade are met, because the packaging policies do not account for downgrades and things are allowed to break. If you want, I can clone or file a separate bug for absence of such a warning. Can you paste the output of `apt-cache policy` and the content of /etc/apt/preferences and /etc/apt/preferences.d/* Sure, attaching outputs of apt-cache policy and cat /etc/apt/preferences /etc/apt/preferences.d/*. My preferences probably are somewhat broken according to apt-cache policy libgl-mesa-dri. They don't do what I expected them to -- that is, make the latest libgl1-mesa-dri from either testing, unstable or experimental the prefered candidate. However I don't see a way how they could enable a downgrade. Regards, Zoran $ apt-cache policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://download.virtualbox.org/virtualbox/debian/ lenny/non-free i386 Packages release o=Oracle Corporation,n=lenny,l=Oracle Corporation,c=non-free origin download.virtualbox.org 500 http://download.skype.com/linux/repos/debian/ stable/non-free i386 Packages origin download.skype.com 400 http://deb.opera.com/opera-snapshot/ stable/non-free i386 Packages release o=Opera Software ASA,a=stable,n=lenny,l=The Opera web browser,c=non-free origin deb.opera.com 400 http://deb.opera.com/opera/ stable/non-free i386 Packages release o=Opera Software ASA,a=stable,n=lenny,l=The Opera web browser,c=non-free origin deb.opera.com 500 file:/home/jelly/mnt/burek/packages/wine/ ./ Packages 500 file:/home/jelly/packages/ ./ Packages 300 http://www.debian-multimedia.org/ sid/non-free i386 Packages release v=None,o=Unofficial Multimedia Packages,a=unstable,n=sid,l=Unofficial Multimedia Packages,c=non-free origin www.debian-multimedia.org 300 http://www.debian-multimedia.org/ sid/main i386 Packages release v=None,o=Unofficial Multimedia Packages,a=unstable,n=sid,l=Unofficial Multimedia Packages,c=main origin www.debian-multimedia.org 500 http://www.lamaresh.net/apt/ squeeze/main i386 Packages release o=Wine Squeeze
Bug#599523: [update-manager-gnome] wants to downgrade packages without any notice
Package: update-manager-gnome
Version: 0.200.4-1
Severity: serious
--- Please enter the report below this line. ---
update-manager wants to downgrade a package I explicitely installed from
experimental without any special notice. This downgrade would break
functionality on my machine. apt and aptitude don't try to do anything
similar, nor suggest it be done.
$ apt-cache policy libgl1-mesa-dri
libgl1-mesa-dri:
Installed: 7.8.2-2
Candidate: 7.7.1-4
Package pin: 7.7.1-4
Version table:
*** 7.8.2-2 990
200 http://debian.iskon.hr/debian/ experimental/main i386 Packages
100 /var/lib/dpkg/status
7.7.1-4 990
700 http://debian.iskon.hr/debian/ testing/main i386 Packages
300 http://debian.iskon.hr/debian/ unstable/main i386 Packages
7.0.3-7 990
400 http://debian.iskon.hr/debian/ stable/main i386 Packages
$ egrep -vh '^[[:blank:]]*//' /etc/apt/apt.conf /etc/apt/apt.conf.d/*
APT::Cache-Limit 33554432;
Acquire
{
http
{
Timeout 30;
Pipeline-Depth 5;
No-Cache false;
Max-Age 86400; // 1 Day age on index files
No-Store true;// Prevent the cache from storing archives
};
ftp
{
Proxy::ftp.irb.hr DIRECT;
Timeout 30;
};
};
APT
{
NeverAutoRemove
{
^firmware-linux.*;
^linux-firmware$;
^linux-image.*;
^kfreebsd-image.*;
^linux-restricted-modules.*;
^linux-ubuntu-modules-.*;
};
Never-MarkAuto-Sections
{
metapackages;
restricted/metapackages;
universe/metapackages;
multiverse/metapackages;
oldlibs;
restricted/oldlibs;
universe/oldlibs;
multiverse/oldlibs;
};
};
DPkg::Pre-Install-Pkgs {/usr/sbin/apt-listbugs apt || exit 10;};
DPkg::Tools::Options::/usr/sbin/apt-listbugs ;
DPkg::Tools::Options::/usr/sbin/apt-listbugs::Version 2;
APT::Periodic::Update-Package-Lists 1;
APT::Periodic::Download-Upgradeable-Packages 0;
APT::Periodic::AutocleanInterval 0;
APT::Update::Post-Invoke {touch /var/lib/apt/periodic/update-success-stamp
2/dev/null || true;};
APT::Archives::MaxAge 30;
APT::Archives::MinAge 2;
APT::Archives::MaxSize 500;
DPkg::Pre-Install-Pkgs { /usr/bin/apt-listchanges --apt || test $? -ne 10; };
DPkg::Tools::Options::/usr/bin/apt-listchanges::Version 2;
DPkg::Pre-Install-Pkgs {/usr/sbin/dpkg-preconfigure --apt || true;};
DPkg::Post-Invoke {if [ -d /var/lib/update-notifier ]; then touch
/var/lib/update-notifier/dpkg-run-stamp; fi; if [ -e
/var/lib/update-notifier/updates-available ]; then echo
/var/lib/update-notifier/updates-available; fi ; };
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.35-trunk-686
Debian Release: squeeze/sid
700 testing security.debian.org
700 testing debian.iskon.hr
500 squeeze www.lamaresh.net
400 stable debian.iskon.hr
400 stable deb.opera.com
300 unstablewww.debian-multimedia.org
300 unstabledebian.iskon.hr
200 experimentaldebian.iskon.hr
--- Package information. ---
Depends (Version) | Installed
=-+-==
python| 2.6.5-13
python-support(= 0.90.0) | 1.0.10
gconf2 (= 2.28.1-2) | 2.28.1-4
update-manager-core (= 0.200.4-1) | 0.200.4-1
python-gconf | 2.28.1-1
python-dbus | 0.83.1-1
python-gtk2 | 2.17.0-4
gksu | 2.0.2-3
python-gobject(= 2.16.1) | 2.21.4+is.2.21.3-1
python-vte| 1:0.24.3-1
Package's Recommends field is empty.
Suggests (Version) | Installed
==-+-===
update-notifier| 0.99.3debian6
software-properties-gtk|
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
