Running 'aptitude update' clears hold flags on packages

Bug #1817350 reported by Mike Nguyen on 2019-02-22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aptitude (Ubuntu)

Bug Description

When running an 'aptitude update' for the very first time, it seems to clear up any hold flags that were previous put in place via 'apt-mark hold <package>'.

root@cb-qa-lb-1:~# lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04

root@cb-qa-lb-1:~# apt-cache policy aptitude
  Installed: 0.8.10-6ubuntu1
  Candidate: 0.8.10-6ubuntu1
  Version table:
 *** 0.8.10-6ubuntu1 500
        500 bionic/main amd64 Packages
        100 /var/lib/dpkg/status

When a 'hold' flag is set on a package, it should be kept. Doing an 'aptitude update' should not be clearing these package flags. This is not the case as the hold flag is getting removed.

All 'hold' flags on packages that were previously set get cleared.

Upon running 'aptitude update', it seems to create /var/lib/aptitude/pkgstates, and also update /var/lib/dpkg/status, which seems to remove any flags on packages that were present.

Pastebin here with some output:

This only seems to happen when running 'aptitude update' on an initial run. Doing an 'apt update' does not cause any issue.

Note that running subsequent 'aptitude update' with /var/lib/aptitude/pkgstates already existing does not seem to cause any issue anymore and any hold flags that get set are kept.

Mike Nguyen (moozoo) wrote :

I should note that I've also tested this on 16.04.6 and am getting the same unexpected behaviour.

root@ansible:/var/lib/aptitude# lsb_release -rd
Description: Ubuntu 16.04.6 LTS
Release: 16.04

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

Other bug subscribers