-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Drake wrote:
Hi,
The local root exploit-of-the-week would have been unable to run if our
users systems had /proc mounted with nosuid and/or noexec
It would be worthwhile considering making this a default. What are
people's thoughts?
On Sunday 16 July 2006 10:07, Josh Saddler wrote:
Daniel Drake wrote:
Hi,
The local root exploit-of-the-week would have been unable to run if our
users systems had /proc mounted with nosuid and/or noexec
It would be worthwhile considering making this a default. What are
people's thoughts?
Chris Gianelloni wrote:
On Sat, 2006-07-01 at 12:18 -0600, Ryan Hill wrote:
Should arch testers start working with 4.1.1 then? And do you want bugs to
block #117482?
Arch testers should contact their architecture's leads or Release
Engineering Architecture Coordinator. As for bug reports,
Ned Ludd [EMAIL PROTECTED] wrote:
Not 100% sure about the noexec part as that might break upx which
calls /proc/self/exe as part of it's decompresser routines.
/proc/self/exe is a symlink, and the permissions of symlinks aren't used
for anything. It's less than trivial (and I think
On Sat, 2006-07-15 at 15:20 -0400, Mike Frysinger wrote:
On Saturday 15 July 2006 13:41, Ned Ludd wrote:
On Sat, 2006-07-15 at 17:45 +0100, Daniel Drake wrote:
The local root exploit-of-the-week would have been unable to run if our
users systems had /proc mounted with nosuid and/or noexec
(apologies in advance if this goes through twice)
Chris Gianelloni wrote:
On Sat, 2006-07-01 at 12:18 -0600, Ryan Hill wrote:
Should arch testers start working with 4.1.1 then? And do you want bugs to
block #117482?
Arch testers should contact their architecture's leads or Release
Hi All,
As a little weekend project, I wrote a command line interface to
bugzilla in Python that is targetted to Gentoo's bugzilla (but also
generalisable to other bugzillas with a little code modification). It
can do the following:
* search bugzilla and output a table of bugs: bugz search
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alastair Tse wrote:
Hi All,
As a little weekend project, I wrote a command line interface to
bugzilla in Python that is targetted to Gentoo's bugzilla (but also
generalisable to other bugzillas with a little code modification). It
can do the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm happy to announce a new addition to the perl team (no, not that kind
of addition - Dr. says that's in September folks;). You may know him
from such bugzilla favorites as libeperl dies on `awk` and
libwww-perl has incorrect RDEPEND, or under his
Some packages don't provide standard setup.py. Take a look at the attachment.This is a new ebuld.So my suggestion is to add a new variable to distutils.eclass, e.g. SETUP.PY, if it's set, then use it, otherwise let it defaults to
setup.py.Looking forward to hear your feedback on this.-- Zhang Le,
Welcome, Yuval! :D
--
Peter Gordon (codergeek42)
Gentoo Forums Global Moderator
GnuPG Public Key ID: 0xFFC19479 / Fingerprint:
DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479
signature.asc
Description: OpenPGP digital signature
Zhang Le wrote:
Some packages don't provide standard setup.py.
Take a look at the attachment.
This is a new ebuld.
So my suggestion is to add a new variable to distutils.eclass, e.g.
SETUP.PY, if it's set, then use it, otherwise let it defaults to
setup.py.
what about making a simple
Alastair Tse wrote:
You can get it either via my portage overlay in:
http://overlays.gentoo.org/svn/dev/liquidx/app-admin/pybugz
or as a python distutils compat tarball in
http://media.liquidx.net/static/pybugz/pybugz-0.5.tar.gz
Cool! Any reason why not commit it - at least package.masked? ;)
On Sun, 2006-07-16 at 20:33 +0200, Jakub Moc wrote:
Alastair Tse wrote:
You can get it either via my portage overlay in:
http://overlays.gentoo.org/svn/dev/liquidx/app-admin/pybugz
or as a python distutils compat tarball in
http://media.liquidx.net/static/pybugz/pybugz-0.5.tar.gz
Cool!
Welcome yuval.
Regards,
Roy bamford
--
gentoo-dev@gentoo.org mailing list
Alastair Tse wrote:
I know there's gentoo-bugger, which is great, but it's in perl and I
couldn't figure out how to modify the output to suit my needs.
yeah gentoo-bugger was interactive, this one is better :)
I really like it, thank you.
Here's the README attached if you're interested in how
On Monday 10 July 2006 01:51, Ryan Hill wrote:
No, that would be a major pain in the ass for anyone wanting to use
-fast-math, which does have legitimate uses.
I want to pose here that -ffast-math has NO LEGITIMATE use as a global CFLAG.
In some apps it doesn't matter as they don't use math.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Cummings wrote:
I'm happy to announce a new addition to the perl team (no, not that kind
of addition - Dr. says that's in September folks;). You may know him
from such bugzilla favorites as libeperl dies on `awk` and
libwww-perl has
On Tuesday 11 July 2006 04:32, Ryan Hill wrote:
If yes, why ? And what is your better idea ?
I prefer a filter-flags with a ewarn (or elog, haven't read that thread yet
;)) message.
* The -ffast-math option is known to break this package and has been
filtered from your CFLAGS. Link to
Michael Cummings wrote:
I'm happy to announce a new addition to the perl team
Welcome! Perl, huh? :P
http://fastar.detonate.net/ftp/images/matrixse/18/6.jpg
--
Best regards,
Jakub Moc
mailto:[EMAIL PROTECTED]
GPG signature:
http://subkeys.pgp.net:11371/pks/lookup?op=getsearch=0xCEBA3D9E
Paul de Vrieze wrote:
My argument is that we must not filter -ffast-math or any other dangerous
cflags. The reason being that people will request more filters for all
packages that don't work with it. Many users will either ignore or miss the
warning messages. Filtering the flag basically
On Mon, 2006-07-17 at 00:49 +0800, Zhang Le wrote:
Some packages don't provide standard setup.py.
Take a look at the attachment.
This is a new ebuld.
I agree with Stefan, just put a symlink in from whatever their distutils
install script is to setup.py in src_unpack(). This seems to be such
Ryan Hill wrote:
Just an update - I've finished most major desktop stuff for x86 without any
problems. I'm moving onto stuff that's already on the tracker and is fixed in
testing but not stable. Rather than open and track a ton of new bugs, I'd
like
to reopen the original ~arch bugs and
On Thursday 13 July 2006 18:53, Ciaran McCreesh wrote:
On Thu, 13 Jul 2006 14:55:57 +0200 Paul de Vrieze [EMAIL PROTECTED]
wrote:
| The dev manual is *wrong*.
No, the devmanual reflects what's actually being done, rather than an
impractical definition that was written years ago that no
On Thursday 15 June 2006 20:17, Marcus D. Hanwell wrote:
I have to agree that I have never understood the need for the distinction
between herd and team. It does not seem to add anything, I guess some
people do not like being referred to as a herd may be? It really doesn't
bother me. I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
MASKINGS:
- ---
media-gfx/gtksee - Mr. Bones requested this be removed; no update since
Nov 2004. Plenty of other image viewers out there, only uses gtk1
package.mask:
# Michael
On 7/17/06, Alastair Tse [EMAIL PROTECTED] wrote:
On Mon, 2006-07-17 at 00:49 +0800, Zhang Le wrote: Some packages don't provide standard setup.py. Take a look at the attachment. This is a new ebuld.I agree with Stefan, just put a symlink in from whatever their distutils
install script is to
Hi all,
I had a discussion yesterday with the folks and #gentoo-portage
regarding API documentation using epydoc and inline custom doc
strings. Attached is a proposal of what I believe
encompasses a majority of the discussion. Suggestions, comments,
etc. are welcome. My standard gentoo account
On Mon, Jul 17, 2006 at 03:12:25AM +0900, Chris White wrote:
This document is meant to serve as a proposal for the documentation of portage
code using epydoc[1] and custom doc blocks.
epytext actually- that's what relies on, and is supported by
other doc manglers.
2. Other portage API
epytext actually- that's what relies on, and is supported byother doc manglers.
Change noted in the attached proposal
Bad idea.doc strings rules for doc manglers, the base docstringbleeds through to derivative methods iff the prototype hasn't been
mangled.So... you state in the base method, I
30 matches
Mail list logo
