[opensuse-kde] Re: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?
On Wednesday 21 April 2010, 16:29:15 David C. Rankin wrote:
On 04/21/2010 03:48 AM, Michael Schroeder wrote:
On Tue, Apr 20, 2010 at 11:07:59PM +0200, Hans-Peter Jansen wrote:
History: - 'repo2solv.sh' '-o' '/var/cache/zypp/solv/KDE_KDE3/solv' '/var/cache/zypp/raw/KDE_KDE3' Unknown checksum type: 8: sha256
Oops, we updated the createrepo package on the build service host to use some new features, and now all of the repos use sha256 checksums instead of sha1. Unfortunatelly libzypp in 11.1 and older can't handle that checksum (yet). We now use a createrepo option to use sha1 again for older repos, so things should work again for all freshly created build service repositories.
Sorry for the inconvenience.
Cheers, Michael.
Ahah,
You need to stay with the stable branch (0.4.11), the unstable branch (0.9.x) is a radically different beast altogether. I had to build yum, rpm, python-iniparser, etc... to build createrepo on Arch Linux to manage a couple of repositories there. There was no way to get the testing branch of createrepo to work with the current openSuSE repositories. (you may be able to do it, but I couldn't)
createrepo -s sha should do the trick (as it does for Michael, I guess)... BTW, the KDE:KDE3 repo is fixed now, but I had to disable kvirc and qca, as those broke due to factory changes... While at it, I fixed python-kde3 and recovered kinternet. Hopefully, most things are in shape again.. Cheers, Pete -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wed, Apr 21, 2010 at 8:54 PM, Hans-Peter Jansen <hpj@urpla.net> wrote:
On Wednesday 21 April 2010, 16:29:15 David C. Rankin wrote:
On 04/21/2010 03:48 AM, Michael Schroeder wrote:
On Tue, Apr 20, 2010 at 11:07:59PM +0200, Hans-Peter Jansen wrote:
History: - 'repo2solv.sh' '-o' '/var/cache/zypp/solv/KDE_KDE3/solv' '/var/cache/zypp/raw/KDE_KDE3' Unknown checksum type: 8: sha256
Oops, we updated the createrepo package on the build service host to use some new features, and now all of the repos use sha256 checksums instead of sha1. Unfortunatelly libzypp in 11.1 and older can't handle that checksum (yet). We now use a createrepo option to use sha1 again for older repos, so things should work again for all freshly created build service repositories.
Sorry for the inconvenience.
Cheers, Michael.
Ahah,
You need to stay with the stable branch (0.4.11), the unstable branch (0.9.x) is a radically different beast altogether. I had to build yum, rpm, python-iniparser, etc... to build createrepo on Arch Linux to manage a couple of repositories there. There was no way to get the testing branch of createrepo to work with the current openSuSE repositories. (you may be able to do it, but I couldn't)
createrepo -s sha should do the trick (as it does for Michael, I guess)...
BTW, the KDE:KDE3 repo is fixed now, but I had to disable kvirc and qca, as those broke due to factory changes... While at it, I fixed python-kde3 and recovered kinternet.
Hopefully, most things are in shape again..
From those I´m using, KDE:KDE3, multimedia:/libs/openSUSE_11.1, multimedia:/audio:/KMP/openSUSE_11.1_Update are back, but KDE:Qt46, Education, home:/thomas-schraitle:/calibre/openSUSE_11.1/, Emulators:/Wine/openSUSE_11.1/ are still unaccessible. Waiting patiently...
Regards, -- Mark Goldstein -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday 21 April 2010, 20:14:29 Mark Goldstein wrote:
On Wed, Apr 21, 2010 at 8:54 PM, Hans-Peter Jansen <hpj@urpla.net> wrote:
Hopefully, most things are in shape again..
From those I´m using, KDE:KDE3, multimedia:/libs/openSUSE_11.1, multimedia:/audio:/KMP/openSUSE_11.1_Update are back, but KDE:Qt46, Education, home:/thomas-schraitle:/calibre/openSUSE_11.1/, Emulators:/Wine/openSUSE_11.1/ are still unaccessible. Waiting patiently...
Guys, all repos with home: in the name might be worth a mail to their respective maintainers with a _kind_ request to just make a minor change to _one_ package in the affected repo, and commit that. This will finally trigger a rebuild of the repo metadata, and these dreaded sha256 checksums will vanish.. Hopefully the masters of disaster will come up with a proper fix up of all affected repos soon. Cheers, Pete -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (2)
-
Hans-Peter Jansen -
Mark Goldstein