headers
Chris Gianelloni | 1 Dec 2006 02:48
Picon
Favicon

Re: gentoo-sources-2.4 needs a maintainer

On Thu, 2006-11-30 at 18:30 -0500, Daniel Drake wrote:
> Please mention this in the next GWN.

Will do.

--

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
Permalink | Reply | 0 comments |
headers
Doug Goldstein | 1 Dec 2006 04:02
Picon
Favicon

Re: Re: IMPORTANT: bugs/packages/planet/etc downtime

Lance Albertson wrote:
> Lance Albertson wrote:
> 
>> We're going to be finally moving the last two machines at the OSL to the
>> new datacenter later this afternoon. The scheduled time will be 2pm PST
>> or 2200 UTC today. Unless something comes up, plan for about an hour
>> downtime for that today.
> 
> Both moves have been completed. As far as I can tell, everything is back
> up and running as usual. Let me know if you notice any problems.
> 
> Thanks!
> 

Back to your irregularly scheduled uptime of bugs! Close 'em while
you've got 'em!

--

-- 
Doug Goldstein <cardoe <at> gentoo.org>
http://dev.gentoo.org/~cardoe/
Permalink | Reply | 0 comments |
headers
Steve Long | 1 Dec 2006 08:23
Picon

Re: Re: Re: Versioning the tree

Chris Gianelloni wrote:

> It would be much better to simply use what we currently have,
> though.  Honestly, I was pursuing this with Infra a few months back, and
> have since dropped it, due to time constraints.  I plan on picking it
> back up, as I said, so I don't know what is necessary at this point.
> 
Makes sense. 

>> > Now, the release trees are non-moving.  The 2007.0-release tree is
>> > *always* the 2007.0-release tree for as long as we decide to support
>> > it. Likely, this support period would begin as a single release and get
>> > extended as volunteers came around to support it.  New releases get
>> > their own tree.
>> > 
>> Well count me in as a volunteer to help set this up and maintain an x86
>> release. I'm a pretty good coder if that helps.
> 
> There wouldn't be an "x86 release" or anything.  It would be the whole
> thing.  All or nothing.
> 
I hear you- it's the tree that's being released. I guess x86 is the most
common architecture anyway, so testers for it aren't gonna be hard to find.

>> > Users who want to use the current portage tree get what they want.
>> > Users who want a more stable tree get what they want.  Basically,
>> > everyone (hopefully) is happy, or at least as happy as we can feasibly
>> > make them.
>> > 
>> This all sounds great. Respect for the work you've already put in.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Petteri Räty | 1 Dec 2006 08:25
Picon
Favicon

Re: [RFC] Add ALSA_CARDS to USE_EXPAND

Diego 'Flameeyes' Pettenò kirjoitti:
> On Thursday 30 November 2006 22:40, Marius Mauch wrote:
>> Not if you take care of providing the proper defaults in
>> make.defaults (the sample above should not be the default).
> Forgot to say, if no ALSA_CARDS is set, the default is enabling everything 
> (alsa's default)
> 

It should give you what the emerge -pv line says. If it says nothing is
enabled then, it should not give you everything. This is because other
USE_EXPANDed stuff works this way.

Regards,
Petteri
Permalink | Reply | 4 comments |
headers
Steve Long | 1 Dec 2006 08:49
Picon

Re: Re: Versioning the tree

>> There'll always be GLSA's to respond to.  That's another issue that
>> needs to be handled w/ a slow-moving tree.  Are you going to restrict
>> changes in the slow-moving tree only to changes against a GLSA?
> 
> That's what we've said.
> 
I don't have a problem with this at all. The slow-moving tree isn't; it's a
release tree. The only question I have, which Stuart also mentioned, is
whether all security updates go thru the GLSA process.

--

-- 
gentoo-dev <at> gentoo.org mailing list
Permalink | Reply | 4 comments |
headers
Steve Long | 1 Dec 2006 08:54
Picon

Can we have some manners, please?

Just a general point: I think people are being a bit harsh on Stuart in this
thread. I'm picking up on Chris's post as I'm interested in the
releng-related stuff, but this isn't exclusively about his responses.

Stuart Herbert wrote:
> On 11/29/06, Chris Gianelloni <wolf31o2 <at> gentoo.org> wrote:
>> I'm sorry, but how the hell do you know?  You are not a member of
>> Release Engineering, and have *NO CLUE* what we do over there.  What we
>> release isn't the only thing we do.
> 
> Then this is a great opportunity to set the record straight, by
> explaining what server-oriented work releng do with each release.
> 
I agree with Stuart on this. While released stuff is of course not all any
team does in software development, it is all that anyone external usually
sees, or associates with that group.

>> Luckily, I'm not asking you.  Instead, I'm asking interested developers
>> to assist us in making what we plan on doing much more viable.  Feel
>> free to sit over there and naysay until you're blue in the face.  We'll
>> be over here getting something accomplished via teamwork.
> 
> Odd; I'm trying to get involved, by providing feedback and asking
> questions.
> 
Again I think Stuart is right; he's asking questions which while they might
sound irritating if you've explained the stuff before, should be treated
with respect, or at least basic courtesy.

>> Just because we didn't take the time out to stop and make
(Continue reading)

Permalink | Reply | 0 comments |
headers
Steve Long | 1 Dec 2006 09:05
Picon

Re: ACCEPT_LICENSE revisited

Donnie Berkholz wrote:
> Ciaran McCreesh wrote:
>> What, you really think that Donnie doesn't know how the X licence
>> handling situation breaks GLEP 23? Just how exactly is ACCEPT_LICENSE
>> usable when you have this?
> 
> [ cropped groups of similar license combinations ]
> 
> Pretty usable, when you consider that it specifies groups. Throw all
> that stuff into an MIT group and you're good to go.
> 
Ciaran McCreesh wrote:
> On Mon, 20 Nov 2006 02:56:18 -0800 Donnie Berkholz
> <dberkholz <at> gentoo.org> wrote:
> | But I guess you don't think that's good enough for some reason. Since
> | you've already done the work to analyze the various groups, why don't
> | you finish it by figuring out the applicable licenses, and whether
> | new ones need to get added, and send a patch out?
> 
> All things considered, I've little inclination to do your job for
> you... QA and not screwing over Gentoo users is your responsibility, not
> mine.
> 
Ciaran: does the group stuff Donnie mentioned above fix this? Secondly, how
difficult would it be for you to do what he asked? I know it's not your
responsibility, I just want to know whether you can do it fairly easily.

--

-- 
gentoo-dev <at> gentoo.org mailing list
(Continue reading)

Permalink | Reply | 6 comments |
headers
Alec Warner | 1 Dec 2006 11:15
Picon
Favicon

Herds, take your marks...get set...take stuff!

If you look at gpnl[1] you will see a list of packages with NO 
maintainer and NO herd.  If you are a dev and are interested in a 
package please take it.  For herds, you may wish to glance around the 
categories and pick up some packages that you use/are useful/are in your 
herd.

For users, if you see something you use, you may become a 
proxy-maintainer for it.  I'm going to try and improve treecleaners in 
that regard over the next few months.

[1] http://spaceparanoids.org/gentoo/gpnl/qa.php?q=no-herd-maintainer
--

-- 
gentoo-dev <at> gentoo.org mailing list
Permalink | Reply | 8 comments |
headers
Mike Frysinger | 1 Dec 2006 06:45
Picon
Favicon
Gravatar

Monthly Gentoo Council Reminder for December

This is your monthly friendly reminder !  Same bat time (typically the
2nd Thursday at 2000 UTC), same bat channel (#gentoo-council  <at> 
irc.freenode.net) !

If you have something you'd wish for us to chat about, maybe even
vote on, let us know !  Simply reply to this e-mail for the whole
Gentoo dev list to see.

Keep in mind that every GLEP *re*submission to the council for review
must first be sent to the gentoo-dev mailing list 7 days (minimum)
before being submitted as an agenda item which itself occurs 7 days
before the meeting.  Simply put, the gentoo-dev mailing list must be
notified at least 14 days before the meeting itself.

For more info on the Gentoo Council, feel free to browse our homepage:
http://www.gentoo.org/proj/en/council/
--

-- 
gentoo-dev <at> gentoo.org mailing list
Permalink | Reply | 0 comments |
headers
Duncan | 1 Dec 2006 12:29
Picon

Re: Versioning the tree

Steve Long <slong <at> rathaus.eclipse.co.uk> posted
ekol7b$q8i$1 <at> sea.gmane.org, excerpted below, on  Fri, 01 Dec 2006 07:23:09
+0000:

> Excellent; pkgcore really sounds great- is there any possibility that it'll
> become the new portage?

Possibility, yes.  It's not certain, as there are multiple contenders
(paludis is the other), and it will be some time, in any case.

The current problem is that there's no standard definition for what
constitutes an acceptable ebuild, beyond the basic gentoo dev guidelines.
The de facto definition is whatever works with versions of portage
currently in the tree (or just barely removed), but that presents many
difficulties, including both slow upgrades since backward compatibility
must be maintained for longer even when the former functionality is
considered b0rken, and questions of what's broken, the package manager or
the ebuild, when something fails to work as expected.

Thus, all three package managers, the current portage solution, and paludis
and pkgcore as well, are currently under slower development than they might
otherwise be, while interested parties attempt to hash out a working
standard definition of what actually constitutes a proper ebuild, and
what helper functions said ebuild can in fact depend upon the package
manager to make available.  Once that's decided and approved, the playing
field upon which the merits of the next generation package managers can be
judged will be much fairer for all.  Of course, with that defined, portage
itself will be freer to progress at speed as well, and it may be that it
will remain the default "approved" solution for quite some time.
(Continue reading)

Permalink | Reply | 1 comment |

Gmane