Re: [Slackbuilds-users] ganglia is missing, is it not needed anymore?

[Jeremy Hansen]

I was able to build it using:

LDFLAGS=-ltirpc \
CFLAGS=-I/usr/include/trip \
./configure

make completed successfully, but I haven't checked the program beyond that.

Hopefully it will get you on the right trajectory to get an updated
SlackBuild submitted to SBo.

Jeremy

On Thu, Apr 11, 2024, 9:36 AM Karel Venken via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> Emmanuel,
>
> (I did not find anything on the ganglia project about ti-rpc - so I am
> trying myself)
>
> Not there yet, but in SlackBuilds I added to configure the line
> CPPFLAGS=-I/usr/include/tirpc (before OPTS line ) which fixed the
> configure error complaining about the issing rpc. A small step I guess -
> not sure if this already helps. However, (as expected) the code can not
> be linked. I have to figure out how to add this - aditional change in
> configure.ac? - but I am not familiar with the autotools.
>
> kind regards
>
> Emmanuel wrote:
> > Hi,
> >
> > I kept the ganglia package up to 14.2, I'm going to try to compile the
> > new version in 15.0 and send the update as soon as I can.
> > Karel, if you manage to make it work, let me know.
> >
> > Best regards.
> >
> > On Wed, Apr 10, 2024 at 1:27 PM Karel Venken via SlackBuilds-users
> >  > > wrote:
> >
> > Matteo,
> >
> > You are correct, it is not building on 15.0. I have been looking into
> > this and digging trough some history and newsgroups and what I found:
> >
> > ganglia needs sun-rpc: when configure:
> >
> > checking rpc/types.h usability... no
> > checking rpc/types.h presence... no
> > checking for rpc/types.h... no
> > checking for rpc/xdr.h... no
> > configure: error: your system is missing the Sun RPC (ONC/RPC)
> > libraries
> >
> > slackware 15.0 adopted a more recent version of glibc (starting from
> > 2.35 while sunrpc is failing from version 2.26 on) the regression
> > seems
> > not to be mentioned in the Changelog. The libnsl package in 15.0
> > mentions it is linked against TI-RPC and that RPC was in glibc
> before.
> >
> > So, it is suggested to use ti-rpc, but I am not sure this can be done
> > with ganglia. Perhaps I need to check the latest release...
> >
> >
> > I was curious if someone else is using ganglia with slackware
> > 15.0. If
> > so I thought I should have found some information on this problem.
> >
> >
> > Matteo Bernardini wrote:
> > > if I recall correctly I think they were removed when the repository
> > > was migrating to 15.0 because they weren't building...
> > >
> > > sorry, what do you mean by "is it not needed anymore"? if someone
> > > still uses them I don't see any issues for them to be submitted
> > back
> > > to the repo by whoever wishes to maintain them further.
> > >
> > > Matteo
> > >
> > > Il giorno mer 10 apr 2024 alle ore 15:29 Karel Venken via
> > > SlackBuilds-users  > 
> > >  > >> ha scritto:
> > >
> > > Hi,
> > >
> > > I am migrating some of my systems to 15.0 and I noted that
> > ganglia,
> > > ganglia-web was removed from SBo already some time ago. Is
> > it not
> > > needed
> > > anymore?
> > >
> > > kind regards.
> > > ___
> > > SlackBuilds-users mailing list
> > > SlackBuilds-users@slackbuilds.org
> > 
> > >  > >
> > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > > Archives -
> > https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > > FAQ - https://slackbuilds.org/faq/
> > >
> >
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@slackbuilds.org
> > 
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives -
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> >
> >
> > --
> > *
> >Emmanuel
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - 

Re: [Slackbuilds-users] updating dozens/hundreds packages/queues more easily/correctly weekly?

[Jeremy Hansen]

On Mon, Apr 1, 2024, 8:07 PM  wrote:

> I installed more packages built from SlackBuilds.org (SBo) than urchlay
> (a few years ago 1150+, now more) and see after updates, some/many need
> most/all dependencies rebuilt but you never know until either building
> or using crashes.  Is there a way to keep track and rebuild these
> without having to manually load dozens/hundreds queues in sbopkg (nor
> use its command-line)--I heard it may be easier with sborepo?  I have no
> need for my own repository and want to avoid creating one (other than
> just a directory/folder) but are there instructions on updating more
> easily/correctly weekly just for users?
>

Simply put, sbopkg does not have any proper way to handle this other than
rebuilding the entire tree.

The only program I know that decently handles this is slackrepo, but it
seems to be best used on a clean machine (either virtual or not), which can
be difficult with certain users setups.

But I also have only used sbopkg and slackrepo (with the latter used in
conjunction with slapt-get to handle dependencies of packages), so others
might be better set up for it without me being aware of it.

Jeremy

>
___
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] WIP: protobuf3 25.3

[Jeremy Hansen]

If you update just a single package without checking other programs you
have installed, you could continue to run into issues like this. We ensured
the clementine update was pushed in the same public update as protobuf3 to
make sure that the repo continued to work.

This week we're working on an SQLAlchemy update and another package I
maintain (sickchill) needs to have an update to work (I actually have to
remove a patch that allowed it to still work with the older version). If
you update sickchill without updating SQLAlchemy, sickchill will break,
just as if you update SQLAlchemy without updating sickchill, sickchill will
break.

If you do pick and choose which updates to make without doing everything
and something is broken, try rebuilding it to see if it fixes it.

As for the versioning, this is the version from upstream. On SBo, it hadn't
seen an update in almost two years while upstream kept chugging along.
Also, sometimes upstream will change how they version things, so you might
see big jumps at times.

The tools don't care about jumps in versions, in fact, they don't even care
what the version number is, just that the version and/or build number is
different than the current version or build number. This is why there is no
issue using commit IDs as versions or throwing dates or kernel versions
into the version.

Jeremy

On Mon, Mar 11, 2024, 5:14 AM Ruben Carlo Benante  wrote:

> Hi Jeremi,
>
> I did not rebuild clementine after updating protobuf3 at the time.
> Since this is a prod machine, I won't be able to test.
>
> I'm still looking for some guidelines on how developers usually create
> virtual machines to test. I used virtualbox when I developed for debian,
> but I don't like this approach anymore. I'm trying to learn LCX, and for
> slackware it doesn't have templates ready to go, so there is that.
>
> Anyway, thanks for your reply. Good to know it works. I'm still waiting
> for the protobuf3 maintainer reply on the version numbers (previous email)
>
> Cordialmente,
>
> Ruben
>
> --
> Dr. Beco
> AI Researcher
>
>
>
>
>  On Sun, 10 Mar 2024 19:45:43 -0300 *Jeremy Hansen
> >* wrote ---
>
> Did you rebuild clementine after updating protobuf3? You should be on
> build 2 of clementine as that includes fixes for the new protobuf3 version.
>
> It works fine on my end (I'm the clementine maintainer).
>
> Jeremy
>
> On Sun, Mar 10, 2024, 1:51 PM Ruben Carlo Benante via SlackBuilds-users <
> slackbuilds-users@slackbuilds.org> wrote:
>
>
> Another thing that may or may not be related:
>
> The mp3 player Clementine has stoped working after upgrade.
>
> I've returned to grpc-1.48.4 and protobuf3-3.20.1, and after the downgrade
> Clementine works fine again.
>
> Cordialmente,
> Ruben
>
> --
> Dr. Beco
> AI Researcher
>
>
>
>
>  On Sun, 10 Mar 2024 13:54:41 -0300 *Ruben Carlo Benante  >* wrote ---
>
> Hello,
>
> Is there an error in the version number? Or is it going from 3 to 25 and
> keep growing further in the next versions?
>
> The following names are what it looked like in the past:
>
> * Packages/protobuf-2.6.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.17.3-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.18.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.19.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.19.3-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.19.4-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.20.0-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.20.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-25.3-x86_64-1_SBo.tgz
>
>
> I'm afraid slackpkg or sbotools or sbopkg will complain if the next comes
> with something like
>
>  Packages/protobuf3-3.26.0-x86_64-1_SBo.tgz or something as previous format
>
>
> Cordialmente,
> Ruben
>
> --
> Dr. Beco
> AI Researcher
>
>
>
>
>  On Sat, 02 Mar 2024 18:10:31 -0300 *Giancarlo Dessì  >* wrote ---
>
> Il 01/03/24 20:35, Willy Sudiarto Raharjo ha scritto:
> > Hi
> >
> > i have just started to work on protobuf3 updates, pushing 2y of works
> > by upstream since last update.
> >
> > However, there are 26 other scripts which depends on protobuf3, listed
> > here (https://slackbuilds.org/advsearch.php?q=protobuf3=revdep1)
> >
> > although we do have CI engine that could help us test whether the new
> > update will break them or not, it won't help us testing the runtime
> > issues. Therefore, i would like to ask for help by those who are using
> > these 26 packages to see if by upgrading protobuf3 and rebuilding them
> > will have any runtime issues or not.
> >
> > I will keep the protobuf3 updates for future public update (like 1-2
> > weeks delay) to give others more time to test.
> >
&

Re: [Slackbuilds-users] sbotools config issues

[Jeremy Hansen]

On Sun, Mar 10, 2024, 5:51 PM J. Milgram  wrote:

>
> Is sbopkg more actively maintained than sbotools?
>

SBo tools hasn't been updated in almost 5 years.

https://github.com/pink-mist/sbotools

Jeremy

>
___
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] WIP: protobuf3 25.3

[Jeremy Hansen]

Did you rebuild clementine after updating protobuf3? You should be on build
2 of clementine as that includes fixes for the new protobuf3 version.

It works fine on my end (I'm the clementine maintainer).

Jeremy

On Sun, Mar 10, 2024, 1:51 PM Ruben Carlo Benante via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> Another thing that may or may not be related:
>
> The mp3 player Clementine has stoped working after upgrade.
>
> I've returned to grpc-1.48.4 and protobuf3-3.20.1, and after the downgrade
> Clementine works fine again.
>
> Cordialmente,
> Ruben
>
> --
> Dr. Beco
> AI Researcher
>
>
>
>
>  On Sun, 10 Mar 2024 13:54:41 -0300 *Ruben Carlo Benante  >* wrote ---
>
> Hello,
>
> Is there an error in the version number? Or is it going from 3 to 25 and
> keep growing further in the next versions?
>
> The following names are what it looked like in the past:
>
> * Packages/protobuf-2.6.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.17.3-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.18.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.19.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.19.3-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.19.4-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.20.0-x86_64-1_SBo.tgz
> * Packages/protobuf3-3.20.1-x86_64-1_SBo.tgz
> * Packages/protobuf3-25.3-x86_64-1_SBo.tgz
>
>
> I'm afraid slackpkg or sbotools or sbopkg will complain if the next comes
> with something like
>
>  Packages/protobuf3-3.26.0-x86_64-1_SBo.tgz or something as previous format
>
>
> Cordialmente,
> Ruben
>
> --
> Dr. Beco
> AI Researcher
>
>
>
>
>  On Sat, 02 Mar 2024 18:10:31 -0300 *Giancarlo Dessì  >* wrote ---
>
> Il 01/03/24 20:35, Willy Sudiarto Raharjo ha scritto:
> > Hi
> >
> > i have just started to work on protobuf3 updates, pushing 2y of works
> > by upstream since last update.
> >
> > However, there are 26 other scripts which depends on protobuf3, listed
> > here (https://slackbuilds.org/advsearch.php?q=protobuf3=revdep1)
> >
> > although we do have CI engine that could help us test whether the new
> > update will break them or not, it won't help us testing the runtime
> > issues. Therefore, i would like to ask for help by those who are using
> > these 26 packages to see if by upgrading protobuf3 and rebuilding them
> > will have any runtime issues or not.
> >
> > I will keep the protobuf3 updates for future public update (like 1-2
> > weeks delay) to give others more time to test.
> >
> > The protobuf3 update can be seen here
> > https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip
> >
> > Big thanks in advance
> >
> At the moment I tested new protobuf3 in -current, it works for
> protobuf-c/postgis and qgis
>
> After upgrade of protobuf3 the entire tree until qgis was broken, I had
> to rebuild protobuf-c and then postgis and finally qgis because protobuf
> is required as first level dependency also by qgis
>
> --
>
> *
> Giancarlo Dessì
> https://www.giand.it
> https://github.com/giandex
>
> Slackware Linux... because it works!
> *
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] kicad slackbuild

[Jeremy Hansen]

On Sun, Mar 10, 2024, 3:58 AM Fernando Lopez 
wrote:

> yes. it changes every time. just ignore the md5sum.
>
> On Sun, Mar 10, 2024 at 5:33 AM Tim Dickson via SlackBuilds-users <
> slackbuilds-users@slackbuilds.org> wrote:
>
>> anyone having issues with md5sum i'm getting
>> Expected: dd187abbfb1109f8d417aa08fc75d19f
>>  Found:414143a111e9217b3ae792328ff98bdc
>>
>> ?
>> regards, Tim
>
>
If GitLab can't provide consistent downloads to match md5 hashes, maybe it
should be switched to GitHub downloads:

https://github.com/KiCad/kicad-source-mirror/archive/refs/tags/8.0.0/kicad-source-mirror-8.0.0.tar.gz

The SlackBuild would only need minor corrections to reflect the new source
filename, since it is different than the existing filename (introduce a
SRCNAM variable and swap out PRGNAM when the file or folder is referenced).

If something else caused this mismatch, feel free to ignore this message :)

Jeremy
___
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] WIP: protobuf3 25.3

[Jeremy Hansen]

On Mon, Mar 4, 2024 at 9:27 PM Jeremy Hansen 
wrote:

> On Fri, Mar 1, 2024 at 11:35 AM Willy Sudiarto Raharjo <
> will...@slackbuilds.org> wrote:
>
>> Hi
>>
>> i have just started to work on protobuf3 updates, pushing 2y of works by
>> upstream since last update.
>>
>> However, there are 26 other scripts which depends on protobuf3, listed
>> here (https://slackbuilds.org/advsearch.php?q=protobuf3=revdep1)
>>
>> although we do have CI engine that could help us test whether the new
>> update will break them or not, it won't help us testing the runtime
>> issues. Therefore, i would like to ask for help by those who are using
>> these 26 packages to see if by upgrading protobuf3 and rebuilding them
>> will have any runtime issues or not.
>>
>> I will keep the protobuf3 updates for future public update (like 1-2
>> weeks delay) to give others more time to test.
>>
>> The protobuf3 update can be seen here
>> https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip
>>
>> Big thanks in advance
>>
>
> audio/clementine requires a minor update. PR is available below. Update
> works with both current and upgraded protobuf3, so the change is able to be
> merged immediately, whether or not protobuf3 is updated.
>
> https://github.com/SlackBuildsOrg/slackbuilds/pull/5353
>
> Let me know if you have any questions!
>
> Jeremy
>

Ooops :| Disregard... you already did the fix I found :D

I'll close the PR. I should've read the entire email. Sorry for the noise!

Jeremy
___
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] WIP: protobuf3 25.3

[Jeremy Hansen]

On Fri, Mar 1, 2024 at 11:35 AM Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> Hi
>
> i have just started to work on protobuf3 updates, pushing 2y of works by
> upstream since last update.
>
> However, there are 26 other scripts which depends on protobuf3, listed
> here (https://slackbuilds.org/advsearch.php?q=protobuf3=revdep1)
>
> although we do have CI engine that could help us test whether the new
> update will break them or not, it won't help us testing the runtime
> issues. Therefore, i would like to ask for help by those who are using
> these 26 packages to see if by upgrading protobuf3 and rebuilding them
> will have any runtime issues or not.
>
> I will keep the protobuf3 updates for future public update (like 1-2
> weeks delay) to give others more time to test.
>
> The protobuf3 update can be seen here
> https://git.slackbuilds.org/slackbuilds/log/?h=protobuf3-wip
>
> Big thanks in advance
>

audio/clementine requires a minor update. PR is available below. Update
works with both current and upgraded protobuf3, so the change is able to be
merged immediately, whether or not protobuf3 is updated.

https://github.com/SlackBuildsOrg/slackbuilds/pull/5353

Let me know if you have any questions!

Jeremy
___
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] tracking down SBo "dependencies"

[Jeremy Hansen]

This would only show dependencies of dav1d. It wouldn't show any packages
that depend on dav1d (unless there was a circular dependency), so it
wouldn't help find things that would be broken.

You could grep all the queue files for dav1d, but that would only show the
packages that had it as a hard dependency. Several will add support if
dav1d is found on the system (like VLC) without needing to specify it on
the REQUIRES line in the .info.

It's certainly one benefit of building in a clean system to prevent picking
accidental dependencies (which slackrepo does very well when set up
properly).

Jeremy

On Sat, Mar 2, 2024, 1:59 AM Jheengut Pritvi  wrote:

> sqg -p dav1d
>
> On Thu, 29 Feb 2024 at 20:12, Jim  wrote:
>
>> I recently upgraded the SBo dav1d, which upgraded the library from
>> libdav1d.so.6 to libdav1d.so.7.
>>
>> Unfortunately, a couple of other SBo packages (libheif and vlc) had
>> references to (specifically) libdav1d.so.6, which caused them to whine a
>> bit.
>>
>> It was easy enough to recompile libheif and vlc after I found the problem,
>> but this got me wondering...
>>
>> Does anyone have an easy way of tracking down this sort of "breakage"
>> which
>> might happen when upgrading an SBo package?
>>
>> Thanks.
>> Jim
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] tracking down SBo "dependencies"

[Jeremy Hansen]

On Thu, Feb 29, 2024, 11:46 AM Jim  wrote:

