[Mageia-dev] Finalizing update process

nicolas vigier boklm at mars-attacks.org
Thu Jun 9 12:53:31 CEST 2011


On Thu, 09 Jun 2011, Thomas Backlund wrote:

> nicolas vigier skrev 9.6.2011 13:35:
>> On Thu, 09 Jun 2011, Michael Scherer wrote:
>>
>>> Le jeudi 09 juin 2011 à 02:40 +0300, Ahmad Samir a écrit :
>>>
>>>> Yes, but I was talking about the actual submitting to */release, not
>>>> fixing the package itself. IIUC the submission rights will be
>>>> restricted to the Sec team.
>>>
>>> Sorry to be picky, but there is no submit to */release, it is frozen.
>>> And in my proposition, there is also no submit to */update, there is a
>>> move from */updates_testing.
>>
>> In that case, if the package is not rebuilt and only moved from
>> */updates_testing, we need to disable the */updates_testing repository
>> in iurt during builds of packages for */updates_testing repository, to
>> make sure it is not linked to an other testing package.
>> I think this was not the case on testing repository on mandriva.
>>
>
> That wont work.
>
> Think of programs that need to be rebuilt with an other updated package.. 
> and pushed to /updates all at once.
>
> such as a big kde update, ...

Yes. One long term solutions could be to create a temporary testing repository,
for each update.



More information about the Mageia-dev mailing list