[Bug 209407] New: release numbers of packages do not increase even on relevant changes
https://bugzilla.novell.com/show_bug.cgi?id=209407 Summary: release numbers of packages do not increase even on relevant changes Product: openSUSE 10.2 Version: Alpha 4 plus Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: aj@novell.com ReportedBy: rschiele@gmail.com QAContact: qa@suse.de Currently release numbers of packages do not increase even on relevant changes. For instance the current upgrade of the db package to 4.4 release did not increase the number on packages that link to libdb. This results in non-upgradabbility of the system. YaST even destroys the whole system by deciding to uninstall vital parts of the base system (e.g. perl) in that situation. Thus please upgrade the release number on each change that does result in ABI changes. If you have not implemented detecting these changes then do it on _every_ rebuild. The fact that most system destructive bugs when using factory are due to such inconsistencies instead of real package bugs does not cast a positive light on your quality assurance efforts. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 mls@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@novell.com ------- Comment #1 from mls@novell.com 2006-10-02 04:14 MST ------- There seems to be a bug in YaST: it should check the build time if the nevr is identical. I'll CC ma for this. Note also that we used to increase the release number on every rebuild, but we were told to change this because 3rd party vendors and other people complained. So we'll probably not go back. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 ------- Comment #2 from aj@novell.com 2006-10-02 04:19 MST ------- Would it make sense to have different settings for FACTORY/STABLE and released products? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 ------- Comment #3 from mls@novell.com 2006-10-02 04:33 MST ------- We can certainly do that, but as far as I remember the complains were also about alpha/beta versions, i.e. STABLE. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 ------- Comment #4 from aj@novell.com 2006-10-02 04:41 MST ------- With the daily sync out, we cause problems when ABI changes - and dependend packages keep their version. Fixing YaST is one issue but there's smart out as well and people expect that the same rpm version will have the same dependencies. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 ------- Comment #5 from mls@novell.com 2006-10-02 04:46 MST ------- Right. When we decided the current scheme we said that when a package can reach a customer the next rebuild must have a higher release number. As all STABLE packages reach customers nowadays we should make sure the release number increase. -> we should call 'release_number --setfromlist ...' after the factory sync to enforce this. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 ------- Comment #6 from aj@novell.com 2006-10-02 04:51 MST ------- Please call it manually right now so that the next sync will be increased. I guess Rudi should look into the automatic increase for the factory sync since he wrote the scripts. We don't want to do it far too often either... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 danw@ximian.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |danw@ximian.com ------- Comment #7 from danw@ximian.com 2006-10-02 08:17 MST ------- Can't we have autobuild bump the release number only when the dependencies change? I know there's something in autobuild watching out for that happening because it always sends me those "[package check $ARCH] $NAME changes" mails. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 ro@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #8 from ro@novell.com 2006-10-10 16:11 MST ------- well, that check happens "offline", meaning hours or even days after the package was built, definitely too late to bump the release number. Basically you need the release number before even starting to build the package, but at least you need it before the rpm is really written to disk, and at that time you have no real comparision to the previous rpm. The strategy that rel-numbers should be bumped if a package reaches the customer still holds, so the approach from comment #5 sounds workable, but it's a bit too late, since when everything is really spooled to the public server, the distribution might be already in the middle of the next rebuild; I'll have to trigger a little earlier: exactly when the rebuild is completed ... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 ro@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #9 from ro@novell.com 2006-11-02 08:58 MST ------- implemented by now. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 rschiele@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #10 from rschiele@gmail.com 2007-01-18 03:31 MST ------- It happens less often now but still does happen. Example: 72985 2007-01-13 22:05 loki_uninstall-1.0.3_20051201-51.x86_64.rpm 72946 2007-01-17 05:18 loki_uninstall-1.0.3_20051201-51.x86_64.rpm As you can see the size and date differs but the packages version/release number does not. For your research: The build dates of these example packages are: Sat 13 Jan 2007 10:02:09 PM CET Wed 17 Jan 2007 05:16:53 AM CET -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 ro@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WORKSFORME ------- Comment #11 from ro@novell.com 2007-01-18 03:38 MST ------- sure, as said before it can happen. especially if the distribution never finishes, e.g. because there is to much build-load (other distributions/products with higher priority building packages) or too many packages being checked in. For normal times it works good enough. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 rschiele@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Comment #12 from rschiele@gmail.com 2007-02-06 23:29 MST ------- It again happens on almost _every_ sync with almost _every_ package. This again lead to the result that on one of my machines YaST destroyed its own libzypp package infrastructure through an update because of that. So I had to fix this again by calling rpm manually to fix it before being able to use the YaST package manager 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407 ro@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED ------- Comment #13 from ro@novell.com 2007-02-07 16:31 MST ------- the problem is: the rebuilds just never finish on some platforms, I'll have to ignore some more packages probably (or ignore some platforms which are lacking build power) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=209407#c14
Ruediger Oertel
participants (1)
-
bugzilla_noreply＠novell.com