On 07/30/2014 06:26 AM, Anthony G. Basile wrote:
On 07/29/14 22:16, Jack Morgan wrote:
On Sat, Jul 26, 2014 at 04:29:51PM -0400, Anthony G. Basile wrote:
On 07/26/14 09:44, Pacho Ramos wrote:
El sáb, 26-07-2014 a las 09:37 -0400, Anthony G. Basile escribió:
On 07/26/14 09:28, Pacho Ramos wrot
Diego E. Pettenò wrote:
> # Diego E. Pettenò (09 Aug 2009)
> # on behalf of QA team
> #
> # Fails to build with recent linux-headers (bug #241484,
> # October 2008).
> #
> # Removal on 2009-10-08
> x11-misc/xac
>
It builds fine on PowerPC and is still useful there. I never really got
any feedb
For what it's worth, I've got an updated PowerPC handbook pretty much
ready to go (still missing some sections that I want to add for the
PS3). However, I haven't gotten around to figuring out what all of the
XML replacement variables are currently and if they were going to change
to reflect autobu
Joshua Saddler wrote:
> There. I did the x86 and amd64 handbooks (networked, anyway; who cares about
> networkless). They're now ready for the 10th anniversary. I'm pretty sure.
>
> I also did the x86 quickinstall handbooks.
>
> GDP, and interested devs who can contribute patches to Bugzilla:
>
>
Ben de Groot wrote:
> What about ppc64? They are MONTHS behind on stabilization,
> even for security bugs (see bug 281821 for example). The Qt team
> feels this is no longer acceptable. We propose that any arch that
> can't keep up will be demoted to experimental status.
>
>
ppc is also fairly f
> In the past when smaller arches were not that active we used to mark
> Java packages stable after testing by at least one arch team. The
> probability to find arch specific issues in something like Java is not
> so high so I think arrangements like this are acceptable when the arch
> teams have
Ben de Groot wrote:
> I am of the opinion it is irresponsible to leave vulnerable versions of Qt
> with
> known security bugs any longer in the tree. The Qt team therefore requests
> that arches that have not done so already move quickly on stabilizing Qt
> 4.5.3, see bug 290922 and 283810.
>
>
>
> Hello
>
> Let my explain the problem and my suggestion to handle it better (at
> least from my point of view) with an example:
>
> Sometime ago I bumped bluez version from 4.39-r2 to 4.60, with that
> bump, a new and *optional* RDEPEND on sys-libs/libcap-ng was added.
> Since libcap-ng was not
)
Release Engineer Liason: Lars Weiler (Pylon)
Security (PPC): Michael Hanselmann (hansmi)
Security (PPC64): Markus Rothe (corsair)
Profile Maintainer: Daniel Ostrow (dostrow)
Documentation Lead: Joseph Jezak (JoseJX)
2. Pre-Release and 2005.1 Release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Agreed, the PPC team is very good at arbitrarily marking things stable
> whenever they feel like it, and often times before the maintainer does.
This is not usually our policy. However, because we moved GCC-3.4 to
stable before many arches, there w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Homer Parker wrote:
> It is with great please I announce the newest Arch Tester, and the
> first non-AMD64 AT. Johannes Traub (_bambam on IRC), has become the
> first PPC AT. Please give him a warm welcome to the team.
>
Congrats Johannes! Now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Homer Parker wrote:
> It seems the PPC peeps have done it again, it's with great pleasure
> that I announce their newest AT, nixnut. Please give him a warm welcome
> to the team. I know JoseJX said he had plenty of work for him, so he
> might be
Homer Parker wrote:
On Mon, 2005-09-12 at 23:02 +0200, Simon Stelling wrote:
As of now, amd64 has 20 ATs, 6 of them became devs, 1 is inactive. The
rest
stayed AT. The "oldest" of the remaining has been AT since February,
the
youngest since Aug 23, so I think it definitively is.
An
> I have suggested that herd support for the kernelspace side
> (alsa-driver) be slowly reduced, by redirecting users who file bugs
> against it to reproduce with the in-kernel drivers, and then let kernel
For what it's worth, the PPC team has been suggesting the use of the
in-kernel drivers for a
Michael Cummings wrote:
> When you pop into your mail client of choice and find 50+ unread messages in
> the
> last few hours, you know what kind of day [EMAIL PROTECTED] is having.
>
> Don't suppose we could get on with that silly topical thing of development?
> Surely there's a usenet channel w
I can't say if there are any problems, as I didn't received
a bug for a long time. The only thing that's nasty: we
don't have any good utf8-fonts for the console.
I think that's acceptable.
The only issue related to that we really have is this bug, which is
annoying but not fatal:
http://bu
My 2 cents from LWE:
It was really nice to see the huge turnout of Gentoo devs, we had one of
the more busy booths and it's a testament to our community that so many
of us were there. Besides that, O'Reilly rocks, the guys from Slashdot
really do sit around and play XBox 360 all of the time, a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi devs,
The PPC team had a meeting on Sunday, April 30th. I've attached a
summary for those interested. Logs are available by request, (at least
until I get them added to ppc.gentoo.org).
Thanks,
- -Joe
-BEGIN PGP SIGNATURE-
Version: GnuPG
> Heh, a fellow Gentoo dev here in Pittsburgh!
Looks like there's three of us now! :)
Welcome to Gentoo Mike Kelly!
-Joe
--
gentoo-dev@gentoo.org mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Please give him a warm welcome!
Woohoo!
Thanks for all your hard work as an AT Matti, I know I'll be happy
to let you commit on your own now. ;)
- -Joe
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozil
20 matches
Mail list logo
