Unlooping all the trigger loops!!!!!

Status changed to 'Confirmed' because the bug affects multiple users.

I could verify this bug report in a lxd container and that dpkg 1.19.7 (not yet merged) fixes the issue.

cosmic is reaching eol in 8 days, removing that task.

SRUs uploaded for all releases. git branches in

https://code.launchpad.net/~juliank/ubuntu/+source/dpkg/+git/dpkg

with individual cherry-picked commits (git ubuntu import + cherry-picked commits from upstream git :D)

Hello Brian, or anyone else affected,

Accepted dpkg into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpkg/1.19.6ubuntu1.1 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 on 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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Brian, or anyone else affected,

Accepted dpkg into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpkg/1.19.0.5ubuntu2.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 on 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Brian, or anyone else affected,

Accepted dpkg into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpkg/1.18.4ubuntu1.6 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 on 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted dpkg (1.18.4ubuntu1.6) for xenial have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures.

https://people.canonical.com/~ubuntu-archive/pending-sru.html#xenial

Hello Brian, or anyone else affected,

Accepted dpkg into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dpkg/1.19.0.5ubuntu5.1 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 on 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted dpkg (1.19.0.5ubuntu2.2) for bionic have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures.

https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic

All autopkgtests for the newly accepted dpkg (1.19.6ubuntu1.1) for disco have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures.

https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco

All autopkgtests for the newly accepted dpkg (1.19.0.5ubuntu5.1) for cosmic have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures.

https://people.canonical.com/~ubuntu-archive/pending-sru.html#cosmic

I just finished verifying the cosmic->disco upgrade (the reproducer). What is important:

- enable -proposed in your sources.list
- add below pinning for it
- install the proposed dpkg

Only then start the upgrade, so that you get a fixed dpkg before and after the upgrade.

Pinning:
# cat /etc/apt/preferences.d/dpkg
Package: dpkg
Pin: release *-proposed
Pin-Priority: 500

Package: *
Pin: release *-proposed
Pin-Priority: -1

autopkgtest regressions have been fixed except for

apport/xenial which is not a regression (needs a fix eventually to adjust for linux-signed changes)
kdeconnect/bionic which has a _very_ flaky test

So: autopkgtest-wise it's good to go, but need some more upgrade testing for releases other than cosmic -> disco.

testing procedure:

For each test:
- multipass launch $release -d 10G
- Installed new dpkg from proposed
- Installed ubuntu-desktop
- Ran do-release-upgrade

the individual runs were:
- Installed xenial (1.18.4ubuntu1.6), upgraded to bionic (1.19.0.5ubuntu2.2)
- Installed bionic (1.19.0.5ubuntu2.2), upgraded to disco (1.19.6ubuntu1.1)

I tried upgrading all the way from xenial to eoan, but it broke down after the bionic->disco update which somehow went wrong in lxd snap transition somewhere or something.

disco->eoan WIP

disco:

Installed disco 1.19.6ubuntu1.1, upgraded to eoan.

The verification of the Stable Release Update for dpkg 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.

This bug was fixed in the package dpkg - 1.19.6ubuntu1.1

---------------
dpkg (1.19.6ubuntu1.1) disco; urgency=medium

  * Cherry-pick upstream fix for trigger loops (LP: #1828639):
    - dpkg: Split the trigger dependtry into two, the second of which will be
      the one checking trigger cycles when deferring trigger processing due to
      unsatisfiable dependencies. Closes: #928429

 -- Julian Andres Klode <email address hidden> Tue, 16 Jul 2019 14:32:06 +0200

This bug was fixed in the package dpkg - 1.18.4ubuntu1.6

---------------
dpkg (1.18.4ubuntu1.6) xenial; urgency=medium

  * Cherry-pick upstream fixes for trigger loops (LP: #1828639)
    - dpkg: Negate tortoise_not_in_hare() function name and return value
    - dpkg: Initialize trigcyclenode's next member once
    - dpkg: Factor trigproc_new_cyclenode() out from check_trigger_cycle()
    - dpkg: Mark the package we are giving up on a trigger cycle as istobe normal
    - dpkg: Switch dependtry from an int to an enum
    - dpkg: Reset progress_bytrigproc once we have injected into the current iteration
    - dpkg: Split trigger processing types into required, try-queued and try-deferred
    - dpkg: Convert one trigger processing required type into the new try-queued
    - dpkg: Move trigproc cycle reset inside try-deferred conditional
    - dpkg: Introduce a new dependency try level for trigger processing
    - dpkg: Introduce a new dependency try level for trigger cycle checks

 -- Julian Andres Klode <email address hidden> Tue, 16 Jul 2019 14:57:11 +0200

This bug was fixed in the package dpkg - 1.19.0.5ubuntu2.2

---------------
dpkg (1.19.0.5ubuntu2.2) bionic; urgency=medium

  * Cherry-pick upstream fixes for trigger loops (LP: #1828639)
    - dpkg: Negate tortoise_not_in_hare() function name and return value
    - dpkg: Initialize trigcyclenode's next member once
    - dpkg: Factor trigproc_new_cyclenode() out from check_trigger_cycle()
    - dpkg: Mark the package we are giving up on a trigger cycle as istobe normal
    - dpkg: Switch dependtry from an int to an enum
    - dpkg: Reset progress_bytrigproc once we have injected into the current iteration
    - dpkg: Split trigger processing types into required, try-queued and try-deferred
    - dpkg: Convert one trigger processing required type into the new try-queued
    - dpkg: Move trigproc cycle reset inside try-deferred conditional
    - dpkg: Introduce a new dependency try level for trigger processing
    - dpkg: Introduce a new dependency try level for trigger cycle checks

 -- Julian Andres Klode <email address hidden> Tue, 16 Jul 2019 14:57:11 +0200