[opensuse] 13.1 does not update/upgrade - wrong digest
Hi I have tried run update on 13.1 for about a week and now after release continue wrong digest in some files. zypper patch, zypper dup ... not working ! every time shows the same 'xxxx has wrong checksum', digest problem, and does not update/upgrade. Any ideas about that ? and how I fix that ? -- Valentim - following zypper return error: ------------------------------------------------------------------------- linux-1j9o:~ # zypper patch Retrieving repository 'openSUSE BuildService - Mozilla' metadata .........[done] Building repository 'openSUSE BuildService - Mozilla' cache ..............[done] Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW patches are going to be installed: openSUSE-2013-832 openSUSE-2013-854 The following packages are going to be upgraded: apparmor-docs apparmor-parser apparmor-profiles apparmor-utils perl-apparmor rsyslog 6 packages to upgrade. Overall download size: 1.3 MiB. After the operation, additional 9.4 KiB will be used. Continue? [y/n/? shows all options] (y): y Retrieving package apparmor-docs-2.8.2-4.8.1.noarch (1/6), 285.9 KiB (411.8 KiB unpacked) Retrieving: apparmor-docs-2.8.2-4.8.1.noarch.rpm ...........[done (354.1 KiB/s)] Digest verification failed for apparmor-docs-2.8.2-4.8.1.noarch.rpm. Expected 8a98ed4d6c5e3e60c3ee6c014f254d9c62db9acfb4d3d9b7917ef37639715727, found a66f61b46ed3244fb2242010a26fe0b29b83dbe6106074ebbb1ad2322c9d13f6. Continue? [yes/no] (no): Failed to provide Package apparmor-docs-2.8.2-4.8.1. Do you want to retry retrieval? [download.opensuse.org-update_1|http://download.opensuse.org/update/13.1/] Can't provide file './noarch/apparmor-docs-2.8.2-4.8.1.noarch.rpm' from repository 'download.opensuse.org-update_1' History: - apparmor-docs-2.8.2-4.8.1.noarch.rpm has wrong checksum Abort, retry, ignore? [a/r/i] (a): i Retrieving package apparmor-parser-2.8.2-4.8.1.x86_64 (2/6), 296.2 KiB (871.1 KiB unpacked) Retrieving: apparmor-parser-2.8.2-4.8.1.x86_64.rpm .........[done (166.3 KiB/s)] Digest verification failed for apparmor-parser-2.8.2-4.8.1.x86_64.rpm. Expected 77814232fb4275f4811fa52c8d6b2bed074d21ba38641db29bad1d296225a621, found 686b7b822ed5af99f0874a8a3dcb4c0dd25dac978f34f040c46a23be2f8063d6. Continue? [yes/no] (no): Failed to provide Package apparmor-parser-2.8.2-4.8.1. Do you want to retry retrieval? [download.opensuse.org-update_1|http://download.opensuse.org/update/13.1/] Can't provide file './x86_64/apparmor-parser-2.8.2-4.8.1.x86_64.rpm' from repository 'download.opensuse.org-update_1' History: - apparmor-parser-2.8.2-4.8.1.x86_64.rpm has wrong checksum Abort, retry, ignore? [a/r/i] (a): i Retrieving package perl-apparmor-2.8.2-4.8.1.x86_64 (3/6), 85.0 KiB (339.7 KiB unpacked) Retrieving: perl-apparmor-2.8.2-4.8.1.x86_64.rpm ...........[done (181.6 KiB/s)] Digest verification failed for perl-apparmor-2.8.2-4.8.1.x86_64.rpm. Expected ac0a4151192cce4b045841eec8fb9cde9368217f65c42a6a7114d7e0fb9155e6, found d613bf15e0b0d95f63413b30e30392c45c2b3a14f3997397cb624f8283064651. Continue? [yes/no] (no): Failed to provide Package perl-apparmor-2.8.2-4.8.1. Do you want to retry retrieval? [download.opensuse.org-update_1|http://download.opensuse.org/update/13.1/] Can't provide file './x86_64/perl-apparmor-2.8.2-4.8.1.x86_64.rpm' from repository 'download.opensuse.org-update_1' History: - perl-apparmor-2.8.2-4.8.1.x86_64.rpm has wrong checksum Abort, retry, ignore? [a/r/i] (a): i Retrieving package rsyslog-7.4.6-2.4.1.x86_64 (4/6), 516.0 KiB ( 1.9 MiB unpacked) Retrieving: rsyslog-7.4.6-2.4.1.x86_64.rpm .................[done (335.8 KiB/s)] Digest verification failed for rsyslog-7.4.6-2.4.1.x86_64.rpm. Expected 163503e12fa75ea276ce7b520e0559babb686c4ea368c9622f145bd8ce025b1b, found 7c613a445f59cf65e0d93594e58a567c6f21874776a8deb3e3e142c2d52ec40f. Continue? [yes/no] (no): Failed to provide Package rsyslog-7.4.6-2.4.1. Do you want to retry retrieval? [download.opensuse.org-update_1|http://download.opensuse.org/update/13.1/] Can't provide file './x86_64/rsyslog-7.4.6-2.4.1.x86_64.rpm' from repository 'download.opensuse.org-update_1' History: - rsyslog-7.4.6-2.4.1.x86_64.rpm has wrong checksum Abort, retry, ignore? [a/r/i] (a): i Retrieving package apparmor-profiles-2.8.2-4.8.1.noarch (5/6), 79.0 KiB (227.3 KiB unpacked) Retrieving: apparmor-profiles-2.8.2-4.8.1.noarch.rpm .......[done (164.7 KiB/s)] Digest verification failed for apparmor-profiles-2.8.2-4.8.1.noarch.rpm. Expected a8b59cf1602104651706aa1760e54321d50ad3a4e7c3e09e1843d4045898baed, found 8fdc4a65658110e374f24b3e19ce9a1840467bd077dabe601e43bce52c967af9. Continue? [yes/no] (no): Failed to provide Package apparmor-profiles-2.8.2-4.8.1. Do you want to retry retrieval? [download.opensuse.org-update_1|http://download.opensuse.org/update/13.1/] Can't provide file './noarch/apparmor-profiles-2.8.2-4.8.1.noarch.rpm' from repository 'download.opensuse.org-update_1' History: - apparmor-profiles-2.8.2-4.8.1.noarch.rpm has wrong checksum Abort, retry, ignore? [a/r/i] (a): i Retrieving package apparmor-utils-2.8.2-4.8.1.noarch (6/6), 102.7 KiB (204.9 KiB unpacked) Retrieving: apparmor-utils-2.8.2-4.8.1.noarch.rpm ..........[done (174.9 KiB/s)] Digest verification failed for apparmor-utils-2.8.2-4.8.1.noarch.rpm. Expected f876d42c68285c4d2f86d54e08ebbda22af986e7640a3b175d33612fbfec2aea, found 914f43aea8bc29c178a118129c5e048582a4ee51d5ca707d26fe89240cfbe4a3. Continue? [yes/no] (no): Failed to provide Package apparmor-utils-2.8.2-4.8.1. Do you want to retry retrieval? [download.opensuse.org-update_1|http://download.opensuse.org/update/13.1/] Can't provide file './noarch/apparmor-utils-2.8.2-4.8.1.noarch.rpm' from repository 'download.opensuse.org-update_1' History: - apparmor-utils-2.8.2-4.8.1.noarch.rpm has wrong checksum Abort, retry, ignore? [a/r/i] (a): i linux-1j9o:~ # -------------------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 20/11/13 21:00, Valentim Carlos escribió:
Hi
I have tried run update on 13.1 for about a week and now after release continue wrong digest in some files. zypper patch, zypper dup ... not working ! every time shows the same 'xxxx has wrong checksum', digest problem, and does not update/upgrade.
Any ideas about that ? and how I fix that ?
You are probably getting files from: - a mirror that is defective. - You have a intermediate proxy that is messing with files in question try this: http://download.opensuse.org/update/13.1/noarch/apparmor-docs-2.8.2-4.8.1.no... what is your nearest mirror ? Does changing the URL of your "update" repo to http://mirrors1.kernel.org/opensuse/update/13.1/ solves the issue ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
my nearest mirros is: http://opensuse.c3sl.ufpr.br/update/13.1/noarch/apparmor-docs-2.8.2-4.8.1.no... and I do the change URL and did not solves the inssue yet, I'm going to look about intermediate proxy. Em 20-11-2013 22:20, Cristian Rodríguez escreveu:
El 20/11/13 21:00, Valentim Carlos escribió:
Hi
I have tried run update on 13.1 for about a week and now after release continue wrong digest in some files. zypper patch, zypper dup ... not working ! every time shows the same 'xxxx has wrong checksum', digest problem, and does not update/upgrade.
Any ideas about that ? and how I fix that ?
You are probably getting files from:
- a mirror that is defective. - You have a intermediate proxy that is messing with files in question
try this:
http://download.opensuse.org/update/13.1/noarch/apparmor-docs-2.8.2-4.8.1.no...
what is your nearest mirror ?
Does changing the URL of your "update" repo to http://mirrors1.kernel.org/opensuse/update/13.1/ solves the issue ?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-11-21 02:40, Valentim Carlos wrote:
my nearest mirros is:
http://opensuse.c3sl.ufpr.br/update/13.1/noarch/apparmor-docs-2.8.2-4.8.1.no...
and I do the change URL and did not solves the inssue yet, I'm going to look about intermediate proxy.
Another possibility is that you already have a cached copy, bad. You have to erase that cache. Maybe "/var/cache/zypp/". -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
El 20/11/13 22:47, Carlos E. R. escribió:
On 2013-11-21 02:40, Valentim Carlos wrote:
my nearest mirros is:
http://opensuse.c3sl.ufpr.br/update/13.1/noarch/apparmor-docs-2.8.2-4.8.1.no...
and I do the change URL and did not solves the inssue yet, I'm going to look about intermediate proxy.
Another possibility is that you already have a cached copy, bad. You have to erase that cache. Maybe "/var/cache/zypp/".
There is also the possibility (although less likely) that the RAM is broken and is producing bogus checksums. since it has happened to me, causing significant hair loss. I wont rule it out. -- "Judging by their response, the meanest thing you can do to people on the Internet is to give them really good software for free". - Anil Dash -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Em 21-11-2013 01:06, Cristian Rodríguez escreveu:
There is also the possibility (although less likely) that the RAM is broken and is producing bogus checksums. since it has happened to me, causing significant hair loss. I wont rule it out.
if that is the problem, what I need to do about, please ? in advance thanks all replies, I will keep tring any ideas how to solves this inssue ! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 21/11/13 00:43, Valentim Carlos escribió:
Em 21-11-2013 01:06, Cristian Rodríguez escreveu:
There is also the possibility (although less likely) that the RAM is broken and is producing bogus checksums. since it has happened to me, causing significant hair loss. I wont rule it out.
if that is the problem, what I need to do about, please ? in advance thanks all replies, I will keep tring any ideas how to solves this inssue !
should be ruled out by running memtest..however.. This is the least likely cause..you most probably have a corrupted cache (running zypper clean -a will solve that) or a proxy in the middle that is doing weird things. If your memory were broken, other programs may randomly fail too or there will be weird kernel warnings in your logs. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Em 21-11-2013 01:57, Cristian Rodríguez escreveu:
El 21/11/13 00:43, Valentim Carlos escribió:
Em 21-11-2013 01:06, Cristian Rodríguez escreveu:
There is also the possibility (although less likely) that the RAM is broken and is producing bogus checksums. since it has happened to me, causing significant hair loss. I wont rule it out.
if that is the problem, what I need to do about, please ? in advance thanks all replies, I will keep tring any ideas how to solves this inssue !
should be ruled out by running memtest..however.. This is the least likely cause..you most probably have a corrupted cache (running zypper clean -a will solve that) or a proxy in the middle that is doing weird things.
If your memory were broken, other programs may randomly fail too or there will be weird kernel warnings in your logs.
I have cleared the cache several times without success, I have searched and added by proxy but without knowledge of the correct configuration file or other possible things; various repo and different files with the same inssue ! I need more help please ! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Nov 23, 2013 at 5:01 AM, Valentim Carlos <timkhan85@gmail.com> wrote:
I have cleared the cache several times without success, I have searched and added by proxy but without knowledge of the correct configuration file or other possible things; various repo and different files with the same inssue ! I need more help please !
Cant you fetch the complete iso media as an alternative and mount it and dup/zypper from there or even boot from it and use it then? Use aria2c or other similar dependable and verifying means that give you proper stable files as downloads. Maybe storage layer on your system is faulty or similar. How about booting failsafe mode on your current system and trying then? Maybe there is really something bad with your hardware. Good luck. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Em 23-11-2013 22:22, cagsm escreveu:
On Sat, Nov 23, 2013 at 5:01 AM, Valentim Carlos <timkhan85@gmail.com> wrote:
I have cleared the cache several times without success, I have searched and added by proxy but without knowledge of the correct configuration file or other possible things; various repo and different files with the same inssue ! I need more help please !
Cant you fetch the complete iso media as an alternative and mount it and dup/zypper from there or even boot from it and use it then?
I did that without problem ...
Use aria2c or other similar dependable and verifying means that give you proper stable files as downloads.
I did a lot of ways without success and I don't know about aria2c but I will try it !
Maybe storage layer on your system is faulty or similar. How about booting failsafe mode on your current system and trying then? Maybe there is really something bad with your hardware. Good luck.
thanks for all, I've tested my hardware but maybe storage could be some problem that I don't know how to fix that ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-11-26 00:59, Valentim Carlos wrote:
Em 23-11-2013 22:22, cagsm escreveu:
Use aria2c or other similar dependable and verifying means that give you proper stable files as downloads.
I did a lot of ways without success and I don't know about aria2c but I will try it !
You have to give it the URL of the metalink file. You see the extension is ".meta4". Actually, it is the same as the normal ".iso" file, but ending in ".iso.meta4".
thanks for all, I've tested my hardware but maybe storage could be some problem that I don't know how to fix that ...
Are you using FAT partitions? -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
Em 25-11-2013 23:41, Carlos E. R. escreveu:
On 2013-11-26 00:59, Valentim Carlos wrote:
Em 23-11-2013 22:22, cagsm escreveu:
Use aria2c or other similar dependable and verifying means that give you proper stable files as downloads.
I did a lot of ways without success and I don't know about aria2c but I will try it !
You have to give it the URL of the metalink file. You see the extension is ".meta4". Actually, it is the same as the normal ".iso" file, but ending in ".iso.meta4".
Thanks
thanks for all, I've tested my hardware but maybe storage could be some problem that I don't know how to fix that ...
Are you using FAT partitions?
Yes, EFI Boot - FAT only one -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2013-11-26 08:09, Valentim Carlos wrote:
thanks for all, I've tested my hardware but maybe storage could be some problem that I don't know how to fix that ...
Are you using FAT partitions?
Yes, EFI Boot - FAT only one
No, I mean where you store the downloads. The iso specifically. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
Em 26-11-2013 11:08, Carlos E. R. escreveu:
On 2013-11-26 08:09, Valentim Carlos wrote:
thanks for all, I've tested my hardware but maybe storage could be some problem that I don't know how to fix that ...
Are you using FAT partitions?
Yes, EFI Boot - FAT only one
No, I mean where you store the downloads. The iso specifically.
No, I have not, and I have been having the same insue with other repos, whem I use ,zypper up, no problems, but zypper dup does not working given the same insue with wrong digest in some files and does not install the othe packages without insue too. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-11-23 at 02:01 -0200, Valentim Carlos wrote:
I have cleared the cache several times without success, I have searched and added by proxy but without knowledge of the correct configuration file or other possible things;
You can not configure a proxy without knowing the proper config. If you are at home you are not likely to have one. If you are at a university or work center then you very probably have one. In that case, you have to ask the network administrator for the details. In any case, just ask whoever is responsible for the network. If that one is you, then you should know if you installed that thing or not. For instance, on work centers or organizations, specially if they cater for Windows machines, they will probably have a proxy in place that also scan for viruses. They typically capture your download order, download the complete file, scan it, and when cleared, they give it to you. Your computer waits and waits for the download, which does not come for some time, and then suddenly it comes (or not, if they think there is a virus). - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlKT/kIACgkQtTMYHG2NR9UXFgCdGhtLK+vdOY9XOjvNEUY0tSq8 KrAAn2uyB4N18q8CKc0srnaV41Tt/KS4 =vVdU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2013-11-21 at 00:06 -0300, Cristian Rodríguez wrote:
There is also the possibility (although less likely) that the RAM is broken and is producing bogus checksums. since it has happened to me, causing significant hair loss. I wont rule it out.
I can imagine that hair loss. I would bang the table, not having a punch ball at reach. Memory is supposed to have a parity bit, but nowdays perhaps implementations have forgotten about it... - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlKT+/QACgkQtTMYHG2NR9XfRgCfQsJniQykmuuU0NfpctBrhi6L pRoAoIdrtDBxyjMj79E/9nSdm6gTuSs0 =c3HK -----END PGP SIGNATURE-----
Em 20-11-2013 23:47, Carlos E. R. escreveu:
On 2013-11-21 02:40, Valentim Carlos wrote:
my nearest mirros is:
http://opensuse.c3sl.ufpr.br/update/13.1/noarch/apparmor-docs-2.8.2-4.8.1.no...
and I do the change URL and did not solves the inssue yet, I'm going to look about intermediate proxy.
Another possibility is that you already have a cached copy, bad. You have to erase that cache. Maybe "/var/cache/zypp/".
I erase that cache and keep the inssue, I see that proxy is disable, I have tried mirros and 1 click without success too. and does not update working yet. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
cagsm -
Carlos E. R. -
Cristian Rodríguez -
Valentim Carlos