[RPM Fusion] [Reminder] please build your packages for all branches

Sérgio Basto sergio at serjux.com
Fri Apr 27 00:44:21 CEST 2012


Hi, 
One question Nicolas, you have done an update for UsrMove, on VirtualBox-OSE-kmod.spec.
Should I commit same update on F16 and F15 ? 

Reference : 
http://cvs.rpmfusion.org/viewvc/rpms/VirtualBox-OSE-kmod/devel/VirtualBox-OSE-kmod.spec?root=free&r1=1.63&r2=1.62&view=patch

On Mon, 2012-04-16 at 23:15 +0200, Nicolas Chauvet wrote:
> Hi Maintainers,
> 
> As topic says, a remind of few rules:
> 
> Please consider to:
> - Sync your commit from your working branch up from to devel.
> If your are working on an update for F-16, please also commit your
> changes to F-17 and devel branches.
> This will allow devel to be higher in package version. No much check
> is done in this area from the infra side.
> This will ensure devel has the most complete features, so if a rebuilt
> of your package needs a rebuilt in a branch, it will keep all
> improvements.
> 
> - Build your packages for each branches.
> The inheritance process just 'do not work'. Once the repository is
> branched, the package only goes into the tree where it is built for.
> (1).
> Unless there is a huge exeption, please submit a build for devel F-18
> as it may also solve a dependency breakage.
> 
> Thx
> 
> Nicolas (kwizart)
> 
> (1) Until yesterday for nonfree and last thursday for free, there was
> an exception, since the push scripts didn't caught the new 'branched'
> layout, I've prevented any rawhide push so the late built from the
> mass rebuilt that occured in F-17 got manually inherited (via rsync)
> to the rawhide tree.

-- 
Sérgio M. B.


More information about the rpmfusion-developers mailing list