From davidnchmelik at gmail.com Fri Jul 2 08:58:12 2021 From: davidnchmelik at gmail.com (David Chmelik) Date: Fri, 2 Jul 2021 01:58:12 -0700 Subject: [Slackbuilds-users] Moria Message-ID: <1fc41477-b552-4e99-f9f7-18103f02cdfc@gmail.com> A SlackBuild I maintain, moria, no longer has a project/source_code homepage; the maintainer's (David Grabiner) homepage disappeared.? I think he's on LinkedIn.com in New York (and went to Brown University in mathematics/computing) but it won't let me contact him.? Is anyone able to contact him, or if not, what should I do?? Eventually I plan to replace moria with colour moria, but that needs some bugfixes (which I have opened bug reports) before it will even compile... --David From dchmelik at gmail.com Fri Jul 2 08:59:13 2021 From: dchmelik at gmail.com (David Chmelik) Date: Fri, 2 Jul 2021 01:59:13 -0700 Subject: [Slackbuilds-users] Moria Message-ID: A SlackBuild I maintain, moria, no longer has a project/source_code homepage; the maintainer's (David Grabiner) homepage disappeared.? I think he's on LinkedIn.com in New York (and went to Brown University in mathematics/computing) but it won't let me contact him.? Is anyone able to contact him, or if not, what should I do?? Eventually I plan to replace moria with colour moria, but that needs some bugfixes (which I have opened bug reports) before it will even compile... --David -- Sincerely, David homesite mirror (most uptime) homesite (updated first) IRC Diaspora Social GNU Social FB Twitter Goodreads Academia LinkedIn Flickr Pinterest Ebay LiberaPay.com Patreon Buy Me A Coffee Flattr Zazzle Ko-fi SBo Pouet BitFellas deviantART ElfTown ArtCity Internet Archive ModLand Trax in Space Scenestream ModArchive You can ask how to make graphical link signatures. From kingbeowulf at gmail.com Sun Jul 4 01:15:48 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 3 Jul 2021 18:15:48 -0700 Subject: [Slackbuilds-users] Moria In-Reply-To: References: Message-ID: <2763fd65-6a04-0de8-56f7-05d10869721c@gmail.com> On 7/2/21 1:59 AM, David Chmelik wrote: > A SlackBuild I maintain, moria, no longer has a project/source_code > homepage; the maintainer's (David Grabiner) homepage disappeared.? I > think he's on LinkedIn.com in New York (and went to Brown University in > mathematics/computing) but it won't let me contact him.? Is anyone able > to contact him, or if not, what should I do?? Eventually I plan to > replace moria with colour moria, but that needs some bugfixes (which I > have opened bug reports) before it will even compile... > --David > If it's umoria (The Dungeons of Moria) wouldn't it be now here: https://umoria.org/ https://github.com/dungeons-of-moria/umoria Seems this is where moria now resides, based on the readme and historical section. -kb -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From davidnchmelik at gmail.com Sun Jul 4 02:53:31 2021 From: davidnchmelik at gmail.com (David Chmelik) Date: Sat, 3 Jul 2021 19:53:31 -0700 Subject: [Slackbuilds-users] Moria In-Reply-To: <2763fd65-6a04-0de8-56f7-05d10869721c@gmail.com> References: <2763fd65-6a04-0de8-56f7-05d10869721c@gmail.com> Message-ID: <444c66b2-86bd-ea7a-ee0f-4dc09013d2c7@gmail.com> On 7/3/21 6:15 PM, King Beowulf wrote: > On 7/2/21 1:59 AM, David Chmelik wrote: >> A SlackBuild I maintain, moria, no longer has a project/source_code >> homepage; the maintainer's (David Grabiner) homepage disappeared.? I >> think he's on LinkedIn.com in New York (and went to Brown University in >> mathematics/computing) but it won't let me contact him.? Is anyone able >> to contact him, or if not, what should I do?? Eventually I plan to >> replace moria with colour moria, but that needs some bugfixes (which I >> have opened bug reports) before it will even compile... >> --David >> > If it's umoria (The Dungeons of Moria) wouldn't it be now here: > > https://umoria.org/ > https://github.com/dungeons-of-moria/umoria > > Seems this is where moria now resides, based on the readme and > historical section. > > -kb No; that's unofficial, and actually a fork. From willysr at slackbuilds.org Mon Jul 5 09:11:25 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 5 Jul 2021 16:11:25 +0700 Subject: [Slackbuilds-users] SlackBuilds Template Changes Message-ID: <6111f086-92f1-afb1-550e-fb2afa7ac208@slackbuilds.org> Hi everyone We just want to update with the progress we have been doing in the last few weeks as well some changes that is happening during this development cycle. First, we have finished first batch of Python2/3 transition and hopefully we didn't miss anything. There will be some exceptions here and there but we will try to make as consistent as possible. Second, there has been some changes in the default templates. At this point, the changes are in template's master branch which can be seen here: https://git.slackbuilds.org/templates/log/. These change were ported from Slackware main tree. There is one last change that hasn't been merged into SBo master branch and that work in progress is still being reviewed but it can be seen in this branch (https://git.slackbuilds.org/slackbuilds/log/?h=user/pprkut/template-changes) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From sb at rbn.im Mon Jul 5 10:12:04 2021 From: sb at rbn.im (Ruben Schuller) Date: Mon, 5 Jul 2021 12:12:04 +0200 Subject: [Slackbuilds-users] rc scripts with -current Message-ID: <20210705121204.25a5e52d@kiwi.kuchen> hi! i'm not sure if this observation is correct (or already was discussed here), but rc scripts may have to be modified for -current as /var/run isn't persistent anymore. a tmpfs is mounted to /run and this in turn is bind mounted to /var/run in rc.S: # If /run exists, mount a tmpfs on it (unless the # initrd has already done so): if [ -d /run ]; then if ! grep -wq "tmpfs /run tmpfs" /proc/mounts ; then /sbin/mount -v -n -t tmpfs tmpfs /run -o mode=0755,size=32M,nodev,nosuid,noexec fi # Make sure that mounts below /run are visible in both /run and /var/run: /sbin/mount --make-shared /run fi and # Bind mount /run to /var/run: mount -o bind /run /var/run the rc scripts of daemons included in slackware have been changed accordingly, e.g. rc.bind: bind_start() { # Make sure /var/run/named exists: mkdir -p /var/run/named some programs may create their directory themselves (like mariadb seems to do), others will complain on startup if it doesn't exist. in any case, installing /var/run/$name via a package is lost after reboot. i think it usually is enough to just create the directory like it's done in rc.bind. cheers ruben From dickson.tim at googlemail.com Mon Jul 5 10:16:40 2021 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 5 Jul 2021 11:16:40 +0100 Subject: [Slackbuilds-users] rEFInd not building Message-ID: <715ac0dd-164b-49dc-9d10-71a1c05526ad@googlemail.com> rEFInd fails to build on 14.2 with all updates. (for me) it gets stuck trying to create install.o in file included from /usr/include/efi/efi.h:35:0, ??? from gloabl.h:49, ??? from install.c:13: install.c: In function 'RenameFile': install.c:176:43: error: 'gEfiFileInfoGuid' undeclared (first use in this function) ??? &gEfiFileInfoGuid, ???? ^ there's more error stuff. if it helps. Has anyone else tried it recently and had success?. (refind (the repackaged binary) is ok. ) regards, Tim -- This email has been checked for viruses by AVG. https://www.avg.com From duncan_roe at optusnet.com.au Mon Jul 5 11:11:18 2021 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Mon, 5 Jul 2021 21:11:18 +1000 Subject: [Slackbuilds-users] SlackBuilds Template Changes In-Reply-To: <6111f086-92f1-afb1-550e-fb2afa7ac208@slackbuilds.org> References: <6111f086-92f1-afb1-550e-fb2afa7ac208@slackbuilds.org> Message-ID: <20210705111118.GN4147@dimstar.local.net> Hi Heinz, On Mon, Jul 05, 2021 at 04:11:25PM +0700, Willy Sudiarto Raharjo wrote: > Hi everyone > > We just want to update with the progress we have been doing in the last > few weeks as well some changes that is happening during this development > cycle. > > First, we have finished first batch of Python2/3 transition and > hopefully we didn't miss anything. There will be some exceptions here > and there but we will try to make as consistent as possible. > > Second, there has been some changes in the default templates. At this > point, the changes are in template's master branch which can be seen > here: https://git.slackbuilds.org/templates/log/. These change were > ported from Slackware main tree. There is one last change that hasn't > been merged into SBo master branch and that work in progress is still > being reviewed but it can be seen in this branch > (https://git.slackbuilds.org/slackbuilds/log/?h=user/pprkut/template-changes) > > > -- > Willy Sudiarto Raharjo > With reference to your templates commit bab9e3ed89a5, *please* consider '#!/bin/bash -p' in place of '#!/bin/bash'. Without -p, a script will import all exported command functions. This can cause unpredictable results when a function has the name of a command the script uses. I can submit a patch if you would like, Cheers ... Duncan. From yalhcru at gmail.com Mon Jul 5 15:34:42 2021 From: yalhcru at gmail.com (B Watson) Date: Mon, 5 Jul 2021 11:34:42 -0400 Subject: [Slackbuilds-users] Moria In-Reply-To: References: Message-ID: On 7/2/21, David Chmelik wrote: > A SlackBuild I maintain, moria, no longer has a project/source_code > homepage; the maintainer's (David Grabiner) homepage disappeared. Search for the URL on https://web.archive.org. I found this: http://web.archive.org/web/20201130032145/http://www.remarque.org/~grabiner/moria.html ...which will serve as HOMEPAGE until you eventually replace moria with one of the forks you mentioned (color moria). From yalhcru at gmail.com Mon Jul 5 15:52:04 2021 From: yalhcru at gmail.com (B Watson) Date: Mon, 5 Jul 2021 11:52:04 -0400 Subject: [Slackbuilds-users] rEFInd not building In-Reply-To: <715ac0dd-164b-49dc-9d10-71a1c05526ad@googlemail.com> References: <715ac0dd-164b-49dc-9d10-71a1c05526ad@googlemail.com> Message-ID: On 7/5/21, Tim Dickson via SlackBuilds-users wrote: > rEFInd fails to build on 14.2 with all updates. (for me) > it gets stuck trying to create install.o > install.c:176:43: error: 'gEfiFileInfoGuid' undeclared (first use in > this function) > &gEfiFileInfoGuid, I can confirm, I get the same error. From zhu.qunying at gmail.com Wed Jul 7 00:52:27 2021 From: zhu.qunying at gmail.com (Qun-Ying) Date: Tue, 6 Jul 2021 17:52:27 -0700 Subject: [Slackbuilds-users] rEFInd not building In-Reply-To: References: <715ac0dd-164b-49dc-9d10-71a1c05526ad@googlemail.com> Message-ID: gEfiFileInfoGuid is not in the gnu-efi package in 14.2, you may need to use the source of gnu-efi source package to compile the latest one for 14.2 to compile rEFInd. On 7/5/21, B Watson wrote: > On 7/5/21, Tim Dickson via SlackBuilds-users > wrote: >> rEFInd fails to build on 14.2 with all updates. (for me) >> it gets stuck trying to create install.o > >> install.c:176:43: error: 'gEfiFileInfoGuid' undeclared (first use in >> this function) >> &gEfiFileInfoGuid, > > I can confirm, I get the same error. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- Qun-Ying From lenardrspencer at gmail.com Thu Jul 8 15:26:16 2021 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Thu, 8 Jul 2021 11:26:16 -0400 Subject: [Slackbuilds-users] SlackBuilds Template Changes In-Reply-To: <6111f086-92f1-afb1-550e-fb2afa7ac208@slackbuilds.org> References: <6111f086-92f1-afb1-550e-fb2afa7ac208@slackbuilds.org> Message-ID: We probably should add a douninst.sh file to the templates as well. Something like, # douninst.sh # # uninstall script for Slackware >= 15.0 # # NOTE: This script is run AFTER package removal, so be careful! On Mon, Jul 5, 2021 at 5:11 AM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Hi everyone > > We just want to update with the progress we have been doing in the last > few weeks as well some changes that is happening during this development > cycle. > > First, we have finished first batch of Python2/3 transition and > hopefully we didn't miss anything. There will be some exceptions here > and there but we will try to make as consistent as possible. > > Second, there has been some changes in the default templates. At this > point, the changes are in template's master branch which can be seen > here: https://git.slackbuilds.org/templates/log/. These change were > ported from Slackware main tree. There is one last change that hasn't > been merged into SBo master branch and that work in progress is still > being reviewed but it can be seen in this branch > ( > https://git.slackbuilds.org/slackbuilds/log/?h=user/pprkut/template-changes > ) > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From duncan_roe at optusnet.com.au Wed Jul 14 00:06:23 2021 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Wed, 14 Jul 2021 10:06:23 +1000 Subject: [Slackbuilds-users] SlackBuilds Template Changes In-Reply-To: References: <6111f086-92f1-afb1-550e-fb2afa7ac208@slackbuilds.org> <20210705111118.GN4147@dimstar.local.net> Message-ID: <20210714000623.GA10281@dimstar.local.net> On Mon, Jul 12, 2021 at 09:38:51PM -0500, Erik Hanson wrote: > On 7/5/21 6:11 AM, Duncan Roe wrote: > > > With reference to your templates commit bab9e3ed89a5, *please* consider > > '#!/bin/bash -p' in place of '#!/bin/bash'. > > > > Without -p, a script will import all exported command functions. This can cause > > unpredictable results when a function has the name of a command the script uses. > > Do you have an example use-case for this being an issue? SlackBuild > scripts are not intended to be run from a setuid program, in fact we > expect them to be run as root, so I don't see the implications here. > /root/.bashrc -> /home/dunc/.bashrc on my system. Similarly /root/.profile. Perhaps that's unusual, but I'm not about to stop doing it. At the moment I don't export any functions, but am tempted from time to time. E.g. colon is normally a builtin but I have :() { cd "../$1"; } Cheers ... Duncan. From 1.41421 at gmail.com Wed Jul 14 00:50:55 2021 From: 1.41421 at gmail.com (Luveh Keraph) Date: Tue, 13 Jul 2021 18:50:55 -0600 Subject: [Slackbuilds-users] Will there be further 14.2 updates? Message-ID: I notice that ever since (roughly) shortly after the time slackware-current was explicitly labeled as 15.0 alpha, no further updates to 14.2 Slackbuilds packages have been pushed. Does this mean that 14.2 Slackbuilds packages will not be updated any more? -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex at dcclost.com Wed Jul 14 07:10:42 2021 From: alex at dcclost.com (Alexander Grotewohl) Date: Wed, 14 Jul 2021 07:10:42 +0000 Subject: [Slackbuilds-users] Will there be further 14.2 updates? In-Reply-To: References: Message-ID: I believe they're just locked for now so they aren't moving targets. But I'd guess it's up to the maintainers of individual slackbuilds.. -- Alexander Grotewohl https://dcclost.com ________________________________ From: SlackBuilds-users on behalf of Luveh Keraph <1.41421 at gmail.com> Sent: Tuesday, July 13, 2021 8:50:55 PM To: SlackBuilds.org Users List Subject: [Slackbuilds-users] Will there be further 14.2 updates? I notice that ever since (roughly) shortly after the time slackware-current was explicitly labeled as 15.0 alpha, no further updates to 14.2 Slackbuilds packages have been pushed. Does this mean that 14.2 Slackbuilds packages will not be updated any more? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozan.turkyilmaz at gmail.com Wed Jul 14 07:24:57 2021 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Wed, 14 Jul 2021 10:24:57 +0300 Subject: [Slackbuilds-users] Will there be further 14.2 updates? In-Reply-To: References: Message-ID: I plan to give aMule an update after the lockup. Maybe other packages too but only aMule is sure. Alexander Grotewohl , 14 Tem 2021 ?ar, 10:10 tarihinde ?unu yazd?: > I believe they're just locked for now so they aren't moving targets. But > I'd guess it's up to the maintainers of individual slackbuilds.. > > -- > Alexander Grotewohl > https://dcclost.com > > ------------------------------ > *From:* SlackBuilds-users on > behalf of Luveh Keraph <1.41421 at gmail.com> > *Sent:* Tuesday, July 13, 2021 8:50:55 PM > *To:* SlackBuilds.org Users List > *Subject:* [Slackbuilds-users] Will there be further 14.2 updates? > > I notice that ever since (roughly) shortly after the time > slackware-current was explicitly labeled as 15.0 alpha, no further updates > to 14.2 Slackbuilds packages have been pushed. Does this mean that 14.2 > Slackbuilds packages will not be updated any more? > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dwells at alfavinil.com Wed Jul 14 18:45:55 2021 From: dwells at alfavinil.com (David Wells) Date: Wed, 14 Jul 2021 15:45:55 -0300 Subject: [Slackbuilds-users] libosinfo-1.8.0 build problems Message-ID: Hi everybody! I'm attempting to build libosinfo-1.8.0 using slpkg and after installing all the dependencies the build process fails. Here is the output of the build. Could anybody help me figure out what could be the problem? > patching file > tests/isodata/slackware/slackware14.0/slackware-14.0-install-dvd.iso.txt > patching file > tests/isodata/slackware/slackware14.0/slackware64-14.0-install-dvd.iso.txt > patching file > tests/isodata/slackware/slackware14.1/slackware-14.1-install-dvd.iso.txt > patching file > tests/isodata/slackware/slackware14.1/slackware64-14.1-install-dvd.iso.txt > patching file > tests/isodata/slackware/slackware14.2/slackware-14.2-install-dvd.iso.txt > patching file > tests/isodata/slackware/slackware14.2/slackware64-14.2-install-dvd.iso.txt > The Meson build system > Version: 0.57.1 > Source dir: /tmp/SBo/libosinfo-1.8.0 > Build dir: /tmp/SBo/libosinfo-1.8.0/build > Build type: native build > Project name: libosinfo > Project version: 1.8.0 > C compiler for the host machine: ccache cc (gcc 5.5.0 "cc (GCC) 5.5.0") > C linker for the host machine: cc ld.bfd 2.26.20160125 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner) > Vala compiler for the host machine: valac (valac 0.34.9) > Configuring libosinfo.spec using configuration > Configuring mingw-libosinfo.spec using configuration > Program build-aux/dist.sh found: YES > (/tmp/SBo/libosinfo-1.8.0/build-aux/dist.sh) > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency glib-2.0 found: YES 2.46.2 > Run-time dependency gio-2.0 found: YES 2.46.2 > Run-time dependency gobject-2.0 found: YES 2.46.2 > Run-time dependency libsoup-2.4 found: YES 2.52.2 > Run-time dependency libxml-2.0 found: YES 2.9.12 > Run-time dependency libxslt found: YES 1.1.29 > Compiler for C supports arguments -W: YES > Compiler for C supports arguments -Waddress: YES > Compiler for C supports arguments -Waggressive-loop-optimizations: YES > Compiler for C supports arguments -Wall: YES > Compiler for C supports arguments -Warray-bounds: YES > Compiler for C supports arguments -Wattributes: YES > Compiler for C supports arguments -Wbuiltin-macro-redefined: YES > Compiler for C supports arguments -Wchar-subscripts: YES > Compiler for C supports arguments -Wclobbered: YES > Compiler for C supports arguments -Wcomment: YES > Compiler for C supports arguments -Wcomments: YES > Compiler for C supports arguments -Wcoverage-mismatch: YES > Compiler for C supports arguments -Wcpp: YES > Compiler for C supports arguments -Wdate-time: YES > Compiler for C supports arguments -Wdeclaration-after-statement: YES > Compiler for C supports arguments -Wdeprecated-declarations: YES > Compiler for C supports arguments -Wdisabled-optimization: YES > Compiler for C supports arguments -Wdiv-by-zero: YES > Compiler for C supports arguments -Wempty-body: YES > Compiler for C supports arguments -Wendif-labels: YES > Compiler for C supports arguments -Wenum-compare: YES > Compiler for C supports arguments -Wextra: YES > Compiler for C supports arguments -Wformat-contains-nul: YES > Compiler for C supports arguments -Wformat-extra-args: YES > Compiler for C supports arguments -Wformat-security: YES > Compiler for C supports arguments -Wformat-y2k: YES > Compiler for C supports arguments -Wformat-zero-length: YES > Compiler for C supports arguments -Wfree-nonheap-object: YES > Compiler for C supports arguments -Wignored-qualifiers: YES > Compiler for C supports arguments -Wimplicit: YES > Compiler for C supports arguments -Wimplicit-function-declaration: YES > Compiler for C supports arguments -Wimplicit-int: YES > Compiler for C supports arguments -Winit-self: YES > Compiler for C supports arguments -Wno-inline: YES > Compiler for C supports arguments -Wint-to-pointer-cast: YES > Compiler for C supports arguments -Winvalid-memory-model: YES > Compiler for C supports arguments -Winvalid-pch: YES > Compiler for C supports arguments -Wjump-misses-init: YES > Compiler for C supports arguments -Wlogical-op: YES > Compiler for C supports arguments -Wmain: YES > Compiler for C supports arguments -Wmaybe-uninitialized: YES > Compiler for C supports arguments -Wmissing-braces: YES > Compiler for C supports arguments -Wmissing-declarations: YES > Compiler for C supports arguments -Wmissing-field-initializers: YES > Compiler for C supports arguments -Wmissing-include-dirs: YES > Compiler for C supports arguments -Wmissing-parameter-type: YES > Compiler for C supports arguments -Wmissing-prototypes: YES > Compiler for C supports arguments -Wmultichar: YES > Compiler for C supports arguments -Wnarrowing: YES > Compiler for C supports arguments -Wnested-externs: YES > Compiler for C supports arguments -Wnonnull: YES > Compiler for C supports arguments -Wold-style-declaration: YES > Compiler for C supports arguments -Wold-style-definition: YES > Compiler for C supports arguments -Wopenmp-simd: YES > Compiler for C supports arguments -Woverflow: YES > Compiler for C supports arguments -Woverlength-strings: YES > Compiler for C supports arguments -Woverride-init: YES > Compiler for C supports arguments -Wpacked: YES > Compiler for C supports arguments -Wpacked-bitfield-compat: YES > Compiler for C supports arguments -Wparentheses: YES > Compiler for C supports arguments -Wpointer-arith: YES > Compiler for C supports arguments -Wpointer-sign: YES > Compiler for C supports arguments -Wpointer-to-int-cast: YES > Compiler for C supports arguments -Wpragmas: YES > Compiler for C supports arguments -Wreturn-local-addr: YES > Compiler for C supports arguments -Wreturn-type: YES > Compiler for C supports arguments -Wsequence-point: YES > Compiler for C supports arguments -Wshadow: YES > Compiler for C supports arguments -Wsizeof-pointer-memaccess: YES > Compiler for C supports arguments -Wstack-protector: YES > Compiler for C supports arguments -Wstrict-aliasing: YES > Compiler for C supports arguments -Wstrict-overflow: YES > Compiler for C supports arguments -Wstrict-prototypes: YES > Compiler for C supports arguments -Wsuggest-attribute=const: YES > Compiler for C supports arguments -Wsuggest-attribute=format: YES > Compiler for C supports arguments -Wsuggest-attribute=noreturn: YES > Compiler for C supports arguments -Wsuggest-attribute=pure: YES > Compiler for C supports arguments -Wswitch: YES > Compiler for C supports arguments -Wswitch-default: YES > Compiler for C supports arguments -Wsync-nand: YES > Compiler for C supports arguments -Wtrampolines: YES > Compiler for C supports arguments -Wtrigraphs: YES > Compiler for C supports arguments -Wtype-limits: YES > Compiler for C supports arguments -Wuninitialized: YES > Compiler for C supports arguments -Wunknown-pragmas: YES > Compiler for C supports arguments -Wunused: YES > Compiler for C supports arguments -Wunused-but-set-parameter: YES > Compiler for C supports arguments -Wunused-but-set-variable: YES > Compiler for C supports arguments -Wunused-function: YES > Compiler for C supports arguments -Wunused-label: YES > Compiler for C supports arguments -Wunused-local-typedefs: YES > Compiler for C supports arguments -Wunused-parameter: YES > Compiler for C supports arguments -Wunused-result: YES > Compiler for C supports arguments -Wunused-value: YES > Compiler for C supports arguments -Wunused-variable: YES > Compiler for C supports arguments -Wvarargs: YES > Compiler for C supports arguments -Wvariadic-macros: YES > Compiler for C supports arguments -Wvector-operation-performance: YES > Compiler for C supports arguments -Wvla: YES > Compiler for C supports arguments -Wvolatile-register-var: YES > Compiler for C supports arguments -Wwrite-strings: YES > Compiler for C supports arguments -Wnormalized=nfc: YES > Compiler for C supports arguments -Wno-sign-compare: YES > Compiler for C supports arguments -Wno-sign-conversion: YES > Compiler for C supports arguments -Wno-conversion: YES > Compiler for C supports arguments -Wno-unused-parameter: YES > Compiler for C supports arguments -Wjump-misses-init: YES (cached) > Compiler for C supports arguments -Wframe-larger-than=4096: YES > Compiler for C supports arguments -Wno-overlength-strings: YES > Compiler for C supports arguments --param=ssp-buffer-size=4: YES > Compiler for C supports arguments -fexceptions: YES > Compiler for C supports arguments -fasynchronous-unwind-tables: YES > Compiler for C supports arguments -fdiagnostics-show-option: YES > Compiler for C supports arguments -funit-at-a-time: YES > Compiler for C supports arguments -fipa-pure-const: YES > Compiler for C supports arguments -Wno-suggest-attribute=pure: YES > Compiler for C supports arguments -Wno-suggest-attribute=const: YES > Compiler for C supports arguments -Wno-string-plus-int: NO > Compiler for C supports arguments -fstack-protector-all: YES > Message: Location of pci.ids: "/usr/share/hwdata/pci.ids" > Message: Location of usb.ids: "/usr/share/hwdata/usb.ids" > ../meson.build:333: WARNING: Consider using the built-in warning_level > option instead of using "-Wall". > ../meson.build:333: WARNING: Consider using the built-in warning_level > option instead of using "-Wextra". > Configuring osinfo_version.h using configuration > Program glib-mkenums found: YES (/usr/bin/glib-mkenums) > Program glib-mkenums found: YES (/usr/bin/glib-mkenums) > Compiler for C supports link arguments -Wl,--no-undefined: YES > Configuring libosinfo-1.0.pc using configuration > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Build-time dependency gobject-introspection-1.0 found: YES 1.46.0 > Dependency gobject-introspection-1.0 found: YES 1.46.0 (cached) > Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner) > Dependency gobject-introspection-1.0 found: YES 1.46.0 (cached) > Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler) > Program vapigen found: YES (/usr/bin/vapigen) > Program pod2man found: YES (/usr/bin/pod2man) > Program gtkdoc-scan found: YES (/usr/bin/gtkdoc-scan) > Program gtkdoc-scan found: YES (/usr/bin/gtkdoc-scan) > Program gtkdoc-scangobj found: YES (/usr/bin/gtkdoc-scangobj) > Program gtkdoc-mkdb found: YES (/usr/bin/gtkdoc-mkdb) > Program gtkdoc-mkhtml found: YES (/usr/bin/gtkdoc-mkhtml) > Program gtkdoc-fixxref found: YES (/usr/bin/gtkdoc-fixxref) > Program /tmp/SBo/libosinfo-1.8.0/build-aux/syntax-check found: YES > (/tmp/SBo/libosinfo-1.8.0/build-aux/syntax-check) > Program check-symfile found: YES > (/tmp/SBo/libosinfo-1.8.0/tests/check-symfile) > Program check-symsorting found: YES > (/tmp/SBo/libosinfo-1.8.0/tests/check-symsorting) > Build targets in project: 33 > > Option buildtype is: release [default: debugoptimized] > Found ninja-1.10.2 at /usr/bin/ninja > [1/110] Generating osinfo-detect.1 with a custom command > [2/110] Generating osinfo-install-script.1 with a custom command > [3/110] Generating osinfo-query.1 with a custom command > [4/110] Generating osinfo_enum_types.h with a custom command (wrapped > by meson because command contains newlines, to capture output) > [5/110] Generating osinfo_enum_types.c with a custom command (wrapped > by meson because command contains newlines, to capture output) > [6/110] Compiling C object tests/test-firmware.p/test-firmware.c.o > [7/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_datamaplist.c.o > [8/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_devicelist.c.o > [9/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_devicelinkfilter.c.o > [10/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_avatar_format.c.o > [11/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_devicelink.c.o > [12/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_devicelinklist.c.o > [13/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_entity.c.o > [14/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_filter.c.o > [15/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_productfilter.c.o > [16/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_list.c.o > [17/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_device_driver.c.o > [18/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_firmware.c.o > [19/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_firmwarelist.c.o > [20/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_install_config_param.c.o > [21/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_product.c.o > [22/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_productlist.c.o > [23/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_device.c.o > [24/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_device_driverlist.c.o > [25/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_install_config.c.o > [26/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/meson-generated_.._osinfo_enum_types.c.o > [27/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_oslist.c.o > [28/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_os.c.o > [29/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_os_variant.c.o > [30/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_os_variantlist.c.o > [31/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_deployment.c.o > [32/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_deploymentlist.c.o > [33/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_media.c.o > [34/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_datamap.c.o > [35/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_install_script.c.o > [36/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_platform.c.o > [37/110] Compiling C object > tests/test-list.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [38/110] Compiling C object tests/test-list.p/test-list.c.o > [39/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_medialist.c.o > [40/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_resources.c.o > [41/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_resourceslist.c.o > [42/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_tree.c.o > [43/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_treelist.c.o > [44/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_util_private.c.o > [45/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_install_config_paramlist.c.o > [46/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_install_scriptlist.c.o > [47/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_image.c.o > [48/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_imagelist.c.o > [49/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_db.c.o > [50/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_loader.c.o > [51/110] Compiling C object > tools/osinfo-detect.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [52/110] Compiling C object tools/osinfo-detect.p/osinfo-detect.c.o > [53/110] Compiling C object tools/osinfo-query.p/osinfo-query.c.o > [54/110] Compiling C object > tools/osinfo-install-script.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [55/110] Compiling C object > tools/osinfo-query.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [56/110] Compiling C object tests/test-db.p/test-db.c.o > [57/110] Compiling C object > tests/test-device.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [58/110] Compiling C object tests/test-device.p/test-device.c.o > [59/110] Compiling C object > tools/osinfo-install-script.p/osinfo-install-script.c.o > [60/110] Compiling C object > tests/test-db.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [61/110] Compiling C object > tests/test-image.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [62/110] Compiling C object tests/test-image.p/test-image.c.o > [63/110] Compiling C object > tests/test-devicelinklist.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [64/110] Compiling C object > tests/test-entity.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [65/110] Compiling C object tests/test-entity.p/test-entity.c.o > [66/110] Compiling C object tests/test-filter.p/test-filter.c.o > [67/110] Compiling C object > osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_platformlist.c.o > [68/110] Compiling C object > tests/test-devicelinklist.p/test-devicelinklist.c.o > [69/110] Compiling C object > tests/test-filter.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [70/110] Compiling C object > tests/test-firmware.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [71/110] Compiling C object > tests/test-install-script.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [72/110] Compiling C object > tests/test-loader.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [73/110] Compiling C object tests/test-loader.p/test-loader.c.o > [74/110] Compiling C object > tests/test-platform.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [75/110] Compiling C object > tests/test-os.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [76/110] Compiling C object > tests/test-install-script.p/test-install-script.c.o > [77/110] Compiling C object > tests/test-productfilter.p/test-productfilter.c.o > [78/110] Compiling C object > tests/test-product.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [79/110] Compiling C object tests/test-product.p/test-product.c.o > [80/110] Compiling C object > tests/test-media.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [81/110] Compiling C object tests/test-media.p/test-media.c.o > [82/110] Compiling C object tests/test-os.p/test-os.c.o > [83/110] Compiling C object tests/test-platform.p/test-platform.c.o > [84/110] Compiling C object > tests/test-productfilter.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [85/110] Compiling C object > tests/test-tree.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o > [86/110] Compiling C object tests/test-tree.p/test-tree.c.o > [87/110] Linking target osinfo/libosinfo-1.0.so.0.1008.0 > [88/110] Generating symbol file > osinfo/libosinfo-1.0.so.0.1008.0.p/libosinfo-1.0.so.0.1008.0.symbols > [89/110] Linking target tests/test-filter > [90/110] Linking target tests/test-image > [91/110] Linking target tests/test-firmware > [92/110] Linking target tests/test-device > [93/110] Linking target tests/test-product > [94/110] Linking target tests/test-media > [95/110] Linking target tools/osinfo-install-script > [96/110] Linking target tests/test-platform > [97/110] Linking target tests/test-tree > [98/110] Linking target tests/test-db > [99/110] Linking target tests/test-entity > [100/110] Linking target tests/test-list > [101/110] Linking target tests/test-devicelinklist > [102/110] Linking target tools/osinfo-detect > [103/110] Linking target tests/test-loader > [104/110] Linking target tools/osinfo-query > [105/110] Linking target tests/test-os > [106/110] Linking target tests/test-install-script > [107/110] Linking target tests/test-productfilter > [108/110] Generating Libosinfo-1.0.gir with a custom command > FAILED: osinfo/Libosinfo-1.0.gir > /usr/bin/g-ir-scanner --no-libtool --namespace=Libosinfo > --nsversion=1.0 --warn-all --output osinfo/Libosinfo-1.0.gir > --c-include=osinfo/osinfo.h -I/tmp/SBo/libosinfo-1.8.0/osinfo > -I/tmp/SBo/libosinfo-1.8.0/build/osinfo -I./. -I../. -I./osinfo/. > -I../osinfo/. > --filelist=/tmp/SBo/libosinfo-1.8.0/build/osinfo/libosinfo-1.0.so.0.1008.0.p/Libosinfo_1.0_gir_filelist > --include=GObject-2.0 --include=Gio-2.0 --include=libxml2-2.0 > --symbol-prefix=osinfo --identifier-prefix=Osinfo > --pkg-export=libosinfo-1.0 --cflags-begin > -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_44 > -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_44 > '-DPKG_DATA_DIR="/usr/share/libosinfo"' '-DDATA_DIR="/usr/share"' > '-DSYS_CONF_DIR="/etc"' '-DLOCALEDIR="/usr/share/locale"' > '-DGETTEXT_PACKAGE="libosinfo"' -W -Waddress > -Waggressive-loop-optimizations -Wall -Warray-bounds -Wattributes > -Wbuiltin-macro-redefined -Wchar-subscripts -Wclobbered -Wcomment > -Wcomments -Wcoverage-mismatch -Wcpp -Wdate-time > -Wdeclaration-after-statement -Wdeprecated-declarations > -Wdisabled-optimization -Wdiv-by-zero -Wempty-body -Wendif-labels > -Wenum-compare -Wextra -Wformat-contains-nul -Wformat-extra-args > -Wformat-security -Wformat-y2k -Wformat-zero-length > -Wfree-nonheap-object -Wignored-qualifiers -Wimplicit > -Wimplicit-function-declaration -Wimplicit-int -Winit-self -Wno-inline > -Wint-to-pointer-cast -Winvalid-memory-model -Winvalid-pch > -Wjump-misses-init -Wlogical-op -Wmain -Wmaybe-uninitialized > -Wmissing-braces -Wmissing-declarations -Wmissing-field-initializers > -Wmissing-include-dirs -Wmissing-parameter-type -Wmissing-prototypes > -Wmultichar -Wnarrowing -Wnested-externs -Wnonnull > -Wold-style-declaration -Wold-style-definition -Wopenmp-simd > -Woverflow -Woverlength-strings -Woverride-init -Wpacked > -Wpacked-bitfield-compat -Wparentheses -Wpointer-arith -Wpointer-sign > -Wpointer-to-int-cast -Wpragmas -Wreturn-local-addr -Wreturn-type > -Wsequence-point -Wshadow -Wsizeof-pointer-memaccess -Wstack-protector > -Wstrict-aliasing -Wstrict-overflow -Wstrict-prototypes > -Wsuggest-attribute=const -Wsuggest-attribute=format > -Wsuggest-attribute=noreturn -Wsuggest-attribute=pure -Wswitch > -Wswitch-default -Wsync-nand -Wtrampolines -Wtrigraphs -Wtype-limits > -Wuninitialized -Wunknown-pragmas -Wunused -Wunused-but-set-parameter > -Wunused-but-set-variable -Wunused-function -Wunused-label > -Wunused-local-typedefs -Wunused-parameter -Wunused-result > -Wunused-value -Wunused-variable -Wvarargs -Wvariadic-macros > -Wvector-operation-performance -Wvla -Wvolatile-register-var > -Wwrite-strings -Wnormalized=nfc -Wno-sign-compare > -Wno-sign-conversion -Wno-conversion -Wno-unused-parameter > -Wjump-misses-init -Wframe-larger-than=4096 -Wno-overlength-strings > --param=ssp-buffer-size=4 -fexceptions -fasynchronous-unwind-tables > -fdiagnostics-show-option -funit-at-a-time -fipa-pure-const > -Wno-suggest-attribute=pure -Wno-suggest-attribute=const > -fstack-protector-all '-DPCI_IDS="/usr/share/hwdata/pci.ids"' > '-DUSB_IDS="/usr/share/hwdata/usb.ids"' -I./. -I../. -I./osinfo/. > -I../osinfo/. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include > -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 > -I/usr/include/gobject-introspection-1.0 --cflags-end > --add-include-path=/usr/share/gir-1.0 -L./osinfo --library osinfo-1.0 > -lgobject-2.0 -lglib-2.0 -lgio-2.0 -lsoup-2.4 -lxml2 -lxslt -lz -llzma > -lm -ldl -lgirepository-1.0 > /tmp/SBo/libosinfo-1.8.0/osinfo/osinfo_datamap.h:34: syntax error, > unexpected ';' in > '??????????????????????????????????????????????????????? ;' at ';' > /tmp/SBo/libosinfo-1.8.0/osinfo/osinfo_device.h:34: syntax error, > unexpected ';' in > '??????????????????????????????????????????????????????? ;' at ';' > /tmp/SBo/libosinfo-1.8.0/build/tmp-introspectyGgpyt/Libosinfo-1.0: > error while loading shared libraries: libosinfo-1.0.so.0: cannot open > shared object file: No such file or directory > Command > '['/tmp/SBo/libosinfo-1.8.0/build/tmp-introspectyGgpyt/Libosinfo-1.0', > '--introspect-dump=/tmp/SBo/libosinfo-1.8.0/build/tmp-introspectyGgpyt/functions.txt,/tmp/SBo/libosinfo-1.8.0/build/tmp-introspectyGgpyt/dump.xml']' > returned non-zero exit status 127 > ninja: build stopped: subcommand failed. > Total build time for the package libosinfo : 7.04 Sec > > > No such package libosinfo-1.8.0: Can't build Thank you very much in advance. Best regards, David Wells. From dwells at alfavinil.com Wed Jul 14 20:07:42 2021 From: dwells at alfavinil.com (David Wells) Date: Wed, 14 Jul 2021 17:07:42 -0300 Subject: [Slackbuilds-users] libosinfo-1.8.0 build problems In-Reply-To: References: Message-ID: <91f8d5d4-ef97-29ed-48ea-dcb59657db80@alfavinil.com> El 14/7/2021 a las 15:45, David Wells escribi?: > Hi everybody! > > I'm attempting to build libosinfo-1.8.0 using slpkg and after > installing all the dependencies the build process fails. Here is the > output of the build. Could anybody help me figure out what could be > the problem? >> patching file >> tests/isodata/slackware/slackware14.0/slackware-14.0-install-dvd.iso.txt >> patching file >> tests/isodata/slackware/slackware14.0/slackware64-14.0-install-dvd.iso.txt >> patching file >> tests/isodata/slackware/slackware14.1/slackware-14.1-install-dvd.iso.txt >> patching file >> tests/isodata/slackware/slackware14.1/slackware64-14.1-install-dvd.iso.txt >> patching file >> tests/isodata/slackware/slackware14.2/slackware-14.2-install-dvd.iso.txt >> patching file >> tests/isodata/slackware/slackware14.2/slackware64-14.2-install-dvd.iso.txt >> The Meson build system >> Version: 0.57.1 >> Source dir: /tmp/SBo/libosinfo-1.8.0 >> Build dir: /tmp/SBo/libosinfo-1.8.0/build >> Build type: native build >> Project name: libosinfo >> Project version: 1.8.0 >> C compiler for the host machine: ccache cc (gcc 5.5.0 "cc (GCC) 5.5.0") >> C linker for the host machine: cc ld.bfd 2.26.20160125 >> Host machine cpu family: x86_64 >> Host machine cpu: x86_64 >> Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner) >> Vala compiler for the host machine: valac (valac 0.34.9) >> Configuring libosinfo.spec using configuration >> Configuring mingw-libosinfo.spec using configuration >> Program build-aux/dist.sh found: YES >> (/tmp/SBo/libosinfo-1.8.0/build-aux/dist.sh) >> Found pkg-config: /usr/bin/pkg-config (0.29.2) >> Run-time dependency glib-2.0 found: YES 2.46.2 >> Run-time dependency gio-2.0 found: YES 2.46.2 >> Run-time dependency gobject-2.0 found: YES 2.46.2 >> Run-time dependency libsoup-2.4 found: YES 2.52.2 >> Run-time dependency libxml-2.0 found: YES 2.9.12 >> Run-time dependency libxslt found: YES 1.1.29 >> Compiler for C supports arguments -W: YES >> Compiler for C supports arguments -Waddress: YES >> Compiler for C supports arguments -Waggressive-loop-optimizations: YES >> Compiler for C supports arguments -Wall: YES >> Compiler for C supports arguments -Warray-bounds: YES >> Compiler for C supports arguments -Wattributes: YES >> Compiler for C supports arguments -Wbuiltin-macro-redefined: YES >> Compiler for C supports arguments -Wchar-subscripts: YES >> Compiler for C supports arguments -Wclobbered: YES >> Compiler for C supports arguments -Wcomment: YES >> Compiler for C supports arguments -Wcomments: YES >> Compiler for C supports arguments -Wcoverage-mismatch: YES >> Compiler for C supports arguments -Wcpp: YES >> Compiler for C supports arguments -Wdate-time: YES >> Compiler for C supports arguments -Wdeclaration-after-statement: YES >> Compiler for C supports arguments -Wdeprecated-declarations: YES >> Compiler for C supports arguments -Wdisabled-optimization: YES >> Compiler for C supports arguments -Wdiv-by-zero: YES >> Compiler for C supports arguments -Wempty-body: YES >> Compiler for C supports arguments -Wendif-labels: YES >> Compiler for C supports arguments -Wenum-compare: YES >> Compiler for C supports arguments -Wextra: YES >> Compiler for C supports arguments -Wformat-contains-nul: YES >> Compiler for C supports arguments -Wformat-extra-args: YES >> Compiler for C supports arguments -Wformat-security: YES >> Compiler for C supports arguments -Wformat-y2k: YES >> Compiler for C supports arguments -Wformat-zero-length: YES >> Compiler for C supports arguments -Wfree-nonheap-object: YES >> Compiler for C supports arguments -Wignored-qualifiers: YES >> Compiler for C supports arguments -Wimplicit: YES >> Compiler for C supports arguments -Wimplicit-function-declaration: YES >> Compiler for C supports arguments -Wimplicit-int: YES >> Compiler for C supports arguments -Winit-self: YES >> Compiler for C supports arguments -Wno-inline: YES >> Compiler for C supports arguments -Wint-to-pointer-cast: YES >> Compiler for C supports arguments -Winvalid-memory-model: YES >> Compiler for C supports arguments -Winvalid-pch: YES >> Compiler for C supports arguments -Wjump-misses-init: YES >> Compiler for C supports arguments -Wlogical-op: YES >> Compiler for C supports arguments -Wmain: YES >> Compiler for C supports arguments -Wmaybe-uninitialized: YES >> Compiler for C supports arguments -Wmissing-braces: YES >> Compiler for C supports arguments -Wmissing-declarations: YES >> Compiler for C supports arguments -Wmissing-field-initializers: YES >> Compiler for C supports arguments -Wmissing-include-dirs: YES >> Compiler for C supports arguments -Wmissing-parameter-type: YES >> Compiler for C supports arguments -Wmissing-prototypes: YES >> Compiler for C supports arguments -Wmultichar: YES >> Compiler for C supports arguments -Wnarrowing: YES >> Compiler for C supports arguments -Wnested-externs: YES >> Compiler for C supports arguments -Wnonnull: YES >> Compiler for C supports arguments -Wold-style-declaration: YES >> Compiler for C supports arguments -Wold-style-definition: YES >> Compiler for C supports arguments -Wopenmp-simd: YES >> Compiler for C supports arguments -Woverflow: YES >> Compiler for C supports arguments -Woverlength-strings: YES >> Compiler for C supports arguments -Woverride-init: YES >> Compiler for C supports arguments -Wpacked: YES >> Compiler for C supports arguments -Wpacked-bitfield-compat: YES >> Compiler for C supports arguments -Wparentheses: YES >> Compiler for C supports arguments -Wpointer-arith: YES >> Compiler for C supports arguments -Wpointer-sign: YES >> Compiler for C supports arguments -Wpointer-to-int-cast: YES >> Compiler for C supports arguments -Wpragmas: YES >> Compiler for C supports arguments -Wreturn-local-addr: YES >> Compiler for C supports arguments -Wreturn-type: YES >> Compiler for C supports arguments -Wsequence-point: YES >> Compiler for C supports arguments -Wshadow: YES >> Compiler for C supports arguments -Wsizeof-pointer-memaccess: YES >> Compiler for C supports arguments -Wstack-protector: YES >> Compiler for C supports arguments -Wstrict-aliasing: YES >> Compiler for C supports arguments -Wstrict-overflow: YES >> Compiler for C supports arguments -Wstrict-prototypes: YES >> Compiler for C supports arguments -Wsuggest-attribute=const: YES >> Compiler for C supports arguments -Wsuggest-attribute=format: YES >> Compiler for C supports arguments -Wsuggest-attribute=noreturn: YES >> Compiler for C supports arguments -Wsuggest-attribute=pure: YES >> Compiler for C supports arguments -Wswitch: YES >> Compiler for C supports arguments -Wswitch-default: YES >> Compiler for C supports arguments -Wsync-nand: YES >> Compiler for C supports arguments -Wtrampolines: YES >> Compiler for C supports arguments -Wtrigraphs: YES >> Compiler for C supports arguments -Wtype-limits: YES >> Compiler for C supports arguments -Wuninitialized: YES >> Compiler for C supports arguments -Wunknown-pragmas: YES >> Compiler for C supports arguments -Wunused: YES >> Compiler for C supports arguments -Wunused-but-set-parameter: YES >> Compiler for C supports arguments -Wunused-but-set-variable: YES >> Compiler for C supports arguments -Wunused-function: YES >> Compiler for C supports arguments -Wunused-label: YES >> Compiler for C supports arguments -Wunused-local-typedefs: YES >> Compiler for C supports arguments -Wunused-parameter: YES >> Compiler for C supports arguments -Wunused-result: YES >> Compiler for C supports arguments -Wunused-value: YES >> Compiler for C supports arguments -Wunused-variable: YES >> Compiler for C supports arguments -Wvarargs: YES >> Compiler for C supports arguments -Wvariadic-macros: YES >> Compiler for C supports arguments -Wvector-operation-performance: YES >> Compiler for C supports arguments -Wvla: YES >> Compiler for C supports arguments -Wvolatile-register-var: YES >> Compiler for C supports arguments -Wwrite-strings: YES >> Compiler for C supports arguments -Wnormalized=nfc: YES >> Compiler for C supports arguments -Wno-sign-compare: YES >> Compiler for C supports arguments -Wno-sign-conversion: YES >> Compiler for C supports arguments -Wno-conversion: YES >> Compiler for C supports arguments -Wno-unused-parameter: YES >> Compiler for C supports arguments -Wjump-misses-init: YES (cached) >> Compiler for C supports arguments -Wframe-larger-than=4096: YES >> Compiler for C supports arguments -Wno-overlength-strings: YES >> Compiler for C supports arguments --param=ssp-buffer-size=4: YES >> Compiler for C supports arguments -fexceptions: YES >> Compiler for C supports arguments -fasynchronous-unwind-tables: YES >> Compiler for C supports arguments -fdiagnostics-show-option: YES >> Compiler for C supports arguments -funit-at-a-time: YES >> Compiler for C supports arguments -fipa-pure-const: YES >> Compiler for C supports arguments -Wno-suggest-attribute=pure: YES >> Compiler for C supports arguments -Wno-suggest-attribute=const: YES >> Compiler for C supports arguments -Wno-string-plus-int: NO >> Compiler for C supports arguments -fstack-protector-all: YES >> Message: Location of pci.ids: "/usr/share/hwdata/pci.ids" >> Message: Location of usb.ids: "/usr/share/hwdata/usb.ids" >> ../meson.build:333: WARNING: Consider using the built-in >> warning_level option instead of using "-Wall". >> ../meson.build:333: WARNING: Consider using the built-in >> warning_level option instead of using "-Wextra". >> Configuring osinfo_version.h using configuration >> Program glib-mkenums found: YES (/usr/bin/glib-mkenums) >> Program glib-mkenums found: YES (/usr/bin/glib-mkenums) >> Compiler for C supports link arguments -Wl,--no-undefined: YES >> Configuring libosinfo-1.0.pc using configuration >> Found pkg-config: /usr/bin/pkg-config (0.29.2) >> Build-time dependency gobject-introspection-1.0 found: YES 1.46.0 >> Dependency gobject-introspection-1.0 found: YES 1.46.0 (cached) >> Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner) >> Dependency gobject-introspection-1.0 found: YES 1.46.0 (cached) >> Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler) >> Program vapigen found: YES (/usr/bin/vapigen) >> Program pod2man found: YES (/usr/bin/pod2man) >> Program gtkdoc-scan found: YES (/usr/bin/gtkdoc-scan) >> Program gtkdoc-scan found: YES (/usr/bin/gtkdoc-scan) >> Program gtkdoc-scangobj found: YES (/usr/bin/gtkdoc-scangobj) >> Program gtkdoc-mkdb found: YES (/usr/bin/gtkdoc-mkdb) >> Program gtkdoc-mkhtml found: YES (/usr/bin/gtkdoc-mkhtml) >> Program gtkdoc-fixxref found: YES (/usr/bin/gtkdoc-fixxref) >> Program /tmp/SBo/libosinfo-1.8.0/build-aux/syntax-check found: YES >> (/tmp/SBo/libosinfo-1.8.0/build-aux/syntax-check) >> Program check-symfile found: YES >> (/tmp/SBo/libosinfo-1.8.0/tests/check-symfile) >> Program check-symsorting found: YES >> (/tmp/SBo/libosinfo-1.8.0/tests/check-symsorting) >> Build targets in project: 33 >> >> Option buildtype is: release [default: debugoptimized] >> Found ninja-1.10.2 at /usr/bin/ninja >> [1/110] Generating osinfo-detect.1 with a custom command >> [2/110] Generating osinfo-install-script.1 with a custom command >> [3/110] Generating osinfo-query.1 with a custom command >> [4/110] Generating osinfo_enum_types.h with a custom command (wrapped >> by meson because command contains newlines, to capture output) >> [5/110] Generating osinfo_enum_types.c with a custom command (wrapped >> by meson because command contains newlines, to capture output) >> [6/110] Compiling C object tests/test-firmware.p/test-firmware.c.o >> [7/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_datamaplist.c.o >> [8/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_devicelist.c.o >> [9/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_devicelinkfilter.c.o >> [10/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_avatar_format.c.o >> [11/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_devicelink.c.o >> [12/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_devicelinklist.c.o >> [13/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_entity.c.o >> [14/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_filter.c.o >> [15/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_productfilter.c.o >> [16/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_list.c.o >> [17/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_device_driver.c.o >> [18/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_firmware.c.o >> [19/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_firmwarelist.c.o >> [20/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_install_config_param.c.o >> [21/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_product.c.o >> [22/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_productlist.c.o >> [23/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_device.c.o >> [24/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_device_driverlist.c.o >> [25/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_install_config.c.o >> [26/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/meson-generated_.._osinfo_enum_types.c.o >> [27/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_oslist.c.o >> [28/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_os.c.o >> [29/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_os_variant.c.o >> [30/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_os_variantlist.c.o >> [31/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_deployment.c.o >> [32/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_deploymentlist.c.o >> [33/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_media.c.o >> [34/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_datamap.c.o >> [35/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_install_script.c.o >> [36/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_platform.c.o >> [37/110] Compiling C object >> tests/test-list.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [38/110] Compiling C object tests/test-list.p/test-list.c.o >> [39/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_medialist.c.o >> [40/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_resources.c.o >> [41/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_resourceslist.c.o >> [42/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_tree.c.o >> [43/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_treelist.c.o >> [44/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_util_private.c.o >> [45/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_install_config_paramlist.c.o >> [46/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_install_scriptlist.c.o >> [47/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_image.c.o >> [48/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_imagelist.c.o >> [49/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_db.c.o >> [50/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_loader.c.o >> [51/110] Compiling C object >> tools/osinfo-detect.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [52/110] Compiling C object tools/osinfo-detect.p/osinfo-detect.c.o >> [53/110] Compiling C object tools/osinfo-query.p/osinfo-query.c.o >> [54/110] Compiling C object >> tools/osinfo-install-script.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [55/110] Compiling C object >> tools/osinfo-query.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [56/110] Compiling C object tests/test-db.p/test-db.c.o >> [57/110] Compiling C object >> tests/test-device.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [58/110] Compiling C object tests/test-device.p/test-device.c.o >> [59/110] Compiling C object >> tools/osinfo-install-script.p/osinfo-install-script.c.o >> [60/110] Compiling C object >> tests/test-db.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [61/110] Compiling C object >> tests/test-image.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [62/110] Compiling C object tests/test-image.p/test-image.c.o >> [63/110] Compiling C object >> tests/test-devicelinklist.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [64/110] Compiling C object >> tests/test-entity.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [65/110] Compiling C object tests/test-entity.p/test-entity.c.o >> [66/110] Compiling C object tests/test-filter.p/test-filter.c.o >> [67/110] Compiling C object >> osinfo/libosinfo-1.0.so.0.1008.0.p/osinfo_platformlist.c.o >> [68/110] Compiling C object >> tests/test-devicelinklist.p/test-devicelinklist.c.o >> [69/110] Compiling C object >> tests/test-filter.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [70/110] Compiling C object >> tests/test-firmware.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [71/110] Compiling C object >> tests/test-install-script.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [72/110] Compiling C object >> tests/test-loader.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [73/110] Compiling C object tests/test-loader.p/test-loader.c.o >> [74/110] Compiling C object >> tests/test-platform.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [75/110] Compiling C object >> tests/test-os.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [76/110] Compiling C object >> tests/test-install-script.p/test-install-script.c.o >> [77/110] Compiling C object >> tests/test-productfilter.p/test-productfilter.c.o >> [78/110] Compiling C object >> tests/test-product.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [79/110] Compiling C object tests/test-product.p/test-product.c.o >> [80/110] Compiling C object >> tests/test-media.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [81/110] Compiling C object tests/test-media.p/test-media.c.o >> [82/110] Compiling C object tests/test-os.p/test-os.c.o >> [83/110] Compiling C object tests/test-platform.p/test-platform.c.o >> [84/110] Compiling C object >> tests/test-productfilter.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [85/110] Compiling C object >> tests/test-tree.p/meson-generated_.._.._osinfo_osinfo_enum_types.c.o >> [86/110] Compiling C object tests/test-tree.p/test-tree.c.o >> [87/110] Linking target osinfo/libosinfo-1.0.so.0.1008.0 >> [88/110] Generating symbol file >> osinfo/libosinfo-1.0.so.0.1008.0.p/libosinfo-1.0.so.0.1008.0.symbols >> [89/110] Linking target tests/test-filter >> [90/110] Linking target tests/test-image >> [91/110] Linking target tests/test-firmware >> [92/110] Linking target tests/test-device >> [93/110] Linking target tests/test-product >> [94/110] Linking target tests/test-media >> [95/110] Linking target tools/osinfo-install-script >> [96/110] Linking target tests/test-platform >> [97/110] Linking target tests/test-tree >> [98/110] Linking target tests/test-db >> [99/110] Linking target tests/test-entity >> [100/110] Linking target tests/test-list >> [101/110] Linking target tests/test-devicelinklist >> [102/110] Linking target tools/osinfo-detect >> [103/110] Linking target tests/test-loader >> [104/110] Linking target tools/osinfo-query >> [105/110] Linking target tests/test-os >> [106/110] Linking target tests/test-install-script >> [107/110] Linking target tests/test-productfilter >> [108/110] Generating Libosinfo-1.0.gir with a custom command >> FAILED: osinfo/Libosinfo-1.0.gir >> /usr/bin/g-ir-scanner --no-libtool --namespace=Libosinfo >> --nsversion=1.0 --warn-all --output osinfo/Libosinfo-1.0.gir >> --c-include=osinfo/osinfo.h -I/tmp/SBo/libosinfo-1.8.0/osinfo >> -I/tmp/SBo/libosinfo-1.8.0/build/osinfo -I./. -I../. -I./osinfo/. >> -I../osinfo/. >> --filelist=/tmp/SBo/libosinfo-1.8.0/build/osinfo/libosinfo-1.0.so.0.1008.0.p/Libosinfo_1.0_gir_filelist >> --include=GObject-2.0 --include=Gio-2.0 --include=libxml2-2.0 >> --symbol-prefix=osinfo --identifier-prefix=Osinfo >> --pkg-export=libosinfo-1.0 --cflags-begin >> -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_44 >> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_44 >> '-DPKG_DATA_DIR="/usr/share/libosinfo"' '-DDATA_DIR="/usr/share"' >> '-DSYS_CONF_DIR="/etc"' '-DLOCALEDIR="/usr/share/locale"' >> '-DGETTEXT_PACKAGE="libosinfo"' -W -Waddress >> -Waggressive-loop-optimizations -Wall -Warray-bounds -Wattributes >> -Wbuiltin-macro-redefined -Wchar-subscripts -Wclobbered -Wcomment >> -Wcomments -Wcoverage-mismatch -Wcpp -Wdate-time >> -Wdeclaration-after-statement -Wdeprecated-declarations >> -Wdisabled-optimization -Wdiv-by-zero -Wempty-body -Wendif-labels >> -Wenum-compare -Wextra -Wformat-contains-nul -Wformat-extra-args >> -Wformat-security -Wformat-y2k -Wformat-zero-length >> -Wfree-nonheap-object -Wignored-qualifiers -Wimplicit >> -Wimplicit-function-declaration -Wimplicit-int -Winit-self >> -Wno-inline -Wint-to-pointer-cast -Winvalid-memory-model >> -Winvalid-pch -Wjump-misses-init -Wlogical-op -Wmain >> -Wmaybe-uninitialized -Wmissing-braces -Wmissing-declarations >> -Wmissing-field-initializers -Wmissing-include-dirs >> -Wmissing-parameter-type -Wmissing-prototypes -Wmultichar -Wnarrowing >> -Wnested-externs -Wnonnull -Wold-style-declaration >> -Wold-style-definition -Wopenmp-simd -Woverflow -Woverlength-strings >> -Woverride-init -Wpacked -Wpacked-bitfield-compat -Wparentheses >> -Wpointer-arith -Wpointer-sign -Wpointer-to-int-cast -Wpragmas >> -Wreturn-local-addr -Wreturn-type -Wsequence-point -Wshadow >> -Wsizeof-pointer-memaccess -Wstack-protector -Wstrict-aliasing >> -Wstrict-overflow -Wstrict-prototypes -Wsuggest-attribute=const >> -Wsuggest-attribute=format -Wsuggest-attribute=noreturn >> -Wsuggest-attribute=pure -Wswitch -Wswitch-default -Wsync-nand >> -Wtrampolines -Wtrigraphs -Wtype-limits -Wuninitialized >> -Wunknown-pragmas -Wunused -Wunused-but-set-parameter >> -Wunused-but-set-variable -Wunused-function -Wunused-label >> -Wunused-local-typedefs -Wunused-parameter -Wunused-result >> -Wunused-value -Wunused-variable -Wvarargs -Wvariadic-macros >> -Wvector-operation-performance -Wvla -Wvolatile-register-var >> -Wwrite-strings -Wnormalized=nfc -Wno-sign-compare >> -Wno-sign-conversion -Wno-conversion -Wno-unused-parameter >> -Wjump-misses-init -Wframe-larger-than=4096 -Wno-overlength-strings >> --param=ssp-buffer-size=4 -fexceptions -fasynchronous-unwind-tables >> -fdiagnostics-show-option -funit-at-a-time -fipa-pure-const >> -Wno-suggest-attribute=pure -Wno-suggest-attribute=const >> -fstack-protector-all '-DPCI_IDS="/usr/share/hwdata/pci.ids"' >> '-DUSB_IDS="/usr/share/hwdata/usb.ids"' -I./. -I../. -I./osinfo/. >> -I../osinfo/. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include >> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 >> -I/usr/include/gobject-introspection-1.0 --cflags-end >> --add-include-path=/usr/share/gir-1.0 -L./osinfo --library osinfo-1.0 >> -lgobject-2.0 -lglib-2.0 -lgio-2.0 -lsoup-2.4 -lxml2 -lxslt -lz >> -llzma -lm -ldl -lgirepository-1.0 >> /tmp/SBo/libosinfo-1.8.0/osinfo/osinfo_datamap.h:34: syntax error, >> unexpected ';' in >> '??????????????????????????????????????????????????????? ;' at ';' >> /tmp/SBo/libosinfo-1.8.0/osinfo/osinfo_device.h:34: syntax error, >> unexpected ';' in >> '??????????????????????????????????????????????????????? ;' at ';' >> /tmp/SBo/libosinfo-1.8.0/build/tmp-introspectyGgpyt/Libosinfo-1.0: >> error while loading shared libraries: libosinfo-1.0.so.0: cannot open >> shared object file: No such file or directory >> Command >> '['/tmp/SBo/libosinfo-1.8.0/build/tmp-introspectyGgpyt/Libosinfo-1.0', >> '--introspect-dump=/tmp/SBo/libosinfo-1.8.0/build/tmp-introspectyGgpyt/functions.txt,/tmp/SBo/libosinfo-1.8.0/build/tmp-introspectyGgpyt/dump.xml']' >> returned non-zero exit status 127 >> ninja: build stopped: subcommand failed. >> Total build time for the package libosinfo : 7.04 Sec >> >> >> No such package libosinfo-1.8.0: Can't build > > Thank you very much in advance. > Best regards, > David Wells. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > I seem to have found the culprit. I downgraded meson from 0.57.1 to 0.55.3 which I had laying around from a previous install and it compiled without a problem. Is there anything that could be done to compile using the most recent version of meson? Thanks again! Best regards, David Wells. From willysr at slackbuilds.org Thu Jul 15 00:19:42 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 15 Jul 2021 07:19:42 +0700 Subject: [Slackbuilds-users] libosinfo-1.8.0 build problems In-Reply-To: <91f8d5d4-ef97-29ed-48ea-dcb59657db80@alfavinil.com> References: <91f8d5d4-ef97-29ed-48ea-dcb59657db80@alfavinil.com> Message-ID: <23153640-8c19-e1f3-721f-d7a5e41458be@slackbuilds.org> > I seem to have found the culprit. I downgraded meson from 0.57.1 to > 0.55.3 which I had laying around from a previous install and it compiled > without a problem. Is there anything that could be done to compile using > the most recent version of meson? Is this on 14.2 or in -current? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From jdashiel at panix.com Thu Jul 15 11:26:50 2021 From: jdashiel at panix.com (Jude DaShiell) Date: Thu, 15 Jul 2021 07:26:50 -0400 Subject: [Slackbuilds-users] insync run fails Message-ID: I installed insync using sbopkg and it fails to run as a result of insync/pythonlib3 being missing. The man page was sparse in terms of commands and options and what those do so that's why I ran insync --help and discovered this error. Next I'll try and build insync with the SlackBuild script since I want to see if I can replicate this error with that kind of build. If I can't sbopkg for whatever reason for insync is inappropriate as a build tool. I did run sqg -p insync and got no sqf file created since there was nothing to put into it. I suppose for completeness I ought to try installing with spi in order to have all bases covered. From didier at slint.fr Thu Jul 15 12:14:31 2021 From: didier at slint.fr (Didier Spaier) Date: Thu, 15 Jul 2021 14:14:31 +0200 Subject: [Slackbuilds-users] insync run fails In-Reply-To: References: Message-ID: <0a97ec85-54c7-e9e9-fff7-3e439e540fd6@slint.fr> Hi, Le 15/07/2021 ? 13:26, Jude DaShiell a ?crit : > I installed insync using sbopkg and it fails to run as a result of > insync/pythonlib3 being missing. The man page was sparse in terms of > commands and options and what those do so that's why I ran insync --help > and discovered this error. Next I'll try and build insync with the > SlackBuild script since I want to see if I can replicate this error with > that kind of build. If I can't sbopkg for whatever reason for insync is > inappropriate as a build tool. I did run sqg -p insync and got no sqf > file created since there was nothing to put into it. I suppose for > completeness I ought to try installing with spi in order to have all bases > covered. spi won't help, Jude, as it's just a front-end to slapt-get and slapt-src and sbopkg is not guilty either. I installed insync using slapt-src on Slint. When starting it from a terminal the error message is: Error loading Python lib '/usr/lib64/insync/libpython3.7m.so.1.0': dlopen: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib64/insync/libpython3.7m.so.1.0) Indeed Slint64-2.2.1 ships glibc-2.23 (same package as in Slackware64-14.2) so I assume that the same issue occurs in Slackware. If I am correct, there's nothing simple we can do to fix this issue, as the repackaged Debian binary bundles a lot of stuff but not glibc. Additionally in Slint we ship python3.9 and the python stuff in the package are for Python3.7 so this thing wouldn't probably work in Slint anyway (SBo provides Python 3.7 instead at time of writing but I chose to update to the major version shipped in -current, to avoid upgrading all Python packages twice from 3.5 that we shipped previously). I send this email also to the maintainer of insync @ SBo. Cheers, Didier From didier at slint.fr Thu Jul 15 12:20:19 2021 From: didier at slint.fr (Didier Spaier) Date: Thu, 15 Jul 2021 14:20:19 +0200 Subject: [Slackbuilds-users] insync run fails In-Reply-To: <0a97ec85-54c7-e9e9-fff7-3e439e540fd6@slint.fr> References: <0a97ec85-54c7-e9e9-fff7-3e439e540fd6@slint.fr> Message-ID: <3a3f03e6-0994-9cbc-bfb2-429699e06363@slint.fr> PS: forwarding to Christopher who last updated the SlackBuild. I will downgrade the source to the previousli shipped version and see what happens. Le 15/07/2021 ? 14:14, Didier Spaier a ?crit?: > Hi, > > Le 15/07/2021 ? 13:26, Jude DaShiell a ?crit : > > I installed insync using sbopkg and it fails to run as a result of > > insync/pythonlib3 being missing.? The man page was sparse in terms of > > commands and options and what those do so that's why I ran insync --help > > and discovered this error.? Next I'll try and build insync with the > > SlackBuild script since I want to see if I can replicate this error with > > that kind of build.? If I can't sbopkg for whatever reason for insync is > > inappropriate as a build tool.? I did run sqg -p insync and got no sqf > > file created since there was nothing to put into it.? I suppose for > > completeness I ought to try installing with spi in order to have all > bases > > covered. > > spi won't help, Jude, as it's just a front-end to slapt-get and > slapt-src and sbopkg is not guilty either. > > I installed insync using slapt-src on Slint. When starting it from a > terminal > the error message is: > > Error loading Python lib '/usr/lib64/insync/libpython3.7m.so.1.0': > dlopen: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by > /usr/lib64/insync/libpython3.7m.so.1.0) > > Indeed Slint64-2.2.1 ships glibc-2.23 (same package as in > Slackware64-14.2) so > I assume that the same issue occurs in Slackware. > > If I am correct, there's nothing simple we can do to fix this issue, as the > repackaged Debian binary bundles a lot of stuff but not glibc. > > Additionally in Slint we ship python3.9 and the python stuff in the > package are > for Python3.7 so this thing wouldn't probably work in Slint anyway (SBo > provides > Python 3.7 instead at time of writing but I chose to update to the major > version > shipped in -current, to avoid upgrading? all Python packages twice from > 3.5 that > we shipped previously). > > I send this email also to the maintainer of insync @ SBo. > > Cheers, > Didier From didier at slint.fr Thu Jul 15 12:54:10 2021 From: didier at slint.fr (Didier Spaier) Date: Thu, 15 Jul 2021 14:54:10 +0200 Subject: [Slackbuilds-users] insync run fails In-Reply-To: <3a3f03e6-0994-9cbc-bfb2-429699e06363@slint.fr> References: <0a97ec85-54c7-e9e9-fff7-3e439e540fd6@slint.fr> <3a3f03e6-0994-9cbc-bfb2-429699e06363@slint.fr> Message-ID: <733e5e5d-b93b-9464-15ef-57997dfc9c88@slint.fr> Le 15/07/2021 ? 14:20, Didier Spaier a ?crit : > PS: forwarding to Christopher who last updated the SlackBuild. > > I will downgrade the source to the previousli shipped version and see > what happens. > My mistake, I didn't realize that this commit: https://git.slackbuilds.org/slackbuilds/commit/?h=14.2&id=fc55f7ff63a9232601984eefff4f34c505e8e636 was not yet applied as this dircetory: http://slackbuilds.org/repository/14.2/network/insync/ is for version 3.1.3.40790 Applying the commit works in Slint: at least the GUI starts. Sorry for the confusion Cheers, Didier From dwells at alfavinil.com Thu Jul 15 19:46:53 2021 From: dwells at alfavinil.com (David Wells) Date: Thu, 15 Jul 2021 16:46:53 -0300 Subject: [Slackbuilds-users] libosinfo-1.8.0 build problems In-Reply-To: <23153640-8c19-e1f3-721f-d7a5e41458be@slackbuilds.org> References: <91f8d5d4-ef97-29ed-48ea-dcb59657db80@alfavinil.com> <23153640-8c19-e1f3-721f-d7a5e41458be@slackbuilds.org> Message-ID: El 14/7/2021 a las 21:19, Willy Sudiarto Raharjo escribi?: >> I seem to have found the culprit. I downgraded meson from 0.57.1 to >> 0.55.3 which I had laying around from a previous install and it compiled >> without a problem. Is there anything that could be done to compile using >> the most recent version of meson? > Is this on 14.2 or in -current? > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > 14.2, haven't compiled anything from slackbuilds yet in current. From kingbeowulf at gmail.com Fri Jul 16 03:20:55 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 15 Jul 2021 20:20:55 -0700 Subject: [Slackbuilds-users] (no subject) Message-ID: <59c9a6e2-32b7-f76d-469a-b5dddaa5e5fb@gmail.com> hello roccat-tools-5.9 does not detect 'lua' correctly. The stanza LUAVERSION="$( lua -e 'print(_VERSION)' | cut -d' ' -f2 )" LUA="-DWITH_LUA='$LUAVERSION' breaks with lua 5.2.x and lua 5.3.x since there is no 'lua' executable: # lua -e 'print(_VERSION)' -su: lua: command not found My temporary solution is to explicitly require lua53 and set LUA="-DWITH_LUA='5.3' as per the roccat-tools INSTALL, or create lua -> lua5.3 symlink. Since supported versions are lua-5.1 and higher, the buildscript should allow newer lua, especially for those of us who do not what to pollute or installation with unneeded packages. -ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From rworkman at slackbuilds.org Fri Jul 16 04:54:50 2021 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 15 Jul 2021 23:54:50 -0500 Subject: [Slackbuilds-users] rc scripts with -current In-Reply-To: <20210705121204.25a5e52d@kiwi.kuchen> References: <20210705121204.25a5e52d@kiwi.kuchen> Message-ID: <20210715235450.1b2dea9f@home.rlworkman.net> On Mon, 5 Jul 2021 12:12:04 +0200 Ruben Schuller wrote: > hi! > > i'm not sure if this observation is correct (or already was discussed > here), but rc scripts may have to be modified for -current as /var/run > isn't persistent anymore. a tmpfs is mounted to /run and this in turn > is bind mounted to /var/run in rc.S: > > # If /run exists, mount a tmpfs on it (unless the > # initrd has already done so): > if [ -d /run ]; then > if ! grep -wq "tmpfs /run tmpfs" /proc/mounts ; then > /sbin/mount -v -n -t tmpfs tmpfs /run -o > mode=0755,size=32M,nodev,nosuid,noexec fi > # Make sure that mounts below /run are visible in both /run > and /var/run: /sbin/mount --make-shared /run > fi > > and > > # Bind mount /run to /var/run: > mount -o bind /run /var/run > > the rc scripts of daemons included in slackware have been changed > accordingly, e.g. rc.bind: > > bind_start() { > # Make sure /var/run/named exists: > mkdir -p /var/run/named > > some programs may create their directory themselves (like mariadb > seems to do), others will complain on startup if it doesn't exist. in > any case, installing /var/run/$name via a package is lost after > reboot. > > i think it usually is enough to just create the directory like it's > done in rc.bind. Yes, this issue is quite valid, and the solution isn't always as easy as what was done in rc.bind, unfortunately. I'm (SLOWLY) working through the ones that I know about and/or the ones that are easily findable with a grep. We'll be happy to review pull requests and/or patches to any of them that you happen to notice. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From christopher.duston at protonmail.com Fri Jul 16 14:44:00 2021 From: christopher.duston at protonmail.com (Christopher L Duston) Date: Fri, 16 Jul 2021 14:44:00 +0000 Subject: [Slackbuilds-users] insync run fails In-Reply-To: <733e5e5d-b93b-9464-15ef-57997dfc9c88@slint.fr> References: <0a97ec85-54c7-e9e9-fff7-3e439e540fd6@slint.fr> <3a3f03e6-0994-9cbc-bfb2-429699e06363@slint.fr> <733e5e5d-b93b-9464-15ef-57997dfc9c88@slint.fr> Message-ID: Was that a mistake on my end? I am a pretty newb user of Git. Should I have done something else with that commit? Sent with ProtonMail Secure Email. ??????? Original Message ??????? On Thursday, July 15th, 2021 at 8:54 AM, Didier Spaier wrote: > Le 15/07/2021 ? 14:20, Didier Spaier a ?crit : > > > PS: forwarding to Christopher who last updated the SlackBuild. > > > I will downgrade the source to the previousli shipped version and see > > > what happens. > > My mistake, I didn't realize that > > this commit: > > https://git.slackbuilds.org/slackbuilds/commit/?h=14.2&id=fc55f7ff63a9232601984eefff4f34c505e8e636 > > was not yet applied as this dircetory: > > http://slackbuilds.org/repository/14.2/network/insync/ > > is for version 3.1.3.40790 > > Applying the commit works in Slint: > > at least the GUI starts. > > Sorry for the confusion > > Cheers, > > Didier From sb at rbn.im Fri Jul 16 20:48:01 2021 From: sb at rbn.im (Ruben Schuller) Date: Fri, 16 Jul 2021 22:48:01 +0200 Subject: [Slackbuilds-users] rc scripts with -current In-Reply-To: <20210715235450.1b2dea9f@home.rlworkman.net> References: <20210705121204.25a5e52d@kiwi.kuchen> <20210715235450.1b2dea9f@home.rlworkman.net> Message-ID: <20210716224801.1681c017@kiwi.kuchen> 2021-07-15 Robby Workman : > On Mon, 5 Jul 2021 12:12:04 +0200 > Ruben Schuller wrote: > > > hi! > > > > i'm not sure if this observation is correct (or already was > > discussed here), but rc scripts may have to be modified for > > -current as /var/run isn't persistent anymore. a tmpfs is mounted > > to /run and this in turn is bind mounted to /var/run in rc.S: > > > > # If /run exists, mount a tmpfs on it (unless the > > # initrd has already done so): > > if [ -d /run ]; then > > if ! grep -wq "tmpfs /run tmpfs" /proc/mounts ; then > > /sbin/mount -v -n -t tmpfs tmpfs /run -o > > mode=0755,size=32M,nodev,nosuid,noexec fi > > # Make sure that mounts below /run are visible in both > > /run and /var/run: /sbin/mount --make-shared /run > > fi > > > > and > > > > # Bind mount /run to /var/run: > > mount -o bind /run /var/run > > > > the rc scripts of daemons included in slackware have been changed > > accordingly, e.g. rc.bind: > > > > bind_start() { > > # Make sure /var/run/named exists: > > mkdir -p /var/run/named > > > > some programs may create their directory themselves (like mariadb > > seems to do), others will complain on startup if it doesn't exist. > > in any case, installing /var/run/$name via a package is lost after > > reboot. > > > > i think it usually is enough to just create the directory like it's > > done in rc.bind. > > > Yes, this issue is quite valid, and the solution isn't always as > easy as what was done in rc.bind, unfortunately. > > I'm (SLOWLY) working through the ones that I know about and/or > the ones that are easily findable with a grep. > > We'll be happy to review pull requests and/or patches to any of > them that you happen to notice. > > -RW Ok, I'll send follow ups with patches for things I've already found! Ruben From sb at rbn.im Fri Jul 16 21:22:29 2021 From: sb at rbn.im (Ruben Schuller) Date: Fri, 16 Jul 2021 23:22:29 +0200 Subject: [Slackbuilds-users] rc scripts with -current In-Reply-To: <20210716224801.1681c017@kiwi.kuchen> References: <20210705121204.25a5e52d@kiwi.kuchen> <20210715235450.1b2dea9f@home.rlworkman.net> <20210716224801.1681c017@kiwi.kuchen> Message-ID: <20210716232229.6f7d76f4@kiwi.kuchen> 2021-07-16 Ruben Schuller : > > Ok, I'll send follow ups with patches for things I've already found! > > Ruben Attached are patches for three things I use, murmur, rspamd and yadifa. All patches are rather similar: Adding a check to create the respective directory in /var/run (or /run) to the rc script and removing creation of /var/run/$PRGNAM for the package. (CC Ebben Aries, Edward W. Koenig and Sergei Fedosoff) -------------- next part -------------- A non-text attachment was scrubbed... Name: rspamd.patch Type: text/x-patch Size: 1031 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: yadifa.patch Type: text/x-patch Size: 1071 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: murmur.patch Type: text/x-patch Size: 1353 bytes Desc: not available URL: From rworkman at slackbuilds.org Sat Jul 17 03:12:37 2021 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 16 Jul 2021 22:12:37 -0500 Subject: [Slackbuilds-users] rc scripts with -current In-Reply-To: <20210716232229.6f7d76f4@kiwi.kuchen> References: <20210705121204.25a5e52d@kiwi.kuchen> <20210715235450.1b2dea9f@home.rlworkman.net> <20210716224801.1681c017@kiwi.kuchen> <20210716232229.6f7d76f4@kiwi.kuchen> Message-ID: <20210716221237.65fba897@home.rlworkman.net> On Fri, 16 Jul 2021 23:22:29 +0200 Ruben Schuller wrote: > 2021-07-16 Ruben Schuller : > > > > Ok, I'll send follow ups with patches for things I've already found! > > > > Ruben > > Attached are patches for three things I use, murmur, rspamd and > yadifa. All patches are rather similar: Adding a check to create the > respective directory in /var/run (or /run) to the rc script and > removing creation of /var/run/$PRGNAM for the package. > > (CC Ebben Aries, Edward W. Koenig and Sergei Fedosoff) rspamd patch merged locally. Do you actually use this one? If so, can you advise if a logrotate file is installed with the package? There are three examples included with the source tarball: $ find . -name "*logrotate*" ./debian/rspamd.logrotate ./centos/sources/rspamd.logrotate ./centos/sources/rspamd.logrotate.systemd Does one of these get installed? If so, then we need to patch that one to account for /var/log/rspamd/ being owned by a non-root user. If the package does not have a logrotate file, then we need to install one and account for the ownership of /var/log/rspamd/ -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sun Jul 18 02:53:07 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 17 Jul 2021 19:53:07 -0700 Subject: [Slackbuilds-users] recent rc.murmur 'Create piddir during init' patch Message-ID: Hello the patch needs to not explicitly use the default murmur:murmur since this can be altered during build (see README) + chown murmur:murmur $(dirname $PIDFILE) to + chown @USER@:@GROUP@ $(dirname $PIDFILE) with corresponding added 'sed' and removal of '-e "s,pidfile=.*,pidfile=/var/run/$PRGNAM/$PRGNAM.pid," in buildscript since that one is created in the rc. I'll do a fix either tonight of tomorrow, unless someone gets to it first. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From rworkman at slackbuilds.org Sun Jul 18 03:23:34 2021 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 17 Jul 2021 22:23:34 -0500 Subject: [Slackbuilds-users] recent rc.murmur 'Create piddir during init' patch In-Reply-To: References: Message-ID: <20210717222334.1ee3e2bb@home.rlworkman.net> On Sat, 17 Jul 2021 19:53:07 -0700 King Beowulf wrote: > Hello > > the patch needs to not explicitly use the default murmur:murmur since > this can be altered during build (see README) > > + chown murmur:murmur $(dirname $PIDFILE) > > to > > + chown @USER@:@GROUP@ $(dirname $PIDFILE) > > with corresponding added 'sed' and removal of > '-e "s,pidfile=.*,pidfile=/var/run/$PRGNAM/$PRGNAM.pid," > in buildscript since that one is created in the rc. > > I'll do a fix either tonight of tomorrow, unless someone gets to it > first. I did a fixup on the commit since it's still in my branch instead of master; see if it looks okay now. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From slackbuilds at schoepfer.info Sun Jul 18 21:24:10 2021 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 18 Jul 2021 23:24:10 +0200 Subject: [Slackbuilds-users] Texlive 2021 -extra/-docs Message-ID: <7182fe11d621024faf87e3edcd73c6a0@schoepfer.info> Hello, i know submissions are closed, but just in case if someone wants to put them up anyway, see my post on lq https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/page532.html#post6267554 for the texlive 2021 -extra/-docs updates. If that happens, please remove texlive-base as it seems it will be part of slackware 15.0. Johannes From matteo.bernardini at gmail.com Mon Jul 19 05:39:21 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 19 Jul 2021 07:39:21 +0200 Subject: [Slackbuilds-users] Texlive 2021 -extra/-docs In-Reply-To: <7182fe11d621024faf87e3edcd73c6a0@schoepfer.info> References: <7182fe11d621024faf87e3edcd73c6a0@schoepfer.info> Message-ID: hi Johannes, I was about to push both but I noticed that $VERSION in the texlive-*.SlackBuild is defined dinamically based on $TEXMFVERSION: it's ok if we define it directly as 2021.210418 so that is consistent also with the texlive-*.info files? thanks for the updated scripts! Matteo Il giorno dom 18 lug 2021 alle ore 23:24 Franzen via SlackBuilds-users ha scritto: > > Hello, > > i know submissions are closed, but just in case if someone wants to put > them up anyway, > see my post on lq > https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/page532.html#post6267554 > for the texlive 2021 -extra/-docs updates. > If that happens, please remove texlive-base as it seems it will be part > of slackware 15.0. > > Johannes > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From slackbuilds at schoepfer.info Mon Jul 19 06:36:03 2021 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 19 Jul 2021 08:36:03 +0200 Subject: [Slackbuilds-users] Texlive 2021 -extra/-docs In-Reply-To: References: <7182fe11d621024faf87e3edcd73c6a0@schoepfer.info> Message-ID: <0bc5b5605f3fe6921f07aaf115df9997@schoepfer.info> Hi Matteo, > I was about to push both but I noticed that $VERSION in the > texlive-*.SlackBuild is defined dinamically based on $TEXMFVERSION: > it's ok if we define it directly as 2021.210418 so that is consistent > also with the texlive-*.info files? Sure, didn't thought about that. $TEXMFVERSION needs to stay( then maybe set by $VERSION and strip away 2021 with some sed foo), as the tarball doesn't contain YYYY anymore. Johannes From matteo.bernardini at gmail.com Mon Jul 19 07:36:29 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 19 Jul 2021 09:36:29 +0200 Subject: [Slackbuilds-users] Texlive 2021 -extra/-docs In-Reply-To: <0bc5b5605f3fe6921f07aaf115df9997@schoepfer.info> References: <7182fe11d621024faf87e3edcd73c6a0@schoepfer.info> <0bc5b5605f3fe6921f07aaf115df9997@schoepfer.info> Message-ID: please have a look at my branch if it's all ok! https://git.slackbuilds.org/slackbuilds/log/?h=user/ponce/updates Matteo Il giorno lun 19 lug 2021 alle ore 08:36 Franzen via SlackBuilds-users ha scritto: > > Hi Matteo, > > > I was about to push both but I noticed that $VERSION in the > > texlive-*.SlackBuild is defined dinamically based on $TEXMFVERSION: > > it's ok if we define it directly as 2021.210418 so that is consistent > > also with the texlive-*.info files? > > Sure, didn't thought about that. > $TEXMFVERSION needs to stay( then maybe set by $VERSION and strip away > 2021 with some sed foo), as the tarball doesn't contain YYYY anymore. > > Johannes > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From slackbuilds at schoepfer.info Mon Jul 19 07:47:42 2021 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 19 Jul 2021 09:47:42 +0200 Subject: [Slackbuilds-users] Texlive 2021 -extra/-docs In-Reply-To: References: <7182fe11d621024faf87e3edcd73c6a0@schoepfer.info> <0bc5b5605f3fe6921f07aaf115df9997@schoepfer.info> Message-ID: <16d83712cb12b857be2ae15374186e1f@schoepfer.info> On 2021-07-19 09:36, Matteo Bernardini wrote: > please have a look at my branch if it's all ok! > > https://git.slackbuilds.org/slackbuilds/log/?h=user/ponce/updates Looks good to me, thanks! Johannes From kingbeowulf at gmail.com Mon Jul 19 23:41:30 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 19 Jul 2021 16:41:30 -0700 Subject: [Slackbuilds-users] recent rc.murmur 'Create piddir during init' patch In-Reply-To: <20210717222334.1ee3e2bb@home.rlworkman.net> References: <20210717222334.1ee3e2bb@home.rlworkman.net> Message-ID: <7687203a-eec9-90e4-1af5-c483b6536851@gmail.com> On 7/17/21 8:23 PM, Robby Workman wrote: > On Sat, 17 Jul 2021 19:53:07 -0700 > King Beowulf wrote: > >> Hello >> >> the patch needs to not explicitly use the default murmur:murmur since >> this can be altered during build (see README) >> >> + chown murmur:murmur $(dirname $PIDFILE) >> > > I did a fixup on the commit since it's still in my branch > instead of master; see if it looks okay now. > > -RW > All systems nominal. Thanks. I ended up taking a nap and then forgot all about it. No like anyone logs into my murmur server! -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From alik at ejik.org Wed Jul 21 00:08:48 2021 From: alik at ejik.org (Alexander Verbovetsky) Date: Wed, 21 Jul 2021 03:08:48 +0300 Subject: [Slackbuilds-users] libbson Message-ID: <436671626824154@mail.yandex.ru> An HTML attachment was scrubbed... URL: From skaendo at linuxmail.org Fri Jul 30 00:41:40 2021 From: skaendo at linuxmail.org (Edward Ender) Date: Fri, 30 Jul 2021 02:41:40 +0200 Subject: [Slackbuilds-users] Giving up 2 SlackBuilds Message-ID: An HTML attachment was scrubbed... URL: From skaendo at linuxmail.org Fri Jul 30 00:43:32 2021 From: skaendo at linuxmail.org (Edward Ender) Date: Fri, 30 Jul 2021 02:43:32 +0200 Subject: [Slackbuilds-users] Questions about SlackBuild licenses Message-ID: An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Fri Jul 30 01:38:19 2021 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 30 Jul 2021 02:38:19 +0100 Subject: [Slackbuilds-users] Questions about SlackBuild licenses In-Reply-To: References: Message-ID: <20210730013818.GA27923@localhost> On 30/07/21 02:43, Edward Ender put forth the proposition: > I know that each SlackBuild must include a license block, but what about these off-brand licenses like WTFPL, etc? > Are these legit or should they be changed to the MIT-style block? > Is there a list of "accepted" licenses? Or should they just follow the OSI standards? > Thanks, > Ed Ben / Urchlay uses WTFPL so I assume any off-brand is OK. We don't have a list of accepted licenses that I know about. -- Dave From joshuakwood at gmail.com Fri Jul 30 02:26:04 2021 From: joshuakwood at gmail.com (JK Wood) Date: Thu, 29 Jul 2021 21:26:04 -0500 Subject: [Slackbuilds-users] Questions about SlackBuild licenses In-Reply-To: <20210730013818.GA27923@localhost> References: <20210730013818.GA27923@localhost> Message-ID: On Thu, Jul 29, 2021, 20:38 Dave Woodfall wrote: > On 30/07/21 02:43, > Edward Ender put forth the proposition: > > I know that each SlackBuild must include a license block, but what > about these off-brand licenses like WTFPL, etc? > > Are these legit or should they be changed to the MIT-style block? > > Is there a list of "accepted" licenses? Or should they just follow > the OSI standards? > > Thanks, > > Ed > > Ben / Urchlay uses WTFPL so I assume any off-brand is OK. We don't > have a list of accepted licenses that I know about. > > -- > Dave > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ My understanding is that the licenses have to ensure the rights of the end user to modify them. Public domain does not exist in all jurisdictions, so the license has to specifically give rights to the end user to ensure that it's useable everywhere by everyone. See any of my SlackBuilds for pretty much the minimal acceptable license. --JK > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alik at ejik.org Sat Jul 31 13:00:15 2021 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 31 Jul 2021 16:00:15 +0300 Subject: [Slackbuilds-users] pdfstudio and pdfstudioviewer up for grabs In-Reply-To: References: <58bba8b2-9d27-466b-8e9b-9c462ee7fad8@www.fastmail.com> <25f5b49-8de0-8585-22c1-27ed54a65da1@beingboiled.info> <850211624965775@mail.yandex.ru> Message-ID: <580031627735255@mail.yandex.ru> An HTML attachment was scrubbed... URL: From lists at osh.id.au Sat Jul 31 14:43:37 2021 From: lists at osh.id.au (David O'Shaughnessy) Date: Sat, 31 Jul 2021 22:43:37 +0800 Subject: [Slackbuilds-users] pdfstudio and pdfstudioviewer up for grabs In-Reply-To: <580031627735255@mail.yandex.ru> References: <58bba8b2-9d27-466b-8e9b-9c462ee7fad8@www.fastmail.com> <25f5b49-8de0-8585-22c1-27ed54a65da1@beingboiled.info> <850211624965775@mail.yandex.ru> <580031627735255@mail.yandex.ru> Message-ID: On Sat, 31 Jul 2021, at 9:00 PM, Alexander Verbovetsky wrote: > They (the pdfstudio upstream) changed their minds and published .debs > for 64 bit version of pdfstudio and the viewer. (Probably, the Arch > developers were able to convince them.) > > Hence, I will continue to maintain pdfstudio and pdfstudioviewer > SlackBuilds. Great! (I emailed them too asking about an alternative packaging format rather than a point and click installer). Although, where exactly is the .deb? I can't see any link on the download page (https://www.qoppa.com/pdfstudio/download/) now that 2021 has been released. -- Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From alik at ejik.org Sat Jul 31 15:42:49 2021 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 31 Jul 2021 18:42:49 +0300 Subject: [Slackbuilds-users] pdfstudio and pdfstudioviewer up for grabs In-Reply-To: References: <58bba8b2-9d27-466b-8e9b-9c462ee7fad8@www.fastmail.com> <25f5b49-8de0-8585-22c1-27ed54a65da1@beingboiled.info> <850211624965775@mail.yandex.ru> <580031627735255@mail.yandex.ru> Message-ID: <619941627745727@mail.yandex.ru> An HTML attachment was scrubbed... URL: