Re: [Slackbuilds-users] Help with guile-dbi.

[Duncan Roe]

Hi Vladimir,

On Fri, Jul 14, 2023 at 10:00:28AM +0800, Lockywolf wrote:
> Hello, everyone
>
> I really should ask for help at guile-dbi or guile's channels, but I
> have already done so, and they are not particularly active.
>
> So, I have two slackbuilds:
> https://gitlab.com/Lockywolf/lwfslackbuilds/-/tree/master/guile-dbi
> https://gitlab.com/Lockywolf/lwfslackbuilds/-/tree/master/guile-dbd-mysql
>
> They compile and install fine, however, using the guile-dbi module fails
> with a cryptic error:
>
> scheme@(guile-user)> (load "/dbi/dbi.scm")
> guile: symbol lookup error: /usr/lib64/libguile-dbi.so: undefined symbol: 
> lt_dlinit
>
> Indeed, nm'ing /usr/lib64/libguile-dbi.so I find lt_dlinit being U for
> "undefined".
>
> I have never seen such an error before. I know that libtool is not
> expected to be simple, but I have never ever seen libtool errors.
> Can someone sugges a debugging method?
>
>
> --
> Your sincerely,
> Vladimir Nikishkin (MiEr, lockywolf)
> (Laptop)
> ___
Not sure if this helps you but lt_dlinit is provided by libltdl.so (use -ldtl
in the build).

Found by grepping all files (but not symlinks) under /usr/lib64. In particular:

> php/build/libtool.m4:2671:  AC_CHECK_LIB(ltdl, lt_dlinit,
> grep: ./libltdl.so.7.3.1: binary file matches
> $ findit libltdl.so lt_dlinit
> Found lt_dlinit in libltdl.so at 0x7fcb8c28bfc0

(findit is from g...@github.com:duncan-roe/command_line_tools)

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Uploads to web.sourceforge.net

[Duncan Roe]

Hi Admins,

I uploaded a new directory called remake to my area last week but it hasn't yet
made it onto slackbuildsdirectlinks.

Is there some step I missed?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] slackbuilds up for grabs

[Duncan Roe]

On Mon, May 08, 2023 at 08:02:42AM +0200, Didier Spaier wrote:
> Le 08/05/2023 à 06:29, Franzen via SlackBuilds-users a écrit :
> > The find -L ... on this sources takes forever on my old hardware, and spits
> > thousand
> > "chmod: cannot operate on dangling symlink
> > './links/22/actions/fileview-preview.svg"
> > I changed it to
> > chmod -R u+w,go-w,a+rX-st .
> > and it's ready under one second.
> >
> > There are also some duplicate files(not much, but anyway), to replace them 
> > by
> > symlinks i added:
> > LASTSIZE=x
> > find $PKG -type f -printf '%s %p\n' | sort -n |
> > while read -r SIZE FILE; do
> >   # symlinks alse need some bytes, don't link under 10 bytes
> >   if [ "$SIZE" -gt 10 -a "$SIZE" == "$LASTSIZE" ]; then
> >     if [ "$(sha512sum $FILE | cut -d' ' -f1)" \
> >   == "$(sha512sum $LASTFILE | cut -d' ' -f1)" ] ; then
> >   ln -srf $FILE $LASTFILE
> >     fi
> >   fi
> >   LASTSIZE="$SIZE"; LASTFILE="$FILE"
> > done
>
> Thanks Johannes, I will take your changes.
>
> As an aside, I included this package in Slint so users be able to add 
> XFCE-4.18
> as packaged by George Vlahavas in
> http://slackware.uk/salix/x86_64/xfce4.18-15.0/ (with the same look) trying 
> just
> this command:
> slapt-get --install-set xfce
>
> Cheers,
> Didier
>
I'm a little concerned by the comment

  "symlinks alse need some bytes, don't link under 10 bytes"

Files occupy a multiple of 4K bytes. So replacing a 1-byte file with a symlink
will usually save 4KB. Occasionally it will bump the directory size by 4KB so
there is no saving.

I suggest symlinking should be unconditional.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20230128.1

[Duncan Roe]

On Tue, Jan 31, 2023 at 02:27:05AM +0300, Mohammad Matini wrote:
[...]
>
> One man's useful automation is another's inflexibility, and surprise :]
>
[...]
Indeed. That's why I suggest a line in the README would be best.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20230128.1

[Duncan Roe]

On Sun, Jan 29, 2023 at 04:36:26PM -0500, B. Watson wrote:
>
>
> On Sun, 29 Jan 2023, Andrew Clemons wrote:
>
> > This looks like you have not sourced /etc/profile.d/go.sh or
> > /etc/profile.d/go.csh after installing google-go-lang.
> > I get your error above if I try building containerd with gccgo.

That was it. Rather than log out/in (and lose my directory stack), I did:

> pushd /etc/profile.d
> LLCT # LLCT is aliased to `ls -AFlct --time-style=long-iso|head'
> . ladspa.sh
> . lv2.sh
> . vamp.sh
> . go.sh

since they had all changed since login.
>
> I got a question. If a SlackBuild needs a profile script to be
> sourced, why oh why doesn't it just source it, instead of requiring
> the user to log out and back in?
>
> If it's already been sourced, sure, you might end up with duplicates
> in $PATH or such, but that won't cause any harm. And it'll save a lot
> of headaches, and make automated mass-rebuilds a lot easier.

Ah well. The thing is, you have to source the profile script *in your terminal
session*: it's no use the SlackBuild or installpkg doing it because the
environment of the process running the command is lost on command completion.

Best might be a line in the README maybe like

> To use  without logging out and in, enter . /etc/profile.d/.sh

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20230128.1

[Duncan Roe]

Hi Andrew,

On Sun, Jan 29, 2023 at 06:04:10PM +0900, Andrew Clemons wrote:
> On 2023-01-28 13:42:10 +0900, andrew.clem...@gmail.com wrote:
> > On 2023-01-28 08:48:12 +0700, will...@slackbuilds.org wrote:
> > > hi all,
> > >
> > > this week we bumped google go lang to 1.19.5, which is needed by newer
> > > docker, but potentially break other scripts. If you happened to find them,
> > > please report them and we will try to fix it on next week update
> >
> > Sorry, there was a bit of a miscommunication here. I had not finished my
> > testing yet - I had only checked that all the docker stack was working.
> > I had not yet built google-go-lang on i586 or checked any other
> > builds that depend on google-go-lang, so I expect there are broken
> > scripts. I'll at least kick off rebuilding all the x86_64 downstream
> > scripts now.
>
> I only found one broken build - terraform. I sent a message to the maintainer.
> I also built google-go-lang on i586. It needed a small tweak which I've
> staged to my branch.
>
> While rebuilding the whole repo, I ran across these other broken builds:
>
> multimedia/ccextractor - ftbfs - email sent to maintainer
> ham/freedv - ftbfs - email sent to maintainer
>
>
> system/razergenie - ftbfs (maybe related to upgraded system/openrazer-daemon, 
> system/openrazer-kernel) maybe upgrade to 1.0.0?
> system/nix - ftbfs - (configure: error: Package requirements (lowdown >= 
> 0.9.0) were not met: No package 'lowdown' found)
>
> broken by upgraded fmt
>   desktop/waybar
>   libraries/folly
>
> matio - fails, hdf5 is too new - there is a newer upstream version, package 
> seems unmaintained on sbo
> audio/mpdscribble - completely broken after last update
> multimedia/musixmatch - only a snap now?
> network/havp - broken by clamav upgrade - maybe the patch from openbsd would 
> work
>
> broken by upgraded mpv:
>   graphics/qimgv
>   multimedia/minitube
>
> accessibility/magnus - fixed on Urchlay's branch
>
> function2 - tests failed (32bit) - 
> https://github.com/Naios/function2/issues/57
> libfabric - fails on 32bit
> nodejs - fails on 32bit
>
> Cheers,
> Andrew

I can't build containerd. Here's what I get:

