January 2021 - openSUSE Packaging - openSUSE Mailing Lists

prmlint: hardlink-across-partition
by Axel Braun 18 Jan '21

18 Jan '21

Hi, I see suddenly rpmlint-error in TW (Leap builds fine): mygnuhealth.noarch: E: hardlink-across-partition (Badness: 10000) /usr/lib/ python3.8/site-packages/mygnuhealth/images/mygnuhealth.svg /usr/share/icons/ hicolor/scalable/apps/mygnuhealth.svg As nothing is changed compared to yesterday, my suspect is: # menu-entry desktop-file-install --dir %{buildroot}%{_datadir}/applications org.kde.mygnuhealth.desktop Side-effect of the new rpmlint? Cheers Axel

2 4

Rotate this between your ears to keep them clean
by Earwax Removal Tool 18 Jan '21

18 Jan '21

1 0

Rotate this between your ears to keep them clean
by Earwax Removal Tool 18 Jan '21

18 Jan '21

1 0

FW:RE:RE: Invoice -Bank Advice (PAID) TT0449871
by Account wect 17 Jan '21

17 Jan '21

1 0

Need help fix build fail for mint-x-icon-theme
by andythe_great 16 Jan '21

16 Jan '21

Hello, I need help fix build fail for mint-x-icon-theme. https://build.opensuse.org/package/show/X11:Cinnamon:Factory/mint-x-icon-th… I update it from version 1.5.5 to 1.5.9 which I did not change any macro except the version. The issue look like missing symbolic link. [ 24s] ERROR: link target doesn't exist (neither in build root nor in installed system): [ 24s] /usr/share/icons/Mint-X/apps/16/file-manager.png -> system-file-manager.png [ 24s] Add the package providing the target to BuildRequires and Requires Which I believe this macro have the issue, but I don't know how to fix it, because I did not write that macro. mkdir -p %{buildroot}%{_datadir}/icons/ ls .%{_datadir}/icons/ | while read icons; do sed -i 's/^$Inherits=$.*$/\1Adwaita/' .%{_datadir}/icons/$icons/index.theme cp -a .%{_datadir}/icons/$icons %{buildroot}%{_datadir}/icons/$icons # %%icon_theme_cache_create_ghost fails to work here. touch %{buildroot}%{_datadir}/icons/$icons/icon-theme.cache done Any ideas? Kind regards, Andy

4 5

PHP packaging changes
by Arjen de Korte 15 Jan '21

15 Jan '21

Dear fellow packagers, With PHP8 released a couple of weeks ago, you may have been wondering when it will be available in Factory. Good news: we're almost there. For the time being, we are going to provide both php7 and php8 packages. Due to some BC-breaking changes in PHP-8, it is expected that not all PHP packages will be able to migrate to PHP-8 yet. Therefor no automatic upgrade will be attempted. Notable change: the command-line binary will *not* be installed by default anymore when the base php7 or php8 packages are installed. Only if no sapi (mod_php, embed, fastcgi or fpm) is installed already, php-cli will be selected. So in order to guarantee the CLI is present, you need to explicitly (Build)Require (PHP version independent) 'php-cli' or '/usr/bin/php' or (PHP version dependent) 'php7-cli' or 'php8-cli' respectively. Note that only one of 'php7-cli' and 'php8-cli' can be used (due to hard-coded paths in the command-line binary /usr/bin/php). One thing that changed recently, is openssl support. We've build openssl as a shared module in PHP for years already, but until recently openssl happened to be built-in through mysqlnd (which was built-in). Now that has been fixed by building mysqlnd as a shared module as well, openssl will no longer be built-in. So if you need SSL support pretty much anywhere in PHP, you *must* require/install php-openssl. Last but not least: the base php7 and php8 packages theoretically can be installed side-by-side, as well as the 'mod_php' and 'embed' targets (and the shared PHP modules). In theory it should be possible to run multiple versions on the same system, but do note that in that case if you install (or require) shared PHP modules, you'll get the php8 version by default if you don't explicitly tell the system to use the php7 version. So although it is probably possible to run them side-by-side, it may give unexpected results and we don't recommend this. Best regards, Arjen de Korte

1 0

Question on rpm SPEC - file
by Dr.-Ing. Dieter Jurzitza 14 Jan '21

14 Jan '21

Dear listmembers, I am maintaining an application where I have to run two subsequent compilation processes to care for different screen resolutions. Now, here is my question: I have to apply a patch after the completion of th first compilation and after moving the first binary apart. Unfortunately I cannot do that from the very begin. There is a declaration Patch14: ABCD.patch but I cannot do a %patch14 in the %prep section because this would cause this patch to be effective from the start. Currently I am doing a patch -p0 < ../../SOURCES/ABCD.patch after the first build and after having moved the first binary away but within the %install section of the spec file. However I assume this is not the way it should be ... I mean, this works but I hope there is a more elegant way to get this done within the spec file. Any hints for me? Thank you very much, take care Dieter -- ----------------------------------------------------------- Dr.-Ing. Dieter Jurzitza 76131 Karlsruhe

6 11

Re: Revise Quotaion
by Nasr Koujan 14 Jan '21

14 Jan '21

1 0

drumstick-2.0.0
by Konstantin Voinov 11 Jan '21

11 Jan '21

Hi, I'd like to provide recently updated drumstick library among the other plcl's stuff: vmpk, kmidimon, kmetronome https://drumstick.sourceforge.io/ It builds fine and I have a question how the new version should be numbered, current version in openSUSE is the: libdrumstick-alsa1 libdrumstick-file1 libdrumstick-rt1 libdrumstick-rt-plugins libdrumstick-devel libdrumstick-doc with new version of SO I suppose to name it: libdrumstick-alsa2 libdrumstick-file2 libdrumstick-rt2 libdrumstick-rt2-plugins libdrumstick-widgets2 (new lib) libdrumstick-devel libdrumstick-doc or it should be named libdrumstick2-alsa libdrumstick2-file etc? I've read https://en.opensuse.org/openSUSE:Shared_library_packaging_policy but still not sure also there is the new plugin for QtCreator /usr/lib64/qt5/plugins/designer/libdrumstick-vpiano-plugin.so should it be placed inside the libdrumstick-devel or in separate package? I haven't find example of QtCreator plugin package. Thanks in advance.

2 1

file system on ppc64 worker broken?
by Bernhard Voelker 10 Jan '21

10 Jan '21

Hi *, I'm seeing such failures on PPC64 for a couple of days. According to a web search, the error message "Structure needs cleaning" indicates that the file system should be fsck'ed. Would anyone check, please? Have a nice day, Berny -------- Forwarded Message -------- Subject: Build failure of Base:System/coreutils in openSUSE_Factory_PowerPC/ppc64 Date: Sat, 09 Jan 2021 21:01:30 +0000 From: OBS Notification <admin(a)opensuse.org> To: Bernhard Voelker <mail(a)bernhard-voelker.de> Visit https://build.opensuse.org/package/live_build_log/Base:System/coreutils/ope… Package Base:System/coreutils failed to build in openSUSE_Factory_PowerPC/ppc64 Check out the package for editing: osc checkout Base:System coreutils Last lines of build log: [ 3s] rm: cannot remove 'build-preinstall/sbin/unix_chkpwd': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/sfdisk': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/fsck.minix': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/cfdisk': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/unix2_chkpwd': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/fstrim': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/faillock': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/unix_update': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/mkfs.bfs': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/switch_root': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/pwhistory_helper': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/chcpu': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/pam_timestamp_check': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/mkfs': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/pivot_root': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/mkhomedir_helper': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/swapoff': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/swaplabel': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/fsck': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/swapon': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/hwclock': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/findfs': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/mkfs.cramfs': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/mkfs.minix': Structure needs cleaning [ 3s] rm: cannot remove 'build-preinstall/sbin/losetup': Structure needs cleaning [ 3s] mkdir: cannot create directory 'build-preinstall': File exists [ 3s] [ 3s] obs-power8-05 failed "build coreutils.spec" at Sat Jan 9 21:01:15 UTC 2021. [ 3s] -- Configure notifications at https://build.opensuse.org/my/subscriptions openSUSE Build Service (https://build.opensuse.org/)

5 4