Re: [Slackbuilds-users] Update Apache Tomcat for new version 22
On 18/07/22 15:45,
Jheengut Pritvi put forth the proposition:
> Hi Dave,
>
> I was never before requested to send patches as such and I sent the email
> to the maintainer and CC to slackbuilds. By experience, if the maintainer
> is not free or could not have time to update, someone in the admins would
> patch it themselves.
We do accept patches if you don't hear back from the maintainer
within a reasonable time. It's usually best to wait a few days to
give them chance to reply.
Or if you know that the maintainer hasn't been active for a very long
time then that's OK too.
> Thanks
> Pritvi
>
> On Mon, 18 Jul 2022 at 15:25, Dave Woodfall wrote:
>
> > On 18/07/22 12:21,
> > Dave Woodfall put forth the proposition:
> > > On 18/07/22 15:01,
> > > Jheengut Pritvi put forth the proposition:
> > > > Hi,
> > > >
> > > > Apache Tomcat has been updated to version 10.0.22.
> > > >
> > > > Please accept the diff ==>
> > > >
> > > >
> > > > root:/var/lib/sbopkg/SBo/15.0/system/apache-tomcat# diff
> > apache-tomcat.info
> > > > apache-tomcat.info.sbopkg
> > > > 2c2
> > > > < VERSION="10.0.20"
> > > > ---
> > > > > VERSION="10.0.22"
> > > > 4,5c4,5
> > > > < DOWNLOAD="
> > > >
> > https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.20/bin/apache-tomcat-10.0.20.tar.gz
> > "
> > > >
> > > > < MD5SUM="cc94dae513e06c3f9dae191a73cdd558"
> > > > ---
> > > > > DOWNLOAD="
> > > >
> > https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.22/bin/apache-tomcat-10.0.22.tar.gz
> > "
> > > >
> > > > > MD5SUM="e01967a23bd19fa1cc314215edfbe92d"
> > > >
> > > > root:/var/lib/sbopkg/SBo/15.0/system/apache-tomcat# diff
> > > > apache-tomcat.SlackBuild apache-tomcat.SlackBuild.sbopkg
> > > > 29c29
> > > > < VERSION=${VERSION:-10.0.20}
> > > > ---
> > > > > VERSION=${VERSION:-10.0.22}
> > > >
> > > >
> > > >
> > > > Best regards
> > > > Pritvi Jheengut
> > >
> > > Can you please add patches as attachments?
> > >
> > > Quick way without git - `a' is the old slackbuild directory, `b' is
> > > the updated slackbuild directory:
> > >
> > > LC_ALL=C TZ=UTC0 diff -Naur a b > whatever-update.patch
> > >
> > > Then attach the patch here.
> > >
> > > Thanks.
> > >
> > > It's easier for us than copy/pasting from emails.
> > >
> > > Willy has a HOWTO on making git patches on his blog.
> > >
> >
> > You aren't the maintainer. If you haven't yet, please first contact
> > the maintainer to ask about updating it.
> >
> > Thanks
> >
> > --
> > Dave
> >
> > sbo-maintainer-tools:
> > https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
> > SBo templates:
> > https://slackbuilds.org/templates/
> > How to format github downloads:
> > https://slackbuilds.org/GITHUB_URLs.txt
> >
> >
> 2c2
> < VERSION="10.0.20"
> ---
> > VERSION="10.0.22"
> 4,5c4,5
> <
> DOWNLOAD="https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.20/bin/apache-tomcat-10.0.20.tar.gz;
> < MD5SUM="cc94dae513e06c3f9dae191a73cdd558"
> ---
> > DOWNLOAD="https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.22/bin/apache-tomcat-10.0.22.tar.gz;
> > MD5SUM="e01967a23bd19fa1cc314215edfbe92d"
> 29c29
> < VERSION=${VERSION:-10.0.20}
> ---
> > VERSION=${VERSION:-10.0.22}
--
Dave
sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt
___
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 15.1-current] Cairo Clock?
On 17/07/22 03:06, David Chmelik put forth the proposition: > Does anyone use Slackware 15.1-current (especially x86(64)) with Cairo > Clock? > It works on Slackware 15-stable but I help test Slackware-current > and get new features so mostly use it since mid-to-late 2010s except servers > and secondary PCs. > On Slackware-current (x86(64)) Cairo Clock goes to taskbar (in KDE, > XFCE) but has no window (and may not work on old window managers (WM). I > told maintainer in early April but got no reply so I guess doesn't care > about Slackware-current. > Analogue clocks are faster to read than digital. KDE has analogue > clock widget but not standard/normal 12-marks rather than 'trendy' with few > marks (harder to read than normal/standard digital.) > Hi Have you tried asking on the LQ forum for scripts in -current about this? https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/ -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] Update Apache Tomcat for new version 22
On 18/07/22 12:21,
Dave Woodfall put forth the proposition:
> On 18/07/22 15:01,
> Jheengut Pritvi put forth the proposition:
> > Hi,
> >
> > Apache Tomcat has been updated to version 10.0.22.
> >
> > Please accept the diff ==>
> >
> >
> > root:/var/lib/sbopkg/SBo/15.0/system/apache-tomcat# diff apache-tomcat.info
> > apache-tomcat.info.sbopkg
> > 2c2
> > < VERSION="10.0.20"
> > ---
> > > VERSION="10.0.22"
> > 4,5c4,5
> > < DOWNLOAD="
> > https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.20/bin/apache-tomcat-10.0.20.tar.gz;
> >
> > < MD5SUM="cc94dae513e06c3f9dae191a73cdd558"
> > ---
> > > DOWNLOAD="
> > https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.22/bin/apache-tomcat-10.0.22.tar.gz;
> >
> > > MD5SUM="e01967a23bd19fa1cc314215edfbe92d"
> >
> > root:/var/lib/sbopkg/SBo/15.0/system/apache-tomcat# diff
> > apache-tomcat.SlackBuild apache-tomcat.SlackBuild.sbopkg
> > 29c29
> > < VERSION=${VERSION:-10.0.20}
> > ---
> > > VERSION=${VERSION:-10.0.22}
> >
> >
> >
> > Best regards
> > Pritvi Jheengut
>
> Can you please add patches as attachments?
>
> Quick way without git - `a' is the old slackbuild directory, `b' is
> the updated slackbuild directory:
>
> LC_ALL=C TZ=UTC0 diff -Naur a b > whatever-update.patch
>
> Then attach the patch here.
>
> Thanks.
>
> It's easier for us than copy/pasting from emails.
>
> Willy has a HOWTO on making git patches on his blog.
>
You aren't the maintainer. If you haven't yet, please first contact
the maintainer to ask about updating it.
Thanks
--
Dave
sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt
___
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] Update Apache Tomcat for new version 22
On 18/07/22 15:01,
Jheengut Pritvi put forth the proposition:
> Hi,
>
> Apache Tomcat has been updated to version 10.0.22.
>
> Please accept the diff ==>
>
>
> root:/var/lib/sbopkg/SBo/15.0/system/apache-tomcat# diff apache-tomcat.info
> apache-tomcat.info.sbopkg
> 2c2
> < VERSION="10.0.20"
> ---
> > VERSION="10.0.22"
> 4,5c4,5
> < DOWNLOAD="
> https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.20/bin/apache-tomcat-10.0.20.tar.gz;
>
> < MD5SUM="cc94dae513e06c3f9dae191a73cdd558"
> ---
> > DOWNLOAD="
> https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.22/bin/apache-tomcat-10.0.22.tar.gz;
>
> > MD5SUM="e01967a23bd19fa1cc314215edfbe92d"
>
> root:/var/lib/sbopkg/SBo/15.0/system/apache-tomcat# diff
> apache-tomcat.SlackBuild apache-tomcat.SlackBuild.sbopkg
> 29c29
> < VERSION=${VERSION:-10.0.20}
> ---
> > VERSION=${VERSION:-10.0.22}
>
>
>
> Best regards
> Pritvi Jheengut
Can you please add patches as attachments?
Quick way without git - `a' is the old slackbuild directory, `b' is
the updated slackbuild directory:
LC_ALL=C TZ=UTC0 diff -Naur a b > whatever-update.patch
Then attach the patch here.
Thanks.
It's easier for us than copy/pasting from emails.
Willy has a HOWTO on making git patches on his blog.
--
Dave
sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt
___
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] MEGAcmd-1.5.1_Linux
On 25/06/22 07:55,
ABE Shin-ichi put forth the proposition:
> Sorry, previous diff of SlackBuild was not correct.
> Here is a correct diff.
> --- MEGAcmd.SlackBuild2022-04-02 20:23:28.0 +0900
> +++ MEGAcmd.SlackBuild.new2022-06-25 07:48:07.785686653 +0900
> @@ -26,8 +26,8 @@
> cd $(dirname $0) ; CWD=$(pwd)
> PRGNAM=MEGAcmd
> -VERSION=${VERSION:-1.5.0}
> -SDK=${SDK:-3.9.11b}
> +VERSION=${VERSION:-1.5.1}
> +SDK=${SDK:-3.9.11d}
> BUILD=${BUILD:-1}
> TAG=${TAG:-_SBo}
> PKGTYPE=${PKGTYPE:-tgz}
Done.
Willy wrote an article on his blog on how to send patches here:
https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html
Dave
> On Sat, 25 Jun 2022 06:34:19 +0900
> ABE Shin-ichi wrote:
> > Hi,
> >
> > I'm a maintainer of MEGAcmd.
> > Since MEGAcmd-1.5.1_Linux has been released a few days ago, I updated SBo
> > script as follows.
> >
> >
> > 1. Change to MEGAcmd.SlackBuild
> > === BEGIN diff ===
> >
> > --- MEGAcmd.SlackBuild 2022-04-02 20:23:28.0 +0900
> > +++ MEGAcmd.SlackBuild.new 2022-06-25 06:09:44.189881176 +0900
> > @@ -26,8 +26,8 @@
> > cd $(dirname $0) ; CWD=$(pwd)
> >
> > PRGNAM=MEGAcmd
> > -VERSION=${VERSION:-1.5.0}
> > -SDK=${SDK:-3.9.11b}
> > +VERSION=${VERSION:-1.5.1}
> > +SDK=${SDK:-3.9.11d}
> > BUILD=${BUILD:-1}
> > TAG=${TAG:-_SBo}
> > PKGTYPE=${PKGTYPE:-tgz}
> > @@ -104,6 +104,11 @@
> > 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
> >
> > +find $PKG -name perllocal.pod \
> > + -o -name ".packlist" \
> > + -o -name "*.bs" \
> > + | xargs rm -f
> > +
> > mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
> > cp -a \
> >LICENSE README.md UserGuide.md $PKG/usr/doc/$PRGNAM-$VERSION
> >
> > === END diff ===
> >
> > 2. Change to MEGA.info
> > === BEGIN diff ===
> >
> > --- MEGAcmd.info2022-04-02 20:23:28.0 +0900
> > +++ MEGAcmd.info.new2022-06-25 06:09:59.503880671 +0900
> > @@ -1,10 +1,10 @@
> > PRGNAM="MEGAcmd"
> > -VERSION="1.5.0"
> > +VERSION="1.5.1"
> > HOMEPAGE="https://github.com/meganz/MEGAcmd;
> > -DOWNLOAD="https://github.com/meganz/MEGAcmd/archive/1.5.0_Linux/MEGAcmd-1.5.0_Linux.tar.gz
> > \
> > -
> > https://github.com/meganz/sdk/archive/v3.9.11b/sdk-3.9.11b.tar.gz;
> > -MD5SUM="4f6f71a7e43e3096406657b5bb44bd99 \
> > -e8bafc8be1fefb17fc09513d79ffa58b"
> > +DOWNLOAD="https://github.com/meganz/MEGAcmd/archive/1.5.1_Linux/MEGAcmd-1.5.1_Linux.tar.gz
> > \
> > +
> > https://github.com/meganz/sdk/archive/v3.9.11d/sdk-3.9.11d.tar.gz;
> > +MD5SUM="a0047f8f025c46b4646c8e7f953b79d8 \
> > +5028b95cad49c7cc654d1249e39e8f84"
> > DOWNLOAD_x86_64=""
> > MD5SUM_x86_64=""
> > REQUIRES="FreeImage libmediainfo"
> >
> > === END diff ===
> >
> > 3. ChangeLog
> >
> > From build/megacmd/debian.changelog
> >
> > megacmd (1.5.1) stable; urgency=low
> >
> > * Security adjustments
> >
> > -- MEGA Team Wed, 15 Jun 2022 17:55:34 +0200
> >
> >
> >
> > Thank you for maintaining slackbuils_org.
> > Cheers,
> >
> > JW
> >
> > --
> > JW (ABE Shin-ichi)
> --
> JW (ABE Shin-ichi )
--
Dave
sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt
___
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] (no subject)
On 16/06/22 17:09, Fernando Lopez put forth the proposition: > any ideas on how to fix this issue with nvidia-legacy390-kernel (390.151)? > I am running slackware current kernel 5.18.3. > CONFTEST: is_export_symbol_gpl_refcount_inc > CONFTEST: is_export_symbol_gpl_refcount_dec_and_test > CC [M] /tmp/SBo/NVIDIA-Linux-x86_64-390.151/kernel/nvidia/nv-frontend.o > CC [M] /tmp/SBo/NVIDIA-Linux-x86_64-390.151/kernel/nvidia/nv-instance.o > CC [M] /tmp/SBo/NVIDIA-Linux-x86_64-390.151/kernel/nvidia/nv-gpu-numa.o > CC [M] /tmp/SBo/NVIDIA-Linux-x86_64-390.151/kernel/nvidia/nv.o > /tmp/SBo/NVIDIA-Linux-x86_64-390.151/kernel/nvidia/nv.c: In function > ‘nv_set_dma_address_size’: > /tmp/SBo/NVIDIA-Linux-x86_64-390.151/kernel/nvidia/nv.c:2745:9: error: > implicit declaration of function ‘pci_set_dma_mask’ > [-Werror=implicit-function-declaration] > 2745 | pci_set_dma_mask(nvl->dev, new_mask); > | ^~~~ That's probably defined in a header, but not found, probably due to kernel changes since then. At a guess I'd think you'd need to #include somewhere in nv.c or nv.h if it exists. -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] Question about sbo-maintainer-tools
On 09/06/22 09:33, Franzen via SlackBuilds-users put forth the proposition: > Hi, > this week a submission from me was rejected because i had a too long line in > slack-desc, the mail from the maintainer said: > slack-desc:11: line length longer than maximum of 78 (79) > This looks like an output from sbolint, but i had checked my script with it, > it didn't output a problem. > I can't find anything what checks about 'line length' in the scripts from > sbo-maintainer-tools, do you sbo-maintainers use > another version or additional lint scripts? > i've got version 0.5.1 installed. > Johannes The comma at the end of line 11 is just past the edge of the ruler. That was from my own lint script that checks the length of $PRGNAM + length of handy-ruler. > Long description of appname, wrapped at 71 characters *after* the > colon following "appname" (and the 'handy ruler' should start at > that colon and be exactly 71 characters long). -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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/pysqlite can be removed
> python/pysqlite is largely unmaintained upstream (replaced by sqlite3 in the > python standard library). As far as I can tell nothing depends on it > anymore. Unless someone sees a reason to maintain it, can it be removed? > Thanks, > Barry Done. -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] DevIL - Does not Compile when nvidia-texture-tools is installed
> > On 22/05/22 14:46, > > Konrad J Hambrick put forth the proposition: > > > All -- > > > I emailed the maintainer on May 12 but have received no reply. > > > Below is the email I sent. > > > The Punchline is that the DevIL SBo will not compile on my Slackware64 > > > 15.0 + Multilib System when the nvidia-texture-tools SBo is installed. > > > The simplest fix is to turn off nvidia-texture-tools via a cmake Config > > > > > Is this the best place to post such info ? > > > Thanks everyone ! > > > -- kjh > > This is the right place, usually we accept patches as attachments, > > but if this only the one flag. I can take a look this week. > > We don't support multilib though, so do you know if it fails still on > > a non-multilib full 15.0 installation? > It still fails on pure 15.0. The error I get is a missing > mvcore/Memory,h which was included in nvidia-texture-tools nvcore/Memory.h even. -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] DevIL - Does not Compile when nvidia-texture-tools is installed
> On 22/05/22 14:46, > Konrad J Hambrick put forth the proposition: > > All -- > > I emailed the maintainer on May 12 but have received no reply. > > Below is the email I sent. > > The Punchline is that the DevIL SBo will not compile on my Slackware64 > > 15.0 + Multilib System when the nvidia-texture-tools SBo is installed. > > The simplest fix is to turn off nvidia-texture-tools via a cmake Config > > > Is this the best place to post such info ? > > Thanks everyone ! > > -- kjh > This is the right place, usually we accept patches as attachments, > but if this only the one flag. I can take a look this week. > We don't support multilib though, so do you know if it fails still on > a non-multilib full 15.0 installation? It still fails on pure 15.0. The error I get is a missing mvcore/Memory,h which was included in nvidia-texture-tools but isn't in the version on SBo or the latest. > Link to blog post on sending patches: > https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html. -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] DevIL - Does not Compile when nvidia-texture-tools is installed
On 22/05/22 14:46,
Konrad J Hambrick put forth the proposition:
> All --
> I emailed the maintainer on May 12 but have received no reply.
> Below is the email I sent.
> The Punchline is that the DevIL SBo will not compile on my Slackware64
> 15.0 + Multilib System when the nvidia-texture-tools SBo is installed.
> The simplest fix is to turn off nvidia-texture-tools via a cmake Config
> Is this the best place to post such info ?
> Thanks everyone !
> -- kjh
This is the right place, usually we accept patches as attachments,
but if this only the one flag. I can take a look this week.
We don't support multilib though, so do you know if it fails still on
a non-multilib full 15.0 installation?
Link to blog post on sending patches:
https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html.
> # --original email to the maintainer
> Yth - Arnaud
> I am running Slackware64 15.0 System with Multilib +
> NVIDIA-Linux-x86_64-510.68.02.run
> I discovered that if nvidia-texture-tools ( aka nvtt ) is installed, that
> DevIL will not compile.
> I tried with nvidia-texture-tools version 2.1.1 and also with the more
> recent version 2.1.2
> There are missing Header Files in /usr/include/nvcore/ ( and maybe others )
> To reproduce: build and install nvidia-texture-tools.SlackBuild and then
> try to build DevIL.SlackBuild
> I changed the nvidia-texture-tools CMakeLists.txt so that the header files
> are installed in /usr/include/{nvtt,nvthread,nvmath,nvimage,nvcore}/
> as well as installing nvconfig.h
> The DevIL.SlackBuild compile makes it past the missing Headers in src-IL/
> However, the compiler finally fails building
> src-IL/CMakeFiles/IL.dir/src/il_nvidia.cpp.o because the nvtt headers
> differ from what is DevIL expects to find ( output below mu sig )
> I found a CMake switch ( -DIL_USE_DXTC_NVIDIA=NO ) that can be turned off
> in the DevIL.SlackBuild to avoid nvtt altogether.
> Then it builds as expected.
> Here is diff -Naur
> # cut here --
> # diff -Naur DevIL~01.SlackBuild DevIL.SlackBuild
> --- or/DevIL.SlackBuild 2022-04-23 17:41:07.620019227 -0500
> +++ DevIL.SlackBuild2022-05-12 11:19:49.873854478 -0500
> @@ -73,6 +73,7 @@
> -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
> -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS -std=c++14 -fpermissive" \
> -DCMAKE_INSTALL_PREFIX=/usr \
> +-DIL_USE_DXTC_NVIDIA=NO \
> -DCMAKE_BUILD_TYPE=Release ..
>make
>make install/strip DESTDIR=$PKG
> # - cut there ---
> Thanks for all the SlackBuilds !
> -- kjh
> This is the failure after installing the nvtt header files.
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp: In function 'ILubyte*
> ilNVidiaCompressDXT(ILubyte*, ILuint, ILuint, ILuint, ILenum, ILuint*)':
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:104:28: error: cannot declare
> variable 'outputHandler' to be of abstract type 'ilOutputHandlerMem'
> 104 | ilOutputHandlerMem outputHandler(Width, Height, DxtFormat);
> |^
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:38:8: note: because the
> following virtual functions are pure within 'ilOutputHandlerMem':
>38 | struct ilOutputHandlerMem : public nvtt::OutputHandler
> |^~
> In file included from /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:20:
> /usr/include/nvtt/nvtt.h:341:22: note: 'virtual void
> nvtt::OutputHandler::endImage()'
> 341 | virtual void endImage() = 0;
> | ^~~~
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp: In function 'ILuint
> ilNVidiaCompressDXTFile(ILubyte*, ILuint, ILuint, ILuint, ILenum)':
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:188:29: error: cannot declare
> variable 'outputHandler' to be of abstract type 'ilOutputHandlerFile'
> 188 | ilOutputHandlerFile outputHandler(Width, Height, DxtFormat);
> | ^
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:148:8: note: because the
> following virtual functions are pure within 'ilOutputHandlerFile':
> 148 | struct ilOutputHandlerFile : public nvtt::OutputHandler
> |^~~
> In file included from /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:20:
> /usr/include/nvtt/nvtt.h:341:22: note: 'virtual void
> nvtt::OutputHandler::endImage()'
> 341 | virtual void endImage() = 0;
> | ^~~~
> make[2]: *** [src-IL/CMakeFiles/IL.dir/build.make:678:
> src-IL/CMakeFiles/IL.dir/src/il_nvidia.cpp.o] Error 1
> make[1]: *** [CMakeFiles/Makefile2:134: src-IL/CMakeFiles/IL.dir/all] Error
> 2
> make: *** [Makefile:136: all] Error 2
--
Dave
sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt
Re: [Slackbuilds-users] Anki ModuleNotFoundError
On 21/05/22 14:52, Daniel Mackle put forth the proposition: > Dave, > That is it. Propose removing Markdown from the dependencies for anki. I > removed Markdown and reinstalled python-markdown and it works fine. The /usr/bin/markdown_py in Markdown is overwriting the python3 version in stock python-markdown. I'll push that change in my branch, and see what the situation is with the other builds that require it. > Thank you. > V/R > Dan > On Sat, May 21, 2022 at 2:39 PM Dave Woodfall wrote: > > On 21/05/22 14:05, > > Daniel Mackle put forth the proposition: > > > I have run into an error with anki since I upgraded to Slackware 15.0. I > > > have re-installed all of the dependencies and still get the same error. > > > This includes and up to the latest version on Slackbuilds. I have > > searched > > > the web, SBo mailing list archives, Anki mailing list, etc. and still > > have > > > not been able to resolve. If anyone has any ideas, please let me know. > > > Anki builds just fine, but when I try to run I get the following error: > > > Traceback (most recent call last): > > > File "/usr/bin/anki", line 5, in > > >from aqt import run > > > File "/usr/lib64/python3.9/site-packages/aqt/__init__.py", line 39, in > > > > > >import anki.lang > > > File "/usr/lib64/python3.9/site-packages/anki/lang.py", line 12, in > > > > > >import anki._backend > > > File "/usr/lib64/python3.9/site-packages/anki/_backend/__init__.py", > > line > > > 11, in > > >from markdown import markdown > > > File "/usr/lib64/python3.9/site-packages/markdown/__init__.py", line 35, > > > in > > >from .__version__ import version, version_info # noqa > > > ModuleNotFoundError: No module named 'markdown.__version__' > > > I believe it may have something to do with Python2.7/Python3.9, but I am > > > not sure. Thank you in advance for any advice. I do have Markdown > > > installed. > > > V/R > > > Dan > > > > It looks like Markdown (python2) might be conflicting slightly with > > the stock python-markdown (python3) package. > > > > Can you try uninstalling Markdown and reinstalling python-markdown to > > see if it helps? > > > > -- > > Dave > > > > sbo-maintainer-tools: > > https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ > > SBo templates: > > https://slackbuilds.org/templates/ > > How to format github downloads: > > https://slackbuilds.org/GITHUB_URLs.txt > > > > -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] Anki ModuleNotFoundError
On 21/05/22 14:05, Daniel Mackle put forth the proposition: > I have run into an error with anki since I upgraded to Slackware 15.0. I > have re-installed all of the dependencies and still get the same error. > This includes and up to the latest version on Slackbuilds. I have searched > the web, SBo mailing list archives, Anki mailing list, etc. and still have > not been able to resolve. If anyone has any ideas, please let me know. > Anki builds just fine, but when I try to run I get the following error: > Traceback (most recent call last): > File "/usr/bin/anki", line 5, in >from aqt import run > File "/usr/lib64/python3.9/site-packages/aqt/__init__.py", line 39, in > >import anki.lang > File "/usr/lib64/python3.9/site-packages/anki/lang.py", line 12, in > >import anki._backend > File "/usr/lib64/python3.9/site-packages/anki/_backend/__init__.py", line > 11, in >from markdown import markdown > File "/usr/lib64/python3.9/site-packages/markdown/__init__.py", line 35, > in >from .__version__ import version, version_info # noqa > ModuleNotFoundError: No module named 'markdown.__version__' > I believe it may have something to do with Python2.7/Python3.9, but I am > not sure. Thank you in advance for any advice. I do have Markdown > installed. > V/R > Dan It looks like Markdown (python2) might be conflicting slightly with the stock python-markdown (python3) package. Can you try uninstalling Markdown and reinstalling python-markdown to see if it helps? -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] couple of DEP fixes
> Hi all, > Now that the prerequisites are in place the following dependencies need to > be updated. > desktop/anki > -change Flask-Cors to python3-Flask-Cors > python/python3-Flask-RESTful > -change aniso8601 to python3-aniso8601 > Cheers Done. Can all these be removed now? python/Flask-Babel python/Flask-Bcrypt python/Flask-Compress python/Flask-Dance python/Flask-Login python/Flask-Mail python/Flask-Principal python/Flask-SQLAlchemy python/Flask-WTF python/flask-paginate -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] env var
On 20/05/22 16:51, Ralph Spitzner put forth the proposition: > if I check an env var in a slackbuild, do I document the variable in the > README, or slack-desc ? Usually it would be in the README. If it is critical for build dependencies then also add %README% to REQUIRES in the .info too. -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] eyeD3 slackbuild
> > Could you also put [PATCH] at the start of the message subject too, > Noted, and will do. In fact `git send-email' does that already. > On Fri, May 13, 2022 at 8:52 PM Dave Woodfall wrote: > > On 14/05/22 03:30, > > Dave Woodfall put forth the proposition: > > > On 11/05/22 17:24, > > > fourtysixandtwo put forth the proposition: > > > > Hi all, > > > > I found eyeD3 was broken while testing updates to pylast. I've emailed > > > > Larry a couple of times in the last 10 days but he hasn't responded. > > > > I've attached both format-patches I have for eyeD3. > > > > Cheers > > > Hi > > > Can you make a single patch of the whole folder next time please? > > > Thanks > > > > In fact Willy made a good blog post on how to make patches to send to > > the list: > > > > https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html > > > > Could you also put [PATCH] at the start of the message subject too, > > so it's more obvious there is one. > > > > -- > > Dave > > > > sbo-maintainer-tools: > > https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ > > SBo templates: > > https://slackbuilds.org/templates/ > > How to format github downloads: > > https://slackbuilds.org/GITHUB_URLs.txt > > > > -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] eyeD3 slackbuild
On 14/05/22 03:30, Dave Woodfall put forth the proposition: > On 11/05/22 17:24, > fourtysixandtwo put forth the proposition: > > Hi all, > > I found eyeD3 was broken while testing updates to pylast. I've emailed > > Larry a couple of times in the last 10 days but he hasn't responded. > > I've attached both format-patches I have for eyeD3. > > Cheers > Hi > Can you make a single patch of the whole folder next time please? > Thanks In fact Willy made a good blog post on how to make patches to send to the list: https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html Could you also put [PATCH] at the start of the message subject too, so it's more obvious there is one. -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] eyeD3 slackbuild
On 11/05/22 17:24, fourtysixandtwo put forth the proposition: > Hi all, > I found eyeD3 was broken while testing updates to pylast. I've emailed > Larry a couple of times in the last 10 days but he hasn't responded. > I've attached both format-patches I have for eyeD3. > Cheers Hi Can you make a single patch of the whole folder next time please? Thanks -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] Volatility/pythonX-yara
On 08/05/22 17:40, Barry J. Grundy put forth the proposition: > Good Afternoon, > I'm trying to submit the following updates (via SBo form): > python2-yara (update/rename/split) > volatility(fix dependency name changes[python2-distorm and > python2-yara]) > python3-yara (update/rename/split) > volatility3 (added-rewrite of volatility framework) > I cannot get the pythonX-yara submissions to upload because it says they are > already in pending (they are not). And there is already a package in > pending for volatility that fixes only one of the dependency names (I did > not submit that change). > I may have screwed something up, but I had submitted all of the above last > week and they were rejected because neither python-yara package would build > against the older yara already in 15.0, even though the correct version of > yara was submitted along side them (and was approved). Did I miss > something? > Thanks, > Barry Hi Barry Can you try now please? -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] github URL - Content Disposition Part 3
On 06/05/22 08:28, Konrad J Hambrick put forth the proposition: > All -- > I've got still more github-related questions. > The gmic project ( https://gmic.eu/ ) was reorganized between versions 2 > and 3. > The gmic version 2.9.4 source code included the source for the zart > subproject, but now zart is in a separate github Project ( URL = > https://github.com/c-koi/zart ) > There are no tags and no versions on the zart project. > I can download zart via wget like so: > # wget https://github.com/c-koi/zart/archive/master/zart.tar.gz > This returns a viable tar archive. However, the root directory is > zart-master/ instead of simply zart/ as the SlackBuild expects > If I `mv zart-master /tmp/SBo/gmic-3.1,0/` then the I can use the existing > gmic.SlackBuilt to create gmic-3.1.0-x86_64-1_SBo.tgz > Q1: Does it matter that there is no version on zart ? A definitive version is best, or it can't be verified as usable. > Q2: Is it bad form to rename / move the contents of a tar-archive after > extracting it ? A better idea is to find the latest commit hash and do something like: https://github.com/c-koi/zart/archive//zart-.tar.gz That's offhand from memory > Thanks > -- kjh -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ How to format github downloads: https://slackbuilds.org/GITHUB_URLs.txt ___ 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] Proper Method to Categorize Desktop Apps
On 01/05/22 04:58, Konrad J Hambrick put forth the proposition: > Question: is there a better way ( or a recommended way ) to enter long, > formatted > lists of text like NEW_CAT in the code snippet below ? ... >NEW_CAT="Science;Math;ImageProcessing;DataVisualization" >NEW_CAT="$NEW_CAT;Geoscience;NumericalAnalysis;Qt;" If text width matters then that's how to enter long strings and keeping within a limit. Under bash/zsh you can also use += NEW_CAT="Science;Math;ImageProcessing;DataVisualization" NEW_CAT+=";Geoscience;NumericalAnalysis;Qt;" > Note that many other SBo Packages also fail `desktop-file-validate` so > maybe this was > all a fools-errand :) Well it is only a warning, not an error, so it wouldn't fail the slackbuild. -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ ___ 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] Content Disposition part 2
On 30/04/22 18:00, Andrew Payne put forth the proposition: > > On 30/04/22 17:24, > > Andrew Payne put forth the proposition: > >> For example, my NC url had this typo: > >> https://github.com/nextcloud/desktop/archive/refs/tags/v3.4.3/desktop-3.4.4.tar.gz > > > > In the end the tag wins. The file will download as any name you > > choose, so in that link it will be version 3.4.3. This is the > > correct URL for version 3.4.4: > > > > https://github.com/nextcloud/desktop/archive/v3.4.4/desktop-3.4.4.tar.gz > > > > > >> As for my sakura slackbuild, the tarball naming is > >> "sakura-SAKURA_3_8_5", > >> which is silly so I did this: > >> SRCNAM = SAKURA_3_8_5 > >> [...] > >> tar xvf $CWD/$PRGNAM-$SRCNAM.tar.gz || tar xvf $CWD/$SRCNAM.tar.gz > >> mv $TMP/$PRGNAM-$SRCNAM $TMP/$PRGNAM-$VERSION > >> [...] > > > > This seems the same as libxlswriter except you have SAKURA_ instead > > of RELEASE_. > > > > SAKURA_3_8_5 is the tag/version so: > > > > https://github.com/dabisu/sakura/archive/SAKURA_3_8_5/sakura-SAKURA_3_8_5.tar.gz > > > > Which will extract a directory: sakura-SAKURA_3_8_5 > > > > With a more normal version 3.8.5 and like you have: > > > >> SRCNAM = SAKURA_3_8_5 > > > > That should be OK: > > > > tar xvf $CWD/$PRGNAM-$SRCNAM.tar.gz > > > > Should be all that's needed. I might be tempted to use $SRCVER > > perhaps, since it is the version according to github. > > > Ok, thanks Dave, I'll kill the "if" statement and use that URL. Just to prove that the tag always wins, try: wget https://github.com/dabisu/sakura/archive/SAKURA_3_8_5/mickey-mouse.tar.gz It will download as mickey-mouse.tar.gz, but test it and: tar tf mickey-mouse.tar.gz | head -n1 sakura-SAKURA_3_8_5/ -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ ___ 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] Content Disposition part 2
On 30/04/22 17:24, Andrew Payne put forth the proposition: > D & B, it's the script I just took over for Sakura. > https://github.com/dabisu/sakura/tags > I'm sure there's a bespoke url that can be crafted, but I was curious > about a more generic solution to a problem that pops up a lot. > I can't visualize how the || "if" statement would cause trouble, but I > accept it if this is not the right fix. > In my experience, tweaking the url must be done by hand and is thus prone > to typos. > For example, my NC url had this typo: > https://github.com/nextcloud/desktop/archive/refs/tags/v3.4.3/desktop-3.4.4.tar.gz > (see the mismatched versions) and the 3.4.3 version was downloaded with no > error. (?) Copy-paste from github tarball urls is mostly fool proof. In the end the tag wins. The file will download as any name you choose, so in that link it will be version 3.4.3. This is the correct URL for version 3.4.4: https://github.com/nextcloud/desktop/archive/v3.4.4/desktop-3.4.4.tar.gz > As for my sakura slackbuild, the tarball naming is "sakura-SAKURA_3_8_5", > which is silly so I did this: > SRCNAM = SAKURA_3_8_5 > [...] > tar xvf $CWD/$PRGNAM-$SRCNAM.tar.gz || tar xvf $CWD/$SRCNAM.tar.gz > mv $TMP/$PRGNAM-$SRCNAM $TMP/$PRGNAM-$VERSION > [...] This seems the same as libxlswriter except you have SAKURA_ instead of RELEASE_. SAKURA_3_8_5 is the tag/version so: https://github.com/dabisu/sakura/archive/SAKURA_3_8_5/sakura-SAKURA_3_8_5.tar.gz Which will extract a directory: sakura-SAKURA_3_8_5 With a more normal version 3.8.5 and like you have: > SRCNAM = SAKURA_3_8_5 That should be OK: tar xvf $CWD/$PRGNAM-$SRCNAM.tar.gz Should be all that's needed. I might be tempted to use $SRCVER perhaps, since it is the version according to github. > > > > On Sat, 30 Apr 2022, Andrew Payne wrote: > > > >> Hi all, revisiting the Github tarball 'content disposition' problem. > >> > >> While manually tweaking the tarball url to > >> > >> https://github.com/DEVELOPER/PRGNAM/archive/refs/tags/vVERSION/PRGNAM-VERSION.tar.gz > >> > >> works, I have a case where the devs use underscores instead of dots and > >> I > >> cannot seem to get a workable url with the above. > > > > Can you show us the actual URL you're having problems with? > > > >> tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || tar xvf $CWD/$VERSION.tar.gz > >> > >> This means I can copy paste the Github tarball url into the *.info file, > >> and it matters not how the user downloads it. > >> > >> Thoughts? > > > > That will work, but it's suboptimal. If there's no other way to get a > > consistent filename, it'll have to be done that way. > > > > But it can cause problem for automated tools that people use to > > download the file and check its md5sum. It can also cause problems > > for the SBo source archive: https://slackware.uk/sbosrcarch/ > > > > You might want to host the file on a different web server, if you have > > one handy. > > -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ ___ 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] Proper Method to Categorize Desktop Apps
On 30/04/22 15:23, Konrad J Hambrick put forth the proposition: > All -- > Been playing with the OTB.SlackBuild and OTB Version 8.0.0 > I am getting clean builds and the program works as expected. > `sbolint` returns no errors or warnings, but when I run > sbopkglint /tmp/OTB-8.0.0-x86_64-1_SBo.tgz I get a hint: > Running test: 35-desktop...usr/share/applications/monteverdi.desktop: hint: > value "Education;Science;ImageProcessing;Geography;Qt;" for key > "Categories" in group "Desktop Entry" contains more than one main category; > application might appear more than once in the application menu > OK > Otherwise, all tests are OK > Note that sbopkglint returns the same hint on the OTB Version 7.3.0 > Package file. > There is a doinst.sh script that I took from the Version 7.3 SlackBuild ( > below by sig ) > What is the proper way to set up a Desktop App in an SBo ? > Thanks. You need to decide which menu category the application should be in, then edit the .desktop to match. > value "Education;Science;ImageProcessing;Geography;Qt;" >From the description, I'd say ImageProcessing. OTB.desktop file is installed by the application so the usual way is to sed the file somewhere after the make install. -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ ___ 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] Content Disposition part 2
On 30/04/22 12:17, Andrew Payne put forth the proposition: > Hi all, revisiting the Github tarball 'content disposition' problem. > While manually tweaking the tarball url to > https://github.com/DEVELOPER/PRGNAM/archive/refs/tags/vVERSION/PRGNAM-VERSION.tar.gz > works, I have a case where the devs use underscores instead of dots and I > cannot seem to get a workable url with the above. > The result is that using wget or in my case python's urllib.request I get > a truncated tarball name, whereas downloading with firefox will retrieve > the full name. > Before I dive into how to manually fix the url or fool with content > disposition, what about using some variant of this in the slackbuild: > tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || tar xvf $CWD/$VERSION.tar.gz I mentioned using this as a last resort but if you can let us know the link to the repo we could take a look. > This means I can copy paste the Github tarball url into the *.info file, > and it matters not how the user downloads it. > Thoughts? I have one that uses underscores in the tag - libxlswriter: https://github.com/jmcnamara/libxlsxwriter/archive/RELEASE_1.0.2/libxlsxwriter-RELEASE_1.0.2.tar.gz With that I use: tar xvf $CWD/$PRGNAM-RELEASE_$VERSION.tar.gz I should add that there are also files that are added manually by the developer as `assets' in Github-speak, that are extra to the automatic tag releases and can be named any way the developer likes. -- Dave sbo-maintainer-tools: https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/ SBo templates: https://slackbuilds.org/templates/ ___ 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] network/snownews
On 26/04/22 19:51, Brandon Pribula put forth the proposition: > Hi, > Could you please remove snownews from SBo. I just noticed when I went to > update that it's included in Slackware already. I'm sorry for the > inconvenience. > Thanks, > Brandon Done -- Dave ___ 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] 'Correct' download link from Github?
On 17/04/22 14:42,
Ruben Schuller put forth the proposition:
> Hi,
> 2022-04-17 Ozan Türkyılmaz :
> > Paz, 2022-04-17 tarihinde 09:33 +0100 saatinde, Dave Woodfall yazdı:
> > > No policy yet AFAIK but you can find the release tag (add /tags/ to
> > > the end of the URL) and then do something like:
> > >
> > >
> > I remember a talk about content disposition (and how wget ignores it
> > by default) and github links should give same file with or without
> > content disposition. I dont remember when thou. My memory is not as
> > it used to be.
I think what you're referring to is that github will tend to send any
name tarball that you ask for from some links, but using the release
source links sends the format 1.2.3.tar.gz by default. This isn't
very useful if you use sbopkg and /var/cache/sbopkg fills up with
1.2.3.tar.gz, 3.4.5.tar.gz etc., because at some point you might need
to find some source and seeing them named like that is unhelpful.
> I think the decision was that scripts should assume content disposition
> is used. I usually use
> tar xvf v${VERSION}.tar.gz || tar ${PRGNAM}-${VERSION}.tar.gz
> (or the other way around..) in my scripts to catch the case when it
> isn't. I think it's fine, either of those tarballs should be MD5-checked
We can't assume that it is always used. Content-Disposition doesn't
always work, and is still marked as experimental in wget(1), and in
curl can give errors when mixed with other flags like -C.
"--content-disposition
If this is set to on, experimental (not fully-functional) support for
"Content-Disposition" headers is enabled. This can currently result in
extra round-trips to the server for a "HEAD" request, and is known to
suffer from a few bugs, which is why it is not currently enabled by
default."
The method I showed should always download $PRGNAM-$VERSION.tar.gz
and I change github URLs in submissions when I come across one.
One simple way to do this (test without -i first):
source the .info
sed -E
"s,(https://github.com/[^/]+/$PRGNAM)/archive/refs/tags/v?($VERSION)(.tar.gz),\1/archive/v\2/$PRGNAM-\2\3,"
-i $PRGNAM.info
--
Dave
___
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] 'Correct' download link from Github?
On 17/04/22 18:08, andrew put forth the proposition: > I am putting a new Slackbuild together for opustags, which is hosted > on github: > https://github.com/fmang/opustags > I am a little unsure of the correct download link from github which > shows some variation whether wget or browser is used. > Is there an SBo policy about such links? No policy yet AFAIK but you can find the release tag (add /tags/ to the end of the URL) and then do something like: URL/archive/TAG/PRGNAM-TAG.tar.gz which would be: https://github.com/fmang/opustags/archive/1.2.3/opustags-1.2.3.tar.gz or https://github.com/fmang/opustags/archive/v1.2.3/opustags-1.2.3.tar.gz (note the v before the first TAG sometimes works if the first URL gives a 404.) The downloaded tarball can be tested with `tar tf | head' to see if the directory name really matches the expected version number. HTH -- Dave ___ 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] THE.SlackBuild
On 16/04/22 13:54, Richard Narron put forth the proposition: > I recently submitted a new THE.SlackBuild script that copied > documentation from the install directory like this: > install -m0644 COPYING FAQ HISTORY INSTALL README* TODO \ > $PKG/usr/doc/$PRGNAM-$VERSION > But when it was installed, the first line leaves out the INSTALL document: > install -m0644 COPYING FAQ HISTORY README* TODO \ > ... > Please advise. > Richard Narron We don't really need INSTALL documents, because it's already installed by the time anyone reads it, right? -- Dave ___ 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] Admins - Question about Brave browser
On 15/04/22 16:27, Andrew Payne put forth the proposition: > > Forwarded Message > > Subject:[Slackbuilds-users] Question about Brave browser > > Date: Thu, 24 Mar 2022 10:54:05 -0600 > > From: Luveh Keraph <1.41...@gmail.com> > > Reply-To: SlackBuilds.org Users List > > To: SlackBuilds.org Users List > > > > Â Â $ xdg-mime query default x-scheme-handler/http > > Â Â brave-browser.desktop > > > > Â Â $ xdg-mime query default x-scheme-handler/https > > Â Â brave-browser.desktop I just installed brave-browser to see and the first time that I started it a window popped up asking to make brave the default browser, ticked yes by default, so I guess he missed that. -- Dave ___ 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] Admins - Question about Brave browser
On 15/04/22 17:58, B. Watson put forth the proposition: > Please, no. This is extra work and complexity for something that > doesn't *do* anything at all (see my previous message). > Adding this won't hurt the SlackBuild (it will still work), but it > will act as a red herring, a thing that will confuse users and cause > them to think it's somehow important, and waste their time trying to > decide what option to choose. > In reality both options are the same: nothing happens to > /usr/share/mime/mime.cache at all, either way. Yes, on thinking about it again, the command will run the next time something is installed that updates the cache anyway. -- Dave ___ 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] Admins - Question about Brave browser
On 15/04/22 16:27,
Andrew Payne put forth the proposition:
> I'll pose this to the admins.
> I would be happy to add this to the readme:
> This slackbuild will adjust MIME settings for Brave. If you
> wish to retain your current MIME settings, you can remove:
> if [ -x /usr/bin/update-mime-database ]; then
> /usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
> fi
> from the doinst.sh file before building.
> ++
> OR pull the MIME lines out of doinst.sh altogether.
> Thoughts?
> >
> >
> > Forwarded Message
> > Subject:[Slackbuilds-users] Question about Brave browser
> > Date: Thu, 24 Mar 2022 10:54:05 -0600
> > From: Luveh Keraph <1.41...@gmail.com>
> > Reply-To: SlackBuilds.org Users List
> > To: SlackBuilds.org Users List
> >
> >
> >
> > I have installed the Brave browser in my 15.0 system using the
> > Slackbuilds software for the purpose. I noticed that, after the
> > installation is completed, some MIME handling settings are silently
> > changed:
> >
> > Â Â $ xdg-mime query default x-scheme-handler/http
> > Â Â brave-browser.desktop
> >
> > Â Â $ xdg-mime query default x-scheme-handler/https
> > Â Â brave-browser.desktop
> >
> > Before installing Brave, the output of these commands was, in my case,
> > chromium.desktop. The default browser setting remains unchanged though:
> >
> >   $ xdg-settings  get default-web-browser
> > Â Â Â chromium.desktop
> >
> > The above changes imply that when clicking on a link embedded in an
> > email in Thunderbird, the Brave browser will be launched, instead of
> > whatever was the default before - Chromium, in my case. This is OK if
> > you want to use the Brave browser for that purpose. It is, however, a
> > bit annoying that the changes are carried out under the wraps and
> > without asking the person in charge of the installation of this browser
> > whether such an action is what one wants to do - installing a browser
> > does not necessarily mean that it is meant to become the default browser
> > for MIME data handling.
> >
> > It is easy enough to restore the MIME settings to what they were - in my
> > case I would do
> >
> > Â Â $ xdg-mime default chromium.desktop x-scheme-handler/http
> > Â Â $ xdg-mime default chromium.desktop x-scheme-handler/https
> >
> > However, it would be nice if the installation software were not to
> > change the MIME settings silently, or, at the very least, for the
> > documentation in the Slackbuilds installer to warn about this action and
> > explain how to revert it.
> >
> > Looking into the files in the Slackbuilds installation software it would
> > seem that doinst.sh has something to do with all this, but being totally
> > ignorant about such issues, I wouldn't know - the xdg-mime recipes that
> > I mentioned I got from a network search, they work for me, and that's
> > all I know about them.
You could make it optional and add something like the following to
the slackbuild:
if [ "${BRAVE_MIME:-yes}" = "yes" ]; then
echo '
if [ -x /usr/bin/update-mime-database ]; then
/usr/bin/update-mime-database usr/share/mime >/dev/null 2>&1
fi' >> doinst.sh
fi
to default to yes, or Change the first line to:
if [ "${BRAVE_MIME:-no}" = "yes" ]; then
to default to no.
--
Dave
___
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] evolution-data-server
On 15/04/22 17:30, Ozan Türkyılmaz put forth the proposition: > Hello All, > I checked but evolution-data-server does not show up in pending or > approved yet the submission form complains about it being in the > pending. > Regards, > Ozan Please try now. -- Dave ___ 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] libgweather
On 15/04/22 09:10, Ozan Türkyılmaz put forth the proposition: > Hello All, > Can of the admins fix the below problem? > doinst.sh file should be like below: (Last line was if and it should be > fi) > if [ -e usr/share/glib-2.0/schemas ]; then > if [ -x /usr/bin/glib-compile-schemas ]; then > /usr/bin/glib-compile-schemas usr/share/glib-2.0/schemas >/dev/null > 2>&1 > fi > fi > Regards, > Ozan Done. -- Dave ___ 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] Pleae remove THE.tar.gz from pending list
On 14/04/22 09:03, Richard Narron put forth the proposition: > My checksum does not seem to be working... > Can someone please remove the THE.tar.gz from the pending list or > send me the correct checksum? > I have a newer better build of THE to submit. > Richard Narron Try it now. -- Dave ___ 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] make -j${NUMJOBS} discussion
On 03/04/22 22:19, Ozan Türkyılmaz put forth the proposition: > Pzt, 2022-04-04 tarihinde 01:22 +0700 saatinde, Willy Sudiarto Raharjo > yazdı: > > > > > > You can just export MAKEFLAGS in your machine to achive same results > > Don't expect others to use same machine as yours and we often test > > those > > scripts in a VM with only small specs. > > > Don't do that. MAKEFLAGS is for passing command line arguments to > submake processes [1]. I dont know if MAKEFLAGS="-j2" sh configure > would do any problem or even make would get it. > Regards, > Ozan > [1] There's some long talk abut it > here:https://www.gnu.org/software/make/manual/html_node/Options_002fRecursion.html > Also here: https://stackoverflow.com/a/19622824/7247759 But also The MAKEFLAGS variable can also be useful if you want to have certain options, such as ‘-k’ (see Summary of Options), set each time you run make. You simply put a value for MAKEFLAGS in your environment. However: If you do put MAKEFLAGS in your environment, you should be sure not to include any options that will drastically affect the actions of make and undermine the purpose of makefiles and of make itself. For instance, the ‘-t’, ‘-n’, and ‘-q’ options, Same ref[1] -- Dave ___ 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] Request to team members: File exists; a submission by the name 'molequeue' is already pending approval
On 31/03/22 22:23, Giancarlo Dessì put forth the proposition: > Hi, > I uploaded some slackbuilds for a new package, Avogadro 2, but the > slack-desc of two slackbuilds wasn't correctly formatted, then I removed > them: avogadroapp, avogadrolibs, and molequeue. Second step I uploaded > avogadroapp and avogadrolibs with the slack-desc fixed. > However I cannot upload "molequeue.tar.gz" (dependency needed by > "avogadrolibs") because it appears already uploaded: > *"*File exists; a submission by the name 'molequeue' is already pending > approval" > But the old tarball has been removed! It appears only in the database of > pending istances. Sorry, I surely made a mistake with the removal, but > Avogadro 2 cannot be built without molequeue and I can't send this > dependency. Please, would you solve the issue? > Thanks > gian Hi Gian molequeue can't be removed because it's required by the other 2, so they need to be re-removed first and then molequeue removed. -- Dave ___ 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] fcron for 15.0
On 23/03/22 07:18, Richard Narron put forth the proposition: > On Tue, 22 Mar 2022, Michel BEGUE wrote: > > fcron does not build. > > just a line to add to ./configure > > " --with-sendmail=/usr/sbin/postfix " > I do not get any errors in building 3.3.0 > With postfix installed, the fcron 3.3.0 build finds sendmail at > /usr/sbin/sendmail. > What error did you get building fcron 3.3.0? Hi I also assumed that because sendmail is in extra/ now, that postfix would be the correct binary to use, but it seems that postfix comes with it's own version of sendmail. I'll revert that change. If /usr/sbin/sendmail doesn't exist, then reinstalling postfix ought to fix it. -- Dave ___ 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 change email in system/pax
On 22/03/22 19:46, Ben Collver put forth the proposition: > Greetings, > I plan to delete my Google account. Please change the email in > system/pax/pax.info > OLD: EMAIL="bencoll...@gmail.com" > NEW: EMAIL="bencoll...@riseup.net" > Thanks! > -Ben Done. -- Dave ___ 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] fcron for 15.0
On 22/03/22 18:25, Michel BEGUE put forth the proposition: > fcron does not build. > just a line to add to ./configure > " --with-sendmail=/usr/sbin/postfix " > and maybe get to v3.3.1. > regards. > Michel Done. -- Dave ___ 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] qemu build issue
On 21/03/22 13:54, Matteo Bernardini put forth the proposition: > well, to be fair that shouldn't actually be a problem in a Slackware stable > setup because libraries' versions should be the same... > that should only happens when you are using current or upgrading between > Slackware versions (but in that case many other things could happen). > Matteo I've just put a small note at the bottom of the README, that if there are any problems with missing or wrong versioned libraries to try uninstalling older versions first. Dave > Il giorno lun 21 mar 2022 alle ore 13:48 Tim Dickson via SlackBuilds-users < > slackbuilds-users@slackbuilds.org> ha scritto: > > thanks Matteo, that did the trick. It looks like part of the build process > > uses already created binaries to process files, and when older binaries are > > already in the path they are used instead, giving the error. > > > > It may be worth adding a comment to remove existing version of qemu before > > installing a newer one into the README. > > > > regards, Tim > > > > On 20/03/2022 18:31, Matteo Bernardini wrote: > > > > have you tried removing the already installed qemu package first? > > > > Il giorno dom 20 mar 2022 alle ore 19:29 Tim Dickson via SlackBuilds-users > > ha scritto: > > > >> I am getting the following error when attempting to create qemu package. > >> > >> /usr/bin/qemu-keymap: error while loading shared libraries: > >> libjemalloc.so.1: cannot open shared object file: No such file or > >> directory > >> > >> /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there > >> is a libjemalloc installed (part of slackware 15.0). > >> It seems that the build script is looking for the wrong version of the > >> lib. Ideally it would try libjemalloc.so and thus pick up whichever > >> version was installed. > >> Is there a quick fix. (if it involves a sim-link would that have to be > >> done on target computers as well?) > >> regards, Tim > >> > > > > -- Dave ___ 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] qemu build issue
On 20/03/22 18:38, Dave Woodfall put forth the proposition: > On 20/03/22 18:29, > Tim Dickson via SlackBuilds-users put > forth the proposition: > > I am getting the following error when attempting to create qemu package. > > /usr/bin/qemu-keymap: error while loading shared libraries: > It looks like qemu was compiled against an older jemalloc and not > jemalloc-3.6.0 in 15.0 jemalloc-5.2.1 :-) > > libjemalloc.so.1: cannot open shared object file: No such file or directory > > /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there is a > > libjemalloc installed (part of slackware 15.0). > > It seems that the build script is looking for the wrong version of the lib. > > Ideally it would try libjemalloc.so and thus pick up whichever version was > > installed. > > Is there a quick fix. (if it involves a sim-link would that have to be done > > on target computers as well?) > > regards, Tim > > -- > > This email has been checked for viruses by AVG. > > https://www.avg.com > -- > Dave -- Dave ___ 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] qemu build issue
On 20/03/22 18:29, Tim Dickson via SlackBuilds-users put forth the proposition: > I am getting the following error when attempting to create qemu package. > /usr/bin/qemu-keymap: error while loading shared libraries: It looks like qemu was compiled against an older jemalloc and not jemalloc-3.6.0 in 15.0 > libjemalloc.so.1: cannot open shared object file: No such file or directory > /usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there is a > libjemalloc installed (part of slackware 15.0). > It seems that the build script is looking for the wrong version of the lib. > Ideally it would try libjemalloc.so and thus pick up whichever version was > installed. > Is there a quick fix. (if it involves a sim-link would that have to be done > on target computers as well?) > regards, Tim > -- > This email has been checked for viruses by AVG. > https://www.avg.com -- Dave ___ 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] Tor is up for grabs
On 17/03/22 01:43, MDrights put forth the proposition: > Hi Markus, > Thanks for raising this thread again, after several months! > I thought my request was forgotten by folks :) > Yes, I am glad to take on Tor Slackbuild. I have been a long time Tor user as > well :) > I will submit an updated script shortly. > My slackbuilds fork: https://gitlab.com/mdrights/slackbuilds/-/tree/local > Let me know if any of you folks have any suggestions/concerns. > (I am really feeling painful for the situation in Ukraine. God bless. and > hope Tor may help.) > Cheers, > MDrights > On Wed, Mar 16, 2022 at 11:26:02PM +0100, Markus Reichelt via > SlackBuilds-users wrote: > > * Dionysis Ntreou wrote: > > > > > Hello, > > > I would like Tor too if nobody has taken it . > > > > Thank you for your interest. I would like to stick to the paragraph > > highlighted >> below for the short term, because Ukraine crisis > > happened. I feel an obligation to make this right. I've seen > > 'MDrights' work on this list before. > > > > so let's see what we can come up with together, eventually. > > > > > > > Although I do not have the same experience as you Markus but I am > > > keen to learn. > > > > We all started at some point. Kudos for starting in the first place. > > > > Mabye SBo manages to evolve to the point that there can be a team > > of maintainers for a given application. IMHO such an approach would > > need 'release signing keys' like so many other projects use. > > > > Not talking about how, or how fast one could get onto the team, it's > > about trust within the team. a working team is the goal. the team > > shall be resiliant. > > > > I was just thinking out loud... > > > > We'll see. There's time. > > > > > > > > > On Wed, Mar 16, 2022 at 5:00 PM Markus Reichelt via > > > SlackBuilds-users wrote: > > > > > > > * MDrights wrote: > > > > > > > > > Tor is not taken up by anyone yet, right? > > > > > I will take it. > > > > > > > > I know this thread is old, but: [...] > > > > > > >>> > If not, I'll keep holding up the torch. Let's return to giving > > >>> > (potentially new) maintainers that fancy 2 weeks grace period. > > >>> > We haven't heard from you back by April, then we know. Since MDrights was the first to say he'd take it I've added him as new maintainer in my branch. Thanks -- Dave ___ 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] Update wavbreaker (audio) for 15.0
On 09/03/22 18:26, andrew put forth the proposition: > Hi, > I picked up wavbreaker some time back: > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2021-April/025629.html > I have updated the SlackBuild for 15.0, diff taken against latest SBo > git. > All the best, > Andrew Strong > -- > You think that's air you're breathing now? Pushed to my branch. Thanks for the update. -- Dave ___ 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] network/et
On 09/03/22 06:16, khronosschoty put forth the proposition: > hi, > I was looking over the master branch and saw this: > http://git.slackbuilds.org/slackbuilds/commit/?id=59677cfd76fecb1c323dcd37d320bdc87118f588 > "network/et: Removed" > I was wondering what the reason for this might be? Hi It didn't build in 15.0, and a version couldn't be found that would. But if you do manage to get it to build, let us know and/or send a patch etc. Removals without a reason given will likely be the for the same problem. -- Dave ___ 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] rtl8821ce: Reason for removal
On 06/03/22 17:36, Andrzej Telszewski put forth the proposition: > >> I have a report from a user that some recent commit from the upstream repo > >> builds fine on 15.0. > >> I'm not actively using this driver any more, so I cannot test it on real > >> HW, but I surely can try building it. > >> Would you like me to try it out and report back? > > > > Please do. > I reverted _83c64a3e52_, then applied the attached patch. > The driver builds and it can be loaded into the kernel (tested in VM). > Because recently I received a ping from one of the *rtl8821ce* driver users, > I assume it is still in use by someone. > Please incorporate the attached patch. > Please note that it is slightly different from what _B Watson_ did in his > branch (thanks for testing :-)). > Thank you! :-) Thanks Andrzej -- Dave ___ 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] New Templates and 15.0 Repository Progress
On 06/03/22 08:48, Dan Whisman put forth the proposition: > I was able to build CubicSDR 0.2.7 just fine with the repo as-is, but it > needed SoapySDR 0.8.1 which is not in master. I have attached a patch > (which I also emailed to the maintainer). It bumps the version, adds > Python3 support, and fixes the man page directory. > With the upgraded SoapySDR, I was able to successfully test CubicSDR by > listening to a local FM station. I did use newer versions of SoapySDRPlay > and SDRPlay packages and I also emailed patches to the maintainer. Thanks Dan -- Dave ___ 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] rtl8821ce: Reason for removal
On 04/03/22 20:36, Andrzej Telszewski put forth the proposition: > Mar 4, 2022 21:07:44 Dave Woodfall : > > I removed it because it failed to build when I tested it on 15.0. > I wonder, is it a general rule in preparation for 15.0 to remove what does > not build? Yes > I'm kind of concerned, because you didn't contact me about that. Unfortunately, it would take too long to contact someone every time. > I have a report from a user that some recent commit from the upstream repo > builds fine on 15.0. > I'm not actively using this driver any more, so I cannot test it on real HW, > but I surely can try building it. > Would you like me to try it out and report back? Please do. -- Dave ___ 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] rtl8821ce: Reason for removal
On 04/03/22 20:07, Dave Woodfall put forth the proposition: > On 04/03/22 19:37, > Andrzej Telszewski put forth the proposition: > > Hi, > > I noticed that _network/rtl8821ce_ has been removed from master branch. > > There is no info in the log why is it so. > > Could you please explain? > > Thank you! :-) > Hi, > I removed it because it failed to build when I tested it on 15.0. It > looks like a header file was moved, but I'll try to make a patch for > it. /tmp/SBo/rtl8821ce-20201006_fe97b50/core/rtw_br_ext.c:20:18: fatal error: net/ipx.h: No such file or directory 20 | #include however: find /usr/include -name ipx.h /usr/include/netipx/ipx.h and grep -wrs ipx.h /var/lib/pkgtools/packages/* /var/lib/pkgtools/packages/glibc-2.33-x86_64-5:usr/include/netipx/ipx.h but changing it also fails: sed -i "s,,," core/rtw_br_ext.c /tmp/SBo/rtl8821ce-20201006_fe97b50/core/rtw_br_ext.c:20:18: fatal error: netipx/ipx.h: No such file or directory 20 | #include -- Dave ___ 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] rtl8821ce: Reason for removal
On 04/03/22 19:37, Andrzej Telszewski put forth the proposition: > Hi, > I noticed that _network/rtl8821ce_ has been removed from master branch. > There is no info in the log why is it so. > Could you please explain? > Thank you! :-) Hi, I removed it because it failed to build when I tested it on 15.0. It looks like a header file was moved, but I'll try to make a patch for it. -- Dave ___ 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] patch for a suggested update: misc/ltunify
On 02/03/22 10:03, Fellype put forth the proposition: > Hi all! > Here follows a patch to update misc/ltunify. > Currently, Xgates (emailed in cc) is listed as the maintainer of this > package. > I don't want to take over maintenance of ltunify. I'm just suggesting an > update and sharing a patch with the necessary changes. > ltunify-0.2 (the version at SBo) is ~9yo and it is very outdated. > Regards, > Fellype Pushed to my branch. Thanks -- Dave ___ 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] Is Ekiga being phased out of SBo
> There is also a plugin for Pidgin called SIPE (an extended version of > SIP), but I have never tested it, and don't know how compatible it is > with normal SIP: > http://slackbuilds.org/repository/14.2/network/pidgin-sipe/ I've just had a look at this and pushed an update to get it to build on 15.0. SIP shows in pidgin's "add account" menu as SIMPLE, and I successfully managed to make an account and register it to my asterisk PBX. I added a buddy, which was my home phone, but it shows offline, so "enable offline buddies" then configure the buddy to always show is needed. That's as far as I tested it, but I noticed some menu entries to configure audio/video, so I imagine it ought to work. -- Dave ___ 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] Is Ekiga being phased out of SBo
On 22/02/22 16:10, Sebastian Arcus put forth the proposition: > On 22/02/2022 15:38, Dave Woodfall wrote: > > On 22/02/22 13:27, > > Sebastian Arcus put forth the proposition: > > > I haven't been able to get Ekiga to work any more since end of March 2021 > > > after updating this machine to latest -current (at the time). I eventually > > > managed to get it compiled and installed, but then when trying to connect > > > to > > > any sip account it crashes. > > > When trying to recompile it now I noticed that ponce's SBo git repo now > > > doesn't have Ekiga or Opal any more. Do I take it that Ekiga is now being > > > phased out from SBo? I guess it makes sense as the upstream code hasn't > > > been > > > updated for a few years. > > > I would be ok with switching to another SIP client - but haven't found any > > > so far which actually work properly. Linphone installs fine, but when I > > > try > > > to add a SIP account, it just doesn't do it. No error, nothing. > > > Any suggestions for a SIP client, or how to get Ekiga to work again > > > please? > > > I would prefer a client which supports multiple accounts - but frankly at > > > this stage I would try anything. Thank you. > Hi David, > > > > Hi Sebastian > > > > I have been down this road in the past too, and was surprised at the > > lack of a good software phone that had any kind of contacts list, or > > didn't they didn't support basic things like contact groups. > > > > I found Ekiga to be the most user-friendly phone out there (if you > > can get past some of the cryptic error messages), which is why I > > began maintaining it, but now I use a hardware VOIP phone + local > > asterisk PBX. > I found Ekiga reasonably good as well - until it stopped working. I actually > use myself VoIP desk phone (mainly Grandstream and old Cisco stuff) + > Asterisk PBX's at a number of sites. But I need a VoIP softphone on my > laptop to troubleshoot and reconfigure remotely Asterisk servers. > > > > Unfortunately, the developers stopped working on Ekiga many years > > ago. The problem now is that one of the dependencies fails to build > > in 15.0, which renders it useless. Linphone is probably the most, > > maybe only, maintained software phone at the moment, and has been > > getting better over the years. > I've just about managed to get Linphone working now. The trouble was that it > expects a specific syntax when configuring a sip account (username in the > format , and the proxy address needs to start with > "sip:" as well) - but there were zero error messages in the GUI if you > didn't follow that syntax - it just didn't add the account - so I was > flummoxed for a while. > Thank you everyone for the suggestions. I plan to have a look at Twinkle and > see if it will compile and install. I used to use the CLI part of linphone for testing things: linphonec. You may find the errors and warnings bit more verbose than the GUI, but it worked fine. I can't recall if it takes SIP address as a flag when starting it though, which would be useful. IIRC the syntax it uses is sip:user/extension@. It keeps history between sessions, so you only need to up-arrow a few times the next time you use it. -- Dave ___ 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] Is Ekiga being phased out of SBo
On 22/02/22 13:27, Sebastian Arcus put forth the proposition: > I haven't been able to get Ekiga to work any more since end of March 2021 > after updating this machine to latest -current (at the time). I eventually > managed to get it compiled and installed, but then when trying to connect to > any sip account it crashes. > When trying to recompile it now I noticed that ponce's SBo git repo now > doesn't have Ekiga or Opal any more. Do I take it that Ekiga is now being > phased out from SBo? I guess it makes sense as the upstream code hasn't been > updated for a few years. > I would be ok with switching to another SIP client - but haven't found any > so far which actually work properly. Linphone installs fine, but when I try > to add a SIP account, it just doesn't do it. No error, nothing. > Any suggestions for a SIP client, or how to get Ekiga to work again please? > I would prefer a client which supports multiple accounts - but frankly at > this stage I would try anything. Thank you. Hi Sebastian I have been down this road in the past too, and was surprised at the lack of a good software phone that had any kind of contacts list, or didn't they didn't support basic things like contact groups. I found Ekiga to be the most user-friendly phone out there (if you can get past some of the cryptic error messages), which is why I began maintaining it, but now I use a hardware VOIP phone + local asterisk PBX. Unfortunately, the developers stopped working on Ekiga many years ago. The problem now is that one of the dependencies fails to build in 15.0, which renders it useless. Linphone is probably the most, maybe only, maintained software phone at the moment, and has been getting better over the years. There is also a plugin for Pidgin called SIPE (an extended version of SIP), but I have never tested it, and don't know how compatible it is with normal SIP: http://slackbuilds.org/repository/14.2/network/pidgin-sipe/ Most of the focus the past few years seems to be on hardware phones. I recall that there were some quite good SIP apps for Android when I used to use one, and some old Sony Ericsson feature phones can make SIP calls and connect to the LAN by either USB or Bluetooth (like my old Cybershot C702) if you can find a used one somewhere. Gigaset make some fairly good SIP phones and base stations (n300) that have all the features you'd expect from a phone, and can be extended when combined with a local asterisk PBX running on your LAN. I know this has drifted away from the subject, but user-friendly SIP software have always been lacking for some reason, and proprietary programs like skype have always been more popular unfortunately. -- Dave ___ 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] xjadeo fix for build with new portimidi 2.0.2
MuseScore hatari hydrogen mame mixxx odamex pd prboom-plus pygame seq24 xjadeo All checked and working. -- Dave ___ 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] xjadeo fix for build with new portimidi 2.0.2
On 21/02/22 17:56, Franzen via SlackBuilds-users put forth the proposition: > Hi Matteo, > > maybe I'm missing something I just tried but it seems to link to > > porttime already if it finds portmidi installed... > This seems to be the case since this commit to portmidi: > https://git.slackbuilds.org/slackbuilds/patch/?id=ea1c6894e221ed242ecd9308f0c5cf9779961463 > I think it would be better to fix the apps to use libportmidi instead of > rely on a compatibility link(and remove that link again) to libportmidi. > I grep'ed through the tree, following apps use portmidi as dep or optional: > MuseScore > hatari > hydrogen > mame > mixxx > odamex > pd > prboom-plus > pygame > seq24 > xjadeo I pushed an update for hydrogen and there was also an update to pygame recently. Portmidi is one of mine so I'll go through the list and see which fail. -- Dave ___ 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] some SlackBuilds can't handle MAKEFLAGS other than -j1
On 14/02/22 00:02, David Chmelik put forth the proposition: > Some SlackBuilds can't handle MAKEFLAGS other than -j1. Is it possible in > future sbopkg will let you set MAKEFLAGS for multiple threads, and if a > script can't handle it, reset to one? You can set MAKEFLAGS in the options box for the application, where you would usually put options specific to the build. -- Dave ___ 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] Concerning 15.0 and 14.2
On 01/02/22 13:44, Luveh Keraph <1.41...@gmail.com> put forth the proposition: > There have been no updates to any Slackbuilds packages for 14.2 for many > months now - I guess that we all thought that 15.0 would be released > earlier than in fact it will, whenever that happens. My guess is that, > shortly after this release hits the street, normal updating activity will > start for Slackbuilds packages for 15.0. What happens to 14.2? No > Slackbuilds packages for 14.2 will be updated any more? Hi Luveh - yeah, 14.2 is frozen now. Updates and submissions will resume with the 15.0 release. -- Dave ___ 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] remove Photivo and Alchemy
On 11/12/21 20:07, Giorgio Peron put forth the proposition: > please remove from the current repository my packages: > Alchemy > Photivo > because the source is not more actively mantained > thanks > Giorgio Done. -- Dave ___ 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] Questions about SlackBuild licenses
On 30/07/21 02:43, Edward Ender put forth the proposition: >I know that each SlackBuild must include a license block, but what about > these off-brand licenses like WTFPL, etc? >Are these legit or should they be changed to the MIT-style block? >Is there a list of "accepted" licenses? Or should they just follow the OSI > standards? >Thanks, >Ed Ben / Urchlay uses WTFPL so I assume any off-brand is OK. We don't have a list of accepted licenses that I know about. -- Dave ___ SlackBuilds-users mailing list SlackBuilds-users@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] Clementine up for grabs
On 24/04/21 13:45, Jeremy Hansen put forth the proposition: > On Sat, Apr 24, 2021, 7:24 AM Dave Woodfall wrote: > > On 02/11/20 22:29, > > Jeremy Hansen put forth the proposition: > > > I haven't used it before, but I was a big fan of the old amarok. If > > someone > > > already uses it and wants to take over, I'm totally fine with that, but > > if > > > no one else claims it by the end of the week, I'll take it over. > > > Jeremy > > > > Would you like to take it on still? > > > I'd be happy to take it, but since Spycrowsoft stated they're actually > using it and are willing to maintain it, I'll give them the opportunity to > take it on if they want. > Jeremy I can't find a message from him about it, but OK. -- Dave ___ 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] Clementine up for grabs
On 02/11/20 22:29, Jeremy Hansen put forth the proposition: > I haven't used it before, but I was a big fan of the old amarok. If someone > already uses it and wants to take over, I'm totally fine with that, but if > no one else claims it by the end of the week, I'll take it over. > Jeremy Would you like to take it on still? -- Dave ___ 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] Clementine up for grabs
On 03/11/20 20:48, Andrzej Telszewski put forth the proposition: > On 03/11/2020 06:29, Jeremy Hansen wrote: > > I haven't used it before, but I was a big fan of the old amarok. If > > someone already uses it and wants to take over, I'm totally fine with > > that, but if no one else claims it by the end of the week, I'll take it > > over. > > > > Jeremy > > > > > I'm actually using *Clementine* as my main music player. > I'll happily take it over. > I'm bold enough to say that I'm better fir than Jeremy, because I actually > use it. :-> > On the other hand, I use it to play local collection exclusively, I don't > use services like Spotify. > And for that reason, I will not be able to reassure correct operation for > networked services. > If you find me a good fit for the job, I'm ready to take it. :-) > Cheers! > -- > Andrzej Andrzej, what did you decide? -- Dave ___ 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] Regarding Fixes and Patches for 15.0
Hello all, May I request that people hold on to their 15.0 patches and fixes for now, rather than posting them to the list? They really need to go through the usual submission system once we reopen it, so that they get added to the database properly, or via git if you use that method. Thanks! -- Dave ___ 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] My -current scripts
Hi I can take psi if nobody else wants it. I maintain psi-plus, so I could do both. Dave Eugen Wissner put forth the proposition: > Hi, > I would like to ask to remove the following SlackBuilds: > - gcc-d: Part of Slackware current > - gkrellm-volume: The home page and download link are dead, I'm not sure > if this software still exists > - oniguruma: In Slackware current > - opendbx: It builds on current, but opendbx doesn't seem to be active, > the last release was in 2012 and nothing depends on it. > - tanya: It is my own development; I wasn't working on it a lot in the > last time and I'm not sure I will. Anyway it is not the best way to > build D dependencies. > I don't use the following SlackBuilds anymore. I will maintain them if > someone needs them, but it would be great if they can be removed or find > a new maintainer who can update them on a regular basis: > - ioncube-loader: It probably builds on current, but it won't work > since it should be updated for PHP 7. > - psi > - universal-ctags: Language servers replaced this one in the most cases > The following scripts work on current: > - composer > - d-tools > - dmd > I'll try to update php-apcu and hhvm next week. > On my production server with Slackware current I have modified versions > of the following scripts: > - colm > - dovecot-pigeonhole > - hyperscan > - php-pgsql > - ragel > The reason I have them is that I couldn't build them at some point. > Maybe I'm just ignorant and some problems where already fixed. Just for > the case some of the maintainers struggle with an update, clone > git://caraus.tech/pub/slackbuilder.git and look into private/ directory. > Here is the web view: > https://www.caraus.tech/projects/pub-slackbuilds/repository/26/revisions/master/show/private > I have dovecot-pgsql and postfix-pgsql there if someone uses dovecot and > postfix with PostgreSQL since the SBo's scripts support PostgreSQL, but > the slackware's ones don't. > Eugen -- Dave ___ 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] Development Cycle Towards 15.0 Repository SlackBuilds-users Digest, Vol 180, Issue 12
Hi Rob, When submissions open again, and we will be in 15.0, which would be the correct time. Dave Slackbuilds Users put forth the proposition: > Hi Willy, > When would it be possible to submit scripts for packages that only run > on current and that should replace outdated, no-longer maintained > (e.g python2-only) packages that are in the repository for 14.2 atm? > For example I maintain PDF-shuffler which should be dropped. This I > would like to replace in the 15.0 repository with PDFarranger plus Pike > PDF, which work fine for me on current > (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > PikePDF relies on a version of qpdf not available in stock 14.2. > Good luck with the work ahead... > Rob > > > > Message: 2 > > Date: Fri, 16 Apr 2021 17:27:07 +0700 > > From: Willy Sudiarto Raharjo > > To: "SlackBuilds.org Users List" > > Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository > > Message-ID: > > Content-Type: text/plain; charset="utf-8" -- Dave ___ 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] Pari version obsolete
I've just tested 2.13.1 and it builds OK, but the man pages are in /usr/man instead of /usr/man/man1. Matteo Bernardini put forth the proposition: > https://pari.math.u-bordeaux.fr/pub/pari/OLD/2.11/pari-2.11.2.tar.gz > I'll update the download link. > Matteo > Il giorno gio 15 apr 2021 alle ore 14:52 Luveh Keraph > <1.41...@gmail.com> ha scritto: > > > > The version of Pari (2.11.2) that the Slackbuilds script attempts to > > download is not found in the Pari repository any more - versions 2.13 and > > 2.13.1 alone seem to be present there. > > -- Dave ___ 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] Warzone 2100 4.0.0 will have to wait.
Slackbuilds Users put forth the proposition: > Hi everybody, > unfortunately 14.2 oldness striked again. > This time it's SQLite that is too old for the brand new 4.0.0 version of > Warzone > 2100. Have you looked at the possibility of using a bundled version of sqlite? A few slackbuilds download and use internal versions of libs etc. when the stock ones are too old. -- Dave ___ 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] wxMaxima not building in 14.2-64
Luveh Keraph <1.41...@gmail.com> put forth the proposition: > CMake Error: The source directory "/tmp/SBo/wxmaxima-Version-21.01.0/build" > does not appear to contain CMakeLists.txt. > Specify --help for usage, or press the help button on the CMake GUI. Do you have cmake-202x (3.19.6) and ninja (1.10.2) installed? -- Dave ___ 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] TauonMusicBox needs more deps
On 05/04/21 15:29, Fellype put forth the proposition: > Hi all, > It looks like tauonmb also requires BeautifulSoup4 (runtime dep), which in > turn require python3-soupsieve since tauonmb is built under some python3 > Regards, > Fellype Thanks, I'll add those for next weeks updates. -- Dave ___ 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] Angband
On 07/03/21 22:55, David Chmelik put forth the proposition: > After many years, I'm thinking of giving up the Angband SlackBuild in the > case someone else wants it. Since they removed charisma from the game (so > you don't do as well in shops or perhaps with neutral monsters) they made > many more changes away from classic style, which I don't really like (like > to magic/spells, so it no longer feels like playing Moria.) I'd want to > make a new 'retro' Angband SlackBuild, the last Angband that had charisma... > would that be an acceptable one to submit? > Sincerely, > David I can't see it as problem personally. -- Dave ___ 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] haskell/shellcheck cannot build
On 22/02/21 21:56, Jude DaShiell put forth the proposition: > Many missing dependencies and this was after running sqg -p > haskell/shellcheck then building with that .sqf file. > Are the missing dependencies not yet available in slackbuilds archive yet or > does the build script need improving? Try without the category. # sqg -p haskell/haskell-ShellCheck haskell/haskell-ShellCheck: not found. # sqg -p haskell-ShellCheck Processing haskell-ShellCheck. Done. -- Dave ___ 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] Burning .iso to a DVD
On 11/02/21 14:41, Rich Shepard put forth the proposition: > On Thu, 11 Feb 2021, Dave Woodfall wrote: > > Tried cdrecord yet? > Dave, > Ah, no. I had tried mounting the drive but it could not read superblocks > because the disk was blank. You don't mount CDs or DVDs to write to them. Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] Burning .iso to a DVD
On 11/02/21 14:10, Rich Shepard put forth the proposition: > I just downloaded -current64 and tried to burn it to a DVD. xcdroast told me > that cdrecord and mkisofs are too old (see attached screenshot) with the > xcdroast-1.19 in the SBo repo. > Please suggest how I can put this file on a DVD-R. > Thanks in advance, > Rich Tried cdrecord yet? -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] Invoke ffmpeg without configuration display
On 10/02/21 14:48,
Rich Shepard put forth the proposition:
> Each time I invoke ffmpeg I get a large heading:
> $ ffmpeg
> ffmpeg version 3.2.4 Copyright (c) 2000-2017 the FFmpeg developers
> built with gcc 5.5.0 (GCC)
> configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64
> --docdir=/usr/doc/ffmpeg-3.2.4/html --mandir=/usr/man --disable-debug
> --enable-shared --disable-static --enable-gpl --enable-version3
> --enable-avresample --arch=x86_64 --enable-libfontconfig --enable-libfreetype
> --enable-libfribidi --enable-gnutls --enable-libcaca --enable-libcdio
> --enable-libssh --enable-libtheora --enable-libv4l2 --enable-libvorbis
> --enable-libvpx --enable-opengl --enable-libopenjpeg --enable-libpulse
> --enable-libsmbclient --enable-libwavpack --enable-x11grab
> libavutil 55. 34.101 / 55. 34.101
> libavcodec 57. 64.101 / 57. 64.101
> libavformat57. 56.101 / 57. 56.101
> libavdevice57. 1.100 / 57. 1.100
> libavfilter 6. 65.100 / 6. 65.100
> libavresample 3. 1. 0 / 3. 1. 0
> libswscale 4. 2.100 / 4. 2.100
> libswresample 2. 3.100 / 2. 3.100
> libpostproc54. 1.100 / 54. 1.100
> Hyper fast Audio and Video encoder
> usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options]
> outfile}...
> Reading the man page and looking at the -help output I don't see a command
> line option for turning off all that information. Is there a way to do so?
> TIA,
> Rich
The option is -hide_banner.
alias ffmpeg='ffmpeg -hide_banner'
and you'll never see it again.
--
Dave
Love is a snowmobile racing across the tundra and then suddenly it flips over,
pinning you underneath. At night, the ice weasels come.
--Friedrich Nietzsche
___
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] Updating a slackbuild
On 19/01/21 12:08, Slackbuilds Users put forth the proposition: > Hi, > I'm new here so please be gentle! > I've updated the hyperscan slackbuild to use the latest version 5.4.0 and i > noticed that by default the slackbuild won't build HSCollider which is an > important testing module in Hyperscan. This is because Slackware64-14.2 > doesn't ship the required PCRE 8.41. Hyperscan will build and use PCRE 8.41 > if the source code is available in the hyperscan build directory and i've > made a simple patch for this, but my question is whether it's frowned upon > to wget files from within a slackbuild script ? > Regards > Iain Hi Iain, Slackbuilds are usually intended to work without needing a network connection. What we tend to do in cases like this is add the extra source(s) to the .info file, and the slackbuild can move it to wherever it needs to be. Of course if it is something for your own use, you're free to do what you like with it. I have some on my website that clone from git, but they would never be accepted by SBo. Out of interest, did you test hyperscan with our pcre2, which is at 10.35 at the moment? https://slackbuilds.org/repository/14.2/libraries/pcre2/ -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] qwt-6.1.6 fails to build
On 17/01/21 22:09, Dave Woodfall put forth the proposition: > A full 14.2 system includes qt4. Oops, as Didier says it's actually named qt. We usually refer to it as qt4 because the version is 4.8.7 and we want to distinguish it from qt5 etc. -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] qwt-6.1.6 fails to build
On 17/01/21 13:57, Rich Shepard put forth the proposition: > On Sun, 17 Jan 2021, Didier Spaier wrote: > > All the SlackBuilds @ SBo should be run in a full Slackware > > installation. Period. > > > > So please complete your installatipon (meaning all packages shipped in > > the distribution should be installed and none removed) before reporting > > an issue. > This desktop had 14.2/x86_64 installed when built. Since then it's been > patched with core and SBo packages. > What's a 'full' Slackware installation if not all packages on the > distribution DVDs? Since qwt-6.1.3, -6.1.4, and -6.1.5 built without > problems you're suggesting that my system must have become non-full since > then? > Rich A full 14.2 system includes qt4. If you say that you don't have it installed then either you removed it, or you didn't know that it was installed? -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] stone_soup
On 10/01/21 05:06, Jude DaShiell put forth the proposition: > Where did you get SDL2_image-2.0.5 from? It's not in any repository I use > or I could be searching for it wrong. https://slackbuilds.org/repository/14.2/libraries/SDL2_image/ 14.2 > Libraries > SDL2_image (2.0.5) > 0.24 of stone_soup didn't use this library when run in console. How I found > out about this was first running in mate since I was curious what the > interface might be like with orca. I ran into this error. So I try again > down in console and get the same error. > On Sun, 10 Jan 2021, Dave Woodfall wrote: > > On 10/01/21 03:56, > > Jude DaShiell put forth the proposition: > > > Built successfully run fails with: > > > crawl: symbol lookup error: /usr/lib64/libSDL2_image-2.0.so.0: undefined > > > symbol: SDLRWseek > > > How would I find which uninstalled package has this symbol? I think I may > > > have to do a similar search since if one package is missing it could be > > > others are also missing. > > > > I have SDL_RWseek in SDL2_image-2.0.5 > > > > -- > > Dave > > > > Love is a snowmobile racing across the tundra and then suddenly it flips > > over, > > pinning you underneath. At night, the ice weasels come. > > --Friedrich Nietzsche > > > > -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] stone_soup
On 10/01/21 03:56, Jude DaShiell put forth the proposition: > Built successfully run fails with: > crawl: symbol lookup error: /usr/lib64/libSDL2_image-2.0.so.0: undefined > symbol: SDLRWseek > How would I find which uninstalled package has this symbol? I think I may > have to do a similar search since if one package is missing it could be > others are also missing. I have SDL_RWseek in SDL2_image-2.0.5 -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] When to increment BUILD number?
On 10/01/21 06:38, CRTS put forth the proposition: > Should the BUILD number in a *.SlackBuild script only be incremented > when the *.SlackBuild script itself changes or shall it be also incremented > when the *.info file or any other file is changed? Hi CRTS, This is my personal take on it. A BUILD bump is a sign that users need to update, other than a VERSION change. Usually the BUILD will increment if something significant changes in the package. Usually something that affects usage. Maybe a bugfix or patch, or perhaps adding some new documentation or a man page etc. Changing something in the slackbuild that doesn't really affect the resulting package shouldn't need a BUILD bump. If something changes in the .info, maybe like a new md5sum or download location, then it isn't usually necessary to bump the BUILD. An exception might be if perhaps there was some security implications with an old download location (I think most of us know about the rumpus that happened when sourceforge decided to interfere with source tarballs a few years ago). If VERSION changes then BUILD is usually reset to 1. With other files it will depend on what they are, and how much they affect usage and the end package. It's mostly a matter of common sense. Would someone that has the package installed really need to update because of whatever was changed? Hope this helps. There are probably some things I forgot, and there will probably be other opinions coming about this. -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] Request for when taking over as a SlackBuild maintainer
When agreeing to take over a script as a new maintainer, could we have an update with your name and email in the .info ASAP please? Thanks and have a great 2021 :-) -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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 - 20201206.1
On 06/12/20 11:25, Slackbuilds Users put forth the proposition: > Hello, > I had an issue when compiling the most recent version of avahi. > Digging a little, it turns out that I have Qt5 installed and the > "configure" phase was bothering with it. > Inserting a "--disable-qt5" solved the problem. > Attached below follows a patch that hopefully solves the problem not > only in my system. Hi Luiz I don't have this problem in a clean chroot with qt5 installed. Are you using qt5 5.12.8 from SBo? -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] libcapi20 not found.
On 26/11/20 14:28, Fernando Lopez put forth the proposition: > HTTP request sent, awaiting response... 503 Service Unavailable That's a server error. There's nothing we can do about it. -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] New submission: protonvpn-cli
On 13/11/20 14:41, Slackbuilds Users put forth the proposition: > Hello list, > I just tried to re-upload a new submission, protonvpn-cli. The only change > is to add a missing dependency, docopt. I get a "File exists; a submission > by the name 'protonvpn-cli' is already pending approval." error, so I assume > the submission failed? Hi Erich, You will need to remove the old submission before you can submit a new one. Submissions are usually checked and approved at the weekend so your old one is still in the list. You should have had an email when you submitted with the removal URL and a removal code, -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] Clementine up for grabs
On 03/11/20 20:48, Andrzej Telszewski put forth the proposition: > On 03/11/2020 06:29, Jeremy Hansen wrote: > > On Mon, Nov 2, 2020, 12:21 PM Dave Woodfall > <mailto:d...@slackbuilds.org>> wrote: > > > > I no longer want to maintain clementine. I haven't used it for > > a very long time. There is still some development happening, as I > > often get emails from github about commits etc. > > > > If anyone would like to take it over, they are welcome to. If not, > > I'll mark it as orphaned. > > > > > > I haven't used it before, but I was a big fan of the old amarok. If > > someone already uses it and wants to take over, I'm totally fine with > > that, but if no one else claims it by the end of the week, I'll take it > > over. > > > > Jeremy > > > > > I'm actually using *Clementine* as my main music player. > I'll happily take it over. > I'm bold enough to say that I'm better fir than Jeremy, because I actually > use it. :-> > On the other hand, I use it to play local collection exclusively, I don't > use services like Spotify. > And for that reason, I will not be able to reassure correct operation for > networked services. > If you find me a good fit for the job, I'm ready to take it. :-) > Cheers! > -- > Andrzej Andrzej, have you tried the Strawberry fork, by the way? http://slackbuilds.org/repository/14.2/multimedia/strawberry/ -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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] Clementine up for grabs
I no longer want to maintain clementine. I haven't used it for a very long time. There is still some development happening, as I often get emails from github about commits etc. If anyone would like to take it over, they are welcome to. If not, I'll mark it as orphaned. -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche ___ 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-user] Teamviewer3 EULA bypass
On 28/10/20 00:01,
B Watson put forth the proposition:
> On 10/23/20, Dave Woodfall wrote:
> >
> > I must admit that I'm a bit uncomfortable with this, and I wouldn't
> > want anything to backfire on SBo for hosting it. In my mind it's no
> > worse than having to download jdk etc. source manually to build it.
> >
> > Just because it's an inconvenience for build tools is no reason to
> > try to bypass what the developers are trying their hardest to have
> > people read, and there may be good reason for someone to *want* to
> > read it to understand if they agree and want to continue to install
> > it, or not, as the case may be.
> >
> > I would put a note in the README about it and leave it at that.
> >
> > What do the other admins think?
> I think it'd actually be OK to add an environment variable EULA=agree
> or such, defaulting to off. The user's only required to read the
> EULA *once*, not every time he has to rebuild/reinstall the package
> (possibly on a different Slackware box than the first time). Set the
> variable and it skips the EULA (by whatever means).
> This will especially helpful to the maintainer of the package, who
> might have to run the script multiple times while developing/testing
> it.
> Also, if it doesn't already do so, it would be nice to include a copy
> of the EULA as e.g. /usr/doc/$PRGNAM-$VERSION/EULA.txt in the package.
That's a fair point. Perhaps a more specific name for the variable
to the equivalent of ${PRGNAM}_EULA would be the way to go, in case
more crop up in the future and we need to distinguish between them.
--
Dave
Love is a snowmobile racing across the tundra and then suddenly it flips over,
pinning you underneath. At night, the ice weasels come.
--Friedrich Nietzsche
___
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-user] Teamviewer3 EULA bypass
On 23/10/20 16:21, King Beowulf put forth the proposition: > On 10/21/20 4:01 PM, Rich Shepard wrote: > > On Wed, 21 Oct 2020, King Beowulf wrote: > > > >> Teamviewer3 will run the EULA acceptance no matter what - there doesn't > >> seem to me a command line option to automatically accept. as a result, > >> any > >> automated SBo build tools get "stuck." As my bash-fu is rudimentary, > >> anyone know a good bashism to allow for automatic acceptance? > > > > Ed, > > > > Would 'expect' do this for you? > > > >... > Sure. I was hoping for a solution less dependent on external, non-bash > commands. > -Ed I must admit that I'm a bit uncomfortable with this, and I wouldn't want anything to backfire on SBo for hosting it. In my mind it's no worse than having to download jdk etc. source manually to build it. Just because it's an inconvenience for build tools is no reason to try to bypass what the developers are trying their hardest to have people read, and there may be good reason for someone to *want* to read it to understand if they agree and want to continue to install it, or not, as the case may be. I would put a note in the README about it and leave it at that. What do the other admins think? -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche signature.asc Description: PGP signature ___ 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] fontforge
On 21/10/20 18:47, Dave Woodfall put forth the proposition: > On 21/10/20 13:33, > B Watson put forth the proposition: > > On 10/21/20, Matteo Bernardini wrote: > > > > > > I was about to test it, but before trying I just want to be sure that > > > you have noted this bit in fontforge's README > > > > > > "NOTE: please remove previous version before building new version." > > I know from experience that trying to build a new fontforge without > > following this advice causes a build failure. > > A question for the maintainer: Why doesn't the SlackBuild check for > > this and abort or at least warn the user? It could be done with very > > little code, and would have saved however much time we've collectively > > spent thinking and writing about it, in this thread. > I'll add that this week. I do something similar in Qt5 already. > -- > Dave > Love is a snowmobile racing across the tundra and then suddenly it flips over, > pinning you underneath. At night, the ice weasels come. >--Friedrich Nietzsche By the way, this usually only happens after a significant update. Minor changes don't seem to trigger this. -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche signature.asc Description: PGP signature ___ 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] fontforge
On 21/10/20 13:33, B Watson put forth the proposition: > On 10/21/20, Matteo Bernardini wrote: > > > > I was about to test it, but before trying I just want to be sure that > > you have noted this bit in fontforge's README > > > > "NOTE: please remove previous version before building new version." > I know from experience that trying to build a new fontforge without > following this advice causes a build failure. > A question for the maintainer: Why doesn't the SlackBuild check for > this and abort or at least warn the user? It could be done with very > little code, and would have saved however much time we've collectively > spent thinking and writing about it, in this thread. I'll add that this week. I do something similar in Qt5 already. -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche signature.asc Description: PGP signature ___ 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] Bug in OpenCASCADE cmake "includes"?
On 16/10/20 19:03,
Heiko Rosemann put forth the proposition:
> Hi everyone,
> I recently ran across what looks like a small bug in OpenCASCADE's cmake
> scripts, for example the one in
> /usr/lib64/cmake/opencascade/OpenCASCADEFoundationClassesTargets-release.cmake
> It seems to me like ${OCCT_INSTALL_BIN_LETTER} should not be in there,
> for example in line 11:
> IMPORTED_LOCATION_RELEASE
> "${_IMPORT_PREFIX}/lib64\${OCCT_INSTALL_BIN_LETTER}/libTKernel.so.7.3.0"
> This caused compilation errors for me when I tried installing FreeCAD
> 0.18.4 on -current, but the files look the same on 14.2.
> I'm not sure where the blame lies - OpenCASCADE upstream, our packaging
> of OpenCASCADE or FreeCAD's searching for OpenCASCADE are my candidates.
> Cheers,
> Heiko
> JFTR: Adding -DOCCT_CMAKE_FALLBACK=ON to FreeCAD's cmake option helps
> FreeCAD compile - no idea about other software that might also depend on
> OpenCASCADE.
> --
> eMails verschlüsseln mit PGP - privacy is your right!
> Mein PGP-Key zur Verifizierung: http://pgp.mit.edu
Heiko,
Did you contact the maintainer about it? It might also be worth
checking ponce's -current slackbuilds repo to see if this has been
implemented.
https://github.com/Ponce/slackbuilds/
--
Dave
Love is a snowmobile racing across the tundra and then suddenly it flips over,
pinning you underneath. At night, the ice weasels come.
--Friedrich Nietzsche
signature.asc
Description: PGP signature
___
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] Wrong Download Links in Yubikey related Slackbuilds
On 13/10/20 22:04, T3slider put forth the proposition: > On Sun, Oct 11, 2020 at 03:55:57AM +, Linus Yeung wrote: > > I found these Yubikey related SB have a typo in their download links: > > > > - libyubikey > > - yubikey-personalization-gui > > - ykpers > > > > The links: https://developers.yubico.com/yubico-c/releases/x.tar.gz > > > > should be: https://developers.yubico.com/yubico-c/Releases/x.tar.gz > Thanks for the heads-up, this used to be working, so I expect upstream > changed the case of the source directory (or recently became case > sensitive). I'll push an update tomorrow. > -T3slider Hi, I fixed these in my branch. -- Dave Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Friedrich Nietzsche signature.asc Description: PGP signature ___ 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 wants to upgrade non-installed package
On 03/10/20 13:27, Rich Shepard put forth the proposition: > On Sat, 3 Oct 2020, Dave Woodfall wrote: > > On 14.2 or -current? > Dave, > I should have provided more information in my message; 14-2/x86_64. > > Please supply the output of sbopkg -c > Among others, > dokuwiki: > POTENTIAL UPDATE > Installed version: dokuwiki-20180422b-noarch-1_SBo > Repo version: dokuwiki-20200729-noarch-1_SBo > $ ls /var/log/packages/ | grep docuwiki > $ Does `locate dokuwiki-20180422b-noarch-1_SBo' output anything? -- Dave signature.asc Description: PGP signature ___ 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 wants to upgrade non-installed package
On 03/10/20 12:19, Rich Shepard put forth the proposition: > On Sat, 3 Oct 2020, Jheengut Pritvi wrote: > > what does ls /var/log/packages/ | grep docuwiki -i show up? > That it's not installed. > Regards, > Rich On 14.2 or -current? Please supply the output of sbopkg -c -- Dave signature.asc Description: PGP signature ___ 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] Signal-Desktop obsolete
On 27/09/20 23:14, David O'Shaughnessy put forth the proposition: > Hello, just a heads up that Signal-Desktop-0.42.2 ought to be removed, it's > from August 2017* and such a build will not function on the Signal network. > In fact upstream now denies service after a client becomes too out of date > (and three years is far beyond that limit). Removed. -- Dave signature.asc Description: PGP signature ___ 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 - 20200926.1
On 27/09/20 11:24, Slackbuilds Users put forth the proposition: > Hello, > supertuxkart much likely has the MD5 sum not updated from version 1.1 to > 1.2 in the .info file. Fixed in my branch. -- Dave signature.asc Description: PGP signature ___ 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 - 20200926.1
On 27/09/20 00:18, Arnaud put forth the proposition: > Hi ! > it looks like the new rspamd does not compile with 14.2 cmake. > It needs the package cmake-202x, and the Slackbuild itself needs to be changed > to use cmake-202x. > After doing that, it builds fine. Fixed in my branch. Also added libsodium to REQUIRES. -- Dave signature.asc Description: PGP signature ___ 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 md5sum failure
On 26/09/20 17:11, B Watson put forth the proposition: > On 9/26/20, Dave Woodfall wrote: > >> Length: 402751 (393K) [text/html] > >> Saving to: smplayer-20.4.2.tar.bz2 > > You need to download the source in a browser for that one. What you > > have there is `text/html', which shows in the download output. > > Sourceforge has unfortunately been broken for many downloads for a > > while now. One trick I found is to do: > Not so. I just downloaded it with wget, and it was fine. You are correct. I'd forgotten that I'd set a user-agent in curl, and it turns out using a Firefox UA produces 241K HTML files, but when I unset the UA I do get bz2. > Aside: 393K for an HTML page? Insane. Yeah, that is pretty bad. I opened one in links to check, and it turns out to be the usual smplayer homepage. I imagine there is a lot of inline