> # github.com/containerd/containerd/cmd/ctr
> /usr/bin/ld: 
> /root/.cache/go-build/10/1057086cbae2f2af7483037be77189e85eb5442d0db4f28a061a3ac01c15820b-d(_go_.o):
>  in function `github_0com_1containerd_1containerd_1mount.Mount.Mount':
> /tmp/SBo/containerd-1.6.15/mount/fmountat_linux.go:120: undefined reference 
> to `syscall.runtime_BeforeFork'
> /usr/bin/ld: 
> /root/.cache/go-build/10/1057086cbae2f2af7483037be77189e85eb5442d0db4f28a061a3ac01c15820b-d(_go_.o):
>  in function `github.com/containerd/containerd/mount.forkAndMountat':
> /tmp/SBo/containerd-1.6.15/mount/fmountat_linux.go:132: undefined reference 
> to `syscall.runtime_AfterForkInChild'
> /usr/bin/ld: /tmp/SBo/containerd-1.6.15/mount/fmountat_linux.go:127: 
> undefined reference to `syscall.runtime_AfterFork'
> collect2: error: ld returned 1 exit status
> make: *** [Makefile:249: bin/ctr] Error 2

I saw a lot more errors earlier when the SB was modified to do make
-j$(($(nproc)+1)), including a gccgo compiler crash. Might be worth trying a
make -i.

Cheers ... Duncan
___
SlackBuilds-users mailing list
SlackBuilds-users@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] SBo HTTPS certificate seems to have expired

[Duncan Roe]

Hi Admins,

Firefox won't let me connect any more. It says:

> slackbuilds.org has a security policy called HTTP Strict Transport
> Security (HSTS), which means that Firefox can only connect to it
> securely. You can't add an exception to visit this site.

Google Chrome tells me that the cert expired in the last day and does let me in
(for now)

Please fix if you can,

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Explanation regarding reverting python3-mistune to build python-m2r

[Duncan Roe]

Hi Guys,

On Fri, Jan 27, 2023 at 10:38:36AM +0100, Arnaud wrote:
> >
> > Hi Duncan,
> >
> > I suggest simply removing python 3 support from python-m2r instead.
> > In that case, we do not need to update python2-mistune.
> >
> > If we really need python 3 support for python-m2r, I would suggest splitting
> > python-m2r into 2 packages: python2-m2r (v0.2.1), which depends on
> > python2-mistune (v0.8.4) python3-m2r (v0.3.1), which depends on
> > python3-mistune1 (v0.8.4) ??
> > As I mentioned, python3-mistune1 is meant to be an older version of
> > python3-mistune (at v2.0.4).
> >
> > ???After all, it was Yth's original intention to split mistune 
> > into
> > python2-mistune and python3-mistune.
> >
> > - Isaac
>
> I think it's the best thing to do.
> m2r is only used by Automat, and has been removed as requirement, because it's
> optional, and only used for generating better documentations.
>
> It is very possible that Automat uses the /usr/bin/m2r command, and not any
> Python import, so having the python2 version of m2r wouldn't prevent
> python3-automat for using it.
>
> Since m2r looks very unmaintained, and should still work while being python2
> only, it looks safe to remove the python3 support for it.
>
> As for mistune, the python2 version, stuck at 0.8.4, is only used by 
> python-m2r,
> so all this stays pretty legacy, and we have nice updated stuff on python3.
>
> My advice is that we don't need a python3-m2r or a python3-mistune1.
>
> Cheers,
>
>   - Yth.
>
Whatever you decide to do is fine with me - I was just trying to update all my
pre-15 builds.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Explanation regarding reverting python3-mistune to build python-m2r

[Duncan Roe]

Hi Isaac,

On Wed, Jan 25, 2023 at 02:56:43AM +0100, isaac...@isaacyu1.com wrote:
>
> Hi Duncan,
>
> Regarding python3-mistune at 2.0.4 (which caused python-m2r to fail to build):
>
> A few months ago, I uploaded python3-mistune at 2.0.4.
> The reason was because I wanted to update jupyter-nbconvert to versions >= 
> 7.0.0 (which required mistune >= 2.0.3).
>
> Previously, there was only 1 package named 'mistune' at SlackBuilds.org.
> Yth was the maintainer of mistune.
> I initially requested taking over mistune and updating it to 
> 2.0.4 (and for me to upload mistune1, a legacy package for python-m2r).
> However, Yth requested me to upload a python3-mistune package at 2.0.4.
> Yth also renamed mistune to python2-mistune (and kept it at 0.8.4).
> In other words, Yth suggested splitting the existing mistune package into 
> Python 2 and 3 versions, rather than updating mistune and uploading mistune1.
>
> Therefore, since python3-mistune is at 2.0.4, python-m2r does not build in 
> python 3.
> As you have shown, python-m2r requires python3-mistune at 0.8.4 instead.
> 
> Would you like me to upload a python3-mistune1 SlackBuild, at 0.8.4?
> There is only a python2-mistune at 0.8.4, maintained by Yth.
>
> That being said, if I upload python3-mistune1, it will conflict with my 
> existing python3-mistune.
> Therefore, I have to indicate that both python3-mistune1 and python3-mistune 
> cannot be installed in the same system at the same time.
>
> - Isaac
>
IN BRIEF:

After some tests, I suggest to
 - Upgrade python-m2r to 0.3.1
 - Recombine python2-mistune and python3-mistune to python-mistune-2.0.4

IN DETAIL:

I built python2-mistune 2.0.4 after eliminating error copying CHANGES.rst.

I built python-m2r-0.3.1. The python3 build gets the same error as in my
original post: fixed by not doing a python3 build. /usr/bin/m2r is a python2
program but I think that's OK: reverse dependency search finds 0 dependees for
python-m2r.

https://pypi.org/project/m2r/ Project description says "NO MORE UPDATES". Make
of that what you will.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Had to revert python3-mistune to build python-m2r

[Duncan Roe]

Hi,

python-m2r says it requires python2-mistune but it also seems to require
python3-mistune or maybe only uses it if available.

python3-mistune is at 2.0.4 while python2-mistune is at 0.8.4. python-m2r for
python3 gets build error

> ++ python3 setup.py install --root=/tmp/SBo/package-python-m2r
> Traceback (most recent call last):
>   File "/tmp/SBo/m2r-0.2.1/setup.py", line 14, in 
> from m2r import parse_from_file
>   File "/tmp/SBo/m2r-0.2.1/m2r.py", line 59, in 
> class RestBlockGrammar(mistune.BlockGrammar):
> AttributeError: module 'mistune' has no attribute 'BlockGrammar'

Reverting python3-mistune to 0.8.4 allowed me to build python-m2r (/usr/bin/m2r
starts #!/usr/bin/python3).

Cheeers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Trouble building graphviz 7.0.6

[Duncan Roe]

Hi again,

On Thu, Jan 19, 2023 at 10:10:00AM +1100, Duncan Roe wrote:
> Hi Guys,
>
> Sorry for late reply, have been a bit time-poor recently.
>
> On Mon, Jan 16, 2023 at 05:41:29AM -0600, Konrad J Hambrick wrote:
> > Duncan Roe --
> >
> > graphviz built fine here too.
> >
> > I attached the final graphviz configure output from my build logs to this
> > email.
> >
[...]
> >
> > On Mon, Jan 16, 2023 at 5:35 AM marav  wrote:
> >
[...}
> > >
> > > Le 16/01/2023 à 12:05, Arnaud via SlackBuilds-users a écrit :
> > > >> Hi,
[...]
>
> Thanks indeed for that! I found graphviz built fine on a slk15 VM here also.
>
> The difference is, on tha bare metal system where build fails, I have the 14.2
> build of mono.
>
> Will rebuild mono and deps then try again and report to list.
>
> Cheers ... Duncan.

graphviz still built fine on the VM after I installed mono.

I guess I need to upgrade all 14.2 SBs on the main system before I post again.

Except, I did notice graphviz ships a number of .la files. But then, so does
imagemagick from the Slackware distro - maybe it's a graphics thing.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Trouble building graphviz 7.0.6

[Duncan Roe]

Hi Guys,

Sorry for late reply, have been a bit time-poor recently.

On Mon, Jan 16, 2023 at 05:41:29AM -0600, Konrad J Hambrick wrote:
> Duncan Roe --
>
> graphviz built fine here too.
>
> I attached the final graphviz configure output from my build logs to this
> email.
>
> Maybe there is a clue in there ?
>
> One note, there are sure a lot of compiler warnings on Slackware64 15.0 ...
>
> HTH
>
> -- kjh
>
> On Mon, Jan 16, 2023 at 5:35 AM marav  wrote:
>
> > Hi,
> >
> > FYI
> > Ditto here, it builds fine (-current & 15.0)
> >
> > Cheers
> >
> > Le 16/01/2023 à 12:05, Arnaud via SlackBuilds-users a écrit :
> > >> Hi,
> > >>
> > >> Build originally failed when sed could not open /usr/lib64/
> > libglib-2.0.la.
> > >>
> > >> I tried messing around with Makefiles but I couldn't make it go away so
> > >> patched graphviz.SlackBuild to temporarily inject libglib-2.0.la into
> > the build
> > >> system.
> > >>
> > >> You are welcome to the patch, just say
> > >>
> > >> Cheers ... Duncan.
> > >
> > > That's strange, it had been tested and not only by me.
> > > I've reconstructed my build environment from scratch, and built graphviz.
> > >
> > > It worked perfectly fine.
> > >
> > > Could you tell me more about your setup, and the error itself ?
> > > Are the requirements up-to-date ?
> > >
> > > Cheers,
> > >
> > >   - Yth

> 
>
> graphviz-7.0.6 will be compiled with the following:
>
> options:
>   cgraph:Yes (always enabled)
>   digcola:   Yes
>   expat: Yes
>   fontconfig:Yes
>   freetype:  Yes
>   glut:  Yes
>   ann:   No (no ann.pc or ANN.h found)
>   gts:   Yes
>   ipsepcola: Yes
>   ltdl:  Yes
>   ortho: Yes
>   sfdp:  Yes
>   swig:  Yes ( 4.0.2 )
>   shared:Yes
>   static:No (disabled by default)
>   qt:Yes
>   x: Yes
>
> commands:
>   dot:   Yes (always enabled)
>   neato: Yes (always enabled)
>   fdp:   Yes (always enabled)
>   circo: Yes (always enabled)
>   twopi: Yes (always enabled)
>   gvpr:  Yes (always enabled)
>   gvmap: Yes (always enabled)
>   smyrna:Yes
>   gvedit:Yes
>
> plugin libraries:
>   dot_layout:Yes (always enabled)
>   neato_layout:  Yes (always enabled)
>   core:  Yes (always enabled)
>   devil: No (missing library)
>   gd:Yes
>   gdiplus:   No (disabled by default - Windows only)
>   gdk:   Yes
>   gdk_pixbuf:Yes
>   ghostscript:   Yes
>   gtk:   Yes
>   lasi:  No (lasi library not available)
>   pangocairo:Yes
>   poppler:   Yes
>   quartz:No (disabled by default - Mac only)
>   rsvg:  Yes
>   visio: Yes
>   webp:  Yes
>   xlib:  Yes
>
> language extensions:
>   gv_sharp:  No (mcs not available)
>   gv_d:  No (disabled by default - incomplete)
>   gv_go: Yes
>   gv_guile:  Yes
>   gv_io: No (disabled by default - no swig support yet)
>   gv_java:   No (missing header)
>   gv_javascript: No (disabled by default - incomplete)
>   gv_lua:Yes
>   gv_ocaml:  Yes
>   gv_perl:   Yes
>   gv_php:Yes
>   gv_python3:Yes
>   gv_R:  Yes
>   gv_ruby:   No (missing header)
>   gv_tcl:Yes
>
>   tcldot:Yes
>   tclpathplan:   Yes
>   gdtclft:   Yes
>
> Testing utilities:
>   criterion: No (Criterion unit testing framework not installed)

Thanks indeed for that! I found graphviz built fine on a slk15 VM here also.

The difference is, on tha bare metal system where build fails, I have the 14.2
build of mono.

Will rebuild mono and deps then try again and report to list.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Trouble building graphviz 7.0.6

[Duncan Roe]

Hi,

Build originally failed when sed could not open /usr/lib64/libglib-2.0.la.

I tried messing around with Makefiles but I couldn't make it go away so
patched graphviz.SlackBuild to temporarily inject libglib-2.0.la into the build
system.

You are welcome to the patch, just say

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] xbps slackbuild script

[Duncan Roe]

Hi Jacob,

On Sat, Oct 01, 2022 at 12:47:31PM -0700, Jacob Ulrich wrote:
> Hello Dave,
>
> This is an entirely new SlackBuild I put together myself, using the
> template by Rob Workman. The submissions portion of sbopkg.org wouldn???t
> work so I sent it here instead. Are you telling me there is some other form
> to submit a new script?
>
> best regards, Jacob Ulrich
>
[SNIP]

Have you tried https://slackbuilds.org/submit/ ?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [Slackbuilds-devel] New SBo Upload: xv

[Duncan Roe]

Hi Willy,

On Fri, Sep 30, 2022 at 06:32:23AM +0700, Willy Sudiarto Raharjo wrote:
> > But where is the source for extra? Do you know?
>
> it's in the source/extra directory
>
>
Finally found xv in extra/source. And it no longer builds!

To build with gcc 11.2.0 on Stable, xv needs the new patch in the rejected
New SBo Upload.

Should I start a thread on linuxquestions.org or what?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] smplayer 22.7.0 md5sum

[Duncan Roe]

Hi Alexander,

Suggest something strange with your installation.

/etc/profile.d/qt5.sh should put /usr/lib64/qt5 in root's PATH, making qt5
visible.

Cheers ... Duncan.

On Sat, Sep 10, 2022 at 05:07:54PM +, Alexander Grotewohl wrote:
> Apparently not.. the recent edits also remove
>
> QMAKE=qmake-qt5
>
> Since just 'qmake' doesn't seem to be in root's path it dies instantly..
>
> --
> Alexander Grotewohl
> https://dcclost.com
> 
> From: SlackBuilds-users  on behalf 
> of Alexander Grotewohl 
> Sent: Saturday, September 10, 2022 12:59 PM
> To: SlackBuilds.org Users List 
> Subject: Re: [Slackbuilds-users] smplayer 22.7.0 md5sum
>
> does it work the regular (manual) way? :)
> 
> From: SlackBuilds-users  on behalf 
> of Jim Diamond 
> Sent: Saturday, September 10, 2022 12:43:59 PM
> To: slackbuilds-users@slackbuilds.org 
> Subject: [Slackbuilds-users] smplayer 22.7.0 md5sum
>
> When trying to upgrade smplayer,
>
> # sboupgrade smplayer
> 
> --2022-09-10 13:42:03--  
> https://downloads.sourceforge.net/smplayer/smplayer-22.7.0.tar.bz2
> Resolving downloads.sourceforge.net (downloads.sourceforge.net)... 
> 204.68.111.105
> Connecting to downloads.sourceforge.net 
> (downloads.sourceforge.net)|204.68.111.105|:443... connected.
> HTTP request sent, awaiting response... 301 Moved Permanently
> Location: 
> https://sourceforge.net/projects/smplayer/files/SMPlayer/22.7.0/smplayer-22.7.0.tar.bz2/download?use_mirror=versaweb
>  [following]
> --2022-09-10 13:42:04--  
> https://sourceforge.net/projects/smplayer/files/SMPlayer/22.7.0/smplayer-22.7.0.tar.bz2/download?use_mirror=versaweb
> Resolving sourceforge.net (sourceforge.net)... 172.64.153.13, 104.18.34.243
> Connecting to sourceforge.net (sourceforge.net)|172.64.153.13|:443... 
> connected.
> HTTP request sent, awaiting response... 200 OK
> Length: unspecified [text/html]
> Saving to: ?smplayer-22.7.0.tar.bz2?
>
> smplayer-22.7.0.tar [<=> ] 170.90K   110KB/sin 1.6s
>
> 2022-09-10 13:42:07 (110 KB/s) - ?smplayer-22.7.0.tar.bz2? saved [174999]
>
> --2022-09-10 13:42:07--  
> ftp://slackware.uk/sbosrcarch/by-md5/8/8/88725d5c418cbf82f815bf1f09476cde/smplayer-22.7.0.tar.bz2
>=> ?smplayer-22.7.0.tar.bz2?
> Resolving slackware.uk (slackware.uk)... 216.119.155.61, 
> 2a02:2498:e004:2a::a861
> Connecting to slackware.uk (slackware.uk)|216.119.155.61|:21... connected.
> Logging in as anonymous ... Logged in!
> ==> SYST ... done.==> PWD ... done.
> ==> TYPE I ... done.  ==> CWD (1) 
> /sbosrcarch/by-md5/8/8/88725d5c418cbf82f815bf1f09476cde ...
> No such directory ?sbosrcarch/by-md5/8/8/88725d5c418cbf82f815bf1f09476cde?.
>
> Unable to download/verify source file(s) for smplayer:
>   md5sum failure for /usr/sbo/distfiles/smplayer-22.7.0.tar.bz2.
>
> Do you want to proceed? [n] Failures:
>   smplayer: md5sum failure for /usr/sbo/distfiles/smplayer-22.7.0.tar.bz2.
>
>
>
>
>
> Is this just me?
>
> Thanks.
>
> Jim
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Bad md5sum building python/python3-babel

[Duncan Roe]

On Tue, Jun 28, 2022 at 05:43:30PM +1000, Duncan Roe wrote:
> Hi,
>
> python3-babel.SlackBuild errorred out as below:
>
> > ++ python3 setup.py import_cldr
> > running import_cldr
> > Traceback (most recent call last):
[...]

Thanks for the offer Tim and thanks for trying the build 46&2.

The md5sum was good again when I downloaded this morning and the package built
OK.

Firefox gave me a warning that I hadn't seen before: "The connection is insecure
and the file might be corrupted". Weird eh?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Bad md5sum building python/python3-babel

[Duncan Roe]

Hi,

python3-babel.SlackBuild errorred out as below:

> ++ python3 setup.py import_cldr
> running import_cldr
> Traceback (most recent call last):
>   File "/tmp/SBo/babel-2.10.1/scripts/download_import_cldr.py", line 106, in 
> 
> main()
>   File "/tmp/SBo/babel-2.10.1/scripts/download_import_cldr.py", line 81, in 
> main
> while not is_good_file(zip_path):
>   File "/tmp/SBo/babel-2.10.1/scripts/download_import_cldr.py", line 66, in 
> is_good_file
> raise RuntimeError('Checksum mismatch: %r != %r'
> RuntimeError: Checksum mismatch: 
> 'cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e'
>  != 
> 'c64f3338e292962817b043dd11e9c47f533c9b70d432f83e80654e20f4937c72b37e66a60485df43f734b1ff94ebf0452547a063076917889303c9653b4d6ce5'
> Traceback (most recent call last):
>   File "/tmp/SBo/babel-2.10.1/setup.py", line 29, in 
> setup(
>   File "/usr/lib64/python3.9/site-packages/setuptools/__init__.py", line 153, 
> in setup
> return distutils.core.setup(**attrs)
>   File "/usr/lib64/python3.9/distutils/core.py", line 148, in setup
> dist.run_commands()
>   File "/usr/lib64/python3.9/distutils/dist.py", line 966, in run_commands
> self.run_command(cmd)
>   File "/usr/lib64/python3.9/distutils/dist.py", line 985, in run_command
> cmd_obj.run()
>   File "/tmp/SBo/babel-2.10.1/setup.py", line 26, in run
> subprocess.check_call([sys.executable, 'scripts/download_import_cldr.py'])
>   File "/usr/lib64/python3.9/subprocess.py", line 373, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['/usr/bin/python3', 
> 'scripts/download_import_cldr.py']' returned non-zero exit status 1.

When I checked the md5sum of cldr-common-41.0.zip it was wrong:

> 17:34:52$ echo d346710d2beb5133bdb1d14f966ae2cd;md5sum cldr-common-41.0.zip
> d346710d2beb5133bdb1d14f966ae2cd
> d41d8cd98f00b204e9800998ecf8427e  cldr-common-41.0.zip

I downloaded cldr-common-41.0.zip again, but had the same wrong md5sum as last
time.

Do you have a good file you can put up somewhere?

Could you contact the site and let them know about this?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] URL of site that lists Slackbuilds needing attention

[Duncan Roe]

Hi,

I lost the bookmark for a site that listed errors (like: URL is dead, URL
redirects to https ).

Can anyone provide it? Is it on the SBo site somewhere? (I did look)

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] python-template.SlackBuild comment/question, Re: mathics

[Duncan Roe]

On Mon, Mar 14, 2022 at 02:24:25AM -0700, David Chmelik wrote:
> Working on mathics.SlackBuild, I'm thinking does maybe maybe
> python-template.SlackBuild template need update?  Seems /any/all/ (almost
> 10+) Python programs I try anymore use pip, not setuptools (haven't seen it
> for years) so shouldn't both be in template(s)?  But, maybe pip isn't going
> to work right without pip2tgz...
>
> On 3/14/22 12:54 AM, David Chmelik wrote:
> > On 3/14/22 12:46 AM, Duncan Roe wrote:
> > > @David Chmelik: in your earlier email, you talked about mathics. I
> > > built Mathics
> > > 1.0. Now you are talking about Mathics-omnibus. As you say,
> > > Mathics-omnibus
> > > doesn't offer a source distro. pip2tgz can't build it. [...]
> > Mathics 1 SlackBuild existed since Slackware 14.2 and doesn't need
> > changes.
> >     Mathics-omnibus is newer stable Mathics full installation, which is
> > what I want to update SlackBuild for, so of course I'm talking about it:
> > many SlackBuilds will be being updated, sometimes with major changes.
> I mean Slackware 14.2 is barely older than Mathics 1, from 2 October 2016,
> w/newer commits (I didn't use) since that October 4th, until late 2020's
> 1.1.  Mathics 4 (though renamed still Mathics3) was mid-2021, so if anyone
> might prefer basic package, that would've been what to try.  I might make
> basic and/or full installation Mathics build scripts.  I want full but
> depends what others may want.
>     Incidentally 'pip3tgz Mathics3-4.0.0.tar.gz' builds (but crashes, so
> I'll be talking to upstream) but I avoid unusual build methods, like seems
> poor style when discord.SlackBuild gets .deb instead of .tar.gz (though
> pip2tgz may be better than plain pip because can/does specify .tar.gz.)  It
> may (or not--comments/suggestions/policies?) be best see if pip can be made
> to install to /tmp/SBo/package-mathics then do normal makepkg. W/pip2tgz
> would I put .tar.gz in mathics.info then use pip2tgz on it?
>
With pip2tgz, get the source archive from PyPI (may be tar.gz or zip) and
pip2tgz will make an actual package ready to install.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] python-template.SlackBuild comment/question, Re: mathics

[Duncan Roe]

On Mon, Mar 14, 2022 at 08:16:29AM -0600, Jeremy Hansen wrote:
> On Mon, Mar 14, 2022, 3:24 AM David Chmelik  wrote:
>
> > Working on mathics.SlackBuild, I'm thinking does maybe maybe
> > python-template.SlackBuild template need update?  Seems /any/all/
> > (almost 10+) Python programs I try anymore use pip, not setuptools
> > (haven't seen it for years) so shouldn't both be in template(s)?  But,
> > maybe pip isn't going to work right without pip2tgz...
> >
> > On 3/14/22 12:54 AM, David Chmelik wrote:
> > > On 3/14/22 12:46 AM, Duncan Roe wrote:
> > >> @David Chmelik: in your earlier email, you talked about mathics. I
> > >> built Mathics
> > >> 1.0. Now you are talking about Mathics-omnibus. As you say,
> > >> Mathics-omnibus
> > >> doesn't offer a source distro. pip2tgz can't build it. [...]
> > > Mathics 1 SlackBuild existed since Slackware 14.2 and doesn't need
> > > changes.
> > > Mathics-omnibus is newer stable Mathics full installation, which
> > > is what I want to update SlackBuild for, so of course I'm talking
> > > about it: many SlackBuilds will be being updated, sometimes with major
> > > changes.
> > I mean Slackware 14.2 is barely older than Mathics 1, from 2 October
> > 2016, w/newer commits (I didn't use) since that October 4th, until late
> > 2020's 1.1.  Mathics 4 (though renamed still Mathics3) was mid-2021, so
> > if anyone might prefer basic package, that would've been what to try.  I
> > might make basic and/or full installation Mathics build scripts.  I want
> > full but depends what others may want.
> >  Incidentally 'pip3tgz Mathics3-4.0.0.tar.gz' builds (but crashes,
> > so I'll be talking to upstream) but I avoid unusual build methods, like
> > seems poor style when discord.SlackBuild gets .deb instead of .tar.gz
> > (though pip2tgz may be better than plain pip because can/does specify
> > .tar.gz.)  It may (or not--comments/suggestions/policies?) be best see
> > if pip can be made to install to /tmp/SBo/package-mathics then do normal
> > makepkg. W/pip2tgz would I put .tar.gz in mathics.info then use pip2tgz
> > on it?
> >
>
> I'm not sure why discord came up when talking about python and pip2tgz, but
> I chose to use the deb because it places the files in the normal package
> locations.
>
> The tar.gz would need to be placed in /opt/ and it would need extra lines
> of code to get everything set up.
>
> Jeremy

No, the created tar.gz is a Slackware package, same as you get from a SlackBuild
normally.

I think all the *2tgz packages work that way.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] mathics/dependencies (mpmath, python-django-legacy)

[Duncan Roe]

On Sun, Mar 13, 2022 at 09:51:39PM -0700, David Chmelik wrote:
> On 3/13/22 8:10 PM, Duncan Roe wrote:
> > On Sun, Mar 13, 2022 at 03:11:27AM -0700, David Chmelik wrote:
> > > I immediately drop mpath, python-django-legacy: now unneeded for mathics.
> > >  Seems only documented way to install is pip, which doesn't seem to 
> > > work
> > > in SlackBuilds, and since you can install it yourself w/pip, I may drop
> > > mathics unless its programmers/developers/engineers finish instructions.
> > > They write you can install it from GitHub, but it's undocumented, and they
> > > admit the documentation is unfinished.
> > >  Their main repository says it's 'now "mostly" in archive' and link a 
> > > new
> > > one, Mathics3--which is actually Mathics 4--and a new one with more stuff,
> > > mathicsomnibus (which would be the one I use, but this is all getting 
> > > rather
> > > confusing/obscure.)
> > pip2tgz builds it (I just tried) which means you can write a SlackBuild
> > that follows the python template. [...]
>
> Okay; how?  The pip2tgz manpage says uses package archives like from PyPi
> which https://pypi.org/project/Mathics-omnibus/#files has .egg files.  I ran
> 'pip2tgz Mathics_omnibus-4.0.1-py3.9.egg ' which says it's not a .tar.  Best
> when manpages have examples...
>
@David Chmelik: in your earlier email, you talked about mathics. I built Mathics
1.0. Now you are talking about Mathics-omnibus. As you say, Mathics-omnibus
doesn't offer a source distro. pip2tgz can't build it.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Has 15.0 dropped chromium?

[Duncan Roe]

google-chrome is in 15.0 extra, as it was in Curent.

Cheers ... Duncan.

On Sun, Mar 13, 2022 at 08:48:17PM +0100, Didier Spaier wrote:
> You can use on of the versions provided by Eric Hameleers, as mentioned on his
> blog: https://alien.slackbook.org/blog/
>
> Cheers,
> Didier
>
> Le 13/03/2022 à 16:59, Rich Shepard a écrit :
> > I could not find chromium in an SBo repository and it's not part of the core
> > distribution. Is it no longer available for use in 15.0?
> >
> > TIA,
> >
> > Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] mathics/dependencies (mpmath, python-django-legacy)

[Duncan Roe]

On Sun, Mar 13, 2022 at 03:11:27AM -0700, David Chmelik wrote:
> I immediately drop mpath, python-django-legacy: now unneeded for mathics.
> Seems only documented way to install is pip, which doesn't seem to work
> in SlackBuilds, and since you can install it yourself w/pip, I may drop
> mathics unless its programmers/developers/engineers finish instructions.
> They write you can install it from GitHub, but it's undocumented, and they
> admit the documentation is unfinished.
> Their main repository says it's 'now "mostly" in archive' and link a new
> one, Mathics3--which is actually Mathics 4--and a new one with more stuff,
> mathicsomnibus (which would be the one I use, but this is all getting rather
> confusing/obscure.)

pip2tgz builds it (I just tried) which means you can write a SlackBuild
that follows the python template.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] lxml SlackBuild needs to be newer version

[Duncan Roe]

On Mon, Mar 07, 2022 at 07:25:48PM +0700, Willy Sudiarto Raharjo wrote:
> > just be sure that the newer lxml doesn't break anything depending on lxml...
>
> I hope the changes listed here
> (https://github.com/lxml/lxml/blob/master/CHANGES.txt) are not that
> invasive to other projects
>
They LGTM. w.r.t. 4.7.1:

> Wheels include libxml2 2.9.12+ and libxslt 1.1.34

15.0 ships libxml2.so.2.9.12 and libxslt.so.1.1.34

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] lxml SlackBuild needs to be newer version

[Duncan Roe]

Hi Larry,

Your lxml SB is the only one left in the repo for which Type1_to_OTF needs a
newer version.

Would it be OK with you if I pushed a rev bump?

Cheers ... Duncan.

On Sun, Feb 27, 2022 at 12:24:37PM +1100, Duncan Roe wrote:
> On Sun, Feb 27, 2022 at 12:15:27PM +1100, Duncan Roe wrote:
> > Hi Larry,
> >
> > lxml SB is at version 4.6.3 but PyPi has 4.8.0.
> >
> > afdko (that I maintain) requires at least 4.7.1.
> >
> > For now, I built afdko using pip2tgz to get an up-to-date lxml,
> > but could you update your SB please?
>
> Some clarification: lxml is a *runtime* dependency of afdko. afdko *builds*
> w/out lxml.
>
> Type1_to_OTF uses afdko to build: I should have posted "I built Type1_to_OTF
> using pip2tgz to get an up-to-date lxml".
>
> Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Please update your zopfli SlackBuild

[Duncan Roe]

On Sun, Mar 06, 2022 at 06:01:34PM -0500, B Watson wrote:
> On 3/1/22, Duncan Roe  wrote:
>
> > zopfli is a runtime dependency of afdko and hence a build time dependency
> > of
> > Type1_to_OTF (which I maintain).
>
> Apparently afdko also needs at least one new dep, since you updated it.
>
> Have you already got a build for python3-fontpens?
>
>   File "/usr/lib64/python3.9/site-packages/afdko/ufotools.py", line 9,
> in 
> from fontPens.thresholdPen import ThresholdPen
> ModuleNotFoundError: No module named 'fontPens'
>
> We're trying to clear the queue of broken builds (either fix or
> remove them), so we can launch the 15.0 repository in 100% working
> condition. Type1_to_OTF is failing to build, so if you have a working
> script for it and all its dependencies, please post them somewhere
> (patches on this mailing list would be my preference, or just tarball
> attachments).
>
> Possibly you already did this as a PR/MR on github... in which case,
> don't worry about this email. I don't do github, but others on the SBo
> team will take care of it.

There are at least 15 new deps, but I have them all covered.

Hope to do a PR later today (needs to be a PR because tqdm will then be in front
of it).

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Please update your zopfli SlackBuild

[Duncan Roe]

Hi again Oleg,

On Wed, Mar 02, 2022 at 12:15:26PM +1100, Duncan Roe wrote:
> Hi Oleg,
>
> zopfli is now a Python Package on https://pypi.org/.
[...]

Sorry for the noise, please ignore this request.

Your SB builds /usr/bin/zopfli, the PyPI package does not.

I will make a python3-zopfli package Type1_to_OTF.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Please update your tqdm SlackBuild

[Duncan Roe]

On Fri, Mar 04, 2022 at 02:55:38PM +0100, SlackBuilds wrote:
> > > Hi Dionysis,
> > >
> > > Many thanks for that: I sent a pull request with the minumum necessary 
> > > changes.
> > > On a freshly installed 15.0 system, python is python3, so your SB only 
> > > makes the
> > > 3.9 packages. You might want to change `python` to `python2`, but I leave 
> > > that
> > > up to you.
> >
> > No, /usr/bin/python points to python2.7: [...]
> > Looks like existing practice on SBo is split between "python setup.py" and 
> > python2 setup.py", with the majority being "python setup.py":
> >
> > $ git grep "python setup.py" | wc -l
> > 662
> > $ git grep "python2 setup.py" | wc -l
> > 298
> > $ git grep "python3 setup.py" | wc -l
> > 671
> >
> > > > Erich
>
> Looking at install scripts for slackware's python2 and python3, the symbolic 
> link /usr/bin/python is for python2, whatever package you install first. And 
> even if python2 is uninstalled, you won't have a /usr/bin/python executable.
>
> So python is python2, and python3 is always explicit.
>
> However, more and more slackbuilds are explicit for python2 also, which is a 
> good thing, and should be the rule, at least whenever any given python2 
> package is updated for another good reason.
>
>   - Yth.

My bad - tqdm did install 2.7. Must have scrolled off the screen and I didn't
scroll up to look.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Please update your tqdm SlackBuild

[Duncan Roe]

On Fri, Mar 04, 2022 at 02:38:04AM +, Dionysis Ntreou wrote:
> Hello Duncan,
>
> Sorry about this
>
> I will update it, I am just on Holidays getting back home on Monday.
> If you need it urgently I am happy for you to push an update in the
> meantime.
>
> Regards
> Dionysi
>
> On Fri, Mar 4, 2022 at 1:25 AM Duncan Roe 
> wrote:
>
> > Hi Dionysis,
> >
> > tqdm on PyPi is at version 4.63.0, but your SB is installing 4.62.0.
> >
> > Could you update your SB please? Type1_to_OTF (that I maintain) requires at
> > least 4.62.3 to build.
> >
> > Cheers ... Duncan.
> >

Hi Dionysis,

Many thanks for that: I sent a pull request with the minumum necessary changes.

On a freshly installed 15.0 system, python is python3, so your SB only makes the
3.9 packages. You might want to change `python` to `python2`, but I leave that
up to you.

Sorry to interrupt your holiday and enjoy the rest of it,

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Please update your tqdm SlackBuild

[Duncan Roe]

Hi Dionysis,

tqdm on PyPi is at version 4.63.0, but your SB is installing 4.62.0.

Could you update your SB please? Type1_to_OTF (that I maintain) requires at
least 4.62.3 to build.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] NodeJS version in Slackbuild causing issues

[Duncan Roe]

On Wed, Mar 02, 2022 at 01:12:13PM -0300, Ricardo J. Barberis wrote:
> FYI, SBo admins surely know already but nodejs LTS got added to Slackware
> today:
>
> slackware64 current changes for Wed, 02 Mar 2022 01:54:23 GMT
> a/lrzip-0.650-x86_64-1.txz:  Upgraded.
> d/mercurial-6.1-x86_64-1.txz:  Upgraded.
> l/nodejs-16.14.0-x86_64-1.txz:  Added.
>   Thanks to Audrius Kažukauskas, Ryan P.C. McQuen, and Willy Sudiarto Raharjo
>   for the slackbuilds.org version of the build script.
>
> El sabado, 26 de febrero de 2022 20:41:33 -03 nix escribio:
> > > The last post in that thread indicates to try upgrading nodejs to 17.6.0.
> > > Try that -- it's been updated in the SBo master branch already.
> > >
> > > -RW
> >
> > Ah, I forgot to pull the latest version in the repo. Thanks for for
> > that. I will give it a try.
> >
> > Eric
>
I don't see this in 15.0 patches
http://slackware.osuosl.org/slackware64-15.0/patches/packages/

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Please update your zopfli SlackBuild

[Duncan Roe]

On Wed, Mar 02, 2022 at 12:15:26PM +1100, Duncan Roe wrote:
> Hi Oleg,
>
> zopfli is now a Python Package on https://pypi.org/.
>
> zopfli changed its revision numbering scheme so PyPi has 0.1.9 but e.g.
>
> > diff zopfli-zopfli-1.0.0/src/zopfli/zopfli.h 
> > zopfli-0.1.9/zopfli/src/zopfli/zopfli.h
>
> shows 1.0.9 is newer.
*** 0.1.9
>
> I suggest adjust the C build for changed directory structure then insert
>
> > python3 setup.py install --root=$PKG
>
> before the line starting 'find $PKG -print0 | xargs -0 file |'
>
> zopfli is a runtime dependency of afdko and hence a build time dependency of
> Type1_to_OTF (which I maintain).
>
> Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Please update your zopfli SlackBuild

[Duncan Roe]

Hi Oleg,

zopfli is now a Python Package on https://pypi.org/.

zopfli changed its revision numbering scheme so PyPi has 0.1.9 but e.g.

> diff zopfli-zopfli-1.0.0/src/zopfli/zopfli.h 
> zopfli-0.1.9/zopfli/src/zopfli/zopfli.h

shows 1.0.9 is newer.

I suggest adjust the C build for changed directory structure then insert

> python3 setup.py install --root=$PKG

before the line starting 'find $PKG -print0 | xargs -0 file |'

zopfli is a runtime dependency of afdko and hence a build time dependency of
Type1_to_OTF (which I maintain).

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [SlackBuildsOrg/slackbuilds] Afdkov2 (PR #1276)

[Duncan Roe]

On Tue, Mar 01, 2022 at 06:43:59AM -0800, Willy Sudiarto Raharjo wrote:
> why do you put set -x when you have set -e at the middle? in scikit-build
>
Forgot to remove my local changes. When building, I always make up to 3 changes:

1. put 'set -x' at top

2. Change 'tar xvf' to 'tar xf' (to not lose o/p from 'set -x')

3. Change 'make' to 'make -j$$($(nproc)+1))||make' (N/A for scikit-build)

set -e at the middle is from the template.

Will do a v3 PR.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Please update your pipdeptree SlackBuild

[Duncan Roe]

Hi Dimitris,

pipdeptree on PyPi is at version 2.2.1, but your SB is installing 0.11.0.

Could you update your SB please? pip2tgz (that I maintain) lists pipdeptree as a
requirement (but only because the man page mentions pipdeptree).

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] afdko

[Duncan Roe]

On Fri, Feb 25, 2022 at 01:32:51PM +0700, Willy Sudiarto Raharjo wrote:
>
> If it's a mandatory dependencies for existing scripts to build under 15.0,
> then please send the PR for us to review
>
PR sent.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Where are keywords kept?

[Duncan Roe]

Hi admins,

Just curious - keywords are not in the slackbuilds git repo - are they kept
anywhere that is publically accessible?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] lxml SlackBuild needs to be newer version

[Duncan Roe]

On Sun, Feb 27, 2022 at 12:15:27PM +1100, Duncan Roe wrote:
> Hi Larry,
>
> lxml SB is at version 4.6.3 but PyPi has 4.8.0.
>
> afdko (that I maintain) requires at least 4.7.1.
>
> For now, I built afdko using pip2tgz to get an up-to-date lxml,
> but could you update your SB please?

Some clarification: lxml is a *runtime* dependency of afdko. afdko *builds*
w/out lxml.

Type1_to_OTF uses afdko to build: I should have posted "I built Type1_to_OTF
using pip2tgz to get an up-to-date lxml".

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] lxml SlackBuild needs to be newer version

[Duncan Roe]

Hi Larry,

lxml SB is at version 4.6.3 but PyPi has 4.8.0.

afdko (that I maintain) requires at least 4.7.1.

For now, I built afdko using pip2tgz to get an up-to-date lxml,
but could you update your SB please?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] afdko

[Duncan Roe]

Hi,

I have an updated afdko.SlackBuild which builds under 15.0.

You need 2 new SlackBuilds to build afdko: python/wheel and python/scikit-build.

Admins, how do you want to handle this? I can put the new SBs in a pull request
with keywords in the comment box (f.i. scikit-build provides skbuild, but a
search on PyPi doesn't tell you that).

Type1_to_OTF exposes new afdko runtime dependencies, many not currently on SBo,
but I think that is best discussed in a separate thread.

Should I submit a pull request with updated afdko and the 2 new SBs?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [SlackBuildsOrg/slackbuilds] academic/sage-bin: Updated for version 9.4 (PR #1160)

[Duncan Roe]

Hi Willy,

On Sat, Feb 05, 2022 at 10:03:11PM -0800, Willy Sudiarto Raharjo wrote:
> Hi @duncan-roe is it possible to put the tar_xz files outside of the 
> repository and put it in the .info files?

debian_binaries-11.2.tar_xz is <2K so not worth worrying about I'd suggest.

debian_libraries-11.2.tar_xz at 270K would add 25% to the repo size so
can we put it in the repo you have for big files? Then I could list it
on the DOWNLOAD line.
Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [SlackBuildsOrg/slackbuilds] For s bo (PR #1143)

[Duncan Roe]

Hi Willy,

You already have the latest mkchroot in master. You got an extra copy because I
didn't delete and recreate my for_SBo branch on GitHub.

Cheers ... Duncan.

On Thu, Feb 03, 2022 at 08:16:09PM -0800, Willy Sudiarto Raharjo wrote:
> mkchroot patch does not apply, probably it has been updated and you haven't 
> rebased to latest changes in master?
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [SlackBuildsOrg/slackbuilds] For s bo (PR #1143)

[Duncan Roe]

Hi Willy,

I must be doing something wrong but I don't know just what.

I forked the GitHub mirror https://github.com/SlackBuildsOrg/slackbuilds

I left Firefox on https://github.com/duncan-roe/slackbuilds-1/tree/for_SBo

Whenever I clicked "Fetch upstream" I got "This branch is not behind the
upstream SlackBuildsOrg:master.".

Just now I moved to
https://github.com/duncan-roe/slackbuilds-1/tree/for_SBo/academic and then
update fetched 420 changes.

Perhaps a GitHub bug?

Anyway, I'll fix up mkchroot ASAP.

Cheers ... Duncan.

On Thu, Feb 03, 2022 at 08:16:09PM -0800, Willy Sudiarto Raharjo wrote:
> mkchroot patch does not apply, probably it has been updated and you haven't 
> rebased to latest changes in master?
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Slackbuild of sage-bin

[Duncan Roe]

On Sat, Dec 25, 2021 at 10:19:43AM +0100, Pourpier wrote:
> The only problem which remains is that even after making these changes I got
> several error messages related to dangling symlinks and the unability to
> find /usr/bin/bash, /sbin/ldconfig and the like.

I see these now. I will need to make a new mkchroot for Current.

Also sage-bin 9.4 will have a patch file to avoid some warnings as sage starts.
So far I have verified about half of these against latest source in git.

(I fluked a working 9.4 by building under 14.2 and running under Current).
>
> Le 25/12/21 à 00:55, Duncan Roe a écrit :
> > Hi Serge,
> >
> > On Fri, Dec 24, 2021 at 07:52:05PM +0100, Pourpier wrote:
> > > Dear Sir,
> > >
> > > Could you edit the sage-bin.info and replace 8.3 with 9.4, 9 with 11 and 
> > > the
> > > MD5SUM with 3128ef3530f514932cabcaf62b78030a ? Could you also edit the
> > > sage-bin. Slackbuild and replace 8.3 with 9.4 and 9 with 11 ?
> > >
> > > Best regards,
> > >
> > > Serge
> > >
> > Thanks for the heads-up.
> >
> > I look forward to trying the new release. Will then send a pull request -
> > you should see the repo update in a week or 2.
> >
Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] sbopkg -c note

[Duncan Roe]

On Thu, Oct 21, 2021 at 10:42:04AM -0600, Jeremy Hansen wrote:
> On Thu, Oct 21, 2021, 3:45 AM Jude DaShiell  wrote:
>
> > Note: repo version not obtainable by standard method, may be inaccurate.
> > Can this be cleared by now or should it be cleared later by configuration?
> > One thing I have noticed about slackware and maybe this applies to other
> > linux distros is that the /tmp directory tree tends to be rather permanent
> > unless cleaned out every so often.  I've had instances where the root user
> > ran out of space on the system and this was with I think the standard 30gb
> > root partition install space a while ago.
> > I need to go through logs and clean some of those out too so disk quota
> > situations don't happen again for a while.
> >
>
> I can't answer about your error, but while sbopkg doesn't clean up the
> files in /tmp/ by default, you can change it by setting the following in
> /etc/sbopkg/sbopkg.conf
>
> CLEANUP=${CLEANUP:-NO}
>
> to
>
> CLEANUP=YES
>
> Jeremy

I think you are meant to:

export CLEANUP=YES

before running (un-amended) sbopkg

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] git access

[Duncan Roe]

On Wed, Oct 13, 2021 at 09:21:25PM +0200, Ruben Schuller wrote:
> Hi list!
>
> I'm pretty sure it was already discussed here or I missed some
> documentation, but what is the process to get git access to SBo?
> It just would be easier to push updates to my SlackBuilds somewhere
> instead of uploading a tarball, as i have them already stored in a git
> repository.
>
> Cheers
> Ruben

git clone git://git.slackbuilds.org/slackbuilds.git

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] SlackBuilds Template Changes

[Duncan Roe]

On Mon, Jul 12, 2021 at 09:38:51PM -0500, Erik Hanson wrote:
> On 7/5/21 6:11 AM, Duncan Roe wrote:
>
> > With reference to your templates commit bab9e3ed89a5, *please* consider
> > '#!/bin/bash -p' in place of '#!/bin/bash'.
> >
> > Without -p, a script will import all exported command functions. This can 
> > cause
> > unpredictable results when a function has the name of a command the script 
> > uses.
>
> Do you have an example use-case for this being an issue? SlackBuild
> scripts are not intended to be run from a setuid program, in fact we
> expect them to be run as root, so I don't see the implications here.
>
/root/.bashrc -> /home/dunc/.bashrc on my system. Similarly /root/.profile.
Perhaps that's unusual, but I'm not about to stop doing it.
At the moment I don't export any functions, but am tempted from time to time.
E.g. colon is normally a builtin but I have :() { cd "../$1"; }

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] SlackBuilds Template Changes

[Duncan Roe]

Hi Heinz,

On Mon, Jul 05, 2021 at 04:11:25PM +0700, Willy Sudiarto Raharjo wrote:
> Hi everyone
>
> We just want to update with the progress we have been doing in the last
> few weeks as well some changes that is happening during this development
> cycle.
>
> First, we have finished first batch of Python2/3 transition and
> hopefully we didn't miss anything. There will be some exceptions here
> and there but we will try to make as consistent as possible.
>
> Second, there has been some changes in the default templates. At this
> point, the changes are in template's master branch which can be seen
> here: https://git.slackbuilds.org/templates/log/. These change were
> ported from Slackware main tree. There is one last change that hasn't
> been merged into SBo master branch and that work in progress is still
> being reviewed but it can be seen in this branch
> (https://git.slackbuilds.org/slackbuilds/log/?h=user/pprkut/template-changes)
>
>
> --
> Willy Sudiarto Raharjo
>
With reference to your templates commit bab9e3ed89a5, *please* consider
'#!/bin/bash -p' in place of '#!/bin/bash'.

Without -p, a script will import all exported command functions. This can cause
unpredictable results when a function has the name of a command the script uses.

I can submit a patch if you would like,

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] brace expansion

[Duncan Roe]

On Wed, Jun 16, 2021 at 09:51:41PM +0200, Spycrowsoft wrote:
>
> Op 16-06-2021 om 21:09 schreef Eugen Wissner:
> > Pat changed /bin/sh to /bin/bash in all
> > rc-scripts, so they work with other shells.
>
> We should confirm this with Patrick Volderding, but if he's doing that, my
> take on the matters is: "Follow what the BDFL is doing".
>
Yes it's fine to start *rc* scripts wih #!/bin/bash.

All other scripts should start #!/bin/bash -p

The reason being, plain /bin/bash will import functions from the environment.
These functions will supplant commands of the same name (e.g. rm, mkdir).
/bin/bash -p does not import functions.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Test message - please ignore

[Duncan Roe]

Sent from dimstar - nothing special
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] QT5 documentation not building

[Duncan Roe]

That was it. I had an old llvm.

Thanks ... Duncan.

On Thu, Mar 11, 2021 at 09:18:41PM -0500, Lenard Spencer wrote:
> You need the newer llvm package in /extra to build the docs.
>
>
> On Thu, Mar 11, 2021, 20:04 Duncan Roe  wrote:
>
> > Hi,
> >
> > I built and installed qt5-5.12.8 with examples.
> >
> > Later I tried to build with examples and documentation. This build failed
> > at
> > `make docs` with error
> > > /tmp/SBo/qt-everywhere-src-5.12.8/qtbase/src/corelib/qdoc_wrapper.sh:
> > line 12: /usr/lib64/qt5/bin/qdoc: No such file or directory
> >
> > If I had done this when qt5-5.9.8 was still installed then I wouldn't have
> > noticed a problem because that rev did build qdoc.
> >
> > So it looks like a config problem in the SB for qt5-5.12.8.
> >
> > Cheers ... Duncan.
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@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@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@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] QT5 documentation not building

[Duncan Roe]

Hi,

I built and installed qt5-5.12.8 with examples.

Later I tried to build with examples and documentation. This build failed at
`make docs` with error
> /tmp/SBo/qt-everywhere-src-5.12.8/qtbase/src/corelib/qdoc_wrapper.sh: line 
> 12: /usr/lib64/qt5/bin/qdoc: No such file or directory

If I had done this when qt5-5.9.8 was still installed then I wouldn't have
noticed a problem because that rev did build qdoc.

So it looks like a config problem in the SB for qt5-5.12.8.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] multiple definition of... first defined here -fcommon fix

[Duncan Roe]

On Sun, Jan 10, 2021 at 06:49:28PM +0200, Petar Petrov wrote:
> Hi guys,
>
> I recently updated my -current installation, and some programs fail to
> compile with errors like this:
>
> /usr/bin/ld: gui.o:(.bss+0x20): multiple definition of
> `notify_notification_close'; mod_notify.o:(.bss+0x10): first defined
> here
> /usr/bin/ld: gui.o:(.bss+0x30): multiple definition of
> `notify_notification_update'; mod_notify.o:(.bss+0x20): first defined
> here
> /usr/bin/ld: gui.o:(.bss+0x28): multiple definition of
> `notify_notification_show'; mod_notify.o:(.bss+0x18): first defined
> here
> /usr/bin/ld: gui.o:(.bss+0x38): multiple definition of
> `notify_notification_new'; mod_notify.o:(.bss+0x28): first defined
> here
> /usr/bin/ld: gui.o:(.bss+0x40): multiple definition of
> `notify_uninit'; mod_notify.o:(.bss+0x30): first defined here
> /usr/bin/ld: gui.o:(.bss+0x48): multiple definition of `notify_init';
> mod_notify.o:(.bss+0x38): first defined here
>
> an example is artha, another one is treebest-ensembl that I maintain.
> This seems to get fixed by adding "-fcommon" to the compiler flags.
> For more info:
> https://gcc.gnu.org/gcc-10/porting_to.html
>
> sorry if this has been already discussed, I did not have time to read
> the mailing list.
>
> best,
>
> Petar
> ___
I think no_fortran_common is the default now - will need fixing upstream if 
that's the culprit

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [Slackware-current] zfs-on-linux

[Duncan Roe]

On Sun, Jan 03, 2021 at 07:00:41PM -0800, David Chmelik wrote:
> On 1/1/21 8:34 AM, Markus Reichelt wrote:
> > * David Chmelik  wrote:
> >
> > > On Slackware-current with the 5.10.n kernels, I get this error
> > > building zfs-on-linux.  I don't know if the ZFS project updated it
> > > for 5.10.n.
> > >    CC [M]  /tmp/SBo/zfs-0.8.5/module/zfs/vdev_disk.o
> > > [...]
> > zfs-0.8.5 is outdated.
> >
> > I've got no trouble using zfs-2.0.0 on -current
>
> I don't see how you'd build that with the SlackBuild; what about 0.8.6? 
> Though I see people had various other (non-ZFS, but display/X/KDE) problems
> with 5.10.n kernels; I might wait...
>
Too right - at 5.10.* my laptop display went blank and system hung when it
should have changed to small font during boot. Now fixed by reverting the patch
that git bisect identified, submitting a bug report now.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] FreeBASIC update fails

[Duncan Roe]

On Wed, Dec 23, 2020 at 04:09:40PM -0500, Jude DaShiell wrote:
> From what I understand the script command also catches stderr that's the
> reason for using script at all.  I can do as you suggested earlier but I
> doubt you'll get any additional useful information from that output.
>
>
>
> On Wed, 23 Dec 2020, B Watson wrote:
>
> > On 12/23/20, Jude DaShiell  wrote:
> > > This may be useful it's a typescript file stripped of the ansi characters.
> >
> > It's only the standard output, doesn't include standard error, so the
> > error messages aren't in there.
> > ___

The error *is* in the typescript file:

> LINK bootstrap/fbc
> mkdir -p bin
> cp bootstrap/fbc bin/fbc
> make: Nothing to be done for 
> '/usr/src/slapt-src/development/FreeBASIC/FreeBASIC-1.07.1-source-bootstrap/inc'.
> mkdir -p src/compiler/obj/linux-x86_64
> fbc -e -m fbc -w pedantic -d ENABLE_LIB64 -d ENABLE_STRIPALL  -maxerr 1 -c 
> src/compiler/ast-gosub.bas -o src/compiler/obj/linux-x86_64/ast-gosub.o
> make: fbc: Command not found

'make' built fbc and copied it to local directory 'bin'.

'fbc' is then not found, either because
 a. local directory 'bin' is not in PATH (why would it be?)
 b. 'fbc' is not executable

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Vim indent settings for SlackBuilds

[Duncan Roe]

On Sat, Sep 05, 2020 at 05:40:02PM +1000, Christoph Willing wrote:
> On 5/9/20 10:13 am, flinchx via SlackBuilds-users wrote:
> > Vim has a thing called modeline.
> >
> > Perhaps such settings could be added straighgt into SlackBuild template 
> > files, this will exclude the need for each contributor to manage them 
> > explicitly in vimrc?
> >
>
> Not everyone uses vim to edit their SlackBuilds so I'd be against adding
> such support.
>
> chris

Seconded

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] 'wayland-egl' can be removed from SBO

[Duncan Roe]

On Thu, Apr 16, 2020 at 05:51:19PM -0400, Logan Rathbone wrote:
> Hello all,
>
> Now that Diniz Bortlotto has updated wayland to 1.18.0, wayland-egl can
> be removed from SBo, as this is now part of wayland and is no longer a
> separate project.
>
> Thanks,
> Logan "Poprocks"

Fine with me.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20200208.1

[Duncan Roe]

On Mon, Feb 10, 2020 at 10:44:14AM +0700, Willy Sudiarto Raharjo wrote:
> > You are quite right about the patches. I don't know what happened. I
> > submitted it correctly the first time. I suspect the new patches were
> > somehow added to the old. At any rate, I submitted a second build. I've
> > attached the slackbuild so you don't have to wait another week for the
> > next update.
>
> Hi Donald
>
> I tried this SlackBuild and it still failed here
>
> --
> Willy Sudiarto Raharjo
>
Built fine for me. Did you "rm -r netcat-openbsd" before restoring the tarball?

It sems -q is broken worse than before: nc *never* exits now, even with "-q 1".

I shall be looking into that,

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] [PATCH netcat-openbsd 1/1] Fix zero seconds quit

[Duncan Roe]

Patch 0006-quit-timer.patch introduced -q  for nc to exit after EOF on
stdin. However it used the same variable as a flag (-q option present) and a
value (number of seconds to wait) so that -q 0 had no effect rather than causing
immediate exit on EOF as the documentation implied it should.

Have separate qflag and qval to fix.

Signed-off-by: Duncan Roe 
---
 network/netcat-openbsd/netcat-openbsd.SlackBuild   |  2 +-
 .../netcat-openbsd/patches/SB-zero-secs-quit.patch | 34 ++
 2 files changed, 35 insertions(+), 1 deletion(-)
 create mode 100644 network/netcat-openbsd/patches/SB-zero-secs-quit.patch

diff --git a/network/netcat-openbsd/netcat-openbsd.SlackBuild 
b/network/netcat-openbsd/netcat-openbsd.SlackBuild
index c807a163db..a63707a4bf 100644
--- a/network/netcat-openbsd/netcat-openbsd.SlackBuild
+++ b/network/netcat-openbsd/netcat-openbsd.SlackBuild
@@ -24,7 +24,7 @@
 
 PRGNAM=netcat-openbsd
 VERSION=${VERSION:-1.105}
-BUILD=${BUILD:-2}
+BUILD=${BUILD:-3}
 TAG=${TAG:-_SBo}
 
 DEBVER=7
diff --git a/network/netcat-openbsd/patches/SB-zero-secs-quit.patch 
b/network/netcat-openbsd/patches/SB-zero-secs-quit.patch
new file mode 100644
index 00..f80e4d5ec9
--- /dev/null
+++ b/network/netcat-openbsd/patches/SB-zero-secs-quit.patch
@@ -0,0 +1,34 @@
+# This patch enables nc -q 0 to immediately exit on stdin EOF.# This was 
already the documented behaviour.--- netcat.c 2020/01/12 01:10:58 1.1
 a/netcat.c 2020/01/12 04:22:20 1.4
+@@ -127,6 +127,7 @@
+ char   *Pflag;/* Proxy username */
+ char   *pflag;/* Localport flag */
+ int qflag = 0; /* Quit after some secs */
++int qval = 0;  /* # secs to wait for quit */
+ int   rflag;  /* Random ports flag */
+ char   *sflag;/* Source Address */
+ int   tflag;  /* Telnet Emulation */
+@@ -256,7 +257,8 @@
+   pflag = optarg;
+   break;
+ case 'q':
+-  qflag = strtonum(optarg, INT_MIN, INT_MAX, );
++  qflag = 1;
++  qval = strtonum(optarg, INT_MIN, INT_MAX, );
+   if (errstr)
+   errx(1, "quit timer %s: %s", errstr, optarg);
+   break;
+@@ -1089,9 +1091,11 @@
+   close(wfd);
+   }
+   /* if user asked to die after a while, arrange for it */
+-  if (qflag > 0) {
++  if (qval == 0)
++  exit(0);
++  if (qval > 0) {
+   signal(SIGALRM, quit);
+-  alarm(qflag);
++  alarm(qval);
+   }
+   pfd[1].fd = -1;
+   pfd[1].events = 0;
-- 
2.14.5

___
SlackBuilds-users mailing list
SlackBuilds-users@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] [PATCH netcat-openbsd 0/1] Fix zero seconds quit

[Duncan Roe]

Hi Donald,

I needed netcat -q 0 to work in a hurry so crufted up the following patch.
You might like to post it as a SlackBuild update.
The git site https://salsa.debian.org/debian/netcat-openbsd.git is up to
revision 1.206 now so not sure if they'd be interested but cc'ing last guy to
touch this area anyway.
Also cc'ing the list in case anyone else would find this patch useful.

Duncan Roe (1):
  Fix zero seconds quit

 network/netcat-openbsd/netcat-openbsd.SlackBuild   |  2 +-
 .../netcat-openbsd/patches/SB-zero-secs-quit.patch | 34 ++
 2 files changed, 35 insertions(+), 1 deletion(-)
 create mode 100644 network/netcat-openbsd/patches/SB-zero-secs-quit.patch

-- 
2.14.5

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] How to build a slackpackage for a software without a version number ?

[Duncan Roe]

On Sun, Oct 13, 2019 at 10:13:11PM +0200, J. Scheurich wrote:
> Hi,
>
> I need to add the OpenSubdiv library to slackbuild, but the software do
> not have a
> file with a version number 8-(
>
> http://graphics.pixar.com/opensubdiv/docs/getting_started.html
>
> points to a git repository and
>
> https://github.com/PixarAnimationStudios/OpenSubdiv/archive/master.zip
>
> which has no version number 8-(
>
> If Pixar needs to patch this file, the archive checksum will be changed
> and a
> slackbuild port would become invalid 8-(
>
> How to solve the problem ?
>
> so long
> MUFTI

Hi Mufti,

I went to https://github.com/PixarAnimationStudios/OpenSubdiv and there *are*
revisions - latest is 3.4.0.

If you click on RELEASES you get offerred OpenSubdiv-3_4_0.tar.gz (somewhat
preferred over the zip file).

The URL to get it is
https://github.com/PixarAnimationStudios/OpenSubdiv/archive/v3_4_0.tar.gz

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Qt5 build failure

[Duncan Roe]

Hi,

When building qt5 5.9.8, this error appeared:

> g++ -L/usr/lib64 -Wl,--no-undefined -Wl,-O1 -Wl,--enable-new-dtags -shared -o 
> libqsqltds.so .obj/qsql_tds.o .obj/main.o .obj/moc_qsql_tds_p.o  
> -L/tmp/SBo/qt-everywhere-opensource-src-5.9.8/qtbase/lib -lQt5Sql -lQt5Core 
> -lpthread -L/opt/sybase/lib
> .obj/qsql_tds.o: In function `qFieldType(QTDSResultPrivate*, int)':
> qsql_tds.cpp:(.text+0x34f): undefined reference to `dbcoltype'
> .obj/qsql_tds.o: In function `QTDSDriver::init()':
> qsql_tds.cpp:(.text+0x426): undefined reference to `dbinit'
> qsql_tds.cpp:(.text+0x43c): undefined reference to `dberrhandle'
> .obj/qsql_tds.o: In function `QTDSDriver::~QTDSDriver()':
> qsql_tds.cpp:(.text+0x805): undefined reference to `dberrhandle'
> qsql_tds.cpp:(.text+0x80c): undefined reference to `dbmsghandle'
> qsql_tds.cpp:(.text+0x811): undefined reference to `dbexit'
> .obj/qsql_tds.o: In function `QTDSDriver::open(QString const&, QString 
> const&, QString const&, QString const&, int, QString const&)':
> qsql_tds.cpp:(.text+0x892): undefined reference to `dblogin'
> qsql_tds.cpp:(.text+0x8e1): undefined reference to `dbsetlname'
> qsql_tds.cpp:(.text+0x938): undefined reference to `dbsetlname'
> qsql_tds.cpp:(.text+0x978): undefined reference to `tdsdbopen'
> qsql_tds.cpp:(.text+0x9bf): undefined reference to `dbuse'
> qsql_tds.cpp:(.text+0x9e9): undefined reference to `dbclose'
> .obj/qsql_tds.o: In function `QTDSDriver::close()':
> qsql_tds.cpp:(.text+0xc18): undefined reference to `dbloginfree'
> .obj/qsql_tds.o: In function `qTdsErrHandler':
> qsql_tds.cpp:(.text+0x163f): undefined reference to `dbdead'
> .obj/qsql_tds.o: In function `QTDSResult::cleanup()':
> qsql_tds.cpp:(.text+0x1f69): undefined reference to `dbcanquery'
> qsql_tds.cpp:(.text+0x1f76): undefined reference to `dbfreebuf'
> .obj/qsql_tds.o: In function `QTDSResult::reset(QString const&)':
> qsql_tds.cpp:(.text+0x205b): undefined reference to `dbcmd'
> qsql_tds.cpp:(.text+0x2085): undefined reference to `dbsqlexec'
> qsql_tds.cpp:(.text+0x2095): undefined reference to `dbresults'
> qsql_tds.cpp:(.text+0x20b6): undefined reference to `dbfreebuf'
> qsql_tds.cpp:(.text+0x210f): undefined reference to `dbcmdrow'
> qsql_tds.cpp:(.text+0x212a): undefined reference to `dbnumcols'
> qsql_tds.cpp:(.text+0x2191): undefined reference to `dbcoltype'
> qsql_tds.cpp:(.text+0x21b6): undefined reference to `dbcolname'
> qsql_tds.cpp:(.text+0x222a): undefined reference to `dbcollen'
> qsql_tds.cpp:(.text+0x228d): undefined reference to `dbbind'
> qsql_tds.cpp:(.text+0x2395): undefined reference to `dbbind'
> qsql_tds.cpp:(.text+0x23ab): undefined reference to `dbcollen'
> qsql_tds.cpp:(.text+0x23c8): undefined reference to `dbcollen'
> qsql_tds.cpp:(.text+0x23e2): undefined reference to `dbbind'
> qsql_tds.cpp:(.text+0x2415): undefined reference to `dbbind'
> qsql_tds.cpp:(.text+0x242b): undefined reference to `dbcollen'
> qsql_tds.cpp:(.text+0x2448): undefined reference to `dbcollen'
> qsql_tds.cpp:(.text+0x2462): undefined reference to `dbbind'
> qsql_tds.cpp:(.text+0x2480): undefined reference to `dbcolname'
> qsql_tds.cpp:(.text+0x2578): undefined reference to `dbnullbind'
> .obj/qsql_tds.o: In function `QTDSResult::gotoNext(QVector&, int)':
> qsql_tds.cpp:(.text+0x2ed3): undefined reference to `dbnextrow'
> .obj/qsql_tds.o: In function `QTDSResult::~QTDSResult()':
> qsql_tds.cpp:(.text+0x36f9): undefined reference to `dbclose'
> .obj/qsql_tds.o: In function `QTDSResult::QTDSResult(QTDSDriver const*)':
> qsql_tds.cpp:(.text+0x3970): undefined reference to `tdsdbopen'
> qsql_tds.cpp:(.text+0x39f9): undefined reference to `dbuse'
> qsql_tds.cpp:(.text+0x3b7a): undefined reference to `dbcmd'
> qsql_tds.cpp:(.text+0x3b86): undefined reference to `dbsqlexec'
> .obj/qsql_tds.o: In function `QTDSResult::numRowsAffected()':
> qsql_tds.cpp:(.text+0x1c): undefined reference to `dbcount'
> .obj/qsql_tds.o: In function `QTDSDriver::init()':
> qsql_tds.cpp:(.text+0x449): undefined reference to `dbmsghandle'
> collect2: error: ld returned 1 exit status

Looking back, I found I had the same problem with qt5 5.9.7, but must have
gotten around it somehow.

I have freetds installed, and found that the missing references were all
satisfied by libsybdb from that package.

After patching
/tmp/SBo/qt-everywhere-opensource-src-5.9.8/qtbase/src/plugins/sqldrivers/tds/Makefile
as follows:

> 40c40
> < LFLAGS= -L/usr/lib64 -Wl,--no-undefined -Wl,-O1 
> -Wl,--enable-new-dtags -shared
> ---
> > LFLAGS= -L/usr/lib64 -Wl,--no-undefined -Wl,-O1 
> > -Wl,--enable-new-dtags -shared -lsybdb

"make" proceeds.

I don't know is this is an upstream problem with configure or what.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - 

Re: [Slackbuilds-users] Qemu-4.1.0

[Duncan Roe]

On Sat, Aug 24, 2019 at 11:21:05AM +0400, MyRequiem wrote:
> Re: John Yost 24.08.2019 
>
> I have the same problem (Slackware64 14.2)
>
> >The slackbuild fails for me with:
> >
> >contrib/vhost-user-gpu/vugbm.c: In function 'map_bo':
> >contrib/vhost-user-gpu/vugbm.c:161:17: warning: implicit declaration of
> >function 'gbm_bo_map' [-Wimplicit-function-declaration]
> > buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
> > ^
> >contrib/vhost-user-gpu/vugbm.c:161:5: warning: nested extern declaration
> >of 'gbm_bo_map' [-Wnested-externs]
> > buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
> > ^
> >contrib/vhost-user-gpu/vugbm.c:162:28: error:
> >'GBM_BO_TRANSFER_READ_WRITE' undeclared (first use in this function)
> >GBM_BO_TRANSFER_READ_WRITE, ,
> >^
> >contrib/vhost-user-gpu/vugbm.c:162:28: note: each undeclared identifier
> >is reported only once for each function it appears in
> >contrib/vhost-user-gpu/vugbm.c: In function 'unmap_bo':
> >contrib/vhost-user-gpu/vugbm.c:173:5: warning: implicit declaration of
> >function 'gbm_bo_unmap' [-Wimplicit-function-declaration]
> > gbm_bo_unmap(buf->bo, buf->mmap_data);
> > ^
> >contrib/vhost-user-gpu/vugbm.c:173:5: warning: nested extern declaration
> >of 'gbm_bo_unmap' [-Wnested-externs]
> >/tmp/SBo/qemu-4.1.0/rules.mak:69: recipe for target
> >'contrib/vhost-user-gpu/vugbm.o' failed
> >make: *** [contrib/vhost-user-gpu/vugbm.o] Error 1
> >
> >Any suggestions ?
> >Thanks in Advance
> >--
> >John David Yost
> >AlleyTrotter
> >pub   2048D/F3BDEB55 2014-05-23 [expires: Never]
>
The missing gbm_bo_map() and GBM_BO_TRANSFER_READ_WRITE are satisfied by a newer
version of mesa than comes with 14.2 (or Current which has the same version of
mesa)

I don't have time to pursue this further at present :(

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] scipy3: cannot find numpy3 when building [RESOLVED]

[Duncan Roe]

On Fri, Aug 09, 2019 at 01:44:02AM +, Daniel Prosser wrote:
> That's because the software itself is just called numpy. The package was 
> named numpy3 to distinguish it from the Python 2 version. The numpy stuff in 
> /usr/lib64/python3.7 comes from the numpy3 package.
>
> Dan
>
So the original message, "scipy3: cannot find numpy3 when building" is output
by an SBo script when it sees REQUIRES="numpy3 ..." and
/var/log/packages/numpy3-1.14.3-x86_64-1P_SBo does not exist.

Could that be the underlying problem?

Cheers ... Duncan.
>
> On Aug 8, 2019 9:22 PM, Duncan Roe  wrote:
>
> Hey Rich,
>
> On Thu, Aug 08, 2019 at 02:06:36PM -0700, Rich Shepard wrote:
> > On Thu, 8 Aug 2019, Didier Spaier wrote:
> >
> > > Please run from the systems in concern as root: updateb
> >
> > Didier,
> >
> > updatedb runs automatically overnight. The system is not turned off when I
> > log out.
> >
> > > then provide the full output of this command:
> > > locate numpy.py
> >
> > # locate numpy.py
> > /usr/share/apps/kdevpythonsupport/documentation_files/numpy.py
> > /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.pyc
> > /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.py
> > /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.py
> > /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.pyc
> > /home/rshepard/gis/grass/grass_dev/lib/python/pygrass/raster/testsuite/test_numpy.py
> >
> > But, ...
> >
> > # find / -name numpy
> > /usr/lib64/python2.7/site-packages/numpy
> > /usr/lib64/python2.7/site-packages/pandas/compat/numpy
> > /usr/lib64/python2.7/site-packages/Cython/Includes/numpy
> > /usr/lib64/R/library/BH/include/boost/python/numpy
> > /usr/lib64/python3.7/site-packages/numpy
> > /usr/lib64/python3.7/site-packages/numpy/core/include/numpy
> > /var/lib/sbopkg/SBo/14.2/development/numpy
> > /opt/slackbuilds/Development/numpy
>
> These are all directories. If you try again with "-tye f" you won't see them.
> (Quick check: find /usr/lib64 -type f -name numpy).
> >
> > Rich
> > ___
> I tried this:
>
> 09:12:16# find /usr/lib64 /usr/src/slackbuilds -type f -name '*numpy*'
> /usr/lib64/python3.7/site-packages/numpy/core/__pycache__/generate_numpy_api.cpython-37.pyc
> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy/numpyconfig.h
> /usr/lib64/python3.7/site-packages/numpy/core/generate_numpy_api.py
> /usr/lib64/python3.7/site-packages/numpy/distutils/__pycache__/numpy_distribution.cpython-37.pyc
> /usr/lib64/python3.7/site-packages/numpy/distutils/numpy_distribution.py
> /usr/lib64/python3.7/site-packages/numpy/tests/test_numpy_version.py
> /usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.pyc
> /usr/lib64/python2.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
> /usr/lib64/python2.7/site-packages/numpy/core/include/numpy/numpyconfig.h
> /usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.py
> /usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.pyc
> /usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.py
> /usr/lib64/python2.7/site-packages/numpy/tests/test_numpy_version.py
> /usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.py
> /usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.pyc
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.pyc
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.py
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.py
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.pyc
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.py
> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.pyc
> /usr/lib64/python2.7/site-packages/vtk/util/numpy_support.py
> /usr/lib64/python2.7/site-packages/vtk/util/numpy_support.pyc
> /usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.py
> /usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.pyc
> /usr/src/slackbuilds/python/numpydoc/numpydoc.SlackBuild
> /usr/src/slackbuilds/python/numpydoc/numpydoc.info
> /usr/src/slackbuilds/development/numpy3/numpy3.SlackBuild
> /usr/src/slackbuilds/development/numpy3/numpy3.info
> /usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.info
> /usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.SlackBuild
> /usr/src/slackbuilds/developm

Re: [Slackbuilds-users] scipy3: cannot find numpy3 when building [RESOLVED]

[Duncan Roe]

Hey Rich,

On Thu, Aug 08, 2019 at 02:06:36PM -0700, Rich Shepard wrote:
> On Thu, 8 Aug 2019, Didier Spaier wrote:
>
> > Please run from the systems in concern as root: updateb
>
> Didier,
>
> updatedb runs automatically overnight. The system is not turned off when I
> log out.
>
> > then provide the full output of this command:
> > locate numpy.py
>
> # locate numpy.py
> /usr/share/apps/kdevpythonsupport/documentation_files/numpy.py
> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.pyc
> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.py
> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.py
> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.pyc
> /home/rshepard/gis/grass/grass_dev/lib/python/pygrass/raster/testsuite/test_numpy.py
>
> But, ...
>
> # find / -name numpy
> /usr/lib64/python2.7/site-packages/numpy
> /usr/lib64/python2.7/site-packages/pandas/compat/numpy
> /usr/lib64/python2.7/site-packages/Cython/Includes/numpy
> /usr/lib64/R/library/BH/include/boost/python/numpy
> /usr/lib64/python3.7/site-packages/numpy
> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy
> /var/lib/sbopkg/SBo/14.2/development/numpy
> /opt/slackbuilds/Development/numpy

These are all directories. If you try again with "-tye f" you won't see them.
(Quick check: find /usr/lib64 -type f -name numpy).
>
> Rich
> ___
I tried this:

09:12:16# find /usr/lib64 /usr/src/slackbuilds -type f -name '*numpy*'
/usr/lib64/python3.7/site-packages/numpy/core/__pycache__/generate_numpy_api.cpython-37.pyc
/usr/lib64/python3.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
/usr/lib64/python3.7/site-packages/numpy/core/include/numpy/numpyconfig.h
/usr/lib64/python3.7/site-packages/numpy/core/generate_numpy_api.py
/usr/lib64/python3.7/site-packages/numpy/distutils/__pycache__/numpy_distribution.cpython-37.pyc
/usr/lib64/python3.7/site-packages/numpy/distutils/numpy_distribution.py
/usr/lib64/python3.7/site-packages/numpy/tests/test_numpy_version.py
/usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.pyc
/usr/lib64/python2.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
/usr/lib64/python2.7/site-packages/numpy/core/include/numpy/numpyconfig.h
/usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.py
/usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.pyc
/usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.py
/usr/lib64/python2.7/site-packages/numpy/tests/test_numpy_version.py
/usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.py
/usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.pyc
/usr/lib64/python2.7/site-packages/vtk/util/numpy_support.py
/usr/lib64/python2.7/site-packages/vtk/util/numpy_support.pyc
/usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.py
/usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.pyc
/usr/src/slackbuilds/python/numpydoc/numpydoc.SlackBuild
/usr/src/slackbuilds/python/numpydoc/numpydoc.info
/usr/src/slackbuilds/development/numpy3/numpy3.SlackBuild
/usr/src/slackbuilds/development/numpy3/numpy3.info
/usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.info
/usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.SlackBuild
/usr/src/slackbuilds/development/numpy/numpy.info
/usr/src/slackbuilds/development/numpy/numpy.SlackBuild
/usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.info
/usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.SlackBuild

Here's the rub: I *do* have numpy3 installed. But no files named '*numpy3*'
anywhere in the system except /var/log/packages/numpy3-1.14.3-x86_64-1P_SBo

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20190622.1

[Duncan Roe]

