From kjhambrick at gmail.com  Sun May  1 09:58:47 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 1 May 2022 04:58:47 -0500
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <Ym2l5SsbUDx6Ece5@localhost>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
 <Ym2l5SsbUDx6Ece5@localhost>
Message-ID: <CANBHt+M_BXtNBsCSGa4Eisv221Ke8HLnXk7-z9NBPb3oZbFM=A@mail.gmail.com>

On Sat, Apr 30, 2022 at 4:11 PM Dave Woodfall <dave at slackbuilds.org> wrote:

> On 30/04/22 15:23,
> Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> > All --
> > Been playing with the OTB.SlackBuild and OTB Version 8.0.0
> > I am getting clean builds and the program works as expected.
> > `sbolint` returns no errors or warnings, but when I run
> > sbopkglint /tmp/OTB-8.0.0-x86_64-1_SBo.tgz I get a hint:
> > Running test: 35-desktop...usr/share/applications/monteverdi.desktop:
> hint:
> > value "Education;Science;ImageProcessing;Geography;Qt;" for key
> > "Categories" in group "Desktop Entry" contains more than one main
> category;
> > application might appear more than once in the application menu
> > OK
> > Otherwise, all tests are OK
> > Note that sbopkglint returns the same hint on the  OTB Version 7.3.0
> > Package file.
> > There is a doinst.sh script that I took from the Version 7.3 SlackBuild (
> > below by sig )
> > What is the proper way to set up a Desktop App in an SBo ?
> > Thanks.
>
> You need to decide which menu category the application should be in,
> then edit the .desktop to match.
>
> > value "Education;Science;ImageProcessing;Geography;Qt;"
>
> From the description, I'd say ImageProcessing.
>
> OTB.desktop file is installed by the application so the usual way is
> to sed the file somewhere after the make install.
>
> --
> Dave
>
Well now ...

There's a lot to know before a .desktop file will pass
`/usr/bin/desktop-file-validate`
I ended up spending more time than I had to spend here:

   https://www.freedesktop.org/wiki/Specifications/menu-spec/

and the specific info about Desktop Categories is here:

   https://specifications.freedesktop.org/menu-spec/latest/apa.html

I ended up with the if-block below my sig ...

Note that the monteverdi app ends up all by itself under the 'Science and
Math'
Desktop Menu Category.

But now the package passes sbopkglint without Errors, Warnings or Hints.

Thanks for the feedback Dave and B. Watson !

Question:  is there a better way ( or a recommended way ) to enter long,
formatted
lists of text like NEW_CAT in the code snippet below ?

Note that many other SBo Packages also fail `desktop-file-validate` so
maybe this was
all a fools-errand :)

-- kjh

# ------------------- cut  here -----------------
# default Categories=Education;Science;ImageProcessing;Geography;Qt;
# in build/monteverdi.desktop annoys sbopkglint try this instead ...
# see: https://specifications.freedesktop.org/menu-spec/latest/apa.html

if [ "$MONTEVERDI" = "ON" ] ; then
   NEW_CAT="Science;Math;ImageProcessing;DataVisualization"
   NEW_CAT="$NEW_CAT;Geoscience;NumericalAnalysis;Qt;"

   sed -i -e "s/^Categories=.*$/Categories=$NEW_CAT/" \
   $PKG/usr/share/applications/monteverdi.desktop
fi
# ------------------- cut there -----------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220501/211bcf60/attachment.htm>

From dave at slackbuilds.org  Sun May  1 10:09:58 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 1 May 2022 11:09:58 +0100
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <CANBHt+M_BXtNBsCSGa4Eisv221Ke8HLnXk7-z9NBPb3oZbFM=A@mail.gmail.com>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
 <Ym2l5SsbUDx6Ece5@localhost>
 <CANBHt+M_BXtNBsCSGa4Eisv221Ke8HLnXk7-z9NBPb3oZbFM=A@mail.gmail.com>
Message-ID: <Ym5cdn0EKeA89Jyo@localhost>

On 01/05/22 04:58,
Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
<snip>
> Question:  is there a better way ( or a recommended way ) to enter long,
> formatted
> lists of text like NEW_CAT in the code snippet below ?
...
>    NEW_CAT="Science;Math;ImageProcessing;DataVisualization"
>    NEW_CAT="$NEW_CAT;Geoscience;NumericalAnalysis;Qt;"

If text width matters then that's how to enter long strings and
keeping within a limit.  Under bash/zsh you can also use +=

NEW_CAT="Science;Math;ImageProcessing;DataVisualization"
NEW_CAT+=";Geoscience;NumericalAnalysis;Qt;"

> Note that many other SBo Packages also fail `desktop-file-validate` so
> maybe this was
> all a fools-errand :)

Well it is only a warning, not an error, so it wouldn't fail the
slackbuild.

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/

From kjhambrick at gmail.com  Sun May  1 12:21:22 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 1 May 2022 07:21:22 -0500
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <Ym5cdn0EKeA89Jyo@localhost>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
 <Ym2l5SsbUDx6Ece5@localhost>
 <CANBHt+M_BXtNBsCSGa4Eisv221Ke8HLnXk7-z9NBPb3oZbFM=A@mail.gmail.com>
 <Ym5cdn0EKeA89Jyo@localhost>
Message-ID: <CANBHt+PsKakMiS+dPir1nSFVHup00QDNLj4ojw_bc4CjYtxWPw@mail.gmail.com>

On Sun, May 1, 2022 at 5:10 AM Dave Woodfall <dave at slackbuilds.org> wrote:

> On 01/05/22 04:58,
> Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> <snip>
> > Question:  is there a better way ( or a recommended way ) to enter long,
> > formatted
> > lists of text like NEW_CAT in the code snippet below ?
> ...
> >    NEW_CAT="Science;Math;ImageProcessing;DataVisualization"
> >    NEW_CAT="$NEW_CAT;Geoscience;NumericalAnalysis;Qt;"
>
> If text width matters then that's how to enter long strings and
> keeping within a limit.  Under bash/zsh you can also use +=
>
> NEW_CAT="Science;Math;ImageProcessing;DataVisualization"
> NEW_CAT+=";Geoscience;NumericalAnalysis;Qt;"
>
> > Note that many other SBo Packages also fail `desktop-file-validate` so
> > maybe this was
> > all a fools-errand :)
>
> Well it is only a warning, not an error, so it wouldn't fail the
> slackbuild.
>
> --
> Dave
>
Thanks Dave !

I had forgotten that SlackBuilds for Slackware 15.0 and beyond require
#!/bin/bash

The += Operator is the way to go :)

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220501/f4064676/attachment.htm>

From urchlay at slackware.uk  Sun May  1 17:09:12 2022
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 1 May 2022 13:09:12 -0400 (EDT)
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <CANBHt+M_BXtNBsCSGa4Eisv221Ke8HLnXk7-z9NBPb3oZbFM=A@mail.gmail.com>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
 <Ym2l5SsbUDx6Ece5@localhost>
 <CANBHt+M_BXtNBsCSGa4Eisv221Ke8HLnXk7-z9NBPb3oZbFM=A@mail.gmail.com>
Message-ID: <36a64a28-edff-4d83-7f9d-375f49a9647@slackware.uk>



On Sun, 1 May 2022, Konrad J Hambrick wrote:

> Question:? is there a better way ( or a recommended way ) to enter long,
> formatted?
> lists of?text like NEW_CAT in the code snippet below ?

There's an easier-to-read way to do the same thing: include your own
.desktop file(s) with your SlackBuild, and overwrite the one(s) from
'make install' with your own:

cat $CWD/$PRGNAM.desktop > $PKG/usr/share/applications/$PRGNAM.desktop

I do this if the sed or whatever code that changes the .desktop gets
to be too long or complex.

> Note that many other SBo Packages also fail `desktop-file-validate` so maybe
> this was?
> all a fools-errand?:)

Nope. Making the .desktop file standards-compliant is an improvement.

Even if the invalid .desktop file "works OK" with KDE and/or XFCE,
fixing it is future-proofing. Plus, there are other DEs that people
use on Slackware (e.g. TDE, Mate, Gnome, LXDE), that SBo maintainers
are unlikely to test against. Correct .desktop files will work with
any of them (or if not, it's a bug in the DE, not the .desktop file).

It's even possible to use .desktop files with WindowMaker (see
xdgmenumaker on SBo) or dmenu on a tiling WM (see j4-dmenu-desktop).
Or with FluxBox (fbmenugen).

In other words, there are a lot of use cases, and it's unrealistic for
you to try to test them all for every build you maintain that includes
.desktop files. If desktop-file-validate says they're OK, you don't
have to.

From sbo at linuxgalaxy.org  Sun May  1 17:12:17 2022
From: sbo at linuxgalaxy.org (KB_SBo)
Date: Sun, 01 May 2022 17:12:17 +0000
Subject: [Slackbuilds-users] apporved listed odd entry for
 thunar-archive-plugin
Message-ID: <57aa18bc-672e-e3f5-312f-ddaeb452dc04@linuxgalaxy.org>

Admins,

Hopefully just a glitch in the page display. Slackbuild column is blank,
and 'thunar-archive-plugin' listed under category.

List of submissions that have been approved and are ready for the next
update.
SlackBuild	Category	Commit	Message
	thunar-archive-plugin 	bd86d1366 	Updated for version 0.5.0.
doit 	python 	8441b97f2 	Add dependency python-importlib_metadata.
...

-Ed


From rworkman at slackbuilds.org  Sun May  1 21:08:52 2022
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 1 May 2022 16:08:52 -0500
Subject: [Slackbuilds-users] apporved listed odd entry for
 thunar-archive-plugin
In-Reply-To: <57aa18bc-672e-e3f5-312f-ddaeb452dc04@linuxgalaxy.org>
References: <57aa18bc-672e-e3f5-312f-ddaeb452dc04@linuxgalaxy.org>
Message-ID: <20220501160852.55c229ee@home.rlworkman.net>

On Sun, 01 May 2022 17:12:17 +0000
KB_SBo <sbo at linuxgalaxy.org> wrote:

> Admins,
> 
> Hopefully just a glitch in the page display. Slackbuild column is
> blank, and 'thunar-archive-plugin' listed under category.
> 
> List of submissions that have been approved and are ready for the next
> update.
> SlackBuild	Category	Commit	Message
> 	thunar-archive-plugin 	bd86d1366 	Updated for
> version 0.5.0. doit 	python 	8441b97f2 	Add
> dependency python-importlib_metadata. ...


The category wasn't in the commit message, which was absolutely my fault. Fixed now; thanks!

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220501/155e9d0f/attachment.asc>

From kjhambrick at gmail.com  Mon May  2 10:09:11 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Mon, 2 May 2022 05:09:11 -0500
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <36a64a28-edff-4d83-7f9d-375f49a9647@slackware.uk>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
 <Ym2l5SsbUDx6Ece5@localhost>
 <CANBHt+M_BXtNBsCSGa4Eisv221Ke8HLnXk7-z9NBPb3oZbFM=A@mail.gmail.com>
 <36a64a28-edff-4d83-7f9d-375f49a9647@slackware.uk>
Message-ID: <CANBHt+O74pN19SNhq9YcwntTmNO2b8=yidfziUO7mauG7kBWfg@mail.gmail.com>

On Sun, May 1, 2022 at 12:09 PM B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Sun, 1 May 2022, Konrad J Hambrick wrote:
>
> > Question:  is there a better way ( or a recommended way ) to enter long,
> > formatted
> > lists of text like NEW_CAT in the code snippet below ?
>
> There's an easier-to-read way to do the same thing: include your own
> .desktop file(s) with your SlackBuild, and overwrite the one(s) from
> 'make install' with your own:
>
> cat $CWD/$PRGNAM.desktop > $PKG/usr/share/applications/$PRGNAM.desktop
>
> I do this if the sed or whatever code that changes the .desktop gets
> to be too long or complex.
>
> <<snip>>

Thanks for the feedback B.Watson.

I like your idea a lot !

One thing I've noticed is that .desktop internationalization among the SBo
Packages is spotty at best.

This would be one way to start addressing  that 'need' -- all we need is an
army of volunteer translators :)

-- kjh(<G> I am a 'merkin and I don't need no steenkin' UTF8 <G>)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220502/0783daad/attachment.htm>

From urchlay at slackware.uk  Mon May  2 15:19:49 2022
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 2 May 2022 11:19:49 -0400 (EDT)
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <CANBHt+O74pN19SNhq9YcwntTmNO2b8=yidfziUO7mauG7kBWfg@mail.gmail.com>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
 <Ym2l5SsbUDx6Ece5@localhost>
 <CANBHt+M_BXtNBsCSGa4Eisv221Ke8HLnXk7-z9NBPb3oZbFM=A@mail.gmail.com>
 <36a64a28-edff-4d83-7f9d-375f49a9647@slackware.uk>
 <CANBHt+O74pN19SNhq9YcwntTmNO2b8=yidfziUO7mauG7kBWfg@mail.gmail.com>
Message-ID: <1b403690-d456-9af5-8536-8b44fb549024@slackware.uk>



On Mon, 2 May 2022, Konrad J Hambrick wrote:

> One thing I've noticed is that .desktop internationalization among the SBo
> Packages is spotty at best.
> 
> This would be one way to start addressing ?that 'need' -- all we need is an
> army of volunteer translators :)

Ideally, any translations in the .desktop file for a project would go
to the upstream devs, instead of just being on SBo.

I've always thought the trouble with translations is that there
aren't that many bilingual people... and even fewer tri- or more. If
I want to support 10 languages, that probably means I need 10
translators... and if it's my project and I only speak one language,
how do I verify that the translations from those 10 translators are
any good? I can take their word for it, but some people are more
micro-managerish than that.

Machine translations have improved in recent years. I wonder if any of
the big desktop environments (gnome/kde/etc) have given any thought to
auto-translating the contents of .desktop files? The results might be
worse than useless though.

From ozan.turkyilmaz at gmail.com  Mon May  2 15:36:37 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Mon, 02 May 2022 18:36:37 +0300
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <1b403690-d456-9af5-8536-8b44fb549024@slackware.uk>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
 <Ym2l5SsbUDx6Ece5@localhost>
 <CANBHt+M_BXtNBsCSGa4Eisv221Ke8HLnXk7-z9NBPb3oZbFM=A@mail.gmail.com>
 <36a64a28-edff-4d83-7f9d-375f49a9647@slackware.uk>
 <CANBHt+O74pN19SNhq9YcwntTmNO2b8=yidfziUO7mauG7kBWfg@mail.gmail.com>
 <1b403690-d456-9af5-8536-8b44fb549024@slackware.uk>
Message-ID: <5b94502faafaf4a9e814e433396644226159b665.camel@gmail.com>

Pzt, 2022-05-02 tarihinde 11:19 -0400 saatinde, B. Watson yazd?:
> Machine translations have improved in recent years. I wonder if any
> of
> the big desktop environments (gnome/kde/etc) have given any thought
> to
> auto-translating the contents of .desktop files? The results might be
> worse than useless though.
> 
Let's say if you know a language some (like basic grammar and basic
vocabulary) machine translation will give you something you edit to
useful. It can also be useful for checking the submitted translations.
I also know big vendors like MS uses machine translation to translate
their help pages into different languages.

Regards,
Ozan


From kjhambrick at gmail.com  Mon May  2 17:21:59 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Mon, 2 May 2022 12:21:59 -0500
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <1b403690-d456-9af5-8536-8b44fb549024@slackware.uk>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
 <Ym2l5SsbUDx6Ece5@localhost>
 <CANBHt+M_BXtNBsCSGa4Eisv221Ke8HLnXk7-z9NBPb3oZbFM=A@mail.gmail.com>
 <36a64a28-edff-4d83-7f9d-375f49a9647@slackware.uk>
 <CANBHt+O74pN19SNhq9YcwntTmNO2b8=yidfziUO7mauG7kBWfg@mail.gmail.com>
 <1b403690-d456-9af5-8536-8b44fb549024@slackware.uk>
Message-ID: <CANBHt+NvsfpyXrFQrZXN9gEdcFxP6Dn=y3nWet-GgCVp1c9v0A@mail.gmail.com>

On Mon, May 2, 2022 at 10:20 AM B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Mon, 2 May 2022, Konrad J Hambrick wrote:
>
> > One thing I've noticed is that .desktop internationalization among the
> SBo
> > Packages is spotty at best.
> >
> > This would be one way to start addressing  that 'need' -- all we need is
> an
> > army of volunteer translators :)
>
> Ideally, any translations in the .desktop file for a project would go
> to the upstream devs, instead of just being on SBo.
>
> Yet another great Idea, B. Watson.

I'll send the edited .desktop file to the OTB Developers :)

Problem solved, until next time :)

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220502/366468dd/attachment.htm>

From kjhambrick at gmail.com  Mon May  2 17:24:45 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Mon, 2 May 2022 12:24:45 -0500
Subject: [Slackbuilds-users] Proper Method to Categorize Desktop Apps
In-Reply-To: <5b94502faafaf4a9e814e433396644226159b665.camel@gmail.com>
References: <CANBHt+NaxtPSD-hzt3mahGEa-_F3eJc-fj-YOL=LHarT62s86g@mail.gmail.com>
 <Ym2l5SsbUDx6Ece5@localhost>
 <CANBHt+M_BXtNBsCSGa4Eisv221Ke8HLnXk7-z9NBPb3oZbFM=A@mail.gmail.com>
 <36a64a28-edff-4d83-7f9d-375f49a9647@slackware.uk>
 <CANBHt+O74pN19SNhq9YcwntTmNO2b8=yidfziUO7mauG7kBWfg@mail.gmail.com>
 <1b403690-d456-9af5-8536-8b44fb549024@slackware.uk>
 <5b94502faafaf4a9e814e433396644226159b665.camel@gmail.com>
Message-ID: <CANBHt+NZWEQ=RQXjCtGc71+-M7s-67mO5nzxfyyCNvMt3xjZqA@mail.gmail.com>

On Mon, May 2, 2022 at 10:37 AM Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>
wrote:

> Pzt, 2022-05-02 tarihinde 11:19 -0400 saatinde, B. Watson yazd?:
> > Machine translations have improved in recent years. I wonder if any
> > of
> > the big desktop environments (gnome/kde/etc) have given any thought
> > to
> > auto-translating the contents of .desktop files? The results might be
> > worse than useless though.
> >
> Let's say if you know a language some (like basic grammar and basic
> vocabulary) machine translation will give you something you edit to
> useful. It can also be useful for checking the submitted translations.
> I also know big vendors like MS uses machine translation to translate
> their help pages into different languages.
>

Ozan --

Yes, machine translations do give a good start but I don't have all the
fonts :)

Lets' see what the upstream people do with the monteverdi.desktop ( OTB )
file

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220502/bedcab2a/attachment-0001.htm>

From b.pribs11 at gmail.com  Thu May  5 01:17:50 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Wed, 4 May 2022 18:17:50 -0700
Subject: [Slackbuilds-users] uthash update
Message-ID: <CAC3J=ZbY8Vk7meUb+7qApe7BjrZsWhyqSyvko_WZh=nO_QFJ_A@mail.gmail.com>

I'm trying to reach Ulrich Shaefer who is the maintainer of uthash. I
wanted to ask if it was possible to update uthash to version 2.3.0. I'm
packaging an application that depends on uthash but fails to build with the
SBo version. I sent him an email to the address listed in the info file but
it bounced back.

Any ideas how I can reach him? Or if he's active on the mailing list?

Thanks,

Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220504/70db4fc7/attachment.htm>

From b.pribs11 at gmail.com  Thu May  5 01:19:51 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Wed, 4 May 2022 18:19:51 -0700
Subject: [Slackbuilds-users] uthash update
In-Reply-To: <CAC3J=ZbY8Vk7meUb+7qApe7BjrZsWhyqSyvko_WZh=nO_QFJ_A@mail.gmail.com>
References: <CAC3J=ZbY8Vk7meUb+7qApe7BjrZsWhyqSyvko_WZh=nO_QFJ_A@mail.gmail.com>
Message-ID: <CAC3J=ZaVzz14PF1Okucm3PN7ngnJ76y3Wm5O5-bV-jfW4KGDLQ@mail.gmail.com>

I meant he's the maintainer of the uthash slackbuild.

On Wed, May 4, 2022 at 6:17 PM Brandon Pribula <b.pribs11 at gmail.com> wrote:

> I'm trying to reach Ulrich Shaefer who is the maintainer of uthash. I
> wanted to ask if it was possible to update uthash to version 2.3.0. I'm
> packaging an application that depends on uthash but fails to build with the
> SBo version. I sent him an email to the address listed in the info file but
> it bounced back.
>
> Any ideas how I can reach him? Or if he's active on the mailing list?
>
> Thanks,
>
> Brandon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220504/09e3272f/attachment.htm>

From sbo at linuxgalaxy.org  Thu May  5 03:10:01 2022
From: sbo at linuxgalaxy.org (KB_SBo)
Date: Thu, 05 May 2022 03:10:01 +0000
Subject: [Slackbuilds-users] peer-to-peer: aMule / mldonkey , gnutella,
 soulseek, transmission-qt, etc.?
In-Reply-To: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com>
References: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com>
Message-ID: <70384ca0-4327-1cc5-7207-087fee2dbd26@linuxgalaxy.org>

