cache marking worked without resolution

Bug #1358291 reported by Jonathan Riddell
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libqapt (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Fix Released
Undecided
Unassigned
Utopic
Fix Released
Undecided
Unassigned

Bug Description

libqapt in trusty has a bug because of a change in apt where it marks the cache after the resolver resolved.

This effectively meant that the cache marking worked without resolution ultimately resulting in a broken cache.

http://quickgit.kde.org/?p=libqapt.git&a=commitdiff&h=48ca41c210c30e75817d7559cdf8bad7ceab141c&hp=2dc82ff1668d3d6983d226dd93b0b75702dedf48&o=plain

relevant discussion thread that lead to the breakage:
https://lists.ubuntu.com/archives/kubuntu-devel/2013-December/007623.html

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libqapt - 2.2.0-0ubuntu2

---------------
libqapt (2.2.0-0ubuntu2) utopic; urgency=medium

  * Add upstream_fix-package-remove-resolver.diff LP: #1358291
    cache marking worked without resolution
 -- Jonathan Riddell <email address hidden> Mon, 18 Aug 2014 15:35:24 +0200

Changed in libqapt (Ubuntu Utopic):
status: New → Fix Released
Revision history for this message
Jonathan Riddell (jr) wrote :

TEST CASE:
Install qtcreator
With muon remove qtcreator, it will give an error that it can not be marked for removal with the old version but will successfully remove with the new libqapt version

Uploaded to utopic
Uploaded to trusty awaiting ~ubuntu-sru

Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Jonathan, or anyone else affected,

Accepted libqapt into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libqapt/2.1.70-0ubuntu4.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in libqapt (Ubuntu Trusty):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Michał Zając (quintasan) wrote :

Just installed libqapt2 2.1.70-0ubuntu4.2 from trusty-proposed and I can confirm that it resolves the issue. I have not noticed any other problems.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libqapt - 2.1.70-0ubuntu4.2

---------------
libqapt (2.1.70-0ubuntu4.2) trusty; urgency=medium

  * Add upstream_fix-package-remove-resolver.diff LP: #1358291
    ensure package resolution happens after cache is marked
 -- Jonathan Riddell <email address hidden> Mon, 18 Aug 2014 15:26:22 +0200

Changed in libqapt (Ubuntu Trusty):
status: Fix Committed → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Update Released

The verification of the Stable Release Update for libqapt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.