On Sun, 27 Jan 2013 00:26:38 +0100
"Andreas K. Huettel" <dilfri...@gentoo.org> wrote:

> Just to keep everyone updated, ...
> > FYI, the new 13.0 profiles are now all available in profiles.desc, for now
> > all with status "dev" (i.e. repoman includes them only when you request
> > developer profile checking).
> > 
> > This means the procedure below is complete up to and including point 5)
> > now.
> > 
> > Please consider changing your profile symlink manually and testing the new
> > profile tree. In case of problems, please file a bug and assign it to me
> > (or tell me if I'm around).
> > 
> > If all goes well, we'll continue in a week.
> > 
> A small bug in repoman turned up when testing the EAPI=5 profiles, and 
> therefore we will wait for the next stable portage version before the 10.0 
> profiles are deprecated. So, another 3-4 weeks to go maybe.
> [The only alternative would be to require all devs to run at least ~arch 
> portage, since the bug only affects repoman, not emerge.]

To be honest, I don't think this is really a blocker to deprecating
the old profiles, unless you're talking about other bug than the one I

That bug just caused repoman to error about unstable dependencies when
flags were stable-masked. This just means that developers with old
repoman won't be able to commit stable ebuilds using stable-masked
flags. Note that using the old profiles workarounds the issue through
having those flags completely masked and therefore devs having no
repoman checks on their dependencies at all...

Best regards,
Michał Górny

Attachment: signature.asc
Description: PGP signature

Reply via email to