On Tuesday 20 April 2010, 20:26:16 Mark Goldstein wrote:
On Tue, Apr 20, 2010 at 9:05 PM, David C. Rankin
<drankinatty@suddenlinkmail.com> wrote:
On 04/20/2010 12:24 PM, Mark Goldstein wrote:
On Tue, Apr 20, 2010 at 7:54 PM, David C. Rankin
<drankinatty@suddenlinkmail.com> 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-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org