-------------------------------------------------------------------------------- Fedora Test Update Notification FEDORA-2007-3507 2007-11-20 17:50:55.827610 --------------------------------------------------------------------------------
Name : mock Product : Fedora 8 Version : 0.8.8 Release : 1.fc8 URL : http://fedoraproject.org/wiki/Projects/Mock Summary : Builds packages inside chroots Description : Mock takes a srpm and builds it in a chroot
-------------------------------------------------------------------------------- Update Information:
- make it run correctly when called by the 'root' user - internal_setarch: optionally run 'setarch' internally. This eliminates the need to run "setarch i386 mock ..." when building on target_arch != build_arch. This is turned on by default. Limitations: must have 'ctypes' python module available, which is only available by default in python 2.5, or as an extension module in <= 2.4. If the 'ctypes' module is not available, this feature will be disabled and you must manually run 'setarch'. - Does not run 'clean' action for 'shell', 'chroot', 'install', or 'installdeps' (docs updated) - fix build for top_builddir != top_srcdir - fix 'installdeps' so that it works with both rpms/srpms - missing device file /dev/ptmx was causing 'expect' command to always fail. Affected any SRPM build that used 'expect'. - hard spec file dep on python >= 2.4 due to python syntax changes. - resultdir can now contain python-string substitutions for any variable in the chroot config. rebuild my.src.rpm - add 'dist' variable to all chroot config files so that it is available for resultdir substitutions. - give good error message when logging.ini cannot be found. - change default logging format to remove verbosity from build.log. - make logging format configurable from defaults.cfg or chroot cfg. - less verbose state.log format
-------------------------------------------------------------------------------- ChangeLog:
* Mon Nov 19 2007 Michael Brown mebrown@michaels-house.net - 0.8.8-1 - make it run correctly when called by the 'root' user - internal_setarch: optionally run 'setarch' internally. This eliminates the need to run "setarch i386 mock ..." when building on target_arch != build_arch. This is turned on by default. Limitations: must have 'ctypes' python module available, which is only available by default in python 2.5, or as an extension module in <= 2.4. If the 'ctypes' module is not available, this feature will be disabled and you must manually run 'setarch'. - Does not run 'clean' action for 'shell', 'chroot', 'install', or 'installdeps' (docs updated) - fix build for top_builddir != top_srcdir - fix 'installdeps' so that it works with both rpms/srpms - missing device file /dev/ptmx was causing 'expect' command to always fail. Affected any SRPM build that used 'expect'. - hard spec file dep on python >= 2.4 due to python syntax changes. - resultdir can now contain python-string substitutions for any variable in the chroot config. rebuild my.src.rpm - add 'dist' variable to all chroot config files so that it is available for resultdir substitutions. - give good error message when logging.ini cannot be found. - change default logging format to remove verbosity from build.log. - make logging format configurable from defaults.cfg or chroot cfg. - less verbose state.log format -------------------------------------------------------------------------------- Updated packages:
c02bb9d294d825667fd4ac4849ee0b2074c38c76 mock-debuginfo-0.8.8-1.fc8.ppc64.rpm 6957b323990ddb3cb11f1fa93918660646e16ecb mock-0.8.8-1.fc8.ppc64.rpm d2fcdbaa16821f2f868900bb1f650f41057fae6d mock-0.8.8-1.fc8.i386.rpm 9f86130852e6663852f21aaa8a83c9bda88f2ffc mock-debuginfo-0.8.8-1.fc8.i386.rpm 9a348f5d0683f2d7dfcc1d0314f5c7ba888ceb21 mock-debuginfo-0.8.8-1.fc8.x86_64.rpm e3ac11b0204fcb76ec14321011ed1f03c96c1feb mock-0.8.8-1.fc8.x86_64.rpm bd3a90da4fe8a7df897a2cc5952375a2d8dfe66f mock-0.8.8-1.fc8.ppc.rpm f3c0c9e95bb2cf31453969c070288106a696a10b mock-debuginfo-0.8.8-1.fc8.ppc.rpm 9beff1c3c445563fe13afe83c5a96e0e0ddb35dd mock-0.8.8-1.fc8.src.rpm
This update can be installed with the "yum" update program. Use su -c 'yum --enablerepo=updates-testing update mock' at the command line. For more information, refer to "Managing Software with yum", available at http://docs.fedoraproject.org/yum/. --------------------------------------------------------------------------------
i'm sure there's a reason for this, but why is the fedora *test* list being used as an announcement list for regular release updates? i subscribed to the test list because it was the official forum for ***test*** releases. and until there's another test release, i would have thought there'd be little or no traffic on this list.
why can't there be another list -- say "updates" -- for update announcements?
rday --
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
http://crashcourse.ca ========================================================================
On Tue, 20 Nov 2007 12:57:05 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
i'm sure there's a reason for this, but why is the fedora *test* list being used as an announcement list for regular release updates? i subscribed to the test list because it was the official forum for ***test*** releases. and until there's another test release, i would have thought there'd be little or no traffic on this list.
why can't there be another list -- say "updates" -- for update announcements?
Because these are testing updates, not final updates.
Anyway, we're working on solutions to cut down the noise, like an rss feed of updates announcements.
Jesse Keating said the following on 11/20/2007 10:21 AM Pacific Time:
On Tue, 20 Nov 2007 12:57:05 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
i'm sure there's a reason for this, but why is the fedora *test* list being used as an announcement list for regular release updates? i subscribed to the test list because it was the official forum for ***test*** releases. and until there's another test release, i would have thought there'd be little or no traffic on this list.
why can't there be another list -- say "updates" -- for update announcements?
Because these are testing updates, not final updates.
Anyway, we're working on solutions to cut down the noise, like an rss feed of updates announcements.
I thought we decided to move those to fedora-qa-list so I filed this ticket: https://hosted.fedoraproject.org/projects/bodhi/ticket/130
On Wed November 21 2007 01:33:17 John Poelstra wrote:
Jesse Keating said the following on 11/20/2007 10:21 AM Pacific Time:
On Tue, 20 Nov 2007 12:57:05 -0500 (EST)
"Robert P. J. Day" rpjday@crashcourse.ca wrote:
i'm sure there's a reason for this, but why is the fedora *test* list being used as an announcement list for regular release updates? i subscribed to the test list because it was the official forum for ***test*** releases. and until there's another test release, i would have thought there'd be little or no traffic on this list.
why can't there be another list -- say "updates" -- for update announcements?
Because these are testing updates, not final updates.
Anyway, we're working on solutions to cut down the noise, like an rss feed of updates announcements.
I thought we decided to move those to fedora-qa-list so I filed this ticket: https://hosted.fedoraproject.org/projects/bodhi/ticket/130
Another list will take the updates away from the eyes of testers this is bad, but something along the lines of "Fedora n Test Update Report" is the perfect solution to me.
https://hosted.fedoraproject.org/projects/bodhi/ticket/137
...dex
Jesse Keating wrote:
On Tue, 20 Nov 2007 12:57:05 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
i'm sure there's a reason for this, but why is the fedora *test* list being used as an announcement list for regular release updates? i subscribed to the test list because it was the official forum for ***test*** releases. and until there's another test release, i would have thought there'd be little or no traffic on this list.
why can't there be another list -- say "updates" -- for update announcements?
Because these are testing updates, not final updates.
Anyway, we're working on solutions to cut down the noise, like an rss feed of updates announcements.
rss isn't convenient for everyone. My vote goes to a new list, initially populated with the members of this.
maybe for the future, the description for this list could include something like this text:
If you want to track and discuss testing package updates, then you might join fedora-test-updates too.
John Summerfield wrote:
Jesse Keating wrote:
On Tue, 20 Nov 2007 12:57:05 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
i'm sure there's a reason for this, but why is the fedora *test* list being used as an announcement list for regular release updates? i subscribed to the test list because it was the official forum for ***test*** releases. and until there's another test release, i would have thought there'd be little or no traffic on this list.
why can't there be another list -- say "updates" -- for update announcements?
Because these are testing updates, not final updates.
Anyway, we're working on solutions to cut down the noise, like an rss feed of updates announcements.
rss isn't convenient for everyone. My vote goes to a new list, initially populated with the members of this.
maybe for the future, the description for this list could include something like this text:
If you want to track and discuss testing package updates, then you might join fedora-test-updates too.
I'd rather see it continue to make sure those on the test discussion list were aware of the test updates that are being pushed out... the noise of the announcements is not drowning the list by any means, and if people aren't aware that packages are being pushed to test then less testing will occur. The sooner those on the list download the packages the better, and not everyone is doing nightly updates I'm sure.
Is another list really necessary? These announcements themselves provide a great thread top email for discussing a broken update.
On Thu, 22 Nov 2007, Andrew Farris wrote:
John Summerfield wrote:
Jesse Keating wrote:
On Tue, 20 Nov 2007 12:57:05 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
i'm sure there's a reason for this, but why is the fedora *test* list being used as an announcement list for regular release updates? i subscribed to the test list because it was the official forum for ***test*** releases. and until there's another test release, i would have thought there'd be little or no traffic on this list.
why can't there be another list -- say "updates" -- for update announcements?
Because these are testing updates, not final updates.
Anyway, we're working on solutions to cut down the noise, like an rss feed of updates announcements.
rss isn't convenient for everyone. My vote goes to a new list, initially populated with the members of this.
maybe for the future, the description for this list could include something like this text:
If you want to track and discuss testing package updates, then you might join fedora-test-updates too.
I'd rather see it continue ...
not to sound rude, but what you'd rather see is not really germane to the discussion. what *is* germane -- as i've already suggested -- is that i originally joined this ML because i wanted to participate in the discussion regarding fedora test *releases*. OTOH, i have little interest in staying on top of the constant stream of fedora test *updates*, but i'm being force-fed that information anyway. so what's the problem with a new ML with that particular mandate?
to make sure those on the test discussion list were aware of the test updates that are being pushed out...
except that there are some of us who aren't interested in that information.
the noise of the announcements is not drowning the list by any means, ...
um ... have you counted the number of recent posts related to package test updates? in fact, that is *all* that is being posted on this list. how precisely does that *not* constitute "drowning the list"?
and if people aren't aware that packages are being pushed to test then less testing will occur.
once again, that's not my problem. if you want to test packages, feel free. i don't, so i don't want to hear about them. why is that such a difficult concept to grok?
Is another list really necessary?
yes.
rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
http://crashcourse.ca ========================================================================
Robert P. J. Day wrote:
not to sound rude, but what you'd rather see is not really germane to the discussion. what *is* germane -- as i've already suggested -- is that i originally joined this ML because i wanted to participate in the discussion regarding fedora test *releases*. OTOH, i have little interest in staying on top of the constant stream of fedora test *updates*, but i'm being force-fed that information anyway. so what's the problem with a new ML with that particular mandate?
to make sure those on the test discussion list were aware of the test updates that are being pushed out...
except that there are some of us who aren't interested in that information.
So your point is that you feel the community really needs to have list setup such as below? fedora-test-updates-list fedora-test-release-list fedora-devel-list
all of which relate to testing and development issues for packages not yet released...
Just having the announcements split off to another list hardly suits your needs either given your feelings above and not wanting to know anything about updates and discussion of them.
the noise of the announcements is not drowning the list by any means, ...
um ... have you counted the number of recent posts related to package test updates? in fact, that is *all* that is being posted on this list. how precisely does that *not* constitute "drowning the list"?
and if people aren't aware that packages are being pushed to test then less testing will occur.
once again, that's not my problem. if you want to test packages, feel free. i don't, so i don't want to hear about them. why is that such a difficult concept to grok?
Email filtering? All update announcements originate from updates@fedoraproject.org, you could simply not see any of them with 2minutes of your time. Granted if the *majority* of people on the list fall into your category its wasted bandwidth to have all the announcements going out to them all, but thats not necessarily the case. I'm not saying your ideas are invalid, just playing devil's advocate about even *MORE* email lists... everyone's needs and interest in the information stream is going to be different.
Splintering discussions about updates away from next release testing will tend to also reduce cross-talk on related problems. Just my 2c, thats a bad thing.
On Thu, 22 Nov 2007, Andrew Farris wrote:
Robert P. J. Day wrote:
except that there are some of us who aren't interested in that information.
So your point is that you feel the community really needs to have list setup such as below? fedora-test-updates-list fedora-test-release-list fedora-devel-list
um ... yes. if those lists represent different mandates, they should be different lists.
all of which relate to testing and development issues for packages not yet released...
but they don't, do they? as i have already pointed out *twice*, this very list is advertised as being devoted to development *releases*, not development *packages*. and that's why i subscribed. if i wanted to know about test *updates*, i'd be willing to subscribe to another list.
Email filtering? All update announcements originate from updates@fedoraproject.org, you could simply not see any of them with 2minutes of your time.
why should it be necessary for me to filter the contents of a mailing list because the majority of its postings aren't relevant? and filtering doesn't do anything about the fact that all this irrelevant content ends up on my mail server anyway.
Splintering discussions about updates away from next release testing will tend to also reduce cross-talk on related problems. Just my 2c, thats a bad thing.
*not* breaking that stuff off onto another list will *definitely* reduce feedback on test releases since i, for one, will unsubscribe from this list if it continues to tell me stuff i'm not interested in. if red hat wants to announce and get feedback on test updates, they can create a new list specifically for that and i can choose whether or not to *opt in*. i *don't* like the situation where i begin getting stuff i never signed up for, which requires me to *opt out*. see the difference?
in any event, i've said my piece, and i'll abide by the decision of the powers that be. if the decision is to preserve the current situation, then i'll just unsubscribe.
rday --
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
http://crashcourse.ca ========================================================================
On Thu, 2007-11-22 at 03:17 -0800, Andrew Farris wrote:
So your point is that you feel the community really needs to have list setup such as below? fedora-test-updates-list fedora-test-release-list fedora-devel-list
all of which relate to testing and development issues for packages not yet released...
Just having the announcements split off to another list hardly suits your needs either given your feelings above and not wanting to know anything about updates and discussion of them.
Actually, I believe there is discussion going on (devel-list maybe?) about disbanding the test-list and moving all discussions to devel-list anyway.
Now, upon whether that happens or not, if it does, there is already a fedora-package-announce list for official updates. Either there is a separate one for test-updates, or they too will also move to devel-list and you'll need to specify more in your filters to help separate the emails on conversion vs announcements, as I have.
I guess it all comes down to, what is easier to use/maintain in all of this, fewer lists and just setup filters to get through them easier, but more traffic? Or more lists, less traffic, but also more things to admin, take care of, and watch on the hosting side? Lots of things to consider?
Mike Chambers wrote:
On Thu, 2007-11-22 at 03:17 -0800, Andrew Farris wrote:
So your point is that you feel the community really needs to have list setup such as below? fedora-test-updates-list fedora-test-release-list fedora-devel-list
all of which relate to testing and development issues for packages not yet released...
Just having the announcements split off to another list hardly suits your needs either given your feelings above and not wanting to know anything about updates and discussion of them.
Actually, I believe there is discussion going on (devel-list maybe?) about disbanding the test-list and moving all discussions to devel-list anyway.
I won't be joining it. Not entirely related to this, I'm reflecting on my membership of fedora-list, I find I'm spending too much time on it.
So if there's no list for discussing pending new releases and I find fedora-list takes more of my time than I wish to spend, how/where then do I participate?
Now, upon whether that happens or not, if it does, there is already a fedora-package-announce list for official updates. Either there is a separate one for test-updates, or they too will also move to devel-list and you'll need to specify more in your filters to help separate the emails on conversion vs announcements, as I have.
I guess it all comes down to, what is easier to use/maintain in all of this, fewer lists and just setup filters to get through them easier, but more traffic? Or more lists, less traffic, but also more things to admin, take care of, and watch on the hosting side? Lots of things to consider?
Put it all in one list. I'll get my coat and leave. I want less mail, not more.
Really, there's not much ongoing maintenance for a list, it's more related to volume (and class of user) than the number of lists, and sharing the workload is easier if there are more units to share around.
Andrew Farris wrote:
Robert P. J. Day wrote:
not to sound rude, but what you'd rather see is not really germane to the discussion. what *is* germane -- as i've already suggested -- is that i originally joined this ML because i wanted to participate in the discussion regarding fedora test *releases*. OTOH, i have little interest in staying on top of the constant stream of fedora test *updates*, but i'm being force-fed that information anyway. so what's the problem with a new ML with that particular mandate?
to make sure those on the test discussion list were aware of the test updates that are being pushed out...
except that there are some of us who aren't interested in that information.
So your point is that you feel the community really needs to have list setup such as below? fedora-test-updates-list
More-or-less daily package releases and consequential discussion.
fedora-test-release-list
Fedora betas, maybe Rawhide as a whole as it would be increasingly appropriate as a new Fedora's birth approaches.
fedora-devel-list
Hacking on packages for Fedora and any affiliates.
Sounds good to me.
all of which relate to testing and development issues for packages not yet released...
Just having the announcements split off to another list hardly suits your needs either given your feelings above and not wanting to know anything about updates and discussion of them.
Speaking of which, I wonder whether the newsletter (which I value) could have its own list too?
Email filtering? All update announcements originate from
Until recently I was pulling (much to my astonishment) 3 Gbytes/month. That's through a modem.
Once it's arrived, it's too late.
updates@fedoraproject.org, you could simply not see any of them with 2minutes of your time. Granted if the *majority* of people on the list fall into your category its wasted bandwidth to have all the announcements going out to them all, but thats not necessarily the case. I'm not saying your ideas are invalid, just playing devil's advocate about even *MORE* email lists... everyone's needs and interest in the information stream is going to be different.
I think more lists doesn't actually mean much in terms of administrative cost, and it falls on the few anyway whereas the burden of dealing with the relatively large volume falls on many.
Splintering discussions about updates away from next release testing will tend to also reduce cross-talk on related problems. Just my 2c, thats a bad thing.
People involved in all two or three areas are likely to be on all two or three. If there's something relevant to two lists, they'll make the connexion and (maybe) cc the other. Yes, I hate it when someone takes a discussion from one list to another, but that's not exactly what I'm talking about here.
Those of us who don't want the daily updates don't read them. Rather than pay my ISP to receive them so I can discard them, I'd rather not receive them.
On Thu, 22 Nov 2007, John Summerfield wrote:
Jesse Keating wrote:
On Tue, 20 Nov 2007 12:57:05 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
i'm sure there's a reason for this, but why is the fedora *test* list being used as an announcement list for regular release updates? i subscribed to the test list because it was the official forum for ***test*** releases. and until there's another test release, i would have thought there'd be little or no traffic on this list.
why can't there be another list -- say "updates" -- for update announcements?
Because these are testing updates, not final updates.
Anyway, we're working on solutions to cut down the noise, like an rss feed of updates announcements.
rss isn't convenient for everyone. My vote goes to a new list, initially populated with the members of this.
maybe for the future, the description for this list could include something like this text:
If you want to track and discuss testing package updates, then you might join fedora-test-updates too.
yes, that sounds about right. my objection was based on this list's own description in the "To:" line above, and i emphasize:
"For testers of Fedora Core development ***releases***"
not "packages". "releases". so, not to put too fine a point on it, unless you have something to discuss related to a fedora development ***release***, you should take that information elsewhere, and a new ML would seem to be the perfect solution.
rday --
======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
http://crashcourse.ca ========================================================================
Robert P. J. Day wrote:
On Thu, 22 Nov 2007, John Summerfield wrote:
maybe for the future, the description for this list could include something like this text:
If you want to track and discuss testing package updates, then you might join fedora-test-updates too.
yes, that sounds about right. my objection was based on this list's own description in the "To:" line above, and i emphasize:
"For testers of Fedora Core development ***releases***"
not "packages". "releases". so, not to put too fine a point on it, unless you have something to discuss related to a fedora development ***release***, you should take that information elsewhere, and a new ML would seem to be the perfect solution.
rday
I joined for the same reason as rday. I want to be here to talk about how the next _release_ is broken, and maybe opine as to what its content should be.
I'm not a hacker, and I'm not sure I want to flog myself with raw hide. As I recall from the Westerns I used to read, it hurts.
Robert P. J. Day schrieb:
On Thu, 22 Nov 2007, John Summerfield wrote:
Jesse Keating wrote:
On Tue, 20 Nov 2007 12:57:05 -0500 (EST) "Robert P. J. Day" rpjday@crashcourse.ca wrote:
i'm sure there's a reason for this, but why is the fedora *test* list being used as an announcement list for regular release updates? i subscribed to the test list because it was the official forum for ***test*** releases. and until there's another test release, i would have thought there'd be little or no traffic on this list.
why can't there be another list -- say "updates" -- for update announcements?
Because these are testing updates, not final updates.
Anyway, we're working on solutions to cut down the noise, like an rss feed of updates announcements.
rss isn't convenient for everyone. My vote goes to a new list, initially populated with the members of this.
maybe for the future, the description for this list could include something like this text:
If you want to track and discuss testing package updates, then you might join fedora-test-updates too.
yes, that sounds about right. my objection was based on this list's own description in the "To:" line above, and i emphasize:
"For testers of Fedora Core development ***releases***"
not "packages". "releases". so, not to put too fine a point on it, unless you have something to discuss related to a fedora development ***release***, you should take that information elsewhere, and a new ML would seem to be the perfect solution.
which ML would you prefer or suggest? fedora-test-update-list ? fedora-update-test-list ? ...
here is a short list oif the fedora MLs:
https://www.redhat.com/mailman/listinfo ----snip---- fedora-advisory-board [no description available] fedora-announce-list Announcements related to the Fedora Project fedora-arm Discussions about the Fedora ARM Project Fedora-art-list Discussions about the artwork included with Fedora, including icons, themes, and wallpapers. fedora-board-list [no description available] Fedora-buildsys-list Discussion of Fedora build system Fedora-cs-list Fedora user list for Czech and Slovak people. fedora-cvs-commits Fedora Core cvs commits Fedora-de-list Fedora discussions in German Fedora-desktop-list Discussions about development for the Fedora desktop Fedora-devel-announce [no description available] fedora-devel-java-list Discussion list for java related Fedora development fedora-devel-list Development discussions related to Fedora Fedora-developer-sig [no description available] Fedora-directory-announce Announcements for the Fedora Directory server project Fedora-directory-commits List of CVS commits to the Fedora Directory server project Fedora-directory-devel Fedora Directory server developer discussion. Fedora-directory-users General discussion list for the Fedora Directory server project. Fedora-docs-br Projeto de Documentação Fedora Brasil Fedora-docs-commits For tracking commits to Docs Project CVS module (/cvs/docs/) fedora-docs-list For participants of the Documentation Project Fedora-eclipse-commits [no description available] Fedora-edu-br [no description available] Fedora-education-list Fedora Education Initiative Fedora-el-list The mailing list of the greek Fedora community Fedora-es-list Fedora discussions in Spanish fedora-extras-commits Fedora Extras CVS commits fedora-extras-list Closed -- please use fedora-devel-list instead (Was: Discussion related to Fedora Extras) Fedora-fonts-bugs-list Automated issue tracking on fonts and other Fedora text rendering components Fedora-fonts-list Discussions on fonts and other Fedora text rendering components Fedora-fr-list [no description available] Fedora-games-list Fedora Games Fedora-i18n-list Fedora internationalization discussions Fedora-ia64-list ia64 Fedora Core Development Fedora-india Mailing list for Indian contributors and users Fedora-infrastructure-list [no description available] Fedora-ja-list Fedora discussions in Japanese Fedora-kernel-list Fedora kernel development. Fedora-laptop-list Laptop related things fedora-legacy-list Discussion of the Fedora Legacy Project Fedora-legal-list [no description available] fedora-list For users of Fedora Fedora-marketing-list For discussions about marketing and expanding the Fedora user base Fedora-mentors-list Mailing list for Fedora project mentors Fedora-mktg-poland [no description available] Fedora-music-list [no description available] Fedora-news-list [no description available] Fedora-ocaml-list Fedora OCaml list Fedora-package-announce Fedora Package Announcements Fedora-package-review Fedora Package Reviews Fedora-packaging Discussion of RPM packaging standards and practices for Fedora Fedora-perl-devel-list Fedora perl development team Fedora-php-devel-list Fedora PHP development team fedora-qa-list Fedora QA Fedora-r-devel-list [no description available] Fedora-relnotes-content Raw content for release notes and docs flows into this mailing list. Fedora-security-commits Commit messages about changes in fedora-security module Fedora-security-list Public discussions about Fedora Related security issues fedora-selinux-list Fedora SELinux support list for users & developers. Fedora-sparc [no description available] fedora-test-list For testers of Fedora Core development releases Fedora-trans-ar Arabic Translation Team for Fedora Core Fedora-trans-as Mailing list for Fedora Assamese translations Fedora-trans-bg [no description available] Fedora-trans-bn [no description available] Fedora-trans-bn_in Mailing List for Fedora Bengali India Translation Community Fedora-trans-el Discussions about fedora localization in the greek language Fedora-trans-hi [no description available] Fedora-trans-ja Fedora translation discussion in Japanese Fedora-trans-list Fedora Translation Project List Fedora-trans-sk [no description available] Fedora-trans-sr Fedora Serbian translators team Fedora-trans-urdu Fedora Urdu Translator's Mailing List fedora-triage-list Fedora BugZappers Triage Discussion Fedora-users-br Lista de discussão voltada para os usuários brasileiros do Fedora Fedora-websites-list For maintainers and developers of all formal Fedora websites. Fedora-women-list List for discussion among the women of Fedora Fedora-xen About using Xen with Fedora ----snap----
-
Andrew Farris -
dexter -
Jesse Keating -
John Poelstra -
John Summerfield -
Mike Chambers -
Robert P. J. Day -
shrek-m＠gmx.de -
updates＠fedoraproject.org