Le 18/12/2013 17:13, Adrian Schröter a écrit :
> On Mittwoch, 18. Dezember 2013, 17:09:40 wrote Guillaume Gardet:
>> Le 18/12/2013 16:56, Adrian Schröter a écrit :
>>> On Mittwoch, 18. Dezember 2013, 16:52:10 wrote Guillaume Gardet:
>>>> Le 16/12/2013 14:10, Michal Marek a écrit :
>>>>> On 16.12.2013 10:52, Adrian Schröter wrote:
>>>>>> JFYI, after checking the needed sizes of the builds for the 
>>>>>> architectures,
>>>>>> I set this now
>>>>>>
>>>>>> %ifarch armv7l
>>>>>> Constraint: hardware:disk:size unit=G 7
>>>>>> %else
>>>>>> Constraint: hardware:disk:size unit=G 14
>>>>>> Constraint: hardware:processors 8
>>>>>> %endif
>>>>> Thanks for letting me know. The prjconf is autogenerated, so it will be
>>>>> reset after the next push to openSUSE-13.1. So I need to add one more
>>>>> special case :-|
>>>> We should update rpm/_constraints in GIT repo. That is what you meant or 
>>>> not?
>>>>
>>>> If so, it have not been updated yet neither for Factory nor 13.1.
>>> This is in the Kernel:* prjconf, so it is independend of the sources.
>>> Factory and 13.1 do not have these settings (which may lead to build 
>>> failures)
>>>
>> Ok. So, if I understand it right, _constraints file must be updated for all 
>> projects except Kernel:* which add additionnal constraints through prjconf.
>> That is it?
> erm, no, you are right, we need also update the _constratins file. Or drop it 
> in sources, entirely for now, 
> since we have it prjconf anyway.
>
> (I thought it had just 1GB required in that file, but it is also 14GB now 
> ....)

I think the best way is to update _constraints file and drop OBS prjconf 
constraint. That way, all projects will use the same constraints.

The problem is how we could set arch dependent constraints in _constraints 
file? Is it possible?


Guillaume



>
>> Who could update prjconf? Michal? Is it possible to do it, please? Because 
>> most 13.1 ARM images are still broken due to that. :(
>>
>>
>> Guillaume
>>
>>

-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to