Remaining F16 blockers and F16 planning (2011-10-27)
by Adam Williamson
[meant to go out last night but failed thanks to internet connection
silliness]
Yes, it's episode three of the blockbuster 'Remaining F16 blockers'
trilogy - thanks for lining up all week, folks, have a complimentary
small popcorn.
As mentioned last time, we span a TC3 image for testing while we try to
zap the remaining blockers:
http://dl.fedoraproject.org/pub/alt/stage/16.TC3/
It has the rebuilt glibc and all affected packages rebuilt against that
glibc. See the TC3 announce for more details. Onto the main event!
1. http://bugzilla.redhat.com/show_bug.cgi?id=749661 "repoclosure
failure on 16.TC3 DVD - PackageKit-zif-0.6.19-3.fc16 requires zif >=
0:0.2.5"
This is new in TC3, but it's straightforward and should be easy to solve
for the next compose. No action really needed.
2. http://bugzilla.redhat.com/show_bug.cgi?id=736893 "New Install of
Fedora 16 TC1 on iBFT iSCSI NIC fails on first reboot"
We've got more data on this one since last time; given that data it'll
likely get dropped from the blocker list, but we'll poke it a bit more
first to make sure.
3. https://bugzilla.redhat.com/show_bug.cgi?id=731245 "KDE fails to
start inside a VM , large amount of memory [@ miCopyRegion]"
We've had some progress on this one today but it still needs work; with
qxl driver, KDE no longer crashes, but has serious rendering problems.
We also determined the issue with the cirrus driver (which is used in
older KVM configs, and 32-bit VMs) is separate and needs to be addressed
separately. Soren says he hopes to have this fixed early tomorrow.
4. http://bugzilla.redhat.com/show_bug.cgi?id=749618 "Mimetype tree is
not a DAG!" errors + crashes when using SMI 0.91"
This causes crashes in some KDE apps, it's already fixed, so the only
action is to pull in the fixed build for the next compose.
5. http://bugzilla.redhat.com/show_bug.cgi?id=749647 "KDE fails to start
in side a VM using the cirrus driver and 'raster' Qt renderer"
This is the cirrus KDE bug: we need X developers to fix this if
possible. I've tried to contact all who may be able to work on it,
including upstream.
6. http://bugzilla.redhat.com/show_bug.cgi?id=748920 "Setting back time
breaks boot"
We've worked out more stuff about this one since yesterday; we may be
able to declare it not a blocker based on the various workarounds
available, but we could really do with input from Lennart on why systemd
apparently doesn't provide the emergency mode sometimes when
systemd-fsck fails.
7. http://bugzilla.redhat.com/show_bug.cgi?id=748747 "Totem doesn't
display video when using software 3D rendering"
We're still really waiting on ajax (or anyone)... to fix this one. We've
confirmed that every test case we've tried with no hardware-accelerated
3D rendering causes broken gstreamer video.
8. http://bugzilla.redhat.com/show_bug.cgi?id=749516 "date doesn't set
persistent date"
This is newly proposed and could do with more info, but may well not
really be serious enough to take as a blocker.
We're obviously pushing the F16 schedule quite hard at this point, but
we can still stay on track if we manage to get all the blockers
addressed tomorrow; we will try to get all validation tests done against
TC3 so we can be reasonably sure there are no other blockers lurking,
and that should give us a reasonable chance at spinning an RC1 with the
extra fixes that passes testing on the first try.
Please, help out with any of the above bugs you can. Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
11 years, 7 months
Remaining F16 blockers and F16 planning (2011-10-26)
by Adam Williamson
Hey, folks. This mail brought to you by my ever-increasing empty liquor
bottle collection and ever-receding hairline.
We unfortunately still have open blockers today, which means we will
likely do a TC3 compose tonight instead of RC1. The remaining
unaddressed blockers are:
1. https://bugzilla.redhat.com/show_bug.cgi?id=668282 "PackageKit yum
backend uses incorrect encoding for dynamic category names, makes them
show up with '?' characters in KPackageKit"
Nils reported that he would complete work on this today, but has not
checked in today at all. This leaves us somewhat stuck, as only Richard
Hughes and Nils are really qualified to work on this. Richard is away
this week.
2. https://bugzilla.redhat.com/show_bug.cgi?id=731245 "KDE fails to
start inside a VM , large amount of memory [@ miCopyRegion]"
Soren fixed the initial issue, but KDE on qxl still doesn't really work
correctly. Details and logs are in the latest comments on the bug, and
I'm currently uploading a live image for convenient reproduction. Again,
contributions are welcome here.
3. https://bugzilla.redhat.com/show_bug.cgi?id=736893 "New Install of
Fedora 16 TC1 on iBFT iSCSI NIC fails on first reboot"
Again, we're still rather looking for information from the reporter
here. Tim may be able to acquire an iBFT NIC for testing today.
4. https://bugzilla.redhat.com/show_bug.cgi?id=748747 "Totem doesn't
display video when using software 3D rendering"
Did not hear from ajax in relation to this bug today. Again, we really
need development input on this one.
5. https://bugzilla.redhat.com/show_bug.cgi?id=747377 "heap corruption
via multi-threaded "git grep""
This is the bug in glibc 12.999 and 13 which can at least potentially
cause just about any app to crash. We're in the middle of addressing it;
a fixed glibc is out for testing and we are now mass-rebuilding all
packages which hit stable since glibc 12.999 made it to the buildroot.
This, obviously, isn't speeding up the whole release process any.
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
11 years, 7 months
Remaining F16 blockers and F16 planning
by Adam Williamson
Hey, folks. Just thought I'd send out an overview of remaining
unaddressed F16 blockers, in case anyone can help with them. We were
scheduled to do the F16 RC compose today, but with these unaddressed, we
can't. We hope we'll be able to do the compose tomorrow, but if blockers
remain unaddressed, we'll fall back to doing a compose labelled TC3 so
we can at least test and ensure that the release is ready aside from the
remaining known blockers.
1. https://bugzilla.redhat.com/show_bug.cgi?id=668282 "PackageKit yum
backend uses incorrect encoding for dynamic category names, makes them
show up with '?' characters in KPackageKit"
Nils is working on this one and currently expects to have a fix ready
for tomorrow.
2. https://bugzilla.redhat.com/show_bug.cgi?id=731245 "KDE fails to
start inside a VM , large amount of memory [@ miCopyRegion]"
Any input on this bug is welcome; it's easy enough to reproduce
(download any post-Alpha F16 KDE live image and try to boot to a desktop
within a typical virt-manager created KVM). Soren has said he'll look at
this tomorrow, but any other contributions would be good.
3. https://bugzilla.redhat.com/show_bug.cgi?id=736893 "New Install of
Fedora 16 TC1 on iBFT iSCSI NIC fails on first reboot"
We're still rather looking for information from the reporter here, but
if others have iSCSI-capable setups it would be good to have more
testing. Tim Flink from the QA team has done successful iSCSI testing,
but that's only one data point.
4. https://bugzilla.redhat.com/show_bug.cgi?id=743273 "grub2 fails to
install on IMSM raid device"
This is another where we could probably do with more data: we know
install to Intel BIOS RAID *can* work, but it also seems somewhat
fragile. Jes had various issues in some of his tests but eventually got
it to work; pjones and I have had successful tests but I also had a
couple of that failed with similar errors to Jes'. More tests of
installs of F16 Final TC2 to Intel BIOS RAID might help establish
exactly where the bugs are.
5. https://bugzilla.redhat.com/show_bug.cgi?id=748747 "Totem doesn't
display video when using software 3D rendering"
ajax is planning to look at this one tomorrow, I believe, but again, it
would be great to have input from anyone else who's able to help fix the
issue. Note that the issue affects most GNOME components which do video
- not just totem, but cheese and empathy also. Video is broken when
using software 3D in all of them.
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
11 years, 7 months
Upcoming elections for FAmSCo, FESCo, and the Fedora Board
by Jared K. Smith
One of the things I like most about Fedora is the orderly way in which
people are able to move in and out of leadership positions within our
community. Each development cycle, we have a set of elections for the
steering committees and for the Fedora Board. The next election cycle
is nearly upon us, so I'd like to take this opportunity to share the
details of the upcoming elections with you.
As quick reminder, the nomination period for this election cycle will
open on 25 October 2011, and will close promptly on 5 November 2011 at
23:59:59 UTC. The full elections schedule, along with more details
about the elections, can be found at
https://fedoraproject.org/wiki/Elections
I strongly encourage you to consider running for an open position in
one of the elections. This is one way to serve your fellow community
members and help move Fedora forward at the same time. Additionally,
I'm looking for a few volunteers to help with the coordination of the
candidate questionnaires and town hall meetings. If you're willing to
help, please let me know.
== Fedora Board ==
This election cycle will fill two elected seats for the Board (seats
E1 and E2). Prior to the election I will also announce the first of
two appointed seat in this cycle (seats A1 and A2), with the second
appointment announcement to follow after the election. For more
information on nominations, and the process refer to:
https://fedoraproject.org/wiki/Board_nominations
https://fedoraproject.org/wiki/Board/Elections
https://fedoraproject.org/wiki/Board/History
== FESCo ==
This cycle will also see four candidates elected to open seats in the
Fedora Engineering Steering Committee. For information on the
nominations and elections:
https://fedoraproject.org/wiki/FESCo_election_policy
https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations
== FAmSCo ==
This election cycle will also see candidates elected to fill all all
seven seats on the Fedora Ambassadors Steering Committee. For more
information, refer to:
https://fedoraproject.org/wiki/FAmSCo_election_rules
https://fedoraproject.org/wiki/FAmSCo_elections
https://fedoraproject.org/wiki/FAmSCo_election_2011_nominations
== Candidate Questionnaire and Town Hall meetings ==
Additionally, the nomination period also serves as the time for the
community to present questions to be posed to candidates. If you wish
to ask questions to be answered by candidates, you can add them at
https://fedoraproject.org/wiki/F17_elections_questionnaire. Candidates
will have the questions posed to them and responses made available to
the community before the voting period begins.
As we get closer to the elections, we will try to schedule several
Town Hall Meetings in IRC to help you get to know the candidates
better, and to ask them additional questions.
As always, I'm thankful to those who have given their time, talents,
and abilities to serve the Fedora community.
--
Jared Smith
Fedora Project Leader
11 years, 7 months
last stable push for f16 GA
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
on Monday October 24 we will be doing the last push to stable, after
that the only things that will get pushed to stable before GA will be
things that have been accepted as release blockers.
Thanks
Release Engineering
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iEYEARECAAYFAk6i3tAACgkQkSxm47BaWfchrwCgoouqgTQq84Rsyt8hOFRM+l8E
4JMAn36WeYlQT2MLo6FVAFQroAcS6QjX
=RLXF
-----END PGP SIGNATURE-----
11 years, 7 months
Subsidy requests for FUDCon Blacksburg are now OOOOOPEN!
by Robyn Bergeron
Greetings, FUDCon friends, near and far:
As you are probably aware, the 2012 North American FUDCon will be held
in Blacksburg, Virginia, on the campus of Virginia Tech. If you are
planning on attending, it's never too early to pre-register, and to
start thinking about your travel plans. FUDCon Blacksburg will take
place January 13-15, 2012.
https://fedoraproject.org/wiki/FUDCon:Blacksburg_2012
I'm happy to announce that we are officially accepting subsidy requests
for travel to Blacksburg. If you are requesting a subsidy, we just have
a few steps that we ask you to follow:
1: Register on the FUDCon: Blacksburg wiki page in the pre-registration
area.
https://fedoraproject.org/wiki/FUDCon:Blacksburg_2012#Pre-registration
2: Put an X in the $$$ column.
3: Create a funding request ticket in the FUDCon trac at:
https://fedorahosted.org/fudcon-planning/wiki/FundingRequest
General information about being sponsored can be found at
http://fedoraproject.org/wiki/Sponsoring_event_attendees .
Requests are processed in a first-come, first-served manner, though
generally prioritization is giving to local travel over international
travel first. Requests will be reviewed by fellow Fedora community
members at FUDCon subsidy request meetings over the next few weeks.
The first subsidy meeting will take place on Wednesday, November 9th.
The time and IRC channel will be announced as we approach that day.
As always, participation both in planning as well as subsidy granting is
ALWAYS welcome. Please join us on the fudcon-planning mailing list for
information about meetings, as well as for general FUDCon updates, and
see the "meetings" section of your FUDCon's wiki page for meeting
information.
Mailing list:
https://admin.fedoraproject.org/mailman/listinfo/fudcon-planning
FUDCon Blacksburg Meetings:
https://fedoraproject.org/wiki/FUDCon:Blacksburg_2012#Meetings
11 years, 7 months
Subject: IMPORTANT: Mandatory password and ssh key change by 2011-11-30
by Kevin Fenzi
Subject: IMPORTANT: Mandatory password and ssh key change by 2011-11-30
Summary:
All existing users of the Fedora Account System (FAS) at
https://admin.fedoraproject.org/accounts are required to change their
password and upload a NEW ssh public key before 2011-11-30.
Failure to do so may result in your account being marked inactive.
Passwords changed and NEW ssh public keys uploaded after 2011-10-10
will meet this requirement.
Backgound and reasoning:
This change event has NOT been triggered by any specific compromise or
vulnerability in Fedora Infrastructure. Rather, we believe, due to the
large number of high profile sites with security breaches in recent
months, that this is a great time for all Fedora contributors and users
to review their security settings and move to "best practices" on their
machines. Additionally, we are putting in place new rules for passwords
to make them harder to guess.
New Password Rules:
* Nine or more characters with lower and upper case letters, digits and
punctuation marks.
* Ten or more characters with lower and upper case letters and digits.
* Twelve or more characters with lower case letters and digits
* Twenty or more characters with all lower case letters.
* No maximum length.
Some Do's and Don'ts:
* NEVER store your ssh private key on a shared or public system.
* ALWAYS use a strong passphrase on your ssh key.
* If you must store passwords, use an application specifically for this
purpose like revelation, gnome-keyring, seahorse, or keepassx.
* Regularly apply your operating system's security related updates.
* Only use ssh agent forwarding when needed ( .ssh/config:
"ForwardAgent no")
* DO verify ssh host keys via dnssec protected dns. ( .ssh/config:
"VerifyHostKeyDNS yes")
* DO consider a seperate ssh key for Fedora Infrastructure.
* Work with and use security features like SELinux and iptables.
* Review the Community Standard Infrastructure security document (link
below)
Q&A:
Q: My password and ssh private key are fine and secure!
Can't I just skip this change?
No. We believe the new guidelines above provide an added measure of
security compared to the previous requirements. We want all users of
our infrastructure to follow the new guidelines to improve one aspect
of security across the systems they share. Awareness is also an
aspect of good security. By requiring these changes, we also hope to
maintain and improve awareness of the process for changing passwords
and keys.
Q: Can I just change my password and re-upload my same ssh public key?
Or upload a bogus ssh public key and then re-upload my old one?
A: No. We've installed safeguards to ensure that your new ssh public
key is different from your old one. Additionally, some of our
contributors may have had accounts on compromised high profile Linux
sites recently, and we want to make sure no ssh private keys or
passwords used in Fedora Infrastructure were obtained via those
incidents.
Q: This is a hassle. How often is this going to happen?
A: The last mass password change in Fedora was more than 3 years ago.
Absent a triggering event, these mass changes will be infrequent.
Q: The new password length requirements/rules are too strict.
How will I remember passwords that are that long?
A: You can employ a password storage application (see above), or
use a method like diceware (see below), or construct a memorable
sentence or phrase.
Q: How do I generate a new ssh key? How do I use it for just Fedora
hosts?
A: See http://fedoraproject.org/wiki/Cryptography and use a
~/.ssh/config file to match fedoraproject.org hosts for that key.
Q: I never uploaded a ssh key to the Fedora Account System, nor am I
in a group that needs one, do I still have to upload a new one?
A: No. If you don't have a ssh public key uploaded or desire to do so,
you can just change your password.
More reading:
http://infrastructure.fedoraproject.org/csi/security-policy/en-US/html-si...
https://fedoraproject.org/wiki/Infrastructure_mass_password_update
http://xkcd.com/936/
http://www.iusmentis.com/security/passphrasefaq/
http://world.std.com/~reinhold/diceware.html
http://fedoraproject.org/wiki/Cryptography
11 years, 8 months
Announcing the release of Fedora 16 Beta!!
by Dennis Gilmore
Mark your calendars, and get ready to go exploring: The release of
Fedora 16, codenamed "Verne," is scheduled for release in early
November. Fedora is the leading edge, free and open source operating
system that continues to bring everyone fresh, innovative features
with each release, delighting users worldwide every six months.
We are proud to announce the availability of the Beta release of Fedora 16.
Come see why we love Fedora so much. We are betting you will, too.
Download it now:
http://fedoraproject.org/get-prerelease?anF16b
== What is the Beta Release? ==
The Beta release is the last important milestone of Fedora 16. Only
critical bug fixes will be pushed as updates leading to the general
release of Fedora 16 in early November. We invite you to join us in
making Fedora 16 a solid release by downloading, testing, and
providing your valuable feedback.
Of course, this is a beta release, meaning that some problems may
still be lurking. A list of the problems we already know about is
found at the Common F16 bugs page, seen here:
http://fedoraproject.org/wiki/Common_F16_bugs
== Features ==
This release of Fedora includes a variety of features both over and
under the hood that show off the power and flexibility of the
advancing state of free software. Examples include:
* System Boot. Fedora 16 introduces GRUB2, the long-awaited
next-generation boot-loader for Linux. GRUB2 automatically recognizes
other operating systems, supports LVM2 and LUKS partitions, and is
more customizable than the previous version. In this release, only x86
systems with a BIOS uses GRUB2 by default. Work is ongoing for making
GRUB2 the default for other architectures and systems.
* Services Management. Fedora 15 introduced the Systemd services
management program. This release features better integration of
Systemd via conversion to native systemd services from legacy init
scripts in many software components -- for desktop users, this means
faster boot times; for system administrators it means more powerful
management of services.
* Desktop Updates. The two major desktop environments have been
updated to the latest releases: KDE Software Compilation 4.7 and GNOME
3.1 development release.
* SELinux Enhancements. SELinux policy package now includes a
pre-built policy that will only rebuild policy if any customizations
have been made. A sample test run shows 4 times speedup on installing
the package from 48 Seconds to 12 Seconds and max memory usage from
38M to 6M. In addition to that, SELinux file name transition allows
better policy management. For instance, policy writers can take
advantage of this and write a policy rule that states, if a SELinux
unconfined process creates a file named resolv.conf in a directory
labelled etc_t, the file should get labeled appropriately. This
results is less chances of mislabeled files. Also, from this release
onwards, selinuxfs is mounted at /sys/fs/selinux instead of in
/selinux. All the affected components including anaconda, dracut,
livecd-tools and policycoreutils have been modified to work with this
change.
* System Accounts. Fedora now standardizes on login.defs as
authority for UID/GID space allocation, and has moved boundary between
system and user accounts from 500 to 1000 to match conventions
followed by several other Linux distributions. Upgrading from a
existing release will not be affected by this change and you can use
kickstart to override this change during installation if necessary.
* HAL Removal. HAL, a hardware abstraction layer which has been a
deprecated component for several releases, has been completely removed
from all Fedora spins and DVD. Software components using HAL have
moved over to using udisks and upower as well as libudev for device
discovery. This results in faster system bootup and faster startup for
applications depending on device discovery.
* Cloud Updates. Fedora now includes a number of new and improved
features to support cloud computing, including HekaFS, a "cloud ready"
version of GlusterFS, including additional auth*/crypto/multi-tenancy;
pacemaker-cloud, application service high availability in a cloud
environment; and IaaS implementations such as Aeolus and OpenStack.
* Virtualization. Once again Fedora raises the bar on
virtualization support, including expanded virtual network support, an
improved Spice for managing virtual machines, restored Xen support, a
new virtual machine lock manager, and improved ability to browse guest
file systems.
* Developer Improvements. Developers get many goodies with Verne,
including updated Ada, Haskell and Perl environments, a new Python
plugin for GCC and a number of new and improved APIs.
And that's only the beginning. A more complete list and details of all
the new features in Fedora 16 is available here:
http://fedoraproject.org/wiki/Releases/16/FeatureList
We have nightly composes of alternate spins available here:
http://alt.fedoraproject.org/pub/alt/nightly-composes/
== Contributing to Fedora ==
For more information on common and known bugs, tips on how to report
bugs, and the official release schedule, please refer to the release
notes:
http://docs.fedoraproject.org
There are many ways to contribute beyond bug reporting. You can help
translate software and content, test and give feedback on software
updates, write and edit documentation, help with all sorts of
promotional activities, and package free software for use by millions
of Fedora users worldwide. To get started, visit
http://join.fedoraproject.org today!
11 years, 8 months
