[Mageia-dev] Copying dependencies from Release to Updates Testing

Balcaen John mikala at mageia.org
Thu Sep 8 13:52:49 CEST 2011


Le Jeudi 8 Septembre 2011 13:53:07 Samuel Verschelde a écrit :
> Le jeudi 8 septembre 2011 10:39:47, Samuel Verschelde a écrit :
> > Hi,
> > 
> > During yesterday's packager meeting, it was agreed that the
> > sysadmins will provide a tool allowing packagers to copy packages
> > from Release media to Updates Testing media.
> > 
> > QA Team should be able soon to ask the packagers to provide needed
> > dependencies in Updates Testing so that updates are not blocked by
> > https://bugs.mageia.org/show_bug.cgi?id=2317
> > 
> > Then those dependencies will have to be moved from Updates Testing
> > to Updates, like the other packages submitted by the packagers
> > for the update.
> > 
> > Could someone complete the update procedure wiki page with
> > detailed
> > instructions for packagers to follow, regarding how to identify
> > dependencies that need to be copied to Updates Testing along with
> > an update candidate ?
> > 
> > Until that tool is made available, we can list the needed
> > dependencies in the bug report and ask the sysadmins to move them
> > directly.
> > 
> > Best regards
> > 
> > Samuel Verschelde
> 
> Good question from MrsB : must we link only the needed binary RPMs, or
> all those coming from the SRPM ?
> 
> Example : qt4-database-plugin-sqlite-4.7.3-1.mga1.i586.rpm is needed,
> will we link all packages from the qt4 SRPM or only
> qt4-database-plugin- sqlite-4.7.3-1.mga1.i586.rpm ? The first option
> is probably cleaner, but this means copy much more packages.
Well we shoud links only the *requirements* for qt4-database-plugin- 
sqlite so probably not all qt4 packages (but most of them :/ )

-- 
Balcaen John


More information about the Mageia-dev mailing list