Hello Fedora package maintainers,
Kindly build and push your packages with latest translation files (ie,
pull the latest translations from Transifex/Zanata) by FRIDAY
2013-09-27, for Fedora 20 L10n test scheduled on 2013-10-03 (Thursday).
The packages with latest translations can thus be used to create the
live image, which the language translators worldwide can use for testing
in their own languages on this test day. Any issues they find will be
filed as bug. Appreciate your help in this regard as this is an
opportunity for the translators to check and modify the translation
quality of your package.
Thanks for your support and understanding.
devel-announce mailing list
GNOME 3.10.0 release is this week and we're going to collect all the
builds together and filing them as a single Bodhi megaupdate for F20.
As usual, the spreadsheet for collecting all the builds together is at
We've also got a separate koji build target that can be used with:
$ fedpkg build --target f20-gnome
I'm seeing corruption occur after doing a balance of a btrfs volume. Scrubs before the balance are error free. Scrubs after balance have many errors, so far all seem to be either unlisted or point to a systemd-journal log path. Example:
[ 318.029771] btrfs: checksum error at logical 2209439744 on dev /dev/sda4, sector 6412464, root 256, inode 25764, offset 6746112, length 4096, links 1 (path: var/log/journal/10db2764a11a4829bf82a94c6559d121/system.journal)
Further, this is not a corruption of btrfs metadata, but data itself:
[ 19.354354] systemd-journald: /var/log/journal/8e4cbfea404512ae70096c6202c9a3bf/system.journal: Journal file corrupted, rotating.
If I change systemd-journaling to volatile storage, erase the persistent storage location logs, reboot, and try to reproduce the problem, I can't. There are some reports of VM images on btrfs being corrupted somehow (although I don't think it's related to balance, I could be wrong), and the solution is to set VM images to nodatacow. So I wonder if there's some behavior of systemd journaling that's similar?
Bug is here:
I was wondering as to why Ananconda has no facility to overwrite a
distro already present on the target machine. I've studied it & apart
from destroying the existing partition with GParted there seems to be no
other way (this happens on 18 & 19).
Most painful it is.
If anybody can show me a workaround I'd be most grateful.
Arch Linux, CentOS 5.9 & 6.4, Debian Squeeze & Wheezy, Fedora Beefy, Spherical & That Damn Cat, Lubuntu 12.10, OS X Snow Leopard & Tiger, Ubuntu Precise, Quantal & Raring
GnuGPG Key : http://phildobbin.org/publickey.asc
This bug is nearly a year old, requesting that package offlineimap be
upgraded to what was then the latest release (6.5.4, now it is
6.5.5-rc2). There has been no response from the maintainer.
I posted a bug comment on 01 July asking for something from the package
maintainer and received no word.
I don't want to take over the package, but would like either the primary
or else a co-maintainer to upgrade the package as it has bugs that have
been fixed since 6.5.2 (the currently packaged release).
Darryl L. Pierce <mcpierce(a)gmail.com>
"What do you care what people think, Mr. Feynman?"
-----BEGIN PGP SIGNED MESSAGE-----
Basically looking at compressing the policy file to shrink SELinux footprint
in the minimal install/cloud image.
Currently the policy modules (pp files) are shipped with bzip compression but
the actually policy file.
But the /etc/selinux/targeted/policy/policy.29 is not compressed. systemd and
load_policy use libselinux to read in the policy file and load it into the
kernel, so since systemd currently uses libxz, I figured this would be the
best solution to add libxz support to libselinux.
ls -l /etc/selinux/targeted/policy/policy.29*
- -rw-r--r--. 1 root root 2703245 Sep 11 13:56
- -rw-r--r--. 1 root root 395072 Sep 11 13:56
Worth the effort?
Should I use a different algorithm?
Advise on using libxz? Keep memory small?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----