* Marco Calistri [07-04-22 08:58]:

...

Hello,

During today zypper dup I get:

file 'bc682374586d1d6891027ce2ba8efbe3707c46b78d6bda2065b73fb09a6e218d-primary.xml.gz' failed

[/var/tmp/AP_0xv8MnMr/repodata/bc682374586d1d6891027ce2ba8efbe3707c46b78d6bda2065b73fb09a6e218d-primary.xml.gz]

  expected bc682374586d1d6891027ce2ba8efbe3707c46b78d6bda2065b73fb09a6e218d

  but found 1a9393afada271226a3e4d8be2bc2df461633cc75eb69906b1a60cea2d23336b

Accepting packets with incorrect checksums can lead to system corruption and in extreme cases can even compromise it.

However, if you are sure that the file containing the checksum '1a93 ..' is safe, correct

and should be used in this operation, enter the first 4 characters of the checksum

to unlock the use of this file at your own risk. Do not enter data to ignore the file.

May I safely ignore this warning or it could be represent a system corruption risk?

what repo has the bad checksum? I guess was this one: (NON-OSS) since error appeared after this being

Il 04/07/22 10:04, Patrick Shanahan ha scritto: listed.

abort the dup and retry try a different mirror delay the dup until tomorrow and see if it clears itself

Ok thanks I will await till tomorrow. Regards, -- Marco Calistri Build: openSUSE Tumbleweed 20220523 Kernel: 5.17.9-1-default - Cinnamon 5.2.7

You may also get this error if the repo is in the process of being update. In between the repo refresh and download files can change causing a checksum error. Ken Schneider

On Jul 4, 2022, at 9:53 AM, Patrick Shanahan wrote:

* Marco Calistri [07-04-22 09:24]:

...

...

* Marco Calistri [07-04-22 08:58]:

...

Hello,

During today zypper dup I get:

file 'bc682374586d1d6891027ce2ba8efbe3707c46b78d6bda2065b73fb09a6e218d-primary.xml.gz' failed

[/var/tmp/AP_0xv8MnMr/repodata/bc682374586d1d6891027ce2ba8efbe3707c46b78d6bda2065b73fb09a6e218d-primary.xml.gz]

expected bc682374586d1d6891027ce2ba8efbe3707c46b78d6bda2065b73fb09a6e218d

but found 1a9393afada271226a3e4d8be2bc2df461633cc75eb69906b1a60cea2d23336b

Accepting packets with incorrect checksums can lead to system corruption and in extreme cases can even compromise it.

However, if you are sure that the file containing the checksum '1a93 ..' is safe, correct

and should be used in this operation, enter the first 4 characters of the checksum

to unlock the use of this file at your own risk. Do not enter data to ignore the file.

May I safely ignore this warning or it could be represent a system corruption risk?

what repo has the bad checksum? I guess was this one: (NON-OSS) since error appeared after this being

Il 04/07/22 10:04, Patrick Shanahan ha scritto: listed.

...

abort the dup and retry try a different mirror delay the dup until tomorrow and see if it clears itself

Ok thanks I will await till tomorrow.

when a "checksum" does not match, the <subject> file is corrupt and depending on the intent of the file, may do most anything to your system.

or nothing, but not worth the chance.

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

Il 04/07/22 14:29, Knurpht-openSUSE ha scritto:

Op maandag 4 juli 2022 19:25:03 CEST schreef kschneider bout-tyme. net:

...

You may also get this error if the repo is in the process of being update. In between the repo refresh and download files can change causing a checksum error.

Ken Schneider This would solve it in that case: sudo zypper clean sudo zypper ref sudo zypper (d)up

where on TW it should be dup, on Leap up

Thanks for the additional info! Regards, -- Marco Calistri Build: openSUSE Tumbleweed 20220523 Kernel: 5.17.9-1-default - Cinnamon 5.2.7

* Marco Calistri [07-05-22 08:44]:

Il 04/07/22 16:40, Marco Calistri ha scritto:

...

Il 04/07/22 14:29, Knurpht-openSUSE ha scritto:

...

Op maandag 4 juli 2022 19:25:03 CEST schreef kschneider bout-tyme. net:

...

You may also get this error if the repo is in the process of being update. In between the repo refresh and download files can change causing a checksum error.

Ken Schneider This would solve it in that case: sudo zypper clean sudo zypper ref sudo zypper (d)up

where on TW it should be dup, on Leap up

Thanks for the additional info!

Regards,

The Checksum Warning persists today.

Is there anybody else facing this issue during zypper dup?

I am not. what repo? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

* Marco Calistri [07-05-22 10:02]:

Il 05/07/22 09:59, Patrick Shanahan ha scritto:

...

* Marco Calistri [07-05-22 08:44]:

...

Il 04/07/22 16:40, Marco Calistri ha scritto:

...

Il 04/07/22 14:29, Knurpht-openSUSE ha scritto:

...

Op maandag 4 juli 2022 19:25:03 CEST schreef kschneider bout-tyme. net:

...

You may also get this error if the repo is in the process of being update. In between the repo refresh and download files can change causing a checksum error.

Ken Schneider This would solve it in that case: sudo zypper clean sudo zypper ref sudo zypper (d)up

where on TW it should be dup, on Leap up

Thanks for the additional info!

Regards,

The Checksum Warning persists today.

Is there anybody else facing this issue during zypper dup? I am not.

what repo?

(OSS).

I'm located in Brazil, maybe this has some relationship with the selected mirror.

your repo can reference more than one site, I have: baseurl=https://download.opensuse.org/tumbleweed/repo/oss/ http://download.opensuse.org/tumbleweed/repo/oss/ https://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.ussg.iu.edu/linux/opensuse/tumbleweed/repo/oss/ http://distro.ibiblio.org/opensuse/tumbleweed/repo/oss/ http://suse.mobile-central.org/tumbleweed/repo/oss/ http://ftp.uni-erlangen.de/opensuse/tumbleweed/repo/non-oss/ http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ so if needed package is not yet mirrored or the package is not good, zypper can get it from another site. and it works 99% of the time. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

* Marco Calistri [07-05-22 11:10]:

Il 05/07/22 11:22, Patrick Shanahan ha scritto:

...

* Marco Calistri [07-05-22 10:02]:

...

Il 05/07/22 09:59, Patrick Shanahan ha scritto:

...

* Marco Calistri [07-05-22 08:44]:

...

Il 04/07/22 16:40, Marco Calistri ha scritto:

...

Il 04/07/22 14:29, Knurpht-openSUSE ha scritto: > Op maandag 4 juli 2022 19:25:03 CEST schreef kschneider bout-tyme. net: > > You may also get this error if the repo is in the process of > > being update. > > In between the repo refresh and download files can change causing a > > checksum error. > > > > Ken Schneider > This would solve it in that case: > sudo zypper clean > sudo zypper ref > sudo zypper (d)up > > where on TW it should be dup, on Leap up > Thanks for the additional info!

Regards,

The Checksum Warning persists today.

Is there anybody else facing this issue during zypper dup? I am not.

what repo?

(OSS).

I'm located in Brazil, maybe this has some relationship with the selected mirror. your repo can reference more than one site, I have:

baseurl=https://download.opensuse.org/tumbleweed/repo/oss/ http://download.opensuse.org/tumbleweed/repo/oss/ https://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.ussg.iu.edu/linux/opensuse/tumbleweed/repo/oss/ http://distro.ibiblio.org/opensuse/tumbleweed/repo/oss/ http://suse.mobile-central.org/tumbleweed/repo/oss/ http://ftp.uni-erlangen.de/opensuse/tumbleweed/repo/non-oss/ http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss/

so if needed package is not yet mirrored or the package is not good, zypper can get it from another site.

and it works 99% of the time.

I think that the checksum should be verified/updated  BEFORE the packages going to be distributed worldwide.

undoubtedly they are but the mirror you are accessing most likely has a corrupt file

I can't (I wont)  change my repositories URL anytime the checksum is going to be changed.

it is not necessary to "change my repositories URL anytime the checksum", just add several of the "specific" mirrors and with a small amount of luck, your problem will disappear. and leave the added mirrors in the repo file.

Then I will just await until the normalization. Yesterday for example it started to work again.

or you can "continue" to wait. but the mirror with the faulty file will probably not notice. as always, it is *your* choice. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

Il 05/07/22 14:24, Marco Calistri ha scritto:

Il 05/07/22 14:21, Patrick Shanahan ha scritto:

...

...

...

your repo can reference more than one site, I have:

baseurl=https://download.opensuse.org/tumbleweed/repo/oss/ http://download.opensuse.org/tumbleweed/repo/oss/ https://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.ussg.iu.edu/linux/opensuse/tumbleweed/repo/oss/ http://distro.ibiblio.org/opensuse/tumbleweed/repo/oss/ http://suse.mobile-central.org/tumbleweed/repo/oss/ http://ftp.uni-erlangen.de/opensuse/tumbleweed/repo/non-oss/ http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss/

so if needed package is not yet mirrored or the package is not good, zypper can get it from another site.

