zypper doesn't work with official opensuse repositories

Bug #1639428 reported by Markus Ueberall
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Expired
Medium
Unassigned
zypper (Ubuntu)
Expired
Medium
Unassigned

Bug Description

1) The release of Ubuntu in use:
$ lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04

2) The version of the package (see https://bugs.launchpad.net/ubuntu/+source/zypper/+bug/1638306):
$ LANG=C apt-cache policy zypper
zypper:
  Installed: 1.12.4-1build1
  Candidate: 1.12.4-1build1
  Version table:
 *** 1.12.4-1build1 100
        100 /var/lib/dpkg/status
     1.12.4-1 500
        500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

3) What was expected to happen: zypper should work with the official opensuse repositories

4) What happened instead: zypper failed to build the cache
(NB the commands below are part of the /usr/share/lxc/templates/lxc-opensuse script, tested w/ v13.2, but v42.x yield the same errors)
[...]
+ echo 'Downloading opensuse minimal ...'
Downloading opensuse minimal ...
+ mkdir -p /var/cache/lxc/opensuse/13.2/partial-x86_64-packages
+ zypper --quiet --root /var/cache/lxc/opensuse/13.2/partial-x86_64-packages --non-interactive ar http://download.opensuse.org/distribution/13.2/repo/oss/ repo-oss
[...]
+ zypper --quiet --root /var/cache/lxc/opensuse/13.2/partial-x86_64-packages --non-interactive ar http://download.opensuse.org/update/13.2/ update
+ zypper --quiet --root /var/cache/lxc/opensuse/13.2/partial-x86_64-packages --non-interactive --gpg-auto-import-keys update
Error building the cache:
[repo-oss|http://download.opensuse.org/distribution/13.2/repo/oss/] Valid metadata not found at specified URL
Warning: The metadata cache needs to be built for the 'repo-oss' repository. You can run 'zypper refresh' as root to do this.
Error building the cache:
[update|http://download.opensuse.org/update/13.2/] Valid metadata not found at specified URL
Warning: The metadata cache needs to be built for the 'update' repository. You can run 'zypper refresh' as root to do this.
[...]

Tags: xenial
Mathew Hodson (mhodson)
tags: added: xenial
Revision history for this message
Dirk Mueller (dmllr) wrote :

I ran into the same issue. the issue is that the "zypper" package is using /usr/bin/gpg2 to validate repository signatures, but zypper does not depend on that. the fix is to merely install "gnupg2" beforehand.

Maybe this could be fixed by adding a runtime dependency on gnupg to the package.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in zypper (Ubuntu):
status: New → Confirmed
Revision history for this message
Dirk Mueller (dmllr) wrote :

gnupg2 I meant, sorry.

Changed in zypper (Ubuntu):
importance: Undecided → Medium
Changed in hundredpapercuts:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Paul White (paulw2u) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.

Changed in hundredpapercuts:
status: Confirmed → Incomplete
Changed in zypper (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for zypper (Ubuntu) because there has been no activity for 60 days.]

Changed in zypper (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for One Hundred Papercuts because there has been no activity for 60 days.]

Changed in hundredpapercuts:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.