This bug was fixed in the package apt - 1.6.14
---
apt (1.6.14) bionic; urgency=medium
* RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026)
* Fix downloads of unsized files that are largest in pipeline (LP: #1921626),
and warn about packages without size
This bug was fixed in the package apt - 2.0.6
---
apt (2.0.6) focal; urgency=medium
* RunScripts: Do not reset SIGQUIT and SIGINT to SIG_DFL (LP: #1898026)
* test suite fix: Check for and discard expected warning from MaybeAddAuth
* Fix downloads of unsized files that are
bionic, 1.6.14 is good too.
root@b:~# python3 a.py
WAITING
^C
root@b:~# apt install libapt-pkg5.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
libfreetype6
Use 'apt
focal/2.0.6: The standalone test certainly worked, and the keyboard
interrupts were delivered to do-release-upgrade
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hello udippel, or anyone else affected,
Accepted apt into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.0.6 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package ubuntu-release-upgrader - 1:20.10.16
---
ubuntu-release-upgrader (1:20.10.16) groovy; urgency=medium
* DistUpgrade/DistUpgradeController.py: restore sources.list where possible
if a KeyboardInterrupt event is received and redirect the output of
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1898026
Title:
interruption of dist-upgrade can leave you next release in
sources.list
I tested and upgrade from a Focal system to Groovy using do-release-
upgrade -p and as you can see in the attached screenshot the "Inhibiting
until Ctrl+C is pressed" message no longer appears. So I'm setting this
to verification-done for ubuntu-release-upgrader.
** Attachment added:
On Mon, May 24, 2021, 8:20 AM Launchpad Bug Tracker <
1898...@bugs.launchpad.net> wrote:
> This bug was fixed in the package ubuntu-release-upgrader - 1:20.04.33
>
> ---
> ubuntu-release-upgrader (1:20.04.33) focal; urgency=medium
>
> * DistUpgrade/DistUpgradeController.py: restore
This bug was fixed in the package ubuntu-release-upgrader - 1:20.04.33
---
ubuntu-release-upgrader (1:20.04.33) focal; urgency=medium
* DistUpgrade/DistUpgradeController.py: restore sources.list where possible
if a KeyboardInterrupt event is received and redirect the output of
Hello udippel, or anyone else affected,
Accepted ubuntu-release-upgrader into groovy-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:20.10.16 in a few hours, and then in the
-proposed repository.
Please help us by testing
I tested and upgrade from a Bionic system to Focal using do-release-
upgrade -p and as you can see in the attached screenshot the "Inhibiting
until Ctrl+C is pressed" message no longer appears. So I'm setting this
to verification-done.
** Attachment added: "bug-1898026-focal-verification.png"
Hello udippel, or anyone else affected,
Accepted ubuntu-release-upgrader into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:20.04.33 in a few hours, and then in the
-proposed repository.
Please help us by testing
** Description changed:
[Impact]
Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have
set for them.
In case of ubuntu-release-upgrader, this results in the release upgrader
being
** Description changed:
[Impact]
Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have
set for them.
In case of ubuntu-release-upgrader, this results in the release upgrader
being
** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
Status: New => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: ubuntu-release-upgrader (Ubuntu Groovy)
Status: New => In Progress
**
This bug was fixed in the package apt - 2.1.10ubuntu0.3
---
apt (2.1.10ubuntu0.3) groovy; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
With respect to #12, I am not sufficiently well versed in rolling back to 18_04
in order to try once again, as much as I would love to do so and help by
repeating my earlier steps that lead to the upgrade.
Though, it looks like others have been able to simulate the steps.
Thanks a lot for all
I checked do-release-upgrade -d before upgrading apt, and pressing
Ctrl+C at the prompt for conforming changes left hirsute in
sources.list.
I upgraded to apt 2.1.10ubuntu0.3 from proposed, ran it again, and
Ctrl+C now caused the restore code to run:
Continue [yN] Details [d]^C
Restoring
The small simple script also worked with the proposed version:
# python3 a.py
WAITING
^CSeen KeyboardInterrupt()
END
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug notification because you are
Hello udippel, or anyone else affected,
Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
For the record, we are going to roll the apt change out in groovy
shortly, but delay the LTS updates to give it some more real world
testing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
This bug was fixed in the package ubuntu-release-upgrader - 1:21.04.5
---
ubuntu-release-upgrader (1:21.04.5) hirsute; urgency=medium
[ William 'jawn-smith' Wilson ]
* Add quirk to block upgrade if docker containers are configured to use the
aufs storage-driver (LP: #1907713)
** Description changed:
- As a long-time-user of ?ubuntu, with apt-get as tool of choice for
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
+ [Impact]
+ Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL,
** Also affects: apt (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects:
This bug was fixed in the package apt - 2.2.1
---
apt (2.2.1) unstable; urgency=medium
[ Julian Andres Klode ]
* Do not require force-loopbreak on Protected packages (Closes: #983014)
* Branch of as 2.2.y for bullseye
* configuration: Add missing #include
* Remove
** Changed in: apt (Ubuntu Hirsute)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1898026
Title:
interruption of dist-upgrade can
While a KeyboardInterrupt handler has been introduced to ubuntu-release-
upgrader apt is actually sending the SIGINT back to the distribution
upgrade process. This can be fixed in apt by removing the following:
--- apt-2.1.10ubuntu0.2/apt-pkg/contrib/fileutl.cc 2021-01-14
03:29:25.0
28 matches
Mail list logo