> On Thu, Feb 29, 2024 at 17:47 (+0100), Andrzej Telszewski wrote:
>
> > *From: *Jim 
> > *To: *slackbuilds-users@slackbuilds.org
> > *Date: *29 Feb 2024 17:12:58
> > *Subject: *[Slackbuilds-users] tracking down SBo "dependencies"
>
> >> I recently upgraded the SBo dav1d, which upgraded the library from
> >> libdav1d.so.6 to libdav1d.so.7.
>
> >> Unfortunately, a couple of other SBo packages (libheif and vlc) had
> >> references to (specifically) libdav1d.so.6, which caused them to whine a
> >> bit.
>
> >> It was easy enough to recompile libheif and vlc after I found the
> problem,
> >> but this got me wondering...
>
> >> Does anyone have an easy way of tracking down this sort of "breakage"
> which
> >> might happen when upgrading an SBo package?
>
> > Please consider tool like _slackrepo_.
> > It will rebuild a package in question should its dependiences be updated.
>
> Hi Andrzej,
>
> thanks for that pointer.
>
> From other discussions it's not clear that slackrepo would catch this, but
> maybe I'll find out.
>
> Jim
>

Looking at VLC's SBo page, dav1d support is detected automatically, but not
listed as a required dependency.

If slackrepo is used in a clean environment like expected, VLC would not be
compiled with dav1d support without explicitly adding that dependency
through the ADDREQUIRES option in the hintfile.

Thus, an upgrade to dav1d would leave VLC unaffected unless you manually
added that dependency to the hint file. If the dependency was added, VLC
would be rebuilt automatically by slackrepo.

Jeremy

>
___
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] Good practice to manage autodetected optional deps

[Jeremy Hansen]

On Tue, Feb 13, 2024, 4:34 PM Tonus  wrote:

> Hi all
>
> I have a slackbuild that builds man pages if Pandoc is installed
> (autodetected).
>
> If it isn't, the man pages compression in the SBo template makes the
> script fail
> What's the good practice ? Add `|| true` at the end of the lines ?
>
> Tryed on clean system without Pandoc and on my system that has Pandoc,
> it builds fine.
>
> --
> Regards,
>
> Tonus
>

There are a couple of options:

1. You could do an if/then check to see if the man pages exist and then run
the command if found.
2. You could require the user to pass an option to enable man page support
(with the note pandoc is required) and then use that to enable/disable the
building of the man pages (I assume they have an on/off override of the
autodetect). You could continue to use that flag to determine if the man
pages should be compressed.
3. You could detect whether pandoc is installed and make the above decision
for the user based on that.

Personally, #1 seems the easiest. Just detect if there are man pages with
an if/then statement and if they are, run the compression command:

if [ -d $PKG/usr/man ]; then
  # run compression command
fi

(You may need to tweak that if statement depending on how the program
handles dirs.)

Jeremy
___
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 homepage query

[Jeremy Hansen]

On Tue, Feb 13, 2024, 6:30 AM Tim Dickson via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> Hi all, there are three slackbuilds I look after which need a homepage
> update from http to https
> should I submit 3 updates with .info updated and build no. bumped, or is
> there an easier way.
>
> as the build is identical, maybe the build number doesn't need bumping,
> but is it possible
> to do an updated with no change in version or build?
>
> the old http home sites still work, they are just permanently redirected
> to the https versions.
> regards, Tim
>

I wouldn't do a build number bump since the resulting program that's
created remains unchanged. If you changed dependencies or the compilation
process, that should constitute a build number bump.

Personally, I would do individual commits but submit them under a single
PR... like I did here in the following PR:

https://github.com/SlackBuildsOrg/slackbuilds/pull/3261

Jeremy

>
___
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] Larry Hajali's SlackBuilds

[Jeremy Hansen]

Are Larry Hajali's SlackBuilds up for grabs? There has only been one update
from him since April 2021 and that was in May of 2022[1]. I found this
because another python3 package I'm working on required lxml and it pulled
in several python2 packages as dependencies, so I'd like to split lxml into
python2 and python3 packages. It seems many of his other python packages
could use naming changes and/or splits.

If they are available, I can take the following as they're dependencies for
some of the SlackBuilds I maintain:

libraries/libcec/
libraries/libnfs/
libraries/platform/
libraries/tinyxml/
libraries/tinyxml2/
python/lxml/

The remaining SlackBuilds are:

academic/chartgeany
academic/qalculate-gtk
academic/speedcrunch
academic/tuxmath
academic/wxMaxima
accessibility/easystroke
audio/eyeD3
audio/kradio
desktop/notification-daemon
development/ldns
development/xmlcopyeditor
games/alienarena
games/assaultcube
games/brainparty
games/chroma
games/chromium-bsu
games/cubosphere
games/cuyo
games/dustrac
games/glestae
games/jag
games/meandmyshadow
games/megaglest
games/opensonic
games/pasang-emas
games/peg-e
games/rezerwar
games/yabause
graphics/qcad
graphics/yagf
libraries/bitstream
libraries/cdk
libraries/cuneiform
libraries/dcadec
libraries/enca
libraries/fpconst
libraries/gdata
libraries/gtkimageview
libraries/http-parser
libraries/irrlicht
libraries/libaacs
libraries/libb64
libraries/libbdplus
libraries/libdc1394
libraries/libdivecomputer
libraries/libdvbcsa
libraries/libgit2
libraries/libmodplug
libraries/libmusicbrainz3
libraries/libotf
libraries/libunique
libraries/lockdev
libraries/mini18n
libraries/ois
libraries/podofo
libraries/soil
libraries/t4k_common
misc/keychain
misc/subsurface
multimedia/audiopreview
multimedia/dvblast
multimedia/shotcut
multimedia/xvst
network/flvstreamer
network/nginx
network/pidgin-toobars
office/grisbi
office/sigil
office/texmaker
office/texstudio
perl/perl-Cstools
perl/perl-IO-CaptureOutput
perl/perl-Unicode-Map
perl/perl-Unicode-Map8
perl/perl-trayicon
python/apsw
python/boto
python/boto3
python/css-parser
python/cssselect
python/cssutils
python/dnspython
python/dukpy
python/filechunkio
python/gst0-python
python/html5-parser
python/mechanize
python/pydf
python/pyinotify
python/pymysql
python/pypoppler
python/python-distutils-extra
python/python-libnacl
python/python-musicbrainz2
python/python-sh
python/python2-MarkupSafe
python/python2-dateutil
python/python2-keyczar
python/rope
python/rsa
python/s3cmd
python/simplejson
python/unrardll
system/dosemu
system/sysdig

Thanks,
Jeremy

[1]
https://git.slackbuilds.org/slackbuilds/log/?h=15.0=author=Larry+Hajali
___
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] icalendar & python3-icalendar Duplicate

[Jeremy Hansen]

It seems that icalendar has been added twice by tonus. One as
python/icalendar and another as python/python3-icalendar.

https://slackbuilds.org/repository/15.0/python/icalendar/
https://slackbuilds.org/repository/15.0/python/python3-icalendar/

There seems to be no real difference between the two, so I propose we
remove icalendar and keep python3-icalendar.

Only desktop/calcure will need its REQUIRES line updated.

Jeremy
___
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 - 20240106.1

[Jeremy Hansen]

On Tue, Jan 9, 2024, 9:26 AM Petar Petrov  wrote:

> >And then on github I simply make a pull request
> how do you "simply make a pull request"?
>
> -p
>

I'm a relative git and GitHub newb, but here's what I did to start working
with GitHub. (For those who are far more knowledgeable than me, if there
are improvements to be made, please let me know.) I'm sure GitLab is
similar, but they have slight variations in terminology.

This is aimed at other git/GitHub newbs... if you aren't one, I apologize.

To get started, do the following:

1. Fork SBo's GitHub repo through the GitHub interface (you need to have a
GitHub account and be logged into it to fork).
2. Clone your newly forked repo onto your computer.
  git clone $your_new_repo_address
3. Set SBo's GitHub as upstream to make getting public updates easier.
  git remote add upstream git://github.com/SlackBuildsOrg/slackbuilds.git

If you've never used git on your computer to make commits before, you'll
need to tell git who you are so it can know who to attribute your commits
to:

  git config --global user.email "y...@example.com"
  git config --global user.name "Your Name"

Now you're ready to start updating on your local computer.

1. Create a new branch for the package you're updating and switch to that
branch. Typically this will be the package name that you're updating, but
naming schemes are more for you than anything. The name of the branch won't
affect the SBo admins reviewing your pull request.
  git checkout -B $branch_name
2. Make the changes to the files and verify everything works. This may
require moving those files to a clean VM to verify they build properly in a
clean environment.
3. Commit those changes to that branch on your local repo:
  git commit -m "network/discord: Update version to 1.2.3"
location/to/changes
(If there are multiple package changes due to dependency bumps or similar,
do an individual commit for each package.)
4. Once all commits are complete that apply to your update, push those
commits to your GitHub repo, forcing GitHub to create a new remote branch
(since it only exists locally):
  git push -f origin $branch_name
5. Git will provide a link in the output you can visit to submit the pull
request (PR) or you can just browse to your GitHub repo and you can submit
the PR yourself (if the push was recent, it'll list the option at the top
of the nation page, otherwise you can go into the branches area and can
submit it that way.
6. Explain your changes, if necessary, when submitting the PR back to SBo's
repo.

Then it's just a matter of waiting for SBo admins to review your
submission. If changes are needed, they'll suggest them. Once the changes
are accepted, you can delete the branch on your repo online and on your
local repo:
  git checkout master  # first make sure you're on your master branch
  git branch -D $branch_name

Once a public update is released, you can then update your local copy on
the master branch using:
  git checkout master
  git pull upstream master

>From here, you can then create a new branch again to make more changes,
commit them, push them back to GitHub, and submit a new PR.

Always commit changes into a separate branch. If you commit changes to
master, it'll give you problems when trying to sync with upstream after
public updates.

Hopefully this all makes sense. If there are any suggestions others have
that might improve this, feel free to add them.

Jeremy

>
___
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 - 20240106.1

[Jeremy Hansen]

On Tue, Jan 9, 2024, 8:51 AM Willy Sudiarto Raharjo 
wrote:

> >> I never group PR for unrelated packages.
> >> A single commit should only be on one package, not multiple packages.
> >>
> >
> > I've always grouped unrelated packages into a single PR. I've asked in
> the
> > past if they'd prefer one PR per package (or related packages) or all in
> > one PR and they said it doesn't matter.
> >
> > I just create an updates branch after each public update and will update
> my
> > packages throughout the week on my local machine. Towards the end of the
> > week, I'll push my changes to GitHub and submit a PR.
> >
> > I have no issues changing my workflow if SBo admins would prefer a
> certain
> > method, but when I've asked in the past, they said whatever works best
> for
> > me.
>
> basically it doesn't matter whether it's one big PR or separate PR, but
> personally i prefer split PR, unless it's a dependency, then it must be
> in one big PR
>
> having split PR is just easier for us (admins) to review the build
> process and also to write the trigger command to run the build.
>

That works for me. I'll update my process to simplify the admins' job. With
how many you guys review, I want to embrace KISS for you guys.

Also, can we trigger the build bot ourselves so it might be finished by the
time you see it? I've thought about trying it, but haven't yet.

Jeremy

>
___
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 - 20240106.1

[Jeremy Hansen]

On Tue, Jan 9, 2024, 7:58 AM Arnaud via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> I never group PR for unrelated packages.
> A single commit should only be on one package, not multiple packages.
>

I've always grouped unrelated packages into a single PR. I've asked in the
past if they'd prefer one PR per package (or related packages) or all in
one PR and they said it doesn't matter.

I just create an updates branch after each public update and will update my
packages throughout the week on my local machine. Towards the end of the
week, I'll push my changes to GitHub and submit a PR.

I have no issues changing my workflow if SBo admins would prefer a certain
method, but when I've asked in the past, they said whatever works best for
me.

Jeremy

>
___
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 rolling source packages and version numbers

[Jeremy Hansen]

On Mon, Jan 8, 2024, 6:44 PM Erik Falor  wrote:

> Hi all,
>
> LuaJIT uses rolling releases. There are no release tarballs available for
> download.  Instead of manual increments for each release, the build process
> uses the POSIX time stamp of the latest commit as the release number of the
> semantic version.
>
> The full version number is in the format `$major.$minor.$timestamp`.  For
> instance, the latest SlackBuild I'm preparing has this version number:
> 2.1.1703358377.
>
> One can download a tarball of a specific commit from their GitHub
> mirror[1].
> Because they aren't given tags with the version number, you have to refer
> to
> them by the commit ID:
>
>
> https://github.com/LuaJIT/LuaJIT/archive/c525bcb9024510cad9e170e12b6209aedb330f83/LuaJIT-c525bcb9024510cad9e170e12b6209aedb330f83.tar.gz
>
> Of course, this means that the tarball expands to a subdirectory that
> contains
> the commit ID instead of a version number in its name.
>
> I can reconcile this by adding the $REVISION variable to the SlackBuild:
>
> PRGNAM=luajit
> REVISION=${REVISION:-c525bcb9024510cad9e170e12b6209aedb330f83}
> VERSION=${VERSION:-2.1.1703358377}
>
> Is this a satisfactory solution, or has this problem been solved in a
> better way
> by another maintainer?
>
>
> [1] https://github.com/LuaJIT/LuaJIT
>
> --
> Erik Falor
>

I do something similar with picard-plugins [1]. They don't do formal
releases, just I just grab the commit that was current at the time of the
version of picard I'm packaging when it was released.

I don't think there is a formalized process to handle different versions
within the source name and folder structure. I like using SRCNAM, but
REVISION works well in your case as well.

[1] https://slackbuilds.org/repository/15.0/multimedia/picard-plugins/

Jeremy

>
___
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] xmlsec download link has moved

[Jeremy Hansen]

On Sun, Dec 31, 2023, 2:27 PM Jason Graham  wrote:

> The download link for the SBo xmlsec version is now in older-releases
> download folder:
> https://www.aleksey.com/xmlsec/download/older-releases/xmlsec1-1.2.38.tar.gz
> .
>
> Best,
> Jason
>

Releases are also available on GitHub, which might be the better option if
the website is changing folders of older releases.

https://github.com/lsh123/xmlsec/releases

Jeremy
___
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 - 20231014.1

[Jeremy Hansen]

On Sun, Oct 15, 2023, 9:38 AM fourtysixandtwo 
wrote:

> Tried it on my build vm and saw the same thing.   python3-mesonpy is also
> missing as a dep.
>
> I was able to build scipy without openBLAS by adding cblas as a dep and
> making the following change to the slackbuild.  (Everything needs to be
> rebuilt without openBLAS):
>
> -python3 -m build --wheel --no-isolation
> +python3 -m build --wheel --no-isolation -Csetup-args="-Dblas=blas"
> -Csetup-args="-Dlapack=lapack"
>

Is there a benefit with cblas over openBLAS? I'm not familiar enough with
either of them.

Jeremy
___
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] Added python3-meson-opt

[Jeremy Hansen]

On Wed, Oct 4, 2023 at 8:21 AM fourtysixandtwo 
wrote:

> Hi all,
>
> Thanks to a comment on LQ by brobr (not sure if you are on this list) I've
> uploaded three new builds that will allow builds like numpy and pandas to
> be upgraded to their latest versions and use the PEP517 build process.  In
> both cases this significantly decreases the build time due to the meson
> backend making use of all cores.
>
> Here's all 5 slackbuilds and the build queue for python3-pandas.  Please
> test.
> https://slackware.uk/~fourtysixandtwo/src/python3-meson-opt-test.tar.gz
>
> FYI Jeremy, when you get a chance to look at it let me know if you're ok
> with the newer versions of meson and meson-python (mesonpy) than what
> pandas 2.1.1 was pinned to.
>
> Cheers.
>

I was actually just looking into this more in depth yesterday after
ignoring it last week since I have two programs stuck due to not having
mesonpy.. Luckily, I didn't spend too much time with it :) I've looked over
your changes and tried them successfully with your pandas SlackBuild
update. Feel free to push your python3-pandas update on my behalf.

I'll wait until the public update before I update python3-scipy as that
requires mesonpy as well (but I got it working here with your packages
after a few changes to its pyproject.toml). Seems easier for SBo admins to
not have to pull updates from multiple branches to test if an update
works...

Thanks for your efforts!

Jeremy
___
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] precompiled "sources" missing libraries

[Jeremy Hansen]

On Sat, Sep 23, 2023, 3:10 AM Petar Petrov  wrote:

> Hi all!
>
> How do we check if a package is really missing some libs? SBo has
> scripts that just repackage the binaries provided by upstream. Using
> sbbdep can tell if a package is missing libs in the standard
> locations. However, many of these precompiled programs ship with their
> own libs installed in a custom location. Yet, sbbdep will see these as
> missing. I made myself a simple script
> (https://github.com/slackalaxy/revcheck) to check within install paths
> of packages if something is still missing. What do we do in cases like
> this:
>
> calibre-bin
> [MISSING] libQt6EglFSDeviceIntegration.so.6
> [MISSING] libQt6EglFsKmsSupport.so.6
> [MISSING] libQt6Pdf.so.6
> [MISSING] libQt6PdfWidgets.so.6
> [MISSING] libQt6SvgWidgets.so.6
> [MISSING] libQt6Test.so.6
> [MISSING] libQt6WlShellIntegration.so.6
>
> microsoft-edge
> [MISSING] libQt6Core.so.6
> [MISSING] libQt6Gui.so.6
> [MISSING] libQt6Widgets.so.6
>
> openoffice.org
> [MISSING] libdb-4.3.so
> [MISSING] libgstinterfaces-0.10.so.0
> [MISSING] libgstreamer-0.10.so.0
> [MISSING] libjawt.so
>
> vivaldi
> [MISSING] libQt6Core.so.6
> [MISSING] libQt6Gui.so.6
> [MISSING] libQt6Widgets.so.6
>
> wps-office
> [MISSING] libsystemd.so.0
>
> If someone is interested, this is how I use the script. Make sure
> sbbdep has updated its database, then:
>
> $ revcheck
> /var/lib/pkgtools/packages/openoffice.org-4.1.14_en_US-x86_64-3_SBo
>

A similar issue was reported a few weeks back with the nvidia driver, with
the ldd based script noticing that libcrypto.so.3 was not being found.

As it turns out, the binary Nvidia driver is made to support multiple
versions of libraries and will link to different versions based on what's
on the system. libcrypto.so.3 is for openssl v3, which isn't used in
Slackware 15.0, but it does have a fallback to use openssl v1.1 if v3 isn't
found.

https://lists.slackbuilds.org/pipermail/slackbuilds-users/2023-August/028485.html

We are likely seeing a similar issue here where several of your reported
programs are probably designed to work with both qt5 and qt6, depending on
what's found on the system. The software likely has a priority of qt6 and
would use that unless it's not found, and then fall back to qt5 libraries.

As long as the software works, it's likely what we're seeing and can likely
be safely ignored.

Jeremy
___
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] Intent for python SlackBuilds with SLKCFLAGS and LIBDIRSUFFIX

