| 2020-10-01 10:01:24 |
udippel |
bug |
|
|
added bug |
| 2020-10-05 21:45:35 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu): status |
New |
Incomplete |
|
| 2020-12-07 04:17:28 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu): status |
Incomplete |
Expired |
|
| 2020-12-07 16:21:54 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu): status |
Expired |
Confirmed |
|
| 2020-12-07 16:22:32 |
Brian Murray |
summary |
upgrade to 20.04 is quite invasive |
interruption of dist-upgrade can leave you next release in sources.list |
|
| 2020-12-07 16:22:40 |
Brian Murray |
tags |
amd64 apport-bug dist-upgrade focal |
amd64 apport-bug dist-upgrade focal rls-ff-incoming |
|
| 2021-01-14 16:21:40 |
Matthieu Clemenceau |
tags |
amd64 apport-bug dist-upgrade focal rls-ff-incoming |
amd64 apport-bug dist-upgrade focal fr-1056 rls-ff-incoming |
|
| 2021-01-14 16:54:17 |
Brian Murray |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-01-14 16:54:17 |
Brian Murray |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Hirsute) |
|
| 2021-01-14 16:54:29 |
Brian Murray |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 rls-ff-incoming |
amd64 apport-bug dist-upgrade focal fr-1056 |
|
| 2021-02-26 19:14:15 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Hirsute): assignee |
|
Brian Murray (brian-murray) |
|
| 2021-02-26 19:14:18 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Hirsute): status |
Confirmed |
In Progress |
|
| 2021-02-26 19:14:20 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Hirsute): importance |
Undecided |
High |
|
| 2021-02-26 20:29:41 |
Brian Murray |
bug task added |
|
apt (Ubuntu) |
|
| 2021-02-26 20:31:48 |
Brian Murray |
apt (Ubuntu Hirsute): importance |
Undecided |
High |
|
| 2021-02-26 20:31:48 |
Brian Murray |
apt (Ubuntu Hirsute): status |
New |
Triaged |
|
| 2021-02-26 20:32:03 |
Brian Murray |
apt (Ubuntu Hirsute): assignee |
|
Julian Andres Klode (juliank) |
|
| 2021-03-02 08:00:14 |
Julian Andres Klode |
apt (Ubuntu Hirsute): status |
Triaged |
Fix Committed |
|
| 2021-03-02 20:10:16 |
Launchpad Janitor |
apt (Ubuntu Hirsute): status |
Fix Committed |
Fix Released |
|
| 2021-03-04 15:54:22 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Focal |
|
| 2021-03-04 15:54:22 |
Julian Andres Klode |
bug task added |
|
apt (Ubuntu Focal) |
|
| 2021-03-04 15:54:22 |
Julian Andres Klode |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Focal) |
|
| 2021-03-04 15:54:22 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Groovy |
|
| 2021-03-04 15:54:22 |
Julian Andres Klode |
bug task added |
|
apt (Ubuntu Groovy) |
|
| 2021-03-04 15:54:22 |
Julian Andres Klode |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Groovy) |
|
| 2021-03-04 15:54:22 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Bionic |
|
| 2021-03-04 15:54:22 |
Julian Andres Klode |
bug task added |
|
apt (Ubuntu Bionic) |
|
| 2021-03-04 15:54:22 |
Julian Andres Klode |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Bionic) |
|
| 2021-03-04 15:54:36 |
Julian Andres Klode |
apt (Ubuntu Groovy): status |
New |
Triaged |
|
| 2021-03-05 18:58:34 |
Julian Andres Klode |
description |
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'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu version; just all packages including new ones. Version updates had to be initiated manually, and I was always asked if I really wanted the new ?ubuntu version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a number of times earlier; just to *check* if the upgrade was on offer; but this is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected through an adequate pipe? Are you sitting with full batteries; better a power supply?" would be convenient; since I am using my PC for urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481 |
[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 unable to handle interrupts after it did the initial update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(10000)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen KeyboardInterrupt, and importantly, also the END line.
[Where problems could occur]
apt: This specific change removes the two lines that SIG_DFL the signal handlers after running scripts. AFAWCT those lines are unnecessary - the code that calls it temporarily sets the handlers to SIG_IGN but restores previous handlers at the end; it was wrongly refactored decades ago. A regression could occur in that those signals will now continue to be ignored if we missed a spot.
[Original bug report]
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'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu version; just all packages including new ones. Version updates had to be initiated manually, and I was always asked if I really wanted the new ?ubuntu version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a number of times earlier; just to *check* if the upgrade was on offer; but this is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected through an adequate pipe? Are you sitting with full batteries; better a power supply?" would be convenient; since I am using my PC for urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481 |
|
| 2021-03-05 18:58:50 |
Julian Andres Klode |
apt (Ubuntu Groovy): status |
Triaged |
In Progress |
|
| 2021-03-05 21:56:49 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Hirsute): status |
In Progress |
Fix Released |
|
| 2021-03-24 22:34:27 |
Brian Murray |
apt (Ubuntu Groovy): status |
In Progress |
Fix Committed |
|
| 2021-03-24 22:34:30 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-03-24 22:34:34 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2021-03-24 22:34:41 |
Brian Murray |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 |
amd64 apport-bug dist-upgrade focal fr-1056 verification-needed verification-needed-groovy |
|
| 2021-03-30 15:05:45 |
Julian Andres Klode |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 verification-needed verification-needed-groovy |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done verification-done-groovy |
|
| 2021-04-06 18:04:32 |
Launchpad Janitor |
apt (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2021-04-06 18:04:56 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-05-14 00:34:10 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Focal): status |
New |
In Progress |
|
| 2021-05-14 00:34:10 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Focal): assignee |
|
Brian Murray (brian-murray) |
|
| 2021-05-14 00:34:29 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Groovy): status |
New |
In Progress |
|
| 2021-05-14 00:34:29 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Groovy): assignee |
|
Brian Murray (brian-murray) |
|
| 2021-05-14 16:47:04 |
Brian Murray |
description |
[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 unable to handle interrupts after it did the initial update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(10000)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen KeyboardInterrupt, and importantly, also the END line.
[Where problems could occur]
apt: This specific change removes the two lines that SIG_DFL the signal handlers after running scripts. AFAWCT those lines are unnecessary - the code that calls it temporarily sets the handlers to SIG_IGN but restores previous handlers at the end; it was wrongly refactored decades ago. A regression could occur in that those signals will now continue to be ignored if we missed a spot.
[Original bug report]
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'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu version; just all packages including new ones. Version updates had to be initiated manually, and I was always asked if I really wanted the new ?ubuntu version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a number of times earlier; just to *check* if the upgrade was on offer; but this is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected through an adequate pipe? Are you sitting with full batteries; better a power supply?" would be convenient; since I am using my PC for urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481 |
[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 unable to handle interrupts after it did the initial update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(10000)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen KeyboardInterrupt, and importantly, also the END line.
[[ubuntu-release-upgrader]]
1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
2) At the "Do you want to start the upgrade?" question say Y.
3) When you see the "Lock screen disabled" message you will also see "Inhibiting until Ctrl+C is pressed".
4) Press "Ctrl+C"
Your /etc/apt/sources.list file will now have focal in it instead of bionic although the upgrade has quit. With the version of ubuntu-release-upgrader in -proposed you will not see the "Ctrl+C" message. For your sources.list file to be restored you'll need the version of apt from bionic-proposed installed before starting the upgrade.
[Where problems could occur]apt: This specific change removes the two lines that SIG_DFL the signal handlers after running scripts. AFAWCT those lines are unnecessary - the code that calls it temporarily sets the handlers to SIG_IGN but restores previous handlers at the end; it was wrongly refactored decades ago. A regression could occur in that those signals will now continue to be ignored if we missed a spot.
[Original bug report]
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'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu version; just all packages including new ones. Version updates had to be initiated manually, and I was always asked if I really wanted the new ?ubuntu version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a number of times earlier; just to *check* if the upgrade was on offer; but this is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected through an adequate pipe? Are you sitting with full batteries; better a power supply?" would be convenient; since I am using my PC for urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481 |
|
| 2021-05-14 16:57:23 |
Brian Murray |
description |
[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 unable to handle interrupts after it did the initial update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(10000)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen KeyboardInterrupt, and importantly, also the END line.
[[ubuntu-release-upgrader]]
1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
2) At the "Do you want to start the upgrade?" question say Y.
3) When you see the "Lock screen disabled" message you will also see "Inhibiting until Ctrl+C is pressed".
4) Press "Ctrl+C"
Your /etc/apt/sources.list file will now have focal in it instead of bionic although the upgrade has quit. With the version of ubuntu-release-upgrader in -proposed you will not see the "Ctrl+C" message. For your sources.list file to be restored you'll need the version of apt from bionic-proposed installed before starting the upgrade.
[Where problems could occur]apt: This specific change removes the two lines that SIG_DFL the signal handlers after running scripts. AFAWCT those lines are unnecessary - the code that calls it temporarily sets the handlers to SIG_IGN but restores previous handlers at the end; it was wrongly refactored decades ago. A regression could occur in that those signals will now continue to be ignored if we missed a spot.
[Original bug report]
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'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu version; just all packages including new ones. Version updates had to be initiated manually, and I was always asked if I really wanted the new ?ubuntu version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a number of times earlier; just to *check* if the upgrade was on offer; but this is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected through an adequate pipe? Are you sitting with full batteries; better a power supply?" would be convenient; since I am using my PC for urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481 |
[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 unable to handle interrupts after it did the initial update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(10000)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen KeyboardInterrupt, and importantly, also the END line.
[[ubuntu-release-upgrader]]
1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
2) At the "Do you want to start the upgrade?" question say Y.
3) When you see the "Lock screen disabled" message you will also see "Inhibiting until Ctrl+C is pressed".
4) Press "Ctrl+C"
Your /etc/apt/sources.list file will now have focal in it instead of bionic although the upgrade has quit. With the version of ubuntu-release-upgrader in -proposed you will not see the "Ctrl+C" message. For your sources.list file to be restored you'll need the version of apt from bionic-proposed installed before starting the upgrade.
[Where problems could occur]
apt: This specific change removes the two lines that SIG_DFL the signal handlers after running scripts. AFAWCT those lines are unnecessary - the code that calls it temporarily sets the handlers to SIG_IGN but restores previous handlers at the end; it was wrongly refactored decades ago. A regression could occur in that those signals will now continue to be ignored if we missed a spot.
ubuntu-release-upgrader: The change is wrapping a bunch of code in a try: except: block so if the indentation was off the pyflakes / pycodestyle tests would fail but autopkgtest will catch that.
[Original bug report]
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'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu version; just all packages including new ones. Version updates had to be initiated manually, and I was always asked if I really wanted the new ?ubuntu version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a number of times earlier; just to *check* if the upgrade was on offer; but this is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected through an adequate pipe? Are you sitting with full batteries; better a power supply?" would be convenient; since I am using my PC for urgent duties, and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481 |
|
| 2021-05-14 19:10:21 |
Steve Langasek |
ubuntu-release-upgrader (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2021-05-14 19:10:26 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-05-14 19:10:32 |
Steve Langasek |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done verification-done-groovy |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-groovy verification-needed verification-needed-focal |
|
| 2021-05-17 22:33:02 |
Brian Murray |
attachment added |
|
bug-1898026-focal-verification.png https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898026/+attachment/5498327/+files/bug-1898026-focal-verification.png |
|
| 2021-05-17 22:33:27 |
Brian Murray |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-groovy verification-needed verification-needed-focal |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-focal verification-done-groovy verification-needed |
|
| 2021-05-24 10:11:40 |
Łukasz Zemczak |
ubuntu-release-upgrader (Ubuntu Groovy): status |
In Progress |
Fix Committed |
|
| 2021-05-24 10:11:47 |
Łukasz Zemczak |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-focal verification-done-groovy verification-needed |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-focal verification-needed verification-needed-groovy |
|
| 2021-05-24 15:14:22 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-05-26 23:10:34 |
Brian Murray |
attachment added |
|
bug-1898026-groovy-verification.png https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898026/+attachment/5500595/+files/bug-1898026-groovy-verification.png |
|
| 2021-05-26 23:12:24 |
Brian Murray |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-focal verification-needed verification-needed-groovy |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-focal verification-done-groovy verification-needed |
|
| 2021-05-28 08:22:04 |
Mathew Hodson |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-focal verification-done-groovy verification-needed |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-focal verification-done-groovy |
|
| 2021-06-03 00:04:58 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2021-06-17 18:16:43 |
Brian Murray |
apt (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2021-06-17 18:16:52 |
Brian Murray |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-focal verification-done-groovy |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-groovy verification-needed verification-needed-focal |
|
| 2021-06-17 18:20:50 |
Brian Murray |
apt (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2021-06-17 18:20:59 |
Brian Murray |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-groovy verification-needed verification-needed-focal |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-groovy verification-needed verification-needed-bionic verification-needed-focal |
|
| 2021-06-24 09:44:08 |
Julian Andres Klode |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-groovy verification-needed verification-needed-bionic verification-needed-focal |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-focal verification-done-groovy verification-needed verification-needed-bionic |
|
| 2021-06-24 09:52:12 |
Julian Andres Klode |
tags |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done-focal verification-done-groovy verification-needed verification-needed-bionic |
amd64 apport-bug dist-upgrade focal fr-1056 verification-done verification-done-bionic verification-done-focal verification-done-groovy |
|
| 2021-07-01 22:17:42 |
Launchpad Janitor |
apt (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-07-01 22:28:14 |
Launchpad Janitor |
apt (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
