[opensuse] Zypper data probably corrupted, how to re-create?

newer
[opensuse] full disk encryption...

older
[opensuse] Re: [opensuse-announce]...

Mark Goldstein

20 Apr 2010 20 Apr '10

14:04

Hello, I´m on oS 11.1 (32bit) + KDE3. Recently I noticed that something is wrong with zypper db. Somehow it lost information about a number of repositories. For example, I have http://download.opensuse.org/repositories/KDE:/Qt46/openSUSE_11.1 added and I have 12 packages, installed from this repository (according to rpm), but zypper/yast indicates no packages from this repo. E.g. rpm -qa|xargs rpm -qi|grep -ic qt46 returns 12, but zypper pa|grep -ic qt46 returns 0. One package from this repo is definitely libqt4: === #zypper if libqt4 Loading repository data... Reading installed packages... Information for package libqt4: Repository: @System Name: libqt4 Version: 4.6.3+4.6.20100413-1.1 Arch: i586 Vendor: openSUSE Build Service Installed: Yes Status: up-to-date Installed Size: 12.5 M Summary: C++ Program Library, Core Components Description: Qt is a set of libraries for developing applications. This package contains base tools, like string, xml, and network handling. What is @System?? === # rpm -qi libqt4 Name : libqt4 Relocations: (not relocatable) Version : 4.6.3+4.6.20100413 Vendor: openSUSE Build Service Release : 1.1 Build Date: Tue Apr 13 06:20:35 2010 Install Date: Tue Apr 13 20:20:43 2010 Build Host: build19 Group : System/Libraries Source RPM: libqt4-4.6.3+4.6.20100413-1.1.src.rpm Size : 13086939 License: GPL v3 only ; LGPL v2.1 or later Signature : DSA/SHA1, Tue Apr 13 06:31:32 2010, Key ID 58d8ff412e1efa87 URL : http://www.qtsoftware.com Summary : C++ Program Library, Core Components Description : Qt is a set of libraries for developing applications. This package contains base tools, like string, xml, and network handling. Authors: -------- Qt Software Distribution: KDE:Qt46 / openSUSE_11.1 ========== In Yast / Software management if I choose ¨Filter: Repositories¨, yast shows @System repo and many packages in it which definitely belong to some real repos. At the same time, it shows no packages in KDE:Qt46. I remember some advices of how to re-create zypper db, but could not find them right now in archive. Could someone please advice? TIA, -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Show replies by date

Mark Goldstein

20 Apr 20 Apr

16:41

New subject: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On Tue, Apr 20, 2010 at 5:04 PM, Mark Goldstein wrote:

...

Hello,

I´m on oS 11.1 (32bit) + KDE3. Recently I noticed that something is wrong with zypper db. Somehow it lost information about a number of repositories. For example, I have http://download.opensuse.org/repositories/KDE:/Qt46/openSUSE_11.1 added and I have 12 packages, installed from this repository (according to rpm), but zypper/yast indicates no packages from this repo.

E.g. rpm -qa|xargs rpm -qi|grep -ic qt46 returns 12, but zypper pa|grep -ic qt46 returns 0.

One package from this repo is definitely libqt4:

===

#zypper if libqt4 Loading repository data... Reading installed packages...

Information for package libqt4:

Repository: @System Name: libqt4 Version: 4.6.3+4.6.20100413-1.1 Arch: i586 Vendor: openSUSE Build Service Installed: Yes Status: up-to-date Installed Size: 12.5 M Summary: C++ Program Library, Core Components Description: Qt is a set of libraries for developing applications.

This package contains base tools, like string, xml, and network handling.

What is @System??

=== # rpm -qi libqt4 Name : libqt4 Relocations: (not relocatable) Version : 4.6.3+4.6.20100413 Vendor: openSUSE Build Service Release : 1.1 Build Date: Tue Apr 13 06:20:35 2010 Install Date: Tue Apr 13 20:20:43 2010 Build Host: build19 Group : System/Libraries Source RPM: libqt4-4.6.3+4.6.20100413-1.1.src.rpm Size : 13086939 License: GPL v3 only ; LGPL v2.1 or later Signature : DSA/SHA1, Tue Apr 13 06:31:32 2010, Key ID 58d8ff412e1efa87 URL : http://www.qtsoftware.com Summary : C++ Program Library, Core Components Description : Qt is a set of libraries for developing applications.

This package contains base tools, like string, xml, and network handling.

Authors: -------- Qt Software Distribution: KDE:Qt46 / openSUSE_11.1

==========

In Yast / Software management if I choose ¨Filter: Repositories¨, yast shows @System repo and many packages in it which definitely belong to some real repos. At the same time, it shows no packages in KDE:Qt46.

I remember some advices of how to re-create zypper db, but could not find them right now in archive.

I removed everything in /var/cache/zypp and re-created with zypper refresh, but nothing changed. Started thinking, maybe it is something with repositories themselves (at least 2 of problematic ones were updated this morning - KDE:Qt46 and KDE:KDE3, though the files in repositories look OK). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

David C. Rankin

16:54

New subject: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On 04/20/2010 11:41 AM, Mark Goldstein wrote:

...

I removed everything in /var/cache/zypp and re-created with zypper refresh, but nothing changed. Started thinking, maybe it is something with repositories themselves (at least 2 of problematic ones were updated this morning - KDE:Qt46 and KDE:KDE3, though the files in repositories look OK).

Mark, I don't know if this is your problem, but I have had a number of issues with the 'download.opensuse.org' redirector system lately. To cure this I've eliminated the redirector system by just choosing and using a specific mirror. This has completely cured my problems with slow/no downloads. For example, instead of: http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.0/ I use: http://ftp5.gwdg.de/pub/opensuse/repositories/KDE:/KDE3/openSUSE_11.0/ When looking at the packages at download.opensuse.org, you can just click on the 'mirrors' link and select an individual site. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Mark Goldstein

17:24

New subject: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On Tue, Apr 20, 2010 at 7:54 PM, David C. Rankin wrote:

...

On 04/20/2010 11:41 AM, Mark Goldstein wrote:

...
I removed everything in /var/cache/zypp and re-created with zypper refresh, but nothing changed. Started thinking, maybe it is something with repositories themselves (at least 2 of problematic ones were updated this morning - KDE:Qt46 and KDE:KDE3, though the files in repositories look OK).

Mark,

I don't know if this is your problem, but I have had a number of issues with the 'download.opensuse.org' redirector system lately. To cure this I've eliminated the redirector system by just choosing and using a specific mirror. This has completely cured my problems with slow/no downloads. For example, instead of:

http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.0/

I use:

http://ftp5.gwdg.de/pub/opensuse/repositories/KDE:/KDE3/openSUSE_11.0/

When looking at the packages at download.opensuse.org, you can just click on the 'mirrors' link and select an individual site.

David, Thank you for suggestion. I tried defining specific mirror, but the problem persists. I did it with Qt6 and still for the packages from this repo Yast shows the ïnstalled versions in red, alternative versions being older and belonging to @System... Like zypper could not see any packages in the repo. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

David C. Rankin

18:05

New subject: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On 04/20/2010 12:24 PM, Mark Goldstein wrote:

...

On Tue, Apr 20, 2010 at 7:54 PM, David C. Rankin wrote:

...
On 04/20/2010 11:41 AM, Mark Goldstein wrote:

...
I removed everything in /var/cache/zypp and re-created with zypper refresh, but nothing changed. Started thinking, maybe it is something with repositories themselves (at least 2 of problematic ones were updated this morning - KDE:Qt46 and KDE:KDE3, though the files in repositories look OK).

Mark,

I don't know if this is your problem, but I have had a number of issues with the 'download.opensuse.org' redirector system lately. To cure this I've eliminated the redirector system by just choosing and using a specific mirror. This has completely cured my problems with slow/no downloads. For example, instead of:

http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.0/

I use:

http://ftp5.gwdg.de/pub/opensuse/repositories/KDE:/KDE3/openSUSE_11.0/

When looking at the packages at download.opensuse.org, you can just click on the 'mirrors' link and select an individual site.

David,

Thank you for suggestion. I tried defining specific mirror, but the problem persists. I did it with Qt6 and still for the packages from this repo Yast shows the ïnstalled versions in red, alternative versions being older and belonging to @System... Like zypper could not see any packages in the repo.

