[Bug 417594] New: Build0019: Failed to cache repo
https://bugzilla.novell.com/show_bug.cgi?id=417594 Summary: Build0019: Failed to cache repo Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: libzypp AssignedTo: dmacvicar@novell.com ReportedBy: cthiel@novell.com QAContact: qa@suse.de CC: visnov@novell.com Found By: --- Created an attachment (id=233629) --> (https://bugzilla.novell.com/attachment.cgi?id=233629) screenshot Installation of Build0019 fails with the following error message -- see attachement. Logs will also be attached shortly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=417594 Christoph Thiel <cthiel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=417594 User cthiel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=417594#c1 --- Comment #1 from Christoph Thiel <cthiel@novell.com> 2008-08-15 07:50:55 MDT --- Created an attachment (id=233630) --> (https://bugzilla.novell.com/attachment.cgi?id=233630) yast logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=417594 User visnov@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=417594#c2 --- Comment #2 from Stanislav Visnovsky <visnov@novell.com> 2008-08-15 07:52:05 MDT --- BTW, the message should look more reasonably ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=417594 User dmacvicar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=417594#c3 --- Comment #3 from Duncan Mac-Vicar <dmacvicar@novell.com> 2008-08-15 08:00:37 MDT --- 2008-08-15 11:41:13 <2> linux(2958) [zypp] RepoManager.cc(buildCache):834 3299 Killed | susetags2solv -c "${olddir}/content" $parser_options 2008-08-15 11:41:13 <1> linux(2958) [zypp++] ExternalProgram.cc(checkStatus):345 Pid 3288 exited with status 4 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=417594 User dmacvicar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=417594#c4 --- Comment #4 from Duncan Mac-Vicar <dmacvicar@novell.com> 2008-08-15 08:08:34 MDT --- dmacvicar@piscola:/space/git/suse/zypp/sat-solver/build/tools> cat packages | susetags2solv -c ./content > solv Out of memory allocating 0 bytes! it does not work for the simple case. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=417594 User kkaempf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=417594#c5 --- Comment #5 from Klaus Kämpf <kkaempf@novell.com> 2008-08-15 08:21:34 MDT --- Argh, my bad. Put NAME before REFERENCES in the content file -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=417594 User kkaempf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=417594#c6 Klaus Kämpf <kkaempf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Klaus Kämpf <kkaempf@novell.com> 2008-08-15 08:22:46 MDT --- Explanation NAME triggers creation of the Solvable REFERENCES tries to store into. Having REFERENCES before NAME stores into a non-existing Solvable :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=417594 User kkaempf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=417594#c7 --- Comment #7 from Klaus Kämpf <kkaempf@novell.com> 2008-08-15 08:30:33 MDT --- Finally fixed in satsolver svn rev 10875, now order of tags (except for CONTENTSTYLE) doesn't matter. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=417594 User dmacvicar@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=417594#c8 --- Comment #8 from Duncan Mac-Vicar <dmacvicar@novell.com> 2008-08-15 08:30:57 MDT --- http://en.opensuse.org/Software_Repositories/YaST/content explicitly says: NAME must be the second tag of the content file So the parser is correct. It should only not complain with 0 bytes allocator but tell the product builder he should RT*M :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=417594 User kkaempf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=417594#c9 --- Comment #9 from Klaus Kämpf <kkaempf@novell.com> 2008-08-15 08:36:56 MDT --- (In reply to comment #8 from Duncan Mac-Vicar)
http://en.opensuse.org/Software_Repositories/YaST/content explicitly says: NAME must be the second tag of the content file
Yeah, thats what I just edited. Before (when Christoph looked at it) it requested REFERENCES as second tag.
So the parser is correct. It should only not complain with 0 bytes allocator but tell the product builder he should RT*M :-)
No, the parser is^wwas buggy. :-( Quick fix: see comment #5 Real fix: submit a new satsolver(-tools) package -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com