Mailinglist Archive: opensuse-packaging (31 mails)

< Previous Next >
Re: [opensuse-packaging] Problem packaging icon file
    I aggree with you "cp is not ln"... But fdupes detects when there
are identical files in your package and it hardlinks them, as shown in
the log file.

[ 94s] + dupes -q -p -n -H -o name -r
[ 94s] + test -z
[ 94s] + test 0 = 1
[ 94s] + ln -f


    I think including icons in the python library path is a bad practice
and you should avoid it. However, if you really need it, I do not know
how to solve the problem (tune fdupes check? modify rpmlintrc?). I hope
this helps.
    Best regards,

Le 13/09/2019 à 19:30, Axel Braun a écrit :

I'm currently building a python 3 program, that will create a desktop file
entry. The samepackaging sequence as for the python 2.7 does - surprisingly -
not work.

What I do:
# menu-entry
desktop-file-install --dir %{buildroot}%{_datadir}/applications %
%suse_update_desktop_file %{name}

mkdir -p %{buildroot}%{_datadir}/pixmaps
cp tryton/data/pixmaps/tryton/gnuhealth-icon.png %{buildroot}%{_datadir}/

That works *but* the rpm check moans about:

gnuhealth-client.noarch: E: hardlink-across-partition (Badness: 10000) /usr/
lib/python3.6/site-packages/tryton/data/pixmaps/tryton/gnuhealth-icon.png /
[ 12s] Your package contains two files that are apparently hardlinked and
that are
[ 12s] likely on different partitions. Installation of such an RPM will fail
due to
[ 12s] RPM being unable to unpack the hardlink. do not hardlink across the
first two
[ 12s] levels of a path, e.g. between /srv/ftp and /srv/www or /etc and /

This is kinda strange - cp is not ln, no?
Any ideas?


To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups