Postings by Germano Massullo

nextcloud-client 2.5: help for updating qt syslibs patch

Hi there. I am testing nextcloud-client 2.5 beta 1 [0], and I am in
troubles with syslib patch[1].

Errors in compiling darktable subpackages

I am working on adding more features to darktable (basecurve tool and
noise tool subpackages).

In log [1] from line

BUILDSTDERR: /usr/bin/ld:
CMakeFiles/dt-curve-tool.dir/dt-curve-tool.c.o: relocation R_X86_64_32S
against symbol `spline_set' can not be used when making a shared object;
recompile with -fPIC

there are many errors, and I don't understand if they are upstream
programming errors or more likely errors in my spec file.

Build URL is
<a href="" title=""></a>

Thank you for your time

<a href="" title=""></a>

Fixing KeepassXC missing Gnome tray icon

A user filled the following bugreport
<a href="" title=""></a>
concerning KeepassXC from Fedora repository missing the Gnome tray icon.
He states that the upstream AppImage build instead is not affected by
this problem.

The spec file seems to be fine so I don't understand where the problem
could be.

Best regards

Understanding popd pushd usage in RPM spec file

Hi, I need some help in understanding how popd and pushd work in rpm
files creation.
Today I started working on enhancing darktable spec file [1] in order to
add basecurve-tool and noise-tool subpackages, and I had some
difficulties in understanding popd/pushd usage in that spec file.
Despite is a package that I maintain, the popd/pushd usage has been
implemented by past Fedora maintainers.
I have spent the afternoon searching on internet and reading again the
guide <a href="" title=""></a>
and I also made some practise after having read StackOverflow question
[2], but I still do

nextcloud-client packaging help wanted

Hello, I am the maintainer of nextcloud-client.
I am writing to ask for help in maintaining nextcloud-client.
Actually nextcloud-client is just a nextcloud themed version[1] of
The new nextcloud-client[3] instead is still at a very alpha state.
We used to be 5 maintainers, but after months of co-maintainers being
unresponsive, I removed them, otherwise people could think that there
are plenty of people working on the package.

The package needs to be updated to lastest owncloud-client version and
there is also the need for starting working on a new spec file for the
next ge

Concerning /etc/opt usage

Today I have received pull request [1].
Since line 62
%dir %{_sysconfdir}/opt/chrome/native-messaging-hosts/
and since packaging guidelines [2] say that a package may only use
directories in the |/opt/fedora,|
I would reject this pull request.
What do you think about?
Best regards

<a href="" title=""></a>
<a href="" title=""></a>

Estonia Open-EID available again

Hello, I am glad to announce that the Estonia Open-EID client software
stack[1], has been unretired and updated to lastest version.
To use it, simply install open-eid package.
System reboot is recommended[2].

Best regards

[1]: <a href="" title=""></a>
[2]: <a href="" title=""></a>

Estonia Open-EID available again

Hello, I am glad to announce that the Estonia Open-EID client software
stack[1], has been unretired and updated to lastest version.
To use it, simply install open-eid package.
System reboot is recommended[2].

Best regards

[1]: <a href="" title=""></a>
[2]: <a href="" title=""></a>

Packages optimized for very specific x86_64 "x" generation (OpenSUSE OBS / Fedora Koji)

As darktable co-maintainer, today I was speaking with darix from
OpenSUSE community, which maintains such package on that distro.
On their OBS build system, they are able to build various packages each
one optimized for a single x86_64 CPU generation using @BUILD_FLAVOR@ +
_multibuild file.[1] So for example they have packages

 darix also said "that is an OBS feature, nothing that you can just copy
to koji[...]"
"there is no generic solution to this for a normal distro package".

I would l

Suggestions for upgrading qdigidoc 3.x spec file to qdigidoc 4.x

Hi, I am going to start working on upgrading qdigidoc 3.x spec file[1],
in order making it compatible with the new (beta) qdigidoc 4.x [2].

I am not yet confident in creating spec files from the scratch, like
often happens with major updates, so I would like to ask you some
suggestions that come to your mind by quickly checking out [2] tree.

Best regards

[1]: <a href="" title=""></a>
[2]: <a href="" title=""></a>

QMake equivalent of CMake flag -DCMAKE_INSTALL_LIBDIR:PATH=%{_libdir}

Package firefox-pkcs11-loader[1] tries to install files under /usr/lib/
instead of %{_libdir}/
the problem has been solved using CMake flag

Package webextension-token-signing[2] is affected by the same problem,
but it uses QMake rather than CMake, so I am investing on how to
implement the same instruction.

%{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

During package firefox-pkcs11-loader build, the following two spec file

%dir %_prefix/%{_lib}/mozilla/pkcs11-modules/

and also this variant

%dir %{_libdir}/mozilla/pkcs11-modules/

lead to errors

Directory not found: /builddir/build/BUILDROOT/firefox-pkcs11-loader-3.13.0-2.fc27.x86_64/usr/lib64/mozilla/pkcs11-modules
File not found: /builddir/build/BUILDROOT/firefox-pkcs11-loader-3.13.0-2.fc27.x86_64/usr/lib64/mozilla/pkcs11-modules/onepinopenscpkcs11.json


Patching JSON tag without hardcoding library path (package firefox-pkcs11-loader)

<a href="" title=""></a>
(upstream) <a href="" title=""></a>

contains file
<a href="" title=""></a>
that has the tag
"path": ""

This tag is wrong and for example on x86_64 CPU architecture systems, it
must be
"path": "/usr/lib64/pkcs11/"

How could I patch this file without having to hardcode the /usr/lib64 path?

Thank you
Best regards

Help for fixing %install spec file section (Error make: *** No rule to make target 'install'. Stop.)

Hi there, I working on packaging the last missing (on Fedora repos)
piece of user side Estonia ID card software stack: the web extension[1]
for web signing
I need some help in fixing %install section of spec file
<a href="" title=""></a>
because during builds [2] I am getting error message

make: *** No rule to make target 'install'.

Packaging wiki: shortcoming in Github Source0 (?)

I think I have found a shortcoming in
<a href="" title=""></a>
Github line, which is
but I am not sure, so I have not made any edit to the wiki page.

In my case I am packaging bettercap-ng with the following attributes
commit eb1a53efa3171aefed0ec9766d8c5047bd0df289
shortcommit eb1a53e

rpmbuild parser will translate Source0 into
<a href="" title=""></a>
but if you try

Unretiring Estonia ID cards utilities

Good day,
I am unretiring packages for Estonia ID cards

Review request: qdigidoc - Estonian digital signature application
<a href="" title=""></a>

Review request: qesteidutil - Estonian ID card utility
<a href="" title=""></a>

Review request: libdigidocpp - Library offers creating, signing and
verification of digitally signed documents, according to XAdES and
XML-DSIG standards
<a href="" title=""></a>

Review request: esteidcerts - Estonian ID card root, intermediate and
OCSP certificates
<a href="https://bugzilla.redh" title="https://bugzilla.redh">https://bugzilla.redh</a>

compat-openssl10 and openssl conflict

I am working on unretiring Estonia ID Card utilities[1] and I noticed
that ‎ compat-openssl10 conflicts with openssl. In my case I am speaking
about ‎ compat-openssl10-devel and openssl-devel.

Concerning Beignet OpenCL driver stability

As darktable co-maintainer, I am getting a lot of crash reports related
to Beignet OpenCL driver (see below).

Preventing broken updates tree (packages downgrade) during release upgrades

There are many package maintainers who caused F25 packages being newer
than F26 packages, so during F25->F26 upgrade, dnf wanted to downgrade
them, for example packages quoted below.
I think that bodhi quality assurance should be improved to prevent such
events that break updates "tree"

expat i686
fedora 91 k
expat x86_64

Use industry-proven solution for XML routines

Fedora has a strong history of collaboration with upstream. A guy, Artem
Vorotnikov, is developing Volunode[1] a fork of boinc-client very
focused on improving Linux side of such software.

Security of confined user/application and access to video group

Hi there, I am the co-maintainer of boinc-client [1].
boinc-client runs as a service, and both it and its working units run as
'boinc' user and they are confined by SELinux.
Recently, I investigated to figure out why boinc-client, while running
as a service, could not detect videocard for GPU calculus. In order to
fix this problem I had to add Group=video to boinc-client systemd unit file.
I have not yet pushed such change to boinc-client Fedora git, because I
would like to ask you if this can cause a breach into boinc-client

Review swap: keepassxc - Cross-platform password manager

‎Hello, I am looking for a review swap: here is mine:
keepassxc - Cross-platform password manager
<a href="" title=""></a>

Fedora spins torrents statistics

As torrents seeder of certain Fedora spins, I would like to share some
upload statistics:
47.81 GB Fedora 25 KDE x86_64
29.40 GB Fedora 25 KDE i386
24.14 GB Fedora 25 Xfce i386
21.96 GB Fedora 25 Xfce x86_64
20.09 GB Fedora 25 LXDE x86_64
19.45 GB Fedora 25 LXDE i386

Torrents have been added on 25 November 2016

Best regards

ovirt status and ovirt alternatives

I have noticed that the most important ovirt packages have been orphaned
and/or retired, so ovirt user experience seems to be compromised. Was
that on purpose? What are some good alternatives?
Thank you very much

dracut-initqueue errors while using virt-install + kickstart file

I am trying to install a CentOS qemu/kvm virtual machine using a
virt-install script[1].
Since Anaconda text user interface does not permit to users to edit
filesystem type and mount points[2], I decided to use a kickstart file
to customize such settings. To create a kickstart file, I used a trick:
I installed a CentOS machine using Anaconda graphical user interface,
and I made all customizations I need, then when the installation has
been completed, I got the kickstart file (generated by Anaconda) in

IPFS and Fedora repositories

In past days I started playing with IPFS[1] "A peer-to-peer hypermedia
protocol to make the web faster, safer, and more open."
At [2] there is a very quick explanation about how IPFS works.
The Freenode IRC channel #ipfs has more than 1000 users, so there is a
great interest in it.
By reading some articles, I noticed a nice paragraph of article [3],
that made me wonder about IPFS usage on Fedora repositories:

Pinning Data to Save It

IPFS has a notion of pinning content onto your IPFS node.

upstream dev. asks suggestions about howto make packagers work easier (bundled libraries, etc.)

We often deal with upstream developers that bundle libraries in their
code, so to make a package we have to debundle them, etc.
This time, an upstream dev.

BOINC service does not write into log files

Hi, I am one of BOINC client maintainers.
I am trying to figure out why BOINC client 7.6.x does not write logs
inside /var/log/boinc{,_err}.log files so I started a very little thread
in BOINC forum [1], attaching boinc.service file and other stuff.

Reading guides about systemd's debugging, I decided to add
to boinc-client.service file, then I have runned:
# journalctl -u boinc-client
but nothing useful come out, only a few BOINC regular messages, instead
#journalctl -b _PID=28226
-- Logs begin at dom 2015-12-13 09:18:03 CET, end at sab 2016-05-21

Name of some Ruby "application" packages

Hi, I am studying Ruby packaging guidelines. I would need to know some
packages names that have been built following the "Applications" [1]
rules, in order to read their spec file and upstream sources tree.

Thank you for your time

<a href="" title=""></a>

Package presentation: python-netdiff

Hi, I would like to present you a package that has just been accepted to
be in Fedora repositories: python-netdiff.
Netdiff is a Python librarybased on networkxthat provides utilities for
parsing network topology formatsof open source dynamic
routing protocols (like OLSR [2], BATMAN [3]) and detecting changes in
these topologies.
It provides standard NetJSONNetworkGraph[4] output facilitating the
detection of changes in network topology (more infos at [1]).

Main contributors come from European wireless communities like
[5] [6] and [7]

Some examples of netdiff use are sof