Hi, The repository has been restored (a snapshot was available Friday afternoon, and we switched back to live data just some hours ago. Ciao, Marcus On Fri, Mar 22, 2019 at 02:15:59PM +0100, Marcus Meissner wrote:

Hi,

Due to a internal problem the update repository for 15.0 is currently empty.

We are restoring it currently and it should be available again soon.

Ciao, Marcus

On Fri, Mar 22, 2019 at 02:09:43PM +0100, Manfred Hollstein wrote:

...

Hi there,

I'm pretty sure this is the wrong forum, but, considering the appearance "this is all about development", I doubt it's normal/OK what has happened to http://download.opensuse.org/update/leap/15.0/oss/...

Take a look at the suggested source packages of all package updates submitted so far:

http://download.opensuse.org/update/leap/15.0/oss/src/

There are NONE?!?!

What the hell has been going on here? Luckily this does not appear to affect other distributions, but still...

Any ideas?

TIA, cheers.

l8er manfred

-- Marcus Meissner,SUSE LINUX GmbH; Maxfeldstrasse 5; D-90409 Nuernberg; Zi. 3.1-33,+49-911-740 53-432,,serv=loki,mail=wotan,type=real -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- Marcus Meissner,SUSE LINUX GmbH; Maxfeldstrasse 5; D-90409 Nuernberg; Zi. 3.1-33,+49-911-740 53-432,,serv=loki,mail=wotan,type=real -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 24/03/2019 09.27, openSUSE Lietuviškai wrote:

However some packages from update repository now are broken. E.g. during appliance build with KIWI, I get:

DEBUG: bootstrap: Retrieving: libX11-data-1.6.5-lp150.2.3.1.noarch.rpm [...done (1.1 KiB/s)] DEBUG: bootstrap: Warning: Digest verification failed for file 'libX11-data-1.6.5-lp150.2.3.1.noarch.rpm'

Several people are reporting the same problem. See: https://lists.opensuse.org/opensuse/2019-03/msg00262.html [opensuse] Corrupt files in update repository https://lists.opensuse.org/opensuse/2019-03/msg00261.html [opensuse] Digest verification failed when doing system upgrade -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

Hi, Can you run "zypper refresh"? Are you using download.opensuse.org? If not, the mirrors need to catch up still. Ciao, Marcus On Mon, Mar 25, 2019 at 12:07:29PM +0100, Hans-Peter Jansen wrote:

Dear Marcus,

On Samstag, 23. März 2019 21:08:03 Marcus Meissner wrote:

...

Hi,

The repository has been restored (a snapshot was available Friday afternoon, and we switched back to live data just some hours ago.

It's still broken. In an attempt to upgrade my wife's 42.3 system to 15.0 yesterday evening, it revealed its full scope.

The usual way of sed'ing the repos and zypper dup'ing resulted in:

Retrieving package apparmor-docs-2.12-lp150.6.6.1.noarch (93/3093), 306.0 KiB (353.0 KiB unpacked) Retrieving: apparmor-docs-2.12-lp150.6.6.1.noarch.rpm ..............................................[done (283.8 KiB/s)]

Warning: Digest verification failed for file 'apparmor-docs-2.12- lp150.6.6.1.noarch.rpm' [/var/adm/mount/AP_0xITdps1/noarch/apparmor-docs-2.12-lp150.6.6.1.noarch.rpm]

expected 607e9527fc21811b82da32adfc70b654fe4157ae58b7a3ca6e5458c08b7fe1b8 but got 9a9f16c0db35e8936dcd087019ab9bcb5de92c3f66dec43ebfe262c60671e003

Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.

However if you made certain that the file with checksum '9a9f..' is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file.

Unblock or discard? [9a9f/...? shows all options] (discard):

Next, I attempted to upgrade the old, lame way (usb stick, DVD version). Again, it raised the very same issue as above. Duh.

When comparing the meta data of this package with a properly installed one, it didn't show any difference. Since I know, that rpm, as used from openSUSE, is integrity checked, the problem must be located in the update repo setup.

And because I have backups, I forced the installation anyway. I had to confirm installation of about 2/3 of all updated packages, since the "No show this again" in YaST didn't work as expected. No fun.

I would declare 15.0 not installable as such, at least not with the default settings of updating right away.

Looks, like it needs a plain createrepo run (not an update run).

Cheers, Pete

-- Marcus Meissner,SUSE LINUX GmbH; Maxfeldstrasse 5; D-90409 Nuernberg; Zi. 3.1-33,+49-911-740 53-432,,serv=loki,mail=wotan,type=real -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mon, Mar 25, 2019 at 01:51:03PM +0100, Hans-Peter Jansen wrote:

On Montag, 25. März 2019 12:54:27 Marcus Meissner wrote:

...

Hi,

Can you run "zypper refresh"?

Did that, of course. As well as removing everything under /var/cache/zypp/{packages,raw,solv} manually.

...

Are you using download.opensuse.org? If not, the mirrors need to catch up still.

That might be a reason, but the behavior was consistent during 21:00 and 24:00 last night (CET) on several zypper dup runs.. Wouldn't the load balancer distribute the requests to diverse hosts.

The system is up and running fine.

If time allows, I will setup a throw away 15.0 VM later one to check, if things settled meanwhile.

It is fixed only since around 10:00 am this morning. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 25/03/2019 12.07, Hans-Peter Jansen wrote:

Dear Marcus,

On Samstag, 23. März 2019 21:08:03 Marcus Meissner wrote:

...

Hi,

The repository has been restored (a snapshot was available Friday afternoon, and we switched back to live data just some hours ago.

It's still broken. In an attempt to upgrade my wife's 42.3 system to 15.0 yesterday evening, it revealed its full scope.

The usual way of sed'ing the repos and zypper dup'ing resulted in:

Retrieving package apparmor-docs-2.12-lp150.6.6.1.noarch (93/3093), 306.0 KiB (353.0 KiB unpacked) Retrieving: apparmor-docs-2.12-lp150.6.6.1.noarch.rpm ..............................................[done (283.8 KiB/s)]

Warning: Digest verification failed for file 'apparmor-docs-2.12- lp150.6.6.1.noarch.rpm' [/var/adm/mount/AP_0xITdps1/noarch/apparmor-docs-2.12-lp150.6.6.1.noarch.rpm]

expected 607e9527fc21811b82da32adfc70b654fe4157ae58b7a3ca6e5458c08b7fe1b8 but got 9a9f16c0db35e8936dcd087019ab9bcb5de92c3f66dec43ebfe262c60671e003

Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise.

However if you made certain that the file with checksum '9a9f..' is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file.

Unblock or discard? [9a9f/...? shows all options] (discard):

Next, I attempted to upgrade the old, lame way (usb stick, DVD version). Again, it raised the very same issue as above. Duh.

Because you allowed network. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

On Mon, Mar 25, 2019 at 08:40:12PM +0100, Olaf Hering wrote:

On Sat, Mar 23, Marcus Meissner wrote:

...

The repository has been restored (a snapshot was available Friday afternoon, and we switched back to live data just some hours ago.

Is it supposed to be fully restored? zypper dup gives:

The following 15 packages are going to be downgraded: cpp7 7.4.0+r266845-lp150.3.3.1 -> 7.3.1+r258812-lp150.2.10 x86_64 oss openSUSE

obs ls -lbv openSUSE:Leap:15.0:Update gcc7.9409 -> HTTP Error 404: Not Found

Yes, I briefly removed the gcc7 update as it caused i586 failures. I will rerelease the gcc8 update and then rerelease gcc7. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Montag, 25. März 2019, 21:21:04 CET Michael Ströder wrote:

On 3/25/19 8:43 PM, Marcus Meissner wrote:

...

On Mon, Mar 25, 2019 at 08:40:12PM +0100, Olaf Hering wrote:

...

On Sat, Mar 23, Marcus Meissner wrote:

...

The repository has been restored (a snapshot was available Friday afternoon, and we switched back to live data just some hours ago.

Is it supposed to be fully restored? zypper dup gives:

The following 15 packages are going to be downgraded: cpp7 7.4.0+r266845-lp150.3.3.1 -> 7.3.1+r258812-lp150.2.10 x86_64 oss openSUSE

obs ls -lbv openSUSE:Leap:15.0:Update gcc7.9409 -> HTTP Error 404: Not Found> Yes, I briefly removed the gcc7 update as it caused i586 failures.

I will rerelease the gcc8 update and then rerelease gcc7.

I suspect that OBS is currently not publishing to download.o.o.

Since several hours several of my builds are in the state "repository not yet created".

well, we need to re-publish really all 15.0 repos .. means OBS has quite some backlog atm. And our stage server is also heavy loaded, since the mirrors need to re- download the content. So, I expect that we will have reduce publishing speed this week.... -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org