and it works 99% of the time.

I think that the checksum should be verified/updated  BEFORE the packages going to be distributed worldwide. undoubtedly they are but the mirror you are accessing most likely has a corrupt file I can't (I wont)  change my repositories URL anytime the checksum is going to be changed. it is not necessary to "change my repositories URL anytime the checksum", just add several of the "specific" mirrors and with a small amount of luck, your problem will disappear.  and leave the added mirrors in the repo file. Then I will just await until the normalization. Yesterday for example it started to work again. or you can "continue" to wait.  but the mirror with the faulty file will probably not notice.  as always, it is *your* choice.

This is an interesting workaround but where I can change/add additional URL in my repositories settings?

Thanks!

I got it! I found it! Best Regards! -- Marco Calistri Build: openSUSE Tumbleweed 20220703 Kernel: 5.18.6-1-default - XFCE: (4.16.0)

Il 05/07/22 14:30, Manfred Hollstein ha scritto:

On Tue, 05 Jul 2022, 19:24:33 +0200, Marco Calistri wrote:

...

Il 05/07/22 14:21, Patrick Shanahan ha scritto:

...

...

...

your repo can reference more than one site, I have:

baseurl=https://download.opensuse.org/tumbleweed/repo/oss/ http://download.opensuse.org/tumbleweed/repo/oss/ https://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.ussg.iu.edu/linux/opensuse/tumbleweed/repo/oss/ http://distro.ibiblio.org/opensuse/tumbleweed/repo/oss/ http://suse.mobile-central.org/tumbleweed/repo/oss/ http://ftp.uni-erlangen.de/opensuse/tumbleweed/repo/non-oss/ http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss/

so if needed package is not yet mirrored or the package is not good, zypper can get it from another site.

and it works 99% of the time. I think that the checksum should be verified/updated  BEFORE the packages going to be distributed worldwide. undoubtedly they are but the mirror you are accessing most likely has a corrupt file I can't (I wont)  change my repositories URL anytime the checksum is going to be changed. it is not necessary to "change my repositories URL anytime the checksum", just add several of the "specific" mirrors and with a small amount of luck, your problem will disappear. and leave the added mirrors in the repo file. Then I will just await until the normalization. Yesterday for example it started to work again. or you can "continue" to wait. but the mirror with the faulty file will probably not notice. as always, it is *your* choice.

This is an interesting workaround but where I can change/add additional URL in my repositories settings? Just take what Patrick has shown above and put it in your /etc/zypp/repos.d/<whatever-your-oss-repo-is-called>.repo file.

...

Thanks!

-- Marco Calistri HTH, cheers.

l8er manfred Yes but for the moment I just add one https line in the tumbleweed repos files wherein I had just one http (not secure) URL.

Best regards, -- Marco Calistri Build: openSUSE Tumbleweed 20220703 Kernel: 5.18.6-1-default - XFCE: (4.16.0)

Il 05/07/22 15:13, Patrick Shanahan ha scritto:

* Marco Calistri [07-05-22 13:44]:

...

Il 05/07/22 14:30, Manfred Hollstein ha scritto:

...

On Tue, 05 Jul 2022, 19:24:33 +0200, Marco Calistri wrote:

...

Il 05/07/22 14:21, Patrick Shanahan ha scritto:

...

...

> your repo can reference more than one site, I have: > > baseurl=https://download.opensuse.org/tumbleweed/repo/oss/ > http://download.opensuse.org/tumbleweed/repo/oss/ > https://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ > http://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ > http://ftp.ussg.iu.edu/linux/opensuse/tumbleweed/repo/oss/ > http://distro.ibiblio.org/opensuse/tumbleweed/repo/oss/ > http://suse.mobile-central.org/tumbleweed/repo/oss/ > http://ftp.uni-erlangen.de/opensuse/tumbleweed/repo/non-oss/ > http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ > > so if needed package is not yet mirrored or the package is not good, > zypper can get it from another site. > > and it works 99% of the time. I think that the checksum should be verified/updated  BEFORE the packages going to be distributed worldwide. undoubtedly they are but the mirror you are accessing most likely has a corrupt file I can't (I wont)  change my repositories URL anytime the checksum is going to be changed. it is not necessary to "change my repositories URL anytime the checksum", just add several of the "specific" mirrors and with a small amount of luck, your problem will disappear. and leave the added mirrors in the repo file. Then I will just await until the normalization. Yesterday for example it started to work again. or you can "continue" to wait. but the mirror with the faulty file will probably not notice. as always, it is *your* choice.

