On 17 July 2011 23:43, Samuel Verschelde <[email protected]> wrote: > Hi, > > I wanted to share the method I use when I need to push a new package (new = > missing from Mageia 1) from cauldron to Mageia 1 updates. This concerns only > packages available in Mandriva 2010.2 but absent from Mageia 1. > > I'm sharing for 2 reasons : > - maybe I'm doing it wrong, so you can comment and maybe give me better > instructions > - it can be of use, the way I do it or the way I will be told to do :) > > Here is my procedure : > > svn cp svn+ssh://svn.mageia.org/svn/packages/cauldron/PACKAGENAME > svn+ssh://svn.mageia.org/svn/packages/updates/1/PACKAGENAME > (with comment "Add PACKAGENAME to Mageia 1") > svn mkdir svn+ssh://svn.mageia.org/svn/binrepos/updates/1/putty > (with comment "Add PACKAGENAME")
'svn mkdir' step is redundant, 'mgarepo sync -c' will automatically create the binrepos/updates/1/$pkg-name. > mgarepo co 1/PACKAGENAME > cd PACKAGENAME > cp PATH_TO_BINARY_SOURCE_FILES_IN_CAULDRON SOURCES/ > mgarepo sync -c #uploads the source files to binrepo > vi SPECS/PACKAGENAME.spec #update release and add subrel > mgarepo submit -t 1 --define section=core/updates_testing > > For release and subrel, usually a new package would have release 0 and subrel > 1, but to allow migration from mandriva, I set a higher release that in > mandriva 2010.2 if the version is the same, + subrel 1, then increase it in > cauldron too so > that it's higher than in Mageia 1. > > I do that to be safe : the point of subrel is to be increased without any risk > of the package becoming not upgradable to the version in the n+1 distribution. > If cauldron has release 5.mga2 and updates has 5.mga1, it looks safe, but as > soon as we'll fix a bug in mga1, release will become 5.1.mga1 which is higher > than 5.mga2. That's why, for security, I would set the release in cauldron to > 6.mga2 so that we can increase the subrel at will in mga1. > > Comments ? > > Samuel Verschelde > -- Ahmad Samir
