From glen at pld-linux.org Mon Aug 2 09:13:12 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Mon, 2 Aug 2021 10:13:12 +0300 Subject: coq-8.13.1-2.x86_64: capabilities will be splitted due to their size over 64KB Message-ID: <8c633eaa-36ab-d75c-b14f-b9a8a081ac90@pld-linux.org> poldek --up: coq-8.13.1-2.x86_64: capabilities will be splitted due to their size over 64KB coq-8.13.1-2.x86_64: capabilities will be splitted due to their size over 64KB coq-8.13.1-2.x86_64: capabilities will be splitted due to their size over 64KB From atler at pld-linux.org Thu Aug 12 10:54:29 2021 From: atler at pld-linux.org (Jan Palus) Date: Thu, 12 Aug 2021 10:54:29 +0200 Subject: TEST build ERRORS: gtk-webkit.spec In-Reply-To: References: <98926360-ddca-441d-9db9-c20bdef9e97e@pld.src.builder> Message-ID: <20210812085429.suh3a5t7noscs3wl@pine> On 12.08.2021 04:45, PLD th-x86_64 builder wrote: > gtk-webkit.spec (HEAD): FAILED ... > /usr/bin/ld: cannot find /usr/lib64/libXcomposite.so: Too many open files > /usr/bin/ld: cannot find /usr/lib64/libXdamage.so: Too many open files > /usr/bin/ld: cannot find /usr/lib64/libXfixes.so: Too many open files > /usr/bin/ld: cannot find /usr/lib64/libXrender.so: Too many open files > /usr/bin/ld: cannot find /usr/lib64/libXt.so: Too many open files > /usr/bin/ld: cannot find /usr/lib64/libSM.so: Too many open files > /usr/bin/ld: cannot find /usr/lib64/libuuid.so: Too many open files > /usr/bin/ld: cannot find /usr/lib64/libICE.so: Too many open files > /usr/bin/ld: cannot find /usr/lib64/libX11.so: Too many open files > /usr/bin/ld: cannot find /usr/lib64/libxcb.so: Too many open files > /usr/bin/ld: cannot find /usr/lib64/libXau.so: Too many open files > /usr/bin/ld: cannot find /usr/lib64/libXdmcp.so: Too many open files > /usr/bin/ld: cannot find -lbsd > /usr/bin/ld: cannot find -ldl > /usr/bin/ld: cannot find -lz > /usr/bin/ld: cannot find /usr/lib64/libstdc++.so: Too many open files > /usr/bin/ld: cannot find -lm > /usr/bin/ld: cannot find -lc > /usr/bin/ld: cannot find -lgcc_s > /usr/bin/ld: cannot find /usr/lib64/gcc/x86_64-pld-linux/11.2.0/crtendS.o: Too many open files > /usr/bin/ld: cannot find /usr/lib64/gcc/x86_64-pld-linux/11.2.0/../../../../lib64/crtn.o: Too many open files > collect2: error: ld returned 1 exit status > make[1]: *** [GNUmakefile:45096: libwebkitgtk-1.0.la] Error 1 > make[1]: Leaving directory '/tmp/B.C1fudw/BUILD/webkitgtk-2.4.11' > make: *** [GNUmakefile:30370: all] Error 2 > error: Bad exit status from /tmp/B.C1fudw/BUILD/tmp/rpm-tmp.w010mY (%build) Would it be possible to raise limit of opened file descriptors on builders? From baggins at pld-linux.org Thu Aug 12 23:47:18 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Thu, 12 Aug 2021 23:47:18 +0200 Subject: TEST build ERRORS: gtk-webkit.spec In-Reply-To: <20210812085429.suh3a5t7noscs3wl@pine> References: <98926360-ddca-441d-9db9-c20bdef9e97e@pld.src.builder> <20210812085429.suh3a5t7noscs3wl@pine> Message-ID: On Thu, 12 Aug 2021, Jan Palus wrote: > On 12.08.2021 04:45, PLD th-x86_64 builder wrote: > > gtk-webkit.spec (HEAD): FAILED > ... > > /usr/bin/ld: cannot find /usr/lib64/libXcomposite.so: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/libXdamage.so: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/libXfixes.so: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/libXrender.so: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/libXt.so: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/libSM.so: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/libuuid.so: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/libICE.so: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/libX11.so: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/libxcb.so: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/libXau.so: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/libXdmcp.so: Too many open files > > /usr/bin/ld: cannot find -lbsd > > /usr/bin/ld: cannot find -ldl > > /usr/bin/ld: cannot find -lz > > /usr/bin/ld: cannot find /usr/lib64/libstdc++.so: Too many open files > > /usr/bin/ld: cannot find -lm > > /usr/bin/ld: cannot find -lc > > /usr/bin/ld: cannot find -lgcc_s > > /usr/bin/ld: cannot find /usr/lib64/gcc/x86_64-pld-linux/11.2.0/crtendS.o: Too many open files > > /usr/bin/ld: cannot find /usr/lib64/gcc/x86_64-pld-linux/11.2.0/../../../../lib64/crtn.o: Too many open files > > collect2: error: ld returned 1 exit status > > make[1]: *** [GNUmakefile:45096: libwebkitgtk-1.0.la] Error 1 > > make[1]: Leaving directory '/tmp/B.C1fudw/BUILD/webkitgtk-2.4.11' > > make: *** [GNUmakefile:30370: all] Error 2 > > error: Bad exit status from /tmp/B.C1fudw/BUILD/tmp/rpm-tmp.w010mY (%build) > > Would it be possible to raise limit of opened file descriptors on > builders? Seems that 4k is the best that can be done. I sent gtk-webkit test build, let's see if that is enough. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From atler at pld-linux.org Fri Aug 13 10:44:59 2021 From: atler at pld-linux.org (Jan Palus) Date: Fri, 13 Aug 2021 10:44:59 +0200 Subject: TEST build ERRORS: gtk-webkit.spec In-Reply-To: References: <98926360-ddca-441d-9db9-c20bdef9e97e@pld.src.builder> <20210812085429.suh3a5t7noscs3wl@pine> Message-ID: <20210813084459.abfgi7ok5amog3az@pine> On 12.08.2021 23:47, Jan R?korajski wrote: > On Thu, 12 Aug 2021, Jan Palus wrote: > > > On 12.08.2021 04:45, PLD th-x86_64 builder wrote: > > > gtk-webkit.spec (HEAD): FAILED > > ... > > > /usr/bin/ld: cannot find /usr/lib64/libXcomposite.so: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/libXdamage.so: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/libXfixes.so: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/libXrender.so: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/libXt.so: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/libSM.so: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/libuuid.so: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/libICE.so: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/libX11.so: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/libxcb.so: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/libXau.so: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/libXdmcp.so: Too many open files > > > /usr/bin/ld: cannot find -lbsd > > > /usr/bin/ld: cannot find -ldl > > > /usr/bin/ld: cannot find -lz > > > /usr/bin/ld: cannot find /usr/lib64/libstdc++.so: Too many open files > > > /usr/bin/ld: cannot find -lm > > > /usr/bin/ld: cannot find -lc > > > /usr/bin/ld: cannot find -lgcc_s > > > /usr/bin/ld: cannot find /usr/lib64/gcc/x86_64-pld-linux/11.2.0/crtendS.o: Too many open files > > > /usr/bin/ld: cannot find /usr/lib64/gcc/x86_64-pld-linux/11.2.0/../../../../lib64/crtn.o: Too many open files > > > collect2: error: ld returned 1 exit status > > > make[1]: *** [GNUmakefile:45096: libwebkitgtk-1.0.la] Error 1 > > > make[1]: Leaving directory '/tmp/B.C1fudw/BUILD/webkitgtk-2.4.11' > > > make: *** [GNUmakefile:30370: all] Error 2 > > > error: Bad exit status from /tmp/B.C1fudw/BUILD/tmp/rpm-tmp.w010mY (%build) > > > > Would it be possible to raise limit of opened file descriptors on > > builders? > > Seems that 4k is the best that can be done. > I sent gtk-webkit test build, let's see if that is enough. Worked fine, thanks! From glen at pld-linux.org Sun Aug 15 15:10:52 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Sun, 15 Aug 2021 16:10:52 +0300 Subject: rpm 4.16 /etc/rpm/sysinfo/Requirename Message-ID: Does rpm 4.16 have equivalent of /etc/rpm/sysinfo/Requirename? it's used to prevent some package being uninstalled: - http://git.pld-linux.org/?p=packages/pld-builder.git;a=commitdiff;h=d37d3a926108b86a52d91a4c78f3bfb647b7b6a2 From ngompa13 at gmail.com Sun Aug 15 15:21:21 2021 From: ngompa13 at gmail.com (Neal Gompa) Date: Sun, 15 Aug 2021 09:21:21 -0400 Subject: rpm 4.16 /etc/rpm/sysinfo/Requirename In-Reply-To: References: Message-ID: On Sun, Aug 15, 2021 at 9:11 AM Elan Ruusam?e wrote: > > Does rpm 4.16 have equivalent of /etc/rpm/sysinfo/Requirename? > > it's used to prevent some package being uninstalled: > > - > http://git.pld-linux.org/?p=packages/pld-builder.git;a=commitdiff;h=d37d3a926108b86a52d91a4c78f3bfb647b7b6a2 > No, that's usually something implemented at the higher-level package manager. For example, DNF has a concept of protected packages and packages can install drop-in files to configure packages to be considered protected by default. -- ?????????/ Always, there's only one truth! From baggins at pld-linux.org Wed Aug 18 22:34:48 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Wed, 18 Aug 2021 22:34:48 +0200 Subject: qt4 broken on i686 Message-ID: New builds of qt4 on i686 exhibit crashes (ex. linguist in avogadro), or infinite looping (ex. meinproc4 in kde4-kig). I'm running out of ideas[1] and time to troubleshoot this and would appreciate if anyone would be willing to try and figure out WTF is broken there. [1] neither -O0, nor -std=gnu98 seem to do the trick, it could be a glibc 2.34 issue, but I don't have resources at hand to validate it. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From atler at pld-linux.org Thu Aug 19 09:30:57 2021 From: atler at pld-linux.org (Jan Palus) Date: Thu, 19 Aug 2021 09:30:57 +0200 Subject: BuildConflicts on builders Message-ID: <20210819073057.4hp3ul3p5sitmnbk@pine> Did http://git.pld-linux.org/?p=projects/pld-builder.new.git;a=commit;h=b2679a6 land on builders yet? If not would it be possible to deploy it? From baggins at pld-linux.org Thu Aug 19 20:08:26 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Thu, 19 Aug 2021 20:08:26 +0200 Subject: BuildConflicts on builders In-Reply-To: <20210819073057.4hp3ul3p5sitmnbk@pine> References: <20210819073057.4hp3ul3p5sitmnbk@pine> Message-ID: On Thu, 19 Aug 2021, Jan Palus wrote: > Did http://git.pld-linux.org/?p=projects/pld-builder.new.git;a=commit;h=b2679a6 > land on builders yet? If not would it be possible to deploy it? Done. -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From qboosh at pld-linux.org Thu Aug 19 21:09:32 2021 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Thu, 19 Aug 2021 21:09:32 +0200 Subject: qt4 broken on i686 In-Reply-To: References: Message-ID: <20210819190932.GA1671@mail> On Wed, Aug 18, 2021 at 10:34:48PM +0200, Jan R?korajski wrote: > New builds of qt4 on i686 exhibit crashes (ex. linguist in avogadro), or > infinite looping (ex. meinproc4 in kde4-kig). > > I'm running out of ideas[1] and time to troubleshoot this and would > appreciate if anyone would be willing to try and figure out WTF is > broken there. > > [1] neither -O0, nor -std=gnu98 seem to do the trick, it could be a > glibc 2.34 issue, but I don't have resources at hand to validate it. I don't know yet if it's related to glibc, gcc or binutils, but simple testcase is searching in empty QMap: ``` #include int main() { QMap mm; mm.constFind(999); } ``` It hangs even on carme-x86_64. Issue is probably related to shared_null static field (SIOF?) -- Jakub Bogusz http://qboosh.pl/ From krzysztof at mrozowicz.eu Fri Aug 20 10:01:50 2021 From: krzysztof at mrozowicz.eu (Krzysztof Mrozowicz) Date: Fri, 20 Aug 2021 09:01:50 +0100 Subject: kodi rebuild error Message-ID: <20210820090150.54373193@oko> Hi, I updated libfmt which caused a need to rebuild few other packages. When I'm trying to rebuild kodi, I'm getting: rpm: error: Failed build dependencies: rpm: squish-devel conflicts with kodi-18.4-5.x86_64 What should I do in this situation? I believe squish-devel needs to be uninstalled from builders, but how can I do it? Best Regards -- Krzysiek From baggins at pld-linux.org Fri Aug 20 10:57:18 2021 From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=) Date: Fri, 20 Aug 2021 10:57:18 +0200 Subject: kodi rebuild error In-Reply-To: <20210820090150.54373193@oko> References: <20210820090150.54373193@oko> Message-ID: On Fri, 20 Aug 2021, Krzysztof Mrozowicz via pld-devel-en wrote: > Hi, > I updated libfmt which caused a need to rebuild few other packages. > When I'm trying to rebuild kodi, I'm getting: > > rpm: error: Failed build dependencies: > rpm: squish-devel conflicts with kodi-18.4-5.x86_64 > > What should I do in this situation? I believe squish-devel needs to be > uninstalled from builders, but how can I do it? This should get uninstalled automatically, you hit a builder bug. Fixed now: http://buildlogs.pld-linux.org//index.php?dist=th&arch=x86_64&ok=0&name=kodi&id=77157a1d-2efb-4149-acc0-4e7d2515e3ea&action=tail -- Jan R?korajski | PLD/Linux SysAdm | bagginspld-linux.org | http://www.pld-linux.org/ From krzysztof at mrozowicz.eu Sun Aug 22 15:24:55 2021 From: krzysztof at mrozowicz.eu (Krzysztof Mrozowicz) Date: Sun, 22 Aug 2021 14:24:55 +0100 Subject: kodi rebuild error In-Reply-To: References: <20210820090150.54373193@oko> Message-ID: <20210822142455.72075de1@oko> Dnia 2021-08-20, o godz. 10:57:18 Jan R?korajski napisa?(a): > This should get uninstalled automatically, you hit a builder bug. > > Fixed now: > > http://buildlogs.pld-linux.org//index.php?dist=th&arch=x86_64&ok=0&name=kodi&id=77157a1d-2efb-4149-acc0-4e7d2515e3ea&action=tail > Hi, I'm afraid the problem is not fully fixed. https://buildlogs.pld-linux.org//index.php?dist=th&arch=x86_64&ok=0&name=ka5-akonadi-contacts&id=d80de448-2986-458a-b920-ed5817be348b&action=tail Regards -- Krzysiek From glen at pld-linux.org Mon Aug 23 07:03:22 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Mon, 23 Aug 2021 08:03:22 +0300 Subject: kodi rebuild error In-Reply-To: <20210822142455.72075de1@oko> References: <20210820090150.54373193@oko> <20210822142455.72075de1@oko> Message-ID: On 22.08.2021 16:24, Krzysztof Mrozowicz via pld-devel-en wrote: > Dnia 2021-08-20, o godz. 10:57:18 > Jan R?korajski napisa?(a): > >> This should get uninstalled automatically, you hit a builder bug. >> >> Fixed now: >> >> http://buildlogs.pld-linux.org//index.php?dist=th&arch=x86_64&ok=0&name=kodi&id=77157a1d-2efb-4149-acc0-4e7d2515e3ea&action=tail >> > Hi, I'm afraid the problem is not fully fixed. > > https://buildlogs.pld-linux.org//index.php?dist=th&arch=x86_64&ok=0&name=ka5-akonadi-contacts&id=d80de448-2986-458a-b920-ed5817be348b&action=tail that's different problem, even different package (so you should created new thread, nothing related to kodi here) there's no buildconflicts in the package you linked: -http://git.pld-linux.org/?p=packages/ka5-akonadi-contacts.git;a=blob;f=ka5-akonadi-contacts.spec;h=d8cf179c8ff8b482c616217aedf5ca9c4a1e552b;hb=d4a0802983bd4e7c8daeb540861aea999472964a your install conflict appears due packages chosen for install produce file conflicts (files with different checksum belong to two packages) From krzysztof at mrozowicz.eu Mon Aug 23 08:36:36 2021 From: krzysztof at mrozowicz.eu (Krzysztof Mrozowicz) Date: Mon, 23 Aug 2021 07:36:36 +0100 Subject: kodi rebuild error In-Reply-To: References: <20210820090150.54373193@oko> <20210822142455.72075de1@oko> Message-ID: <20210823073636.41aa06cd@oko> Dnia 2021-08-23, o godz. 08:03:22 Elan Ruusam?e napisa?(a): > > Hi, I'm afraid the problem is not fully fixed. > > > > https://buildlogs.pld-linux.org//index.php?dist=th&arch=x86_64&ok=0&name=ka5-akonadi-contacts&id=d80de448-2986-458a-b920-ed5817be348b&action=tail > > > > that's different problem, even different package (so you should > created new thread, nothing related to kodi here) > > there's no buildconflicts in the package you linked: > > -http://git.pld-linux.org/?p=packages/ka5-akonadi-contacts.git;a=blob;f=ka5-akonadi-contacts.spec;h=d8cf179c8ff8b482c616217aedf5ca9c4a1e552b;hb=d4a0802983bd4e7c8daeb540861aea999472964a > > your install conflict appears due packages chosen for install produce > file conflicts (files with different checksum belong to two packages) My problem with kodi was in fact a problem with builders not being able (or not even trying) to uninstall packages conflicting with build requirements. And I think I hit the same problem again when installed akonadi-libs prevents installation of ka5-akonadi and the builder is not trying to uninstall akonadi-libs to make room for ka5-akonadi. That's why I used the same thread. If I'm wrong about the reason why ka5-akonadi-contacts doesn't want to build, please correct me. Best Regards -- Krzysiek From zawadaa at gmail.com Mon Aug 23 10:53:11 2021 From: zawadaa at gmail.com (Andrzej Zawadzki) Date: Mon, 23 Aug 2021 10:53:11 +0200 Subject: git with vim Message-ID: Hi! I don't since when exactly but recently I notice: $ git commit -a hint: Waiting for your editor to close the file... Vim: Caught deadly signal FPE Vim: Finished. error: vi died of signal 8 error: There was a problem with the editor 'vi'. Please supply the message using either -m or -F option. glibc? After change editor, for example to mcedit everything works. Alone VIM works too. -- Andrzej Zawadzki From glen at pld-linux.org Mon Aug 23 19:49:06 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Mon, 23 Aug 2021 20:49:06 +0300 Subject: ka5-akonadi-contacts file-conflicts (was Re: kodi rebuild error) In-Reply-To: <20210823073636.41aa06cd@oko> References: <20210820090150.54373193@oko> <20210822142455.72075de1@oko> <20210823073636.41aa06cd@oko> Message-ID: <11cdf9cc-7492-5de7-6b76-b0f0308fd308@pld-linux.org> On 23.08.2021 09:36, Krzysztof Mrozowicz via pld-devel-en wrote: > Dnia 2021-08-23, o godz. 08:03:22 > Elan Ruusam?e napisa?(a): > >>> Hi, I'm afraid the problem is not fully fixed. >>> >>> https://buildlogs.pld-linux.org//index.php?dist=th&arch=x86_64&ok=0&name=ka5-akonadi-contacts&id=d80de448-2986-458a-b920-ed5817be348b&action=tail >>> [snip] >>> there's no buildconflicts in the package you linked: >>> >>> -http://git.pld-linux.org/?p=packages/ka5-akonadi-contacts.git;a=blob;f=ka5-akonadi-contacts.spec;h=d8cf179c8ff8b482c616217aedf5ca9c4a1e552b;hb=d4a0802983bd4e7c8daeb540861aea999472964a >>> >>> your install conflict appears due packages chosen for install produce >>> file conflicts (files with different checksum belong to two packages) [snip] >> If I'm wrong about the reason why ka5-akonadi-contacts doesn't want to >> build, please correct me. i already corrected you, you have no buildconflicts: akionadi-libs in your spec ps: if you don't do interleaved replies, you may as well do top post! [1] [1]: https://en.wikipedia.org/wiki/Posting_style From glen at pld-linux.org Tue Aug 24 12:19:17 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 24 Aug 2021 13:19:17 +0300 Subject: Empty %files file Message-ID: <7741f0b9-049c-ffac-02f8-0172d614622f@pld-linux.org> error: Empty %files file /home/users/glen/rpm/packages/BUILD.x86_64-linux/zabbix-5.4.3/debugsourcefiles.list is this something specific to carme? and how to prevent the error and proceed? From glen at pld-linux.org Tue Aug 24 14:12:32 2021 From: glen at pld-linux.org (=?UTF-8?Q?Elan_Ruusam=c3=a4e?=) Date: Tue, 24 Aug 2021 15:12:32 +0300 Subject: rpmlib(ShortCircuited) Message-ID: <8920b93c-a787-1638-e128-28d08530dc20@pld-linux.org> https://www.pld-linux.org/packages/rpm#spec_development * rpm.org rpm generates|rpmlib(ShortCircuited)|dependencies when package is build using|--short-circuit|option. To disable that add|%disable_short_circuited_deps 1|to ~/.rpmmacros # rpm -Uhv /home/users/glen/rpm/packages/RPMS/zabbix-common-5.4.3-0.1.x86_64.rpm error: Failed dependencies: ??????? rpmlib(ShortCircuited) <= 4.9.0-1 is needed by zabbix-common-5.4.3-0.1.x86_64 this does not seem to work, can't even find matching such macro: $ grep -r short_circuited_deps /usr/lib/rpm|wc -l 0 From ngompa13 at gmail.com Tue Aug 24 17:30:43 2021 From: ngompa13 at gmail.com (Neal Gompa) Date: Tue, 24 Aug 2021 11:30:43 -0400 Subject: Empty %files file In-Reply-To: <7741f0b9-049c-ffac-02f8-0172d614622f@pld-linux.org> References: <7741f0b9-049c-ffac-02f8-0172d614622f@pld-linux.org> Message-ID: On Tue, Aug 24, 2021 at 6:19 AM Elan Ruusam?e wrote: > > > error: Empty %files file > /home/users/glen/rpm/packages/BUILD.x86_64-linux/zabbix-5.4.3/debugsourcefiles.list > > is this something specific to carme? > > > and how to prevent the error and proceed? > That happens when your compilation flags aren't being respected and debuginfo isn't getting built properly for -debuginfo and -debugsource subpackages to be generated. -- ?????????/ Always, there's only one truth! From qboosh at pld-linux.org Tue Aug 24 17:59:01 2021 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Tue, 24 Aug 2021 17:59:01 +0200 Subject: Empty %files file In-Reply-To: References: <7741f0b9-049c-ffac-02f8-0172d614622f@pld-linux.org> Message-ID: <20210824155901.GA8159@mail> On Tue, Aug 24, 2021 at 11:30:43AM -0400, Neal Gompa wrote: > On Tue, Aug 24, 2021 at 6:19 AM Elan Ruusam?e wrote: > > > > > > error: Empty %files file > > /home/users/glen/rpm/packages/BUILD.x86_64-linux/zabbix-5.4.3/debugsourcefiles.list > > > > is this something specific to carme? > > > > > > and how to prevent the error and proceed? > > > > That happens when your compilation flags aren't being respected and > debuginfo isn't getting built properly for -debuginfo and -debugsource > subpackages to be generated. Explaining further: - if binary packages don't contain any native code (just scripts, data or some bytecode), then -debuginfo is empty (and solution is to set _enable_debug_packages to 0) - if there is some native code, -debuginfo is created - if there is no enough debug information, -debugsource packages are not created; the reason can be lack of compiler/linker flags (or binary stripping in %install stage), but also if binaries are created by compiler not supported by rpm debuginfo machinery (like golang or rust); in the last case, solution is to disable debugsource packages (define _debugsource_packages to 0); in other case, solution is to properly pass compiler flags or disable stripping in build system -- Jakub Bogusz http://qboosh.pl/ From qboosh at pld-linux.org Tue Aug 24 18:01:26 2021 From: qboosh at pld-linux.org (Jakub Bogusz) Date: Tue, 24 Aug 2021 18:01:26 +0200 Subject: rpmlib(ShortCircuited) In-Reply-To: <8920b93c-a787-1638-e128-28d08530dc20@pld-linux.org> References: <8920b93c-a787-1638-e128-28d08530dc20@pld-linux.org> Message-ID: <20210824160126.GB8159@mail> On Tue, Aug 24, 2021 at 03:12:32PM +0300, Elan Ruusam?e wrote: > https://www.pld-linux.org/packages/rpm#spec_development > > * > rpm.org rpm generates|rpmlib(ShortCircuited)|dependencies when > package is build using|--short-circuit|option. To disable that > add|%disable_short_circuited_deps 1|to ~/.rpmmacros > > > # rpm -Uhv > /home/users/glen/rpm/packages/RPMS/zabbix-common-5.4.3-0.1.x86_64.rpm > error: Failed dependencies: > ??????? rpmlib(ShortCircuited) <= 4.9.0-1 is needed by > zabbix-common-5.4.3-0.1.x86_64 > > > this does not seem to work, can't even find matching such macro: > > $ grep -r short_circuited_deps /usr/lib/rpm|wc -l > 0 I suppose it needs to be set at the time of creating .rpm file, not installing it. Test exist in (patched) rpm code, not external macros: rpm/shortcircuited-deps.patch:+ (rc = packageBinaries(spec, cookie, ((didBuild == 0) && !rpmExpandNumeric("%{?disable_short_circuited_deps}"))))) -- Jakub Bogusz http://qboosh.pl/ From ngompa13 at gmail.com Tue Aug 24 18:01:20 2021 From: ngompa13 at gmail.com (Neal Gompa) Date: Tue, 24 Aug 2021 12:01:20 -0400 Subject: Empty %files file In-Reply-To: <20210824155901.GA8159@mail> References: <7741f0b9-049c-ffac-02f8-0172d614622f@pld-linux.org> <20210824155901.GA8159@mail> Message-ID: On Tue, Aug 24, 2021 at 11:59 AM Jakub Bogusz wrote: > > On Tue, Aug 24, 2021 at 11:30:43AM -0400, Neal Gompa wrote: > > On Tue, Aug 24, 2021 at 6:19 AM Elan Ruusam?e wrote: > > > > > > > > > error: Empty %files file > > > /home/users/glen/rpm/packages/BUILD.x86_64-linux/zabbix-5.4.3/debugsourcefiles.list > > > > > > is this something specific to carme? > > > > > > > > > and how to prevent the error and proceed? > > > > > > > That happens when your compilation flags aren't being respected and > > debuginfo isn't getting built properly for -debuginfo and -debugsource > > subpackages to be generated. > > Explaining further: > > - if binary packages don't contain any native code (just scripts, data or some > bytecode), then -debuginfo is empty (and solution is to set > _enable_debug_packages to 0) > > - if there is some native code, -debuginfo is created > > - if there is no enough debug information, -debugsource packages are not > created; the reason can be lack of compiler/linker flags (or binary > stripping in %install stage), but also if binaries are created by > compiler not supported by rpm debuginfo machinery (like golang or > rust); in the last case, solution is to disable debugsource packages > (define _debugsource_packages to 0); in other case, solution is to > properly pass compiler flags or disable stripping in build system > Both Rust and Go are supported by RPM debuginfo machinery, it's just not done by default unless you pass flags for it. In Fedora, for example, those flags are set, so those things do work. If there is no native code, then BuildArch: noarch should be set, which turns off debuginfo stuff too. -- ?????????/ Always, there's only one truth!