[Jeremy Hansen]

Thanks everyone! My original intent with stating for mass edits was not to
necessarily suggest using a mass edit to remove the ARCH if/then block, but
to have it present if used as a common point for any mass edits in the
future.

Also, indeed, it is a note and not a warning. However, I took it to be
something that while the stated item wouldn't stop the SlackBuild from
working, that the item causing the note should still probably be adjusted.

Thanks again! It was a lot of great input and gave me some stuff to think
about.

Jeremy

On Thu, Sep 21, 2023 at 12:20 PM fourtysixandtwo <
fourtysixand...@sliderr.net> wrote:

> > It would be easier when we do this thing during development cycle, not
> > during normal cycle like today. We can write anything into the git
> > during development cycle
>
> It will be indeed...instead of just getting involved at the end of the
> FTBFS stage.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Intent for python SlackBuilds with SLKCFLAGS and LIBDIRSUFFIX

[Jeremy Hansen]

Since sbolint (from system/sbo-maintainer-tools) is being ran on github PR
requests and newer versions of sbolint are catching when SLKCFLAGS and
LIBDIRSUFFIX are not being used, are we expected to not include them on the
SlackBuilds? If so, should we remove the entire if/then block for the ARCH
detection since that's typically all it does?

I ask because the templates for python SlackBuilds still include the ARCH
detection block and I don't want to remove it from my SlackBuilds if the
admins are expecting them to be there to simplify mass edits in the future.

I imagine this also applies to other SlackBuilds, but have only noticed it
so far with python ones. I expect there is a desire for consistency when
possible, so I'd love some clarification!

Thanks for everyone's work!
Jeremy (aka bassmadrigal)
___
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] codec2 1.0.3 Source No Longer Available

[Jeremy Hansen]

Gustavo,

In working on a project and testing possible dependencies, I came across
ham/codec2 on SBo. Unfortunately, it looks like the developer deleted the
1.0.3 release when they added the 1.2.0 release in July.

I see two ways forward, although, having not used it, I'm sure if one is
better than the other.

1. Find a saved copy of 1.0.3 and upload it somewhere else (sbodirectlinks
on sf.net or maybe ponce.cc, if he's willing). Then link SBo's source to
that copy.
2. Update codec2 to 1.2.0, assuming it doesn't break anything that depends
on it, and hope the developer doesn't delete that release when they drop
the next version.

I do not use this software, so if you no longer wish to maintain it, maybe
someone else can step in.

Thanks!
Jeremy
___
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] slackrepo fails to build youtube-dl due to URL encoding

[Jeremy Hansen]

On Fri, Jun 23, 2023, 8:22 AM Erich Ritz via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> Hello Dimitris and Andrew and list,
>
> I don't know if this message is more appropriate for the slackrepo
> maintainer or the youtube-dl maintainer.
>
> When trying to build youtube-dl with slackrepo it fails with:
>
> Building network/youtube-dl (update for version
> 2021.12.17+20230618_07af47960) 2023-06-23 14:25:18
> Removing old source files ...
> Downloading source files ...
> Verifying source files ...
> Running youtube-dl.SlackBuild ...   ETA
> 14:26:??
> env MAKEFLAGS='-j176 -l89' nice -n 5 bash ./youtube-dl.SlackBuild
> tar:
> /tmp/slackrepo/etr/slackrepo.MOV0A0/slackbuild_youtube-dl/youtube-dl-2021.12.17+20230618_07af47960.tar.xz:
> Cannot open: No such file or directory
> tar: Error is not recoverable: exiting now
> network/youtube-dl: youtube-dl.SlackBuild failed (status 2)
>  14:25:20
> Unmounting chroot ...
> :-( network/youtube-dl FAILED )-:
>
> slackrepo downloads the source file, but it is saved with a "%2B" instead
> of "+" in the filename.  This is due to curl not doing URL decoding.  Note
> these (partial) excerpts from curl's man page:
>
>-J, --remote-header-name
>   There's no attempt to decode %-sequences (yet) in the
> provided file name,
>   so this option may provide you with rather unexpected file
> names.
>-O, --remote-name
>   There  is  no  URL decoding done on the file name. If it has
> %20 or other
>   URL encoded parts of the name, they will end up as-is as
> file name.
>
> But I can see why slackrepo chooses to use curl instead of wget for
> sourceforge (as pointed out by a comment in srcfunctions.sh of slackrepo):
>
> $ wget --content-disposition
> https://downloads.sourceforge.net/project/dslackw/src/youtube-dl-2021.12.17%2B20230618_07af47960.tar.xz
> 2023-06-23
> 
> 10:14:19 (1.09 MB/s) -
> ‘youtube-dl-2021.12.17+20230618_07af47960.tar.xz?viasf=1’ saved
> [1172376/1172376]
>
> sourceforge "helpfully" tacks on "?viasf=1" to the filename.
>
> What's the best way forward?  If I remember correctly SBo policy allows
> for (if not encourages) the use of the "--content-disposition" flag for
> wget and similarly the "-J" flag for curl.  However, these break the
> filename in this case.  Should slackrepo do its own URL decoding when using
> curl?  Should slackrepo use wget for sourceforge and rename the files
> (stripping off "?viasf=1")?  Should SBo discourage URL encoding in
> filenames?
>
> Erich


Have you tried the download_basename pragma in your hintfile?

download_basename — provide a symlink for source downloads using the URL's
basename, for the benefit of SlackBuilds that don't expect
content-disposition to be respected.

Jeremy
___
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] Submission pending approval after removal

[Jeremy Hansen]

I removed the submission of python3-tus.py after I realized I used a poorly
formatted download url. It was still sitting in the pending queue, so I
removed it following the instructions in the submission email, corrected
the .info file, recreated the tarball and tried to upload it again.

I got the following error:

File exists; a submission by the name 'python3-tus.py' is already pending
approval.

This should not be a dependency of any other programs that were submitted
(but it is a dependency of a program I'm working to submit later this week
or next).

Can an admin please do their thing so I can reupload this tarball?

Thanks!
Jeremy
___
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] Next week, I will no longer maintain and update SlackBuilds

[Jeremy Hansen]

After working on a new program I'll be submitting to SBo, the following
programs are required dependencies, so I'll take them on since no one else
has:

python3-atomicwrites
python3-slugify
python3-text-unidecode
send2trash

Jeremy

On Sun, Jun 4, 2023 at 4:34 PM isaac...@isaacyu1.com 
wrote:

> Hi everyone,
>
> ​I now have 200+ SlackBuilds to maintain.
> Given my part-time job and my coursework, I am going to have a harder time
> maintaining it all.
>
> This is the last week in which I will maintain and update SlackBuilds.
>
> I will also switch my email address (on SlackBuilds) to
> isaa...@protonmail.com:
> https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
>
> I need to pay a small yearly subscription fee (to Gandi, the company) for
> the isaacyu1.com domain. However, the ProtonMail email service is free.
> Hence the email address change.
>
> My SlackBuilds are available at the following link:
> https://github.com/isaackwy/slackbuilds-15.0
>
> I plan on switching to Debian.
> Debian 12 (Bookworm) will be released in a few days, on June 10.
>
> - Isaac ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Replacement for broken network/sickrage

[Jeremy Hansen]

SBo admins,

network/sickrage has been broken for quite some time... at least since Feb
2022 when it was updated to its current version (at the very least, the
startup script needs modification and it is missing dependencies -- it
might have more issues). I was the original maintainer and someone took it
over without my permission and knowledge, but the version on SBo worked at
the time and newer versions were becoming harder to support, so I left it
as is.

Now that I'm on 15.0, I have been wanting to get a more modern version, but
current versions of sickrage are very difficult to work with as they have
specific dependency versions set for everything, not ranges like most
python packages. I can change those with a sed, but I ran into issues with
needing newer dependencies than were available on SBo.

Due to this, I looked for an alternative and came across sickchill (which
is a fork of sickrage, which was a fork of sickbeard). This one, while
having a ridiculous number of dependencies, I've been able to get to work
on 15.0. Due to this, I'd like to replace sickrage with sickchill on SBo. I
plan to formally request sickrage be removed when I go to submit
sickchill (which I hope to finish this week, but I still need to validate
and upload at least 26 new dependencies that weren't already on SBo, so it
might be longer).

That being said, I had a user/group set up back in 2016 when I first
submitted sickrage, called sickrage, with a uid/gid of 324. Would it be
possible to rename this to either sickchill or sickuser (in case a new fork
is needed in the future)? If preferred, I can request it when I go to
submit sickchill itself. I just wanted to run it by before I submit things
with the uid/gid changed.

Sorry for the wall of text.

Thanks!
Jeremy
___
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] linux kernel slackbuild

[Jeremy Hansen]

David Spencer (aka idlemoor & 55020) created a SlackBuild a few years ago
(geez, 6.5 years ago) to build kernels, calling his project dusk (Dave's
Unofficial Slackbuilt Kernels). It was envisioned to be set up in a cron
job and for it to automatically build new kernels point releases as they
were released by kernel.org, but the script can be ran by itself too.

The script might be of interest to some.

https://gitlab.com/idlemoor/dusk

On Wed, Jun 7, 2023, 10:10 PM David Chmelik  wrote:

> I like the idea because sometime after/in Linux kernel v2, documentation
> on how to build a kernel disappeared from the main site or from The
> Linux Documentation Project (TLDP) and/or was outdated.  For a while
> there was no documentation or only informal/partial documentation, not
> always very good.  Sometime by v4 there was documentation elsewhere but
> I don't know that it's official... I don't recall if there is any
> official documentation anymore or if it's back in TLDP, so I'd just like
> to see how it's done again.  In the days of v2 I build kernels maybe
> 200+ times trying to get a Matrox display/video card to work with dual
> monitors (as separate terminals) to no avail. I'd just like to see how
> it's done again and if we can be assured the SlackBuild does it right,
> that'd be something nice to see...
>
> On 6/7/23 6:48 PM, Julian Grinblat wrote:
> > I was wondering if a slackbuild for packaging the linux kernel is
> > something that would be accepted into SlackBuilds, or if people would
> > be interested in it to begin with.
> > I put together a small script for building and packaging the kernel
> > for personal use, here:
> > https://github.com/perrin4869/linux-kernel-slackbuild
> > 
> > The goal is to be able to install and remove and test kernels easily.
> > The repo follows the SlackBuild.org guidelines for the most part.
> > If this would be acceptable, is there anything that should be fixed?
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Next week, I will no longer maintain and update SlackBuilds

[Jeremy Hansen]

I had already claimed python3-pluggy and python3-pytest, but that was just
because they were dependencies of a few of my scripts and I didn't want
them abandoned. However, I'm in no way tied to them and if you'd like them,
I'm fine with you taking them. I haven't submitted a pull request to update
the maintainer info yet (probably do that tomorrow), so no harm done either
way.

Jeremy

On Mon, Jun 5, 2023, 10:43 PM Jay Lanagan via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> There is actually quite a few of your slackbuilds that I depend on for
> the nwg-shell project. I’d need to make a list but I would happily take
> them over. I couldn’t possibly take over all 200+ having never used
> many of them personally. But here’s ones that I’m interested in taking:
>
> Python3-aiohttp
> Python3-aiosignal
> Python3-async-timeout
> Python3-frozenlist
> python3-multidict
> python3-pluggy
> python3-pytest
> Python3-yarl
>
> If any of these have been previously taken and I missed it, then of
> course I'll concede on taking them. But any not claimed (I think I
> removed them all from my list) I'd like.
>
> Sorry to lose you to Debian, though truth be told, my main box is
> running sid as of late. Bookworm is going to be an excellent Linux
> release. Debian has a few things right over the slack world and the
> amount of available software is second to none. I totally understand
> the need for one to move on and free up the time spent doing such
> things.
>
> — Jay Lanagan
>
>
> > On Jun 4, 2023 at 7:34 PM,  wrote:
> >
> > Hi everyone,
> >
> > ​I now have 200+ SlackBuilds to maintain.
> > Given my part-time job and my coursework, I am going to have a harder
> > time maintaining it all.
> >
> > This is the last week in which I will maintain and update
> > SlackBuilds.
> >
> > I will also switch my email address (on SlackBuilds) to
> > isaa...@protonmail.com:
> > https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
> >
> > I need to pay a small yearly subscription fee (to Gandi, the company)
> > for the isaacyu1.com domain. However, the ProtonMail email service is
> > free. Hence the email address change.
> >
> > My SlackBuilds are available at the following link:
> > https://github.com/isaackwy/slackbuilds-15.0
> >
> > I plan on switching to Debian.
> > Debian 12 (Bookworm) will be released in a few days, on June 10.
> >
> > - Isaac ___ SlackBuilds-
> > users mailing list SlackBuilds-users@slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Next week, I will no longer maintain and update SlackBuilds

[Jeremy Hansen]

Thanks for all your work, Isaac! Best of luck to your future.

I can take the following as they're all dependencies of other packages I'm
maintaining:

cppy
iniconfig
ipython
pickleshare
python3-beniget
python3-deprecation
python3-executing
python3-gast
python3-iniconfig
python3-jedi
python3-joblib
python3-kiwisolver
python3-matplotlib-inline
python3-pandas
python3-pluggy
python3-pure_eval
python3-py
python3-pytest
python3-pytest-runner
python3-scipy
python3-stack_data
python3-threadpoolctl
python3-tornado
scikit-learn
traitlets
typing-extensions
xsimd

I can submit a pull request later this week to switch maintainership over.
Jeremy

On Sun, Jun 4, 2023 at 4:34 PM isaac...@isaacyu1.com 
wrote:

> Hi everyone,
>
> ​I now have 200+ SlackBuilds to maintain.
> Given my part-time job and my coursework, I am going to have a harder time
> maintaining it all.
>
> This is the last week in which I will maintain and update SlackBuilds.
>
> I will also switch my email address (on SlackBuilds) to
> isaa...@protonmail.com:
> https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
>
> I need to pay a small yearly subscription fee (to Gandi, the company) for
> the isaacyu1.com domain. However, the ProtonMail email service is free.
> Hence the email address change.
>
> My SlackBuilds are available at the following link:
> https://github.com/isaackwy/slackbuilds-15.0
>
> I plan on switching to Debian.
> Debian 12 (Bookworm) will be released in a few days, on June 10.
>
> - Isaac ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Including runit script with slackbuild?

[Jeremy Hansen]

On Tue, Apr 25, 2023, 4:56 AM Charadon via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> Hey all,
>
> I want to include runit scripts with my earlyoom slackbuild. What's the
> policy with it? Do I have to include an environment variable like
> RUNIT=YES so the user can choose if they want it, or can I just include it?
>
> - Charadon
>

If it's part of the program, I'd probably include it in the default
location. Pat does the same thing with systemd scripts.¹ He won't modify a
package to remove functionality that others might choose to later use
simply to save a few KB.

If it isn't included with the program by default, that is more up to you.
It may not be a bad idea to include it in the doc directory with a note in
the README that it's available if someone wants to incorporate it, or using
Chris's idea of keeping scripts in a separate repo.

Jeremy

¹
https://www.linuxquestions.org/questions/slackware-14/systemd-creeping-into-slackware-4175614385/#post5762104
___
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] Starting a daemon in rc

[Jeremy Hansen]

On Fri, Mar 10, 2023, 9:11 AM  wrote:

> On 2023-03-10 10:06, Ruben Schuller wrote:
> > Hi!
> >
> > 2023-03-10 phala...@komputermatrix.com:
> >
> >> I have slackbuild for tailscale that includes a daemon. The daemon
> >> should ideally be started by the init system. But it requires an
> >> internet connection, and in the case of using wifi, starting this
> >> daemon from rc.local halts the init -- *I think* because it's
> >> searching for a connection before wifi is connected.
> >>
> >> Any suggestions for starting a daemon like this?
> >
> > You could try the "daemon" package for this, it's shipped with
> > Slackware
> > and works pretty well! Here's how I do it for my dendrite SlackBuild
> > (not on SBo yet):
> >
> > 8<---
> > #!/bin/sh
> >
> > if [ -f /etc/default/dendrite ]; then
> >   . /etc/default/dendrite
> > fi
> >
> > dendrite_start() {
> >   if [ -x /usr/bin/dendrite-monolith-server ]; then
> >   daemon -n dendrite -u dendrite -- dendrite-monolith-server-tls-key
> > $TLSKEY -tls-cert $TLSCERT -config /etc/dendrite/dendrite.yaml
> >   fi
> > }
> >
> > dendrite_stop() {
> >   daemon -n dendrite -u dendrite --stop
> > }
> >
> > dendrite_restart() {
> >   dendrite_stop
> >   sleep 1
> >   dendrite_start
> > }
> >
> > case "$1" in
> > 'start')
> >   dendrite_start
> >   ;;
> > 'stop')
> >   dendrite_stop
> >   ;;
> > 'restart')
> >   dendrite_restart
> >   ;;
> > *)
> >   echo "usage $0 start|stop|restart"
> > esac
> > 8<---
> >
> > I'm not sure how to handle the waiting for the network. I suppose you
> > could add something which checks if network manager is connected, but
> > be aware that there are people (myself included) who use the classic
> > Slackware network scripts for this and it wouldn't work. Maybe you
> > could add something which pings the tailscale servers, you are going
> > to connect to them anyway.
> >
> > Cheers
> > Ruben
> > ___
> > 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/
>
> Thanks Ruben, I appreciate the idea. Doesn't this require the user to
> issue a command still?
>
> -AP
>

Personally, I'd just make a note of it in the README.

For people using Slackware's networking scripts, you could just add a
simple command to rc.local.

if [ -x /etc/rc.d/rc.tailscale ]; then
  /etc/rc.d/rc.tailscale start
fi

For people using NetworkManager, they could add a script (maybe
00-tailscale.sh) to /etc/NetworkManager/dispatcher.d/ containing something
like:

if [ "$2" = "up" ]; then
  if [ -x /etc/rc.d/rc.tailscale ]; then
/etc/rc.d/rc.tailscale start
  fi
fi

I don't use NetworkManager, but I believe that is the correct format.

Jeremy
___
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] tailscale sbo

[Jeremy Hansen]

It's up to you on if you want to become a maintainer. It's open to anyone.

Just make sure you follow the guidelines and then submit the tarball to the
upload form. The admins will check it over and make sure it meets the
guidelines and builds. If so, then your program will show up on the next
public update, which is typically every weekend.

https://slackbuilds.org/guidelines/

Jeremy

On Tue, Mar 7, 2023, 1:24 PM  wrote:

> I'm resending this to the group; never got a reply. If no interest, I'll
> leave it at that. Or if just overlooked, let me know.
>
> On 2023-02-26 17:01, phala...@komputermatrix.com wrote:
> > SBo devs, I have a build for the tailscale binary that I maintain for
> > myself. Happy to maintain for SBo if there's interest.
> >
> > The only issue I've encountered was automatically launching tailscaled
> > (daemon) from rc.local created an endless loop. I think because wifi
> > was not connected when tailscaled was started from rc.local, it
> > couldn't establish a connection. I left it so the user would have to
> > start tailscaled from a terminal. If there's a more elegant solution
> > I'm open.
> >
> >
> > -A
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] .info file variable expansion

[Jeremy Hansen]

On Sat, Feb 25, 2023, 6:23 AM Petar Petrov  wrote:

> I do not intend to sound nagging, but why not implement such a feature
> in order to make maintainers' job easier?
>
> -petar
>

I can't speak on whether or not it's worth adjusting everything to support
variables in there, but if it's just a simple version bump and the version
is the only thing that needs to be changed in the url(s), you can use a
script to update the versions pretty easily.

I made my own script that will update all instances of the version number
in the .info and .SlackBuild, reset the build number, download the
source(s), calculate the md5 for those sources and update that field in the
.info, and check the copyright year in the SlackBuild.

https://github.com/bassmadrigal/scripts/blob/master/version-bump.sh

It doesn't work for every script, but should work for most. Most of the
time, it's a very quick way to update everything and not miss the little
things (like resetting the build number). Occasionally, I'll still need to
manually adjust the download link and calculate my own md5, but over the
years I've been using this, it makes updating most of my SlackBuilds
breezes. It's definitely made my job easier.

Jeremy
___
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] wmctrl Source 404

[Jeremy Hansen]

It seems the site hosting the source for desktop/wmctrl is down.

I found the same file (with the same MD5SUM) on fedora's servers. I'm not
sure if we should just update it to that or save the source elsewhere and
link to the new location.

I'll let better minds than mine make that decision.

https://src.fedoraproject.org/repo/pkgs/wmctrl/wmctrl-1.07.tar.gz/1fe3c7a2caa6071e071ba34f587e1555/wmctrl-1.07.tar.gz
https://slackbuilds.org/repository/15.0/desktop/wmctrl/

Jeremy
___
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] Previous version of Thunderbird

[Jeremy Hansen]

On Wed, Jan 25, 2023, 5:45 AM Luveh Keraph <1.41...@gmail.com> wrote:

> Thanks. The only one I can find there is version 91.5.1 though - which is
> a bit long in the tooth.
>

You gotta look under the patches/ folder.

The cumulative mirror syncs everything without deleting older packages. So
older versions will be found under the folders they're posted in, which in
this case will be the patches/ directory.

Jeremy
___
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 - 20230121.1

[Jeremy Hansen]

Shoot. I'm not sure how that got through my checks. The file is no longer
needed since Slackware'updated its python version.

I'll get an update pushed after work today.

Jeremy

On Sat, Jan 21, 2023, 5:07 AM Cristiano Urban  wrote:

> Hi,
> i tried to upgrade Kodi from v19.4 to v19.5 using sbotools, but it fails
> due to missing README.python.
>
> -- Installing: /tmp/SBo/package-kodi/usr/lib64/kodi/cmake/KodiConfig.cmake
> -- Installing:
> /tmp/SBo/package-kodi/usr/share/kodi/addons/skin.estuary/media/Textures.xbt
> -- Installing:
> /tmp/SBo/package-kodi/usr/share/kodi/addons/skin.estuary/media/curial.xbt
> -- Installing:
> /tmp/SBo/package-kodi/usr/share/kodi/addons/skin.estuary/media/flat.xbt
> -- Installing:
> /tmp/SBo/package-kodi/usr/share/kodi/addons/skin.estouchy/media/Textures.xbt
> -- Installing: /tmp/SBo/package-kodi/usr/bin/JsonSchemaBuilder
> cat: /usr/sbo/repo/multimedia/kodi/README.python: File o directory non
> esistente
> Failure encountered while building kodi:
>   kodi.SlackBuild return non-zero
>
> Do you want to proceed? [n]
>
> Cheers,
> Cristiano.
>
>
> Il 21 gen 2023 04:50, Willy Sudiarto Raharjo  ha
> scritto:
>
> Hi all
>
> i know some updates are still in pending, but here are what's ready for
> this week public update
>
>
> Sat Jan 21 03:22:56 UTC 2023
> academic/OpenVSP: Moved from graphics. Updated for version 3.31.1.
> academic/fet: Fix DOWNLOAD.
> academic/gcompris-qt: Updated for version 3.0.
> academic/zotero: Updated for version 6.0.20.
> accessibility/magnus: Fix icon symlink.
> audio/audacity: Updated for version 3.2.3.
> audio/cubeb: Updated for version 0.2.1566.
> audio/qpwgraph: Updated for version 0.3.9.
> audio/wildmidi: Updated for version 0.4.5.
> desktop/anki: Remove Markdown from REQUIRES.
> desktop/anki: Updated for version 2.1.56.
> desktop/xpra: Add missing patch (derp).
> development/aflplusplus: Fix md5sum.
> development/asl: Updated for version 142_bld235.
> development/bpython: Updated for version 0.24.
> development/codespell: Updated for version 2.2.1.
> development/dbeaver-ce: Updated for version 22.3.2.
> development/hugo: Updated for version 0.110.0.
> development/jupyter-ipykernel: Update for 6.20.2
> development/jupyter-nbconvert: Update for 7.2.8
> development/jupyter-nbformat: Update for 5.7.3
> development/jupyter_client: Update for 7.4.9
> development/jupyter_events: Update for 0.6.3
> development/jupyter_server: Update for 2.1.0
> development/kodespel: Added (spell-checker for source code)
> development/leiningen: Remove trailing newline for sbolint.
> development/mysql-workbench: Updated for version 8.0.32.
> development/postman: Updated for version 10.7.0
> development/txr: Updated for version 284.
> development/universal-ctags: Updated for version p6.0.20230115.0
> development/z88dk: Clean up doc dir.
> games/clksignal-roms: Updated for version 20230114.
> games/clksignal: Updated for version 20221125.
> games/doomretro: Updated for version 4.7.2.
> games/eduke32: Updated for version 20221225_10166_122aee012.
> games/mesen-x: Updated for version 0.9.9.3358.
> games/supertuxkart: Updated for version 1.4.
> games/wolf4sdl: Updated for version 2.0+20210408_f31f41a.
> games/xemu: Updated for version 0.7.79.
> games/xonotic: Fix swapped sdl-glx binaries.
> games/xu4: Fix md5sum.
> gis/google-earth: Updated for version 7.3.6.9345.
> graphics/OpenVSP: Moved to Academic.
> graphics/converseen: Updated for version 0.9.10.1.
> graphics/paraview: Fix MD5SUM_x86_64
> graphics/teighafileconverter: Strip bins/libs, rm bad icon.
> graphics/xmedcon: Fix slack-desc for sbolint.
> libraries/cpp-httplib: Updated for version 0.11.4.
> libraries/fast_float: Updated for version 3.8.1.
> libraries/flatbuffers: Updated for version 23.1.4.
> libraries/fox-toolkit-devel: Fix download link.
> libraries/fox-toolkit: Fix download link.
> libraries/imgui: Updated for version 1.89.2.
> libraries/libmediainfo: Updated for version 22.12.
> libraries/libnsgif: Updated for version 0.2.1+20220113_105a920.
> libraries/librelp: Updated for version 1.11.0.
> libraries/libzen: Updated for version 0.4.40.
> libraries/mysql-connector-c++: Updated for version 8.0.32.
> libraries/tblis: Fix .info for sbolint.
> libraries/xbyak: Updated for version 6.68.
> libraries/zycore-c: Updated for version 1.4.1.
> multimedia/kodi: Updated for version 19.5.
> multimedia/mediainfo: Updated for version 22.12.
> multimedia/strawberry: Updated for version 1.0.14.
> network/discord: Updated for version 0.0.24.
> network/element-desktop: Updated for version 1.11.18.
> network/firewalld: Updated for version 1.3.0.
> network/nextcloud-desktop: Updated for version 3.6.6.
> network/squirrelmail: misc fixes for website purposes only
> network/surf: Strip library.
> network/telegram-cli: Removed (abandoned).
> network/telegram: Updated for version 4.5.3.
> network/zoom-linux: Updated for version 5.13.5.431.
> office/fbpdf: Updated for version 20220624_6276360.
> office/fop: Updated for version 2.8.
> 

Re: [Slackbuilds-users] Kodi doesn't build anymore (fmt)

[Jeremy Hansen]

On Sun, Oct 16, 2022, 11:15 AM martin schmidt 
wrote:

> Hi,
>
> according to https://github.com/xbmc/xbmc/pull/21649/commits
> we need a patch for builds with libfmt 9.0.0
>
> I adapted the patch so it does work now with the Slackbuild for kodi 19.4
>
> Here it comes - enjoy :-)
>
> diff --git a/xbmc/utils/GLUtils.cpp b/xbmc/utils/GLUtils.cpp
> index 1ef804709f..df8921e2b0 100644
> --- a/xbmc/utils/GLUtils.cpp
> +++ b/xbmc/utils/GLUtils.cpp
>
> @@ -148,29 +149,29 @@ void _VerifyGLState(const char* szfile, const char*
> szfunction, int lineno)
>   void LogGraphicsInfo()
>   {
>   #if defined(HAS_GL) || defined(HAS_GLES)
> -  const GLubyte *s;
> +  const char* s;
>
> -  s = glGetString(GL_VENDOR);
> +  s = reinterpret_cast(glGetString(GL_VENDOR));
> if (s)
> -CLog::Log(LOGINFO, "GL_VENDOR = %s", s);
> +CLog::Log(LOGINFO, "GL_VENDOR = {}", s);
> else
>   CLog::Log(LOGINFO, "GL_VENDOR = NULL");
>
> -  s = glGetString(GL_RENDERER);
> +  s = reinterpret_cast(glGetString(GL_RENDERER));
> if (s)
> -CLog::Log(LOGINFO, "GL_RENDERER = %s", s);
> +CLog::Log(LOGINFO, "GL_RENDERER = {}", s);
> else
>   CLog::Log(LOGINFO, "GL_RENDERER = NULL");
>
> -  s = glGetString(GL_VERSION);
> +  s = reinterpret_cast(glGetString(GL_VERSION));
> if (s)
> -CLog::Log(LOGINFO, "GL_VERSION = %s", s);
> +CLog::Log(LOGINFO, "GL_VERSION = {}", s);
> else
>   CLog::Log(LOGINFO, "GL_VERSION = NULL");
>
> -  s = glGetString(GL_SHADING_LANGUAGE_VERSION);
> +  s = reinterpret_cast char*>(glGetString(GL_SHADING_LANGUAGE_VERSION));
> if (s)
> -CLog::Log(LOGINFO, "GL_SHADING_LANGUAGE_VERSION = %s", s);
> +CLog::Log(LOGINFO, "GL_SHADING_LANGUAGE_VERSION = {}", s);
> else
>   CLog::Log(LOGINFO, "GL_SHADING_LANGUAGE_VERSION = NULL");
>
> diff --git a/xbmc/windowing/X11/WinSystemX11.cpp
> b/xbmc/windowing/X11/WinSystemX11.cpp
> index 8a18288fd8..cdb2a1da2e 100644
> --- a/xbmc/windowing/X11/WinSystemX11.cpp
> +++ b/xbmc/windowing/X11/WinSystemX11.cpp
>
> @@ -1038,7 +1048,10 @@ bool CWinSystemX11::HasWindowManager()
>
> if(status == Success && items_read)
> {
> -CLog::Log(LOGDEBUG,"Window Manager Name: %s", data);
> +const char* s;
> +
> +s = reinterpret_cast(data);
> +CLog::Log(LOGDEBUG, "Window Manager Name: {}", s);
> }
> else
>   CLog::Log(LOGDEBUG,"Window Manager Name: ");
>


I'm the maintainer and already submitted a fix, I just screwed up and left
an extra command in the SlackBuild, so I'll be resubmitting later today.

Is there a reason you messaged the mailing list instead of me directly (or
at least cc'ing me in this message)? In general, you should always message
the maintainer as not all of them are subscribed to the mailing list.

Jeremy
___
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] Trimming my buildscripts - FREE!

[Jeremy Hansen]

On Sat, Aug 27, 2022, 5:48 PM KB_SBo  wrote:

> I hope to pass on the following to a good home.  Mostly JAVA, closed
> source and stuff I no longer use.
>
> SweetHome3D Java. By the time I model the remodel, I've lost
> interest in remodeling!
> TeamSpeak3  no one to talk to. It's all freaking Discord these days.
> closed source. Besides, mumble FTW!
> jin Java. Not updated in 11 yrs. functionality now exists in
> eboard (part of Slackware) and scid.
> smath-studioMono. closed source.
>
>
> I'll continue to maintain these with a low priority until someone else
> takes them.
>
> -kb
>

I'll take SweetHome3D, but I'm still finishing up a move and don't have an
easy way to submit an update for maintenance. If kb or an admin want to
submit an update for me with my info, I'll continue maintenance from that
point.

Name: Jeremy Hansen
Email: jebrhansen+...@gmail.com

Thanks for your efforts with these!
Jeremy
___
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] Letter in version number

[Jeremy Hansen]

On Mon, Aug 22, 2022, 3:13 PM Brandon Pribula  wrote:

> I guess I remembered wrong about the version numbers. Thanks for your
> replies everyone. Much appreciated.
>
> Also, I don't believe it's a beta version. Looking at the release history
> 2.2.7b was released after 2.2.7.
>
> https://github.com/Orc/discount/tags
>


Seems to be a maintenance release.


version 2.2.7b - Another maintenance release to fix a bug in the Makefile;
> I didn’t have the proper dependencies for the pandoc_headers tool, so if a
> parallel make was tried it would fall over complaining about missing
> objects when it tried to link everything together.
>

Jeremy

>
___
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] Deal with source that requires submodules

[Jeremy Hansen]

On Thu, Jul 28, 2022, 4:39 PM Christoph Willing 
wrote:

> On 29/7/22 04:11, Heinz Wiesinger wrote:
> > On Thursday, 28 July 2022 20:08:02 CEST Wen-Wei Kao wrote:
> >> Hello,
> >>
> >> Recently while writing SlackBuilds, there is a particular package
> (https://
> >> github.com/fcitx/libime) that requires a submodule pulled in before
> >> compiling, but the Github release tags' sources don't have it included.
> >> What are the recommended ways to deal with this? Should I mark both as
> >> assets in the .info file, and decompress them in appropriate places?
> TIA.
> >
> > There's a second source tarball :)
> >
> > https://download.fcitx-im.org/fcitx5/libime/libime-1.0.13_dict.tar.xz
> >
> > Notice the "_dict" at the end. That one shouldn't need any external
> additions.
> >
>
> Although there's an easy solution in this particular case, I would be
> interested in hearing of a more general solution for cases where there
> is no such additional tarball available.
>
> I maintain another SlackBuild which has exactly the same problem. My
> solution so far has been to locally checkout the commit which
> corresponds to the (incomplete) release tarball. Then I pull in the
> required submodules and generate a new (complete) tarball which I host
> at slackbuildsdirectlinks, from where can be used as a single download
> for the SlackBuild.
>
> While that's a workable solution, I would definitely be interested in
> alternatives.
>
> chris


In the few SlackBuilds I've had that used git submodules, I'll just view
the .gitmodules file and use some bash to extract the modules' repos and
see where the extracted source belongs. That .gitmodules file will let you
know if it is based on the master branch or a specific tag/version/commit.
If it's the master branch, then I'll go through and find the commit ID I
want to download and add it to the PRGNAM.info download section. If it's a
specific version, I'll sometimes use bash to generate my download links,
other times, I'll just manually do it (it depends on how many downloads
there end up being).

Sometimes you'll luck out and all the submodules belong in the same folder
as their own subfolder. In that case, you can simply extract all the
submodules to the same directory with a wildcard, otherwise you need to
manually add specific lines in the SlackBuild for each.

One of mine, redeclipse, has 38 submodules, so I actually created a
separate submodule file that the SlackBuild references to know what
tarballs to extract. Since the versions aren't used in the folder name when
properly placed, I don't worry about what the files are called and just use
a wildcard for the version.

Unfortunately, it seems I was dumb and just had all the generated
information done by a piped together command that I didn't save.
Apparently, I'm a glutton for punishment when it needs to be updated.

https://slackbuilds.org/repository/15.0/games/redeclipse/
https://slackbuilds.org/repository/14.2/games/glPortal/ (haven't had time
to get this to work on 15.0 yet)

In the case of the OP's situation, they could just add
https://github.com/kpu/kenlm/archive/bcd4af6/kenlm-bcd4af619a2fa45f5876d8855f7876cc09f663af.tar.gz
to the DOWNLOAD in the .info with its corresponding MD5SUM and then add
something like the following into the SlackBuild:

