Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

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

           Summary: old stale sources - warning
           Product: Sorcery
           Version: 1.14.x
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Feature Request
        AssignedTo: sm-sorcery-bugs AT lists.ibiblio.org
        ReportedBy: hgr AT vabo.cz


>From time to time the mainteiners of source packages (vendors) change sources
without updating their version. If user already have old stale sources and new
sources were changed (there is new HASH or SIGN in grimoire) user get warning
about bad HASH or SIG (of course user already cast it, this problem is only of
user want to re-cast it, for example sorcery rebuild). 

It would be fine if users get also info that he/she already downloaded sources
but sources on vendor's website were changed without update to new version and
he/she should "summon -d" them. Imho stale HASH or SIG could stay in grimoire
until new version so user could be informed that sources can be check against
old HASH or SIG but their were changed.

Imho, when HASH or SIG is changed in grimoire, users used old sources (already
casted it) should be informed (during sorcery system-update) that sources were
changed and users should "summon -d " them and "cat -c" again.

We need some standard how to do this. We can check sources in PRE_BUILD 
against
stale HASH or SIG. How to name old stale HASH and SIG, ..., how to inform 
users
that sources were changed? SOURCE_STALE=1?


-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.