Public SourceMage Discussion List

[Seth Alan Woolley <seth AT positivism.org>]

On Tue, May 03, 2005 at 11:32:21PM +0200, Arwed von Merkatz wrote:
> On Tue, May 03, 2005 at 02:14:04PM -0700, Eric Sandall wrote:
> > Quoting Arwed von Merkatz <v.merkatz AT gmx.net>:
> > <snip>
> > > What about updates without a bug? E.g. I update libmpeg2 knowing that
> > > all spells using it will need to be recompiled due to an ABI change.
> > > This doesn't happen often enough to warrant the onslaught of triggers
> > > we'd need to prevent it. But it should be documented, so we need a way
> > > to get that info to the people doing the actual stable grimoire
> > > releases.
> > > I'm not sure what the best option is here. One option would be a
> > > text file in the spell describing such things, another would be filing
> > > bugs on such updates explicitly and get those to the QA team.
> > 
> > Talked about in the linux-pam bug:
> > http://bugs.sourcemage.org/show_bug.cgi?id=680
> > 
> > Short:
> > A versioned trigger based on the minor number (2.4 -> 2.6, e.g.) should be
> > enough, and only parse "valid" VERSION tags (such as x.x.x, not 
> > BetaIII-42b and
> > such). Then we could have:
> > 
> > wget/TRIGGERS:
> > on_minor_update gettext cast_self
> > 
> > */TRIGGERS:
> > on_minor_update linux-pam cast_self
> > 
> > Then, only when linux-pam goes from 0.76 -> 0.77 would a trigger be 
> > caused, and
> > not just any recompile of Linux-PAM.
> > 
> > openssh/TRIGGERS:
> > on_revision_update openssl cast_self
> > 
> > This way openssh would only be updated when openssl goes from 0.9.6 -> 
> > 0.9.7
> > (since their revisions change the shared library names), but not 0.9.6a ->
> > 0.9.6b (hopefully).
>  
> This would definitely help for some things, but it doesn't solve what I
> was talking about.
> What about a _single_ update that needs recompiles of dependent spells?
> Triggers don't help here as those spells can't know about that recompile
> dependency before it happens. It's something cleanse --fix usually
> catches nicely, but I want a way for gurus to document that so the QA
> team can put it in the release notes of the stable grimoire.

Nothing QA team does in the grimoires can do anything about this libmpeg2 
example without some sort of trigger.

Because putting abi-new-libmpeg2 into stable will break all spells 
unless all libmpeg2-dependent spells have a version update as well (We 
could increment UPDATED on all dependent spells at the same time 
libmpeg2 is integrated to stable, I suppose) as the system update 
process should guarantee dependency-aware compile order, but only if all 
spells were compiled at that system update.

Won't a cleanse --fix find the abi update since whenever you do an abi 
update you're supposed to increment the library version number, right?

I'm wondering just exactly what you want done for test -> stable 
integration, and then maybe I can integrate it into a policy document in 
this case.

Seth

-- 
Seth Alan Woolley [seth at positivism.org], SPAM/UCE is unauthorized
Key id 00BA3AF3 = 8BE0 A72E A47E A92A 0737  F2FF 7A3F 6D3C 00BA 3AF3
Quality Assurance Team Leader; Security Team Member, Leader Emeritus
Linux so advanced, it may as well be magic http://www.sourcemage.org
Elected Coordinating Committee Member, Secretary, and Finances Chair
Pacific Green Party of Oregon - Peace - http://www.pacificgreens.org

Attachment: pgpeoyyadgLH0.pgp
Description: PGP signature