Oh... You are getting caught by the new zypper setting that prevents new users from changing the source of packages.... I disabled that in 11.2 and all was well. I can't remember it being in 11.1, but I haven't used 11.1 in ages so it may have been added. From memory, in Yast SW mgmt, you should either be able to rt-click the packages in red and choose something like "change source of package to new source" or "allow update from xyz source", I don't recall exactly. You may also try choosing the repository filter (instead of the default 'search') filter and then look at the individual repository containing the packages, then I believe you will have a clickable selection at the top of the package list that lets you update to packages in that repository. The bottom line is the setting in /etc/zypp/zypp.conf - here is a snippet: The Issues All distro releases have bugs – including openSUSE, many of which will of course be fixed via online updates in the coming weeks and months. However so far I’m not aware of any major bugs that will cause a lot of grief to legions of people. I predict that the thing that will cause the most people to say “wtf!?!” in 11.2 is actually intended behaviour. YaST/zypper will not show nor perform updates that involve “vendor changes” (i.e. updating an official package to a newer version of the same software from packman) unless the user explicitly does some extra work. You roughly have these coping strategies: * Don’t worry about it and stick with the old versions included in the distro no matter how many 3rd party repositories you add. * Manually go to the Repositories tab or the Versions tab in YaST Software Management, and manually select the updates you want – or manually specify the versions you want on the command line with zypper (note, you only have to do the extra work to change vendor once per package). * Set AllowVendorChange = true in /etc/zypp/zypp.conf – this way YaST/zypper will update everything to whatever has the highest version number – and let you ping-pong back and forth between package vendors, if that’s what you want. In the future the tools are expected to be improved, so that the vendor stickyness becomes less annoying and obtrusive. from: http://mschlander.wordpress.com/2009/11/11/opensuse-11-2-coming/ -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Mark Goldstein

18:26

New subject: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On Tue, Apr 20, 2010 at 9:05 PM, David C. Rankin wrote:

...

On 04/20/2010 12:24 PM, Mark Goldstein wrote:

...
On Tue, Apr 20, 2010 at 7:54 PM, David C. Rankin wrote:

...
On 04/20/2010 11:41 AM, Mark Goldstein wrote:

...
I removed everything in /var/cache/zypp and re-created with zypper refresh, but nothing changed. Started thinking, maybe it is something with repositories themselves (at least 2 of problematic ones were updated this morning - KDE:Qt46 and KDE:KDE3, though the files in repositories look OK). Oh...

You are getting caught by the new zypper setting that prevents new users from changing the source of packages.... I disabled that in 11.2 and all was well. I can't remember it being in 11.1, but I haven't used 11.1 in ages so it may have been added.

From memory, in Yast SW mgmt, you should either be able to rt-click the packages in red and choose something like "change source of package to new source" or "allow update from xyz source", I don't recall exactly. You may also try choosing the repository filter (instead of the default 'search') filter and then look at the individual repository containing the packages, then I believe you will have a clickable selection at the top of the package list that lets you update to packages in that repository.

The bottom line is the setting in /etc/zypp/zypp.conf - here is a snippet:

The Issues

All distro releases have bugs – including openSUSE, many of which will of course be fixed via online updates in the coming weeks and months. However so far I’m not aware of any major bugs that will cause a lot of grief to legions of people.

I predict that the thing that will cause the most people to say “wtf!?!” in 11.2 is actually intended behaviour. YaST/zypper will not show nor perform updates that involve “vendor changes” (i.e. updating an official package to a newer version of the same software from packman) unless the user explicitly does some extra work.

You roughly have these coping strategies:

* Don’t worry about it and stick with the old versions included in the distro no matter how many 3rd party repositories you add. * Manually go to the Repositories tab or the Versions tab in YaST Software Management, and manually select the updates you want – or manually specify the versions you want on the command line with zypper (note, you only have to do the extra work to change vendor once per package). * Set AllowVendorChange = true in /etc/zypp/zypp.conf – this way YaST/zypper will update everything to whatever has the highest version number – and let you ping-pong back and forth between package vendors, if that’s what you want.

In the future the tools are expected to be improved, so that the vendor stickyness becomes less annoying and obtrusive.

from: http://mschlander.wordpress.com/2009/11/11/opensuse-11-2-coming/

Thanks again for explanations. Not sure that this is my issue. The problem is that when I select these repositories using ¨Filter¨ Repositories, I see no packages at all... (e.g. in KDE:Qt46, wine snapshots and so on). My impression is that these repositories undergo some changes today. I´m getting something new almost every time, like message about wrong type of checksum (it has already been discussed on the list). Probably I´ll need to wait for some time. Anyway, tried adding AllowVendorChange = true to zypp.conf - nothing changed. Probably this is not applicable to 11.1 -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hans-Peter Jansen

21:07

New subject: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On Tuesday 20 April 2010, 20:26:16 Mark Goldstein wrote:

...

On Tue, Apr 20, 2010 at 9:05 PM, David C. Rankin

wrote:

...
On 04/20/2010 12:24 PM, Mark Goldstein wrote:

...
On Tue, Apr 20, 2010 at 7:54 PM, David C. Rankin

wrote:

...
On 04/20/2010 11:41 AM, Mark Goldstein wrote:

...
I removed everything in /var/cache/zypp and re-created with zypper refresh, but nothing changed. Started thinking, maybe it is something with repositories themselves (at least 2 of problematic ones were updated this morning - KDE:Qt46 and KDE:KDE3, though the files in repositories look OK).

Mark, I noticed the exact same problem with KDE:KDE3 here, been through cache cleanup et al., and problem persists. While I have no solution for this issue, here are some more more or less educated guesses, hence the crosspost to buildservice. Mark and me have problems with certain repos from build service for 11.1, where zypper doesn't see any packages from that repo. # zyp se -s -r KDE_KDE3 Verbosity: 1 Initializing Target Checking whether to refresh metadata for Latest KDE 3 environment for released SUSE distributions (openSUSE_11.1) Retrieving: repomd.xml [done] Retrieving: repomd.xml [done] Retrieving: repomd.xml.asc [done] Retrieving: repomd.xml.key [done] Retrieving: repomd.xml [done] Retrieving: primary.xml.gz [done] Retrieving repository 'Latest KDE 3 environment for released SUSE distributions (openSUSE_11.1)' metadata [done] Building repository 'Latest KDE 3 environment for released SUSE distributions (openSUSE_11.1)' cache [done] Error building the cache: History: - 'repo2solv.sh' '-o' '/var/cache/zypp/solv/KDE_KDE3/solv' '/var/cache/zypp/raw/KDE_KDE3' Unknown checksum type: 8: sha256 - [|] Failed to cache repo (4). Warning: Disabling repository 'Latest KDE 3 environment for released SUSE distributions (openSUSE_11.1)' because of the above error. Loading repository data... Reading installed packages... Force resolution: No No packages found. Ahh, zypper chokes on sha256. If I compare these repos with those that operate correctly, there are significant differences in the repomd.xml. Here I'm going to compare the packman 11.1 repo (okay) with KDE:KDE3 for openSUSE_11.1: Let's compare the primary data section, first packman: <data type="primary"> <location href="repodata/primary.xml.gz"/> <checksum type="sha">57ac66c34bdf5c44fd2cdb00fb07620706f0c4f8</checksum> <timestamp>1271759831</timestamp> <open-checksum type="sha">2cb77a5d202f6572e86a2027637bb682b832b20f</open-checksum> </data> and here KDE:KDE3: <data type="primary"> <checksum type="sha256">1805495e28cdff0b638fb19db31091045be88eae2f48ba2ab8ee845bfe3203bb</checksum> <timestamp>1271737040</timestamp> <size>408803</size> <open-size>3136333</open-size> <open-checksum type="sha256">3561980446cb496f46c9b88d6fd0af34de6154060c7ff81c8b87467abd58e08c</open-checksum> <location href="repodata/1805495e28cdff0b638fb19db31091045be88eae2f48ba2ab8ee845bfe3203bb-primary.xml.gz"/> </data> Indeed, checksum is sha256 now. Let's check: # grep 'type="sha256"' $(find /var/cache/zypp/raw -name repomd.xml) results in KDE_KDE3, devel_tools, openSUSE_Factory_Contrib, and openSUSE_Tools_Unstable repos with sha256 checksums. Let's pick another one: # zyp se -s -r openSUSE_Tools_Unstable Verbosity: 1 Initializing Target Checking whether to refresh metadata for Stabilizing version of the openSUSE Tools (openSUSE_11.1) Loading repository data... Reading installed packages... Force resolution: No No packages found. Well, it should. Cross check: # zyp se -s -r KDE4_11.1 Verbosity: 1 Initializing Target Checking whether to refresh metadata for KDE 4.3.5 (openSUSE_11.1) Loading repository data... Reading installed packages... Force resolution: No S | Name | Type | Version | Arch | Repository --+--------------------------------------+------------+-----------------------+--------+-------------------------- | KDE 4 Devel | pattern | | noarch | KDE 4.3.5 (openSUSE_11.1) | KDE 4 Games | pattern | | noarch | KDE 4.3.5 (openSUSE_11.1) i | KDE 4.1 Basis | pattern | | noarch | KDE 4.3.5 (openSUSE_11.1) | NetworkManager-kde4 | package | 0.9.svn1043876-4.10 | i586 | KDE 4.3.5 (openSUSE_11.1) [...] Expected output. The question is, how do we trick BS, namely publisher to generate palatable repo descriptions for our systems? Of course, we could mirror the offending repos locally, and run createrepo on them :-( , but there ought to be an easier way, doesn't it? TIA, Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Marcus Rueckert