KENVER=${KENVER:-bcd4af619a2fa45f5876d8855f7876cc09f663af}

(extract main source)

rm -r src/libime/core/kenlm
tar xvf $CWD/kenlm-$KENVER.tar.gz
mv kenlm-$KENVER src/libime/core/kenlm

And then continue the build.

Jeremy
___
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 - 20220618.1

[Jeremy Hansen]

On Fri, Jun 17, 2022, 8:24 PM Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> This will be my last public update for this month as i will be on
> holiday next week.
>

It's well deserved just with what you do for SBo, let alone your personal
and professional life.

Enjoy your trip!

Jeremy
___
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 your support

[Jeremy Hansen]

On Sun, Apr 17, 2022, 9:06 PM Francois Gingras 
wrote:

> Are you seriously asking us to commit to your gitlab? Can you grab a few
> projects yourself and commit those on your own?
>
>
> On Sun, 17 Apr 2022 at 23:04, Frank Gingras  wrote:
>
>> Are you seriously asking us to commit to your gitlab? Can you do grab a
>> few projects yourself and commit those on your own?
>>
>> On Sun, 17 Apr 2022 at 13:54, Dimitris Zlatanidis 
>> wrote:
>>
>>> Greetings to all members,
>>>
>>> I would like to ask for your support.
>>> I'm giving a job interview (Python Developer) and my Gitlab repository,
>>> will play an important role, so whoever wants to add an asterisk in my
>>> Projects and especially in slpkg, colored, sun, dropbox-filemanager,
>>> sbo-templates etc., I would appreciate it a lot!
>>>
>>> Thank you very much,
>>> Dimitris
>>>
>>> --
>>> Dimitris Zlatanidis
>>> https://dslackw.gitlab.io/slpkg/
>>> https://gitlab.com/dslackw
>>>
>>
No, I think he's asking us to "star" or basically favorite his projects if
you've think they've been helpful to you.

Jeremy
___
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] Maintenance gummi

[Jeremy Hansen]

On Tue, Apr 12, 2022, 8:22 AM B. Watson  wrote:

>
>
> On Tue, 12 Apr 2022, Franzen via SlackBuilds-users wrote:
>
> > Hi,
> >
> > since Larry Hajali seems not be active anymore i'd like to take over
> > maintenance for https://slackbuilds.org/repository/15.0/office/gummi/
> > Any objections?
>
> Have you tried to contact Larry? His last activity was April 2021,
> which isn't *that* long ago...
>

I tried contacting him about a month ago to take over Kodi without a
response either.

Jeremy

>
___
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

[Jeremy Hansen]

On Sun, Apr 3, 2022, 5:44 PM Slackbuilds  wrote:

> On 4/3/22 11:59, B. Watson wrote:
> > How about you do this instead?
> >
> > if [ -z "$MAKEFLAGS" ]; then
> >NUMJOBS="${NUMJOBS:-1}"
> >export MAKEFLAGS="-j$NUMJOBS"
> > fi
> > make
> >
> > ...that way, your builds work the way you want: they respect NUMJOBS
> > if MAKEFLAGS isn't set... but they'll still work the way everyone else
> > wants: people who already use MAKEFLAGS will still get the expected
> > results.
>
> I'm still not convinced that globally setting MAKEFLAGS won't have
> unintended consequences. I keep seeing in the make docs that the
> toplevel make creates/sets MAKEFILE for sub-makes, but isn't clear in
> what happens if MAKEFILES is already set, unless upstream source adds
> that logic.
>
> Setting 'make -j$NUMJOBS' seems a safer path, and is what Pat does in
> Slackware source.
>

This had been discussed on LQ and it was found that make is smart enough to
talk with its own sub-makes to ensure no more than the max number of jobs
can take place (specifically post #23, which is mine).

https://www.linuxquestions.org/questions/slackware-14/multi-thread-builds-via-sbopkg-slackbuilds-4175684827/

The only time it doesn't happen is if a makefile is poorly made as
demonstrated by pan64. However, I've had a global MAKEFLAGS set with only
what essentially sets -j17 in there since 2017 and I've never seen build
issues from it.

So, while theoretical, global MAKEFLAGS can cause issues with a poorly made
MAKEFILE, it seems they are extremely uncommon (if they exist at all).

NOTE: This is not to say we shouldn't have NUMJOBS in SlackBuilds (I don't
really have a preference), but just to say that setting -jXX in a global
MAKEFLAGS is unlikely to cause any issues in practice.

Here's the content of my /etc/profile.d/make-exports.sh. I have it do the
number of CPUs the kernel sees + 1 (this will include total threads, at
least on AMD systems).

export MAKEFLAGS="-j$(expr $(nproc) + 1)"

Jeremy

>
___
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] Updated ftbfs list

[Jeremy Hansen]

On Sun, Mar 27, 2022, 2:13 PM B. Watson  wrote:

>
>
> On Sun, 27 Mar 2022, Jeremy Hansen wrote:
>
> >
> > Where do you go to find how Debian builds its packages? I know about the
> AUR
> > for Arch and Gentoo's gitweb.
>
> Search for the package name on https://www.debian.org/distrib/packages
>
> > When I was updating handbrake to the latest version to allow building on
> > 15.0, I was hoping to find the ability to use system versions¹, but I
> > couldn't find any patches. It seems they existed with Debian, but my
> > google-fu was lacking.
>
> When you find the package in the Debian search, click on the
> version you want (the version you're packaging for SBo, if it
> exists), and on the details page there's a "Download Source Package"
> section... the debian patches are found inside the file with a name
> like "whatever_1.2.3-1.debian.tar.xz"
>
> Sometimes it's a .tar.gz, sometimes it's a .diff.gz, sometimes there's
> extra components in the version number (dfsg shows up a lot), but you
> get the idea.
>
> The HandBrake patch I based mine on is in the
> handbrake_1.5.1+ds1-1.debian.tar.xz tarball, as
>
> debian/patches/0001-Remove-embedded-downloaded-copies-of-various-librari.patch
>
> Hope this helps. I probably should write it up in more detail and
> post it somewhere more permanent than this...
>

Thanks everyone! I now have new tools in my toolbox.

Jeremy

>
___
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] Updated ftbfs list

[Jeremy Hansen]

On Fri, Mar 25, 2022, 1:19 AM B. Watson  wrote:

>
>
> On Thu, 24 Mar 2022, Ozan Türkyılmaz wrote:
>
> > News on HandBrake:
> > First of all, it seems HandBrake does not support 32bit compile anymore
> > [1]. However, someone did get it compile it as 32bit [2] with disabling
> > x265. I know x265 itself builds actually, if we can find a way to force
> > it using the system x265 and we will be fine.
>
> That's actually what I did. Debian's got a patch for HandBrake that
> makes it use system libraries for everything it bundles... I adapted
> that patch, made it only use the system x265.
>
> It might be better to use the whole patch, and make HandBrake
> depend on only system libraries, but that would be something for
> the maintainer to try, not me (I just made it build with the minimum
> possible change).
>

Where do you go to find how Debian builds its packages? I know about the
AUR for Arch and Gentoo's gitweb.

When I was updating handbrake to the latest version to allow building on
15.0, I was hoping to find the ability to use system versions¹, but I
couldn't find any patches. It seems they existed with Debian, but my
google-fu was lacking.

Jeremy

¹
https://www.linuxquestions.org/questions/slackware-14/when-will-https-slackbuilds-org-have-15-0-in-their-repos-4175708745/page3.html#post6335052

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

Re: [Slackbuilds-users] Slackbuild with Two Executables

[Jeremy Hansen]

On Tue, Mar 22, 2022, 10:32 PM Brandon Pribula  wrote:

>
>
> On Tue, Mar 22, 2022, 8:35 PM B. Watson,  wrote:
>
>>
>>
>> On Tue, 22 Mar 2022, Brandon Pribula wrote:
>>
>> > only options I can see are either splitting the package up into two
>> separate
>> > slackbuilds, or install both.
>>
>> > Which of those two options are preferable or is there another option?
>>
>> Other options:
>>
>> - Install both scripts in $PKG/usr/bin, call one "appname" and the other
>>"appname-posix", and explain the situation in your README.
>>
>> - Use an environment variable (APPNAME_POSIX=yes|no) to let the user
>>choose which of the scripts to include in the package.
>>
>> One thing that's *not* an option: Don't have one SlackBuild script
>> that creates two separate packages (in other words, don't ever
>> call makepkg twice).
>>
>> If you do decide to make separate packages for 'appname' and
>> 'appname-posix', it'll have to be two separate SlackBuilds.
>> Personally, I'd choose one of the other options (one SlackBuild, one
>> package, either include both scripts or use the env to select one).
>> ___
>> 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/
>
>
> Thanks for the reply, B. Watson :)
>
> For the option of using an ENV variable, can it also be used to install
> both scripts as long as makepkg isn't called twice?
>
> Then just use appname for the package name no matter which option is
> chosen. In the README I could specify which executable to call depending on
> the options chosen.
>

If you'd like to see an example of enabling different options, you could
look at my mediainfo script. It defaults to build only the CLI, but you can
enable the GUI with the CLI or do only the GUI.

It'd be a little different since you're only dealing with scripts instead
of compiling programs.

https://slackbuilds.org/repository/15.0/multimedia/mediainfo/

Jeremy

>
___
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 for ngspice.SlackBuild for Slackware 15.0

[Jeremy Hansen]

You would fork the repo from GitHub or GitLab and create a new branch with
your changes. Then submit a Pull Request (GitHub) or Merge Request (GitLab)
with those changes back to the upstream repo.

https://github.com/SlackBuildsOrg/slackbuilds
https://gitlab.com/SlackBuilds.org/slackbuilds/

Jeremy

On Tue, Mar 22, 2022, 9:50 AM Ananda Murthy  wrote:

> How to do PR and MR?
>
> On Tue, Mar 22, 2022 at 8:28 PM Willy Sudiarto Raharjo <
> will...@slackbuilds.org> wrote:
>
>> > Sorry. Can you please elaborate what is PR or MR?
>>
>> pull request / merge request
>> if you want to send to the list, please do it in .patch format, not diffs
>>
>>
>> --
>> Willy Sudiarto Raharjo
>> ___
>> 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/
>>
>>
>
> --
>
>
> Close Windows ! Open source !!
> Free software from proprietary mafia !!!
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Creating First Slackbuilds and Github

[Jeremy Hansen]

On Sun, Mar 20, 2022, 4:58 PM Ruben Schuller  wrote:

> Hi,
>
> 2022-03-20 "B. Watson" :
>
> > On Sat, 19 Mar 2022, Ruben Schuller wrote:
> > >
> > > ZIPVER="1369d247e3d2bc697892795dea8cc1713344749f"
> > >
> > > for the version I'd either go with the date like 220319 if there
> > > aren't multiple commits on that date, or with the short-hash of
> > > git:
> >
> > Recommendations... in fact I'm begging you: if you're going to use
> > a git commit, *please* include the date in YYMMDD format in your
> > VERSION number. Example:
> >
> > VERSION="20220319+1369d24"
> >
> > Notice the 4-digit year comes first... the point of doing it this way
> > is that a user can easily tell which version is newer, when looking
> > at multiple packages. If you use only the git commit hash, those are
> > effectively random, there's no sense of which is newest.
> >
> > The SlackBuild can split up the VERSION variable as needed.
> >
> > Also, while I'm thinking about it: VERSION *must* be a constant that
> > can be overridden by the environment. Example:
> >
> > VERSION=${VERSION:-3.4.1}
>
> Very good point, including the date never hurts.
>
> > *Please* don't try to get clever and do stuff like:
> >
> > COMMIT=1369d247e3d2bc697892795dea8cc1713344749f
> > VERSION="$( echo $COMMIT | head -c7 )"
>
> Note, for completeness, that the git short hash might be longer than
> seven characters because of collisions. The git command figures that
> out. Don't just shorten it :)
>

On SBo, it won't matter if there's collisions. It's simply a reference to a
version that exists on SBo. If there's collisions within the upstream repo,
it won't affect the version we have on SBo.

Jeremy

>
___
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] peer-to-peer: aMule / mldonkey , gnutella, soulseek, transmission-qt, etc.?

[Jeremy Hansen]

On Thu, Mar 17, 2022, 9:38 PM David Chmelik  wrote:

>  I hope to see transmission-qt back.  The transmission-gtk doesn't
> seem to be able to change to a 'night mode' (bright text on black.)


Have you looked into transgui at all? I maintain it on SBo and they show a
dark theme on their README (likely tied to the system theme, which I don't
currently use a dark one, so I can't verify it works).

https://github.com/transmission-remote-gui/transgui
https://slackbuilds.org/repository/15.0/network/transgui/

Note: transgui is just a frontend for transmission's webclient. I use it
with transmission-daemon, but it should work fine with transmission-gtk as
long as you enable web control.

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

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

[Jeremy Hansen]

On Tue, Mar 15, 2022, 1:41 PM Logan Rathbone  wrote:

> On Tue, Mar 15, 2022 at 03:02:43PM EDT, Jeremy Hansen wrote:
> > On Tue, Mar 15, 2022, 12:55 PM Logan Rathbone 
> wrote:
> >
> > > On Mon, Mar 14, 2022 at 01:26:33AM EDT, David Chmelik wrote:
> > > [reversed top-posting, for readability]
> > > > On 3/13/22 8:18 PM, Duncan Roe wrote:
> > >
> > > > Eric (alienBOB) is on Slackware team, so one can trust his newer
> > > > versions with fixes.
> > >
> > > These are very high-quality packages as well, but they are de-googled.
> > > This may be against the grain around these parts, but for me, half the
> > > reason I *do* use Chrome is to get the Google Account integration.
> > >
> >
> > He has both regular chromium and chromium-ungoogled packages.
> >
> > http://www.slackware.com/~alien/slackbuilds/chromium/
> > http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/
>
> Hm, yes, I have seen this. I think I'll take a second look, but I'm
> thinking ("googled") Chromium and Google Chrome still would have
> different levels of Google integration (Googlization, if you will).
>
> For instance, last time I checked, Google Account integration was not
> working with Alien's (googled) Chromium packages; as I understand, this
> was due to Google's muzzling of unofficial Chromium packages as of 15
> March 2021; see
> https://alien.slackbook.org/blog/google-muzzles-all-chromium-browsers-on-15-march-2021/


Yeah, I have no idea the difference between them, I just saw both on his
repo and that he has 15.0 packages for both.

I imagine there's some difference between them if he's packaging both.

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

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

[Jeremy Hansen]

On Tue, Mar 15, 2022, 12:55 PM Logan Rathbone  wrote:

> On Mon, Mar 14, 2022 at 01:26:33AM EDT, David Chmelik wrote:
> [reversed top-posting, for readability]
> > On 3/13/22 8:18 PM, Duncan Roe wrote:
>
> > Eric (alienBOB) is on Slackware team, so one can trust his newer
> > versions with fixes.
>
> These are very high-quality packages as well, but they are de-googled.
> This may be against the grain around these parts, but for me, half the
> reason I *do* use Chrome is to get the Google Account integration.
>

He has both regular chromium and chromium-ungoogled packages.

http://www.slackware.com/~alien/slackbuilds/chromium/
http://www.slackware.com/~alien/slackbuilds/chromium-ungoogled/

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

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

[Jeremy Hansen]

On Mon, Mar 14, 2022 at 2:55 PM Duncan Roe 
wrote:

> On Mon, Mar 14, 2022 at 08:16:29AM -0600, Jeremy Hansen wrote:
> > On Mon, Mar 14, 2022, 3:24 AM David Chmelik  wrote:
> >
> > > Working on mathics.SlackBuild, I'm thinking does maybe maybe
> > > python-template.SlackBuild template need update?  Seems /any/all/
> > > (almost 10+) Python programs I try anymore use pip, not setuptools
> > > (haven't seen it for years) so shouldn't both be in template(s)?  But,
> > > maybe pip isn't going to work right without pip2tgz...
> > >
> > > On 3/14/22 12:54 AM, David Chmelik wrote:
> > > > On 3/14/22 12:46 AM, Duncan Roe wrote:
> > > >> @David Chmelik: in your earlier email, you talked about mathics. I
> > > >> built Mathics
> > > >> 1.0. Now you are talking about Mathics-omnibus. As you say,
> > > >> Mathics-omnibus
> > > >> doesn't offer a source distro. pip2tgz can't build it. [...]
> > > > Mathics 1 SlackBuild existed since Slackware 14.2 and doesn't need
> > > > changes.
> > > > Mathics-omnibus is newer stable Mathics full installation, which
> > > > is what I want to update SlackBuild for, so of course I'm talking
> > > > about it: many SlackBuilds will be being updated, sometimes with
> major
> > > > changes.
> > > I mean Slackware 14.2 is barely older than Mathics 1, from 2 October
> > > 2016, w/newer commits (I didn't use) since that October 4th, until late
> > > 2020's 1.1.  Mathics 4 (though renamed still Mathics3) was mid-2021, so
> > > if anyone might prefer basic package, that would've been what to try.
> I
> > > might make basic and/or full installation Mathics build scripts.  I
> want
> > > full but depends what others may want.
> > >  Incidentally 'pip3tgz Mathics3-4.0.0.tar.gz' builds (but crashes,
> > > so I'll be talking to upstream) but I avoid unusual build methods, like
> > > seems poor style when discord.SlackBuild gets .deb instead of .tar.gz
> > > (though pip2tgz may be better than plain pip because can/does specify
> > > .tar.gz.)  It may (or not--comments/suggestions/policies?) be best see
> > > if pip can be made to install to /tmp/SBo/package-mathics then do
> normal
> > > makepkg. W/pip2tgz would I put .tar.gz in mathics.info then use
> pip2tgz
> > > on it?
> > >
> >
> > I'm not sure why discord came up when talking about python and pip2tgz,
> but
> > I chose to use the deb because it places the files in the normal package
> > locations.
> >
> > The tar.gz would need to be placed in /opt/ and it would need extra lines
> > of code to get everything set up.
> >
> > Jeremy
>
> No, the created tar.gz is a Slackware package, same as you get from a
> SlackBuild
> normally.
>
> I think all the *2tgz packages work that way.
>
>
The discord tar.gz you download from their site is a self-contained version
of discord. It does not contain the normal folder structure found in a
package. It is simply in a Discord/ folder, which everything extracts into
that Discord/ folder. You can run it from that directory. If I used this, I
would need to add extra lines into the script to place files properly (like
a link in /usr/bin and placing the discord.desktop and icon in the proper
locations for them to show up in a menu -- not hard, but entirely
unnecessary when the .deb package already does it). The .deb is already
prepped and ready to go. You just extract it and you're ready to make a
Slackware package minus the Slackware specific things like a slack-desc,
doinst.sh, and making the /usr/doc directory..

However, my initial question of why was discord brought up within a pip2tgz
topic wasn't answered... Discord is not python and won't be found via pip.
There is discord.py that can be found via pip, but it is an API wrapper,
not the official discord chat app. So, pip2tgz can't do anything with
discord, so what was the point in mentioning discord?

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

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

[Jeremy Hansen]

On Mon, Mar 14, 2022, 3:24 AM David Chmelik  wrote:

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

I'm not sure why discord came up when talking about python and pip2tgz, but
I chose to use the deb because it places the files in the normal package
locations.

The tar.gz would need to be placed in /opt/ and it would need extra lines
of code to get everything set up.

Jeremy
___
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 ssvnc for 15.0 in slackbuilds

[Jeremy Hansen]

On Mon, Mar 14, 2022, 12:53 AM B Watson  wrote:

If it'd help, I could make a list of builds that got removed, maybe
> some of you mailing list folk could pick them up and maintain them.
>

I'd definitely be interested in looking through it.

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

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

[Jeremy Hansen]

On Sun, Mar 13, 2022, 9:59 AM Rich Shepard  wrote:

> I could not find chromium in an SBo repository and it's not part of the
> core
> distribution. Is it no longer available for use in 15.0?
>

Chromium was rarely updated, so it was removed from SBo in 2018.

https://git.slackbuilds.org/slackbuilds/log/network/chromium?h=master

If you want to continue to use chromium, Alien Bob keeps chromium packages
and his SlackBuild available on his repo.

http://www.slackware.com/~alien/slackbuilds/chromium/

If you are fine with regular chrome, as already mentioned, Pat makes his
SlackBuild for it available in extra/, or ruario has his excellent
latest-chrome SlackBuild.

https://gist.github.com/ruario/9672759

Jeremy
___
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 ssvnc for 15.0 in slackbuilds

[Jeremy Hansen]

On Sun, Mar 13, 2022, 3:53 PM Luveh Keraph <1.41...@gmail.com> wrote:

> I notice that ssvnc is not present for 15.0, despite the fact that it was
> there for 14.2. Any idea why it was not added to 15.0?
>

It failed to build on 15.0, so it was removed so the 15.0 repo didn't have
failed builds.

https://git.slackbuilds.org/slackbuilds/commit/network/ssvnc?id=cfe9b2973baba1fabf6196e71a393968c3af34ba

Jeremy
___
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] Kodi Fix for CEC

[Jeremy Hansen]

Matteo,

Thanks for catching the downloads that occur as well as the fact that I
forgot to remove the build directory (or if you didn't catch them, for at
least getting the fix submitted). I did check if crossguid was installed if
it would use the system version, and it seems it will not.

USUARIONUEVO found another thing I missed. I used LIBCEC as the variable in
the cmake and CEC as the variable in the pkg-config detection.

Can you please fix it? Attached is a patch, but it just needs the cmake
line to have the variable changed from LIBCEC to CEC.

I'm going to CC the SBo mailing list, since you're probably in bed right
now.

Thanks,
Jeremy (aka bassmadrigal)
From 98875e01ab82b82c8c18ebf8eeb6c99bcc83bddf Mon Sep 17 00:00:00 2001
From: Jeremy Hansen 
Date: Tue, 8 Mar 2022 19:27:47 -0700
Subject: [PATCH] multimedia/kodi: Fix CEC variable

---
 multimedia/kodi/kodi.SlackBuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/multimedia/kodi/kodi.SlackBuild b/multimedia/kodi/kodi.SlackBuild
index 093682504e..0d89e50cb9 100644
--- a/multimedia/kodi/kodi.SlackBuild
+++ b/multimedia/kodi/kodi.SlackBuild
@@ -106,7 +106,7 @@ cd $TMP/$PRGNAM-build
 -DENABLE_INTERNAL_UDFREAD=ON \
 -DENABLE_AIRTUNES=$AIRPLAY \
 -DENABLE_AVAHI=$AVAHI \
--DENABLE_CEC=$LIBCEC \
+-DENABLE_CEC=$CEC \
 -DENABLE_DAV1D=$DAV1D \
 -DENABLE_EVENTCLIENTS=$CWIID \
 -DENABLE_LIRCCLIENT=$LIRC \
-- 
2.14.5

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

Re: [Slackbuilds-users] Pitivi not running

[Jeremy Hansen]

On Sat, Mar 5, 2022 at 2:59 PM B Watson  wrote:

> On 3/5/22, B Watson  wrote:
> >
> > Thanks for that, it'll help a lot.
> >
>
> I spake too soone: there's already python3- versions of kiwisolver
> and cycler.
>
>
It should already be good. If you follow the dependencies of pitivi, you
get python3 versions of the right dependencies. Here's the output from sqg

python3-tornado
python3-kiwisolver
python3-cycler
pytz
python3-dateutil
numpy3
python3-matplotlib
libpeas
gst-python
gst-plugins-bad
gst-editing-services
gsound
gcab
appstream-glib
pitivi

I'm not sure why Luis installed the python2 versions, unless they didn't
pay close enough attention to the dependencies and just
installed "matplotlib" instead of "python3-matplotlib".

Jeremy
___
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] Pitivi not running

[Jeremy Hansen]

On Sat, Mar 5, 2022, 11:00 AM Luiz Carlos Ramos via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> Hello,
>
> today I tried to upgrade Pitivi version to the last one, and it turns
> out that the final binary (in fact, a Python3 script) didn't run,
> showing signs of a missing matplotlib.
>
> Digging a little bit, one found that the problem was on two
> dependencies, kiwisolver and cycler, which didn't have the Python3
> version built.
>
> I could solve it including in these packages a command to build Python3
> bits along the Python2 ones, like that:
>
>  python setup.py install --root $PKG
> [+]  python3 setup.py install --root $PKG
>
> and rebuilding kiwisource and cycler.
>
> Conversely to what the error message points, it seems there is no need
> to install the whole matplotlib. By the way, the current matplotlib SBo
> lacks Python3 support.
>

I'm the maintainer of pitivi. It relies on python3-matplotlib, not the
regular matplotlib on SBo. It should build properly with the dependencies
listed on REQUIRES line in the pitivi.info. I tested it on a clean VM using
sqg and sbopkg before I submitted it. If I missed something, let me know.

Jeremy
___
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] Version Bump for HandBrake (1.5.1) Submitted to GitHub

[Jeremy Hansen]

Klaatu,

I took the liberty today to update HandBrake to v1.5.1 so it can compile on
15.0 and I added support for an optional dependency of onevpl (Intel's
video processing library). onevpl did not already exist on SBo, so I
created a SlackBuild for it.

I submitted a PR on SBo's github if you'd like to review it.

https://github.com/bassmadrigal/SBo-forked/pull/new/HandBrake

I did not do this with the intention of taking over maintenance unless you
no longer want to maintain it.

Jeremy (aka bassmadrigal)
___
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] Any help?

[Jeremy Hansen]

Johannes,

No, I was referencing the "plenty of updates and new submissions to add
once submissions are open again" portion of Barry's message.

However, if there is a list of SlackBuilds that no one is maintaining that
aren't working, I'd be happy to review them and potentially step up as
maintainer. Until that becomes available, I'll just maintain my own.

Jeremy

On Wed, Mar 2, 2022 at 5:22 PM Johannes Georgi 
wrote:

> Hi Barry,
> I suspect Jeremy misundestood you, and what you want is a list of SBo
> SlackBuilds that aren't yet updated AND weren't yet tested to work on
> Slackware 15.0.
> I think such a list exists only implicitly, as, to my knowledge, no
> infrastructure/workflow exists to maintain it. It implicitly exists
> inform of the repo itself, insofar as SlackBuilds tested negative and
> with no one willing to change that are dropped from the repo. If someone
> is willing to change it (maintain maintainership, so to say), they'll
> get updated eventually.
> So it's not much use testing if a package works if one is not willing to
> maintain it, because the maintainer will do that anyway, and if they
> don't, it will get dropped.
> I hope I got that right, cya, j12i
>
> On 28.02.22 00:07, Barry J. Grundy wrote:
> > I have tested all my SlackBuilds as the currently sit in the master
> > repo.  They all compile without error.  I have plenty of updates and new
> > submissions to add once submissions are open again.
> >
> > In the meantime I'm wondering if there is a list of SlackBuilds we can
> > test or that need some attention. Any other way the larger community can
> > help with the workload?
> >
> > Thanks for all the hard work,
> > Barry
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Any help?

[Jeremy Hansen]

On Sun, Feb 27, 2022, 4:07 PM Barry J. Grundy  wrote:

> I have tested all my SlackBuilds as the currently sit in the master
> repo.  They all compile without error.  I have plenty of updates and new
> submissions to add once submissions are open again.
>

If you're interested in getting those updates in now and are familiar with
git, you can either email patches to this mailing list or submit a
Pull/Merge Request through GitHub/GitLab.

https://github.com/SlackBuildsOrg/slackbuilds
https://gitlab.com/SlackBuilds.org/slackbuilds

>From my understanding, they're only taking new submissions if they're new
dependencies for your updates.

Jeremy
___
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] Fwd: Picard maintainer updated without permission

[Jeremy Hansen]

Thanks for the info Matteo!

Wow... Pouria and I had a discussion about discord at the beginning of
November with no indication that I'm stepping down from any of my
SlackBuilds. Then he flat out lies saying he got in contact with me and
that I'm no longer using Slackware (I'm very much continuing to use
Slackware and there were no contact attempts after discord). That's a
little messed up on his part.

I'll send in a new PR.

Jeremy

On Fri, Feb 25, 2022 at 1:54 AM Matteo Bernardini <
matteo.bernard...@gmail.com> wrote:

> I think there has been a bit of confusion
>
> https://github.com/SlackBuildsOrg/slackbuilds/pull/1057
>
> Jeremy, it's ok if you correct this.
>
> Matteo
>
> Il giorno ven 25 feb 2022 alle ore 09:20 Jeremy Hansen
>  ha scritto:
> >
> > Pouria,
> >
> > You took over maintainership of picard without notifying or requesting
> it from me. Was this an oversight? I was getting ready to submit my update
> for the 15.0 repo today only to find out you had replaced me as maintainer
> without ever notifying me.
> >
> > I did not intend to give up maintenance of this SlackBuild and would
> prefer to keep it myself.
> >
> > @SBo admins, are you ok with me submitting a PR correcting the info?
> Pouria also neglected to keep the picard-plugins SlackBuild up-to-date.
> >
> > Thanks
> > Jeremy aka bassmadrigal
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Fwd: Picard maintainer updated without permission

[Jeremy Hansen]

Pouria,

You took over maintainership of picard without notifying or requesting it
from me. Was this an oversight? I was getting ready to submit my update for
the 15.0 repo today only to find out you had replaced me as maintainer
without ever notifying me.

I did not intend to give up maintenance of this SlackBuild and would prefer
to keep it myself.

@SBo admins, are you ok with me submitting a PR correcting the info? Pouria
also neglected to keep the picard-plugins SlackBuild up-to-date.

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

Re: [Slackbuilds-users] Slackbuild cloning source from git

[Jeremy Hansen]

Ugh, the Gmail app is making it impossible to reply inline, so it's going
above.

Programs that use subprojects will still need to be manually downloaded and
moved into place. You can see an example of this (with a lot of subprojects
-- 38 if I counted correctly) with my redeclipse SlackBuild.

Due to the massive number of submodules, I listed them all in a separate
file, which helps with both maintenance and building of the package.

https://slackbuilds.org/repository/14.2/games/redeclipse/

My glPortal SlackBuild has far fewer submodules with only 4, so I handle
those individually within the SlackBuild

https://slackbuilds.org/slackbuilds/14.2/games/glPortal/

Hopefully these examples will help.

Jeremy

On Fri, Feb 11, 2022, 11:40 AM Ralph Spitzner  wrote:

> Hi all,
> would a Slackbuild cloning the source of the project from github stand any
> chance of
> being accepted (couldn't find any info on this)
> The project in turn uses 'subprojects' which get cloned from git
> recursively.
> There's no tar.gz containing everything and installing the subprojects
> wouldn't make any sense
> as they are only needed to build this and don't install anything
> themselves
>
>
> regards
>  -rasp
> --
> "ich brauche keine Verschluesselung, mich versteht eh keiner"  -Icke
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Howto for slackware tgz

[Jeremy Hansen]

On Mon, Jan 10, 2022, 7:19 PM Beco via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> Hello there, Slack users,
>
> I just joined.
> I hope you are all doing well, and that this list is still active.
>
> I am migrating from Debian systemD. I tried Devuan as well. It is
> difficult to change distros when you have many computers/notebooks and
> you want them to share the same distro.
>
> Some of my small scripts and programs need to adapt. It is not a big
> deal, but I want them to keep organized. I think the best way is to
> reorganize them within the parameters and directory structure of a
> slackware package.
>
>
> Please, what is a good updated detailed source of explanation about
> the format and internals of a tgz tar-ball (package)?
>
>
> Thanks and still in time, happy 2022.
>


Welcome! They're pretty simple. The majority of it is simply extracted to
the root filesystem and is stored with the exact layout it is expected to
have on the root filesystem.

Where it differs is the install/ directory. This houses the files for the
Slackware package manager. The two most common are slack-desc and
doinst.sh. The former is used as the information displayed by Slackware's
package manager during installation and maintenance. The latter is an
optional file that is run immediately after the package is installed. You
can see SBo's templates for both at the below address.

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

Re: [Slackbuilds-users] sbopkg -c note

[Jeremy Hansen]

On Thu, Oct 21, 2021, 6:33 PM Duncan Roe  wrote:

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

If you want this to stick, you'd need to add the export to your ~/.profile
or change the config file I mentioned earlier.

Exporting it will only save it for that instance of bash (and any bash
sessions spawned from this one) and won't stick to any other sessions
already running.

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

Re: [Slackbuilds-users] sbopkg -c note

[Jeremy Hansen]

On Thu, Oct 21, 2021, 3:45 AM Jude DaShiell  wrote:

> Note: repo version not obtainable by standard method, may be inaccurate.
> Can this be cleared by now or should it be cleared later by configuration?
> One thing I have noticed about slackware and maybe this applies to other
> linux distros is that the /tmp directory tree tends to be rather permanent
> unless cleaned out every so often.  I've had instances where the root user
> ran out of space on the system and this was with I think the standard 30gb
> root partition install space a while ago.
> I need to go through logs and clean some of those out too so disk quota
> situations don't happen again for a while.
>

I can't answer about your error, but while sbopkg doesn't clean up the
files in /tmp/ by default, you can change it by setting the following in
/etc/sbopkg/sbopkg.conf

CLEANUP=${CLEANUP:-NO}

to

CLEANUP=YES

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

Re: [Slackbuilds-users] git access

[Jeremy Hansen]

On Wed, Oct 13, 2021, 6:47 PM Duncan Roe  wrote:

> On Wed, Oct 13, 2021 at 09:21:25PM +0200, Ruben Schuller wrote:
> > Hi list!
> >
> > I'm pretty sure it was already discussed here or I missed some
> > documentation, but what is the process to get git access to SBo?
> > It just would be easier to push updates to my SlackBuilds somewhere
> > instead of uploading a tarball, as i have them already stored in a git
> > repository.
> >
> > Cheers
> > Ruben
>
> git clone git://git.slackbuilds.org/slackbuilds.git
>
> Cheers ... Duncan.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/



You can also use the SBo mirrors on GitHub and GitLab to submit pull/merge
requests.

https://github.com/SlackBuildsOrg/slackbuilds
https://gitlab.com/SlackBuilds.org/slackbuilds

That is generally how I submit my updates.

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

Re: [Slackbuilds-users] brace expansion

[Jeremy Hansen]

On Wed, Jun 16, 2021, 1:51 PM Spycrowsoft  wrote:

>
> Op 16-06-2021 om 21:09 schreef Eugen Wissner:
> > Pat changed /bin/sh to /bin/bash in all
> > rc-scripts, so they work with other shells.
>
> We should confirm this with Patrick Volderding, but if he's doing that,
> my take on the matters is: "Follow what the BDFL is doing".
>
> The fact that the SlackBuild contains a pointer to the right shell also
> makes sense to me.
>


Here's the changelog entry.

a/sysvinit-scripts-15.0-noarch-2.txz: Rebuilt. Use #!/bin/bash for these
scripts so that bashisms don't cause script issues if /bin/sh is some other
shell. Thanks to mumahendras3. rc.S: Use GazL's proposals for
detecting/mounting /proc and /sys.

I'd prefer to allow bashisms and just use a /bin/bash shebang with the
SlackBuilds.

Jeremy
___
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

[Jeremy Hansen]

On Sun, Apr 25, 2021, 3:24 AM Spycrowsoft  wrote:

> You can take it as I am not actively looking for more slackbuilds to
> maintain.
>
> But if you are not willing to do so, I will take up the work.
> Op 25-04-2021 om 00:02 schreef Jeremy Hansen:
>
> On Sat, Apr 24, 2021, 1:58 PM Dave Woodfall  wrote:
>
>> 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.
>>
>
> Looks like they sent that message directly to me.
>
> I am actively using it.
>>
>>
>>> I want to give others the option of taking over this slackbuild first,
>>> but if no one else takes over, I will do so.
>>
>>
>>> Spycrowsoft
>>
>>
> I'm adding them directly to the email.
>
> @Spycrowsoft, feel free to take over maintenance if you're still
> interested. Otherwise let me know and I'll take over.
>
> Jeremy
>
> Dave,

Since Spycrowsoft is not interested in maintaining it, I'll take clementine
and will submit the change once submissions reopen. If you want to just
change it to my info on your branch, that's fine too.

Name: Jeremy Hansen
Email: jebrhansen+...@gmail.com

Jeremy
___
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

[Jeremy Hansen]

On Sat, Apr 24, 2021, 1:58 PM Dave Woodfall  wrote:

> 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.
>

Looks like they sent that message directly to me.

I am actively using it.
>
>
>> I want to give others the option of taking over this slackbuild first,
>> but if no one else takes over, I will do so.
>
>
>> Spycrowsoft
>
>
I'm adding them directly to the email.

@Spycrowsoft, feel free to take over maintenance if you're still
interested. Otherwise let me know and I'll take over.

Jeremy
___
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

[Jeremy Hansen]

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
___
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 (Again!)

[Jeremy Hansen]

On Tue, Apr 20, 2021, 2:59 PM Barry J. Grundy  wrote:

> I know this has come up before and perhaps been answered and I've also
> read through the related threads on LQ, but I still have not seen a
> definitive answer (if there is one):
>
> Since python2 is EOL and -current/15 ships with python3, is it good
> practice now to build python packages with python3 by default?  If so,
> then what's the best way to handle the multiple versions?  This
> discussion was had on the list back in Feb of '19, but I don't see
> anything definitive.
>
> For example, I maintain dpkt.  The version in the -current (ponce's)
> repo works, but I have an update ready to go when submissions open
> again.  Right now dpkt builds for python2. Here's my question:
>
> My "ready to go" update switches to python3 by default and uses a
> "PYTHON2=yes" option to build python2 modules if the user wants. Would
> it be better to create python3-dpkt and leave the dpkt script at
> python2?  I see it both ways in the 14.2 repo.
>
> Another probably better example is distorm, which is a requirement for
> volatility (which is python2 only).  volatility3 is a separate re-write
> for python3 with different prerequisites (and I already have a
> slackbuild to submit for that when things open again).  So for
> volatility it makes sense to leave distorm as is.  I can submit a
> separate python3-distorm script when I submit volatility3.
>
> Perhaps with the submissions freeze it would be a good time to either
> separate the scripts or at least decide on a "best practice".  My
> apologies if I'm simply kicking a dead horse here.
>
> Thanks,
>
> Barry
>

In my opinion, I think SBo for 15.0 should default to python3 for any
packages and python2 should be something that can be optional (for those
packages that support both).

If there's a need to have separate python2 and python3 packages, the
python3 package should not need an identifier in front of it, where the
python2 package should ($PRGNAM for python3 and python2-$PRGNAM for
python2).

Jeremy
___
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] ptlib doesn't compile on -current any more

[Jeremy Hansen]

On Sun, Apr 4, 2021, 12:59 PM Sebastian Arcus  wrote:

> On 04/04/2021 19:21, Matteo Bernardini wrote:
> > strange, builds fine here: I just add this last patch after the other
> > ones already applied in the modified ptlib.SlackBuild of the
> > unofficial repository for current.
> > one of them is specific to port ptlib to openssl-1.1.x and from the
> > output you posted could it be that is not applied?
>
> Sorry - I was getting confused between willysr's and ponce's repos. I
> take it ponce's is the most up to date one? I re-downloaded the scripts
> from ponce's, added the patch you suggested and it all compiled fine
> now. Thank you again.
>

The repo from ponce is an unofficial repo just for -current, where Willy's
is for 14.2. Both are up-to-date, but designed for different versions of
Slackware.

SBo does not imply any support for -current, although, many scripts happen
to work without modification. The unofficial repo from ponce keeps any
modifications needed to ensure the scripts build properly and the resulting
packages run properly on -current.

Jeremy

>
___
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] Upgrading packages

