systemd 238 and sysusers
by Zbigniew Jędrzejewski-Szmek
Hi,
systemd 238 has been released [1] and is building in F28 and rawhide.
This release has more bugfixes than new features, but there are some
changes that might be particularly interesting for Fedora:
- cgroups v2 is now supported much better. In particular a long-standing
conflict between cgroups v2 and systemd-run --user --scope has
been fixed. Please try systemd-cgtop with a recent kernel and the v2
hierarchy to check out the improved accounting.
- various transfiletriggers have been ported from Mageia, for the udev
hwdb and rules, the journal catalog, sysctl.d, binfmt.d, sysusers.d,
and tmpfiles.d. This means that for many packages, which do not need
those rules to be applied immediately, scriptlets can be totally
removed.
- somewhat independently, systemd-sysusers has been beefed up so it is
possible to use it to create system users before any files are
installed on disk, but honouring admin overrides. In short, we now
recommend the following invocation to create users for an rpm which
contains files owned by those users:
%sysusers_create_package %{name} %SOURCEN
where %SOURCEN is the tmpfiles.d config file which will be installed
by package. This expands to
echo "u NAME - -" | systemd-sysusers --replace=/usr/lib/sysusers.d/NAME.conf - >/dev/null 2>&1 || :
and the "u NAME - -" configuration is applied with a priority that
/usr/lib/sysusers.d/NAME.conf normally has (so e.g.
/etc/sysusers.d/NAME.conf will override this).
[1] https://raw.githubusercontent.com/systemd/systemd/master/NEWS
Zbyszek
6 years, 2 months
orphaning German dictionary/thesaurus/hyphenation
by Michael Stahl
hello,
i've orphaned these linguistic packages for "de" languages:
* hunspell-de
this tends to have a new release once or twice a year
* mythes-de
upstream is a bit odd in that there is a new automatically generated
.oxt file once per day, but the file name never changes...
* hyphen-de
this one never changes
they are all up-to-date in rawhide/F28.
6 years, 2 months
Unannounced soname bump (Rawhide): brotli
(libbrotli{common,enc,dec}.so.1.0.1 -> libbrotli{common,enc,dec}.so.1)
by Adam Williamson
brotli was updated from 1.0.1-3 to 1.0.3-1 in Rawhide on 2018-03-03.
This update bumped the sonames from libbrotli{common,enc,dec}.so.1.0.1
to libbrotli{common,enc,dec}.so.1 (not a typo, that's really the change).
This soname bump was not announced, as it is supposed to be.
httpd (Apache) and webkit2gtk3 (via woff2) depend on these libs. So this
broke any web server, and multiple images (including release blocking
ones) which depend on webkit2gtk3 for one reason or another, and so the
whole Rawhide compose - the 20180305.n.0 Rawhide compose failed due to
this issue.
Both dependencies have now been rebuilt. However, I still wanted to
send this mail to draw attention to another unannounced soname bump
that broke the compose.
Once again, folks, *please* announce your soname bumps, and co-ordinate
rebuilds.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
6 years, 2 months
[Modularity] Working Group IRC meeting minutes (2018-03-06)
by Nils Philippsen
=================================================================================
#fedora-meeting-3: Meeting of the Modularity Working Group (once every two weeks)
=================================================================================
Meeting started by nils at 15:00:00 UTC.
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-3/2018-03-06/modularity_...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-3/2018-03-06/modularity_...
Log: https://meetbot.fedoraproject.org/fedora-meeting-3/2018-03-06/modularity_...
Meeting summary
---------------
* Roll Call (nils, 15:00:06)
* Agenda (nils, 15:01:48)
* [puiterwijk]: Using Bodhi for modular content (nils, 15:01:48)
* [sgallagh]: imminent libmodulemd-1.1 release (nils, 15:03:37)
* Using Bodhi for modular content (nils, 15:03:59)
* puiterwijk's suggestion to enable the bodhi workflow for modules was
accepted (nils, 15:21:57)
* imminent libmodulemd-1.1 release (nils, 15:22:19)
* libmodulemd-1.1 coming sometime this week, may require minor tweaks
to python import (sgallagh, 15:28:19)
* Open Floor (nils, 15:29:11)
* autosigning is now working for modules and signs it as soon as a
module is submitted to Bodhi (nils, 15:30:03)
Meeting ended at 15:33:01 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* nils (40)
* sgallagh (24)
* puiterwijk (20)
* zodbot (15)
* contyk (5)
* sct (4)
* tflink (2)
* langdon (2)
* asamalik (1)
* dgilmore (1)
* mikedep333 (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Nils Philippsen "Those who would give up Essential Liberty to
Software Engineer purchase a little Temporary Safety, deserve neither
Red Hat Liberty nor Safety." -- Benjamin Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011
6 years, 2 months
Call for testing of xserver 1.20 release candidates
by Adam Jackson
Short version:
$ sudo dnf copr enable ajax/upstream
$ sudo dnf upgrade
Long version:
I've set up a copr containing a rebuild of the X server and drivers for
the upstream 1.20 release candidates. Unfortunately the upstream and
Fedora schedules didn't line up as well as I'd have liked, so I'm not
going to try to land this for F28 GA. But I would _very_ much like to
push this as an update, and would appreciate any and all testing and
feedback.
- ajax
6 years, 2 months
Kernel marking files in /boot as %ghost
by Samuel Rakitničan
Dear list,
I've stumbled upon a serious issue that has not been discussed before. Somewhere around May 2015 kernel files was moved to /usr/lib/modules/<kernelver>, which are then copied to /boot in post scriptlets [1]. The issue is that such files are marked with %ghost because they don't exist initially and are being copied when installed. Now because of that rpm (rpm -qV) can't verify the files attributes correctly and heck even doesn't point out if they don't exist at all as it is the case if dnf fails in the middle of transaction. Because of that I've opened a bug report [2], but it was closed because that was supposedly intended, but looking at mailing list archive, I don't see this particular issue being raised and frankly in my opinion marking files that are responsible to boot the system as %ghost should not happen. %ghost should be used only when there is not any other option left in case when files truly doesn't exist and its integrity could not be verified in advance.
[1] https://lists.fedoraproject.org/pipermail/kernel/2015-May/005819.html
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1467450
6 years, 2 months