22:18

New subject: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

someone needs to trigger publishing for the affect repositories. adrian could we do that on our side to get them all fixed at once? darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hans-Peter Jansen

22:50

New subject: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On Wednesday 21 April 2010, 00:18:58 Marcus Rueckert wrote:

...

someone needs to trigger publishing for the affect repositories. adrian could we do that on our side to get them all fixed at once?

Marcus, yeah, that would be fine. But what does prevent the regeneration of the issues again and again... Did somebody fix this issue meanwhile? Thanks, Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

David C. Rankin

21 Apr 21 Apr

06:36

New subject: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On 04/20/2010 05:18 PM, Marcus Rueckert wrote:

...

someone needs to trigger publishing for the affect repositories. adrian could we do that on our side to get them all fixed at once?

darix

Marcus, Hans, You guys seem to know what is going on with this problem. I guess some of the metadata is hosed and there isn't anyway to trigger createrepo on the mirrors to fix it... or something to that effect. Any guestimation on the time we are looking at until this gets fixed? Is this one of those things where we are going to have to wait on the new metadata to propagate to all the mirrors after it has been created? Thanks for any additional information you can provide. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Michael Schueller

07:35

New subject: [opensuse] Re: Zypper data probably corrupted, how to re-create?

Am Dienstag, 20. April 2010 schrieb Hans-Peter Jansen:

...

Mark, I noticed the exact same problem with KDE:KDE3 here, been through cache cleanup et al., and problem persists.

While I have no solution for this issue, here are some more more or less educated guesses, hence the crosspost to buildservice.

Mark and me have problems with certain repos from build service for 11.1, where zypper doesn't see any packages from that repo.

Same Problem here ... Zwischenspeicher für Repository 'openSUSE BuildService - KDE3' wird erzeugt [fertig] Fehler beim Bau des Zwischenspeichers: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/openSUSE_BuildService_-_KDE3/solv' '/var/cache/zypp/raw/openSUSE_BuildService_-_KDE3' Unknown checksum type: 8: sha256 Warnung: Repository 'openSUSE BuildService - KDE3' wird aufgrund des obigen Fehlers deaktiviert. Zwischenspeicher für Repository 'openSUSE BuildService - KDE4 Desktop' wird erzeugt [fertig] Fehler beim Bau des Zwischenspeichers: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/openSUSE_BuildService_-_KDE4_Desktop/solv' '/var/cache/zypp/raw/openSUSE_BuildService_-_KDE4_Desktop' Unknown checksum type: 8: sha256 Warnung: Repository 'openSUSE BuildService - KDE4 Desktop' wird aufgrund des obigen Fehlers deaktiviert. Zwischenspeicher für Repository 'openSUSE BuildService - Wine-CVS-Pakete' wird erzeugt [fertig] Fehler beim Bau des Zwischenspeichers: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/repo_1/solv' '/var/cache/zypp/raw/repo_1' Unknown checksum type: 8: sha256 Warnung: Repository 'openSUSE BuildService - Wine-CVS-Pakete' wird aufgrund des obigen Fehlers deaktiviert. Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Michael Schroeder

08:48

New subject: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

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. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

David C. Rankin

14:29

New subject: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

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) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hans-Peter Jansen

17:54

