| 2020-04-25 15:29:07 |
Saverio Miroddi |
bug |
|
|
added bug |
| 2020-04-25 15:39:24 |
Saverio Miroddi |
summary |
Ubiquit 20.04 interferes with existing ZFS pools, making them "disappear" |
Ubiquity 20.04 interferes with existing ZFS pools, making them "disappear" |
|
| 2020-04-25 17:52:07 |
Jean-Baptiste Lallement |
tags |
amd64 apport-bug focal ubiquity-20.04.15 ubuntu-mate |
amd64 apport-bug focal ubiquity-20.04.15 ubuntu-mate zfs |
|
| 2020-04-25 22:22:19 |
Saverio Miroddi |
summary |
Ubiquity 20.04 interferes with existing ZFS pools, making them "disappear" |
Ubiquity 20.04 exports existing ZFS pools |
|
| 2020-04-25 22:22:54 |
Saverio Miroddi |
description |
For unclear reasons (18.04 didn't have this issue), Ubiquity on 20.04 interferes with existing ZFS pools, making them "disappear" (it's not clear what exactly happens).
To repeat (assumes a `/dev/sda` disk):
- start a 20.04 Ubuntu Desktop live media
- open a terminal
- create a zfs pool: `zpool create test /dev/sda`
- verify that it's been created: `zpool list`
- launch ubiquity: `ubiquity`
- open a separate terminal
- list the ZFS pools: `zpool list`
no pools are now listed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/vmlinuz
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: MATE
Date: Sat Apr 25 15:21:25 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
For unclear reasons (18.04 didn't have this issue), Ubiquity on 20.04 exports existing ZFS pools, (very) shortly after execution.
To repeat (assumes a `/dev/sda` disk):
- start a 20.04 Ubuntu Desktop live media
- open a terminal
- create a zfs pool: `zpool create test /dev/sda`
- verify that it's been created: `zpool list`
- launch ubiquity: `ubiquity`
- open a separate terminal
- list the ZFS pools: `zpool list`
no pools are now listed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/vmlinuz
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: MATE
Date: Sat Apr 25 15:21:25 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2020-04-27 14:19:50 |
Jean-Baptiste Lallement |
ubiquity (Ubuntu): status |
New |
Triaged |
|
| 2020-04-27 14:19:52 |
Jean-Baptiste Lallement |
ubiquity (Ubuntu): importance |
Undecided |
Low |
|
| 2020-05-27 15:19:42 |
Jean-Baptiste Lallement |
ubiquity (Ubuntu): assignee |
|
Jean-Baptiste Lallement (jibel) |
|
| 2020-05-28 07:39:58 |
Jean-Baptiste Lallement |
ubiquity (Ubuntu): status |
Triaged |
In Progress |
|
| 2020-05-28 08:20:22 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~jibel/ubiquity/+git/ubiquity-1/+merge/384701 |
|
| 2020-05-28 13:01:47 |
Jean-Baptiste Lallement |
ubiquity (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2020-06-03 02:04:16 |
Launchpad Janitor |
ubiquity (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2020-06-16 10:38:46 |
Dimitri John Ledkov |
description |
For unclear reasons (18.04 didn't have this issue), Ubiquity on 20.04 exports existing ZFS pools, (very) shortly after execution.
To repeat (assumes a `/dev/sda` disk):
- start a 20.04 Ubuntu Desktop live media
- open a terminal
- create a zfs pool: `zpool create test /dev/sda`
- verify that it's been created: `zpool list`
- launch ubiquity: `ubiquity`
- open a separate terminal
- list the ZFS pools: `zpool list`
no pools are now listed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/vmlinuz
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: MATE
Date: Sat Apr 25 15:21:25 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
===
For unclear reasons (18.04 didn't have this issue), Ubiquity on 20.04 exports existing ZFS pools, (very) shortly after execution.
To repeat (assumes a `/dev/sda` disk):
- start a 20.04 Ubuntu Desktop live media
- open a terminal
- create a zfs pool: `zpool create test /dev/sda`
- verify that it's been created: `zpool list`
- launch ubiquity: `ubiquity`
- open a separate terminal
- list the ZFS pools: `zpool list`
no pools are now listed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/vmlinuz
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: MATE
Date: Sat Apr 25 15:21:25 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2020-06-16 10:40:57 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~xnox/ubiquity/+git/ubiquity/+merge/385805 |
|
| 2020-06-24 13:21:25 |
Jean-Baptiste Lallement |
description |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
[Regression Potential]
* discussion of how regressions are most likely to manifest as a result of this change.
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
===
For unclear reasons (18.04 didn't have this issue), Ubiquity on 20.04 exports existing ZFS pools, (very) shortly after execution.
To repeat (assumes a `/dev/sda` disk):
- start a 20.04 Ubuntu Desktop live media
- open a terminal
- create a zfs pool: `zpool create test /dev/sda`
- verify that it's been created: `zpool list`
- launch ubiquity: `ubiquity`
- open a separate terminal
- list the ZFS pools: `zpool list`
no pools are now listed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/vmlinuz
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: MATE
Date: Sat Apr 25 15:21:25 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
[Impact]
* Ubiquity unmounts everything that could be mounted on the target file system when it starts and on tear down. For ZFS it exports all the pools.
* If a user had existing pools, they are exported too.
* This fix only unmount pool that are used as a target for the installation, leaving alone any other pool.
[Test Case]
1. Boot a live session
2. Create a new pool with:
$ zpool create -R /mnt tpool /dev/vda
3. Verify that the pool is created with zpool list
4. Start ubiquity
5. Quit ubiquity
=> Verify that the pool is still there with zpool list. Without the fix, tpool is exported.
[Regression Potential]
* Low risk of regression. Worst case, the bug is not fixed and pools are still unmounted.
===
For unclear reasons (18.04 didn't have this issue), Ubiquity on 20.04 exports existing ZFS pools, (very) shortly after execution.
To repeat (assumes a `/dev/sda` disk):
- start a 20.04 Ubuntu Desktop live media
- open a terminal
- create a zfs pool: `zpool create test /dev/sda`
- verify that it's been created: `zpool list`
- launch ubiquity: `ubiquity`
- open a separate terminal
- list the ZFS pools: `zpool list`
no pools are now listed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/vmlinuz
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: MATE
Date: Sat Apr 25 15:21:25 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2020-06-24 13:21:31 |
Jean-Baptiste Lallement |
nominated for series |
|
Ubuntu Focal |
|
| 2020-06-24 13:21:31 |
Jean-Baptiste Lallement |
bug task added |
|
ubiquity (Ubuntu Focal) |
|
| 2020-06-24 13:22:59 |
Jean-Baptiste Lallement |
description |
[Impact]
* Ubiquity unmounts everything that could be mounted on the target file system when it starts and on tear down. For ZFS it exports all the pools.
* If a user had existing pools, they are exported too.
* This fix only unmount pool that are used as a target for the installation, leaving alone any other pool.
[Test Case]
1. Boot a live session
2. Create a new pool with:
$ zpool create -R /mnt tpool /dev/vda
3. Verify that the pool is created with zpool list
4. Start ubiquity
5. Quit ubiquity
=> Verify that the pool is still there with zpool list. Without the fix, tpool is exported.
[Regression Potential]
* Low risk of regression. Worst case, the bug is not fixed and pools are still unmounted.
===
For unclear reasons (18.04 didn't have this issue), Ubiquity on 20.04 exports existing ZFS pools, (very) shortly after execution.
To repeat (assumes a `/dev/sda` disk):
- start a 20.04 Ubuntu Desktop live media
- open a terminal
- create a zfs pool: `zpool create test /dev/sda`
- verify that it's been created: `zpool list`
- launch ubiquity: `ubiquity`
- open a separate terminal
- list the ZFS pools: `zpool list`
no pools are now listed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/vmlinuz
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: MATE
Date: Sat Apr 25 15:21:25 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
[Impact]
* Ubiquity unmounts everything that could be mounted on the target file system when it starts and on tear down. For ZFS it exports all the pools.
* If a user had existing pools, they are exported too.
* This fix only unmount pool that are used as a target for the installation, leaving alone any other pool.
[Test Case]
1. Boot a live session
2. Create a new pool with:
$ zpool create -R /mnt tpool /dev/vda
3. Verify that the pool is created with zpool list
4. Start ubiquity
5. Quit ubiquity
=> Verify that the pool is still there with zpool list. Without the fix, tpool is exported.
[Regression Potential]
* Low risk of regression. Worst case, the bug is not fixed and pools are still unmounted.
[Other info]
* Already shipped in Groovy.
===
For unclear reasons (18.04 didn't have this issue), Ubiquity on 20.04 exports existing ZFS pools, (very) shortly after execution.
To repeat (assumes a `/dev/sda` disk):
- start a 20.04 Ubuntu Desktop live media
- open a terminal
- create a zfs pool: `zpool create test /dev/sda`
- verify that it's been created: `zpool list`
- launch ubiquity: `ubiquity`
- open a separate terminal
- list the ZFS pools: `zpool list`
no pools are now listed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/vmlinuz
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: MATE
Date: Sat Apr 25 15:21:25 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2020-06-24 13:24:05 |
Jean-Baptiste Lallement |
description |
[Impact]
* Ubiquity unmounts everything that could be mounted on the target file system when it starts and on tear down. For ZFS it exports all the pools.
* If a user had existing pools, they are exported too.
* This fix only unmount pool that are used as a target for the installation, leaving alone any other pool.
[Test Case]
1. Boot a live session
2. Create a new pool with:
$ zpool create -R /mnt tpool /dev/vda
3. Verify that the pool is created with zpool list
4. Start ubiquity
5. Quit ubiquity
=> Verify that the pool is still there with zpool list. Without the fix, tpool is exported.
[Regression Potential]
* Low risk of regression. Worst case, the bug is not fixed and pools are still unmounted.
[Other info]
* Already shipped in Groovy.
===
For unclear reasons (18.04 didn't have this issue), Ubiquity on 20.04 exports existing ZFS pools, (very) shortly after execution.
To repeat (assumes a `/dev/sda` disk):
- start a 20.04 Ubuntu Desktop live media
- open a terminal
- create a zfs pool: `zpool create test /dev/sda`
- verify that it's been created: `zpool list`
- launch ubiquity: `ubiquity`
- open a separate terminal
- list the ZFS pools: `zpool list`
no pools are now listed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/vmlinuz
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: MATE
Date: Sat Apr 25 15:21:25 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
[Impact]
* Ubiquity unmounts everything that could be mounted on the target file system when it starts and on tear down. For ZFS it exports all the pools.
* If a user had existing pools, they are exported too.
* This fix only unmount pool that are used as a target for the installation, leaving alone any other pool.
[Test Case]
1. Boot a live session
2. Create a new pool with:
$ zpool create -R /mnt tpool /dev/vda
3. Verify that the pool is created with zpool list
4. Start ubiquity
5. Quit ubiquity
=> Verify that the pool is still there with zpool list. Without the fix, tpool is exported.
[Regression Potential]
* Low risk of regression. Worst case, the bug is not fixed and pools are still unmounted or none of the pools are exported. This case would prevent to do 2 installations in a row from the same live session.
[Other info]
* Already shipped in Groovy.
===
For unclear reasons (18.04 didn't have this issue), Ubiquity on 20.04 exports existing ZFS pools, (very) shortly after execution.
To repeat (assumes a `/dev/sda` disk):
- start a 20.04 Ubuntu Desktop live media
- open a terminal
- create a zfs pool: `zpool create test /dev/sda`
- verify that it's been created: `zpool list`
- launch ubiquity: `ubiquity`
- open a separate terminal
- list the ZFS pools: `zpool list`
no pools are now listed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./casper/vmlinuz
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: MATE
Date: Sat Apr 25 15:21:25 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed quiet splash ---
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2020-06-24 13:30:03 |
Jean-Baptiste Lallement |
ubiquity (Ubuntu Focal): status |
New |
Triaged |
|
| 2020-06-24 13:30:06 |
Jean-Baptiste Lallement |
ubiquity (Ubuntu Focal): importance |
Undecided |
Low |
|
| 2020-06-24 16:43:50 |
Brian Murray |
ubiquity (Ubuntu Focal): status |
Triaged |
Fix Committed |
|
| 2020-06-24 16:43:52 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-06-24 16:43:55 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2020-06-24 16:43:58 |
Brian Murray |
tags |
amd64 apport-bug focal ubiquity-20.04.15 ubuntu-mate zfs |
amd64 apport-bug focal ubiquity-20.04.15 ubuntu-mate verification-needed verification-needed-focal zfs |
|
| 2020-06-25 10:39:44 |
Jean-Baptiste Lallement |
tags |
amd64 apport-bug focal ubiquity-20.04.15 ubuntu-mate verification-needed verification-needed-focal zfs |
amd64 apport-bug focal ubiquity-20.04.15 ubuntu-mate verification-done verification-done-focal zfs |
|
| 2020-07-02 08:11:47 |
Launchpad Janitor |
ubiquity (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-07-02 08:12:11 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-01-19 13:55:31 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~mfo/ubiquity/+git/ubiquity/+merge/396499 |
|
