Your message dated Wed, 18 May 2016 20:53:04 +0200 with message-id <20160518185304.GF3632@gnuservers.com.ar> and subject line Re: Bug#793618: baloo: fails to upgrade from jessie - apt does not find an upgrade path has caused the Debian Bug report #793618, regarding baloo: fails to upgrade from jessie - apt does not find an upgrade path 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 owner@bugs.debian.org immediately.) -- 793618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793618 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: baloo: fails to upgrade from jessie - apt does not find an upgrade path
- From: Andreas Beckmann <anbe@debian.org>
- Date: Sat, 25 Jul 2015 17:37:06 +0200
- Message-id: <20150725153706.16003.71600.reportbug@zam581.zam.kfa-juelich.de>
Package: baloo Version: 4:5.9.2-3 Severity: serious User: debian-qa@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'stretch' fails because apt did not find an upgrade path. >From the attached log (scroll to the bottom...): 1m43.7s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpHo82BY', 'apt-get', '-yf', 'dist-upgrade'] 4m18.7s DUMP: Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 2 Settings used to calculate pkgProblemResolver::Scores:: [...] 1 baloo-utils [ amd64 ] < 4:4.14.2-1 -> 4:4.14.2-1.1 > ( kde ) -1 baloo-kf5-data [ amd64 ] < none > ( none ) -1 baloo-kf5 [ amd64 ] < none -> 5.9.2-3 > ( utils ) -1 baloo [ amd64 ] < 4:4.14.2-1 -> 4:5.9.2-3 > ( oldlibs ) [...] Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) libgnutls-deb0-28 [ amd64 ] < 3.3.8-6+deb8u1 -> 3.3.16-1 > ( libs ) Broken libgnutls-deb0-28:amd64 Conflicts on libhogweed2 [ amd64 ] < 2.7.1-5 > ( libs ) Considering libhogweed2:amd64 -3 as a solution to libgnutls-deb0-28:amd64 18 Added libhogweed2:amd64 to the remove list Broken libgnutls-deb0-28:amd64 Conflicts on libnettle4 [ amd64 ] < 2.7.1-5 > ( libs ) Considering libnettle4:amd64 -2 as a solution to libgnutls-deb0-28:amd64 18 Added libnettle4:amd64 to the remove list Fixing libgnutls-deb0-28:amd64 via remove of libhogweed2:amd64 Fixing libgnutls-deb0-28:amd64 via remove of libnettle4:amd64 Investigating (0) baloo4 [ amd64 ] < 4:4.14.2-1 -> 4:4.14.2-1.1 > ( kde ) Broken baloo4:amd64 Conflicts on baloo-kf5 [ amd64 ] < none -> 5.9.2-3 > ( utils ) Considering baloo-kf5:amd64 -1 as a solution to baloo4:amd64 0 Added baloo-kf5:amd64 to the remove list Fixing baloo4:amd64 via keep of baloo-kf5:amd64 Investigating (0) baloo [ amd64 ] < 4:4.14.2-1 -> 4:5.9.2-3 > ( oldlibs ) Broken baloo:amd64 Depends on baloo-kf5 [ amd64 ] < none -> 5.9.2-3 > ( utils ) (>= 5.9.2) Considering baloo-kf5:amd64 -1 as a solution to baloo:amd64 -1 Holding Back baloo:amd64 rather than change baloo-kf5:amd64 Try to Re-Instate (1) baloo:amd64 Done [...] The following packages will be REMOVED: libhogweed2 libnettle4 The following NEW packages will be installed: The following packages have been kept back: baloo The following packages will be upgraded: [...] 138 upgraded, 38 newly installed, 2 to remove and 1 not upgraded. Hmm, why is baloo4 still in testing (or unstable)? Getting src:baloo removed from the archive should probably fix this. Let's see what would happen: anbe@coccia:~$ dak rm -Rn baloo Will remove the following packages from unstable: baloo | 4:4.14.2-1.1 | source baloo-dbg | 4:4.14.2-1.1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc baloo-dev | 4:4.14.2-1.1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc baloo-utils | 4:4.14.2-1.1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc baloo4 | 4:4.14.2-1.1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc libbaloocore4 | 4:4.14.2-1.1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc libbaloofiles4 | 4:4.14.2-1.1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc libbaloopim4 | 4:4.14.2-1.1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc libbalooqueryparser4 | 4:4.14.2-1.1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc libbalooxapian4 | 4:4.14.2-1.1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x, sparc Maintainer: Debian/Ubuntu Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> ------------------- Reason ------------------- ---------------------------------------------- Checking reverse dependencies... # Broken Depends: baloo-widgets: libbaloowidgets4 digikam: digikam-private-libs [amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc ppc64el s390x sparc] gwenview: gwenview kde-baseapps: dolphin kdepim: knotes libkdepim4 libmessagelist4 nepomuk-core: nepomuk-core-runtime # Broken Build-Depends: baloo-kcmadv: baloo-dev baloo-widgets: baloo-dev digikam: baloo-dev gwenview: baloo-dev (>= 4.13) kde-baseapps: baloo-dev kdepim: baloo-dev (>= 4:4.13) baloo-dev (>= 4:4.14) nepomuk-core: baloo-dev (>= 4:4.13.0) Dependency problem found. Looks like you need a baloo-dev transition ... cheers, AndreasAttachment: baloo.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
- To: Andreas Beckmann <anbe@debian.org>, 793618-done@bugs.debian.org
- Subject: Re: Bug#793618: baloo: fails to upgrade from jessie - apt does not find an upgrade path
- From: Maximiliano Curia <maxy@debian.org>
- Date: Wed, 18 May 2016 20:53:04 +0200
- Message-id: <20160518185304.GF3632@gnuservers.com.ar>
- In-reply-to: <20150725153706.16003.71600.reportbug__14761.4567577422$1437838789$gmane$org@zam581.zam.kfa-juelich.de>
- References: <20150725153706.16003.71600.reportbug__14761.4567577422$1437838789$gmane$org@zam581.zam.kfa-juelich.de>
Version: 4:5.16.0-1 ¡Hola Andreas! El 2015-07-25 a las 17:37 +0200, Andreas Beckmann escribió:Package: baloo Version: 4:5.9.2-3 Severity: serious User: debian-qa@lists.debian.org Usertags: piupartsduring a test with piuparts I noticed your package fails to upgrade from 'jessie'. It installed fine in 'jessie', then the upgrade to 'stretch' fails because apt did not find an upgrade path.This was fixed some versions ago, but we haven't tagged it as such.The upgrade from jessie to stretch seems to be working, or at least it worked in my chroot.Happy hacking, --Porque no respeta el orden natural en el que se leen las cosas¿Por qué contestar al principio del mensaje es malo?Saludos /\/\ /\ >< `/Attachment: signature.asc
Description: Digital signature
--- End Message ---