public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New, shiny EAPI=5 profiles: volunteer, procedure, preparations
Date: Sun, 27 Jan 2013 00:26:38 +0100	[thread overview]
Message-ID: <201301270026.45926.dilfridge@gentoo.org> (raw)
In-Reply-To: <201301182137.10840.dilfridge@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 1028 bytes --]

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.]

Cheers, 
Andreas

-- 

Andreas K. Huettel
Gentoo Linux developer 
dilfridge@gentoo.org
http://www.akhuettel.de/


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-01-26 23:27 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12 20:47 [gentoo-dev] New, shiny EAPI=5 profiles: volunteer, procedure, preparations Andreas K. Huettel
2013-01-14 20:24 ` Andreas K. Huettel
2013-01-18  9:05   ` Ultrabug
2013-01-18 10:51 ` Michael Weber
2013-01-18 11:50   ` Markos Chandras
2013-01-18 11:56   ` [gentoo-dev] " Michael Palimaka
2013-01-18 20:37 ` [gentoo-dev] " Andreas K. Huettel
2013-01-18 22:20   ` Michał Górny
2013-01-18 23:47     ` Andreas K. Huettel
2013-01-19  0:10       ` Michał Górny
2013-01-26 23:26   ` Andreas K. Huettel [this message]
2013-01-27 11:26     ` Pacho Ramos
2013-01-27 21:16       ` Zac Medico
2013-01-28 23:24     ` Michał Górny
2013-02-09 22:29 ` Andreas K. Huettel
2013-02-10  2:43   ` Douglas Freed
2013-02-10  8:32     ` Ben de Groot
2013-02-10 13:34       ` Markos Chandras
2013-02-10 14:06         ` Andreas K. Huettel
2013-02-10 14:15           ` Markos Chandras
2013-02-10 15:02             ` News item (was: Re: [gentoo-dev] New, shiny EAPI=5 profiles: volunteer, procedure, preparations) Andreas K. Huettel
2013-02-10 15:15               ` Ben de Groot
2013-02-10 16:12               ` Markos Chandras
2013-02-10 21:07               ` Andreas K. Huettel
2013-02-10 22:11               ` [gentoo-dev] Re: News item James Cloos
2013-02-10 14:59           ` [gentoo-dev] New, shiny EAPI=5 profiles: volunteer, procedure, preparations Patrick Nagel
2013-02-10 15:05             ` Andreas K. Huettel
2013-02-10 22:06           ` James Cloos
2013-02-10 23:34             ` Michał Górny
2013-02-10 23:45               ` Andreas K. Huettel
2013-02-11  3:10                 ` Zac Medico
2013-02-10 23:46               ` Zac Medico
2013-02-10  5:21   ` [gentoo-dev] " Duncan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201301270026.45926.dilfridge@gentoo.org \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox