Hi!
Last thursday we had a dist meeting to discuss policy changes for our
distributions that affect a lot of teams. So these are the minutes, if you
have questions, feel free to ask - this is just me typing.
Greetings, Stephan
Present: jpr, holgi, matz, cfarrel, mls, kukuk, hvogel,
meissner, radmanic, ro, coolo, adrian,
nadvornik, jsrain, gekker
Patchrpms considered harmful
no consistency checkin, so created problems in the past
update stack can not check the integrity (by design)
delta rpms are better anyway, just little bigger in cases
new patches for old or only new products? too dangerous to disable
Marcus decided: go for >= 10.3 and disable patch rpms
Stricter checks for updates
texlive update removed some manual pages
some files were not marked as %noverify, which are changed by %post
delta packages could not be applied, creating a 200MB update
suggested policy:
%post call in package build and rpm -Va output fails package
Conclusion:
rpm -V output is a critical bug
(TODO: at least 257 packages in Factory affected)
Sync build service with factory
e.g. gnome team wants to maintain packages in build service
time left out to discuss this
Conclusion between those left in the room:
GNOME team should go ahead, but should be aware that
whoever submits a package to autobuild is responsible for reviewing
the changes, no matter where they come from.
Tools support earliest in spring 2008 according to build service road map
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
