[Bug 429083] New: Incorrect parsing of package versions (.9 > .10)
https://bugzilla.novell.com/show_bug.cgi?id=429083 Summary: Incorrect parsing of package versions (.9 > .10) Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: christopher.lang@acurana.de QAContact: adrian@novell.com Found By: --- If there are for example the following rpm's in a build repository: kernel-default-2.6.18.8-0.10.i586.rpm kernel-default-2.6.18.8-0.1.i586.rpm kernel-default-2.6.18.8-0.3.i586.rpm kernel-default-2.6.18.8-0.5.i586.rpm kernel-default-2.6.18.8-0.7.i586.rpm kernel-default-2.6.18.8-0.8.i586.rpm kernel-default-2.6.18.8-0.9.i586.rpm the .9 package is taken as the latest version (instead of the .10). tested with: obs-server-0.5-3.1 obs-worker-0.5-3.1 obs-api-0.5-3.1 -- 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=429083 User christopher.lang@acurana.de added comment https://bugzilla.novell.com/show_bug.cgi?id=429083#c1 Christopher Lang <christopher.lang@acurana.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christopher.lang@acurana.de --- Comment #1 from Christopher Lang <christopher.lang@acurana.de> 2008-09-23 05:54:14 MDT --- it seems to be worse: Even with a "preferred" statement in the conf like Prefer: kernel-default-2.6.18.8-0.10 it ignores the .10 version. Support: kernel-default-2.6.18.8-0.10 in the conf leads to expansion error. It seems that if there is a .1 version a .10 version will be ignored. -- 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=429083 User adrian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=429083#c2 Adrian Schröter <adrian@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mls@novell.com Priority|P5 - None |P2 - High --- Comment #2 from Adrian Schröter <adrian@novell.com> 2008-09-27 15:09:15 MDT --- Micha, this can become also a problem with the SLES update channels. -- 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=429083 User mls@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=429083#c3 Michael Schröder <mls@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #3 from Michael Schröder <mls@novell.com> 2008-09-29 07:25:18 MDT --- Sorry, you mustn't put multiple versions of a package in the :full trees. -- 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=429083 User christopher.lang@acurana.de added comment https://bugzilla.novell.com/show_bug.cgi?id=429083#c4 Christopher Lang <christopher.lang@acurana.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #4 from Christopher Lang <christopher.lang@acurana.de> 2008-09-29 09:21:13 MDT --- I strongly disagree with comment #3. The automatic selection of latest package version works in the :full tree for .1 to .9. It is broken in two ways for .10 .. Not fixing this leaves potential problems for all packages having .10 and beyond versioning. It must be possible to put the "update" folder of a certain distribution - which might contain .10, .11 etc. - into the :full folder of a build repository. It *is* possible for .1 to .9. I think it is not a good idea to expect the build repository maintainer to verify a package if there is an older one in the repo every time he updates the build repo with updated packages. Also not fixing this contradicts the "Prefer:" clause in .conf. Please reconsider. thanks. -- 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=429083 User mls@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=429083#c5 --- Comment #5 from Michael Schröder <mls@novell.com> 2008-09-29 09:37:26 MDT --- Well, it just doesn't work at the moment. I know that this can be fixed, put currently the code assumes that there is only one package version in the :full tree. Multiple places would need to be changed: - built packages are stored as name.rpm instead name-version-release.arch.rpm. - the :full:cache file only uses "name" - all the dependency expansion code only uses "name" - the workers download packages just with "name" (there's a hack in the repo server that makes it pick a version if name.rpm doesn't exist) - and probably some other places as well And it's only about packages in the :full tree, there can be multiple packages in the exported repo. It is possible to put the update folder into the full tree: just delete all of the older versions. Prefer "name-version" doesn't work at all. Dunno why you think it does. -- 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=429083 User christopher.lang@acurana.de added comment https://bugzilla.novell.com/show_bug.cgi?id=429083#c6 --- Comment #6 from Christopher Lang <christopher.lang@acurana.de> 2008-09-29 10:05:02 MDT --- So for the time being one needs to pay close attention when updating the :full path with new packages. ok. While I did not look into the build server code, I tested the above described: the build server automatically picks the latest package for single digit (.1 to 9) versions. It fails as soon as a .10 version shows up. It then picks the latest single digit version. Now that this is a known fact, I can live with that. I am just not sure whether this bug should be closed so easily. I think sooner or later it will pop up again. -- 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=429083 Michael Schröder <mls@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement Priority|P2 - High |P3 - Medium -- 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