On Sun, 16 Feb 2014 15:53:57 +0100
Pacho Ramos <[email protected]> wrote:
In this case:
> > > - Versions that are not stabilized because arch team doesn't have
> > > the man power to do that.
> >
> > As above, package.mask would be a good intermediate solution,
> > communicating the problem to the arch users for, say, thirty days.
> > Of course it may just delay solving the problem when a new set of
> > stabilisations is due and again no one responds.
>
> I disagree in this case as the package can still be in "testing", not
> like the above case that, if the package is broken, it shouldn't be
> neither in testing tree.
In this case, a newer version hasn't been (sufficiently) tested on a
certain architecture, so it is still in the "testing" phase. In this
case, you haven't established that it's broken.
Also, the general idea is to temporarily mask the _old_ stable
version(s) on the arch profile and not _all_ versions.
jer
