| 2023-11-15 23:14:48 |
Luca Boccassi |
bug |
|
|
added bug |
| 2023-11-15 23:19:57 |
Luca Boccassi |
description |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE image started to fail this week.
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845 |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE image started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked.
[Regression Potential]
Very minimal. The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support. The worst case scenario is that support for zstd does not work in some ways, which is not any worse than status quo. |
|
| 2023-11-15 23:20:07 |
Luca Boccassi |
libsolv (Ubuntu): status |
New |
Confirmed |
|
| 2023-11-15 23:31:16 |
Luca Boccassi |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-11-15 23:31:16 |
Luca Boccassi |
bug task added |
|
libsolv (Ubuntu Lunar) |
|
| 2023-11-15 23:31:16 |
Luca Boccassi |
nominated for series |
|
Ubuntu Noble |
|
| 2023-11-15 23:31:16 |
Luca Boccassi |
bug task added |
|
libsolv (Ubuntu Noble) |
|
| 2023-11-15 23:31:16 |
Luca Boccassi |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-11-15 23:31:16 |
Luca Boccassi |
bug task added |
|
libsolv (Ubuntu Jammy) |
|
| 2023-11-15 23:31:16 |
Luca Boccassi |
nominated for series |
|
Ubuntu Mantic |
|
| 2023-11-15 23:31:16 |
Luca Boccassi |
bug task added |
|
libsolv (Ubuntu Mantic) |
|
| 2023-11-15 23:31:24 |
Luca Boccassi |
libsolv (Ubuntu Mantic): status |
New |
Confirmed |
|
| 2023-11-15 23:31:27 |
Luca Boccassi |
libsolv (Ubuntu Lunar): status |
New |
Confirmed |
|
| 2023-11-15 23:31:29 |
Luca Boccassi |
libsolv (Ubuntu Jammy): status |
New |
Confirmed |
|
| 2023-11-15 23:34:37 |
Luca Boccassi |
description |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE image started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked.
[Regression Potential]
Very minimal. The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support. The worst case scenario is that support for zstd does not work in some ways, which is not any worse than status quo. |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked.
[Regression Potential]
Very minimal. The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support. The worst case scenario is that support for zstd does not work in some ways, which is not any worse than status quo. |
|
| 2023-11-16 00:08:59 |
Luca Boccassi |
description |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked.
[Regression Potential]
Very minimal. The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support. The worst case scenario is that support for zstd does not work in some ways, which is not any worse than status quo. |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
Support for zstd was added upstream in version 0.6.35:
https://github.com/openSUSE/libsolv/commit/f51d048e6774c180a9fef21b87d7303accae3809
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked.
[Regression Potential]
Very minimal. The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support. The worst case scenario is that support for zstd does not work in some ways, which is not any worse than status quo. |
|
| 2023-11-16 00:22:43 |
Luca Boccassi |
attachment added |
|
jammy.debdiff https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/2043625/+attachment/5719853/+files/jammy.debdiff |
|
| 2023-11-16 00:23:19 |
Luca Boccassi |
libsolv (Ubuntu Noble): status |
Confirmed |
In Progress |
|
| 2023-11-16 00:42:36 |
Luca Boccassi |
attachment added |
|
lunar.debdiff https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/2043625/+attachment/5719854/+files/lunar.debdiff |
|
| 2023-11-16 00:54:28 |
Luca Boccassi |
attachment added |
|
mantic.debdiff https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/2043625/+attachment/5719855/+files/mantic.debdiff |
|
| 2023-11-16 00:55:35 |
Luca Boccassi |
description |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
Support for zstd was added upstream in version 0.6.35:
https://github.com/openSUSE/libsolv/commit/f51d048e6774c180a9fef21b87d7303accae3809
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked.
[Regression Potential]
Very minimal. The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support. The worst case scenario is that support for zstd does not work in some ways, which is not any worse than status quo. |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
Support for zstd was added upstream in version 0.6.35:
https://github.com/openSUSE/libsolv/commit/f51d048e6774c180a9fef21b87d7303accae3809
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked. Without the fix, the following error can be seen:
Building repository 'test.repo' cache .........................................................................[error]
Error building the cache:
[test.repo|https://download.opensuse.org/tumbleweed/repo/oss/] Failed to cache repo (1).
History:
- 'repo2solv' '-o' '/tmp/img/var/cache/zypp/solv/test.repo/solv' '-X' '/tmp/img/var/cache/zypp/raw/test.repo'
/tmp/img/var/cache/zypp/raw/test.repo/repodata/d6fbf1152bab99fc7ceacf974422a9799694274b64c36015b10288e6cabadd81e4649b19f52570efc5f3ab5b28817c9561fa8eeca117a05f3caea6c33e48cb69-primary.xml.zst: No such file or directory
Command exited with status 1.
Warning: Skipping repository 'test.repo' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
'distribution-release' not found in package names. Trying capabilities.
No provider of 'distribution-release' found.
'filesystem' not found in package names. Trying capabilities.
No provider of 'filesystem' found.
Resolving package dependencies...
Nothing to do.
[Regression Potential]
Very minimal. The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support. The worst case scenario is that support for zstd does not work in some ways, which is not any worse than status quo. |
|
| 2023-11-16 00:55:57 |
Luca Boccassi |
libsolv (Ubuntu Noble): status |
In Progress |
Fix Committed |
|
| 2023-11-16 00:56:01 |
Luca Boccassi |
libsolv (Ubuntu Mantic): status |
Confirmed |
In Progress |
|
| 2023-11-16 00:56:04 |
Luca Boccassi |
libsolv (Ubuntu Lunar): status |
Confirmed |
In Progress |
|
| 2023-11-16 00:56:07 |
Luca Boccassi |
libsolv (Ubuntu Jammy): status |
Confirmed |
In Progress |
|
| 2023-11-16 00:56:38 |
Luca Boccassi |
summary |
libsolv: lack of zstd support makes it impossible to build SUSE/Fedora images with zypper/dnf |
libsolv: lack of zstd support makes it impossible to create SUSE Tumbleweed/Fedora Rawhide chroots with zypper/dnf |
|
| 2023-11-16 00:57:40 |
Luca Boccassi |
bug |
|
|
added subscriber Ubuntu Sponsors |
| 2023-11-16 01:25:39 |
Luca Boccassi |
description |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
Support for zstd was added upstream in version 0.6.35:
https://github.com/openSUSE/libsolv/commit/f51d048e6774c180a9fef21b87d7303accae3809
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked. Without the fix, the following error can be seen:
Building repository 'test.repo' cache .........................................................................[error]
Error building the cache:
[test.repo|https://download.opensuse.org/tumbleweed/repo/oss/] Failed to cache repo (1).
History:
- 'repo2solv' '-o' '/tmp/img/var/cache/zypp/solv/test.repo/solv' '-X' '/tmp/img/var/cache/zypp/raw/test.repo'
/tmp/img/var/cache/zypp/raw/test.repo/repodata/d6fbf1152bab99fc7ceacf974422a9799694274b64c36015b10288e6cabadd81e4649b19f52570efc5f3ab5b28817c9561fa8eeca117a05f3caea6c33e48cb69-primary.xml.zst: No such file or directory
Command exited with status 1.
Warning: Skipping repository 'test.repo' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
'distribution-release' not found in package names. Trying capabilities.
No provider of 'distribution-release' found.
'filesystem' not found in package names. Trying capabilities.
No provider of 'filesystem' found.
Resolving package dependencies...
Nothing to do.
[Regression Potential]
Very minimal. The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support. The worst case scenario is that support for zstd does not work in some ways, which is not any worse than status quo. |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
Support for zstd was added upstream in version 0.6.35:
https://github.com/openSUSE/libsolv/commit/f51d048e6774c180a9fef21b87d7303accae3809
Fix proposal for Debian stable: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056006
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked. Without the fix, the following error can be seen:
Building repository 'test.repo' cache .........................................................................[error]
Error building the cache:
[test.repo|https://download.opensuse.org/tumbleweed/repo/oss/] Failed to cache repo (1).
History:
- 'repo2solv' '-o' '/tmp/img/var/cache/zypp/solv/test.repo/solv' '-X' '/tmp/img/var/cache/zypp/raw/test.repo'
/tmp/img/var/cache/zypp/raw/test.repo/repodata/d6fbf1152bab99fc7ceacf974422a9799694274b64c36015b10288e6cabadd81e4649b19f52570efc5f3ab5b28817c9561fa8eeca117a05f3caea6c33e48cb69-primary.xml.zst: No such file or directory
Command exited with status 1.
Warning: Skipping repository 'test.repo' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
'distribution-release' not found in package names. Trying capabilities.
No provider of 'distribution-release' found.
'filesystem' not found in package names. Trying capabilities.
No provider of 'filesystem' found.
Resolving package dependencies...
Nothing to do.
[Regression Potential]
Very minimal. The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support. The worst case scenario is that support for zstd does not work in some ways, which is not any worse than status quo. |
|
| 2023-11-16 01:27:30 |
Luca Boccassi |
tags |
|
patch |
|
| 2023-11-16 16:36:49 |
Simon Quigley |
removed subscriber Ubuntu Sponsors |
|
|
|
| 2023-11-16 16:37:00 |
Simon Quigley |
libsolv (Ubuntu Jammy): assignee |
|
Luca Boccassi (bluca) |
|
| 2023-11-16 16:37:06 |
Simon Quigley |
libsolv (Ubuntu Lunar): assignee |
|
Luca Boccassi (bluca) |
|
| 2023-11-16 16:37:11 |
Simon Quigley |
libsolv (Ubuntu Mantic): assignee |
|
Luca Boccassi (bluca) |
|
| 2023-11-16 16:37:17 |
Simon Quigley |
libsolv (Ubuntu Noble): assignee |
|
Luca Boccassi (bluca) |
|
| 2023-11-16 16:37:20 |
Simon Quigley |
libsolv (Ubuntu Jammy): importance |
Undecided |
High |
|
| 2023-11-16 16:37:21 |
Simon Quigley |
libsolv (Ubuntu Lunar): importance |
Undecided |
High |
|
| 2023-11-16 16:37:22 |
Simon Quigley |
libsolv (Ubuntu Mantic): importance |
Undecided |
High |
|
| 2023-11-16 16:37:24 |
Simon Quigley |
libsolv (Ubuntu Noble): importance |
Undecided |
High |
|
| 2023-11-16 16:53:51 |
Luca Boccassi |
description |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
Support for zstd was added upstream in version 0.6.35:
https://github.com/openSUSE/libsolv/commit/f51d048e6774c180a9fef21b87d7303accae3809
Fix proposal for Debian stable: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056006
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked. Without the fix, the following error can be seen:
Building repository 'test.repo' cache .........................................................................[error]
Error building the cache:
[test.repo|https://download.opensuse.org/tumbleweed/repo/oss/] Failed to cache repo (1).
History:
- 'repo2solv' '-o' '/tmp/img/var/cache/zypp/solv/test.repo/solv' '-X' '/tmp/img/var/cache/zypp/raw/test.repo'
/tmp/img/var/cache/zypp/raw/test.repo/repodata/d6fbf1152bab99fc7ceacf974422a9799694274b64c36015b10288e6cabadd81e4649b19f52570efc5f3ab5b28817c9561fa8eeca117a05f3caea6c33e48cb69-primary.xml.zst: No such file or directory
Command exited with status 1.
Warning: Skipping repository 'test.repo' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
'distribution-release' not found in package names. Trying capabilities.
No provider of 'distribution-release' found.
'filesystem' not found in package names. Trying capabilities.
No provider of 'filesystem' found.
Resolving package dependencies...
Nothing to do.
[Regression Potential]
Very minimal. The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support. The worst case scenario is that support for zstd does not work in some ways, which is not any worse than status quo. |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
Support for zstd was added upstream in version 0.6.35:
https://github.com/openSUSE/libsolv/commit/f51d048e6774c180a9fef21b87d7303accae3809
Fix proposal for Debian stable: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056006
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked. Without the fix, the following error can be seen:
Building repository 'test.repo' cache .........................................................................[error]
Error building the cache:
[test.repo|https://download.opensuse.org/tumbleweed/repo/oss/] Failed to cache repo (1).
History:
- 'repo2solv' '-o' '/tmp/img/var/cache/zypp/solv/test.repo/solv' '-X' '/tmp/img/var/cache/zypp/raw/test.repo'
/tmp/img/var/cache/zypp/raw/test.repo/repodata/d6fbf1152bab99fc7ceacf974422a9799694274b64c36015b10288e6cabadd81e4649b19f52570efc5f3ab5b28817c9561fa8eeca117a05f3caea6c33e48cb69-primary.xml.zst: No such file or directory
Command exited with status 1.
Warning: Skipping repository 'test.repo' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
'distribution-release' not found in package names. Trying capabilities.
No provider of 'distribution-release' found.
'filesystem' not found in package names. Trying capabilities.
No provider of 'filesystem' found.
Resolving package dependencies...
Nothing to do.
[Regression Potential]
The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support, so the overall risk appears low.
What could happen is that support for zstd does not work as expected, which means Tumbleweed/Rawhide chroots will remain not possible to create. The download/unpack could fail at a different time in the process.
Another possible scenario is that enabling the zstd decompressor support breaks the artifact unpack process, regardless of the compression format used, which would be a new regression w.r.t the current status quo, affecting for example creating Fedora 38 or SUSE 15 chroots. |
|
| 2023-11-16 16:54:03 |
Luca Boccassi |
description |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not build with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
Support for zstd was added upstream in version 0.6.35:
https://github.com/openSUSE/libsolv/commit/f51d048e6774c180a9fef21b87d7303accae3809
Fix proposal for Debian stable: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056006
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked. Without the fix, the following error can be seen:
Building repository 'test.repo' cache .........................................................................[error]
Error building the cache:
[test.repo|https://download.opensuse.org/tumbleweed/repo/oss/] Failed to cache repo (1).
History:
- 'repo2solv' '-o' '/tmp/img/var/cache/zypp/solv/test.repo/solv' '-X' '/tmp/img/var/cache/zypp/raw/test.repo'
/tmp/img/var/cache/zypp/raw/test.repo/repodata/d6fbf1152bab99fc7ceacf974422a9799694274b64c36015b10288e6cabadd81e4649b19f52570efc5f3ab5b28817c9561fa8eeca117a05f3caea6c33e48cb69-primary.xml.zst: No such file or directory
Command exited with status 1.
Warning: Skipping repository 'test.repo' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
'distribution-release' not found in package names. Trying capabilities.
No provider of 'distribution-release' found.
'filesystem' not found in package names. Trying capabilities.
No provider of 'filesystem' found.
Resolving package dependencies...
Nothing to do.
[Regression Potential]
The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support, so the overall risk appears low.
What could happen is that support for zstd does not work as expected, which means Tumbleweed/Rawhide chroots will remain not possible to create. The download/unpack could fail at a different time in the process.
Another possible scenario is that enabling the zstd decompressor support breaks the artifact unpack process, regardless of the compression format used, which would be a new regression w.r.t the current status quo, affecting for example creating Fedora 38 or SUSE 15 chroots. |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not built with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
Support for zstd was added upstream in version 0.6.35:
https://github.com/openSUSE/libsolv/commit/f51d048e6774c180a9fef21b87d7303accae3809
Fix proposal for Debian stable: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056006
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked. Without the fix, the following error can be seen:
Building repository 'test.repo' cache .........................................................................[error]
Error building the cache:
[test.repo|https://download.opensuse.org/tumbleweed/repo/oss/] Failed to cache repo (1).
History:
- 'repo2solv' '-o' '/tmp/img/var/cache/zypp/solv/test.repo/solv' '-X' '/tmp/img/var/cache/zypp/raw/test.repo'
/tmp/img/var/cache/zypp/raw/test.repo/repodata/d6fbf1152bab99fc7ceacf974422a9799694274b64c36015b10288e6cabadd81e4649b19f52570efc5f3ab5b28817c9561fa8eeca117a05f3caea6c33e48cb69-primary.xml.zst: No such file or directory
Command exited with status 1.
Warning: Skipping repository 'test.repo' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
'distribution-release' not found in package names. Trying capabilities.
No provider of 'distribution-release' found.
'filesystem' not found in package names. Trying capabilities.
No provider of 'filesystem' found.
Resolving package dependencies...
Nothing to do.
[Regression Potential]
The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support, so the overall risk appears low.
What could happen is that support for zstd does not work as expected, which means Tumbleweed/Rawhide chroots will remain not possible to create. The download/unpack could fail at a different time in the process.
Another possible scenario is that enabling the zstd decompressor support breaks the artifact unpack process, regardless of the compression format used, which would be a new regression w.r.t the current status quo, affecting for example creating Fedora 38 or SUSE 15 chroots. |
|
| 2023-11-16 21:43:05 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Simon Quigley |
| 2023-11-16 23:23:59 |
Luca Boccassi |
description |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not built with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
Support for zstd was added upstream in version 0.6.35:
https://github.com/openSUSE/libsolv/commit/f51d048e6774c180a9fef21b87d7303accae3809
Fix proposal for Debian stable: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056006
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked. Without the fix, the following error can be seen:
Building repository 'test.repo' cache .........................................................................[error]
Error building the cache:
[test.repo|https://download.opensuse.org/tumbleweed/repo/oss/] Failed to cache repo (1).
History:
- 'repo2solv' '-o' '/tmp/img/var/cache/zypp/solv/test.repo/solv' '-X' '/tmp/img/var/cache/zypp/raw/test.repo'
/tmp/img/var/cache/zypp/raw/test.repo/repodata/d6fbf1152bab99fc7ceacf974422a9799694274b64c36015b10288e6cabadd81e4649b19f52570efc5f3ab5b28817c9561fa8eeca117a05f3caea6c33e48cb69-primary.xml.zst: No such file or directory
Command exited with status 1.
Warning: Skipping repository 'test.repo' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
'distribution-release' not found in package names. Trying capabilities.
No provider of 'distribution-release' found.
'filesystem' not found in package names. Trying capabilities.
No provider of 'filesystem' found.
Resolving package dependencies...
Nothing to do.
[Regression Potential]
The feature had been supported for many versions prior to the current ones, and when enabled it only affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support, so the overall risk appears low.
What could happen is that support for zstd does not work as expected, which means Tumbleweed/Rawhide chroots will remain not possible to create. The download/unpack could fail at a different time in the process.
Another possible scenario is that enabling the zstd decompressor support breaks the artifact unpack process, regardless of the compression format used, which would be a new regression w.r.t the current status quo, affecting for example creating Fedora 38 or SUSE 15 chroots. |
Both Fedora Rawhide and SUSE Tumbleweed started to compress their respective RepoData with zstd. The libsolv version in all Ubuntu releases is not built with zstd support, so using zypper/dnf from any Ubuntu version to build a new Fedora/SUSE chroot started to fail this week.
Noble will be fixed in the next sync of libsolv from Debian unstable, where I enabled libzstd support in 0.7.26-2. I would like SRUs all the way back to jammy to fix the CI jobs. The fix is very low risk as it enables an already available and optional feature, that is exercised only when referring to zstd-compressed repositories, which currently cannot work at all without this flag enabled.
There is an older distro-wide LP tracking libzstd enablement across all packages: https://bugs.launchpad.net/ubuntu/+source/libsolv/+bug/1923845
Support for zstd was added upstream in version 0.6.35:
https://github.com/openSUSE/libsolv/commit/f51d048e6774c180a9fef21b87d7303accae3809
Fix proposal for Debian stable: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056006
[Impact]
This affects our CI jobs in the systemd projects on Github Actions, which are running on Jammy and using dnf and zypper (with libsolv) to build images. e.g.:
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/8?urlExpires=2023-11-15T23%3A13%3A32.0430115Z&urlSigningMethod=HMACV1&urlSignature=vLbcJy6TM0PlI%2FQQsuRjhqwKLKo00%2B%2FvuURQuAWNpac%3D
https://pipelinesghubeus21.actions.githubusercontent.com/fW9YnoEKBASdi1Tl6Qk8OxwlrJgIZvKOJ6c0FMLt24imZ5L13v/_apis/pipelines/1/runs/254815/signedlogcontent/4?urlExpires=2023-11-15T23%3A13%3A49.1567762Z&urlSigningMethod=HMACV1&urlSignature=deiHR5B%2FxW9RXe%2FtC5YYYLDcWnCMa1gDGkYciaU3amo%3D
[Major Changes]
The libsolv versions in Ubuntu already support zstd, but it is not enabled at build time. It is trivially enabled with a build-dependency on libzstd and by passing a build configuration flag to cmake.
[Test Plan]
Install zypper, create a minimal config file and try to bootstrap a minimal SUSE Tumbleweed chroot with these 3 simple commands:
mkdir -p repos.d img
cat <<EOF>repos.d/test.repo
[test.repo]
name=test.repo
baseurl=https://download.opensuse.org/tumbleweed/repo/oss/
gpgcheck=1
enabled=1
autorefresh=0
keeppackages=1
EOF
zypper --reposd-dir=$PWD/repos.d --root=$PWD/img --gpg-auto-import-keys install distribution-release filesystem
If it works, then the fix worked. Without the fix, the following error can be seen:
Building repository 'test.repo' cache .........................................................................[error]
Error building the cache:
[test.repo|https://download.opensuse.org/tumbleweed/repo/oss/] Failed to cache repo (1).
History:
- 'repo2solv' '-o' '/tmp/img/var/cache/zypp/solv/test.repo/solv' '-X' '/tmp/img/var/cache/zypp/raw/test.repo'
/tmp/img/var/cache/zypp/raw/test.repo/repodata/d6fbf1152bab99fc7ceacf974422a9799694274b64c36015b10288e6cabadd81e4649b19f52570efc5f3ab5b28817c9561fa8eeca117a05f3caea6c33e48cb69-primary.xml.zst: No such file or directory
Command exited with status 1.
Warning: Skipping repository 'test.repo' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
'distribution-release' not found in package names. Trying capabilities.
No provider of 'distribution-release' found.
'filesystem' not found in package names. Trying capabilities.
No provider of 'filesystem' found.
Resolving package dependencies...
Nothing to do.
[Regression Potential]
The feature had been supported for many versions prior to the current ones, and when enabled it mainly affects code paths that deal with zstd compressed artifacts, which currently cannot work at all due to the lack of support, so the overall risk appears low.
What could happen is that support for zstd does not work as expected, which means Tumbleweed/Rawhide chroots will remain not possible to create. The download/unpack could fail at a different time in the process.
Another possible scenario is that enabling the zstd decompressor support breaks the artifact unpack process, regardless of the compression format used, which would be a new regression w.r.t the current status quo, affecting for example creating Fedora 38 or SUSE 15 chroots.
Also potential regressions in the newly added libzstd dependency could affect the workflows enabled by this change, while previously this package would have been unaffected. |
|
| 2023-11-17 09:50:53 |
Timo Aaltonen |
libsolv (Ubuntu Mantic): status |
In Progress |
Fix Committed |
|
| 2023-11-17 09:50:54 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-11-17 09:50:56 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2023-11-17 09:50:58 |
Timo Aaltonen |
tags |
patch |
patch verification-needed verification-needed-mantic |
|
| 2023-11-17 09:51:39 |
Timo Aaltonen |
libsolv (Ubuntu Lunar): status |
In Progress |
Fix Committed |
|
| 2023-11-17 09:51:42 |
Timo Aaltonen |
tags |
patch verification-needed verification-needed-mantic |
patch verification-needed verification-needed-lunar verification-needed-mantic |
|
| 2023-11-17 09:52:24 |
Timo Aaltonen |
libsolv (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-11-17 09:52:26 |
Timo Aaltonen |
tags |
patch verification-needed verification-needed-lunar verification-needed-mantic |
patch verification-needed verification-needed-jammy verification-needed-lunar verification-needed-mantic |
|
| 2023-11-17 11:25:10 |
Luca Boccassi |
libsolv (Ubuntu Noble): status |
Fix Committed |
Fix Released |
|
| 2023-11-17 19:31:34 |
Luca Boccassi |
tags |
patch verification-needed verification-needed-jammy verification-needed-lunar verification-needed-mantic |
patch verification-done verification-done-jammy verification-done-lunar verification-done-mantic |
|
| 2023-11-28 23:32:22 |
Launchpad Janitor |
libsolv (Ubuntu Mantic): status |
Fix Committed |
Fix Released |
|
| 2023-11-28 23:32:26 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-11-28 23:32:36 |
Launchpad Janitor |
libsolv (Ubuntu Lunar): status |
Fix Committed |
Fix Released |
|
| 2023-11-28 23:32:47 |
Launchpad Janitor |
libsolv (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