This is an interesting workaround but where I can change/add additional URL in my repositories settings? Just take what Patrick has shown above and put it in your /etc/zypp/repos.d/<whatever-your-oss-repo-is-called>.repo file.

...

Thanks!

-- Marco Calistri HTH, cheers.

l8er manfred Yes but for the moment I just add one https line in the tumbleweed repos files wherein I had just one http (not secure) URL.

Best regards,

-- Marco Calistri Build: openSUSE Tumbleweed 20220703 Kernel: 5.18.6-1-default - XFCE: (4.16.0)

and you still may have problems that having multiple mirrors listed might solve. it *is* *your* choice.

Yes, I will remember about your recommendation and in case of facing again the same checksum issue, I will have the solution ready. Thanks! -- Marco Calistri Build: openSUSE Tumbleweed 20220704 Kernel: 5.18.6-1-default - XFCE: (4.16.0)

* Marco Calistri [07-05-22 13:25]:

Il 05/07/22 14:21, Patrick Shanahan ha scritto:

...

...

...

your repo can reference more than one site, I have:

baseurl=https://download.opensuse.org/tumbleweed/repo/oss/ http://download.opensuse.org/tumbleweed/repo/oss/ https://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.ussg.iu.edu/linux/opensuse/tumbleweed/repo/oss/ http://distro.ibiblio.org/opensuse/tumbleweed/repo/oss/ http://suse.mobile-central.org/tumbleweed/repo/oss/ http://ftp.uni-erlangen.de/opensuse/tumbleweed/repo/non-oss/ http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss/

so if needed package is not yet mirrored or the package is not good, zypper can get it from another site.

and it works 99% of the time.

I think that the checksum should be verified/updated  BEFORE the packages going to be distributed worldwide. undoubtedly they are but the mirror you are accessing most likely has a corrupt file I can't (I wont)  change my repositories URL anytime the checksum is going to be changed. it is not necessary to "change my repositories URL anytime the checksum", just add several of the "specific" mirrors and with a small amount of luck, your problem will disappear. and leave the added mirrors in the repo file. Then I will just await until the normalization. Yesterday for example it started to work again. or you can "continue" to wait. but the mirror with the faulty file will probably not notice. as always, it is *your* choice.

This is an interesting workaround but where I can change/add additional URL in my repositories settings?

what is not to understand: baseurl=https://download.opensuse.org/tumbleweed/repo/oss/ http://download.opensuse.org/tumbleweed/repo/oss/ https://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ http://ftp.ussg.iu.edu/linux/opensuse/tumbleweed/repo/oss/ http://distro.ibiblio.org/opensuse/tumbleweed/repo/oss/ http://suse.mobile-central.org/tumbleweed/repo/oss/ http://ftp.uni-erlangen.de/opensuse/tumbleweed/repo/non-oss/ http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss/ look at the repo, /etc/zypp/repos.d/ -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

Il 04/07/22 14:25, kschneider bout-tyme.net ha scritto:

You may also get this error if the repo is in the process of being update. In between the repo refresh and download files can change causing a checksum error.

Ken Schneider Yes,

I awaited a bit then re-run zypper dup and no checksum warning received so I completed the update. Regards,

...

On Jul 4, 2022, at 9:53 AM, Patrick Shanahan wrote:

* Marco Calistri [07-04-22 09:24]:

...

Il 04/07/22 10:04, Patrick Shanahan ha scritto:

...

* Marco Calistri [07-04-22 08:58]:

...

Hello,

During today zypper dup I get:

file 'bc682374586d1d6891027ce2ba8efbe3707c46b78d6bda2065b73fb09a6e218d-primary.xml.gz' failed

[/var/tmp/AP_0xv8MnMr/repodata/bc682374586d1d6891027ce2ba8efbe3707c46b78d6bda2065b73fb09a6e218d-primary.xml.gz]

expected bc682374586d1d6891027ce2ba8efbe3707c46b78d6bda2065b73fb09a6e218d

but found 1a9393afada271226a3e4d8be2bc2df461633cc75eb69906b1a60cea2d23336b

Accepting packets with incorrect checksums can lead to system corruption and in extreme cases can even compromise it.

However, if you are sure that the file containing the checksum '1a93 ..' is safe, correct

and should be used in this operation, enter the first 4 characters of the checksum

to unlock the use of this file at your own risk. Do not enter data to ignore the file.

May I safely ignore this warning or it could be represent a system corruption risk?

-- Marco Calistri Build: openSUSE Tumbleweed 20220523 Kernel: 5.17.9-1-default - Cinnamon 5.2.7