[SM-Grimoire-Bugs] [Bug 8736] New: UPDATED behaviour is broken

bugzilla-daemon at bugs.sourcemage.org bugzilla-daemon at bugs.sourcemage.org
Wed Apr 27 16:11:58 EDT 2005


http://bugs.sourcemage.org/show_bug.cgi?id=8736

           Summary: UPDATED behaviour is broken
           Product: Sorcery
           Version: Untargetted future release
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: subroutines
        AssignedTo: sm-sorcery-bugs at lists.ibiblio.org
        ReportedBy: eric at sandall.us
                CC: security at sourcemage.org,sm-grimoire-
                    bugs at lists.ibiblio.org


The reason PATCHLEVEL would be better than UPDATED is because UPDATED only works
for test (and then only if users stay up-to-date), but not for stable.

(copied from Bug #8379).

Example of UPDATED not working.
We modify package X to fix some headers, update UPDATED to 20050427 and pull
this from devel to test.
A user installs package X on 2005-04-27 from stable.
Package X eventually gets to stable with the fix and isn't updated because
UPDATED is not newer than when the package was installed.

There are many variations, all of which happen if the user casts the old version
after the package has been updated. We also can't do UPDATED more than once a
day and have it work (e.g. if we have to fix a fix or another fix comes out we
want to add) unless we put the package in the future. ;)

PATCHLEVEL should be "reset" for each version of a package:
e.g.
* apache2 2.0.54 has PATCHLEVEL=0 initially
* We add a security patch to apache2 and increment PATCHLEVEL=1
* Another security vulnerability comes out that same day after we've already
applied the patch, so we add the patch and increment PATCHLEVEL=2
* apache2 2.0.55 comes out the next day (let's say after 6 hours), we update
VERSION=2.0.55 and PATCHLEVEL=0

UPDATED would not work for that scenario above if the user installed our
PATCHLEVEL=1 fix. UPDATED is also broken due to fun timezones (who's day is it?).

For displaying/comparing versions  (e.g. `gaze version` or `sorcery queue`) I
think Sorcery should use $VERSION-$PATCHLEVEL instead of $VERSION.

-- 
Configure bugmail: http://bugs.sourcemage.org/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.



More information about the SM-Grimoire-Bugs mailing list