[Jeremy Hansen]

On Sat, Feb 27, 2021, 7:42 AM Rich Shepard  wrote:

> Installed here is python3-PyQt5--5.13.2-x86_64-1_SBo. I don't see an
> upgrade
> to that package in the weekly list and wonder why sbopkg keeps suggesting I
> upgrade since 5.13.2 is installed and the version in the repo.
>
> Today I decided to let it run for the several hours it takes but am curious
> why sbopkg offers to upgrade to the same version. Was there a SlackBuild
> change I missed seeing?
>

It's because you have build 1 installed and build 2 is what's on the repo
now. The build was incremented back in May 2020 with this commit.

https://git.slackbuilds.org/slackbuilds/commit/libraries/python3-PyQt5?h=14.2=47f31d21c7b44346917fd1048f5a6dc31ef7f545

Jeremy

>
___
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] zfs-on-linux

[Jeremy Hansen]

On Tue, Feb 23, 2021, 2:52 PM David Chmelik  wrote:

> On 2/21/21 1:50 PM, Markus Reichelt wrote:
> > * David Chmelik  wrote:
> >
> >> On 5.10.n kernels I always get the error below (so am forced to use
> >> older kernels.)  However you said it works for you somehow (with
> >> modifications?)
> > It worked on -current some time in the past, it doesn't anymore as of
> -current Sat Feb 20 21:04:15 UTC 2021
> >
> > you might want to try something like this
> >
> > cd /tmp
> > gpg --keyserver keys.gnupg.net --recv-key "D307 6BC3 E783 EE74 7F09
> B8B7 0368 EF57 9C7B A3B6"
> > wget https://slackbuilds.org/slackbuilds/14.2/system/zfs-on-linux.tar.gz
> https://slackbuilds.org/slackbuilds/14.2/system/zfs-on-linux.tar.gz.asc
> > gpg zfs-on-linux.tar.gz.asc && tar xf zfs-on-linux.tar.gz && cd
> zfs-on-linux
> >
> > gpg --keyserver keys.gnupg.net --recv-key "4F3B A9AB 6D1F 8D68 3DC2
> DFB5 6AD8 60EE D459 8027"
> > wget
> https://github.com/openzfs/zfs/releases/download/zfs-2.0.3/zfs-2.0.3.tar.gz.asc
> https://github.com/openzfs/zfs/releases/download/zfs-2.0.3/zfs-2.0.3.tar.gz
> > gpg zfs-2.0.3.tar.gz.asc && su -lc "VERSION=2.0.3 sh
> zfs-on-linux.SlackBuild"
>
> Changing the version to 2.0.3 and building with that worked to build a
> package, which does not work.  The module is somewhere it shouldn't be:
> /usr/lib/modules , instead of /lib/modules .  Modprobe couldn't load
> it.  I think the build script is even now broken for 0.8.6 (same
> problem) for Slackware stable.
>

I just tried building the 0.8.6 version on my 14.2 system running a 5.10.x
kernel, which obviously didn't work. I then specified an older 5.4.66
kernel I used and it built fine and stored the modules in the correct
location (/lib/modules/5.4.66/extra/).

It might be that the newer 2.0.x versions require different build options.

Jeremy

>
___
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] Chromium?

[Jeremy Hansen]

On Fri, Feb 19, 2021, 3:09 PM Rich Shepard  wrote:

> I had an SBo chromium package installed. Now I don't find one in the SBo
> repo or in the core distribution.
>
> Is there one available?
>

There was one on SBo, but it was horribly outdated and was likely removed
because of security issues. The only place I'm aware of that offers it for
Slackware now is from Alien Bob.

http://www.slackware.com/~alien/slackbuilds/chromium/pkg64/14.2/

Jeremy

>
___
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] Building atlas

[Jeremy Hansen]

On Thu, Feb 18, 2021, 1:04 PM Rich Shepard  wrote:

> On Thu, 18 Feb 2021, Erich Ritz wrote:
>
> > Perhaps it meant to reference this?
> >
> https://slackbuilds.org/slackbuilds/14.2/libraries/atlas/README.SLACKWARE
> > which instructs you to do:
> > /etc/rc.d/rc.cpufreq performance
>
> Erich,
>
> I saw the README.SLACKWARE file but was looking for the INSTALL.txt file
> the
> build suggested.
>

This is likely something that's in the source tarball and resides in the
/tmp/SBo/atlas-$VERSION directory. It wouldn't be something on SBo if it's
referenced by the source itself.

Jeremy
___
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] geoclue2: wants optional dependencies [FIXED]

[Jeremy Hansen]

On Thu, Feb 18, 2021, 8:03 AM Rich Shepard  wrote:

> On Thu, 18 Feb 2021, Tim Dickson via SlackBuilds-users wrote:
>
> > if you had run "sync" from within sbopkg as you just said, your
> > geoclue2.SlackBuild would have been the most up-to-date one, and you
> would
> > have avoided the problem you had, which makes it puzzling.
>
> Tim,
>
> Does sync find packages I need that are not already installed? I was under
> the impression that when I ran sync it compared the SBo packages here with
> those on the SBo repo.
>

All sbopkg's sync does is sync its local repo with SBo's online repo. If
you go into the "Updates" section of the program, it will present you with
a list of packages that are installed that have had either the VERSION or
BUILD variables (or both) change from what you have installed.

However, since sbopkg itself doesn't track dependencies (that is kinda done
with sqg), it won't/can't notify you of new packages you need to install.
Other programs that interact with SBo are able to provide this
functionality if it's something you're looking for, but I'm not familiar
enough with them to provide guidance on what to use.

Jeremy

>
___
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] geoclue2: wants optional dependencies [FIXED]

[Jeremy Hansen]

On Wed, Feb 17, 2021, 9:35 PM Rich Shepard  wrote:

> On Wed, 17 Feb 2021, Jeremy Hansen wrote:
>
> > Those are taken directly from the SlackBuild script. It's how the script
> > determines whether or not to pass --disable-nmea-source to the configure
> > script.
>
> Jeremy,
>
> Thanks for pointing me to the problem and its solution.
>
> When I went to rebuild geoclue2 I checked the current SBo version with what
> I have here; they're the same. So I used the existing build script.
>
> Reading your message I downloaded the build script from the SBo repo and
> diff'd it against the one here:
>
> $ diff geoclue2.SlackBuild geoclue2/geoclue2.SlackBuild
> 4c4
> < # Copyright 2017 Aaditya Bagga 
> ---
> > # Copyright 2017-2018 Aaditya Bagga 
> 73,74c73,74
> < # to avoid avahi as a dependency add --disable-nmea-source
> < # to the configure options
> ---
> > avahi_opts='--disable-nmea-source'
> > [ "${AVAHI:-no}" != "no" ] && avahi_opts=''
> 85a86
> >   $avahi_opts \
>
> The one that's been here since 2017 was modified in 2018 to include the
> missing lines. I assumed that if the source tarballs were the same version
> the build scripts would also be the same. That's been the case with other
> packages but now we know, not with geoclue2.
>

You should never expect that the SlackBuilds haven't changed just because
the source tarballs haven't. You should always grab the latest as they
might include changes, fixes, or patches. If the update is substantial, the
maintainer is supposed to update the BUILD variable of the SlackBuild.

If you're going to build packages manually, it would probably be good to
keep a local git repo of SBo and update that before running SlackBuilds.

You can create the repo by running:

git clone git://git.slackbuilds.org/slackbuilds.git sbo-repo

Then you can update it by going in the directory and running:

git pull

Hopefully this will prevent

>
___
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] geoclue2: wants optional dependencies

[Jeremy Hansen]

On Wed, Feb 17, 2021, 7:16 PM Rich Shepard  wrote:

> On Wed, 17 Feb 2021, Jeremy Hansen wrote:
>
> > I don't know what to tell you. The SlackBuild defaults to disabling nmea
> > unless the AVAHI variable is set to anything other than "no". If it is
> > left unset, nmea is disabled.
>
> > The only other thing to check would be running the script with bash -x to
> > see everything bash sees when it's running the script. This way it would
> be
> > able to tell you what happens with the above code block.
>
> Jeremy,
>
> geoclue2 was installed long ago with no problems, and upgraded since then.
> Why it should now ask for a non-present file is puzzling.
>
> If I could find an avahi something to install that would make geoclue2
> happy
> I'd do it. But I haven't found anything.
>
> Running the script from bash yields the same results.
>
> > avahi_opts='--disable-nmea-source'
> > [ "${AVAHI:-no}" != "no" ] && avahi_opts=''
>
> What should I do with these? Put them in the build script somewhere? A
> quick
> web search suggests that 'nmea' is a software gps emulator. There ought to
> be something that will tell the build script to ignore nmea, avahi, and all
> similar optional inputs.
>

Those are taken directly from the SlackBuild script. It's how the script
determines whether or not to pass --disable-nmea-source to the configure
script.

Based on your log, it seems you don't have the proper script. There's
nothing in the log setting the avahi_opts variable, which tells me the
above line seems to not be in your SlackBuild.

I got the following in between the extraction of the tarball and the
configure command.

geoclue-2.4.7/COPYING.LIB
geoclue-2.4.7/intltool-merge.in
+ cd geoclue-2.4.7
+ chown -R root:root .
+ find -L . '(' -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm
555 -o -perm 511 ')' -exec chmod 755 '{}' ';' -o '(' -perm 666 -o -perm 664
-o -perm 640 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 ')' -exec
chmod 644 '{}' ';'
+ avahi_opts=--disable-nmea-source
+ '[' no '!=' no ']'
+ CFLAGS='-O2 -fPIC'
+ CXXFLAGS='-O2 -fPIC'
+ ./configure --prefix=/usr --libdir=/usr/lib64 --sysconfdir=/etc
--localstatedir=/var --mandir=/usr/man --infodir=/usr/info
--docdir=/usr/doc/geoclue2-2.4.7 --disable-nmea-source --enable-static=no
--build=x86_64-slackware-linux

Your log is missing the red section, which means that the code to set it
(which I included in a previous message) must be missing in your
SlackBuild. Otherwise there'd be something in there about what the avahi
variable is.

Jeremy
___
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] geoclue2: wants optional dependencies

[Jeremy Hansen]

On Wed, Feb 17, 2021 at 1:53 PM Rich Shepard 
wrote:

> On Wed, 17 Feb 2021, B Watson wrote:
>
> > Are you sure you didn't run the script with the AVAHI variable set
> > in the environment?
>
> B,
>
> Yes.
>
> > From looking at the SlackBuild, it needs to be either unset, set to ""
> > (empty), or set to "no" (lowercase), to build without avahi. If it were
> > set to anything else (including for example "NO" or "false"), the
> > --disable-nmea-source option doesn't get passed to configure.
>
> On the SBo page I read,
>
> "avahi is an optional dependency, used for location sharing (by redshift,
> for example).  To enable it, use the option AVAHI=yes
>
>AVAHI=yes ./geoclue2.Slackbuild"
>
> Since I don't want to enable it I did not add AVAHI=yes.
>
> That's also in the README file. I didn't see anything about setting
> AVAHI=no
> or anything else.
>
> > If you're using 'export AVAHI=', you might have a leftover
> > value in your environment. Use 'unset AVAHI' to clear it out.
>
> There's no AVAHI here to export.
>
> If AVAHI is not on the system how would it be in the environment?
>
> My web search showed me that AVAHI is a networking implentation which
> enables programs to publish and discover services and hosts running on a
> local network. If it's part of core Slackware then it's missing here after
> my running 'slackpkg upgrade-all'.
>
> > In general, when the README says 'set VARIABLE=value in the
> > environment', the script specifically looks for 'value',
> > case-sensitive. 'Value' or 'VALUE' won't match.
>
> When package maintainers write 'to add this option use this in front of the
> build script' and I don't want to add it I've always left it off.
>
> > Also, you can try forcing the issue with AVAHI="no" in the env. That
> > should work.
>
> Worth a try. Command line: AVAHI=no ./geoclue2.SlackBuild &>
> geoclue2-build.log
>
> Same results. Build log attached.
>

I don't know what to tell you. The SlackBuild defaults to disabling nmea
unless the AVAHI variable is set to anything other than "no". If it is left
unset, nmea is disabled.

avahi_opts='--disable-nmea-source'
[ "${AVAHI:-no}" != "no" ] && avahi_opts=''

The only other thing to check would be running the script with bash -x to
see everything bash sees when it's running the script. This way it would be
able to tell you what happens with the above code block.

Jeremy
___
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] hdf5 md5sums don't match

[Jeremy Hansen]

On Tue, Feb 16, 2021, 5:38 PM Rich Shepard  wrote:

> Bringing my system back to only -14.2 packages and no multilib/compat32 I
> mistakenly ran 'slackpkg clean-system' and uninstalled all 582 SBo
> packages.
> Long days ahead.
>
> Rebuilding packages and ensuring I have the current versions (because
> sbopkg
> upgraded many but left the local version as-is) and am finding packages
> that
> don't build which surprises me.
>
> Now it's hdf5:
> # time ./hdf5.SlackBuild
> tar: This does not look like a tar archive
> tar: Skipping to next header
> tar: Exiting with failure status due to previous errors
>
> I just downloaded hdf5-1.10.6.tar.gz so I compared the downloaded md5sum
> with that on the SBo page:
> $ md5sum hdf5-1.10.6.tar.gz
> de8a3ac2682b95f918dd19d61748ddb2  hdf5-1.10.6.tar.gz
> $ 37f3089e7487daf0890baf3d3328e54a (from SBo)
>
> Please advise.
>

I just tested it on my system and it downloaded fine and the md5sum matched
SBo's. It might've been a temporary outage from the server and caused you
to download a text file.

Jeremy

>
___
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] geoclue2: wants optional dependencies

[Jeremy Hansen]

On Tue, Feb 16, 2021, 5:22 PM Rich Shepard  wrote:

> On Tue, 16 Feb 2021, Jeremy Hansen wrote:
>
> >> I don't know that I need it so I tried building without it:
>
> > It works fine on my 14.2 system without avahi installed. Did you pass
> > AVAHI=yes to the script?
>
> Jeremy,
>
> As I wrote, no. I've no need for avahi so I tried building without it.
> That's why I was surprised when the build script asked for it.
>
> I've a clean 14.2 so I don't know why it didn't build.
>