On 3/17/22 20:37, 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.)

eh?  Back from where?

I have both transmission-{qt,htk} installed from SBo.  In Xfce dark
theme, transmission-gtk is dark (honors GTK theme) but -qt is not (does
not honor GTK theme)

I haven't tested on KDE5/Plasma.

-kb


From urchlay at slackware.uk  Thu May  5 06:03:08 2022
From: urchlay at slackware.uk (B. Watson)
Date: Thu, 5 May 2022 02:03:08 -0400 (EDT)
Subject: [Slackbuilds-users] peer-to-peer: aMule / mldonkey , gnutella,
 soulseek, transmission-qt, etc.?
In-Reply-To: <70384ca0-4327-1cc5-7207-087fee2dbd26@linuxgalaxy.org>
References: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com>
 <70384ca0-4327-1cc5-7207-087fee2dbd26@linuxgalaxy.org>
Message-ID: <58a7a76a-5ac6-58e2-a681-1686adb3c43@slackware.uk>



On Thu, 5 May 2022, KB_SBo wrote:

> On 3/17/22 20:37, 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.)
>
> eh?  Back from where?

For a while, there was a separate transmission-qt4 SlackBuild for
14.2, which was an older version of transmission that worked with
qt4. I removed it when we were getting ready for the 15.0 repo, and
enabled the qt5 UI in the regular transmission SlackBuild.

Later I added qt4 to SBo, but didn't re-add transmission-qt4 because I
don't see any use for it.

David Chmelik, if you want there to be a transmission-qt4 build again,
you could submit one. I'm not interested in maintaining it, but you
can if you like. You can even use the old transmission-qt4 from the
14.2 repo as a starting point: it shouldn't need much modification
(probably change "qmake" to "qmake-qt4", and add REQUIRES="qt4" and
your name/email to the .info file). Make sure it doesn't conflict with
the regular transmission package (don't use transmission-qt for the
executable filename, .desktop file, etc).

From willysr at slackbuilds.org  Thu May  5 16:55:00 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 5 May 2022 23:55:00 +0700
Subject: [Slackbuilds-users] uthash update
In-Reply-To: <CAC3J=ZbY8Vk7meUb+7qApe7BjrZsWhyqSyvko_WZh=nO_QFJ_A@mail.gmail.com>
References: <CAC3J=ZbY8Vk7meUb+7qApe7BjrZsWhyqSyvko_WZh=nO_QFJ_A@mail.gmail.com>
Message-ID: <f71a5872-9df9-5380-394a-629d8f69bbba@slackbuilds.org>

> I'm trying to reach Ulrich Shaefer who is the maintainer of uthash. I
> wanted to ask if it was possible to update uthash to version 2.3.0. I'm
> packaging an application that depends on uthash but fails to build with the
> SBo version. I sent him an email to the address listed in the info file but
> it bounced back.
> 
> Any ideas how I can reach him? Or if he's active on the mailing list?

Feel free to take over the script


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220505/0aaa42a1/attachment.asc>

From slackbuilds at schoepfer.info  Thu May  5 17:33:31 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Thu, 05 May 2022 19:33:31 +0200
Subject: [Slackbuilds-users] uthash update
In-Reply-To: <CAC3J=ZaVzz14PF1Okucm3PN7ngnJ76y3Wm5O5-bV-jfW4KGDLQ@mail.gmail.com>
References: <CAC3J=ZbY8Vk7meUb+7qApe7BjrZsWhyqSyvko_WZh=nO_QFJ_A@mail.gmail.com>
 <CAC3J=ZaVzz14PF1Okucm3PN7ngnJ76y3Wm5O5-bV-jfW4KGDLQ@mail.gmail.com>
Message-ID: <984c2022b154a286cdee07ae75d831cc@schoepfer.info>


>> Any ideas how I can reach him? Or if he's active on the mailing
>> list?

The correct mailadress might be the one from 
https://slackbuilds.org/repository/15.0/network/mrtg/ ,
updated 12 days ago.

From b.pribs11 at gmail.com  Thu May  5 19:40:13 2022
From: b.pribs11 at gmail.com (Brandon Pribula)
Date: Thu, 5 May 2022 12:40:13 -0700
Subject: [Slackbuilds-users] uthash update
In-Reply-To: <984c2022b154a286cdee07ae75d831cc@schoepfer.info>
References: <CAC3J=ZbY8Vk7meUb+7qApe7BjrZsWhyqSyvko_WZh=nO_QFJ_A@mail.gmail.com>
 <CAC3J=ZaVzz14PF1Okucm3PN7ngnJ76y3Wm5O5-bV-jfW4KGDLQ@mail.gmail.com>
 <984c2022b154a286cdee07ae75d831cc@schoepfer.info>
Message-ID: <CAC3J=ZZJ3tQw9SQXm8oGqX9XskgiKwLX7EdSLJBxB0GaEkTaaQ@mail.gmail.com>

@Willy @Franzen

Thanks for the replies. I've sent him an email to the new address and I'm
going to wait to see if he responds.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220505/89ae02da/attachment.htm>

From dominik.drobek at o2.pl  Thu May  5 23:07:01 2022
From: dominik.drobek at o2.pl (Dominik Drobek)
Date: Fri, 6 May 2022 01:07:01 +0200
Subject: [Slackbuilds-users] SoulSeek?
In-Reply-To: <3bfcc910-99ab-c910-d3ca-9ed9209ac790@gmail.com>
References: <091f33c3-2aec-6561-d983-19d6ea29c075@gmail.com>
 <9a835028-58ef-43ed-31a7-6a1baba3f510@o2.pl>
 <3bfcc910-99ab-c910-d3ca-9ed9209ac790@gmail.com>
Message-ID: <81c8530d-4c55-8b32-e1c2-da27934ccb42@o2.pl>

W dniu 25.04.2022 o?02:15, David Chmelik pisze:
> Nicotine+ never seemed to work--I guess I managed to add account but 
> wasn't able to search and/or join rooms, etc... seems far fewer features 
> than the official client.? I'd still like to see the official client 
> updated soon as I use it almost all the time.
Hi David,

I prepared an updated Slackbuild script with SELinux dependency 
workaround (attached). Could you please test it and see if it works fine 
for you?

I tested this in a very limited scope (I just checked if the application 
is starting and if it a launcher is correctly added to the menu).

Regards,
Dominik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SoulseekQt.tar
Type: application/x-tar
Size: 20480 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220506/72928b80/attachment-0001.tar>

From 1.41421 at gmail.com  Fri May  6 00:59:56 2022
From: 1.41421 at gmail.com (Luveh Keraph)
Date: Thu, 5 May 2022 18:59:56 -0600
Subject: [Slackbuilds-users] Opera not launching
Message-ID: <CAFy1yb1K24Y8vK2QpDKE5ZfevKffzEkyKBP8FxonDVTe5n6LuA@mail.gmail.com>

I upgraded the Opera browser a few days ago to the latest version in
SlackBuilds (86.0.4363.23) in my Slackware64 15.0 box. After this upgrade,
it won't launch:

$ opera
opera: symbol lookup error: opera: undefined symbol: av_stream_get_first_dts

An online search reveals that, according to some, the issue is the Opera
FFMPEG codecs. I do have the latest of such codecs from SlackBuilds, which
I upgraded last 16 March. I am a bit skeptical that this is indeed the root
cause, but I thought I'd mention it anyway.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220505/b737b661/attachment.htm>

From d.zlatanidis at gmail.com  Fri May  6 07:24:06 2022
From: d.zlatanidis at gmail.com (Dimitris Zlatanidis)
Date: Fri, 6 May 2022 10:24:06 +0300
Subject: [Slackbuilds-users] runc slackbuild failed to build
Message-ID: <4cba2fb6-1c83-7c7c-27a1-730b8d6609fd@gmail.com>

go build -trimpath "-mod=vendor" "-buildmode=pie"? -tags "seccomp" 
-ldflags "-X main.gitCommit=12644e614e25b05da6fd08a38ffa0cfe1903fdec -X 
main.version=1.0.2 " -o runc .
go build: when using gccgo toolchain, please pass linker flags using 
-gccgoflags, not -ldflags
# github.com/opencontainers/runc
/usr/bin/ld: $WORK/b001/_pkg1_.a(_cgo_defun.o): relocation R_X86_64_32 
against `.rodata' can not be used when making a PIE object; recompile 
with -fPIE
/usr/bin/ld: $WORK/b001/_pkg2_.a(_cgo_defun.o): relocation R_X86_64_32 
against `.rodata' can not be used when making a PIE object; recompile 
with -fPIE
/usr/bin/ld: $WORK/b001/_pkg3_.a(_cgo_defun.o): relocation R_X86_64_32 
against `.rodata' can not be used when making a PIE object; recompile 
with -fPIE
collect2: error: ld returned 1 exit status
make: *** [Makefile:34: runc] Error 2

Anyone who knows?

Cheers,
Dimitris

-- 
Dimitris Zlatanidis
https://dslackw.gitlab.io/slpkg/
https://gitlab.com/dslackw


From matteo.bernardini at gmail.com  Fri May  6 07:26:43 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 6 May 2022 09:26:43 +0200
Subject: [Slackbuilds-users] runc slackbuild failed to build
In-Reply-To: <4cba2fb6-1c83-7c7c-27a1-730b8d6609fd@gmail.com>
References: <4cba2fb6-1c83-7c7c-27a1-730b8d6609fd@gmail.com>
Message-ID: <CAPsDuS5mWeAMuhtpUCDPTgRyFUdPCSDhUTYSWjE6Jj0CtrnyeQ@mail.gmail.com>

hi Dimitris,

I think you haven't logged out and logged back in from your root session
after having installed google-go-lang because from your output it seems you
are still using go from gcc.

Matteo

Il giorno ven 6 mag 2022 alle ore 09:22 Dimitris Zlatanidis <
d.zlatanidis at gmail.com> ha scritto:

> go build -trimpath "-mod=vendor" "-buildmode=pie"  -tags "seccomp"
> -ldflags "-X main.gitCommit=12644e614e25b05da6fd08a38ffa0cfe1903fdec -X
> main.version=1.0.2 " -o runc .
> go build: when using gccgo toolchain, please pass linker flags using
> -gccgoflags, not -ldflags
> # github.com/opencontainers/runc
> /usr/bin/ld: $WORK/b001/_pkg1_.a(_cgo_defun.o): relocation R_X86_64_32
> against `.rodata' can not be used when making a PIE object; recompile
> with -fPIE
> /usr/bin/ld: $WORK/b001/_pkg2_.a(_cgo_defun.o): relocation R_X86_64_32
> against `.rodata' can not be used when making a PIE object; recompile
> with -fPIE
> /usr/bin/ld: $WORK/b001/_pkg3_.a(_cgo_defun.o): relocation R_X86_64_32
> against `.rodata' can not be used when making a PIE object; recompile
> with -fPIE
> collect2: error: ld returned 1 exit status
> make: *** [Makefile:34: runc] Error 2
>
> Anyone who knows?
>
> Cheers,
> Dimitris
>
> --
> Dimitris Zlatanidis
> https://dslackw.gitlab.io/slpkg/
> https://gitlab.com/dslackw
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220506/2155012f/attachment.htm>

From chris.willing at linux.com  Fri May  6 07:41:59 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Fri, 6 May 2022 17:41:59 +1000
Subject: [Slackbuilds-users] runc slackbuild failed to build
In-Reply-To: <CAPsDuS5mWeAMuhtpUCDPTgRyFUdPCSDhUTYSWjE6Jj0CtrnyeQ@mail.gmail.com>
References: <4cba2fb6-1c83-7c7c-27a1-730b8d6609fd@gmail.com>
 <CAPsDuS5mWeAMuhtpUCDPTgRyFUdPCSDhUTYSWjE6Jj0CtrnyeQ@mail.gmail.com>
Message-ID: <89e4e6bb-5745-bd36-b5f3-abf7494afcfd@linux.com>

On 6/5/22 17:26, Matteo Bernardini wrote:
> hi Dimitris,
> 
> I think you haven't logged out and logged back in from your root session
> after having installed google-go-lang because from your output it seems
> you are still using go from gcc.
> 

As suggested elsewhere, I think all packages like runc which depend on
google-go-lang should have the following line, or some approved variant,
somewhere early in the SlackBuild:

[ -z "$GOROOT" ] && source /etc/profile.d/go.sh


This will remove the need to log out and back in if the google-go-lang
installation is new - as will be the case when building in a clean VM,
which many of us do.


chris

From heiko.rosemann at web.de  Fri May  6 12:50:46 2022
From: heiko.rosemann at web.de (Heiko Rosemann)
Date: Fri, 6 May 2022 14:50:46 +0200
Subject: [Slackbuilds-users] Opera not launching
In-Reply-To: <CAFy1yb1K24Y8vK2QpDKE5ZfevKffzEkyKBP8FxonDVTe5n6LuA@mail.gmail.com>
References: <CAFy1yb1K24Y8vK2QpDKE5ZfevKffzEkyKBP8FxonDVTe5n6LuA@mail.gmail.com>
Message-ID: <877df935-875f-95fc-7a34-96cefee50362@web.de>

On 5/6/22 02:59, Luveh Keraph wrote:
> I upgraded the Opera browser a few days ago to the latest version in 
> SlackBuilds (86.0.4363.23) in my Slackware64 15.0 box. After this 
> upgrade, it won't launch:
> 
> $ opera
> opera: symbol lookup error: opera: undefined symbol: av_stream_get_first_dts
> 
> An online search reveals that, according to some, the issue is the Opera 
> FFMPEG codecs. I do have the latest of such codecs from SlackBuilds, 
> which I upgraded last 16 March. I am a bit skeptical that this is indeed 
> the root cause, but I thought I'd mention it anyway.

I can confirm this.

Removing opera-ffmpeg-codecs allows opera to launch, but then it doesn't 
play any videos any more (obviously).

Heiko

-- 
eMails verschl?sseln mit PGP - privacy is your right!
Mein PGP-Key zur Verifizierung: http://pgp.mit.edu

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220506/e2e5a196/attachment.asc>

From kjhambrick at gmail.com  Fri May  6 13:28:56 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Fri, 6 May 2022 08:28:56 -0500
Subject: [Slackbuilds-users] github URL - Content Disposition Part 3
Message-ID: <CANBHt+OgNOmWhX4nHHmOP2M2ZKo6R=JX-7WuDzLDyr0uctRB0g@mail.gmail.com>

All --

I've got still more github-related questions.

