The deadline for submitting Self-Contained Changes for Fedora 30 is
Tuesday, 29 January. Changes must be set to the ChangeReadyForWrangler
category by the end of the day Tuesday.
Fedora Program Manager
Sorry for the delay….
Please submit the new documents as soon as possible.
Invoice EP329947-932 (previous version is attached)
Thank you for your business!
I got a bug report that the applications that use a libpcreposix library
crash after building with an --as-needed linker flag
<https://bugzilla.redhat.com/show_bug.cgi?id=1667614>. It turned out
that many distributions (except Fedora) have already patched
libpcreposix (in an incompatible way) and that upstream rejected that
change in PCRE (because PCRE is obsolete) and applied a partial fix to
After some tests and deliberation, I came to a following resolution for
PCRE2's libpcre2-posix library will receive the upstream fix and will be
patched so that an application built with the patched library does not
suffer from the crashes. This change is compatible with future upstream
PCRE's libpcreposix library will receive similar fix. This change is
incompatible with future upstream releases (assuming upstream won't
change his mind).
This change is implemented in pcre2-10.32-6.fc30 and pcre-8.42-7.fc30.
For applications to take the benefit of this change, they need to be
rebuilt. I will perform the rebuild in Rawhide. These packages are
Both PCRE and PCRE2 libraries will be patched in older Fedoras later.
gcc9 exposed an underlying issue with some inline asm on s390x. I've emailed
upstream about the issue but it's still not fixed. In the interest of
continuing to test kernels, I've disabled this arch in rawhide kernels
for now. I'll be keeping an eye on this and plan to turn this arch back
on as soon as I can.
I'm updating icu to 63.1 in rawhide and rebuilding anything that links with libicu. We'll also have a compat package with libicu 62 soname, so I don't expect much rawhide breakage: anything that is currently built with libicu 62 but fails to build with libicu 63 should just continue using the compat package.
Hello, I am testing various changes in boinc-client systemd unit file.
At every RPM package update, it happens really often that on a machine
that installs the new RPM version, does not get the new systemd unit
file version, so it is not updated. To successfully update the file, I
have to remove the old one from
and reinstall the RPM file.
How can this happen? Perhaps manual edits (on localhost) can prevent
the file to be updated?