New subject: [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+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Togan Muftuoglu

18:10

New subject: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

Hans-Peter Jansen wrote:

...

Hopefully, most things are in shape again..

Well on my side (for opensuse 11.1) the following are broken and KDE4 and Publishing are the most important ones for me KDE:KDE4:STABLE:Desktop M17N Publishing Mozilla Repo Togan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Mark Goldstein

18:14

New subject: [opensuse-kde] Re: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On Wed, Apr 21, 2010 at 8:54 PM, Hans-Peter Jansen 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+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hans-Peter Jansen

21:24

New subject: [opensuse-kde] Re: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On Wednesday 21 April 2010, 20:14:29 Mark Goldstein wrote:

...

On Wed, Apr 21, 2010 at 8:54 PM, Hans-Peter Jansen 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+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

David C. Rankin

23:49

New subject: [opensuse-kde] Re: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On 04/21/2010 01:14 PM, Mark Goldstein wrote:

...

...
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

Of course we could always claim this whole mess is Mark's fault. After all he is the one that brought the issue up to begin with. And... we all know, "The guilty dog barks first!" Shame shame Mark. ;-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

David C. Rankin

19:26

New subject: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On 04/21/2010 12:54 PM, Hans-Peter Jansen wrote:

...

...
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

Pete, Thanks for the help with the kde3 repo. See, I know you guys could figure a way to get the new createrepo to work. When I was playing with it, it would just spit errors back at me. I ran out of time to play with it and just went back to the stable branch. Which works great running on arch. The old issue I currently have in the repo management routine is a few deprecated warnings from repoview, but until the stable branch stops working, I think I'll hold there until I get time to learn the new version :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

David C. Rankin

19:35

New subject: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On 04/21/2010 12:54 PM, Hans-Peter Jansen wrote:

...

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

Great, things are getting better. Many of the 11.0 repo errors are fixed. Here is the current issues for my 11.0 repositories: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/sbstd/solv' '/var/cache/zypp/raw/sbstd' (repositories/home:/sbrabec:/branches:/graphics/standard/) 'repo2solv.sh' '-o' '/var/cache/zypp/solv/security/solv' '/var/cache/zypp/raw/security' (repositories/security/openSUSE_11.0) 'repo2solv.sh' '-o' '/var/cache/zypp/solv/edu/solv' '/var/cache/zypp/raw/edu' (/repositories/Education/openSUSE_11.0) 'repo2solv.sh' '-o' '/var/cache/zypp/solv/monitor/solv' '/var/cache/zypp/raw/monitor' (repositories/server:/monitoring/openSUSE_11.0) 'repo2solv.sh' '-o' '/var/cache/zypp/solv/lxde-gwdg/solv' '/var/cache/zypp/raw/lxde-gwdg' (repositories/X11:/lxde/openSUSE_11.0) Thanks again for your help! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hans-Peter Jansen

21:12

New subject: [opensuse-buildservice] Re: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On Wednesday 21 April 2010, 10:48:50 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.

This isn't an simple inconvenience. It's grown to a large scale denial of update service thread, and those of us who suffer from this might have to wait for weeks, until some packages _with differences_¹ are build by chance in all these damaged repos. Those of us, who are using the build service heavily, are even punished harder: we need to do "zypper dup" all the time to get really all updated packages, and it's not unusual, that the update list is huge. Now if you're not _really_ careful, you're going to shot yourself in both knees: all packages from damaged repos get downgraded to the basic repos. Needless to say, that this will damage the build service reputation as a whole for quite some time.. Hence, fix this as soon as possible please or give me a shell account with access to all repos and I'm going to fix it with an ad hoc script this night. Thanks, Pete ¹) which is a feature, as Adrian noted, but one that's biting us now.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

David C. Rankin

20 Apr 20 Apr

21:58

New subject: [opensuse] Re: Zypper data probably corrupted, how to re-create?

On 04/20/2010 01:26 PM, Mark Goldstein wrote:

...

Thanks again for explanations. Not sure that this is my issue. The problem is that when I select these repositories using ¨Filter¨ Repositories, I see no packages at all... (e.g. in KDE:Qt46, wine snapshots and so on). My impression is that these repositories undergo some changes today. I´m getting something new almost every time, like message about wrong type of checksum (it has already been discussed on the list). Probably I´ll need to wait for some time. Anyway, tried adding AllowVendorChange = true to zypp.conf - nothing changed. Probably this is not applicable to 11.1

