-----BEGIN PGP SIGNED MESSAGE-----
As of yesterday, the deadline for submitting bids for Flock 2015 has
passed. There were four bids made:
* Salt Lake City, Utah, USA
* Colorado Springs, Colorado, USA
* Rochester, New York, USA
* Cape Cod, Massachusetts, USA
Ultimately, the selection of the location is up to the Flock Planning
Committee, but I'd like to run an informal poll on this list to ask
people to rate each of these locations on a scale of -5 to 5 how much
this particular location would affect their interest in attending Flock.
In other words:
- -5: I would not want to attend Flock if it was held in this location.
0: This location has no effect on my decision to go to Flock.
5: I would go to Flock just for the excuse to visit this location.
Note: this is *not* asking whether you plan to attend Flock, just how
much the selection of each of these locations would play into your
(For the sake of fairness, I'd ask those that submitted bids to excuse
themselves from this poll.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----
I realize I should have done this a long time ago, but perhaps better
now than never. I haven't been around in the Fedora community in a while
and it looks like life will keep me busy for the foreseeable future. As
a result, I'm looking for maintainers for the following packages in
Fedora, most of which are Sugar related.
There are more packages which currently have a co-maintainer, but I
suspect it would make sense to transition ownership away from me. So if
those of you (or someone else) wanted to pick those up, that would be
If you want to claim any of these, please let me know. I'll otherwise
orphan them in about a day or two.
I have orphaned postr a flicker uploader, I have not used it for years
Upstream has been stalled for years, but there has been some recent activity
latest upstream release is 0.13.1 not yet in fedora, because of
python-bsddb3 is not in fedora, only python3-bsddb3 is.
Hi folks! We've met every week for a while, and had blocker review
meetings too. I don't see anything pressing for discussion, either, so I
figure it might be a good week for us to take a break and everyone can
sleep in / get to the pub early (delete as appropriate) :)
Please, do yell if you wanted to have a meeting this week and have an
agenda item, and we can go ahead and do it. Thanks folks!
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
test-announce mailing list
Just spend some time debugging this and thought I should share this, see:
for details, I've filed a bug to track fixing this in Fedora:
There are 2 ways this problem shows itself:
1) If using an initrd which has been generated with the troublesome microcode
update into it, things may already crash during the initrd, e.g. in my case
some luks volumes would not unlock because of this
2) When booting an older kernel (and thus an older initrd) things start crashing
(mostly systemd* processes, grinding everything to a halt) as soon as udev
from the rootfs loads the microcode update
2. often will still get you to an emergency shell, at which point one can
create a /etc/modprobe.conf.d/no_microcode.conf file with:
In there to work around the problem, then regenerate the initrds for newer
kernels, and you should be good to go until bug 1147062 gets fixed properly.