Hmm, looks like the last update installed openSUSE-build-key - The public gpg keys for rpm package signature verification 1.0-24.4.1 instead of the latest suse-build-key-1.0-907.928.42.1.noarch.rpm that can be found here: https://software.opensuse.org/package/suse-build-key ->? Am 27/08/16 um 16:16 schrieb Markus Egg:

I am having 2 problems: 1) the keys seem to be expired:

" Key: E3A5C360307E3D54 Name: SuSE Package Signing Key Finger Print: 4E98E67519D98DC7362A5990E3A5C360307E3D54 Created: 04/05/10 Expires: 03/05/14 (The key is expired.)"

2) the SuSE repos lag (my internet connection is fine though):

"[...] Timeout exceeded when accessing 'http://download.opensuse.org/debug/update/13.1-non-oss/repodata/repomd.xml'.

Abort, retry, ignore? [a/r/i] (r): Trying again... [...] Timeout exceeded when accessing 'http://download.opensuse.org/distribution/13.1/repo/oss/content'.

Abort, retry, ignore? [a/r/i] (r): Autoselecting 'r' after 21 seconds. r [...]"

and "Retrieving repository 'openSUSE-13.1-Update' metadata ---------------------------------------------------------------------------------------[-] File 'repomd.xml' from repository 'openSUSE-13.1-Update' is unsigned, continue? [yes/no] (no): ... Skipping repository 'openSUSE-13.1-Update' because of the above error."

What is going on here? Never had these problems before...

BR ME

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am 27/08/16 um 19:06 schrieb Marcus Meissner:

Hi,

the key will auto-refresh from the 13.1 update repository, not from this build-key package.

The fun is that the refreshed key is expired after the last update.

The timeouts are weird, these should not happen. Perhaps a ipv6 issue?

Ciao, Marcus

IPv6 is turned off. Maybe the mirrors are laggy today. Where can I see which mirrors are used? Can I explicitly tell yast2 to use a certain mirror per http path? Did not find a hint for this on the net. BR

On Sat, Aug 27, 2016 at 06:03:28PM +0200, Markus Egg wrote:

...

Hmm, looks like the last update installed openSUSE-build-key - The public gpg keys for rpm package signature verification 1.0-24.4.1

instead of the latest suse-build-key-1.0-907.928.42.1.noarch.rpm that can be found here: https://software.opensuse.org/package/suse-build-key ->?

Am 27/08/16 um 16:16 schrieb Markus Egg:

...

I am having 2 problems: 1) the keys seem to be expired:

" Key: E3A5C360307E3D54 Name: SuSE Package Signing Key Finger Print: 4E98E67519D98DC7362A5990E3A5C360307E3D54 Created: 04/05/10 Expires: 03/05/14 (The key is expired.)"

2) the SuSE repos lag (my internet connection is fine though):

"[...] Timeout exceeded when accessing 'http://download.opensuse.org/debug/update/13.1-non-oss/repodata/repomd.xml'.

Abort, retry, ignore? [a/r/i] (r): Trying again... [...] Timeout exceeded when accessing 'http://download.opensuse.org/distribution/13.1/repo/oss/content'.

Abort, retry, ignore? [a/r/i] (r): Autoselecting 'r' after 21 seconds. r [...]"

and "Retrieving repository 'openSUSE-13.1-Update' metadata ---------------------------------------------------------------------------------------[-] File 'repomd.xml' from repository 'openSUSE-13.1-Update' is unsigned, continue? [yes/no] (no): ... Skipping repository 'openSUSE-13.1-Update' because of the above error."

What is going on here? Never had these problems before...

BR ME

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2016-08-27 20:01, Felix Miata wrote:

Markus Egg composed on 2016-08-27 19:29 (UTC+0200): ...

...

Can I explicitly tell yast2 to use a certain mirror per http path? Did not find a hint for this on the net.

I use MC for nearly everything it is capable of doing. For this process MC makes it simple. Just copy a different *.repo* file to *.repo for whichever repo is misbehaving. YaST & Zypp only pay any attention to *.repo so the extra files in /etc/zypp/ function as handy repo switchers as well as local backup.

Instead of trying to figure out what to copy and paste to zypper ar to add a BS repo, I just save the .repo file from a mirror to /etc/zypp/repos.d/. Disabling or enabling a particular repo is a simple matter of having or not having that particular *.repo file. This repo configuration "feature" is one of a multitude of things that makes zypp a bunch better than Yum, DNF and other package management systems I'm familiar with.

# ls -lgG /etc/zypp/repos.d/ | egrep 'OSS|date' -rw-r--r-- 1 288 Nov 19 2013 NonFreeUpdate.repoD -rw-r--r-- 1 292 Nov 19 2013 NonFreeUpdate.repo-gwdg -rw-r--r-- 1 148 Nov 19 2013 Non-OSS.repo -rw-r--r-- 1 148 Nov 19 2013 Non-OSS.repoD -rw-r--r-- 1 152 Nov 19 2013 Non-OSS.repo-gwdg -rw-r--r-- 1 157 Nov 19 2013 Non-OSS.repoK -rw-r--r-- 1 147 Nov 19 2013 Non-OSS.repoW

Interesting trick. What I so is edit the file and comment out the URL with "#", and write another. YaST/zyper think the repo did not change. Another trick. If you want an automatic change, use this trick: [EXT_Packman] name=EXT: Packman Repository enabled=1 autorefresh=1 path=/ mirrorlist=http://localhost/packmanmirrorlist.file type=rpm-md priority=95 keeppackages=1 The local apache points to /etc/zypp/repos.d/packmanmirrorlist.file, which contains: http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_13.1/ http://mirror.karneval.cz/pub/linux/packman/suse/openSUSE_13.1/ If one url does not work, it automatically loads from the other ;-) That's on 13.1, maybe there are more recent tricks. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)