Well, You can always try to download them to your box and then installing them with rpm -Uvh. The easiest way is to use 'lynx -dump' to get a listing of the rpms, then save the list as a txt file and use the list as the getfile for 'wget -i getfile -b' and let wget download the rpms for you. At one time I had a script that automated this, but I don't know where it is currently. But basically use lynx -dump and sed as follows: lynx -dump http://download.opensuse.org/repositories/<repo-you-want>/openSUSE_11.0/i586/ | sed -e 's/^......//' that will give you a list like this: http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... <snip> Then just cut & paste what you want into a text file (i.e. getfile.txt): http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... http://ftp5.gwdg.de/pub/opensuse/repositories/home:/hennichodernich:/backpor... Then just call wget like this: wget -i getfile.txt -b ## -b just sends the process to the background When it's done, if you have the files isolated in a directory, then just: rpm -Uvh dirToFiles/*.rpm done... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

David C. Rankin

21 Apr 21 Apr

01:41

New subject: SuSE - Repositories Broken (Unknown checksum type: 7: sha256) (was [Re: [opensuse] Zypper data probably corrupted, how to re-create?]

On 04/20/2010 09:04 AM, Mark Goldstein wrote:

...

Hello,

I´m on oS 11.1 (32bit) + KDE3. Recently I noticed that something is wrong with zypper db. Somehow it lost information about a number of repositories. For example, I have http://download.opensuse.org/repositories/KDE:/Qt46/openSUSE_11.1 added and I have 12 packages, installed from this repository (according to rpm), but zypper/yast indicates no packages from this repo.

E.g. rpm -qa|xargs rpm -qi|grep -ic qt46 returns 12, but zypper pa|grep -ic qt46 returns 0.

One package from this repo is definitely libqt4:

===

#zypper if libqt4 Loading repository data... Reading installed packages...

Information for package libqt4:

Repository: @System Name: libqt4 Version: 4.6.3+4.6.20100413-1.1 Arch: i586 Vendor: openSUSE Build Service Installed: Yes Status: up-to-date Installed Size: 12.5 M Summary: C++ Program Library, Core Components Description: Qt is a set of libraries for developing applications.

This package contains base tools, like string, xml, and network handling.

What is @System??

=== # rpm -qi libqt4 Name : libqt4 Relocations: (not relocatable) Version : 4.6.3+4.6.20100413 Vendor: openSUSE Build Service Release : 1.1 Build Date: Tue Apr 13 06:20:35 2010 Install Date: Tue Apr 13 20:20:43 2010 Build Host: build19 Group : System/Libraries Source RPM: libqt4-4.6.3+4.6.20100413-1.1.src.rpm Size : 13086939 License: GPL v3 only ; LGPL v2.1 or later Signature : DSA/SHA1, Tue Apr 13 06:31:32 2010, Key ID 58d8ff412e1efa87 URL : http://www.qtsoftware.com Summary : C++ Program Library, Core Components Description : Qt is a set of libraries for developing applications.

This package contains base tools, like string, xml, and network handling.

Authors: -------- Qt Software Distribution: KDE:Qt46 / openSUSE_11.1

==========

In Yast / Software management if I choose ¨Filter: Repositories¨, yast shows @System repo and many packages in it which definitely belong to some real repos. At the same time, it shows no packages in KDE:Qt46.

I remember some advices of how to re-create zypper db, but could not find them right now in archive.

Could someone please advice? TIA,

Mark, Devs, the repositories and/or zypper are broken for a large number of repositories. I get multiple failures when trying to refresh my repositories all of the form: Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/fact-kde4/solv' '/var/cache/zypp/raw/fact-kde4' Unknown checksum type: 15: sha256 Skipping repository 'fact-kde4' because of the above error. -- or -- Building repository 'gwdg-k3' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/gwdg-k3/solv' '/var/cache/zypp/raw/gwdg-k3' Unknown checksum type: 7: sha256 Skipping repository 'gwdg-k3' because of the above error. I don't know what in the heck it means by: "Unknown checksum type: 7" other than it got the wrong checksum. But if that's the case, then roughly 30%-40% of all repositories are hosed. Here is the actual output for my 'zypper ref': [20:32 alchemy:/home/david] # zypper ref Repository 'gwdg-k3comm' is up to date. Repository 'gwdg-oostable' is up to date. Repository 'fact-kde4' is up to date. Building repository 'fact-kde4' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/fact-kde4/solv' '/var/cache/zypp/raw/fact-kde4' Unknown checksum type: 15: sha256 Skipping repository 'fact-kde4' because of the above error. Repository 'gwdg-k3' is up to date. Building repository 'gwdg-k3' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/gwdg-k3/solv' '/var/cache/zypp/raw/gwdg-k3' Unknown checksum type: 7: sha256 Skipping repository 'gwdg-k3' because of the above error. Repository 'k3' is up to date. Building repository 'k3' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/k3/solv' '/var/cache/zypp/raw/k3' Unknown checksum type: 7: sha256 Skipping repository 'k3' because of the above error. Repository 'sbstd' is up to date. Building repository 'sbstd' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/sbstd/solv' '/var/cache/zypp/raw/sbstd' cat: primary.xml*: No such file or directory repo_rpmmd: no element found at line 1:0 Skipping repository 'sbstd' because of the above error. Repository 'debugupdt' is up to date. Repository 'rmtdsktp' is up to date. Downloading repository 'fact-kde4play' metadata [done] Building repository 'fact-kde4play' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/fact-kde4play/solv' '/var/cache/zypp/raw/fact-kde4play' Unknown checksum type: 7: sha256 Skipping repository 'fact-kde4play' because of the above error. Repository 'moz' is up to date. Repository 'security' is up to date. Building repository 'security' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/security/solv' '/var/cache/zypp/raw/security' Unknown checksum type: 7: sha256 Skipping repository 'security' because of the above error. Repository 'gwdg-update' is up to date. Repository 'xgl' is up to date. Repository 'subpixel' is up to date. Repository 'pwd-gwdg' is up to date. Repository 'edu' is up to date. Building repository 'edu' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/edu/solv' '/var/cache/zypp/raw/edu' Unknown checksum type: 7: sha256 Skipping repository 'edu' because of the above error. Repository 'mm' is up to date. Building repository 'mm' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/mm/solv' '/var/cache/zypp/raw/mm' cat: primary.xml*: No such file or directory repo_rpmmd: no element found at line 1:0 Skipping repository 'mm' because of the above error. Repository 'tools' is up to date. Building repository 'tools' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/tools/solv' '/var/cache/zypp/raw/tools' Unknown checksum type: 7: sha256 Skipping repository 'tools' because of the above error. Repository 'gccdev' is up to date. Repository 'selinux' is up to date. Repository 'monitor' is up to date. Repository 'jaddon' is up to date. Repository 'wm' is up to date. Repository 'pm' is up to date. Repository 'javapkg' is up to date. Repository 'openSUSE-11.0-Oss' is up to date. Repository 'sbfact' is up to date. Repository 'bzr' is up to date. Repository 'xfce' is up to date. Repository 'games' is up to date. Repository 'e' is up to date. Repository 'science' is up to date. Downloading repository 'fact-kde4comm' metadata [done] Building repository 'fact-kde4comm' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/fact-kde4comm/solv' '/var/cache/zypp/raw/fact-kde4comm' Unknown checksum type: 23: sha256 Skipping repository 'fact-kde4comm' because of the above error. Repository 'lxde-gwdg' is up to date. Building repository 'lxde-gwdg' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/lxde-gwdg/solv' '/var/cache/zypp/raw/lxde-gwdg' Unknown checksum type: 7: sha256 Skipping repository 'lxde-gwdg' because of the above error. Repository 'debuggwdg' is up to date. Repository 'php' is up to date. Repository 'cpplib' is up to date. Repository 'jengle' is up to date. Repository 'gnome-gwdg' is up to date. Repository 'xine-gwdg' is up to date. Repository 'gwdg-x11' is up to date. Repository 'skyline' is up to date. Repository 'gnome1' is up to date. Repository 'mmaps' is up to date. Building repository 'mmaps' cache [done] Error building the cache database: 'repo2solv.sh' '-o' '/var/cache/zypp/solv/mmaps/solv' '/var/cache/zypp/raw/mmaps' cat: primary.xml*: No such file or directory repo_rpmmd: no element found at line 1:0 Skipping repository 'mmaps' because of the above error. Repository 'videolan' is up to date. Repository 'gwdg-gcomm' is up to date. Repository 'sambatest' is up to date. Repository 'photo-gwdg' is up to date. Repository 'gwdg-k3back' is up to date. Some of the repositories have not been refreshed because of an error. A list of my current repositories can be found at the following location to help those interested correlate the errors above to the actual repositories: http://www.3111skyline.com/dl/bugs/zypp/repos-current.repo -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

5125

Age (days ago)

5126

Last active (days ago)

List overview

Download

22 comments

7 participants

participants (7)

David C. Rankin
Hans-Peter Jansen
Marcus Rueckert
Mark Goldstein
Michael Schroeder
Michael Schueller
Togan Muftuoglu