Bug 358853 - repositories factory oss and non oss repomd.xml broken, no update possible.
Summary: repositories factory oss and non oss repomd.xml broken, no update possible.
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Update Problems (show other bugs)
Version: Alpha 2
Hardware: x86 openSUSE 11.0
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Jan Kupec
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-05 14:39 UTC by Casual J. Programmer
Modified: 2008-02-11 11:42 UTC (History)
1 user (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Casual J. Programmer 2008-02-05 14:39:01 UTC 
http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/repodata/repomd.xml

contains:

XML Parsing Error: syntax error
Location: http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/repodata/repomd.xml
Line Number 1, Column 1:-----BEGIN PGP PUBLIC KEY BLOCK-----
^
Comment 1 Felix Möller 2008-02-05 15:05:06 UTC 
This is a duplicate of bug #358429. As far as I can see.

*** This bug has been marked as a duplicate of bug 358429 ***
Comment 2 Casual J. Programmer 2008-02-06 12:05:11 UTC 
I think this still needs some attention:

While smart can now update properly, zypper cannot, it doesn't show _any_ updates with zypper -lu -t package nor does it do anything on zypper dup.

Also the repository at http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/i586/ contains old and new packages together.
Comment 3 Jan Kupec 2008-02-10 04:26:38 UTC 
Works for me, does it still occur? If not, please attach also zypper.log (remove the old log before reproducing).
Comment 4 Casual J. Programmer 2008-02-10 08:52:25 UTC 
Works for me too. 

Alas it took almost 5 days to stabilize. I suggest that the repository sync process is redesigned, in a way that makes the publicly available repository only accessible when stabilized. Otherwise public alpha / beta testing is completely unreliable and a waste of time for all participants.
Comment 5 Jan Kupec 2008-02-11 11:42:53 UTC 
I guess it was an accident, but i don't have much info. CCing Coolo in case he has something to say to your suggestion.

OK, so as for this bug, closing as FIXED.