On Tue, Jan 24, 2017 at 11:11 AM, Mart Raudsepp wrote:
> Currently this seems to be resulting in broken deptrees for arches that
> don't have a stable profile. arm64 in particular.
Last I checked, "ekeyword all foo.ebuild" will skip arches that have
no stable profiles. Ago must be using some othe
On 01/24/2017 11:11 AM, Mart Raudsepp wrote:
>
> Currently this seems to be resulting in broken deptrees for arches that
> don't have a stable profile. arm64 in particular.
ALLARCHES should not include the unstable ones unless they are
specifically in CC, and of course you should be running repom
Ühel kenal päeval, T, 24.01.2017 kell 09:55, kirjutas Matthew Thode:
> So, to be clear, we need to wait for an AT to mark stable for one
> arch
> on an ALLARCHES package. Once that is done any dev can mark the rest
> of
> the arches stable.
Currently this seems to be resulting in broken deptrees
On 01/24/2017 07:54 AM, Agostino Sarubbo wrote:
> We are working to provide some tools for the stabilization process.
>
>
>
>
>
> Unfortunately, there isn't atm something able to manage the requests
> with the ALLARCHES keyword,
>
>
>
> So, *everyone* with the commit access can keyword f
We are working to provide some tools for the
stabilization process.
Unfortunately, there isn't atm something able to
manage the requests with the ALLARCHES keyword,
So, *everyone* with the commit access can keyword for
all after a stabilization/keyword happened at least for
one arch.
Thanks