Your attached build.log (which isn't an actual build log, just the output
from the configure script -- config.log from the build directory would be
more beneficial) showed it ended on:

checking for NMEA_SOURCE... no

Looking at the SlackBuild, it should only check for NMEA if the AVAHI
variable is set to anything other than "no".

This seems to work fine on my system, so I'm not sure why it wouldn't on
yours unless the avahi variable is set to anything other than "no" (unset
is fine).

Can you try again ensuring avahi is unset? If that still doesn't work, try
specifically forcing AVAHI=no when running the SlackBuild.

Jeremy

>
___
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] geoclue2: wants optional dependencies

[Jeremy Hansen]

On Tue, Feb 16, 2021, 3:24 PM Rich Shepard  wrote:

> I need to rebuild/re-install geoclue2. The SBo page says that,
> avahi is an optional dependency, used for location sharing (by redshift,
> for example).  To enable it, use the option AVAHI=yes
>
>AVAHI=yes ./geoclue2.Slackbuild
>
> I don't know that I need it so I tried building without it:
>
> configure: error: Package requirements (
>  avahi-client >= 0.6.10
>  avahi-glib >= 0.6.10) were not met:
>
> No package 'avahi-client' found
> No package 'avahi-glib' found
>
> Full build log attached.
>

It works fine on my 14.2 system without avahi installed. Did you pass
AVAHI=yes to the script? Because that forces avahi support and the
configure will fail without it installed. If you don't pass it to the
script, it disables nmea support, which means avahi is no longer needed.

Jeremy

>
___
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

[Jeremy Hansen]

On Sun, Jan 10, 2021, 3:06 AM Jude DaShiell  wrote:

> 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.
> 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
>

I'm not Dave, but it's available on SBo.

https://slackbuilds.org/repository/14.2/libraries/SDL2_image/

Jeremy
___
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] vlc-3.0.11.1 build fails

[Jeremy Hansen]

On Thu, Dec 24, 2020, 6:45 AM Frédéric Falsetti 
wrote:

> Hi,
> I have rebuild VTK-8.2.0-i486-2_SBo
> opencv-4.5.0-i586-1(ffmpeg-3.2.4-i486-1), I have qt5-5.12.8-i586-1
> and absolutely no idee why vlc fails with
> /tmp/SBo/vlc-3.0.11.1/bin/.libs/lt-vlc-cache-gen: symbol lookup error:
> /usr/lib/libvtkCommonExecutionModel.so.1: undefined symbol:
> _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv
>
> thanks in advence for any help
>
>
> make[2] : on entre dans le répertoire « /tmp/SBo/vlc-3.0.11.1/bin »
>   CC   vlc-vlc.o
>   CC   vlc-override.o
>   CCLD vlc
>   CC   rootwrap.o
> rootwrap.c: Dans la fonction ‘main’:
> rootwrap.c:251:5: attention : ignoring return value of ‘setuid’, declared
> with attribute warn_unused_result [-Wunused-result]
>  setuid (uid);
>  ^
>   CCLD vlc-wrapper
>   CC   vlc_static-vlc.o
>   CC   vlc_static-override.o
>   CCLD vlc-static
>   CC   cachegen.o
>   CCLD vlc-cache-gen
>   GEN  ../modules/plugins.dat
> /tmp/SBo/vlc-3.0.11.1/bin/.libs/lt-vlc-cache-gen: symbol lookup error:
> /usr/lib/libvtkCommonExecutionModel.so.1: undefined symbol:
> _ZN33vtkFilteringInformationKeyManager13ClassFinalizeEv
> Makefile:1799 : la recette pour la cible « ../modules/plugins.dat » a
> échouée
> make[2]: *** [../modules/plugins.dat] Erreur 127
> make[2] : on quitte le répertoire « /tmp/SBo/vlc-3.0.11.1/bin »
> Makefile:1561 : la recette pour la cible « all-recursive » a échouée
> make[1]: *** [all-recursive] Erreur 1
> make[1] : on quitte le répertoire « /tmp/SBo/vlc-3.0.11.1 »
> Makefile:1446 : la recette pour la cible « all » a échouée
> make: *** [all] Erreur 2
>

Unless it's a typo, your VTK build is screwed up. The SlackBuild isn't able
to create an i486 package as it will do i586 when run on a 32bit Slackware.

That being said, I'm not sure if this is related to your problem.

Googling the error shows a message on the SBo mailing list back in May with
a similar issue, and it seems other's weren't seeing the same issue when
tested. They suggested removing VTK and opencv and rebuilding both and that
seemed to fix the issue.

https://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-May/024560.html

Good luck!
Jeremy

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

Re: [Slackbuilds-users] FreeBASIC update fails

[Jeremy Hansen]

On Wed, Dec 23, 2020, 3:44 AM Jude DaShiell  wrote:

> What I have is fakeroot 1.20.2 on slackware 14.2 (slint) and slint could
> have added packages or this could have installed as part of the FreeBASIC
> install.  Since fakeroot is a dependency of FreeBASIC it's strange when
> doing sqg -p FreeBASIC the package comes back with no requirements from
> sqg and won't build.  At this point, I'm confused.  Don't worry though I'm
> easily confused much of the time especially before coffee.
>
>
>
> On Wed, 23 Dec 2020, B Watson wrote:
>
> > On 12/22/20, Jude DaShiell  wrote:
> >> For whatever reason one of the fakeroot commands fails and fakeroot is
> by
> >> default a part of slackware and on this system.
> >
> > What version of Slackware? 14.2 doesn't have fakeroot. There's a
> > fakeroot build on SBo, are you saying the FreeBASIC build fails if
> > fakeroot is installed at build time?
> >
> >> 7 errors happen with the last one being fatal.
> >>
> >> FreeBASIC-1.07.1-source-bootstrap/doc/manual/cache/CatPgError.wakka
> >>
> FreeBASIC-1.07.1-source-bootstrap/doc/manual/cache/ProPgErrorHandling.wakka
> >> FreeBASIC-1.07.1-source-bootstrap/doc/manual/cache/KeyPgError.wakka
> >>
> FreeBASIC-1.07.1-source-bootstrap/doc/manual/cache/TblRuntimeErrors.wakka
> >> FreeBASIC-1.07.1-source-bootstrap/inc/X11/Xmu/Error.bi
> >> FreeBASIC-1.07.1-source-bootstrap/inc/CUnit/CUError.bi
> >> make: *** [src/compiler/obj/linux-x86_64/ast-gosub.o] Error 127
> >
> > Those aren't the useful error messages. Any chance you could re-run
> > the build and post the entire build log? Something like:
> >
> > ./FreeBASIC.SlackBuild &> build.log
> >
> > ...then send the entire build.log to the mailing list.
>

Fakeroot is not part of actual Slackware (Slint is an unofficial fork that
SBo doesn't test against) and there's so specific requirements in the
SlackBuild for fakeroot. So if this is tied to fakeroot, it might only be
an issue on Slint.

Posting more or all of the log might help us in figuring out the issue and
suggesting a way to fix it.

Jeremy

>
___
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] sqg for teapot

[Jeremy Hansen]

teapot does not have any required dependencies (it has an optional
dependency of fltk, but sqg doesn't pick up optional dependencies). This is
why sqg presents that prompt. Generating a queue for a program that has no
dependencies is a little redundant.

If you still want to generate a queue file for a program that doesn't need
it, you'd uncomment that line in the sqg script itself (located at
/usr/bin/sqg) and you'd remove the # from line 50 (at least that's the line
on my system).

Jeremy

On Tue, Nov 17, 2020, 10:40 AM Jude DaShiell  wrote:

> I run sqg -p "teapot" to get this information.
> On Tue, 17 Nov 2020,
> Jheengut Pritvi wrote:
>
> > Date: Tue, 17 Nov 2020 05:55:28
> > From: Jheengut Pritvi 
> > Reply-To: SlackBuilds.org Users List 
> > To: SlackBuilds.org Users List 
> > Subject: Re: [Slackbuilds-users] sqg for teapot
> >
> > Hi,
> >
> > where do you get this info ??
> >
> > :: Uncomment SKIP_EMPTY to change this.
> >
> > On Mon, 16 Nov 2020 at 22:50, Jude DaShiell  wrote:
> >
> > > teapot: empty REQUIRES line. No queuefile generated.
> > > Uncomment SKIP_EMPTY to change this.
> > > Done.
> > >
> > > Where do I uncomment SKIP_EMPTY?  I want to find out if installing this
> > > package again gets me a user guide in /usr/share/doc/teapot.
> > >
> > >
> > > --
> > > United States has 633 Billionaires with only 10 doing any annual
> > > significant giving.
> > >
> > > ___
> > > 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/
> > >
> > >
> >
>
> --
> United States has 633 Billionaires with only 10 doing any annual
> significant giving.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Clementine up for grabs

[Jeremy Hansen]

On Mon, Nov 2, 2020, 12:21 PM Dave Woodfall  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

>
___
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] Add Autodetect to ffmpeg for Optional Dependencies

[Jeremy Hansen]

Heinz,

I'm a bit frustrated that the developers of ffmpeg don't have autodetect in
their ./configure. Your script has definitely helped improve building
ffmpeg, but even with that, it is quite inconvenient to have to pass all
those VARs to the SlackBuild script (and for users of SBo building programs
to figure out how to pass those variables to the program).

So I decided to add autodetection for those packages into the SlackBuild
script itself and update the variables passed to the ./configure based on
that autodetection. pkg-config is used for most of them, but there's 7
programs that don't support it, so I just checked for that program's header
file.

Now users would just need to disable any optional features if they have the
packages installed but don't want that support in ffmpeg.

I've also updated the README to reflect the change and bumped the build
number.

The only thing that might need tweaking is the length of the lines doing
the autodetection. They go well beyond the soft 72 character limit on a
single line (all of them are over 100 characters and the longest is 186
characters). I started going through and breaking them up, but there are
some unique lines that don't have a natural break before the 72 character
point. Feel free to make any adjustments if you feel they're necessary.

Hopefully you'll agree that this would be a beneficial change to the
SlackBuild and switch things over. Let me know if you have any thoughts or
suggestions.

Jeremy (aka bassmadrigal on the LQ forum)
From a0f627934b0d016a407fb0528705840e15be2bea Mon Sep 17 00:00:00 2001
From: Jeremy Hansen 
Date: Sat, 24 Oct 2020 17:43:55 -0600
Subject: [PATCH 1/1] multimedia/ffmpeg: Add autodetection support for optional
 dependencies

---
 multimedia/ffmpeg/README|  81 +++---
 multimedia/ffmpeg/ffmpeg.SlackBuild | 131 +++-
 2 files changed, 126 insertions(+), 86 deletions(-)

diff --git a/multimedia/ffmpeg/README b/multimedia/ffmpeg/README
index 09b08b00df..d93a142fc5 100644
--- a/multimedia/ffmpeg/README
+++ b/multimedia/ffmpeg/README
@@ -4,46 +4,49 @@ FFmpeg is a complete solution to record, convert and stream audio
 and video. It includes libavcodec, the leading audio/video codec
 library.
 
-You can enable a lot of optional (not-autodetected) features by
-passing variables to the script (VAR=yes/no ./ffmpeg.SlackBuild):
-ASS=yes|no (default: no), requires libass
-BLURAY=yes|no (default: no), requires libbluray
-BS2B=yes|no (default: no), requires libbs2b
-CELT=yes|no (default: no), requires celt
-CHROMAPRINT=yes|no (default: no), requires chromaprint
-DC1394=yes|no (default: no), requires libdc1394
-DECKLINK=yes|no (default: no), requires decklink-sdk
-EBUR128=yes|no (default: no), requires libebur128
-FDK_AAC=yes|no (default: no), requires libfdk-aac (creates non-redistributable binary)
-FLITE=yes|no (default: no), requires flite
-FREI0R=yes|no (default: no), requires frei0r
-GME=yes|no (default: no), requires libgme
-GSM=yes|no (default: no), requires gsm
-IEC61883=yes|no (default: no), requires libiec61883 and libavc1394
-ILBC=yes|no (default: no), requires libilbc
-LADSPA=yes|no (default: no), requires ladspa_sdk
-LAME=yes|no (default: no), requires lame
-MODPLUG=yes|no (default: no), requires libmodplug
-NETCDF=yes|no (default: no), requires netcdf
-OPENAL=yes|no (default: no), requires OpenAL
-OPENCORE=yes|no (default: no), requires opencore-amr
-OPENCV=yes|no (default: no), requires opencv-legacy
+The following packages are optional dependencies. They will be enabled
+if autodetected. If you want them disabled, pass:
+VAR=no .ffmpeg.SlackBuild
+
+OpenAL		(disable via OPENAL=no)
+celt		(disable via CELT=no)
+chromaprint	(disable via CHROMAPRINT=no)
+decklink-sdk	(disable via DECKLINK=no)
+flite		(disable via FLITE=no)
+frei0r		(disable via FREI0R=no)
+gsm		(disable via GSM=no)
+ladspa_sdk	(disable via LADSPA=no)
+lame		(disable via LAME=no)
+libass		(disable via ASS=no)
+libbluray	(disable via BLURAY=no)
+libbs2b		(disable via BS2B=no)
+libdc1394	(disable via DC1394=no)
+libebur128	(disable via EBUR128=no)
+libfdk-aac	(disable via FDK_AAC=no) (creates non-redistributable binary)
+libgme		(disable via GME=no)
+libilbc		(disable via ILBC=no)
+libmodplug	(disable via MODPLUG=no)
+libwebp		(disable via WEBP=no)
+netcdf		(disable via NETCDF=no)
+opencore-amr	(disable via OPENCORE=no)
+opencv-legacy	(disable via OPENCV=no)
+opus		(disable via OPUS=no)
+rtmpdump	(disable via RTMP=no)
+rubberband	(disable via RUBBERBAND=no)
+schroedinger	(disable via SCHROEDINGER=no)
+snappy		(disable via SNAPPY=no)
+speex		(disable via SPEEX=no)
+tesseract	(disable via TESSERACT=no)
+twolame		(disable via TWOLAME=no)
+vid.stab	(disable via VIDSTAB=no)
+x264		(disable via X264=no)
+x265		(disable via X265=no)
+xvidcore	(disable via XVID=no)
+zeromq		(disable via ZMQ=no)
+zvbi		(disable via ZVBI=no)
+libiec61883 & libavc1394 (disable via IEC61883=no)
+
 OPENSSL=yes|no (def

Re: [Slackbuilds-users] use git to submit package update?

[Jeremy Hansen]

On Sun, Oct 4, 2020, 9:32 PM Donald Cooley via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> Can I submit a git pull request to update my packages?
>
> ==
> Regards,
> Donald Cooley
>

Willy accepts PRs on GitHub or MRs on GitLab.

https://github.com/SlackBuildsOrg/slackbuilds

https://gitlab.com/SlackBuilds.org/slackbuilds

I frequently use GitHub for pull requests.

Jeremy
___
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

[Jeremy Hansen]

On Sat, Oct 3, 2020, 2:45 PM Rich Shepard  wrote:

> On Sat, 3 Oct 2020, Rich Shepard wrote:
>
> > I just deleted /tmp/SBo and let sbopkg re-create it and sync it with the
> > repo. Should have done this before writing.
>
> I found the sourc(s). First, /var/log/packages | grep dokuwiki returns
> nothing, but /var/log/packages | grep dokuwiki-20180422b-noarch-1_SBo finds
> it. Using locate that package showed up as well as an executable script in
> /var/log/scripts/.
>
> Removed both files. While I expected them to be removed when I removed the
> package now I know why sbopkg kept showing me an available update.
>
> Stay well, all,
>
> Rich
>

How did you remove the package? I don't think think I've ever had an entry
remain in /var/log/packages after using removepkg for that package (unless
more than one version was installed).

My worry is that the package might still be installed and you just removed
the references to what files are installed to the system.

Jeremy

>
___
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

[Jeremy Hansen]

On Sun, Sep 27, 2020, 8:24 AM Luiz Carlos Ramos 
wrote:

> Hello,
>
> supertuxkart much likely has the MD5 sum not updated from version 1.1 to
> 1.2 in the .info file.
>
> Thanks,
>
> Luiz Ramos
> Sao Paulo - Brazil
>

Shoot! Thanks for the heads up and thanks to Dave for fixing my screw-up.

Jeremy

>
___
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] discord download fails

[Jeremy Hansen]

On Wed, Sep 16, 2020, 2:29 AM David Chmelik  wrote:

> On 9/16/20 12:11 AM, Jeremy Hansen wrote:
> > On Fri, Sep 11, 2020, 10:48 AM Dave Woodfall  > <mailto:d...@slackbuilds.org>> wrote:
> >
> > On 11/09/20 12:06,
> > Barry Grundy mailto:bgru...@gmail.com>> put
> > forth the proposition:
> > > The .info file for discord:
> > > DOWNLOAD_x86_64="
> > > https://dl.discordapp.net/apps/linux/0.0.10/discord-0.0.11.deb;
> > > Should be:
> > > DOWNLOAD_x86_64="https://dl.discordapp.net/apps/linux/0.0.*11*
> > > /discord-0.0.11.deb"
> > > (FYI: version 12 is available and works fine with a version bump
> > only)
> > > --
> > > 
> > > Barry Grundy
> > > bgru...@gmail.com <mailto:bgru...@gmail.com>
> > > bgru...@linuxleo.com <mailto:bgru...@linuxleo.com>
> >
> > Fixed in my branch.  Thanks Barry.
> >
> > --
> > Dave
> >
> >
> > Thanks for fixing this Dave. I was out camping and didn't have service.
> >
> > Barry, I'll get the update to 0.0.12 pushed before the weekend. Thanks
> > for the heads up!
> >
> > Jeremy
>
> Yes, and why use a .deb?  Discord makes .tar.gz
>

They had the tar.gz available when I first created the SlackBuild, but I
think the deb had simpler locations and required less tweaking. However,
it's been a while since I looked, so I don't remember for sure.

If you know of any benefits with the tar.gz, I'd be happy to reconsider.

Jeremy

>
___
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/