The gmic project ( https://gmic.eu/ ) was  reorganized between versions 2
and 3.

The gmic version 2.9.4 source code included the source for the zart
subproject, but now zart is in a separate github  Project ( URL =
https://github.com/c-koi/zart )

There are no tags and no versions on the zart project.

I can download zart via wget like so:

# wget https://github.com/c-koi/zart/archive/master/zart.tar.gz

This returns a viable tar archive.  However, the root directory is
zart-master/ instead of simply zart/ as the SlackBuild expects

If I `mv zart-master /tmp/SBo/gmic-3.1,0/` then the I can use the existing
gmic.SlackBuilt to create gmic-3.1.0-x86_64-1_SBo.tgz

Q1:  Does it matter that there is no version on zart ?

Q2:  Is it bad form to rename / move the contents of a tar-archive after
extracting it ?

Thanks

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220506/bd1c0096/attachment-0001.htm>

From 1.41421 at gmail.com  Fri May  6 13:42:19 2022
From: 1.41421 at gmail.com (Luveh Keraph)
Date: Fri, 6 May 2022 07:42:19 -0600
Subject: [Slackbuilds-users] Opera not launching
In-Reply-To: <877df935-875f-95fc-7a34-96cefee50362@web.de>
References: <CAFy1yb1K24Y8vK2QpDKE5ZfevKffzEkyKBP8FxonDVTe5n6LuA@mail.gmail.com>
 <877df935-875f-95fc-7a34-96cefee50362@web.de>
Message-ID: <CAFy1yb08paMp7=KedY6hzaJYuk4nYmDiGth7aa00F5_y8DhHRg@mail.gmail.com>

Using the latest version of the Opera ffmpeg codecs (0.63.1)  in the
repository, rather than the one in Slackbuilds (0.44.1) solves the problem.

On Fri, May 6, 2022 at 6:50 AM Heiko Rosemann <heiko.rosemann at web.de> wrote:

> On 5/6/22 02:59, Luveh Keraph wrote:
> > I upgraded the Opera browser a few days ago to the latest version in
> > SlackBuilds (86.0.4363.23) in my Slackware64 15.0 box. After this
> > upgrade, it won't launch:
> >
> > $ opera
> > opera: symbol lookup error: opera: undefined symbol:
> av_stream_get_first_dts
> >
> > An online search reveals that, according to some, the issue is the Opera
> > FFMPEG codecs. I do have the latest of such codecs from SlackBuilds,
> > which I upgraded last 16 March. I am a bit skeptical that this is indeed
> > the root cause, but I thought I'd mention it anyway.
>
> I can confirm this.
>
> Removing opera-ffmpeg-codecs allows opera to launch, but then it doesn't
> play any videos any more (obviously).
>
> Heiko
>
> --
> eMails verschl?sseln mit PGP - privacy is your right!
> Mein PGP-Key zur Verifizierung: http://pgp.mit.edu
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220506/bca526f3/attachment.htm>

From dave at slackbuilds.org  Fri May  6 13:48:45 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Fri, 6 May 2022 14:48:45 +0100
Subject: [Slackbuilds-users] github URL - Content Disposition Part 3
In-Reply-To: <CANBHt+OgNOmWhX4nHHmOP2M2ZKo6R=JX-7WuDzLDyr0uctRB0g@mail.gmail.com>
References: <CANBHt+OgNOmWhX4nHHmOP2M2ZKo6R=JX-7WuDzLDyr0uctRB0g@mail.gmail.com>
Message-ID: <YnUnPY3GjcpPiPaA@localhost>

On 06/05/22 08:28,
Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> All --
> I've got still more github-related questions.
> The gmic project ( https://gmic.eu/ ) was  reorganized between versions 2
> and 3.
> The gmic version 2.9.4 source code included the source for the zart
> subproject, but now zart is in a separate github  Project ( URL =
> https://github.com/c-koi/zart )
> There are no tags and no versions on the zart project.
> I can download zart via wget like so:
> # wget https://github.com/c-koi/zart/archive/master/zart.tar.gz
> This returns a viable tar archive.  However, the root directory is
> zart-master/ instead of simply zart/ as the SlackBuild expects
> If I `mv zart-master /tmp/SBo/gmic-3.1,0/` then the I can use the existing
> gmic.SlackBuilt to create gmic-3.1.0-x86_64-1_SBo.tgz
> Q1:  Does it matter that there is no version on zart ?

A definitive version is best, or it can't be verified as usable.

> Q2:  Is it bad form to rename / move the contents of a tar-archive after
> extracting it ?

A better idea is to find the latest commit hash and do something
like:

https://github.com/c-koi/zart/archive/<first 7 chars of hash>/zart-<long hash>.tar.gz

That's offhand from memory

> Thanks
> -- kjh

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From vbatts at hashbangbash.com  Fri May  6 15:32:13 2022
From: vbatts at hashbangbash.com (Vincent Batts)
Date: Fri, 6 May 2022 11:32:13 -0400
Subject: [Slackbuilds-users] runc slackbuild failed to build
In-Reply-To: <89e4e6bb-5745-bd36-b5f3-abf7494afcfd@linux.com>
References: <4cba2fb6-1c83-7c7c-27a1-730b8d6609fd@gmail.com>
 <CAPsDuS5mWeAMuhtpUCDPTgRyFUdPCSDhUTYSWjE6Jj0CtrnyeQ@mail.gmail.com>
 <89e4e6bb-5745-bd36-b5f3-abf7494afcfd@linux.com>
Message-ID: <YnU/fcTkZuwp32x3@vbatts-Lemur-Pro>

On 06/05/22 17:41 +1000, Christoph Willing wrote:
>On 6/5/22 17:26, Matteo Bernardini wrote:
>> hi Dimitris,
>>
>> I think you haven't logged out and logged back in from your root session
>> after having installed google-go-lang because from your output it seems
>> you are still using go from gcc.
>>
>
>As suggested elsewhere, I think all packages like runc which depend on
>google-go-lang should have the following line, or some approved variant,
>somewhere early in the SlackBuild:
>
>[ -z "$GOROOT" ] && source /etc/profile.d/go.sh

Good suggestion. Audrius, could you make that update?
Also, it looks like our v1.0.2 has needed updates that ought not be
breaking. Latest is v1.1.1

>This will remove the need to log out and back in if the google-go-lang
>installation is new - as will be the case when building in a clean VM,
>which many of us do.
>
>
>chris
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220506/ce3ba962/attachment.asc>

From willysr at slackbuilds.org  Sat May  7 07:19:08 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 7 May 2022 14:19:08 +0700
Subject: [Slackbuilds-users] Updates - 20220507.1
Message-ID: <4bbc2e0e-6253-1d5a-905d-2fb13e2ff50e@slackbuilds.org>

Sat May  7 07:00:10 UTC 2022
academic/boinc: Upgraded to version 7.18.1
academic/gwyddion: Updated for version 2.61.
academic/nco: Updated for version 5.0.7.
accessibility/mbrola: Added (speech synthesizer)
audio/SongRec: Added (Shazam client for linux)
audio/ncspot: Updated for version 0.9.8.
audio/pogo: Updated for version 1.0.1. New maintainer.
audio/spectmorph: Added (Analyze samples and combine them)
audio/whipper: Update DEP and README.
desktop/emwm: Added (enhanced motif window manager)
desktop/grim: Added (Grab images from a Wayland compositor)
desktop/mwm-utils: Added (utilities for emwm)
desktop/thunar-archive-plugin: Updated for version 0.5.0.
development/OpenJDK11: Updated for version 11.0.15.
development/OpenJDK17: Updated for version 17.0.3.
development/jupyter-nbclient: Updated for version 0.6.2.
development/jupyter-nbformat: Updated for version 5.4.0.
development/jupyter_server: Updated for version 1.17.0.
development/jupyterlab: Updated for version 3.4.0.
development/mutagen: Updated for version 1.45.1. New maintainer.
development/mysql-workbench: Add network warning to README.
development/pgmodeler: Fix slack-desc.
development/pycharm: Updated for version 2022.1.
development/vscodium: Updated for version 1.66.2.
games/opensurge: Added (2D retro platformer)
games/pcgen: Strip bins/libs, fix ARCH, etc.
games/protontricks: Fix doinst.sh.
games/redeclipse: Fix docs.
games/rlvm: Clean up package.
games/scid_vs_pc: Fix fonts, docs.
games/scummvm: Fix doinst.sh and docs.
games/stuntrally: Don't include 32bit libs in 64bit pkg.
games/surgescript: Added (scripting language for games)
games/ufoai: Strip shared lib.
games/waterCloset: Fix doinst and desktop nitpicks.
games/wesnoth: Strip binaries.
games/wolfmame: Added (A secure fork of MAME)
gis/gdal: Updated for version 3.4.3.
gis/python3-pyshp: Updated for version 2.3.0.
gis/python3-shapely: Updated for version 1.8.2.
graphics/graphviz: Updated for version 3.0.0.
graphics/vuescan: Updated for version 9.7.85.
libraries/hoel: Updated for version 1.4.23.
libraries/libgweather4: Added (weather library for GNOME)
libraries/libreadline-java: Updated for version 0.8.3.
libraries/mysql-connector-c++: Updated for version 8.0.29.
libraries/pylast: Updated for version 5.0.0. New maintainer.
libraries/python-ruamel: Updated for version 0.16.13.
libraries/rabbitmq-c: Fix missing backslash in script.
libraries/uthash: Updated for version 2.3.0.
libraries/xmlsec: Updated for version 1.2.34.
misc/xcape: Updated for version 1.2.
misc/yara: Updated for version 4.2.1.
multimedia/beets: Updated for version 1.6.0. New maintainer.
multimedia/plexmediaserver: Updated for v 1.26.0.5715_8cf78dab3.
multimedia/vlc: Updated for version 3.0.17.3. New maintainer.
network/brave-browser: Updated for version 1.38.111.
network/element-desktop: Updated for version 1.10.11.
network/elinks: Allow content-disposition filenames.
network/emailrelay: Updated for version 2.3.
network/glewlwyd: Updated for version 2.7.0.
network/liferea: Fix build with newer webkit2gtk.
network/microsoft-edge: Updated for version 101.0.1210.32.
network/onedrive: Updated for version 2.4.17.
network/openconnect: Updated for version 9.01.
network/qbittorrent: Updated for version 4.4.2. New maintainer.
network/qutebrowser-bin: Added (keyboard-focused browser)
network/signal-desktop: Updated for version 5.42.0.
network/social-engineer-toolkit: Removed. (Unmaintained).
network/sshguard: Updated for version 2.4.2.
network/tcpflow: Updated for version 1.6.1.
network/teams: Updated for version 1.5.00.10453.
network/tor-browser: Updated for version 11.0.11.
network/wireshark: Updated for version 3.6.5.
network/yle-dl: Updated for version 20220425.
network/zabbix_frontend: Added (distributed monitoring solution)
office/LibreOffice: Updated for version 7.3.3.2
office/MasterPDFEditor: Updated for version 5.8.52.
office/calibre-bin: Updated for version 5.42.0.
office/featherpad: Added (text editor)
office/libreoffice-helppack: Updated for version 7.3.3.
office/libreoffice-langpack: Updated for version 7.3.3.
office/libreoffice: Updated for version 7.3.3.
perl/perl-Test-Harness: Updated for versino 3.44.
python/distorm: Removed. (Renamed to python/python2-distorm).
python/doit: Add dependency python-importlib_metadata.
python/pefile: Updated for version 2021.9.3.
python/pycdio: Update source URL.
python/python2-distorm: Added (Disassembler Library)
python/python3-autobahn: Updated for version 22.4.2.
python/python3-bcrypt: updated for version 3.2.2
python/python3-filetype: Added (file type and MIME type checking)
python/python3-h11: Added (little HTTP/1.1 library in Python)
python/python3-httpcore: Added (a minimal low-level HTTP client)
python/python3-httpx: Added (A next-gen HTTP client for Python)
python/python3-rfc3986: Added (validation and authority parsing)
ruby/ruby-build: Updated for version 20220426.
system/arqiver: Added (Simple Qt archive manager)
system/binfmt-support: Update HOMEPAGE.
system/bitrot: Updated for version 1.0.0.
system/bulk_extractor: Fix 32bit build.
system/jenkins: Updated for version 2.332.3.
system/letsencrypt: Updated for version 1.27.0.
system/mhddfs: Update email.
system/redis: updated for version 7.0.0
system/sakura: Updated for version 3.8.5.
system/swtpm: Fix 32bit build.
system/telegraf: Updated for version 1.22.3.
system/xen: Add logic for sysconfig *enhanced* systems.
system/zzzfm: Added (Multi-panel tabbed file manager)
+--------------------------+


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220507/e6311360/attachment.asc>

From slackbuilds at schoepfer.info  Sat May  7 20:40:57 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 07 May 2022 22:40:57 +0200
Subject: [Slackbuilds-users] Fwd: sbo-maintainer-tools 50-icons
In-Reply-To: <ca1ea74743c65ae6947092e04caf0643@schoepfer.info>
References: <ca1ea74743c65ae6947092e04caf0643@schoepfer.info>
Message-ID: <c220399fb8bd71edd224f493cafb319b@schoepfer.info>

Hi,

as i got no feedback, i'll try over this list:

-------- Original Message --------
Subject: sbo-maintainer-tools 50-icons
Date: 2022-04-28 19:38
 From: Franzen <slackbuilds at schoepfer.info>
To: yalhcru at gmail.com

Hi B.Watson,

here is a small nitpick patch for 50-icons pkg lint.

Cheers,

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 50-icons.patch
Type: text/x-diff
Size: 457 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220507/7da79e40/attachment.bin>

From dpross1100 at msn.com  Sun May  8 03:25:53 2022
From: dpross1100 at msn.com (Daniel Prosser)
Date: Sat, 7 May 2022 23:25:53 -0400
Subject: [Slackbuilds-users] KiCad not loading symbols
Message-ID: <SN6PR03MB3536683C86CE64D5C03EF8ECCCC79@SN6PR03MB3536.namprd03.prod.outlook.com>

Hello,


Hopefully someone knows something about KiCad and can tell me what I'm 
doing wrong. I am a complete novice trying to learn how to use it. I 
installed it from SBo along with all dependencies as well as most of the 
extra packages (kicad-symbols, kicad-templates, kicad-footprints, 
skipped kicad-packages3D because it's so huge), but when I go to insert 
a symbol in the schematic editor, there are none available. I checked in 
the preferences and it does have the relevant environment variable 
pointing to /usr/share/kicad/library, where kicad-symbols installs the 
files, but it still doesn't "see" them there. Also, there were no 
symbols installed by the base kicad package; I'm not sure if that is 
expected or not.

Am I missing some simple step to load the symbols library, or did 
something go wrong with the build?


Thanks,

Dan



From dickson.tim at googlemail.com  Sun May  8 07:02:33 2022
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Sun, 8 May 2022 08:02:33 +0100
Subject: [Slackbuilds-users] KiCad not loading symbols
In-Reply-To: <SN6PR03MB3536683C86CE64D5C03EF8ECCCC79@SN6PR03MB3536.namprd03.prod.outlook.com>
References: <SN6PR03MB3536683C86CE64D5C03EF8ECCCC79@SN6PR03MB3536.namprd03.prod.outlook.com>
Message-ID: <bba4900d-51a7-dc0f-f4f2-61483e947999@googlemail.com>

Hi Dan, when you first run kicad you need to create a project (this is 
directory and main file). then you need to start with the schematic 
editor, and kicad will ask for the locations of the files, giving you 
the option to copy the default global symbol table, which you should do 
(because the slackware packages install global data files, and kicad 
expects each user to use their own copy)

Now you can place devices on the schematic, and power rails and 
connections between them. (that works fine on mine)
then you need to set the footprints for each device (the physical sizes 
of the devices). Finally, you can open the pcb editor, and load in your 
schematic. you can then place the devices, and sort out the routing etc.
If you did the kicad-packages-3D then you are also able to view a 
preview of your circuit board in 3d.

I didn't have to set any environment variables or do anything special. 
(at least to get as far as the schematic editor and adding parts from 
the library)

Regards, Tim

On 08/05/2022 04:25, Daniel Prosser wrote:
> Hello,
>
>
> Hopefully someone knows something about KiCad and can tell me what I'm 
> doing wrong. I am a complete novice trying to learn how to use it. I 
> installed it from SBo along with all dependencies as well as most of 
> the extra packages (kicad-symbols, kicad-templates, kicad-footprints, 
> skipped kicad-packages3D because it's so huge), but when I go to 
> insert a symbol in the schematic editor, there are none available. I 
> checked in the preferences and it does have the relevant environment 
> variable pointing to /usr/share/kicad/library, where kicad-symbols 
> installs the files, but it still doesn't "see" them there. Also, there 
> were no symbols installed by the base kicad package; I'm not sure if 
> that is expected or not.
>
> Am I missing some simple step to load the symbols library, or did 
> something go wrong with the build?
>
>
> Thanks,
>
> Dan
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


-- 
This email has been checked for viruses by AVG.
https://www.avg.com


From urchlay at slackware.uk  Sun May  8 15:24:06 2022
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 8 May 2022 11:24:06 -0400 (EDT)
Subject: [Slackbuilds-users] Fwd: sbo-maintainer-tools 50-icons
In-Reply-To: <c220399fb8bd71edd224f493cafb319b@schoepfer.info>
References: <ca1ea74743c65ae6947092e04caf0643@schoepfer.info>
 <c220399fb8bd71edd224f493cafb319b@schoepfer.info>
Message-ID: <49f7a0a-b268-653b-7cc-751d74a2bd67@slackware.uk>



On Sat, 7 May 2022, Franzen via SlackBuilds-users wrote:

> Hi,
>
> as i got no feedback, i'll try over this list:

D'oh!

Sorry, I'm in the process of changing my email address and had forgot
to change the one in my ~/.gitconfig. The address I'm replying from
now is the correct one... I haven't changed email addresses in almost
20 years so I'm kinda out of practice.

Now I wonder how much other sbopkglint-related mail I've missed... the
old account still works, for now, but I haven't checked it in a week.
Mea culpa.

> here is a small nitpick patch for 50-icons pkg lint.

Thanks! I might also change the "incorrectly sized (or named)" to read
"incorrectly sized (or in wrong dir)". Saying it's "incorrectly named"
might be confusing (actually not "might be", someone on IRC asked about
it just now).

Maybe re-word it thus:

warn "Icon $f is $actualsize, but is in a directory named .../$size/..."

From bgrundy at gmail.com  Sun May  8 21:40:54 2022
From: bgrundy at gmail.com (Barry J. Grundy)
Date: Sun, 8 May 2022 17:40:54 -0400
Subject: [Slackbuilds-users] Volatility/pythonX-yara
Message-ID: <df3a9e8b-dd02-1a64-c11c-760389d352d7@gmail.com>

Good Afternoon,

I'm trying to submit the following updates (via SBo form):

python2-yara  (update/rename/split)
volatility    (fix dependency name changes[python2-distorm and 
python2-yara])

python3-yara  (update/rename/split)
volatility3   (added-rewrite of volatility framework)


I cannot get the pythonX-yara submissions to upload because it says they 
are already in pending (they are not).  And there is already a package 
in pending for volatility that fixes only one of the dependency names (I 
did not submit that change).

I may have screwed something up, but I had submitted all of the above 
last week and they were rejected because neither python-yara package 
would build against the older yara already in 15.0, even though the 
correct version of yara was submitted along side them (and was 
approved).  Did I miss something?

Thanks,
Barry


From dpross1100 at msn.com  Sun May  8 22:02:30 2022
From: dpross1100 at msn.com (Daniel Prosser)
Date: Sun, 8 May 2022 18:02:30 -0400
Subject: [Slackbuilds-users] KiCad not loading symbols
In-Reply-To: <bba4900d-51a7-dc0f-f4f2-61483e947999@googlemail.com>
References: <SN6PR03MB3536683C86CE64D5C03EF8ECCCC79@SN6PR03MB3536.namprd03.prod.outlook.com>
 <bba4900d-51a7-dc0f-f4f2-61483e947999@googlemail.com>
Message-ID: <SN6PR03MB3536C5F7E2D4B4B93929E558CCC79@SN6PR03MB3536.namprd03.prod.outlook.com>

Hi Tim,

I think the trick was that I had to delete ~/.config/kicad, and then the 
next time I started it up, it gave me the option to copy over the global 
symbols table. Thanks for the pointers!

Dan

On 5/8/22 03:02, Tim Dickson via SlackBuilds-users wrote:
> Hi Dan, when you first run kicad you need to create a project (this is 
> directory and main file). then you need to start with the schematic 
> editor, and kicad will ask for the locations of the files, giving you 
> the option to copy the default global symbol table, which you should 
> do (because the slackware packages install global data files, and 
> kicad expects each user to use their own copy)
>
> Now you can place devices on the schematic, and power rails and 
> connections between them. (that works fine on mine)
> then you need to set the footprints for each device (the physical 
> sizes of the devices). Finally, you can open the pcb editor, and load 
> in your schematic. you can then place the devices, and sort out the 
> routing etc.
> If you did the kicad-packages-3D then you are also able to view a 
> preview of your circuit board in 3d.
>
> I didn't have to set any environment variables or do anything special. 
> (at least to get as far as the schematic editor and adding parts from 
> the library)
>
> Regards, Tim
>
> On 08/05/2022 04:25, Daniel Prosser wrote:
>> Hello,
>>
>>
>> Hopefully someone knows something about KiCad and can tell me what 
>> I'm doing wrong. I am a complete novice trying to learn how to use 
>> it. I installed it from SBo along with all dependencies as well as 
>> most of the extra packages (kicad-symbols, kicad-templates, 
>> kicad-footprints, skipped kicad-packages3D because it's so huge), but 
>> when I go to insert a symbol in the schematic editor, there are none 
>> available. I checked in the preferences and it does have the relevant 
>> environment variable pointing to /usr/share/kicad/library, where 
>> kicad-symbols installs the files, but it still doesn't "see" them 
>> there. Also, there were no symbols installed by the base kicad 
>> package; I'm not sure if that is expected or not.
>>
>> Am I missing some simple step to load the symbols library, or did 
>> something go wrong with the build?
>>
>>
>> Thanks,
>>
>> Dan
>>
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>
>

From dave at slackbuilds.org  Sun May  8 22:09:29 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 8 May 2022 23:09:29 +0100
Subject: [Slackbuilds-users] Volatility/pythonX-yara
In-Reply-To: <df3a9e8b-dd02-1a64-c11c-760389d352d7@gmail.com>
References: <df3a9e8b-dd02-1a64-c11c-760389d352d7@gmail.com>
Message-ID: <Yng/mRTZSOjX5mXv@localhost>

On 08/05/22 17:40,
Barry J. Grundy <bgrundy at gmail.com> put forth the proposition:
> Good Afternoon,
> I'm trying to submit the following updates (via SBo form):
> python2-yara  (update/rename/split)
> volatility    (fix dependency name changes[python2-distorm and
> python2-yara])
> python3-yara  (update/rename/split)
> volatility3   (added-rewrite of volatility framework)
> I cannot get the pythonX-yara submissions to upload because it says they are
> already in pending (they are not).  And there is already a package in
> pending for volatility that fixes only one of the dependency names (I did
> not submit that change).
> I may have screwed something up, but I had submitted all of the above last
> week and they were rejected because neither python-yara package would build
> against the older yara already in 15.0, even though the correct version of
> yara was submitted along side them (and was approved).  Did I miss
> something?
> Thanks,
> Barry

Hi Barry

Can you try now please?

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From dchmelik at gmail.com  Mon May  9 07:06:52 2022
From: dchmelik at gmail.com (David Chmelik)
Date: Mon, 9 May 2022 00:06:52 -0700
Subject: [Slackbuilds-users] policy request: don't alter/overwrite system
 files without consent!
Message-ID: <f06203f1-5915-9d7b-f984-7908c222a389@gmail.com>

I request SBo policy is SlackBuilds don't alter/overwrite system 
files/symlinks without asking; providing alternatives is fine, but I've 
had many horrible experiences with this over years.
 ??????? A recent critical offender is dropbear SSH(D.)? I installed to 
try alternative SSH client then found it overwrites Slackware's sshd and 
I could no longer remotely connect (had to go there physically)--this is 
/extremely/ bad (README doesn't even warn you!: ) let user/sysadmin 
decide if they want to replace such things themselves (/after/ 
installing) or just try out!
 ??????? Another problem for years was several/many fonts, which got so 
bad I simply quit installing fonts from SBo but would like to again... 
what several do is overwrite system font configuration, then when I 
opened programs such as a text editor, default fonts had been replaced 
with ones that shrunk to unreadable size... again, let user/sysadmin 
decide if they want to replace such things themselves (/after/ 
installing) or just try out! (I doubt font READMEs said they'd replace 
defaults either.)? Font configuration overwrite was also critically bad 
for me, because I didn't know there was font configuration and couldn't 
find out what happened (even asking several experts) so thought 
Slackware broke, so I ended up doing an OS drive format (took a day w/dd 
on SSD, maybe before blkdiscard appeared) and fresh installation, losing 
part of a week of time... remember if someone installs a font, it 
usually doesn't mean they want to replace default system font 
configuration--give them instructions for that, sure, but don't make 
unwarranted assumptions that cause problems!
 ??????? Alternative csh is an example of few that may do this right: it 
offers alternative csh.login and it's made pretty clear (in the file, 
though I don't recall if slackpkg new-config just offers overwrite)... 
sad that it appears it isn't the majority of builds that do this right, 
on something as strictly Unix-like as Slackware!

From urchlay at slackware.uk  Mon May  9 15:27:36 2022
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 9 May 2022 11:27:36 -0400 (EDT)
Subject: [Slackbuilds-users] policy request: don't alter/overwrite
 system files without consent!
In-Reply-To: <f06203f1-5915-9d7b-f984-7908c222a389@gmail.com>
References: <f06203f1-5915-9d7b-f984-7908c222a389@gmail.com>
Message-ID: <2de653-2c59-3831-f3f6-86346751cb8@slackware.uk>



On Mon, 9 May 2022, David Chmelik wrote:

> I request SBo policy is SlackBuilds don't alter/overwrite system 
> files/symlinks without asking; providing alternatives is fine, but I've 
> had many horrible experiences with this over years.

That actually *is* SBo policy. Any build that doesn't follow it, is
broken, and you should report the issue to the maintainer (or to the
mailing list).

> ??????? A recent critical offender is dropbear SSH(D.)? I installed to 
> try alternative SSH client then found it overwrites Slackware's sshd and 
> I could no longer remotely connect (had to go there physically)--this is 
> /extremely/ bad (README doesn't even warn you!: ) let user/sysadmin 
> decide if they want to replace such things themselves (/after/ 
> installing) or just try out!

Hm, how long ago was that, what version of dropbear? The one we
currently have in the repo doesn't do this (I just checked).

> ??????? Another problem for years was several/many fonts, which got so 
> bad I simply quit installing fonts from SBo but would like to again... 
> what several do is overwrite system font configuration, then when I 
> opened programs such as a text editor, default fonts had been replaced 
> with ones that shrunk to unreadable size...

Can you tell us which font builds caused this problem? Email the
maintainers of those builds explaining the issue.

> Font configuration overwrite was also critically bad 
> for me, because I didn't know there was font configuration and couldn't

Removing the offending font packages didn't fix the problem? Also
after removal, run "fc-cache -f" as root (or just reboot; the boot
scripts run this for you).

> ??????? Alternative csh is an example of few that may do this right: it 
> offers alternative csh.login and it's made pretty clear (in the file, 
> though I don't recall if slackpkg new-config just offers overwrite)...

slackpkg new-config offers the same options for all config
files. Including the option to diff the old & new files, which would
show you the comments in the replacement csh.login.

> sad that it appears it isn't the majority of builds that do this right, 
> on something as strictly Unix-like as Slackware!

Did you contact the maintainers of the builds you found that caused
problems? That's what they're there for...

From davidnchmelik at gmail.com  Tue May 10 07:21:14 2022
From: davidnchmelik at gmail.com (David Chmelik)
Date: Tue, 10 May 2022 00:21:14 -0700
Subject: [Slackbuilds-users] policy request: don't alter/overwrite
 system files without consent!
In-Reply-To: <2de653-2c59-3831-f3f6-86346751cb8@slackware.uk>
References: <f06203f1-5915-9d7b-f984-7908c222a389@gmail.com>
 <2de653-2c59-3831-f3f6-86346751cb8@slackware.uk>
Message-ID: <7938c3cf-087f-353b-20c6-623b293b420e@gmail.com>

On 5/9/22 8:27 AM, B. Watson wrote:
> On Mon, 9 May 2022, David Chmelik wrote:
>> [...] ? A recent critical offender is dropbear SSH(D.)? I installed 
>> to try alternative SSH client then found it overwrites Slackware's 
>> sshd and I could no longer remotely connect (had to go there 
>> physically)--this is /extremely/ bad (README doesn't even warn you!: 
>> ) let user/sysadmin decide if they want to replace such things 
>> themselves (/after/ installing) or just try out!
>
> Hm, how long ago was that, what version of dropbear? The one we 
> currently have in the repo doesn't do this (I just checked).
Recent years to earlier 2022 but now I verified fixed.

>> ??????? Another problem for years was several/many fonts, which got 
>> so bad I simply quit installing fonts from SBo but would like to 
>> again... what several do is overwrite system font configuration, then 
>> when I opened programs such as a text editor, default fonts had been 
>> replaced with ones that shrunk to unreadable size...
>
> Can you tell us which font builds caused this problem? Email the 
> maintainers of those builds explaining the issue.
That year, stress of reinstalling caused me give up fonts; maybe someday.

>> Font configuration overwrite was also critically bad for me, because 
>> I didn't know there was font configuration and couldn't
>
> Removing the offending font packages didn't fix the problem?
I doubt, but hard to know wasn't Slackware bug, because not 
configuration I set.? If it overwrote, confusing/risky in contrast to 
Unix (FreeBSD, etc.) local/extra/unofficial packages go in 
/usr/local/{bin|etc|lib}... ? Apparently problem likely was n-font.conf 
files, n less than default, loaded in order; possibly didn't overwrite 
system but 'got in front:' equally bad (should go to optional directory 
(may exist for fonts) or /usr/doc/font sample/example configuration one 
can /choose/.)? There are approaching 50 /etc/fonts/conf.d/*.conf and 
approaching 100 /etc/fonts/conf.avail/*.conf, some approaching 10KB, so 
was exhausting debugging.

> Also after removal, run "fc-cache -f" as root (or just reboot; the 
> boot scripts run this for you).
I started doing that after installation but don't plan to remove any (if 
I try extras again, after these years, it'll possibly be easier to 
figure out what happened.)


From ozan.turkyilmaz at gmail.com  Tue May 10 08:26:37 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Tue, 10 May 2022 11:26:37 +0300
Subject: [Slackbuilds-users] policy request: don't alter/overwrite
 system files without consent!
In-Reply-To: <2de653-2c59-3831-f3f6-86346751cb8@slackware.uk>
References: <f06203f1-5915-9d7b-f984-7908c222a389@gmail.com>
 <2de653-2c59-3831-f3f6-86346751cb8@slackware.uk>
Message-ID: <8b605cbbfe4b9942589aeccb93afea46f5842d77.camel@gmail.com>

Pzt, 2022-05-09 tarihinde 11:27 -0400 saatinde, B. Watson yazd?:
> 
> 
> On Mon, 9 May 2022, David Chmelik wrote:
> 
> > I request SBo policy is SlackBuilds don't alter/overwrite system 
> > files/symlinks without asking; providing alternatives is fine, but
> > I've 
> > had many horrible experiences with this over years.
> 
> That actually *is* SBo policy. Any build that doesn't follow it, is
> broken, and you should report the issue to the maintainer (or to the
> mailing list).

This policy talk reminded me to ask where is the policy files stored?
It's always good thing to look at them time to time.

Regards,
Ozan

From rworkman at slackbuilds.org  Wed May 11 04:21:19 2022
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 10 May 2022 23:21:19 -0500
Subject: [Slackbuilds-users] policy request: don't alter/overwrite
 system files without consent!
In-Reply-To: <f06203f1-5915-9d7b-f984-7908c222a389@gmail.com>
References: <f06203f1-5915-9d7b-f984-7908c222a389@gmail.com>
Message-ID: <20220510232119.5df76a78@home.rlworkman.net>

On Mon, 9 May 2022 00:06:52 -0700
David Chmelik <dchmelik at gmail.com> wrote:

> I request SBo policy is SlackBuilds don't alter/overwrite system 
> files/symlinks without asking; providing alternatives is fine, but
> I've had many horrible experiences with this over years.


That is and has been our policy since the beginning.


>  ??????? A recent critical offender is dropbear SSH(D.)? I installed
> to try alternative SSH client then found it overwrites Slackware's
> sshd and I could no longer remotely connect (had to go there
> physically)--this is /extremely/ bad (README doesn't even warn you!:
> ) let user/sysadmin decide if they want to replace such things
> themselves (/after/ installing) or just try out!


I am not convinced. I just spent quite a few minutes looking at 
every git commit since dropbear was added to the SBo repo.
What I found was that scp could have been overwritten, but it
was not the default *and* there was a warning in README.
If you built dropbear using the sources for the Slackware installer,
then you would overwrite the ssh binary but still not the sshd
binary.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220510/22c245d1/attachment.asc>

From fourtysixandtwo at sliderr.net  Wed May 11 23:24:29 2022
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Wed, 11 May 2022 17:24:29 -0600
Subject: [Slackbuilds-users] eyeD3 slackbuild
In-Reply-To: <CAAZ8Hain2KjC1e6YDCCLbSg4JYszAzJHrNKk7ewiii23kDYSrg@mail.gmail.com>
References: <CAAZ8Haj5kBMaq0WLs4hxuR3v8hPk9vPPvcJ2MHk7cBnqBTQjxQ@mail.gmail.com>
 <CAAZ8Haj4Bpxzhd02LyzoRo0XZ9gyPEbE_uHhxxx2o8mSqzziHw@mail.gmail.com>
 <CAAZ8Hain2KjC1e6YDCCLbSg4JYszAzJHrNKk7ewiii23kDYSrg@mail.gmail.com>
Message-ID: <CAAZ8Hag4d6hM-uj-0LY+7k-f+gk+hHU1JZBERw3bdhDy9W5k0w@mail.gmail.com>

Hi all,

I found eyeD3 was broken while testing updates to pylast.  I've emailed
Larry a couple of times in the last 10 days but he hasn't responded.

I've attached both format-patches I have for eyeD3.

Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220511/9ca8732e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0124-audio-eyeD3-Change-i486-to-i586.patch
Type: application/x-patch
Size: 708 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220511/9ca8732e/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0007-audio-eyeD3-Fix-REQUIRES.patch
Type: application/x-patch
Size: 779 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220511/9ca8732e/attachment-0001.bin>

From alik at ejik.org  Thu May 12 01:29:14 2022
From: alik at ejik.org (Alexander Verbovetsky)
Date: Thu, 12 May 2022 04:29:14 +0300
Subject: [Slackbuilds-users] scripts for grab or remove
Message-ID: <Ynxi6mTqP3XPGmH/@mail.ejik.org>

Hello,

I'd like to make available the following Slackbuilds I no longer use:
pdfstudio
pdfstudioviewer
poster
prosody-mod-block-strangers
reduce-algebra

Also, I suggest to remove these two scripts:
sendxmpp
UDR

Both of them are long abandoned. sendxmpp doesn't work anymore. There
are many alternatives, one of them, go-sendxmpp, I submitted to SBo.

UDR is a great program that makes rsync 2-3 times faster in some
situations. But now it's not needed, the kernel settings
net.core.default_qdisc=fq
net.ipv4.tcp_congestion_control=bbr
(on the sender side) do the same and even better.

Best regards,
Alexander

From andrew.clemons at gmail.com  Thu May 12 21:46:06 2022
From: andrew.clemons at gmail.com (Andrew Clemons)
Date: Fri, 13 May 2022 09:46:06 +1200
Subject: [Slackbuilds-users] scripts for grab or remove
In-Reply-To: <Ynxi6mTqP3XPGmH/@mail.ejik.org>
References: <Ynxi6mTqP3XPGmH/@mail.ejik.org>
Message-ID: <47b3128a-5824-6c52-a408-9401e5e16eb8@gmail.com>

On 12/05/22 13:29, Alexander Verbovetsky wrote:
> Hello,
> 
> I'd like to make available the following Slackbuilds I no longer use:
> [...]
> prosody-mod-block-strangers

I'll take this one.

From rcb at beco.cc  Fri May 13 00:00:10 2022
From: rcb at beco.cc (Ruben Carlo Benante)
Date: Thu, 12 May 2022 21:00:10 -0300
Subject: [Slackbuilds-users] NVIDIA open sources drivers
Message-ID: <3446573.dWV9SEqChM@marvin>

Hello there guys, and specially nouveau maintainers and beautiful people that makes video 
card drivers under linux,

I just got this news 

https://github.com/NVIDIA/open-gpu-kernel-modules[1]

NVIDIA opened its kernel modules source. From the news , it speculates NVIDIA will open 
source its drivers.

At this stage, it is still dependent on proprietary firmware. But being that it is a fresh breaking 
news, we can't expect much immediately. Lets see what comes up the next months.

I'll wait to see, before any commemoration, but I think it is a step forward.

What do you guys think about it? Are you optimist?

And from what is already open, do you think it will impact the quality of the drivers we 
already have?

I hope so.

Best,
Dr. B?co

PS. Some references:

* https://hothardware.com/news/nvidia-open-source-gpu-kernel-drivers[2]
* https://www.pcgamer.com/the-unthinkable-has-happened-nvidia-has-finally-embraced-open-source-gpu-drivers/[3]

-- 
Dr. B?co
AI researcher

"As I grow older, I pay less attention to what men say. I just watch what they do." (Carnegie)

Essa mensagem ? destinada exclusivamente ao seu destinat?rio e pode conter informa??es 
confidenciais, protegidas por sigilo profissional, direitos autorais reservados, ou cuja 
divulga??o seja proibida por lei. O uso n?o autorizado de tais informa??es ? proibido e est? 
sujeito ?s penalidades cab?veis.

This message is intended exclusively for its addressee and may contain information that is 
confidential and protected by a professional privilege, reserved copyright, or whose 
disclosure is prohibited by law. Unauthorised use of such information is prohibited and 
subject to applicable penalties.

--------
[1] https://github.com/NVIDIA/open-gpu-kernel-modules
[2] https://hothardware.com/news/nvidia-open-source-gpu-kernel-drivers
[3] https://www.pcgamer.com/the-unthinkable-has-happened-nvidia-has-finally-embraced-open-source-gpu-drivers/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220512/0ab1b19b/attachment.htm>

From rcb at beco.cc  Fri May 13 00:04:53 2022
From: rcb at beco.cc (Ruben Carlo Benante)
Date: Thu, 12 May 2022 21:04:53 -0300
Subject: [Slackbuilds-users] NVIDIA open sources drivers
In-Reply-To: <3446573.dWV9SEqChM@marvin>
References: <3446573.dWV9SEqChM@marvin>
Message-ID: <6769945.9J7NaK4W3v@marvin>

On Thursday, 12 May 2022 21:00:10 -03 you wrote:
> Hello there guys, and specially nouveau maintainers and beautiful people
> that makes video card drivers under linux,
> 
> I just got this news
> 
> https://github.com/NVIDIA/open-gpu-kernel-modules[1]
>  [cut...]
> PS. Some references:
> 
> * https://hothardware.com/news/nvidia-open-source-gpu-kernel-drivers[2]
> *
> https://www.pcgamer.com/the-unthinkable-has-happened-nvidia-has-finally-emb
> raced-open-source-gpu-drivers/[3]

ofc, the official announcement here:

* https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/[1]

Beco



--------
[1] https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220512/7cb26af6/attachment.htm>

From ozan.turkyilmaz at gmail.com  Fri May 13 05:42:21 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Fri, 13 May 2022 08:42:21 +0300
Subject: [Slackbuilds-users] NVIDIA open sources drivers
In-Reply-To: <3446573.dWV9SEqChM@marvin>
References: <3446573.dWV9SEqChM@marvin>
Message-ID: <5b14bedd6f95d2c646969eebbbba19cecb36af0e.camel@gmail.com>

Pr?, 2022-05-12 tarihinde 21:00 -0300 saatinde, Ruben Carlo Benante via
SlackBuilds-users yazd?:
> Hello there guys, and specially nouveau maintainers and beautiful
> people that makes video card drivers under linux,
> 
> I just got this news 
> 

nouveau people probably are already digging into the source by now. It
will be helpful for them to better?
their kernel modules and the other sections indirectly. Let's hope they
will open up the rest of the drivers.
Also, I don't think nouveau will stop if NVidia opens up their drivers
fully. Their work is important as an alternative.

Regards,
Ozan?


From dave at slackbuilds.org  Sat May 14 02:30:48 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sat, 14 May 2022 03:30:48 +0100
Subject: [Slackbuilds-users] eyeD3 slackbuild
In-Reply-To: <CAAZ8Hag4d6hM-uj-0LY+7k-f+gk+hHU1JZBERw3bdhDy9W5k0w@mail.gmail.com>
References: <CAAZ8Haj5kBMaq0WLs4hxuR3v8hPk9vPPvcJ2MHk7cBnqBTQjxQ@mail.gmail.com>
 <CAAZ8Haj4Bpxzhd02LyzoRo0XZ9gyPEbE_uHhxxx2o8mSqzziHw@mail.gmail.com>
 <CAAZ8Hain2KjC1e6YDCCLbSg4JYszAzJHrNKk7ewiii23kDYSrg@mail.gmail.com>
 <CAAZ8Hag4d6hM-uj-0LY+7k-f+gk+hHU1JZBERw3bdhDy9W5k0w@mail.gmail.com>
Message-ID: <Yn8UWHxBccbvT9aJ@localhost>

On 11/05/22 17:24,
fourtysixandtwo <fourtysixandtwo at sliderr.net> put forth the proposition:
> Hi all,
> I found eyeD3 was broken while testing updates to pylast.  I've emailed
> Larry a couple of times in the last 10 days but he hasn't responded.
> I've attached both format-patches I have for eyeD3.
> Cheers

Hi

Can you make a single patch of the whole folder next time please?

Thanks

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From dave at slackbuilds.org  Sat May 14 02:52:11 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sat, 14 May 2022 03:52:11 +0100
Subject: [Slackbuilds-users] eyeD3 slackbuild
In-Reply-To: <Yn8UWHxBccbvT9aJ@localhost>
References: <CAAZ8Haj5kBMaq0WLs4hxuR3v8hPk9vPPvcJ2MHk7cBnqBTQjxQ@mail.gmail.com>
 <CAAZ8Haj4Bpxzhd02LyzoRo0XZ9gyPEbE_uHhxxx2o8mSqzziHw@mail.gmail.com>
 <CAAZ8Hain2KjC1e6YDCCLbSg4JYszAzJHrNKk7ewiii23kDYSrg@mail.gmail.com>
 <CAAZ8Hag4d6hM-uj-0LY+7k-f+gk+hHU1JZBERw3bdhDy9W5k0w@mail.gmail.com>
 <Yn8UWHxBccbvT9aJ@localhost>
Message-ID: <Yn8ZW9xDVTYHMFhZ@localhost>

On 14/05/22 03:30,
Dave Woodfall <dave at slackbuilds.org> put forth the proposition:
> On 11/05/22 17:24,
> fourtysixandtwo <fourtysixandtwo at sliderr.net> put forth the proposition:
> > Hi all,
> > I found eyeD3 was broken while testing updates to pylast.  I've emailed
> > Larry a couple of times in the last 10 days but he hasn't responded.
> > I've attached both format-patches I have for eyeD3.
> > Cheers
> Hi
> Can you make a single patch of the whole folder next time please?
> Thanks

In fact Willy made a good blog post on how to make patches to send to
the list:

https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html

Could you also put [PATCH] at the start of the message subject too,
so it's more obvious there is one.

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From fourtysixandtwo at sliderr.net  Sat May 14 03:17:30 2022
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Fri, 13 May 2022 21:17:30 -0600
Subject: [Slackbuilds-users] werkzeug, click, and Flask upgrades
Message-ID: <CAAZ8HahzosesBNZRBw2GpLgtu_n=DRC+hjXveE4omOAoOVwm4w@mail.gmail.com>

Hi all,

I uploaded upgrades today along with two legacy builds, werkzeug-legacy1
and click-legacy7.

Since these upgrades have many dependant slackbuilds (51 in total), I'd
like to give an update on the result of my testing.  If you're a maintainer
of one of those builds, you'll be getting an email from me in the next
couple days.

-the following builds were already non-functional
  network/FireWorks (upgrade available, but needs work)
  network/flexget (upgrade available, but needs a lot of work)
  python/odoo (upgrade available, but needs work and a form filled out to
download)
  python/Flask-Security (unmaintained, but there's an updated fork)
  python/flask-restplus (unmaintained, but there's a replacement)
-the following need to use the legacy builds as specified to work
  network/onionshare  (werkzeug-legacy1)
  python/Kallithea  (click-legacy7)
  gis/gj2ascii  (click-legacy7)
  office/watson  (click-legacy7)
-everything else I have a patch for to get working and passes a rudimentary
functional test
  -most of the Flask related builds are python2 and Jinja2 (now included in
15) is only python3.
  -majority are easily fixed by adding python3 to the build and an updated
version.

Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220513/7440ea0e/attachment-0001.htm>

From fourtysixandtwo at sliderr.net  Sat May 14 03:22:35 2022
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Fri, 13 May 2022 21:22:35 -0600
Subject: [Slackbuilds-users] eyeD3 slackbuild
In-Reply-To: <Yn8ZW9xDVTYHMFhZ@localhost>
References: <CAAZ8Haj5kBMaq0WLs4hxuR3v8hPk9vPPvcJ2MHk7cBnqBTQjxQ@mail.gmail.com>
 <CAAZ8Haj4Bpxzhd02LyzoRo0XZ9gyPEbE_uHhxxx2o8mSqzziHw@mail.gmail.com>
 <CAAZ8Hain2KjC1e6YDCCLbSg4JYszAzJHrNKk7ewiii23kDYSrg@mail.gmail.com>
 <CAAZ8Hag4d6hM-uj-0LY+7k-f+gk+hHU1JZBERw3bdhDy9W5k0w@mail.gmail.com>
 <Yn8UWHxBccbvT9aJ@localhost> <Yn8ZW9xDVTYHMFhZ@localhost>
Message-ID: <CAAZ8HagkFSkRs1XpAPyHNtdaLSuHODNev6fkfWzh-e0cc0t0=g@mail.gmail.com>

Noted, and will do.

On Fri, May 13, 2022 at 8:52 PM Dave Woodfall <dave at slackbuilds.org> wrote:

> On 14/05/22 03:30,
> Dave Woodfall <dave at slackbuilds.org> put forth the proposition:
> > On 11/05/22 17:24,
> > fourtysixandtwo <fourtysixandtwo at sliderr.net> put forth the proposition:
> > > Hi all,
> > > I found eyeD3 was broken while testing updates to pylast.  I've emailed
> > > Larry a couple of times in the last 10 days but he hasn't responded.
> > > I've attached both format-patches I have for eyeD3.
> > > Cheers
> > Hi
> > Can you make a single patch of the whole folder next time please?
> > Thanks
>
> In fact Willy made a good blog post on how to make patches to send to
> the list:
>
> https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html
>
> Could you also put [PATCH] at the start of the message subject too,
> so it's more obvious there is one.
>
> --
> Dave
>
> sbo-maintainer-tools:
> https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
> SBo templates:
> https://slackbuilds.org/templates/
> How to format github downloads:
> https://slackbuilds.org/GITHUB_URLs.txt
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220513/ac62aa79/attachment.htm>

From dave at slackbuilds.org  Sat May 14 03:24:18 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sat, 14 May 2022 04:24:18 +0100
Subject: [Slackbuilds-users] eyeD3 slackbuild
In-Reply-To: <CAAZ8HagkFSkRs1XpAPyHNtdaLSuHODNev6fkfWzh-e0cc0t0=g@mail.gmail.com>
References: <CAAZ8Haj5kBMaq0WLs4hxuR3v8hPk9vPPvcJ2MHk7cBnqBTQjxQ@mail.gmail.com>
 <CAAZ8Haj4Bpxzhd02LyzoRo0XZ9gyPEbE_uHhxxx2o8mSqzziHw@mail.gmail.com>
 <CAAZ8Hain2KjC1e6YDCCLbSg4JYszAzJHrNKk7ewiii23kDYSrg@mail.gmail.com>
 <CAAZ8Hag4d6hM-uj-0LY+7k-f+gk+hHU1JZBERw3bdhDy9W5k0w@mail.gmail.com>
 <Yn8UWHxBccbvT9aJ@localhost> <Yn8ZW9xDVTYHMFhZ@localhost>
 <CAAZ8HagkFSkRs1XpAPyHNtdaLSuHODNev6fkfWzh-e0cc0t0=g@mail.gmail.com>
Message-ID: <Yn8g4mKI/8UKbmYe@localhost>

> > Could you also put [PATCH] at the start of the message subject too,
> Noted, and will do.

In fact `git send-email' does that already.

> On Fri, May 13, 2022 at 8:52 PM Dave Woodfall <dave at slackbuilds.org> wrote:
> > On 14/05/22 03:30,
> > Dave Woodfall <dave at slackbuilds.org> put forth the proposition:
> > > On 11/05/22 17:24,
> > > fourtysixandtwo <fourtysixandtwo at sliderr.net> put forth the proposition:
> > > > Hi all,
> > > > I found eyeD3 was broken while testing updates to pylast.  I've emailed
> > > > Larry a couple of times in the last 10 days but he hasn't responded.
> > > > I've attached both format-patches I have for eyeD3.
> > > > Cheers
> > > Hi
> > > Can you make a single patch of the whole folder next time please?
> > > Thanks
> >
> > In fact Willy made a good blog post on how to make patches to send to
> > the list:
> >
> > https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html
> >
> > Could you also put [PATCH] at the start of the message subject too,
> > so it's more obvious there is one.
> >
> > --
> > Dave
> >
> > sbo-maintainer-tools:
> > https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
> > SBo templates:
> > https://slackbuilds.org/templates/
> > How to format github downloads:
> > https://slackbuilds.org/GITHUB_URLs.txt
> >
> >

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From willysr at slackbuilds.org  Sat May 14 12:42:00 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 14 May 2022 19:42:00 +0700
Subject: [Slackbuilds-users] Updates - 20220514.1
Message-ID: <d9625bc6-b4ae-23ec-2c4a-9ffbdd643864@slackbuilds.org>

Sat May 14 12:28:49 UTC 2022
academic/R: Updated for version 4.2.0.
academic/fet: Updated for version 6.3.4.
academic/labplot2: Updated for version 2.9.0.
academic/openboard: Fix build on current.
academic/xsimd: Updated for version 8.1.0.
accessibility/mbrola: Fix github tarball handling.
audio/eyeD3: Update REQUIRES. Change i486 to i586.
desktop/anki: Updated for version 2.1.51. New maintainer.
desktop/catfish: Use python3 dep.
desktop/labwc: Added (wlroots-based stacking compositor)
desktop/river: Added (dynamic tiling wayland compositor)
desktop/xob: Added (lightweight overlay bar for the X Window System)
development/gambas3: Updated for version 3.17.2.
development/github-cli: Updated for version 2.10.1.
development/jupyter-nbclient: Updated for version 0.6.3.
development/roswell: Added (Common Lisp environment setup utility)
development/vscode-bin: Updated for version 1.67.1.
development/zig: Fix libraries path.
games/bzflag: Updated for version 2.4.24.
games/larn: Fix doc permissions.
games/nestopia: Fix doinst.sh.
games/nexuiz: Fix docs.
games/nsuds: Fix docs.
graphics/mangohud: Updated for version 0.6.7.
graphics/nomacs: Update the quazip patch.
graphics/vuescan: Updated for version 9.7.86.
libraries/geocode-glib: Use yes/no for build options
libraries/gnome-autoar: Use yes/no for build options
libraries/libcreg: Added (libYAL CREG library)
libraries/libfido2: Updated for version 1.11.0.
libraries/libfilezilla: Updated for version 0.37.2.
libraries/libfsext: Added (libYAL EXT file system library)
libraries/libfshfs: Added (libYAL HFS file system library)
libraries/libfsxfs: Added (libYAL XFS file system library)
libraries/libgdata: Use yes/no for build options
libraries/libinklevel: Resurrected (printer ink level library)
libraries/libluksde: Added (libYAL LUKS Encryption library)
libraries/libmodi: Added (libYAL MacOS disk image formats library)
libraries/libphdi: Added (libYAL lib to access PHDI image format)
libraries/libpst: New download/homepage URLs.
libraries/libvsgpt: Added (libYAL access to GUID partition system)
libraries/pexpect: Remove python3 bindings.
libraries/rrdtool: Updated for version 1.8.0.
libraries/spglib: Updated for version 1.16.5. Slackbuild fixes.
misc/simh-classic: Updated for version 3.12_2.
multimedia/guvcview: Updated for version 2.0.8.
network/SoulseekQt: Updated for version 20180130.
network/asuka: Added (gemini client)
network/castor: Added (gemini client)
network/element-desktop: Updated for version 1.10.12.
network/exim: Updated for version 4.95.
network/gnome-bluetooth: Fix the build directory variable name.
network/go-sendxmpp: Added (send xmpp messages from command line)
network/haproxy: Updated for version 2.5.7.
network/mattermost-desktop: Updated for version 5.1.0.
network/prosody-mod-block-strangers: New maintainer.
network/vivaldi: Updated for version 5.2.2623.46.
network/zoom-linux: Updated for version 5.10.6.2943.
office/evolution-ews: Updated to 3.44.1
office/evolution: Updated to 3.44.1
office/featherpad: Fix github tarball handling.
office/ghostwriter: Updated for version 2.1.2.
office/gummi: Updated for version 0.8.3. New maintainer.
office/navi: Added (cheat tool for command-line and apps launchers)
office/onlyoffice-desktopeditors: Updated for version 7.1.0.
office/watson: Update DEP.
perl/perl-DBD-SQLite: Updated for version 1.70.
perl/perl-FCGI: Updated for version 0.82.
python/Flask: Updated for version 2.1.2.
python/click-legacy7: Added (Python command line utility).
python/click: Updated for version 8.1.3.
python/email-validator: Added (Validate Email Addresses)
python/pickleshare: New maintainer.
python/ptyprocess: Remove python3 bindings.
python/python2-pkgconfig: Updated for version 1.5.5. New maintainer.
python/python2-yara: Added (Python2 for yara)
python/python3-celery: Update DEP.
python/python3-json5: Updated for version 0.9.8.
python/python3-lz4: Added (py3 bindings for lz4 compression library)
python/python3-pkgconfig: Added (python interface to pkg-config)
python/python3-yara: Added (Python3 for yara)
python/roundrobin: Added (Python module).
python/snuggs: Update DEP.
python/werkzeug-legacy1: Added (WSGI utility library for Python).
python/werkzeug: Updated for version 2.1.2.
python/xattr: Added (Py wrapper for extended file system attributes)
system/bat: Updated for version 0.21.0.
system/etsh: Add /bin/etsh to /etc/shells.
system/evolution-data-server: Updated to 3.44.1
system/forkstat: Added (trace process creation/termination)
system/ink: Resurrected (printer ink level monitor)
system/intel-microcode: Updated for version 20220510.
system/sbo-maintainer-tools: Updated for version 0.5.1.
system/slackrepo-hints: Updated for version 20220513.
system/slackrepo: Updated for version 20220513.
system/slpkg: Updated for version 3.9.8.
system/volatility3: Added (memory extraction utility framework.)
system/volatility: Fixed dependencies. Explicit python2 call.
+--------------------------+


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220514/5f02dcb5/attachment.asc>

From amadvance at gmail.com  Sat May 14 19:55:54 2022
From: amadvance at gmail.com (Andrea Mazzoleni)
Date: Sat, 14 May 2022 21:55:54 +0200
Subject: [Slackbuilds-users] FIX for curlftpfs Input/Output error in write
Message-ID: <CAGKKSfU=g-4q9rBVevDmqun-yzwmtDLqjyKZ=mDo_63wrBCCAw@mail.gmail.com>

Hi,

The slackware 15 package for curlftpfs fails when copying files to FTP
servers with the message "Input/Output" error.

It looks like it's a known issue, already fixed in other distributions,
like in the SuSe package:
http://download.opensuse.org/update/13.2/src/curlftpfs-0.9.2-61.3.1.src.rpm

Applying the two bug-580609.patch and bug-955687.patch makes it working on
my system.

Some references:
https://bugzilla.redhat.com/show_bug.cgi?id=671204
https://bugs.mageia.org/show_bug.cgi?id=17324

Ciao,
Andrea
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220514/8c1309cb/attachment.htm>

From fourtysixandtwo at sliderr.net  Sun May 15 22:01:45 2022
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Sun, 15 May 2022 16:01:45 -0600
Subject: [Slackbuilds-users] [PATCH] anki: Update DEP.
Message-ID: <CAAZ8HajROHQQ-ovZa+b2gShoysSzcdV+0UYrvQDKgGty2DmKPw@mail.gmail.com>

Hi,

Here's a patch to update/add a couple of dependencies for python3 to work
with the new Flask, click, and werkzeug.

It also needs an updated Flask-Cors (sitting in the pending queue) and
complains about missing orjson (no slackbuild) but appears to work fine
without it.

Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220515/22c7e210/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0052-desktop-anki-Update-DEP.patch
Type: text/x-patch
Size: 1144 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220515/22c7e210/attachment-0001.bin>

From slackbuilds at schoepfer.info  Tue May 17 04:52:52 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 17 May 2022 06:52:52 +0200
Subject: [Slackbuilds-users] [PATCH 101/101] graphics/simple-scan: Updated
 for version 42.1
Message-ID: <9b6e6480013f0960208ffe737b45a022@schoepfer.info>

Hi,

update for simplescan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0101-graphics-simple-scan-Updated-for-version-42.1.patch
Type: text/x-diff
Size: 5200 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220517/1a8b27ac/attachment.bin>

From fourtysixandtwo at sliderr.net  Tue May 17 16:53:31 2022
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Tue, 17 May 2022 10:53:31 -0600
Subject: [Slackbuilds-users] [PATCH] network/EarthReader-Web: Updated for
 version 0.3.0, changed REQUIRES.
Message-ID: <CAAZ8Hah4u3b2Upz+EGemXgkQcFTGMuFr7bbcBKUz8vDkbtOuBg@mail.gmail.com>

This is needed to work with the Flask update.

Cheers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220517/a6a98047/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0011-network-EarthReader-Web-Updated-for-version-0.3.0-ch.patch
Type: text/x-patch
Size: 2322 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220517/a6a98047/attachment.bin>

From bgrundy at linuxleo.com  Fri May 20 14:03:45 2022
From: bgrundy at linuxleo.com (Barry J. Grundy)
Date: Fri, 20 May 2022 10:03:45 -0400
Subject: [Slackbuilds-users] [PATCH] office/catdoc: Update for version 0.95
Message-ID: <9abbf65e-99ba-667d-ab91-dc48c5f10949@linuxleo.com>

Good morning,

The version of office/catdoc on SBo is over 16 years old, and while it 
builds, it segfaults at runtime.  I contacted the maintainer and never 
heard back.

The attached patch is an update to the latest version (still over 5 
years old), which builds and runs without segfault. I doubt there will 
be many updates to follow.

Note that there is no license in the original script as required by the 
instructions at SBo for SlackBuilds.  I would not know how to add one to 
someone else's script.  This is just a functional patch.

Thanks,
Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-office-catdoc-Updated-for-version-0.95.patch
Type: text/x-patch
Size: 2265 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220520/9ebae6f0/attachment.bin>

From rasp at spitzner.org  Fri May 20 14:51:02 2022
From: rasp at spitzner.org (Ralph Spitzner)
Date: Fri, 20 May 2022 16:51:02 +0200
Subject: [Slackbuilds-users] env var
Message-ID: <f55256bb-3d89-547d-2d9f-d688478f3879@spitzner.org>

if  I check an  env var in a slackbuild, do I document the variable in  the README, or slack-desc ?

     -rasp

-- 
"ich brauche keine Verschluesselung, mich versteht eh keiner"  -Icke

From dave at slackbuilds.org  Fri May 20 15:04:17 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Fri, 20 May 2022 16:04:17 +0100
Subject: [Slackbuilds-users] env var
In-Reply-To: <f55256bb-3d89-547d-2d9f-d688478f3879@spitzner.org>
References: <f55256bb-3d89-547d-2d9f-d688478f3879@spitzner.org>
Message-ID: <Yoet8UukE7wPm8wl@localhost>

On 20/05/22 16:51,
Ralph Spitzner <rasp at spitzner.org> put forth the proposition:
> if  I check an  env var in a slackbuild, do I document the variable in  the README, or slack-desc ?

Usually it would be in the README.  If it is critical for build
dependencies then also add %README% to REQUIRES in the .info too.

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From fourtysixandtwo at sliderr.net  Fri May 20 18:43:25 2022
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Fri, 20 May 2022 12:43:25 -0600
Subject: [Slackbuilds-users] couple of DEP fixes
Message-ID: <CAAZ8HajU2TFtkoA4oRjP=Mun_1d5hzd3rqHOCUjVjATWnaK+3w@mail.gmail.com>

Hi all,

Now that the prerequisites are in place the following dependencies need to
be updated.

desktop/anki
  -change Flask-Cors to python3-Flask-Cors
python/python3-Flask-RESTful
  -change aniso8601 to python3-aniso8601

Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220520/e4995cca/attachment-0001.htm>

From dave at slackbuilds.org  Fri May 20 19:33:41 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Fri, 20 May 2022 20:33:41 +0100
Subject: [Slackbuilds-users] couple of DEP fixes
In-Reply-To: <CAAZ8HajU2TFtkoA4oRjP=Mun_1d5hzd3rqHOCUjVjATWnaK+3w@mail.gmail.com>
References: <CAAZ8HajU2TFtkoA4oRjP=Mun_1d5hzd3rqHOCUjVjATWnaK+3w@mail.gmail.com>
Message-ID: <YoftFTPk8ACTlg39@localhost>

> Hi all,
> Now that the prerequisites are in place the following dependencies need to
> be updated.
> desktop/anki
>   -change Flask-Cors to python3-Flask-Cors
> python/python3-Flask-RESTful
>   -change aniso8601 to python3-aniso8601
> Cheers

Done.

Can all these be removed now?

python/Flask-Babel
python/Flask-Bcrypt
python/Flask-Compress
python/Flask-Dance
python/Flask-Login
python/Flask-Mail
python/Flask-Principal
python/Flask-SQLAlchemy
python/Flask-WTF
python/flask-paginate

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From fourtysixandtwo at sliderr.net  Fri May 20 20:08:29 2022
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Fri, 20 May 2022 14:08:29 -0600
Subject: [Slackbuilds-users] couple of DEP fixes
In-Reply-To: <YoftFTPk8ACTlg39@localhost>
References: <CAAZ8HajU2TFtkoA4oRjP=Mun_1d5hzd3rqHOCUjVjATWnaK+3w@mail.gmail.com>
 <YoftFTPk8ACTlg39@localhost>
Message-ID: <CAAZ8Hagga46T0JwH9QouGS3KKcZ+4Oi1Rc37Lq13EJXKgC5AWQ@mail.gmail.com>

> Can all these be removed now?
>
> python/Flask-Babel
> python/Flask-Bcrypt
> python/Flask-Compress
> python/Flask-Dance
> python/Flask-Login
> python/Flask-Mail
> python/Flask-Principal
> python/Flask-SQLAlchemy
> python/Flask-WTF
> python/flask-paginate

Yes, they are all "broken" builds.  I would also add the following as
they broken and unmaintained projects.

python/Flask-Security
python/restplus

Cheers

From willysr at slackbuilds.org  Sat May 21 01:47:19 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 21 May 2022 08:47:19 +0700
Subject: [Slackbuilds-users] Updates - 20220521.1
Message-ID: <e750edf3-1655-a727-88da-dd45738d697f@slackbuilds.org>

Sat May 21 01:26:30 UTC 2022
academic/bibletime: Updated for version 3.0.3.
academic/openboard: Fix applying patch for -current.
academic/pysam: Updated for version 0.19.0.
academic/scipy3: Updated for version 1.8.1.
academic/xsimd: Fix 32bit build.
business/binance-desktop: Added (Enhance Your Trading Experience)
desktop/anki: Update REQUIRES.
desktop/grim: Fix build on 32bit.
desktop/hushboard: Updated for version 20220515_5539a9a.
desktop/picom: Fix man page directory.
desktop/ptwit: Updated for version 0.2. New maintainer.
desktop/rofi-lbonn-wayland: Added (wayland window switcher)
desktop/sfwbar: Added (Sway Floating Window Bar)
desktop/wmamixer: Added (ALSA mixer dockapp)
development/REDasm: Fix offline build.
development/SQLAlchemy: Updated for version 1.4.36. New maintainer.
development/dotnet-runtime-3.1: Updated for version 3.1.25.
development/dotnet-runtime-5.0: Updated for version 5.0.17.
development/dotnet-runtime-6.0: Updated for version 6.0.5.
development/dotnet-sdk-3.1: Updated for version 3.1.419.
development/dotnet-sdk-5.0: Updated for version 5.0.408.
development/dotnet-sdk-6.0: Updated for version 6.0.300.
development/ghidra: Updated for version 10.1.4.
development/jupyter_client: Updated for version 7.3.1.
development/jupyterlab: Updated for version 3.4.2.
development/mongodb-compass: Updated for version 1.31.3.
development/txr: Added (pattern-based text extraction language)
graphics/mangohud: Fix 32bit error.
graphics/mangohud: Remove patches (included in .info).
graphics/simple-scan: Updated for version 42.1.
libraries/aspnetcore-runtime-3.1: Updated for version 3.1.25.
libraries/aspnetcore-runtime-5.0: Updated for version 5.0.17.
libraries/aspnetcore-runtime-6.0: Updated for version 6.0.5.
libraries/dcmtk: Updated for version 3.6.7
libraries/libbde: Updated for version 20220121.
libraries/libesedb: Updated for version 20210424.
libraries/libevt: Updated for version 20210424.
libraries/libevtx: Updated for version 20210525.
libraries/libexe: Updated for version 20210424.
libraries/libfsapfs: Updated for version 20210424.
libraries/libfsntfs: Updated for version 20220220.
libraries/libfvde: Updated for version 20220125.
libraries/libfwnt: Updated for version 20210906.
libraries/libfwsi: Updated for version 20220123.
libraries/libgweather Use yes/no for build options
libraries/liblnk: Updated for version 20210417.
libraries/libmsiecf: Updated for version 20210420.
libraries/libolecf: Updated for version 20210512.
libraries/libpff: Updated for version 20211114.
libraries/libqcow: Updated for version 20210419.
libraries/libregf: Updated for version 20220131.
libraries/libscca: Updated for version 20210419.
libraries/libsigscan: Updated for version 20220124.
libraries/libsmdev: Updated for version 20210418.
libraries/libsmraw: Updated for version 20210807.
libraries/libvhdi: Explicit python3 bindings.
libraries/libvshadow: Updated for version 20211114.
libraries/libvslvm: Updated for version 20210807.
libraries/libwrc: Updated for version 20220104.
libraries/luaexpat: Update HOMEPAGE, DOWNLOAD.
libraries/webkit2gtk4.1: Updated for version 2.36.2.
libraries/webkit2gtk: Updated for version 2.36.2.
misc/wl-clipboard: Added (Wayland clipboard utilities)
multimedia/LBRY: Updated for version 0.53.3.
multimedia/kaffeine: Compress manpages.
multimedia/plexmediaserver: Updated for v 1.26.1.5798_99a4a6ac9.
network/EarthReader-Web: Updated for version 0.3.0.
network/asuka: Allow content-disposition filenames.
network/castor: Allow content-disposition filenames.
network/flexget: Update REQUIRES.
network/microsoft-edge: Updated for version 101.0.1210.47.
network/microsoft-edge: Updated for version 101.0.1210.53.
network/phpmyadmin: Updated for version 5.2.0.
network/qutebrowser-bin: Update pdfjs to 2.14.305.
network/signal-desktop: Updated for version 5.43.0.
network/vivaldi: Updated for version 5.2.2623.48.
network/windscribe: Updated for version 2.4.8.
office/catdoc: Updated for version 0.95.
office/navi: Fix github tarball handling.
office/task: Updated for version 2.6.2.
office/timetrap: Fix to not remove executable.
python/Flask-Babel: Removed. Python3 script added.
python/Flask-Bcrypt: Removed. Python3 script added.
python/Flask-Compress: Removed. Python3 script added.
python/Flask-Cors: Removed. Python3 script added.
python/Flask-Dance: Removed. Python3 script added.
python/Flask-Login: Removed. Python3 script added.
python/Flask-Mail: Removed. Python3 script added.
python/Flask-Principal: Removed. Python3 script added.
python/Flask-RESTful: Removed. Python3 script added.
python/Flask-SQLAlchemy: Removed. Python3 script added.
python/Flask-Security: Removed. Python3 script added.
python/Flask-WTF: Removed. Python3 script added.
python/XlsxWriter: Updated for version 3.0.3.
python/aniso8601: Removed. Python3 script added.
python/artifacts: Updated for version 20220429.
python/click-default-group: Updated for v 1.2.2. New maintainer.
python/dfdatetime: Updated for version 20220131.
python/dfvfs: Updated for version 20220419.
python/dfwinreg: Updated for version 20211207.
python/dpkt: Updated for version 1.9.7.2.
python/dtfabric: Updated for version 20220219.
python/esptool: Updated for version 4.0.
python/flask-paginate: Removed. Python3 script added.
python/flask-restplus: Removed. Python3 script added.
python/mypy: Updated for version 0.950.
python/pikepdf: Updated for version 5.1.3.
python/plaso: Updated for version 20220428.
python/python-fonttools: Updated for version 4.33.3.
python/python2-pkgconfig: Downgraded to version 1.5.2.
python/python3-Flask-Babel: Added (i18n/l10n support to Flask apps)
python/python3-Flask-Bcrypt: Added (Bcrypt extension for Flask)
python/python3-Flask-Compress: Added (gzip responses in Flask apps)
python/python3-Flask-Cors: Added (Flask extension for handling CORS)
python/python3-Flask-Dance: Added (Doing the OAuth using Flask)
python/python3-Flask-Login: Added (Flask user session management)
python/python3-Flask-Mail: Added (Flask extension for sending email)
python/python3-Flask-Principal: Added (Flask identity management)
python/python3-Flask-RESTX: Added (community fork of Flask-RESTPlus)
python/python3-Flask-RESTful: Updated for v 0.3.9. New maintainer.
python/python3-Flask-SQLAlchemy: Added (SQLAlchemy support to Flask)
python/python3-Flask-Security-Too: Added (Security for Flask apps)
python/python3-Flask-WTF: Added (Python Flask WTF)
python/python3-WTForms: Added (web forms validation/rendering lib)
python/python3-aniso8601: Added (ISO 8601 string parsing ibrary)
python/python3-anyio: Updated for version 3.6.1.
python/python3-attrs: Updated for version 21.4.0.
python/python3-bencode: Added (python3 bittorrent module)
python/python3-blinker: Added (object-to-object/broadcast signaling)
python/python3-defcon: Updated for version 0.10.1.
python/python3-elgato-streamdeck: Added (Elgato Stream Deck library)
python/python3-flask-paginate: Added (Simple paginate for flask)
python/pytsk: Updated for version 20211111.
python/pywayland: Updated for version 0.4.12.
python/pywlroots: Updated for version 0.15.14.
python/scikit-learn: Updated for version 1.1.1.
python/thonny: Updated for version 3.3.14.
system/containerd: Fix path.
system/containerd: Updated for version 1.6.4.
system/docker-cli: Updated for version 20.10.16.
system/docker: Updated for version 20.10.16.
system/epson-inkjet-printer-escpr2: Updated for version 1.1.48.
system/geckodriver: Updated for version 0.31.0. New maintainer.
system/gnu-unifont: Updated for version 14.0.03.
system/hyperfine: Updated for version 1.14.0.
system/lynis: Updated for version 3.0.8.
system/mergerfs: Added (a featureful union filesystem)
system/mpollux-digisign-client: Updated for version 4.2.2_8099.
system/nvidia-legacy340-kernel: Fix package ARCH.
system/nvidia-legacy340-kernel: Patch for the newer kernels.
system/openrazer-kernel: Allow building for $KERNEL.
system/postgresql: Updated for version 14.3.
system/powershell: Updated for version 7.2.4.
system/pw: Added (view data passing through a pipe)
system/runc: Updated for version 1.1.2.
system/swtpm: Updated for version 0.7.3.
system/telegraf: Updated for version 1.22.4.
system/tmuxp: Updated for version 1.11.1. New maintainer.
system/v7sh: Added (port of original Steve Bourne shell from 1978)
system/victor-mono-fonts: Updated for version 1.5.2.
system/watch-fs: Move to python3. New maintainer.
+--------------------------+


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220521/5aa2cf20/attachment.asc>

From gerswing at gmail.com  Sat May 21 05:05:26 2022
From: gerswing at gmail.com (Daniel Mackle)
Date: Sat, 21 May 2022 14:05:26 +0900
Subject: [Slackbuilds-users] Anki ModuleNotFoundError
Message-ID: <CADkN_HRV1=dzT4LyEviRp4nMo+_UFvK9CX7H=J+HJ+Bg7BdDXw@mail.gmail.com>

I have run into an error with anki since I upgraded to Slackware 15.0.  I
have re-installed all of the dependencies and still get the same error.
This includes and up to the latest version on Slackbuilds.  I have searched
the web, SBo mailing list archives, Anki mailing list, etc. and still have
not been able to resolve.  If anyone has any ideas, please let me know.

Anki builds just fine, but when I try to run I get the following error:

Traceback (most recent call last):
 File "/usr/bin/anki", line 5, in <module>
   from aqt import run
 File "/usr/lib64/python3.9/site-packages/aqt/__init__.py", line 39, in
<module>
   import anki.lang
 File "/usr/lib64/python3.9/site-packages/anki/lang.py", line 12, in
<module>
   import anki._backend
 File "/usr/lib64/python3.9/site-packages/anki/_backend/__init__.py", line
11, in <module>
   from markdown import markdown
 File "/usr/lib64/python3.9/site-packages/markdown/__init__.py", line 35,
in <module>
   from .__version__ import version, version_info  # noqa
ModuleNotFoundError: No module named 'markdown.__version__'

I believe it may have something to do with Python2.7/Python3.9, but I am
not sure.  Thank you in advance for any advice.  I do have Markdown
installed.

V/R

Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220521/ebbe797c/attachment.htm>

From dave at slackbuilds.org  Sat May 21 05:39:51 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sat, 21 May 2022 06:39:51 +0100
Subject: [Slackbuilds-users] Anki ModuleNotFoundError
In-Reply-To: <CADkN_HRV1=dzT4LyEviRp4nMo+_UFvK9CX7H=J+HJ+Bg7BdDXw@mail.gmail.com>
References: <CADkN_HRV1=dzT4LyEviRp4nMo+_UFvK9CX7H=J+HJ+Bg7BdDXw@mail.gmail.com>
Message-ID: <Yoh7JwzcRjjgDaNb@localhost>

On 21/05/22 14:05,
Daniel Mackle <gerswing at gmail.com> put forth the proposition:
> I have run into an error with anki since I upgraded to Slackware 15.0.  I
> have re-installed all of the dependencies and still get the same error.
> This includes and up to the latest version on Slackbuilds.  I have searched
> the web, SBo mailing list archives, Anki mailing list, etc. and still have
> not been able to resolve.  If anyone has any ideas, please let me know.
> Anki builds just fine, but when I try to run I get the following error:
> Traceback (most recent call last):
>  File "/usr/bin/anki", line 5, in <module>
>    from aqt import run
>  File "/usr/lib64/python3.9/site-packages/aqt/__init__.py", line 39, in
> <module>
>    import anki.lang
>  File "/usr/lib64/python3.9/site-packages/anki/lang.py", line 12, in
> <module>
>    import anki._backend
>  File "/usr/lib64/python3.9/site-packages/anki/_backend/__init__.py", line
> 11, in <module>
>    from markdown import markdown
>  File "/usr/lib64/python3.9/site-packages/markdown/__init__.py", line 35,
> in <module>
>    from .__version__ import version, version_info  # noqa
> ModuleNotFoundError: No module named 'markdown.__version__'
> I believe it may have something to do with Python2.7/Python3.9, but I am
> not sure.  Thank you in advance for any advice.  I do have Markdown
> installed.
> V/R
> Dan

It looks like Markdown (python2) might be conflicting slightly with
the stock python-markdown (python3) package.

Can you try uninstalling Markdown and reinstalling python-markdown to
see if it helps?

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From gerswing at gmail.com  Sat May 21 05:52:18 2022
From: gerswing at gmail.com (Daniel Mackle)
Date: Sat, 21 May 2022 14:52:18 +0900
Subject: [Slackbuilds-users] Anki ModuleNotFoundError
In-Reply-To: <Yoh7JwzcRjjgDaNb@localhost>
References: <CADkN_HRV1=dzT4LyEviRp4nMo+_UFvK9CX7H=J+HJ+Bg7BdDXw@mail.gmail.com>
 <Yoh7JwzcRjjgDaNb@localhost>
Message-ID: <CADkN_HS826ymvBr7gf4iB1Bm4hP2HtiovONZK9nKK7OGTd7VDg@mail.gmail.com>

Dave,

That is it.  Propose removing Markdown from the  dependencies for anki.  I
removed Markdown and reinstalled python-markdown and it works fine.

Thank you.

V/R

Dan

On Sat, May 21, 2022 at 2:39 PM Dave Woodfall <dave at slackbuilds.org> wrote:

> On 21/05/22 14:05,
> Daniel Mackle <gerswing at gmail.com> put forth the proposition:
> > I have run into an error with anki since I upgraded to Slackware 15.0.  I
> > have re-installed all of the dependencies and still get the same error.
> > This includes and up to the latest version on Slackbuilds.  I have
> searched
> > the web, SBo mailing list archives, Anki mailing list, etc. and still
> have
> > not been able to resolve.  If anyone has any ideas, please let me know.
> > Anki builds just fine, but when I try to run I get the following error:
> > Traceback (most recent call last):
> >  File "/usr/bin/anki", line 5, in <module>
> >    from aqt import run
> >  File "/usr/lib64/python3.9/site-packages/aqt/__init__.py", line 39, in
> > <module>
> >    import anki.lang
> >  File "/usr/lib64/python3.9/site-packages/anki/lang.py", line 12, in
> > <module>
> >    import anki._backend
> >  File "/usr/lib64/python3.9/site-packages/anki/_backend/__init__.py",
> line
> > 11, in <module>
> >    from markdown import markdown
> >  File "/usr/lib64/python3.9/site-packages/markdown/__init__.py", line 35,
> > in <module>
> >    from .__version__ import version, version_info  # noqa
> > ModuleNotFoundError: No module named 'markdown.__version__'
> > I believe it may have something to do with Python2.7/Python3.9, but I am
> > not sure.  Thank you in advance for any advice.  I do have Markdown
> > installed.
> > V/R
> > Dan
>
> It looks like Markdown (python2) might be conflicting slightly with
> the stock python-markdown (python3) package.
>
> Can you try uninstalling Markdown and reinstalling python-markdown to
> see if it helps?
>
> --
> Dave
>
> sbo-maintainer-tools:
> https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
> SBo templates:
> https://slackbuilds.org/templates/
> How to format github downloads:
> https://slackbuilds.org/GITHUB_URLs.txt
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220521/478282a4/attachment-0001.htm>

From dave at slackbuilds.org  Sat May 21 05:57:29 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sat, 21 May 2022 06:57:29 +0100
Subject: [Slackbuilds-users] Anki ModuleNotFoundError
In-Reply-To: <CADkN_HS826ymvBr7gf4iB1Bm4hP2HtiovONZK9nKK7OGTd7VDg@mail.gmail.com>
References: <CADkN_HRV1=dzT4LyEviRp4nMo+_UFvK9CX7H=J+HJ+Bg7BdDXw@mail.gmail.com>
 <Yoh7JwzcRjjgDaNb@localhost>
 <CADkN_HS826ymvBr7gf4iB1Bm4hP2HtiovONZK9nKK7OGTd7VDg@mail.gmail.com>
Message-ID: <Yoh/SbA+0beiTgR0@localhost>

On 21/05/22 14:52,
Daniel Mackle <gerswing at gmail.com> put forth the proposition:
> Dave,
> That is it.  Propose removing Markdown from the  dependencies for anki.  I
> removed Markdown and reinstalled python-markdown and it works fine.

The /usr/bin/markdown_py in Markdown is overwriting the python3
version in stock python-markdown.

I'll push that change in my branch, and see what the situation is
with the other builds that require it.

> Thank you.
> V/R
> Dan
> On Sat, May 21, 2022 at 2:39 PM Dave Woodfall <dave at slackbuilds.org> wrote:
> > On 21/05/22 14:05,
> > Daniel Mackle <gerswing at gmail.com> put forth the proposition:
> > > I have run into an error with anki since I upgraded to Slackware 15.0.  I
> > > have re-installed all of the dependencies and still get the same error.
> > > This includes and up to the latest version on Slackbuilds.  I have
> > searched
> > > the web, SBo mailing list archives, Anki mailing list, etc. and still
> > have
> > > not been able to resolve.  If anyone has any ideas, please let me know.
> > > Anki builds just fine, but when I try to run I get the following error:
> > > Traceback (most recent call last):
> > >  File "/usr/bin/anki", line 5, in <module>
> > >    from aqt import run
> > >  File "/usr/lib64/python3.9/site-packages/aqt/__init__.py", line 39, in
> > > <module>
> > >    import anki.lang
> > >  File "/usr/lib64/python3.9/site-packages/anki/lang.py", line 12, in
> > > <module>
> > >    import anki._backend
> > >  File "/usr/lib64/python3.9/site-packages/anki/_backend/__init__.py",
> > line
> > > 11, in <module>
> > >    from markdown import markdown
> > >  File "/usr/lib64/python3.9/site-packages/markdown/__init__.py", line 35,
> > > in <module>
> > >    from .__version__ import version, version_info  # noqa
> > > ModuleNotFoundError: No module named 'markdown.__version__'
> > > I believe it may have something to do with Python2.7/Python3.9, but I am
> > > not sure.  Thank you in advance for any advice.  I do have Markdown
> > > installed.
> > > V/R
> > > Dan
> >
> > It looks like Markdown (python2) might be conflicting slightly with
> > the stock python-markdown (python3) package.
> >
> > Can you try uninstalling Markdown and reinstalling python-markdown to
> > see if it helps?
> >
> > --
> > Dave
> >
> > sbo-maintainer-tools:
> > https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
> > SBo templates:
> > https://slackbuilds.org/templates/
> > How to format github downloads:
> > https://slackbuilds.org/GITHUB_URLs.txt
> >
> >

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From kjhambrick at gmail.com  Sun May 22 19:46:37 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 22 May 2022 14:46:37 -0500
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
Message-ID: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>

All --

I emailed the maintainer on May 12 but have received no reply.

Below is the email I sent.

The Punchline is that the DevIL SBo will not compile on my Slackware64
15.0 + Multilib System when the nvidia-texture-tools SBo is installed.

The simplest fix is to turn off nvidia-texture-tools via a cmake Config
Flag:

# --------------------- cut  here -------------------
# diff -Naur DevIL~01.SlackBuild DevIL.SlackBuild
--- or/DevIL.SlackBuild 2022-04-23 17:41:07.620019227 -0500
+++ DevIL.SlackBuild    2022-05-12 11:19:49.873854478 -0500
@@ -73,6 +73,7 @@
     -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
     -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS -std=c++14 -fpermissive" \
     -DCMAKE_INSTALL_PREFIX=/usr \
+    -DIL_USE_DXTC_NVIDIA=NO \
     -DCMAKE_BUILD_TYPE=Release ..
   make
   make install/strip DESTDIR=$PKG
# --------------------- cut  here -------------------

Is this the best place to post such info ?

Thanks everyone !

-- kjh

# ----------------------original email to the maintainer ------------

Yth - Arnaud

I am running Slackware64 15.0 System with Multilib +
NVIDIA-Linux-x86_64-510.68.02.run

I discovered that if nvidia-texture-tools ( aka nvtt ) is installed, that
DevIL will not compile.

I tried with nvidia-texture-tools version 2.1.1 and also with the more
recent version 2.1.2

There are missing Header Files in /usr/include/nvcore/ ( and maybe others )

To reproduce:  build and install nvidia-texture-tools.SlackBuild  and then
try to build DevIL.SlackBuild

I changed the nvidia-texture-tools CMakeLists.txt so that the header files
are installed in /usr/include/{nvtt,nvthread,nvmath,nvimage,nvcore}/
as well as installing nvconfig.h

The DevIL.SlackBuild compile makes it past the missing Headers in src-IL/

However, the compiler finally fails building
src-IL/CMakeFiles/IL.dir/src/il_nvidia.cpp.o because the nvtt headers
differ from what is DevIL expects to find ( output below mu sig )

I found a CMake switch ( -DIL_USE_DXTC_NVIDIA=NO ) that can be turned off
in the DevIL.SlackBuild to avoid nvtt altogether.

Then it builds as expected.

Here is diff -Naur
#-------------------- cut  here --------------
# diff -Naur DevIL~01.SlackBuild DevIL.SlackBuild
--- or/DevIL.SlackBuild 2022-04-23 17:41:07.620019227 -0500
+++ DevIL.SlackBuild    2022-05-12 11:19:49.873854478 -0500
@@ -73,6 +73,7 @@
     -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
     -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS -std=c++14 -fpermissive" \
     -DCMAKE_INSTALL_PREFIX=/usr \
+    -DIL_USE_DXTC_NVIDIA=NO \
     -DCMAKE_BUILD_TYPE=Release ..
   make
   make install/strip DESTDIR=$PKG
# --------------------- cut there -------------------

Thanks for all the SlackBuilds !

-- kjh

This is the failure after installing the nvtt header files.

/tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp: In function 'ILubyte*
ilNVidiaCompressDXT(ILubyte*, ILuint, ILuint, ILuint, ILenum, ILuint*)':
/tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:104:28: error: cannot declare
variable 'outputHandler' to be of abstract type 'ilOutputHandlerMem'
  104 |         ilOutputHandlerMem outputHandler(Width, Height, DxtFormat);
      |                            ^~~~~~~~~~~~~
/tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:38:8: note:   because the
following virtual functions are pure within 'ilOutputHandlerMem':
   38 | struct ilOutputHandlerMem : public nvtt::OutputHandler
      |        ^~~~~~~~~~~~~~~~~~
In file included from /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:20:
/usr/include/nvtt/nvtt.h:341:22: note:     'virtual void
nvtt::OutputHandler::endImage()'
  341 |         virtual void endImage() = 0;
      |                      ^~~~~~~~
/tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp: In function 'ILuint
ilNVidiaCompressDXTFile(ILubyte*, ILuint, ILuint, ILuint, ILenum)':
/tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:188:29: error: cannot declare
variable 'outputHandler' to be of abstract type 'ilOutputHandlerFile'
  188 |         ilOutputHandlerFile outputHandler(Width, Height, DxtFormat);
      |                             ^~~~~~~~~~~~~
/tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:148:8: note:   because the
following virtual functions are pure within 'ilOutputHandlerFile':
  148 | struct ilOutputHandlerFile : public nvtt::OutputHandler
      |        ^~~~~~~~~~~~~~~~~~~
In file included from /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:20:
/usr/include/nvtt/nvtt.h:341:22: note:     'virtual void
nvtt::OutputHandler::endImage()'
  341 |         virtual void endImage() = 0;
      |                      ^~~~~~~~
make[2]: *** [src-IL/CMakeFiles/IL.dir/build.make:678:
src-IL/CMakeFiles/IL.dir/src/il_nvidia.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:134: src-IL/CMakeFiles/IL.dir/all] Error
2
make: *** [Makefile:136: all] Error 2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220522/0e5c6219/attachment.htm>

From dave at slackbuilds.org  Sun May 22 20:35:23 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 22 May 2022 21:35:23 +0100
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
Message-ID: <Yoqei6RateVQWuf8@localhost>

On 22/05/22 14:46,
Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> All --
> I emailed the maintainer on May 12 but have received no reply.
> Below is the email I sent.
> The Punchline is that the DevIL SBo will not compile on my Slackware64
> 15.0 + Multilib System when the nvidia-texture-tools SBo is installed.
> The simplest fix is to turn off nvidia-texture-tools via a cmake Config
<snip>
> Is this the best place to post such info ?
> Thanks everyone !
> -- kjh

This is the right place, usually we accept patches as attachments,
but if this only the one flag.  I can take a look this week.

We don't support multilib though, so do you know if it fails still on
a non-multilib full 15.0 installation?

Link to blog post on sending patches:
https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html.

> # ----------------------original email to the maintainer ------------
> Yth - Arnaud
> I am running Slackware64 15.0 System with Multilib +
> NVIDIA-Linux-x86_64-510.68.02.run
> I discovered that if nvidia-texture-tools ( aka nvtt ) is installed, that
> DevIL will not compile.
> I tried with nvidia-texture-tools version 2.1.1 and also with the more
> recent version 2.1.2
> There are missing Header Files in /usr/include/nvcore/ ( and maybe others )
> To reproduce:  build and install nvidia-texture-tools.SlackBuild  and then
> try to build DevIL.SlackBuild
> I changed the nvidia-texture-tools CMakeLists.txt so that the header files
> are installed in /usr/include/{nvtt,nvthread,nvmath,nvimage,nvcore}/
> as well as installing nvconfig.h
> The DevIL.SlackBuild compile makes it past the missing Headers in src-IL/
> However, the compiler finally fails building
> src-IL/CMakeFiles/IL.dir/src/il_nvidia.cpp.o because the nvtt headers
> differ from what is DevIL expects to find ( output below mu sig )
> I found a CMake switch ( -DIL_USE_DXTC_NVIDIA=NO ) that can be turned off
> in the DevIL.SlackBuild to avoid nvtt altogether.
> Then it builds as expected.
> Here is diff -Naur
> #-------------------- cut  here --------------
> # diff -Naur DevIL~01.SlackBuild DevIL.SlackBuild
> --- or/DevIL.SlackBuild 2022-04-23 17:41:07.620019227 -0500
> +++ DevIL.SlackBuild    2022-05-12 11:19:49.873854478 -0500
> @@ -73,6 +73,7 @@
>      -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
>      -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS -std=c++14 -fpermissive" \
>      -DCMAKE_INSTALL_PREFIX=/usr \
> +    -DIL_USE_DXTC_NVIDIA=NO \
>      -DCMAKE_BUILD_TYPE=Release ..
>    make
>    make install/strip DESTDIR=$PKG
> # --------------------- cut there -------------------
> Thanks for all the SlackBuilds !
> -- kjh
> This is the failure after installing the nvtt header files.
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp: In function 'ILubyte*
> ilNVidiaCompressDXT(ILubyte*, ILuint, ILuint, ILuint, ILenum, ILuint*)':
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:104:28: error: cannot declare
> variable 'outputHandler' to be of abstract type 'ilOutputHandlerMem'
>   104 |         ilOutputHandlerMem outputHandler(Width, Height, DxtFormat);
>       |                            ^~~~~~~~~~~~~
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:38:8: note:   because the
> following virtual functions are pure within 'ilOutputHandlerMem':
>    38 | struct ilOutputHandlerMem : public nvtt::OutputHandler
>       |        ^~~~~~~~~~~~~~~~~~
> In file included from /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:20:
> /usr/include/nvtt/nvtt.h:341:22: note:     'virtual void
> nvtt::OutputHandler::endImage()'
>   341 |         virtual void endImage() = 0;
>       |                      ^~~~~~~~
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp: In function 'ILuint
> ilNVidiaCompressDXTFile(ILubyte*, ILuint, ILuint, ILuint, ILenum)':
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:188:29: error: cannot declare
> variable 'outputHandler' to be of abstract type 'ilOutputHandlerFile'
>   188 |         ilOutputHandlerFile outputHandler(Width, Height, DxtFormat);
>       |                             ^~~~~~~~~~~~~
> /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:148:8: note:   because the
> following virtual functions are pure within 'ilOutputHandlerFile':
>   148 | struct ilOutputHandlerFile : public nvtt::OutputHandler
>       |        ^~~~~~~~~~~~~~~~~~~
> In file included from /tmp/SBo/DevIL/DevIL/src-IL/src/il_nvidia.cpp:20:
> /usr/include/nvtt/nvtt.h:341:22: note:     'virtual void
> nvtt::OutputHandler::endImage()'
>   341 |         virtual void endImage() = 0;
>       |                      ^~~~~~~~
> make[2]: *** [src-IL/CMakeFiles/IL.dir/build.make:678:
> src-IL/CMakeFiles/IL.dir/src/il_nvidia.cpp.o] Error 1
> make[1]: *** [CMakeFiles/Makefile2:134: src-IL/CMakeFiles/IL.dir/all] Error
> 2
> make: *** [Makefile:136: all] Error 2

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From arnaud.garcia-fernandez at laposte.net  Sun May 22 21:28:03 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Sun, 22 May 2022 23:28:03 +0200
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <Yoqei6RateVQWuf8@localhost>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost>
Message-ID: <20220522232803.f31d6c50346eb02570385e26@laposte.net>

> On 22/05/22 14:46,
> Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> > All --
> > I emailed the maintainer on May 12 but have received no reply.
> > Below is the email I sent.
> > The Punchline is that the DevIL SBo will not compile on my Slackware64
> > 15.0 + Multilib System when the nvidia-texture-tools SBo is installed.
> > The simplest fix is to turn off nvidia-texture-tools via a cmake Config
> <snip>
> > Is this the best place to post such info ?
> > Thanks everyone !
> > -- kjh
> 
> This is the right place, usually we accept patches as attachments,
> but if this only the one flag.  I can take a look this week.
> 
> We don't support multilib though, so do you know if it fails still on
> a non-multilib full 15.0 installation?
> 
> Link to blog post on sending patches:
> https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html.

Well, I did reply, but my mail provider has been quite unprofessional lately.
I'll look into it, and push an update.

 - Yth / Arnaud.

From dave at slackbuilds.org  Sun May 22 21:33:31 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 22 May 2022 22:33:31 +0100
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <Yoqei6RateVQWuf8@localhost>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost>
Message-ID: <YoqsK6QSRUfR7j+i@localhost>

> On 22/05/22 14:46,
> Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> > All --
> > I emailed the maintainer on May 12 but have received no reply.
> > Below is the email I sent.
> > The Punchline is that the DevIL SBo will not compile on my Slackware64
> > 15.0 + Multilib System when the nvidia-texture-tools SBo is installed.
> > The simplest fix is to turn off nvidia-texture-tools via a cmake Config
> <snip>
> > Is this the best place to post such info ?
> > Thanks everyone !
> > -- kjh
> This is the right place, usually we accept patches as attachments,
> but if this only the one flag.  I can take a look this week.
> We don't support multilib though, so do you know if it fails still on
> a non-multilib full 15.0 installation?

It still fails on pure 15.0.  The error I get is a missing
mvcore/Memory,h which was included in nvidia-texture-tools
but isn't in the version on SBo or the latest.

> Link to blog post on sending patches:
> https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html.
--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From dave at slackbuilds.org  Sun May 22 21:44:55 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 22 May 2022 22:44:55 +0100
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <YoqsK6QSRUfR7j+i@localhost>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost> <YoqsK6QSRUfR7j+i@localhost>
Message-ID: <Yoqu1yiWB5/AElIi@localhost>

> > On 22/05/22 14:46,
> > Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> > > All --
> > > I emailed the maintainer on May 12 but have received no reply.
> > > Below is the email I sent.
> > > The Punchline is that the DevIL SBo will not compile on my Slackware64
> > > 15.0 + Multilib System when the nvidia-texture-tools SBo is installed.
> > > The simplest fix is to turn off nvidia-texture-tools via a cmake Config
> > <snip>
> > > Is this the best place to post such info ?
> > > Thanks everyone !
> > > -- kjh
> > This is the right place, usually we accept patches as attachments,
> > but if this only the one flag.  I can take a look this week.
> > We don't support multilib though, so do you know if it fails still on
> > a non-multilib full 15.0 installation?
> It still fails on pure 15.0.  The error I get is a missing
> mvcore/Memory,h which was included in nvidia-texture-tools

nvcore/Memory.h even.

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From kjhambrick at gmail.com  Sun May 22 22:24:47 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 22 May 2022 17:24:47 -0500
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <20220522232803.f31d6c50346eb02570385e26@laposte.net>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost>
 <20220522232803.f31d6c50346eb02570385e26@laposte.net>
Message-ID: <CANBHt+OqmjU6QKYKcCEMwF9K5rph5y6L31qDtToGDK6vfZcMGw@mail.gmail.com>

On Sun, May 22, 2022 at 4:28 PM Arnaud via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> > On 22/05/22 14:46,
> > Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> > > All --
> > > I emailed the maintainer on May 12 but have received no reply.
> > > Below is the email I sent.
> > > The Punchline is that the DevIL SBo will not compile on my Slackware64
> > > 15.0 + Multilib System when the nvidia-texture-tools SBo is installed.
> > > The simplest fix is to turn off nvidia-texture-tools via a cmake Config
> > <snip>
> > > Is this the best place to post such info ?
> > > Thanks everyone !
> > > -- kjh
> >
> > This is the right place, usually we accept patches as attachments,
> > but if this only the one flag.  I can take a look this week.
> >
> > We don't support multilib though, so do you know if it fails still on
> > a non-multilib full 15.0 installation?
> >
> > Link to blog post on sending patches:
> > https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html.
>
> Well, I did reply, but my mail provider has been quite unprofessional
> lately.
> I'll look into it, and push an update.
>
>  - Yth / Arnaud.
>

Thanks Yth

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220522/f64266a3/attachment.htm>

From kjhambrick at gmail.com  Sun May 22 22:27:31 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 22 May 2022 17:27:31 -0500
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <Yoqei6RateVQWuf8@localhost>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost>
Message-ID: <CANBHt+OLLKoTfhr9Yw2XKBwZTmr7gp3QZG3k6+Y=3w_tPk4XrA@mail.gmail.com>

On Sun, May 22, 2022 at 3:35 PM Dave Woodfall <dave at slackbuilds.org> wrote:

> On 22/05/22 14:46,
> Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> > All --
> > I emailed the maintainer on May 12 but have received no reply.
>
> This is the right place, usually we accept patches as attachments,
> but if this only the one flag.  I can take a look this week.
>
> We don't support multilib though, so do you know if it fails still on
> a non-multilib full 15.0 installation?
>
> Link to blog post on sending patches:
> https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html.
>
Thanks Dave, next time.

I don't have another Machine for testing non-MultiLib.

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220522/4821089f/attachment.htm>

From kjhambrick at gmail.com  Sun May 22 22:42:19 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 22 May 2022 17:42:19 -0500
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <YoqsK6QSRUfR7j+i@localhost>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost> <YoqsK6QSRUfR7j+i@localhost>
Message-ID: <CANBHt+OVYp4t48+hwHcBfMM15o1cUpexATMM3u+L-ezPhqyiLw@mail.gmail.com>

On Sun, May 22, 2022 at 4:33 PM Dave Woodfall <dave at slackbuilds.org> wrote:

> > On 22/05/22 14:46,
> > Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
> > > All --
> > > I emailed the maintainer on May 12 but have received no reply.
> > > Below is the email I sent.
> > > The Punchline is that the DevIL SBo will not compile on my Slackware64
> > > 15.0 + Multilib System when the nvidia-texture-tools SBo is installed.
> > > The simplest fix is to turn off nvidia-texture-tools via a cmake Config
> > <snip># ---v from my original email to yth:
>  # ---v from my original email to yth:

> > Is this the best place to post such info ?
> > > Thanks everyone !
> > > -- kjh
> > This is the right place, usually we accept patches as attachments,
> > but if this only the one flag.  I can take a look this week.
> > We don't support multilib though, so do you know if it fails still on
> > a non-multilib full 15.0 installation?# grep usr/include/nvcore/Memory.h
> /var/log/packages/*
>
>
> /var/log/packages/nvidia-texture-tools-2.1.2-x86_64-1_SBo:usr/include/nvcore/Memory.h
>
>
>
> It still fails on pure 15.0.  The error I get is a missing
> mvcore/Memory,h which was included in nvidia-texture-tools
> but isn't in the version on SBo or the latest.
>
> > Link to blog post on sending patches:
> > https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html.
>
> Interesting catch Dave.

I DO have nvidia-texture-tools version 2.1.2 installed but I modified the
SBo to install the 'missing' files from /usr/include/nv*/

I mentioned in my original email that I installed the latest version of
nvtt to see if that fixed the DevIL SBO.

# ---v from my original email to yth:
I changed the nvidia-texture-tools CMakeLists.txt so that the header files
are installed in /usr/include/{nvtt,nvthread,nvmath,nvimage,nvcore}/
as well as installing nvconfig.h
# ---^ from my original email to yth:

ick.  What a mess.

I'll remove my modified nvtt ; reinstall the official
nvidia-texture-tools.SlackBuild and see what happens with the additional
cmake flag in the DevIL.SlackBuild:

   -DIL_USE_DXTC_NVIDIA=NO

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220522/4cc3c710/attachment.htm>

From kjhambrick at gmail.com  Sun May 22 22:55:34 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 22 May 2022 17:55:34 -0500
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <CANBHt+OVYp4t48+hwHcBfMM15o1cUpexATMM3u+L-ezPhqyiLw@mail.gmail.com>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost> <YoqsK6QSRUfR7j+i@localhost>
 <CANBHt+OVYp4t48+hwHcBfMM15o1cUpexATMM3u+L-ezPhqyiLw@mail.gmail.com>
Message-ID: <CANBHt+NVZxio3EoVELB5C93VD8CDd6Vj-yRUXBsS0PQUHg0mzA@mail.gmail.com>

On Sun, May 22, 2022 at 5:42 PM Konrad J Hambrick <kjhambrick at gmail.com>
wrote:

>
> On Sun, May 22, 2022 at 4:33 PM Dave Woodfall <dave at slackbuilds.org>
> wrote:
>
>> > On 22/05/22 14:46,
>> > Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
>> > > All --
>> > > I emailed the maintainer on May 12 but have received no reply.
>> > > Below is the email I sent.
>> > > The Punchline is that the DevIL SBo will not compile on my Slackware64
>> > > 15.0 + Multilib System when the nvidia-texture-tools SBo is installed.
>> > > The simplest fix is to turn off nvidia-texture-tools via a cmake
>> Config
>> > <snip># ---v from my original email to yth:
>>  # ---v from my original email to yth:
>
> > > Is this the best place to post such info ?
>> > > Thanks everyone !
>> > > -- kjh
>> > This is the right place, usually we accept patches as attachments,
>> > but if this only the one flag.  I can take a look this week.
>> > We don't support multilib though, so do you know if it fails still on
>> > a non-multilib full 15.0 installation?# grep
>> usr/include/nvcore/Memory.h /var/log/packages/*
>>
>>
>> /var/log/packages/nvidia-texture-tools-2.1.2-x86_64-1_SBo:usr/include/nvcore/Memory.h
>>
>>
>>
>> It still fails on pure 15.0.  The error I get is a missing
>> mvcore/Memory,h which was included in nvidia-texture-tools
>> but isn't in the version on SBo or the latest.
>>
>> > Link to blog post on sending patches:
>> > https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html
>> .
>>
>> Interesting catch Dave.
>
> I DO have nvidia-texture-tools version 2.1.2 installed but I modified the
> SBo to install the 'missing' files from /usr/include/nv*/
>
> I mentioned in my original email that I installed the latest version of
> nvtt to see if that fixed the DevIL SBO.
>
> # ---v from my original email to yth:
> I changed the nvidia-texture-tools CMakeLists.txt so that the header files
> are installed in /usr/include/{nvtt,nvthread,nvmath,nvimage,nvcore}/
> as well as installing nvconfig.h
> # ---^ from my original email to yth:
>
> ick.  What a mess.
>
> I'll remove my modified nvtt ; reinstall the official
> nvidia-texture-tools.SlackBuild and see what happens with the additional
> cmake flag in the DevIL.SlackBuild:
>
>    -DIL_USE_DXTC_NVIDIA=NO
>
> -- kjh
>
> All --

I removed nvidia-texture-tools-2.1.2 which included the extra include files.

Then I rebuild and installed nvidia-texture-tools-2.1.1 using the original
nvidia-texture-tools.SlackBuild ( log is attached )

Then I executed the attach
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220522/d584a207/attachment-0001.htm>

From kjhambrick at gmail.com  Sun May 22 23:02:01 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Sun, 22 May 2022 18:02:01 -0500
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <CANBHt+NVZxio3EoVELB5C93VD8CDd6Vj-yRUXBsS0PQUHg0mzA@mail.gmail.com>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost> <YoqsK6QSRUfR7j+i@localhost>
 <CANBHt+OVYp4t48+hwHcBfMM15o1cUpexATMM3u+L-ezPhqyiLw@mail.gmail.com>
 <CANBHt+NVZxio3EoVELB5C93VD8CDd6Vj-yRUXBsS0PQUHg0mzA@mail.gmail.com>
Message-ID: <CANBHt+OLHMWruQ4HMU6c7FkzmP=PM4X7_w=79o1AWV0N8FQ3pA@mail.gmail.com>

Sorry I hit [Send] instead of [Attach] ...

All --

I removed nvidia-texture-tools-2.1.2 which included the extra include files.

Then I rebuild and installed nvidia-texture-tools-2.1.1 using the original
nvidia-texture-tools.SlackBuild ( log is attached )

Then I executed the attached DevIL.SlackBuild which includes the new cmake
flag: -DIL_USE_DXTC_NVIDIA=NO

It builds fine and now I'll test it.

The punchline:  I believe all we need to do is add -DIL_USE_DXTC_NVIDIA=NO
to the cmake command in DevIL.SlackBuild

Thanks

-- kjh


On Sun, May 22, 2022 at 5:55 PM Konrad J Hambrick <kjhambrick at gmail.com>
wrote:

>
> On Sun, May 22, 2022 at 5:42 PM Konrad J Hambrick <kjhambrick at gmail.com>
> wrote:
>
>>
>> On Sun, May 22, 2022 at 4:33 PM Dave Woodfall <dave at slackbuilds.org>
>> wrote:
>>
>>> > On 22/05/22 14:46,
>>> > Konrad J Hambrick <kjhambrick at gmail.com> put forth the proposition:
>>> > > All --
>>> > > I emailed the maintainer on May 12 but have received no reply.
>>> > > Below is the email I sent.
>>> > > The Punchline is that the DevIL SBo will not compile on my
>>> Slackware64
>>> > > 15.0 + Multilib System when the nvidia-texture-tools SBo is
>>> installed.
>>> > > The simplest fix is to turn off nvidia-texture-tools via a cmake
>>> Config
>>> > <snip># ---v from my original email to yth:
>>>  # ---v from my original email to yth:
>>
>> > > Is this the best place to post such info ?
>>> > > Thanks everyone !
>>> > > -- kjh
>>> > This is the right place, usually we accept patches as attachments,
>>> > but if this only the one flag.  I can take a look this week.
>>> > We don't support multilib though, so do you know if it fails still on
>>> > a non-multilib full 15.0 installation?# grep
>>> usr/include/nvcore/Memory.h /var/log/packages/*
>>>
>>>
>>> /var/log/packages/nvidia-texture-tools-2.1.2-x86_64-1_SBo:usr/include/nvcore/Memory.h
>>>
>>>
>>>
>>> It still fails on pure 15.0.  The error I get is a missing
>>> mvcore/Memory,h which was included in nvidia-texture-tools
>>> but isn't in the version on SBo or the latest.
>>>
>>> > Link to blog post on sending patches:
>>> >
>>> https://slackblogs.blogspot.com/2022/03/how-to-send-patches-to-sbo.html.
>>>
>>> Interesting catch Dave.
>>
>> I DO have nvidia-texture-tools version 2.1.2 installed but I modified the
>> SBo to install the 'missing' files from /usr/include/nv*/
>>
>> I mentioned in my original email that I installed the latest version of
>> nvtt to see if that fixed the DevIL SBO.
>>
>> # ---v from my original email to yth:
>> I changed the nvidia-texture-tools CMakeLists.txt so that the header
>> files are installed in /usr/include/{nvtt,nvthread,nvmath,nvimage,nvcore}/
>> as well as installing nvconfig.h
>> # ---^ from my original email to yth:
>>
>> ick.  What a mess.
>>
>> I'll remove my modified nvtt ; reinstall the official
>> nvidia-texture-tools.SlackBuild and see what happens with the additional
>> cmake flag in the DevIL.SlackBuild:
>>
>>    -DIL_USE_DXTC_NVIDIA=NO
>>
>> -- kjh
>>
>> All --
>
> I removed nvidia-texture-tools-2.1.2 which included the extra include
> files.
>
> Then I rebuild and installed nvidia-texture-tools-2.1.1 using the original
> nvidia-texture-tools.SlackBuild ( log is attached )
>
> Then I executed the attach
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220522/9c854425/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DevIL.SlackBuild-1.8.0.log
Type: text/x-log
Size: 55592 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220522/9c854425/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DevIL.SlackBuild
Type: application/octet-stream
Size: 2433 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220522/9c854425/attachment-0001.obj>

From ozan.turkyilmaz at gmail.com  Mon May 23 04:42:42 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Mon, 23 May 2022 07:42:42 +0300
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <CANBHt+OLLKoTfhr9Yw2XKBwZTmr7gp3QZG3k6+Y=3w_tPk4XrA@mail.gmail.com>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost>
 <CANBHt+OLLKoTfhr9Yw2XKBwZTmr7gp3QZG3k6+Y=3w_tPk4XrA@mail.gmail.com>
Message-ID: <672c6994294bb234df352d5e77c0416e2f8afc35.camel@gmail.com>

Paz, 2022-05-22 tarihinde 17:27 -0500 saatinde, Konrad J Hambrick
yazd?:
> 
> I don't have another Machine for testing non-MultiLib.
> 

I have chroot to test in clean environment. I recommend it. Easy to
install?
and no performance hit from emulation.

Regards,
Ozan


From kjhambrick at gmail.com  Mon May 23 08:31:11 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Mon, 23 May 2022 03:31:11 -0500
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <672c6994294bb234df352d5e77c0416e2f8afc35.camel@gmail.com>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost>
 <CANBHt+OLLKoTfhr9Yw2XKBwZTmr7gp3QZG3k6+Y=3w_tPk4XrA@mail.gmail.com>
 <672c6994294bb234df352d5e77c0416e2f8afc35.camel@gmail.com>
Message-ID: <CANBHt+PsYJY3JDmndmxhRPwqeNZuwrKthv8Yj89Z409qssF0ew@mail.gmail.com>

On Sun, May 22, 2022 at 11:43 PM Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>
wrote:

> Paz, 2022-05-22 tarihinde 17:27 -0500 saatinde, Konrad J Hambrick
> yazd?:
> >
> > I don't have another Machine for testing non-MultiLib.
> >
> I have chroot to test in clean environment. I recommend it. Easy to
> install
> and no performance hit from emulation.
>
> Interesting Idea Ozan !

How did you set that up ?

Is the chroot env simply a virgin set of  /bin/ /etc/ /lib64/ and /usr/ ?

Did you need other directories -and-or- configs ?

Thanks !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220523/f0ee066d/attachment.htm>

From ozan.turkyilmaz at gmail.com  Mon May 23 08:59:35 2022
From: ozan.turkyilmaz at gmail.com (Ozan =?UTF-8?Q?T=C3=BCrky=C4=B1lmaz?=)
Date: Mon, 23 May 2022 11:59:35 +0300
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <CANBHt+PsYJY3JDmndmxhRPwqeNZuwrKthv8Yj89Z409qssF0ew@mail.gmail.com>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost>
 <CANBHt+OLLKoTfhr9Yw2XKBwZTmr7gp3QZG3k6+Y=3w_tPk4XrA@mail.gmail.com>
 <672c6994294bb234df352d5e77c0416e2f8afc35.camel@gmail.com>
 <CANBHt+PsYJY3JDmndmxhRPwqeNZuwrKthv8Yj89Z409qssF0ew@mail.gmail.com>
Message-ID: <ae4ca640d7cbc82c8b110370981f2991fee40501.camel@gmail.com>

Pzt, 2022-05-23 tarihinde 03:31 -0500 saatinde, Konrad J Hambrick yazd?
> > I have chroot to test in clean environment. I recommend it. Easy to
> > install?
> > and no performance hit from emulation.
> > 
> > 
> 
> Interesting Idea Ozan !
> 
> How did you set that up ?
> 
> Is the?chroot env simply a virgin set of ?/bin/ /etc/ /lib64/ and
> /usr/ ?
> 
> Did you need other directories -and-or- configs ?

I followed
this:?https://docs.slackware.com/howtos:general_admin:setting_up_a_slackware_chroot
Basically you can simply do installpkg --root /chroot-folder */*.t?z
and all folders will be fine.
The wiki doc is for creating 32bit chroot under 64bit system but you
can simply install 64bit packages?
instead of 32bit and you will be fine. For network connection, you need
to link /etc/resolv.conf rtp?
/chroot/etc/resolv.conf ?and you can use slackpkg to keep it up to date
as well. I use chroot to test?
new scripts or updates regularly.

Regards,
Ozan


From kjhambrick at gmail.com  Mon May 23 10:59:39 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Mon, 23 May 2022 05:59:39 -0500
Subject: [Slackbuilds-users] DevIL - Does not Compile when
 nvidia-texture-tools is installed
In-Reply-To: <ae4ca640d7cbc82c8b110370981f2991fee40501.camel@gmail.com>
References: <CANBHt+O9fdpf8RCivkXOBPS5r-Yz1gZ87gRHyXhB8V1O+0LcNQ@mail.gmail.com>
 <Yoqei6RateVQWuf8@localhost>
 <CANBHt+OLLKoTfhr9Yw2XKBwZTmr7gp3QZG3k6+Y=3w_tPk4XrA@mail.gmail.com>
 <672c6994294bb234df352d5e77c0416e2f8afc35.camel@gmail.com>
 <CANBHt+PsYJY3JDmndmxhRPwqeNZuwrKthv8Yj89Z409qssF0ew@mail.gmail.com>
 <ae4ca640d7cbc82c8b110370981f2991fee40501.camel@gmail.com>
Message-ID: <CANBHt+Na83YDDdeB0uL80BsQprrjZH7PxUg8=ivM=_=NYdv4AA@mail.gmail.com>

On Mon, May 23, 2022 at 4:00 AM Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>
wrote:

> Pzt, 2022-05-23 tarihinde 03:31 -0500 saatinde, Konrad J Hambrick yazd?
> > > I have chroot to test in clean environment. I recommend it. Easy to
> > > install
> > > and no performance hit from emulation.
> > >
> > >
> >
> > Interesting Idea Ozan !
> >
> > How did you set that up ?
> >
> > Is the chroot env simply a virgin set of  /bin/ /etc/ /lib64/ and
> > /usr/ ?
> >
> > Did you need other directories -and-or- configs ?
>
> I followed
> this:
> https://docs.slackware.com/howtos:general_admin:setting_up_a_slackware_chroot
> Basically you can simply do installpkg --root /chroot-folder */*.t?z
> and all folders will be fine.
> The wiki doc is for creating 32bit chroot under 64bit system but you
> can simply install 64bit packages
> instead of 32bit and you will be fine. For network connection, you need
> to link /etc/resolv.conf rtp
> /chroot/etc/resolv.conf  and you can use slackpkg to keep it up to date
> as well. I use chroot to test
> new scripts or updates regularly.
>
> Thanks again Ozan  !

I'll check it out.

It certainly will be useful for testing SBo's in a clean Environment !!

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220523/cf0e1a8f/attachment.htm>

From bgrundy at linuxleo.com  Tue May 24 21:52:20 2022
From: bgrundy at linuxleo.com (Barry J. Grundy)
Date: Tue, 24 May 2022 17:52:20 -0400
Subject: [Slackbuilds-users] python/pysqlite can be removed
Message-ID: <0637b77c-10d0-e98f-d4e6-11ed0f78e4ca@linuxleo.com>

python/pysqlite is largely unmaintained upstream (replaced by sqlite3 in 
the python standard library).? As far as I can tell nothing depends on 
it anymore.? Unless someone sees a reason to maintain it, can it be removed?

Thanks,

Barry


From dave at slackbuilds.org  Wed May 25 06:50:48 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Wed, 25 May 2022 07:50:48 +0100
Subject: [Slackbuilds-users] python/pysqlite can be removed
In-Reply-To: <0637b77c-10d0-e98f-d4e6-11ed0f78e4ca@linuxleo.com>
References: <0637b77c-10d0-e98f-d4e6-11ed0f78e4ca@linuxleo.com>
Message-ID: <Yo3RyA1IvRNfQ8Bp@localhost>

> python/pysqlite is largely unmaintained upstream (replaced by sqlite3 in the
> python standard library).? As far as I can tell nothing depends on it
> anymore.? Unless someone sees a reason to maintain it, can it be removed?
> Thanks,
> Barry

Done.

--
Dave

sbo-maintainer-tools:
https://slackbuilds.org/repository/15.0/system/sbo-maintainer-tools/
SBo templates:
https://slackbuilds.org/templates/
How to format github downloads:
https://slackbuilds.org/GITHUB_URLs.txt

From marav8 at free.fr  Thu May 26 14:42:03 2022
From: marav8 at free.fr (marav)
Date: Thu, 26 May 2022 16:42:03 +0200
Subject: [Slackbuilds-users] Maintain Spotify slackbuild
Message-ID: <311c69b7-b33c-3dfd-aedc-b84002b6b9e3@free.fr>

Hi,

I sent a mail to the current maintainer on May 21, and I haven't receive 
any response yet (mail attached)
I would like to maintain it if possible

Cheers all,
marav
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220526/16e91c76/attachment-0001.htm>
-------------- next part --------------
 

From marav8 at free.fr  Thu May 26 14:43:46 2022
From: marav8 at free.fr (marav)
Date: Thu, 26 May 2022 16:43:46 +0200
Subject: [Slackbuilds-users] Maintain Spotify slackbuild
In-Reply-To: <311c69b7-b33c-3dfd-aedc-b84002b6b9e3@free.fr>
References: <311c69b7-b33c-3dfd-aedc-b84002b6b9e3@free.fr>
Message-ID: <dbf92e0c-3f8a-0077-3907-831ec6a6616e@free.fr>

Le 26/05/2022 ? 16:42, marav a ?crit?:
>
> Hi,
>
> I sent a mail to the current maintainer on May 21, and I haven't 
> receive any response yet (mail attached)
> I would like to maintain it if possible
>
> Cheers all,
> marav
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ -https://slackbuilds.org/faq/
>
The original mail :

Content-Type: multipart/alternative;
  boundary="------------6YM8WxtElWOIzqDNjlcVSNd7"
Message-ID:<71c711e9-4365-e1bd-a28b-0e34d2aafd8a at free.fr>
Date: Sat, 21 May 2022 10:40:10 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
  Thunderbird/91.9.1
Content-Language: fr
To:slack.dhabyx at gmail.com
From: marav<marav8 at free.fr>
Subject: Spotify on SBo

This is a multi-part message in MIME format.
--------------6YM8WxtElWOIzqDNjlcVSNd7
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

Do you still maintain Spotify on slackbuild.org?
If not, can I get it back?

Cheers,
marav

--------------6YM8WxtElWOIzqDNjlcVSNd7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
   <head>

     <meta http-equiv="content-type" content="text/html; charset=UTF-8">
   </head>
   <body>
     <p><font size="4">Hi,</font></p>
     <p><font size="4">Do you still maintain Spotify on slackbuild.org?<br>
         If not, can I get it back?<br>
       </font></p>
     <p><font size="4">Cheers,<br>
         marav<br>
       </font></p>
   </body>
</html>

--------------6YM8WxtElWOIzqDNjlcVSNd7--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220526/222a9406/attachment.htm>

From slackbuilds at schoepfer.info  Fri May 27 07:45:36 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 27 May 2022 09:45:36 +0200
Subject: [Slackbuilds-users] Github project download links
Message-ID: <99ac9f5fd4b31f1bf9a21d8af6fd12db@schoepfer.info>

Hi,

i can't find the link to Dave's writeup about how to get correct links 
from github projects for the .info-file.
Is there a link somewhere on https://slackbuilds.org/ for that?

Thanks, Johannes

From marav8 at free.fr  Fri May 27 08:02:48 2022
From: marav8 at free.fr (marav)
Date: Fri, 27 May 2022 10:02:48 +0200
Subject: [Slackbuilds-users] Github project download links
In-Reply-To: <99ac9f5fd4b31f1bf9a21d8af6fd12db@schoepfer.info>
References: <99ac9f5fd4b31f1bf9a21d8af6fd12db@schoepfer.info>
Message-ID: <976968fb-ab96-9f3c-c82d-b1f68599d197@free.fr>

Le 27/05/2022 ? 09:45, Franzen via SlackBuilds-users a ?crit?:
> Hi,
>
> i can't find the link to Dave's writeup about how to get correct links 
> from github projects for the .info-file.
> Is there a link somewhere on https://slackbuilds.org/ for that?
>
> Thanks, Johannes
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
https://slackbuilds.org/GITHUB_URLs.txt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220527/f3c45e8b/attachment.htm>

From kjhambrick at gmail.com  Fri May 27 08:22:40 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Fri, 27 May 2022 03:22:40 -0500
Subject: [Slackbuilds-users] Github project download links
In-Reply-To: <976968fb-ab96-9f3c-c82d-b1f68599d197@free.fr>
References: <99ac9f5fd4b31f1bf9a21d8af6fd12db@schoepfer.info>
 <976968fb-ab96-9f3c-c82d-b1f68599d197@free.fr>
Message-ID: <CANBHt+NSvYJtph1_SUKaG+9c_4yiX9SFS7oDMK7OV9x53Mde5w@mail.gmail.com>

On Fri, May 27, 2022 at 3:02 AM marav <marav8 at free.fr> wrote:

> Le 27/05/2022 ? 09:45, Franzen via SlackBuilds-users a ?crit :
>
> Hi,
>
> i can't find the link to Dave's writeup about how to get correct links
> from github projects for the .info-file.
> Is there a link somewhere on https://slackbuilds.org/ for that?
>
> Thanks, Johannes
>
> https://slackbuilds.org/GITHUB_URLs.txt
>
Thank you marav !

Bookmarked.

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220527/2d2d9ba9/attachment.htm>

From willysr at slackbuilds.org  Sat May 28 02:46:43 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 28 May 2022 09:46:43 +0700
Subject: [Slackbuilds-users] Updates - 20220528.1
Message-ID: <f3f73090-8732-6f63-74bd-8effa33fefcd@slackbuilds.org>

Sat May 28 02:33:18 UTC 2022
academic/sage-bin: Fix .info.
audio/qpwgraph: Added (a PipeWire Graph Qt GUI Interface)
desktop/adwaita-qt: Updated for v 1.4.1.
desktop/anki: Remove Markdown from REQUIRES.
desktop/chrome-gnome-shell: Added (GNOME Shell Browser Integration)
desktop/gdm: Added (GNOME Display Manager)
desktop/gnome-backgrounds: Added (GNOME Backgrounds)
desktop/gnome-control-center: Added (GNOME Control Center)
desktop/gnome-session: Added (GNOME Session Manager)
desktop/gnome-settings-daemon: Added (GNOME Settings Daemon)
desktop/gnome-shell-extensions: Added (GNOME Shell Extensions)
desktop/gnome-shell: Added (GNOME Shell)
desktop/gnome-tweaks: Added (GNOME Tweaks)
desktop/mutter: Added (GNOME Display Server and Window Manager)
desktop/nautilus: Added (GNOME Files Application)
desktop/wmamixer: Fix github tarball handling.
development/arcan: Added (Display Server, MM Framework, Game Engine)
development/dbeaver-ce: Updated for version 22.0.5.
development/github-cli: Updated for version 2.11.1.
development/hugo: Updated for version 0.99.1.
development/onetrueawk: Added (port of original UNIX awk)
development/robotframework: Updated for version 5.0.1.
development/squeak-vm: Fix download URL.
development/uemacs: Update maintainer email.
development/xmake: Updated for version 2.6.6.
games/7kaa: Updated for version 2.15.5.
games/vkBasalt: Added (Vulkan post processing layer)
games/vkQuake: Updated for version 1.13.1. New email.
gis/gdal: Updated for version 3.5.0.
graphics/birdfont: Updated for version 2.32.0.
graphics/mangohud: Updated for v 0.6.7.1.
ham/codec2: Updated for version 1.0.3.
ham/cqrlog: Updated for version 2.5.2.
ham/flrig: Updated for version 1.4.5.
ham/svxlink: Updated for version 19.09.2.
libraries/libcurl-gnutls: Added (libcurl linked against gnutls)
libraries/libvmdk: Enable python3.
libraries/libxnvctrl: Updated for version 510.73.05.
misc/sbo-templates: Updated for version 1.3.5.
misc/wl-clipboard: Fix github content-disposition handling.
multimedia/mkvtoolnix: Updated for version 67.0.0
network/FireWorks: Update REQUIRES.
network/brave-browser: Updated for version 1.39.111.
network/ejabberd: Added (xmpp server)
network/element-desktop: Updated for version 1.10.13.
network/filezilla: Updated for version 3.60.0.
network/haproxy: Shorten CHANGELOG.
network/i2pd: Updated for version 2.42.1.
network/netqmail: Update HOMEPAGE and DOWNLOAD urls.
network/nextcloud-desktop: Updated for version 3.5.1.
network/ngrok: Updated for version 3.0.3.
network/putty: Updated for version 0.77.
network/qbittorrent: Updated for version 4.4.3.
network/qutebrowser-bin: Updated for version 2.5.1.
network/sfeed: Update for 1.5
network/signal-desktop: Updated for version 5.44.1.
network/teamviewer: Updated for version 15.30.3
network/tor-browser: Updated for version 11.0.13.
network/wsdd2: Updated for version 1.8.7.
network/yle-dl: Updated for version 20220518.
network/zoom-linux: Updated for version 5.10.6.3192.
office/calibre-bin: Updated for version 5.43.0.
office/epy: Added (terminal ebook reader)
office/khal: Update REQUIRES.
office/navi: Updated for version 2.20.1.
perl/perl-Math-BigInt-GMP: Updated for version 1.6011.
perl/perl-Math-BigInt: Updated for version 1.999831.
perl/perl-Math-MPFR: Updated for version 4.23.
python/cloudpickle: Updated for version 2.1.0.
python/cssselect: Build python3 support by default.
python/esptool: Updated for version 4.0.1.
python/plaso: Add missing data files.
python/pysqlite: Removed (use sqlite3).
python/python-oauthlib: Remove python3 test. Make python2 explicit.
python/python3-openpyxl: Updated for version 3.0.10.
python/tqdm: Updated for version 4.64.0.
python/typed_ast: Updated for version 1.5.4.
system/Type1_to_OTF: Update dependencies.
system/afdko: Updated for version 3.8.3.
system/bochs: New maintainer.
system/clamav: Updated for version 0.105.0.
system/epson-printer-utility: Update models. Remove qt4 requirment.
system/gnu-unifont: Reflow README.
system/guefi: Updated for version 0.2.0.
system/nvidia-driver: Updated for version 510.73.05.
system/nvidia-kernel: Updated for version 510.73.05.
system/nvidia-legacy390-driver: Updated for version 390.151.
system/nvidia-legacy390-kernel: Updated for version 390.151.
system/nvidia-legacy470-driver: Updated for version 470.129.06.
system/nvidia-legacy470-kernel: Updated for version 470.129.06.
system/password-store: Update README for optional dep.
system/sarasa-gothic: Added (CJK programming fonts)
system/slackrepo-hints: Updated for version 20220527.
system/ttf-hanazono: Updated for version 20170904.
system/xen-nox: Added (Xen Project Hypervisor)
+--------------------------+


-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220528/a69fb220/attachment.asc>

From d.zlatanidis at gmail.com  Sat May 28 08:06:41 2022
From: d.zlatanidis at gmail.com (Dimitris Zlatanidis)
Date: Sat, 28 May 2022 11:06:41 +0300
Subject: [Slackbuilds-users] SBo API
Message-ID: <f0fd400a-15aa-7da8-3c7a-1222aa8c9972@gmail.com>

Hi everybody,

Playing around with the repository, I have created an API for it.
Whoever thinks it will be helpful, let's take a look:


https://gitlab.com/dslackw/sboapi
http://dslackw.pythonanywhere.com/api/packages

Cheers,
Dimitris



-- 
Dimitris Zlatanidis
https://dslackw.gitlab.io/slpkg/
https://gitlab.com/dslackw


From dominik.drobek at o2.pl  Mon May 30 19:48:50 2022
From: dominik.drobek at o2.pl (Dominik Drobek)
Date: Mon, 30 May 2022 21:48:50 +0200
Subject: [Slackbuilds-users] SBo API
In-Reply-To: <f0fd400a-15aa-7da8-3c7a-1222aa8c9972@gmail.com>
References: <f0fd400a-15aa-7da8-3c7a-1222aa8c9972@gmail.com>
Message-ID: <4181a37c-4f7d-19a9-91a3-9628d16a0584@o2.pl>

Hi Dimitris,

Nice work.

I played with the API for a while, and I have a few comments from API 
user perspective:

1. Fields which contain multiple entries (e.g. "files", "md5sum" or 
"download") could be JSON arrays instead of long strings where entries 
are separated by whitespace.

2. Instead of an empty string (e.g. in "requires" field) it might be 
better to return an empty array.

3. The magic value "UNSUPPORTED" in "download" or "download_x86_64" 
fields seems unnecessary. I think having an empty array would be 
sufficient for API user to notice that, or to test against it. The value 
could be a JSON null if we wanted to be really expressive.

4. Leading "./" in "location" field is not needed. But I think it would 
be better to have a "category" instead of "location". There already is a 
"name" in API response, and "location" is just "category/name".

5. "short_description" field can be renamed to just "description" (it's 
the only description present in API response).

6. If we ever have a package name conflict across categories, what would 
the API endpoint /api/packages/<package_name> return? We don't seem to 
have such problem now, but we could potentially have one or more name 
clashes in the future. Having an endpoint 
/api/packages/<category>/<package_name> would be future-proof.


Taking into account suggestions 1-5, current API result:

{
   "4397": {
     "download": "UNSUPPORTED",
     "download_x86_64": 
"https://www.slsknet.org/SoulseekQt/Linux/SoulseekQt-2018-1-30-64bit-appimage.tgz",
     "files": "README SoulseekQt.SlackBuild SoulseekQt.desktop 
SoulseekQt.info doinst.sh selinux-stub.c slack-desc",
     "location": "./network/SoulseekQt",
     "md5sum": "",
     "md5sum_x86_64": "1d98331893bc9b9d45ba34f6523353ab",
     "name": "SoulseekQt",
     "requires": "",
     "short_description": "SoulseekQt (Soulseek P2P network client)",
     "version": "20180130"
   }
}

would become:

{
   "4397": {
     "category": "network",
     "download": [],
     "download_x86_64": [
 
"https://www.slsknet.org/SoulseekQt/Linux/SoulseekQt-2018-1-30-64bit-appimage.tgz"
     ],
     "files": [
       "README",
       "SoulseekQt.SlackBuild",
       "SoulseekQt.desktop",
       "SoulseekQt.info",
       "doinst.sh",
       "selinux-stub.c",
       "slack-desc"
     ],
     "md5sum": [],
     "md5sum_x86_64": [
       "1d98331893bc9b9d45ba34f6523353ab"
     ],
     "name": "SoulseekQt",
     "requires": [],
     "short_description": "SoulseekQt (Soulseek P2P network client)",
     "version": "20180130"
   }
}


Regards,
Dominik

From mjolnirdam at gmail.com  Thu May 26 03:00:37 2022
From: mjolnirdam at gmail.com (Damian Perticone)
Date: Thu, 26 May 2022 03:00:37 -0000
Subject: [Slackbuilds-users] arcan slackbuilds
Message-ID: <CAEW3CoEuavcz=XHitsydV0+-oOoo7uxpJjgX3D7Q1peAGJpcaA@mail.gmail.com>

Hi i made two arcan slackbuilds, i dont know which version would be better,
in test 2 i used a patch made by me using this info
https://github.com/letoram/arcan/issues/249
patch one was not made by me . Both create the same file path. which one
should i send for submission?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220526/c1d5335e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: arcantest1tar.gz
Type: application/gzip
Size: 5800 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220526/c1d5335e/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: arcantest2tar.gz
Type: application/gzip
Size: 3238 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220526/c1d5335e/attachment-0001.bin>