[gentoo-dev] net-mail/mailman needs a new maintainer
net-mail/mailman is without an ebuild maintainer and has an open security bug #129136 https://bugs.gentoo.org/show_bug.cgi?id=129136 Anyone willing to take care of this package in the future, please update metadata.xml and CC yourself on the bug. -- Sune Kloppenborg Jeppesen Gentoo Linux Security Team pgpxOiuFbho4j.pgp Description: PGP signature
Re: [gentoo-dev] net-mail/mailman needs a new maintainer
Am Donnerstag, 13. April 2006 07:07 schrieb Sune Kloppenborg Jeppesen: net-mail/mailman is without an ebuild maintainer and has an open security bug #129136 https://bugs.gentoo.org/show_bug.cgi?id=129136 Anyone willing to take care of this package in the future, please update metadata.xml and CC yourself on the bug. I'm running mailman on a server and was already looking at improving the ebuild a bit. So I think I can take it. I hope I'll get to the revision-bump today, but I can't promise how fast I'll get to the other stuff that's pending (especially webapp-config). For the long term, I plan to include at least optionally the patches for searchable archives, vhosts and gpg-lists. -- Hanno Böck Blog: http://www.hboeck.de/ GPG: 3DBD3B20 Jabber: [EMAIL PROTECTED] pgp0wHYf1w7ac.pgp Description: PGP signature
[gentoo-dev] automatically killing invalid CFLAGS/warning about bad CFLAGS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For about a month now, we (amd64) have had some code in our profile.bashrc that filters CFLAGS that are unrecognized by gcc, and warnings the user about bad CFLAGS. So far it has worked fairly well, and it has really cut down on the number of bugs that filed by people with extreme ricer CFLAGS. It might be an idea to have something similar in the global bashrc, and have a system for arches to customize the CFLAGS that are warned about. The code is at gentoo-x86/profiles/default-linux/amd64/profile.bashrc for those who want to see it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEPqtzWt/XSf2CZdkRArCCAKCR66ousc1+FGOMvz9hGxqFsA0jWQCfbyEM YexV1DYsR286gW+XGyG9Ah4= =ha1J -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: automatically killing invalid CFLAGS/warning about bad CFLAGS
Patrick McLean posted [EMAIL PROTECTED], excerpted below, on Thu, 13 Apr 2006 15:50:11 -0400: For about a month now, we (amd64) have had some code in our profile.bashrc that filters CFLAGS that are unrecognized by gcc, and warnings the user about bad CFLAGS. So far it has worked fairly well, and it has really cut down on the number of bugs that filed by people with extreme ricer CFLAGS. It might be an idea to have something similar in the global bashrc, and have a system for arches to customize the CFLAGS that are warned about. The code is at gentoo-x86/profiles/default-linux/amd64/profile.bashrc for those who want to see it. Not just ricer flags (or I wouldn't call them that anyway and unlike some, can explain each one and why I use it)... I'm running gcc-4.0.x and 4.1.0, the latter as my default compiler, in addition to 3.4.6. One of the flags I use (-ftree-pre) isn't recognized by 3.4.x, and it has been a bit of a hassle removing it each time I revert to 3.4.6 to test something or other. I've been /very/ impressed with the way this works, as now I don't have to worry about killing the flag when I switch gccs, because the profile code kills it for me! =8^) The first time I noticed it, I wondered what kind of magic the ebuild was doing. Then I saw it on a couple others, and then happened across it while reviewing the profile. It works! =8^) -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] automatically killing invalid CFLAGS/warning about bad CFLAGS
Patrick McLean wrote: For about a month now, we (amd64) have had some code in our profile.bashrc that filters CFLAGS that are unrecognized by gcc, and warnings the user about bad CFLAGS. So far it has worked fairly well, and it has really cut down on the number of bugs that filed by people with extreme ricer CFLAGS. It might be an idea to have something similar in the global bashrc, and have a system for arches to customize the CFLAGS that are warned about. The code is at gentoo-x86/profiles/default-linux/amd64/profile.bashrc for those who want to see it. Except you need a way for them to turn it off, and you do not currently provide one. We can set default flags all we want, but I don't see filtering 'bad' flags as necessarily our problem. If you want to say: Hey we have had issues with people filing bogus bug reports with CFLAGS that are completely inappropriate, so by default we check the sanity of your CFLAGS, this is how you turn those checks off. then I'd be ok with it. Most of the Ricers won't read it, and maybe you can print a warning that CFLAG checking is disabled. However leaving it on all the time merely imposes penalties on the power users who wish to use your profile. Your profile is a tool that should be useful to all classes of users. -Alec Warner -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] automatically killing invalid CFLAGS/warning about bad CFLAGS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alec Warner wrote: Except you need a way for them to turn it off, and you do not currently provide one. We can set default flags all we want, but I don't see filtering 'bad' flags as necessarily our problem. If you want to say: Hey we have had issues with people filing bogus bug reports with CFLAGS that are completely inappropriate, so by default we check the sanity of your CFLAGS, this is how you turn those checks off. then I'd be ok with it. Most of the Ricers won't read it, and maybe you can print a warning that CFLAG checking is disabled. However leaving it on all the time merely imposes penalties on the power users who wish to use your profile. Your profile is a tool that should be useful to all classes of users. The only flags that are actually removed are the _invalid_ flags. These are the flags that gcc does not accept, and will error out on. The bad flags, IE the ones that the developers consider to be broken, but that are accepted by gcc are not filtered, the profile simply prints a warning and pauses for 5 seconds to encourage users to read the warning, it does not automatically filter any flags that the compiler accepts. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEPw20Wt/XSf2CZdkRAotCAJ9pRFXAbPine5qYbycGXoeDWyy+DACaA84z KZ43edqxiv30vniE2e2wxlc= =0vEQ -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: automatically killing invalid CFLAGS/warning about bad CFLAGS
Patrick McLean wrote: For about a month now, we (amd64) have had some code in our profile.bashrc that filters CFLAGS that are unrecognized by gcc, and warnings the user about bad CFLAGS. The broken flags part is useful. So far it has worked fairly well, and it has really cut down on the number of bugs that filed by people with extreme ricer CFLAGS. It might be an idea to have something similar in the global bashrc, and have a system for arches to customize the CFLAGS that are warned about. There's an endless number of CFLAGS that could be warned about, and just as many situations where they're actually useful. Aside, I've yet to hear of _anything_ that's broken because of -fvisibility-inlines-hidden. (course someone will undoubtedly point one out now ;)) Maybe if the sleep 5 were removed this would be helpful. Right now i'm just rm-ing the bashrc in my --sync alias. --de. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: automatically killing invalid CFLAGS/warning about bad CFLAGS
R Hill wrote: There's an endless number of CFLAGS that could be warned about, and just as many situations where they're actually useful. Aside, I've yet to hear of _anything_ that's broken because of -fvisibility-inlines-hidden. (course someone will undoubtedly point one out now ;)) How about kde? signature.asc Description: OpenPGP digital signature
[gentoo-dev] Re: automatically killing invalid CFLAGS/warning about bad CFLAGS
Donnie Berkholz wrote: R Hill wrote: There's an endless number of CFLAGS that could be warned about, and just as many situations where they're actually useful. Aside, I've yet to hear of _anything_ that's broken because of -fvisibility-inlines-hidden. (course someone will undoubtedly point one out now ;)) How about kde? Close, that's -fvisibility=hidden. :) http://gcc.gnu.org/gcc-4.0/changes.html#visibility --de. -- gentoo-dev@gentoo.org mailing list
