From 1.41421 at gmail.com Tue May 1 00:07:02 2018 From: 1.41421 at gmail.com (JCA) Date: Mon, 30 Apr 2018 18:07:02 -0600 Subject: [Slackbuilds-users] ffmpeg not building Message-ID: I tried building ffmpeg with all the optional dependencies enabled. Here is where I am getting stuck: In file included from /usr/include/fribidi/fribidi.h:37:0, from libavfilter/vf_drawtext.c:65: /usr/include/fribidi/fribidi-unicode.h:46:5: warning: "DONT_HAVE_FRIBIDI_UNICODE_VERSION_H" is not defined [-Wundef] #if DONT_HAVE_FRIBIDI_UNICODE_VERSION_H+0 ^ In file included from libavfilter/vf_drawtext.c:65:0: /usr/include/fribidi/fribidi.h:54:5: warning: "FRIBIDI_NO_DEPRECATED" is not defined [-Wundef] #if FRIBIDI_NO_DEPRECATED+0 ^ CC libavfilter/vf_edgedetect.o CC libavfilter/vf_elbg.o CC libavfilter/vf_eq.o CC libavfilter/vf_extractplanes.o CC libavfilter/vf_fade.o CC libavfilter/vf_fftfilt.o CC libavfilter/vf_field.o CC libavfilter/vf_fieldhint.o CC libavfilter/vf_fieldmatch.o CC libavfilter/vf_fieldorder.o CC libavfilter/vf_find_rect.o CC libavfilter/vf_format.o CC libavfilter/vf_fps.o CC libavfilter/vf_framepack.o CC libavfilter/vf_framerate.o CC libavfilter/vf_framestep.o CC libavfilter/vf_frei0r.o CC libavfilter/vf_fspp.o CC libavfilter/vf_gblur.o CC libavfilter/vf_geq.o CC libavfilter/vf_gradfun.o CC libavfilter/vf_hflip.o CC libavfilter/vf_histeq.o CC libavfilter/vf_histogram.o CC libavfilter/vf_hqdn3d.o CC libavfilter/vf_hqx.o CC libavfilter/vf_hue.o CC libavfilter/vf_hwdownload.o CC libavfilter/vf_hwupload.o libavfilter/vf_hwupload.c: In function 'hwupload_query_formats': libavfilter/vf_hwupload.c:84:5: warning: ignoring return value of 'ff_formats_ref', declared with attribute warn_unused_result [-Wunused-result] ff_formats_ref(input_formats, &avctx->inputs[0]->out_formats); ^ libavfilter/vf_hwupload.c:86:5: warning: ignoring return value of 'ff_formats_ref', declared with attribute warn_unused_result [-Wunused-result] ff_formats_ref(ff_make_format_list(output_pix_fmts), ^ CC libavfilter/vf_hysteresis.o CC libavfilter/vf_idet.o CC libavfilter/vf_il.o CC libavfilter/vf_interlace.o CC libavfilter/vf_kerndeint.o CC libavfilter/vf_lenscorrection.o CC libavfilter/vf_libopencv.o In file included from /usr/include/opencv2/core/types_c.h:59:0, from /usr/include/opencv2/core/core_c.h:48, from libavfilter/vf_libopencv.c:28: /usr/include/opencv2/core/cvdef.h:485:1: error: unknown type name 'namespace' namespace cv { ^ /usr/include/opencv2/core/cvdef.h:485:14: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token namespace cv { ^ common.mak:60: recipe for target 'libavfilter/vf_libopencv.o' failed make: *** [libavfilter/vf_libopencv.o] Error 1 ffmpeg: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. (Y)es to continue, (N)o to abort, (R)etry the build?: -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Tue May 1 01:11:24 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 1 May 2018 11:11:24 +1000 Subject: [Slackbuilds-users] ffmpeg not building In-Reply-To: References: Message-ID: <5eee649b-fb9d-607a-c6e7-9eaf961d607b@iinet.net.au> On 01/05/18 10:07, JCA wrote: [snip] > CClibavfilter/vf_libopencv.o > In file included from /usr/include/opencv2/core/types_c.h:59:0, > ? ? ? ? ? ? ? ? ?from /usr/include/opencv2/core/core_c.h:48, > ? ? ? ? ? ? ? ? ?from libavfilter/vf_libopencv.c:28: > /usr/include/opencv2/core/cvdef.h:485:1: error: unknown type name > 'namespace' > ?namespace cv { > ?^ > /usr/include/opencv2/core/cvdef.h:485:14: error: expected '=', ',', ';', > 'asm' or '__attribute__' before '{' token > ?namespace cv { > ? ? ? ? ? ? ? ^ > common.mak:60: recipe for target 'libavfilter/vf_libopencv.o' failed > make: *** [libavfilter/vf_libopencv.o] Error 1 > This has been raised previously and a fix suggested. I was going to update the SlackBuild to apply the appropriate patch but have since forgotten about it. Sorry about that - I will definitely do it this week. In the meantime the fix (found by Ythogtha on this list) is at: https://github.com/opencv/opencv/issues/10963 chris From chris.willing at iinet.net.au Tue May 1 06:22:17 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 1 May 2018 16:22:17 +1000 Subject: [Slackbuilds-users] ffmpeg not building In-Reply-To: <5eee649b-fb9d-607a-c6e7-9eaf961d607b@iinet.net.au> References: <5eee649b-fb9d-607a-c6e7-9eaf961d607b@iinet.net.au> Message-ID: <3ecfcbd7-9df2-e916-f14b-f4fd5414c65a@iinet.net.au> On 01/05/18 11:11, Christoph Willing wrote: > On 01/05/18 10:07, JCA wrote: > [snip] >> CClibavfilter/vf_libopencv.o >> In file included from /usr/include/opencv2/core/types_c.h:59:0, >> ? ? ? ? ? ? ? ? ?from /usr/include/opencv2/core/core_c.h:48, >> ? ? ? ? ? ? ? ? ?from libavfilter/vf_libopencv.c:28: >> /usr/include/opencv2/core/cvdef.h:485:1: error: unknown type name >> 'namespace' >> ?namespace cv { >> ?^ >> /usr/include/opencv2/core/cvdef.h:485:14: error: expected '=', ',', ';', >> 'asm' or '__attribute__' before '{' token >> ?namespace cv { >> ? ? ? ? ? ? ? ^ >> common.mak:60: recipe for target 'libavfilter/vf_libopencv.o' failed >> make: *** [libavfilter/vf_libopencv.o] Error 1 >> > > This has been raised previously and a fix suggested. I was going to > update the SlackBuild to apply the appropriate patch but have since > forgotten about it. Sorry about that - I will definitely do it this week. > > In the meantime the fix (found by Ythogtha on this > list) is at: > https://github.com/opencv/opencv/issues/10963 > I've pushed the updated version so it will be part of the next release, probably at the weekend. Until then, it's available at: https://git.slackbuilds.org/slackbuilds/tree/libraries/opencv?h=user/chris.willing/updates I used the resulting patched opencv to do a test build of ffmpeg (with OPENCV=yes) and it all seemed to go OK: CC libavfilter/vf_il.o CC libavfilter/vf_interlace.o CC libavfilter/vf_kerndeint.o CC libavfilter/vf_lenscorrection.o CC libavfilter/vf_libopencv.o CC libavfilter/vf_lut.o CC libavfilter/vf_lut2.o CC libavfilter/vf_lut3d.o (etc.) chris From 1.41421 at gmail.com Tue May 1 14:13:34 2018 From: 1.41421 at gmail.com (JCA) Date: Tue, 1 May 2018 08:13:34 -0600 Subject: [Slackbuilds-users] perl-Try-Tiny and decklink-sdk not working Message-ID: The Slackbuilds script expects version 0.28 by default, a version that has already been superseded by version 0.29. Straightforward to work around, but I thought I'd let you guys know. As for decklink-sdk, the sources that it tries to download are not available at the repository. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue May 1 17:30:34 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 2 May 2018 00:30:34 +0700 Subject: [Slackbuilds-users] perl-Try-Tiny and decklink-sdk not working In-Reply-To: References: Message-ID: <9db5f93a-22d1-067a-3c88-95105292d375@slackbuilds.org> > As for decklink-sdk, the sources that it tries to download are not > available at the repository. Please read the README. It has been clearly described how to get the source for decklink-sdk -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From 1.41421 at gmail.com Tue May 1 18:17:11 2018 From: 1.41421 at gmail.com (JCA) Date: Tue, 1 May 2018 12:17:11 -0600 Subject: [Slackbuilds-users] perl-Try-Tiny and decklink-sdk not working In-Reply-To: <9db5f93a-22d1-067a-3c88-95105292d375@slackbuilds.org> References: <9db5f93a-22d1-067a-3c88-95105292d375@slackbuilds.org> Message-ID: So it does. My apologies. On Tue, May 1, 2018 at 11:30 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > As for decklink-sdk, the sources that it tries to download are not > > available at the repository. > > Please read the README. > It has been clearly described how to get the source for decklink-sdk > > > -- > 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 jbernts at broadpark.no Tue May 1 19:41:24 2018 From: jbernts at broadpark.no (Jostein Berntsen) Date: Tue, 1 May 2018 21:41:24 +0200 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: References: Message-ID: <20180501194124.GA12307@jbsupah> On 31.10.17,03:43, Daniel Prosser wrote: > Trying to submit an update to one of my SlackBuilds, I get this error: > > ***** > [my email address] was rejected by mx2.hotmail.com. > Go back and enter a valid E-Mail address. > > If your mailserver uses Greylisting you may want to Whitelist > slackbuilds-users at slackbuilds.org. > ***** > > I have added slackbuilds-users at slackbuilds.org and also the > slackbuilds.org domain to my safe senders list. Anything else I can do? > This has never happened to me in the past. > I got the same message today for two uploads I tried to do with the Slackbuilds upload form. Output: "jbernts at broadpark.no was rejected by mx1.broadpark.no. Go back and enter a valid E-Mail address. If your mailserver uses Greylisting you may want to Whitelist slackbuilds-users at slackbuilds.org." This is the first time it has happened to me. Inconveniently my mail provider has made a new webmail interface where rules are disables. Any suggestion what to do here? Jostein From rob0 at slackbuilds.org Tue May 1 21:36:13 2018 From: rob0 at slackbuilds.org (Rob McGee) Date: Tue, 1 May 2018 16:36:13 -0500 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: <20180501194124.GA12307@jbsupah> References: <20180501194124.GA12307@jbsupah> Message-ID: <20180501213613.GV5126@harrier.slackbuilds.org> On Tue, May 01, 2018 at 09:41:24PM +0200, Jostein Berntsen wrote: > I got the same message today for two uploads I tried to do with the > Slackbuilds upload form. Output: > > "jbernts at broadpark.no was rejected by mx1.broadpark.no. > Go back and enter a valid E-Mail address. > > If your mailserver uses Greylisting you may want to Whitelist > slackbuilds-users at slackbuilds.org." > > This is the first time it has happened to me. Inconveniently my > mail provider has made a new webmail interface where rules are > disables. Any suggestion what to do here? Sometimes greylisting can be bypassed by retrying the submission in 5 minutes. Depends what greylisting implementation is in use and how it was configured, of course. Other suggestion (which IIRC was also mentioned in this thread) is that you use some other non-greylisted address for SBo submissions. You can still keep your @broadpark.no address in the INFO file. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From slackalaxy at gmail.com Wed May 2 12:51:35 2018 From: slackalaxy at gmail.com (Petar Petrov) Date: Wed, 2 May 2018 15:51:35 +0300 Subject: [Slackbuilds-users] Rename muParser to muparser Message-ID: > May I suggest renaming muParser to muparser? I don't mind renaming, but: 1. This will happen only upon update submission. 2. Everything that depends on muParser should have their info files updated. So, is it really worth it? > Alien Bob's package is named muparser, and package manage tools (like > slackpkgplus) work better if different packages of the same program > have the same name. It is a different repo. Until we agree on a single unified repository for Slackware packages/SlackBuilds, issues like this will exist. So, short answer is: no, I will probably not change the name. -petar From didier at slint.fr Wed May 2 18:47:18 2018 From: didier at slint.fr (Didier Spaier) Date: Wed, 2 May 2018 20:47:18 +0200 Subject: [Slackbuilds-users] Wrong symlinks in packages Message-ID: <103b84e4-3756-664d-a101-312953cbdb20@slint.fr> Hello, Today someone nicknamed Jardenblack posted this in a Salix forum: [quoted post] Here is a list of packages that have bad soft links and need to be fixed: fvwm95-2.0.43f-i486-2salix HawkNL-1.68-i486-1salix http-parser-2.7.1-i486-1salix libiptcdata-1.0.4-i486-2salix oss-4.2.2011-i586-1salix PDCurses-3.4-i486-1salix qt3-3.3.8b-i486-5salix example of the problem: ( cd usr/lib ; ln -sf /usr/src/slapt-src/libraries/PDCurses/package-PDCurses/usr/lib/libXCurses.so libXpanel.so ) I found this problem searching thur the /var/log/scripts files. I hope this helps. [/quoted post] I couldn't answer because for an unknown reason the thread and the user disappeared. However I had a look at two cases and confirm the issue. For PDCurses the wrong links are mad by by install target in Makefile.in in the source archive as shown below install: ln -f -s $(libdir)/$(SHLPRE)$(SHLFILE)$(SHLPST) \ $(libdir)/$(SHLPRE)Xpanel$(SHLPST) ln -f -s $(libdir)/libXCurses.a $(libdir)/libXpanel.a -$(RANLIB) $(libdir)/libXpanel.a For fvwm95 the wrong link comes from the install target in sample.fvwmrc/Makefile.in in the source archive as sown below: install: ${INSTALL_DATA} ${RC} ${fvwm_dir} ${LN} ${fvwm_dir}/${RC} ${fvwm_dir}/${fvwm_rc} (LN is converted to ln -s during the build) I was too lazy to check the other packages (I don't use any of those listed by Jardenblack) but I assume that other packages have a similar issue, i.e. symlinks from a file in the build dir that will be broken as soon as the build dir is removed. Maybe the broken symlinks do not always hurt but still, a systematic check that the symlinks (in install/doinst.sh or /var/log/scripts) will survive the removal of the build dir could be useful? Best, Didier From pilbender at gmail.com Wed May 2 21:27:37 2018 From: pilbender at gmail.com (Richard Scott Smith) Date: Wed, 2 May 2018 14:27:37 -0700 Subject: [Slackbuilds-users] Samhain Slackbuild Update Message-ID: Long overdue. Also, if there is a better way to submit patches, school me. It's been a loooooong time since I've done this. scott -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Version-bump-for-samhain.patch Type: text/x-patch Size: 1425 bytes Desc: not available URL: From francois.gingras at gmail.com Wed May 2 21:32:19 2018 From: francois.gingras at gmail.com (Francois Gingras) Date: Wed, 02 May 2018 21:32:19 +0000 Subject: [Slackbuilds-users] Wrong symlinks in packages In-Reply-To: <103b84e4-3756-664d-a101-312953cbdb20@slint.fr> References: <103b84e4-3756-664d-a101-312953cbdb20@slint.fr> Message-ID: Wait, why are you asking for help with salix packages on the SBo mailing list? On Wed, May 2, 2018 at 2:47 PM Didier Spaier wrote: > Hello, > > Today someone nicknamed Jardenblack posted this in a Salix forum: > [quoted post] > Here is a list of packages that have bad soft links and need to be fixed: > fvwm95-2.0.43f-i486-2salix > HawkNL-1.68-i486-1salix > http-parser-2.7.1-i486-1salix > libiptcdata-1.0.4-i486-2salix > oss-4.2.2011-i586-1salix > PDCurses-3.4-i486-1salix > qt3-3.3.8b-i486-5salix > > example of the problem: > ( cd usr/lib ; ln -sf > /usr/src/slapt-src/libraries/PDCurses/package-PDCurses/usr/lib/libXCurses.so > libXpanel.so ) > > I found this problem searching thur the /var/log/scripts files. I hope > this helps. > [/quoted post] > > I couldn't answer because for an unknown reason the thread and the user > disappeared. > > However I had a look at two cases and confirm the issue. > For PDCurses the wrong links are mad by by install target in Makefile.in > in the source archive as shown below > install: > > ln -f -s $(libdir)/$(SHLPRE)$(SHLFILE)$(SHLPST) \ > $(libdir)/$(SHLPRE)Xpanel$(SHLPST) > ln -f -s $(libdir)/libXCurses.a $(libdir)/libXpanel.a > -$(RANLIB) $(libdir)/libXpanel.a > For fvwm95 the wrong link comes from the install target in > sample.fvwmrc/Makefile.in in the source archive as sown below: > install: > ${INSTALL_DATA} ${RC} ${fvwm_dir} > ${LN} ${fvwm_dir}/${RC} ${fvwm_dir}/${fvwm_rc} > (LN is converted to ln -s during the build) > > I was too lazy to check the other packages (I don't use any of those > listed by Jardenblack) > but I assume that other packages have a similar issue, i.e. symlinks > from a file in the build dir that will be broken as soon as the build > dir is removed. > > Maybe the broken symlinks do not always hurt but still, a systematic > check that the symlinks (in install/doinst.sh or /var/log/scripts) will > survive the removal of the build dir could be useful? > > Best, > > Didier > _______________________________________________ > 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 didier at slint.fr Wed May 2 21:43:35 2018 From: didier at slint.fr (Didier Spaier) Date: Wed, 2 May 2018 23:43:35 +0200 Subject: [Slackbuilds-users] Wrong symlinks in packages In-Reply-To: References: <103b84e4-3756-664d-a101-312953cbdb20@slint.fr> Message-ID: <57b9db4a-9d29-4d32-dcb5-45cce346201f@slint.fr> Le 02/05/2018 ? 23:32, Francois Gingras a ?crit?: > Wait, why are you asking for help with salix packages on the SBo mailing list? I am not asking for help and the packages tagged salix below are built using SlackBuilds coming from SBo. They are tagged salix because they are stored in a Salix repository and the FAQ says (rule n? 20): "If you do make such a repository available to the public, we request that you change the "SBo" tag in your packages to something else." "We do not want to be associated with 3rd-party package repositories." > On Wed, May 2, 2018 at 2:47 PM Didier Spaier > wrote: > > Hello, > > Today someone nicknamed Jardenblack posted this in a Salix forum: > [quoted post] > Here is a list of packages that have bad soft links and need to be fixed: > fvwm95-2.0.43f-i486-2salix > HawkNL-1.68-i486-1salix > http-parser-2.7.1-i486-1salix > libiptcdata-1.0.4-i486-2salix > oss-4.2.2011-i586-1salix > PDCurses-3.4-i486-1salix > qt3-3.3.8b-i486-5salix > > example of the problem: > ( cd usr/lib ; ln -sf /usr/src/slapt-src/libraries/PDCurses/package-PDCurses/usr/lib/libXCurses.so libXpanel.so ) > > I found this problem searching thur the /var/log/scripts files. I hope this helps. > [/quoted post] > > I couldn't answer because for an unknown reason the thread and the user > disappeared. > > However I had a look at two cases and confirm the issue. > For PDCurses the wrong links are mad by by install target in Makefile.in > in the source archive as shown below > install: > > ? ? ? ? ln -f -s $(libdir)/$(SHLPRE)$(SHLFILE)$(SHLPST) \ > ? ? ? ? ? ? ? ? $(libdir)/$(SHLPRE)Xpanel$(SHLPST) > ? ? ? ? ln -f -s $(libdir)/libXCurses.a $(libdir)/libXpanel.a > ? ? ? ? -$(RANLIB) $(libdir)/libXpanel.a > For fvwm95 the wrong link comes from the install target in > sample.fvwmrc/Makefile.in in the source archive as sown below: > install: > ? ? ? ? ${INSTALL_DATA} ${RC} ${fvwm_dir} > ? ? ? ? ${LN} ${fvwm_dir}/${RC} ${fvwm_dir}/${fvwm_rc} > (LN is converted to ln -s during the build) > > I was too lazy to check the other packages (I don't use any of those > listed by Jardenblack) > but I assume that other packages have a similar issue, i.e. symlinks > from a file in the build dir that will be broken as soon as the build > dir is removed. > > Maybe the broken symlinks do not always hurt but still, a systematic > check that the symlinks (in install/doinst.sh or /var/log/scripts) will > survive the removal of the build dir could be useful? > > Best, > > Didier > _______________________________________________ > 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/ > > > > _______________________________________________ > 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 jbernts at broadpark.no Thu May 3 00:26:45 2018 From: jbernts at broadpark.no (Jostein Berntsen) Date: Thu, 3 May 2018 02:26:45 +0200 Subject: [Slackbuilds-users] Email rejected during submission In-Reply-To: <20180501213613.GV5126@harrier.slackbuilds.org> References: <20180501194124.GA12307@jbsupah> <20180501213613.GV5126@harrier.slackbuilds.org> Message-ID: <20180503002645.GD12307@jbsupah> On 01.05.18,16:36, Rob McGee wrote: > On Tue, May 01, 2018 at 09:41:24PM +0200, Jostein Berntsen wrote: > > I got the same message today for two uploads I tried to do with the > > Slackbuilds upload form. Output: > > > > "jbernts at broadpark.no was rejected by mx1.broadpark.no. > > Go back and enter a valid E-Mail address. > > > > If your mailserver uses Greylisting you may want to Whitelist > > slackbuilds-users at slackbuilds.org." > > > > This is the first time it has happened to me. Inconveniently my > > mail provider has made a new webmail interface where rules are > > disables. Any suggestion what to do here? > > Sometimes greylisting can be bypassed by retrying the submission in 5 > minutes. Depends what greylisting implementation is in use and how > it was configured, of course. > > Other suggestion (which IIRC was also mentioned in this thread) is > that you use some other non-greylisted address for SBo submissions. > You can still keep your @broadpark.no address in the INFO file. > -- I will try the different mail address here, thanks. Jostein From 1.41421 at gmail.com Thu May 3 17:19:46 2018 From: 1.41421 at gmail.com (JCA) Date: Thu, 3 May 2018 11:19:46 -0600 Subject: [Slackbuilds-users] Plex version too old Message-ID: I recently moved my Plex library from a Slack 14.2 box to a Slack64 14.2 system. It is actually exactly the same hardware, from a different hard drive. I therefore installed the plexmediaserver package from slackbuilds.org in my Slack64 14.2. This installs version 1.4.2, while the most recent version seems to be 1.12.3. The problem is that version 1.4.2 does not work in my Slack64 14.2 - in a nutshell, videos cannot be played, because the relevant codecs can't be downloaded by that version of the Plex server. After removing the 1.4.2 version, I proceeded to download and install the 1.12.3 version, by modifying the plexmediaserver.Slackbuild file from slackbuilds.org. With this version, the codecs are automatically downloaded, as they should, and my videos play without a problem. I think that this has already been discussed in this forum, but it may be worth the while bringing it up again: what's the point of keeping a package that leads to a non-working installed software? I understand that, for the sake of a stable system, as Slackware is deservedly reputed to be, having the latest and greatest is probably not always a good idea - although sometimes it may be. This aside, the other side of the coin is that slackbuilds.org packages should result in installed software that works. Should this not be part of the responsibility of package maintainers? I acknowledge that this can be a pain in the neck, but it you can't do so for whatever reason, do not maintain the package. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu May 3 17:24:03 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 4 May 2018 00:24:03 +0700 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: Message-ID: <59971f8e-ebbe-21e7-5ae5-2c4b98ba59ef@slackbuilds.org> > I recently moved my Plex library from a Slack 14.2 box to a Slack64 14.2 > system. It is actually exactly the same hardware, from a different hard > drive. I therefore installed the plexmediaserver package from > slackbuilds.org in my Slack64 14.2. This > installs version 1.4.2, while the most recent version seems to be 1.12.3.? > > The problem is that version 1.4.2 does not work in my Slack64 14.2 - in > a nutshell, videos cannot be played, because the relevant codecs can't > be downloaded by that version of the Plex server. After removing the > 1.4.2 version, I proceeded to download and install the 1.12.3 version, > by modifying the plexmediaserver.Slackbuild file from slackbuilds.org > . With this version, the codecs are > automatically downloaded, as they should, and my videos play without a > problem. > > I think that this has already been discussed in this forum, but it may > be worth the while bringing it up again: what's the point of keeping a > package that leads to a non-working installed software? I understand > that, for the sake of a stable system, as Slackware is? deservedly > reputed to be, having the latest and greatest is probably not always a > good idea - although sometimes it may be. This aside, the other side of > the coin is that slackbuilds.org packages > should result in installed software that works.? > > Should this not be part of the responsibility of package maintainers? I > acknowledge that this can be a pain in the neck, but it you can't do so > for whatever reason, do not maintain the package. Have you tried to contact the maintainer? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From 1.41421 at gmail.com Thu May 3 18:24:42 2018 From: 1.41421 at gmail.com (JCA) Date: Thu, 3 May 2018 12:24:42 -0600 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: <59971f8e-ebbe-21e7-5ae5-2c4b98ba59ef@slackbuilds.org> References: <59971f8e-ebbe-21e7-5ae5-2c4b98ba59ef@slackbuilds.org> Message-ID: I haven't. Past attempts to contact individual maintainers have not been very successful. I'll try anyway. On Thu, May 3, 2018 at 11:24 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > I recently moved my Plex library from a Slack 14.2 box to a Slack64 14.2 > > system. It is actually exactly the same hardware, from a different hard > > drive. I therefore installed the plexmediaserver package from > > slackbuilds.org in my Slack64 14.2. This > > installs version 1.4.2, while the most recent version seems to be > 1.12.3. > > > > The problem is that version 1.4.2 does not work in my Slack64 14.2 - in > > a nutshell, videos cannot be played, because the relevant codecs can't > > be downloaded by that version of the Plex server. After removing the > > 1.4.2 version, I proceeded to download and install the 1.12.3 version, > > by modifying the plexmediaserver.Slackbuild file from slackbuilds.org > > . With this version, the codecs are > > automatically downloaded, as they should, and my videos play without a > > problem. > > > > I think that this has already been discussed in this forum, but it may > > be worth the while bringing it up again: what's the point of keeping a > > package that leads to a non-working installed software? I understand > > that, for the sake of a stable system, as Slackware is deservedly > > reputed to be, having the latest and greatest is probably not always a > > good idea - although sometimes it may be. This aside, the other side of > > the coin is that slackbuilds.org packages > > should result in installed software that works. > > > > Should this not be part of the responsibility of package maintainers? I > > acknowledge that this can be a pain in the neck, but it you can't do so > > for whatever reason, do not maintain the package. > > Have you tried to contact the maintainer? > > > -- > 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 yalhcru at gmail.com Thu May 3 20:51:54 2018 From: yalhcru at gmail.com (B Watson) Date: Thu, 3 May 2018 16:51:54 -0400 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: Message-ID: On 5/3/18, JCA <1.41421 at gmail.com> wrote: > This aside, the other side of the coin is that > slackbuilds.org packages should result in installed software that works. > > Should this not be part of the responsibility of package maintainers? At the time it was submitted, I bet the package worked fine. You're right, the maintainer should be updating it. But, this happens all the time: someone submits a SlackBuild for a piece of software they use, and then a year or two later, they stop using that software for whatever reason... or possibly they stop using Slackware and switch to another OS. If we're very lucky, the maintainer will post a message to this list saying "I'm giving up my builds, here's a list of them". But all too often, it happens silently. The answer is: now that you're using plexmediaserver, you should take over as maintainer. Try to contact the old maintainer first, either to get permission or to verify that they're not responding... if you don't get a response within a few days, post a message to this list announcing you're taking over as maintainer. If you're not willing to step up and be a maintainer, it's not very helpful to say things like this: > I acknowledge that this can be a pain in the neck, but it you can't do so for > whatever reason, do not maintain the package. From 1.41421 at gmail.com Thu May 3 21:34:32 2018 From: 1.41421 at gmail.com (JCA) Date: Thu, 3 May 2018 15:34:32 -0600 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: Message-ID: I am not interested in becoming a package maintainer, in part precisely because I am all too aware of what is involved. I am very thankful that there are people willing to do so. I am merely pointing out that, if they can't or won't do what is concomitant to maintaining a package, they should not volunteer - it is obvious that, if the Slackbuilds packages are poorly maintained, Slackbuilds loses reliability and credibility. On Thu, May 3, 2018 at 2:51 PM, B Watson wrote: > On 5/3/18, JCA <1.41421 at gmail.com> wrote: > > This aside, the other side of the coin is that > > slackbuilds.org packages should result in installed software that works. > > > > Should this not be part of the responsibility of package maintainers? > > At the time it was submitted, I bet the package worked fine. > > You're right, the maintainer should be updating it. But, this happens all > the time: someone submits a SlackBuild for a piece of software they use, > and then a year or two later, they stop using that software for whatever > reason... or possibly they stop using Slackware and switch to another OS. > > If we're very lucky, the maintainer will post a message to this list > saying "I'm giving up my builds, here's a list of them". But all too > often, it happens silently. > > The answer is: now that you're using plexmediaserver, you should take > over as maintainer. Try to contact the old maintainer first, either to > get permission or to verify that they're not responding... if you don't > get a response within a few days, post a message to this list announcing > you're taking over as maintainer. > > If you're not willing to step up and be a maintainer, it's not very > helpful to say things like this: > > > I acknowledge that this can be a pain in the neck, but it you can't do > so for > > whatever reason, do not maintain the package. > _______________________________________________ > 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 andrew at stevens.is Thu May 3 21:49:56 2018 From: andrew at stevens.is (Andrew) Date: Thu, 03 May 2018 17:49:56 -0400 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: Message-ID: <1404jxAiQ2n1cNVZjbBKKfBoSeSHTYxVL4tOG8wSfLeAsL8PbsYnhofzT22kcBJDBpZMd8NxLPJSIyEHVwgWtn5og9wqbNWXpoOEXGvaqp0=@stevens.is> I use and am willing to maintain plexmediaserver if no one has any objections. But unfortunately I won't be able to submit a diff until Saturday if that is alright? Regards, Andrew Stevens andrew at stevens.is ??????? Original Message ??????? On May 4, 2018 9:34 AM, JCA <1.41421 at gmail.com> wrote: > I am not interested in becoming a package maintainer, in part precisely because I am all too aware of what is involved. I am very thankful that there are people willing to do so. I am merely pointing out that, if they can't or won't do what is concomitant to maintaining a package, they should not volunteer - it is obvious that, if the Slackbuilds packages are poorly maintained, Slackbuilds loses reliability and credibility. > > On Thu, May 3, 2018 at 2:51 PM, B Watson wrote: > >> On 5/3/18, JCA <1.41421 at gmail.com> wrote: >>> This aside, the other side of the coin is that >>> slackbuilds.org packages should result in installed software that works. >>> >>> Should this not be part of the responsibility of package maintainers? >> >> At the time it was submitted, I bet the package worked fine. >> >> You're right, the maintainer should be updating it. But, this happens all >> the time: someone submits a SlackBuild for a piece of software they use, >> and then a year or two later, they stop using that software for whatever >> reason... or possibly they stop using Slackware and switch to another OS. >> >> If we're very lucky, the maintainer will post a message to this list >> saying "I'm giving up my builds, here's a list of them". But all too >> often, it happens silently. >> >> The answer is: now that you're using plexmediaserver, you should take >> over as maintainer. Try to contact the old maintainer first, either to >> get permission or to verify that they're not responding... if you don't >> get a response within a few days, post a message to this list announcing >> you're taking over as maintainer. >> >> If you're not willing to step up and be a maintainer, it's not very >> helpful to say things like this: >> >>> I acknowledge that this can be a pain in the neck, but it you can't do so for >>> whatever reason, do not maintain the package. >> _______________________________________________ >> 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 1.41421 at gmail.com Thu May 3 22:49:50 2018 From: 1.41421 at gmail.com (JCA) Date: Thu, 3 May 2018 16:49:50 -0600 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: <1404jxAiQ2n1cNVZjbBKKfBoSeSHTYxVL4tOG8wSfLeAsL8PbsYnhofzT22kcBJDBpZMd8NxLPJSIyEHVwgWtn5og9wqbNWXpoOEXGvaqp0=@stevens.is> References: <1404jxAiQ2n1cNVZjbBKKfBoSeSHTYxVL4tOG8wSfLeAsL8PbsYnhofzT22kcBJDBpZMd8NxLPJSIyEHVwgWtn5og9wqbNWXpoOEXGvaqp0=@stevens.is> Message-ID: Speaking for myself, that would be terrific, and much appreciated. On Thu, May 3, 2018 at 3:49 PM, Andrew wrote: > I use and am willing to maintain plexmediaserver if no one has any > objections. But unfortunately I won't be able to submit a diff until > Saturday if that is alright? > > Regards, > > Andrew Stevens > andrew at stevens.is > > > ??????? Original Message ??????? > On May 4, 2018 9:34 AM, JCA <1.41421 at gmail.com> wrote: > > I am not interested in becoming a package maintainer, in part precisely > because I am all too aware of what is involved. I am very thankful that > there are people willing to do so. I am merely pointing out that, if they > can't or won't do what is concomitant to maintaining a package, they should > not volunteer - it is obvious that, if the Slackbuilds packages are poorly > maintained, Slackbuilds loses reliability and credibility. > > On Thu, May 3, 2018 at 2:51 PM, B Watson wrote: > >> On 5/3/18, JCA <1.41421 at gmail.com> wrote: >> > This aside, the other side of the coin is that >> > slackbuilds.org packages should result in installed software that >> works. >> > >> > Should this not be part of the responsibility of package maintainers? >> >> At the time it was submitted, I bet the package worked fine. >> >> You're right, the maintainer should be updating it. But, this happens all >> the time: someone submits a SlackBuild for a piece of software they use, >> and then a year or two later, they stop using that software for whatever >> reason... or possibly they stop using Slackware and switch to another OS. >> >> If we're very lucky, the maintainer will post a message to this list >> saying "I'm giving up my builds, here's a list of them". But all too >> often, it happens silently. >> >> The answer is: now that you're using plexmediaserver, you should take >> over as maintainer. Try to contact the old maintainer first, either to >> get permission or to verify that they're not responding... if you don't >> get a response within a few days, post a message to this list announcing >> you're taking over as maintainer. >> >> If you're not willing to step up and be a maintainer, it's not very >> helpful to say things like this: >> >> > I acknowledge that this can be a pain in the neck, but it you can't do >> so for >> > whatever reason, do not maintain the package. >> _______________________________________________ >> 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/ >> >> > > _______________________________________________ > 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 thumbs at apache.org Wed May 2 21:29:45 2018 From: thumbs at apache.org (Frank Gingras) Date: Wed, 02 May 2018 21:29:45 +0000 Subject: [Slackbuilds-users] Wrong symlinks in packages In-Reply-To: <103b84e4-3756-664d-a101-312953cbdb20@slint.fr> References: <103b84e4-3756-664d-a101-312953cbdb20@slint.fr> Message-ID: Wait, why are you asking for help with salix packages on the SBo mailing list? On Wed, May 2, 2018 at 2:47 PM Didier Spaier wrote: > Hello, > > Today someone nicknamed Jardenblack posted this in a Salix forum: > [quoted post] > Here is a list of packages that have bad soft links and need to be fixed: > fvwm95-2.0.43f-i486-2salix > HawkNL-1.68-i486-1salix > http-parser-2.7.1-i486-1salix > libiptcdata-1.0.4-i486-2salix > oss-4.2.2011-i586-1salix > PDCurses-3.4-i486-1salix > qt3-3.3.8b-i486-5salix > > example of the problem: > ( cd usr/lib ; ln -sf > /usr/src/slapt-src/libraries/PDCurses/package-PDCurses/usr/lib/libXCurses.so > libXpanel.so ) > > I found this problem searching thur the /var/log/scripts files. I hope > this helps. > [/quoted post] > > I couldn't answer because for an unknown reason the thread and the user > disappeared. > > However I had a look at two cases and confirm the issue. > For PDCurses the wrong links are mad by by install target in Makefile.in > in the source archive as shown below > install: > > ln -f -s $(libdir)/$(SHLPRE)$(SHLFILE)$(SHLPST) \ > $(libdir)/$(SHLPRE)Xpanel$(SHLPST) > ln -f -s $(libdir)/libXCurses.a $(libdir)/libXpanel.a > -$(RANLIB) $(libdir)/libXpanel.a > For fvwm95 the wrong link comes from the install target in > sample.fvwmrc/Makefile.in in the source archive as sown below: > install: > ${INSTALL_DATA} ${RC} ${fvwm_dir} > ${LN} ${fvwm_dir}/${RC} ${fvwm_dir}/${fvwm_rc} > (LN is converted to ln -s during the build) > > I was too lazy to check the other packages (I don't use any of those > listed by Jardenblack) > but I assume that other packages have a similar issue, i.e. symlinks > from a file in the build dir that will be broken as soon as the build > dir is removed. > > Maybe the broken symlinks do not always hurt but still, a systematic > check that the symlinks (in install/doinst.sh or /var/log/scripts) will > survive the removal of the build dir could be useful? > > Best, > > Didier > _______________________________________________ > 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 jebrhansen+SBo at gmail.com Fri May 4 02:52:04 2018 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 04 May 2018 02:52:04 +0000 Subject: [Slackbuilds-users] Wrong symlinks in packages In-Reply-To: References: <103b84e4-3756-664d-a101-312953cbdb20@slint.fr> Message-ID: On Thu, May 3, 2018, 7:13 PM Frank Gingras wrote: > Wait, why are you asking for help with salix packages on the SBo mailing > list? > > On Wed, May 2, 2018 at 2:47 PM Didier Spaier wrote: > >> Hello, >> >> Today someone nicknamed Jardenblack posted this in a Salix forum: >> [quoted post] >> Here is a list of packages that have bad soft links and need to be fixed: >> fvwm95-2.0.43f-i486-2salix >> HawkNL-1.68-i486-1salix >> http-parser-2.7.1-i486-1salix >> libiptcdata-1.0.4-i486-2salix >> oss-4.2.2011-i586-1salix >> PDCurses-3.4-i486-1salix >> qt3-3.3.8b-i486-5salix >> >> example of the problem: >> ( cd usr/lib ; ln -sf >> /usr/src/slapt-src/libraries/PDCurses/package-PDCurses/usr/lib/libXCurses.so >> libXpanel.so ) >> >> I found this problem searching thur the /var/log/scripts files. I hope >> this helps. >> [/quoted post] >> >> I couldn't answer because for an unknown reason the thread and the user >> disappeared. >> >> However I had a look at two cases and confirm the issue. >> For PDCurses the wrong links are mad by by install target in Makefile.in >> in the source archive as shown below >> install: >> >> ln -f -s $(libdir)/$(SHLPRE)$(SHLFILE)$(SHLPST) \ >> $(libdir)/$(SHLPRE)Xpanel$(SHLPST) >> ln -f -s $(libdir)/libXCurses.a $(libdir)/libXpanel.a >> -$(RANLIB) $(libdir)/libXpanel.a >> For fvwm95 the wrong link comes from the install target in >> sample.fvwmrc/Makefile.in in the source archive as sown below: >> install: >> ${INSTALL_DATA} ${RC} ${fvwm_dir} >> ${LN} ${fvwm_dir}/${RC} ${fvwm_dir}/${fvwm_rc} >> (LN is converted to ln -s during the build) >> >> I was too lazy to check the other packages (I don't use any of those >> listed by Jardenblack) >> but I assume that other packages have a similar issue, i.e. symlinks >> from a file in the build dir that will be broken as soon as the build >> dir is removed. >> >> Maybe the broken symlinks do not always hurt but still, a systematic >> check that the symlinks (in install/doinst.sh or /var/log/scripts) will >> survive the removal of the build dir could be useful? >> >> Best, >> >> Didier >> _______________________________________________ >> 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/ >> >> _______________________________________________ > 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/ He's mentioning that builds from SlackBuilds on SBo have incorrect symlinks. Just because they're built with a salix tag doesn't mean that the incorrect symlinks generated when building the packages aren't a problem. It doesn't sound like this is a SlackBuild issue so much as a program issue (based on Didier's research on those two packages, although, I haven't looked into any of them), but the maintainers of those packages might want to look into it and either contact upstream or correct for it in the SlackBuild. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Fri May 4 03:00:23 2018 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 04 May 2018 03:00:23 +0000 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: Message-ID: On Thu, May 3, 2018, 3:34 PM JCA <1.41421 at gmail.com> wrote: > I am not interested in becoming a package maintainer, in part precisely > because I am all too aware of what is involved. I am very thankful that > there are people willing to do so. I am merely pointing out that, if they > can't or won't do what is concomitant to maintaining a package, they should > not volunteer - it is obvious that, if the Slackbuilds packages are poorly > maintained, Slackbuilds loses reliability and credibility. > So, if a maintainer thinks they might not be using Slackware in two years, they just shouldn't submit a SlackBuild? If they've done the work to automate a build, why not submit it? Even if it ends up being broken in six months, that's six months that uses can use and enjoy it. If it breaks, maybe the maintainer will push a new version, or maybe someone else will take it over (or maybe the admins will bump the version to get it to work, but leave the script assigned to the original author until someone else offers to maintain it). I'm grateful for any SlackBuilds that are submitted, even if the maintainers never push another update or they eventually stop using Slackware and can't maintain it. It gives someone the ability to use that software as-is. How many people have been able to enjoy plexmediaserver since it's been available on SBo? How many others have found it isn't working and did a simple version bump and got it working (like you did)? Then, when issues are found, if the maintainer doesn't respond, someone else can take over, just like what happened here. Is the SBo situation ideal since maintainers can drop off the face of the planet at any time? Probably not, but if we removed all the software that was published by one person that never had additional updates pushed, the repo would probably be a lot smaller. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ekinakoglu at gmail.com Fri May 4 08:50:40 2018 From: ekinakoglu at gmail.com (Ekin Akoglu) Date: Fri, 4 May 2018 11:50:40 +0300 Subject: [Slackbuilds-users] Inkscape 0.92.3 error In-Reply-To: <445fb5eb-1ee8-e63d-d7c2-a39718a8df6f@slackbuilds.org> References: <445fb5eb-1ee8-e63d-d7c2-a39718a8df6f@slackbuilds.org> Message-ID: Hi, Thank you for your suggestion, Willy. I have just rebuilt all the inkscape's dependencies and the dependencies' dependencies in a cyclic manner. Below is the map, in reverse order, of what I have rebuilt: inkscape -> lxml -> BeautifulSoup4, html5lib -> six, python-webencodings inkscape -> numpy However, even after all this work, I could not rebuild inkscape successfully. The error is the same, related to libiconv, as below in the linking step of the build process: ? CXX????? ui/widget/addtoicon.o ? CXXLD??? inkscape libuemf/libuemf.a(uemf_utf.o): In function `U_Utf32leToUtf16le': uemf_utf.c:(.text+0x323): undefined reference to `libiconv_open' uemf_utf.c:(.text+0x346): undefined reference to `libiconv' uemf_utf.c:(.text+0x351): undefined reference to `libiconv_close' libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToUtf32le': uemf_utf.c:(.text+0x41f): undefined reference to `libiconv_open' uemf_utf.c:(.text+0x442): undefined reference to `libiconv' uemf_utf.c:(.text+0x44d): undefined reference to `libiconv_close' libuemf/libuemf.a(uemf_utf.o): In function `U_Latin1ToUtf32le': uemf_utf.c:(.text+0x50f): undefined reference to `libiconv_open' uemf_utf.c:(.text+0x532): undefined reference to `libiconv' uemf_utf.c:(.text+0x53d): undefined reference to `libiconv_close' libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToUtf32le': uemf_utf.c:(.text+0x5ff): undefined reference to `libiconv_open' uemf_utf.c:(.text+0x622): undefined reference to `libiconv' uemf_utf.c:(.text+0x62d): undefined reference to `libiconv_close' libuemf/libuemf.a(uemf_utf.o): In function `U_Utf32leToUtf8': uemf_utf.c:(.text+0x6f3): undefined reference to `libiconv_open' uemf_utf.c:(.text+0x71a): undefined reference to `libiconv' uemf_utf.c:(.text+0x725): undefined reference to `libiconv_close' libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToUtf16le': uemf_utf.c:(.text+0x818): undefined reference to `libiconv_open' uemf_utf.c:(.text+0x83b): undefined reference to `libiconv' uemf_utf.c:(.text+0x846): undefined reference to `libiconv_close' libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToLatin1': uemf_utf.c:(.text+0x907): undefined reference to `libiconv_open' uemf_utf.c:(.text+0x92a): undefined reference to `libiconv' uemf_utf.c:(.text+0x935): undefined reference to `libiconv_close' libuemf/libuemf.a(uemf_utf.o): In function `U_Latin1ToUtf8': uemf_utf.c:(.text+0x9f8): undefined reference to `libiconv_open' uemf_utf.c:(.text+0xa1b): undefined reference to `libiconv' uemf_utf.c:(.text+0xa26): undefined reference to `libiconv_close' libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToUtf8': uemf_utf.c:(.text+0xb8f): undefined reference to `libiconv_open' uemf_utf.c:(.text+0xbb6): undefined reference to `libiconv' uemf_utf.c:(.text+0xbc1): undefined reference to `libiconv_close' libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToLatin1': uemf_utf.c:(.text+0xccf): undefined reference to `libiconv_open' uemf_utf.c:(.text+0xcf6): undefined reference to `libiconv' uemf_utf.c:(.text+0xd01): undefined reference to `libiconv_close' collect2: error: ld returned 1 exit status Makefile:7232: recipe for target 'inkscape' failed make[3]: *** [inkscape] Error 1 make[3]: Leaving directory '/tmp/SBo/inkscape-0.92.3/src' Makefile:5292: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/tmp/SBo/inkscape-0.92.3/src' Makefile:1473: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/inkscape-0.92.3' Makefile:1129: recipe for target 'all' failed make: *** [all] Error 2 Do you have an idea or is inkscape.SlackBuild broken on SBo? My system is Slackware64 14.2 -stable. Best, Ekin On 30/04/18 14:45, Willy Sudiarto Raharjo wrote: > On 04/30/2018 05:05 PM, Ekin Akoglu wrote: >> Hi, >> >> When compiling the following error occurs related to libiconv: >> >> CXXLD??? inkscape >> libuemf/libuemf.a(uemf_utf.o): In function `U_Utf32leToUtf16le': >> uemf_utf.c:(.text+0x323): undefined reference to `libiconv_open' >> uemf_utf.c:(.text+0x346): undefined reference to `libiconv' >> uemf_utf.c:(.text+0x351): undefined reference to `libiconv_close' >> libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToUtf32le': >> uemf_utf.c:(.text+0x41f): undefined reference to `libiconv_open' >> uemf_utf.c:(.text+0x442): undefined reference to `libiconv' >> uemf_utf.c:(.text+0x44d): undefined reference to `libiconv_close' >> libuemf/libuemf.a(uemf_utf.o): In function `U_Latin1ToUtf32le': >> uemf_utf.c:(.text+0x50f): undefined reference to `libiconv_open' >> uemf_utf.c:(.text+0x532): undefined reference to `libiconv' >> uemf_utf.c:(.text+0x53d): undefined reference to `libiconv_close' >> libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToUtf32le': >> uemf_utf.c:(.text+0x5ff): undefined reference to `libiconv_open' >> uemf_utf.c:(.text+0x622): undefined reference to `libiconv' >> uemf_utf.c:(.text+0x62d): undefined reference to `libiconv_close' >> libuemf/libuemf.a(uemf_utf.o): In function `U_Utf32leToUtf8': >> uemf_utf.c:(.text+0x6f3): undefined reference to `libiconv_open' >> uemf_utf.c:(.text+0x71a): undefined reference to `libiconv' >> uemf_utf.c:(.text+0x725): undefined reference to `libiconv_close' >> libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToUtf16le': >> uemf_utf.c:(.text+0x818): undefined reference to `libiconv_open' >> uemf_utf.c:(.text+0x83b): undefined reference to `libiconv' >> uemf_utf.c:(.text+0x846): undefined reference to `libiconv_close' >> libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToLatin1': >> uemf_utf.c:(.text+0x907): undefined reference to `libiconv_open' >> uemf_utf.c:(.text+0x92a): undefined reference to `libiconv' >> uemf_utf.c:(.text+0x935): undefined reference to `libiconv_close' >> libuemf/libuemf.a(uemf_utf.o): In function `U_Latin1ToUtf8': >> uemf_utf.c:(.text+0x9f8): undefined reference to `libiconv_open' >> uemf_utf.c:(.text+0xa1b): undefined reference to `libiconv' >> uemf_utf.c:(.text+0xa26): undefined reference to `libiconv_close' >> libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToUtf8': >> uemf_utf.c:(.text+0xb8f): undefined reference to `libiconv_open' >> uemf_utf.c:(.text+0xbb6): undefined reference to `libiconv' >> uemf_utf.c:(.text+0xbc1): undefined reference to `libiconv_close' >> libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToLatin1': >> uemf_utf.c:(.text+0xccf): undefined reference to `libiconv_open' >> uemf_utf.c:(.text+0xcf6): undefined reference to `libiconv' >> uemf_utf.c:(.text+0xd01): undefined reference to `libiconv_close' >> collect2: error: ld returned 1 exit status >> Makefile:7232: recipe for target 'inkscape' failed >> make[3]: *** [inkscape] Error 1 >> make[3]: Leaving directory '/tmp/SBo/inkscape-0.92.3/src' >> Makefile:5292: recipe for target 'all' failed >> make[2]: *** [all] Error 2 >> make[2]: Leaving directory '/tmp/SBo/inkscape-0.92.3/src' >> Makefile:1473: recipe for target 'all-recursive' failed >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory '/tmp/SBo/inkscape-0.92.3' >> Makefile:1129: recipe for target 'all' failed >> make: *** [all] Error 2 >> >> I have also tried with libiconv 1.15 installed but it did not work. Do >> you have an idea about what could be wrong? > Is this on -current or -stable? > have you tried to rebuilt all deps as well? > > > > > > _______________________________________________ > 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 rsamurti at gmail.com Fri May 4 09:32:59 2018 From: rsamurti at gmail.com (Ananda Murthy R S) Date: Fri, 04 May 2018 09:32:59 +0000 Subject: [Slackbuilds-users] Inkscape 0.92.3 error In-Reply-To: References: <445fb5eb-1ee8-e63d-d7c2-a39718a8df6f@slackbuilds.org> Message-ID: Hello It is building properly on my system running on Slackware64 14.2 Anand On Fri 4 May, 2018, 2:21 PM Ekin Akoglu, wrote: > Hi, > > Thank you for your suggestion, Willy. > > I have just rebuilt all the inkscape's dependencies and the dependencies' > dependencies in a cyclic manner. Below is the map, in reverse order, of > what I have rebuilt: > > inkscape -> lxml -> BeautifulSoup4, html5lib -> six, python-webencodings > > inkscape -> numpy > > However, even after all this work, I could not rebuild inkscape > successfully. The error is the same, related to libiconv, as below in the > linking step of the build process: > > CXX ui/widget/addtoicon.o > CXXLD inkscape > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf32leToUtf16le': > uemf_utf.c:(.text+0x323): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x346): undefined reference to `libiconv' > uemf_utf.c:(.text+0x351): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToUtf32le': > uemf_utf.c:(.text+0x41f): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x442): undefined reference to `libiconv' > uemf_utf.c:(.text+0x44d): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Latin1ToUtf32le': > uemf_utf.c:(.text+0x50f): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x532): undefined reference to `libiconv' > uemf_utf.c:(.text+0x53d): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToUtf32le': > uemf_utf.c:(.text+0x5ff): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x622): undefined reference to `libiconv' > uemf_utf.c:(.text+0x62d): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf32leToUtf8': > uemf_utf.c:(.text+0x6f3): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x71a): undefined reference to `libiconv' > uemf_utf.c:(.text+0x725): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToUtf16le': > uemf_utf.c:(.text+0x818): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x83b): undefined reference to `libiconv' > uemf_utf.c:(.text+0x846): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToLatin1': > uemf_utf.c:(.text+0x907): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x92a): undefined reference to `libiconv' > uemf_utf.c:(.text+0x935): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Latin1ToUtf8': > uemf_utf.c:(.text+0x9f8): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0xa1b): undefined reference to `libiconv' > uemf_utf.c:(.text+0xa26): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToUtf8': > uemf_utf.c:(.text+0xb8f): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0xbb6): undefined reference to `libiconv' > uemf_utf.c:(.text+0xbc1): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToLatin1': > uemf_utf.c:(.text+0xccf): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0xcf6): undefined reference to `libiconv' > uemf_utf.c:(.text+0xd01): undefined reference to `libiconv_close' > collect2: error: ld returned 1 exit status > Makefile:7232: recipe for target 'inkscape' failed > make[3]: *** [inkscape] Error 1 > make[3]: Leaving directory '/tmp/SBo/inkscape-0.92.3/src' > Makefile:5292: recipe for target 'all' failed > make[2]: *** [all] Error 2 > make[2]: Leaving directory '/tmp/SBo/inkscape-0.92.3/src' > Makefile:1473: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/inkscape-0.92.3' > Makefile:1129: recipe for target 'all' failed > make: *** [all] Error 2 > > Do you have an idea or is inkscape.SlackBuild broken on SBo? My system is > Slackware64 14.2 -stable. > > Best, > > Ekin > > On 30/04/18 14:45, Willy Sudiarto Raharjo wrote: > > On 04/30/2018 05:05 PM, Ekin Akoglu wrote: > > Hi, > > When compiling the following error occurs related to libiconv: > > CXXLD inkscape > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf32leToUtf16le': > uemf_utf.c:(.text+0x323): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x346): undefined reference to `libiconv' > uemf_utf.c:(.text+0x351): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToUtf32le': > uemf_utf.c:(.text+0x41f): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x442): undefined reference to `libiconv' > uemf_utf.c:(.text+0x44d): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Latin1ToUtf32le': > uemf_utf.c:(.text+0x50f): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x532): undefined reference to `libiconv' > uemf_utf.c:(.text+0x53d): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToUtf32le': > uemf_utf.c:(.text+0x5ff): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x622): undefined reference to `libiconv' > uemf_utf.c:(.text+0x62d): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf32leToUtf8': > uemf_utf.c:(.text+0x6f3): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x71a): undefined reference to `libiconv' > uemf_utf.c:(.text+0x725): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToUtf16le': > uemf_utf.c:(.text+0x818): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x83b): undefined reference to `libiconv' > uemf_utf.c:(.text+0x846): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf8ToLatin1': > uemf_utf.c:(.text+0x907): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0x92a): undefined reference to `libiconv' > uemf_utf.c:(.text+0x935): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Latin1ToUtf8': > uemf_utf.c:(.text+0x9f8): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0xa1b): undefined reference to `libiconv' > uemf_utf.c:(.text+0xa26): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToUtf8': > uemf_utf.c:(.text+0xb8f): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0xbb6): undefined reference to `libiconv' > uemf_utf.c:(.text+0xbc1): undefined reference to `libiconv_close' > libuemf/libuemf.a(uemf_utf.o): In function `U_Utf16leToLatin1': > uemf_utf.c:(.text+0xccf): undefined reference to `libiconv_open' > uemf_utf.c:(.text+0xcf6): undefined reference to `libiconv' > uemf_utf.c:(.text+0xd01): undefined reference to `libiconv_close' > collect2: error: ld returned 1 exit status > Makefile:7232: recipe for target 'inkscape' failed > make[3]: *** [inkscape] Error 1 > make[3]: Leaving directory '/tmp/SBo/inkscape-0.92.3/src' > Makefile:5292: recipe for target 'all' failed > make[2]: *** [all] Error 2 > make[2]: Leaving directory '/tmp/SBo/inkscape-0.92.3/src' > Makefile:1473: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/inkscape-0.92.3' > Makefile:1129: recipe for target 'all' failed > make: *** [all] Error 2 > > I have also tried with libiconv 1.15 installed but it did not work. Do > you have an idea about what could be wrong? > > > Is this on -current or -stable? > have you tried to rebuilt all deps as well? > > > > > > > _______________________________________________ > SlackBuilds-users mailing listSlackBuilds-users at slackbuilds.orghttps://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > _______________________________________________ > 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 1.41421 at gmail.com Fri May 4 13:57:05 2018 From: 1.41421 at gmail.com (JCA) Date: Fri, 4 May 2018 07:57:05 -0600 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: Message-ID: The repo would probably be smaller, and also probably more reliable. Many of us come to Slackbuilds because it affords the capability of simply and reliably compiling software that, otherwise, might be painful to build. There are many examples of that in the Slackbuilds repository - kudos to their maintainers for their diligence and their time. Another reason to come to Slackbuilds is to gain access to reasonably recent software for Slackware. Finally, some of us implicitly trust that the software obtained from Slackbuilds has been tested (even if only basically) under the target Slackware distribution, and that it works. The plexmediaserver case illustrates a case in which the three assumptions above are not met. First, building the software itself is trivial - it is delivered as a .deb package, which can be trivially installed under Slackware. Second, the Slackbuilds version is old, and not for reasons of stability. Third, as I pointed out, it does not work. It would have taken me (or almost anyone) a fraction of the time to get it installed and running on a Slack64 14.2 system had one just downloaded and installed it oneself, bypassing Slackbuilds altogether. I.e. in this occasion, having a Slackbuilds package was a complete waste of time, rather than an asset. Maintaining a Slackbuilds package is not just a matter of coming up with the *.Slackbuild script and associated infrastructure - that really is a fairly easy undertaking for anyone with a little bit of experience in this kind of thing. Keeping track of updates, making sure that the resulting package work, testing, etc. - that's the bulk of the maintenance work, and something that quite a few Slackbuilds maintainers don't do, for whatever reasons. Should we thankful for that? Should we be thankful because they are claiming to be doing something that, in fact, they are not doing? Should we be thankful for the time wasted as a consequence of such negligence? We should be thankful for a job well done, not because someone volunteers to donate their time and effort to do something, and then they do not follow through. It would be better if packages could be tagged with degrees of maintenance quality: "fully", "incompletely" and "neglected". Had plexmediaserver been tagged as "incompletely" I would have been made aware of a potentially bumpy road ahead. Had it been tagged as "neglected" I wouldn't even have bothered, thus saving quite a bit of time. I would suggest putting in place a mechanism whereby maintainers should regularly reaffirm that they are actively maintaining their packages - for example, by explicitly communicating so to some Slackbuilds authority on a regular basis. Failing to do so would allow this authority to tag said packages adequately, and therefore potentially save some unnecessary aggravation. This is by no means perfect, and one could still end up with effectively unmaintained packages being tagged as "fully", despite the updates above - which could, of course, be easy to do automatically. But, it would take an extra effort from the maintainer, which makes it probably less likely that the situations that we are discussing would arise - after all, it takes no effort to stop responding to emails. Plus most of us do no relish to be revealed as fibbers in public. To answer your question, if a maintainer is not willing or capable to do what it takes to maintain a package, they should not do so in the first place. If, for whatever reasons, they cannot maintain a package any more, and they can't find the time or the stamina to let Slackbuilds know so, there should be a mechanism to let Slackbuilds users know what packages are, for all practical purposes, unmaintained. What I propose is no more than an idea for an idea, but it is a step in that direction. With some more thought, I am sure that we can come up with a scheme that would be far more efficient. Maybe this is all too much to do on a voluntary, unpaid basis. I don't know. On Thu, May 3, 2018 at 9:00 PM, Jeremy Hansen wrote: > > > On Thu, May 3, 2018, 3:34 PM JCA <1.41421 at gmail.com> wrote: > >> I am not interested in becoming a package maintainer, in part precisely >> because I am all too aware of what is involved. I am very thankful that >> there are people willing to do so. I am merely pointing out that, if they >> can't or won't do what is concomitant to maintaining a package, they should >> not volunteer - it is obvious that, if the Slackbuilds packages are poorly >> maintained, Slackbuilds loses reliability and credibility. >> > > So, if a maintainer thinks they might not be using Slackware in two years, > they just shouldn't submit a SlackBuild? If they've done the work to > automate a build, why not submit it? Even if it ends up being broken in six > months, that's six months that uses can use and enjoy it. If it breaks, > maybe the maintainer will push a new version, or maybe someone else will > take it over (or maybe the admins will bump the version to get it to work, > but leave the script assigned to the original author until someone else > offers to maintain it). > > I'm grateful for any SlackBuilds that are submitted, even if the > maintainers never push another update or they eventually stop using > Slackware and can't maintain it. It gives someone the ability to use that > software as-is. How many people have been able to enjoy plexmediaserver > since it's been available on SBo? How many others have found it isn't > working and did a simple version bump and got it working (like you did)? > > Then, when issues are found, if the maintainer doesn't respond, someone > else can take over, just like what happened here. > > Is the SBo situation ideal since maintainers can drop off the face of the > planet at any time? Probably not, but if we removed all the software that > was published by one person that never had additional updates pushed, the > repo would probably be a lot smaller. > > Jeremy > >> > _______________________________________________ > 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 alex at dcclost.com Fri May 4 14:42:07 2018 From: alex at dcclost.com (Alexander Grotewohl) Date: Fri, 4 May 2018 10:42:07 -0400 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: Message-ID: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> A few things: You say it's trivial, but you don't want to do it yourself. It's also trivial to make && make install, keep a Changelog for your system, etc. But those things are time consuming.. and we're talking conveniences. The belief that Slackbuilds are somehow more reliable is naive. We're human, and there can be bugs in the Slackbuilds or the software itself. Also, anything with even a modest chain of dependencies must be remembered for next time, lest you build everything out of order. (which IIRC software like sbopkg will totally do). We kind of signed up for this. To be honest, even the oldest of Slackbuilds that haven't been touched in years often work just fine by swapping the version number in the script and downloading a different tarball. Have I benefited from not having to write my own Slackbuild scripts because of this fact? Absolutely. Three of the Slackbuilds I use often are currently like that, and I'm not gonna say which :) Because that's not the point. Are they neglected? Sure. Did they help me though? Yep. Alex On 05/04/2018 09:57 AM, JCA wrote: > The repo would probably be smaller, and also probably more reliable. > Many of us come to Slackbuilds because it affords the capability of > simply and reliably compiling software that, otherwise, might be > painful to build. There are many examples of that in the Slackbuilds > repository - kudos to their maintainers for their diligence and their > time. Another reason to come to Slackbuilds is to gain access to > reasonably recent software for Slackware. Finally, some of us > implicitly trust that the software obtained from Slackbuilds has been > tested (even if only basically) under the target Slackware > distribution, and that it works. The plexmediaserver case illustrates > a case in which the three assumptions above are not met. First, > building the software itself is trivial - it is delivered as a .deb > package, which can be trivially installed under Slackware. Second, the > Slackbuilds version is old, and not for reasons of stability. Third, > as I pointed out, it does not work. It would have taken me (or almost > anyone)? a fraction of the time to get it installed and running on a? > Slack64 14.2 system had one just downloaded and installed it oneself, > bypassing Slackbuilds altogether. I.e. in this occasion, having a > Slackbuilds package was a complete waste of time, rather than an asset. > > Maintaining a Slackbuilds package is not just a matter of coming up > with the *.Slackbuild script and associated infrastructure - that > really is a fairly easy undertaking for anyone with a little bit of > experience in this kind of thing. Keeping track of updates, making > sure that the resulting package work, testing, etc. - that's the bulk > of the maintenance work, and something that quite a few Slackbuilds > maintainers don't do, for whatever reasons. Should we thankful for > that? Should we be thankful because they are claiming to be doing > something that, in fact, they are not doing? Should we be thankful for > the time wasted as a consequence of such negligence? We should be > thankful? for a job well done, not because someone volunteers to > donate their time and effort to do something, and then they do not > follow through. > > It would be better if packages could be tagged with degrees of > maintenance quality: "fully", "incompletely" and "neglected". Had > plexmediaserver been tagged as "incompletely" I would have been made > aware of a potentially bumpy road ahead. Had it been tagged as > "neglected"? I wouldn't even have bothered, thus saving quite a bit of > time. I would suggest putting in place a mechanism whereby maintainers > should regularly reaffirm that they are actively maintaining their > packages - for example, by explicitly communicating so to some > Slackbuilds authority on a regular basis. Failing to do so would allow > this authority to tag said packages adequately, and therefore > potentially save some unnecessary aggravation. This is by no means > perfect, and one could still end up with effectively unmaintained > packages being tagged as "fully", despite the updates above - which > could, of course, be easy to do automatically. But, it would take an > extra effort from the maintainer, which makes it probably less likely > that the situations that we are discussing would arise - after all, it > takes no effort to stop responding to emails. Plus most of us do no > relish to be revealed as fibbers in public. > > To answer your question, if a maintainer is not willing or capable to > do what it takes to maintain a package, they should not do so in the > first place. If, for whatever reasons, they cannot maintain a package > any more, and they can't find the time or the stamina to let > Slackbuilds know so, there should be a mechanism to let Slackbuilds > users know what packages are, for all practical purposes, > unmaintained. What I propose is no more than an idea for an idea, but > it is a step in that direction. With some more thought, I am sure that > we can come up with a scheme that would be far more efficient. Maybe > this is all too much to do on a voluntary, unpaid basis. I don't know. > > > > On Thu, May 3, 2018 at 9:00 PM, Jeremy Hansen > > wrote: > > > > On Thu, May 3, 2018, 3:34 PM JCA <1.41421 at gmail.com > > wrote: > > I am not interested in becoming a package maintainer, in part > precisely because I am all too aware of what is involved. I am > very thankful that there are people willing to do so. I am > merely pointing out that, if they can't or won't do what is > concomitant to maintaining a package, they should not > volunteer - it is obvious that, if the Slackbuilds packages > are poorly maintained, Slackbuilds loses reliability and > credibility. > > > So, if a maintainer thinks they might not be using Slackware in > two years, they just shouldn't submit a SlackBuild? If they've > done the work to automate a build, why not submit it? Even if it > ends up being broken in six months, that's six months that uses > can use and enjoy it. If it breaks, maybe the maintainer will push > a new version, or maybe someone else will take it over (or maybe > the admins will bump the version to get it to work, but leave the > script assigned to the original author until someone else offers > to maintain it). > > I'm grateful for any SlackBuilds that are submitted, even if the > maintainers never push another update or they eventually stop > using Slackware and can't maintain it. It gives someone the > ability to use that software as-is. How many people have been able > to enjoy plexmediaserver since it's been available on SBo? How > many others have found it isn't working and did a simple version > bump and got it working (like you did)? > > Then, when issues are found, if the maintainer doesn't respond, > someone else can take over, just like what happened here. > > Is the SBo situation ideal since maintainers can drop off the face > of the planet at any time? Probably not, but if we removed all the > software that was published by one person that never had > additional updates pushed, the repo would probably be a lot smaller. > > Jeremy > > > _______________________________________________ > 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/ > > > > > > _______________________________________________ > 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 matteo.bernardini at gmail.com Fri May 4 15:08:04 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 4 May 2018 17:08:04 +0200 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> Message-ID: I can't see the problem in notifying the maintainer of any issues with the SlackBuild and eventually report to this mailing list if he hasn't answered back after a reasonable amount of time (two weeks). doing that ensure that the SlackBuild that the inactive maintainers maintain will be taken care by someone after a while. please, do that. Matteo From 1.41421 at gmail.com Fri May 4 15:35:18 2018 From: 1.41421 at gmail.com (JCA) Date: Fri, 4 May 2018 09:35:18 -0600 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> Message-ID: On Fri, May 4, 2018 at 8:42 AM, Alexander Grotewohl wrote: > A few things: > > You say it's trivial, but you don't want to do it yourself. > Read what I wrote. What is trivial is to come up with the basic infrastructure for a Slackbuild package. What is not that trivial is to apply patches (if necessary) to keep track of updates and to make sure that the installed package works. That's much more laborious and intellectually demanding than make && make install. > It's also trivial to make && make install, keep a Changelog for your > system, etc. But those things are time consuming.. and we're talking > conveniences. > > The belief that Slackbuilds are somehow more reliable is naive. We're > human, and there can be bugs in the Slackbuilds or the software itself. > Also, anything with even a modest chain of dependencies must be remembered > for next time, lest you build everything out of order. (which IIRC software > like sbopkg will totally do). We kind of signed up for this. > Indeed. However, we are not talking about bugs here. We are talking about not doing due diligence when volunteering to maintain a package. Which is why I do not volunteer to maintain any: because I know that I do not have what it takes to do a proper job. Many current maintainers are obviously in the same situation. > To be honest, even the oldest of Slackbuilds that haven't been touched in > years often work just fine by swapping the version number in the script and > downloading a different tarball. Have I benefited from not having to write > my own Slackbuild scripts because of this fact? Absolutely. Three of the > Slackbuilds I use often are currently like that, and I'm not gonna say > which :) Because that's not the point. Are they neglected? Sure. Did they > help me though? Yep. > That's a fair point. I think that, on the basis of what you have so accurately described, the Slackbuilds home page should feature a big warning, advising Slackbuilds users that the hope is that Slackbuilds packages may be of use, but that no guarantee is made - in particular, that some packages may not install at all or, if they will, they will not work properly, or even at all, not because of upstream bugs, but because Slackbuilds can't guarantee that the packages are being maintained. That's effectively what is already happening - I think it is fair to make sure that potential Slackbuilds users are made aware of this fact before they even try. Not everybody who is trying to use Slackbuilds is an old-timer. And I think that we all agree that we would like for Slackware and Slackbuilds to be more and more popular. Well, at least I hope so. The gist of what I am proposing is to have an inkling of whether a Slackbuilds package is being well maintained, before finding out so after having to waste time and effort trying to install and make it it work. That's all. Like you said, it is possible for a package that has not been maintained for years to still do the right thing - but it would be nice to be forewarned. Alex > > On 05/04/2018 09:57 AM, JCA wrote: > > The repo would probably be smaller, and also probably more reliable. Many > of us come to Slackbuilds because it affords the capability of simply and > reliably compiling software that, otherwise, might be painful to build. > There are many examples of that in the Slackbuilds repository - kudos to > their maintainers for their diligence and their time. Another reason to > come to Slackbuilds is to gain access to reasonably recent software for > Slackware. Finally, some of us implicitly trust that the software obtained > from Slackbuilds has been tested (even if only basically) under the target > Slackware distribution, and that it works. The plexmediaserver case > illustrates a case in which the three assumptions above are not met. First, > building the software itself is trivial - it is delivered as a .deb > package, which can be trivially installed under Slackware. Second, the > Slackbuilds version is old, and not for reasons of stability. Third, as I > pointed out, it does not work. It would have taken me (or almost anyone) a > fraction of the time to get it installed and running on a Slack64 14.2 > system had one just downloaded and installed it oneself, bypassing > Slackbuilds altogether. I.e. in this occasion, having a Slackbuilds package > was a complete waste of time, rather than an asset. > > Maintaining a Slackbuilds package is not just a matter of coming up with > the *.Slackbuild script and associated infrastructure - that really is a > fairly easy undertaking for anyone with a little bit of experience in this > kind of thing. Keeping track of updates, making sure that the resulting > package work, testing, etc. - that's the bulk of the maintenance work, and > something that quite a few Slackbuilds maintainers don't do, for whatever > reasons. Should we thankful for that? Should we be thankful because they > are claiming to be doing something that, in fact, they are not doing? > Should we be thankful for the time wasted as a consequence of such > negligence? We should be thankful for a job well done, not because someone > volunteers to donate their time and effort to do something, and then they > do not follow through. > > It would be better if packages could be tagged with degrees of maintenance > quality: "fully", "incompletely" and "neglected". Had plexmediaserver been > tagged as "incompletely" I would have been made aware of a potentially > bumpy road ahead. Had it been tagged as "neglected" I wouldn't even have > bothered, thus saving quite a bit of time. I would suggest putting in place > a mechanism whereby maintainers should regularly reaffirm that they are > actively maintaining their packages - for example, by explicitly > communicating so to some Slackbuilds authority on a regular basis. Failing > to do so would allow this authority to tag said packages adequately, and > therefore potentially save some unnecessary aggravation. This is by no > means perfect, and one could still end up with effectively unmaintained > packages being tagged as "fully", despite the updates above - which could, > of course, be easy to do automatically. But, it would take an extra effort > from the maintainer, which makes it probably less likely that the > situations that we are discussing would arise - after all, it takes no > effort to stop responding to emails. Plus most of us do no relish to be > revealed as fibbers in public. > > To answer your question, if a maintainer is not willing or capable to do > what it takes to maintain a package, they should not do so in the first > place. If, for whatever reasons, they cannot maintain a package any more, > and they can't find the time or the stamina to let Slackbuilds know so, > there should be a mechanism to let Slackbuilds users know what packages > are, for all practical purposes, unmaintained. What I propose is no more > than an idea for an idea, but it is a step in that direction. With some > more thought, I am sure that we can come up with a scheme that would be far > more efficient. Maybe this is all too much to do on a voluntary, unpaid > basis. I don't know. > > > > On Thu, May 3, 2018 at 9:00 PM, Jeremy Hansen > wrote: > >> >> >> On Thu, May 3, 2018, 3:34 PM JCA <1.41421 at gmail.com> wrote: >> >>> I am not interested in becoming a package maintainer, in part precisely >>> because I am all too aware of what is involved. I am very thankful that >>> there are people willing to do so. I am merely pointing out that, if they >>> can't or won't do what is concomitant to maintaining a package, they should >>> not volunteer - it is obvious that, if the Slackbuilds packages are poorly >>> maintained, Slackbuilds loses reliability and credibility. >>> >> >> So, if a maintainer thinks they might not be using Slackware in two >> years, they just shouldn't submit a SlackBuild? If they've done the work to >> automate a build, why not submit it? Even if it ends up being broken in six >> months, that's six months that uses can use and enjoy it. If it breaks, >> maybe the maintainer will push a new version, or maybe someone else will >> take it over (or maybe the admins will bump the version to get it to work, >> but leave the script assigned to the original author until someone else >> offers to maintain it). >> >> I'm grateful for any SlackBuilds that are submitted, even if the >> maintainers never push another update or they eventually stop using >> Slackware and can't maintain it. It gives someone the ability to use that >> software as-is. How many people have been able to enjoy plexmediaserver >> since it's been available on SBo? How many others have found it isn't >> working and did a simple version bump and got it working (like you did)? >> >> Then, when issues are found, if the maintainer doesn't respond, someone >> else can take over, just like what happened here. >> >> Is the SBo situation ideal since maintainers can drop off the face of the >> planet at any time? Probably not, but if we removed all the software that >> was published by one person that never had additional updates pushed, the >> repo would probably be a lot smaller. >> >> Jeremy >> >>> >> _______________________________________________ >> 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/ >> >> >> > > > _______________________________________________ > SlackBuilds-users mailing listSlackBuilds-users at slackbuilds.orghttps://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > > _______________________________________________ > 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 rvnues at disroot.org Fri May 4 15:41:11 2018 From: rvnues at disroot.org (rob van nues) Date: Fri, 4 May 2018 16:41:11 +0100 Subject: [Slackbuilds-users] Inkscape 0.92.3 error In-Reply-To: References: Message-ID: <20180504164111.3720d7af@knotsUL> On Fri, 04 May 2018 09:33:13 +0000 slackbuilds-users-request at slackbuilds.org wrote: > 2. Re: Inkscape 0.92.3 error (Ekin Akoglu) > 3. Re: Inkscape 0.92.3 error (Ananda Murthy R S) Hi, I have inkscape working as well. But no libiconv on my system. When you do a 'content'-search on the slackware package browser (https://packages.slackware.com/) no libiconv is part of 14.2. A usr/include/iconv.h comes with glibc . Maybe try to find whether you have a package on your box that provides a libiconv and needs to be removed/changed in order to let inkscape compile. It could interfere with glibc it seems according to this old thread on LQ: https://www.linuxquestions.org/questions/slackware-14/undefined-reference-to-libiconv-341284/ HTH Rob From 1.41421 at gmail.com Fri May 4 15:42:43 2018 From: 1.41421 at gmail.com (JCA) Date: Fri, 4 May 2018 09:42:43 -0600 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> Message-ID: On Fri, May 4, 2018 at 9:08 AM, Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > I can't see the problem in notifying the maintainer of any issues with > the SlackBuild and eventually report to this mailing list if he hasn't > answered back after a reasonable amount of time (two weeks). > Having tried that a few times in the past, I think that approach all too often will amount to wasting two weeks. On this basis, and as a matter of principle, I would have thought that a conscientious maintainer ought to keep track of this forum precisely for this kind of issues. In fact, it seems to be the case that such maintainers already do so. To put it in a nutshell, don't you think that one of the duties of a package maintainer ought to be to keep track of this forum? > doing that ensure that the SlackBuild that the inactive maintainers > maintain will be taken care by someone after a while. > please, do that. > > Matteo > _______________________________________________ > 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 idlemoor at slackbuilds.org Fri May 4 15:46:53 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Fri, 4 May 2018 16:46:53 +0100 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> Message-ID: > Having tried that a few times in the past, I think that approach all too > often will amount to wasting two weeks. On this basis, and as a matter > of principle, I would have thought that a conscientious maintainer ought > to keep track of this forum precisely for this kind of issues. In fact, > it seems to be the case that such maintainers already do so.? > > To put it in a nutshell, don't you think that one of the duties of a > package maintainer ought to be to keep track of this forum? I'll be very pissed off if I'm no longer allowed to take two weeks holiday, or sick, just to please impatient and lazy users. Thanks -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Fri May 4 15:47:51 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 4 May 2018 22:47:51 +0700 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> Message-ID: > Having tried that a few times in the past, I think that approach all too > often will amount to wasting two weeks. On this basis, and as a matter > of principle, I would have thought that a conscientious maintainer ought > to keep track of this forum precisely for this kind of issues. In fact, > it seems to be the case that such maintainers already do so.? > > To put it in a nutshell, don't you think that one of the duties of a > package maintainer ought to be to keep track of this forum? While that's the ideal situation, please note that we are all doing this in our free time. We don't get paid by doing it, so please have respect if they have to deal with real-life first. As others have said, you are free to modify the SlackBuild and report back to us if you managed to fix them and let the maintainer knows about it. If they didn't step up, feel free to take over. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From 1.41421 at gmail.com Fri May 4 15:53:25 2018 From: 1.41421 at gmail.com (JCA) Date: Fri, 4 May 2018 09:53:25 -0600 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> Message-ID: Could you not post a notice to the forum to that effect? Or set up your email so that a relevant notification is automatically sent when receiving email? Otherwise, like I said, let's make sure that users are informed about the responsibilities of maintainers, and what to expect. Which, right now, and traditionally, seems to be whatever the maintainer wants. Which is fine; if that's what Slackbuilds offers, let's make it clear. On Fri, May 4, 2018 at 9:46 AM, David Spencer wrote: > > Having tried that a few times in the past, I think that approach all too > > often will amount to wasting two weeks. On this basis, and as a matter > > of principle, I would have thought that a conscientious maintainer ought > > to keep track of this forum precisely for this kind of issues. In fact, > > it seems to be the case that such maintainers already do so. > > > > To put it in a nutshell, don't you think that one of the duties of a > > package maintainer ought to be to keep track of this forum? > > I'll be very pissed off if I'm no longer allowed to take two weeks > holiday, or sick, just to please impatient and lazy users. > > Thanks > -D. > > > _______________________________________________ > 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 1.41421 at gmail.com Fri May 4 16:16:19 2018 From: 1.41421 at gmail.com (JCA) Date: Fri, 4 May 2018 10:16:19 -0600 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> Message-ID: On Fri, May 4, 2018 at 9:47 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Having tried that a few times in the past, I think that approach all too > > often will amount to wasting two weeks. On this basis, and as a matter > > of principle, I would have thought that a conscientious maintainer ought > > to keep track of this forum precisely for this kind of issues. In fact, > > it seems to be the case that such maintainers already do so. > > > > To put it in a nutshell, don't you think that one of the duties of a > > package maintainer ought to be to keep track of this forum? > > While that's the ideal situation, please note that we are all doing this > in our free time. We don't get paid by doing it, so please have respect > if they have to deal with real-life first. > > As others have said, you are free to modify the SlackBuild and report > back to us if you managed to fix them and let the maintainer knows about > it. If they didn't step up, feel free to take over. > Quite. But, like I said, no kudos is due when somebody claims to do something in their free time, and then they don't do what they claim, or they do it shoddily. Let me suggest something. The Slackbuilds home page contains some text with appropriate disclaimers. I would propose to add the following to this page, in a big font, so nobody will miss it: "The Slackbuilds team makes no guarantees about the quality of the packages. We hope that you will be able to download and build the relevant software, but we cannot guarantee it. We also hope that the software will run properly, but we can also not guarantee it. First, there may be problems with the upstream feed, over which we have we no control whatsoever. Second, since their contribution is totally voluntary and unpaid, we can also not guarantee that package maintainers are, in fact, maintaining their packages. In this sense, we can't be held responsible for the potential lack of maintenance of packages, and any subsequent inconveniences that this may cause." I believe that this accurately describes what one can expect from Slackbuilds. There is no point in concealing it, if nothing can reasonably be done to change the status quo. Slackbuilds will remain tremendously useful, but this will make it clear to newcomers what its limitations are. Reality is the way it is, and not the way we would like it to be. Is this not a fair deal? > > > -- > 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 idlemoor at slackbuilds.org Fri May 4 16:19:15 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Fri, 4 May 2018 17:19:15 +0100 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> Message-ID: <78233d21-2d90-a3be-bebb-edf294d1ff1c@slackbuilds.org> > Could you not post a notice to the forum to that effect? Or set up your > email so that a relevant notification is automatically sent when > receiving email?? I wonder if Debian Developers would put up with that. > Otherwise, like I said, let's make sure that users are informed about > the responsibilities of maintainers, and what to expect. Which, right > now, and traditionally, seems to be whatever the maintainer wants. Which > is fine; if that's what Slackbuilds offers, let's make it clear. Ok, here's what to expect. There are more than 7000 packages in the repo and more than 700 maintainers. We cannot functionally test all that lot proactively. We rely on the community to find and report problems. If someone tells us something's bust, we try to fix it. Out of respect for our volunteer maintainers, we prefer to give the maintainer first chance to do that. If it's somebody we know has been active recently, we give them plenty of time to respond. If it's someone who hasn't contributed in a long time, there's no point waiting and we will move quicker. But as admins we cannot be experts in every package in the repo. We don't necessarily know even how to start most of it up. That's the maintainer's job. In the absence of the maintainer, that's *your* job if you use it. We are also sometimes under a great deal of pressure to keep our repo stable: not to be a rolling distribution on top of stable Slackware. We explicitly don't chase the latest version of everything. Our last major quality checkpoint and campaign of recontacting maintainers was at the release of 14.2. I expect we'll be doing that again for 15.0. Meanwhile, thanks for the report. -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Fri May 4 16:19:02 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 4 May 2018 23:19:02 +0700 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> Message-ID: <235e990a-61f5-75d7-1c8e-ee9e86d9a4db@slackbuilds.org> > Let me suggest something. The Slackbuilds home page contains some text > with appropriate disclaimers. I would propose to add the following to > this page, in a big font, so nobody will miss it: > > "The Slackbuilds team makes no guarantees about the quality of the > packages. We hope that you will be able to download and build the > relevant software, but we cannot guarantee it. We also hope that the > software will run properly, but we can also not guarantee it. First, > there may be problems with the upstream feed, over which we have we no > control whatsoever. Second, since their contribution is totally > voluntary and unpaid, we can also not guarantee that package maintainers > are, in fact, maintaining their packages. In this sense, we can't be > held responsible for the potential lack of maintenance of packages, and > any subsequent inconveniences that this may cause." > > I believe that this accurately describes what one can expect from > Slackbuilds. There is no point in concealing it, if? nothing can > reasonably be done to change the status quo. Slackbuilds will remain > tremendously useful, but this will make it clear to newcomers what its > limitations are.? Reality is the way it is, and not the way we would > like it to be. Is this not a fair deal? I think the LICENSE covered that part See here: https://slackbuilds.org/templates/autotools-template.SlackBuild # THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" .... -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Fri May 4 16:35:54 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 4 May 2018 18:35:54 +0200 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: <235e990a-61f5-75d7-1c8e-ee9e86d9a4db@slackbuilds.org> References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> <235e990a-61f5-75d7-1c8e-ee9e86d9a4db@slackbuilds.org> Message-ID: 2018-05-04 18:19 GMT+02:00 Willy Sudiarto Raharjo : >> Let me suggest something. The Slackbuilds home page contains some text >> with appropriate disclaimers. I would propose to add the following to >> this page, in a big font, so nobody will miss it: >> >> "The Slackbuilds team makes no guarantees about the quality of the >> packages. We hope that you will be able to download and build the >> relevant software, but we cannot guarantee it. We also hope that the >> software will run properly, but we can also not guarantee it. First, >> there may be problems with the upstream feed, over which we have we no >> control whatsoever. Second, since their contribution is totally >> voluntary and unpaid, we can also not guarantee that package maintainers >> are, in fact, maintaining their packages. In this sense, we can't be >> held responsible for the potential lack of maintenance of packages, and >> any subsequent inconveniences that this may cause." >> >> I believe that this accurately describes what one can expect from >> Slackbuilds. There is no point in concealing it, if nothing can >> reasonably be done to change the status quo. Slackbuilds will remain >> tremendously useful, but this will make it clear to newcomers what its >> limitations are. Reality is the way it is, and not the way we would >> like it to be. Is this not a fair deal? > > I think the LICENSE covered that part > See here: https://slackbuilds.org/templates/autotools-template.SlackBuild > # THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" .... ...and this exposes the real issue: pretty much nobody reads the READMEs or the scripts they run in the first place. Matteo From 1.41421 at gmail.com Fri May 4 16:40:15 2018 From: 1.41421 at gmail.com (JCA) Date: Fri, 4 May 2018 10:40:15 -0600 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: <78233d21-2d90-a3be-bebb-edf294d1ff1c@slackbuilds.org> References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> <78233d21-2d90-a3be-bebb-edf294d1ff1c@slackbuilds.org> Message-ID: On Fri, May 4, 2018 at 10:19 AM, David Spencer wrote: > > Could you not post a notice to the forum to that effect? Or set up your > > email so that a relevant notification is automatically sent when > > receiving email? > > I wonder if Debian Developers would put up with that. > This is package maintenance, not development. Also, I, for one, use Slackware, not Debian, because I think it is better than Debian, not because I think that things surrounding Slackware are limited in the same way as things surrounding Debian are. > > > Otherwise, like I said, let's make sure that users are informed about > > the responsibilities of maintainers, and what to expect. Which, right > > now, and traditionally, seems to be whatever the maintainer wants. Which > > is fine; if that's what Slackbuilds offers, let's make it clear. > > Ok, here's what to expect. > > There are more than 7000 packages in the repo and more than 700 > maintainers. We cannot functionally test all that lot proactively. We > rely on the community to find and report problems. > > If someone tells us something's bust, we try to fix it. Out of respect > for our volunteer maintainers, we prefer to give the maintainer first > chance to do that. If it's somebody we know has been active recently, > we give them plenty of time to respond. If it's someone who hasn't > contributed in a long time, there's no point waiting and we will move > quicker. > > But as admins we cannot be experts in every package in the repo. We > don't necessarily know even how to start most of it up. That's the > maintainer's job. In the absence of the maintainer, that's *your* job if > you use it. > > We are also sometimes under a great deal of pressure to keep our repo > stable: not to be a rolling distribution on top of stable Slackware. We > explicitly don't chase the latest version of everything. Our last major > quality checkpoint and campaign of recontacting maintainers was at the > release of 14.2. I expect we'll be doing that again for 15.0. > Fair enough. Now make sure to enter the gist of this in the Slackbuilds home page, in a big font, so nobody will be led to think that packages are properly maintained throughout. > > Meanwhile, thanks for the report. > Any time. My hope is that will do something to improve things for this, and other packages in similar situations of abandonment. > -D. > > > _______________________________________________ > 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 1.41421 at gmail.com Fri May 4 16:44:31 2018 From: 1.41421 at gmail.com (JCA) Date: Fri, 4 May 2018 10:44:31 -0600 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> <235e990a-61f5-75d7-1c8e-ee9e86d9a4db@slackbuilds.org> Message-ID: On Fri, May 4, 2018 at 10:35 AM, Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > 2018-05-04 18:19 GMT+02:00 Willy Sudiarto Raharjo >: > >> Let me suggest something. The Slackbuilds home page contains some text > >> with appropriate disclaimers. I would propose to add the following to > >> this page, in a big font, so nobody will miss it: > >> > >> "The Slackbuilds team makes no guarantees about the quality of the > >> packages. We hope that you will be able to download and build the > >> relevant software, but we cannot guarantee it. We also hope that the > >> software will run properly, but we can also not guarantee it. First, > >> there may be problems with the upstream feed, over which we have we no > >> control whatsoever. Second, since their contribution is totally > >> voluntary and unpaid, we can also not guarantee that package maintainers > >> are, in fact, maintaining their packages. In this sense, we can't be > >> held responsible for the potential lack of maintenance of packages, and > >> any subsequent inconveniences that this may cause." > >> > >> I believe that this accurately describes what one can expect from > >> Slackbuilds. There is no point in concealing it, if nothing can > >> reasonably be done to change the status quo. Slackbuilds will remain > >> tremendously useful, but this will make it clear to newcomers what its > >> limitations are. Reality is the way it is, and not the way we would > >> like it to be. Is this not a fair deal? > > > > I think the LICENSE covered that part > > See here: https://slackbuilds.org/templates/autotools-template. > SlackBuild > > # THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" .... > > ...and this exposes the real issue: pretty much nobody reads the > READMEs or the scripts they run in the first place. > Precisely. Which is why I was suggesting the Slackbuilds home page, in a big font. In obnoxiously flashing text, if you want. That does not guarantee that people will read it, but it is far more difficult to miss. This aside, that's boilerplate, legalese stuff. What matters is what can be reasonably expected. > > Matteo > _______________________________________________ > 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 matteo.bernardini at gmail.com Fri May 4 16:50:09 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 4 May 2018 18:50:09 +0200 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> <235e990a-61f5-75d7-1c8e-ee9e86d9a4db@slackbuilds.org> Message-ID: 2018-05-04 18:40 GMT+02:00 JCA <1.41421 at gmail.com>: > Fair enough. Now make sure to enter the gist of this in the Slackbuilds home > page, in a big font, so nobody will be led to think that packages are > properly maintained throughout. it's not that finding a limited number of not maintained SlackBuilds means that all of 7000 of them are unmaintained: just calculate the percentage and you can see they are a very small part. >> Meanwhile, thanks for the report. > > > Any time. My hope is that will do something to improve things for this, and > other packages in similar situations of abandonment. IMHO is only maintaining stuff yourself that helps in these cases. 2018-05-04 18:44 GMT+02:00 JCA <1.41421 at gmail.com>: > wrote: >> ...and this exposes the real issue: pretty much nobody reads the >> READMEs or the scripts they run in the first place. > > > Precisely. Which is why I was suggesting the Slackbuilds home page, in a big > font. In obnoxiously flashing text, if you want. That does not guarantee > that people will read it, but it is far more difficult to miss. This aside, > that's boilerplate, legalese stuff. What matters is what can be reasonably > expected. I think you got this completely wrong: if you don't read the READMEs and the scripts you run, it's just your fault and you shouldn't blame nobody else. Matteo From rob0 at slackbuilds.org Fri May 4 17:11:58 2018 From: rob0 at slackbuilds.org (Rob McGee) Date: Fri, 4 May 2018 12:11:58 -0500 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> Message-ID: <20180504171158.GY5126@harrier.slackbuilds.org> First, in another subthread, you suggest that David use an email autoresponder when away on holiday. Slackbuilds.org mail services do not and WILL NOT support autoresponders, because the postmaster is an old curmudgeon who has never seen an autoresponder which cannot be tricked into doing something stupid. No. Don't ask. The answer will still be no. You also suggested that we require maintainers to monitor this mailing list. This idea has been considered and rejected in the past; so again, no. On Fri, May 04, 2018 at 09:35:18AM -0600, JCA wrote: > On Fri, May 4, 2018 at 8:42 AM, Alexander Grotewohl > wrote: > > > To be honest, even the oldest of Slackbuilds that haven't been > > touched in years often work just fine by swapping the version > > number in the script and downloading a different tarball. Have I > > benefited from not having to write my own Slackbuild scripts > > because of this fact? Absolutely. Three of the Slackbuilds I use > > often are currently like that, and I'm not gonna say which :) > > Because that's not the point. Are they neglected? Sure. Did they > > help me though? Yep. > > > That's a fair point. I think that, on the basis of what you have so > accurately described, the Slackbuilds home page should feature a > big warning, advising Slackbuilds users that the hope is that > Slackbuilds packages may be of use, but that no guarantee is made - > in particular, that some packages may not install at all or, if > they will, they will not work properly, or even at all, not because > of upstream bugs, but because Slackbuilds can't guarantee that the > packages are being maintained. Again, we are an all-volunteer free software project, and we have already made this disclaimer in an appropriate place: the LICENSE template file. Too much of the Internet is full of such garbage, and some of us have to deal with that junk in $dayjob. We do not have to put up with that here, and we will not. No. Don't ask. The answer will still be no. > That's effectively what is already happening - I think it is fair > to make sure that potential Slackbuilds users are made aware of > this fact before they even try. Not everybody who is trying to use > Slackbuilds is an old-timer. Everyone who is using Slackbuilds is welcome to learn about the realities of all-volunteer free software projects, along with the details of competent system administration. We're happy to help these new users in their efforts to learn. > And I think that we all agree that we would like for Slackware and > Slackbuilds to be more and more popular. Well, at least I hope so. If popularity means more whining and complaining non-contributing users, no, I am not particularly interested in that. > The gist of what I am proposing is to have an inkling of whether a > Slackbuilds package is being well maintained, before finding out so > after having to waste time and effort trying to install and make it > it work. Start the build. Go off and do something useful while it builds. After a reasonable time come back and see if it works. If it does not, you can move on, having invested only a few minutes. I think this thread has run its course. I see no need to continue. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From orbea at fredslev.dk Fri May 4 17:44:07 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Fri, 4 May 2018 10:44:07 -0700 Subject: [Slackbuilds-users] mdocml/mandoc SlackBuild Message-ID: <20180504104407.1a6ccd85@Akita.witch.org> Hi, I am interested in seeing the mdocml updated to the current upstream version of 1.14.3. Additionally it had since been renamed to mandoc upstream and should also be renamed for SBo. I have contacted the maintainer, but I have not received a reply even though I have waited more than a week. Does anyone have a reliable way of contacting the maintainer? If required I am willing to take over maintaining the SlackBuild. From matteo.bernardini at gmail.com Fri May 4 17:54:54 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 4 May 2018 19:54:54 +0200 Subject: [Slackbuilds-users] mdocml/mandoc SlackBuild In-Reply-To: <20180504104407.1a6ccd85@Akita.witch.org> References: <20180504104407.1a6ccd85@Akita.witch.org> Message-ID: 2018-05-04 19:44 GMT+02:00 orbea at fredslev.dk : > Hi, > > I am interested in seeing the mdocml updated to the current upstream > version of 1.14.3. Additionally it had since been renamed to mandoc > upstream and should also be renamed for SBo. > > I have contacted the maintainer, but I have not received a reply even > though I have waited more than a week. Does anyone have a reliable way > of contacting the maintainer? If required I am willing to take > over maintaining the SlackBuild. Daniel is usually pretty much active (last time eleven days ago), so maybe just wait a little more and he will surely get in touch. Matteo From khronosschoty at posteo.org Fri May 4 18:13:43 2018 From: khronosschoty at posteo.org (Vasily Sora) Date: Fri, 4 May 2018 11:13:43 -0700 Subject: [Slackbuilds-users] "[....] nobody will be led to think that packages are properly maintained throughout." In-Reply-To: References: Message-ID: <20180504181342.GA7454@darkstar.localhost> I think its already been mentioned here that there is no guarantee that the SlackBuilds will work. That information is kept inside the SlackBuild itself. I don't think we need to adopt a lengthy disclaimer on how its possible there might be scripts not working. Its impossible to cover ever last bit of information that needs to be covered right on the front page. The fact is everyone should review the SlackBuilds themselves before using them. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From thedoogster at gmail.com Fri May 4 18:17:30 2018 From: thedoogster at gmail.com (Doogster) Date: Fri, 4 May 2018 11:17:30 -0700 Subject: [Slackbuilds-users] "[....] nobody will be led to think that packages are properly maintained throughout." In-Reply-To: <20180504181342.GA7454@darkstar.localhost> References: <20180504181342.GA7454@darkstar.localhost> Message-ID: You don't have an automated (continuous integration) process to ensure that the SlackBuilds at least build on a clean, updated 14.2 system? On Fri, May 4, 2018 at 11:13 AM, Vasily Sora wrote: > I think its already been mentioned here that there is no guarantee that > the SlackBuilds will work. That information is kept inside the > SlackBuild itself. I don't think we need to adopt a lengthy disclaimer > on how its possible there might be scripts not working. Its impossible > to cover ever last bit of information that needs to be covered right on > the front page. The fact is everyone should review the SlackBuilds > themselves before using them. > > _______________________________________________ > 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 1.41421 at gmail.com Fri May 4 18:42:39 2018 From: 1.41421 at gmail.com (JCA) Date: Fri, 4 May 2018 12:42:39 -0600 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> <235e990a-61f5-75d7-1c8e-ee9e86d9a4db@slackbuilds.org> Message-ID: On Fri, May 4, 2018 at 10:50 AM, Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > 2018-05-04 18:40 GMT+02:00 JCA <1.41421 at gmail.com>: > > Fair enough. Now make sure to enter the gist of this in the Slackbuilds > home > > page, in a big font, so nobody will be led to think that packages are > > properly maintained throughout. > > it's not that finding a limited number of not maintained SlackBuilds > means that all of 7000 of them are unmaintained: just calculate the > percentage and you can see they are a very small part. > The fact still remains that poorly maintained packages exist. Why not say so, if it is true? This aside, my own experience is that I have to massage things often to get them to work - admittedly mostly in straightforward ways, although the plexmediaserver fiasco is not a first. Also bear in mind that package that has not been updated in a long time might still work, but might be missing important patches, security upgrades and improvements. Again, something that a good maintainer should be on top of. > >> Meanwhile, thanks for the report. > > > > > > Any time. My hope is that will do something to improve things for this, > and > > other packages in similar situations of abandonment. > > IMHO is only maintaining stuff yourself that helps in these cases. > True. However, like I said, I, and many like me, are not interested in maintaining, but on using. Again, this may be something frowned upon in this forum, and not in the spirit of Slackbuilds. This would be completely legitimate - just make it obvious in the home page that, if you want to make sure that a package is really functional, you should maintain it yourself, for it is neither the purview nor the responsibility of the Slackbuilds team to guarantee that maintainers of Slackbuilds packages are doing what they committed to do. This is what is already happening; it is just that, as a new Slackware/Slackbuilds user, one may not be aware of that initially. I think that not making this clear to such users amounts to making them a disservice. > > 2018-05-04 18:44 GMT+02:00 JCA <1.41421 at gmail.com>: > > wrote: > >> ...and this exposes the real issue: pretty much nobody reads the > >> READMEs or the scripts they run in the first place. > > > > > > Precisely. Which is why I was suggesting the Slackbuilds home page, in a > big > > font. In obnoxiously flashing text, if you want. That does not guarantee > > that people will read it, but it is far more difficult to miss. This > aside, > > that's boilerplate, legalese stuff. What matters is what can be > reasonably > > expected. > > I think you got this completely wrong: if you don't read the READMEs > and the scripts you run, it's just your fault and you shouldn't blame > nobody else. > And I think that you are not being realistic. Since probably the vast majority of freely distributed software packages contain similarly-worded disclaimers, those words mean very little. A very conspicuous warning in the Slackware home page would command more attention. And would kill discussions like this before they are even born, for everybody who has visited the Slackbuilds page even once would have no choice but to see the warning. Just make it clear in that page that Slackbuilds is for enthusiasts, by enthusiasts; that packages may, or may not, work; that they may, or may not, be maintained; that the vast majority of them seem to be maintained and work, although nothing can be guaranteed; that, if you want to make sure, just maintain yourself the packages that you are interested in. That's the way it is. And it may be intentional. Which would, again, be completely legitimate. > Matteo > _______________________________________________ > 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 orbea at fredslev.dk Fri May 4 20:03:08 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Fri, 4 May 2018 13:03:08 -0700 Subject: [Slackbuilds-users] guix and guile-json Message-ID: <20180504130308.09dac3b9@Akita.witch.org> I am the maintainer of the guix SlackBuild and its optional dependency, guile-json. However I have suffered deal breaking runtime issues which may or not be pebkac and an unresponsive upstream. I lack the knowledge and interest in guile to pursue this further. So if anyone would be willing to take over maintaining guix and/or guile-json they are up for grabs. Alternatively I would not complain if they are removed. Both are several versions out of date and could be updated. Thanks, Hunter From yth at ythogtha.org Fri May 4 21:11:11 2018 From: yth at ythogtha.org (Ythogtha) Date: Fri, 4 May 2018 23:11:11 +0200 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> <235e990a-61f5-75d7-1c8e-ee9e86d9a4db@slackbuilds.org> Message-ID: <20180504231111.fe07c766b0bd55d771919ee8@ythogtha.org> > > > Fair enough. Now make sure to enter the gist of this in the Slackbuilds > > > home > > > page, in a big font, so nobody will be led to think that packages are > > > properly maintained throughout. But they are, properly maintained... > > it's not that finding a limited number of not maintained SlackBuilds > > means that all of 7000 of them are unmaintained: just calculate the > > percentage and you can see they are a very small part. > The fact still remains that poorly maintained packages exist. Why not say > so, if it is true? Because, maybe, it is not relevant? What IS SBo ? It is a collection of scripts that are allowing you, or anybody, to compile and build a (awful big) lot of softwares, more easily than starting from scratch. It simply turns out that this works well enough that some people not directly related to either Slackware or Sbo, thought they could make things even easier by providing tools like sbopkg. But SBo is *only* a tool for bootstraping *your* work on building your own package ! And most of the time, really really most of the time, you have nothing else to do than running package.Slackbuild (or "your_favorite_SBo_tool build package"). This is the Slackware way, not the Redhat or Ubuntu backed-up by big (or huge) companies. This is volunteer work, nobody's being paid here, and the whole SBo project isn't even part of Slackware ! Though patrick acknowledged it's quality by officially endorsing it, which means only that he thinks we're doing a job worth of being noticed, and worth of the Slackware philosophy. If people want to be simple users, and not handle the work that comes with slackbuilding your own packages, there are very good binary repositories out there, with which you don't have anything to do. That is the way of the people who don't want to handle messy stuff. For example : https://packages.slackonly.com/pub/packages/14.2-x86_64/multimedia/plexmediaserver/ -- Arnaud From jebrhansen+SBo at gmail.com Fri May 4 22:30:33 2018 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 04 May 2018 22:30:33 +0000 Subject: [Slackbuilds-users] Plex version too old In-Reply-To: References: <85eb9611-de7f-131b-3893-15051e8f2bca@dcclost.com> <235e990a-61f5-75d7-1c8e-ee9e86d9a4db@slackbuilds.org> Message-ID: On Fri, May 4, 2018, 12:42 PM JCA <1.41421 at gmail.com> wrote: > On Fri, May 4, 2018 at 10:50 AM, Matteo Bernardini < > matteo.bernardini at gmail.com> wrote: > >> 2018-05-04 18:40 GMT+02:00 JCA <1.41421 at gmail.com>: >> > Fair enough. Now make sure to enter the gist of this in the Slackbuilds >> home >> > page, in a big font, so nobody will be led to think that packages are >> > properly maintained throughout. >> >> it's not that finding a limited number of not maintained SlackBuilds >> means that all of 7000 of them are unmaintained: just calculate the >> percentage and you can see they are a very small part. >> > > The fact still remains that poorly maintained packages exist. Why not say > so, if it is true? > > This aside, my own experience is that I have to massage things often to > get them to work - admittedly mostly in straightforward ways, although the > plexmediaserver fiasco is not a first. Also bear in mind that package that > has not been updated in a long time might still work, but might be missing > important patches, security upgrades and improvements. Again, something > that a good maintainer should be on top of. > > >> >> Meanwhile, thanks for the report. >> > >> > >> > Any time. My hope is that will do something to improve things for this, >> and >> > other packages in similar situations of abandonment. >> >> IMHO is only maintaining stuff yourself that helps in these cases. >> > > True. However, like I said, I, and many like me, are not interested in > maintaining, but on using. Again, this may be something frowned upon in > this forum, and not in the spirit of Slackbuilds. This would be completely > legitimate - just make it obvious in the home page that, if you want to > make sure that a package is really functional, you should maintain it > yourself, for it is neither the purview nor the responsibility of the > Slackbuilds team to guarantee that maintainers of Slackbuilds packages are > doing what they committed to do. This is what is already happening; it is > just that, as a new Slackware/Slackbuilds user, one may not be aware of > that initially. I think that not making this clear to such users amounts to > making them a disservice. > > >> >> 2018-05-04 18:44 GMT+02:00 JCA <1.41421 at gmail.com>: >> > wrote: >> >> ...and this exposes the real issue: pretty much nobody reads the >> >> READMEs or the scripts they run in the first place. >> > >> > >> > Precisely. Which is why I was suggesting the Slackbuilds home page, in >> a big >> > font. In obnoxiously flashing text, if you want. That does not guarantee >> > that people will read it, but it is far more difficult to miss. This >> aside, >> > that's boilerplate, legalese stuff. What matters is what can be >> reasonably >> > expected. >> >> I think you got this completely wrong: if you don't read the READMEs >> and the scripts you run, it's just your fault and you shouldn't blame >> nobody else. >> > > And I think that you are not being realistic. Since probably the vast > majority of freely distributed software packages contain similarly-worded > disclaimers, those words mean very little. A very conspicuous warning in > the Slackware home page would command more attention. And would kill > discussions like this before they are even born, for everybody who has > visited the Slackbuilds page even once would have no choice but to see the > warning. > > Just make it clear in that page that Slackbuilds is for enthusiasts, by > enthusiasts; that packages may, or may not, work; that they may, or may > not, be maintained; that the vast majority of them seem to be maintained > and work, although nothing can be guaranteed; that, if you want to make > sure, just maintain yourself the packages that you are interested in. > That's the way it is. And it may be intentional. Which would, again, be > completely legitimate. > > >> Matteo >> _______________________________________________ >> 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/ >> >> _______________________________________________ > 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/ So, we have a project that you're using, but refuse to contributing to (other than bug reports and complaints) and yet you complain that it isn't being run the way *you* want? Even when the admins all state it's been run the way *they* want? You seem to think that the frontpage will be read, but most people probably use tools to interact with SBo (sbotools, sbopkg, slackrepo, etc), so a notice on the frontage would go unnoticed. We already know that a lot of READMEs go unread based on reports here and on LQ. If anything belongs anywhere, it'd probably be an entry in the FAQ on if a package isn't working as expected and what to do (which may already be there, but I'm on mobile and too lazy to look). Why is it so hard to just contact the maintainer when something is broken (especially since there's a link on that SlackBuild's page)? You can even CC this list in case the maintainer doesn't respond. The amount of scripts that are broken are probably quite small, and if the maintainers aren't quick to respond or it's an easy fix, the admins will usually fix it relatively quick. Long story short, the current prices works great for almost everyone but you. Since you refuse to take up the mantle of maintainership, you lose a lot of credibility when you complain how others, who have stepped up at some point, handle their SlackBuilds. And it isn't always trivial to get a SlackBuild generated, especially when you need to create patches, rc files, or other tweaks that may be required. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat May 5 00:00:41 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 May 2018 07:00:41 +0700 Subject: [Slackbuilds-users] Updates - 20180504.1 Message-ID: <61147ecc-61ad-8319-b003-c959f9fb947c@slackbuilds.org> Hi Welcome to first update in May. Wireshark is now bumped to 2.6.0 and this branch (2.6.x) will be the last version that supports GTK+-based UI. Next major version will completely removed it and it's only Qt5-based. As for maintainers, we remind you to always take our latest version of SlackBuild from our website or repository before pushing an update as we (admins) might have made some changes to your submission. Failing to do so might results in a rejection of the submission and then it will have to be resubmitted and wait in the pending queue again. For new scripts, also please make sure to use the latest template files available here https://slackbuilds.org/templates/. Do not use an old copy from your other scripts. Enjoy your weekend :) Fri May 4 23:47:20 UTC 2018 academic/QtiPlot: Updated homepage. academic/R: Updated for version 3.5.0. academic/biblesync: Updated for version 2.0.1. academic/sundials: Updated for version 3.1.0. audio/atunes: Fixed download. audio/audioconvert: Added (Audio Sync and Conversion Utility). audio/fst: Update homepage. audio/qmmp-plugin-pack-qt5: Added (additional plugins for Qmmp). audio/qmmp-qt5: Added (QT based multimedia player). desktop/Zafiro-icons: Added (icon pack flat with light colors). desktop/adapta-gtk-theme: Added (Gtk+ theme). desktop/bunsen-themes: Updated for version 9.4.1. desktop/mh5000: Fixed md5sum. desktop/openbox-themes-extra: Added (additional themes for Openbox). desktop/oranchelo-icon-theme: Updated for version 0.7.6.8.1. development/android-studio: Updated for version 3.1.2.0_173_4720617. development/d-tools: Updated for version 2.080.0 development/dmd: Updated for version 2.080.0 development/git-cola: Updated for version 3.1. development/google-go-lang: Updated for version 1.10.2. development/ht: Added (file viewer, analyzer for files). development/icecream: Fixed download. development/jupyter-nbdime: Update REQUIRES. development/kotlin: Updated for version 1.2.41. development/love: Updated for version 11.1. development/mcrl2: Updated homepage and download. development/meld3: Updated for version 3.18.1. development/mrustc: Updated for git173dfa9. development/qbs: Updated for version 1.11.1. development/qt-creator-llvm: Updated with new patches from upstream. development/qt-creator: Updated for version 4.6.1. development/rmlmmc: Update homepage. development/scala: Updated homepage. development/tanya: Updated for version 0.8.1 development/tiled: Updated for version 1.1.5. development/universal-ctags: Updated for version 576c750 games/RetroArch: Updated for version 1.7.3. games/flare-game: Updated for version 1.05. games/flare: Updated for version 1.05. gis/OTB: Script improvements. gis/osm2pgsql: Updated for version 0.96.0. gis/ossim: Updated for version 2.3.2. graphics/FreeCAD: Updated for version 0.17. graphics/openimageio: Updated for version 1.8.11 graphics/qelectrotech: Updated for version 0.6. libraries/CGAL: Updated for version 4.12. libraries/exiftool: Updated for version 10.80. libraries/futures: Updated for version 3.2.0. libraries/jai-imageio: Updated homepage and dowload. libraries/jai: Updated homepage and download. libraries/leptonica: Updated for version 1.76.0. libraries/libetonyek: Updated for version 0.1.8. libraries/libhoard: Fixed download. libraries/libinput: Updated for version 1.10.6. libraries/libmwaw: Updated for version 0.3.14. libraries/libstaroffice: Updated for version 0.0.6. libraries/libwps: Updated for version 0.4.9. libraries/opencv: Patched to suit ffmpeg misc/grc: Updated for version 1.11.3. misc/mosquitto: Updated for version 1.5 misc/sgrep: Added (sorted grep). multimedia/devedeng: Updated for version 4.10.0. network/basilisk-src: Updated for version 2018.04.23. network/opera-legacy: Updated homepage and download. network/sflowtool: Fixed md5sum. network/signal-desktop: Updated for version 1.9.0. network/vnstat: Updated homepage and download. network/wireshark: Updated for version 2.6.0. office/gnucash-docs: added PDF and EPUB to build options. office/gnucash3-docs: Updated for version 3.1. office/gnucash3: Updated for version 3.1. office/gnucash: Change option to WITHPYTHON. office/mobiperl: Update homepage and download. office/notmuch: Updated for version 0.26.2. perl/perl-ExtUtils-ModuleMaker: Updated for version 0.57. python/gunicorn: Updated for version 19.8.0. python/python-neovim: Updated for version 0.2.6. python/thonny: Updated for version 2.1.17. ruby/sequel: Updated for version 5.8.0. system/ZoneMinder: Updated for version 1.31.1. system/alacritty: Updated for version gitabe678c. system/dislocker: Added (read/write Windows BitLocker-ed volumes). system/foomatic-db-engine: Updated for version 4.0.13. system/isdct: Updated for version 3.0.12. system/lynis: Updated for version 2.6.4. system/nano-syntax-highlighting: Added (Nano Syntax Highlighting). system/pdfgrep: Updated for version 2.1.0. system/pspg: Updated for version 1.1.1. system/samhain: Updated for version 4.2.4. system/spman: Updated for version 1.5.0. system/tm: Fixed version. system/tp_smapi: Fixed download. system/vagrant: Updated for version 2.1.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From artourter at gmail.com Sat May 5 13:18:37 2018 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sat, 5 May 2018 14:18:37 +0100 Subject: [Slackbuilds-users] Updates - 20180504.1 In-Reply-To: <61147ecc-61ad-8319-b003-c959f9fb947c@slackbuilds.org> References: <61147ecc-61ad-8319-b003-c959f9fb947c@slackbuilds.org> Message-ID: The info file for android-studio seems to be using some unicode characters instead of / https:??dl.google.com ?dl?android?studio?ide-zips?3.1.2.0?android-studio-ide-173.4720617-linux.zip it should be https://dl.google.com/dl/android/studio/ide-zips/3.1.2.0/android-studio-ide-173.4720617-linux.zip Cheers Greg On 5 May 2018 at 01:00, Willy Sudiarto Raharjo wrote: > Hi > > Welcome to first update in May. > > Wireshark is now bumped to 2.6.0 and this branch (2.6.x) will be the > last version that supports GTK+-based UI. Next major version will > completely removed it and it's only Qt5-based. > > As for maintainers, we remind you to always take our latest version of > SlackBuild from our website or repository before pushing an update as we > (admins) might have made some changes to your submission. Failing to do > so might results in a rejection of the submission and then it will have > to be resubmitted and wait in the pending queue again. > > For new scripts, also please make sure to use the latest template files > available here https://slackbuilds.org/templates/. Do not use an old > copy from your other scripts. > > Enjoy your weekend :) > > > Fri May 4 23:47:20 UTC 2018 > academic/QtiPlot: Updated homepage. > academic/R: Updated for version 3.5.0. > academic/biblesync: Updated for version 2.0.1. > academic/sundials: Updated for version 3.1.0. > audio/atunes: Fixed download. > audio/audioconvert: Added (Audio Sync and Conversion Utility). > audio/fst: Update homepage. > audio/qmmp-plugin-pack-qt5: Added (additional plugins for Qmmp). > audio/qmmp-qt5: Added (QT based multimedia player). > desktop/Zafiro-icons: Added (icon pack flat with light colors). > desktop/adapta-gtk-theme: Added (Gtk+ theme). > desktop/bunsen-themes: Updated for version 9.4.1. > desktop/mh5000: Fixed md5sum. > desktop/openbox-themes-extra: Added (additional themes for Openbox). > desktop/oranchelo-icon-theme: Updated for version 0.7.6.8.1. > development/android-studio: Updated for version 3.1.2.0_173_4720617. > development/d-tools: Updated for version 2.080.0 > development/dmd: Updated for version 2.080.0 > development/git-cola: Updated for version 3.1. > development/google-go-lang: Updated for version 1.10.2. > development/ht: Added (file viewer, analyzer for files). > development/icecream: Fixed download. > development/jupyter-nbdime: Update REQUIRES. > development/kotlin: Updated for version 1.2.41. > development/love: Updated for version 11.1. > development/mcrl2: Updated homepage and download. > development/meld3: Updated for version 3.18.1. > development/mrustc: Updated for git173dfa9. > development/qbs: Updated for version 1.11.1. > development/qt-creator-llvm: Updated with new patches from upstream. > development/qt-creator: Updated for version 4.6.1. > development/rmlmmc: Update homepage. > development/scala: Updated homepage. > development/tanya: Updated for version 0.8.1 > development/tiled: Updated for version 1.1.5. > development/universal-ctags: Updated for version 576c750 > games/RetroArch: Updated for version 1.7.3. > games/flare-game: Updated for version 1.05. > games/flare: Updated for version 1.05. > gis/OTB: Script improvements. > gis/osm2pgsql: Updated for version 0.96.0. > gis/ossim: Updated for version 2.3.2. > graphics/FreeCAD: Updated for version 0.17. > graphics/openimageio: Updated for version 1.8.11 > graphics/qelectrotech: Updated for version 0.6. > libraries/CGAL: Updated for version 4.12. > libraries/exiftool: Updated for version 10.80. > libraries/futures: Updated for version 3.2.0. > libraries/jai-imageio: Updated homepage and dowload. > libraries/jai: Updated homepage and download. > libraries/leptonica: Updated for version 1.76.0. > libraries/libetonyek: Updated for version 0.1.8. > libraries/libhoard: Fixed download. > libraries/libinput: Updated for version 1.10.6. > libraries/libmwaw: Updated for version 0.3.14. > libraries/libstaroffice: Updated for version 0.0.6. > libraries/libwps: Updated for version 0.4.9. > libraries/opencv: Patched to suit ffmpeg > misc/grc: Updated for version 1.11.3. > misc/mosquitto: Updated for version 1.5 > misc/sgrep: Added (sorted grep). > multimedia/devedeng: Updated for version 4.10.0. > network/basilisk-src: Updated for version 2018.04.23. > network/opera-legacy: Updated homepage and download. > network/sflowtool: Fixed md5sum. > network/signal-desktop: Updated for version 1.9.0. > network/vnstat: Updated homepage and download. > network/wireshark: Updated for version 2.6.0. > office/gnucash-docs: added PDF and EPUB to build options. > office/gnucash3-docs: Updated for version 3.1. > office/gnucash3: Updated for version 3.1. > office/gnucash: Change option to WITHPYTHON. > office/mobiperl: Update homepage and download. > office/notmuch: Updated for version 0.26.2. > perl/perl-ExtUtils-ModuleMaker: Updated for version 0.57. > python/gunicorn: Updated for version 19.8.0. > python/python-neovim: Updated for version 0.2.6. > python/thonny: Updated for version 2.1.17. > ruby/sequel: Updated for version 5.8.0. > system/ZoneMinder: Updated for version 1.31.1. > system/alacritty: Updated for version gitabe678c. > system/dislocker: Added (read/write Windows BitLocker-ed volumes). > system/foomatic-db-engine: Updated for version 4.0.13. > system/isdct: Updated for version 3.0.12. > system/lynis: Updated for version 2.6.4. > system/nano-syntax-highlighting: Added (Nano Syntax Highlighting). > system/pdfgrep: Updated for version 2.1.0. > system/pspg: Updated for version 1.1.1. > system/samhain: Updated for version 4.2.4. > system/spman: Updated for version 1.5.0. > system/tm: Fixed version. > system/tp_smapi: Fixed download. > system/vagrant: Updated for version 2.1.0. > +--------------------------+ > > > -- > 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 dpross1100 at msn.com Sat May 5 13:35:21 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 5 May 2018 13:35:21 +0000 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder Message-ID: Hi, ZoneMinder was upgraded to version 1.31.1 in the last update. The new version builds fine, but I am having trouble running the zmupdate.pl script to update my database. Using this command: /usr/bin/zmupdate.pl --version=1.30.4 --user={dbuser} --pass={dbpass} I get this result: ---------- Initiating database upgrade to version 1.31.1 from version 1.30.4 Please ensure that ZoneMinder is stopped on your system prior to upgrading the database. Press enter to continue or ctrl-C to stop : Do you wish to take a backup of your database prior to upgrading? This may result in a large file in /var/tmp/zm if you have a lot of events. Press 'y' for a backup or 'n' to continue : n Upgrading database to version 1.31.1 Loading config from DBNo option 'ZM_DIR_EVENTS' found, removing. No option 'ZM_DIR_IMAGES' found, removing. No option 'ZM_DIR_SOUNDS' found, removing. No option 'ZM_FRAME_SOCKET_SIZE' found, removing. No option 'ZM_OPT_FRAME_SERVER' found, removing. No option 'ZM_PATH_ARP' found, removing. No option 'ZM_PATH_LOGS' found, removing. No option 'ZM_PATH_MAP' found, removing. No option 'ZM_PATH_SOCKS' found, removing. No option 'ZM_PATH_SWAP' found, removing. No option 'ZM_PATH_ZMS' found, removing. 207 entries Saving config to DB 207 entries DBD::mysql::db do failed: Access denied for user 'zmuser'@'localhost' to database 'zm' at /usr/share/perl5/vendor_perl/ZoneMinder/Config.pm line 214, line 2. Can't lock Config table: Access denied for user 'zmuser'@'localhost' to database 'zm' at /usr/bin/zmupdate.pl line 464. ---------- I have also tried without specifying --user and --pass, but I get the same error. For now I have gone back to my old version and restored the backup database. I can also ask on the ZoneMinder forums, but I'm not sure if the issue lies with zmupdate.pl or with the way ZoneMinder is configured by the SBo package. Seems like pretty much everyone over there uses Ubuntu, CentOS, or Debian. Dan From kjhambrick at gmail.com Sat May 5 13:42:00 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 5 May 2018 08:42:00 -0500 Subject: [Slackbuilds-users] google-go-lang.SlackBuild Version 1.10.2 + RUN_TEST=true fails with CC=gcc Message-ID: Vincent -- I am running Slackware64 14.2 + Multilib on a 4.4.131 Kernel. I've been building google-go-lang with the RUN_TEST=true option since last November or so and I've been keeping up with SBo Updates and RUN_TEST=true has always worked just fine for `go` versions 1.8.5, 1.9.2 and 1.9.5 However with this weekend's Version 1.10.2 Update, the SlackBuild failed with RUN_TEST=true on the ../misc/cgo/testsanitizers tests Log Snippet is below ... but I can send the full log if you like. I found a number of hits on google about the failure and this one: https://github.com/golang/go/issues/14602 suggested setting CC=clang ( for clang .ge. 3.8 ) to get past the testsanitizers fail. A very simple patch is attached. Setting CC=clang did work for me, but I am not sure if it is a good idea to override gcc with clang ... I've got a few test programs that I'll be running thru `go` when I get a break from my work schedule. I'll let you know if I see any issues with the compiler switch. Thanks for the google-go-lang.SlackBuild Vincent ! -- kjh # testsanitizers fail from my SBo build log: # ----------------------------------------- #### ../misc/cgo/testsanitizers --- FAIL: TestShared (0.02s) --- FAIL: TestShared/tsan_shared (1.61s) cshared_test.go:71: `/tmp/TestShared867470121/tsan_shared` exited with exit status 66 ================== WARNING: ThreadSanitizer: data race (pid=8218) Write of size 8 at 0x7f241f795c70 by thread T1: #0 pthread_attr_getstacksize (tsan_shared+0x00000041bcf2) #1 x_cgo_init (libtsan_shared.so+0x00000008961f) #2 runtime.rt0_go /tmp/SBo/package-google-go-lang/usr/lib64/go1.10.2/go/src/runtime/ asm_amd64.s:199 (libtsan_shared.so+0x00000007fdf6) Previous write of size 8 at 0x7f241f795c70 by main thread: #0 (0x000000000001) Location is stack of thread T1. Thread T1 (tid=8225, running) created by main thread at: #0 pthread_create (tsan_shared+0x00000040c604) #1 _cgo_try_pthread_create (libtsan_shared.so+0x0000000894e0) #2 x_cgo_sys_thread_create (libtsan_shared.so+0x000000089282) #3 _rt0_amd64_lib /tmp/SBo/package-google-go-lang/usr/lib64/go1.10.2/go/src/runtime/ <> asm_amd64.s:56 (libtsan_shared.so+0x00000007fc26) SUMMARY: ThreadSanitizer: data race ??:0 threadentry ================== ThreadSanitizer: reported 5 warnings FAIL 2018/05/05 07:08:40 Failed: exit status 1 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: google-go-lang.SlackBuild-patch-for-RUN_TEST-true.patch Type: text/x-patch Size: 806 bytes Desc: not available URL: From willysr at slackbuilds.org Sat May 5 14:13:30 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 May 2018 21:13:30 +0700 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: > ZoneMinder was upgraded to version 1.31.1 in the last update. The new > version builds fine, but I am having trouble running the zmupdate.pl > script to update my database. Using this command: > > /usr/bin/zmupdate.pl --version=1.30.4 --user={dbuser} --pass={dbpass} > > I get this result: > > ---------- > Initiating database upgrade to version 1.31.1 from version 1.30.4 > > Please ensure that ZoneMinder is stopped on your system prior to > upgrading the database. > Press enter to continue or ctrl-C to stop : > > Do you wish to take a backup of your database prior to upgrading? > This may result in a large file in /var/tmp/zm if you have a lot of > events. > Press 'y' for a backup or 'n' to continue : n > > Upgrading database to version 1.31.1 > Loading config from DBNo option 'ZM_DIR_EVENTS' found, removing. > No option 'ZM_DIR_IMAGES' found, removing. > No option 'ZM_DIR_SOUNDS' found, removing. > No option 'ZM_FRAME_SOCKET_SIZE' found, removing. > No option 'ZM_OPT_FRAME_SERVER' found, removing. > No option 'ZM_PATH_ARP' found, removing. > No option 'ZM_PATH_LOGS' found, removing. > No option 'ZM_PATH_MAP' found, removing. > No option 'ZM_PATH_SOCKS' found, removing. > No option 'ZM_PATH_SWAP' found, removing. > No option 'ZM_PATH_ZMS' found, removing. > 207 entries > Saving config to DB 207 entries > DBD::mysql::db do failed: Access denied for user 'zmuser'@'localhost' to > database 'zm' at /usr/share/perl5/vendor_perl/ZoneMinder/Config.pm line > 214, line 2. > Can't lock Config table: Access denied for user 'zmuser'@'localhost' to > database 'zm' at /usr/bin/zmupdate.pl line 464. > ---------- > > I have also tried without specifying --user and --pass, but I get the > same error. For now I have gone back to my old version and restored the > backup database. I can also ask on the ZoneMinder forums, but I'm not > sure if the issue lies with zmupdate.pl or with the way ZoneMinder is > configured by the SBo package. Seems like pretty much everyone over > there uses Ubuntu, CentOS, or Debian. After looking at the last commit, it seems a mystery for me as the sources are taken NOT from upstream but from third party repository. The latest release by upstream is still at 1.30.4 as well. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat May 5 14:15:23 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 May 2018 21:15:23 +0700 Subject: [Slackbuilds-users] Updates - 20180504.1 In-Reply-To: References: <61147ecc-61ad-8319-b003-c959f9fb947c@slackbuilds.org> Message-ID: <0d567bbd-434c-68df-51e6-61eda4c13b66@slackbuilds.org> > The info file for android-studio seems to be using some unicode > characters instead of / > > https:??dl.google.com > ?dl?android?studio?ide-zips?3.1.2.0?android-studio-ide-173.4720617-linux.zip > > it should be > > https://dl.google.com/dl/android/studio/ide-zips/3.1.2.0/android-studio-ide-173.4720617-linux.zip Thanks fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From dpross1100 at msn.com Sat May 5 18:24:34 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 5 May 2018 18:24:34 +0000 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: Interesting. I didn't catch that. In that case, I will just stick with 1.30.4. It would be nice to hear from the maintainer why it was updated in the first place. Dan On Sat, May 05, 2018 at 09:13:30PM +0700, Willy Sudiarto Raharjo wrote: > > ZoneMinder was upgraded to version 1.31.1 in the last update. The new > > version builds fine, but I am having trouble running the zmupdate.pl > > script to update my database. Using this command: > > > > /usr/bin/zmupdate.pl --version=1.30.4 --user={dbuser} --pass={dbpass} > > > > I get this result: > > > > ---------- > > Initiating database upgrade to version 1.31.1 from version 1.30.4 > > > > Please ensure that ZoneMinder is stopped on your system prior to > > upgrading the database. > > Press enter to continue or ctrl-C to stop : > > > > Do you wish to take a backup of your database prior to upgrading? > > This may result in a large file in /var/tmp/zm if you have a lot of > > events. > > Press 'y' for a backup or 'n' to continue : n > > > > Upgrading database to version 1.31.1 > > Loading config from DBNo option 'ZM_DIR_EVENTS' found, removing. > > No option 'ZM_DIR_IMAGES' found, removing. > > No option 'ZM_DIR_SOUNDS' found, removing. > > No option 'ZM_FRAME_SOCKET_SIZE' found, removing. > > No option 'ZM_OPT_FRAME_SERVER' found, removing. > > No option 'ZM_PATH_ARP' found, removing. > > No option 'ZM_PATH_LOGS' found, removing. > > No option 'ZM_PATH_MAP' found, removing. > > No option 'ZM_PATH_SOCKS' found, removing. > > No option 'ZM_PATH_SWAP' found, removing. > > No option 'ZM_PATH_ZMS' found, removing. > > 207 entries > > Saving config to DB 207 entries > > DBD::mysql::db do failed: Access denied for user 'zmuser'@'localhost' to > > database 'zm' at /usr/share/perl5/vendor_perl/ZoneMinder/Config.pm line > > 214, line 2. > > Can't lock Config table: Access denied for user 'zmuser'@'localhost' to > > database 'zm' at /usr/bin/zmupdate.pl line 464. > > ---------- > > > > I have also tried without specifying --user and --pass, but I get the > > same error. For now I have gone back to my old version and restored the > > backup database. I can also ask on the ZoneMinder forums, but I'm not > > sure if the issue lies with zmupdate.pl or with the way ZoneMinder is > > configured by the SBo package. Seems like pretty much everyone over > > there uses Ubuntu, CentOS, or Debian. > > After looking at the last commit, it seems a mystery for me as the > sources are taken NOT from upstream but from third party repository. The > latest release by upstream is still at 1.30.4 as well. > > > > -- > 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/ > From geno.bob at gmail.com Sat May 5 22:51:08 2018 From: geno.bob at gmail.com (Geno Bob) Date: Sat, 5 May 2018 15:51:08 -0700 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: Daniel, According to your error, your credentials are incorrect for your SQL database. Try signing into your database using mysql -u zmuser -p when it asks for a password put in your password (the same credentials you used in the 'zmupdate.pl' command above). Thank you, On Sat, May 5, 2018 at 6:35 AM, Daniel Prosser wrote: > Hi, > > ZoneMinder was upgraded to version 1.31.1 in the last update. The new > version builds fine, but I am having trouble running the zmupdate.pl > script to update my database. Using this command: > > /usr/bin/zmupdate.pl --version=1.30.4 --user={dbuser} --pass={dbpass} > > I get this result: > > ---------- > Initiating database upgrade to version 1.31.1 from version 1.30.4 > > Please ensure that ZoneMinder is stopped on your system prior to > upgrading the database. > Press enter to continue or ctrl-C to stop : > > Do you wish to take a backup of your database prior to upgrading? > This may result in a large file in /var/tmp/zm if you have a lot of > events. > Press 'y' for a backup or 'n' to continue : n > > Upgrading database to version 1.31.1 > Loading config from DBNo option 'ZM_DIR_EVENTS' found, removing. > No option 'ZM_DIR_IMAGES' found, removing. > No option 'ZM_DIR_SOUNDS' found, removing. > No option 'ZM_FRAME_SOCKET_SIZE' found, removing. > No option 'ZM_OPT_FRAME_SERVER' found, removing. > No option 'ZM_PATH_ARP' found, removing. > No option 'ZM_PATH_LOGS' found, removing. > No option 'ZM_PATH_MAP' found, removing. > No option 'ZM_PATH_SOCKS' found, removing. > No option 'ZM_PATH_SWAP' found, removing. > No option 'ZM_PATH_ZMS' found, removing. > 207 entries > Saving config to DB 207 entries > DBD::mysql::db do failed: Access denied for user 'zmuser'@'localhost' to > database 'zm' at /usr/share/perl5/vendor_perl/ZoneMinder/Config.pm line > 214, line 2. > Can't lock Config table: Access denied for user 'zmuser'@'localhost' to > database 'zm' at /usr/bin/zmupdate.pl line 464. > ---------- > > I have also tried without specifying --user and --pass, but I get the > same error. For now I have gone back to my old version and restored the > backup database. I can also ask on the ZoneMinder forums, but I'm not > sure if the issue lies with zmupdate.pl or with the way ZoneMinder is > configured by the SBo package. Seems like pretty much everyone over > there uses Ubuntu, CentOS, or Debian. > > Dan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dpross1100 at msn.com Sun May 6 03:12:12 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Sun, 6 May 2018 03:12:12 +0000 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: I failed to reply all in my previous message, but anyway it wasn't very important. The long and short of it was that I changed the password for the "zmuser" DB user, but I think I needed to regrant permission to the zm database after that. However, after taking care of that and ensuring I can log in to mysql as zmuser, I am right back to the original error when I try to run zmupdate.pl. But anyway, as far as I'm concerned, I'm not going to upgrade to a new version until it's actually released by upstream. Hopefully the zmupdate script will work when that happens. Dan On Sat, May 05, 2018 at 03:51:08PM -0700, Geno Bob wrote: > Daniel, > According to your error, your credentials are incorrect for your SQL > database. Try signing into your database using mysql -u zmuser -p > when it asks for a password put in your password (the same credentials > you used in the '[1]zmupdate.pl' command above). > Thank you, > > On Sat, May 5, 2018 at 6:35 AM, Daniel Prosser <[2]dpross1100 at msn.com> > wrote: > > Hi, > ZoneMinder was upgraded to version 1.31.1 in the last update. The > new > version builds fine, but I am having trouble running the > [3]zmupdate.pl > script to update my database. Using this command: > /usr/bin/[4]zmupdate.pl --version=1.30.4 --user={dbuser} > --pass={dbpass} > I get this result: > ---------- > Initiating database upgrade to version 1.31.1 from version 1.30.4 > Please ensure that ZoneMinder is stopped on your system prior to > upgrading the database. > Press enter to continue or ctrl-C to stop : > Do you wish to take a backup of your database prior to upgrading? > This may result in a large file in /var/tmp/zm if you have a lot of > events. > Press 'y' for a backup or 'n' to continue : n > Upgrading database to version 1.31.1 > Loading config from DBNo option 'ZM_DIR_EVENTS' found, removing. > No option 'ZM_DIR_IMAGES' found, removing. > No option 'ZM_DIR_SOUNDS' found, removing. > No option 'ZM_FRAME_SOCKET_SIZE' found, removing. > No option 'ZM_OPT_FRAME_SERVER' found, removing. > No option 'ZM_PATH_ARP' found, removing. > No option 'ZM_PATH_LOGS' found, removing. > No option 'ZM_PATH_MAP' found, removing. > No option 'ZM_PATH_SOCKS' found, removing. > No option 'ZM_PATH_SWAP' found, removing. > No option 'ZM_PATH_ZMS' found, removing. > 207 entries > Saving config to DB 207 entries > DBD::mysql::db do failed: Access denied for user > 'zmuser'@'localhost' to > database 'zm' at /usr/share/perl5/vendor_perl/ZoneMinder/Config.pm > line > 214, line 2. > Can't lock Config table: Access denied for user 'zmuser'@'localhost' > to > database 'zm' at /usr/bin/[5]zmupdate.pl line 464. > ---------- > I have also tried without specifying --user and --pass, but I get > the > same error. For now I have gone back to my old version and restored > the > backup database. I can also ask on the ZoneMinder forums, but I'm > not > sure if the issue lies with [6]zmupdate.pl or with the way > ZoneMinder is > configured by the SBo package. Seems like pretty much everyone over > there uses Ubuntu, CentOS, or Debian. > Dan > > References > > 1. http://zmupdate.pl/ > 2. mailto:dpross1100 at msn.com > 3. http://zmupdate.pl/ > 4. http://zmupdate.pl/ > 5. http://zmupdate.pl/ > 6. http://zmupdate.pl/ From geno.bob at gmail.com Sun May 6 07:11:37 2018 From: geno.bob at gmail.com (Geno Bob) Date: Sun, 6 May 2018 00:11:37 -0700 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: If you get a few minutes, you might try updating the database one step at a time. You are going from 1.30.4 right to 1.31.1, however there is a decent amount of updates in the 1.31.0 db file. Try updating the db to 1.31.0 and then to 1.31.1 and see if it makes a difference. When I get a chance I will spin up a VM with 1.30.4 and see if I cant replicate your issue. Also, Urchlay is THE urchlay. If you ever go onto a slackware forum or IRC, he will be there. Thank you, GenoBob On Sat, May 5, 2018 at 8:12 PM, Daniel Prosser wrote: > I failed to reply all in my previous message, but anyway it wasn't very > important. The long and short of it was that I changed the password for > the "zmuser" DB user, but I think I needed to regrant permission to the > zm database after that. However, after taking care of that and ensuring > I can log in to mysql as zmuser, I am right back to the original error > when I try to run zmupdate.pl. > > But anyway, as far as I'm concerned, I'm not going to upgrade to a new > version until it's actually released by upstream. Hopefully the zmupdate > script will work when that happens. > > Dan > > On Sat, May 05, 2018 at 03:51:08PM -0700, Geno Bob wrote: > > Daniel, > > According to your error, your credentials are incorrect for your SQL > > database. Try signing into your database using mysql -u zmuser -p > > when it asks for a password put in your password (the same credentials > > you used in the '[1]zmupdate.pl' command above). > > Thank you, > > > > On Sat, May 5, 2018 at 6:35 AM, Daniel Prosser <[2]dpross1100 at msn.com > > > > wrote: > > > > Hi, > > ZoneMinder was upgraded to version 1.31.1 in the last update. The > > new > > version builds fine, but I am having trouble running the > > [3]zmupdate.pl > > script to update my database. Using this command: > > /usr/bin/[4]zmupdate.pl --version=1.30.4 --user={dbuser} > > --pass={dbpass} > > I get this result: > > ---------- > > Initiating database upgrade to version 1.31.1 from version 1.30.4 > > Please ensure that ZoneMinder is stopped on your system prior to > > upgrading the database. > > Press enter to continue or ctrl-C to stop : > > Do you wish to take a backup of your database prior to upgrading? > > This may result in a large file in /var/tmp/zm if you have a lot of > > events. > > Press 'y' for a backup or 'n' to continue : n > > Upgrading database to version 1.31.1 > > Loading config from DBNo option 'ZM_DIR_EVENTS' found, removing. > > No option 'ZM_DIR_IMAGES' found, removing. > > No option 'ZM_DIR_SOUNDS' found, removing. > > No option 'ZM_FRAME_SOCKET_SIZE' found, removing. > > No option 'ZM_OPT_FRAME_SERVER' found, removing. > > No option 'ZM_PATH_ARP' found, removing. > > No option 'ZM_PATH_LOGS' found, removing. > > No option 'ZM_PATH_MAP' found, removing. > > No option 'ZM_PATH_SOCKS' found, removing. > > No option 'ZM_PATH_SWAP' found, removing. > > No option 'ZM_PATH_ZMS' found, removing. > > 207 entries > > Saving config to DB 207 entries > > DBD::mysql::db do failed: Access denied for user > > 'zmuser'@'localhost' to > > database 'zm' at /usr/share/perl5/vendor_perl/ZoneMinder/Config.pm > > line > > 214, line 2. > > Can't lock Config table: Access denied for user 'zmuser'@ > 'localhost' > > to > > database 'zm' at /usr/bin/[5]zmupdate.pl line 464. > > ---------- > > I have also tried without specifying --user and --pass, but I get > > the > > same error. For now I have gone back to my old version and restored > > the > > backup database. I can also ask on the ZoneMinder forums, but I'm > > not > > sure if the issue lies with [6]zmupdate.pl or with the way > > ZoneMinder is > > configured by the SBo package. Seems like pretty much everyone over > > there uses Ubuntu, CentOS, or Debian. > > Dan > > > > References > > > > 1. http://zmupdate.pl/ > > 2. mailto:dpross1100 at msn.com > > 3. http://zmupdate.pl/ > > 4. http://zmupdate.pl/ > > 5. http://zmupdate.pl/ > > 6. http://zmupdate.pl/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dpross1100 at msn.com Mon May 7 03:47:21 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Mon, 7 May 2018 03:47:21 +0000 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: If I get time, I will give that a try. But seeing as how upstream still has 1.30.4 as the latest source, I'm not exactly sure where I'm supposed to get 1.31.0. I'm guessing the same urchlay site, but just adjust the download URL? I guess I'm just ignorant, but I have been active on the Slackware forum on Linuxquestions.org for a couple years and never remember coming across someone named Urchlay. But that aside, I'm not sure why being a well-known Slackware user makes him the correct upstream for ZoneMinder. Is he a ZoneMinder dev also? Why does the official upstream still have 1.30.4 as the latest stable release? I need a better reason for the upgrade than what you have provided, and I'm sure the rest of the ZoneMinder users on SBo would appreciate one too. (Please don't get me wrong -- I'm very appreciative of your maintainership efforts.) Regards, Dan On Sun, May 06, 2018 at 12:11:37AM -0700, Geno Bob wrote: > If you get a few minutes, you might try updating the database one step > at a time. You are going from 1.30.4 right to 1.31.1, however there is > a decent amount of updates in the 1.31.0 db file. Try updating the db > to 1.31.0 and then to 1.31.1 and see if it makes a difference. When I > get a chance I will spin up a VM with 1.30.4 and see if I cant > replicate your issue. > Also, Urchlay is THE urchlay. If you ever go onto a slackware forum or > IRC, he will be there. > Thank you, > GenoBob > > On Sat, May 5, 2018 at 8:12 PM, Daniel Prosser <[1]dpross1100 at msn.com> > wrote: > > I failed to reply all in my previous message, but anyway it wasn't > very > important. The long and short of it was that I changed the password > for > the "zmuser" DB user, but I think I needed to regrant permission to > the > zm database after that. However, after taking care of that and > ensuring > I can log in to mysql as zmuser, I am right back to the original > error > when I try to run [2]zmupdate.pl. > But anyway, as far as I'm concerned, I'm not going to upgrade to a > new > version until it's actually released by upstream. Hopefully the > zmupdate > script will work when that happens. > Dan > On Sat, May 05, 2018 at 03:51:08PM -0700, Geno Bob wrote: > > Daniel, > > According to your error, your credentials are incorrect for > your SQL > > database. Try signing into your database using mysql -u zmuser > -p > > when it asks for a password put in your password (the same > credentials > > you used in the '[1][3]zmupdate.pl' command above). > > Thank you, > > > > On Sat, May 5, 2018 at 6:35 AM, Daniel Prosser > <[2][4]dpross1100 at msn.com> > > wrote: > > > > Hi, > > ZoneMinder was upgraded to version 1.31.1 in the last update. > The > > new > > version builds fine, but I am having trouble running the > > [3][5]zmupdate.pl > > script to update my database. Using this command: > > /usr/bin/[4][6]zmupdate.pl --version=1.30.4 --user={dbuser} > > > --pass={dbpass} > > I get this result: > > ---------- > > Initiating database upgrade to version 1.31.1 from version > 1.30.4 > > Please ensure that ZoneMinder is stopped on your system prior to > > upgrading the database. > > Press enter to continue or ctrl-C to stop : > > Do you wish to take a backup of your database prior to > upgrading? > > This may result in a large file in /var/tmp/zm if you have a lot > of > > events. > > Press 'y' for a backup or 'n' to continue : n > > Upgrading database to version 1.31.1 > > Loading config from DBNo option 'ZM_DIR_EVENTS' found, removing. > > No option 'ZM_DIR_IMAGES' found, removing. > > No option 'ZM_DIR_SOUNDS' found, removing. > > No option 'ZM_FRAME_SOCKET_SIZE' found, removing. > > No option 'ZM_OPT_FRAME_SERVER' found, removing. > > No option 'ZM_PATH_ARP' found, removing. > > No option 'ZM_PATH_LOGS' found, removing. > > No option 'ZM_PATH_MAP' found, removing. > > No option 'ZM_PATH_SOCKS' found, removing. > > No option 'ZM_PATH_SWAP' found, removing. > > No option 'ZM_PATH_ZMS' found, removing. > > 207 entries > > Saving config to DB 207 entries > > DBD::mysql::db do failed: Access denied for user > > 'zmuser'@'localhost' to > > database 'zm' at /usr/share/perl5/vendor_perl/ > ZoneMinder/Config.pm > > line > > 214, line 2. > > Can't lock Config table: Access denied for user > 'zmuser'@'localhost' > > to > > > database 'zm' at /usr/bin/[5][7]zmupdate.pl line 464. > > ---------- > > I have also tried without specifying --user and --pass, but I > get > > the > > same error. For now I have gone back to my old version and > restored > > the > > backup database. I can also ask on the ZoneMinder forums, but > I'm > > not > > sure if the issue lies with [6][8]zmupdate.pl or with the way > > ZoneMinder is > > configured by the SBo package. Seems like pretty much > everyone over > > there uses Ubuntu, CentOS, or Debian. > > Dan > > > > > References > > > > 1. [9]http://zmupdate.pl/ > > 2. mailto:[10]dpross1100 at msn.com > > 3. [11]http://zmupdate.pl/ > > 4. [12]http://zmupdate.pl/ > > 5. [13]http://zmupdate.pl/ > > 6. [14]http://zmupdate.pl/ > > References > > 1. mailto:dpross1100 at msn.com > 2. http://zmupdate.pl/ > 3. http://zmupdate.pl/ > 4. mailto:dpross1100 at msn.com > 5. http://zmupdate.pl/ > 6. http://zmupdate.pl/ > 7. http://zmupdate.pl/ > 8. http://zmupdate.pl/ > 9. http://zmupdate.pl/ > 10. mailto:dpross1100 at msn.com > 11. http://zmupdate.pl/ > 12. http://zmupdate.pl/ > 13. http://zmupdate.pl/ > 14. http://zmupdate.pl/ From yalhcru at gmail.com Mon May 7 08:42:45 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 7 May 2018 04:42:45 -0400 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: On 5/6/18, Daniel Prosser wrote: > I guess I'm just ignorant, but I have been active on the Slackware forum > on Linuxquestions.org for a couple years and never remember coming > across someone named Urchlay. But that aside, I'm not sure why being a > well-known Slackware user makes him the correct upstream for ZoneMinder. I'm Urchlay, and I'm nothing special. I offered to host the new ZoneMinder source for GenoBob, just to help him out. > Is he a ZoneMinder dev also? Definitely not. I've never even used ZoneMinder. The reason for hosting a tarball on my site instead of using upstream's URL is that the version Bob is packaging only ships as a source RPM, which contains the source tarball (plus a spec file and whatever else). What I did is extract and host just the source tarball from the SRPM, so Bob doesn't have to write code in his SlackBuild to do that part. > Why does the official upstream still have > 1.30.4 as the latest stable release? I need a better reason for the > upgrade than what you have provided, and I'm sure the rest of the > ZoneMinder users on SBo would appreciate one too. (Please don't get me > wrong -- I'm very appreciative of your maintainership efforts.) The later versions come from the (semi?) official Red Hat ZoneMinder repo, as source RPMs. For whatever reason, the RH RPMs have version numbers higher than the latest source release. No idea what code changes there might have been nor whether they're redhat-specific, I just hosted the tarball GenoBob asked me to (he's maintainer, I figure he knows what he's doing). From ekinakoglu at gmail.com Mon May 7 11:03:12 2018 From: ekinakoglu at gmail.com (Ekin Akoglu) Date: Mon, 7 May 2018 14:03:12 +0300 Subject: [Slackbuilds-users] Inkscape 0.92.3 error In-Reply-To: <20180504164111.3720d7af@knotsUL> References: <20180504164111.3720d7af@knotsUL> Message-ID: Hi, Thank you, Rob, for your helpful advice. I could manage to compile inkscape with "CXXFLAGS=-liconv" successfully. On my system I need this library and somehow I must have changed something in the default install of Slackware64 when installing it and that's why inkscape produced this error. By the way, after building and installing, "inkscape -V" still shows the version as "0.92.2". I suspect that there must be something wrong with the source archive downloaded from Inkscape's web site. Best, Ekin On 04/05/18 18:41, rob van nues wrote: > On Fri, 04 May 2018 09:33:13 +0000 > slackbuilds-users-request at slackbuilds.org wrote: > >> 2. Re: Inkscape 0.92.3 error (Ekin Akoglu) >> 3. Re: Inkscape 0.92.3 error (Ananda Murthy R S) > Hi, I have inkscape working as well. But no libiconv on my system. > > When you do a 'content'-search on the slackware package > browser (https://packages.slackware.com/) no libiconv is part of 14.2. > A usr/include/iconv.h comes with glibc . > > Maybe try to find whether you have a package on your box that provides a > libiconv and needs to be removed/changed in order to let inkscape > compile. It could interfere with glibc it seems according to this old > thread on LQ: > https://www.linuxquestions.org/questions/slackware-14/undefined-reference-to-libiconv-341284/ > > > > HTH > > Rob > _______________________________________________ > 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 idlemoor at slackbuilds.org Mon May 7 11:31:31 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Mon, 7 May 2018 12:31:31 +0100 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: > I'm Urchlay, and I'm nothing special. I offered to host the new ZoneMinder > source for GenoBob, just to help him out. You're nothing special, except (among other things) you're the wonderful person who gave us sbosrcarch, which is probably why people ask you for help with hosting stuff :) Thanks! -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From didier at slint.fr Mon May 7 12:02:16 2018 From: didier at slint.fr (Didier Spaier) Date: Mon, 7 May 2018 14:02:16 +0200 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: <7a920b4f-944c-d9fc-8a36-fe1d5dff1d35@slint.fr> Le 07/05/2018 ? 13:31, David Spencer a ?crit?: >> I'm Urchlay, and I'm nothing special. I offered to host the new ZoneMinder >> source for GenoBob, just to help him out. > > You're nothing special, except (among other things) you're the wonderful > person who gave us sbosrcarch, which is probably why people ask you for > help with hosting stuff :) > > Thanks! > -D. +1 Didier From geno.bob at gmail.com Mon May 7 04:25:21 2018 From: geno.bob at gmail.com (Geno Bob) Date: Sun, 6 May 2018 21:25:21 -0700 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: I apologize, no. Anytime you upgrade Zoneminder from any version to another newer version, you have to upgrade the database incrementally. My easiest method is no not use the zmupdate tool (it works great if you are working with incremental versions, but anything more and I like to do it the old fashioned way), but instead to access mysql directly. In this case run: mysql -u zmuser -p databasename < /usr/share/zoneminder/db/zm_update-1.31.0.sql and mysql -u zmuser -p databasename < /usr/share/zoneminder/db/zm_update-1.31.1.sql replacing zmuser with your database username and databasename with your db name (probably just zm ?) This will also give us some more info as to what issue you are having with the db files, and which file it is having the issue with. Let me know if this works for you or not. Thank you, GenoBob On Sun, May 6, 2018 at 8:47 PM, Daniel Prosser wrote: > If I get time, I will give that a try. But seeing as how upstream still > has 1.30.4 as the latest source, I'm not exactly sure where I'm supposed > to get 1.31.0. I'm guessing the same urchlay site, but just adjust the > download URL? > > I guess I'm just ignorant, but I have been active on the Slackware forum > on Linuxquestions.org for a couple years and never remember coming > across someone named Urchlay. But that aside, I'm not sure why being a > well-known Slackware user makes him the correct upstream for ZoneMinder. > Is he a ZoneMinder dev also? Why does the official upstream still have > 1.30.4 as the latest stable release? I need a better reason for the > upgrade than what you have provided, and I'm sure the rest of the > ZoneMinder users on SBo would appreciate one too. (Please don't get me > wrong -- I'm very appreciative of your maintainership efforts.) > > Regards, > Dan > > On Sun, May 06, 2018 at 12:11:37AM -0700, Geno Bob wrote: > > If you get a few minutes, you might try updating the database one step > > at a time. You are going from 1.30.4 right to 1.31.1, however there is > > a decent amount of updates in the 1.31.0 db file. Try updating the db > > to 1.31.0 and then to 1.31.1 and see if it makes a difference. When I > > get a chance I will spin up a VM with 1.30.4 and see if I cant > > replicate your issue. > > Also, Urchlay is THE urchlay. If you ever go onto a slackware forum or > > IRC, he will be there. > > Thank you, > > GenoBob > > > > On Sat, May 5, 2018 at 8:12 PM, Daniel Prosser <[1]dpross1100 at msn.com > > > > wrote: > > > > I failed to reply all in my previous message, but anyway it wasn't > > very > > important. The long and short of it was that I changed the password > > for > > the "zmuser" DB user, but I think I needed to regrant permission to > > the > > zm database after that. However, after taking care of that and > > ensuring > > I can log in to mysql as zmuser, I am right back to the original > > error > > when I try to run [2]zmupdate.pl. > > But anyway, as far as I'm concerned, I'm not going to upgrade to a > > new > > version until it's actually released by upstream. Hopefully the > > zmupdate > > script will work when that happens. > > Dan > > On Sat, May 05, 2018 at 03:51:08PM -0700, Geno Bob wrote: > > > Daniel, > > > According to your error, your credentials are incorrect for > > your SQL > > > database. Try signing into your database using mysql -u zmuser > > -p > > > when it asks for a password put in your password (the same > > credentials > > > you used in the '[1][3]zmupdate.pl' command above). > > > Thank you, > > > > > > On Sat, May 5, 2018 at 6:35 AM, Daniel Prosser > > <[2][4]dpross1100 at msn.com> > > > wrote: > > > > > > Hi, > > > ZoneMinder was upgraded to version 1.31.1 in the last update. > > The > > > new > > > version builds fine, but I am having trouble running the > > > [3][5]zmupdate.pl > > > script to update my database. Using this command: > > > /usr/bin/[4][6]zmupdate.pl --version=1.30.4 --user={dbuser} > > > > > --pass={dbpass} > > > I get this result: > > > ---------- > > > Initiating database upgrade to version 1.31.1 from version > > 1.30.4 > > > Please ensure that ZoneMinder is stopped on your system prior > to > > > upgrading the database. > > > Press enter to continue or ctrl-C to stop : > > > Do you wish to take a backup of your database prior to > > upgrading? > > > This may result in a large file in /var/tmp/zm if you have a > lot > > of > > > events. > > > Press 'y' for a backup or 'n' to continue : n > > > Upgrading database to version 1.31.1 > > > Loading config from DBNo option 'ZM_DIR_EVENTS' found, > removing. > > > No option 'ZM_DIR_IMAGES' found, removing. > > > No option 'ZM_DIR_SOUNDS' found, removing. > > > No option 'ZM_FRAME_SOCKET_SIZE' found, removing. > > > No option 'ZM_OPT_FRAME_SERVER' found, removing. > > > No option 'ZM_PATH_ARP' found, removing. > > > No option 'ZM_PATH_LOGS' found, removing. > > > No option 'ZM_PATH_MAP' found, removing. > > > No option 'ZM_PATH_SOCKS' found, removing. > > > No option 'ZM_PATH_SWAP' found, removing. > > > No option 'ZM_PATH_ZMS' found, removing. > > > 207 entries > > > Saving config to DB 207 entries > > > DBD::mysql::db do failed: Access denied for user > > > 'zmuser'@'localhost' to > > > database 'zm' at /usr/share/perl5/vendor_perl/ > > ZoneMinder/Config.pm > > > line > > > 214, line 2. > > > Can't lock Config table: Access denied for user > > 'zmuser'@'localhost' > > > to > > > > > database 'zm' at /usr/bin/[5][7]zmupdate.pl line 464. > > > ---------- > > > I have also tried without specifying --user and --pass, but I > > get > > > the > > > same error. For now I have gone back to my old version and > > restored > > > the > > > backup database. I can also ask on the ZoneMinder forums, but > > I'm > > > not > > > sure if the issue lies with [6][8]zmupdate.pl or with the > way > > > ZoneMinder is > > > configured by the SBo package. Seems like pretty much > > everyone over > > > there uses Ubuntu, CentOS, or Debian. > > > Dan > > > > > > > > References > > > > > > 1. [9]http://zmupdate.pl/ > > > 2. mailto:[10]dpross1100 at msn.com > > > 3. [11]http://zmupdate.pl/ > > > 4. [12]http://zmupdate.pl/ > > > 5. [13]http://zmupdate.pl/ > > > 6. [14]http://zmupdate.pl/ > > > > References > > > > 1. mailto:dpross1100 at msn.com > > 2. http://zmupdate.pl/ > > 3. http://zmupdate.pl/ > > 4. mailto:dpross1100 at msn.com > > 5. http://zmupdate.pl/ > > 6. http://zmupdate.pl/ > > 7. http://zmupdate.pl/ > > 8. http://zmupdate.pl/ > > 9. http://zmupdate.pl/ > > 10. mailto:dpross1100 at msn.com > > 11. http://zmupdate.pl/ > > 12. http://zmupdate.pl/ > > 13. http://zmupdate.pl/ > > 14. http://zmupdate.pl/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From orbea at fredslev.dk Mon May 7 19:53:51 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Mon, 7 May 2018 12:53:51 -0700 Subject: [Slackbuilds-users] qt5 + pulseaudio Message-ID: <20180507125351.624292e9@Akita.witch.org> Hi, I e-mailed a very small patch to the qt5.SlackBuild maintainer more than once to allow dynamically detecting if pulseaudio is installed with pkg-config and disabling it if its not. However its been a few weeks since my last attempt and much longer for the previous ones. I have received absolutely 0 replies. I also e-mailed a similar patch to Pat for mpg123 and now Slackware supports a pure alsa install in extra. It would really mean a lot to me if this was applied to qt5 too so I that I didn't constantly have to edit the SlackBuild every time I update or rebuild qt5. Something which I routinely forget to do until the build fails... Can this be done? I've attached the patch to this e-mail. Thanks, Hunter -------------- next part -------------- A non-text attachment was scrubbed... Name: qt5.SlackBuild.patch Type: text/x-patch Size: 479 bytes Desc: not available URL: From matteo.bernardini at gmail.com Mon May 7 21:18:21 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 7 May 2018 23:18:21 +0200 Subject: [Slackbuilds-users] qt5 + pulseaudio In-Reply-To: <20180507125351.624292e9@Akita.witch.org> References: <20180507125351.624292e9@Akita.witch.org> Message-ID: 2018-05-07 21:53 GMT+02:00 orbea at fredslev.dk : > Hi, > > I e-mailed a very small patch to the qt5.SlackBuild maintainer more > than once to allow dynamically detecting if pulseaudio is installed with > pkg-config and disabling it if its not. However its been a few weeks > since my last attempt and much longer for the previous ones. I have > received absolutely 0 replies. > > I also e-mailed a similar patch to Pat for mpg123 and now Slackware > supports a pure alsa install in extra. It would really mean a lot to me > if this was applied to qt5 too so I that I didn't constantly have to > edit the SlackBuild every time I update or rebuild qt5. Something which > I routinely forget to do until the build fails... > > Can this be done? I've attached the patch to this e-mail. > > Thanks, > Hunter I'm sorry Hunter, but if these kind of patches are to be applied is up to the maintainers. maybe if Larry hasn't answered yet is because he's not gonna apply it, but he has the last call on his own scripts. consider also that we assume for our scripts a full and clean installation of the latest Slackware stable, and such platform contain pulseaudio, we don't officially support pure alsa installations. Matteo From dpross1100 at msn.com Tue May 8 02:08:22 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Tue, 8 May 2018 02:08:22 +0000 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: Bob, Thank you for helping me try to sort this out. I was able to use the upgrade dbs in /usr/share/zoneminder/db to incrementally upgrade my database to 1.31.1. At least, the commands completed without reporting any errors. Before I could do that, I did have to grant alter permission to zmuser, which wasn't mentioned in README.SLACKWARE, FYI. However, after upgrading I'm getting a bunch of errors in the logs about not having proper permissions on directories, sockets not existing, etc. Those logs recommend running zmupdate.pl -f, which I am still unable to do. So I'm not really sure if the database was actually upgraded correctly. These errors may be fixable with some hand editing of the paths through the web interface, but I need to do more research to find out. B Watson, aka Urchlay, ank youthay orfay explainingay erewhay ethay ourcesay amecay omfray. (Pardon my poor pig latin.) Dan On Sun, May 06, 2018 at 09:25:21PM -0700, Geno Bob wrote: > I apologize, no. Anytime you upgrade Zoneminder from any version to > another newer version, you have to upgrade the database incrementally. > My easiest method is no not use the zmupdate tool (it works great if > you are working with incremental versions, but anything more and I like > to do it the old fashioned way), but instead to access mysql directly. > In this case run: > mysql -u zmuser -p databasename < > /usr/share/zoneminder/db/zm_update-1.31.0.sql > and > mysql -u zmuser -p databasename < > /usr/share/zoneminder/db/zm_update-1.31.1.sql > replacing zmuser with your database username and databasename with your > db name (probably just zm ?) > This will also give us some more info as to what issue you are having > with the db files, and which file it is having the issue with. > Let me know if this works for you or not. > Thank you, > GenoBob > > On Sun, May 6, 2018 at 8:47 PM, Daniel Prosser <[1]dpross1100 at msn.com> > wrote: > > If I get time, I will give that a try. But seeing as how upstream > still > has 1.30.4 as the latest source, I'm not exactly sure where I'm > supposed > to get 1.31.0. I'm guessing the same urchlay site, but just adjust > the > download URL? > I guess I'm just ignorant, but I have been active on the Slackware > forum > on Linuxquestions.org for a couple years and never remember coming > across someone named Urchlay. But that aside, I'm not sure why being > a > well-known Slackware user makes him the correct upstream for > ZoneMinder. > Is he a ZoneMinder dev also? Why does the official upstream still > have > 1.30.4 as the latest stable release? I need a better reason for the > upgrade than what you have provided, and I'm sure the rest of the > ZoneMinder users on SBo would appreciate one too. (Please don't get > me > wrong -- I'm very appreciative of your maintainership efforts.) > Regards, > Dan > On Sun, May 06, 2018 at 12:11:37AM -0700, Geno Bob wrote: > > If you get a few minutes, you might try updating the database > one step > > at a time. You are going from 1.30.4 right to 1.31.1, however > there is > > a decent amount of updates in the 1.31.0 db file. Try updating > the db > > to 1.31.0 and then to 1.31.1 and see if it makes a difference. > When I > > get a chance I will spin up a VM with 1.30.4 and see if I cant > > replicate your issue. > > Also, Urchlay is THE urchlay. If you ever go onto a slackware > forum or > > IRC, he will be there. > > Thank you, > > GenoBob > > > > On Sat, May 5, 2018 at 8:12 PM, Daniel Prosser > <[1][2]dpross1100 at msn.com> > > wrote: > > > > I failed to reply all in my previous message, but anyway it > wasn't > > very > > important. The long and short of it was that I changed the > password > > for > > the "zmuser" DB user, but I think I needed to regrant > permission to > > the > > zm database after that. However, after taking care of that > and > > ensuring > > I can log in to mysql as zmuser, I am right back to the > original > > error > > when I try to run [2][3]zmupdate.pl. > > But anyway, as far as I'm concerned, I'm not going to upgrade > to a > > new > > version until it's actually released by upstream. Hopefully > the > > zmupdate > > script will work when that happens. > > Dan > > On Sat, May 05, 2018 at 03:51:08PM -0700, Geno Bob wrote: > > > Daniel, > > > According to your error, your credentials are incorrect > for > > your SQL > > > database. Try signing into your database using mysql -u > zmuser > > -p > > > when it asks for a password put in your password (the > same > > credentials > > > you used in the '[1][3][4]zmupdate.pl' command above). > > > Thank you, > > > > > > On Sat, May 5, 2018 at 6:35 AM, Daniel Prosser > > <[2][4][5]dpross1100 at msn.com> > > > wrote: > > > > > > Hi, > > > ZoneMinder was upgraded to version 1.31.1 in the last > update. > > The > > > new > > > version builds fine, but I am having trouble running > the > > > [3][5][6]zmupdate.pl > > > script to update my database. Using this command: > > > /usr/bin/[4][6][7]zmupdate.pl --version=1.30.4 > --user={dbuser} > > > > > > --pass={dbpass} > > > I get this result: > > > ---------- > > > Initiating database upgrade to version 1.31.1 from version > > 1.30.4 > > > Please ensure that ZoneMinder is stopped on your system > prior to > > > upgrading the database. > > > Press enter to continue or ctrl-C to stop : > > > Do you wish to take a backup of your database prior to > > upgrading? > > > This may result in a large file in /var/tmp/zm if you have > a lot > > of > > > events. > > > Press 'y' for a backup or 'n' to continue : n > > > Upgrading database to version 1.31.1 > > > Loading config from DBNo option 'ZM_DIR_EVENTS' found, > removing. > > > No option 'ZM_DIR_IMAGES' found, removing. > > > No option 'ZM_DIR_SOUNDS' found, removing. > > > No option 'ZM_FRAME_SOCKET_SIZE' found, removing. > > > No option 'ZM_OPT_FRAME_SERVER' found, removing. > > > No option 'ZM_PATH_ARP' found, removing. > > > No option 'ZM_PATH_LOGS' found, removing. > > > No option 'ZM_PATH_MAP' found, removing. > > > No option 'ZM_PATH_SOCKS' found, removing. > > > No option 'ZM_PATH_SWAP' found, removing. > > > No option 'ZM_PATH_ZMS' found, removing. > > > 207 entries > > > Saving config to DB 207 entries > > > DBD::mysql::db do failed: Access denied for user > > > 'zmuser'@'localhost' to > > > database 'zm' at /usr/share/perl5/vendor_perl/ > > ZoneMinder/Config.pm > > > line > > > 214, line 2. > > > Can't lock Config table: Access denied for user > > 'zmuser'@'localhost' > > > to > > > > > > database 'zm' at /usr/bin/[5][7][8]zmupdate.pl line > 464. > > > ---------- > > > I have also tried without specifying --user and > --pass, but I > > get > > > the > > > same error. For now I have gone back to my old version > and > > restored > > > the > > > backup database. I can also ask on the ZoneMinder > forums, but > > I'm > > > not > > > sure if the issue lies with [6][8][9]zmupdate.pl or > with the way > > > ZoneMinder is > > > configured by the SBo package. Seems like pretty much > > everyone over > > > there uses Ubuntu, CentOS, or Debian. > > > Dan > > > > > > > > References > > > > > > 1. [9][10]http://zmupdate.pl/ > > > 2. mailto:[10][11]dpross1100 at msn.com > > > 3. [11][12]http://zmupdate.pl/ > > > 4. [12][13]http://zmupdate.pl/ > > > 5. [13][14]http://zmupdate.pl/ > > > 6. [14][15]http://zmupdate.pl/ > > > > References > > > > 1. mailto:[16]dpross1100 at msn.com > > 2. [17]http://zmupdate.pl/ > > 3. [18]http://zmupdate.pl/ > > 4. mailto:[19]dpross1100 at msn.com > > 5. [20]http://zmupdate.pl/ > > 6. [21]http://zmupdate.pl/ > > 7. [22]http://zmupdate.pl/ > > 8. [23]http://zmupdate.pl/ > > 9. [24]http://zmupdate.pl/ > > 10. mailto:[25]dpross1100 at msn.com > > 11. [26]http://zmupdate.pl/ > > 12. [27]http://zmupdate.pl/ > > 13. [28]http://zmupdate.pl/ > > 14. [29]http://zmupdate.pl/ > > References > > 1. mailto:dpross1100 at msn.com > 2. mailto:dpross1100 at msn.com > 3. http://zmupdate.pl/ > 4. http://zmupdate.pl/ > 5. mailto:dpross1100 at msn.com > 6. http://zmupdate.pl/ > 7. http://zmupdate.pl/ > 8. http://zmupdate.pl/ > 9. http://zmupdate.pl/ > 10. http://zmupdate.pl/ > 11. mailto:dpross1100 at msn.com > 12. http://zmupdate.pl/ > 13. http://zmupdate.pl/ > 14. http://zmupdate.pl/ > 15. http://zmupdate.pl/ > 16. mailto:dpross1100 at msn.com > 17. http://zmupdate.pl/ > 18. http://zmupdate.pl/ > 19. mailto:dpross1100 at msn.com > 20. http://zmupdate.pl/ > 21. http://zmupdate.pl/ > 22. http://zmupdate.pl/ > 23. http://zmupdate.pl/ > 24. http://zmupdate.pl/ > 25. mailto:dpross1100 at msn.com > 26. http://zmupdate.pl/ > 27. http://zmupdate.pl/ > 28. http://zmupdate.pl/ > 29. http://zmupdate.pl/ From larryhaja at gmail.com Tue May 8 02:22:31 2018 From: larryhaja at gmail.com (Larry Hajali) Date: Mon, 7 May 2018 19:22:31 -0700 Subject: [Slackbuilds-users] qt5 + pulseaudio In-Reply-To: <20180507125351.624292e9@Akita.witch.org> References: <20180507125351.624292e9@Akita.witch.org> Message-ID: Hi, > I e-mailed a very small patch to the qt5.SlackBuild maintainer more > than once to allow dynamically detecting if pulseaudio is installed with > pkg-config and disabling it if its not. However its been a few weeks > since my last attempt and much longer for the previous ones. I have > received absolutely 0 replies. > I only see one email from you in my inbox on April 22. I haven't replied as I started a new job and life has gotten in the way. Can this be done? I've attached the patch to this e-mail. > I'll look at the patch this weekend. --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From orbea at fredslev.dk Mon May 7 21:36:12 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Mon, 7 May 2018 14:36:12 -0700 Subject: [Slackbuilds-users] qt5 + pulseaudio In-Reply-To: Message-ID: <20180507143612.05be6364@Akita.witch.org> That assumption is irrelevant and if a maintainer is not willing to respond to bug reports then it should be possible to implement fixes without the maintainer. The bottom line is that this patch would make the qt5.SlackBuild more fail proof and the only reason to not accept it is to spite people who do not use pulseaudio. This can only have a negative effect on the usefulness and reliability of SBo... From geno.bob at gmail.com Tue May 8 02:24:26 2018 From: geno.bob at gmail.com (Geno Bob) Date: Mon, 7 May 2018 19:24:26 -0700 Subject: [Slackbuilds-users] Problems upgrading ZoneMinder In-Reply-To: References: Message-ID: No problem. Thank you for testing. I will test on my VM and see if I can replicate. Thank you, GenoBob On Mon, May 7, 2018 at 7:08 PM, Daniel Prosser wrote: > Bob, > > Thank you for helping me try to sort this out. I was able to use the > upgrade dbs in /usr/share/zoneminder/db to incrementally upgrade my > database to 1.31.1. At least, the commands completed without reporting > any errors. Before I could do that, I did have to grant alter permission > to zmuser, which wasn't mentioned in README.SLACKWARE, FYI. However, > after upgrading I'm getting a bunch of errors in the logs about not > having proper permissions on directories, sockets not existing, etc. > Those logs recommend running zmupdate.pl -f, which I am still unable to > do. So I'm not really sure if the database was actually upgraded > correctly. These errors may be fixable with some hand editing of the > paths through the web interface, but I need to do more research to find > out. > > B Watson, aka Urchlay, ank youthay orfay explainingay erewhay ethay > ourcesay amecay omfray. (Pardon my poor pig latin.) > > Dan > > On Sun, May 06, 2018 at 09:25:21PM -0700, Geno Bob wrote: > > I apologize, no. Anytime you upgrade Zoneminder from any version to > > another newer version, you have to upgrade the database incrementally. > > My easiest method is no not use the zmupdate tool (it works great if > > you are working with incremental versions, but anything more and I > like > > to do it the old fashioned way), but instead to access mysql directly. > > In this case run: > > mysql -u zmuser -p databasename < > > /usr/share/zoneminder/db/zm_update-1.31.0.sql > > and > > mysql -u zmuser -p databasename < > > /usr/share/zoneminder/db/zm_update-1.31.1.sql > > replacing zmuser with your database username and databasename with > your > > db name (probably just zm ?) > > This will also give us some more info as to what issue you are having > > with the db files, and which file it is having the issue with. > > Let me know if this works for you or not. > > Thank you, > > GenoBob > > > > On Sun, May 6, 2018 at 8:47 PM, Daniel Prosser <[1]dpross1100 at msn.com > > > > wrote: > > > > If I get time, I will give that a try. But seeing as how upstream > > still > > has 1.30.4 as the latest source, I'm not exactly sure where I'm > > supposed > > to get 1.31.0. I'm guessing the same urchlay site, but just adjust > > the > > download URL? > > I guess I'm just ignorant, but I have been active on the Slackware > > forum > > on Linuxquestions.org for a couple years and never remember coming > > across someone named Urchlay. But that aside, I'm not sure why being > > a > > well-known Slackware user makes him the correct upstream for > > ZoneMinder. > > Is he a ZoneMinder dev also? Why does the official upstream still > > have > > 1.30.4 as the latest stable release? I need a better reason for the > > upgrade than what you have provided, and I'm sure the rest of the > > ZoneMinder users on SBo would appreciate one too. (Please don't get > > me > > wrong -- I'm very appreciative of your maintainership efforts.) > > Regards, > > Dan > > On Sun, May 06, 2018 at 12:11:37AM -0700, Geno Bob wrote: > > > If you get a few minutes, you might try updating the database > > one step > > > at a time. You are going from 1.30.4 right to 1.31.1, however > > there is > > > a decent amount of updates in the 1.31.0 db file. Try updating > > the db > > > to 1.31.0 and then to 1.31.1 and see if it makes a difference. > > When I > > > get a chance I will spin up a VM with 1.30.4 and see if I cant > > > replicate your issue. > > > Also, Urchlay is THE urchlay. If you ever go onto a slackware > > forum or > > > IRC, he will be there. > > > Thank you, > > > GenoBob > > > > > > On Sat, May 5, 2018 at 8:12 PM, Daniel Prosser > > <[1][2]dpross1100 at msn.com> > > > wrote: > > > > > > I failed to reply all in my previous message, but anyway it > > wasn't > > > very > > > important. The long and short of it was that I changed the > > password > > > for > > > the "zmuser" DB user, but I think I needed to regrant > > permission to > > > the > > > zm database after that. However, after taking care of that > > and > > > ensuring > > > I can log in to mysql as zmuser, I am right back to the > > original > > > error > > > when I try to run [2][3]zmupdate.pl. > > > But anyway, as far as I'm concerned, I'm not going to upgrade > > to a > > > new > > > version until it's actually released by upstream. Hopefully > > the > > > zmupdate > > > script will work when that happens. > > > Dan > > > On Sat, May 05, 2018 at 03:51:08PM -0700, Geno Bob wrote: > > > > Daniel, > > > > According to your error, your credentials are incorrect > > for > > > your SQL > > > > database. Try signing into your database using mysql -u > > zmuser > > > -p > > > > when it asks for a password put in your password (the > > same > > > credentials > > > > you used in the '[1][3][4]zmupdate.pl' command above). > > > > Thank you, > > > > > > > > On Sat, May 5, 2018 at 6:35 AM, Daniel Prosser > > > <[2][4][5]dpross1100 at msn.com> > > > > wrote: > > > > > > > > Hi, > > > > ZoneMinder was upgraded to version 1.31.1 in the last > > update. > > > The > > > > new > > > > version builds fine, but I am having trouble running > > the > > > > [3][5][6]zmupdate.pl > > > > script to update my database. Using this command: > > > > /usr/bin/[4][6][7]zmupdate.pl --version=1.30.4 > > --user={dbuser} > > > > > > > > > --pass={dbpass} > > > > I get this result: > > > > ---------- > > > > Initiating database upgrade to version 1.31.1 from version > > > 1.30.4 > > > > Please ensure that ZoneMinder is stopped on your system > > prior to > > > > upgrading the database. > > > > Press enter to continue or ctrl-C to stop : > > > > Do you wish to take a backup of your database prior to > > > upgrading? > > > > This may result in a large file in /var/tmp/zm if you have > > a lot > > > of > > > > events. > > > > Press 'y' for a backup or 'n' to continue : n > > > > Upgrading database to version 1.31.1 > > > > Loading config from DBNo option 'ZM_DIR_EVENTS' found, > > removing. > > > > No option 'ZM_DIR_IMAGES' found, removing. > > > > No option 'ZM_DIR_SOUNDS' found, removing. > > > > No option 'ZM_FRAME_SOCKET_SIZE' found, removing. > > > > No option 'ZM_OPT_FRAME_SERVER' found, removing. > > > > No option 'ZM_PATH_ARP' found, removing. > > > > No option 'ZM_PATH_LOGS' found, removing. > > > > No option 'ZM_PATH_MAP' found, removing. > > > > No option 'ZM_PATH_SOCKS' found, removing. > > > > No option 'ZM_PATH_SWAP' found, removing. > > > > No option 'ZM_PATH_ZMS' found, removing. > > > > 207 entries > > > > Saving config to DB 207 entries > > > > DBD::mysql::db do failed: Access denied for user > > > > 'zmuser'@'localhost' to > > > > database 'zm' at /usr/share/perl5/vendor_perl/ > > > ZoneMinder/Config.pm > > > > line > > > > 214, line 2. > > > > Can't lock Config table: Access denied for user > > > 'zmuser'@'localhost' > > > > to > > > > > > > > > database 'zm' at /usr/bin/[5][7][8]zmupdate.pl line > > 464. > > > > ---------- > > > > I have also tried without specifying --user and > > --pass, but I > > > get > > > > the > > > > same error. For now I have gone back to my old version > > and > > > restored > > > > the > > > > backup database. I can also ask on the ZoneMinder > > forums, but > > > I'm > > > > not > > > > sure if the issue lies with [6][8][9]zmupdate.pl or > > with the way > > > > ZoneMinder is > > > > configured by the SBo package. Seems like pretty much > > > everyone over > > > > there uses Ubuntu, CentOS, or Debian. > > > > Dan > > > > > > > > > > > References > > > > > > > > 1. [9][10]http://zmupdate.pl/ > > > > 2. mailto:[10][11]dpross1100 at msn.com > > > > 3. [11][12]http://zmupdate.pl/ > > > > 4. [12][13]http://zmupdate.pl/ > > > > 5. [13][14]http://zmupdate.pl/ > > > > 6. [14][15]http://zmupdate.pl/ > > > > > > References > > > > > > 1. mailto:[16]dpross1100 at msn.com > > > 2. [17]http://zmupdate.pl/ > > > 3. [18]http://zmupdate.pl/ > > > 4. mailto:[19]dpross1100 at msn.com > > > 5. [20]http://zmupdate.pl/ > > > 6. [21]http://zmupdate.pl/ > > > 7. [22]http://zmupdate.pl/ > > > 8. [23]http://zmupdate.pl/ > > > 9. [24]http://zmupdate.pl/ > > > 10. mailto:[25]dpross1100 at msn.com > > > 11. [26]http://zmupdate.pl/ > > > 12. [27]http://zmupdate.pl/ > > > 13. [28]http://zmupdate.pl/ > > > 14. [29]http://zmupdate.pl/ > > > > References > > > > 1. mailto:dpross1100 at msn.com > > 2. mailto:dpross1100 at msn.com > > 3. http://zmupdate.pl/ > > 4. http://zmupdate.pl/ > > 5. mailto:dpross1100 at msn.com > > 6. http://zmupdate.pl/ > > 7. http://zmupdate.pl/ > > 8. http://zmupdate.pl/ > > 9. http://zmupdate.pl/ > > 10. http://zmupdate.pl/ > > 11. mailto:dpross1100 at msn.com > > 12. http://zmupdate.pl/ > > 13. http://zmupdate.pl/ > > 14. http://zmupdate.pl/ > > 15. http://zmupdate.pl/ > > 16. mailto:dpross1100 at msn.com > > 17. http://zmupdate.pl/ > > 18. http://zmupdate.pl/ > > 19. mailto:dpross1100 at msn.com > > 20. http://zmupdate.pl/ > > 21. http://zmupdate.pl/ > > 22. http://zmupdate.pl/ > > 23. http://zmupdate.pl/ > > 24. http://zmupdate.pl/ > > 25. mailto:dpross1100 at msn.com > > 26. http://zmupdate.pl/ > > 27. http://zmupdate.pl/ > > 28. http://zmupdate.pl/ > > 29. http://zmupdate.pl/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Tue May 8 16:43:01 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 8 May 2018 18:43:01 +0200 Subject: [Slackbuilds-users] qt5 + pulseaudio In-Reply-To: <20180507143612.05be6364@Akita.witch.org> References: <20180507143612.05be6364@Akita.witch.org> Message-ID: 2018-05-07 23:36 GMT+02:00 orbea at fredslev.dk : > That assumption is irrelevant and if a maintainer is not willing to > respond to bug reports then it should be possible to implement fixes > without the maintainer. > > The bottom line is that this patch would make the qt5.SlackBuild more > fail proof and the only reason to not accept it is to spite people who > do not use pulseaudio. This can only have a negative effect on the > usefulness and reliability of SBo... we have different opinion on what is a bug an what are legit maintainer decisions. optional pulseaudio support is surely not a bug: pulseaudio is not optional at all in slackware 14.2 and I explained why we cannot consider it optional even in the next Slackware release: stuff in /extra is not part of a Slackware full installation and we support just that. that said, is up to the maintainer if they want to add a switch in their SlackBuilds to make pulseaudio optional (with pulseaudio enabled by default, of course), and it's up to the users to use it (under their own responsibility) or not. Matteo From chris.willing at iinet.net.au Tue May 8 22:12:27 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 9 May 2018 08:12:27 +1000 Subject: [Slackbuilds-users] qt5 + pulseaudio In-Reply-To: <20180507125351.624292e9@Akita.witch.org> References: <20180507125351.624292e9@Akita.witch.org> Message-ID: <98280a2d-ca1c-ec2c-c15e-c86e4a068b26@iinet.net.au> On 08/05/18 05:53, orbea at fredslev.dk wrote: [snip] > It would really mean a lot to me > if this was applied to qt5 too so I that I didn't constantly have to > edit the SlackBuild every time I update or rebuild qt5. Something which > I routinely forget to do until the build fails... > Many (most?) of us have at least one SlackBuild which we change to suit personal requirements. No doubt, those who have multiple SlackBuilds in this category also have some strategy to work through these differences with minimal pain whenever there is an update. In my case, I use git branches to accommodate the different SlackBuild versions I want to maintain. Apart from the branches connected with SlackBuilds for which I am the maintainer (therefore conforming strictly to SBo conventions), I have a separate branch which contains all the changes in the various SlackBuilds that I use for my local systems. At each SBo update, I rebase that separate branch to master so that the branch is up to date but local changes remain intact. Occasionally the rebase will conflict with a change in the branch but that's easily fixed. chris From atelszewski at gmail.com Tue May 8 23:05:21 2018 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 9 May 2018 01:05:21 +0200 Subject: [Slackbuilds-users] qt5 + pulseaudio In-Reply-To: <98280a2d-ca1c-ec2c-c15e-c86e4a068b26@iinet.net.au> References: <20180507125351.624292e9@Akita.witch.org> <98280a2d-ca1c-ec2c-c15e-c86e4a068b26@iinet.net.au> Message-ID: <7c21edf8-a03e-ed88-f140-f74e4aa01dc1@gmail.com> On 09/05/18 00:12, Christoph Willing wrote: > In my case, I use git branches to accommodate the different SlackBuild > versions I want to maintain. Apart from the branches connected with > SlackBuilds for which I am the maintainer (therefore conforming strictly > to SBo conventions), I have a separate branch which contains all the > changes in the various SlackBuilds that I use for my local systems. At > each SBo update, I rebase that separate branch to master so that the > branch is up to date but local changes remain intact. Occasionally the > rebase will conflict with a change in the branch but that's easily fixed. I do the exact same thing. Works very well. Thanks for wording it up. :-) -- Best regards / Pozdrawiam, Andrzej Telszewski From richard at aaazen.com Wed May 9 20:53:47 2018 From: richard at aaazen.com (Richard Narron) Date: Wed, 9 May 2018 13:53:47 -0700 (PDT) Subject: [Slackbuilds-users] qt5 + pulseaudio In-Reply-To: References: <20180507143612.05be6364@Akita.witch.org> Message-ID: On Tue, 8 May 2018, Matteo Bernardini wrote: > 2018-05-07 23:36 GMT+02:00 orbea at fredslev.dk : > > That assumption is irrelevant and if a maintainer is not willing to > > respond to bug reports then it should be possible to implement fixes > > without the maintainer. > > > > The bottom line is that this patch would make the qt5.SlackBuild more > > fail proof and the only reason to not accept it is to spite people who > > do not use pulseaudio. This can only have a negative effect on the > > usefulness and reliability of SBo... > > we have different opinion on what is a bug an what are legit > maintainer decisions. > optional pulseaudio support is surely not a bug: pulseaudio is not > optional at all in slackware 14.2 and I explained why we cannot > consider it optional even in the next Slackware release: stuff in > /extra is not part of a Slackware full installation and we support > just that. > that said, is up to the maintainer if they want to add a switch in > their SlackBuilds to make pulseaudio optional (with pulseaudio enabled > by default, of course), and it's up to the users to use it (under > their own responsibility) or not. I would suggest that the alsa files in /extra are not actually "extra". They are replacements for standard pulseaudio Slackware current packages. It would be hard for someone with with pulseaudio to test the alsa side of things and hard for someone with alsa to test the pulseaudio side of things. So instead of an alsa-pulseaudio switch perhaps we should allow two sets of packages, the standard ones with pulseaudio and another set with alsa. Maybe have a naming convention or separate directory? Richard Narron From chris.willing at iinet.net.au Wed May 9 21:53:35 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Thu, 10 May 2018 07:53:35 +1000 Subject: [Slackbuilds-users] qt5 + pulseaudio In-Reply-To: References: <20180507143612.05be6364@Akita.witch.org> Message-ID: <88ef04bb-9f0b-e69e-5c69-afae81c42201@iinet.net.au> On 10/05/18 06:53, Richard Narron wrote: > On Tue, 8 May 2018, Matteo Bernardini wrote: > >> 2018-05-07 23:36 GMT+02:00 orbea at fredslev.dk : >>> That assumption is irrelevant and if a maintainer is not willing to >>> respond to bug reports then it should be possible to implement fixes >>> without the maintainer. >>> >>> The bottom line is that this patch would make the qt5.SlackBuild more >>> fail proof and the only reason to not accept it is to spite people who >>> do not use pulseaudio. This can only have a negative effect on the >>> usefulness and reliability of SBo... >> >> we have different opinion on what is a bug an what are legit >> maintainer decisions. >> optional pulseaudio support is surely not a bug: pulseaudio is not >> optional at all in slackware 14.2 and I explained why we cannot >> consider it optional even in the next Slackware release: stuff in >> /extra is not part of a Slackware full installation and we support >> just that. >> that said, is up to the maintainer if they want to add a switch in >> their SlackBuilds to make pulseaudio optional (with pulseaudio enabled >> by default, of course), and it's up to the users to use it (under >> their own responsibility) or not. > > I would suggest that the alsa files in /extra are not actually "extra". > They are replacements for standard pulseaudio Slackware current packages. > > It would be hard for someone with with pulseaudio to test the alsa side of > things and hard for someone with alsa to test the pulseaudio side of > things. > > So instead of an alsa-pulseaudio switch perhaps we should allow two sets > of packages, the standard ones with pulseaudio and another set with alsa. > How would that make testing any easier for a maintainer - or are you suggesting having multiple maintainers too? It sounds like a lot of complication just for the sake of the few SlackBuilds that would actually be involved. No doubt alsa enthusiasts are smart enough to make their own changes in cases where the maintainer hasn't adopted some pulseaudio/alsa switch arrangement. Hint to alsa-enthusiasts: suggest your alsa-tested switch arrangement directly to the relevant maintainers. I'm sure such suggestions would mostly be adopted provided they don't adversely affect normal systems. chris From dpross1100 at msn.com Wed May 9 23:43:22 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Wed, 9 May 2018 23:43:22 +0000 Subject: [Slackbuilds-users] qt5 + pulseaudio In-Reply-To: <88ef04bb-9f0b-e69e-5c69-afae81c42201@iinet.net.au> Message-ID: >> Hint to alsa-enthusiasts: suggest your alsa-tested switch arrangement directly to the relevant maintainers. I'm sure such suggestions would mostly be adopted provided They don't adversely affect normal systems. Isn't that exactly what Hunter has done? On May 9, 2018 5:53 PM, Christoph Willing wrote: On 10/05/18 06:53, Richard Narron wrote: > On Tue, 8 May 2018, Matteo Bernardini wrote: > >> 2018-05-07 23:36 GMT+02:00 orbea at fredslev.dk : >>> That assumption is irrelevant and if a maintainer is not willing to >>> respond to bug reports then it should be possible to implement fixes >>> without the maintainer. >>> >>> The bottom line is that this patch would make the qt5.SlackBuild more >>> fail proof and the only reason to not accept it is to spite people who >>> do not use pulseaudio. This can only have a negative effect on the >>> usefulness and reliability of SBo... >> >> we have different opinion on what is a bug an what are legit >> maintainer decisions. >> optional pulseaudio support is surely not a bug: pulseaudio is not >> optional at all in slackware 14.2 and I explained why we cannot >> consider it optional even in the next Slackware release: stuff in >> /extra is not part of a Slackware full installation and we support >> just that. >> that said, is up to the maintainer if they want to add a switch in >> their SlackBuilds to make pulseaudio optional (with pulseaudio enabled >> by default, of course), and it's up to the users to use it (under >> their own responsibility) or not. > > I would suggest that the alsa files in /extra are not actually "extra". > They are replacements for standard pulseaudio Slackware current packages. > > It would be hard for someone with with pulseaudio to test the alsa side of > things and hard for someone with alsa to test the pulseaudio side of > things. > > So instead of an alsa-pulseaudio switch perhaps we should allow two sets > of packages, the standard ones with pulseaudio and another set with alsa. > How would that make testing any easier for a maintainer - or are you suggesting having multiple maintainers too? It sounds like a lot of complication just for the sake of the few SlackBuilds that would actually be involved. No doubt alsa enthusiasts are smart enough to make their own changes in cases where the maintainer hasn't adopted some pulseaudio/alsa switch arrangement. Hint to alsa-enthusiasts: suggest your alsa-tested switch arrangement directly to the relevant maintainers. I'm sure such suggestions would mostly be adopted provided they don't adversely affect normal systems. chris _______________________________________________ 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 chris.willing at iinet.net.au Thu May 10 00:03:28 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Thu, 10 May 2018 10:03:28 +1000 Subject: [Slackbuilds-users] qt5 + pulseaudio In-Reply-To: References: Message-ID: <4a7e72f4-0a9d-08c8-caa2-c34ea604adda@iinet.net.au> On 10/05/18 09:43, Daniel Prosser wrote: >>>?Hint to alsa-enthusiasts:?suggest your alsa-tested switch arrangement > directly to the relevant maintainers. I'm sure such suggestions would > mostly be adopted provided They don't adversely affect normal systems.? > > Isn't that exactly what Hunter has done? Yes, bravo Hunter. However, I was responding to Richard's suggestion for a second set of SlackBuilds just to accommodate special requirements for ALSA-only users. chris > > On May 9, 2018 5:53 PM, Christoph Willing > wrote: > > On 10/05/18 06:53, Richard Narron wrote: > > On Tue, 8 May 2018, Matteo Bernardini wrote: > > > >> 2018-05-07 23:36 GMT+02:00 orbea at fredslev.dk : > >>> That assumption is irrelevant and if a maintainer is not willing to > >>> respond to bug reports then it should be possible to implement > fixes > >>> without the maintainer. > >>> > >>> The bottom line is that this patch would make the qt5.SlackBuild > more > >>> fail proof and the only reason to not accept it is to spite > people who > >>> do not use pulseaudio. This can only have a negative effect on the > >>> usefulness and reliability of SBo... > >> > >> we have different opinion on what is a bug an what are legit > >> maintainer decisions. > >> optional pulseaudio support is surely not a bug: pulseaudio is not > >> optional at all in slackware 14.2 and I explained why we cannot > >> consider it optional even in the next Slackware release: stuff in > >> /extra is not part of a Slackware full installation and we support > >> just that. > >> that said, is up to the maintainer if they want to add a switch in > >> their SlackBuilds to make pulseaudio optional (with pulseaudio > enabled > >> by default, of course), and it's up to the users to use it (under > >> their own responsibility) or not. > > > > I would suggest that the alsa files in /extra are not actually > "extra". > > They are replacements for standard pulseaudio Slackware current > packages. > > > > It would be hard for someone with with pulseaudio to test the alsa > side of > > things and hard for someone with alsa to test the pulseaudio side of > > things. > > > > So instead of an alsa-pulseaudio switch perhaps we should allow > two sets > > of packages, the standard ones with pulseaudio and another set > with alsa. > > > > How would that make testing any easier for a maintainer - or are you > suggesting having multiple maintainers too? It sounds like a lot of > complication just for the sake of the few SlackBuilds that would > actually be involved. > > No doubt alsa enthusiasts are smart enough to make their own changes in > cases where the maintainer hasn't adopted some pulseaudio/alsa switch > arrangement. > > Hint to alsa-enthusiasts: > ??? suggest your alsa-tested switch arrangement directly to the > relevant > maintainers. I'm sure such suggestions would mostly be adopted provided > they don't adversely affect normal systems. > > chris > > _______________________________________________ > 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/ > > > > > _______________________________________________ > 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 atelszewski at gmail.com Thu May 10 22:19:53 2018 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 11 May 2018 00:19:53 +0200 Subject: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm Message-ID: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> Hi, I've been talking with a user, who has problems building qt-creator together with optional qt-creator-llvm dependency. Because it builds fine on my side, I run out of ideas what might be wrong on his side. I'd like to ask some of you to test building the following configuration: $ ./qbs.SlackBuild and install $ ./qt-creator-llvm.SlackBuild and install $ USE_LLVM=yes ./qt-creator.SlackBuild and let me know if it works for you. Thanks in advance! -- Best regards / Pozdrawiam, Andrzej Telszewski From yalhcru at gmail.com Fri May 11 00:27:34 2018 From: yalhcru at gmail.com (B Watson) Date: Thu, 10 May 2018 20:27:34 -0400 Subject: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm In-Reply-To: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> References: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> Message-ID: On 5/10/18, Andrzej Telszewski wrote: > > Because it builds fine on my side, I run out of ideas what might be > wrong on his side. You and your user both using the same version of Slackware, the same arch (32-bit or 64-bit)? With or without multilib, if you're both on 64-bit? From chris.willing at iinet.net.au Fri May 11 01:15:12 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 11 May 2018 11:15:12 +1000 Subject: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm In-Reply-To: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> References: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> Message-ID: <0575eb44-c73d-98b9-ffc4-7c3a8d76d4f6@iinet.net.au> On 11/05/18 08:19, Andrzej Telszewski wrote: > Hi, > > I've been talking with a user, who has problems building qt-creator > together with optional qt-creator-llvm dependency. > > Because it builds fine on my side, I run out of ideas what might be > wrong on his side. > > I'd like to ask some of you to test building the following configuration: > > $ ./qbs.SlackBuild and install > $ ./qt-creator-llvm.SlackBuild and install > $ USE_LLVM=yes ./qt-creator.SlackBuild > > and let me know if it works for you. > It works for me in a fresh 64bit 14.2 VM. chris From fernando.lopezjr at gmail.com Fri May 11 03:59:43 2018 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 10 May 2018 21:59:43 -0600 Subject: [Slackbuilds-users] handbrake is downloading dependencies on its own... Message-ID: handbrake is downloading dependencies on its own... I thought it wasn't allowed. -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From john at server.ky Fri May 11 10:56:05 2018 From: john at server.ky (John) Date: Fri, 11 May 2018 12:56:05 +0200 Subject: [Slackbuilds-users] perl-WWW-Curl Message-ID: <9a29bdb4-230d-ca42-17e9-82b0d2b67f1f@server.ky> Hi All, Since nix no longer depends on perl-WWW-Curl, I would like to relinquish maintainership of it. Any takers? John -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat May 12 00:16:34 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 12 May 2018 07:16:34 +0700 Subject: [Slackbuilds-users] Updates - 20180512.1 Message-ID: <17df5e1f-e20a-6934-fd90-f896fecde217@slackbuilds.org> Hi Another weekly updates with more than 100+ changes in this batch. I wanted to include webkit2gtk update on this batch since it fixed some security vulnerabilities, but 2.20.2 keeps failing here, so any pointers will be gladly accepted :) Thank you for your contributions and have a great weekend. Sat May 12 00:00:00 UTC 2018 academic/ds9: Updated for version 7.6. desktop/Zafiro-icons: Updated for version 0.1.6. desktop/elementary-xfce: Updated for version 0.12. desktop/flatpak: Updated for version 0.11.7. desktop/xfce4-whiskermenu-plugin: Updated for version 1.7.5. development/android-studio: Fix unicode characters. development/composer: Updated for version 1.6.5 development/diffoscope: Updated for version 94. development/guzzle_sphinx_theme: Added (Sphinx theme for Guzzle). development/hhvm: Updated for version 3.24.7 development/ioncube-loader: Updated for version 10.2.1 development/jupyter-notebook: Updated for version 5.5.0. development/rstudio-desktop: Updated for version 1.1.447. development/sphinx_rtd_theme: Updated for version 0.3.1. development/srcML: Update homepage. development/universal-ctags: Updated for version 744610c games/RetroArch: Patched from upstream + add optional dep. games/dreamchess-music: Update homepage. games/dreamchess: Update homepage. games/hedgewars: Updated for version 0.9.24.1. games/oolite: Updated for version 1.86. games/redeclipse: Update homepage. games/speed-dreams: Updated for version 2.2.2_rc2_r6527. games/stockfish: Updated for version 9. games/tome: Updated for version 1.5.8. gis/osm2pgrouting: Update homepage. gis/pgrouting: Update homepage. gis/qmapshack: Updated for version 1.11.1. graphics/CairoSVG: Update homepage. libraries/botocore: Updated for version 1.10.14. libraries/hoel: Added (Database abstraction library written in C). libraries/libconfig: Updated for version 1.7.2. libraries/libfilezilla: Updated for version 0.12.2. libraries/libfm-extra: Upgraded for version 1.3.0.2. libraries/libfm: Upgraded for version 1.3.0.2. libraries/libinput: Remove libwacom leftover. libraries/libjwt: Added (JWT C Library). libraries/libtomcrypt: Update homepage. libraries/libuv: Updated for version 1.20.3. libraries/libwebp: Updated for version 1.0.0. libraries/msgpack-c: Updated for version 3.0.0. libraries/orcania: Added (C functions). libraries/physfs: Changed build options. libraries/rocksdb: Update homepage. libraries/tbb: Updated for version 2018u3. libraries/ulfius: Added (HTTP Framework for REST Applications in C). libraries/xcb-util-xrm: Updated for version 1.3. libraries/yder: Added (Logging library written in C). misc/KeePass: Updated for version 2.39. multimedia/exaile: Update homepage. multimedia/flashplayer-plugin: Updated for version 29.0.0.171. multimedia/opera-ffmpeg-codecs: Updated for version 66.0.3359.139. multimedia/pepperflash-plugin: Updated for version 29.0.0.171. multimedia/plexmediaserver: Updated for v 1.12.3.4973_215c28d86. network/PaleMoon: Updated for version 27.9.1. network/awscli: Updated for version 1.15.14. network/bip: Updated for version 0.9.0-rc3. network/discord: Updated for version 0.0.5. network/filezilla: Updated for version 3.33.0. network/glewlwyd: Added (Oauth 2 authentication server). network/ip2location-c: Updated for version 8.0.7. network/ipv6calc: Updated for version 1.0.0. network/miniupnpd: Added (IGD Protocol, NAT-PMP, and PCP daemon). network/opera-developer: Updated for version 54.0.2949.0. network/opera: Updated for version 53.0.2907.37. network/palemoon: Updated for version 27.9.1. network/radicale: Update homepage. network/tor-browser: Updated for version 7.5.4. network/verm: Updated for version 1.4.0. network/weathercli: Update script & DOWNLOAD. network/youtube-dl: Updated for version 2018.05.01. office/LibreOffice: Updated for version 6.0.4.2 office/asymptote: Updated for version 2.44. office/keepassxc: Updated for version 2.3.3. office/libreoffice-helppack: Updated for version 6.0.4. office/libreoffice-langpack: Updated for version 6.0.4. office/libreoffice: Updated for version 6.0.4. office/trelby: Update homepage. perl/perl-ExtUtils-InstallPaths: Updated for version 0.012. perl/perl-ExtUtils-ModuleMaker: Updated for version 0.58. perl/perl-Math-MPFR: Updated for version 4.04. perl/perl-Mojolicious: Update homepage. perl/perl-Sidef: Updated for version 3.16. perl/perl-strictures: Updated for version 2.000005. python/Flask: Updated for version 1.0.2. python/ipython: Upgraded for version 5.7.0. python/munch: Updated for version 2.3.2. python/pendulum: Updated for version 2.0.0. python/ps_mem: Updated for version 20180328. python/pycodestyle: Updated for version 2.4.0. python/pyglet: Updated for version 1.3.2. python/python-cached-property: Updated for version 1.4.2. python/python-docker-pycreds: Updated for version 0.2.3. python/python-docker: Updated for version 3.3.0. python/python-dockerpty: Update download URL. python/python-fonttools: Updated for version 3.26.0. python/python-m2r: Updated for version 0.1.14. python/python-texttable: Update download URL. python/python3-dateutil: Updated for version 2.7.3. python/python3-ipython: Updated for version 6.4.0. python/tqdm: Updated for version 4.23.3. ruby/ruby-faraday: Updated for version 0.15.1. ruby/rubygem-activesupport: Update homepage. system/borgbackup: Updated for version 1.1.5. system/containerd: Updated for version 1.0.3. system/dehydrated: Updated for version 0.6.2. system/docker-compose: Updated for version 1.21.1. system/docker-machine-kvm: Updated libraries. system/docker-machine: Updated for version 0.14.0. system/docker-proxy: Updated for version 20180412_c15b372. system/docker: Updated for version 18.03.1. system/eaglemode: Updated for version 0.93.1. system/fwupd: Updated for version 1.0.7. system/kbfs: Updated for version 1.0.48_20180510163508. system/kexec-tools: Updated for version 2.0.17. system/keybase: Updated for version 1.0.48. system/multicorn: Update homepage. system/nano-syntax-highlighting: Updated for version 20180505. system/nix: Updated for version 2.0.2. system/pcmanfm: Changed homepage. system/powerpanel: Added (CyberPower PowerPanel Personal Edition). system/pytrash: Added (CLI implementation of the "trash"). system/ranger: Updated for version 1.9.1. system/redis: Updated for version 4.0.9. system/sbbdep: Updated for version 0.3.1. system/sboui: Updated for version 1.1. system/slack-scripts: Updated for version 0.0.2. system/spman: Updated for version 1.5.1. system/vagrant: Updated for version 2.1.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kjhambrick at gmail.com Sat May 12 01:11:48 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Fri, 11 May 2018 20:11:48 -0500 Subject: [Slackbuilds-users] youtube-dl 2018.05.01 DOWNLOAD Message-ID: Dimitris -- Minor issue with this week's youtube-dl version 2018.05.01 update. The DOWNLOAD= Setting is a tad off. Patch for the youtube-dl.info file attached. Thanks for the youtube-dl.SlackBuild ( :) I use it WAY too often :) ) -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: youtube-dl.info-2018.05.01.patch Type: text/x-patch Size: 490 bytes Desc: not available URL: From dave at dawoodfall.net Sun May 13 00:27:14 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sun, 13 May 2018 01:27:14 +0100 Subject: [Slackbuilds-users] Calc Message-ID: <20180513002714.GF26365@blackswan> On the 6th I emailed the maintainer about adding readline support to calc to fix problems with backspace and delete keys, and I also mentioned possibly updating it. I haven't heard back so I'm mailing here in case he reads the list. Dave From slackbuilds at schoepfer.info Sun May 13 23:08:15 2018 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 14 May 2018 01:08:15 +0200 Subject: [Slackbuilds-users] texlive 2017 download location Message-ID: <8293ae8778995548c57b0a5717e22af9@schoepfer.info> Hi, the texlive-2017 sources were removed from ctan, alternative location: ftp://tug.org/historic/systems/texlive/2017/texlive-20170524-source.tar.xz The md5sum may also be diffrent, since there was a slightly diffrent(but same content) version on ctan. I'll submit an update, or some kind admin may fix it. Thanks, Johannes From matteo.bernardini at gmail.com Mon May 14 03:32:12 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 14 May 2018 05:32:12 +0200 Subject: [Slackbuilds-users] texlive 2017 download location In-Reply-To: <8293ae8778995548c57b0a5717e22af9@schoepfer.info> References: <8293ae8778995548c57b0a5717e22af9@schoepfer.info> Message-ID: 2018-05-14 1:08 GMT+02:00 Franzen : > Hi, > > the texlive-2017 sources were removed from ctan, > alternative location: > ftp://tug.org/historic/systems/texlive/2017/texlive-20170524-source.tar.xz > The md5sum may also be diffrent, since there was a slightly diffrent(but > same content) version on ctan. > > I'll submit an update, or some kind admin may fix it. Hi Johannes, I mirrored the original tarball, hope it's ok for you. https://git.slackbuilds.org/slackbuilds/commit/?id=4421e4830d531414fb190399cab79257c38f1ef9 Matteo From slackbuilds at schoepfer.info Mon May 14 07:18:44 2018 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 14 May 2018 09:18:44 +0200 Subject: [Slackbuilds-users] texlive 2017 download location In-Reply-To: References: <8293ae8778995548c57b0a5717e22af9@schoepfer.info> Message-ID: <3971ee8ff4ef6fefb07f5c1008304e79@schoepfer.info> On 2018-05-14 05:32, Matteo Bernardini wrote: > 2018-05-14 1:08 GMT+02:00 Franzen : >> Hi, >> >> the texlive-2017 sources were removed from ctan, >> alternative location: >> ftp://tug.org/historic/systems/texlive/2017/texlive-20170524-source.tar.xz >> The md5sum may also be diffrent, since there was a slightly >> diffrent(but >> same content) version on ctan. >> >> I'll submit an update, or some kind admin may fix it. > > Hi Johannes, > > I mirrored the original tarball, hope it's ok for you. > > https://git.slackbuilds.org/slackbuilds/commit/?id=4421e4830d531414fb190399cab79257c38f1ef9 Sure, thank you, Johannes From andreas.guldstrand at gmail.com Mon May 14 12:03:39 2018 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Mon, 14 May 2018 14:03:39 +0200 Subject: [Slackbuilds-users] perl-WWW-Curl In-Reply-To: <9a29bdb4-230d-ca42-17e9-82b0d2b67f1f@server.ky> References: <9a29bdb4-230d-ca42-17e9-82b0d2b67f1f@server.ky> Message-ID: On 11 May 2018 at 12:56, John wrote: > Hi All, > > Since nix no longer depends on perl-WWW-Curl, I would like to relinquish > maintainership of it. > > Any takers? I'll happily take it, thanks! > John > > > _______________________________________________ > 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 rshepard at appl-ecosys.com Mon May 14 16:32:37 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 14 May 2018 09:32:37 -0700 (PDT) Subject: [Slackbuilds-users] Request of Python package maintainers Message-ID: I've learned that many Python packages, even those that are supposed to support python2 and python3, build and install only for python2. While I have applications written by others that still depend on python-2.7.x, I'm now writing using only python3, and getting tools to work has been time consuming. While pylint-1.7.1 is installed here, I discovered that it does not work on python3 code. Changing /usr/bin/pylint and /usr/bin/pyreverse to invoke python3 did not fix the problem for two reasons: 1. Many installed dependencies are found in only /usr/lib/python2.7/site-packages/ and had to be re-built with the 'python setup.py install ...' line changed to use python3. 2. Some new dependences popped up, including isort, wrapt, and asteroid. These, too, needed their SlackBuild scripts modifed to install in /usr/lib/python3.6/site-packages/ rather than in the 2.7/site-packages/ directory. Now pylint and pyreverse work here. Whew! My request is to please test your scripts with python-3.6 or later (since some changes were made in 3.3 and 3.4), or prepare separate python3-* scripts. Thanks in advance, Rich From atelszewski at gmail.com Tue May 15 13:24:07 2018 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 15 May 2018 15:24:07 +0200 Subject: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm In-Reply-To: <0575eb44-c73d-98b9-ffc4-7c3a8d76d4f6@iinet.net.au> References: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> <0575eb44-c73d-98b9-ffc4-7c3a8d76d4f6@iinet.net.au> Message-ID: On 11/05/18 03:15, Christoph Willing wrote: > On 11/05/18 08:19, Andrzej Telszewski wrote: >> Hi, >> >> I've been talking with a user, who has problems building qt-creator >> together with optional qt-creator-llvm dependency. >> >> Because it builds fine on my side, I run out of ideas what might be >> wrong on his side. >> >> I'd like to ask some of you to test building the following configuration: >> >> $ ./qbs.SlackBuild and install >> $ ./qt-creator-llvm.SlackBuild and install >> $ USE_LLVM=yes ./qt-creator.SlackBuild >> >> and let me know if it works for you. >> > > It works for me in a fresh 64bit 14.2 VM. > > chris Thanks for testing. -- Best regards / Pozdrawiam, Andrzej Telszewski From atelszewski at gmail.com Tue May 15 13:25:18 2018 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 15 May 2018 15:25:18 +0200 Subject: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm In-Reply-To: References: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> Message-ID: <59146946-91f7-a5b8-0f4d-52b93c948da1@gmail.com> On 11/05/18 02:27, B Watson wrote: > On 5/10/18, Andrzej Telszewski wrote: >> >> Because it builds fine on my side, I run out of ideas what might be >> wrong on his side. > > You and your user both using the same version of Slackware, the same arch > (32-bit or 64-bit)? With or without multilib, if you're both on 64-bit? He confirms that our setups are mostly the same. Anyway, I asked him to post to the ML. Thanks. -- Best regards / Pozdrawiam, Andrzej Telszewski From yalhcru at gmail.com Fri May 18 05:21:56 2018 From: yalhcru at gmail.com (B Watson) Date: Fri, 18 May 2018 01:21:56 -0400 Subject: [Slackbuilds-users] addition for faq or howto Message-ID: Got an email from a new user... he had read the README for the build he was trying to run, and it said to set an environment variable... being completely new to *nix, he didn't know how to do that. Would it hurt to add some text to the HOWTO page explaining this? I know it's pretty elementary stuff, but the HOWTO already details how to extract a tarball and launch a shell script from the current directory, which are also elementary tasks... Proposed text to add to the end of "Step 2 - Read the README": ---cut-here--- If the README mentions any options controlled by environment variables, you can set these options now by running: export VARIABLE=value For instance, if the README says you can build against SDL 2.0 by setting SDL2=yes in the environment, you would type: export SDL2=yes If there are multiple options, you can use multiple export commands. If you're unsure, don't set any variables here. In most cases, the SlackBuild maintainer has made the default behaviour (no options) the most common or most useful way to build the package. ---cut-here--- ...yes, it's possible (and "cleaner") to just say SDL2=yes ./whatever.SlackBuild in Step 4, but the way the howto is split up into steps, it would make less sense for step 4 to effectively say "Oh, by the way, you should have noticed if there were environment variable options in step 2". So Step 2 has to mention them, since that's where they're visible. Thoughts? From klaatu at member.fsf.org Fri May 18 06:12:37 2018 From: klaatu at member.fsf.org (Klaatu) Date: Fri, 18 May 2018 18:12:37 +1200 Subject: [Slackbuilds-users] addition for faq or howto In-Reply-To: References: Message-ID: <1CECD7E0-2C3F-4F3D-A7D1-00BA6FC0B1FD@member.fsf.org> I thought about suggesting this myself, some time ago. I think it's not a bad idea to encourage maintainers to provide an example in the README too, just for the user's convenience. On 18 May 2018 5:21:56 PM NZST, B Watson wrote: >Got an email from a new user... he had read the README for the build he >was trying to run, and it said to set an environment variable... being >completely new to *nix, he didn't know how to do that. > >Would it hurt to add some text to the HOWTO page explaining this? I >know it's pretty elementary stuff, but the HOWTO already details how to >extract a tarball and launch a shell script from the current directory, >which are also elementary tasks... > >Proposed text to add to the end of "Step 2 - Read the README": > >---cut-here--- >If the README mentions any options controlled by environment variables, >you can set these options now by running: > > export VARIABLE=value > >For instance, if the README says you can build against SDL 2.0 by >setting >SDL2=yes in the environment, you would type: > > export SDL2=yes > >If there are multiple options, you can use multiple export commands. > >If you're unsure, don't set any variables here. In most cases, the >SlackBuild maintainer has made the default behaviour (no options) the >most common or most useful way to build the package. >---cut-here--- > >...yes, it's possible (and "cleaner") to just say SDL2=yes >./whatever.SlackBuild in Step 4, but the way the howto is split up >into steps, it would make less sense for step 4 to effectively say "Oh, >by the way, you should have noticed if there were environment variable >options in step 2". So Step 2 has to mention them, since that's where >they're visible. > >Thoughts? >_______________________________________________ >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/ -- Klaatu -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Fri May 18 08:54:10 2018 From: didier at slint.fr (Didier Spaier) Date: Fri, 18 May 2018 10:54:10 +0200 Subject: [Slackbuilds-users] addition for faq or howto In-Reply-To: References: Message-ID: <171af65e-69f9-41ea-0c48-fcff493eabe8@slint.fr> Hello, Le 18/05/2018 ? 07:21, B Watson a ?crit?: > Proposed text to add to the end of "Step 2 - Read the README": > > ---cut-here--- > If the README mentions any options controlled by environment variables, > you can set these options now by running: > > export VARIABLE=value > > For instance, if the README says you can build against SDL 2.0 by setting > SDL2=yes in the environment, you would type: > > export SDL2=yes > > If there are multiple options, you can use multiple export commands. > > If you're unsure, don't set any variables here. In most cases, the > SlackBuild maintainer has made the default behaviour (no options) the > most common or most useful way to build the package. > ---cut-here--- Yes, that would certainly help users not acquainted with shell scripting and I assume there are many. Greetings, Didier From alleytrotter at gmail.com Fri May 18 12:17:26 2018 From: alleytrotter at gmail.com (John) Date: Fri, 18 May 2018 08:17:26 -0400 Subject: [Slackbuilds-users] firejail Message-ID: firejail chokes on latest firefox-60.0.1 firejail firefox Reading profile /etc/firejail/firefox.profile Reading profile /etc/firejail/disable-common.inc Reading profile /etc/firejail/disable-devel.inc Reading profile /etc/firejail/disable-programs.inc Reading profile /etc/firejail/whitelist-common.inc Reading profile /etc/firejail/whitelist-var-common.inc Parent pid 16412, child pid 16413 Blacklist violations are logged to syslog Child process initialized in 57.85 ms [Parent 6, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 709 [Parent 6, Gecko_IOThread] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc, line 22 ###!!! [Parent][MessageChannel] Error: (msgtype=0x2C000B,name=PContent::Msg_InitRendering) Channel error: cannot send/recv [Parent 6, Main Thread] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc, line 22 ###!!! [Parent][MessageChannel] Error: (msgtype=0x2C003A,name=PContent::Msg_LoadAndRegisterSheet) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x2C000F,name=PContent::Msg_SetProcessSandbox) Channel error: cannot send/recv [Parent 6, Main Thread] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc, line 22 ###!!! [Parent][MessageChannel] Error: (msgtype=0x2C0055,name=PContent::Msg_SetPermissionsWithKey) Channel error: cannot send/recv thank you AlleyTrotter -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at osh.id.au Fri May 18 13:01:59 2018 From: lists at osh.id.au (David O'Shaughnessy) Date: Fri, 18 May 2018 23:01:59 +1000 Subject: [Slackbuilds-users] firejail In-Reply-To: References: Message-ID: <26bb6a89-b4c0-325d-c736-2cc4f4bf9bcc@osh.id.au> On 05/18/2018 10:17 PM, John wrote: > firejail chokes on latest firefox-60.0.1 I had a bunch of errors also, bumping Firejail to the latest version seems to fix it. -- Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: firejail.patch Type: text/x-patch Size: 1005 bytes Desc: not available URL: From alleytrotter at gmail.com Fri May 18 13:36:55 2018 From: alleytrotter at gmail.com (John Yost) Date: Fri, 18 May 2018 09:36:55 -0400 Subject: [Slackbuilds-users] firejail In-Reply-To: <26bb6a89-b4c0-325d-c736-2cc4f4bf9bcc@osh.id.au> References: <26bb6a89-b4c0-325d-c736-2cc4f4bf9bcc@osh.id.au> Message-ID: <0881c6bb-6f2e-f161-fc46-0636c1c0ead7@gmail.com> On 05/18/2018 09:01 AM, David O'Shaughnessy wrote: > On 05/18/2018 10:17 PM, John wrote: >> firejail chokes on latest firefox-60.0.1 > > I had a bunch of errors also, bumping Firejail to the latest version > seems to fix it. > > -- > 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/ > works fine her also with new version John -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x2C7AF6BEF3BDEB55.asc Type: application/pgp-keys Size: 2312 bytes Desc: not available URL: From willysr at slackbuilds.org Fri May 18 21:26:05 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 19 May 2018 04:26:05 +0700 Subject: [Slackbuilds-users] firejail In-Reply-To: <0881c6bb-6f2e-f161-fc46-0636c1c0ead7@gmail.com> Message-ID: An HTML attachment was scrubbed... URL: From idlemoor at slackbuilds.org Sat May 19 00:33:04 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Sat, 19 May 2018 01:33:04 +0100 Subject: [Slackbuilds-users] Updates - 20180519.1 Message-ID: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> Hi everybody, Here's this week's public update. Thanks to all our contributors! Please note that there is a small problem with the .info file for prosody, we'll fix this in another update very soon. Sat May 19 00:00:01 UTC 2018 academic/STAR: Added (Spliced Transcripts Alignment to a Reference). academic/calc: Updated for version 2.12.6.5. academic/flexbar: Updated for version 3.1.0. academic/pysam: Updated for version 0.14.1. audio/clockchimes: Updated for version 0.2. audio/pd: Updated for version 0.48_1. desktop/Zafiro-icons: Updated for version 0.1.8. desktop/mh5000: Updated for version 1.3.4. desktop/murrine: Fix build with slibtool. desktop/neofetch: Updated for version 4.0.0. desktop/oranchelo-icon-theme: Updated for version 0.7.9. desktop/xpenguins_themes: Added (addon for xpenguins). development/atom-amd64: Updated for version 1.27.0. development/byacc: Updated for version 20180510. development/cargo-vendor: Updated for version 0.1.14. development/extra-cmake-modules: Updated for version 5.46.0. development/jupyter-nbdime: Updated for version 1.0.0. development/mlton: Updated for version 20180207 + new maintainer. development/p4: Updated for version 2018.1.1660568. development/p4d: Updated for version 2018.1.1660568. games/doomretro: Updated for version 2.6.9. games/javacpc: Updated for version 2.9.6d. games/nethack: Updated for version 3.6.1. games/oolite: Updated for version 1.86. games/pcsx2: Updated for version 2018.05.16_290397d. gis/gdal: Updated for version 2.3.0. gis/geopy: Updated for version 1.14.0. gis/gpxsee: Updated for version 5.11. gis/pdal: Updated for version 1.7.2. graphics/feh: Updated for version 2.26.2. graphics/viewnior: Updated for version 1.7. libraries/VTK: Updated for version 8.1.1 libraries/libinput: Updated for version 1.10.7. libraries/liblxi: Updated for version 1.13 libraries/msgpack-c: Updated for version 3.0.1. libraries/ulfius: Updated for version 2.3.5. libraries/wxSQLite3: Updated for version 4.0.3. misc/KeePass: Updated for version 2.39.1. misc/xdelta: Fixed download. multimedia/devedeng: Updated for version 4.11.0. multimedia/get_iplayer: Updated for version 3.14. multimedia/obs-studio: Updated for version 21.1.2 multimedia/opera-ffmpeg-codecs: Updated for version 66.0.3359.170. multimedia/plexmediaserver: Updated for version 1.13.0. network/WireGuard: Updated for version 0.0.20180514. network/aria2: Updated for version 1.34.0. network/basilisk-src: Updated for version 2018.05.15. network/basilisk: Updated for version 2018.05.15. network/liferea: Updated for version 1.12.3 + new maintainer. network/lxi-tools: Updated for version 1.20 network/offlineimap: Updated for version 7.2.0. network/opera-developer: Updated for version 55.0.2955.0. network/opera: Updated for version 53.0.2907.57. network/palemoon: Updated for version 27.9.2. network/phpmyadmin: Updated for version 4.8.0.1. network/postfix: Retain license files. network/prosody: Updated for version 0.10.1 network/qbittorrent-qt5: Updated for version 4.1.0. network/qbittorrent: Update to rc init file. network/qutebrowser: Updated for version 1.3.0. network/riot-web: Updated for version 0.14.2. network/shorewall-core: Updated for version 5.2.0.3. network/shorewall6: Updated for version 5.2.0.3. network/shorewall: Updated for version 5.2.0.3. network/strongswan: Updated for version 5.6.2 + new maintainer. network/verm: Updated for version 1.5.0. network/vivaldi: Updated for version 1.15.1147.42. network/youtube-dl: Updated for version 2018.05.09. office/texlive: Fix download. perl/perl-ExtUtils-ModuleMaker: Updated for version 0.62. python/invoke: Updated for version 1.0.0.. python/python-autobahn: Updated for version 18.5.1. python/ruffus: Updated for version 2.6.3. system/ansible: Updated for version 2.5.2. system/cronie: Updated for version 1.5.2. system/dar: Updated for version 2.5.15. system/dosbox-dev: Updated for version 0.74.r4101. system/firejail: Updated for version 0.9.54. system/geoclue2: Updated for version 2.4.10. system/inxi: Updated for version 3.0.09. system/jdupes: Added (taking action upon duplicate files). system/lynis: Update DOWNLOAD url. system/nano-syntax-highlighting: Updated for version 20180508. system/pytrash: Updated for version 1.1.1. system/sbbdep: Updated for version 0.3.2. system/spman: Updated for version 1.5.2. system/thin-provisioning-tools: Updated for version 0.7.6. system/wine: Updated for version 3.0.1. system/xen: Updated for version 4.10.1. +--------------------------+ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From dpross1100 at msn.com Sat May 19 01:56:12 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 19 May 2018 01:56:12 +0000 Subject: [Slackbuilds-users] Updates - 20180519.1 In-Reply-To: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> References: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> Message-ID: Hi, Can someone explain why wine was downgraded from 3.1 to 3.0.1? Regards, Dan On Sat, 2018-05-19 at 01:33 +0100, David Spencer wrote: > Hi everybody, > > Here's this week's public update. Thanks to all our contributors! > > Please note that there is a small problem with the .info file for > prosody, we'll fix this in another update very soon. > > Sat May 19 00:00:01 UTC 2018 > academic/STAR: Added (Spliced Transcripts Alignment to a Reference). > academic/calc: Updated for version 2.12.6.5. > academic/flexbar: Updated for version 3.1.0. > academic/pysam: Updated for version 0.14.1. > audio/clockchimes: Updated for version 0.2. > audio/pd: Updated for version 0.48_1. > desktop/Zafiro-icons: Updated for version 0.1.8. > desktop/mh5000: Updated for version 1.3.4. > desktop/murrine: Fix build with slibtool. > desktop/neofetch: Updated for version 4.0.0. > desktop/oranchelo-icon-theme: Updated for version 0.7.9. > desktop/xpenguins_themes: Added (addon for xpenguins). > development/atom-amd64: Updated for version 1.27.0. > development/byacc: Updated for version 20180510. > development/cargo-vendor: Updated for version 0.1.14. > development/extra-cmake-modules: Updated for version 5.46.0. > development/jupyter-nbdime: Updated for version 1.0.0. > development/mlton: Updated for version 20180207 + new maintainer. > development/p4: Updated for version 2018.1.1660568. > development/p4d: Updated for version 2018.1.1660568. > games/doomretro: Updated for version 2.6.9. > games/javacpc: Updated for version 2.9.6d. > games/nethack: Updated for version 3.6.1. > games/oolite: Updated for version 1.86. > games/pcsx2: Updated for version 2018.05.16_290397d. > gis/gdal: Updated for version 2.3.0. > gis/geopy: Updated for version 1.14.0. > gis/gpxsee: Updated for version 5.11. > gis/pdal: Updated for version 1.7.2. > graphics/feh: Updated for version 2.26.2. > graphics/viewnior: Updated for version 1.7. > libraries/VTK: Updated for version 8.1.1 > libraries/libinput: Updated for version 1.10.7. > libraries/liblxi: Updated for version 1.13 > libraries/msgpack-c: Updated for version 3.0.1. > libraries/ulfius: Updated for version 2.3.5. > libraries/wxSQLite3: Updated for version 4.0.3. > misc/KeePass: Updated for version 2.39.1. > misc/xdelta: Fixed download. > multimedia/devedeng: Updated for version 4.11.0. > multimedia/get_iplayer: Updated for version 3.14. > multimedia/obs-studio: Updated for version 21.1.2 > multimedia/opera-ffmpeg-codecs: Updated for version 66.0.3359.170. > multimedia/plexmediaserver: Updated for version 1.13.0. > network/WireGuard: Updated for version 0.0.20180514. > network/aria2: Updated for version 1.34.0. > network/basilisk-src: Updated for version 2018.05.15. > network/basilisk: Updated for version 2018.05.15. > network/liferea: Updated for version 1.12.3 + new maintainer. > network/lxi-tools: Updated for version 1.20 > network/offlineimap: Updated for version 7.2.0. > network/opera-developer: Updated for version 55.0.2955.0. > network/opera: Updated for version 53.0.2907.57. > network/palemoon: Updated for version 27.9.2. > network/phpmyadmin: Updated for version 4.8.0.1. > network/postfix: Retain license files. > network/prosody: Updated for version 0.10.1 > network/qbittorrent-qt5: Updated for version 4.1.0. > network/qbittorrent: Update to rc init file. > network/qutebrowser: Updated for version 1.3.0. > network/riot-web: Updated for version 0.14.2. > network/shorewall-core: Updated for version 5.2.0.3. > network/shorewall6: Updated for version 5.2.0.3. > network/shorewall: Updated for version 5.2.0.3. > network/strongswan: Updated for version 5.6.2 + new maintainer. > network/verm: Updated for version 1.5.0. > network/vivaldi: Updated for version 1.15.1147.42. > network/youtube-dl: Updated for version 2018.05.09. > office/texlive: Fix download. > perl/perl-ExtUtils-ModuleMaker: Updated for version 0.62. > python/invoke: Updated for version 1.0.0.. > python/python-autobahn: Updated for version 18.5.1. > python/ruffus: Updated for version 2.6.3. > system/ansible: Updated for version 2.5.2. > system/cronie: Updated for version 1.5.2. > system/dar: Updated for version 2.5.15. > system/dosbox-dev: Updated for version 0.74.r4101. > system/firejail: Updated for version 0.9.54. > system/geoclue2: Updated for version 2.4.10. > system/inxi: Updated for version 3.0.09. > system/jdupes: Added (taking action upon duplicate files). > system/lynis: Update DOWNLOAD url. > system/nano-syntax-highlighting: Updated for version 20180508. > system/pytrash: Updated for version 1.1.1. > system/sbbdep: Updated for version 0.3.2. > system/spman: Updated for version 1.5.2. > system/thin-provisioning-tools: Updated for version 0.7.6. > system/wine: Updated for version 3.0.1. > system/xen: Updated for version 4.10.1. > +--------------------------+ > > _______________________________________________ > 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 dave at dawoodfall.net Sat May 19 02:27:09 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sat, 19 May 2018 03:27:09 +0100 Subject: [Slackbuilds-users] Updates - 20180519.1 In-Reply-To: References: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> Message-ID: <20180519022709.GA9791@blackswan> On Saturday 19 May 2018 01:56, Daniel Prosser put forth the proposition: >Hi, > >Can someone explain why wine was downgraded from 3.1 to 3.0.1? > >Regards, >Dan I did it because wine is meant to follow the stable branch and I had a bit of a brainfart and updated it to an (old) dev version the last time I updated it. wine-staging follows the dev branch. Best, -Dave -- Please don't reply directly to me or CC me. /* * [...] Note that 120 sec is defined in the protocol as the maximum * possible RTT. I guess we'll have to use something other than TCP * to talk to the University of Mars. * PAWS allows us longer timeouts and large windows, so once implemented * ftp to mars will work nicely. */ -- from /usr/src/linux/net/inet/tcp.c, concerning RTT [round trip time] oo .--. \\(____) `~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From dpross1100 at msn.com Sat May 19 02:35:41 2018 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 19 May 2018 02:35:41 +0000 Subject: [Slackbuilds-users] Updates - 20180519.1 In-Reply-To: <20180519022709.GA9791@blackswan> References: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> <20180519022709.GA9791@blackswan> Message-ID: Makes sense, then. Thanks! On Sat, 2018-05-19 at 03:27 +0100, David Woodfall wrote: > On Saturday 19 May 2018 01:56, > Daniel Prosser put forth the proposition: > > Hi, > > > > Can someone explain why wine was downgraded from 3.1 to 3.0.1? > > > > Regards, > > Dan > > I did it because wine is meant to follow the stable branch and I had > a bit of a brainfart and updated it to an (old) dev version the last > time I updated it. > > wine-staging follows the dev branch. > > Best, > > -Dave > > -- > > Please don't reply directly to me or CC me. > > /* > ?* [...] Note that 120 sec is defined in the protocol as the maximum > ?* possible RTT.??I guess we'll have to use something other than TCP > ?* to talk to the University of Mars. > ?* PAWS allows us longer timeouts and large windows, so once > implemented > ?* ftp to mars will work nicely. > ?*/ > ? -- from /usr/src/linux/net/inet/tcp.c, concerning RTT [round trip > time] > > oo??.--. > ?\\(____) > ? `~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > _______________________________________________ > 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 skaendo at excite.com Sat May 19 02:41:04 2018 From: skaendo at excite.com (Ed Ender) Date: Fri, 18 May 2018 22:41:04 -0400 Subject: [Slackbuilds-users] palemoon and basilisk SlackBuilds Message-ID: <20180518224104.17344@web002.roc2.bluetie.com> Anyone who would like to take over maintaining the palemoon and/or the basilisk SlackBuilds of mine (both are binary repackage), they are up for grabs as I no longer use them. https://slackbuilds.org/repository/14.2/network/palemoon/ https://slackbuilds.org/repository/14.2/network/basilisk/ They are both currently up to date. From dave at dawoodfall.net Sat May 19 03:24:30 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sat, 19 May 2018 04:24:30 +0100 Subject: [Slackbuilds-users] pudb Message-ID: <20180519032430.GC12999@blackswan> Mailing here in the hope that the maintainer sees it. The sbo version is at least 2 years old. The latest version is 2017.1.4 Support for python3 could be added too. I'm running the py3 version right now. -Dave -- Please don't reply directly to me or CC me. Anyone who thinks UNIX is intuitive should be forced to write 5000 lines of code using nothing but vi or emacs. AAAAACK! -- Discussion on the intuitiveness of commands, especially Emacs .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From chris.willing at iinet.net.au Sat May 19 08:25:55 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 19 May 2018 18:25:55 +1000 Subject: [Slackbuilds-users] Updates - 20180519.1 (geoclue2) In-Reply-To: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> References: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> Message-ID: <97577de7-f2dd-f60c-251b-1e14b6e43985@iinet.net.au> On 19/05/18 10:33, David Spencer wrote: > Hi everybody, > > Here's this week's public update. Thanks to all our contributors! > > Please note that there is a small problem with the .info file for > prosody, we'll fix this in another update very soon. > [snip] > system/geoclue2: Updated for version 2.4.10. I'm having a build problem with this update (previous version was fine) in a clean x86_64 14.2 VM: checking for GTKDOC_DEPS... yes checking for GEOCLUE... yes checking for gobject-introspection... yes checking for LIBGEOCLUE... yes checking for ModemManager... no configure: error: Package requirements (mm-glib >= 1.6) were not met: Requested 'mm-glib >= 1.6' but version of mm-glib is 1.4.14 I have /var/log/packages/ModemManager-1.4.14-x86_64-1 installed which is the latest for 14.2 according to the ChangeLog.txt. I see that -current has ModemManager-1.6.12-x86_64-2.txz so it looks like this particular geoclue2 update is meant for -current, not -stable. Any other ideas? chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From dave at dawoodfall.net Sat May 19 09:31:11 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sat, 19 May 2018 10:31:11 +0100 Subject: [Slackbuilds-users] Updates - 20180519.1 (geoclue2) In-Reply-To: <97577de7-f2dd-f60c-251b-1e14b6e43985@iinet.net.au> References: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> <97577de7-f2dd-f60c-251b-1e14b6e43985@iinet.net.au> Message-ID: <20180519093111.GF12999@blackswan> On Saturday 19 May 2018 18:25, Christoph Willing put forth the proposition: > On 19/05/18 10:33, David Spencer wrote: > > Hi everybody, > > > > Here's this week's public update. Thanks to all our contributors! > > > > Please note that there is a small problem with the .info file for > > prosody, we'll fix this in another update very soon. > > > [snip] > > system/geoclue2: Updated for version 2.4.10. > > I'm having a build problem with this update (previous version was fine) > in a clean x86_64 14.2 VM: > > checking for GTKDOC_DEPS... yes > checking for GEOCLUE... yes > checking for gobject-introspection... yes > checking for LIBGEOCLUE... yes > checking for ModemManager... no > configure: error: Package requirements (mm-glib >= 1.6) were not met: > > Requested 'mm-glib >= 1.6' but version of mm-glib is 1.4.14 > > I have /var/log/packages/ModemManager-1.4.14-x86_64-1 installed which is > the latest for 14.2 according to the ChangeLog.txt. I see that -current > has ModemManager-1.6.12-x86_64-2.txz so it looks like this particular > geoclue2 update is meant for -current, not -stable. > > Any other ideas? > > chris Which version of glibmm do you have? glibmm-2.46.4 here. -Dave -- Please don't reply directly to me or CC me. Excusing bad programming is a shooting offence, no matter _what_ the circumstances. -- Linus Torvalds, to the linux-kernel list .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From chris.willing at iinet.net.au Sat May 19 11:23:26 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 19 May 2018 21:23:26 +1000 Subject: [Slackbuilds-users] Updates - 20180519.1 (geoclue2) In-Reply-To: <20180519093111.GF12999@blackswan> References: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> <97577de7-f2dd-f60c-251b-1e14b6e43985@iinet.net.au> <20180519093111.GF12999@blackswan> Message-ID: <01acb8e5-0afd-8b9b-4311-a8346df139dd@iinet.net.au> On 19/05/18 19:31, David Woodfall wrote: > On Saturday 19 May 2018 18:25, > Christoph Willing put forth the proposition: >> On 19/05/18 10:33, David Spencer wrote: >>> Hi everybody, >>> >>> Here's this week's public update. Thanks to all our contributors! >>> >>> Please note that there is a small problem with the .info file for >>> prosody, we'll fix this in another update very soon. >>> >> [snip] >>> system/geoclue2: Updated for version 2.4.10. >> >> I'm having a build problem with this update (previous version was fine) >> in a clean x86_64 14.2 VM: >> >> checking for GTKDOC_DEPS... yes >> checking for GEOCLUE... yes >> checking for gobject-introspection... yes >> checking for LIBGEOCLUE... yes >> checking for ModemManager... no >> configure: error: Package requirements (mm-glib >= 1.6) were not met: >> >> Requested 'mm-glib >= 1.6' but version of mm-glib is 1.4.14 >> >> I have /var/log/packages/ModemManager-1.4.14-x86_64-1 installed which is >> the latest for 14.2 according to the ChangeLog.txt. I see that -current >> has ModemManager-1.6.12-x86_64-2.txz so it looks like this particular >> geoclue2 update is meant for -current, not -stable. >> >> Any other ideas? >> >> chris > > Which version of glibmm do you have? > > glibmm-2.46.4 here. > Yes, glibmm-2.46.4-x86_64-1 here too. However I think the mm-glib reported in the error message refers to when the the geoclue2 configuration is checking the /usr/lib64/pkgconfig/mm-glib.pc file (part of the ModemManager package). chris From dave at dawoodfall.net Sat May 19 11:47:12 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sat, 19 May 2018 12:47:12 +0100 Subject: [Slackbuilds-users] Updates - 20180519.1 (geoclue2) In-Reply-To: <01acb8e5-0afd-8b9b-4311-a8346df139dd@iinet.net.au> References: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> <97577de7-f2dd-f60c-251b-1e14b6e43985@iinet.net.au> <20180519093111.GF12999@blackswan> <01acb8e5-0afd-8b9b-4311-a8346df139dd@iinet.net.au> Message-ID: <20180519114712.GI12999@blackswan> On Saturday 19 May 2018 21:23, Christoph Willing put forth the proposition: > On 19/05/18 19:31, David Woodfall wrote: > > On Saturday 19 May 2018 18:25, > > Christoph Willing put forth the proposition: > >> On 19/05/18 10:33, David Spencer wrote: > >>> Hi everybody, > >>> > >>> Here's this week's public update. Thanks to all our contributors! > >>> > >>> Please note that there is a small problem with the .info file for > >>> prosody, we'll fix this in another update very soon. > >>> > >> [snip] > >>> system/geoclue2: Updated for version 2.4.10. > >> > >> I'm having a build problem with this update (previous version was fine) > >> in a clean x86_64 14.2 VM: > >> > >> checking for GTKDOC_DEPS... yes > >> checking for GEOCLUE... yes > >> checking for gobject-introspection... yes > >> checking for LIBGEOCLUE... yes > >> checking for ModemManager... no > >> configure: error: Package requirements (mm-glib >= 1.6) were not met: > >> > >> Requested 'mm-glib >= 1.6' but version of mm-glib is 1.4.14 > >> > >> I have /var/log/packages/ModemManager-1.4.14-x86_64-1 installed which is > >> the latest for 14.2 according to the ChangeLog.txt. I see that -current > >> has ModemManager-1.6.12-x86_64-2.txz so it looks like this particular > >> geoclue2 update is meant for -current, not -stable. > >> > >> Any other ideas? > >> > >> chris > > > > Which version of glibmm do you have? > > > > glibmm-2.46.4 here. > > > > Yes, glibmm-2.46.4-x86_64-1 here too. > > However I think the mm-glib reported in the error message refers to when > the the geoclue2 configuration is checking the > /usr/lib64/pkgconfig/mm-glib.pc file (part of the ModemManager package). > > chris Yeah the configure checks that. What do pkg-config --print-errors --exists mm-glib pkg-config --print-errors --exists ModemManager output? -- Please don't reply directly to me or CC me. > You know you are "there" when you are known by your first name, and > are recognized. > Lemmie see, there is Madonna, and Linus, and ..... help me out here! Bill ? ;-) -- From some postings on comp.os.linux.misc .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From chris.willing at iinet.net.au Sat May 19 12:02:15 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 19 May 2018 22:02:15 +1000 Subject: [Slackbuilds-users] Updates - 20180519.1 (geoclue2) In-Reply-To: <20180519114712.GI12999@blackswan> References: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> <97577de7-f2dd-f60c-251b-1e14b6e43985@iinet.net.au> <20180519093111.GF12999@blackswan> <01acb8e5-0afd-8b9b-4311-a8346df139dd@iinet.net.au> <20180519114712.GI12999@blackswan> Message-ID: On 19/05/18 21:47, David Woodfall wrote: > On Saturday 19 May 2018 21:23, > Christoph Willing put forth the proposition: >> On 19/05/18 19:31, David Woodfall wrote: >>> On Saturday 19 May 2018 18:25, >>> Christoph Willing put forth the proposition: >>>> On 19/05/18 10:33, David Spencer wrote: >>>>> Hi everybody, >>>>> >>>>> Here's this week's public update. Thanks to all our contributors! >>>>> >>>>> Please note that there is a small problem with the .info file for >>>>> prosody, we'll fix this in another update very soon. >>>>> >>>> [snip] >>>>> system/geoclue2: Updated for version 2.4.10. >>>> >>>> I'm having a build problem with this update (previous version was fine) >>>> in a clean x86_64 14.2 VM: >>>> >>>> checking for GTKDOC_DEPS... yes >>>> checking for GEOCLUE... yes >>>> checking for gobject-introspection... yes >>>> checking for LIBGEOCLUE... yes >>>> checking for ModemManager... no >>>> configure: error: Package requirements (mm-glib >= 1.6) were not met: >>>> >>>> Requested 'mm-glib >= 1.6' but version of mm-glib is 1.4.14 >>>> >>>> I have /var/log/packages/ModemManager-1.4.14-x86_64-1 installed which is >>>> the latest for 14.2 according to the ChangeLog.txt. I see that -current >>>> has ModemManager-1.6.12-x86_64-2.txz so it looks like this particular >>>> geoclue2 update is meant for -current, not -stable. >>>> >>>> Any other ideas? >>>> >>>> chris >>> >>> Which version of glibmm do you have? >>> >>> glibmm-2.46.4 here. >>> >> >> Yes, glibmm-2.46.4-x86_64-1 here too. >> >> However I think the mm-glib reported in the error message refers to when >> the the geoclue2 configuration is checking the >> /usr/lib64/pkgconfig/mm-glib.pc file (part of the ModemManager package). >> >> chris > > Yeah the configure checks that. What do > > pkg-config --print-errors --exists mm-glib > pkg-config --print-errors --exists ModemManager > > output? > Nothing: chris at d7:~$ pkg-config --print-errors --exists mm-glib chris at d7:~$ pkg-config --print-errors --exists ModemManager chris at d7:~$ From artourter at gmail.com Sat May 19 12:06:39 2018 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sat, 19 May 2018 13:06:39 +0100 Subject: [Slackbuilds-users] Updates - 20180519.1 (geoclue2) In-Reply-To: <20180519114712.GI12999@blackswan> References: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> <97577de7-f2dd-f60c-251b-1e14b6e43985@iinet.net.au> <20180519093111.GF12999@blackswan> <01acb8e5-0afd-8b9b-4311-a8346df139dd@iinet.net.au> <20180519114712.GI12999@blackswan> Message-ID: I can reproduce the problem on 14.2 I think the confusion is that mm-glib and glibmm are 2 different things. mm-glib is from modem-manager, whereas glibmm is the C++ API for GLIB (which geoclue2 is not using). One can disable the modem-manager dependency and make it compile fine on 14.2 by add the configure flags: --disable-modem-gps-source --disable-3g-source --disable-cdma-source Hope this helps Greg On 19 May 2018 at 12:47, David Woodfall wrote: > On Saturday 19 May 2018 21:23, > Christoph Willing put forth the proposition: > > On 19/05/18 19:31, David Woodfall wrote: > > > On Saturday 19 May 2018 18:25, > > > Christoph Willing put forth the > proposition: > > >> On 19/05/18 10:33, David Spencer wrote: > > >>> Hi everybody, > > >>> > > >>> Here's this week's public update. Thanks to all our contributors! > > >>> > > >>> Please note that there is a small problem with the .info file for > > >>> prosody, we'll fix this in another update very soon. > > >>> > > >> [snip] > > >>> system/geoclue2: Updated for version 2.4.10. > > >> > > >> I'm having a build problem with this update (previous version was > fine) > > >> in a clean x86_64 14.2 VM: > > >> > > >> checking for GTKDOC_DEPS... yes > > >> checking for GEOCLUE... yes > > >> checking for gobject-introspection... yes > > >> checking for LIBGEOCLUE... yes > > >> checking for ModemManager... no > > >> configure: error: Package requirements (mm-glib >= 1.6) were not met: > > >> > > >> Requested 'mm-glib >= 1.6' but version of mm-glib is 1.4.14 > > >> > > >> I have /var/log/packages/ModemManager-1.4.14-x86_64-1 installed > which is > > >> the latest for 14.2 according to the ChangeLog.txt. I see that > -current > > >> has ModemManager-1.6.12-x86_64-2.txz so it looks like this particular > > >> geoclue2 update is meant for -current, not -stable. > > >> > > >> Any other ideas? > > >> > > >> chris > > > > > > Which version of glibmm do you have? > > > > > > glibmm-2.46.4 here. > > > > > > > Yes, glibmm-2.46.4-x86_64-1 here too. > > > > However I think the mm-glib reported in the error message refers to when > > the the geoclue2 configuration is checking the > > /usr/lib64/pkgconfig/mm-glib.pc file (part of the ModemManager package). > > > > chris > > Yeah the configure checks that. What do > > pkg-config --print-errors --exists mm-glib > pkg-config --print-errors --exists ModemManager > > output? > > -- > > Please don't reply directly to me or CC me. > > > You know you are "there" when you are known by your first name, and > > are recognized. > > Lemmie see, there is Madonna, and Linus, and ..... help me out here! > Bill ? ;-) > -- From some postings on comp.os.linux.misc > > .--. oo > (____)// > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' > _______________________________________________ > 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 idlemoor at slackbuilds.org Sat May 19 12:41:52 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Sat, 19 May 2018 13:41:52 +0100 Subject: [Slackbuilds-users] Updates - 20180519.1 (geoclue2) In-Reply-To: References: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> <97577de7-f2dd-f60c-251b-1e14b6e43985@iinet.net.au> <20180519093111.GF12999@blackswan> <01acb8e5-0afd-8b9b-4311-a8346df139dd@iinet.net.au> <20180519114712.GI12999@blackswan> Message-ID: <62707145-0ae4-9177-0e60-5a8edd7dfa9f@slackbuilds.org> > I can reproduce the problem on 14.2 > > I think the confusion is that mm-glib and glibmm are 2 different things. > mm-glib is from modem-manager, whereas glibmm is the C++ API for GLIB > (which geoclue2 is not using). > > One can disable the modem-manager dependency and make it compile fine on > 14.2 by add the configure flags: > --disable-modem-gps-source --disable-3g-source --disable-cdma-source > > Hope this helps It does, yes, thanks Greg. *However* I think removing modem-manager support would potentially be a regression for some people. I'm going to revert to geoclue2 2.4.7 until Aaditya can look at it. We don't always need the newest version of everything ;) Thanks everybody -D. From lists at osh.id.au Sat May 19 12:59:01 2018 From: lists at osh.id.au (David O'Shaughnessy) Date: Sat, 19 May 2018 22:59:01 +1000 Subject: [Slackbuilds-users] firejail In-Reply-To: References: Message-ID: On 05/19/2018 07:26 AM, Willy Sudiarto Raharjo wrote: > Thanks for reporting > > David, can you take this as well, sorry for troubling you again :( > I don't recall being asked to do anything recently :) But if you are asking me to take over the Firejail SlackBuild I can do that, otherwise all good. Turns out Firefox 60 was a known issue that was fixed with profile updates: https://firejail.wordpress.com/support/#firefox60 -- Dave From idlemoor at slackbuilds.org Sat May 19 13:06:52 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Sat, 19 May 2018 14:06:52 +0100 Subject: [Slackbuilds-users] firejail In-Reply-To: References: Message-ID: <7dd77f62-cd8a-0486-6a40-03b2c9a9d823@slackbuilds.org> On 19/05/18 13:59, David O'Shaughnessy wrote: > On 05/19/2018 07:26 AM, Willy Sudiarto Raharjo wrote: >> Thanks for reporting >> >> David, can you take this as well, sorry for troubling you again :( >> > > I don't recall being asked to do anything recently :) Er, I think Willy meant me :) 26 hours since my previous Multiple Dave Correction :) -D. From khronosschoty at posteo.org Sat May 19 13:21:23 2018 From: khronosschoty at posteo.org (Vasily Sora) Date: Sat, 19 May 2018 06:21:23 -0700 Subject: [Slackbuilds-users] palemoon and basilisk SlackBuilds (Ed Ender) In-Reply-To: References: Message-ID: <20180519132123.GA25750@darkstar.localhost> I'd be glad to take over the SlackBuilds for palemoon and basilisk. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From willysr at slackbuilds.org Sat May 19 13:28:38 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 19 May 2018 20:28:38 +0700 Subject: [Slackbuilds-users] firejail In-Reply-To: <7dd77f62-cd8a-0486-6a40-03b2c9a9d823@slackbuilds.org> References: <7dd77f62-cd8a-0486-6a40-03b2c9a9d823@slackbuilds.org> Message-ID: >>> Thanks for reporting >>> >>> David, can you take this as well, sorry for troubling you again :( >>> >> >> I don't recall being asked to do anything recently :) > > Er, I think Willy meant me :) > 26 hours since my previous Multiple Dave Correction :) Yes, i mean David (idlemoor) Sorry if that confused you :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From lists at osh.id.au Sat May 19 13:31:46 2018 From: lists at osh.id.au (David O'Shaughnessy) Date: Sat, 19 May 2018 23:31:46 +1000 Subject: [Slackbuilds-users] firejail In-Reply-To: References: <7dd77f62-cd8a-0486-6a40-03b2c9a9d823@slackbuilds.org> Message-ID: <0dd4b199-99c3-2306-29c9-d1e1c385b4e0@osh.id.au> On 05/19/2018 11:28 PM, Willy Sudiarto Raharjo wrote: >>>> Thanks for reporting >>>> >>>> David, can you take this as well, sorry for troubling you again :( >>>> >>> >>> I don't recall being asked to do anything recently :) >> >> Er, I think Willy meant me :) >> 26 hours since my previous Multiple Dave Correction :) > > Yes, i mean David (idlemoor) > Sorry if that confused you :) No problem, thought it was a bit odd! :P -- Dave From willysr at slackbuilds.org Sat May 19 13:30:36 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 19 May 2018 20:30:36 +0700 Subject: [Slackbuilds-users] Updates - 20180519.1 (geoclue2) In-Reply-To: <62707145-0ae4-9177-0e60-5a8edd7dfa9f@slackbuilds.org> References: <2b15d7ea-7a7d-dade-2182-a5816bc38fd0@slackbuilds.org> <97577de7-f2dd-f60c-251b-1e14b6e43985@iinet.net.au> <20180519093111.GF12999@blackswan> <01acb8e5-0afd-8b9b-4311-a8346df139dd@iinet.net.au> <20180519114712.GI12999@blackswan> <62707145-0ae4-9177-0e60-5a8edd7dfa9f@slackbuilds.org> Message-ID: >> I can reproduce the problem on 14.2 >> >> I think the confusion is that mm-glib and glibmm are 2 different >> things. mm-glib is from modem-manager, whereas glibmm is the C++ API >> for GLIB (which geoclue2 is not using). >> >> One can disable the modem-manager dependency and make it compile fine >> on 14.2 by add the configure flags: >> --disable-modem-gps-source --disable-3g-source --disable-cdma-source >> >> Hope this helps > > It does, yes, thanks Greg.? *However* I think removing modem-manager > support would potentially be a regression for some people. > > I'm going to revert to geoclue2 2.4.7 until Aaditya can look at it. > We don't always need the newest version of everything ;) Hi all I was the one asking Aaditya to make avahi as optional dep instead of mandatory dep for geoclue2, but i didn't know that he was going to update the script to newer version which only works in -current. David (idlemoor) has fixed the version in his branch and will be merged to master soon. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat May 19 13:37:44 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 19 May 2018 20:37:44 +0700 Subject: [Slackbuilds-users] pudb In-Reply-To: <20180519032430.GC12999@blackswan> References: <20180519032430.GC12999@blackswan> Message-ID: > Mailing here in the hope that the maintainer sees it. > > The sbo version is at least 2 years old. The latest version is > 2017.1.4 > > Support for python3 could be added too. I'm running the py3 version > right now. Sure, go ahead if you want to take over this script. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From skaendo at excite.com Sat May 19 14:48:46 2018 From: skaendo at excite.com (Ed Ender) Date: Sat, 19 May 2018 10:48:46 -0400 Subject: [Slackbuilds-users] palemoon and basilisk SlackBuilds (Ed Ender) Message-ID: <20180519104846.4761@web008.roc2.bluetie.com> Done. They're all yours. Enjoy :) -----Original Message----- From: "Vasily Sora" [khronosschoty at posteo.org] Date: 05/19/2018 08:22 AM To: slackbuilds-users at slackbuilds.org Subject: Re: [Slackbuilds-users] palemoon and basilisk SlackBuilds (Ed Ender) I'd be glad to take over the SlackBuilds for palemoon and basilisk. From dave at dawoodfall.net Sat May 19 15:17:52 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sat, 19 May 2018 16:17:52 +0100 Subject: [Slackbuilds-users] pudb In-Reply-To: References: <20180519032430.GC12999@blackswan> Message-ID: <20180519151752.GL12999@blackswan> On Saturday 19 May 2018 20:37, Willy Sudiarto Raharjo put forth the proposition: > > Mailing here in the hope that the maintainer sees it. > > > > The sbo version is at least 2 years old. The latest version is > > 2017.1.4 > > > > Support for python3 could be added too. I'm running the py3 version > > right now. > > Sure, go ahead if you want to take over this script. > > > -- > Willy Sudiarto Raharjo Ok dokes -- Please don't reply directly to me or CC me. Footnotes are for things you believe don't really belong in LDP manuals, but want to include anyway. -- Joel N. Weber II discussing the 'make' chapter of LPG .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From idlemoor at slackbuilds.org Sat May 19 15:49:32 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Sat, 19 May 2018 16:49:32 +0100 Subject: [Slackbuilds-users] handbrake is downloading dependencies on its own... In-Reply-To: References: Message-ID: <7b8a3c90-8d63-2078-5d18-011b0f55f2b6@slackbuilds.org> On 11/05/18 04:59, Fernando Lopez wrote: > > handbrake is downloading dependencies on its own... I thought it wasn't > allowed. Fixed :D Thanks :D -D. From orbea at fredslev.dk Sat May 19 16:31:18 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Sat, 19 May 2018 09:31:18 -0700 Subject: [Slackbuilds-users] mdocml/mandoc SlackBuild In-Reply-To: Message-ID: <20180519093118.65c3cd33@Akita.witch.org> Its been 2 more weeks without a reply, does anyone know what's up? From willysr at slackbuilds.org Sun May 20 01:46:38 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 20 May 2018 08:46:38 +0700 Subject: [Slackbuilds-users] Updates - 20180520.1 Message-ID: <9c9d218c-74d2-3f5e-0c2b-931e280f0dba@slackbuilds.org> Hi all Here's another public update to fix prosody and geoclue2 issues we found in yesterday's update and also included a bunch of updates in this batch. Sun May 20 01:37:03 UTC 2018 accessibility/xdotool: Update homepage. audio/flake: Updated for version 0.11.5. desktop/keynav: Update homepage. desktop/wmimagedock: Added (changes image inside of dockapp). desktop/xpenguins-xtrathemes: Added (Addon for xpenguins). desktop/xpenguins_themes: Removed (look for xpenguins-xtrathemes). development/apache-maven: Updated for version 3.5.3. development/libretro-samples: Updated for version 2018.04. development/pycharm: Updated for version 2018.1.3. development/sbcl: Updated for version 1.4.7. development/slibtool: Updated for version 0.5.19. games/conquest: Fixed homepage and download. games/larn: Switch homepage to archive.org. games/pcsx2: Fix build. games/pinball: Update README. gis/cartopy: Update homepage. gis/gdal: Updated for version 2.2.4. graphics/feh: Updated for version 2.26.3. graphics/qcad: Update homepage. ham/cwstation: Switch homepage to archive.org. libraries/libsigc++-legacy12: Update homepage. misc/chemical-mime-data: Fix homepage and download. misc/protobuf3: Updated for version 3.5.2. multimedia/HandBrake: Don't download source archives. multimedia/emoc: Switch homepage to archive.org. multimedia/plexmediaserver: Fix reversed MD5SUMs. network/PaleMoon: Updated for version 27.9.2. network/mod_chroot: Switch homepage to archive.org. network/prosody: Fixed .info. network/riot-web: Updated for version 0.15.3. network/signal-desktop: Updated for version 1.11.0. network/urlwatch: Updated for version 2.11. office/MasterPDFEditor: Updated for version 5.0.02. python/python3-django: Added (Web framework). ruby/rubygem-bundler: Update homepage. system/Iosevka: Updated for version 1.14.3. system/dislocker: Fixed manpages. system/fira-fonts: Fix homepage and download. system/geoclue2: Updated for version 2.4.7. system/image-analyzer: Updated for version 3.1.0 + new maintainer. system/letsencrypt: Updated for version 0.24.0. system/ttf-crosscorefonts: Updated for version 20180322. system/worker: Updated for version 3.15.1. system/xonsh: Updated for version 0.6.4. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From aaditya_gnulinux at zoho.com Sun May 20 04:53:50 2018 From: aaditya_gnulinux at zoho.com (Aaditya Bagga) Date: Sun, 20 May 2018 10:23:50 +0530 Subject: [Slackbuilds-users] Updates - 20180519.1 (geoclue2) Message-ID: <723d80b9-c4ab-d35f-a51f-f585e9cb850d@zoho.com> > >>> I can reproduce the problem on 14.2 >>> >>> I think the confusion is that mm-glib and glibmm are 2 different >>> things. mm-glib is from modem-manager, whereas glibmm is the C++ API >>> for GLIB (which geoclue2 is not using). >>> >>> One can disable the modem-manager dependency and make it compile fine >>> on 14.2 by add the configure flags: >>> --disable-modem-gps-source --disable-3g-source --disable-cdma-source >>> >>> Hope this helps >> >> It does, yes, thanks Greg.? *However* I think removing modem-manager >> support would potentially be a regression for some people. >> >> I'm going to revert to geoclue2 2.4.7 until Aaditya can look at it. >> We don't always need the newest version of everything > > Hi all > > I was the one asking Aaditya to make avahi as optional dep instead of > mandatory dep for geoclue2, but i didn't know that he was going to > update the script to newer version which only works in -current. > > David (idlemoor) has fixed the version in his branch and will be merged > to master soon. > > > -- > Willy Sudiarto Raharjo Thanks guys David and Willy for the revert, indeed I am running current and did not check the build on 14.2. Suggestions appreciated on how to simply setup a Slackware 14.2 system within a Slackware current install (docker, vagrant, virtualbox?) Regards, Aaditya From duncan_roe at optusnet.com.au Sun May 20 06:32:43 2018 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sun, 20 May 2018 16:32:43 +1000 Subject: [Slackbuilds-users] Updates - 20180519.1 (geoclue2) In-Reply-To: <723d80b9-c4ab-d35f-a51f-f585e9cb850d@zoho.com> References: <723d80b9-c4ab-d35f-a51f-f585e9cb850d@zoho.com> Message-ID: <20180520063243.GA14169@dimstar.local.net> On Sun, May 20, 2018 at 10:23:50AM +0530, Aaditya Bagga wrote: > > Thanks guys David and Willy for the revert, indeed I am running current and > did not check the build on 14.2. > > Suggestions appreciated on how to simply setup a Slackware 14.2 system > within a Slackware current install (docker, vagrant, virtualbox?) > > Regards, > Aaditya > I create a new VM in virt-manager and point its DVD to the appropriate ISO (32 or 64). Then do a Slackware install. I give them 10GB storage, don't install kernel source and nfs-mount almost everything from the desktop. Just a suggestion, Cheers ... Duncan. From chris.willing at iinet.net.au Sun May 20 07:45:46 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 20 May 2018 17:45:46 +1000 Subject: [Slackbuilds-users] Updates - 20180520.1 (gdal) In-Reply-To: <9c9d218c-74d2-3f5e-0c2b-931e280f0dba@slackbuilds.org> References: <9c9d218c-74d2-3f5e-0c2b-931e280f0dba@slackbuilds.org> Message-ID: <87b87008-fb45-26ea-ea87-ab914ffd55cb@iinet.net.au> On 20/05/18 11:46, Willy Sudiarto Raharjo wrote: > Hi all > > Here's another public update to fix prosody and geoclue2 issues we found > in yesterday's update and also included a bunch of updates in this batch. > > > Sun May 20 01:37:03 UTC 2018 [snip] > gis/gdal: Updated for version 2.2.4. I was wondering why this was being downgraded from 2.3.0 so soon after its recent upgrade; then saw in git log that it was due to recent breakage of "lots of dependent packages that don't use c++11". In fact I had noticed this when rebuilding OpenSceneGraph (which optionally requires gdal) and had already suggested to the maintainer a fairly simple change to the OSG SlackBuild which fixed the problem for OSG with gdal-2.3.0. I had three other SlackBuilds which depend on gdal and their rebuilds were all unaffected by the c++11 issue. I see there are quite a few SlackBuilds which depend on gdal, however might it be possible for them to be changed (like OSG) so that gdal isn't stuck at 2.2.4? All that needed to be done in the OSG case was to add "-std=c++11" to the compiler environment. In OSG's case, using cmake: -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS -std=c++11" \ -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS -std=c++11" \ It may not be so simple for all affected SlackBuilds but worth a try? chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From idlemoor at slackbuilds.org Sun May 20 08:38:35 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Sun, 20 May 2018 09:38:35 +0100 Subject: [Slackbuilds-users] Updates - 20180520.1 (gdal) In-Reply-To: <87b87008-fb45-26ea-ea87-ab914ffd55cb@iinet.net.au> References: <9c9d218c-74d2-3f5e-0c2b-931e280f0dba@slackbuilds.org> <87b87008-fb45-26ea-ea87-ab914ffd55cb@iinet.net.au> Message-ID: Hi Chris, hi everybody -- On 20/05/18 08:45, Christoph Willing wrote: >> gis/gdal: Updated for version 2.2.4. > > I was wondering why this was being downgraded from 2.3.0 so soon after > its recent upgrade; then saw in git log that it was due to recent > breakage of "lots of dependent packages that don't use c++11". Yes, sorry everybody -- due to me being stupid and looking in the wrong VM, I didn't see all the breakage that 2.3.0 had caused until yesterday. So I pushed a quick revert before Willy did yesterday's public update :) > In fact I had noticed this when rebuilding OpenSceneGraph (which > optionally requires gdal) and had already suggested to the maintainer a > fairly simple change to the OSG SlackBuild which fixed the problem for > OSG with gdal-2.3.0. I had three other SlackBuilds which depend on gdal > and their rebuilds were all unaffected by the c++11 issue. > > I see there are quite a few SlackBuilds which depend on gdal, however > might it be possible for them to be changed (like OSG) so that gdal > isn't stuck at 2.2.4? All that needed to be done in the OSG case was to > add "-std=c++11" to the compiler environment. In OSG's case, using cmake: > -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS -std=c++11" \ > -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS -std=c++11" \ > > It may not be so simple for all affected SlackBuilds but worth a try? Thanks for bringing a solution instead of a problem :) The first fail on my list (libLAS) explicity sets gnu89. libLAS seems to be dying or dead upstream, so I gave up. We might need to make some difficult decisions, depending on which packages are unfixable. I'll try to do some more this week (more carefully!) Thanks again -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From idlemoor at slackbuilds.org Sun May 20 08:57:09 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Sun, 20 May 2018 09:57:09 +0100 Subject: [Slackbuilds-users] Updates - 20180520.1 (gdal) In-Reply-To: References: <9c9d218c-74d2-3f5e-0c2b-931e280f0dba@slackbuilds.org> <87b87008-fb45-26ea-ea87-ab914ffd55cb@iinet.net.au> Message-ID: <0affc202-c2f4-d46c-7843-367d5770a26d@slackbuilds.org> > The first fail on my list (libLAS) explicity sets gnu89. libLAS seems to > be dying or dead upstream, so I gave up. Ok, that's really unfair, sorry. There are fixes in their git master. It would be nice to see something about laszip and an actual release :) Cheers -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun May 20 12:50:31 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 20 May 2018 19:50:31 +0700 Subject: [Slackbuilds-users] addition for faq or howto In-Reply-To: References: Message-ID: <84b924b2-cb49-c9b8-51ea-a9813bb70d90@slackbuilds.org> > Would it hurt to add some text to the HOWTO page explaining this? I > know it's pretty elementary stuff, but the HOWTO already details how to > extract a tarball and launch a shell script from the current directory, > which are also elementary tasks... > > Proposed text to add to the end of "Step 2 - Read the README": > > ---cut-here--- > If the README mentions any options controlled by environment variables, > you can set these options now by running: > > export VARIABLE=value > > For instance, if the README says you can build against SDL 2.0 by setting > SDL2=yes in the environment, you would type: > > export SDL2=yes > > If there are multiple options, you can use multiple export commands. > > If you're unsure, don't set any variables here. In most cases, the > SlackBuild maintainer has made the default behaviour (no options) the > most common or most useful way to build the package. > ---cut-here--- > > ...yes, it's possible (and "cleaner") to just say SDL2=yes > ./whatever.SlackBuild in Step 4, but the way the howto is split up > into steps, it would make less sense for step 4 to effectively say "Oh, > by the way, you should have noticed if there were environment variable > options in step 2". So Step 2 has to mention them, since that's where > they're visible. IMO, it would be best to put the steps in step 4 since it's how you run the script that matters. In step 2 we can tell that maintainers can put variable-controlled options. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kjhambrick at gmail.com Sun May 20 16:47:57 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sun, 20 May 2018 11:47:57 -0500 Subject: [Slackbuilds-users] postgis and CGAL 4.12 Message-ID: All -- Slackware64 14.2 + Multilib system here... I was holding back until I could figure it out for myself but due to the gdal reversion I thought maybe I should let fly with my email anyway. Anyhow I was unable to rebuild postgis with the newest gdal-2.2.4 and CGAL-4.12 ( and a rebuilt SFCGAL-1.3.5 ). I consistently ran into a boost issue when compiling postgis-2.4.4: make[2]: Entering directory '/tmp/SBo/postgis-2.4.4/raster/loader' gcc -O2 -fPIC -fPIC -DPIC -Wall -Wmissing-prototypes -I../rt_core -I../../liblwgeom -I/usr/include -I/usr/include -c raster2pgsql.c /bin/sh ../../libtool --mode=link gcc -O2 -fPIC -fPIC -DPIC -Wall -Wmissing-prototypes -I../rt_core -I../../liblwgeom -I/usr/include -I/usr/include ../rt_core/librtcore.a raster2pgsql.o ../../liblwgeom/ liblwgeom.la -L/usr/lib64 -lgdal -L/usr/lib64 -lgeos_c -lc -lm -o raster2pgsql libtool: link: gcc -O2 -fPIC -fPIC -DPIC -Wall -Wmissing-prototypes -I../rt_core -I../../liblwgeom -I/usr/include -I/usr/include raster2pgsql.o -o .libs/raster2pgsql ../rt_core/librtcore.a ../../liblwgeom/.libs/liblwgeom.so -L/usr/lib64 /usr/lib64/libgdal.so /usr/lib64/libgeos_c.so -lc -lm -pthread /usr/lib64/libSFCGAL.so.1: undefined reference to `typeinfo for boost::archive::detail::basic_oserializer' I reverted to CGAL-4.11.1 and rebuilt SFCGAL-1.3.5 and postgis-2.4.4 builds fine and `cd /tmp/SBo/postgis-2.4.4 ; make check` passes all tests. Looking at the CGAL-4.12 README there is a note about boost: ### Compiler Support - The Microsoft Visual C++ 2017 version 15.3 has introduced support for C++17, with the compilation flag `/std:c++17`. CGAL 4.12 has an initial support for that flag: the code will compile, but a lot of deprecation warnings will remain. Note that Boost version 1.67 is the first version of Boost supporting `/std:c++17`. I've got several compiler logs based on various versions of Hard and Soft ( Optional ) Dependencies for postgis-2.2.4 if that would help. I the meantime, postgis does work with everything updated EXCEPT CGAL-4.12 ... Any ideas ? Thanks. -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: From aaditya_gnulinux at zoho.com Sun May 20 18:36:18 2018 From: aaditya_gnulinux at zoho.com (Aaditya Bagga) Date: Mon, 21 May 2018 00:06:18 +0530 Subject: [Slackbuilds-users] Updates - 20180519.1 (geoclue2) Message-ID: > > On Sun, May 20, 2018 at 10:23:50AM +0530, Aaditya Bagga wrote: > > > > Thanks guys David and Willy for the revert, indeed I am running current and > > did not check the build on 14.2. > > > > Suggestions appreciated on how to simply setup a Slackware 14.2 system > > within a Slackware current install (docker, vagrant, virtualbox?) > > > > Regards, > > Aaditya > > > I create a new VM in virt-manager and point its DVD to the appropriate ISO (32 > or 64). Then do a Slackware install. I give them 10GB storage, don't install > kernel source and nfs-mount almost everything from the desktop. Just a suggestion, > > Cheers ... Duncan. Thanks, I went with a similar option, using vagrant to download and setup a Slackware 14.2 image (https://app.vagrantup.com/talosthoren/boxes/slackware64-14.2) with provider Virtualbox as it was already installed. Regards, Aaditya From ole.andre.rodlie at gmail.com Mon May 21 00:43:02 2018 From: ole.andre.rodlie at gmail.com (Ole Andre Rodlie) Date: Mon, 21 May 2018 02:43:02 +0200 Subject: [Slackbuilds-users] Update/Maintenance of system/qtfm Message-ID: Hi, I'm currently the new maintainer/developer of QtFM ( https://github.com/rodlie/qtfm). I found QtFM in SBo and was wondering if you are interested in syncing with the new upstream. I didn't contact the maintainer since the last update was 5 years ago and that person is probably not connected with SBo anymore(?). So, should I contact the maintainer or just submit a new SlackBuild to SBo? What are the "rules" for unmaintained/stale packages (and new upstream)? Regards Ole-Andr? -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon May 21 01:20:35 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 21 May 2018 08:20:35 +0700 Subject: [Slackbuilds-users] Update/Maintenance of system/qtfm In-Reply-To: References: Message-ID: <8ec146e5-9a0d-340c-973a-f4c742b6b822@slackbuilds.org> > I'm currently the new maintainer/developer of QtFM > (https://github.com/rodlie/qtfm). > > I found QtFM in SBo and was wondering if you are interested in syncing > with the new upstream. > > I didn't contact the maintainer since the last update was 5 years ago > and that person is probably not connected with SBo anymore(?). > > So, should I contact the maintainer or just submit a new SlackBuild to > SBo? What are the "rules" for unmaintained/stale packages (and new > upstream)? Hi Ole You can try to contact the maintainer first and if he is not responding for some time (give 1-2 weeks), you can take over the script and sync with upstream. That should give you enough time to finalize 6.0 release as well :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From ole.andre.rodlie at gmail.com Mon May 21 01:29:55 2018 From: ole.andre.rodlie at gmail.com (Ole Andre Rodlie) Date: Mon, 21 May 2018 03:29:55 +0200 Subject: [Slackbuilds-users] Update/Maintenance of system/qtfm In-Reply-To: <8ec146e5-9a0d-340c-973a-f4c742b6b822@slackbuilds.org> References: <8ec146e5-9a0d-340c-973a-f4c742b6b822@slackbuilds.org> Message-ID: Thanks for the information. I will contact the maintainer and prepare a reference SlackBuild for 6.0.0. Ole-Andr? On Mon, May 21, 2018 at 3:20 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > I'm currently the new maintainer/developer of QtFM > > (https://github.com/rodlie/qtfm). > > > > I found QtFM in SBo and was wondering if you are interested in syncing > > with the new upstream. > > > > I didn't contact the maintainer since the last update was 5 years ago > > and that person is probably not connected with SBo anymore(?). > > > > So, should I contact the maintainer or just submit a new SlackBuild to > > SBo? What are the "rules" for unmaintained/stale packages (and new > > upstream)? > > Hi Ole > > You can try to contact the maintainer first and if he is not responding > for some time (give 1-2 weeks), you can take over the script and sync > with upstream. > > That should give you enough time to finalize 6.0 release as well :) > > > -- > 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 ml at mareichelt.com Mon May 21 12:32:40 2018 From: ml at mareichelt.com (Markus Reichelt) Date: Mon, 21 May 2018 14:32:40 +0200 Subject: [Slackbuilds-users] python/mock up for grabs Message-ID: <20180521123240.GA2405@pc21.mareichelt.com> long story short: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2018-February/020850.html From matteo.bernardini at gmail.com Mon May 21 13:33:45 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 21 May 2018 15:33:45 +0200 Subject: [Slackbuilds-users] mdocml/mandoc SlackBuild In-Reply-To: <20180519093118.65c3cd33@Akita.witch.org> References: <20180519093118.65c3cd33@Akita.witch.org> Message-ID: 2018-05-19 18:31 GMT+02:00 orbea at fredslev.dk : > Its been 2 more weeks without a reply, does anyone know what's up? could you please send him the email again putting this list in cc (in the same email)? From ekinakoglu at gmail.com Mon May 21 13:47:18 2018 From: ekinakoglu at gmail.com (Ekin Akoglu) Date: Mon, 21 May 2018 16:47:18 +0300 Subject: [Slackbuilds-users] Liferea 1.12.3 Message-ID: <2e270fc7-9f4c-f065-7442-2561fbd6896b@gmail.com> Hi, For the new version of Liferea, I think "pygobject3-python3" should be listed as "required" because it seems that it is necessary for loading plugins. For instance, without it I could not enable the "tray icon" plugin of Liferea. Best regards, Ekin From atelszewski at gmail.com Mon May 21 16:59:35 2018 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 21 May 2018 18:59:35 +0200 Subject: [Slackbuilds-users] Liferea 1.12.3 In-Reply-To: <2e270fc7-9f4c-f065-7442-2561fbd6896b@gmail.com> References: <2e270fc7-9f4c-f065-7442-2561fbd6896b@gmail.com> Message-ID: On 21/05/18 15:47, Ekin Akoglu wrote: > Hi, > > For the new version of Liferea, I think "pygobject3-python3" should be > listed as "required" because it seems that it is necessary for loading > plugins. For instance, without it I could not enable the "tray icon" > plugin of Liferea. > > Best regards, > > Ekin > > I'll take a look ASAP. -- Best regards / Pozdrawiam, Andrzej Telszewski From orbea at fredslev.dk Mon May 21 16:48:59 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Mon, 21 May 2018 09:48:59 -0700 Subject: [Slackbuilds-users] mdocml/mandoc SlackBuild In-Reply-To: Message-ID: <20180521094859.6cef5ee0@Akita.witch.org> Below is the original message sent regarding mdocml/mandoc, if you could please reply it would be very much appreciated. Also note I put your address in the cc for the related messages to the SBo users mailing list so you should of received those too? ==================== Hi, I'm not sure if you noticed, but mdocml has now been renamed mandoc upstream and 1.14.3 is now out. Would you be willing to update the build script? If this is done you should no longer ship /etc/mandoc.conf as this is no longer installed upstream or in FreeBSD and mandoc works fine without it. Also you can avoid the sed to fix symlinks by adding LN="ln -sf" to configure.local. Alternatively I am fully willing to take over the SlackBuild if you are no longer interested. Thanks, Hunter From yalhcru at gmail.com Tue May 22 03:27:37 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 21 May 2018 23:27:37 -0400 Subject: [Slackbuilds-users] Download URLs gone MIA Message-ID: Downloads for multimedia/makemkv are 404. Found copies with matching md5sums here: http://ftp.osuosl.org/pub/gentoo/distfiles/makemkv-oss-1.12.0.tar.gz http://ftp.osuosl.org/pub/gentoo/distfiles/makemkv-bin-1.12.0.tar.gz Also office/gnucash3 is missing, found a matching copy here: http://ftp.netbsd.org/pub/pkgsrc/distfiles/gnucash-3.1.tar.bz2 From t3slider at gmail.com Tue May 22 03:32:38 2018 From: t3slider at gmail.com (T3 slider) Date: Mon, 21 May 2018 23:32:38 -0400 Subject: [Slackbuilds-users] Download URLs gone MIA In-Reply-To: References: Message-ID: The "official" links to old versions for MakeMKV are here: https://makemkv.com/download/old/ However, I'll see if I can upgrade this tomorrow (it's currently one minor version behind). -T3slider On Mon, May 21, 2018, 11:27 PM B Watson wrote: > Downloads for multimedia/makemkv are 404. Found copies with matching > md5sums here: > > http://ftp.osuosl.org/pub/gentoo/distfiles/makemkv-oss-1.12.0.tar.gz > http://ftp.osuosl.org/pub/gentoo/distfiles/makemkv-bin-1.12.0.tar.gz > > Also office/gnucash3 is missing, found a matching copy here: > > http://ftp.netbsd.org/pub/pkgsrc/distfiles/gnucash-3.1.tar.bz2 > _______________________________________________ > 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 yalhcru at gmail.com Tue May 22 04:58:30 2018 From: yalhcru at gmail.com (B Watson) Date: Tue, 22 May 2018 00:58:30 -0400 Subject: [Slackbuilds-users] mismatched md5sums Message-ID: These builds have mismatched md5sums: business/stansoft desktop/oomox network/lizardfs network/riot-web (32-bit download only, 64-bit is OK) This one does too: games/open-adventure ...but it's my build, so only I have to worry about it. From yalhcru at gmail.com Tue May 22 06:23:44 2018 From: yalhcru at gmail.com (B Watson) Date: Tue, 22 May 2018 02:23:44 -0400 Subject: [Slackbuilds-users] git-fame download URL Message-ID: The .info file for python/git-fame has: DOWNLOAD="https://pypi.python.org/packages/8b/0f/dfb31752f4df3e0d5561efff4b7965614f1e47fe64ee65cf98e6e80e09cb/git-fame-1.4.2.tar.gz#md5=jbj" The #md5=jbj stuff at the end is causing problems for sbosrcarch, and possibly some other automated tools... and seems to be completely unnecessary. File downloads fine without it, md5sum matches. So I propose changing the .info file: DOWNLOAD="https://pypi.python.org/packages/8b/0f/dfb31752f4df3e0d5561efff4b7965614f1e47fe64ee65cf98e6e80e09cb/git-fame-1.4.2.tar.gz" Sound OK to you? From atelszewski at gmail.com Tue May 22 17:28:48 2018 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 22 May 2018 19:28:48 +0200 Subject: [Slackbuilds-users] Liferea 1.12.3 In-Reply-To: <2e270fc7-9f4c-f065-7442-2561fbd6896b@gmail.com> References: <2e270fc7-9f4c-f065-7442-2561fbd6896b@gmail.com> Message-ID: <432e05b3-df7d-feb2-e499-f434f587653f@gmail.com> On 21/05/18 15:47, Ekin Akoglu wrote: > Hi, > > For the new version of Liferea, I think "pygobject3-python3" should be > listed as "required" because it seems that it is necessary for loading > plugins. For instance, without it I could not enable the "tray icon" > plugin of Liferea. > > Best regards, > > Ekin > > Ekin, thanks for the report. You are correct. Admins, please add "pygobject3-python3" to the REQUIRES= for liferea. Thanks! -- Best regards / Pozdrawiam, Andrzej Telszewski From fernando.lopezjr at gmail.com Tue May 22 18:55:42 2018 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 22 May 2018 12:55:42 -0600 Subject: [Slackbuilds-users] radare2 1.6.0 compile error. Message-ID: would anyone know why is not compiling? =\ https://pastebin.ca/4031449 -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Tue May 22 19:13:32 2018 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 22 May 2018 13:13:32 -0600 Subject: [Slackbuilds-users] radare2 1.6.0 compile error. In-Reply-To: References: Message-ID: i wasnt catching any errors on previous paste. *https://pastebin.ca/4031451 * On Tue, May 22, 2018 at 12:55 PM, Fernando Lopez wrote: > would anyone know why is not compiling? =\ > > https://pastebin.ca/4031449 > > > -- > > ------------ > Regards, > Fernando Lopez Jr. > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Tue May 22 19:24:31 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 22 May 2018 21:24:31 +0200 Subject: [Slackbuilds-users] radare2 1.6.0 compile error. In-Reply-To: References: Message-ID: 2018-05-22 21:13 GMT+02:00 Fernando Lopez : > i wasnt catching any errors on previous paste. > > https://pastebin.ca/4031451 > > On Tue, May 22, 2018 at 12:55 PM, Fernando Lopez > wrote: >> >> would anyone know why is not compiling? =\ >> >> https://pastebin.ca/4031449 looks like there's an open issue upstream https://github.com/radare/radare2/issues/10159 From aclemons at runbox.no Tue May 22 19:47:28 2018 From: aclemons at runbox.no (Andrew Clemons) Date: Wed, 23 May 2018 07:47:28 +1200 Subject: [Slackbuilds-users] git-fame download URL In-Reply-To: References: Message-ID: <20180522194727.GA6186@runbox.no> On 2018-05-22 02:23:44 -0400, yalhcru at gmail.com wrote: > [...] > So I propose changing the .info file: > > DOWNLOAD="https://pypi.python.org/packages/8b/0f/dfb31752f4df3e0d5561efff4b7965614f1e47fe64ee65cf98e6e80e09cb/git-fame-1.4.2.tar.gz" > > Sound OK to you? Yes, I?ve updated it on my branch. Thanks for the notice. Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From willysr at slackbuilds.org Tue May 22 23:59:48 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 23 May 2018 06:59:48 +0700 Subject: [Slackbuilds-users] Liferea 1.12.3 In-Reply-To: <432e05b3-df7d-feb2-e499-f434f587653f@gmail.com> References: <2e270fc7-9f4c-f065-7442-2561fbd6896b@gmail.com> <432e05b3-df7d-feb2-e499-f434f587653f@gmail.com> Message-ID: <6d23fd72-ec9a-e610-4be1-756f3df9d8c7@slackbuilds.org> >> For the new version of Liferea, I think "pygobject3-python3" should be >> listed as "required" because it seems that it is necessary for loading >> plugins. For instance, without it I could not enable the "tray icon" >> plugin of Liferea. >> >> Best regards, >> >> Ekin >> >> > > Ekin, thanks for the report. > You are correct. > > Admins, please add "pygobject3-python3" to the REQUIRES= for liferea. Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed May 23 00:44:56 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 23 May 2018 07:44:56 +0700 Subject: [Slackbuilds-users] mismatched md5sums In-Reply-To: References: Message-ID: <528789c2-cf8f-8495-c3ad-ddd98c1d3956@slackbuilds.org> > These builds have mismatched md5sums: > > business/stansoft > desktop/oomox > network/lizardfs > network/riot-web (32-bit download only, 64-bit is OK) Thanks i have fixed them on my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed May 23 00:49:20 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 23 May 2018 07:49:20 +0700 Subject: [Slackbuilds-users] postgis and CGAL 4.12 In-Reply-To: References: Message-ID: > I was holding back until I could figure it out for myself but due to the > gdal reversion I thought maybe I should let fly with my email anyway. > > Anyhow I was unable to rebuild postgis with the newest gdal-2.2.4 and > CGAL-4.12 ( and a rebuilt SFCGAL-1.3.5 ). > > I consistently ran into a boost issue when compiling postgis-2.4.4: > > make[2]: Entering directory '/tmp/SBo/postgis-2.4.4/raster/loader' > gcc -O2 -fPIC? -fPIC -DPIC? -Wall -Wmissing-prototypes -I../rt_core > -I../../liblwgeom? -I/usr/include -I/usr/include?? -c raster2pgsql.c > /bin/sh ../../libtool --mode=link gcc -O2 -fPIC? -fPIC -DPIC? -Wall > -Wmissing-prototypes -I../rt_core -I../../liblwgeom? -I/usr/include > -I/usr/include?? ../rt_core/librtcore.a raster2pgsql.o > ../../liblwgeom/liblwgeom.la -L/usr/lib64 -lgdal? > -L/usr/lib64 -lgeos_c? -lc -lm -o raster2pgsql > libtool: link: gcc -O2 -fPIC -fPIC -DPIC -Wall -Wmissing-prototypes > -I../rt_core -I../../liblwgeom -I/usr/include -I/usr/include > raster2pgsql.o -o .libs/raster2pgsql? ../rt_core/librtcore.a > ../../liblwgeom/.libs/liblwgeom.so -L/usr/lib64 /usr/lib64/libgdal.so > /usr/lib64/libgeos_c.so -lc -lm -pthread > /usr/lib64/libSFCGAL.so.1: undefined reference to `typeinfo for > boost::archive::detail::basic_oserializer' > > I reverted to CGAL-4.11.1 and rebuilt SFCGAL-1.3.5 and postgis-2.4.4 > builds fine and `cd /tmp/SBo/postgis-2.4.4 ; make check` passes all tests. > > Looking at the CGAL-4.12 README there is a note about boost: > > ### Compiler Support > > -?? The Microsoft Visual C++ 2017 version 15.3 has introduced support for > ??? C++17, with the compilation flag `/std:c++17`. CGAL 4.12 has an initial > ??? support for that flag: the code will compile, but a lot of deprecation > ??? warnings will remain. Note that Boost version 1.67 is the first version > ??? of Boost supporting `/std:c++17`. > > I've got several compiler logs based on various versions of Hard and > Soft ( Optional ) Dependencies for postgis-2.2.4 if that would help. > > I the meantime, postgis does work with everything updated EXCEPT > CGAL-4.12 ... I don't know if this is the case, but can you look on this commit by Ben? https://git.slackbuilds.org/slackbuilds/commit/?h=user/bosth/updates&id=455dfab3b137404582a2b2f8b18bf16b80a686bb -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed May 23 00:56:35 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 23 May 2018 07:56:35 +0700 Subject: [Slackbuilds-users] Could we have --with-lucene option in dovecot.SlackBuild please In-Reply-To: <4bc125d2-f651-227d-08a8-4da8dbafbbb7@open-t.co.uk> References: <4bc125d2-f651-227d-08a8-4da8dbafbbb7@open-t.co.uk> Message-ID: <430af745-fe7d-2c8f-a213-d068c19a3681@slackbuilds.org> > Since Slackware already contains the CLucene library, and Lucene is one > of the recommended full text search indexers in Dovecot, could the SBo > build have --with-lucene added to it - so that it doesn't need > recompiling to use FTS? Sorry, this message was burried into tons of other messages. Have you asked Mario about this? he is an active maintainer, so just drop an email to him or chat with him in IRC. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From orbea at fredslev.dk Wed May 23 00:03:25 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Tue, 22 May 2018 17:03:25 -0700 Subject: [Slackbuilds-users] qt5 + pulseaudio In-Reply-To: Message-ID: <20180522170325.68531955@Akita.witch.org> Sorry for the slow reply. I lost interest in pushing this when it became clear that merging a simple patch required more energy than I had to expend... Take it or leave it, I'm not interested in fighting over this. Previous e-mails were written a while ago and with a previous e-mail address. From slackbuilds at jaxartes.net Wed May 23 02:09:05 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Tue, 22 May 2018 19:09:05 -0700 Subject: [Slackbuilds-users] postgis and CGAL 4.12 In-Reply-To: References: Message-ID: <2571701.8GOG19e1Es@wintermute.sprawl.net> On Sunday, 20 May 2018 09:47:57 PDT Konrad J Hambrick wrote: > I the meantime, postgis does work with everything updated EXCEPT CGAL-4.12 > ... > > Any ideas ? So far I've been able to confirm everything you said: PostGIS won't compile with CGAL 4.12 and SFCGAL. David and I were coordinating on upgrading CGAL from 4.9 and the 4.11 upgrade was fine but I missed how it broke PostGIS with the more recent 4.12. I suppose it's because it's only an optional dependency for PostGIS ... There are a few ways of fixing the issue: remove SFCAL; add --without-sfcgal to PostGIS's configure; or downgrade CGAL to 4.11. The choice likely depends on whether you need the additional PostGIS functions provided by SFCAL and whether you need SFCGAL on your system for something else! Ben From leva at ecentrum.hu Wed May 23 08:22:13 2018 From: leva at ecentrum.hu (=?iso-8859-1?Q?L=C9VAI_D=E1niel?=) Date: Wed, 23 May 2018 10:22:13 +0200 Subject: [Slackbuilds-users] mdocml/mandoc SlackBuild In-Reply-To: <20180521094859.6cef5ee0@Akita.witch.org> References: <20180521094859.6cef5ee0@Akita.witch.org> Message-ID: <20180523082213.GB2508@serenity.localdomain> orbea at fredslev.dk @ 2018-05-21T18:48:59 +0200: > Below is the original message sent regarding mdocml/mandoc, if you > could please reply it would be very much appreciated. Also note I [...] Cheers guys, I've had this on my todo list for a while now. Daniel -- L?VAI D?niel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F From s.arcus at open-t.co.uk Wed May 23 14:41:52 2018 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 23 May 2018 15:41:52 +0100 Subject: [Slackbuilds-users] Could we have --with-lucene option in dovecot.SlackBuild please In-Reply-To: <430af745-fe7d-2c8f-a213-d068c19a3681@slackbuilds.org> References: <4bc125d2-f651-227d-08a8-4da8dbafbbb7@open-t.co.uk> <430af745-fe7d-2c8f-a213-d068c19a3681@slackbuilds.org> Message-ID: On 23/05/18 01:56, Willy Sudiarto Raharjo wrote: >> Since Slackware already contains the CLucene library, and Lucene is one >> of the recommended full text search indexers in Dovecot, could the SBo >> build have --with-lucene added to it - so that it doesn't need >> recompiling to use FTS? > > Sorry, this message was burried into tons of other messages. > > Have you asked Mario about this? > he is an active maintainer, so just drop an email to him or chat with > him in IRC. Thank you for the suggestion - I just dropped him an email. From n0nb at n0nb.us Thu May 24 12:09:18 2018 From: n0nb at n0nb.us (Nate Bargmann) Date: Thu, 24 May 2018 07:09:18 -0500 Subject: [Slackbuilds-users] graphviz build failure Message-ID: <20180524120918.ugfaer2lbg6etk7a@n0nb.us> I'm not sure what kind of a conflict or lack of specified dependency on Java exists with this package: make install-data-hook make[7]: Entering directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' (cd /tmp/SBo/package-graphviz/usr/lib64/graphviz/java/org/graphviz; ln -s -f org/graphviz/libgv_java.so ../../libgv.so; javac -classpath /tmp/SBo/package-graphviz/usr/lib64/graphviz/java gv.java;) /bin/sh: javac: command not found make[7]: *** [install-data-hook] Error 127 Makefile:3723: recipe for target 'install-data-hook' failed make[7]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' make[6]: *** [install-data-am] Error 2 Makefile:3428: recipe for target 'install-data-am' failed make[6]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' make[5]: *** [install-am] Error 2 Makefile:3350: recipe for target 'install-am' failed make[5]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' make[4]: *** [install-recursive] Error 1 Makefile:3187: recipe for target 'install-recursive' failed make[4]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' make[3]: *** [install-recursive] Error 1 Makefile:648: recipe for target 'install-recursive' failed make[3]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg' Makefile:822: recipe for target 'install-recursive' failed make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory '/tmp/SBo/graphviz-2.40.1' make[1]: *** [install] Error 2 Makefile:1115: recipe for target 'install' failed make[1]: Leaving directory '/tmp/SBo/graphviz-2.40.1' make: *** [install-strip] Error 2 Makefile:1125: recipe for target 'install-strip' failed Failure encountered while building graphviz: graphviz.SlackBuild return non-zero Thanks. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: http://www.n0nb.us GPG key: D55A8819 GitHub: N0NB -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From abraxandor at googlemail.com Thu May 24 12:20:19 2018 From: abraxandor at googlemail.com (Sebastian Aloisi) Date: Thu, 24 May 2018 14:20:19 +0200 Subject: [Slackbuilds-users] graphviz build failure In-Reply-To: <20180524120918.ugfaer2lbg6etk7a@n0nb.us> References: <20180524120918.ugfaer2lbg6etk7a@n0nb.us> Message-ID: <94B2B092-88EB-4E3B-A5A3-29E0F3D6F775@googlemail.com> I had a similar problem, Setting the JAVAHOME variable fixed it for me. Am 24. Mai 2018 14:09:18 MESZ schrieb Nate Bargmann : >I'm not sure what kind of a conflict or lack of specified dependency on >Java exists with this package: > >make install-data-hook >make[7]: Entering directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' >(cd /tmp/SBo/package-graphviz/usr/lib64/graphviz/java/org/graphviz; ln >-s -f org/graphviz/libgv_java.so ../../libgv.so; javac -classpath >/tmp/SBo/package-graphviz/usr/lib64/graphviz/java gv.java;) >/bin/sh: javac: command not found >make[7]: *** [install-data-hook] Error 127 >Makefile:3723: recipe for target 'install-data-hook' failed >make[7]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' >make[6]: *** [install-data-am] Error 2 >Makefile:3428: recipe for target 'install-data-am' failed >make[6]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' >make[5]: *** [install-am] Error 2 >Makefile:3350: recipe for target 'install-am' failed >make[5]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' >make[4]: *** [install-recursive] Error 1 >Makefile:3187: recipe for target 'install-recursive' failed >make[4]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' >make[3]: *** [install-recursive] Error 1 >Makefile:648: recipe for target 'install-recursive' failed >make[3]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg' >Makefile:822: recipe for target 'install-recursive' failed >make[2]: *** [install-recursive] Error 1 >make[2]: Leaving directory '/tmp/SBo/graphviz-2.40.1' >make[1]: *** [install] Error 2 >Makefile:1115: recipe for target 'install' failed >make[1]: Leaving directory '/tmp/SBo/graphviz-2.40.1' >make: *** [install-strip] Error 2 >Makefile:1125: recipe for target 'install-strip' failed >Failure encountered while building graphviz: > graphviz.SlackBuild return non-zero > > >Thanks. > >- Nate > >-- > >"The optimist proclaims that we live in the best of all >possible worlds. The pessimist fears this is true." > >Web: http://www.n0nb.us GPG key: D55A8819 GitHub: N0NB -- Diese Nachricht wurde von meinem Android-Ger?t mit K-9 Mail gesendet. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Thu May 24 12:22:18 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 24 May 2018 14:22:18 +0200 Subject: [Slackbuilds-users] graphviz build failure In-Reply-To: <20180524120918.ugfaer2lbg6etk7a@n0nb.us> References: <20180524120918.ugfaer2lbg6etk7a@n0nb.us> Message-ID: 2018-05-24 14:09 GMT+02:00 Nate Bargmann : > I'm not sure what kind of a conflict or lack of specified dependency on > Java exists with this package: > > make install-data-hook > make[7]: Entering directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' > (cd /tmp/SBo/package-graphviz/usr/lib64/graphviz/java/org/graphviz; ln -s -f org/graphviz/libgv_java.so ../../libgv.so; javac -classpath /tmp/SBo/package-graphviz/usr/lib64/graphviz/java gv.java;) > /bin/sh: javac: command not found > make[7]: *** [install-data-hook] Error 127 > Makefile:3723: recipe for target 'install-data-hook' failed > make[7]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' > make[6]: *** [install-data-am] Error 2 > Makefile:3428: recipe for target 'install-data-am' failed > make[6]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' > make[5]: *** [install-am] Error 2 > Makefile:3350: recipe for target 'install-am' failed > make[5]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' > make[4]: *** [install-recursive] Error 1 > Makefile:3187: recipe for target 'install-recursive' failed > make[4]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg/gv' > make[3]: *** [install-recursive] Error 1 > Makefile:648: recipe for target 'install-recursive' failed > make[3]: Leaving directory '/tmp/SBo/graphviz-2.40.1/tclpkg' > Makefile:822: recipe for target 'install-recursive' failed > make[2]: *** [install-recursive] Error 1 > make[2]: Leaving directory '/tmp/SBo/graphviz-2.40.1' > make[1]: *** [install] Error 2 > Makefile:1115: recipe for target 'install' failed > make[1]: Leaving directory '/tmp/SBo/graphviz-2.40.1' > make: *** [install-strip] Error 2 > Makefile:1125: recipe for target 'install-strip' failed > Failure encountered while building graphviz: > graphviz.SlackBuild return non-zero hi Nate, could it be that you got a version of java installed (like jdk, for example) and graphviz detect it and build a module for it, but you are building graphviz becoming root with a simple "su" and not "su -" so that your shell doesn't have the command javac in its path? Matteo From n0nb at n0nb.us Thu May 24 12:49:54 2018 From: n0nb at n0nb.us (Nate Bargmann) Date: Thu, 24 May 2018 07:49:54 -0500 Subject: [Slackbuilds-users] graphviz build failure In-Reply-To: References: <20180524120918.ugfaer2lbg6etk7a@n0nb.us> Message-ID: <20180524124954.7caxhgcx3vrallsb@n0nb.us> * On 2018 24 May 07:23 -0500, Matteo Bernardini wrote: > hi Nate, > > could it be that you got a version of java installed (like jdk, for > example) and graphviz detect it and build a module for it, but you are > building graphviz becoming root with a simple "su" and not "su -" so > that your shell doesn't have the command javac in its path? I always log in with 'su -l' and this was no exception. I only have the jre package installed: /var/log/packages $ ls *java* gcc-java-5.5.0-x86_64-1_slack14.2 /var/log/packages $ ls *jre* jre-8u162-x86_64-1 /var/log/packages $ ls *jdk* /bin/ls: cannot access '*jdk*': No such file or directory I do find the following from 'locate javac': /usr/lib64/jvm/bin/javac I need to investigate why that is not in my root or user path, I guess. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: http://www.n0nb.us GPG key: D55A8819 GitHub: N0NB -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From matteo.bernardini at gmail.com Thu May 24 13:04:08 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 24 May 2018 15:04:08 +0200 Subject: [Slackbuilds-users] graphviz build failure In-Reply-To: <20180524124954.7caxhgcx3vrallsb@n0nb.us> References: <20180524120918.ugfaer2lbg6etk7a@n0nb.us> <20180524124954.7caxhgcx3vrallsb@n0nb.us> Message-ID: 2018-05-24 14:49 GMT+02:00 Nate Bargmann : > * On 2018 24 May 07:23 -0500, Matteo Bernardini wrote: >> hi Nate, >> >> could it be that you got a version of java installed (like jdk, for >> example) and graphviz detect it and build a module for it, but you are >> building graphviz becoming root with a simple "su" and not "su -" so >> that your shell doesn't have the command javac in its path? > > I always log in with 'su -l' and this was no exception. > > I only have the jre package installed: > > /var/log/packages > $ ls *java* > gcc-java-5.5.0-x86_64-1_slack14.2 > /var/log/packages > $ ls *jre* > jre-8u162-x86_64-1 > /var/log/packages > $ ls *jdk* > /bin/ls: cannot access '*jdk*': No such file or directory > > I do find the following from 'locate javac': > > /usr/lib64/jvm/bin/javac > > I need to investigate why that is not in my root or user path, I guess. we don't have a jre SlackBuild on SBo, just jdk: is there any reason why you have not installed that? if you install that, and logout/login again, you should have an usable javac in your PATH. Matteo From kjhambrick at gmail.com Thu May 24 13:05:30 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Thu, 24 May 2018 08:05:30 -0500 Subject: [Slackbuilds-users] postgis and CGAL 4.12 In-Reply-To: <2571701.8GOG19e1Es@wintermute.sprawl.net> References: <2571701.8GOG19e1Es@wintermute.sprawl.net> Message-ID: Thank you for the replies Willy and Ben. I'll try Ben's patch as linked by Willy. As for why is SFCGAL linked to postgis ... I don't recall ! I've been building and installing CGAL and SFCGAL for 'a while' now and I don't recall why :) OTOH, I've been building and installing postgis for years and years ( much longer than CGAL + SFCGAL ). I've still got a Slackware 13.37 system where I started using postgis. I believe it is postgis-1.5.8. I'll check to see what dependencies are linked. I'll be able to do some more testing later next week but postgis is working very well with CGAL 4.11.1 on my work Laptop and I've got a looming work deadline for a big project that has to go out. I've also got a feeling that the issue with compiling postgis 2.4.4 with ( CGAL 4.12 + SFCGAL 1.3.5 ) is that Slackware 14.2 ships with boost 1.59 while the stdc++17 flag is only supported in boost version 1.67 and greater. Anyhow I've got a few avenues to explore now and I'll report back as soon as I can ! Thanks again for all that y'all do ! -- kjh On Tue, May 22, 2018 at 9:09 PM, Benjamin Trigona-Harany < slackbuilds at jaxartes.net> wrote: > On Sunday, 20 May 2018 09:47:57 PDT Konrad J Hambrick wrote: > > I the meantime, postgis does work with everything updated EXCEPT > CGAL-4.12 > > ... > > > > Any ideas ? > > So far I've been able to confirm everything you said: PostGIS won't > compile > with CGAL 4.12 and SFCGAL. David and I were coordinating on upgrading CGAL > from 4.9 and the 4.11 upgrade was fine but I missed how it broke PostGIS > with > the more recent 4.12. I suppose it's because it's only an optional > dependency > for PostGIS ... > > There are a few ways of fixing the issue: remove SFCAL; add > --without-sfcgal > to PostGIS's configure; or downgrade CGAL to 4.11. The choice likely > depends > on whether you need the additional PostGIS functions provided by SFCAL and > whether you need SFCGAL on your system for something else! > > Ben > > > _______________________________________________ > 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 n0nb at n0nb.us Thu May 24 13:23:59 2018 From: n0nb at n0nb.us (Nate Bargmann) Date: Thu, 24 May 2018 08:23:59 -0500 Subject: [Slackbuilds-users] graphviz build failure In-Reply-To: References: <20180524120918.ugfaer2lbg6etk7a@n0nb.us> <20180524124954.7caxhgcx3vrallsb@n0nb.us> Message-ID: <20180524132359.47hvz4xt2a3o72mu@n0nb.us> * On 2018 24 May 08:05 -0500, Matteo Bernardini wrote: > we don't have a jre SlackBuild on SBo, just jdk: is there any reason > why you have not installed that? I seem to recall that I followed the instructions at: https://mirrors.slackware.com/slackware/slackware-14.2/extra/java/ to install it. > if you install that, and logout/login again, you should have an usable > javac in your PATH. I only needed it (I thought) to run an amateur radio program (not packaged) and then this issue appears out of nowhere. I see that graphviz is a dependency of wireshark which I don't use often, if at all. Also, another wireshark dependency, libinput, is also having a build failure with "dot". dot? Harrumph! I think I'll remove the entire mess and move on! Thanks. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: http://www.n0nb.us GPG key: D55A8819 GitHub: N0NB -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From matteo.bernardini at gmail.com Thu May 24 13:32:12 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 24 May 2018 15:32:12 +0200 Subject: [Slackbuilds-users] graphviz build failure In-Reply-To: <20180524132359.47hvz4xt2a3o72mu@n0nb.us> References: <20180524120918.ugfaer2lbg6etk7a@n0nb.us> <20180524124954.7caxhgcx3vrallsb@n0nb.us> <20180524132359.47hvz4xt2a3o72mu@n0nb.us> Message-ID: 2018-05-24 15:23 GMT+02:00 Nate Bargmann : > * On 2018 24 May 08:05 -0500, Matteo Bernardini wrote: >> we don't have a jre SlackBuild on SBo, just jdk: is there any reason >> why you have not installed that? > > I seem to recall that I followed the instructions at: > > https://mirrors.slackware.com/slackware/slackware-14.2/extra/java/ > > to install it. > >> if you install that, and logout/login again, you should have an usable >> javac in your PATH. > > I only needed it (I thought) to run an amateur radio program (not > packaged) and then this issue appears out of nowhere. I see that > graphviz is a dependency of wireshark which I don't use often, if at > all. Also, another wireshark dependency, libinput, is also having a > build failure with "dot". dot? Harrumph! I think I'll remove the > entire mess and move on! /usr/bin/dot is a tool shipped with graphviz. From slackbuilds at jaxartes.net Thu May 24 15:03:04 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Thu, 24 May 2018 08:03:04 -0700 Subject: [Slackbuilds-users] postgis and CGAL 4.12 In-Reply-To: References: <2571701.8GOG19e1Es@wintermute.sprawl.net> Message-ID: <3213493.H9LUmaZVD9@wintermute.sprawl.net> On Thursday, 24 May 2018 06:05:30 PDT Konrad J Hambrick wrote: > Thank you for the replies Willy and Ben. > > I'll try Ben's patch as linked by Willy. That patch is unrelated. > As for why is SFCGAL linked to postgis ... I don't recall ! > > I've been building and installing CGAL and SFCGAL for 'a while' now and I > don't recall why :) This is probably one of those cases where if you don't know that you need it, you don't need it :) CGAL/SFCGAL add some addtional geometric functions that aren't available in geos, but the application for these is pretty niche. A quick look at the docs should tell you whether you can dispense with SFCGAL altogether: https:// postgis.net/docs/manual-2.4/reference.html#reference_sfcgal > I've also got a feeling that the issue with compiling postgis 2.4.4 with ( > CGAL 4.12 + SFCGAL 1.3.5 ) is that Slackware 14.2 ships with boost 1.59 > while the stdc++17 flag is only supported in boost version 1.67 and greater. > > Anyhow I've got a few avenues to explore now and I'll report back as soon > as I can ! If you find a way forward to build PostGIS with the current versions of CGAL/ SFCGAL, that would be aweseom. Let us know! From alik at ejik.org Thu May 24 17:11:38 2018 From: alik at ejik.org (Alexander Verbovetsky) Date: Thu, 24 May 2018 20:11:38 +0300 Subject: [Slackbuilds-users] Calibre compilation Message-ID: <1527181898.3326034.1383683312.36CD4CC4@webmail.messagingengine.com> Hello, My attempt to build calibre (using slackrepo) failed with the following error: ----- IOError: [Errno 13] Permission denied: u'/tmp/SBo/calibre-3.9.0/build/pyqt/pictureflow/pictureflow.exp' ----- I think that this happens because "setup.py install" drops the root privileges at some moment: ----- Dropping privileges to those of alik: 1000 ----- Correspondingly, I added to the SlackBuild the following snippet from http://www.slackware.com/~alien/slackbuilds/calibre/build/calibre.SlackBuild by Eric Hameleers: ----- # This dropping of privilege is unnecessary and breaks the SlackBuild: sed -i -e "s:if os.geteuid() == 0:if False and os.geteuid() == 0:" \ setup/install.py ----- and the error disappeared. This works for both 3.9.0 (SBo version) and 3.23.0 (current version). Best regards, Alexander From willysr at slackbuilds.org Sat May 26 00:13:57 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 26 May 2018 07:13:57 +0700 Subject: [Slackbuilds-users] Updates - 20180526.1 Message-ID: <0afe9cc2-950b-dfe3-0b41-d0385f72e7cf@slackbuilds.org> Hi this will be the last update in May please note that there are some scripts gets renamed in this batch Sat May 26 00:01:29 UTC 2018 academic/ITK: Add missing header file. audio/abcde: Updated for version 2.9.1. audio/clockchimes: Updated for version 0.3. audio/rplay: Switch homepage to archive.org. audio/sfarkxtc: Update homepage. business/stansoft: Update MD5SUMS. desktop/Buku: Updated for version 3.8. desktop/Zafiro-icons: Updated for version 0.1.9. desktop/cwm: Updated for version 6.3. desktop/jgmenu: Updated for version 0.9. desktop/oomox: Update MD5SUMS. desktop/paper-gtk-theme: Updated for version 20171207. desktop/paper-icon-theme: Updated for version 20180304. desktop/ssr: Updated for version 0.3.11. development/cargo-vendor: Updated for version 0.1.15. development/cppcms: Updated for version 1.2.1. development/diffoscope: Updated for version 95. development/git-lfs: Updated for version 2.4.1. development/libretro-samples: Switch homepage to https. development/mrustc: Updated for version gitb5b7089. development/perf: Updated for version 4.4.132. development/pudb: Updated for version 2017.1.4 + new maintainer. development/pyclewn: Update homepage and download. development/pyenchant: Update homepage. development/samurai: Added (ninja-compatible build tool). development/tkcvs: Switch homepage to archive.org. development/uncrustify: Updated for version 0.67. games/cannonball-libretro: Added (Enhanced OutRun Engine). games/flare-game: Updated for version 1.06. games/flare: Updated for version 1.06. games/mame2014-libretro: Updated for version 2017.12.31_62a932c. gis/geojson: Updated for version 2.4.0. gis/gpxsee: Updated for version 5.12. gis/libLAS: Update homepage. gis/osgEarth: Updated for version 2.9 + new maintainer gis/osm2pgrouting: Updated for version 2.3.5. gis/ossim: Fix tarball extraction. graphics/nvidia-texture-tools: Added (NVIDIA Texture Tools). graphics/whyteboard: Switched homepage to archive.org. ham/7plus: Switch homepage to archive.org. libraries/OpenSceneGraph: Updated for version 3.5.5 + new maintainer libraries/dcmtk: Added (DICOM ToolKit). libraries/libast: Updated homepage. libraries/libgta: Added (Generic Tagged Arrays Library). libraries/libqb: Added (part of linux cluster). libraries/libwacom: Updated for version 0.30. libraries/python3-dvdvideo: Update homepage. misc/par2cmdline-tbb: Update homepage. multimedia/dvgrab: Switch homepage to archive.org. multimedia/makemkv: Updated for version 1.12.2. multimedia/smplayer: Updated for version 18.5.0. multimedia/x265: Updated for version 2.8. network/WireGuard: Updated for version 0.0.20180524. network/broadcom-sta: Updated for Linux kernel 4.16. network/dbmail: Added (IMAP and POP3 Server). network/freerapid: Updated for version 0.9u4. network/glewlwyd: Updated for version 1.4.4. network/liferea: Update DEP. network/lizardfs: Update MD5SUMS. network/opera-developer: Updated for version 55.0.2962.0. network/opera: Updated for version 53.0.2907.68. network/palemoon-bin: Added (renamed from palemoon) + new maint. network/palemoon: Removed (please use palemoon-bin). network/phpmyadmin: Updated for version 4.8.1. network/prosody-mod-cloud-notify: Updated for version hg3010. network/prosody-mod-csi: Fixed MD5SUM. network/prosody-mod-filter-chatstates: Fixed MD5SUM. network/prosody-mod-http-upload: Updated for version hg3011. network/prosody-mod-mam-muc: Updated for version hg3042. network/prosody-mod-smacks: Fixed MD5SUM. network/prosody-mod-throttle-presence: Fixed MD5SUM. network/qupzilla: Updated for version 2.1.2. network/riot-web: Update MD5SUMS. network/shorewall-core: Updated for version 5.2.0.4. network/shorewall6: Updated for version 5.2.0.4. network/shorewall: Updated for version 5.2.0.4. network/slimjet: Updated for version 19.0.0.0. network/verm: Updated for version 1.5.1. network/wireshark: Updated for version 2.6.1. network/youtube-dl: Updated for version 2018.05.18. office/MasterPDFEditor: Updated for version 5.0.03. office/qute: Update homepage. office/smoffice2018: Updated for version 2018_931. office/teapot: Switch homepage to archive.org. perl/perl-Glib-Object-Introspection: Updated for version 0.045. perl/perl-WebService-MusicBrainz: Updated for version 1.0.4. perl/perl-glib: Updated for version 1.327. prosody/prosody-mod-smacks-offline: Fixed MD5SUM. python/PyGithub: Update homepage. python/git-fame: Updated DOWNLOAD. python/parso: Updated for version 0.2.1. python/pybluez: Update homepage. python/python3-django: Update REQUIRES and HOMEPAGE. python/python3-parso: Updated for version 0.2.1. python/pytzdata: Updated for version 2018.5. python/thonny: Updated for version 2.2.0b2. ruby/ruby-faraday: Updated for version 0.15.2. ruby/ruby-gist: Updated for version 5.0.0. ruby/rubygem-rubocop: Updated for version 0.56. system/Eterm: Update homepage. system/emelfm2: Switch homepage to archive.org. system/jdupes: Updated for version 1.10.2. system/kitchen-sync: Updated for version 1.0. system/klish: Added (clish fork). system/mandoc: Added (UNIX manpage compiler). system/mdocml: Removed (Renamed to mandoc). system/mtftar: Switch homepage to archive.org, fix download. system/netdata: Add setcap for apps.plugins. system/nkf: Added (Network Kanji Filter). system/omnidb-app: Added (Database Management System). system/passwordsafe: Fixed download. system/pdfgrep: Updated for version 2.1.1. system/python3-urwid: Updated for version 2.0.1. system/sandbox: Added (Gentoo Sandbox Tool). system/sandy: Switch homepage to archive.org. system/smbldap-tools: Switch homepage to archive.org. system/spl-solaris: Updated for version 0.7.9. system/uae: Switch homepage to archive.org. system/upass: Update REQUIRES. system/zfs-on-linux: Updated for version 0.7.9. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kjhambrick at gmail.com Sat May 26 12:30:13 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 26 May 2018 07:30:13 -0500 Subject: [Slackbuilds-users] OpenCASCADE Download Message-ID: David -- The OpenCASCADE Directory has been removed from ArchLinux Community Directory I was able to create a login and download opencascade-6.9.1.tgz via PaleMoon from the OpenCASCADE WebSite ( still after being redirected to opencascade.com from opencascade.org ) The md5sum of the manually downloaded file matched OpenCASCADE.info and the 020_vtk_InsertNextTupleValue.diff patch applied properly and the Package is now building on my system. Anyhow ... not sure why the directory was removed from the ArchLinux Community Directory but there it is ... Thanks for all the SlackBuilds and for all you do for Slackware in general ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sat May 26 12:39:37 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 26 May 2018 14:39:37 +0200 Subject: [Slackbuilds-users] OpenCASCADE Download In-Reply-To: References: Message-ID: 2018-05-26 14:30 GMT+02:00 Konrad J Hambrick : > David -- > > The OpenCASCADE Directory has been removed from ArchLinux Community > Directory > > I was able to create a login and download opencascade-6.9.1.tgz via PaleMoon > from the OpenCASCADE WebSite ( still after being redirected to > opencascade.com from opencascade.org ) > > The md5sum of the manually downloaded file matched OpenCASCADE.info and the > 020_vtk_InsertNextTupleValue.diff patch applied properly and the Package is > now building on my system. > > Anyhow ... not sure why the directory was removed from the ArchLinux > Community Directory but there it is ... > > Thanks for all the SlackBuilds and for all you do for Slackware in general ! thanks to you for reporting! I mirrored the original download and pushed the new download link in my branch on git. Matteo From w_calandrini at hotmail.com Fri May 25 22:46:24 2018 From: w_calandrini at hotmail.com (William PC) Date: Fri, 25 May 2018 22:46:24 +0000 Subject: [Slackbuilds-users] Email form aprovel white list hotmail Message-ID: Hello I'm trying to update the slackbuilds that I already sent using this new email and an alias used for working with a project that I create called slack-it, for helping to maintaining the things that I have done with Slackware. Best wishes, William PC -------------- next part -------------- An HTML attachment was scrubbed... URL: From w_calandrini at hotmail.com Sat May 26 15:42:38 2018 From: w_calandrini at hotmail.com (William PC) Date: Sat, 26 May 2018 15:42:38 +0000 Subject: [Slackbuilds-users] Problems submiting packages Message-ID: Hello, I'm trying to submit some updated source packs. But I'm getting this error: w_calandrini at hotmail.com was rejected by hotmail-com.olc.protection.outlook.com. I think is something related to Hotmail whitelist, I'm trying to manage it with them. Best wishes, William PC www.slack-it.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From kjhambrick at gmail.com Sat May 26 19:46:00 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 26 May 2018 14:46:00 -0500 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz Message-ID: Chris -- This is a Slackware64 14.2 + Multilib System. The 'root' directory name in OpenSceneGraph-3.5.5.tar.gz is kinda-sorta odd. What's in the OpenSceneGraph.tar.gz file is: OpenSceneGraph-OpenSceneGraph-3.5.5/ What's expected in the OpenSceneGraph.SlackBuild file is: OpenSceneGraph-3.5.5/ This is perfectly fine for the first build -- the tar file is extracted into a new directory so all is well. However, when -or- if one needs to rebuild OpenSceneGraph ( like I did ) then the cmake build will 'continue' in the stale directory. Patch for the odd directory structure of the existing OpenSceneGraph-3.5.5.tar.gz is attached. Or maybe this should be reported upstream ??? Here is another one ... I had the OPTIONAL Package fltk-1.3.3-x86_64-2_SBo.tgz installed for the flSynclient Package. It turns out that OpenSceneGraph will build example_osgviewerFLTK if FLTK is installed. However it fails for fltk-1.3.3. Here is the tail of my build log: Scanning dependencies of target example_osgviewerFLTK [100%] Building CXX object examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/osgviewerFLTK.cpp.o [100%] Linking CXX executable ../../bin/osgviewerFLTK /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../lib64/libfltk_gl.so: undefined reference to `Fl_XFont_On_Demand::value()' collect2: error: ld returned 1 exit status examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/build.make:123: recipe for target 'bin/osgviewerFLTK' failed make[2]: *** [bin/osgviewerFLTK] Error 1 CMakeFiles/Makefile2:18128: recipe for target 'examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all' failed make[1]: *** [examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all] Error 2 Makefile:127: recipe for target 'all' failed make: *** [all] Error 2 I upgraded FLTK to version 1.3.4-2 ( yes ... it is 'dash 2' ) and OpenSceneGraph compiled and installed and runs properly now. One last thing I noticed ( :) I swear that is all :) ) that I am still trying to track down is that the $occ variables ( -DOPENCASCADE_INCLUDE_DIR -and- -DOPENCASCADE_LIBRARY_TYPE ) are both ignored by the OpenSceneGraph cmake configurator. Here is the log message: CMake Warning: Manually-specified variables were not used by the project: OPENCASCADE_INCLUDE_DIR OPENCASCADE_LIBRARY_TYPE Anyhow ... like I said, I am still looking into this one on my System. Thanks for all the SlackBuilds Chris ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenSceneGraph.SlackBuild.patch Type: text/x-patch Size: 351 bytes Desc: not available URL: From chris.willing at linux.com Sun May 27 00:25:11 2018 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 27 May 2018 10:25:11 +1000 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: Message-ID: On 27/05/18 05:46, Konrad J Hambrick wrote: > Chris -- > > This is a Slackware64 14.2 + Multilib System. > > The 'root' directory name in OpenSceneGraph-3.5.5.tar.gz is kinda-sorta odd. > > What's in the OpenSceneGraph.tar.gz file is: > > ?? OpenSceneGraph-OpenSceneGraph-3.5.5/ > > What's expected in the OpenSceneGraph.SlackBuild file is: > > ?? OpenSceneGraph-3.5.5/ > ? > This is perfectly fine for the first build -- the tar file is extracted > into a new directory so all is well. > > However, when -or- if one needs to rebuild OpenSceneGraph ( like I did ) > then the cmake build will 'continue' in the stale directory. > > Patch for the odd directory structure of the existing > OpenSceneGraph-3.5.5.tar.gz is attached. > > Or maybe this should be reported upstream ??? > Thanks Konrad, I'll add this to the other change I have regarding the occ variable (see below). > Here is another one ... I had the OPTIONAL Package > fltk-1.3.3-x86_64-2_SBo.tgz installed for the flSynclient Package. > > It turns out that OpenSceneGraph will build example_osgviewerFLTK if > FLTK is installed. > > However it fails for fltk-1.3.3. > > Here is the tail of my build log: > > Scanning dependencies of target example_osgviewerFLTK > [100%] Building CXX object > examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/osgviewerFLTK.cpp.o > [100%] Linking CXX executable ../../bin/osgviewerFLTK > /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../lib64/libfltk_gl.so: > undefined reference to `Fl_XFont_On_Demand::value()' > collect2: error: ld returned 1 exit status > examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/build.make:123: > recipe for target 'bin/osgviewerFLTK' failed > make[2]: *** [bin/osgviewerFLTK] Error 1 > CMakeFiles/Makefile2:18128: recipe for target > 'examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all' failed > make[1]: *** > [examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all] Error 2 > Makefile:127: recipe for target 'all' failed > make: *** [all] Error 2 > > I upgraded FLTK to version 1.3.4-2 ( yes ... it is 'dash 2' ) and > OpenSceneGraph compiled and installed and runs properly now. > I thought I'd covered all the bases before updating the OSG version but missed this one (obviously!). I'll look at it during the week. > One last thing I noticed ( :) I swear that is all :) ) that I am still > trying to track down is that the $occ variables ( > -DOPENCASCADE_INCLUDE_DIR -and- -DOPENCASCADE_LIBRARY_TYPE ) are both > ignored by the OpenSceneGraph cmake configurator. > > Here is the log message: > > ?? CMake Warning: > ???? Manually-specified variables were not used by the project: > > ?????? OPENCASCADE_INCLUDE_DIR > ?????? OPENCASCADE_LIBRARY_TYPE > The occ variable is left over from when I was testing multiple OSG versions to see how far it could be updated (since quite a few other SlackBuilds depend on OpenSceneGraph). Support for OpenCASCADE doesn't actually start until OSG version 3.5.6 (so superfluous in 3.5.5, as you discovered) but we can't update to 3.5.6 yet because upstreams of other dependent SlackBuilds aren't ready for some of the changes. The occ stuff will be commented out (pending further OSG upgrades) in the next SBo update. Thanks, chris From chris.willing at linux.com Sun May 27 02:46:34 2018 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 27 May 2018 12:46:34 +1000 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: Message-ID: On 27/05/18 10:25, Christoph Willing wrote: > On 27/05/18 05:46, Konrad J Hambrick wrote: [snip] > >> Here is another one ... I had the OPTIONAL Package >> fltk-1.3.3-x86_64-2_SBo.tgz installed for the flSynclient Package. >> >> It turns out that OpenSceneGraph will build example_osgviewerFLTK if >> FLTK is installed. >> >> However it fails for fltk-1.3.3. >> >> Here is the tail of my build log: >> >> Scanning dependencies of target example_osgviewerFLTK >> [100%] Building CXX object >> examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/osgviewerFLTK.cpp.o >> [100%] Linking CXX executable ../../bin/osgviewerFLTK >> /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../lib64/libfltk_gl.so: >> undefined reference to `Fl_XFont_On_Demand::value()' >> collect2: error: ld returned 1 exit status >> examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/build.make:123: >> recipe for target 'bin/osgviewerFLTK' failed >> make[2]: *** [bin/osgviewerFLTK] Error 1 >> CMakeFiles/Makefile2:18128: recipe for target >> 'examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all' failed >> make[1]: *** >> [examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all] Error 2 >> Makefile:127: recipe for target 'all' failed >> make: *** [all] Error 2 >> >> I upgraded FLTK to version 1.3.4-2 ( yes ... it is 'dash 2' ) and >> OpenSceneGraph compiled and installed and runs properly now. >> > I thought I'd covered all the bases before updating the OSG version but > missed this one (obviously!). I'll look at it during the week. > Actually, I can't replicate this problem. In a clean VM with newly built /var/log/packages/fltk-1.3.3-x86_64-2 installed I see: Scanning dependencies of target example_osgviewerFLTK [ 80%] Building CXX object examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/osgviewerFLTK.cpp.o [ 81%] Linking CXX executable ../../bin/osgviewerFLTK [ 81%] Built target example_osgviewerFLTK If I run (still in the VM so with limited GL capability) the command: strings /usr/lib64/libfltk_gl.so.1.3 |less and search for XFont, I see a single reference: glXUseXFont In a real machine with Nvidia graphics and binary driver, the same search reveals: _ZN18Fl_XFont_On_Demand5valueEv glGenLists glXUseXFont Seeing that difference in varying graphics environments (although compilation continues to completion in both these particular cases) I wonder if the issue you're seeing is due to your (perhaps even more different) graphics environment (Intel, nouveau, ...)? That wouldn't necessarily explain why it worked for you with updated fltk though. Or, maybe your fltk-1.3.3 was built some time ago - _before_ you updated your graphics hardware/driver (so failed) but your fltk-1.3.4-2 succeeded because you just built it now using the updated graphics hardware/driver. Anyway, I'll email the fltk maintainer and ask if he's prepared to upgrade the version. My stored source tarball fltk-1.3.3-source.tar.gz is dated Nov 4 2014 i.e. it's a pretty old version. However fltk seems to have a ton of dependent SlackBuilds so checking all of them with a newer fltk won't be trivial. chris From chris at chrisn.me.uk Sun May 27 03:28:46 2018 From: chris at chrisn.me.uk (Chris Novakovic) Date: Sun, 27 May 2018 04:28:46 +0100 Subject: [Slackbuilds-users] Batch update to Perl homepage/download URLs Message-ID: <597927a4-ea7b-d2ee-2907-c5baea5bc4e5@chrisn.me.uk> Last week it was announced that the CPAN search site, search.cpan.org, will shut down on June 25th [1]. search.cpan.org operates as both a HTML-based documentation viewer for Perl modules and a CPAN mirror, so a lot of Perl SlackBuilds use search.cpan.org URLs as homepage and/or download links. Although there's a contingency plan in place to redirect requests for resources on search.cpan.org to their MetaCPAN [2] equivalents, this doesn't yet work for all resources (nor is it clear whether it will), and it hasn't been announced for how long the redirection mechanism will stay in place. In any case, the message from the Perl NOC is clear: start using MetaCPAN in place of search.cpan.org. On a similar note, it's a common complaint on this list that the download link for a Perl module SlackBuild has stopped working. This invariably turns out to be because the tarball was hosted on the primary CPAN mirror, www.cpan.org, and the author has deleted it because it's an obsolete version of the module (which they're encouraged to by the PAUSE admins). Only two mirrors keep a complete history of CPAN: BackPAN [3] and MetaCPAN. This seems like a good time to stop using {search,www}.cpan.org on SBo in favour of MetaCPAN. 273 SlackBuilds in master currently contain {search,www}.cpan.org URLs in some form. Rather than spamming hundreds of individual SBo maintainers with requests to update links, I thought it'd be less time-consuming for everyone involved if I did this en masse, so I've replaced affected URLs with their MetaCPAN equivalents in all *.SlackBuild, *.info, README and slack-desc files. The MetaCPAN URLs tend to be longer than their search.cpan.org counterparts, which in some cases pushes lines in slack-desc files over the length limit; in these cases, I've shortened the URL (by linking to the Perl module distribution's release page instead of a specific page in the documentation) or moved the URL to a new line. The changes (one commit per SlackBuild, as standard) can be pulled from the master branch of: https://github.com/chrisnovakovic/slackbuilds [1] https://log.perl.org/2018/05/goodbye-search-dot-cpan-dot-org.html [2] https://metacpan.org [3] http://backpan.cpantesters.org From willysr at slackbuilds.org Sun May 27 04:01:25 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 27 May 2018 11:01:25 +0700 Subject: [Slackbuilds-users] Batch update to Perl homepage/download URLs In-Reply-To: <597927a4-ea7b-d2ee-2907-c5baea5bc4e5@chrisn.me.uk> References: <597927a4-ea7b-d2ee-2907-c5baea5bc4e5@chrisn.me.uk> Message-ID: <6321903b-a6e9-b015-34e8-37fef571423c@slackbuilds.org> > This seems like a good time to stop using {search,www}.cpan.org on SBo > in favour of MetaCPAN. 273 SlackBuilds in master currently contain > {search,www}.cpan.org URLs in some form. Rather than spamming hundreds > of individual SBo maintainers with requests to update links, I thought > it'd be less time-consuming for everyone involved if I did this en > masse, so I've replaced affected URLs with their MetaCPAN equivalents in > all *.SlackBuild, *.info, README and slack-desc files. The MetaCPAN URLs > tend to be longer than their search.cpan.org counterparts, which in some > cases pushes lines in slack-desc files over the length limit; in these > cases, I've shortened the URL (by linking to the Perl module > distribution's release page instead of a specific page in the > documentation) or moved the URL to a new line. > > The changes (one commit per SlackBuild, as standard) can be pulled from > the master branch of: > > https://github.com/chrisnovakovic/slackbuilds > > [1] https://log.perl.org/2018/05/goodbye-search-dot-cpan-dot-org.html > [2] https://metacpan.org > [3] http://backpan.cpantesters.org Big thanks for the mass effort. Can you send your PR to https://github.com/SlackBuildsOrg/slackbuilds/ ? It will be easier to merge :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From chris at chrisn.me.uk Sun May 27 04:11:14 2018 From: chris at chrisn.me.uk (Chris Novakovic) Date: Sun, 27 May 2018 05:11:14 +0100 Subject: [Slackbuilds-users] Batch update to Perl homepage/download URLs In-Reply-To: <6321903b-a6e9-b015-34e8-37fef571423c@slackbuilds.org> References: <597927a4-ea7b-d2ee-2907-c5baea5bc4e5@chrisn.me.uk> <6321903b-a6e9-b015-34e8-37fef571423c@slackbuilds.org> Message-ID: On 27/05/2018 05:01, Willy Sudiarto Raharjo wrote: > Can you send your PR to https://github.com/SlackBuildsOrg/slackbuilds/ ? > It will be easier to merge :) Sorry, I didn't notice the GitHub mirror --- here you go: https://github.com/SlackBuildsOrg/slackbuilds/pull/111 From willysr at slackbuilds.org Sun May 27 04:12:50 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 27 May 2018 11:12:50 +0700 Subject: [Slackbuilds-users] Batch update to Perl homepage/download URLs In-Reply-To: References: <597927a4-ea7b-d2ee-2907-c5baea5bc4e5@chrisn.me.uk> <6321903b-a6e9-b015-34e8-37fef571423c@slackbuilds.org> Message-ID: <85cabbf1-6216-cdac-eae5-63e238ac1a49@slackbuilds.org> >> Can you send your PR to https://github.com/SlackBuildsOrg/slackbuilds/ ? >> It will be easier to merge :) > > Sorry, I didn't notice the GitHub mirror --- here you go: > > https://github.com/SlackBuildsOrg/slackbuilds/pull/111 and merged to my branch already Again, big thanks!! -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Sun May 27 07:31:10 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 27 May 2018 17:31:10 +1000 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: Message-ID: On 27/05/18 12:46, Christoph Willing wrote: > On 27/05/18 10:25, Christoph Willing wrote: >> On 27/05/18 05:46, Konrad J Hambrick wrote: > [snip] >> >>> Here is another one ... I had the OPTIONAL Package >>> fltk-1.3.3-x86_64-2_SBo.tgz installed for the flSynclient Package. >>> >>> It turns out that OpenSceneGraph will build example_osgviewerFLTK if >>> FLTK is installed. >>> >>> However it fails for fltk-1.3.3. >>> >>> Here is the tail of my build log: >>> >>> Scanning dependencies of target example_osgviewerFLTK >>> [100%] Building CXX object >>> examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/osgviewerFLTK.cpp.o >>> [100%] Linking CXX executable ../../bin/osgviewerFLTK >>> /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../lib64/libfltk_gl.so: >>> undefined reference to `Fl_XFont_On_Demand::value()' >>> collect2: error: ld returned 1 exit status >>> examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/build.make:123: >>> recipe for target 'bin/osgviewerFLTK' failed >>> make[2]: *** [bin/osgviewerFLTK] Error 1 >>> CMakeFiles/Makefile2:18128: recipe for target >>> 'examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all' failed >>> make[1]: *** >>> [examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all] Error 2 >>> Makefile:127: recipe for target 'all' failed >>> make: *** [all] Error 2 >>> >>> I upgraded FLTK to version 1.3.4-2 ( yes ... it is 'dash 2' ) and >>> OpenSceneGraph compiled and installed and runs properly now. >>> >> I thought I'd covered all the bases before updating the OSG version but >> missed this one (obviously!). I'll look at it during the week. >> > > Actually, I can't replicate this problem. In a clean VM with newly built > /var/log/packages/fltk-1.3.3-x86_64-2 installed I see: > > Scanning dependencies of target example_osgviewerFLTK > [ 80%] Building CXX object > examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/osgviewerFLTK.cpp.o > [ 81%] Linking CXX executable ../../bin/osgviewerFLTK > [ 81%] Built target example_osgviewerFLTK > > If I run (still in the VM so with limited GL capability) the command: > strings /usr/lib64/libfltk_gl.so.1.3 |less > and search for XFont, I see a single reference: > glXUseXFont > > In a real machine with Nvidia graphics and binary driver, the same > search reveals: > _ZN18Fl_XFont_On_Demand5valueEv > glGenLists > glXUseXFont > > Seeing that difference in varying graphics environments (although > compilation continues to completion in both these particular cases) I > wonder if the issue you're seeing is due to your (perhaps even more > different) graphics environment (Intel, nouveau, ...)? That wouldn't > necessarily explain why it worked for you with updated fltk though. Or, > maybe your fltk-1.3.3 was built some time ago - _before_ you updated > your graphics hardware/driver (so failed) but your fltk-1.3.4-2 > succeeded because you just built it now using the updated graphics > hardware/driver. > > Anyway, I'll email the fltk maintainer and ask if he's prepared to > upgrade the version. My stored source tarball fltk-1.3.3-source.tar.gz > is dated Nov 4 2014 i.e. it's a pretty old version. However fltk seems > to have a ton of dependent SlackBuilds so checking all of them with a > newer fltk won't be trivial. > Just as well I did some more checking before emailing the maintainer. It turns out that the SBo fltk is excess to requirements since there is already an fltk package in stock Slackware's extra. I guess that means the version in extra won't be updated. However the version at SBo is a mystery - from the git log it seems to be renamed some time ago from fltk13 but I don't understand why it still exists at all now that we have the fltk in extra. I see from your original email that you were using an SBo build (fltk-1.3.3-x86_64-2_SBo.tgz). I wonder if your OpenSceneGraph would succeed if you removed that version and installed the version from extra? I guess you're happy anyway having upgraded your local fltk and built OSG with that but it would be nice to know whether you could build it with the fltk from extra (as it does here). chris From chris.willing at linux.com Sun May 27 07:35:53 2018 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 27 May 2018 17:35:53 +1000 Subject: [Slackbuilds-users] fltk should not be in SBo? Message-ID: <2fa689c0-4182-f6ce-8fcc-23b8fb1bdd1e@linux.com> Since there is an fltk package in extra, should SBo still have libraries/fltk in its repo? The version numbers are identical so I don't see any added value and I have a vague notion that we don't replicate packages which already exist in stock Slackware. chris From matteo.bernardini at gmail.com Sun May 27 07:42:58 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 27 May 2018 09:42:58 +0200 Subject: [Slackbuilds-users] fltk should not be in SBo? In-Reply-To: <2fa689c0-4182-f6ce-8fcc-23b8fb1bdd1e@linux.com> References: <2fa689c0-4182-f6ce-8fcc-23b8fb1bdd1e@linux.com> Message-ID: 2018-05-27 9:35 GMT+02:00 Christoph Willing : > Since there is an fltk package in extra, should SBo still have > libraries/fltk in its repo? The version numbers are identical so I don't > see any added value and I have a vague notion that we don't replicate > packages which already exist in stock Slackware. we assume our scripts are run on Slackware full installations and those don't include stuff in /extra, so we provide also SlackBuilds for things that you can find there (like flash, jdk, fltk...) in particular when they are needed as dependencies of something else. Matteo From chris.willing at iinet.net.au Sun May 27 09:17:15 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 27 May 2018 19:17:15 +1000 Subject: [Slackbuilds-users] fltk should not be in SBo? In-Reply-To: References: <2fa689c0-4182-f6ce-8fcc-23b8fb1bdd1e@linux.com> Message-ID: <0a0182bd-d6f2-f019-5623-140393773615@iinet.net.au> On 27/05/18 17:42, Matteo Bernardini wrote: > 2018-05-27 9:35 GMT+02:00 Christoph Willing : >> Since there is an fltk package in extra, should SBo still have >> libraries/fltk in its repo? The version numbers are identical so I don't >> see any added value and I have a vague notion that we don't replicate >> packages which already exist in stock Slackware. > > we assume our scripts are run on Slackware full installations and > those don't include stuff in /extra, so we provide also SlackBuilds > for things that you can find there (like flash, jdk, fltk...) in > particular when they are needed as dependencies of something else. > OK, fair enough. I guess an advantage of the SBo versions is that they could be updated, or other build options included, if desired (whereas Slackware -stable packages need a strong reason to be changed). At the same time, it can be confusing to have multiple versions around - see the recent thread "Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz" as an example - unless one already knows about them. Perhaps it would be good to add something about this in each relevant README, including what the advantage of each package might be. In the case of fltk, the versions are identical and it's not clear what the advantage(s) of one over the other might be. chris From kjhambrick at gmail.com Sun May 27 10:26:22 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sun, 27 May 2018 05:26:22 -0500 Subject: [Slackbuilds-users] fltk should not be in SBo? In-Reply-To: <0a0182bd-d6f2-f019-5623-140393773615@iinet.net.au> References: <2fa689c0-4182-f6ce-8fcc-23b8fb1bdd1e@linux.com> <0a0182bd-d6f2-f019-5623-140393773615@iinet.net.au> Message-ID: Thanks for the interesting info Chris. I didn't look for fltk in extra/ when I built it for FLSynclient -- I went straight for the SBo fltk.SlackBuild. And had I known about the official extra/ Package ... I would have been confused without knowing why to use SBo over extra/ -- kjh On Sun, May 27, 2018 at 4:17 AM, Christoph Willing < chris.willing at iinet.net.au> wrote: > On 27/05/18 17:42, Matteo Bernardini wrote: > > 2018-05-27 9:35 GMT+02:00 Christoph Willing : > >> Since there is an fltk package in extra, should SBo still have > >> libraries/fltk in its repo? The version numbers are identical so I don't > >> see any added value and I have a vague notion that we don't replicate > >> packages which already exist in stock Slackware. > > > > we assume our scripts are run on Slackware full installations and > > those don't include stuff in /extra, so we provide also SlackBuilds > > for things that you can find there (like flash, jdk, fltk...) in > > particular when they are needed as dependencies of something else. > > > > OK, fair enough. I guess an advantage of the SBo versions is that they > could be updated, or other build options included, if desired (whereas > Slackware -stable packages need a strong reason to be changed). > > At the same time, it can be confusing to have multiple versions around - > see the recent thread "Odd Directory Name in > OpenSceneGraph-3.5.5.tar.gz" as an example - unless one already knows > about them. Perhaps it would be good to add something about this in each > relevant README, including what the advantage of each package might be. > In the case of fltk, the versions are identical and it's not clear what > the advantage(s) of one over the other might be. > > chris > _______________________________________________ > 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 kjhambrick at gmail.com Sun May 27 10:46:40 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sun, 27 May 2018 05:46:40 -0500 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: Message-ID: Chris -- Dang ! I should have noted that I am running Slackware64 14.2 + Multilib + NVIDIA-Linux-x86_64-390.59.run And looking at my SlackBuild Wrapper ( attached ), I probably should have noted the OPTIONAL Dependencies too. Note the nvidia-texture-tools Package. # # built and installed B80525 # # dcmtk - dcmtk-3.6.3-x86_64-1_SBo # libgta - libgta-1.0.8-x86_64-1_SBo # nvidia-texture-tools - nvidia-texture-tools-2.1.1-x86_64-1_SBo # slurm x not needed # openmpi - openmpi-2.1.1-x86_64-1_SBo # python-twisted x skipped - too many dependencies # VTK - VTK-8.1.1-x86_64-1_SBo # FreeImage - FreeImage-3.17.0-x86_64-1_SBo # tbb - tbb-2018u3-x86_64-1_SBo # gl2ps - gl2ps-1.3.7-x86_64-1_SBo # OpenCASCADE - OpenCASCADE-6.9.1-x86_64-3_SBo # SDL2 - SDL2-2.0.8-x86_64-1_SBo # Also note that the SlackBuild wrapper generates a log file for each VERSION + TAG so I do have the full log where the initial osg build failed with fltk-1.3.3 ( not TOO huge at 266,487 bytes ) Thanks for looking at this Chris and thanks for the info about the Official extra/fltk/ Package ! -- kjh On Sun, May 27, 2018 at 2:31 AM, Christoph Willing < chris.willing at iinet.net.au> wrote: > On 27/05/18 12:46, Christoph Willing wrote: > > On 27/05/18 10:25, Christoph Willing wrote: > >> On 27/05/18 05:46, Konrad J Hambrick wrote: > > [snip] > >> > >>> Here is another one ... I had the OPTIONAL Package > >>> fltk-1.3.3-x86_64-2_SBo.tgz installed for the flSynclient Package. > >>> > >>> It turns out that OpenSceneGraph will build example_osgviewerFLTK if > >>> FLTK is installed. > >>> > >>> However it fails for fltk-1.3.3. > >>> > >>> Here is the tail of my build log: > >>> > >>> Scanning dependencies of target example_osgviewerFLTK > >>> [100%] Building CXX object > >>> examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/ > osgviewerFLTK.cpp.o > >>> [100%] Linking CXX executable ../../bin/osgviewerFLTK > >>> /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../.. > /../lib64/libfltk_gl.so: > >>> undefined reference to `Fl_XFont_On_Demand::value()' > >>> collect2: error: ld returned 1 exit status > >>> examples/osgviewerFLTK/CMakeFiles/example_ > osgviewerFLTK.dir/build.make:123: > >>> recipe for target 'bin/osgviewerFLTK' failed > >>> make[2]: *** [bin/osgviewerFLTK] Error 1 > >>> CMakeFiles/Makefile2:18128: recipe for target > >>> 'examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all' > failed > >>> make[1]: *** > >>> [examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all] > Error 2 > >>> Makefile:127: recipe for target 'all' failed > >>> make: *** [all] Error 2 > >>> > >>> I upgraded FLTK to version 1.3.4-2 ( yes ... it is 'dash 2' ) and > >>> OpenSceneGraph compiled and installed and runs properly now. > >>> > >> I thought I'd covered all the bases before updating the OSG version but > >> missed this one (obviously!). I'll look at it during the week. > >> > > > > Actually, I can't replicate this problem. In a clean VM with newly built > > /var/log/packages/fltk-1.3.3-x86_64-2 installed I see: > > > > Scanning dependencies of target example_osgviewerFLTK > > [ 80%] Building CXX object > > examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/ > osgviewerFLTK.cpp.o > > [ 81%] Linking CXX executable ../../bin/osgviewerFLTK > > [ 81%] Built target example_osgviewerFLTK > > > > If I run (still in the VM so with limited GL capability) the command: > > strings /usr/lib64/libfltk_gl.so.1.3 |less > > and search for XFont, I see a single reference: > > glXUseXFont > > > > In a real machine with Nvidia graphics and binary driver, the same > > search reveals: > > _ZN18Fl_XFont_On_Demand5valueEv > > glGenLists > > glXUseXFont > > > > Seeing that difference in varying graphics environments (although > > compilation continues to completion in both these particular cases) I > > wonder if the issue you're seeing is due to your (perhaps even more > > different) graphics environment (Intel, nouveau, ...)? That wouldn't > > necessarily explain why it worked for you with updated fltk though. Or, > > maybe your fltk-1.3.3 was built some time ago - _before_ you updated > > your graphics hardware/driver (so failed) but your fltk-1.3.4-2 > > succeeded because you just built it now using the updated graphics > > hardware/driver. > > > > Anyway, I'll email the fltk maintainer and ask if he's prepared to > > upgrade the version. My stored source tarball fltk-1.3.3-source.tar.gz > > is dated Nov 4 2014 i.e. it's a pretty old version. However fltk seems > > to have a ton of dependent SlackBuilds so checking all of them with a > > newer fltk won't be trivial. > > > > Just as well I did some more checking before emailing the maintainer. It > turns out that the SBo fltk is excess to requirements since there is > already an fltk package in stock Slackware's extra. I guess that means > the version in extra won't be updated. However the version at SBo is a > mystery - from the git log it seems to be renamed some time ago from > fltk13 but I don't understand why it still exists at all now that we > have the fltk in extra. > > I see from your original email that you were using an SBo build > (fltk-1.3.3-x86_64-2_SBo.tgz). I wonder if your OpenSceneGraph would > succeed if you removed that version and installed the version from > extra? I guess you're happy anyway having upgraded your local fltk and > built OSG with that but it would be nice to know whether you could build > it with the fltk from extra (as it does here). > > chris > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: .do-OpenSceneGraph.SlackBuild.sh Type: application/x-sh Size: 3074 bytes Desc: not available URL: From kjhambrick at gmail.com Sun May 27 11:05:06 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sun, 27 May 2018 06:05:06 -0500 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: Message-ID: p.s. Most of all ... thanks for all the time you've spent on this. And moreover, as you noted, digging into the packages dependent on fltk is a huge task. What can I do to help ? -- kjh These are packages where fltk is REQUIRED ( not to mention OPTIONAL dependencies ): # hoorex -m fltk |gawk '{ for ( i = 1 ; i <= NF; i ++ ){ print " " $i }}' fltk lalnview oblige flrig butt alsamixergui flSynclient glbsp horgand lmms edelib oblige-legacy4 xdiskusage Pixie tapiir ede rakarrack sfc dillo vocoder zynaddsubfx pyfltk fldigi yoshimi eureka fgrun htmldoc flpsed seaview chm2pdf On Sun, May 27, 2018 at 5:46 AM, Konrad J Hambrick wrote: > Chris -- > > Dang ! > > I should have noted that I am running Slackware64 14.2 + Multilib + > NVIDIA-Linux-x86_64-390.59.run > > And looking at my SlackBuild Wrapper ( attached ), I probably should have > noted the OPTIONAL Dependencies too. > > Note the nvidia-texture-tools Package. > # > # built and installed B80525 > # > # dcmtk - dcmtk-3.6.3-x86_64-1_SBo > # libgta - libgta-1.0.8-x86_64-1_SBo > # nvidia-texture-tools - nvidia-texture-tools-2.1.1-x86_64-1_SBo > # slurm x not needed > # openmpi - openmpi-2.1.1-x86_64-1_SBo > # python-twisted x skipped - too many dependencies > # VTK - VTK-8.1.1-x86_64-1_SBo > # FreeImage - FreeImage-3.17.0-x86_64-1_SBo > # tbb - tbb-2018u3-x86_64-1_SBo > # gl2ps - gl2ps-1.3.7-x86_64-1_SBo > # OpenCASCADE - OpenCASCADE-6.9.1-x86_64-3_SBo > # SDL2 - SDL2-2.0.8-x86_64-1_SBo > # > > Also note that the SlackBuild wrapper generates a log file for each > VERSION + TAG so I do have the full log > where the initial osg build failed with fltk-1.3.3 ( not TOO huge at > 266,487 bytes ) > > Thanks for looking at this Chris and thanks for the info about the > Official extra/fltk/ Package ! > > -- kjh > > > > On Sun, May 27, 2018 at 2:31 AM, Christoph Willing < > chris.willing at iinet.net.au> wrote: > >> On 27/05/18 12:46, Christoph Willing wrote: >> > On 27/05/18 10:25, Christoph Willing wrote: >> >> On 27/05/18 05:46, Konrad J Hambrick wrote: >> > [snip] >> >> >> >>> Here is another one ... I had the OPTIONAL Package >> >>> fltk-1.3.3-x86_64-2_SBo.tgz installed for the flSynclient Package. >> >>> >> >>> It turns out that OpenSceneGraph will build example_osgviewerFLTK if >> >>> FLTK is installed. >> >>> >> >>> However it fails for fltk-1.3.3. >> >>> >> >>> Here is the tail of my build log: >> >>> >> >>> Scanning dependencies of target example_osgviewerFLTK >> >>> [100%] Building CXX object >> >>> examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/ >> osgviewerFLTK.cpp.o >> >>> [100%] Linking CXX executable ../../bin/osgviewerFLTK >> >>> /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../ >> lib64/libfltk_gl.so: >> >>> undefined reference to `Fl_XFont_On_Demand::value()' >> >>> collect2: error: ld returned 1 exit status >> >>> examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/ >> build.make:123: >> >>> recipe for target 'bin/osgviewerFLTK' failed >> >>> make[2]: *** [bin/osgviewerFLTK] Error 1 >> >>> CMakeFiles/Makefile2:18128: recipe for target >> >>> 'examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all' >> failed >> >>> make[1]: *** >> >>> [examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all] >> Error 2 >> >>> Makefile:127: recipe for target 'all' failed >> >>> make: *** [all] Error 2 >> >>> >> >>> I upgraded FLTK to version 1.3.4-2 ( yes ... it is 'dash 2' ) and >> >>> OpenSceneGraph compiled and installed and runs properly now. >> >>> >> >> I thought I'd covered all the bases before updating the OSG version but >> >> missed this one (obviously!). I'll look at it during the week. >> >> >> > >> > Actually, I can't replicate this problem. In a clean VM with newly built >> > /var/log/packages/fltk-1.3.3-x86_64-2 installed I see: >> > >> > Scanning dependencies of target example_osgviewerFLTK >> > [ 80%] Building CXX object >> > examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/ >> osgviewerFLTK.cpp.o >> > [ 81%] Linking CXX executable ../../bin/osgviewerFLTK >> > [ 81%] Built target example_osgviewerFLTK >> > >> > If I run (still in the VM so with limited GL capability) the command: >> > strings /usr/lib64/libfltk_gl.so.1.3 |less >> > and search for XFont, I see a single reference: >> > glXUseXFont >> > >> > In a real machine with Nvidia graphics and binary driver, the same >> > search reveals: >> > _ZN18Fl_XFont_On_Demand5valueEv >> > glGenLists >> > glXUseXFont >> > >> > Seeing that difference in varying graphics environments (although >> > compilation continues to completion in both these particular cases) I >> > wonder if the issue you're seeing is due to your (perhaps even more >> > different) graphics environment (Intel, nouveau, ...)? That wouldn't >> > necessarily explain why it worked for you with updated fltk though. Or, >> > maybe your fltk-1.3.3 was built some time ago - _before_ you updated >> > your graphics hardware/driver (so failed) but your fltk-1.3.4-2 >> > succeeded because you just built it now using the updated graphics >> > hardware/driver. >> > >> > Anyway, I'll email the fltk maintainer and ask if he's prepared to >> > upgrade the version. My stored source tarball fltk-1.3.3-source.tar.gz >> > is dated Nov 4 2014 i.e. it's a pretty old version. However fltk seems >> > to have a ton of dependent SlackBuilds so checking all of them with a >> > newer fltk won't be trivial. >> > >> >> Just as well I did some more checking before emailing the maintainer. It >> turns out that the SBo fltk is excess to requirements since there is >> already an fltk package in stock Slackware's extra. I guess that means >> the version in extra won't be updated. However the version at SBo is a >> mystery - from the git log it seems to be renamed some time ago from >> fltk13 but I don't understand why it still exists at all now that we >> have the fltk in extra. >> >> I see from your original email that you were using an SBo build >> (fltk-1.3.3-x86_64-2_SBo.tgz). I wonder if your OpenSceneGraph would >> succeed if you removed that version and installed the version from >> extra? I guess you're happy anyway having upgraded your local fltk and >> built OSG with that but it would be nice to know whether you could build >> it with the fltk from extra (as it does here). >> >> chris >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Sun May 27 12:05:02 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 27 May 2018 22:05:02 +1000 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: Message-ID: <1a59384b-a319-e563-884c-baa34ffc8c19@iinet.net.au> On 27/05/18 21:05, Konrad J Hambrick wrote: > p.s.? Most of all ... thanks for all the time you've spent on this. > > And moreover, as you noted, digging into the packages dependent on fltk > is a huge task. > > What can I do to help ? > > -- kjh > > These are packages where fltk is REQUIRED ( not to mention OPTIONAL > dependencies ): > > # hoorex -m fltk |gawk '{ for ( i = 1 ; i <= NF; i ++ ){ print "?? " $i }}' > Nice to see hoorex in use. FYI, the same single column output from hoorex is possible without using gawk via the -1 option i.e. hoorex -m1 fltk Before I found the official version of fltk in extra, I had already done a build test of all the dependents - although just direct dependents (no -m option). That still resulted in 28 packages and building them all was much faster than I imagined, since most of the packages are smallish builds and my build tool will take a list of packages and build them all in one go - assuming no problems on the way. However at the end of it, I discovered that the build system had replaced my new fltk-1.3.4-2 with fltk-1.3.3 so it was not a test of building with 1.3.4-2 after all. Looking into how that happened is when I stumbled onto existence of the official fltk in extra. I didn't go through the build exercise again with 1.3.4-2, thinking that perhaps your OSG build problem might be fixed anyway if you used the official version rather than your SBo version. Did you have a chance to try that? I'll go through the build job again anyway, this time ensuring fltk-1.3.4-2 is used. chris > ? fltk > ? lalnview > ? oblige > ? flrig > ? butt > ? alsamixergui > ? flSynclient > ? glbsp > ? horgand > ? lmms > ? edelib > ? oblige-legacy4 > ? xdiskusage > ? Pixie > ? tapiir > ? ede > ? rakarrack > ? sfc > ? dillo > ? vocoder > ? zynaddsubfx > ? pyfltk > ? fldigi > ? yoshimi > ? eureka > ? fgrun > ? htmldoc > ? flpsed > ? seaview > ? chm2pdf > > > On Sun, May 27, 2018 at 5:46 AM, Konrad J Hambrick > wrote: > > Chris -- > > Dang !? > > I should have noted that I am running Slackware64 14.2 + Multilib + > NVIDIA-Linux-x86_64-390.59.run > > And looking at my SlackBuild Wrapper ( attached ), I probably should > have noted the OPTIONAL Dependencies too. > > Note the nvidia-texture-tools Package. > # > # built and installed B80525 > # > # dcmtk??????????????? - dcmtk-3.6.3-x86_64-1_SBo > # libgta?????????????? - libgta-1.0.8-x86_64-1_SBo > # nvidia-texture-tools - nvidia-texture-tools-2.1.1-x86_64-1_SBo > # slurm??????????????? x not needed > # openmpi????????????? - openmpi-2.1.1-x86_64-1_SBo > # python-twisted?????? x skipped - too many dependencies > # VTK????????????????? - VTK-8.1.1-x86_64-1_SBo > # FreeImage??????????? - FreeImage-3.17.0-x86_64-1_SBo > # tbb????????????????? - tbb-2018u3-x86_64-1_SBo > # gl2ps??????????????? - gl2ps-1.3.7-x86_64-1_SBo > # OpenCASCADE????????? - OpenCASCADE-6.9.1-x86_64-3_SBo > # SDL2???????????????? - SDL2-2.0.8-x86_64-1_SBo > # > > Also note that the SlackBuild wrapper generates a log file for each > VERSION + TAG so I do have the full log > where the initial osg build failed with fltk-1.3.3 ( not TOO huge at > 266,487 bytes ) > > Thanks for looking at this Chris and thanks for the info about the > Official extra/fltk/ Package ! > > -- kjh > > > > On Sun, May 27, 2018 at 2:31 AM, Christoph Willing > > wrote: > > On 27/05/18 12:46, Christoph Willing wrote: > > On 27/05/18 10:25, Christoph Willing wrote: > >> On 27/05/18 05:46, Konrad J Hambrick wrote: > > [snip] > >> > >>> Here is another one ... I had the OPTIONAL Package > >>> fltk-1.3.3-x86_64-2_SBo.tgz installed for the flSynclient > Package. > >>> > >>> It turns out that OpenSceneGraph will build > example_osgviewerFLTK if > >>> FLTK is installed. > >>> > >>> However it fails for fltk-1.3.3. > >>> > >>> Here is the tail of my build log: > >>> > >>> Scanning dependencies of target example_osgviewerFLTK > >>> [100%] Building CXX object > >>> > examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/osgviewerFLTK.cpp.o > >>> [100%] Linking CXX executable ../../bin/osgviewerFLTK > >>> > /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../lib64/libfltk_gl.so: > >>> undefined reference to `Fl_XFont_On_Demand::value()' > >>> collect2: error: ld returned 1 exit status > >>> > examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/build.make:123: > >>> recipe for target 'bin/osgviewerFLTK' failed > >>> make[2]: *** [bin/osgviewerFLTK] Error 1 > >>> CMakeFiles/Makefile2:18128: recipe for target > >>> > 'examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all' failed > >>> make[1]: *** > >>> > [examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all] Error > 2 > >>> Makefile:127: recipe for target 'all' failed > >>> make: *** [all] Error 2 > >>> > >>> I upgraded FLTK to version 1.3.4-2 ( yes ... it is 'dash 2' > ) and > >>> OpenSceneGraph compiled and installed and runs properly now. > >>> > >> I thought I'd covered all the bases before updating the OSG > version but > >> missed this one (obviously!). I'll look at it during the week. > >> > > > > Actually, I can't replicate this problem. In a clean VM with > newly built > > /var/log/packages/fltk-1.3.3-x86_64-2 installed I see: > > > > Scanning dependencies of target example_osgviewerFLTK > > [ 80%] Building CXX object > > > examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/osgviewerFLTK.cpp.o > > [ 81%] Linking CXX executable ../../bin/osgviewerFLTK > > [ 81%] Built target example_osgviewerFLTK > > > > If I run (still in the VM so with limited GL capability) the > command: > >? ? ?strings /usr/lib64/libfltk_gl.so.1.3 |less > > and search for XFont, I see a single reference: > >? ? ?glXUseXFont > > > > In a real machine with Nvidia graphics and binary driver, the same > > search reveals: > >? ? ?_ZN18Fl_XFont_On_Demand5valueEv > >? ? ?glGenLists > >? ? ?glXUseXFont > > > > Seeing that difference in varying graphics environments (although > > compilation continues to completion in both these particular > cases) I > > wonder if the issue you're seeing is due to your (perhaps even > more > > different) graphics environment (Intel, nouveau, ...)? That > wouldn't > > necessarily explain why it worked for you with updated fltk > though. Or, > > maybe your fltk-1.3.3 was built some time ago - _before_ you > updated > > your graphics hardware/driver (so failed) but your fltk-1.3.4-2 > > succeeded because you just built it now using the updated graphics > > hardware/driver. > > > > Anyway, I'll email the fltk maintainer and ask if he's prepared to > > upgrade the version. My stored source tarball > fltk-1.3.3-source.tar.gz > > is dated Nov 4 2014 i.e. it's a pretty old version. However > fltk seems > > to have a ton of dependent SlackBuilds so checking all of them > with a > > newer fltk won't be trivial. > > > > Just as well I did some more checking before emailing the > maintainer. It > turns out that the SBo fltk is excess to requirements since there is > already an fltk package in stock Slackware's extra. I guess that > means > the version in extra won't be updated. However the version at > SBo is a > mystery - from the git log it seems to be renamed some time ago from > fltk13 but I don't understand why it still exists at all now that we > have the fltk in extra. > > I see from your original email that you were using an SBo build > (fltk-1.3.3-x86_64-2_SBo.tgz). I wonder if your OpenSceneGraph would > succeed if you removed that version and installed the version from > extra? I guess you're happy anyway having upgraded your local > fltk and > built OSG with that but it would be nice to know whether you > could build > it with the fltk from extra (as it does here). > > chris > > > > > > _______________________________________________ > 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 kjhambrick at gmail.com Sun May 27 12:40:25 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sun, 27 May 2018 07:40:25 -0500 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: <1a59384b-a319-e563-884c-baa34ffc8c19@iinet.net.au> References: <1a59384b-a319-e563-884c-baa34ffc8c19@iinet.net.au> Message-ID: Chris -- I couldn't 'live' without hoorex :) Thanks for the `hoorex -m1` tip ( and of course thanks for hoorex :) ! Anyhow ... > ... thinking that perhaps your OSG build problem might be fixed anyway > if you used the official version rather than your SBo version. > > Did you have a chance to try that? I am sorry, I missed that suggestion in your earlier email. Babysitting my Granddaughter now ... I'll set up a build for later today and let you know. -- kjh On Sun, May 27, 2018 at 7:05 AM, Christoph Willing < chris.willing at iinet.net.au> wrote: > On 27/05/18 21:05, Konrad J Hambrick wrote: > > p.s. Most of all ... thanks for all the time you've spent on this. > > > > And moreover, as you noted, digging into the packages dependent on fltk > > is a huge task. > > > > What can I do to help ? > > > > -- kjh > > > > These are packages where fltk is REQUIRED ( not to mention OPTIONAL > > dependencies ): > > > > # hoorex -m fltk |gawk '{ for ( i = 1 ; i <= NF; i ++ ){ print " " $i > }}' > > > > Nice to see hoorex in use. FYI, the same single column output from > hoorex is possible without using gawk via the -1 option i.e. > hoorex -m1 fltk > > Before I found the official version of fltk in extra, I had already done > a build test of all the dependents - although just direct dependents (no > -m option). That still resulted in 28 packages and building them all was > much faster than I imagined, since most of the packages are smallish > builds and my build tool will take a list of packages and build them all > in one go - assuming no problems on the way. > > However at the end of it, I discovered that the build system had > replaced my new fltk-1.3.4-2 with fltk-1.3.3 so it was not a test of > building with 1.3.4-2 after all. Looking into how that happened is when > I stumbled onto existence of the official fltk in extra. I didn't go > through the build exercise again with 1.3.4-2, thinking that perhaps > your OSG build problem might be fixed anyway if you used the official > version rather than your SBo version. Did you have a chance to try that? > > I'll go through the build job again anyway, this time ensuring > fltk-1.3.4-2 is used. > > chris > > > fltk > > lalnview > > oblige > > flrig > > butt > > alsamixergui > > flSynclient > > glbsp > > horgand > > lmms > > edelib > > oblige-legacy4 > > xdiskusage > > Pixie > > tapiir > > ede > > rakarrack > > sfc > > dillo > > vocoder > > zynaddsubfx > > pyfltk > > fldigi > > yoshimi > > eureka > > fgrun > > htmldoc > > flpsed > > seaview > > chm2pdf > > > > > > On Sun, May 27, 2018 at 5:46 AM, Konrad J Hambrick > > wrote: > > > > Chris -- > > > > Dang ! > > > > I should have noted that I am running Slackware64 14.2 + Multilib + > > NVIDIA-Linux-x86_64-390.59.run > > > > And looking at my SlackBuild Wrapper ( attached ), I probably should > > have noted the OPTIONAL Dependencies too. > > > > Note the nvidia-texture-tools Package. > > # > > # built and installed B80525 > > # > > # dcmtk - dcmtk-3.6.3-x86_64-1_SBo > > # libgta - libgta-1.0.8-x86_64-1_SBo > > # nvidia-texture-tools - nvidia-texture-tools-2.1.1-x86_64-1_SBo > > # slurm x not needed > > # openmpi - openmpi-2.1.1-x86_64-1_SBo > > # python-twisted x skipped - too many dependencies > > # VTK - VTK-8.1.1-x86_64-1_SBo > > # FreeImage - FreeImage-3.17.0-x86_64-1_SBo > > # tbb - tbb-2018u3-x86_64-1_SBo > > # gl2ps - gl2ps-1.3.7-x86_64-1_SBo > > # OpenCASCADE - OpenCASCADE-6.9.1-x86_64-3_SBo > > # SDL2 - SDL2-2.0.8-x86_64-1_SBo > > # > > > > Also note that the SlackBuild wrapper generates a log file for each > > VERSION + TAG so I do have the full log > > where the initial osg build failed with fltk-1.3.3 ( not TOO huge at > > 266,487 bytes ) > > > > Thanks for looking at this Chris and thanks for the info about the > > Official extra/fltk/ Package ! > > > > -- kjh > > > > > > > > On Sun, May 27, 2018 at 2:31 AM, Christoph Willing > > > > wrote: > > > > On 27/05/18 12:46, Christoph Willing wrote: > > > On 27/05/18 10:25, Christoph Willing wrote: > > >> On 27/05/18 05:46, Konrad J Hambrick wrote: > > > [snip] > > >> > > >>> Here is another one ... I had the OPTIONAL Package > > >>> fltk-1.3.3-x86_64-2_SBo.tgz installed for the flSynclient > > Package. > > >>> > > >>> It turns out that OpenSceneGraph will build > > example_osgviewerFLTK if > > >>> FLTK is installed. > > >>> > > >>> However it fails for fltk-1.3.3. > > >>> > > >>> Here is the tail of my build log: > > >>> > > >>> Scanning dependencies of target example_osgviewerFLTK > > >>> [100%] Building CXX object > > >>> > > examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/ > osgviewerFLTK.cpp.o > > >>> [100%] Linking CXX executable ../../bin/osgviewerFLTK > > >>> > > /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../.. > /../lib64/libfltk_gl.so: > > >>> undefined reference to `Fl_XFont_On_Demand::value()' > > >>> collect2: error: ld returned 1 exit status > > >>> > > examples/osgviewerFLTK/CMakeFiles/example_ > osgviewerFLTK.dir/build.make:123: > > >>> recipe for target 'bin/osgviewerFLTK' failed > > >>> make[2]: *** [bin/osgviewerFLTK] Error 1 > > >>> CMakeFiles/Makefile2:18128: recipe for target > > >>> > > 'examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all' > failed > > >>> make[1]: *** > > >>> > > [examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/all] > Error > > 2 > > >>> Makefile:127: recipe for target 'all' failed > > >>> make: *** [all] Error 2 > > >>> > > >>> I upgraded FLTK to version 1.3.4-2 ( yes ... it is 'dash 2' > > ) and > > >>> OpenSceneGraph compiled and installed and runs properly now. > > >>> > > >> I thought I'd covered all the bases before updating the OSG > > version but > > >> missed this one (obviously!). I'll look at it during the week. > > >> > > > > > > Actually, I can't replicate this problem. In a clean VM with > > newly built > > > /var/log/packages/fltk-1.3.3-x86_64-2 installed I see: > > > > > > Scanning dependencies of target example_osgviewerFLTK > > > [ 80%] Building CXX object > > > > > examples/osgviewerFLTK/CMakeFiles/example_osgviewerFLTK.dir/ > osgviewerFLTK.cpp.o > > > [ 81%] Linking CXX executable ../../bin/osgviewerFLTK > > > [ 81%] Built target example_osgviewerFLTK > > > > > > If I run (still in the VM so with limited GL capability) the > > command: > > > strings /usr/lib64/libfltk_gl.so.1.3 |less > > > and search for XFont, I see a single reference: > > > glXUseXFont > > > > > > In a real machine with Nvidia graphics and binary driver, the > same > > > search reveals: > > > _ZN18Fl_XFont_On_Demand5valueEv > > > glGenLists > > > glXUseXFont > > > > > > Seeing that difference in varying graphics environments > (although > > > compilation continues to completion in both these particular > > cases) I > > > wonder if the issue you're seeing is due to your (perhaps even > > more > > > different) graphics environment (Intel, nouveau, ...)? That > > wouldn't > > > necessarily explain why it worked for you with updated fltk > > though. Or, > > > maybe your fltk-1.3.3 was built some time ago - _before_ you > > updated > > > your graphics hardware/driver (so failed) but your fltk-1.3.4-2 > > > succeeded because you just built it now using the updated > graphics > > > hardware/driver. > > > > > > Anyway, I'll email the fltk maintainer and ask if he's > prepared to > > > upgrade the version. My stored source tarball > > fltk-1.3.3-source.tar.gz > > > is dated Nov 4 2014 i.e. it's a pretty old version. However > > fltk seems > > > to have a ton of dependent SlackBuilds so checking all of them > > with a > > > newer fltk won't be trivial. > > > > > > > Just as well I did some more checking before emailing the > > maintainer. It > > turns out that the SBo fltk is excess to requirements since > there is > > already an fltk package in stock Slackware's extra. I guess that > > means > > the version in extra won't be updated. However the version at > > SBo is a > > mystery - from the git log it seems to be renamed some time ago > from > > fltk13 but I don't understand why it still exists at all now > that we > > have the fltk in extra. > > > > I see from your original email that you were using an SBo build > > (fltk-1.3.3-x86_64-2_SBo.tgz). I wonder if your OpenSceneGraph > would > > succeed if you removed that version and installed the version > from > > extra? I guess you're happy anyway having upgraded your local > > fltk and > > built OSG with that but it would be nice to know whether you > > could build > > it with the fltk from extra (as it does here). > > > > chris > > > > > > > > > > > > _______________________________________________ > > 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 chris.willing at linux.com Sun May 27 14:13:41 2018 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 28 May 2018 00:13:41 +1000 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: <1a59384b-a319-e563-884c-baa34ffc8c19@iinet.net.au> Message-ID: On 27/05/18 22:40, Konrad J Hambrick wrote: > On Sun, May 27, 2018 at 7:05 AM, Christoph Willing > > wrote: > > > I'll go through the build job again anyway, this time ensuring > fltk-1.3.4-2 is used. > I just rebuilt all packages with a direct dependency on fltk using fltk-1.3.4-2. There were no problems at all with the build them but I'm not going to test how they work - just presume they do. chris From matteo.bernardini at gmail.com Sun May 27 14:30:06 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 27 May 2018 16:30:06 +0200 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: <1a59384b-a319-e563-884c-baa34ffc8c19@iinet.net.au> Message-ID: 2018-05-27 16:13 GMT+02:00 Christoph Willing : > I just rebuilt all packages with a direct dependency on fltk using > fltk-1.3.4-2. There were no problems at all with the build them but I'm > not going to test how they work - just presume they do. the best course of action now should be to propose the upgrade to the fltk maintainer on SBo telling him about the tests you have done... From kjhambrick at gmail.com Mon May 28 15:40:43 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Mon, 28 May 2018 10:40:43 -0500 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: <1a59384b-a319-e563-884c-baa34ffc8c19@iinet.net.au> Message-ID: Chris -- Are we all good now ? Do I need to do any testing for you ? Thanks ! -- kjh On Sun, May 27, 2018 at 9:30 AM, Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > 2018-05-27 16:13 GMT+02:00 Christoph Willing : > > I just rebuilt all packages with a direct dependency on fltk using > > fltk-1.3.4-2. There were no problems at all with the build them but I'm > > not going to test how they work - just presume they do. > > the best course of action now should be to propose the upgrade to the > fltk maintainer on SBo telling him about the tests you have done... > _______________________________________________ > 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 chris.willing at iinet.net.au Mon May 28 21:15:01 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 29 May 2018 07:15:01 +1000 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: <1a59384b-a319-e563-884c-baa34ffc8c19@iinet.net.au> Message-ID: On 29/05/18 01:40, Konrad J Hambrick wrote: > Chris -- > > Are we all good now ? > > Do I need to do any testing for you ? > Well, since you have an fltk package that works for you (allows OpenSceneGraph to build), you could stop there. However I am still interested in whether OSG would build with the fltk in the Slackware extra directory. I notice this one includes a patch (Fl_XFont_On_Demand.patch.gz) named suspiciously like the error you first reported: /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../lib64/libfltk_gl.so:undefined reference to `Fl_XFont_On_Demand::value()' collect2: error: ld returned 1 exit status Therefore I wonder if you replaced your existing fltk with the standard one in extra, whether you could still build OpenSceneGraph. It works here so I'm loathe to ask the SBo version's maintainer to update to 1.3.4-2 (even though I've tested it and found no ill-effects). chris From kjhambrick at gmail.com Mon May 28 21:53:02 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Mon, 28 May 2018 16:53:02 -0500 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: <1a59384b-a319-e563-884c-baa34ffc8c19@iinet.net.au> Message-ID: OK Chris. I'll build and install fltk from extra/ and then rebuild the dependent programs and let you know. Thanks ! -- kjh On Mon, May 28, 2018 at 4:15 PM, Christoph Willing < chris.willing at iinet.net.au> wrote: > On 29/05/18 01:40, Konrad J Hambrick wrote: > > Chris -- > > > > Are we all good now ? > > > > Do I need to do any testing for you ? > > > Well, since you have an fltk package that works for you (allows > OpenSceneGraph to build), you could stop there. > > However I am still interested in whether OSG would build with the fltk > in the Slackware extra directory. I notice this one includes a patch > (Fl_XFont_On_Demand.patch.gz) named suspiciously like the error you > first reported: > > /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../.. > /../lib64/libfltk_gl.so:undefined > reference to `Fl_XFont_On_Demand::value()' > collect2: error: ld returned 1 exit status > > Therefore I wonder if you replaced your existing fltk with the standard > one in extra, whether you could still build OpenSceneGraph. It works > here so I'm loathe to ask the SBo version's maintainer to update to > 1.3.4-2 (even though I've tested it and found no ill-effects). > > chris > _______________________________________________ > 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 kjhambrick at gmail.com Wed May 30 00:39:49 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Tue, 29 May 2018 19:39:49 -0500 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: <1a59384b-a319-e563-884c-baa34ffc8c19@iinet.net.au> Message-ID: Chris -- Whew ! That was a lot of SlackBuilding ; upgradepkging ; ldconfiging ! Bottom Line: OpenSceneGraph builds ; installs ; runs fine with fltk 1.3.3 + the Slackware patch from extra/ ! Below are the packages I rebuilt and installed -- from extra/fltk-1.3.3 all the way thru postgis-2.4.4. Now what ??? -- kjh # ver fltk dcmtk libgta nvidia-texture-tools openmpi VTK FreeImage tbb gl2ps OpenCASCADE SDL2 OpenSceneGraph CGAL SFCGAL postgis -rw-r--r-- 1 root root 12589 May 29 15:44 /var/log/packages/fltk-1.3.3- x86_64-2_extra_kjh_B80529 -rw-r--r-- 1 root root 42567 May 29 16:09 /var/log/packages/dcmtk-3.6.3- x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 4487 May 29 16:09 /var/log/packages/libgta-1.0. 8-x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 1522 May 29 16:10 /var/log/packages/nvidia- texture-tools-2.1.1-x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 33842 May 29 16:19 /var/log/packages/openmpi-2.1. 1-x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 178330 May 29 17:35 /var/log/packages/VTK-8.1.1- x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 3795 May 29 17:37 /var/log/packages/FreeImage-3. 17.0-x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 5461 May 29 17:38 /var/log/packages/tbb-2018u3- x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 1108 May 29 17:39 /var/log/packages/gl2ps-1.3.7- x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 3819183 May 29 18:31 /var/log/packages/OpenCASCADE- 6.9.1-x86_64-3_SBo_kjh_B80529_test -rw-r--r-- 1 root root 4816 May 29 18:32 /var/log/packages/SDL2-2.0.8- x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 34589 May 29 19:18 /var/log/packages/ OpenSceneGraph-3.5.5-x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 163750 May 29 19:20 /var/log/packages/CGAL-4.11.1- x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 5684 May 29 19:29 /var/log/packages/SFCGAL-1.3. 5-x86_64-1_SBo_kjh_B80529_test -rw-r--r-- 1 root root 18787 May 29 19:30 /var/log/packages/postgis-2.4. 4-x86_64-1_SBo_kjh_B80529_test On Mon, May 28, 2018 at 4:53 PM, Konrad J Hambrick wrote: > OK Chris. > > I'll build and install fltk from extra/ and then rebuild the dependent > programs and let you know. > > Thanks ! > > -- kjh > > > On Mon, May 28, 2018 at 4:15 PM, Christoph Willing < > chris.willing at iinet.net.au> wrote: > >> On 29/05/18 01:40, Konrad J Hambrick wrote: >> > Chris -- >> > >> > Are we all good now ? >> > >> > Do I need to do any testing for you ? >> > >> Well, since you have an fltk package that works for you (allows >> OpenSceneGraph to build), you could stop there. >> >> However I am still interested in whether OSG would build with the fltk >> in the Slackware extra directory. I notice this one includes a patch >> (Fl_XFont_On_Demand.patch.gz) named suspiciously like the error you >> first reported: >> >> /usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../ >> lib64/libfltk_gl.so:undefined >> reference to `Fl_XFont_On_Demand::value()' >> collect2: error: ld returned 1 exit status >> >> Therefore I wonder if you replaced your existing fltk with the standard >> one in extra, whether you could still build OpenSceneGraph. It works >> here so I'm loathe to ask the SBo version's maintainer to update to >> 1.3.4-2 (even though I've tested it and found no ill-effects). >> >> chris >> _______________________________________________ >> 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 chris.willing at iinet.net.au Wed May 30 02:59:02 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 30 May 2018 12:59:02 +1000 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: <1a59384b-a319-e563-884c-baa34ffc8c19@iinet.net.au> Message-ID: On 30/05/18 10:39, Konrad J Hambrick wrote: > Chris -- > > Whew !? That was a lot of SlackBuilding ; upgradepkging ; ldconfiging ! > > Bottom Line:? OpenSceneGraph builds ; installs ; runs fine with fltk > 1.3.3 + the Slackware patch from extra/ ! > > Below are the packages I rebuilt and installed -- from extra/fltk-1.3.3 > all the way thru postgis-2.4.4. > > Now what ??? > Thanks for all that - and good that it all works. What it all means (I think) is that: 1. the binary 1.3.3 from extra will also work i.e. no need to build an SBo version at all 2. the existing SBo version would also probably work unpatched if you rebuilt it now. It actually has a sed line which emulates the patch from extra and I suspect that the version you first used (which created the error you originally reported building OSG) was built before that sed line was added to the SlackBuild. We could confirm that theory by checking file dates inside that "bad" fltk package (if you still had it) and compare it with the date that the sed line was added to the SlackBuild (using the SBo git history). Life's too short for all that though - it works! chris From kjhambrick at gmail.com Wed May 30 10:05:51 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Wed, 30 May 2018 05:05:51 -0500 Subject: [Slackbuilds-users] Odd Directory Name in OpenSceneGraph-3.5.5.tar.gz In-Reply-To: References: <1a59384b-a319-e563-884c-baa34ffc8c19@iinet.net.au> Message-ID: Chris -- Yes, I believe I'll stand pat here :) For the record, I installed fltk from SBo on 2016-02-19 but the SBo fltk.Slackuild was updated on 2016-07-06 and I do see the sed command. -- kjh These are the removed fltk packages on my System # cd /var/log/removed_packages # ls -lart fltk* -rw-r--r-- 1 root root 12420 Feb 19 2016 fltk-1.3.3-x86_64-2_SBo-upgraded-2018-05-26,12:38:37 -rw-r--r-- 1 root root 12495 May 26 12:38 fltk-1.3.4_2-x86_64-1_SBo-upgraded-2018-05-26,14:06:19 -rw-r--r-- 1 root root 12503 May 26 14:06 fltk-1.3.4.2-x86_64-1_SBo_kjh-upgraded-2018-05-29,15:44:47 And from my local SBo 14.2 `git clone` directory # cd /home/dld/slackbuilds/14.2/libraries/fltk # ls -la total 52 drwxr-xr-x 2 root root 4096 Nov 14 2016 . drwxr-xr-x 994 root root 32768 May 25 21:11 .. -rw-r--r-- 1 root root 540 Jul 6 2016 README -rw-r--r-- 1 root root 3891 Jul 6 2016 fltk.SlackBuild -rw-r--r-- 1 root root 268 Jul 6 2016 fltk.info -rw-r--r-- 1 root root 1044 Nov 14 2016 slack-desc And this is the history of fltk in SBo from the git log: # grep ' fltk ' 14.2-GitLog-all.txt |getfield -tC -c1-4 -w20,10,6 2016-11-13 22:18:16 |libraries |fltk |Fix slack-desc. 2016-01-16 01:12:53 |libraries |fltk |Renamed from libraries/fltk13. 2016-01-15 23:19:49 |libraries |fltk |Removed fltk-1.1.10. 2015-08-07 23:27:44 |libraries |fltk |Patched SlackBuild. 2013-11-13 21:55:14 |network |dillo |Added note about fltk 2012-09-02 08:51:42 |libraries |fltk |Patched to fix underlinking. 2010-06-04 01:06:32 |libraries |fltk |Misc automated cleanups. 2010-05-19 02:36:07 |libraries |fltk |Fixed for bash4. 2010-05-13 00:29:25 |libraries |fltk |Updated for version 1.1.10 2010-05-12 17:40:37 |libraries |fltk |Updated for version 1.1.9 2010-05-11 22:23:40 |libraries |fltk |Updated for version 1.1.9 2010-05-11 20:00:46 |libraries |fltk |Added to 12.0 repository 2010-04-08 19:29:30 |libraries |fltk |Updated download link in fltk.info On Tue, May 29, 2018 at 9:59 PM, Christoph Willing < chris.willing at iinet.net.au> wrote: > On 30/05/18 10:39, Konrad J Hambrick wrote: > > Chris -- > > > > Whew ! That was a lot of SlackBuilding ; upgradepkging ; ldconfiging ! > > > > Bottom Line: OpenSceneGraph builds ; installs ; runs fine with fltk > > 1.3.3 + the Slackware patch from extra/ ! > > > > Below are the packages I rebuilt and installed -- from extra/fltk-1.3.3 > > all the way thru postgis-2.4.4. > > > > Now what ??? > > > > Thanks for all that - and good that it all works. > > What it all means (I think) is that: > 1. the binary 1.3.3 from extra will also work i.e. no need to build an > SBo version at all > > 2. the existing SBo version would also probably work unpatched if you > rebuilt it now. It actually has a sed line which emulates the patch from > extra and I suspect that the version you first used (which created the > error you originally reported building OSG) was built before that sed > line was added to the SlackBuild. We could confirm that theory by > checking file dates inside that "bad" fltk package (if you still had it) > and compare it with the date that the sed line was added to the > SlackBuild (using the SBo git history). Life's too short for all that > though - it works! > > chris > _______________________________________________ > 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 z.coldplayer at gmail.com Thu May 31 18:42:34 2018 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Thu, 31 May 2018 22:42:34 +0400 Subject: [Slackbuilds-users] Batch update to Perl homepage/download URLs In-Reply-To: <85cabbf1-6216-cdac-eae5-63e238ac1a49@slackbuilds.org> References: <597927a4-ea7b-d2ee-2907-c5baea5bc4e5@chrisn.me.uk> <6321903b-a6e9-b015-34e8-37fef571423c@slackbuilds.org> <85cabbf1-6216-cdac-eae5-63e238ac1a49@slackbuilds.org> Message-ID: Kudos to Chris for the great work On Sun, 27 May 2018, 08:14 Willy Sudiarto Raharjo, wrote: > >> Can you send your PR to https://github.com/SlackBuildsOrg/slackbuilds/ > ? > >> It will be easier to merge :) > > > > Sorry, I didn't notice the GitHub mirror --- here you go: > > > > https://github.com/SlackBuildsOrg/slackbuilds/pull/111 > > and merged to my branch already > > Again, big thanks!! > > > -- > 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 idlemoor at slackbuilds.org Thu May 31 23:47:07 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Fri, 1 Jun 2018 00:47:07 +0100 Subject: [Slackbuilds-users] python/mock up for grabs In-Reply-To: <20180521123240.GA2405@pc21.mareichelt.com> References: <20180521123240.GA2405@pc21.mareichelt.com> Message-ID: <874ceddc-b031-12b1-5679-efd87b6502e4@slackbuilds.org> On 2018-05-21 13:32, Markus Reichelt wrote: > long story short: > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2018-February/020850.html Thanks Markus, I've pushed an update, but if somebody else is excited by unit testing, you can still have it :) -D. From idlemoor at slackbuilds.org Thu May 31 23:55:33 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Fri, 1 Jun 2018 00:55:33 +0100 Subject: [Slackbuilds-users] OpenCASCADE Download In-Reply-To: References: Message-ID: <9aa42b41-bf66-fc1b-5ada-8b0298a182e2@slackbuilds.org> On 2018-05-26 13:39, Matteo Bernardini wrote: > 2018-05-26 14:30 GMT+02:00 Konrad J Hambrick : >> David -- >> >> The OpenCASCADE Directory has been removed from ArchLinux Community >> Directory > thanks to you for reporting! > I mirrored the original download and pushed the new download link in > my branch on git. Thanks to both of you for the quick and effective fix! There is now a new version upstream, so I've pushed an update -- hope it's ok for everybody :) Cheers -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: