Greetings testers! Typically we'd have a blocker review meeting
tomorrow, but with Go/No-Go this Thursday and a pretty solid RC out and
being tested, we might not need one. Currently there are no proposed
blockers (and let's hope we've handled all of them), so we won't be
having a meeting.
OTOH, if we do find some tonight or before the meeting tomorrow we'll go
ahead and have the meeting to discuss whatever has been found.
Just wanted to give everyone a heads up. Thanks!
test-announce mailing list
Reposted from <http://fedoramagazine.org/5tftw-2014-12-02/>.
Fedora is a big project, and it’s hard to keep up with everything that
goes on. This series highlights interesting happenings in five
different areas every week. It isn’t comprehensive news coverage — just
quick summaries with links to each. Here are the five things for
December 2nd, 2014:
Fedora 21 on track for Dec. 9!
Things are looking good for our scheduled December 9th release. We’re
in the process of validating release candidates, and everything seems
in great shape. (And it's not too late to join in: see the announcement
on the test list if you're interested in helping.) Assuming no
unexpected showstoppers, we’ll approve this as official at the Thursday
“Go / No-Go” meeting, and then it’ll be off to the mirror network for
release next Tuesday morning!
Presenting the New Fedora Council
With the conclusion of the first round of elections, the new Fedora
Council is in place! If you’ve missed it (perhaps you’re just coming by
to see what’s up with the new Fedora 21 release and this happened while
you weren’t watching), read up on it on the Fedora Council wiki
Five of the six full-vote members are in place:
- **Elected Representative:** Rex Dieter
- **Elected Representative:** Langdon White
- **Engineering Representative:** Josh Boyer
- **Outreach Representative:** Christoph Wickert
- **Fedora Project Leader:** Matthew Miller
The sixth seat is the **Fedora Community Action and Impact
Coordinator**, which will be a full-time position hired and funded by
Red Hat’s Open Source and Standards group. (More on this job opening
The council also includes a number of *auxiliary seats*. As the Council
> They are intended to have significant positive impact on the project
> as a whole, but in order to minimize the overall influence of
> appointed positions vs. those selected by the community, their votes
> in the consensus process are expected to be related to the scope of
> the respective role.
One of these is the **Fedora Program Manager** — Jaroslav Resnik.
Another is the **Diversity Advisor**, a position for which we will be
appointing a search committee shortly. And finally, the Council will
select **Objective Leads** — more on that on my previous Fedora
Magazine post about project objectives.
Thanks to the Outgoing Board
I want to offer a huge personal and also official thank you to all
previous members of the Fedora Project Board, whose care and dedication
have been instrumental in guiding Fedora to where we are today.
And I particularly want to thank the most recent board members —
Christoph Wickert, Garret Holmstrom, John Rose, Matthew Garrett, Eric
Chrstensen, Josh Boyer, Haïkel Guémar, and Neville Cross — and all
other project contributors who provided ideas, feedback, wisdom, and
significant effort in constructing the new governance model.
Fedora EMEA Gets Ready for F21
Jiří Eischmann has a blog post about getting the physical manifestation
of the Fedora release ready for the Europe / Middle East / Africa
> I’ve been using Fedora 21 on my home computer since alpha, so it’s
> really nothing new for me, but I’m really excited about the release.
> In my opinion, it will be the most significant release since Fedora 7
> when Core and Extras got merged. It’s also been the most stable
> release of Fedora I’ve used.
> While Fedora QA guys are working on the final polishing as that F21
> can meet the final criteria, ambassadors are getting ready for the
> release. [...]
In addition to background notes about stickers, Jiří includes a preview
of the awesome F21 DVD sleeves designed by Alexander Smirnov (a.k.a.
How many users does Fedora have?
Alec Leamas started an interesting discussion on the Fedora Devel list,
asking, “How many users does Fedora have?“. The answer is… we don’t
really know. This is notoriously hard to count, and Fedora has always
opted for more privacy-preserving options, something many in our
contributor community care very strongly about. Stephen Smoogen is
working on coming up with some graphs based on mirror traffic, but
that’s only part of the picture, and an imperfect one.
Finding useful metrics for progress towards project goals and then
iteratively acting to improve them is a powerful tool for making sure
that our effort goes towards what we want to do [*] in the most
effective way. Ben Cotton started a sub-thread about _asking the right
questions_, which reminded me of ticket #1 for the Fedora Council
(copied over from previous work by the Board). Let’s keep this
discussion going. (And, one more plug here… helping get these metrics
right is part of the job responsibilities of the future Community
Action and Impact position.)
* This topic is probably better for the Fedora Council Discuss
mailing list, (renamed from board-discuss and, before that,
advisory-board), since it’s not strictly about Fedora development,
but, eh, not everyone is aware of that list. Next time! :)
Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/>
Fedora Project Leader mattdm(a)fedoraproject.org <http://fedoraproject.org/>
Just an F21 validation test status heads up.
We found a cosmetic but highly visible font issue in RC2:
https://bugzilla.redhat.com/show_bug.cgi?id=1169979 . The most obvious
effect is that at least the Workstation and KDE x86-64 lives use a
pretty ugly font 'Nimbus Mono L' as their default monospace font - the
one used in terminals and text editors, for e.g. - instead of the
intended default, DejaVu Sans Mono.
Fortunately we can workaround this problem for the live images pretty
easily and in a way which is very safe: just run fc-cache -f at the end
of the live compose process. We are now spinning RC3 with that change.
As the difference between RC2 and RC3 is so small, we're gonna say that
all RC2 testing is valid against RC3. Once the RC3 compose is done I'll
transfer the RC2 test results into the RC3 test matrix.
So, please just go ahead and carry on testing RC2 completely as normal.
Once RC3 comes out we can switch to testing those images.
The RC3 non-live images should be functionally identical to RC2.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
test-announce mailing list
Resending this as a new thread, for increased visibility.
As explained in the older thread, the Mozilla project has started to
remove CA certificates that contain weak keys. Those removals cause
issues with software based on OpenSSL, and software based on older
versions of GnuTLS.
(A short description of the issue can be found in tracker bug
https://bugzilla.redhat.com/show_bug.cgi?id=1166614 - I intend to file a
ticket against OpenSSL shortly.)
For Fedora, we have decided to keep the legacy CA certificates included
and trusted by default, in order to avoid compatibility issues, until we
get functional updates to OpenSSL.
I'm documenting the changes on top of the Mozilla CA
list at: https://fedoraproject.org/wiki/CA-Certificates
However, we want to provide users/administrators with the ability to
change the default, by configuring the ca-certificates to strictly
follow the trust decisions made by Mozilla, thereby accepting the
compatibility issues (e.g. untrusted TLS connections, if certificates of
affected server configurations cannot be validated).
The above has been implemented for Fedora 21, it looks like it will be
included as part of the Fedora 21 release:
Using the new ca-legacy utility, it is possible to disable trust for the
legacy CA certificates as a systemwide configuration, by executing this
command as root:
The configuration will be remembered in /etc/pki/ca-trust/ca-legacy.conf
and will be used on future package upgrades, when additional
certificates are moved to the legacy state.
If required, it's possible to undo the configuration and revert to the
current default, using:
The current configuration can be shown using:
Regarding Fedora 19 and Fedora 20:
On F19/F20, GnuTLS is also affected by the breakage, when disabling
trust for the legacy CAs, because GnuTLS has been enhanced in Fedora 21
and later, only.
Updated packages for F19 and F20, that provide the update to version 2.1
of the ca-certificates list, and which also include the new ca-legacy
utility and configuration mechanism, have been pushed to
As you might know ABRT attaches 'environ' file to its Bugzilla bugs. The file
contains a full copy of /proc/[pid]/environ. Even though ABRT highlights
black-listed words and encourages users to review the data before submitting
them, it may happen that the reporter misses something and publishes his secrete
data in 'environ' file.
Do you find 'environ' attachment valuable or is ABRT just publishing personal