[Bug 2025400] Re: zypper often fails to download packages when using HTTPS
Christian Ehrhardt
2025400 at bugs.launchpad.net
Fri Jul 21 07:50:17 UTC 2023
Hey, seeing this in the queue again.
Lunar:
- version is ok now
- changelog is ok
- we wouldn't need the "Non-maintainer upload" but that is still ok
- I'd prefer to mention the related patch file in the CL
- overall this keeps/matches the Debian CL style and that is fine to keep as-is IMHO
- patches have headers and match what is in the latest version in upstream, mantic and debian
Jammy:
- here the long version with the release wouldn't be needed (only if adjacent releases have the same version), but it isn't hurting either
- changelog is ok (just like in lunar)
- patches have headers and match what is in the latest version in upstream, mantic and debian
The SRU template was already good, but I made a minor change to the regression risk.
If clear from the changes it is always preferred to point to which use-case, action or step an error would be. in This case all changes are related to file transfer.
** Description changed:
There are known issues in zypper that cause frequent failures to
download packages when using HTTPS:
https://github.com/openSUSE/zypper/issues/420
https://github.com/openSUSE/zypper/issues/399
There are a couple of fixes that solve most of the problems in libzypp:
https://github.com/openSUSE/libzypp/commit/25688b7f6da7a8ab2ef3ec2f68f4df86ff85e4b5
https://github.com/openSUSE/libzypp/commit/ac4f61ea6e3f825b17679cdad7a73f591e393124
It would be good to backport these to Jammy, given zypper is used to
bootstrap SUSE images from CIs running Jammy, like Github Actions.
[Impact]
We are hitting a lot of issues when using zypper with https on Jammy on
Github Actions, and these upstream changes help alleviate those issues.
[Major Changes]
Only two bugfix backports, no API changes:
https://github.com/openSUSE/libzypp/commit/25688b7f6da7a8ab2ef3ec2f68f4df86ff85e4b5
https://github.com/openSUSE/libzypp/commit/ac4f61ea6e3f825b17679cdad7a73f591e393124
[Test Plan]
Verified that zypper still works on jammy to bootstrap a suse image
using mkosi:
root at jammy:~# dpkg -l | grep libzypp1722
ii libzypp1722:amd64 17.25.7-2.1ubuntu0.22.04.1 amd64 openSUSE/SLES package management system (library)
- root at jammy:~# grep VERSION_ID /etc/os-release
+ root at jammy:~# grep VERSION_ID /etc/os-release
VERSION_ID="22.04"
root at jammy:~# mkosi -d opensuse -r tumbleweed --format=directory --package=systemd build
‣ Removing output files…
‣ Building default image
‣ Mounting image…
‣ Installing Opensuse
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 3 NEW packages are going to be installed:
- compat-usrmerge-tools filesystem system-user-root
+ compat-usrmerge-tools filesystem system-user-root
3 new packages to install.
Overall download size: 0 B. Already cached: 371.4 KiB. After the operation, additional 731.5 KiB will be used.
Continue? [y/n/v/...? shows all options] (y): y
In cache compat-usrmerge-tools-84.87-5.14.x86_64.rpm (1/3), 286.6 KiB (730.0 KiB unpacked)
In cache system-user-root-20190513-2.11.noarch.rpm (2/3), 9.1 KiB ( 275 B unpacked)
In cache filesystem-84.87-12.1.x86_64.rpm (3/3), 75.7 KiB ( 1.3 KiB unpacked)
Checking for file conflicts: ...................................................................................[done]
(1/3) Installing: compat-usrmerge-tools-84.87-5.14.x86_64 ......................................................[done]
<...>
Executing %posttrans scripts ...................................................................................[done]
‣ Generating system users
‣ Applying presets…
‣ Generating hardware database
‣ Recording packages in manifest…
‣ Cleaning rpm metadata…
‣ Unmounting image…
‣ Saving manifest image.manifest
‣ /root/mkosi/mkosi.output/image size is 77.6M.
[Regression Potential]
- Minimal, only zypper is using this library:
+ * Changes are limited to the transfer of data from remove hosts, so
+ regressions (if any) should only occur in use-cases that download
+ packages.
+
+ * Generally minimal spread to other components, only zypper is using
+ this library:
root at jammy:~# apt-cache rdepends libzypp1722
libzypp1722
Reverse Depends:
- libzypp-dev
- zypper
- libzypp-doc
- libzypp-bin
+ libzypp-dev
+ zypper
+ libzypp-doc
+ libzypp-bin
--
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2025400
Title:
zypper often fails to download packages when using HTTPS
Status in libzypp package in Ubuntu:
Fix Released
Status in libzypp source package in Jammy:
Confirmed
Status in libzypp source package in Lunar:
Confirmed
Status in libzypp source package in Mantic:
Fix Released
Bug description:
There are known issues in zypper that cause frequent failures to
download packages when using HTTPS:
https://github.com/openSUSE/zypper/issues/420
https://github.com/openSUSE/zypper/issues/399
There are a couple of fixes that solve most of the problems in
libzypp:
https://github.com/openSUSE/libzypp/commit/25688b7f6da7a8ab2ef3ec2f68f4df86ff85e4b5
https://github.com/openSUSE/libzypp/commit/ac4f61ea6e3f825b17679cdad7a73f591e393124
It would be good to backport these to Jammy, given zypper is used to
bootstrap SUSE images from CIs running Jammy, like Github Actions.
[Impact]
We are hitting a lot of issues when using zypper with https on Jammy
on Github Actions, and these upstream changes help alleviate those
issues.
[Major Changes]
Only two bugfix backports, no API changes:
https://github.com/openSUSE/libzypp/commit/25688b7f6da7a8ab2ef3ec2f68f4df86ff85e4b5
https://github.com/openSUSE/libzypp/commit/ac4f61ea6e3f825b17679cdad7a73f591e393124
[Test Plan]
Verified that zypper still works on jammy to bootstrap a suse image
using mkosi:
root at jammy:~# dpkg -l | grep libzypp1722
ii libzypp1722:amd64 17.25.7-2.1ubuntu0.22.04.1 amd64 openSUSE/SLES package management system (library)
root at jammy:~# grep VERSION_ID /etc/os-release
VERSION_ID="22.04"
root at jammy:~# mkosi -d opensuse -r tumbleweed --format=directory --package=systemd build
‣ Removing output files…
‣ Building default image
‣ Mounting image…
‣ Installing Opensuse
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 3 NEW packages are going to be installed:
compat-usrmerge-tools filesystem system-user-root
3 new packages to install.
Overall download size: 0 B. Already cached: 371.4 KiB. After the operation, additional 731.5 KiB will be used.
Continue? [y/n/v/...? shows all options] (y): y
In cache compat-usrmerge-tools-84.87-5.14.x86_64.rpm (1/3), 286.6 KiB (730.0 KiB unpacked)
In cache system-user-root-20190513-2.11.noarch.rpm (2/3), 9.1 KiB ( 275 B unpacked)
In cache filesystem-84.87-12.1.x86_64.rpm (3/3), 75.7 KiB ( 1.3 KiB unpacked)
Checking for file conflicts: ...................................................................................[done]
(1/3) Installing: compat-usrmerge-tools-84.87-5.14.x86_64 ......................................................[done]
<...>
Executing %posttrans scripts ...................................................................................[done]
‣ Generating system users
‣ Applying presets…
‣ Generating hardware database
‣ Recording packages in manifest…
‣ Cleaning rpm metadata…
‣ Unmounting image…
‣ Saving manifest image.manifest
‣ /root/mkosi/mkosi.output/image size is 77.6M.
[Regression Potential]
* Changes are limited to the transfer of data from remove hosts, so
regressions (if any) should only occur in use-cases that download
packages.
* Generally minimal spread to other components, only zypper is using
this library:
root at jammy:~# apt-cache rdepends libzypp1722
libzypp1722
Reverse Depends:
libzypp-dev
zypper
libzypp-doc
libzypp-bin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libzypp/+bug/2025400/+subscriptions
More information about the Ubuntu-sponsors
mailing list