Heads-up: I dropped most of the build flags customizations in mpich.
This "resets" mpich back to the Fedora defaults and, inter alia, adds
all the hardening options. Unit tests pass, including those in dependent
packages, but of course this is not a definitive proof of anything. If
you see any strange crashes or slowdowns, please let me know.
Once upon a time, qca needed this, but hasn't for quite awhile, so I'm no
longer interested in maintaining compat-opensl10-pkcs11-helper
According to repoquery, one item (still) depends on it:
I just submitted my first review request on Bugzilla :
https://bugzilla.redhat.com/show_bug.cgi?id=1706548. The packaged
software is called "simple-dnf" and it is meant to be a lightweight (and
fast) GUI for DNF. I did not create it but I found it very quite cool
and effective; as I was interested by the packaging world I decided to
create a COPR repository for testing purpose:
https://copr.fedorainfracloud.org/coprs/arkelis/simple-dnf/, now I'm
submitting for official repo!
To introduce myself, I'm Guillaume Fayard, a French student at a general
engineering school; I'm interested in Python, Web development, Server
administration... I did not yet contribute to many open source project,
I usually help to translate things (for example Python docs). I have
small website (in French) hosting various documents I'm writing / I
I need to install a directory (/afs) that will be a mountpoint that a systemd
service (also installed in the rpm) will mount upon.
What's the best way to encode this in the specfile?
I did have:
but that doesn't upgrade correctly. Someone gave me another way to do it:
# Create /afs directory if it doesn't exist
if [ ! -d /afs ]; then
chown root.root /afs
chmod 0755 /afs
[ -x /usr/sbin/restorecon ] && /usr/sbin/restorecon /afs
%ghost %dir /afs
but rpmlint complains about the chown:
kafs-client.x86_64: W: dangerous-command-in-%post chown
The git repo is here:
The second patch from the top is the one that tries to fix the mountpoint dir
installation issue ("spec: Treat /afs special").
For some reason, a "mock install" ends up running %post scripts with
LC_ALL=en_US.UTF8, for which I need glibc-all-langpacks.
This does not happen with a manual install from a mock shell.
The tiny spec file below reproduces the problem.
If I use "mock -n install" (I have a few other things in the chroot that I
need), the log file shows that the locale is en_US.UTF8.
If I run a mock shell, and manully "rpm -i" inside the shell, the locale is
the expected C.UTF-8
Anyone knows why I'm getting a bad locale, with mock install?
Summary: Locale in mock
Group: System Environment/Base
rm -rf $RPM_BUILD_ROOT
mkdir -p $RPM_BUILD_ROOT
rm -rf $RPM_BUILD_ROOT
* Mon May 6 2019 Sam Varshavchik <mrsam(a)octopus.email-scan.com> -
- Initial build.