| 2018-10-04 21:17:48 |
Paul Larson |
bug |
|
|
added bug |
| 2019-03-29 16:50:18 |
Brian Murray |
tags |
|
rls-ee-incoming |
|
| 2019-03-29 16:50:44 |
Brian Murray |
bug |
|
|
added subscriber David Ames |
| 2019-03-29 16:51:22 |
Brian Murray |
bug |
|
|
added subscriber Brian Murray |
| 2019-05-09 15:24:55 |
Julian Andres Klode |
apt (Ubuntu): importance |
Undecided |
Medium |
|
| 2019-05-09 19:59:04 |
Brian Murray |
bug task added |
|
ubuntu-release-upgrader (Ubuntu) |
|
| 2019-05-09 19:59:22 |
Launchpad Janitor |
apt (Ubuntu): status |
New |
Confirmed |
|
| 2019-05-09 19:59:22 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu): status |
New |
Confirmed |
|
| 2019-05-09 20:01:50 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu): status |
Confirmed |
Triaged |
|
| 2019-05-09 20:01:52 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu): importance |
Undecided |
Medium |
|
| 2019-05-09 20:33:23 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu): status |
Triaged |
In Progress |
|
| 2019-05-09 20:33:25 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu): assignee |
|
Brian Murray (brian-murray) |
|
| 2019-05-09 20:46:55 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu-release-upgrader |
|
| 2019-05-09 20:47:12 |
Brian Murray |
tags |
rls-ee-incoming |
|
|
| 2019-05-09 20:47:21 |
Brian Murray |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-05-09 20:47:21 |
Brian Murray |
bug task added |
|
apt (Ubuntu Eoan) |
|
| 2019-05-09 20:47:21 |
Brian Murray |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Eoan) |
|
| 2019-05-09 21:32:33 |
Brian Murray |
apt (Ubuntu Eoan): status |
Confirmed |
Incomplete |
|
| 2019-05-10 19:40:03 |
Brian Murray |
summary |
unattended do-release-upgrade asks about /etc/cron.daily/apt-compat |
DistUpgradeViewNonInteractive crashes / requires interaction |
|
| 2019-05-10 19:40:36 |
Brian Murray |
nominated for series |
|
Ubuntu Disco |
|
| 2019-05-10 19:40:36 |
Brian Murray |
bug task added |
|
apt (Ubuntu Disco) |
|
| 2019-05-10 19:40:36 |
Brian Murray |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Disco) |
|
| 2019-05-10 19:40:36 |
Brian Murray |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-05-10 19:40:36 |
Brian Murray |
bug task added |
|
apt (Ubuntu Cosmic) |
|
| 2019-05-10 19:40:36 |
Brian Murray |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Cosmic) |
|
| 2019-05-10 19:40:45 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Disco): status |
New |
In Progress |
|
| 2019-05-10 19:40:47 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Disco): assignee |
|
Brian Murray (brian-murray) |
|
| 2019-05-10 19:40:49 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Cosmic): status |
New |
In Progress |
|
| 2019-05-10 19:40:51 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Cosmic): assignee |
|
Brian Murray (brian-murray) |
|
| 2019-05-10 21:35:40 |
Brian Murray |
description |
I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input.
Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot.
To avoid interactive responses, I'm using:
$ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive
Part way through the upgrade, I do get prompted for something though:
Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...
Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory
Setting up apt (1.6.3ubuntu0.1) ...
Installing new version of config file /etc/apt/apt.conf.d/01autoremove ...
Configuration file '/etc/cron.daily/apt-compat'
==> Deleted (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same:
In /var/log/dist-upgrade/main.log, I also found this:
2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat'
2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile |
[Impact]
The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing.
[Test Case]
You need to create a situation where you'll receive a conffile prompt since the handling of those is broken.
1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal
2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade
3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log
"2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades'
2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile"
With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging.
[Regression Potential]
The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one.
[Original Description]
I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input.
Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot.
To avoid interactive responses, I'm using:
$ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive
Part way through the upgrade, I do get prompted for something though:
Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...
Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory
Setting up apt (1.6.3ubuntu0.1) ...
Installing new version of config file /etc/apt/apt.conf.d/01autoremove ...
Configuration file '/etc/cron.daily/apt-compat'
==> Deleted (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same:
In /var/log/dist-upgrade/main.log, I also found this:
2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat'
2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile |
|
| 2019-05-10 21:42:21 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Eoan): status |
In Progress |
Fix Released |
|
| 2019-05-10 22:19:48 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/ubuntu/disco/ubuntu-release-upgrader/disco |
|
| 2019-05-11 12:37:54 |
Francis Ginther |
tags |
|
id-5cd5d40bf1c69c651a522b2f |
|
| 2019-05-13 22:06:45 |
Brian Murray |
description |
[Impact]
The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing.
[Test Case]
You need to create a situation where you'll receive a conffile prompt since the handling of those is broken.
1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal
2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade
3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log
"2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades'
2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile"
With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging.
[Regression Potential]
The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one.
[Original Description]
I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input.
Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot.
To avoid interactive responses, I'm using:
$ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive
Part way through the upgrade, I do get prompted for something though:
Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...
Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory
Setting up apt (1.6.3ubuntu0.1) ...
Installing new version of config file /etc/apt/apt.conf.d/01autoremove ...
Configuration file '/etc/cron.daily/apt-compat'
==> Deleted (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same:
In /var/log/dist-upgrade/main.log, I also found this:
2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat'
2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile |
[Impact]
The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing.
[Test Case]
You need to create a situation where you'll receive a conffile prompt since the handling of those is broken.
1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal
2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade
3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log
"2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades'
2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile"
With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging.
[Regression Potential]
The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong.
[Original Description]
I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input.
Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot.
To avoid interactive responses, I'm using:
$ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive
Part way through the upgrade, I do get prompted for something though:
Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...
Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory
Setting up apt (1.6.3ubuntu0.1) ...
Installing new version of config file /etc/apt/apt.conf.d/01autoremove ...
Configuration file '/etc/cron.daily/apt-compat'
==> Deleted (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same:
In /var/log/dist-upgrade/main.log, I also found this:
2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat'
2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile |
|
| 2019-05-14 15:40:54 |
Łukasz Zemczak |
ubuntu-release-upgrader (Ubuntu Disco): status |
In Progress |
Fix Committed |
|
| 2019-05-14 15:40:56 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-05-14 15:40:58 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2019-05-14 15:41:03 |
Łukasz Zemczak |
tags |
id-5cd5d40bf1c69c651a522b2f |
id-5cd5d40bf1c69c651a522b2f verification-needed verification-needed-disco |
|
| 2019-05-14 15:42:19 |
Łukasz Zemczak |
ubuntu-release-upgrader (Ubuntu Cosmic): status |
In Progress |
Fix Committed |
|
| 2019-05-14 15:42:24 |
Łukasz Zemczak |
tags |
id-5cd5d40bf1c69c651a522b2f verification-needed verification-needed-disco |
id-5cd5d40bf1c69c651a522b2f verification-needed verification-needed-cosmic verification-needed-disco |
|
| 2019-05-14 23:02:55 |
Brian Murray |
description |
[Impact]
The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing.
[Test Case]
You need to create a situation where you'll receive a conffile prompt since the handling of those is broken.
1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal
2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade
3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log
"2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades'
2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile"
With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging.
[Regression Potential]
The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong.
[Original Description]
I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input.
Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot.
To avoid interactive responses, I'm using:
$ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive
Part way through the upgrade, I do get prompted for something though:
Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...
Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory
Setting up apt (1.6.3ubuntu0.1) ...
Installing new version of config file /etc/apt/apt.conf.d/01autoremove ...
Configuration file '/etc/cron.daily/apt-compat'
==> Deleted (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same:
In /var/log/dist-upgrade/main.log, I also found this:
2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat'
2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile |
[Impact]
The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing.
[Test Case]
You need to create a situation where you'll receive a conffile prompt since the handling of those is broken.
1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal
2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive
3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log
"2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades'
2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile"
With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging.
[Regression Potential]
The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong.
[Original Description]
I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input.
Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot.
To avoid interactive responses, I'm using:
$ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive
Part way through the upgrade, I do get prompted for something though:
Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ...
Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory
Setting up apt (1.6.3ubuntu0.1) ...
Installing new version of config file /etc/apt/apt.conf.d/01autoremove ...
Configuration file '/etc/cron.daily/apt-compat'
==> Deleted (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same:
In /var/log/dist-upgrade/main.log, I also found this:
2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat'
2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile |
|
| 2019-05-15 05:09:26 |
Brian Murray |
tags |
id-5cd5d40bf1c69c651a522b2f verification-needed verification-needed-cosmic verification-needed-disco |
id-5cd5d40bf1c69c651a522b2f verification-done-cosmic verification-needed verification-needed-disco |
|
| 2019-05-15 16:49:04 |
Brian Murray |
tags |
id-5cd5d40bf1c69c651a522b2f verification-done-cosmic verification-needed verification-needed-disco |
id-5cd5d40bf1c69c651a522b2f verification-done verification-done-cosmic verification-done-disco |
|
| 2019-05-15 17:31:25 |
Brian Murray |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-05-15 17:31:25 |
Brian Murray |
bug task added |
|
apt (Ubuntu Bionic) |
|
| 2019-05-15 17:31:25 |
Brian Murray |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Bionic) |
|
| 2019-05-15 17:34:06 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Bionic): status |
New |
In Progress |
|
| 2019-05-15 17:34:06 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Bionic): assignee |
|
Brian Murray (brian-murray) |
|
| 2019-05-16 17:32:11 |
Łukasz Zemczak |
ubuntu-release-upgrader (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-05-16 17:32:18 |
Łukasz Zemczak |
tags |
id-5cd5d40bf1c69c651a522b2f verification-done verification-done-cosmic verification-done-disco |
id-5cd5d40bf1c69c651a522b2f verification-done-cosmic verification-done-disco verification-needed verification-needed-bionic |
|
| 2019-05-17 21:36:25 |
Paul Larson |
tags |
id-5cd5d40bf1c69c651a522b2f verification-done-cosmic verification-done-disco verification-needed verification-needed-bionic |
id-5cd5d40bf1c69c651a522b2f verification-done-bionic verification-done-cosmic verification-done-disco verification-needed |
|
| 2019-05-22 15:09:37 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-05-22 15:09:42 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-05-22 15:25:03 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-05-22 15:26:55 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-09-19 13:31:38 |
Brian Murray |
apt (Ubuntu Eoan): status |
Incomplete |
Invalid |
|
| 2019-10-09 06:25:45 |
Launchpad Janitor |
apt (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2019-10-09 06:25:45 |
Launchpad Janitor |
apt (Ubuntu Cosmic): status |
New |
Confirmed |
|
| 2019-10-09 06:25:45 |
Launchpad Janitor |
apt (Ubuntu Disco): status |
New |
Confirmed |
|
| 2020-07-02 20:00:01 |
Steve Langasek |
apt (Ubuntu Disco): status |
Confirmed |
Won't Fix |
|
| 2021-02-18 15:46:52 |
Julian Andres Klode |
apt (Ubuntu Cosmic): status |
Confirmed |
Invalid |
|
| 2021-02-18 15:47:02 |
Julian Andres Klode |
apt (Ubuntu Bionic): status |
Confirmed |
Invalid |
|