On Sun, Jun 23, 2019 at 06:57:38AM +0700, Willy Sudiarto Raharjo wrote:
> Sat Jun 22 23:46:39 UTC 2019
> academic/latex2html: Added (convert latex document).
> development/Sphinx: Updated for version 2.1.2.
> development/byacc: Updated for version 20190617.
> development/chicken: Updated for version 5.1.0.
> development/d-tools: Updated for version 2.086.1
> development/dmd: Updated for version 2.086.1
> development/hhvm: Updated for version 4.8.1
> development/hub: Updated for version 2.12.0.
> development/jupyter_core: Update for version 4.5.0.
> development/rtags: Updated for version 2.32.
> development/sassc: Updated for version 3.6.1.
> development/universal-ctags: Updated for version 6928d2b
> development/vscode-bin: Updated for version 1.35.1.
> development/yarn: Updated for version 1.17.0.
> games/OpenRA: Updated for version 20190314.
> games/stone_soup: Fix VERSION.
> gis/gpxsee: Updated for version 7.9.
> graphics/vulkan-sdk: Updated for version 1.1.108.0.
> libraries/enchant2: Updated for version 2.2.4.
> libraries/libsass: Updated for version 3.6.1.
> libraries/liburcu: Updated for version 0.11.1.
> libraries/libyang: Added (YANG data modeling language library).
> misc/mosquitto: Updated for version 1.6.3
> multimedia/flashplayer-plugin: Updated for version 32.0.0.207.
> multimedia/makemkv: Updated for version 1.14.4.
> multimedia/openshot: Add requirement for python3-certifi
> multimedia/pepperflash-plugin: Updated for version 32.0.0.207.
> multimedia/plexmediaserver: Updated for v. 1.16.0.1226_7eb2c8f6f.
> multimedia/strawberry: Updated for version 0.5.5.
> multimedia/x265: Updated for version 3.1.
> network/axel: Updated for version 2.17.3.
> network/brave-browser: Updated for version 0.65.121.
> network/dissenter-browser: Updated for version 0.65.120.
> network/palemoon-bin: Updated for version 28.5.2.
> network/palemoon: Updated for version 28.5.2.
> network/pfqueue: Update Copyright year.
> network/prosody-mod-cloud-notify: Updated for version hg3622.
> network/prosody-mod-smacks: Updated for version hg3621.
> network/signal-desktop: Updated for version 1.25.1.
> network/tor-browser: Updated for version 8.5.2.
> network/vivaldi: Updated for version 2.6.1566.40.
> network/waterfox: Updated for version 56.2.11.
> network/yle-dl: Updated for version 20190614.
> network/zoom-linux: Updated for version 2.8.252201.0616.
> office/hunspell-en: Updated for version 2018.04.16.
> office/watson: Updated for version 1.7.0.
> perl/nqp: Update DOWNLOAD source.
> perl/rakudo: Updated for version 2019.03.1.
> python/parso: Updated for version 0.5.0.
> python/python-fonttools: Updated for version 3.43.1.
> python/python3-certifi: Fixed dependencies.
> python/python3-jedi: Updated for version 0.14.0.
> python/python3-wrapt: Updated for version 1.11.2.
> ruby/ruby-build: Updated for version 20190615.
> ruby/sequel: Updated for version 5.21.0.
> system/binfmt-support: Update README.
> system/chronograf: Updated for version 1.7.12.
> system/dosbox-dev: Updated for version 0.74.r4230.
> system/fio: Updated for version 3.14.
> system/jdupes: Updated for version 1.13.1.
> system/kapacitor: Updated for version 1.5.3.
> system/keybase: Updated for version 4.1.0.
> system/letsencrypt: Updated for version 0.35.1.
> system/usbguard: Added (protection against rogue USB devices).
> system/winetricks: Updated for version 20190615.
> system/zfs-on-linux: Updated for version 0.8.1.
> +--+
>
>
> --
> Willy Sudiarto Raharjo
>
office/MasterPDFEditor is also updated (to 5.4.20)

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] libreoffice 6.2 (RPM's) runtime failure

[Duncan Roe]

Hi all,

I am getting the following error:

> 11:01:56$ libreoffice6.2 ~/calendar.ods
> /opt/libreoffice6.2/program/soffice.bin: symbol lookup error: 
> /opt/libreoffice6.2/program/libvclplug_gtk3lo.so: undefined symbol: 
> gdk_wayland_display_get_type

Fwiw avahi is up to date (avahi-0.6.32) and I'm using Oracle Java(TM) SE Runtime
Environment 18.3 (build 10.0.2+13)

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Type1_to_OTF and afdko slackbuilds

[Duncan Roe]

Hi Hazel,

On Tue, Jan 01, 2019 at 05:53:09PM +, Hazel Russman wrote:
> Dear Mr Roe
>
> I find that I cannot run your Type1_to_OTF slackbuild as is, because it
> fails to find the makeotf command from afdko, since this is in /opt and off
> the usual command path.
>
> If I reset the path with PATH=/opt/afdko/Tools/linux:$PATH as a new
> environmental variable for the slackbuild, then it works.

Like many SlackBuilds, afdko creates .sh and .csh files in /etc/profile.d to add
/opt/afdko/Tools/linux to $PATH. The usual advice is to reboot, but it's fine to
only log out and in again, or source the new file which would update the PATH
much as you did.

Some SlackBuilds put a symbolic link in /usr/bin instead. Perhaps that is a
better approach: I'm copying the List for any feedback someone might have.
>
> I'm attaching two build logs. The first is without the path adjustment and
> the second with it.

Your second log is a complete mystery to me. The first file, 'c0648bt_.pfb' is
provided by the Slackware 14.2 package 'font-bitstream-type1-1.0.3-noarch-1'.
Did you install that? The file should be at
'/usr/share/fonts/Type1/c0648bt_.pfb'.

Similarly, 'courb.pfa' is in package 'font-bitstream-type1-1.0.3-noarch-1'.
Are these packages in your /var/log/packages? May be worth a re-install if so,
install if not.

Let me know if you still have a problem,

Cheers ... Duncan.
>
> --
> Hazel Russman

> ./makeotf.sh: line 2: makeotf: command not found
> ./makeotf.sh: line 3: makeotf: command not found
> ./makeotf.sh: line 4: makeotf: command not found
> ./makeotf.sh: line 5: makeotf: command not found
> ./makeotf.sh: line 6: makeotf: command not found
> ./makeotf.sh: line 7: makeotf: command not found
> ./makeotf.sh: line 8: makeotf: command not found
> ./makeotf.sh: line 9: makeotf: command not found
> ./makeotf.sh: line 10: makeotf: command not found
> ./makeotf.sh: line 11: makeotf: command not found
> ./makeotf.sh: line 12: makeotf: command not found
> ./makeotf.sh: line 13: makeotf: command not found
> ./makeotf.sh: line 14: makeotf: command not found
> ./makeotf.sh: line 15: makeotf: command not found
> ./makeotf.sh: line 16: makeotf: command not found
> ./makeotf.sh: line 17: makeotf: command not found
> ./makeotf.sh: line 18: makeotf: command not found
> ./makeotf.sh: line 19: makeotf: command not found
> ./makeotf.sh: line 20: makeotf: command not found
> ./makeotf.sh: line 21: makeotf: command not found
> ./makeotf.sh: line 22: makeotf: command not found
> ./makeotf.sh: line 23: makeotf: command not found
> ./makeotf.sh: line 24: makeotf: command not found
> ./makeotf.sh: line 25: makeotf: command not found
> ./makeotf.sh: line 26: makeotf: command not found
> ./makeotf.sh: line 27: makeotf: command not found
> ./makeotf.sh: line 28: makeotf: command not found
> ./makeotf.sh: line 29: makeotf: command not found
> ./makeotf.sh: line 30: makeotf: command not found
> ./makeotf.sh: line 31: makeotf: command not found
> ./makeotf.sh: line 32: makeotf: command not found
> ./makeotf.sh: line 33: makeotf: command not found
> ./makeotf.sh: line 34: makeotf: command not found
> ./makeotf.sh: line 35: makeotf: command not found
> ./makeotf.sh: line 36: makeotf: command not found
> ./makeotf.sh: line 37: makeotf: command not found
> ./makeotf.sh: line 38: makeotf: command not found
> ./makeotf.sh: line 39: makeotf: command not found
> ./makeotf.sh: line 40: makeotf: command not found
> ./makeotf.sh: line 41: makeotf: command not found

>
> makeotf [Error] Could not find the input font file at 'c0648bt_.pfb'.
>
> makeotf [Error] Could not find the input font file at 'c0632bt_.pfb'.
>
> makeotf [Error] Could not find the input font file at 'c0633bt_.pfb'.
>
> makeotf [Error] Could not find the input font file at 'c0649bt_.pfb'.
>
> makeotf [Error] Could not find the input font file at 'cour.pfa'.
>
> makeotf [Error] Could not find the input font file at 'courb.pfa'.
>
> makeotf [Error] Could not find the input font file at 'courbi.pfa'.
>
> makeotf [Error] Could not find the input font file at 'couri.pfa'.
>
> makeotf [Error] Could not find the input font file at 'c0419bt_.pfb'.
>
> makeotf [Error] Could not find the input font file at 'c0583bt_.pfb'.
>
> makeotf [Error] Could not find the input font file at 'c0611bt_.pfb'.
>
> makeotf [Error] Could not find the input font file at 'c0582bt_.pfb'.
>
> makeotf [Warning] Could not find default features file at 'None'. Font will 
> be built without any layout features.
> makeotf [Note] Writing options file ./current.fpr
> makeotf [Note] Running makeotfexe with commands:
>cd "/tmp/SBo/Type1_to_OTF-1.0"
>makeotfexe "-f" "UTRG.pfa" "-o" "Utopia-Regular.otf" -mf 
> "FontMenuNameDB" -shw
> makeotfexe [NOTE] Wrote new font file 'Utopia-Regular.otf'.
>
> Built development mode font 'Utopia-Regular.otf'.
> Done.
>
> makeotf [Warning] Could not find default features file at 'None'. Font will 
> be built without any layout features.
> makeotf [Note] Writing options file 

Re: [Slackbuilds-users] sage up for grabs UNMAINTAINED

[Duncan Roe]

Hi JCA,

On Tue, Aug 21, 2018 at 06:13:21PM -0600, JCA wrote:
> On Tue, Aug 21, 2018 at 5:49 PM, Duncan Roe 
> wrote:
>
> > On Mon, Aug 13, 2018 at 09:08:46AM -0600, JCA wrote:
> > > Why not use the Debian binary tarball that is available in the Sage
> > > website? I have just tried (for Sage 8.3) and it seems to work fine. Here
> > > is what I did:
> > >
> > > 1. As root, unpacked the tarball in /opt. This create /opt/SageMath.
> > > 2. cd /opt/SageMath.
> > > 3. ./sage. This patches up Sage's files (black magic?) and launches Sage.
> > > You end up at the Sage CLI. It can be checked out that it works, at least
> > > for simple operations - like, e.g. an integration.
> > > 4. Exit Sage.
> > > 5. cd /usr/local/bin.
> > > 6. ln -s /opt/SageMath/sage ./sage.
> > > 7. Exit root.
> > > 8. Assuming that /usr/local/bin is in your path, launch Sage by invoking
> > > the sage command.
> > > 9. Verify that it works.
> > >
> > > Assuming that the above keeps working when using more esoteric Sage
> > > capabilities, getting a Slackbuilds script to do all that should be
> > > straightforward. I haven't tried building for sources, but I find it
> > > difficult to believe that the Debian binary tarball is created using some
> > > knowledge available to members of the inner circle alone.
> > >
> > > If I am missing something here please let me know.
> > >
> > Hi JCA,
> >
> > Sounds like it should be easy enough to automate into a build script using
> > mkchroot. I can give it a go (but I'm not a sage user). Could you please
> > clarify a couple if items:
> >
> > 1. Does ./sage really work after cd-ing to a freshly created directory?
> >
>
>I am not sure I understand your question. What I describe allows one to
> install the Sage executable under /usr/local/bin, and launch it from
> anywhere, provided that /usr/local/bin is in your path. You would only
> invoked ./sage from /usr/local/bin, but - why would you want to that?
>
> >
> > 2. I assume checking with an integration is not essential to the build
> > process -
> > is that correct?
> >
>
>That integration is nothing but a very basic functional test of the
> installed product. I just used the Debian package - I did not build Sage
> myself, for it takes ages and a serious system. I am merely pointing out
> that, following the steps I described above, one ends up with a Sage
> environment that seems to work fine, and one does not have to suffer the
> punishment that the original maintainer described in order to install it in
> a sensible location. I have tried a few other things in the resulting Sage,
> and they all seem to work.
>
>
> > Cheers ... Duncan.
> > >
> > > On Fri, Aug 10, 2018 at 11:26 AM, Didier Spaier  wrote:
> > >
> > > > I forgot: his user a set specific user "maths" for that.
> > > >
> > > > On 08/10/2018 07:23 PM, Didier Spaier wrote:
> > > > >
> > > > > On 08/10/2018 04:22 AM, Daniel Prosser wrote:
> > > > >> Perhaps if upstream is fighting so hard to make it *not* possible to
> > > > package
> > > > >> sage, the best course of action is just to honor their intent and
> > stop
> > > > trying
> > > > >> (take it off SBo). Just my two cents as someone who does not use it
> > > > anyway (so
> > > > >> maybe it's actually only worth one cent).
> > > > >
> > > > > I am not an user either, but I once compiled it as regular user just
> > to
> > > > check
> > > > > its ability to make png files for graphs, for an actual (and blind)
> > user.
> > > > > I just asked this friend, he is currently using the 8.1 version.
> > > > >
> > > > > As for maths there is nothing close to sage's features I'd suggest
> > > > > not providing a SlackBuild but a README explaining the situation.
> > > > >
> > > > > Just my 0.02???.

Thanks for getting back with answers to my dumb questions and sorry for the
noise.

I went ahead and submitted (what became) sage-bin-8.3 (thanks for all the work,
mods) and it's been on SBO for just over a month now.

I guess I should have posted to this thread about that :/

It's a package of the Debian tarball as you suggested, installs (a symlink) in
/usr/bin works from anywhere etc. etc.

I did try some plots and they looked fine, but mostly I just (mis-)use it to do
proper-fraction arithmetic - it's great!

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Python, pip and SlackBuilds.... Fw: [leo-editor/leo-editor] "python setup.py install" does not complete (#810)

[Duncan Roe]

Ui Rob,

On Sun, Aug 26, 2018 at 05:00:37PM +0100, sborg63 wrote:
> Hi all,
>
> There are python programs that no longer depend on setup.py scripts
> using install but exclusively on those that use pip (for example LEO, as
> described below). How are we dealing with this? Is there a way of
> adapting the Slackbuilds for such programs or do we accept that pip
> becomes another way of dealing with python (It already is part of the
> python distribution in current)? Or do we ask upstream to keep providing
> a setup.py that can use install?
>
> Background:
> As a response to my request for a setup.py install script for the
> LEO editor (https://github.com/leo-editor/leo-editor/issues/810), the
> answer is to use pip: The recent version has changed to a complete
> pip-install and bypasses the possibility of using the setup.py install
> method. The latter is -as far as I have been using python
> modules/packages in Slackware- the method of choice to build a package
> via a SlackBuild which produces a  tgz-package that can then be
> installed/updated using the common slackware tools.
>
> The idea behind the pip-only install is that determining
> updates/dependencies is much easier (with the presumed improvements
> linked below). At the moment on SBo these dependencies have been sorted
> out (and SlackBuilds made available) which allows a slacker to use one
> install-method (the distribution-specific tools) instead of a mixture
> of tools (distribitution plus tool-specific methods (like pip for
> python)).
>
> Cheers,
>
> Rob
>
> Begin forwarded message:
[...]
Yes leo only has a whheel, not a tar.gz. This is unusual and unfortunate,
because pip2tgz needs a source archive of some kind.

I tried pip2tgz on a couple od snapshots, but it always fails with:

running install_egg_info
Copying leo.egg-info to 
/tmp/SBo/package-leo-editor/usr/lib64/python2.7/site-packages/leo-5.7.3-py2.7.egg-info
running install_scripts
Traceback (most recent call last):
  File "", line 1, in 
  File "/tmp/pip-req-build-FnJDwJ/setup.py", line 164, in 
'gui_scripts': ['leo = leo.core.runLeo:run']
  File "/usr/lib64/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
  File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
  File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
  File "/usr/lib64/python2.7/site-packages/setuptools/command/install.py", 
line 61, in run
return orig.install.run(self)
  File "/usr/lib64/python2.7/distutils/command/install.py", line 575, in run
self.run_command(cmd_name)
  File "/usr/lib64/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
  File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
  File 
"/usr/lib64/python2.7/site-packages/setuptools/command/install_scripts.py", 
line 35, in run
bw_cmd = self.get_finalized_command("bdist_wininst")
  File "/usr/lib64/python2.7/distutils/cmd.py", line 312, in 
get_finalized_command
cmd_obj.ensure_finalized()
  File "/usr/lib64/python2.7/distutils/cmd.py", line 109, in 
ensure_finalized
self.finalize_options()
  File "/usr/lib64/python2.7/distutils/command/bdist_wininst.py", line 112, 
in finalize_options
for script in self.distribution.scripts:
TypeError: 'NoneType' object is not iterable


I can't fix this. Anyone??

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] sage up for grabs UNMAINTAINED

[Duncan Roe]

On Mon, Aug 13, 2018 at 09:08:46AM -0600, JCA wrote:
> Why not use the Debian binary tarball that is available in the Sage
> website? I have just tried (for Sage 8.3) and it seems to work fine. Here
> is what I did:
>
> 1. As root, unpacked the tarball in /opt. This create /opt/SageMath.
> 2. cd /opt/SageMath.
> 3. ./sage. This patches up Sage's files (black magic?) and launches Sage.
> You end up at the Sage CLI. It can be checked out that it works, at least
> for simple operations - like, e.g. an integration.
> 4. Exit Sage.
> 5. cd /usr/local/bin.
> 6. ln -s /opt/SageMath/sage ./sage.
> 7. Exit root.
> 8. Assuming that /usr/local/bin is in your path, launch Sage by invoking
> the sage command.
> 9. Verify that it works.
>
> Assuming that the above keeps working when using more esoteric Sage
> capabilities, getting a Slackbuilds script to do all that should be
> straightforward. I haven't tried building for sources, but I find it
> difficult to believe that the Debian binary tarball is created using some
> knowledge available to members of the inner circle alone.
>
> If I am missing something here please let me know.
>
Hi JCA,

Sounds like it should be easy enough to automate into a build script using
mkchroot. I can give it a go (but I'm not a sage user). Could you please
clarify a couple if items:

1. Does ./sage really work after cd-ing to a freshly created directory?

2. I assume checking with an integration is not essential to the build process -
is that correct?

Cheers ... Duncan.
>
> On Fri, Aug 10, 2018 at 11:26 AM, Didier Spaier  wrote:
>
> > I forgot: his user a set specific user "maths" for that.
> >
> > On 08/10/2018 07:23 PM, Didier Spaier wrote:
> > >
> > > On 08/10/2018 04:22 AM, Daniel Prosser wrote:
> > >> Perhaps if upstream is fighting so hard to make it *not* possible to
> > package
> > >> sage, the best course of action is just to honor their intent and stop
> > trying
> > >> (take it off SBo). Just my two cents as someone who does not use it
> > anyway (so
> > >> maybe it's actually only worth one cent).
> > >
> > > I am not an user either, but I once compiled it as regular user just to
> > check
> > > its ability to make png files for graphs, for an actual (and blind) user.
> > > I just asked this friend, he is currently using the 8.1 version.
> > >
> > > As for maths there is nothing close to sage's features I'd suggest
> > > not providing a SlackBuild but a README explaining the situation.
> > >
> > > Just my 0.02???.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Why did git report everything as a conflict lust now?

[Duncan Roe]

Hi everyone,

I just did a git pull in my clone of git://git.slackbuilds.org/slackbuilds.git
and every single change was reported as a conflict. I checked the first one:

> Auto-merging system/spman/spman.info
> CONFLICT (add/add): Merge conflict in system/spman/spman.info

> less -N system/spman/spman.info
>  1 PRGNAM="spman"
>  2 <<< HEAD
>  3 VERSION="1.5.3"
>  4 HOMEPAGE="https://github.com/MyRequiem/spman;
>  5 
> DOWNLOAD="https://github.com/MyRequiem/spman/archive/1.5.3/spman-1.5.3.tar.gz;
>  6 MD5SUM="b43a1def97283d7346ce88bd217a0e24"
>  7 ===
>  8 VERSION="1.5.4"
>  9 HOMEPAGE="https://github.com/MyRequiem/spman;
> 10 
> DOWNLOAD="https://github.com/MyRequiem/spman/archive/1.5.4/spman-1.5.4.tar.gz;
> 11 MD5SUM="9096f25e2909be7ca3b8823b53f82699"
> 12 >>> a31868bb76cca8c30498b60dc2fd685c64bfe00a
> 13 DOWNLOAD_x86_64=""
> 14 MD5SUM_x86_64=""
> 15 REQUIRES="python3"
> 16 MAINTAINER="Vladimir MyRequiem"
> 17 EMAIL="mrvladislavov...@gmail.com"

Where's the conflict in that? It's just a straightforward update.

Anyone have any idea what's going on here?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20180519.1 (geoclue2)

[Duncan Roe]

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.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Unable to build runc (for docker)

[Duncan Roe]

On Sat, Apr 14, 2018 at 05:50:43PM +0700, Willy Sudiarto Raharjo wrote:
> > When I ran runc.SlackBuild these errors appeared:
> >> go build -buildmode=pie  -ldflags "-X 
> >> main.gitCommit=4fc53a81fb7c994640722ac585fa9ca548971871 -X 
> >> main.version=1.0.0-rc5 " -tags "seccomp" -o runc .
> >> flag provided but not defined: -buildmode
> >> usage: build [-o output] [-i] [build flags] [packages]
> > slackbuilds/development/google-go-lang/README advises to "see `go help
> > buildmode`", but:
> >> 20:41:40$ go help buildmode
> >> Unknown help topic `buildmode`.  Run 'go help'.
> > I have an unpatched 14.2 system. Should I patch it to get this command to 
> > work?
> > (/usr/bin/go is provided by gcc-go-5.3.0-x86_64-3 but it would patch up to
> > gcc-go-5.5.0-x86_64-1).
>
> use "su -" instead of just su
> also, make sure to run the above command after installing/upgrading
> google-go-lang to make sure you grab the latest GOROOT environment
>
>
> --
> Willy Sudiarto Raharjo
>
I did that, no change. google-go-lang is recently installed:
> 21:31:26# echo $GOROOT
> /usr/lib64/go1.9.5/go
What next?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Unable to build runc (for docker)

[Duncan Roe]

Hi everyone,

When I ran runc.SlackBuild these errors appeared:
> go build -buildmode=pie  -ldflags "-X 
> main.gitCommit=4fc53a81fb7c994640722ac585fa9ca548971871 -X 
> main.version=1.0.0-rc5 " -tags "seccomp" -o runc .
> flag provided but not defined: -buildmode
> usage: build [-o output] [-i] [build flags] [packages]
slackbuilds/development/google-go-lang/README advises to "see `go help
buildmode`", but:
> 20:41:40$ go help buildmode
> Unknown help topic `buildmode`.  Run 'go help'.
I have an unpatched 14.2 system. Should I patch it to get this command to work?
(/usr/bin/go is provided by gcc-go-5.3.0-x86_64-3 but it would patch up to
gcc-go-5.5.0-x86_64-1).

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] freerdp stopped working after latest Microsoft updates

[Duncan Roe]

On Sun, Apr 08, 2018 at 06:41:03AM +0200, Kees Theunissen wrote:
> CC-ing Philip van der Hoeven, the maintainer of the SlackBuild script.
>
> On Sun, 8 Apr 2018, Duncan Roe wrote:
>
> >Hi all,
> >
> >I used to be able to connect to my Windows 7 home laptop with xfreerdp
> >(freerdp-git20160509-x86_64-1ffmpeg3_SBo).
> >
> >But since yesterday when I ran Windows Update for the first time in 3 
> >months, I
> >get these errors:
> >
> >> [11:24:11:093] [2930:2931] [ERROR][com.freerdp.core.transport] - BIO_read 
> >> returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert 
> >> internal error
> >> [11:24:11:093] [2930:2931] [ERROR][com.freerdp.core] - 
> >> freerdp_set_last_error ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x2000D]
> >> [11:24:11:093] [2930:2931] [ERROR][com.freerdp.client.x11] - Freerdp 
> >> connect error exit status 1
> >
> >Anyone else seen anything like this?
>
> Yes.
> The march 13th, 2018 Windows update broke a few things.
> The actual errors encountered depend on the windows version of
> the system you're connecting to and on the configuration of that
> system.
>
> I'm currentently connecting without problems to several windows server
> versions with freerdp downloaded from the git master at March 28, 2018.
> URL: https://github.com/FreeRDP/FreeRDP
>
> Apart from a version adjustment no changes where needed in the
> SlackBuild script.
>
>
> Regards,
>
> Kees Theunissen.
>
Thanks for that! I'm now running with git 20180405,

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] freerdp stopped working after latest Microsoft updates

[Duncan Roe]

Hi all,

I used to be able to connect to my Windows 7 home laptop with xfreerdp
(freerdp-git20160509-x86_64-1ffmpeg3_SBo).

But since yesterday when I ran Windows Update for the first time in 3 months, I
get these errors:

> [11:24:11:093] [2930:2931] [ERROR][com.freerdp.core.transport] - BIO_read 
> returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert 
> internal error
> [11:24:11:093] [2930:2931] [ERROR][com.freerdp.core] - freerdp_set_last_error 
> ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x2000D]
> [11:24:11:093] [2930:2931] [ERROR][com.freerdp.client.x11] - Freerdp connect 
> error exit status 1

Anyone else seen anything like this?

(Windows system patched with Concurrent_RDP_Patcher_KB3003743_Fix.zip to allow
RDP).

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Sage build still broken?

[Duncan Roe]

On Sun, Feb 25, 2018 at 10:59:25AM -0800, King Beowulf wrote:
> On 02/25/2018 08:44 AM, JCA wrote:
> > I built Sage 8.0 as available to Slackware 14.2 using the relevant
> > sbopkg queue.  The build process closes as follows:
> >
> > RROR:  The Sage installation tree has moved
> >
> > from /tmp/SBo/sage-8.0
> >   to /opt/sage
> >
> ---snip
> >
> >This in a freshly installed 14.2 system, with 24G RAM and 1TB disk
> > space. The compilation was completed normally, ending up with 13GB worth
> > of files in /tmp/SBo, and more than 5GB in /opt/sage.
> >
> >What have I done wrong? If nothing, is there any point in keeping
> > Sage in Slackbuilds? Even in a beefy system, compiling Sage takes a
> > several hours - and ending up with lots of GBs eaten up in your hard
> > drive and a nonfunctional application is frustrating.
> >
>
> I feel your pain, and I do not have a workable solution yet.  Sage
> upstream is completely hostile to relocatable packages it seems...  The
> core problem is in how the sage devs have designed their build system.
>
> There are 2 options to get sage working:
> 1. Download their compiled binary and run their script which will patch
> the hard coded paths.
> 2. Compile the sage source in a specific path and leave it there.  You
> will note that after running sage.Slackbuild it works just fine when
> invoked from /tmp/SBo/sage-8.0
> 3. Compile the sage source in a specific path (/opt/sage) and package it
> from there.
> 4. Compile the sage source in /tmp/sage-x but have a script to patch the
> paths to make the package relocatable.  This is what the devs do for
> their binary.
>
> I could just do (1) and forgo compiling.  SBo does that for some, but
> that is not optimal. (2) is non-starter: we just can't leave stuff
> littering /tmp!  Perhaps (3) in a chroot, etc, but I think (4) is
> cleaner if I can ever figure out how the script works in (1).  I'm
> missing a path or variable somewhere.
>
> tl;dr
>
> I'm working on it.
>
> -Ed
>
Hey Ed,

SBo has mkchroot which was put together to solve this kind of problem,

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] conky doesn't build LONGER

[Duncan Roe]

On Mon, Nov 20, 2017 at 12:47:24PM -0500, B Watson wrote:
> On 11/20/17, Matteo Bernardini  wrote:
>
> > - parallel install different lua versions;
> > - checking that the various things that need those find the right one
> > in each case.
> > ...but this solution is really hard to implement, as the script being
> > involved are =~ 150 and they have to be all tested working to
> > implement it on the repository.
> > if someone feels like doing this work it would be highly appreciated.
>
> Looks like a lot of stuff links with lua's shared libs. I'd say,
> keep things exactly as they are for lua 5.1, and add a lua53 build
> that installs version 5.3 to a different prefix (maybe /opt/lua-5.3),
> and doesn't install anything *at all* in /usr (except for /usr/doc/
> I suppose), so there's no chance of conflict.
>
> The lua53 build could also include a script, *disabled by default*,
> that sets $PATH and whatever else lua uses, with instructions in the
> README explaining how to source that script in .bash_profile. So if you
> want your user account to use lua-5.3 when you run a script that says
> "#!/usr/bin/env lua", you can, but root won't be set up that way. A
> script that says "#!/usr/bin/lua" will always run lua-5.1 though.
>
> Doing it that way, everything that currently uses lua 5.1 should continue
> to work as-is. Anything new that needs lua-5.3 will need to explicitly
> set the paths when building (maybe --with-lua=/opt/lua-5.3 or such,
> if it uses autotools), including -Wl,-rpath or whatever's needed to
> get the correct libs linked. SlackBuild scripts could also source the
> abovementioned environment script, if that would help.
>
> Once this is working, those 150 lua-using builds can slowly be tested
> against 5.3, and fixed/patched as needed. Or not: why bother? Working
> scripts are working scripts. Unless switching a script to use lua-5.3
> actually makes the built package more useful to end-users, what would
> be the point?
>
> Disclaimer: I know very little about lua. The only reason it's impinged
> on my awareness is that mame uses it... but it has to build its own
> lua-5.3 from bundled sources, because it can't use 5.1. The rest of
> mame's build system is actually written in lua, I'd love it if things
> could be arranged so that mame could use a pre-existing lua 5.3 install.
>
> The only game-changer here would be if Pat someday decided to include
> lua in core Slackware. No idea if that's likely, so no point worrying
> about it now.

If liblua.so has been bunped to liblua.so.6.x.y, then from a runtime point of
view it should be all right to install as standard. If not, report to upstream
as a bug.

What must not happen is for upgradepkg to remove liblua.so.5.

That could be achieved by having a new package say lua53, or having lua build
liblua.so.5 as well as liblua.so.6 (needs 2 tarballs: could have a COMPAT option
to not build old library).

Either way that should allow gentle migration, or am I missing something?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] [PATCH] SLURM no longer building

[Duncan Roe]

Hi,

The URL for slurm-17.02.7.tar.bz2 gets a 404. It is possible to get this version
via the home page, but the current version slurm-17.02.9 fetches just fine.

Also, the README was still referring to slurm-14.x for configuration file build.

The following patch fixes everything,

Cheers ... Duncan.

diff --git a/network/slurm/README b/network/slurm/README
index faf584c..3ae7439 100644
--- a/network/slurm/README
+++ b/network/slurm/README
@@ -16,7 +16,7 @@ is executed.
 # useradd -u 311 -d /var/lib/slurm -s /bin/false -g slurm slurm

 Next, a configuration file can be build using your favorite web browser
-and the file /usr/doc/slurm-14.11.8/html/configurator.html.
+and the file /usr/doc/slurm-17.02.9/html/configurator.html.

 Optional dependencies:
 HWLOC=yes|no (default: no), requires hwloc
diff --git a/network/slurm/slurm.SlackBuild b/network/slurm/slurm.SlackBuild
index 4f0adab..41e935d 100644
--- a/network/slurm/slurm.SlackBuild
+++ b/network/slurm/slurm.SlackBuild
@@ -23,7 +23,7 @@
 #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 PRGNAM=slurm
-VERSION=${VERSION:-17.02.7}
+VERSION=${VERSION:-17.02.9}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}

diff --git a/network/slurm/slurm.info b/network/slurm/slurm.info
index 61fdd20..3b5d50f 100644
--- a/network/slurm/slurm.info
+++ b/network/slurm/slurm.info
@@ -1,8 +1,8 @@
 PRGNAM="slurm"
-VERSION="17.02.7"
+VERSION="17.02.9"
 HOMEPAGE="http://slurm.schedmd.com/;
-DOWNLOAD="http://www.schedmd.com/download/latest/slurm-17.02.7.tar.bz2;
-MD5SUM="64009c1ed120b9ce5d79424dca743a06"
+DOWNLOAD="http://www.schedmd.com/download/latest/slurm-17.02.9.tar.bz2;
+MD5SUM="6bd0b38e6bf08f3426a7dd1e663a2e3c"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES="munge"
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Spelling error in perl-Unicode-Map README

[Duncan Roe]

Hi Larry,

The fiorst word in README (perl-Unicod-Map) is missing 'e' after 'd'

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20170923.1

[Duncan Roe]

Hi Willy,

I just noticed you're the maintainer ;)

On Sun, Sep 24, 2017 at 07:29:01PM +1000, Duncan Roe wrote:
> Hi Dave,
>
> On Sat, Sep 23, 2017 at 05:06:17PM +0100, David Spencer wrote:
> > Hello everybody,
> >
> > This week's public update is a bit later than usual, because of our
> > personal schedules :)
> >
> ...
> > libraries/webkit2gtk: Fix build issue on single job.
> ...
>
> It seems you need this:
>
> diff --git a/libraries/webkit2gtk/webkit2gtk.SlackBuild 
> b/libraries/webkit2gtk/webkit2gtk.SlackBuild
> index 57e4f2e..2f7c42e 100644
> --- a/libraries/webkit2gtk/webkit2gtk.SlackBuild
> +++ b/libraries/webkit2gtk/webkit2gtk.SlackBuild
> @@ -57,7 +57,7 @@ fi
>
>  # This is needed to fix build issue on single make job
>  # Thanks to ponce for investigating this issue.
> -MAKEFLAGS=${MAKEFLAGS:--j2}
> +export MAKEFLAGS=${MAKEFLAGS:--j2}
>
>  set -eu
>
>
> --
>
> My build just failed after 18 hrs. It only ever ran 1 cc1plus.
>
> With the patch, it's running 2 of them,
>
> Cheers ... Duncan.

My re-build ran to completion with the above patch.

However, I do wonder whether "make -j2" is simply masking a bug in the make
process.

Perhaps you might like to report the failure to upstream. Here's what I found:

As Chris Willing noted in
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-September/019991.html,
sources from the tarball #include WebCore/BackingStoreBackendCairoImpl.h whereas
the file exists at
webkitgtk-2.18.0/Source/WebCore/platform/HysteresisActivity.h.

The successful build generates
webkitgtk-2.18.0/build/DerivedSources/ForwardingHeaders/WebCore/BackingStoreBackendCairoImpl.h
which has the line

#include "WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.h"

(i.e. where the file really is). The single-job make doesn't even get to create
the directory webkitgtk-2.18.0/build/DerivedSources/ForwardingHeaders/WebCore/
before failing. Could this indicate an error in the build sequence?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20170923.1

[Duncan Roe]

Hi Dave,

On Sat, Sep 23, 2017 at 05:06:17PM +0100, David Spencer wrote:
> Hello everybody,
>
> This week's public update is a bit later than usual, because of our
> personal schedules :)
>
...
> libraries/webkit2gtk: Fix build issue on single job.
...

It seems you need this:

diff --git a/libraries/webkit2gtk/webkit2gtk.SlackBuild 
b/libraries/webkit2gtk/webkit2gtk.SlackBuild
index 57e4f2e..2f7c42e 100644
--- a/libraries/webkit2gtk/webkit2gtk.SlackBuild
+++ b/libraries/webkit2gtk/webkit2gtk.SlackBuild
@@ -57,7 +57,7 @@ fi

 # This is needed to fix build issue on single make job
 # Thanks to ponce for investigating this issue.
-MAKEFLAGS=${MAKEFLAGS:--j2}
+export MAKEFLAGS=${MAKEFLAGS:--j2}

 set -eu


--

My build just failed after 18 hrs. It only ever ran 1 cc1plus.

With the patch, it's running 2 of them,

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Mail archives seem to be unavailable

[Duncan Roe]

Hi Admins,

I tried to access the mail archives via the URL in the FAQ but Firefox couldn't
connect. On testing I found:

 - lists.slackbuilds.org answers pings
 - telnet to lists.slackbuilds.org port https gets connection refused
 - telnet to lists.slackbuilds.org port http gets connection refused

HTH,

Cheers ... Duncan.

--
 Please avoid sending me Word or PowerPoint attachments.
 See http://www.gnu.org/philosophy/no-word-attachments.html
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] pyPdf SlackBuild or can't upgrade sofastats

[Duncan Roe]

On Sun, Aug 27, 2017 at 10:01:01AM +0200, 414N wrote:
> Hello Duncan,
> thanks for your reply and sorry for the HTML-only message, I???ll make
> sure to send plaintext versions too. ;-)
> While the suggestion of mentioning the usage of |pip2tgz| to obtain
> pyPdf in the README of sofastats can indeed work as a quite good
> workaround to the issue at hand, I think there are some drawbacks to it:
>
>   * people who use automated tools to install packages (i.e. |sbopkg|)
> will build a package that won???t work at runtime, even if all the
> other hard-dependencies specified in the |REQUIRES| line are installed
>   * dependencies specified in the README should only be optional or
> recommended ones, not mandatory ones (at least, this is what I
> grasped here on SBo)
>
> I guess the second one clashes with the guidelines here on SBo, but I
> don???t know for sure.
> If someone knows better, please correct me if I???m wrong
>
> Cheers
>
> ???
>
> Alan Alberghini
>
> SBo clone: GitHub <https://github.com/414n/slackbuilds.org>
>
Hi Alan,

Sorry for the delay in replying - have had network problems this last week.

If pyPdf is only a *runtime* dependency, I believe you don't absolutely *have*
to have it as a requirement.

But really, the existing package should be renamed. This is not entirely
trivial: as well as renaming the directory the maintainer would also have to
rename a couple of files therein and edit the SlackBuild, info and slack-desc.

The required patches are below. I've cc'd the maintainer (Hi Brent!) in the
hope he can submit the new SB and withdraw the old one,

Cheers ... Duncan.

> On 20/08/2017 05:29, Duncan Roe wrote:
> > On Sat, Aug 19, 2017 at 06:06:47PM +0200, 414N wrote:
> >
> >> I'm working on an updated sofastats SlackBuild but I stumbled upon a
> >> dependency issue...
> >> It seems like the sofastats package depends since some time on the `pyPdf`
> >> python library for managing PDF exports (see the official documentation at
> >> http://www.sofastatistics.com/wiki/doku.php?id=help:linux_installation#packages_required_dependencies,
> >> although they only report distro-specific package names...). Problem is,
> >> that the pyPdf package on SBo is not the original library required for the
> >> build, but instead is a ~2011 fork based on that library that has since 
> >> gone
> >> separate ways and was renamed `PyPDF2`. This is also reflected on the 
> >> module
> >> name, as it is installed as PyPDF2 inside
> >> /usr/lib64/python2.7/site-packages/PyPDF2/.
> >> The full story of the forking is available on the official site of PyPDF2 
> >> at
> >> https://mstamy2.github.io/PyPDF2/, while the original library is still
> >> available at http://pybrary.net/pyPdf/.
> >> What I'd like to propose is:
> >>
> >> - to rename the current pyPdf package to the more proper `PyPDF2` name
> >>
> >> - to submit (I've already created a SlackBuild) the original unmaintained
> >> library as `pyPdf`, so the dependency can be set inside the updated
> >> sofastats.info
> >> --
> >> Alan Alberghini
> > Hi Alan,
> >
> > Please try to avoid sending HTML-only messages to the list in future.
> >
> > pyPdf is indexed by PyPI - the Python Package Index
> > (https://pypi.python.org/pypi),  so pip2tgz will build it. The package ends 
> > up
> > as pyPdf-1.13-x86_64-1_pip2_SBo.tgz. (PyPDF2 is also listed on PyPI BTW).
> >
> > Unfortunately you can't put a pip2tgz-built package as a dependency in
> > sofastats.info. You would have to mention it in the README as being 
> > required.
> > That would enable you to get the main SB out the door.
> >
> > I certainly agree that the existing pyPdf SB should be renamed,
> >
> > Cheers ... Duncan.

-

17:46:36$ diffdir -u /usr/src/slackbuilds/python/pyPdf .
Only in .: PyPDF2.SlackBuild
Only in .: PyPDF2.info
Only in /usr/src/slackbuilds/python/pyPdf: pyPdf.SlackBuild
Only in /usr/src/slackbuilds/python/pyPdf: pyPdf.info
diff -u /usr/src/slackbuilds/python/pyPdf/slack-desc ./slack-desc
--- /usr/src/slackbuilds/python/pyPdf/slack-desc2017-04-08 
09:57:55.0 +1000
+++ ./slack-desc2017-09-03 17:42:07.0 +1000
@@ -5,15 +5,15 @@
 # You must make exactly 11 lines for the formatting to be correct.  It's also
 # customary to leave one space after the ':' except on otherwise blank lines.

- |-handy-ruler--|
-pyPdf: pyPdf (Python PDF toolkit)
-pyPdf:
-pyPdf: A Pure-Python library built as a PDF toolkit.
-pyPdf:
-pyPdf:
-pyPdf:
-p

Re: [Slackbuilds-users] Updates - 20170902.1

[Duncan Roe]

Hi Willy,

libreoffice 5.4.1 is making the dangling symlink /usr/bin/spadmin ->
../../opt/libreoffice5.4/

Looks like spadmin has gone at 5.4,

Cheers ... Duncan.

On Sat, Sep 02, 2017 at 11:02:23AM +0100, David Spencer wrote:
> Hi folks!
>
> Only 99 commits this week.
>
> Sat Sep  2 09:29:23 UTC 2017
> academic/gspiceui: Updated for version 1.1.00.
> academic/libqalculate: Updated for version 2.0.0
> academic/pulseview: Switch to https.
> academic/qalculate-gtk: Updated for version 2.0.0
> academic/sigrok-cli: Switch to https.
> audio/guitarix: Updated for version 0.35.6.
> audio/kid3: Updated for version 3.5.0.
> desktop/fbmenugen: Updated for version 0.80.
> desktop/menutray: Updated for version 0.50.
> desktop/obbrowser: Updated for version 0.07.
> desktop/obmenu-generator: Updated for version 0.80.
> desktop/sawfish: Updated for version 1.12.90.
> desktop/slackware-xdg-menu: Fixed update-menus problem.
> development/asm6809: Fix bad commit d8d8d2be3.
> development/cppcms: Updated for version 1.1.1.
> development/dmd: Fixed download.
> development/jupyter-nbconvert: Updated for version 5.3.0.
> development/meson: Updated for version 0.42.0.
> development/rust: Updated for version 1.20.0.
> development/sassc: Added (C/C++ port of the Sass CSS precompiler).
> games/Pyfa: Updated for version 1.31.0.
> games/angband: Updated for version 4.1.0.
> games/commandergenius: Updated for version 1.9.9.5beta.
> games/doomretro: Updated for version 2.5.4.
> games/edgar: Updated for version 1.27.
> games/freeciv: Updated for version 2.5.9.
> games/instead: Updated for version 3.1.2.
> games/quake_shareware_data: Switch to https.
> games/solarus-quest-editor: Patched to fix guessing the assets dir.
> gis/Shapely: Updated for version 1.6.1.
> gis/geojson: Updated for version 2.1.0.
> graphics/barcode: Added (GNU Barcode).
> graphics/dxftoqet: Added (Element DXF Converter).
> graphics/opencollada: Updated for version 1.6.59
> graphics/openimageio: Updated for version 1.7.17
> libraries/VTK: Updated for version 8.0.1
> libraries/appstream-glib: Updated for version 0.7.2.
> libraries/libiio: Added (Linux Industrial I/O library).
> libraries/libmediainfo: Updated for version 0.7.98.
> libraries/libnodave: Added (Siemens S7 300/400 PLC library).
> libraries/librep: Updated for version 0.92.7.
> libraries/libsass: Added (Sass compiler written in C++).
> libraries/libserialport: Switch to https.
> libraries/libsigrok: Switch to https.
> libraries/libsigrokdecode: Switch to https.
> libraries/libwacom: Updated for version 0.26.
> libraries/libzen: Updated for version 0.4.36.
> libraries/ogre: Updated to latest 1.9 commits.
> libraries/stfl: Switch to i586.
> libraries/unibilium: Updated for version 1.2.1.
> misc/gprename: Patched to use DESTDIR.
> misc/sigrok-firmware-fx2lafw: Switch to https.
> multimedia/mediainfo: Updated for version 0.7.98.
> network/2ping: Added (bi-directional ping utility).
> network/mrtg: Switch to https.
> network/newsbeuter: Apply Podbeuter segfault fix.
> network/phpmyadmin: Updated for version 4.7.4.
> network/plowshare-modules: Updated for version 952eceb.
> network/plowshare: Updated for version 2.1.7.
> network/sickrage: Updated for version 2017.06.05_1.
> network/slimjet: Updated for version 15.1.1.0.
> network/tor: Updated for version 0.3.0.10.
> network/tornado: Updated for version 4.5.2.
> network/uget: Updated for version 2.0.10.
> network/wireshark: Updated for version 2.4.1.
> network/yandex-browser-beta: Updated for version 17.7.1.802.
> network/yle-dl: Added (Download videos from Yle servers).
> office/LibreOffice: Updated for version 5.4.1.2
> office/calibre: Updated for version 3.7.0
> office/extractpdfmark: Added (extract page mode etc from PDF).
> office/libreoffice-helppack: Updated for version 5.4.1.
> office/libreoffice-langpack: Updated for version 5.4.1.
> office/libreoffice: Updated for version 5.4.1.
> office/pdfchain: Updated for version 0.4.4.2.
> perl/perl-Math-GMPf: Updated for version 0.43.
> perl/perl-Sidef: Updated for version 3.03.
> python/dulwich: Updated for version 0.18.2.
> python/egenix-mx-base: Switch to https.
> python/hg-git: Updated for version 0.8.9.
> python/python-gattlib: Fixed odd permissions on some files.
> python/python-keyutils: Fix dep.
> python/python-progress: Added (easy to use progress bars).
> python/python-whisper: Fix SlackBuild.
> python/python3-tornado: Updated for version 4.5.2.
> system/ffproxy: Added (filtering HTTP/HTTPS proxy server).
> system/fileschanged: Added (File Alteration Monitor client).
> system/fpm2: Switch to https.
> system/fwupd: Updated for version 0.9.7.
> system/fzf: Updated for version 0.17.0.
> system/hfsprogs: Added (hfs+ user space utils).
> system/hungrycat: Updated for version 0.4.
> system/iucode_tool: Updated for version 2.2.
> system/mariadb-plugin-saslauthd: Updated for version 1.2.
> system/nagvis: Fixed build.
> system/noto-emoji: Updated for version gita4ddd5b.
> system/pv: New maintainer.
> 

Re: [Slackbuilds-users] pyPdf SlackBuild or can't upgrade sofastats

[Duncan Roe]

On Sat, Aug 19, 2017 at 06:06:47PM +0200, 414N wrote:

> I'm working on an updated sofastats SlackBuild but I stumbled upon a
> dependency issue...
> It seems like the sofastats package depends since some time on the `pyPdf`
> python library for managing PDF exports (see the official documentation at
> http://www.sofastatistics.com/wiki/doku.php?id=help:linux_installation#packages_required_dependencies,
> although they only report distro-specific package names...). Problem is,
> that the pyPdf package on SBo is not the original library required for the
> build, but instead is a ~2011 fork based on that library that has since gone
> separate ways and was renamed `PyPDF2`. This is also reflected on the module
> name, as it is installed as PyPDF2 inside
> /usr/lib64/python2.7/site-packages/PyPDF2/.
> The full story of the forking is available on the official site of PyPDF2 at
> https://mstamy2.github.io/PyPDF2/, while the original library is still
> available at http://pybrary.net/pyPdf/.
> What I'd like to propose is:
>
> - to rename the current pyPdf package to the more proper `PyPDF2` name
>
> - to submit (I've already created a SlackBuild) the original unmaintained
> library as `pyPdf`, so the dependency can be set inside the updated
> sofastats.info
> --
> Alan Alberghini

Hi Alan,

Please try to avoid sending HTML-only messages to the list in future.

pyPdf is indexed by PyPI - the Python Package Index
(https://pypi.python.org/pypi),  so pip2tgz will build it. The package ends up
as pyPdf-1.13-x86_64-1_pip2_SBo.tgz. (PyPDF2 is also listed on PyPI BTW).

Unfortunately you can't put a pip2tgz-built package as a dependency in
sofastats.info. You would have to mention it in the README as being required.
That would enable you to get the main SB out the door.

I certainly agree that the existing pyPdf SB should be renamed,

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@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] What happened to libssh2?

[Duncan Roe]

xen lists libssh2 as an optional dependency, but I can't find it at SBo.

It was there on Nov 10  2016, that's when I last built it.

Did I miss an announcement?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] What happened to libssh2?

[Duncan Roe]

xen lists libssh2 as an optional dependency, but I can't find it at SBo.

It was there on Nov 10  2016, that's when I last built it.

Did I miss an announcement?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] essential patch for afdko SB

[Duncan Roe]

Hi moderators,

The afdko SB needs this patch to work. Without it, the programs in it will
loop indefinitely, looking for the Tools directory.

Please apply when circumstances permit,

Cheers ... Duncan.

-8<--

diff -u /usr/src/slackbuilds/system/afdko/afdko.SlackBuild ./afdko.SlackBuild
--- /usr/src/slackbuilds/system/afdko/afdko.SlackBuild  2017-05-13 
11:33:55.0 +1000
+++ ./afdko.SlackBuild  2017-05-13 21:22:39.0 +1000
@@ -24,7 +24,7 @@

 PRGNAM=afdko
 VERSION=${VERSION:-2.5.65322}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2}
 TAG=${TAG:-_SBo}

 if [ -z "$ARCH" ]; then
@@ -81,12 +81,12 @@
 cd ../..

 # Replacement for make install
-mkdir -p $PKG/opt/$PRGNAM
-mv Tools/linux Tools/SharedData $PKG/opt/$PRGNAM
+mkdir -p $PKG/opt/$PRGNAM/Tools
+mv Tools/linux Tools/SharedData $PKG/opt/$PRGNAM/Tools

-mkdir -p $PKG/opt/$PRGNAM/linux/Python/Current/bin
+mkdir -p $PKG/opt/$PRGNAM/Tools/linux/Python/Current/bin
 ln -s $(readlink -f $(type -p python)) \
-  $PKG/opt/$PRGNAM/linux/Python/Current/bin/python2.7
+  $PKG/opt/$PRGNAM/Tools/linux/Python/Current/bin/python2.7

 find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | 
grep ELF \
   | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
diff -u /usr/src/slackbuilds/system/afdko/afdko.csh ./afdko.csh
--- /usr/src/slackbuilds/system/afdko/afdko.csh 2017-05-13 11:33:55.0 
+1000
+++ ./afdko.csh 2017-05-13 21:22:39.0 +1000
@@ -1,5 +1,5 @@
 #!/bin/csh
-setenv FDK_EXE /opt/afdko/linux
+setenv FDK_EXE /opt/afdko/Tools/linux
 if ( $?PATH ) then
   echo :${PATH}: | grep -q :${FDK_EXE}: || setenv PATH ${PATH}:${FDK_EXE}
 else
diff -u /usr/src/slackbuilds/system/afdko/afdko.sh ./afdko.sh
--- /usr/src/slackbuilds/system/afdko/afdko.sh  2017-05-13 11:33:55.0 
+1000
+++ ./afdko.sh  2017-05-13 21:22:39.0 +1000
@@ -1,5 +1,5 @@
 #!/bin/sh
-FDK_EXE="/opt/afdko/linux"
+FDK_EXE="/opt/afdko/Tools/linux"
 if [ ! "$PATH" = "" ]; then
   echo :$PATH: | grep -q :$FDK_EXE: || PATH=$PATH:$FDK_EXE
 else

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] ffmpeg

[Duncan Roe]

On Mon, Apr 17, 2017 at 08:23:47PM +0200, Chris Abela wrote:
> 1. On my machines, ffmpeg built against the previous version (à la
> wireshark). Removing it before building it again solved missing libraries
> issues.
>
> 2. On my second run, ffmpeg complained on missing chromaprint, despite that
> I had it. Disabling it solved this problem
>
> 3. On third time, I got lucky :-).
>
> Chris
>
>
I hit this yesterday. chromaprint has ffmpeg as an optional dependency, and vice
versa. So, circular dependency. Eventually this worked for me:

 - Build and install ffmpeg without chromaprint (no CHROMAPRINT=yes in the build
line) (VERSION=1a so upgradepkg will install it)
 - Build and install chromaprint
 - Rebuild and install ffmpeg, adding CHROMAPRINT=yes

Maybe I could have built chromaprint twice instead of ffmpeg, but it's done now.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] libebur128 source download gets 404

[Duncan Roe]

The published libebur128 URL

https://github.com/jiixyj/libebur128/archive/1.1.0/libebur128-1.1.0.tar.gz

needs a "v" in front of the revision

https://github.com/jiixyj/libebur128/archive/v1.1.0/libebur128-1.1.0.tar.gz

Willy?

On another note, libebur128 is now at version 1.2.2.

It appears to build OK with a version bump. 1.2.0 removed the dependency on
speex (I haven't myself tried to build w/out speex though).

(copy sent to maintainer),

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] LibreOffice requires

[Duncan Roe]

On Mon, Apr 10, 2017 at 01:04:54AM +0200, Andreas Guldstrand wrote:
> On 10 April 2017 at 00:57, Christoph Willing  
> wrote:
> > On 10/04/17 07:00, B Watson wrote:
> >> On 4/9/17, Andrzej Telszewski  wrote:
> >>>
> >>> I guess what Dimitris meant was that "openjdk" depends on "apache-ant",
> >>> and "LibreOffice" depends on "openjdk", so "apache-ant" might be removed
> >>> from "LibreOffice" requires, because it is pulled in, when "openjdk" is
> >>> pulled in.
> >>
> > Thanks all, will fix in next update.
> >
> > chris
>
> Does LibreOffice then not support being built with jdk instead of
> openjdk? Since regular jdk doesn't depend on apache-ant, then
> apache-ant won't be pulled in if regular jdk is uses instead of
> openjdk ... but perhaps apache-ant is only needed when building with
> openjdk?
>
> Would like a bit of clarification on this if possible?
>
> / Andreas

I've always built libreoffice (binary rmps) with regular jdk,

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Any interest in a qmail SlackBuild?

[Duncan Roe]

Hi Rob,

Thanks for putting together such a detailed response.

On Wed, Mar 08, 2017 at 09:13:36AM -0600, Rob McGee wrote:
> On Wed, Mar 08, 2017 at 10:39:50AM +1100, Duncan Roe wrote:
> > Would anyone use a SlackBuild for the qmail Mail Transport Agent
> > if one was available?
>
> I would recommend against it, as qmail was abandoned almost 20 years
> ago, and the world of email has not stood still in that time.  Even
> netqmail, the semi-official "patched" version which addresses flaws
> which were found in the final qmail release, is way behind.

Neither would I recommend anyone not already using qmail to start using it, so
we agree on that. The SB is intended for folk who are using qmail now and might
like a clean way to install and remove the latest version there is.
>
> You have to add multiple patches to qmail to get important basic
> functionality.  Of course, now that the original is in the public
> domain, you could just prepatch and distribute your own "dqmail" or
> whatever. :)

Netqmail 1.06 looks after that, up to November 2007 anyway. That's what the SB
installs.
>
> > I have written, for my own use, SB's for qmail, its prereq
> > daemontools, and an optional dependency serialmail.
> >
> > I ask if there's any interest, because it will take extra effort
> > to put the builds into a state where they are acceptable to the
> > moderators,
>
> In 2003-05 I worked in a consultancy which (among other things)
> provided qmail for SMB clients, and ugh, that was awful.  I
> personally stayed away from the install of daemontools and qmail;
> boss had that all scripted, adapted to Slackware from the once-
> popular "Life with qmail" (LWQ) howto.

I'm sorry to hear of your unfortunate experience with qmail. qmail has "just
worked" for me since I installed it in 1996.

I have SB's for daemontools, netqmail and serialmail now. The netqmail SB can do
all the configuration in LWQ section 2 except the tests in section 2.9, which
pass when run. It only goes ahead with the invasive parts of section 2 (such as
creating the groups and users) if controlling environment variables are set.
>
> Dr. Bernstein had different ideas about Unix, and indeed, it's
> difficult to imagine having all this stuff packaged according to
> SBo/Slackware standards.
>
> If it's still working for you, fine, but the day of qmail is over;
> let it remain in the past.  Those who are wanting to learn MTA
> management first should have a psychiatric evaulation, and then
> should choose a modern and well-maintained project, such as Exim,
> Postfix, or yes, even Sendmail MTA.
>
> NB: this is a personal opinion and definitely not to be considered
> SBo "official policy."  If you want to make a qmail build, you are
> welcome to develop and to submit it.

On a clean system, with the right environment variables set I can install
daemontools and netqmail and on completion have a running qmail which passes
"qmailctl stat" and "inst_check" tests.

That is the build system I am offering,

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Any interest in a qmail SlackBuild?

[Duncan Roe]

On Wed, Mar 08, 2017 at 02:28:16AM +0100, Andrzej Telszewski wrote:
> On 08/03/17 00:39, Duncan Roe wrote:
> > Would anyone use a SlackBuild for the qmail Mail Transport Agent if one was
> > available?
> >
> > I have written, for my own use, SB's for qmail, its prereq daemontools, and 
> > an
> > optional dependency serialmail.
> >
> > I ask if there's any interest, because it will take extra effort to put the
> > builds into a state where they are acceptable to the moderators,
> >
> > Cheers ... Duncan.
>
> I would say do it properly and submit to SBo, it'll pay back with better
> quality and availability in the future.
> If you have time required, of course.
>
> I'm selfish and I normally wouldn't submit any of my work, but SBo is such a
> nice backup store for my SlackBuilds :^)
>
> --
> Best regards,
> Andrzej Telszewski

The problem is avoiding novelty, rather tnan doing it properly.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Any interest in a qmail SlackBuild?

[Duncan Roe]

Would anyone use a SlackBuild for the qmail Mail Transport Agent if one was
available?

I have written, for my own use, SB's for qmail, its prereq daemontools, and an
optional dependency serialmail.

I ask if there's any interest, because it will take extra effort to put the
builds into a state where they are acceptable to the moderators,

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] gdal SlackBuild fails

[Duncan Roe]

On Sat, Mar 04, 2017 at 03:11:36PM +0100, Matteo Bernardini wrote:
> 2017-03-04 15:02 GMT+01:00 Duncan Roe <duncan_...@acslink.net.au>:
> > On Sat, Mar 04, 2017 at 12:15:29PM +0100, Matteo Bernardini wrote:
> >> 2017-03-04 12:06 GMT+01:00 Duncan Roe <duncan_...@acslink.net.au>:
> >> > On Sat, Mar 04, 2017 at 09:48:36PM +1100, Duncan Roe wrote:
> >> >> Paste is http://pastebin.com/v4gXJbDr
> >> >>
> >> > And, I did not override -j1. This pocessor does have 2 cores though.
> >>
> >> Duncan, sorry, before anyone else asks: the paste above looks done
> >> from your unprivilege used environment.
> >> it could be there are no differences but maybe it's better if you post
> >> the one you got from running the SlackBuild (you can take it directly
> >> from the /tm/SBo/gdal-* directory) from the root environment (in which
> >> you get by running "su -l" from your user shell).
> >>
> >> Matteo
> >
> > Hi Matteo,
> >
> > I ran the build from a logged-in-as-root environment, as evidenced by:
> >
> >> 22:00:11# echo $0
> >> -bash
> >
> > I just do su but then immediately start a fresh xterm (with a pink 
> > background,
> > so I know it's root); then exit from the su.
> >
> > What looks unprivileged in the paste?
>
> in the paste you have these lines
>
> PATH: /home/dunc/bin64
> PATH: /home/dunc/bin
> PATH: /home/dunc/command_line_tools/bin
> PATH: /usr/local/sbin
> PATH: /usr/sbin
> PATH: /sbin
> PATH: /usr/local/bin
> PATH: /usr/bin
> PATH: /bin
> PATH: /usr/games
> PATH: /usr/lib/java/bin
> PATH: /usr/lib64/kde4/libexec
> PATH: /usr/lib64/qt/bin
> PATH: /usr/share/texmf/bin
>
> these mean that you have executed just "su" and not "su -" (or "su
> -l") so your root environment, not having being launched as a true
> login shell, was polluted by user variables (see point 3 of the howto
> https://slackbuilds.org/howto/).
> you shouldn't run SBo's build scripts executing just "su".
>
> Matteo

No, they don't mean that at all:
> 00:47:13# ls -l ~/.bashrc
> lrwxrwxrwx 1 root root 18 May  5  2014 /root/.bashrc -> /home/dunc/.bashrc

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] gdal SlackBuild fails

[Duncan Roe]

On Sat, Mar 04, 2017 at 12:15:29PM +0100, Matteo Bernardini wrote:
> 2017-03-04 12:06 GMT+01:00 Duncan Roe <duncan_...@acslink.net.au>:
> > On Sat, Mar 04, 2017 at 09:48:36PM +1100, Duncan Roe wrote:
> >> On Fri, Mar 03, 2017 at 12:19:09PM +, David Spencer wrote:
> >> > > Looks like the kind of issue caused by using MAKEFLAGS=-j3 (or anything
> >> > > other than -j1). That's a snap diagnosis, I don't know what gdal even 
> >> > > is.
> >> >
> >> > gdal already has 'make -j1' hard-coded, because it definitely fails
> >> > with multiple parallel make jobs.
> >> >
> >> > For some reason that I don't understand, on Duncan's system gcc is
> >> > being invoked through libtool.
> >> > The compilation explicitly has '-o
> >> > build/temp.linux-x86_64-2.7/extensions/.libs/gdal_wrap.o', but that
> >> > file does not exist at the time the next command 'g++ -pthread -shared
> >> > build/temp.linux-x86_64-2.7/extensions/gdal_wrap.o' is invoked.
> >> >
> >> > So this really does look like a multiple parallel make jobs failure.
> >> > Duncan, for avoidance of doubt you haven't removed -j1 or overridden it 
> >> > somehow?
> >> > Are you on -current?
> >> > Do you have CC and/or CXX defined in the environment?
> >> > could you put your config.log on pastebin or somewhere similar?
> >> >
> >> Hi David,
> >>
> >> On 14.2 unpatched
> >>
> >> env has CC=gcc
> >>
> >> Paste is http://pastebin.com/v4gXJbDr
> >>
> > And, I did not override -j1. This pocessor does have 2 cores though.
>
> Duncan, sorry, before anyone else asks: the paste above looks done
> from your unprivilege used environment.
> it could be there are no differences but maybe it's better if you post
> the one you got from running the SlackBuild (you can take it directly
> from the /tm/SBo/gdal-* directory) from the root environment (in which
> you get by running "su -l" from your user shell).
>
> Matteo

Hi Matteo,

I ran the build from a logged-in-as-root environment, as evidenced by:

> 22:00:11# echo $0
> -bash

I just do su but then immediately start a fresh xterm (with a pink background,
so I know it's root); then exit from the su.

What looks unprivileged in the paste?

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] SOLVED: gdal SlackBuild fails

[Duncan Roe]

On Sat, Mar 04, 2017 at 10:06:09PM +1100, Duncan Roe wrote:
> On Sat, Mar 04, 2017 at 09:48:36PM +1100, Duncan Roe wrote:
> > On Fri, Mar 03, 2017 at 12:19:09PM +, David Spencer wrote:
> > > > Looks like the kind of issue caused by using MAKEFLAGS=-j3 (or anything
> > > > other than -j1). That's a snap diagnosis, I don't know what gdal even 
> > > > is.
> > >
> > > gdal already has 'make -j1' hard-coded, because it definitely fails
> > > with multiple parallel make jobs.
> > >
> > > For some reason that I don't understand, on Duncan's system gcc is
> > > being invoked through libtool.
> > > The compilation explicitly has '-o
> > > build/temp.linux-x86_64-2.7/extensions/.libs/gdal_wrap.o', but that
> > > file does not exist at the time the next command 'g++ -pthread -shared
> > > build/temp.linux-x86_64-2.7/extensions/gdal_wrap.o' is invoked.
> > >
> > > So this really does look like a multiple parallel make jobs failure.
> > > Duncan, for avoidance of doubt you haven't removed -j1 or overridden it 
> > > somehow?
> > > Are you on -current?
> > > Do you have CC and/or CXX defined in the environment?
> > > could you put your config.log on pastebin or somewhere similar?
> > >
> > Hi David,
> >
> > On 14.2 unpatched
> >
> > env has CC=gcc
> >
> > Paste is http://pastebin.com/v4gXJbDr
> >
> And, I did not override -j1. This pocessor does have 2 cores though.
>
I removed CC=gcc from the environment and the SB ran to completion.

It's been in my .bashrc for years, will take it out.

Cheers ... Duncan.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/