[opensuse-buildservice] Integrity-probs in koffice pkgs..
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, These are from kde-backports repo ;-) I tought: i'll let y' know ;-) Fout: 3:Pakket koffice-i18n-nl-1.6.3-40.2 voldoet niet aan integriteitscontrole. Fout: 3:Pakket koffice-i18n-nl-doc-1.6.3-40.2 voldoet niet aan integriteitscontrole. Wilt u het opnieuw proberen? - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.22.5-29-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.3 (x86_64) KDE: 3.5.7 "release 71" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG+7ccX5/X5X6LpDgRAju0AKCoB9IVFususEIbFbdYYPDA9SLsoQCgjtaj dDd6flGuOLP2MdSV5TO7v0E= =G3+X -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi all, I've got a similar integrity error report from a user about geda-symbols. (from my home:werner2101 repo in openSUSE_10.2 noarch) I've reproduced the issue with that package, but I think it was ok when I've build and installed it the first time (2007-09-07). What's the "right" solution for the problem? Just rebuild the package? Or can I perform any special tests on that package? Original Message from the user: ---------------------------- The issue: I successfully added your repository in YaST. I was also able to install a few gEDA package successfully from there. But when it came to installation of geda-symbols, YaST gave me an integrity check failure error as follows: suse yast Error: 3:Package geda-symbols-1.2.0-2.1 fails integrity check. Do you want to retry downloading it? Then I tried with both "Retry" and "Ignore" options in YaST, but it kept failing. However, after a while, I was able to figure out the following workaround. ---------------------------- The workaround: I downloaded the geda-symbols package from the noarch folder in your repository: http://download.opensuse.org/repositories/home:/werner2101/openSUSE_10.2/noa... And then installed this package separately using the following command as root: rpm -i geda-symbols-1.2.0-2.1.noarch.rpm This solved my problem. When I opened YaST to install other gEDA packages from your repository, I saw geda-symbols as already installed and this allowed for the other gEDA packages to be smoothly installed. ---------------------------- Regards Werner --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sunday 07 October 2007 18:15:13 wrote Werner Hoch:
Hi all,
I've got a similar integrity error report from a user about geda-symbols. (from my home:werner2101 repo in openSUSE_10.2 noarch)
I've reproduced the issue with that package, but I think it was ok when I've build and installed it the first time (2007-09-07).
What's the "right" solution for the problem? Just rebuild the package? Or can I perform any special tests on that package?
Original Message from the user: ---------------------------- The issue:
I successfully added your repository in YaST. I was also able to install a few gEDA package successfully from there. But when it came to installation of geda-symbols, YaST gave me an integrity check failure error as follows:
suse yast Error: 3:Package geda-symbols-1.2.0-2.1 fails integrity check. Do you want to retry downloading it?
Then I tried with both "Retry" and "Ignore" options in YaST, but it kept failing. However, after a while, I was able to figure out the following workaround.
---------------------------- The workaround:
I downloaded the geda-symbols package from the noarch folder in your repository: http://download.opensuse.org/repositories/home:/werner2101/openSUSE_10.2/no arch/geda-symbols-1.2.0-2.1.noarch.rpm
And then installed this package separately using the following command as root:
rpm -i geda-symbols-1.2.0-2.1.noarch.rpm
This solved my problem. When I opened YaST to install other gEDA packages from your repository, I saw geda-symbols as already installed and this allowed for the other gEDA packages to be smoothly installed. ----------------------------
hm, download.o.o is just a redirector, it would be interessting, if there is a broken mirror out there. When you see it the next time, please try to find out, if there is a broken mirror via "curl -v $URL" and report it. thanks adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Adrian and all, On Monday 08 October 2007 08:28, Adrian Schröter wrote:
On Sunday 07 October 2007 18:15:13 wrote Werner Hoch:
What's the "right" solution for the problem? Just rebuild the package? Or can I perform any special tests on that package?
[...]
hm, download.o.o is just a redirector, it would be interessting, if there is a broken mirror out there.
When you see it the next time, please try to find out, if there is a broken mirror via "curl -v $URL" and report it.
I got the mirror list as discribed in http://en.opensuse.org/Build_Service/Mirror_List#Tips and downloaded all packages: -------- wget "http://ftp5.gwdg.de/pub/opensuse/repositories/home:/werner2101/openSUSE_10.2..." mv geda-symbols-1.2.0-2.1.noarch.rpm ftp5.gwdg.de wget "http://widehat.opensuse.org/repositories/home:/werner2101/openSUSE_10.2/noar..." mv geda-symbols-1.2.0-2.1.noarch.rpm widehat.opensuse.org wget "http://opensuse.mirrors.skynet.be/pub/ftp.opensuse.org/opensuse/repositories..." mv geda-symbols-1.2.0-2.1.noarch.rpm opensuse.mirrors.skynet.be wget "http://ftp.iasi.roedu.net/mirrors/opensuse.org/repositories/home:/werner2101..." mv geda-symbols-1.2.0-2.1.noarch.rpm ftp.iasi.roedu.net wget "http://ftp.twaren.net/Linux/OpenSuSE/repositories/home:/werner2101/openSUSE_..." mv geda-symbols-1.2.0-2.1.noarch.rpm ftp.twaren.net -------- There are two different packages at the mirrors (size and md5sum): ------- -rw-r--r-- 1 werner users 498919 7. Sep 19:31 ftp5.gwdg.de -rw-r--r-- 1 werner users 498410 7. Sep 19:32 ftp.iasi.roedu.net -rw-r--r-- 1 werner users 498410 7. Sep 19:32 ftp.twaren.net -rw-r--r-- 1 werner users 498919 7. Sep 19:31 opensuse.mirrors.skynet.be -rw-r--r-- 1 werner users 498919 7. Sep 19:31 widehat.opensuse.org ----------- linux-m82i:/home/werner/puffer/rpmtest # md5sum * |sort 4a426fb6629540d7bf5c7dfd780fb317 ftp5.gwdg.de 4a426fb6629540d7bf5c7dfd780fb317 opensuse.mirrors.skynet.be 4a426fb6629540d7bf5c7dfd780fb317 widehat.opensuse.org 866a6b2b958707f6ed05e4ffb021ee38 ftp.iasi.roedu.net 866a6b2b958707f6ed05e4ffb021ee38 ftp.twaren.net Both different packages can be installed using rpm -U. rpm --checksig tells that the packages are ok. The question is, whether it is ok the have packages from different size and md5sum? Regards Werner --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Monday 08 October 2007 09:47:14 wrote Werner Hoch: ...
linux-m82i:/home/werner/puffer/rpmtest # md5sum * |sort 4a426fb6629540d7bf5c7dfd780fb317 ftp5.gwdg.de 4a426fb6629540d7bf5c7dfd780fb317 opensuse.mirrors.skynet.be 4a426fb6629540d7bf5c7dfd780fb317 widehat.opensuse.org 866a6b2b958707f6ed05e4ffb021ee38 ftp.iasi.roedu.net 866a6b2b958707f6ed05e4ffb021ee38 ftp.twaren.net
Both different packages can be installed using rpm -U. rpm --checksig tells that the packages are ok.
The question is, whether it is ok the have packages from different size and md5sum?
Just talked with Michael about that ... The publisher currently does replace noarch packages so that the final noarch package comes always from the same architecture. However, the redirector has no chance to deal with different files with same name (except we do a way more expensive scanning). So we will not replace existing files anymore. This should fix this issue. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Oct 08, 2007 at 10:19:50AM +0200, Adrian Schröter wrote:
On Monday 08 October 2007 09:47:14 wrote Werner Hoch:
...
linux-m82i:/home/werner/puffer/rpmtest # md5sum * |sort 4a426fb6629540d7bf5c7dfd780fb317 ftp5.gwdg.de 4a426fb6629540d7bf5c7dfd780fb317 opensuse.mirrors.skynet.be 4a426fb6629540d7bf5c7dfd780fb317 widehat.opensuse.org 866a6b2b958707f6ed05e4ffb021ee38 ftp.iasi.roedu.net 866a6b2b958707f6ed05e4ffb021ee38 ftp.twaren.net
Incidentally, the latter two hosts are the onse which are a little bit further away and syncing to them takes longer...
Both different packages can be installed using rpm -U. rpm --checksig tells that the packages are ok.
The question is, whether it is ok the have packages from different size and md5sum?
Just talked with Michael about that ...
The publisher currently does replace noarch packages so that the final noarch package comes always from the same architecture.
This is the same bug as the one I reported three weeks ago: https://bugzilla.novell.com/show_bug.cgi?id=330400
However, the redirector has no chance to deal with different files with same name (except we do a way more expensive scanning).
So we will not replace existing files anymore. This should fix this issue.
I'd be glad to hear that it is fixed! Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
participants (4)
-
Adrian Schröter -
Dr. Peter Poeml -
M9. -
Werner Hoch