Your message dated Tue, 18 Oct 2011 10:17:35 +0200 with message-id <caaz6_fcwys+ujamtcqectz6vjtko9arnmqofotaxtgzsrmx...@mail.gmail.com> and subject line Re: Bug#645579: apt-get upgrade keeps upgradable package has caused the Debian Bug report #645579, regarding apt-get upgrade keeps upgradable package to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 645579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645579 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: apt Version: 0.8.15.9 Severity: normal I have a very strange m17n-contrib package and apt-get upgrade interaction. In an up to date Sid today with all other packages up to date. apt-get won't offer m17n-contrib for an upgrade but only a dist-upgrade. This can be recreated on my system by ensuring that the previous is installed: # dpkg -i m17n-contrib_1.1.12-2_all.deb And then attempting an upgrade. # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: m17n-contrib 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. And then trying to upgrade. And of course dist-upgrade offers the package for an upgrade okay. # apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: m17n-contrib 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/544 kB of archives. After this operation, 221 kB disk space will be freed. Do you want to continue [Y/n]? Is it possible to ask apt-get to supply more information about this problem to understand why it won't offer this package for an upgrade but only for a dist-upgrade? I tried this: $ apt-get -o Debug::pkgProblemResolver=yes upgrade Reading package lists... Done Building dependency tree Reading state information... Done Entering ResolveByKeep Keeping package m17n-contrib:amd64 The following packages have been kept back: m17n-contrib 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. A debdiff of the packages doesn't show me anything that seems like it should cause this behavior. $ debdiff m17n-contrib_1.1.12-2_all.deb m17n-contrib_1.1.13-1_all.deb [The following lists of changes regard files as different if they have different names, permissions or owners.] Files in second .deb but not in first ------------------------------------- -rw-r--r-- root/root /usr/share/m17n/bo-ewts.mim -rw-r--r-- root/root /usr/share/m17n/hi-vedmata.mim -rw-r--r-- root/root /usr/share/m17n/icons/hi-vedmata.png -rw-r--r-- root/root /usr/share/m17n/icons/si-transliteration.png -rw-r--r-- root/root /usr/share/m17n/icons/te-apple.png -rw-r--r-- root/root /usr/share/m17n/icons/uz-kbd.png -rw-r--r-- root/root /usr/share/m17n/ks-inscript.mim -rw-r--r-- root/root /usr/share/m17n/sa-iast.mim -rw-r--r-- root/root /usr/share/m17n/si-singlish.mim -rw-r--r-- root/root /usr/share/m17n/uz-kbd.mim Files in first .deb but not in second ------------------------------------- -rw-r--r-- root/root /usr/share/m17n/icons/si-trans.png Control files: lines which differ (wdiff format) ------------------------------------------------ Depends: m17n-db (>= [-1.5.0)-] {+1.6.3)+} Description: [-a-] multilingual text processing library - contributed database Installed-Size: [-1400-] {+1184+} Recommends: libm17n-0 (>= [-1.5.0)-] {+1.6.3)+} Version: [-1.1.12-2-] {+1.1.13-1+} I have only the stock apt.conf.d files present. $ ls -log /etc/apt/apt.conf /etc/apt/apt.conf.d ls: cannot access /etc/apt/apt.conf: No such file or directory /etc/apt/apt.conf.d: total 16 -rw-r--r-- 1 40 Apr 30 2010 00trustcdrom -rw-r--r-- 1 430 Apr 5 2011 01autoremove -rw-r--r-- 1 182 Oct 12 2008 70debconf -rw-r--r-- 1 127 May 3 2010 90debsums $ cat /etc/apt/apt.conf.d/* APT::Authentication::TrustCDROM "true"; APT { NeverAutoRemove { "^firmware-linux.*"; "^linux-firmware$"; "^linux-image.*"; "^kfreebsd-image.*"; "^linux-restricted-modules.*"; "^linux-ubuntu-modules-.*"; "^gnumach$"; "^gnumach-image.*"; }; Never-MarkAuto-Sections { "metapackages"; "restricted/metapackages"; "universe/metapackages"; "multiverse/metapackages"; "oldlibs"; "restricted/oldlibs"; "universe/oldlibs"; "multiverse/oldlibs"; }; }; // Pre-configure all packages with debconf before they are installed. // If you don't like it, comment it out. DPkg::Pre-Install-Pkgs {"/usr/sbin/dpkg-preconfigure --apt || true";}; DPkg::Post-Invoke { "if [ -x /usr/bin/debsums ]; then /usr/bin/debsums --generate=nocheck -sp /var/cache/apt/archives; fi"; }; Thank you for maintaining apt-get. Bob -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt depends on: ii debian-archive-keyring 2010.08.28 ii gnupg 1.4.11-3 ii libc6 2.13-21 ii libgcc1 1:4.6.1-15 ii libstdc++6 4.6.1-15 ii zlib1g 1:1.2.3.4.dfsg-3 apt recommends no packages. Versions of packages apt suggests: ii apt-doc 0.8.15.9 ii aptitude 0.6.4-1 ii bzip2 1.0.5-7 ii dpkg-dev 1.16.1.1 ii lzma 4.43-14 ii python-apt 0.8.0 ii synaptic 0.75.3
--- End Message ---
--- Begin Message ---Hello Bob, first of all: Thanks for your detailed bugreport! "Unfortunately" I have to say that this "new" behavior is not a bug… > Control files: lines which differ (wdiff format) > ------------------------------------------------ > Depends: m17n-db (>= [-1.5.0)-] {+1.6.3)+} > Description: [-a-] multilingual text processing library - contributed database > Installed-Size: [-1400-] {+1184+} > Recommends: libm17n-0 (>= [-1.5.0)-] {+1.6.3)+} > Version: [-1.1.12-2-] {+1.1.13-1+} The Recommends here is the bad thing: Currently libm17n-0 is only available in 1.6.2-3 - this means with an upgrade of m17n-contrib now we would break a previously satisfied Recommends which means the user might loose functionality without expecting it as 'upgrade' should be really conservative with a motto like: "Just get bugfixes, not new issues". (This carefulness regarding policy-breakage was introduced in 0.8.15.3) If you wouldn't install Recommends by default or you don't have libm17n-0 installed 'apt-get upgrade' would have the same result as 'dist-upgrade' as there is no policy to break, as it was already broken and therefore we don't have to fear that the user will loose functionality as it was already lost. (There is also no concept of less or more broken, policy breakage handling is binary, either it's broken or not, so if just one Recommends or twenty are missing is no difference for the "policy breakage detector") That we have no debug message telling us something like this is a bumper through, so followup versions will have a lovely debug-message added: Policy breaks with upgrade of foobar < x.y -> x.y.z > Thanks for the suggestion! Thanks also for your report again and sorry for closing it as not-a-bug-but-a-feature, but i hope it get clear with this description. If not feel free to ask/reopen it. Best regards David Kalnischkies
--- End Message ---
