From dev at iotib.net  Thu Aug  1 20:01:52 2024
From: dev at iotib.net (Charadon)
Date: Thu, 1 Aug 2024 16:01:52 -0400
Subject: [Slackbuilds-users] slackbuilds.org not accessible via IPv6
In-Reply-To: <20240731023820.4c65b001@home.rlworkman.net>
References: <1e2facf0-f161-c317-89e5-2decc10869eb@dorfdsl.de>
 <20240731023820.4c65b001@home.rlworkman.net>
Message-ID: <d6421ed9-42fc-402d-aaf1-16f20d3245f0@iotib.net>

On my ftp server, I got my firewall set up so it only allows 1 
connection at a time and rate limits them to 1M. Did you guys try that 
out of curiosity? It works wonders at stopping bots from hitting my 
server. (I guess they timeout, or it's slow enough that it doesn't get 
me to the bandwidth limit)

Obviously 1M might be a bit too slow for a big server like 
slackbuilds.org =P


-----Original Message-----
From: Robby Workman [mailto:rworkman at slackbuilds.org]
Sent: Wednesday, July 31, 2024 03:38 AM -04
To: slackbuilds-users at slackbuilds.org
Subject: Re: [Slackbuilds-users] slackbuilds.org not accessible via IPv6

On Tue, 30 Jul 2024 12:50:36 +0200
Marco Moock <mm at dorfdsl.de> wrote:

Hello!
I can't access SBo via IPv6, no answer, no ICMP. I assume it is an
improperly configured firewall there.

Can somebody of the admins please investigate?


That is intentional.

Unfortunately, we were hit by a large number of bots from various
ipv6 addresses, each of which downloaded Slackware ISO images
repeatedly, which caused us to go *way* over the transfer bandwidth
allowed as part of our agreement with the colo host.

We've got better things to do than play cat-and-mouse, especially
when there's practically an infinite number of (cats|mice), and
we certainly have better things on which we can spend the insane
amounts of money that the game will cost us.

-RW


_______________________________________________
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 mm at dorfdsl.de  Fri Aug  2 04:20:26 2024
From: mm at dorfdsl.de (Marco Moock)
Date: Fri, 2 Aug 2024 06:20:26 +0200
Subject: [Slackbuilds-users] slackbuilds.org not accessible via IPv6
In-Reply-To: <d6421ed9-42fc-402d-aaf1-16f20d3245f0@iotib.net>
References: <1e2facf0-f161-c317-89e5-2decc10869eb@dorfdsl.de>
 <20240731023820.4c65b001@home.rlworkman.net>
 <d6421ed9-42fc-402d-aaf1-16f20d3245f0@iotib.net>
Message-ID: <20240802062026.523281e3@dorfdsl.de>

Am Thu, 1 Aug 2024 16:01:52 -0400
schrieb Charadon via SlackBuilds-users
<slackbuilds-users at slackbuilds.org>:

> On my ftp server, I got my firewall set up so it only allows 1 
> connection at a time and rate limits them to 1M. Did you guys try
> that out of curiosity? It works wonders at stopping bots from hitting
> my server. (I guess they timeout, or it's slow enough that it doesn't
> get me to the bandwidth limit)

IIRC Apache supports bandwidth limits, maybe they can be set per IP
network.

Fail2ban may be also used if the attacker really downloads only a
special file.

From willysr at slackbuilds.org  Sat Aug  3 08:22:13 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 3 Aug 2024 15:22:13 +0700
Subject: [Slackbuilds-users] Updates - 20240803.1
Message-ID: <0b8f53df-5e7b-492d-a147-fa13b9169de3@slackbuilds.org>

Sat Aug  3 08:06:18 UTC 2024
academic/ViennaRNA: patch to compile against swig_4.2
academic/bowtie2: Upgrade to version 2.5.4
academic/pyCRAC: Mark for x86_64.
academic/pysam: Upgrade to version 0.22.1
academic/xiphos: fix script typo
audio/qjackctl: Updated for version 1.0.0.
audio/tauonmb: Update script (Build 3).
desktop/nitrogen: updated maintainer email address
desktop/nwg-panel: Updated for version 0.9.37.
development/SQLAlchemy: Updated for version 2.0.31.
development/abseil-cpp: Update for 20240722.0
development/aws-cdk: Updated for version 2.151.0.
development/cargo-c: Updated for version 0.10.3.
development/github-cli: Updated for version 2.54.0.
development/github-desktop: Downgraded to version 3.4.1.
development/global: Updated for version 6.6.13
development/hugo: updated for version 0.130.0
development/jupyter-qtconsole: Update for 5.5.2
development/lua-language-server: Updated for version 3.10.0.
development/micro: updated maintainer email address
development/mongodb-compass: Updated for version 1.43.5.
development/php-apcu: Updated for version 5.1.23
development/php82: Updated for version 8.2.22
development/postman: Updated for version 11.5.0
development/pre-commit: Updated for version 3.8.0.
development/protobuf3: Updated for version 27.3.
development/python3-matplotlib: Updated for version 3.8.4.
development/vscode-bin: Updated for version 1.92.0.
development/xmake: Updated for version 2.9.4.
games/atari_8bit_utils: Updated for version 20240722_b2a017b.
games/mame: Updated for version 0.268.
games/rolldice: updated maintainer email address
games/zaz: correct typo in man page.
gis/gdal: Updated for version 3.9.1.
graphics/flameshot: Fix script.
graphics/inkscape: Remove comments.
graphics/pencil2d: Update deps.
graphics/ueberzugpp: Updated for version 2.9.6.
ham/gridtracker: Updated for version 1.24.0801.
ham/qlog: Updated for version 0.37.2.
libraries/grpc: Update for 1.65.3
libraries/libcurl-gnutls: Updated for version 8.9.1.
libraries/python3-contourpy: Added (library to calculate contours).
misc/moodbar: Added (Amarok Plugin).
misc/moreutils: Updated for version 0.69
multimedia/amarok: Added (Multimedia Player).
multimedia/amarok: Updated for version 3.1.0.
multimedia/filebot: Version bump to 5.1.4
multimedia/videomass: Updated for version 5.0.20.
network/aerc: Fix script.
network/aerc: Update email.
network/awscli-v2: Updated for version 2.17.18.
network/betterbird-bin: Added (Email Client).
network/brave-browser: Updated for version 1.68.134.
network/cinny-desktop: Updated for version 4.0.3.
network/discord: Version bump to 0.0.62
network/dnsproxy-bin: Updated for version 0.72.2.
network/dropbox: Updated for version 204.4.5420.
network/mullvadvpn-app: Updated for version 2024.4.
network/nextcloud-desktop: updated for version 3.13.2
network/ngrep: use a correct Github link
network/node_exporter: Added (Exporter for machine metrics).
network/radicale: Simplify extracting tarball
network/rspamd: Updated for version 3.9.1.
network/senpai: Added (terminal irc client).
network/signal-desktop: Update for version 7.18.0.
network/tailscale: updated for version 1.70.0.
network/telegram: Updated for version 5.3.0.
network/telegram: Updated for version 5.3.2.
network/translate-shell: Updated for version 0.9.7.1.
network/transmission: Updated for version 4.0.6.
network/whalebird: Updated for version 6.1.3.
network/yt-dlp: Updated for version 2024.08.01.
network/zoom-linux: Updated for version 6.1.6.1013
office/JabRef: Updated for version 5.15.
office/MasterPDFEditor5: Updated for version 5.9.85.
office/calibre-bin: Updated for version 7.16.0.
office/gnucash: fix script typo
office/pandoc-bin: updated for version 3.3.
office/pdfarranger: Upgrade to version 1.11.0
python/cryptography: Updated for version 43.0.0.
python/instaloader: Updated for version 4.12.1.
python/jellyfish: Updated for version 1.1.0.
python/mypy: Updated for version 1.11.1.
python/python3-aiohappyeyeballs: Added (Happy Eyeballs).
python/python3-aiohttp-socks: Updated for version 0.9.0.
python/python3-aiohttp: Updated for version 3.10.0.
python/python3-evdev: Added (Python3 of evdev).
python/python3-grpcio: Update for 1.65.3
python/python3-incremental: Reverted back to version 22.10.0.
python/python3-maturin: Updated for version 1.7.0.
python/python3-orjson: Updated for version 3.10.6.
python/python3-pdm-build-locked: Version bump to 0.3.3
python/python3-pdm: Version bump to 2.17.3
python/python3-pydantic-core: Updated for version 2.20.1.
python/python3-pydantic: Updated for version 2.8.2.
python/python3-pykeepass: Update for 4.1.0.post1
python/python3-pypandoc: Mark for x86_64.
python/python3-pysubs2: Version bump to 1.7.3
python/python3-pytest: Version bump to 8.3.2
python/python3-tenacity: Update for 9.0.0
python/python3-xkbcommon: Update for 1.0.1
python/python3-xkeysnail: Update deps.
ruby/ruby-build: Updated for version 20240727.
system/Solaar: Update deps.
system/apparmor: Updated for version 4.0.2.
system/arch-install-scripts: updated maintainer email address
system/atop: Updated for version 2.11.0.
system/b2: Updated for version 20240720_010024_9f95270.
system/docker-compose: Updated for version 2.29.1.
system/dracut: updated maintainer email address
system/ds4drv: Update deps.
system/dstat: use a correct Github link
system/fastfetch: Updated for version 2.20.0.
system/fwupd: Updated for version 1.9.22.
system/genext2fs: Updated for version 1.5.0
system/libratbag: Update deps.
system/lsyncd: Updated for version 2.3.1
system/mbuffer: updated maintainer email address
system/mongo-tools: Updated for version 100.10.0.
system/nix: Organize script.
system/nix: Revoke tests in builds.
system/openrc: Updated for version 0.54.2.
system/openzfs: updated maintainer email address
system/restic: Updated for version 0.17.0
system/sanoid: updated maintainer email address
system/sbo-maintainer-tools: Updated for version 0.9.1.
system/tabbed: Updated for version 0.8.
system/timeshift: Updated for version 24.06.03.
system/usermin: Updated for version 2.100.
system/virtualbox: fix error when starting
system/webmin: Updated for version 2.201.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From alik at ejik.org  Sat Aug  3 12:59:35 2024
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sat, 3 Aug 2024 15:59:35 +0300
Subject: [Slackbuilds-users] Updates - 20240803.1
In-Reply-To: <0b8f53df-5e7b-492d-a147-fa13b9169de3@slackbuilds.org>
References: <0b8f53df-5e7b-492d-a147-fa13b9169de3@slackbuilds.org>
Message-ID: <Zq4pt72x4uvEgiMd@ejik.org>

> office/MasterPDFEditor5: Updated for version 5.9.85.

Is it MasterPDFEditor5 or MasterPDFEditor as before?

Also, it seems that the source has a wrong md5sum:

ERROR: office/MasterPDFEditor: Failed md5sum:
master-pdf-editor-5.9.85-qt5.x86_64-qt_include.tar.gz

actual md5sum is 568064bee5b7d9b2b852acd24da49657

Best regards,
Alexander

From willysr at slackbuilds.org  Sat Aug  3 13:16:42 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 3 Aug 2024 20:16:42 +0700
Subject: [Slackbuilds-users] Updates - 20240803.1
In-Reply-To: <Zq4pt72x4uvEgiMd@ejik.org>
References: <0b8f53df-5e7b-492d-a147-fa13b9169de3@slackbuilds.org>
 <Zq4pt72x4uvEgiMd@ejik.org>
Message-ID: <c2c93b21-9952-4593-86f0-a2feaabbffa0@slackbuilds.org>

>> office/MasterPDFEditor5: Updated for version 5.9.85.
> 
> Is it MasterPDFEditor5 or MasterPDFEditor as before?
> 
> Also, it seems that the source has a wrong md5sum:
> 
> ERROR: office/MasterPDFEditor: Failed md5sum:
> master-pdf-editor-5.9.85-qt5.x86_64-qt_include.tar.gz
> 
> actual md5sum is 568064bee5b7d9b2b852acd24da49657

i think upstream changed the source during my commit and public update 
but i have them fixed on my branch already

the commit should be MasterPDFEditor


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

From 1.41421 at gmail.com  Sat Aug  3 16:06:30 2024
From: 1.41421 at gmail.com (Luveh Keraph)
Date: Sat, 3 Aug 2024 10:06:30 -0600
Subject: [Slackbuilds-users] Updates - 20240803.1
In-Reply-To: <c2c93b21-9952-4593-86f0-a2feaabbffa0@slackbuilds.org>
References: <0b8f53df-5e7b-492d-a147-fa13b9169de3@slackbuilds.org>
 <Zq4pt72x4uvEgiMd@ejik.org>
 <c2c93b21-9952-4593-86f0-a2feaabbffa0@slackbuilds.org>
Message-ID: <CAFy1yb3vx_s9yoJC_mbKun3_NzPZsPhsQX+_uRyeSsG8XLcGPQ@mail.gmail.com>

The link for the upstream Betterbird tarball used in Slackbuilds does not
exist in the Betterbird host.

On Sat, Aug 3, 2024 at 7:16?AM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> >> office/MasterPDFEditor5: Updated for version 5.9.85.
> >
> > Is it MasterPDFEditor5 or MasterPDFEditor as before?
> >
> > Also, it seems that the source has a wrong md5sum:
> >
> > ERROR: office/MasterPDFEditor: Failed md5sum:
> > master-pdf-editor-5.9.85-qt5.x86_64-qt_include.tar.gz
> >
> > actual md5sum is 568064bee5b7d9b2b852acd24da49657
>
> i think upstream changed the source during my commit and public update
> but i have them fixed on my branch already
>
> the commit should be MasterPDFEditor
>
>
> --
> Willy Sudiarto Raharjo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240803/82b47f08/attachment-0001.htm>

From willysr at slackbuilds.org  Sat Aug  3 22:16:48 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 4 Aug 2024 05:16:48 +0700
Subject: [Slackbuilds-users] Updates - 20240803.1
In-Reply-To: <CAFy1yb3vx_s9yoJC_mbKun3_NzPZsPhsQX+_uRyeSsG8XLcGPQ@mail.gmail.com>
References: <0b8f53df-5e7b-492d-a147-fa13b9169de3@slackbuilds.org>
 <Zq4pt72x4uvEgiMd@ejik.org>
 <c2c93b21-9952-4593-86f0-a2feaabbffa0@slackbuilds.org>
 <CAFy1yb3vx_s9yoJC_mbKun3_NzPZsPhsQX+_uRyeSsG8XLcGPQ@mail.gmail.com>
Message-ID: <47cb3e08-72a0-4ecc-a303-928c08207232@slackbuilds.org>

> The link for the upstream Betterbird tarball used in Slackbuilds does not
> exist in the Betterbird host.

Fixed in my branch
upstream removed the previous build and change the naming


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

From bobfunk11 at gmail.com  Mon Aug  5 16:23:39 2024
From: bobfunk11 at gmail.com (Bob Funk)
Date: Mon, 5 Aug 2024 11:23:39 -0500
Subject: [Slackbuilds-users] libhandy about to update to 1.8.3
In-Reply-To: <CAJOKJPaj2Q+0Rd-8r0SheRjpr=4K5j41TqXfJuAODEwJQ5PX7w@mail.gmail.com>
References: <04d8c3-9f9a-581c-3e81-b91f6e1c1755@slackware.uk>
 <a6e1dba6-2ee3-6acd-7dc2-eabc44a3dbb2@slackware.uk>
 <CAJOKJPaBCrJ_cXxxEW6Wvu1Bxos+7+UNEU0XuFDSQ+oSQXovYA@mail.gmail.com>
 <105693CC-CC01-4231-8797-9CF86D7F8F16@edison.tech>
 <CAJOKJPaj2Q+0Rd-8r0SheRjpr=4K5j41TqXfJuAODEwJQ5PX7w@mail.gmail.com>
Message-ID: <CAJOKJPaUpgACHsAq1XHbbjUw8Z94A1D2Pm1yWDN_7KzJoWOsKw@mail.gmail.com>

I've built libhandy-1.8.3 and all the gnome software that depends on it and
everything is building and running as expected here. Feel free to push that
update for this week's round of upgrades.

Regards,

Bob


On Mon, Jul 29, 2024 at 6:16?PM Bob Funk <bobfunk11 at gmail.com> wrote:

> I looked over the changes from libhandy 1.5.0 up to 1.8.0 and it's bug
> fixes, translation updates, and documentation switching to gi-docgen.
> Nothing major so no surprise if it works fine like Jay tested.
>
> Like I said, I'm not around my machines this week so if B Watson still
> wants to hold off till the following week's update that's fine by me too.
>
> Bob
>
> On Mon, Jul 29, 2024, 16:54 Jay Lanagan via SlackBuilds-users <
> slackbuilds-users at slackbuilds.org> wrote:
>
>> @Bob Funk:
>>
>> I?ve just booted up the sbo gnome desktop and all is working well with
>> updated libhandy over here. I don?t think the internal library has had a so
>> version bump either so it?s expected that it should be compatible either
>> way.
>>
>> Feels like a safe update to make from my point of view. All appears good.
>>
>> ? Jay Lanagan
>>
>>
>> On Jul 29, 2024 at 6:36 PM, <Bob Funk <bobfunk11 at gmail.com>> wrote:
>>
>> If the gnome stack of software is building then it'll probably be fine at
>> runtime too.
>>
>> I am traveling currently and won't be back home till next Sunday so I
>> won't be able to do much until after then. I'll be happy to build and test
>> it all when I get back.
>>
>> Cheers,
>>
>> Bob.
>>
>> On Mon, Jul 29, 2024, 15:42 B. Watson <urchlay at slackware.uk> wrote:
>>
>>>
>>>
>>> On Mon, 29 Jul 2024, B. Watson wrote:
>>>
>>> > I've test-built everything on the list except nwg-shell (because it
>>> > has 106 dependencies) and epiphany (waiting for webkit2gtk-4.1 to
>>> > finish building, as I write this).
>>>
>>> Update: epiphany builds and runs fine.
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>> _______________________________________________ SlackBuilds-users
>> mailing list SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>> _______________________________________________
>> 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/20240805/0ffee60e/attachment.htm>

From urchlay at slackware.uk  Mon Aug  5 17:50:01 2024
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 5 Aug 2024 13:50:01 -0400 (EDT)
Subject: [Slackbuilds-users] libhandy about to update to 1.8.3
In-Reply-To: <CAJOKJPaUpgACHsAq1XHbbjUw8Z94A1D2Pm1yWDN_7KzJoWOsKw@mail.gmail.com>
References: <04d8c3-9f9a-581c-3e81-b91f6e1c1755@slackware.uk>
 <a6e1dba6-2ee3-6acd-7dc2-eabc44a3dbb2@slackware.uk>
 <CAJOKJPaBCrJ_cXxxEW6Wvu1Bxos+7+UNEU0XuFDSQ+oSQXovYA@mail.gmail.com>
 <105693CC-CC01-4231-8797-9CF86D7F8F16@edison.tech>
 <CAJOKJPaj2Q+0Rd-8r0SheRjpr=4K5j41TqXfJuAODEwJQ5PX7w@mail.gmail.com>
 <CAJOKJPaUpgACHsAq1XHbbjUw8Z94A1D2Pm1yWDN_7KzJoWOsKw@mail.gmail.com>
Message-ID: <44aaa4e9-8e6-e1fe-dc62-2947b222b23e@slackware.uk>



On Mon, 5 Aug 2024, Bob Funk wrote:

> I've built libhandy-1.8.3 and all the gnome software that depends on it and everything is building and running as expected here. Feel free to push that update for this week's round
> of upgrades.

Thanks for checking it. Pushed to my branch, it'll be in the next update.

From j at lngn.net  Mon Aug  5 20:34:07 2024
From: j at lngn.net (Jay Lanagan)
Date: Mon, 05 Aug 2024 16:34:07 -0400
Subject: [Slackbuilds-users] cmark 0.31.1 Update
Message-ID: <9de64317007f28c7f8405b979a2e4860@lngn.net>

Hello all,

I'm writing to inform that I will be pushing an update to cmark this 
week to 0.31.1 which will require all dependees to be rebuilt. 
Everything has been checked for operation and all seems well so far. I 
do not anticipate any issues, but it's better to inform than ignore.

If anyone would like to test against, all one needs to do is change 
VERSION=0.31.1 to build. I've personally tested evolution and 
gnome-builder and they operate normally, and Lockywolf tested nheko 
which is the same.

This message is more to inform of the impending rebuilds needed for 
users and maintainers alike, but as always, if there's any issue upon 
testing and I should hold back the update, please let me know.

Thank you,

--
Jay Lanagan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240805/f87f2624/attachment.htm>

From bobfunk11 at gmail.com  Tue Aug  6 05:09:01 2024
From: bobfunk11 at gmail.com (Bob Funk)
Date: Tue, 6 Aug 2024 00:09:01 -0500
Subject: [Slackbuilds-users] cmark 0.31.1 Update
In-Reply-To: <9de64317007f28c7f8405b979a2e4860@lngn.net>
References: <9de64317007f28c7f8405b979a2e4860@lngn.net>
Message-ID: <CAJOKJPYh_=ZypM8E7xd2SLwN7sZ+eyx15Q7RkynxTgsTpYuOcg@mail.gmail.com>

I tested out cmark-0.31.1 with gnome-builder and evolution and they work
fine after a rebuild against the new .so library.

Bob

On Mon, Aug 5, 2024 at 3:34?PM Jay Lanagan <j at lngn.net> wrote:

> Hello all,
>
> I'm writing to inform that I will be pushing an update to cmark this week
> to 0.31.1 which will require all dependees to be rebuilt. Everything has
> been checked for operation and all seems well so far. I do not anticipate
> any issues, but it's better to inform than ignore.
>
> If anyone would like to test against, all one needs to do is change
> VERSION=0.31.1 to build. I've personally tested evolution and gnome-builder
> and they operate normally, and Lockywolf tested nheko which is the same.
>
> This message is more to inform of the impending rebuilds needed for users
> and maintainers alike, but as always, if there's any issue upon testing and
> I should hold back the update, please let me know.
> Thank you,
>
> --
> Jay Lanagan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240806/c68f012f/attachment-0001.htm>

From andrew.david.strong at gmail.com  Tue Aug  6 02:52:23 2024
From: andrew.david.strong at gmail.com (andrew)
Date: Tue, 6 Aug 2024 12:52:23 +1000
Subject: [Slackbuilds-users] Relinquishing scripts
Message-ID: <ZrGP526fmElVUjkv@ilium.andrews-corner.org>

Hi,

Due to some pretty major life changes I am retiring myself from the
following slackbuilds:

 * aom
 * courier-unicode
 * dav1d
 * exhale
 * gimp-plugin-export-layers
 * maildrop
 * nv-codec-headers
 * opustags
 * vvdec
 * vvenc
 * wavbreaker

I hope they all find a good home...

Andrew

-- 
You think that's air you're breathing now?

From j at lngn.net  Tue Aug  6 03:05:46 2024
From: j at lngn.net (Jay Lanagan)
Date: Mon, 05 Aug 2024 23:05:46 -0400
Subject: [Slackbuilds-users] cmark 0.31.1 Update
In-Reply-To: <CAJOKJPYh_=ZypM8E7xd2SLwN7sZ+eyx15Q7RkynxTgsTpYuOcg@mail.gmail.com>
References: <9de64317007f28c7f8405b979a2e4860@lngn.net>
 <CAJOKJPYh_=ZypM8E7xd2SLwN7sZ+eyx15Q7RkynxTgsTpYuOcg@mail.gmail.com>
Message-ID: <7e015c6277f0d0ad91afbb5a6b0b8d36@lngn.net>

Thank you for checking good sir!

The update has been pushed as of some hours ago, and it all checked out 
good on github, so it will go live on this weeks update push.

--
Jay Lanagan

On 2024-08-06 01:09, Bob Funk wrote:

> I tested out cmark-0.31.1 with gnome-builder and evolution and they 
> work fine after a rebuild against the new .so library.
> 
> Bob
> 
> On Mon, Aug 5, 2024 at 3:34?PM Jay Lanagan <j at lngn.net> wrote:
> 
>> Hello all,
>> 
>> I'm writing to inform that I will be pushing an update to cmark this 
>> week to 0.31.1 which will require all dependees to be rebuilt. 
>> Everything has been checked for operation and all seems well so far. I 
>> do not anticipate any issues, but it's better to inform than ignore.
>> 
>> If anyone would like to test against, all one needs to do is change 
>> VERSION=0.31.1 to build. I've personally tested evolution and 
>> gnome-builder and they operate normally, and Lockywolf tested nheko 
>> which is the same.
>> 
>> This message is more to inform of the impending rebuilds needed for 
>> users and maintainers alike, but as always, if there's any issue upon 
>> testing and I should hold back the update, please let me know.
>> 
>> Thank you,
>> 
>> --
>> Jay Lanagan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240805/9a388782/attachment.htm>

From jebrhansen+SBo at gmail.com  Tue Aug  6 03:32:47 2024
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Mon, 5 Aug 2024 20:32:47 -0700
Subject: [Slackbuilds-users] Relinquishing scripts
In-Reply-To: <ZrGP526fmElVUjkv@ilium.andrews-corner.org>
References: <ZrGP526fmElVUjkv@ilium.andrews-corner.org>
Message-ID: <CANi9qSs7q-=VZNRQ=23SqgZSwY6+hqi_8+azyHKvDr0f4E7eRg@mail.gmail.com>

I can take dav1d as an optional dependency for Kodi.

On Mon, Aug 5, 2024, 7:51?PM andrew <andrew.david.strong at gmail.com> wrote:

> Hi,
>
> Due to some pretty major life changes I am retiring myself from the
> following slackbuilds:
>
>  * aom
>  * courier-unicode
>  * dav1d
>  * exhale
>  * gimp-plugin-export-layers
>  * maildrop
>  * nv-codec-headers
>  * opustags
>  * vvdec
>  * vvenc
>  * wavbreaker
>
> I hope they all find a good home...
>
> Andrew
>
> --
> You think that's air you're breathing now?
> _______________________________________________
> 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/20240805/11705222/attachment.htm>

From bobfunk11 at gmail.com  Tue Aug  6 07:42:59 2024
From: bobfunk11 at gmail.com (Bob Funk)
Date: Tue, 6 Aug 2024 02:42:59 -0500
Subject: [Slackbuilds-users] Discrepancy between SLACKBUILDS.TXT MD5SUMs and
 .info file MD5SUMs in a couple slackbuilds.
Message-ID: <CAJOKJPY7NPf3DrqFX9=yjTuce1Yqn8E4xq2Ou_5fp2N6UUeQVw@mail.gmail.com>

Hello,

I was playing around with making some command line tools for parsing the
SLACKBUILDS.TXT file when I noticed a couple improperly listed MD5SUMs in
the SLACKBUILDS.TXT file.

The 'vst3sdk' slackbuild's md5sum in SLACKBUILDS.TXT is listed as:
SLACKBUILD MD5SUM:
463991d7841d15c719a7e06f052b70af42f09893f870635fea4f689aa6b9de989017e25a9ccb87d2de14a7936a37e58153f1eece19363900ccb9f49261e97ffd739bd26a2c2e786d9338e13042e20ee6cdc51a80c28577308b037caeeb274dd2f040faf28ba22514fcbe13667c1435ffb332b0cce26311a2a419b162be53ea54

The 'haskell-test-framework' slackbuild's md5sum in SLACKBUILDS.TXT is
listed as:
SLACKBUILD MD5SUM:
a7e351ab89c8513d2e41f5179c72e98526f4e157fbecb21dcc0d159686918d61

In both cases these are multiple md5sums that have been joined together
instead of separated by spaces, probably because the .info files for those
slackbuilds haven't put spaces between the individual md5sums and the new
line escaping backslashes. E.g: The 'haskell-test-framework.info' file has:

MD5SUM="a7e351ab89c8513d2e41f5179c72e985\
        26f4e157fbecb21dcc0d159686918d61"

When it should probably be:

MD5SUM="a7e351ab89c8513d2e41f5179c72e985 \
        26f4e157fbecb21dcc0d159686918d61"

Perhaps enforcing spaces before backslash/escape characters in .info
files should be done so the files are consistent? Could even be added
to sbolint I suppose.
I'm not sure what is generating that SLACKBUILDS.TXT but perhaps its
parsing code could also be adjusted to allow for those cases as an
alternate fix.

Thanks for your time,

Bob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240806/57f40878/attachment.htm>

From willysr at slackbuilds.org  Tue Aug  6 07:46:36 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 6 Aug 2024 14:46:36 +0700
Subject: [Slackbuilds-users] Discrepancy between SLACKBUILDS.TXT MD5SUMs
 and .info file MD5SUMs in a couple slackbuilds.
In-Reply-To: <CAJOKJPY7NPf3DrqFX9=yjTuce1Yqn8E4xq2Ou_5fp2N6UUeQVw@mail.gmail.com>
References: <CAJOKJPY7NPf3DrqFX9=yjTuce1Yqn8E4xq2Ou_5fp2N6UUeQVw@mail.gmail.com>
Message-ID: <b3c9de96-d8b2-48b9-8fa3-a1cd24df8e4b@slackbuilds.org>

> I was playing around with making some command line tools for parsing the 
> SLACKBUILDS.TXT file when I noticed a couple improperly listed MD5SUMs 
> in the SLACKBUILDS.TXT file.
> 
> The 'vst3sdk' slackbuild's md5sum in SLACKBUILDS.TXT is listed as:
> SLACKBUILD MD5SUM: 
> 463991d7841d15c719a7e06f052b70af42f09893f870635fea4f689aa6b9de989017e25a9ccb87d2de14a7936a37e58153f1eece19363900ccb9f49261e97ffd739bd26a2c2e786d9338e13042e20ee6cdc51a80c28577308b037caeeb274dd2f040faf28ba22514fcbe13667c1435ffb332b0cce26311a2a419b162be53ea54
> 
> The 'haskell-test-framework' slackbuild's md5sum in SLACKBUILDS.TXT is 
> listed as:
> SLACKBUILD MD5SUM: 
> a7e351ab89c8513d2e41f5179c72e98526f4e157fbecb21dcc0d159686918d61
> 
> In both cases these are multiple md5sums that have been joined together 
> instead of separated by spaces, probably because the .info files for 
> those slackbuilds haven't put spaces between the individual md5sums and 
> the new line escaping backslashes. E.g: The 'haskell-test-framework.info 
> <http://haskell-test-framework.info>' file has:
> 
> MD5SUM="a7e351ab89c8513d2e41f5179c72e985\ 26f4e157fbecb21dcc0d159686918d61"
> 
> When it should probably be:
> 
> MD5SUM="a7e351ab89c8513d2e41f5179c72e985 \ 26f4e157fbecb21dcc0d159686918d61"
> 
> Perhaps enforcing spaces before backslash/escape characters in .info 
> files should be done so the files are consistent? Could even be added to 
> sbolint I suppose.
> I'm not sure what is generating that SLACKBUILDS.TXT but perhaps its 
> parsing code could also be adjusted to allow for those cases as an 
> alternate fix.

Fixed in my branch

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x3F617144D7238786.asc
Type: application/pgp-keys
Size: 8363 bytes
Desc: OpenPGP public key
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240806/3a04bbdf/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240806/3a04bbdf/attachment-0001.asc>

From urchlay at slackware.uk  Tue Aug  6 08:13:45 2024
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 6 Aug 2024 04:13:45 -0400 (EDT)
Subject: [Slackbuilds-users] Discrepancy between SLACKBUILDS.TXT MD5SUMs
 and .info file MD5SUMs in a couple slackbuilds.
In-Reply-To: <CAJOKJPY7NPf3DrqFX9=yjTuce1Yqn8E4xq2Ou_5fp2N6UUeQVw@mail.gmail.com>
References: <CAJOKJPY7NPf3DrqFX9=yjTuce1Yqn8E4xq2Ou_5fp2N6UUeQVw@mail.gmail.com>
Message-ID: <4078dd54-622-9f97-dc78-b1b89babd951@slackware.uk>



On Tue, 6 Aug 2024, Bob Funk wrote:

> Perhaps enforcing spaces before backslash/escape characters in .info files should be done so the files are consistent? Could even be added to sbolint I suppose.
> I'm not sure what is generating that SLACKBUILDS.TXT but perhaps its parsing code could also be adjusted to allow for those cases as an alternate fix.

sbolint doesn't check for this... it does check that there are spaces
between multiple md5sums, but in the case of vst3sdk, there *are*
spaces, they're just on the next line (indentation on the line after
the \).

I could add an explicit check, wouldn't be much trouble. Looks like we
have 4 builds in the repo with this problem:

academic/gephi
development/openjdk8
haskell/haskell-test-framework
libraries/vst3sdk

Another check that should maybe be added: do we want to *require*
indendation on continuation lines? Example:

DOWNLOAD="http://whatever.com/blah.tgz \
http://other.com/foo.tgz"

The 2nd line ought to be indented. Same thing could happen with
md5sums... right now, these don't get checked for, and really they
don't cause any problems for tools like sbopkg or sboinstall. So how
picky should we be about whitespace?

From bobfunk11 at gmail.com  Tue Aug  6 09:10:47 2024
From: bobfunk11 at gmail.com (Bob Funk)
Date: Tue, 6 Aug 2024 04:10:47 -0500
Subject: [Slackbuilds-users] Discrepancy between SLACKBUILDS.TXT MD5SUMs
 and .info file MD5SUMs in a couple slackbuilds.
In-Reply-To: <4078dd54-622-9f97-dc78-b1b89babd951@slackware.uk>
References: <CAJOKJPY7NPf3DrqFX9=yjTuce1Yqn8E4xq2Ou_5fp2N6UUeQVw@mail.gmail.com>
 <4078dd54-622-9f97-dc78-b1b89babd951@slackware.uk>
Message-ID: <CAJOKJPZtbUptqFXNO5vzihneoVivM=fc-PykVCWLFiOAJSpCLw@mail.gmail.com>

Really the only problem is how the SLACKBUILDS.TXT presents the md5sums for
those cases, which is inconsistent with the rest of the md5sums in
SLACKBUILDS.TXT.

I was trying to leverage SLACKBUILDS.TXT with some parsing scripts and
expected to find whitespace there. I could use the info files instead to
get the correct md5sum info, I just wanted to raise the issue to the sbo
list in case there was something better that could be done.

It's not really the way the .info files are formatted, as you point out
with where the whitespace is on the next line. I guess it's more about
something wrong with how that SLACKBUILDS.TXT is parsing the info files to
generate those entries. Maybe that's a better place to fix it, so
additional requirements about md5sum formatting in info files aren't needed.

On Tue, Aug 6, 2024, 03:13 B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Tue, 6 Aug 2024, Bob Funk wrote:
>
> > Perhaps enforcing spaces before backslash/escape characters in .info
> files should be done so the files are consistent? Could even be added to
> sbolint I suppose.
> > I'm not sure what is generating that SLACKBUILDS.TXT but perhaps its
> parsing code could also be adjusted to allow for those cases as an
> alternate fix.
>
> sbolint doesn't check for this... it does check that there are spaces
> between multiple md5sums, but in the case of vst3sdk, there *are*
> spaces, they're just on the next line (indentation on the line after
> the \).
>
> I could add an explicit check, wouldn't be much trouble. Looks like we
> have 4 builds in the repo with this problem:
>
> academic/gephi
> development/openjdk8
> haskell/haskell-test-framework
> libraries/vst3sdk
>
> Another check that should maybe be added: do we want to *require*
> indendation on continuation lines? Example:
>
> DOWNLOAD="http://whatever.com/blah.tgz \
> http://other.com/foo.tgz"
>
> The 2nd line ought to be indented. Same thing could happen with
> md5sums... right now, these don't get checked for, and really they
> don't cause any problems for tools like sbopkg or sboinstall. So how
> picky should we be about whitespace?
> _______________________________________________
> 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/20240806/bad0ede2/attachment.htm>

From urchlay at slackware.uk  Tue Aug  6 18:20:16 2024
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 6 Aug 2024 14:20:16 -0400 (EDT)
Subject: [Slackbuilds-users] Discrepancy between SLACKBUILDS.TXT MD5SUMs
 and .info file MD5SUMs in a couple slackbuilds.
In-Reply-To: <CAJOKJPZtbUptqFXNO5vzihneoVivM=fc-PykVCWLFiOAJSpCLw@mail.gmail.com>
References: <CAJOKJPY7NPf3DrqFX9=yjTuce1Yqn8E4xq2Ou_5fp2N6UUeQVw@mail.gmail.com>
 <4078dd54-622-9f97-dc78-b1b89babd951@slackware.uk>
 <CAJOKJPZtbUptqFXNO5vzihneoVivM=fc-PykVCWLFiOAJSpCLw@mail.gmail.com>
Message-ID: <cc1ebc38-bbfc-b198-50b7-baef4e96670@slackware.uk>



On Tue, 6 Aug 2024, Bob Funk wrote:

> Really the only problem is how the SLACKBUILDS.TXT presents the md5sums for those cases, which is inconsistent with the rest of the md5sums in SLACKBUILDS.TXT.

Whatever you're writing that's going to read SLACKBUILDS.TXT, you
could pick apart the md5sums that are jammed together... all the
information is there, there just isn't a space between them. An md5sum
is always 32 hex digits, so your parsing code could rely on that
instead of requiring spaces.

Not a 'clean' solution, I know.

As to the script that generates SLACKBUILDS.TXT, I've never even
looked at it. It's from before my time... but now that someone's found
an actual bug in it, I'll see what I can do.

From mab974 at misouk.com  Tue Aug  6 18:37:32 2024
From: mab974 at misouk.com (Mab974)
Date: Tue, 6 Aug 2024 22:37:32 +0400
Subject: [Slackbuilds-users] Relinquishing scripts
In-Reply-To: <ZrGP526fmElVUjkv@ilium.andrews-corner.org>
References: <ZrGP526fmElVUjkv@ilium.andrews-corner.org>
Message-ID: <20240806223732.31924f9842edeff16bed34e7@misouk.com>

I can take care of

  * maildrop with courier-unicode
  * gimp-plugin-export-layers
  * wavbreaker

if no one absolutely wants one of them.


Selon andrew <andrew.david.strong at gmail.com> :
> Hi,
> 
> Due to some pretty major life changes I am retiring myself from the
> following slackbuilds:
> 
>  * aom
>  * courier-unicode
>  * dav1d
>  * exhale
>  * gimp-plugin-export-layers
>  * maildrop
>  * nv-codec-headers
>  * opustags
>  * vvdec
>  * vvenc
>  * wavbreaker
> 
> I hope they all find a good home...
> 
> Andrew
> 
> -- 
> You think that's air you're breathing now?
> _______________________________________________
> 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/
> 


-*- 
Mab974 <mab974 at misouk.com>

From urchlay at slackware.uk  Tue Aug  6 20:12:09 2024
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 6 Aug 2024 16:12:09 -0400 (EDT)
Subject: [Slackbuilds-users] Discrepancy between SLACKBUILDS.TXT MD5SUMs
 and .info file MD5SUMs in a couple slackbuilds.
In-Reply-To: <CAJOKJPZtbUptqFXNO5vzihneoVivM=fc-PykVCWLFiOAJSpCLw@mail.gmail.com>
References: <CAJOKJPY7NPf3DrqFX9=yjTuce1Yqn8E4xq2Ou_5fp2N6UUeQVw@mail.gmail.com>
 <4078dd54-622-9f97-dc78-b1b89babd951@slackware.uk>
 <CAJOKJPZtbUptqFXNO5vzihneoVivM=fc-PykVCWLFiOAJSpCLw@mail.gmail.com>
Message-ID: <d04b3568-9bec-238b-3ab9-f23a8f5e530@slackware.uk>



On Tue, 6 Aug 2024, Bob Funk wrote:

> Really the only problem is how the SLACKBUILDS.TXT presents the md5sums for those cases, which is inconsistent with the rest of the md5sums in SLACKBUILDS.TXT.

OK, take a look now: https://slackbuilds.org/slackbuilds/15.0/SLACKBUILDS.TXT

There were some that had the download files listed without spaces
between, for the same reason. All should be fixed now.

From lenardrspencer at gmail.com  Tue Aug  6 20:26:00 2024
From: lenardrspencer at gmail.com (Lenard Spencer)
Date: Tue, 6 Aug 2024 16:26:00 -0400
Subject: [Slackbuilds-users] Relinquishing scripts
In-Reply-To: <ZrGP526fmElVUjkv@ilium.andrews-corner.org>
References: <ZrGP526fmElVUjkv@ilium.andrews-corner.org>
Message-ID: <CANSA5-vMbijshdXpgvGCQay_ygL4-s6PJBd6XLT7cBo0ZMPKfg@mail.gmail.com>

I was going to take dav1d but Jeremy spoke first (it's been added to
-current anyway), but I will take nv-codec-headers (also added to -current
but I'll take it until it goes 15.1 stable).

On Mon, Aug 5, 2024 at 10:51?PM andrew <andrew.david.strong at gmail.com>
wrote:

> Hi,
>
> Due to some pretty major life changes I am retiring myself from the
> following slackbuilds:
>
>  * aom
>  * courier-unicode
>  * dav1d
>  * exhale
>  * gimp-plugin-export-layers
>  * maildrop
>  * nv-codec-headers
>  * opustags
>  * vvdec
>  * vvenc
>  * wavbreaker
>
> I hope they all find a good home...
>
> Andrew
>
> --
> You think that's air you're breathing now?
> _______________________________________________
> 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/20240806/2741f13a/attachment-0001.htm>

From bobfunk11 at gmail.com  Wed Aug  7 05:39:45 2024
From: bobfunk11 at gmail.com (Bob Funk)
Date: Wed, 7 Aug 2024 00:39:45 -0500
Subject: [Slackbuilds-users] Discrepancy between SLACKBUILDS.TXT MD5SUMs
 and .info file MD5SUMs in a couple slackbuilds.
In-Reply-To: <d04b3568-9bec-238b-3ab9-f23a8f5e530@slackware.uk>
References: <CAJOKJPY7NPf3DrqFX9=yjTuce1Yqn8E4xq2Ou_5fp2N6UUeQVw@mail.gmail.com>
 <4078dd54-622-9f97-dc78-b1b89babd951@slackware.uk>
 <CAJOKJPZtbUptqFXNO5vzihneoVivM=fc-PykVCWLFiOAJSpCLw@mail.gmail.com>
 <d04b3568-9bec-238b-3ab9-f23a8f5e530@slackware.uk>
Message-ID: <CAJOKJPZcctos4CCLLizx7NG4RqTc5hXMjfcEeGELzANowtbS=w@mail.gmail.com>

I just refreshed my SLACKBUILDS.TXT copy to test it out and everything's
good now. Thanks for looking into it.

@ willy: With the SLACKBUILDS.TXT file getting fixed by B. Watson, the
commits you added are technically no longer needed. The commits are
harmless though, so do what you want with it.

Thanks,

Bob.

On Tue, Aug 6, 2024 at 3:12?PM B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Tue, 6 Aug 2024, Bob Funk wrote:
>
> > Really the only problem is how the SLACKBUILDS.TXT presents the md5sums
> for those cases, which is inconsistent with the rest of the md5sums in
> SLACKBUILDS.TXT.
>
> OK, take a look now:
> https://slackbuilds.org/slackbuilds/15.0/SLACKBUILDS.TXT
>
> There were some that had the download files listed without spaces
> between, for the same reason. All should be fixed now.
> _______________________________________________
> 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/20240807/508edb50/attachment.htm>

From ltlnx at disroot.org  Wed Aug  7 08:54:37 2024
From: ltlnx at disroot.org (Wen-Wei Kao)
Date: Wed, 07 Aug 2024 16:54:37 +0800
Subject: [Slackbuilds-users] Request to remove CNS11643-font
Message-ID: <2144782.9o76ZdvQCi@localhost.localdomain>

Hi, 

The CNS11643-font upstream split the package into two, CNS11643-kai-font and 
CNS11643-sung-font, and I think I should split this into two packages too. 
Would it be OK to remove this (then I'll upload the two SlackBuilds), or is 
there other ways for doing this kind of splitting?

Cheers,
ltlnx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240807/3d499a44/attachment.asc>

From willysr at slackbuilds.org  Wed Aug  7 08:57:15 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 7 Aug 2024 15:57:15 +0700
Subject: [Slackbuilds-users] Request to remove CNS11643-font
In-Reply-To: <2144782.9o76ZdvQCi@localhost.localdomain>
References: <2144782.9o76ZdvQCi@localhost.localdomain>
Message-ID: <cf6c41b9-79da-4617-9658-18987f94242d@slackbuilds.org>

> The CNS11643-font upstream split the package into two, CNS11643-kai-font and
> CNS11643-sung-font, and I think I should split this into two packages too.
> Would it be OK to remove this (then I'll upload the two SlackBuilds), or is
> there other ways for doing this kind of splitting?

Sure, we can remove it so that you can submit 2 scripts

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

From ltlnx at disroot.org  Wed Aug  7 08:58:48 2024
From: ltlnx at disroot.org (Wen-Wei Kao)
Date: Wed, 07 Aug 2024 16:58:48 +0800
Subject: [Slackbuilds-users] Request to remove CNS11643-font
In-Reply-To: <cf6c41b9-79da-4617-9658-18987f94242d@slackbuilds.org>
References: <2144782.9o76ZdvQCi@localhost.localdomain>
 <cf6c41b9-79da-4617-9658-18987f94242d@slackbuilds.org>
Message-ID: <26512401.1r3eYUQgxm@localhost.localdomain>

? 2024?8?7? ??? ??4:57:15 [CST]?Willy Sudiarto Raharjo ??:
> > The CNS11643-font upstream split the package into two, CNS11643-kai-font
> > and CNS11643-sung-font, and I think I should split this into two packages
> > too. Would it be OK to remove this (then I'll upload the two
> > SlackBuilds), or is there other ways for doing this kind of splitting?
> 
> Sure, we can remove it so that you can submit 2 scripts

Thanks!

-- ltlnx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240807/ecea79e2/attachment.asc>

From willysr at slackbuilds.org  Sat Aug 10 01:31:38 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Aug 2024 08:31:38 +0700
Subject: [Slackbuilds-users] Updates - 20240810.1
Message-ID: <ced30a40-8c98-46d9-a262-e4562c2b4991@slackbuilds.org>

Sat Aug 10 01:22:10 UTC 2024
academic/gephi: Fix .info.
audio/pavucontrol-qt: Update for 1.4.0 (+new maintainer)
audio/qjackctl: Updated for version 1.0.1.
audio/rack: Updated for version 2.5.2.
audio/vamp-plugin-sdk: Updated for version 2.10.0.
desktop/mint-l-icons: Updated for version 1.7.2.
desktop/mint-l-theme: Updated for version 1.9.8.
desktop/nwg-shell: Updated for version 0.5.37.
desktop/xdgmenumaker: Updated for version 2.3.
development/bbe: Added (sed-like binary editor).
development/boron: Updated for version 2.1.0.
development/c_count: Updated for version 7.23.
development/cloc: Updated for version 2.02.
development/cproto: Updated for version 4.7w.
development/gitlab-cli: Updated for version 1.45.0
development/heroku-cli: Updated for version 9.1.0
development/hugo: Updated for version 0.131.0.
development/kotlin: Updated for version 2.0.10.
development/lua-language-server: Updated for version 3.10.3.
development/mold: Updated for version 2.33.0.
development/mysql-workbench: Update bundle MySQL.
development/openjdk8: Fix .info.
development/postman: Updated for version 11.7.0
development/qb64pe: Updated for version 3.14.0.
development/rider: Updated for version 2024.1.5.
development/rstudio-desktop-legacy: Update HOMEPAGE
development/rstudio-desktop: Update for 2024.04.2+764 (+new maintainer)
development/sbcl: Updated for version 2.4.7.
development/vscode-bin: Updated for version 1.92.1.
development/yarn: Updated for version 1.22.22.
games/alephone: Updated for version 20240712.
games/chocolate-doom: Updated for version 3.1.0.
games/gzdoom: Updated for version 4.12.2.
games/mame: Add groovy patch.
games/marathon-data: Updated for version 20240712.
games/marathon-infinity-data: Updated for version 20240712.
games/marathon2-data: Updated for version 20240712.
games/trs80gp: Updated for version 2.5.3.
games/uqm-megamod: Updated for version 0.8.3.
games/xroar: Updated for version 1.5.5.
games/xu4: Updated for version 1.4.
git/ci: Update CI dependencies.
graphics/flameshot: Compress man pages.
graphics/openscad-mcad: Updated for version 2021.10.25.bd0a7ba.
ham/redsea: Updated for version 1.0.1.
haskell/haskell-test-framework: Fix .info.
libraries/cmark: Updated for version 0.31.1.
libraries/faun: Updated for version 0.1.5.
libraries/gcab: Updated to 1.5 + new maintainer
libraries/grpc: Update for 1.65.4
libraries/libhandy: Updated for version 1.8.3.
libraries/libheif: Updated for version 1.18.2.
libraries/libmseed: Updated for version 3.1.3.
libraries/skalibs: Updated for version 2.14.2.0
libraries/td_lib: Updated for version 20240421.
libraries/vst3sdk: Fix .info.
libraries/zmusic: Updated for version 1.1.13.
libraries/zziplib: Updated for version 0.13.77.
misc/discount: Note to self.
misc/simh-classic: Updated for version 3.12_5.
misc/vttest: Updated for version 2.7.20240708.
multimedia/pipe-viewer: Updated for version 0.5.1.
multimedia/vkeybd: Updated for version 0.1.18e.
network/amavisd-new: Updated for version 2.13.1.
network/betterbird-bin: Switch to official release.
network/brave-browser: Updated for version 1.68.137.
network/cinny-desktop: Updated for version 4.1.0.
network/discord: Updated for version 0.0.63.
network/dnsproxy-bin: Updated for version 0.72.3.
network/dothost: Updated for version 0.2.1.
network/dropbox: Updated for version 205.4.5765.
network/freedownloadmanager: Updated for version 6.24.0.5820.
network/gallery-dl: Updated for version 1.27.2.
network/librewolf: Updated for version 128.0.3
network/microsoft-edge: Updated for version 127.0.2651.86.
network/plasma-nm-openconnect: Added (NetworkManager Plugin).
network/scrcpy: Updated for version 2.6.1
network/signal-desktop: Updated for version 7.19.0.
network/slack: Updated for version 4.39.95.
network/tor-browser: Updated for version 13.5.2.
network/vivaldi: Updated for version 6.8.3381.53.
network/weechat: Updated for version 4.3.5.
network/whatsie: Updated for version 4.15.3.
office/MasterPDFEditor: Fix MD5SUM.
perl/MoarVM: Updated for version 2024.07
perl/nqp: Updated for version 2024.07
perl/perl-Email-MIME-ContentType: Added (Parse and build a MIME 
Content-Type).
perl/perl-Email-MIME-Encodings: Added (A unified interface to MIME).
perl/perl-Email-MessageID: Added (Generate world unique message-ids).
perl/perl-Email-Simple: Added (simple parsing of RFC2822).
perl/perl-MooX-Types-MooseLike: Added (Moosish types).
perl/perl-Net-IDN-Encode: Added (Internationalizing Domain Names in 
Applications).
perl/perl-Test-File-ShareDir: Added (Perl Module).
perl/perl-Throwable: Added (role for classes).
perl/rakudo: Updated for version 2024.07
perl/zef: Updated for version 0.22.1
python/python-evdev: Removed (renamed to python3-evdev)
python/python3-aiohappyeyeballs: Cleanup SlackBuild script.
python/python3-aiohappyeyeballs: Updated for version 2.3.5.
python/python3-aiohttp: Updated for version 3.10.1.
python/python3-aiohttp: Updated for version 3.10.2.
python/python3-debugpy: Update for 1.8.3
python/python3-debugpy: Update for 1.8.5
python/python3-dunamai: Added (Dynamic version generation).
python/python3-grpcio: Update for 1.65.4
python/python3-h5py: Update for 3.11.0 (+new maintainer)
python/python3-keyring: Update for 25.3.0
python/python3-librosa: Updated for version 0.10.2.post1.
python/python3-poetry-dynamic-versioning: Added (Plugin for Poetry).
python/python3-pyspf: Added (Sender-Policy-Framework queries in Python).
python/python3-tox: Updated for version 4.17.1.
system/CNS11643-font: Removed (Split into 2 new scripts).
system/Iosevka-slab: Updated for version 31.1.0.
system/Iosevka: Updated for version 31.1.0.
system/colorize: Updated for version 0.66.
system/conky: Updated for version 1.21.6.
system/cronie: Updated for version 1.7.2.
system/ded: Updated for version 20240424.
system/earlyoom: Updated for version 1.8.2.
system/execline: Updated for version 2.9.6.0
system/gdu: Added (disk usage analyzer).
system/k3s: Updated to 1.30.3.1.
system/limine: Fix permission.
system/limine: Updated for version 8.0.0
system/openrc-settingsd: Updated for version 1.5.0.
system/polychromatic: Updated for version 0.8.6.
system/prometheus: Updated for version 2.54.0.
system/s6-rc: Updated for version 0.5.4.3
system/s6: Updated for version 2.13.0.0
system/sbo-maintainer-tools: Updated for version 0.9.2.1.
system/telegraf: Updated for version 1.31.2
system/xprintidle: Updated for version 0.3.0.
system/zramen: Updated for version 0.7.0.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From arkadiusz at drabczyk.org  Sun Aug 11 18:03:16 2024
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Sun, 11 Aug 2024 20:03:16 +0200
Subject: [Slackbuilds-users] always run `mandb -c` after installing/removing
 manpages?
Message-ID: <Zrj85MUkLZrauMqa@comp..>

In most packages manual page index caches are not updated which leads
to the following situation:

$ man -k zathura
zathura: nothing appropriate.

man -k can find the manpages only when caches are updated:

$ sudo mandb -c
$ man -k zathura
zathura (1)          - a document viewer
zathurarc (5)        - zathura configuration file

Unfortunately it takes some time, for example 10 seconds on my system.

sbopkglint already has 60-usr_info.t.sh, should a similar error
regarding manpages also be addded?

I know there is /etc/cron.daily/man-db but the command specified there
does not traverse /usr/man/man1/ where zathura manpages are located
for some reason:

$ man -w zathura
/usr/man/man1/zathura.1.gz

-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From urchlay at slackware.uk  Sun Aug 11 21:52:29 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 11 Aug 2024 17:52:29 -0400 (EDT)
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <Zrj85MUkLZrauMqa@comp..>
References: <Zrj85MUkLZrauMqa@comp..>
Message-ID: <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk>



On Sun, 11 Aug 2024, Arkadiusz Drabczyk wrote:

> In most packages manual page index caches are not updated which leads
> to the following situation:
>
> $ man -k zathura
> zathura: nothing appropriate.
>
> man -k can find the manpages only when caches are updated:
>
> $ sudo mandb -c
> $ man -k zathura
> zathura (1)          - a document viewer
> zathurarc (5)        - zathura configuration file
>
> Unfortunately it takes some time, for example 10 seconds on my system.

It takes a lot longer than 10 seconds on my system... long enough that
users would be highly annoyed if they had to wait for it to finish
every time they install or remove a package (and wait for it *twice*
when doing upgradepkg, since it does both installpkg and removepkg).

I just ran your command (sudo mandb -c) and it took 9 minutes and 25
seconds. And that's on a machine that uses a pretty fast SSD. Hate to
think how long it would take with a spinning-platter hard disk.

Actually... are you sure your "10 seconds" figure is based on running
with the -c option? Try "time mandb -c", as root.

> sbopkglint already has 60-usr_info.t.sh, should a similar error
> regarding manpages also be addded?

I think the overhead of constantly regenerating the man database is
just too high. Users who never even use "man -k" would be forced to
pay the penalty for it.

> I know there is /etc/cron.daily/man-db but the command specified there
> does not traverse /usr/man/man1/ where zathura manpages are located
> for some reason:
>
> $ man -w zathura
> /usr/man/man1/zathura.1.gz

Looking at it... the main difference is that your command has "-c",
and the cron job doesn't. -c means "create database from scratch"
instead of updating it if it already exists. Leaving off the -c makes
it run much faster.

However, it appears that leaving off the -c also prevents mandb from
adding the zathura man page to its database. I wonder if this is the
intended behaviour, or if it might be considered a bug in mandb.

The flip side of the coin: After "removepkg zathura", it still shows
up in the man database. Doing "mandb" without the -c does remove it,
and takes about 8 seconds. Behold:

---------------
<root at xiphos:~># man -k zathura
zathura (1)          - a document viewer
zathurarc (5)        - zathura configuration file
<root at xiphos:~># removepkg zathura &> /dev/null
<root at xiphos:~># man -k zathura
zathura (1)          - a document viewer
zathurarc (5)        - zathura configuration file
<root at xiphos:~># time mandb &>/dev/null

real	0m7.254s
user	0m5.198s
sys	0m5.093s
<root at xiphos:~># man -k zathura
zathura: nothing appropriate.
---------------

So it might be considered OK to run mandb (without -c) in a
douninst.sh script. I hate to make it a hard requirement though.

For the doinst.sh, here's a thing: The mandb command has a -f option
that makes it add a single man page to the database. It runs quickly
(less than 1 second), and seems to work fine. Right after installing
the zathura package:

---------------
<root at xiphos:~># man -k zathura
zathura: nothing appropriate.
<root at xiphos:~># mandb -f /usr/man/man1/zathura.1.gz 
mandb: warning: $MANPATH set, inserting /etc/man_db.conf
Processing manual pages under /usr/man...
1 man subdirectory contained newer manual pages.
1 manual page was added.
<root at xiphos:~># mandb -f /usr/man/man5/zathurarc.5.gz 
mandb: warning: $MANPATH set, inserting /etc/man_db.conf
Processing manual pages under /usr/man...
1 man subdirectory contained newer manual pages.
1 manual page was added.
<root at xiphos:~># man -k zathura
zathura (1)          - a document viewer
zathurarc (5)        - zathura configuration file
---------------

So... for doinst.sh, it would make sense to have a "mandb -f" command
for each man page in the package.

Unfortunately the -f option doesn't help with removing entries from
the database. "mandb -c" is the only way I've found to do that, and it
takes forever.

We may add "mandb -f" to our doinst.sh template. If I add a check for
it to sbopkglint, it will be a "note" (not an error or a warning),
since we have thousands of existing SlackBuilds that will fail the
check. Each one would have to be updated (a doinst.sh added, or the
existing one modified), to make it lint-compliant, if it were an error
or warning.

None of this is set in stone. Discussion is welcome.

From arkadiusz at drabczyk.org  Mon Aug 12 08:15:36 2024
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Mon, 12 Aug 2024 10:15:36 +0200
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk>
Message-ID: <ZrnEqGBNrTUB7qTG@comp..>

On Sun, Aug 11, 2024 at 05:52:29PM -0400, B. Watson wrote:
> 
> 
> On Sun, 11 Aug 2024, Arkadiusz Drabczyk wrote:
> 
> > In most packages manual page index caches are not updated which leads
> > to the following situation:
> > 
> > $ man -k zathura
> > zathura: nothing appropriate.
> > 
> > man -k can find the manpages only when caches are updated:
> > 
> > $ sudo mandb -c
> > $ man -k zathura
> > zathura (1)          - a document viewer
> > zathurarc (5)        - zathura configuration file
> > 
> > Unfortunately it takes some time, for example 10 seconds on my system.
> 
> It takes a lot longer than 10 seconds on my system... long enough that
> users would be highly annoyed if they had to wait for it to finish
> every time they install or remove a package (and wait for it *twice*
> when doing upgradepkg, since it does both installpkg and removepkg).
> 
> I just ran your command (sudo mandb -c) and it took 9 minutes and 25
> seconds. And that's on a machine that uses a pretty fast SSD. Hate to
> think how long it would take with a spinning-platter hard disk.
> 
> Actually... are you sure your "10 seconds" figure is based on running
> with the -c option? Try "time mandb -c", as root.

I ran it as root of course, it wouldn't work on /usr/man/man1 if I
didn't since it is writable only by root. How many manpages do you
have? Is this system under heavy load?

> > sbopkglint already has 60-usr_info.t.sh, should a similar error
> > regarding manpages also be addded?
> 
> I think the overhead of constantly regenerating the man database is
> just too high. Users who never even use "man -k" would be forced to
> pay the penalty for it.

Well the same can be said about the info database.

> > I know there is /etc/cron.daily/man-db but the command specified there
> > does not traverse /usr/man/man1/ where zathura manpages are located
> > for some reason:
> > 
> > $ man -w zathura
> > /usr/man/man1/zathura.1.gz
> 
> Looking at it... the main difference is that your command has "-c",
> and the cron job doesn't. -c means "create database from scratch"
> instead of updating it if it already exists. Leaving off the -c makes
> it run much faster.
> 
> However, it appears that leaving off the -c also prevents mandb from
> adding the zathura man page to its database. I wonder if this is the
> intended behaviour, or if it might be considered a bug in mandb.

I was going to read the code to find out if it's a bug or a feature.

> The flip side of the coin: After "removepkg zathura", it still shows
> up in the man database. Doing "mandb" without the -c does remove it,
> and takes about 8 seconds. Behold:
> 
> ---------------
> <root at xiphos:~># man -k zathura
> zathura (1)          - a document viewer
> zathurarc (5)        - zathura configuration file
> <root at xiphos:~># removepkg zathura &> /dev/null
> <root at xiphos:~># man -k zathura
> zathura (1)          - a document viewer
> zathurarc (5)        - zathura configuration file
> <root at xiphos:~># time mandb &>/dev/null
> 
> real	0m7.254s
> user	0m5.198s
> sys	0m5.093s
> <root at xiphos:~># man -k zathura
> zathura: nothing appropriate.
> ---------------
> 
> So it might be considered OK to run mandb (without -c) in a
> douninst.sh script. I hate to make it a hard requirement though.
> 
> For the doinst.sh, here's a thing: The mandb command has a -f option
> that makes it add a single man page to the database. It runs quickly
> (less than 1 second), and seems to work fine. Right after installing
> the zathura package:
> 
> ---------------
> <root at xiphos:~># man -k zathura
> zathura: nothing appropriate.
> <root at xiphos:~># mandb -f /usr/man/man1/zathura.1.gz mandb: warning:
> $MANPATH set, inserting /etc/man_db.conf
> Processing manual pages under /usr/man...
> 1 man subdirectory contained newer manual pages.
> 1 manual page was added.
> <root at xiphos:~># mandb -f /usr/man/man5/zathurarc.5.gz mandb: warning:
> $MANPATH set, inserting /etc/man_db.conf
> Processing manual pages under /usr/man...
> 1 man subdirectory contained newer manual pages.
> 1 manual page was added.
> <root at xiphos:~># man -k zathura
> zathura (1)          - a document viewer
> zathurarc (5)        - zathura configuration file
> ---------------
> 
> So... for doinst.sh, it would make sense to have a "mandb -f" command
> for each man page in the package.
> 
> Unfortunately the -f option doesn't help with removing entries from
> the database. "mandb -c" is the only way I've found to do that, and it
> takes forever.

hmm didn't you just say a few lines above that mandb without -c
removes the manpage?

-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From urchlay at slackware.uk  Mon Aug 12 09:30:48 2024
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 12 Aug 2024 05:30:48 -0400 (EDT)
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <ZrnEqGBNrTUB7qTG@comp..>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk> <ZrnEqGBNrTUB7qTG@comp..>
Message-ID: <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>



On Mon, 12 Aug 2024, Arkadiusz Drabczyk wrote:

> I ran it as root of course, it wouldn't work on /usr/man/man1 if I
> didn't since it is writable only by root.

I meant, are you sure when you timed it and got 10 seconds, that you
were actually using the -c option? I get pretty close to 10 seconds
when I time it *without* -c. If you really get "mandb -c" to run in
only 10 seconds, that's 60x as fast as it does for me, and I want to
know how (so I can make it run that fast for me, too).

> How many manpages do you have? Is this system under heavy load?

The timing test was done on an otherwise-idle system. I have a
lot of SBo packages installed: there are 47918 man pages. But, a
clean install of Slackware 15.0 has 21101 man pages (and on a clean
install with an SSD, the 9+ minutes becomes about 4 minutes; still
too long). On my laptop with a spinning-platter drive and a clean 15.0
install, the 4 minutes becomes 30.

Anyway, as you point out, "mandb -c" isn't actually needed in either
doinst.sh or douninst.sh...

>> I think the overhead of constantly regenerating the man database is
>> just too high. Users who never even use "man -k" would be forced to
>> pay the penalty for it.
>
> Well the same can be said about the info database.

When I wrote that, I was still thinking "mandb -c" would be required.
mandb without the -c is all that's needed, and that's fast enough.

>> However, it appears that leaving off the -c also prevents mandb from
>> adding the zathura man page to its database. I wonder if this is the
>> intended behaviour, or if it might be considered a bug in mandb.
>
> I was going to read the code to find out if it's a bug or a feature.

Yeah, that's a good idea. Also, you might email the man-db author
and ask. He's pretty responsive to emails, or anyway he was
a few years back.

> hmm didn't you just say a few lines above that mandb without -c
> removes the manpage?

Yeah, I did. That's what I get for writing a long email with the parts
out of order (go ahead and write next section of email, while waiting
for a 9+ minute run of "mandb -c" to finish... out-of-order execution
works better for CPUs than humans).

So it looks like: in doinst.sh, can use "mandb -f" for each
man page. And in douninst.sh, can use "mandb" without the -c
option. Neither of those takes a long time to run (seconds, not
minutes).

These could be added to the doinst.sh and douninst.sh templates, and
probably will be (though it's not solely up to me).

When/if they do get added to the templates, I'll add checks in
sbopkglint... but they won't be warnings or errors, just "notes",
because otherwise every single existing SBo build that installs man
pages would suddenly be "broken" and require tons of time/work to
"fix".

From zsd+slackbuilds at jdvb.ca  Mon Aug 12 12:12:33 2024
From: zsd+slackbuilds at jdvb.ca (Jim)
Date: Mon, 12 Aug 2024 09:12:33 -0300
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk>
 <ZrnEqGBNrTUB7qTG@comp..>
 <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
Message-ID: <Zrn8MWFE9a15xdeQ@x360.localdomain>

On Mon, Aug 12, 2024 at 05:30 (-0400), B. Watson wrote:

> On Mon, 12 Aug 2024, Arkadiusz Drabczyk wrote:

>> I ran it as root of course, it wouldn't work on /usr/man/man1 if I
>> didn't since it is writable only by root.

> I meant, are you sure when you timed it and got 10 seconds, that you
> were actually using the -c option? I get pretty close to 10 seconds
> when I time it *without* -c. If you really get "mandb -c" to run in
> only 10 seconds, that's 60x as fast as it does for me, and I want to
> know how (so I can make it run that fast for me, too).

Just as another data point, on a laptop running S64-15.0 with a Ryzen 4700U
and a Samsung MZVLB1T0HBLR-000H1 "disk", running
        time mandb -c
I got
        mandb -c  253.46s user 397.39s system 134% cpu 8:02.15 total

So yeah, 10 seconds would be pretty impressive.

                                Jim

From arkadiusz at drabczyk.org  Mon Aug 12 15:55:42 2024
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Mon, 12 Aug 2024 17:55:42 +0200
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <Zrn8MWFE9a15xdeQ@x360.localdomain>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk>
 <ZrnEqGBNrTUB7qTG@comp..>
 <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
 <Zrn8MWFE9a15xdeQ@x360.localdomain>
Message-ID: <Zrowft1xcLMGI0Nj@comp..>

On Mon, Aug 12, 2024 at 09:12:33AM -0300, Jim wrote:
> On Mon, Aug 12, 2024 at 05:30 (-0400), B. Watson wrote:
> 
> > On Mon, 12 Aug 2024, Arkadiusz Drabczyk wrote:
> 
> >> I ran it as root of course, it wouldn't work on /usr/man/man1 if I
> >> didn't since it is writable only by root.
> 
> > I meant, are you sure when you timed it and got 10 seconds, that you
> > were actually using the -c option? I get pretty close to 10 seconds
> > when I time it *without* -c. If you really get "mandb -c" to run in
> > only 10 seconds, that's 60x as fast as it does for me, and I want to
> > know how (so I can make it run that fast for me, too).
> 
> Just as another data point, on a laptop running S64-15.0 with a Ryzen 4700U
> and a Samsung MZVLB1T0HBLR-000H1 "disk", running
>         time mandb -c
> I got
>         mandb -c  253.46s user 397.39s system 134% cpu 8:02.15 total
> 
> So yeah, 10 seconds would be pretty impressive.

It must be due to
https://gitlab.com/man-db/man-db/-/blob/1e5462f3fd9bfd8cf496e32e23842018b67f9b91/NEWS.md#L233. It
takes 10 seconds on -current with mandb 2.12.1 but it indeed took 6
minutes on -stable in the VirtulBox with mandb 2.9.4. After I compiled
it from source it took 20 seconds on -stable too.

-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From urchlay at slackware.uk  Mon Aug 12 18:14:27 2024
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 12 Aug 2024 14:14:27 -0400 (EDT)
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <Zrowft1xcLMGI0Nj@comp..>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk> <ZrnEqGBNrTUB7qTG@comp..>
 <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
 <Zrn8MWFE9a15xdeQ@x360.localdomain> <Zrowft1xcLMGI0Nj@comp..>
Message-ID: <8b2befb-2ca9-fea3-9d71-a9ce69c6cc2@slackware.uk>



On Mon, 12 Aug 2024, Arkadiusz Drabczyk wrote:

> It must be due to
> https://gitlab.com/man-db/man-db/-/blob/1e5462f3fd9bfd8cf496e32e23842018b67f9b91/NEWS.md#L233. It
> takes 10 seconds on -current with mandb 2.12.1 but it indeed took 6
> minutes on -stable in the VirtulBox with mandb 2.9.4. After I compiled
> it from source it took 20 seconds on -stable too.

That explains it.

I assumed you were talking about 15.0, because SBo only supports 15.0.
Sorry for the confusion.

From urchlay at slackware.uk  Mon Aug 12 18:17:03 2024
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 12 Aug 2024 14:17:03 -0400 (EDT)
Subject: [Slackbuilds-users] polib needs a new maintainer
Message-ID: <b693bc3a-a659-60e8-c7a6-10189a4de9b0@slackware.uk>


I've heard from the polib maintainer (Ken Roberts) via IRC...

Ken hasn't used Slackware in 8 years or so, and is unable to maintain
polib.

The only thing in the SBo repo that depends on polib is your
endgame-singularity build. It would make sense for you to take over
maintenance of polib. Are you interested?

From urchlay at slackware.uk  Mon Aug 12 18:23:21 2024
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 12 Aug 2024 14:23:21 -0400 (EDT)
Subject: [Slackbuilds-users] polib needs a new maintainer
In-Reply-To: <b693bc3a-a659-60e8-c7a6-10189a4de9b0@slackware.uk>
References: <b693bc3a-a659-60e8-c7a6-10189a4de9b0@slackware.uk>
Message-ID: <2cf944b1-6420-4f5b-28dd-5c5c135c33e7@slackware.uk>



On Mon, 12 Aug 2024, B. Watson wrote:

> The only thing in the SBo repo that depends on polib is your
> endgame-singularity build. It would make sense for you to take over
> maintenance of polib. Are you interested?

Apologies, that email wasn't intended for the whole list, it was
directed to CRTS.

From zsd+slackbuilds at jdvb.ca  Mon Aug 12 16:11:59 2024
From: zsd+slackbuilds at jdvb.ca (Jim)
Date: Mon, 12 Aug 2024 13:11:59 -0300
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <Zrowft1xcLMGI0Nj@comp..>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk>
 <ZrnEqGBNrTUB7qTG@comp..>
 <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
 <Zrn8MWFE9a15xdeQ@x360.localdomain> <Zrowft1xcLMGI0Nj@comp..>
Message-ID: <Zro0T25yjvw45kxO@x360.localdomain>

On Mon, Aug 12, 2024 at 17:55 (+0200), Arkadiusz Drabczyk wrote:

> On Mon, Aug 12, 2024 at 09:12:33AM -0300, Jim wrote:
>> On Mon, Aug 12, 2024 at 05:30 (-0400), B. Watson wrote:

>>> On Mon, 12 Aug 2024, Arkadiusz Drabczyk wrote:

>>>> I ran it as root of course, it wouldn't work on /usr/man/man1 if I
>>>> didn't since it is writable only by root.

>>> I meant, are you sure when you timed it and got 10 seconds, that you
>>> were actually using the -c option? I get pretty close to 10 seconds
>>> when I time it *without* -c. If you really get "mandb -c" to run in
>>> only 10 seconds, that's 60x as fast as it does for me, and I want to
>>> know how (so I can make it run that fast for me, too).

>> Just as another data point, on a laptop running S64-15.0 with a Ryzen 4700U
>> and a Samsung MZVLB1T0HBLR-000H1 "disk", running
>> time mandb -c
>> I got
>> mandb -c  253.46s user 397.39s system 134% cpu 8:02.15 total

>> So yeah, 10 seconds would be pretty impressive.

> It must be due to
> https://gitlab.com/man-db/man-db/-/blob/1e5462f3fd9bfd8cf496e32e23842018b67f9b91/NEWS.md#L233. It
> takes 10 seconds on -current with mandb 2.12.1 but it indeed took 6
> minutes on -stable in the VirtulBox with mandb 2.9.4. After I compiled
> it from source it took 20 seconds on -stable too.

Sweet!  I love it when people find huge optimizations for commonly-used
programs like this.

Thanks for clearing up the "10 second vs. 10 minutes" mystery.

                                Jim

From tonus1 at free.fr  Mon Aug 12 19:19:22 2024
From: tonus1 at free.fr (Tonus)
Date: Mon, 12 Aug 2024 21:19:22 +0200
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <Zrowft1xcLMGI0Nj@comp..>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk> <ZrnEqGBNrTUB7qTG@comp..>
 <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
 <Zrn8MWFE9a15xdeQ@x360.localdomain> <Zrowft1xcLMGI0Nj@comp..>
Message-ID: <6680F76A-8D46-4F18-A8BE-DF99FB9353D3@free.fr>

Hi

Isn't such an impressive optimization a real bugfix ?

Since 15.1 isn't even close, do you folks think an upgrade could be suggested to M. Volkerding for 15.0 ?

Best regards 

Tonus

Le 12 ao?t 2024 17:55:42 GMT+02:00, Arkadiusz Drabczyk <arkadiusz at drabczyk.org> a ?crit?:
>On Mon, Aug 12, 2024 at 09:12:33AM -0300, Jim wrote:
>> On Mon, Aug 12, 2024 at 05:30 (-0400), B. Watson wrote:
>> 
>> > On Mon, 12 Aug 2024, Arkadiusz Drabczyk wrote:
>> 
>> >> I ran it as root of course, it wouldn't work on /usr/man/man1 if I
>> >> didn't since it is writable only by root.
>> 
>> > I meant, are you sure when you timed it and got 10 seconds, that you
>> > were actually using the -c option? I get pretty close to 10 seconds
>> > when I time it *without* -c. If you really get "mandb -c" to run in
>> > only 10 seconds, that's 60x as fast as it does for me, and I want to
>> > know how (so I can make it run that fast for me, too).
>> 
>> Just as another data point, on a laptop running S64-15.0 with a Ryzen 4700U
>> and a Samsung MZVLB1T0HBLR-000H1 "disk", running
>>         time mandb -c
>> I got
>>         mandb -c  253.46s user 397.39s system 134% cpu 8:02.15 total
>> 
>> So yeah, 10 seconds would be pretty impressive.
>
>It must be due to
>https://gitlab.com/man-db/man-db/-/blob/1e5462f3fd9bfd8cf496e32e23842018b67f9b91/NEWS.md#L233. It
>takes 10 seconds on -current with mandb 2.12.1 but it indeed took 6
>minutes on -stable in the VirtulBox with mandb 2.9.4. After I compiled
>it from source it took 20 seconds on -stable too.
>

From lenardrspencer at gmail.com  Mon Aug 12 19:21:57 2024
From: lenardrspencer at gmail.com (Lenard Spencer)
Date: Mon, 12 Aug 2024 15:21:57 -0400
Subject: [Slackbuilds-users] nvidia-legacy470-kernel
Message-ID: <CANSA5-ur5gR0hO3Xd2JMo4UYuvTOaNpbgxta6nWaqhHMrZBM+A@mail.gmail.com>

I just tried to resubmit nvidia-legacy470-kernel, but it seems to be stuck
in limbo as it is not in the ready nor the pending queues.  Can you help?
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240812/9651493c/attachment.htm>

From didier at slint.fr  Mon Aug 12 19:27:43 2024
From: didier at slint.fr (Didier Spaier)
Date: Mon, 12 Aug 2024 21:27:43 +0200
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <6680F76A-8D46-4F18-A8BE-DF99FB9353D3@free.fr>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk> <ZrnEqGBNrTUB7qTG@comp..>
 <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
 <Zrn8MWFE9a15xdeQ@x360.localdomain> <Zrowft1xcLMGI0Nj@comp..>
 <6680F76A-8D46-4F18-A8BE-DF99FB9353D3@free.fr>
Message-ID: <951d5ffb-c122-49b5-91e3-de1ef4756477@slint.fr>

Le 8/12/24 ? 21:19, Tonus a ?crit?:
> Since 15.1 isn't even close15.1 is closer than ever!

Other famous quotes:
Demain on rase gratis!
Anne, ma s?ur Anne, ne vois-tu rien venir?

Sorry, I couldn't resist
Didier

From arnaud.garcia-fernandez at laposte.net  Mon Aug 12 20:18:22 2024
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Mon, 12 Aug 2024 20:18:22 +0000
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <951d5ffb-c122-49b5-91e3-de1ef4756477@slint.fr>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk> <ZrnEqGBNrTUB7qTG@comp..>
 <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
 <Zrn8MWFE9a15xdeQ@x360.localdomain> <Zrowft1xcLMGI0Nj@comp..>
 <6680F76A-8D46-4F18-A8BE-DF99FB9353D3@free.fr>
 <951d5ffb-c122-49b5-91e3-de1ef4756477@slint.fr>
Message-ID: <D6E183AE-4195-4CC8-887C-CF0488AC8488@laposte.net>

And as we all know, tomorrow never comes.
And my sister's called Anne, and she's yet to see a black sail coming...

 - Yth ??

Le 12 ao?t 2024 19:27:43 UTC, Didier Spaier <didier at slint.fr> a ?crit?:
>Le 8/12/24 ? 21:19, Tonus a ?crit?:
>> Since 15.1 isn't even close15.1 is closer than ever!
>
>Other famous quotes:
>Demain on rase gratis!
>Anne, ma s?ur Anne, ne vois-tu rien venir?
>
>Sorry, I couldn't resist
>Didier
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/
>

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

From tonus1 at free.fr  Mon Aug 12 20:59:03 2024
From: tonus1 at free.fr (Tonus)
Date: Mon, 12 Aug 2024 22:59:03 +0200
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <D6E183AE-4195-4CC8-887C-CF0488AC8488@laposte.net>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk>
 <ZrnEqGBNrTUB7qTG@comp..>
 <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
 <Zrn8MWFE9a15xdeQ@x360.localdomain> <Zrowft1xcLMGI0Nj@comp..>
 <6680F76A-8D46-4F18-A8BE-DF99FB9353D3@free.fr>
 <951d5ffb-c122-49b5-91e3-de1ef4756477@slint.fr>
 <D6E183AE-4195-4CC8-887C-CF0488AC8488@laposte.net>
Message-ID: <2yfk5rls6jonibhtq4h6kawujl25qa3z33suxqhi2cfxjhjhqg@kwu7yy5ufidn>

On Mon, Aug 12, 2024 at 08:18:22PM GMT, Slackbuilds Mailing List wrote:
>And as we all know, tomorrow never comes.
>And my sister's called Anne, and she's yet to see a black sail coming...
>
> - Yth ??
>
>Le 12 ao?t 2024 19:27:43 UTC, Didier Spaier <didier at slint.fr> a ?crit?:
>>Le 8/12/24 ? 21:19, Tonus a ?crit?:
>>> Since 15.1 isn't even close15.1 is closer than ever!

*15.1 is closer than ever!*

:-D That was not in my message !

>>
>>Other famous quotes:
>>Demain on rase gratis!
>>Anne, ma s?ur Anne, ne vois-tu rien venir?
>>
>>Sorry, I couldn't resist
>>Didier

Anyway, any good advice on whether or not to do a request to our BDFL ?

-- 
Regards,

Tonus

From didier at slint.fr  Mon Aug 12 22:29:30 2024
From: didier at slint.fr (Didier Spaier)
Date: Tue, 13 Aug 2024 00:29:30 +0200
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <2yfk5rls6jonibhtq4h6kawujl25qa3z33suxqhi2cfxjhjhqg@kwu7yy5ufidn>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk> <ZrnEqGBNrTUB7qTG@comp..>
 <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
 <Zrn8MWFE9a15xdeQ@x360.localdomain> <Zrowft1xcLMGI0Nj@comp..>
 <6680F76A-8D46-4F18-A8BE-DF99FB9353D3@free.fr>
 <951d5ffb-c122-49b5-91e3-de1ef4756477@slint.fr>
 <D6E183AE-4195-4CC8-887C-CF0488AC8488@laposte.net>
 <2yfk5rls6jonibhtq4h6kawujl25qa3z33suxqhi2cfxjhjhqg@kwu7yy5ufidn>
Message-ID: <83208ebb-f2b1-4927-b7f0-ebd2df526652@slint.fr>



Le 8/12/24 ? 22:59, Tonus a ?crit?:
> On Mon, Aug 12, 2024 at 08:18:22PM GMT, Slackbuilds Mailing List wrote:
>> And as we all know, tomorrow never comes.
>> And my sister's called Anne, and she's yet to see a black sail coming...
>>
>> - Yth ??
>>
>> Le 12 ao?t 2024 19:27:43 UTC, Didier Spaier <didier at slint.fr> a ?crit?:
>>> Le 8/12/24 ? 21:19, Tonus a ?crit?:
>>>> Since 15.1 isn't even close15.1 is closer than ever!
> 
> *15.1 is closer than ever!*
> 
> :-D That was not in my message !

Yes sorry, missing <end of line> between the quote and the beginning of my answer

>>>
>>> Other famous quotes:
>>> Demain on rase gratis!
>>> Anne, ma s?ur Anne, ne vois-tu rien venir?
>>>
>>> Sorry, I couldn't resist
>>> Didier
> 
> Anyway, any good advice on whether or not to do a request to our BDFL ?

It all depend on what you request.

According to my experience, the more cosmetic is the proposed change, the best
chance it has to be accepted.

If your request is about an issue, it helps to propose a fix or patch rather
than just stating it.

If it's removing a software you deem useless, probably bad luck: Pat is
reluctant to deprive even few existing users of something they use.

He is also reluctant to replace a tool by another one, like lilo/elilo by grub
(I tried several time unsuccessfully, LC has been more convincing). Similarly I
have suggested to use dracut instead of mkinitrd to no avail.

He is also reluctant to adopt something that he will not have the time to
maintain himself (other people could help doing it, but my impression is he
would be afraid that they cease to do it in the future for whatever reason).
This made him deny internationalizing the Slackware installer many years ago,
although he could have just adopted my version, which leaded me to create Slint
project instead, initially as the Slackware Internationalized Installer).

And of course don't request that Slackware handle dependencies as almost all
distributions do, you'd loose your time and make him loose patience ;)

I hope this answers at least partially to your question, maybe others have
better ideas?

Cheers,
Didier



From arkadiusz at drabczyk.org  Mon Aug 12 22:50:06 2024
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Tue, 13 Aug 2024 00:50:06 +0200
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk>
 <ZrnEqGBNrTUB7qTG@comp..>
 <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk>
Message-ID: <ZrqRnmu30H6rQqln@comp..>

On Mon, Aug 12, 2024 at 05:30:48AM -0400, B. Watson wrote:
> > > However, it appears that leaving off the -c also prevents mandb from
> > > adding the zathura man page to its database. I wonder if this is the
> > > intended behaviour, or if it might be considered a bug in mandb.
> > 
> > I was going to read the code to find out if it's a bug or a feature.
> 
> Yeah, that's a good idea. Also, you might email the man-db author
> and ask. He's pretty responsive to emails, or anyway he was
> a few years back.

I think I know what's going on here.

mandb checks if there are new files in the directory by comparing
mtime of the database and the directory
https://gitlab.com/man-db/man-db/-/blob/1e5462f3fd9bfd8cf496e32e23842018b67f9b91/src/check_mandirs.c#L529.

mtime is saved in .tar package metadata and installpkg extracts tar
and effectively changes the date of /usr/man/man1 to the past if
`mandb -c` was run after the package was built. If the mtime of man
database happens to be newer than the new mtime of /usr/man/man1 mandb
isn't able to detect new files.

The interesting question is what would happen on the system on which
cron daily rule never fired (IIUC it fires at 4:40 AM) what would mean
that the database is quite old and mandb would be called without -c,
if /usr/man/man1 in tar is newer than the database it should work. It
works when zathura package is rebuilt and installed after `mandb -c`
has been run so that date in tar is newer.

So at the end of the day it's possible that if everything was done in
the right order and crontab rule would actually fire then `man -k`
would work but I still think that it's reasonable to expect that it
would work immediately after the package is installed, not after 4:40
AM and only if your machine is up.

-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From urchlay at slackware.uk  Tue Aug 13 00:33:06 2024
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 12 Aug 2024 20:33:06 -0400 (EDT)
Subject: [Slackbuilds-users] always run `mandb -c` after
 installing/removing manpages?
In-Reply-To: <ZrqRnmu30H6rQqln@comp..>
References: <Zrj85MUkLZrauMqa@comp..>
 <c574b6e5-c3bd-e14-2086-209ad93f546@slackware.uk> <ZrnEqGBNrTUB7qTG@comp..>
 <baf377f4-736-30f7-1dfe-99f4de13f74@slackware.uk> <ZrqRnmu30H6rQqln@comp..>
Message-ID: <21608c11-582b-5dad-dd5-35767a709996@slackware.uk>



On Tue, 13 Aug 2024, Arkadiusz Drabczyk wrote:

> I think I know what's going on here.
>
> mandb checks if there are new files in the directory by comparing
> mtime of the database and the directory
> https://gitlab.com/man-db/man-db/-/blob/1e5462f3fd9bfd8cf496e32e23842018b67f9b91/src/check_mandirs.c#L529.
>
> mtime is saved in .tar package metadata and installpkg extracts tar
> and effectively changes the date of /usr/man/man1 to the past if
> `mandb -c` was run after the package was built. If the mtime of man
> database happens to be newer than the new mtime of /usr/man/man1 mandb
> isn't able to detect new files.

Good analysis.

> I still think that it's reasonable to expect that it
> would work immediately after the package is installed, not after 4:40
> AM and only if your machine is up.

I agree.

Adding the mandb stuff to the template will eventually fix this (as
builds are updated to use the new template).

From urchlay at slackware.uk  Tue Aug 13 00:39:45 2024
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 12 Aug 2024 20:39:45 -0400 (EDT)
Subject: [Slackbuilds-users] Phillip Warner's builds
Message-ID: <58d0593a-29e6-cbf4-82b-811984ac7631@slackware.uk>


I emailed Phillip Warner to ask if he'd update his dmenu build, and
he responded that he's no longer maintaining any SlackBuilds, and that
anyone was welcome to take them over.

Here's the list:

CEGUI
cmatrix
devilspie
dmenu
docx2txt
gmtk
gnome-mplayer
herrie
solfege
xorgxrdp
xrdp

I went ahead and took cmatrix, dmenu, docx2txt, and solfege, because I
actually use them.

I'd recommend Bob Funk as the new maintainer of gnome-mplayer and its
dependency gmtk, since he maintains the GNOME stack... how about it,
Bob?

CEGUI can probably just be dropped: it's a library, and nothing in the
repo uses it (whatever did use it in the past, has been dropped).

I looked at herrie; it's interesting, a console music player,
something like mpd. It should probably go to someone who actually will
use it, if there's any such person on the list.

Any takers?

From r1w1s1 at disroot.org  Tue Aug 13 00:58:44 2024
From: r1w1s1 at disroot.org (r1w1s1)
Date: Mon, 12 Aug 2024 21:58:44 -0300
Subject: [Slackbuilds-users] Phillip Warner's builds
In-Reply-To: <58d0593a-29e6-cbf4-82b-811984ac7631@slackware.uk>
References: <58d0593a-29e6-cbf4-82b-811984ac7631@slackware.uk>
Message-ID: <D3EDK8C4GMNS.2TBLGQSJQLDBP@disroot.org>

On Mon Aug 12, 2024 at 9:39 PM -03, B. Watson wrote:
>
> I emailed Phillip Warner to ask if he'd update his dmenu build, and
> he responded that he's no longer maintaining any SlackBuilds, and that
> anyone was welcome to take them over.
>
> Here's the list:
>
> CEGUI
> cmatrix
> devilspie
> dmenu
> docx2txt
> gmtk
> gnome-mplayer
> herrie
> solfege
> xorgxrdp
> xrdp
>
> I went ahead and took cmatrix, dmenu, docx2txt, and solfege, because I
> actually use them.
>
> I'd recommend Bob Funk as the new maintainer of gnome-mplayer and its
> dependency gmtk, since he maintains the GNOME stack... how about it,
> Bob?
>
> CEGUI can probably just be dropped: it's a library, and nothing in the
> repo uses it (whatever did use it in the past, has been dropped).
>
> I looked at herrie; it's interesting, a console music player,
> something like mpd. It should probably go to someone who actually will
> use it, if there's any such person on the list.
>
> Any takers?
> _______________________________________________
> 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/

Hi can grab dmenu since I use dwm a lot.


-- 
r1w1s1


From urchlay at slackware.uk  Tue Aug 13 01:12:04 2024
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 12 Aug 2024 21:12:04 -0400 (EDT)
Subject: [Slackbuilds-users] Phillip Warner's builds
In-Reply-To: <D3EDK8C4GMNS.2TBLGQSJQLDBP@disroot.org>
References: <58d0593a-29e6-cbf4-82b-811984ac7631@slackware.uk>
 <D3EDK8C4GMNS.2TBLGQSJQLDBP@disroot.org>
Message-ID: <c0532ef9-4f86-c9a9-c0f3-8f8be797b768@slackware.uk>



On Mon, 12 Aug 2024, r1w1s1 via SlackBuilds-users wrote:

> Hi can grab dmenu since I use dwm a lot.

Already taken, you missed this part:

>> I went ahead and took cmatrix, dmenu, docx2txt, and solfege, because I
>> actually use them.

I don't use dwm, but I do use dmenu with clipmenu, and couldn't live
without it...

From urchlay at slackware.uk  Tue Aug 13 02:48:12 2024
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 12 Aug 2024 22:48:12 -0400 (EDT)
Subject: [Slackbuilds-users] Phillip Warner's builds
In-Reply-To: <58d0593a-29e6-cbf4-82b-811984ac7631@slackware.uk>
References: <58d0593a-29e6-cbf4-82b-811984ac7631@slackware.uk>
Message-ID: <53c121b3-bfa1-368-1bf5-9556c2ecc462@slackware.uk>



On Mon, 12 Aug 2024, B. Watson wrote:

> I'd recommend Bob Funk as the new maintainer of gnome-mplayer and its
> dependency gmtk, since he maintains the GNOME stack... how about it,
> Bob?

Addendum: devilspie looks gnomish, too (depends on gnome-common).

From willysr at slackbuilds.org  Tue Aug 13 04:38:05 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 13 Aug 2024 11:38:05 +0700
Subject: [Slackbuilds-users] nvidia-legacy470-kernel
In-Reply-To: <CANSA5-ur5gR0hO3Xd2JMo4UYuvTOaNpbgxta6nWaqhHMrZBM+A@mail.gmail.com>
References: <CANSA5-ur5gR0hO3Xd2JMo4UYuvTOaNpbgxta6nWaqhHMrZBM+A@mail.gmail.com>
Message-ID: <03bed85f-95b0-4e4f-9e00-cc0cb4afa289@slackbuilds.org>

> I just tried to resubmit nvidia-legacy470-kernel, but it seems to be 
> stuck in limbo as it is not in the ready nor the pending queues.? Can 
> you help??? Thanks.

you can now

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x3F617144D7238786.asc
Type: application/pgp-keys
Size: 8363 bytes
Desc: OpenPGP public key
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240813/b6e5f264/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240813/b6e5f264/attachment.asc>

From urchlay at slackware.uk  Tue Aug 13 22:04:42 2024
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 13 Aug 2024 18:04:42 -0400 (EDT)
Subject: [Slackbuilds-users] About to update libtommath on SBo
Message-ID: <4ce2e9b4-fddf-4a53-a136-1733b7b5d97@slackware.uk>


Heads up to maintainers. I'm about to update libtommath from 1.2.1
to 1.3.0. I did some testing with it, but anyone whose build depends
on it might want to do their own testing.

If your build is on this list:

https://slackbuilds.org/advsearch.php?stype=revdep&q=libtommath

...you should check it against the updated libtommath in my
git branch:

https://git.slackbuilds.org/slackbuilds/commit/?h=urchlay&id=7eb0683c32419515c337c6b1d2e851f9d365cfda

Notice is isn't just a simple VERSION bump, I had to change the code
that handles the pkg-config .pc file also.

I built everything on the list without problems, and tested that the
game stepmania would at least start up and exit cleanly. I can't test
rbutil properly as I don't own the hardware it supports, and I don't
know anything about Perl 6 aka rakudo other than that it compiles with
the new libtommath, and "zef --help" appears to run correctly.

If nobody reports any problems in the next few days, the libtommath
update will go into this weekend's regular update.

From slackalaxy at gmail.com  Fri Aug 16 15:16:12 2024
From: slackalaxy at gmail.com (Petar Petrov)
Date: Fri, 16 Aug 2024 18:16:12 +0300
Subject: [Slackbuilds-users] SlackBuilds up for grabs
Message-ID: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>

dear All,

I am not using Slackware at the moment and I am not sure if I will be
coming back to it any time soon. Therefore, please consider all my
SlackBuilds as being up for grabs. If, at some point, I do return to
Slackware, I will do updates, but i wouldn't hold my breath...

best,

petar

From jebrhansen+SBo at gmail.com  Fri Aug 16 15:43:15 2024
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Fri, 16 Aug 2024 08:43:15 -0700
Subject: [Slackbuilds-users] SlackBuilds up for grabs
In-Reply-To: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>
References: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>
Message-ID: <CANi9qSshRNoHe8VZJx8n54Td6iKSgRE0S=koD1RrMsvsXeF-4Q@mail.gmail.com>

On Fri, Aug 16, 2024, 8:12?AM Petar Petrov <slackalaxy at gmail.com> wrote:

> dear All,
>
> I am not using Slackware at the moment and I am not sure if I will be
> coming back to it any time soon. Therefore, please consider all my
> SlackBuilds as being up for grabs. If, at some point, I do return to
> Slackware, I will do updates, but i wouldn't hold my breath...
>
> best,
>
> petar
>

Thanks for your work and best of luck with your future endeavors!

For those curious, here's the list:

academic/CAFS_divergence
academic/CAPS_coevolution
academic/Data2FCS
academic/DendroPy
academic/EMBASSY
academic/EMBOSS
academic/FCSalyzer
academic/FastTree
academic/FigTree
academic/Gblocks
academic/HMMER
academic/IGV
academic/MetaPhlAn2
academic/PhyML
academic/RAxML
academic/RepeatMasker
academic/SeqMonk
academic/TreeGraph
academic/WEVOTE
academic/aline
academic/aliview
academic/amplicon
academic/amplifx
academic/archaeopteryx
academic/arka
academic/bedGraphToBigWig
academic/bedtools
academic/biopython
academic/bowtie
academic/bowtie2-legacy
academic/bpp-core
academic/bpp-phyl-omics
academic/bpp-phyl
academic/bpp-popgen
academic/bpp-seq-omics
academic/bpp-seq
academic/bpp1.9-numcalc
academic/bpp1.9-phyl
academic/bpp1.9-seq
academic/bpp1.9-utils
academic/bppsuite
academic/bwa
academic/cap3
academic/cistrome-CEAS
academic/cistrome-MACS
academic/cistrome-conductGO
academic/cistrome-extra
academic/cistrome-mdseqpos
academic/clark-ugene
academic/clustalo
academic/clustalw
academic/clustalx
academic/cufflinks
academic/cutadapt
academic/datamash
academic/diamond
academic/exonerate
academic/fiji
academic/finchtv
academic/gchemutils
academic/gelemental
academic/geneconv
academic/genometools
academic/genpak
academic/gp2fasta
academic/hyphy
academic/io_lib
academic/iqtree
academic/isoelectric-point
academic/jalview
academic/jellyfish_k-mer
academic/kalign
academic/kraken
academic/lalnview
academic/mafft
academic/megax
academic/meme-db-gomo
academic/meme-db-motif
academic/meme-db-tgene
academic/meme-suite
academic/mkDSSP
academic/mrbayes
academic/mumsa
academic/muscle
academic/muscle5
academic/ncbi-blast+
academic/ncbi-blast
academic/ncbi-edirect
academic/ncbi-rmblastn
academic/pal2nal
academic/paml
academic/pamlX
academic/perlprimer
academic/plasmidomics
academic/prank-msa
academic/primer3
academic/samtools-legacy
academic/seaview
academic/seqkit
academic/sequence-analysis
academic/sim
academic/snpEff
academic/spades
academic/spidey
academic/squizz
academic/staden
academic/stringtie
academic/t_coffee
academic/tabix-legacy
academic/topdraw
academic/tophat
academic/treebest-ensembl
academic/treerecs
academic/treeviewx
academic/trfind
academic/trimmomatic
academic/ucsc-blat
academic/ugene
academic/vCAPS_coevolution
academic/vcftools
academic/wehi-cellsymphony
academic/wehi-deid
academic/wehi-hackit
academic/wehi-weasel
academic/wise
academic/zotero-gtk2
audio/rezound
audio/xmms-wma
desktop/LX-Colors-Revival
desktop/clearlooks-classic-themes
desktop/gnome-icon-theme-stock
desktop/gnome-icon-theme
desktop/gtk-xfce-engine
desktop/gtk1-industrial-engine
desktop/gtk1-theme-switch
desktop/murrine-themes
desktop/polar-cursor-themes
desktop/protozoa-cursor-themes
desktop/thunar-sendto-clamtk
desktop/xfce4-cpufreq-plugin
desktop/xfwm4-themes
desktop/xmms-skins-almond
desktop/xmms-skins-ater
desktop/xmms-status-plugin
games/homm3_shareware_data
games/njam
games/quake3_shareware_data
graphics/fyre
graphics/gpaint
graphics/inkscape-gtk2
graphics/mtpaint
libraries/PDFlib-Lite
libraries/alglib
libraries/libcifpp
libraries/qt-assistant-compat
libraries/tamu_anova
libraries/tslib
misc/bodr
misc/chemical-mime-data
network/viber
office/MasterPDFEditor4
office/evince-gtk2
office/gbgoffice
office/gcalctool-gtk2
office/gnumeric-gtk2
office/osmo-gtk2
office/referencer
office/wps-office-dicts
office/wps-office
perl/perl-HTML-Template
perl/perl-Text-Soundex
python/xopen
system/apple-emoji
system/apple-fonts-Garamond
system/apple-fonts-NY
system/apple-fonts-SF
system/clamtk
system/file-roller-gtk2
system/gnome-pkgtool
system/ktsuss
system/pbzx

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

From arnaud.garcia-fernandez at laposte.net  Fri Aug 16 16:36:36 2024
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Fri, 16 Aug 2024 18:36:36 +0200
Subject: [Slackbuilds-users] SlackBuilds up for grabs
In-Reply-To: <CANi9qSshRNoHe8VZJx8n54Td6iKSgRE0S=koD1RrMsvsXeF-4Q@mail.gmail.com>
References: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>
 <CANi9qSshRNoHe8VZJx8n54Td6iKSgRE0S=koD1RrMsvsXeF-4Q@mail.gmail.com>
Message-ID: <20240816183636.b4fff84db66a32c74344acc9@laposte.net>

> For those curious, here's the list:
> [ Very long list ]

I'll take over this one as I maintain VCMI, the Heroes III free remake,
which can use those shareware data :
games/homm3_shareware_data


	- Yth.

From andrzej at telszewski.com  Sat Aug 17 08:46:02 2024
From: andrzej at telszewski.com (Andrzej Telszewski)
Date: Sat, 17 Aug 2024 10:46:02 +0200
Subject: [Slackbuilds-users] supervisor.SlackBuild maintainance
Message-ID: <6abfcf32-a319-4031-8e31-398132496cf9@telszewski.com>

Hello,

quite some time ago I asked the maintainer of `supervisor.SlackBuild` 
for an update.
Unfortunately, I haven't heard back.

If the maintainer is not active anymore, I'd like to take over the script.

Thanks!

Bcc'd maintainer.

--
Best regards,
Andrzej Telszewski


From andrzej at telszewski.com  Sat Aug 17 10:52:07 2024
From: andrzej at telszewski.com (Andrzej Telszewski)
Date: Sat, 17 Aug 2024 12:52:07 +0200
Subject: [Slackbuilds-users] supervisor.SlackBuild maintainance
In-Reply-To: <6abfcf32-a319-4031-8e31-398132496cf9@telszewski.com>
References: <6abfcf32-a319-4031-8e31-398132496cf9@telszewski.com>
Message-ID: <047788fb-e509-4378-b51d-3c483fa718ea@telszewski.com>

On 17/08/2024 10:46, Andrzej Telszewski wrote:
> Hello,
>
> quite some time ago I asked the maintainer of `supervisor.SlackBuild` 
> for an update.
> Unfortunately, I haven't heard back.
>
> If the maintainer is not active anymore, I'd like to take over the 
> script.
>
> Thanks!
>
> Bcc'd maintainer.
>
> -- 
> Best regards,
> Andrzej Telszewski
>

Hello again,

I've got permission from the maintainer to take over the script.

Thanks! :-)


From willysr at slackbuilds.org  Sat Aug 17 11:22:45 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 17 Aug 2024 18:22:45 +0700
Subject: [Slackbuilds-users] Updates - 20240817.1
Message-ID: <60f0b3a8-9d72-4f72-8dc6-0c79d328a294@slackbuilds.org>

Sat Aug 17 11:15:23 UTC 2024
academic/fet: Updated for version 6.22.3.
academic/solfege: New maintainer.
academic/zotero: update 7.0.1
accessibility/pastebinit: Updated for version 1.7.0.
audio/SongRec: Simplify README.
audio/drumkv1: Updated for version 1.0.0.
audio/padthv1: Updated for version 1.0.0.
audio/pyalsaaudio: Standardize maintainer info.
audio/samplv1: Updated for version 1.0.0.
audio/synthv1: Updated for version 1.0.0.
desktop/cmatrix: New maintainer.
desktop/dmenu: Updated for version 5.3, new maintainer.
desktop/j4-dmenu-desktop: Updated for version 3.1.
desktop/nwg-dock: Updated for version 0.4.0.
desktop/qtile: Update for 0.28.0
development/arduino-cli: Updated for version 1.0.4
development/aspnetcore-runtime-8.0: Updated for version 8.0.8.
development/astyle: Updated for version 3.6.
development/aws-cdk: Updated for version 2.151.1.
development/bacon: Updated for version 5.0, add GTK3 GUI.
development/dasm: Add doinst/douninst for man database.
development/dotnet-runtime-6.0: Updated for version 6.0.33.
development/dotnet-runtime-8.0: Updated for version 8.0.8.
development/dotnet-sdk-6.0: Updated for version 6.0.425.
development/dotnet-sdk-8.0: Updated for version 8.0.400.
development/gambas3: Updated for version 3.19.4.
development/jdk: Updated for version 8u421.
development/kakoune: Updated for version 2024.05.18.
development/lua-language-server: Updated for version 3.10.4.
development/mawk: Updated for version 1.3.4_20240622.
development/ophis: Updated for version 2.2.
development/postman: Updated for version 11.8.0
development/python3-numpy: Add symlink for includes
development/rgbds: Updated for version 0.8.0.
development/rider: Updated for version 2024.1.6.
development/scikit-build: Updated for version 0.14.1.
development/sublime_text: Updated for version 4.1.80.
development/vscode-bin: Updated for version 1.92.2.
games/Tempus-Irae: Fix sources.
games/burgerspace: Updated for version 1.10.0.
games/cosmosmash: Updated for version 1.5.0.
games/eureka: Updated for version 2.0.2.
games/golly: Updated for version 4.3.
games/jg-bsnes: Updated for version 1.2.0.
games/jg-gambatte: Updated for version 0.6.0.
games/jg-mednafen: Updated for version 1.32.1.
games/jg-nestopia: Updated for version 1.52.1.
games/jg-sameboy: Updated for version 0.16.6.
games/marathon-phoenix-data: Fix source.
games/mednaffe: Updated for version 0.9.3.
games/odamex: Updated for version 10.5.0.
games/open-adventure: Updated for version 1.19.
games/snes9x: Updated for version 1.63.
gis/gdal: Updated for version 3.9.2.
gis/geos: Updated for version 3.12.2.
gis/python3-xarray: Updated 2024.07.0.
graphics/gscan2pdf: Standardize maintainer info.
graphics/yed: Standardize maintainer info.
ham/gridtracker: Updated for version 1.24.0814.
ham/liquid-dsp: Updated for version 1.6.0.
libraries/aspnetcore-runtime-6.0: Updated for version 6.0.33.
libraries/dav1d: Version bump to 1.4.3 + New Maintainer
libraries/flatzebra: Updated for version 0.2.0.
libraries/highway: Updated for version 1.2.0.
libraries/libavif: Updated for version 1.1.1.
libraries/libjxl: Updated for version 0.10.3.
libraries/libtommath: Updated for version 1.3.0.
libraries/poco: Updated for version 1.13.3
libraries/process-cpp: Version bump to 3.0.2
libraries/re2: Update for 2024_07_02
libraries/webkit2gtk4.1: Updated for version 2.44.3.
libraries/webkit2gtk: Updated for version 2.44.3.
misc/po4a: Updated for version 0.73.
multimedia/HandBrake: Version bump to 1.8.2
multimedia/picard-plugins: Version bump to 1fd3cfe
multimedia/pipe-viewer: Updated for version 0.5.2.
multimedia/plexmediaserver: Updated for version 1.40.5.8854_f36c552fd.
multimedia/qdvdauthor: Update script.
multimedia/svt-av1: Updated for version 2.1.2.
network/TeamSpeak3: Fix md5sum
network/TeamSpeak3: Updated for version 3.6.2
network/armcord: Updated for version 3.2.8.
network/discord: Version bump to 0.0.64
network/dovecot-pgsql: Updated for version 2.3.21.1
network/gallery-dl: Updated for version 1.27.3.
network/grsync: Updated for version 1.3.1.
network/insync: Fixed source download link
network/ircII: Update note-to-self.
network/microsoft-edge: Updated for version 127.0.2651.98.
network/mumble-server: Updated for version 1.5.634
network/mumble: Updated for version 1.5.634
network/nessus: Updated for version 10.8.2.
network/newsboat: Updated for version 2.36.
network/nheko: Fix download url
network/openntpd: Fix ownership/perms on /var/empty dir
network/signal-desktop: Updated f0r version 7.20.0.
network/telegram: Updated for version 5.4.0.
network/webex: Updated for version 44.8.0.30404
network/yle-dl: Updated for version 20240806.
network/yt-dlp: Updated for version 2024.08.06.
office/docx2txt: New maintainer.
office/keepassx: Standardize maintainer info.
office/mupdf: Updated for version 1.24.8.
office/zathura-pdf-mupdf: Updated for version 0.4.4.
perl/MoarVM: Standardize maintainer info.
perl/nqp: Standardize maintainer info.
perl/perl-Cairo-GObject: Standardize maintainer info.
perl/perl-Devel-Cycle: Standardize maintainer info.
perl/perl-Email-Abstract: Added (unified interface to mail representations).
perl/perl-Email-MIME: Added (easy MIME message handling).
perl/perl-Email-Sender: Added (a library for sending email).
perl/perl-ExtUtils-Config: Updated for version 0.010.
perl/perl-ExtUtils-Install: Standardize maintainer info.
perl/perl-ExtUtils-ModuleMaker: Standardize maintainer info.
perl/perl-File-Remove: Standardize maintainer info.
perl/perl-File-Save-Home: Standardize maintainer info.
perl/perl-Filesys-Df: Standardize maintainer info.
perl/perl-Font-TTF: Standardize maintainer info.
perl/perl-GD: Updated for version 2.83.
perl/perl-GooCanvas2: Standardize maintainer info.
perl/perl-Gtk3-ImageView: Standardize maintainer info.
perl/perl-Gtk3-SimpleList: Standardize maintainer info.
perl/perl-Gtk3: Standardize maintainer info.
perl/perl-IO-Tty: Updated for version 1.20.
perl/perl-Image-Sane: Standardize maintainer info.
perl/perl-Locale-Codes: Standardize maintainer info.
perl/perl-Mail-DMARC: Added (Perl implementation of DMARC).
perl/perl-Module-Install: Standardize maintainer info.
perl/perl-Mojolicious-Plugin-Humane: Standardize maintainer info.
perl/perl-Mojolicious-Plugin-I18N: Standardize maintainer info.
perl/perl-Net-DNS-Resolver-Mock: Added (Mock a DNS Resolver object for 
testing).
perl/perl-Number-Bites-Human: Standardize maintainer info.
perl/perl-PDF-API2: Standardize maintainer info.
perl/perl-PDF-Builder: Standardize maintainer info.
perl/perl-Set-IntSpan: Standardize maintainer info.
perl/perl-String-PerlIdentifier: Standardize maintainer info.
perl/perl-Test-Harness: Updated for version 3.50.
perl/perl-Test-Memory-Cycle: Standardize maintainer info.
perl/perl-WebService-MusicBrainz: Updated for version 1.0.7.
perl/perl-YAML-Tiny: Standardize maintainer info.
perl/perl-image-bmp: Updated for version 1.26.
perl/raku-Readline: Standardize maintainer info.
perl/rakudo: Standardize maintainer info.
perl/zef: Standardize maintainer info.
python/html2text: Updated for version 2024.2.26.
python/instaloader: Updated for version 4.13.
python/pyelftools: Updated for version 0.31.
python/python-djvulibre: Note to self.
python/python-mysql-replication: Updated for version 1.0.9.
python/python3-aiohappyeyeballs: Updated for version 2.3.6.
python/python3-aiohttp: Updated for version 3.10.3.
python/python3-dunamai: Updated for version 1.22.0.
python/python3-lxml: Version bump to 5.3.0
python/python3-pdfCropMargins: Updated for version 2.1.4.
python/python3-pdm: Version bump to 2.18.1
python/python3-tomlkit: Update for 0.13.2
python/python3-tox: Version bump to 4.18.0
python/python3-watchdog: Update for 4.0.2
python/python3-webcolors: Update for 24.8.0
system/86box: Updated for version 4.2.
system/CNS11643-kai-font: Added (System Font).
system/CNS11643-sung-font: Added (System font).
system/Iosevka-aile: Updated for version 31.2.0.
system/Iosevka-etoile: Updated for version 31.2.0.
system/aespipe: Updated for version 2.4h.
system/bottom: Updated for version 0.10.2.
system/clamav: Updated for version 1.4.0.
system/epson-inkjet-printer-escpr2: Updated for version 1.2.14.
system/exomizer: Updated for version 3.1.2.
system/fastfetch: Updated for version 2.21.3.
system/fwupd: Updated for version 1.9.23.
system/fzf: Updated for version 0.54.3.
system/google-chrome-the-latest: Updated for version 3.3.
system/greetd: Fix out-of-order md5sums for .crate files.
system/jenkins: Updated for version 2.462.1.
system/limine: Updated for version 8.0.5
system/logwatch: Update for version 7.11.
system/lv: Updated for version 4.51_9.
system/mediaextract: Updated for version 1.2.0.
system/mmv: Updated for version 2.7.
system/mount-zip: Updated for version 1.0.15.
system/multitail: Updated for version 7.1.5.
system/nvidia-legacy390-driver: Fix multilib.
system/nvidia-legacy470-kernel: Add patch for 6.10 kernel.
system/openzfs: updated for version 2.2.5
system/pmdk: Updated for version 2.1.0.
system/postgresql: Updated for version 14.13.
system/qemu: Updated for version 9.0.2
system/rtirq: Updated for version 20240816_6ce7525.
system/sarasa-gothic: Updated for version 1.0.18.
system/sdl2trs: Updated for version 1.2.29+20240409_85a3cda4.
system/sdltrs: Updated for version 1.2.29.
system/slackrepo-hints: Updated for version 20240817.
system/slackrepo: Updated for version 20240817.
system/slpkg: Updated for version 5.1.1.
system/smenu: Updated for version 1.4.0.
system/sst: Updated for version 1.14.
system/telegraf: Updated for version 1.31.3
system/thermald: Updated for version 2.5.8.
system/webmin: Updated for version 2.202.
system/xfile: Updated for version 1.0beta_6d2dac7.
system/yash: Updated for version 2.57.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From antonioleal at yahoo.com  Sat Aug 17 14:02:18 2024
From: antonioleal at yahoo.com (Antonio Leal)
Date: Sat, 17 Aug 2024 15:02:18 +0100
Subject: [Slackbuilds-users] SlackBuilds up for grabs
In-Reply-To: <CANi9qSshRNoHe8VZJx8n54Td6iKSgRE0S=koD1RrMsvsXeF-4Q@mail.gmail.com>
References: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>
 <CANi9qSshRNoHe8VZJx8n54Td6iKSgRE0S=koD1RrMsvsXeF-4Q@mail.gmail.com>
Message-ID: <acfc8ea1-bd0e-4621-9be5-a6d3d38a4451@yahoo.com>

Hi,

If nobody else claims it I can take:

office/wps-office-dicts
office/wps-office
system/clamtk

Cheers

Ant?nio


On 16/08/24 16:43, Jeremy Hansen wrote:
> On Fri, Aug 16, 2024, 8:12?AM Petar Petrov <slackalaxy at gmail.com> wrote:
>
>     dear All,
>
>     I am not using Slackware at the moment and I am not sure if I will be
>     coming back to it any time soon. Therefore, please consider all my
>     SlackBuilds as being up for grabs. If, at some point, I do return to
>     Slackware, I will do updates, but i wouldn't hold my breath...
>
>     best,
>
>     petar
>
>
> Thanks for your work and best of luck with your future endeavors!
>
> For those curious, here's the list:
>
> academic/CAFS_divergence
> academic/CAPS_coevolution
> academic/Data2FCS
> academic/DendroPy
> academic/EMBASSY
> academic/EMBOSS
> academic/FCSalyzer
> academic/FastTree
> academic/FigTree
> academic/Gblocks
> academic/HMMER
> academic/IGV
> academic/MetaPhlAn2
> academic/PhyML
> academic/RAxML
> academic/RepeatMasker
> academic/SeqMonk
> academic/TreeGraph
> academic/WEVOTE
> academic/aline
> academic/aliview
> academic/amplicon
> academic/amplifx
> academic/archaeopteryx
> academic/arka
> academic/bedGraphToBigWig
> academic/bedtools
> academic/biopython
> academic/bowtie
> academic/bowtie2-legacy
> academic/bpp-core
> academic/bpp-phyl-omics
> academic/bpp-phyl
> academic/bpp-popgen
> academic/bpp-seq-omics
> academic/bpp-seq
> academic/bpp1.9-numcalc
> academic/bpp1.9-phyl
> academic/bpp1.9-seq
> academic/bpp1.9-utils
> academic/bppsuite
> academic/bwa
> academic/cap3
> academic/cistrome-CEAS
> academic/cistrome-MACS
> academic/cistrome-conductGO
> academic/cistrome-extra
> academic/cistrome-mdseqpos
> academic/clark-ugene
> academic/clustalo
> academic/clustalw
> academic/clustalx
> academic/cufflinks
> academic/cutadapt
> academic/datamash
> academic/diamond
> academic/exonerate
> academic/fiji
> academic/finchtv
> academic/gchemutils
> academic/gelemental
> academic/geneconv
> academic/genometools
> academic/genpak
> academic/gp2fasta
> academic/hyphy
> academic/io_lib
> academic/iqtree
> academic/isoelectric-point
> academic/jalview
> academic/jellyfish_k-mer
> academic/kalign
> academic/kraken
> academic/lalnview
> academic/mafft
> academic/megax
> academic/meme-db-gomo
> academic/meme-db-motif
> academic/meme-db-tgene
> academic/meme-suite
> academic/mkDSSP
> academic/mrbayes
> academic/mumsa
> academic/muscle
> academic/muscle5
> academic/ncbi-blast+
> academic/ncbi-blast
> academic/ncbi-edirect
> academic/ncbi-rmblastn
> academic/pal2nal
> academic/paml
> academic/pamlX
> academic/perlprimer
> academic/plasmidomics
> academic/prank-msa
> academic/primer3
> academic/samtools-legacy
> academic/seaview
> academic/seqkit
> academic/sequence-analysis
> academic/sim
> academic/snpEff
> academic/spades
> academic/spidey
> academic/squizz
> academic/staden
> academic/stringtie
> academic/t_coffee
> academic/tabix-legacy
> academic/topdraw
> academic/tophat
> academic/treebest-ensembl
> academic/treerecs
> academic/treeviewx
> academic/trfind
> academic/trimmomatic
> academic/ucsc-blat
> academic/ugene
> academic/vCAPS_coevolution
> academic/vcftools
> academic/wehi-cellsymphony
> academic/wehi-deid
> academic/wehi-hackit
> academic/wehi-weasel
> academic/wise
> academic/zotero-gtk2
> audio/rezound
> audio/xmms-wma
> desktop/LX-Colors-Revival
> desktop/clearlooks-classic-themes
> desktop/gnome-icon-theme-stock
> desktop/gnome-icon-theme
> desktop/gtk-xfce-engine
> desktop/gtk1-industrial-engine
> desktop/gtk1-theme-switch
> desktop/murrine-themes
> desktop/polar-cursor-themes
> desktop/protozoa-cursor-themes
> desktop/thunar-sendto-clamtk
> desktop/xfce4-cpufreq-plugin
> desktop/xfwm4-themes
> desktop/xmms-skins-almond
> desktop/xmms-skins-ater
> desktop/xmms-status-plugin
> games/homm3_shareware_data
> games/njam
> games/quake3_shareware_data
> graphics/fyre
> graphics/gpaint
> graphics/inkscape-gtk2
> graphics/mtpaint
> libraries/PDFlib-Lite
> libraries/alglib
> libraries/libcifpp
> libraries/qt-assistant-compat
> libraries/tamu_anova
> libraries/tslib
> misc/bodr
> misc/chemical-mime-data
> network/viber
> office/MasterPDFEditor4
> office/evince-gtk2
> office/gbgoffice
> office/gcalctool-gtk2
> office/gnumeric-gtk2
> office/osmo-gtk2
> office/referencer
> office/wps-office-dicts
> office/wps-office
> perl/perl-HTML-Template
> perl/perl-Text-Soundex
> python/xopen
> system/apple-emoji
> system/apple-fonts-Garamond
> system/apple-fonts-NY
> system/apple-fonts-SF
> system/clamtk
> system/file-roller-gtk2
> system/gnome-pkgtool
> system/ktsuss
> system/pbzx
>
>
> _______________________________________________
> 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/20240817/311b9068/attachment.htm>

From urchlay at slackware.uk  Sat Aug 17 20:36:43 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 17 Aug 2024 16:36:43 -0400 (EDT)
Subject: [Slackbuilds-users] SlackBuilds up for grabs
In-Reply-To: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>
References: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>
Message-ID: <9c236792-a361-c276-f3c4-cbf2ec304518@slackware.uk>



On Fri, 16 Aug 2024, Petar Petrov wrote:

> dear All,
>
> I am not using Slackware at the moment and I am not sure if I will be
> coming back to it any time soon. Therefore, please consider all my
> SlackBuilds as being up for grabs. If, at some point, I do return to
> Slackware, I will do updates, but i wouldn't hold my breath...

We will miss you. Come back when you can...

Do you mind if the people taking over your scripts relicense them? I'm
thinking of taking on njam, and I'd really like to use the WTFPL
license since it's what I use for scripts I've written from scratch.

From sultmhoor at gmail.com  Sun Aug 18 06:37:03 2024
From: sultmhoor at gmail.com (Kevin Bryant)
Date: Sun, 18 Aug 2024 06:37:03 +0000
Subject: [Slackbuilds-users] SlackBuilds up for grabs
In-Reply-To: <CANi9qSshRNoHe8VZJx8n54Td6iKSgRE0S=koD1RrMsvsXeF-4Q@mail.gmail.com>
References: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>
 <CANi9qSshRNoHe8VZJx8n54Td6iKSgRE0S=koD1RrMsvsXeF-4Q@mail.gmail.com>
Message-ID: <CAK2P7bsKij=kjVH3iuVVoax+_WeKdidcGs8JuU5k8ZOLThh-tw@mail.gmail.com>

I'll take the two perl mods.

On Fri, Aug 16, 2024 at 3:43?PM Jeremy Hansen <jebrhansen+SBo at gmail.com>
wrote:

> On Fri, Aug 16, 2024, 8:12?AM Petar Petrov <slackalaxy at gmail.com> wrote:
>
>> dear All,
>>
>> I am not using Slackware at the moment and I am not sure if I will be
>> coming back to it any time soon. Therefore, please consider all my
>> SlackBuilds as being up for grabs. If, at some point, I do return to
>> Slackware, I will do updates, but i wouldn't hold my breath...
>>
>> best,
>>
>> petar
>>
>
> Thanks for your work and best of luck with your future endeavors!
>
> For those curious, here's the list:
>
> academic/CAFS_divergence
> academic/CAPS_coevolution
> academic/Data2FCS
> academic/DendroPy
> academic/EMBASSY
> academic/EMBOSS
> academic/FCSalyzer
> academic/FastTree
> academic/FigTree
> academic/Gblocks
> academic/HMMER
> academic/IGV
> academic/MetaPhlAn2
> academic/PhyML
> academic/RAxML
> academic/RepeatMasker
> academic/SeqMonk
> academic/TreeGraph
> academic/WEVOTE
> academic/aline
> academic/aliview
> academic/amplicon
> academic/amplifx
> academic/archaeopteryx
> academic/arka
> academic/bedGraphToBigWig
> academic/bedtools
> academic/biopython
> academic/bowtie
> academic/bowtie2-legacy
> academic/bpp-core
> academic/bpp-phyl-omics
> academic/bpp-phyl
> academic/bpp-popgen
> academic/bpp-seq-omics
> academic/bpp-seq
> academic/bpp1.9-numcalc
> academic/bpp1.9-phyl
> academic/bpp1.9-seq
> academic/bpp1.9-utils
> academic/bppsuite
> academic/bwa
> academic/cap3
> academic/cistrome-CEAS
> academic/cistrome-MACS
> academic/cistrome-conductGO
> academic/cistrome-extra
> academic/cistrome-mdseqpos
> academic/clark-ugene
> academic/clustalo
> academic/clustalw
> academic/clustalx
> academic/cufflinks
> academic/cutadapt
> academic/datamash
> academic/diamond
> academic/exonerate
> academic/fiji
> academic/finchtv
> academic/gchemutils
> academic/gelemental
> academic/geneconv
> academic/genometools
> academic/genpak
> academic/gp2fasta
> academic/hyphy
> academic/io_lib
> academic/iqtree
> academic/isoelectric-point
> academic/jalview
> academic/jellyfish_k-mer
> academic/kalign
> academic/kraken
> academic/lalnview
> academic/mafft
> academic/megax
> academic/meme-db-gomo
> academic/meme-db-motif
> academic/meme-db-tgene
> academic/meme-suite
> academic/mkDSSP
> academic/mrbayes
> academic/mumsa
> academic/muscle
> academic/muscle5
> academic/ncbi-blast+
> academic/ncbi-blast
> academic/ncbi-edirect
> academic/ncbi-rmblastn
> academic/pal2nal
> academic/paml
> academic/pamlX
> academic/perlprimer
> academic/plasmidomics
> academic/prank-msa
> academic/primer3
> academic/samtools-legacy
> academic/seaview
> academic/seqkit
> academic/sequence-analysis
> academic/sim
> academic/snpEff
> academic/spades
> academic/spidey
> academic/squizz
> academic/staden
> academic/stringtie
> academic/t_coffee
> academic/tabix-legacy
> academic/topdraw
> academic/tophat
> academic/treebest-ensembl
> academic/treerecs
> academic/treeviewx
> academic/trfind
> academic/trimmomatic
> academic/ucsc-blat
> academic/ugene
> academic/vCAPS_coevolution
> academic/vcftools
> academic/wehi-cellsymphony
> academic/wehi-deid
> academic/wehi-hackit
> academic/wehi-weasel
> academic/wise
> academic/zotero-gtk2
> audio/rezound
> audio/xmms-wma
> desktop/LX-Colors-Revival
> desktop/clearlooks-classic-themes
> desktop/gnome-icon-theme-stock
> desktop/gnome-icon-theme
> desktop/gtk-xfce-engine
> desktop/gtk1-industrial-engine
> desktop/gtk1-theme-switch
> desktop/murrine-themes
> desktop/polar-cursor-themes
> desktop/protozoa-cursor-themes
> desktop/thunar-sendto-clamtk
> desktop/xfce4-cpufreq-plugin
> desktop/xfwm4-themes
> desktop/xmms-skins-almond
> desktop/xmms-skins-ater
> desktop/xmms-status-plugin
> games/homm3_shareware_data
> games/njam
> games/quake3_shareware_data
> graphics/fyre
> graphics/gpaint
> graphics/inkscape-gtk2
> graphics/mtpaint
> libraries/PDFlib-Lite
> libraries/alglib
> libraries/libcifpp
> libraries/qt-assistant-compat
> libraries/tamu_anova
> libraries/tslib
> misc/bodr
> misc/chemical-mime-data
> network/viber
> office/MasterPDFEditor4
> office/evince-gtk2
> office/gbgoffice
> office/gcalctool-gtk2
> office/gnumeric-gtk2
> office/osmo-gtk2
> office/referencer
> office/wps-office-dicts
> office/wps-office
> perl/perl-HTML-Template
> perl/perl-Text-Soundex
> python/xopen
> system/apple-emoji
> system/apple-fonts-Garamond
> system/apple-fonts-NY
> system/apple-fonts-SF
> system/clamtk
> system/file-roller-gtk2
> system/gnome-pkgtool
> system/ktsuss
> system/pbzx
>
>> _______________________________________________
> 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/20240818/94b0350a/attachment-0001.htm>

From slackalaxy at gmail.com  Sun Aug 18 07:15:13 2024
From: slackalaxy at gmail.com (Petar Petrov)
Date: Sun, 18 Aug 2024 10:15:13 +0300
Subject: [Slackbuilds-users] SlackBuilds up for grabs
In-Reply-To: <9c236792-a361-c276-f3c4-cbf2ec304518@slackware.uk>
References: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>
 <9c236792-a361-c276-f3c4-cbf2ec304518@slackware.uk>
Message-ID: <CAKXpWBeieq-or1SBxvUcCzV0mCXb2wusjkemVpZmbqbtFoLh0Q@mail.gmail.com>

> We will miss you. Come back when you can...

I'll miss SBo, too

> Do you mind if the people taking over your scripts relicense them?

not at all, go ahead

-petar

From wedinm at gmail.com  Sun Aug 18 15:58:55 2024
From: wedinm at gmail.com (M Wedin)
Date: Sun, 18 Aug 2024 17:58:55 +0200
Subject: [Slackbuilds-users] Issues with tkimg
Message-ID: <CAGgjXXhqfDQurKZRX_QO+V07BSj8dGEGwkGqcrFHp+UkTxtw0Q@mail.gmail.com>

I aim to install mcu8051ide

These are the packages to be installed. Dependencies are indented

mcu8051ide
  bwidget
  itcl
!  tkimg
    tcllib
  tDOM
    gumbo-parser

There is no libtiff on SBo. I searched and installed all of *jbig* I
could find. No success. Any help is appreciated.


gcc -shared -O2 -fPIC -pipe -O2 -fomit-frame-pointer -DNDEBUG -Wall
-Wwrite-strings -fPIC  -DTIFFTCLAPI=MODULE_SCOPE -DLOGLUV_PUBLIC=0
-Wl,--export-dynamic  -o libtifftcl3.9.4.so tifftcl.o
tifftclStubInit.o tif_aux.o tif_close.o tif_codec.o tif_compress.o
tif_dir.o tif_dirinfo.o tif_dirread.o tif_dirwrite.o tif_dumpmode.o
tif_error.o tif_fax3.o tif_getimage.o tif_flush.o tif_luv.o tif_lzw.o
tif_next.o tif_open.o tif_packbits.o tif_predict.o tif_print.o
tif_read.o tif_swab.o tif_strip.o tif_thunder.o tif_tile.o
tif_version.o tif_warning.o tif_write.o tif_color.o tif_extension.o
tifftclStubLib.o tif_unix.o tif_fax3sm.o -lm  -L/usr/lib64
-ltclstub8.6 -L/usr/lib64 -ltkstub8.6
/usr/bin/ld: tifftclStubInit.o:(.data.rel.ro.local+0x508): undefined
reference to `TIFFInitJBIG'
/usr/bin/ld: tif_codec.o:(.data.rel+0x118): undefined reference to
`TIFFInitJBIG'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:250: libtifftcl3.9.4.so] Error 1
make[1]: Leaving directory '/tmp/SBo/tkimg1.4/libtiff'
make: *** [Makefile:99: all] Error 2

tkimg:
Would you like to continue processing the rest of the
queue or would you like to abort?  If this failed
package is a dependency of another package in the queue
then it may not make sense to continue.

(Y)es to continue, (N)o to abort, (R)etry the build?:

Wedin

From rellis at dp100.com  Sun Aug 18 16:18:36 2024
From: rellis at dp100.com (Richard Ellis)
Date: Sun, 18 Aug 2024 12:18:36 -0400
Subject: [Slackbuilds-users] Issues with tkimg
In-Reply-To: <CAGgjXXhqfDQurKZRX_QO+V07BSj8dGEGwkGqcrFHp+UkTxtw0Q@mail.gmail.com>
References: <CAGgjXXhqfDQurKZRX_QO+V07BSj8dGEGwkGqcrFHp+UkTxtw0Q@mail.gmail.com>
Message-ID: <ZsIe3C4CaC3YRnEa@d820.dp100.com>

On Sun, Aug 18, 2024 at 05:58:55PM +0200, M Wedin wrote:
>I aim to install mcu8051ide
>
>These are the packages to be installed. Dependencies are indented
>
>mcu8051ide
>  bwidget
>  itcl
>!  tkimg
>    tcllib
>  tDOM
>    gumbo-parser
>
>There is no libtiff on SBo.

That is because libtiff is part of Slackware.

Look here, search for "libtiff" in the file list to find the entries:

https://mirrors.slackware.com/slackware/slackware64-15.0/slackware64/l/

Note that it has also been patched (again search for libtiff in the 
list here):

https://mirrors.slackware.com/slackware/slackware64-15.0/patches/packages/

>I searched and installed all of *jbig* I
>could find. No success. Any help is appreciated.
>
>/usr/bin/ld: tifftclStubInit.o:(.data.rel.ro.local+0x508): undefined
>reference to `TIFFInitJBIG'
>/usr/bin/ld: tif_codec.o:(.data.rel+0x118): undefined reference to
>`TIFFInitJBIG'
>
>tkimg:

I just tested my tkimg slackbuild on my Slack 15 system (with the 4.3.0 
libtiff).  It built without error.

I then upgraded my libtiff (as your question caused me to notice I was 
behind Slackware 15's patches on this one).   The tklib slackbuild 
again built without error.

I don't have anything extra to offer, but there are two questions you 
left open:

Do you have Slackware's libtiff installed?

What Slackware version are you trying to build upon?


From wedinm at gmail.com  Sun Aug 18 16:56:30 2024
From: wedinm at gmail.com (M Wedin)
Date: Sun, 18 Aug 2024 18:56:30 +0200
Subject: [Slackbuilds-users] Issues with tkimg
In-Reply-To: <ZsIe3C4CaC3YRnEa@d820.dp100.com>
References: <CAGgjXXhqfDQurKZRX_QO+V07BSj8dGEGwkGqcrFHp+UkTxtw0Q@mail.gmail.com>
 <ZsIe3C4CaC3YRnEa@d820.dp100.com>
Message-ID: <CAGgjXXhzzycqyZPwgSSEKwvwrTY6nphPQzzuGsno5BNuMmtk8Q@mail.gmail.com>

Den s?n 18 aug. 2024 kl 18:18 skrev Richard Ellis via
SlackBuilds-users <slackbuilds-users at slackbuilds.org>:
>
> On Sun, Aug 18, 2024 at 05:58:55PM +0200, M Wedin wrote:
> >I aim to install mcu8051ide
> >
> >These are the packages to be installed. Dependencies are indented
> >
> >mcu8051ide
> >  bwidget
> >  itcl
> >!  tkimg
> >    tcllib
> >  tDOM
> >    gumbo-parser
> >
> >There is no libtiff on SBo.
>
> That is because libtiff is part of Slackware.
>
> Look here, search for "libtiff" in the file list to find the entries:
>
> https://mirrors.slackware.com/slackware/slackware64-15.0/slackware64/l/

Found libtiff-4.3.0-x86_64-1.txz

> Note that it has also been patched (again search for libtiff in the
> list here):
>
> https://mirrors.slackware.com/slackware/slackware64-15.0/patches/packages/

libtiff-4.4.0-x86_64-1_slack15.0.txz

>From my /var/log/packages:
libtiff-4.4.0-x86_64-1_slack15.0

$ locate libtiff
/usr/lib64/libtiff.so
/usr/lib64/libtiff.so.5
/usr/lib64/libtiff.so.5.7.0
/usr/lib64/libtiff.so.5.8.0
/usr/lib64/libtiffxx.so
/usr/lib64/libtiffxx.so.5
/usr/lib64/libtiffxx.so.5.7.0
/usr/lib64/libtiffxx.so.5.8.0
/usr/lib64/pkgconfig/libtiff-4.pc

> I just tested my tkimg slackbuild on my Slack 15 system (with the 4.3.0
> libtiff).  It built without error.
>
> I then upgraded my libtiff (as your question caused me to notice I was
> behind Slackware 15's patches on this one).   The tklib slackbuild
> again built without error.
>
> I don't have anything extra to offer, but there are two questions you
> left open:
>
> Do you have Slackware's libtiff installed?

Yes

> What Slackware version are you trying to build upon?

Bog standard 15 64-bit. No compatibility.

Thanks for the reply
Wedin

From matteo.bernardini at gmail.com  Sun Aug 18 17:51:02 2024
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 18 Aug 2024 19:51:02 +0200
Subject: [Slackbuilds-users] Issues with tkimg
In-Reply-To: <CAGgjXXhzzycqyZPwgSSEKwvwrTY6nphPQzzuGsno5BNuMmtk8Q@mail.gmail.com>
References: <CAGgjXXhqfDQurKZRX_QO+V07BSj8dGEGwkGqcrFHp+UkTxtw0Q@mail.gmail.com>
 <ZsIe3C4CaC3YRnEa@d820.dp100.com>
 <CAGgjXXhzzycqyZPwgSSEKwvwrTY6nphPQzzuGsno5BNuMmtk8Q@mail.gmail.com>
Message-ID: <CAPsDuS44s051NxYd7wTU5_9bSfBRzGJGQ+Eg7+W-cMVdt1-tPQ@mail.gmail.com>

Il giorno dom 18 ago 2024 alle ore 18:56 M Wedin <wedinm at gmail.com> ha
scritto:

> Den s?n 18 aug. 2024 kl 18:18 skrev Richard Ellis via
> SlackBuilds-users <slackbuilds-users at slackbuilds.org>:
> >
> > On Sun, Aug 18, 2024 at 05:58:55PM +0200, M Wedin wrote:
> > >I aim to install mcu8051ide
> > >
> > >These are the packages to be installed. Dependencies are indented
> > >
> > >mcu8051ide
> > >  bwidget
> > >  itcl
> > >!  tkimg
> > >    tcllib
> > >  tDOM
> > >    gumbo-parser
> > >
> > >There is no libtiff on SBo.
> >
> > That is because libtiff is part of Slackware.
> >
> > Look here, search for "libtiff" in the file list to find the entries:
> >
> > https://mirrors.slackware.com/slackware/slackware64-15.0/slackware64/l/
>
> Found libtiff-4.3.0-x86_64-1.txz
>
> > Note that it has also been patched (again search for libtiff in the
> > list here):
> >
> >
> https://mirrors.slackware.com/slackware/slackware64-15.0/patches/packages/
>
> libtiff-4.4.0-x86_64-1_slack15.0.txz
>
> From my /var/log/packages:
> libtiff-4.4.0-x86_64-1_slack15.0
>
> $ locate libtiff
> /usr/lib64/libtiff.so
> /usr/lib64/libtiff.so.5
> /usr/lib64/libtiff.so.5.7.0
> /usr/lib64/libtiff.so.5.8.0
> /usr/lib64/libtiffxx.so
> /usr/lib64/libtiffxx.so.5
> /usr/lib64/libtiffxx.so.5.7.0
> /usr/lib64/libtiffxx.so.5.8.0
> /usr/lib64/pkgconfig/libtiff-4.pc
>
> > I just tested my tkimg slackbuild on my Slack 15 system (with the 4.3.0
> > libtiff).  It built without error.
> >
> > I then upgraded my libtiff (as your question caused me to notice I was
> > behind Slackware 15's patches on this one).   The tklib slackbuild
> > again built without error.
> >
> > I don't have anything extra to offer, but there are two questions you
> > left open:
> >
> > Do you have Slackware's libtiff installed?
>
> Yes
>
> > What Slackware version are you trying to build upon?
>
> Bog standard 15 64-bit. No compatibility.
>
> Thanks for the reply
> Wedin


Hi Wedin,

I'm not able to reproduce your error either...

if you have already installed in your system jbig2dec, jbig2enc or jbigkit
have you tried (temporarily) removing these packages and rebuilding both
tcllib and tkimg?

Matteo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240818/cc7c7203/attachment.htm>

From rellis at dp100.com  Sun Aug 18 18:11:23 2024
From: rellis at dp100.com (Richard Ellis)
Date: Sun, 18 Aug 2024 14:11:23 -0400
Subject: [Slackbuilds-users] Issues with tkimg
In-Reply-To: <CAPsDuS44s051NxYd7wTU5_9bSfBRzGJGQ+Eg7+W-cMVdt1-tPQ@mail.gmail.com>
References: <CAGgjXXhqfDQurKZRX_QO+V07BSj8dGEGwkGqcrFHp+UkTxtw0Q@mail.gmail.com>
 <ZsIe3C4CaC3YRnEa@d820.dp100.com>
 <CAGgjXXhzzycqyZPwgSSEKwvwrTY6nphPQzzuGsno5BNuMmtk8Q@mail.gmail.com>
 <CAPsDuS44s051NxYd7wTU5_9bSfBRzGJGQ+Eg7+W-cMVdt1-tPQ@mail.gmail.com>
Message-ID: <ZsI5S7w4VXqKjCO9@d820.dp100.com>

On Sun, Aug 18, 2024 at 07:51:02PM +0200, Matteo Bernardini wrote:
>Il giorno dom 18 ago 2024 alle ore 18:56 M Wedin <wedinm at gmail.com> ha
>scritto:
>
>> Den s?n 18 aug. 2024 kl 18:18 skrev Richard Ellis via
>> SlackBuilds-users <slackbuilds-users at slackbuilds.org>:
>> >
>> > On Sun, Aug 18, 2024 at 05:58:55PM +0200, M Wedin wrote:
>> > >I aim to install mcu8051ide
>> > >
>> > >These are the packages to be installed. Dependencies are indented
>> > >
>> > >mcu8051ide
>> > >  bwidget
>> > >  itcl
>> > >!  tkimg
>> > >    tcllib
>> > >  tDOM
>> > >    gumbo-parser
>> > >
>> > >There is no libtiff on SBo.
>> >
>> > That is because libtiff is part of Slackware.
>> >
>> > Look here, search for "libtiff" in the file list to find the entries:
>> >
>> > https://mirrors.slackware.com/slackware/slackware64-15.0/slackware64/l/
>>
>> Found libtiff-4.3.0-x86_64-1.txz
>>
>> > Do you have Slackware's libtiff installed?
>>
>> Yes
>>
>> > What Slackware version are you trying to build upon?
>>
>> Bog standard 15 64-bit. No compatibility.
>
>Hi Wedin,
>
>I'm not able to reproduce your error either...
>
>if you have already installed in your system jbig2dec, jbig2enc or jbigkit
>have you tried (temporarily) removing these packages and rebuilding both
>tcllib and tkimg?
>
>Matteo

Testing in a VM with a vanilla Slackware64 15.0 install plus Slackware 
security patches, tkimg builds successfully after building and 
installing tcllib (tkimg dependency).

I agree with Matteo, try removing the JBIG items you installed and see 
if it builds without those installed.

From wedinm at gmail.com  Sun Aug 18 19:38:39 2024
From: wedinm at gmail.com (M Wedin)
Date: Sun, 18 Aug 2024 21:38:39 +0200
Subject: [Slackbuilds-users] Issues with tkimg
In-Reply-To: <ZsI5S7w4VXqKjCO9@d820.dp100.com>
References: <CAGgjXXhqfDQurKZRX_QO+V07BSj8dGEGwkGqcrFHp+UkTxtw0Q@mail.gmail.com>
 <ZsIe3C4CaC3YRnEa@d820.dp100.com>
 <CAGgjXXhzzycqyZPwgSSEKwvwrTY6nphPQzzuGsno5BNuMmtk8Q@mail.gmail.com>
 <CAPsDuS44s051NxYd7wTU5_9bSfBRzGJGQ+Eg7+W-cMVdt1-tPQ@mail.gmail.com>
 <ZsI5S7w4VXqKjCO9@d820.dp100.com>
Message-ID: <CAGgjXXisxWEsBzphH98bQ+KGD=MoV6sVsGZ2JjbsbuFsf4FA4g@mail.gmail.com>

Den s?n 18 aug. 2024 kl 20:11 skrev Richard Ellis via
SlackBuilds-users <slackbuilds-users at slackbuilds.org>:
>
> On Sun, Aug 18, 2024 at 07:51:02PM +0200, Matteo Bernardini wrote:

> >Hi Wedin,
> >
> >I'm not able to reproduce your error either...
> >
> >if you have already installed in your system jbig2dec, jbig2enc or jbigkit
> >have you tried (temporarily) removing these packages and rebuilding both
> >tcllib and tkimg?
> >
> >Matteo
>
> Testing in a VM with a vanilla Slackware64 15.0 install plus Slackware
> security patches, tkimg builds successfully after building and
> installing tcllib (tkimg dependency).
>
> I agree with Matteo, try removing the JBIG items you installed and see
> if it builds without those installed.

I also tried with my computer at home. Same problem.

I removed jbigkit and no problem installing. jbigkit is reinstalled afterwards.

Many thanks for the tip!

Wedin

From urchlay at slackware.uk  Sun Aug 18 20:09:07 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 18 Aug 2024 16:09:07 -0400 (EDT)
Subject: [Slackbuilds-users] Issues with tkimg
In-Reply-To: <CAGgjXXhqfDQurKZRX_QO+V07BSj8dGEGwkGqcrFHp+UkTxtw0Q@mail.gmail.com>
References: <CAGgjXXhqfDQurKZRX_QO+V07BSj8dGEGwkGqcrFHp+UkTxtw0Q@mail.gmail.com>
Message-ID: <2b96fb26-4bdc-9612-3794-31bdfb3072db@slackware.uk>



On Sun, 18 Aug 2024, M Wedin wrote:

> I aim to install mcu8051ide
>
> These are the packages to be installed. Dependencies are indented
>
> mcu8051ide
>  bwidget
>  itcl
> !  tkimg
>    tcllib
>  tDOM
>    gumbo-parser
>
> There is no libtiff on SBo. I searched and installed all of *jbig* I
> could find. No success. Any help is appreciated.

I can confirm that tkimg fails to build, if jbigkit is installed. I get
the same error you do.

What I couldn't figure out, from your message... you installed all
the builds with *jbig* in the name, but why?

Also, it looks like tkimg isn't using the system libtiff at all. It
ships with its own copy of the libtiff source... a rather old version:

$ cat /tmp/SBo/tkimg1.4/compat/libtiff/VERSION 
3.9.4

This version of libtiff gets configured by a command that comes from
tkimg1.4/libtiff/configure, which needs --disable-jbig added to the
--disable-jpeg that's already there...

Two suggestions:

1. M Wedin, you can temporarily removepkg jbigkit, built tkimg, then
    reinstall jbigkit afterwards if you actually need it.

2. Richard Ellis, you might want to patch tkimg to have its embedded
    libtiff build without jbigkit. One way to do it: just after the
    'make distclean' in tkimg.SlackBuild, add this rather ugly sed command:

      sed -i 's,--disable-pixarlog,& --disable-jbig,' libtiff/configure

   Of course, the result will be a tkimg without jbig support... but
   that's what you'd get anyway, if you built tkimg on a stock 15.0
   system.

From wedinm at gmail.com  Sun Aug 18 20:59:28 2024
From: wedinm at gmail.com (M Wedin)
Date: Sun, 18 Aug 2024 22:59:28 +0200
Subject: [Slackbuilds-users] Issues with tkimg
In-Reply-To: <2b96fb26-4bdc-9612-3794-31bdfb3072db@slackware.uk>
References: <CAGgjXXhqfDQurKZRX_QO+V07BSj8dGEGwkGqcrFHp+UkTxtw0Q@mail.gmail.com>
 <2b96fb26-4bdc-9612-3794-31bdfb3072db@slackware.uk>
Message-ID: <CAGgjXXjv-N2=P8XOqVJGOXHZzfoq-mgcnAUuJuPBC3J+PhNEjQ@mail.gmail.com>

Den s?n 18 aug. 2024 kl 22:09 skrev B. Watson <urchlay at slackware.uk>:
>
>
>
> On Sun, 18 Aug 2024, M Wedin wrote:
>
> > I aim to install mcu8051ide
> >
> > These are the packages to be installed. Dependencies are indented
> >
> > mcu8051ide
> >  bwidget
> >  itcl
> > !  tkimg
> >    tcllib
> >  tDOM
> >    gumbo-parser
> >
> > There is no libtiff on SBo. I searched and installed all of *jbig* I
> > could find. No success. Any help is appreciated.
>
> I can confirm that tkimg fails to build, if jbigkit is installed. I get
> the same error you do.
>
> What I couldn't figure out, from your message... you installed all
> the builds with *jbig* in the name, but why?

Because of my lack of understanding, I figured it couldn't hurt much
to add stuff.
undefined reference to `TIFFInitJBIG'

> Also, it looks like tkimg isn't using the system libtiff at all. It
> ships with its own copy of the libtiff source... a rather old version:
>
> $ cat /tmp/SBo/tkimg1.4/compat/libtiff/VERSION
> 3.9.4
>
> This version of libtiff gets configured by a command that comes from
> tkimg1.4/libtiff/configure, which needs --disable-jbig added to the
> --disable-jpeg that's already there...
>
> Two suggestions:
>
> 1. M Wedin, you can temporarily removepkg jbigkit, built tkimg, then
>     reinstall jbigkit afterwards if you actually need it.

That is exactly what I did, when I got it to work. Thanks to Matteo.

> 2. Richard Ellis, you might want to patch tkimg to have its embedded
>     libtiff build without jbigkit. One way to do it: just after the
>     'make distclean' in tkimg.SlackBuild, add this rather ugly sed command:
>
>       sed -i 's,--disable-pixarlog,& --disable-jbig,' libtiff/configure
>
>    Of course, the result will be a tkimg without jbig support... but
>    that's what you'd get anyway, if you built tkimg on a stock 15.0
>    system.

From rellis at dp100.com  Sun Aug 18 21:44:31 2024
From: rellis at dp100.com (Richard Ellis)
Date: Sun, 18 Aug 2024 17:44:31 -0400
Subject: [Slackbuilds-users] Issues with tkimg
In-Reply-To: <2b96fb26-4bdc-9612-3794-31bdfb3072db@slackware.uk>
References: <CAGgjXXhqfDQurKZRX_QO+V07BSj8dGEGwkGqcrFHp+UkTxtw0Q@mail.gmail.com>
 <2b96fb26-4bdc-9612-3794-31bdfb3072db@slackware.uk>
Message-ID: <ZsJrP+qereo0cSLl@d820.dp100.com>

On Sun, Aug 18, 2024 at 04:09:07PM -0400, B. Watson wrote:
>2. Richard Ellis, you might want to patch tkimg to have its embedded
>   libtiff build without jbigkit. One way to do it: just after the
>   'make distclean' in tkimg.SlackBuild, add this rather ugly sed command:
>
>     sed -i 's,--disable-pixarlog,& --disable-jbig,' libtiff/configure
>
>  Of course, the result will be a tkimg without jbig support... but
>  that's what you'd get anyway, if you built tkimg on a stock 15.0
>  system.

Change made, new tar.gz uploaded via the "submissions upload" form.

A test build after making the change succeeded.

From aschro at gmail.com  Sun Aug 18 17:48:19 2024
From: aschro at gmail.com (Adam)
Date: Sun, 18 Aug 2024 19:48:19 +0200
Subject: [Slackbuilds-users] Bad md5sum on password-store-1.7.4.tar.xz
Message-ID: <CAD+x=znP1vrT5jdOKEwiuUqgPqTrZOA4yH-Ax_2=fBrETupBCw@mail.gmail.com>

Hello,
I noticed an md5 sum mismatch in password-store.
Source Downloads: password-store-1.7.4.tar.xz
(56b918982fd80bedba6590059c332c6d)

In August 2023 the same file version was compatible:
56b918982fd80bedba6590059c332c6d (password-store-1.7.4.tar.xz),
Today (August 2024) there is an incompatibility:
eba4c93d12ef0582853099440261a353 (password-store-1.7.4.tar.xz).

Regards,
aschro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240818/eeadfe43/attachment.htm>

From aschro at gmail.com  Mon Aug 19 06:20:53 2024
From: aschro at gmail.com (Adam)
Date: Mon, 19 Aug 2024 08:20:53 +0200
Subject: [Slackbuilds-users] Bad md5sum on password-store-1.7.4.tar.xz
In-Reply-To: <CAD+x=znP1vrT5jdOKEwiuUqgPqTrZOA4yH-Ax_2=fBrETupBCw@mail.gmail.com>
References: <CAD+x=znP1vrT5jdOKEwiuUqgPqTrZOA4yH-Ax_2=fBrETupBCw@mail.gmail.com>
Message-ID: <CAD+x=zmPWy0mKREJLphp6aQZZrAd0MrNT2TMYBu0bb839jTTmg@mail.gmail.com>

OK, the correct MD5 sum was still on July 31, 2024, I just checked it on my
computer at work.

Regards.


niedz., 18 sie 2024 o 19:48 Adam <aschro at gmail.com> napisa?(a):

> Hello,
> I noticed an md5 sum mismatch in password-store.
> Source Downloads: password-store-1.7.4.tar.xz
> (56b918982fd80bedba6590059c332c6d)
>
> In August 2023 the same file version was compatible:
> 56b918982fd80bedba6590059c332c6d (password-store-1.7.4.tar.xz),
> Today (August 2024) there is an incompatibility:
> eba4c93d12ef0582853099440261a353 (password-store-1.7.4.tar.xz).
>
> Regards,
> aschro
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240819/e1947e5c/attachment.htm>

From willysr at slackbuilds.org  Mon Aug 19 07:15:38 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 19 Aug 2024 14:15:38 +0700
Subject: [Slackbuilds-users] Bad md5sum on password-store-1.7.4.tar.xz
In-Reply-To: <CAD+x=znP1vrT5jdOKEwiuUqgPqTrZOA4yH-Ax_2=fBrETupBCw@mail.gmail.com>
References: <CAD+x=znP1vrT5jdOKEwiuUqgPqTrZOA4yH-Ax_2=fBrETupBCw@mail.gmail.com>
Message-ID: <8b87ac76-e559-47a0-a7dd-d5d9981c1683@slackbuilds.org>

> I noticed an md5 sum mismatch in password-store.
> Source Downloads: password-store-1.7.4.tar.xz 
> (56b918982fd80bedba6590059c332c6d)
> 
> In August 2023 the same file version was compatible: 
> 56b918982fd80bedba6590059c332c6d (password-store-1.7.4.tar.xz),
> Today (August 2024) there is an incompatibility: 
> eba4c93d12ef0582853099440261a353 (password-store-1.7.4.tar.xz).

it has been fixed on my branch

thanks

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x3F617144D7238786.asc
Type: application/pgp-keys
Size: 8363 bytes
Desc: OpenPGP public key
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240819/f67369f3/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240819/f67369f3/attachment-0001.asc>

From antonioleal at yahoo.com  Mon Aug 19 18:55:44 2024
From: antonioleal at yahoo.com (Antonio Leal)
Date: Mon, 19 Aug 2024 19:55:44 +0100
Subject: [Slackbuilds-users] SlackBuilds up for grabs
In-Reply-To: <CANi9qSshRNoHe8VZJx8n54Td6iKSgRE0S=koD1RrMsvsXeF-4Q@mail.gmail.com>
References: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>
 <CANi9qSshRNoHe8VZJx8n54Td6iKSgRE0S=koD1RrMsvsXeF-4Q@mail.gmail.com>
Message-ID: <52b538ee-541b-4e03-b694-867683b56d68@yahoo.com>

If no soul opposes I will also take

desktop/thunar-sendto-clamtk

Ant?nio


On 16/08/24 16:43, Jeremy Hansen wrote:
> On Fri, Aug 16, 2024, 8:12?AM Petar Petrov <slackalaxy at gmail.com> wrote:
>
>     dear All,
>
>     I am not using Slackware at the moment and I am not sure if I will be
>     coming back to it any time soon. Therefore, please consider all my
>     SlackBuilds as being up for grabs. If, at some point, I do return to
>     Slackware, I will do updates, but i wouldn't hold my breath...
>
>     best,
>
>     petar
>
>
> Thanks for your work and best of luck with your future endeavors!
>
> For those curious, here's the list:
>
> academic/CAFS_divergence
> academic/CAPS_coevolution
> academic/Data2FCS
> academic/DendroPy
> academic/EMBASSY
> academic/EMBOSS
> academic/FCSalyzer
> academic/FastTree
> academic/FigTree
> academic/Gblocks
> academic/HMMER
> academic/IGV
> academic/MetaPhlAn2
> academic/PhyML
> academic/RAxML
> academic/RepeatMasker
> academic/SeqMonk
> academic/TreeGraph
> academic/WEVOTE
> academic/aline
> academic/aliview
> academic/amplicon
> academic/amplifx
> academic/archaeopteryx
> academic/arka
> academic/bedGraphToBigWig
> academic/bedtools
> academic/biopython
> academic/bowtie
> academic/bowtie2-legacy
> academic/bpp-core
> academic/bpp-phyl-omics
> academic/bpp-phyl
> academic/bpp-popgen
> academic/bpp-seq-omics
> academic/bpp-seq
> academic/bpp1.9-numcalc
> academic/bpp1.9-phyl
> academic/bpp1.9-seq
> academic/bpp1.9-utils
> academic/bppsuite
> academic/bwa
> academic/cap3
> academic/cistrome-CEAS
> academic/cistrome-MACS
> academic/cistrome-conductGO
> academic/cistrome-extra
> academic/cistrome-mdseqpos
> academic/clark-ugene
> academic/clustalo
> academic/clustalw
> academic/clustalx
> academic/cufflinks
> academic/cutadapt
> academic/datamash
> academic/diamond
> academic/exonerate
> academic/fiji
> academic/finchtv
> academic/gchemutils
> academic/gelemental
> academic/geneconv
> academic/genometools
> academic/genpak
> academic/gp2fasta
> academic/hyphy
> academic/io_lib
> academic/iqtree
> academic/isoelectric-point
> academic/jalview
> academic/jellyfish_k-mer
> academic/kalign
> academic/kraken
> academic/lalnview
> academic/mafft
> academic/megax
> academic/meme-db-gomo
> academic/meme-db-motif
> academic/meme-db-tgene
> academic/meme-suite
> academic/mkDSSP
> academic/mrbayes
> academic/mumsa
> academic/muscle
> academic/muscle5
> academic/ncbi-blast+
> academic/ncbi-blast
> academic/ncbi-edirect
> academic/ncbi-rmblastn
> academic/pal2nal
> academic/paml
> academic/pamlX
> academic/perlprimer
> academic/plasmidomics
> academic/prank-msa
> academic/primer3
> academic/samtools-legacy
> academic/seaview
> academic/seqkit
> academic/sequence-analysis
> academic/sim
> academic/snpEff
> academic/spades
> academic/spidey
> academic/squizz
> academic/staden
> academic/stringtie
> academic/t_coffee
> academic/tabix-legacy
> academic/topdraw
> academic/tophat
> academic/treebest-ensembl
> academic/treerecs
> academic/treeviewx
> academic/trfind
> academic/trimmomatic
> academic/ucsc-blat
> academic/ugene
> academic/vCAPS_coevolution
> academic/vcftools
> academic/wehi-cellsymphony
> academic/wehi-deid
> academic/wehi-hackit
> academic/wehi-weasel
> academic/wise
> academic/zotero-gtk2
> audio/rezound
> audio/xmms-wma
> desktop/LX-Colors-Revival
> desktop/clearlooks-classic-themes
> desktop/gnome-icon-theme-stock
> desktop/gnome-icon-theme
> desktop/gtk-xfce-engine
> desktop/gtk1-industrial-engine
> desktop/gtk1-theme-switch
> desktop/murrine-themes
> desktop/polar-cursor-themes
> desktop/protozoa-cursor-themes
> desktop/thunar-sendto-clamtk
> desktop/xfce4-cpufreq-plugin
> desktop/xfwm4-themes
> desktop/xmms-skins-almond
> desktop/xmms-skins-ater
> desktop/xmms-status-plugin
> games/homm3_shareware_data
> games/njam
> games/quake3_shareware_data
> graphics/fyre
> graphics/gpaint
> graphics/inkscape-gtk2
> graphics/mtpaint
> libraries/PDFlib-Lite
> libraries/alglib
> libraries/libcifpp
> libraries/qt-assistant-compat
> libraries/tamu_anova
> libraries/tslib
> misc/bodr
> misc/chemical-mime-data
> network/viber
> office/MasterPDFEditor4
> office/evince-gtk2
> office/gbgoffice
> office/gcalctool-gtk2
> office/gnumeric-gtk2
> office/osmo-gtk2
> office/referencer
> office/wps-office-dicts
> office/wps-office
> perl/perl-HTML-Template
> perl/perl-Text-Soundex
> python/xopen
> system/apple-emoji
> system/apple-fonts-Garamond
> system/apple-fonts-NY
> system/apple-fonts-SF
> system/clamtk
> system/file-roller-gtk2
> system/gnome-pkgtool
> system/ktsuss
> system/pbzx
>
>
> _______________________________________________
> 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/20240819/370a7b72/attachment.htm>

From sbo at linuxgalaxy.org  Mon Aug 19 23:32:10 2024
From: sbo at linuxgalaxy.org (KB_SBo)
Date: Mon, 19 Aug 2024 23:32:10 +0000
Subject: [Slackbuilds-users] slpkg-5.1.1 script syntax error
Message-ID: <cf22b733-fc7a-49a7-8891-f6ab35c56328@linuxgalaxy.org>

Hello,

slpkg-5.1.0 was ok, but slpkg-5.1.1 gives

# ./slpkg.SlackBuild
./slpkg.SlackBuild: line 95: unexpected EOF while looking for matching `"'
./slpkg.SlackBuild: line 118: syntax error: unexpected end of file

The offending " was in line 63

else
   SLKCFLAGS="-O2
   LIBDIRSUFFIX=""

-------------------8<-----------------------
# diff -u slpkg.SlackBuild.orig slpkg.SlackBuild
--- slpkg.SlackBuild.orig	2024-08-19 16:27:47.599316574 -0700
+++ slpkg.SlackBuild	2024-08-19 16:27:53.156426831 -0700
@@ -60,7 +60,7 @@
    SLKCFLAGS="-O2 -fPIC"
    LIBDIRSUFFIX="64"
  else
-  SLKCFLAGS="-O2
+  SLKCFLAGS="-O2"
    LIBDIRSUFFIX=""
  fi

------------------->8-----------------------


From willysr at slackbuilds.org  Mon Aug 19 23:59:57 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 20 Aug 2024 06:59:57 +0700
Subject: [Slackbuilds-users] slpkg-5.1.1 script syntax error
In-Reply-To: <cf22b733-fc7a-49a7-8891-f6ab35c56328@linuxgalaxy.org>
References: <cf22b733-fc7a-49a7-8891-f6ab35c56328@linuxgalaxy.org>
Message-ID: <24bf6a3c-f4f3-40e5-8dcf-314121082a5b@slackbuilds.org>

> slpkg-5.1.0 was ok, but slpkg-5.1.1 gives
> 
> # ./slpkg.SlackBuild
> ./slpkg.SlackBuild: line 95: unexpected EOF while looking for matching `"'
> ./slpkg.SlackBuild: line 118: syntax error: unexpected end of file
> 
> The offending " was in line 63
> 
> else
>     SLKCFLAGS="-O2
>     LIBDIRSUFFIX=""

it's already fixed on my branch since few days ago

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

From brandon.pribs11 at gmail.com  Tue Aug 20 03:31:03 2024
From: brandon.pribs11 at gmail.com (Brandon Pribula)
Date: Mon, 19 Aug 2024 20:31:03 -0700
Subject: [Slackbuilds-users] python/xopen
Message-ID: <CAGviRBVOzbwPi6CQ7Y0XCsvFouue0RH3vrYSjT0v9Z7Wc4HEcA@mail.gmail.com>

Hello,

If there are no objections I would like to take over maintenance of Petar
Petrov's python/xopen.

Thanks,

Brandon Pribula
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240819/2c064e38/attachment.htm>

From fourtysixandtwo at sliderr.net  Tue Aug 20 04:11:04 2024
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Mon, 19 Aug 2024 22:11:04 -0600
Subject: [Slackbuilds-users] python/xopen
In-Reply-To: <CAGviRBVOzbwPi6CQ7Y0XCsvFouue0RH3vrYSjT0v9Z7Wc4HEcA@mail.gmail.com>
References: <CAGviRBVOzbwPi6CQ7Y0XCsvFouue0RH3vrYSjT0v9Z7Wc4HEcA@mail.gmail.com>
Message-ID: <CAAZ8HaiATEC3VC1kKXNuga6O7g5wHvQrAjS3Lr=D2y5oNLJbmA@mail.gmail.com>

Hi Brandon,

I would suggest submitting a new python3-xopen as xopen has not been
updated in sometime and is still python2.  Are you interested in
creating python3-cutadapt too?  It is also python2, another on his
list, and the only slackbuild that depends on xopen.  Either way we
should remove the python2 versions.

# hoorex -1lm xopen
python/xopen
academic/cutadapt

Cheers

On Mon, Aug 19, 2024 at 9:31?PM Brandon Pribula
<brandon.pribs11 at gmail.com> wrote:
>
> Hello,
>
> If there are no objections I would like to take over maintenance of Petar Petrov's python/xopen.
>
> Thanks,
>
> Brandon Pribula
> _______________________________________________
> 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 brandon.pribs11 at gmail.com  Tue Aug 20 04:45:42 2024
From: brandon.pribs11 at gmail.com (Brandon Pribula)
Date: Mon, 19 Aug 2024 21:45:42 -0700
Subject: [Slackbuilds-users] python/xopen
In-Reply-To: <CAAZ8HaiATEC3VC1kKXNuga6O7g5wHvQrAjS3Lr=D2y5oNLJbmA@mail.gmail.com>
References: <CAGviRBVOzbwPi6CQ7Y0XCsvFouue0RH3vrYSjT0v9Z7Wc4HEcA@mail.gmail.com>
 <CAAZ8HaiATEC3VC1kKXNuga6O7g5wHvQrAjS3Lr=D2y5oNLJbmA@mail.gmail.com>
Message-ID: <CAGviRBV=o6kZuEgQT8rV5rqKmk-grf7nYMTm8Ow36PDEfNiRPQ@mail.gmail.com>

On Mon, Aug 19, 2024 at 9:11?PM fourtysixandtwo <fourtysixandtwo at sliderr.net>
wrote:

> Hi Brandon,
>
> I would suggest submitting a new python3-xopen as xopen has not been
> updated in sometime and is still python2.  Are you interested in
> creating python3-cutadapt too?  It is also python2, another on his
> list, and the only slackbuild that depends on xopen.  Either way we
> should remove the python2 versions.
>
> # hoorex -1lm xopen
> python/xopen
> academic/cutadapt
>
> Cheers
>
> On Mon, Aug 19, 2024 at 9:31?PM Brandon Pribula
> <brandon.pribs11 at gmail.com> wrote:
> >
> > Hello,
> >
> > If there are no objections I would like to take over maintenance of
> Petar Petrov's python/xopen.
> >
> > Thanks,
> >
> > Brandon Pribula
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

Not a problem. I can create and maintain both. Although, I most likely
won't have them submitted until after this week's updates.

IIRC new builds have to be submitted through the main site but for future
reference is it still acceptable to submit updates to the list or do we
have to submit through gitlab or github?

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240819/f9f84517/attachment.htm>

From urchlay at slackware.uk  Tue Aug 20 04:59:21 2024
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 20 Aug 2024 00:59:21 -0400 (EDT)
Subject: [Slackbuilds-users] python/xopen
In-Reply-To: <CAGviRBV=o6kZuEgQT8rV5rqKmk-grf7nYMTm8Ow36PDEfNiRPQ@mail.gmail.com>
References: <CAGviRBVOzbwPi6CQ7Y0XCsvFouue0RH3vrYSjT0v9Z7Wc4HEcA@mail.gmail.com>
 <CAAZ8HaiATEC3VC1kKXNuga6O7g5wHvQrAjS3Lr=D2y5oNLJbmA@mail.gmail.com>
 <CAGviRBV=o6kZuEgQT8rV5rqKmk-grf7nYMTm8Ow36PDEfNiRPQ@mail.gmail.com>
Message-ID: <f0bd6e86-bfc5-cf20-a3d2-c7c15164ae2@slackware.uk>



On Mon, 19 Aug 2024, Brandon Pribula wrote:

> IIRC new builds have to be submitted through the main site but for future reference is it still acceptable to submit updates to the list or do we have to submit through gitlab or
> github?

You can submit updates through the website, just like new builds.

You *can* use github/gitlab, but it's not required.

From brandon.pribs11 at gmail.com  Tue Aug 20 04:59:48 2024
From: brandon.pribs11 at gmail.com (Brandon Pribula)
Date: Mon, 19 Aug 2024 21:59:48 -0700
Subject: [Slackbuilds-users] python/xopen
In-Reply-To: <f0bd6e86-bfc5-cf20-a3d2-c7c15164ae2@slackware.uk>
References: <CAGviRBVOzbwPi6CQ7Y0XCsvFouue0RH3vrYSjT0v9Z7Wc4HEcA@mail.gmail.com>
 <CAAZ8HaiATEC3VC1kKXNuga6O7g5wHvQrAjS3Lr=D2y5oNLJbmA@mail.gmail.com>
 <CAGviRBV=o6kZuEgQT8rV5rqKmk-grf7nYMTm8Ow36PDEfNiRPQ@mail.gmail.com>
 <f0bd6e86-bfc5-cf20-a3d2-c7c15164ae2@slackware.uk>
Message-ID: <CAGviRBVZG0B4tvzbpZye9Y+z7rbev8-YcjL-RhDodDSfnUZO5w@mail.gmail.com>

On Mon, Aug 19, 2024 at 9:59?PM B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Mon, 19 Aug 2024, Brandon Pribula wrote:
>
> > IIRC new builds have to be submitted through the main site but for
> future reference is it still acceptable to submit updates to the list or do
> we have to submit through gitlab or
> > github?
>
> You can submit updates through the website, just like new builds.
>
> You *can* use github/gitlab, but it's not required.
> _______________________________________________
> 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/
>
>
That's great. I'll use the site.

Thanks for the replies fourtysixandtwo and B. Watson. Much appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240819/56a9bd6e/attachment.htm>

From dickson.tim at googlemail.com  Fri Aug 23 15:14:32 2024
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Fri, 23 Aug 2024 16:14:32 +0100
Subject: [Slackbuilds-users] qemu slackbuild
Message-ID: <843efc5d-9d75-4650-a6d8-ef8718835492@googlemail.com>

I noticed that if numactl is installed, then qemu picks it up at build 
time and it becomes a dependency. maybe an addition in the README would 
be handy.
regards, Tim


-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com

From glenn_e_becker at protonmail.com  Fri Aug 23 15:29:59 2024
From: glenn_e_becker at protonmail.com (glenn_e_becker)
Date: Fri, 23 Aug 2024 15:29:59 +0000
Subject: [Slackbuilds-users] my slackbuilds, including treesheets
Message-ID: <HSQE2_nmQM6mylJ_EJ54HO9tlTOrQz5TzaQTnMpvpJZehBJxCn7DmorZ4nUhfOTfVgsT2SGOXuzdkHZzKys88k4JZDq3jPyw7ZWT7-hdI7A=@protonmail.com>

Hi list --

My sincere apologies. Willy was kind enough to nudge me about treesheets some time ago, and I have not? been able to address it. I'm afraid I have been (and am -- it just keeps going on) stuck in serious job uncertainty (I'll say only "potential NASA budget cuts" and leave it there), so I really have to focus on gearing up for a job search.

The following seem to still have my name attached. I'm letting them go and have hopes I'll be back to 'Builds at some point:

WordNet
antiprism
featherpad
lbreakout2
treesheets
xwallpaper

I don't like to do this, but someone with the time and skills should have these.

Thanks,

Glenn Becker

Sent with [Proton Mail](https://proton.me/) secure email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240823/c37b41e7/attachment.htm>

From brandon.pribs11 at gmail.com  Fri Aug 23 16:46:46 2024
From: brandon.pribs11 at gmail.com (Brandon Pribula)
Date: Fri, 23 Aug 2024 09:46:46 -0700
Subject: [Slackbuilds-users] my slackbuilds, including treesheets
In-Reply-To: <HSQE2_nmQM6mylJ_EJ54HO9tlTOrQz5TzaQTnMpvpJZehBJxCn7DmorZ4nUhfOTfVgsT2SGOXuzdkHZzKys88k4JZDq3jPyw7ZWT7-hdI7A=@protonmail.com>
References: <HSQE2_nmQM6mylJ_EJ54HO9tlTOrQz5TzaQTnMpvpJZehBJxCn7DmorZ4nUhfOTfVgsT2SGOXuzdkHZzKys88k4JZDq3jPyw7ZWT7-hdI7A=@protonmail.com>
Message-ID: <CAGviRBUJHJKhVnpchdJj59wp57fY-ygGptbaOyy4YBuByF0SnA@mail.gmail.com>

I will take xwallpaper. I use the application and I was also the original
slackbuild maintainer.

On Fri, Aug 23, 2024, 8:30 AM glenn_e_becker via SlackBuilds-users, <
slackbuilds-users at slackbuilds.org> wrote:

> Hi list --
>
> My sincere apologies. Willy was kind enough to nudge me about *treesheets*
> some time ago, and I have *not*? been able to address it. I'm afraid I
> have been (and am -- it just keeps going on) stuck in serious job
> uncertainty (I'll say only "potential NASA budget cuts" and leave it
> there), so I really have to focus on gearing up for a job search.
>
> The following seem to still have my name attached. I'm letting them go and
> have hopes I'll be back to 'Builds at some point:
>
> WordNet
> antiprism
> featherpad
> lbreakout2
> treesheets
> xwallpaper
>
> I don't like to do this, but someone with the time and skills should have
> these.
>
> Thanks,
>
> Glenn Becker
>
> Sent with Proton Mail <https://proton.me/> secure email.
> _______________________________________________
> 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/20240823/226d8296/attachment.htm>

From arnaud.garcia-fernandez at laposte.net  Fri Aug 23 16:47:00 2024
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Fri, 23 Aug 2024 16:47:00 +0000
Subject: [Slackbuilds-users] my slackbuilds, including treesheets
In-Reply-To: <HSQE2_nmQM6mylJ_EJ54HO9tlTOrQz5TzaQTnMpvpJZehBJxCn7DmorZ4nUhfOTfVgsT2SGOXuzdkHZzKys88k4JZDq3jPyw7ZWT7-hdI7A=@protonmail.com>
References: <HSQE2_nmQM6mylJ_EJ54HO9tlTOrQz5TzaQTnMpvpJZehBJxCn7DmorZ4nUhfOTfVgsT2SGOXuzdkHZzKys88k4JZDq3jPyw7ZWT7-hdI7A=@protonmail.com>
Message-ID: <08D5E886-7D53-4DC3-8465-B64EFB91F3CA@laposte.net>

Hi !

Hoping all will go well for you.
I'm ok babysitting featherpad, feel free to tell us if you're back, I'll return it !

 - Yth.

Le 23 ao?t 2024 15:29:59 UTC, glenn_e_becker via SlackBuilds-users <slackbuilds-users at slackbuilds.org> a ?crit?:
>Hi list --
>
>My sincere apologies. Willy was kind enough to nudge me about treesheets some time ago, and I have not? been able to address it. I'm afraid I have been (and am -- it just keeps going on) stuck in serious job uncertainty (I'll say only "potential NASA budget cuts" and leave it there), so I really have to focus on gearing up for a job search.
>
>The following seem to still have my name attached. I'm letting them go and have hopes I'll be back to 'Builds at some point:
>
>WordNet
>antiprism
>featherpad
>lbreakout2
>treesheets
>xwallpaper
>
>I don't like to do this, but someone with the time and skills should have these.
>
>Thanks,
>
>Glenn Becker
>
>Sent with [Proton Mail](https://proton.me/) secure email.
-- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240823/3b992fc9/attachment.htm>

From urchlay at slackware.uk  Fri Aug 23 18:57:52 2024
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 23 Aug 2024 14:57:52 -0400 (EDT)
Subject: [Slackbuilds-users] my slackbuilds, including treesheets
In-Reply-To: <HSQE2_nmQM6mylJ_EJ54HO9tlTOrQz5TzaQTnMpvpJZehBJxCn7DmorZ4nUhfOTfVgsT2SGOXuzdkHZzKys88k4JZDq3jPyw7ZWT7-hdI7A=@protonmail.com>
References: <HSQE2_nmQM6mylJ_EJ54HO9tlTOrQz5TzaQTnMpvpJZehBJxCn7DmorZ4nUhfOTfVgsT2SGOXuzdkHZzKys88k4JZDq3jPyw7ZWT7-hdI7A=@protonmail.com>
Message-ID: <f44bc82d-202f-2712-23d-13f4ceb52024@slackware.uk>



On Fri, 23 Aug 2024, glenn_e_becker via SlackBuilds-users wrote:

> lbreakout2

Possibly lbreakout2 could just disappear. Its developer replaced it
with an SDL2 remake called lbreakouthd, which has an active maintainer
on SBo. The lbreakout2 web site says "(!!!)This game is no longer
maintained. Please try LBreakoutHD instead", so maybe we don't need
both games on SBo?

On the other hand... I just played both versions. The first level
of lbreakouthd is different from the first level of lbreakout2. So
someone who really likes this game might want to have both of them
installed, to have more levels to choose from.

I think I'll take lbreakout2. Since it's no longer developed, it won't
take up much of my time to maintain it.

From sbo at linuxgalaxy.org  Fri Aug 23 22:44:42 2024
From: sbo at linuxgalaxy.org (KB_SBo)
Date: Fri, 23 Aug 2024 22:44:42 +0000
Subject: [Slackbuilds-users] qemu slackbuild
In-Reply-To: <843efc5d-9d75-4650-a6d8-ef8718835492@googlemail.com>
References: <843efc5d-9d75-4650-a6d8-ef8718835492@googlemail.com>
Message-ID: <df339ff1-6141-40b4-8d87-8c186bcd2885@linuxgalaxy.org>

On 8/23/24 08:14, Tim Dickson via SlackBuilds-users wrote:
> I noticed that if numactl is installed, then qemu picks it up at build
> time and it becomes a dependency. maybe an addition in the README would
> be handy.
> regards, Tim
> 
> 

Well heck. I knew I had forgotten something. Someone mentioned that 
awhile back (you?).  I'll make a not of it for the next update.

-Ed




From willysr at slackbuilds.org  Sat Aug 24 05:06:25 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 24 Aug 2024 12:06:25 +0700
Subject: [Slackbuilds-users] Updates - 20240824.1
Message-ID: <f8893a10-9e71-4452-918d-f668971bad37@slackbuilds.org>

Sat Aug 24 04:56:34 UTC 2024
academic/cdo: Updated for version 2.4.3.
academic/fet: Updated for version 6.24.0.
academic/labplot2: Updated for version 2.11.1.
academic/root: Updated for version 6.32.04 (+fix 32 bit)
accessibility/espeakup: Updated for version 0.80.
desktop/ClamAV-GUI: Added (ClamAV GUI).
desktop/engrampa: Updated for version 1.28.2.
desktop/gnome-icon-theme: New maintainer, noarch, speed up build.
desktop/j4-dmenu-desktop: Fix missing dep.
desktop/nwg-clipman: Updated for version 0.2.3.
desktop/nwg-dock: Updated for version 0.4.1.
desktop/qtile: Update for 0.28.1
desktop/slbar: Update for 20230928
desktop/thunar-sendto-clamtk: Updated for version 0.08.
desktop/xpenguins: Updated for version 3.2.3.
desktop/xwallpaper: New maintainer.
development/apache-maven: Updated for version 3.9.9.
development/aws-cdk: Updated for version 2.152.0.
development/aws-cdk: Updated for version 2.154.0.
development/codespell: Updated for version 2.3.0.
development/composer: Updated for version 2.7.8
development/github-cli: Updated for version 2.55.0
development/hugo: update 0.133.0
development/kotlin: Updated for version 2.0.20.
development/lua-language-server: Updated for version 3.10.5.
development/nodejs: Updated for version 20.17.0.
development/python3-numpy: Enable choice of python3 version
development/racer: Removed (use rust-analyzer).
development/rider: Updated for version 2024.2.1.
development/rustup: Align packaging with upstream.
development/rustup: Updated for version 1.27.1.
development/terraform-ls: Added (Terraform Language Server).
development/terraform: Updated for version 1.9.5
development/tflint: Updated for version 0.53.0.
development/vasm: Updated for version 1.9f.
games/atari_8bit_utils: Updated for version 20240813_6c9fdda.
games/cowsay: Updated for version 3.8.3.
games/crispy-doom: Updated for version 7.0.
games/lbreakout2: Updated for version 2.6.5, new maintainer.
games/njam: New maintainer, various tweaks.
games/sameboy: Updated for version 0.16.6.
games/wolfmame: Updated for version 0.268.
gis/ossim: Fix source.
git/ci: Update CI dependencies.
graphics/GraphicsMagick: Updated for version 1.3.44.
graphics/SweetHome3D: Updated for version 7.5.
graphics/blender: Updated for version 4.2.1.
graphics/chafa: Updated for version 1.14.2.
graphics/veles: Add doinst.sh.
ham/svxlink-sounds-en_US-heather-16k: Updated for version 24.02.
ham/svxlink: Updated for version 24.02.
libraries/ayatana-ido: Updated for version 0.10.4.
libraries/gamemode: Updated for version 1.8.2.
libraries/gcab: Updated to 1.6.
libraries/grpc: Update for 1.65.5
libraries/libewf: Updated for version 20140816.
libraries/libfabric: Updated for version 1.22.0.
libraries/libpff: Updated for version 20231205.
libraries/libuninameslist: Updated for version 20240524.
libraries/libvhdi: Updated for version 20240303.
libraries/libvmdk: Updated for version 20240303.
libraries/libwrc: Updated for version 20240421.
libraries/openvino: Updated for version 2024.3.0.
libraries/psqlodbc: Updated for version 16.0.
libraries/pytorch: Updated for version 2.4.0.
libraries/tkimg: Fix build failure.
libraries/zziplib: Updated for version 0.13.78.
misc/yara: Updated for version 4.5.1.
multimedia/ffmpegfs: Updated for version 2.16.
multimedia/filebot: Updated for version 5.1.5.
multimedia/inputstream.adaptive: Version bump to 21.5.2
multimedia/kodi: Version bump to 21.1
multimedia/l-smash: Updated for version 2.18.0.
multimedia/picard: Version bump to 2.12.1
multimedia/plexmediaserver: Updated for version 1.40.5.8897_e5987a19d.
network/brave-browser: update 1.68.141
network/discord: Updated for version 0.0.65.
network/dnsproxy-bin: Updated for version 0.73.1.
network/dropbox: Updated for version 206.4.6506.
network/electrs: Added (Electrum in Rust).
network/microsoft-edge: Updated for version 128.0.2739.42.
network/mumble-server: suppress warnings as errors for 32-bit builds
network/noip-duc: Updated for version 3.1.1.
network/nordvpn: Updated for version 3.18.4.
network/obfs4proxy: Added (The obfourscator).
network/qbittorrent: Updated for version 4.6.6.
network/signal-desktop: Updated for version 7.21.0.
network/telegram: Updated for version 5.4.1.
network/teleport-connect: Added (Secure Access to Infrastructure).
network/unbound: Updated for version 1.21.0.
network/vivaldi: Updated for version 6.8.3381.55.
network/weechat: Updated for version 4.4.1.
network/windscribe: Downgraded to version 2.9.9 due to compatibility 
issues with Slackware 15.0.
network/zoom-linux: Updated for version 6.1.10.1400
office/LibreOffice: Updated for version 24.8.0.3
office/MasterPDFEditor4: New maintainer, various tweaks.
office/calibre-bin: Update README.
office/eid-mw: Added (card reader).
office/evince-gtk2: New maintainer, fix comic book support.
office/libreoffice-helppack: Updated for version 24.8.0.
office/libreoffice-langpack: Updated for version 24.8.0.
office/libreoffice: Updated for version 24.8.0.
office/python3-xlsx2csv: Updated for version 0.8.3.
office/wps-office-dicts: Updated for version 24.2.6.1
office/wps-office: Updated for version 11.1.0.11723.XA
perl/perl-File-Which: Updated for version 1.27.
perl/perl-GD: Add missing perl-File-Which dep.
perl/perl-GD: Fix dep.
perl/perl-image-bmp: Fix 32-bit build failure.
python/python-mysql-replication: Fix script.
python/python2-yara: Updated for version 4.5.0.
python/python3-aiohappyeyeballs: Updated for version 2.3.7.
python/python3-aiohappyeyeballs: Updated for version 2.4.0.
python/python3-aiohttp: Updated for version 3.10.4.
python/python3-aiohttp: Updated for version 3.10.5.
python/python3-argcomplete: Updated for version 3.5.0.
python/python3-cachetools: Updated for version 5.5.0.
python/python3-fontmake: Update dep.
python/python3-fonttools: Updated for version 4.53.1.
python/python3-glyphslib: Updated for version 6.8.1.
python/python3-grpcio: Update for 1.65.5
python/python3-jaconv: Updated for version 0.4.0.
python/python3-lz4: Updated for version 4.3.3.
python/python3-marisa-trie: Updated for version 1.2.0.
python/python3-nltk: Updated for version 3.9.1.
python/python3-opencv: Added (Python3 binding for OpenCV).
python/python3-opencv: Fix permission.
python/python3-pipx: Updated for version 1.6.0.
python/python3-plexapi: Updated to 4.15.16.
python/python3-pykakasi: Updated for version 2.3.0.
python/python3-qbittorrent-api: Updated for version 2024.8.65.
python/python3-reportlab: Updated for version 4.2.2.
python/python3-socks: Updated for version 2.5.1.
python/python3-stevedore: Updated for version 5.3.0.
python/python3-types-python-dateutil: Update for 2.9.0.20240821
python/python3-ufo2ft: Updated for version 3.2.7.
python/python3-ufolib2: Update dep.
python/python3-uharfbuzz: Updated for version 0.39.3.
python/python3-unearth: Updated for version 0.17.1.
python/python3-yara: Updated for version 4.5.0.
python/rst2pdf: Updated for version 0.102.
system/B-em: Updated for version 20240818_c94008d.
system/CanAce: Added (A Jupiter ACE Emulator).
system/Iosevka-aile: Updated for version 31.3.0.
system/Iosevka-etoile: Updated for version 31.3.0.
system/bulk_extractor: Updated for version 2.1.0.
system/clamtk: Updated for version 6.18.
system/epson-inkjet-printer-escpr2: Updated for version 1.2.15.
system/far2l: Updated for version 2.6.3.
system/intel-microcode: Update for version 20240813
system/kitty: Updated for version 0.36.0
system/nvidia-driver: Updated for version 560.35.03.
system/nvidia-kernel: Updated for version 560.35.03.
system/openrgb: Added (Open source RGB lighting control).
system/password-store: Update MD5SUM.
system/powershell: Updated for version 7.4.5.
system/qemu: Update README optional deps.
system/sarasa-gothic: Updated for version 1.0.19.
system/sboui: Updated for version 2.4.
system/slackrepo-hints: Updated for version 20240823.
system/slackrepo: Updated for version 20240823.
system/slpkg: Fix script.
system/volatility3: Updated for version 2.7.0.
system/xAce: Added (emulator for the Jupiter Ace).
system/xAce: Fix permission.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From urchlay at slackware.uk  Sat Aug 24 06:32:57 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 24 Aug 2024 02:32:57 -0400 (EDT)
Subject: [Slackbuilds-users] RFC: Proposed mandb additions to
 doinst/douninst template
Message-ID: <f688d1-3436-ffd7-d471-80a2da466edc@slackware.uk>


Thinking of adding this to the doinst template:

### in doinst.sh:
# DESCRIPTION: Updates the man database (for "man -k").
# Use one "man -f" command for each man page in the package.
if [ -x usr/bin/mandb ]; then
   usr/bin/mandb -f usr/man/man1/program.1.gz
fi

### in douninst.sh:
# DESCRIPTION: Updates the man database (for "man -k").
# Only use one "mandb" command, and only use it if your package actually
# includes man pages.
if [ -x usr/bin/mandb ]; then
   usr/bin/mandb
fi

The use of "usr/bin/mandb" (rather than "/usr/bin/mandb") is
deliberate: we don't want to add man pages to the system's man
database, if the package is being installed with -root (as sbopkglint
does, for example), and there's no mandb command in that dir.

Opinions? Floor is open for discussion.

From urchlay at slackware.uk  Sat Aug 24 07:30:23 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 24 Aug 2024 03:30:23 -0400 (EDT)
Subject: [Slackbuilds-users] RFC: Proposed mandb additions to
 doinst/douninst template
In-Reply-To: <f688d1-3436-ffd7-d471-80a2da466edc@slackware.uk>
References: <f688d1-3436-ffd7-d471-80a2da466edc@slackware.uk>
Message-ID: <47b7cb40-17a0-49b2-b697-9c61d99758e5@slackware.uk>



On Sat, 24 Aug 2024, B. Watson wrote:

>
> Thinking of adding this to the doinst template:
>
> ### in doinst.sh:
> # DESCRIPTION: Updates the man database (for "man -k").
> # Use one "man -f" command for each man page in the package.
> if [ -x usr/bin/mandb ]; then
>  usr/bin/mandb -f usr/man/man1/program.1.gz
> fi
>
> ### in douninst.sh:
> # DESCRIPTION: Updates the man database (for "man -k").
> # Only use one "mandb" command, and only use it if your package actually
> # includes man pages.
> if [ -x usr/bin/mandb ]; then
>  usr/bin/mandb
> fi

Whoops. Pasted wrong version of the file. The actual code that *should*
have been pasted is:


### in doinst.sh:
# DESCRIPTION: Updates the man database (for "man -k").
# Use one "man -f" command for each man page in the package.
if [ -x usr/bin/mandb ]; then
   chroot . /usr/bin/mandb -f /usr/man/man1/alsacap.1.gz &> /dev/null
fi

### in douninst.sh:
# DESCRIPTION: Updates the man database (for "man -k").
# Only use one "mandb" command, and only use it if your package actually
# includes man pages.
if [ -x usr/bin/mandb ]; then
   chroot . /usr/bin/mandb &> /dev/null
fi


The previous version was missing the chroot's and the
&>/dev/null. Sorry about that. If there were a way to un-mail an
email, I'd have done it :)

Anyway. I'm not adding anything to the template at all until it's been
discussed and tested by people who aren't me.

From antonioleal at yahoo.com  Sat Aug 24 13:43:06 2024
From: antonioleal at yahoo.com (Antonio Leal)
Date: Sat, 24 Aug 2024 14:43:06 +0100
Subject: [Slackbuilds-users] Windows 32/64 apps without multilib
References: <5a9f4916-caaf-459e-9e5c-fbcf300e06aa.ref@yahoo.com>
Message-ID: <5a9f4916-caaf-459e-9e5c-fbcf300e06aa@yahoo.com>

In the spirit of true slackin' been playing around with AppImages and 
build a couple in the form

of a slackbuild script. I think these not "publishable" in 
SlackBuilds.org but could solve some of our members needs.

The idea is to take a wine AppImage, unpack, add a small windows app, 
and repack it in a single file.


The examples :

Notepad++ editor: 
https://github.com/antonioleal/myslackbuilds/tree/main/development/notepad%2B%2B

ZOOM Edit&Share Guitar Pedal app: 
https://github.com/antonioleal/myslackbuilds/tree/main/audio/zoom-edit-n-share


These actually do an "install on first run", but it the app is portable 
is also fine to run it from within the AppImage itself, and

not from the installed binary. Best of all runs win32 and win64 apps 
without multilib...

The SlackBuild scritps are self explanatory.


This nothing special and probably been achieved a million times, but 
anyway here it is...re-done again.

Happy slacking holidays.

Ant?nio


From arkadiusz at drabczyk.org  Sun Aug 25 13:18:35 2024
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Sun, 25 Aug 2024 15:18:35 +0200
Subject: [Slackbuilds-users] RFC: Proposed mandb additions to
 doinst/douninst template
In-Reply-To: <f688d1-3436-ffd7-d471-80a2da466edc@slackware.uk>
References: <f688d1-3436-ffd7-d471-80a2da466edc@slackware.uk>
Message-ID: <ZssvK2LMwhT1G4MN@comp..>

On Sat, Aug 24, 2024 at 02:32:57AM -0400, B. Watson wrote:
> 
> Thinking of adding this to the doinst template:
> 
> ### in doinst.sh:
> # DESCRIPTION: Updates the man database (for "man -k").
> # Use one "man -f" command for each man page in the package.
> if [ -x usr/bin/mandb ]; then
>   usr/bin/mandb -f usr/man/man1/program.1.gz
> fi

so there is no easier way than to run mandb for each manpage
separately? It'll be hard to maintain, especially in case of programs
that can add different manpages based on build options used.

-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From urchlay at slackware.uk  Sun Aug 25 17:42:11 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 25 Aug 2024 13:42:11 -0400 (EDT)
Subject: [Slackbuilds-users] RFC: Proposed mandb additions to
 doinst/douninst template
In-Reply-To: <ZssvK2LMwhT1G4MN@comp..>
References: <f688d1-3436-ffd7-d471-80a2da466edc@slackware.uk>
 <ZssvK2LMwhT1G4MN@comp..>
Message-ID: <b781dd7a-e3ba-4f65-274d-891080cc3a7a@slackware.uk>



On Sun, 25 Aug 2024, Arkadiusz Drabczyk wrote:

>> ### in doinst.sh:
>> # DESCRIPTION: Updates the man database (for "man -k").
>> # Use one "man -f" command for each man page in the package.
>> if [ -x usr/bin/mandb ]; then
>>   usr/bin/mandb -f usr/man/man1/program.1.gz
>> fi
>
> so there is no easier way than to run mandb for each manpage
> separately?

No easier way that I've found yet.

Well, "mandb -c" in doinst.sh would be easier, but it takes too long
to run on Slackware 15.0.

> It'll be hard to maintain, especially in case of programs
> that can add different manpages based on build options used.

The revised version of it has the redirect &>/dev/null. So if build
options prevent one of the man pages from being built, the doinst.sh
won't complain about it.

During SlackBuild development, it'll be useful to run the doinst.sh
without the &>/dev/null's, to see if mandb complains about the format
of the man page.

I've just found out something interesting... in the douninst.sh,
instead of a single "mandb" call (which takes 5 seconds on my box
with an SSD), you can actually use the same "mandb -f" command(s).

# man -k zathura
zathura (1)          - a document viewer
# removepkg zathura &>/dev/null
# man -k zathura
zathura (1)          - a document viewer
# mandb -f /usr/man/man1/zathura.1.gz &>/dev/null
# man -k zathura
zathura: nothing appropriate.

This is quicker than what I posted for douninst.sh, and it's identical
code in doinst.sh and douninst.sh. And it runs instantly. Put that in
zathura's douninst.sh and there won't be a 5-second delay on package
removal.

From brandon.pribs11 at gmail.com  Sun Aug 25 23:16:13 2024
From: brandon.pribs11 at gmail.com (Brandon Pribula)
Date: Sun, 25 Aug 2024 16:16:13 -0700
Subject: [Slackbuilds-users] python/xopen
In-Reply-To: <CAGviRBVZG0B4tvzbpZye9Y+z7rbev8-YcjL-RhDodDSfnUZO5w@mail.gmail.com>
References: <CAGviRBVOzbwPi6CQ7Y0XCsvFouue0RH3vrYSjT0v9Z7Wc4HEcA@mail.gmail.com>
 <CAAZ8HaiATEC3VC1kKXNuga6O7g5wHvQrAjS3Lr=D2y5oNLJbmA@mail.gmail.com>
 <CAGviRBV=o6kZuEgQT8rV5rqKmk-grf7nYMTm8Ow36PDEfNiRPQ@mail.gmail.com>
 <f0bd6e86-bfc5-cf20-a3d2-c7c15164ae2@slackware.uk>
 <CAGviRBVZG0B4tvzbpZye9Y+z7rbev8-YcjL-RhDodDSfnUZO5w@mail.gmail.com>
Message-ID: <CAGviRBUoqvkkD7GOQQMfCBXffqdkQ7minrKWxZJUt_dMJZPkpQ@mail.gmail.com>

I won't be able to take over maintenance of these two packages as I
originally thought so they are still up for grabs.

Sorry for any inconvenience this may have caused.

Thanks

On Mon, Aug 19, 2024 at 9:59?PM Brandon Pribula <brandon.pribs11 at gmail.com>
wrote:

>
>
> On Mon, Aug 19, 2024 at 9:59?PM B. Watson <urchlay at slackware.uk> wrote:
>
>>
>>
>> On Mon, 19 Aug 2024, Brandon Pribula wrote:
>>
>> > IIRC new builds have to be submitted through the main site but for
>> future reference is it still acceptable to submit updates to the list or do
>> we have to submit through gitlab or
>> > github?
>>
>> You can submit updates through the website, just like new builds.
>>
>> You *can* use github/gitlab, but it's not required.
>> _______________________________________________
>> 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/
>>
>>
> That's great. I'll use the site.
>
> Thanks for the replies fourtysixandtwo and B. Watson. Much appreciated.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240825/73ec30ab/attachment-0001.htm>

From urchlay at slackware.uk  Mon Aug 26 19:18:19 2024
From: urchlay at slackware.uk (B. Watson)
Date: Mon, 26 Aug 2024 15:18:19 -0400 (EDT)
Subject: [Slackbuilds-users] Bill Kirkpatrick's builds
Message-ID: <61bd3f3b-1d76-b388-f1e1-74498a445b82@slackware.uk>


I emailed Bill Kirkpatrick about one of his builds... he's no longer
maintaining anything. This may have been posted to the list before,
but I'll post it again.

These builds need maintainers, if anyone's interested:

desktop/wally
games/xye
libraries/libdca
libraries/libshout
libraries/live555
multimedia/zvbi

I'd recommend Steven Voges as maintainer for libdca, libshout,
live555, and zvbi, since they're dependencies for his vlc build.

However, libdca and libshout have other dependees, so if your build
depends on either of these, it makes just as much sense for you to
take over.

From nick at smallbone.se  Fri Aug 30 18:32:29 2024
From: nick at smallbone.se (Nick Smallbone)
Date: Fri, 30 Aug 2024 20:32:29 +0200
Subject: [Slackbuilds-users] SlackBuilds up for grabs
In-Reply-To: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>
References: <CAKXpWBfFAJ65ciHcHsRVedz9XJka=qry9qGxP=z4ej_d6P0piA@mail.gmail.com>
Message-ID: <fe342dd5-fee0-4b17-b3e9-6f0d6ac1da4f@app.fastmail.com>

I'm happy to take the following:

desktop/gtk-xfce-engine
desktop/murrine-themes
desktop/xfce4-cpufreq-plugin
desktop/xfwm4-themes

Nick

On Fri, 16 Aug 2024, at 5:16 PM, Petar Petrov wrote:
> dear All,
>
> I am not using Slackware at the moment and I am not sure if I will be
> coming back to it any time soon. Therefore, please consider all my
> SlackBuilds as being up for grabs. If, at some point, I do return to
> Slackware, I will do updates, but i wouldn't hold my breath...
>
> best,
>
> petar
> _______________________________________________
> 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 willysr at slackbuilds.org  Sat Aug 31 01:14:04 2024
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 31 Aug 2024 08:14:04 +0700
Subject: [Slackbuilds-users] Updates - 20240831.1
Message-ID: <00c45449-cb96-48c7-b721-b8f21ea29e56@slackbuilds.org>

Sat Aug 31 00:57:25 UTC 2024
academic/gaiasky: Updated for version 3.6.3.
audio/alsacap: Add doinst/douninst for mandb.
audio/tauonmb: Compatiblity for non-current.
desktop/insync-thunar: Update download url.
desktop/screenkey: Updated for version 1.5, new maintainer.
development/OpenJDK11: Updated for version 11.0.24.
development/OpenJDK17: Updated for version 17.0.12.
development/OpenJDK21: Updated for version 21.0.4.
development/aws-cdk: Updated for version 2.155.0.
development/dotnet-sdk-8.0: Updated for version 8.0.401.
development/gambas3: Fix md5sum.
development/idea: Updated for version 2024.2.0.2.
development/jdk: Fix source URL.
development/lua53: Updated for version 5.3.6.
development/mongodb-compass: Updated for version 1.43.6.
development/php82: Updated for version 8.2.23
development/portaudio: New maintainer, various fixes.
development/postman: Updated for version 11.9.0
development/qb64pe: Updated for version 3.14.1
development/rider: Updated for version 2024.2.2.
development/spyder: Add python3-spyder-kernels version restriction
games/ltris: Updated for version 2.0, new maintainer.
games/opensurge: Updated for version 0.6.1.2.
games/puNES: Updated for version 0.111, new maintainer.
games/pysolfc-extra-cardsets: Updated for version 3.0.
games/pysolfc: Updated for version 3.0.0.
games/surgescript: Updated for version 0.6.1.
gis/pdal: Remove -j option.
gis/proj-data: Updated for version 1.18.
gis/proj: Updated for version 9.4.1.
gis/python3-pyproj: Updated for version 3.6.1.
gis/qgis: Updated for version 3.38.2.
gis/saga-gis: Updated for version 9.5.1.
gis/survex: Updated for version 1.4.11.
git/ci: Update CI dependencies.
graphics/FotoKilof: Updated for version 4.4.9.
graphics/fim: Updated for version 0.7.1.
graphics/vuescan: Updated for version 9.8.36.
ham/qlog: Updated for version 0.38.0.
ham/sdrangel: Updated for version 7.22.0.
libraries/exempi: Updated for version 2.6.5.
libraries/grpc: Update for 1.66.0
libraries/grpc: Update for 1.66.1
libraries/imlib2_loaders: Updated for version 1.12.3.
libraries/liblqr: Updated for version 0.4.3.
libraries/libsvm: Updated for version 3.34.
libraries/liburcu: Updated for version 0.14.1.
libraries/msgpack-c-c: Updated for version 6.1.0.
libraries/pylast: Updated for version 5.3.0.
libraries/spglib: Updated for version 2.5.0.
libraries/tinygltf: Updated for version 2.9.3.
libraries/wxPython4: Update DEP.
libraries/zimg: Updated for version 3.0.5.
misc/cheat: Added (interactive cheatsheets).
misc/grabc: Updated for v1.0.2 (newer than 1.1), new maintainer.
multimedia/beets: Updated for version 2.0.0.
multimedia/inputstream.adaptive: Version bump to 21.5.4
multimedia/picard: Version bump to 2.12.2
multimedia/vapoursynth-mvtools: Updated for version 24.
multimedia/vapoursynth: Updated for version R69.
multimedia/youtube-music: Added (Youtube Desktop App).
network/discord: Version bump to 0.0.66
network/electrs: Removed debugging line and corrected in rc.electrs
network/pound: Updated for version 4.13
network/vnstat: Update README.SBo.
network/wego: Update for 2.3
network/wireshark: Updated for version 4.4.0.
network/zeek: Updated for version 6.0.5.
network/zoom-linux: Updated for version 6.1.11.1545
office/hebcal: Updated for version 5.8.7.
perl/perl-parallel-forkmanager: Version bump to 2.03 & change to noarch
python/instaloader: Updated for version 4.13.1.
python/mypy: Updated for version 1.11.2.
python/python3-PyGithub: Version bump to 2.4.0
python/python3-gensim: Update for 4.3.3
python/python3-grpcio: Update for 1.66.0
python/python3-grpcio: Update for 1.66.1
python/python3-lz4: Fix dependency.
python/python3-plotly: Update for 5.24.0
python/python3-soupsieve: Updated for version 2.6.
python/python3-watchdog: Update for 5.0.0
python/sphinxcontrib-applehelp: Updated for version 2.0.0.
python/sphinxcontrib-devhelp: Updated for version 2.0.0.
python/sphinxcontrib-htmlhelp: Updated for version 2.1.0.
python/sphinxcontrib-qthelp: Updated for version 2.0.0.
python/sphinxcontrib-serializinghtml: Updated for version 2.0.0.
system/Iosevka-aile: Updated for version 31.4.0.
system/Iosevka-etoile: Updated for version 31.4.0.
system/apparmor: Updated for version 4.0.3.
system/bin2iso: Fix VERSION (not upgraded), new maintainer.
system/containerd: Updated for version 1.7.21.
system/dar: Updated for version 2.7.15, new maintainer.
system/docker-cli: Updated for version 27.2.0.
system/docker-compose: Updated for version 2.29.2
system/docker: Updated for version 27.2.0.
system/doublecmd-qt5: Updated for version 1.1.17.
system/fastfetch: Updated for version 2.22.0.
system/fd: Updated for version 10.2.0.
system/fsarchiver: New maintainer, slight tweaks.
system/fwupd: Updated for version 1.9.24.
system/fzf: Updated for version 0.55.0.
system/gpart: New maintainer.
system/kbfs: Updated for version 6.4.0_20240821175720.
system/kitty: Updated for version 0.36.1
system/mdf2iso: New maintainer.
system/mongodb: Updated for version 7.0.14.
system/netdata: Updated for version 1.47.0.
system/nnn: Update for 5.0
system/nvidia-driver: Remove nvidia-installer.
system/nvidia-legacy390-driver: Remove nvidia-installer.
system/nvidia-legacy390-kernel: Add patch for kernel 6.10.
system/nvidia-legacy470-driver: Remove nvidia-installer.
system/posh: New maintainer.
system/safecopy: New maintainer, slight tweaks.
system/sandbox: Updated for version 3.1, new maintainer.
system/sarasa-gothic: Updated for version 1.0.20.
system/unicode-character-database: Updated for version 16.0.0.
system/usermin: Updated for version 2.102.
+--------------------------+


-- 
Willy Sudiarto Raharjo

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

From belka at caraus.de  Sat Aug 31 17:58:12 2024
From: belka at caraus.de (Eugen Wissner)
Date: Sat, 31 Aug 2024 19:58:12 +0200
Subject: [Slackbuilds-users] nginx maintenance
Message-ID: <D3UAILFQTHXF.3HLU8W785A1S7@caraus.de>

Hello,

I'm a bit concerned about nginx not being updated since 1.23.2, because
I use it in production and wouldn't like to get any security
problems because of it. And the last updates weren't done by the actual
maintainer.

Larry Hajali (the maintainer) doesn't seem to be active anymore. I've
found a commit message from 2022 about his other script,
multimedia/kodi (commit bce52521d6):

> Larry has not responded to several email messages and it seems no
> others have been able to reach him as well.

So I suppose I can take over the maintainence of nginx?

Probably his other scripts need care too. The list is pretty long.

alienarena
apsw
assaultcube
audiopreview
bitstream
brainparty
cdk
chartgeany
chroma
chromium-bsu
css-parser
cssutils
cubosphere
cuneiform
cuyo
dcadec
dosemu
dukpy
dvblast
easystroke
enca
eyeD3
filechunkio
flvstreamer
fpconst
gdata
glestae
gst0-python
gtkimageview
html5-parser
http-parser
irrlicht
jag
keychain
kradio
ldns
libaacs
libb64
libbdplus
libcec
libdc1394
libdivecomputer
libdvbcsa
libmodplug
libmusicbrainz3
libnfs
libotf
libunique
lockdev
meandmyshadow
mechanize
megaglest
mini18n
notification-daemon
ois
opensonic
pasang-emas
peg-e
perl-Cstools
perl-IO-CaptureOutput
perl-Unicode-Map
perl-Unicode-Map8
perl-trayicon
pidgin-toobars
platform
pydf
pymysql
pypoppler
python-distutils-extra
python-libnacl
python-musicbrainz2
python-sh
python2-MarkupSafe
python2-dateutil
python2-keyczar
qalculate-gtk
qcad
rezerwar
rope
s3cmd
shotcut
sigil
simplejson
soil
speedcrunch
subsurface
sysdig
t4k_common
tinyxml
tinyxml2
tuxmath
unrardll
wxMaxima
xmlcopyeditor
xvst
yabause
yagf

From jebrhansen+SBo at gmail.com  Sat Aug 31 18:23:59 2024
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sat, 31 Aug 2024 11:23:59 -0700
Subject: [Slackbuilds-users] nginx maintenance
In-Reply-To: <D3UAILFQTHXF.3HLU8W785A1S7@caraus.de>
References: <D3UAILFQTHXF.3HLU8W785A1S7@caraus.de>
Message-ID: <CANi9qSszSS1fFJ1HyEF9-5fHsY+cPtw85DDQ8itUyOr4-8j2oQ@mail.gmail.com>

I can take libcec, libnfs, tinyxml, and tinyxml2 since they're dependencies
of Kodi.

I can also take over his games as I hate to see games become unmaintained
and dropped, but I'll give people time to take over individuals that they
want to maintain and then I can take over the remaining.

Jeremy

On Sat, Aug 31, 2024, 10:58?AM Eugen Wissner <belka at caraus.de> wrote:

> Hello,
>
> I'm a bit concerned about nginx not being updated since 1.23.2, because
> I use it in production and wouldn't like to get any security
> problems because of it. And the last updates weren't done by the actual
> maintainer.
>
> Larry Hajali (the maintainer) doesn't seem to be active anymore. I've
> found a commit message from 2022 about his other script,
> multimedia/kodi (commit bce52521d6):
>
> > Larry has not responded to several email messages and it seems no
> > others have been able to reach him as well.
>
> So I suppose I can take over the maintainence of nginx?
>
> Probably his other scripts need care too. The list is pretty long.
>
> alienarena
> apsw
> assaultcube
> audiopreview
> bitstream
> brainparty
> cdk
> chartgeany
> chroma
> chromium-bsu
> css-parser
> cssutils
> cubosphere
> cuneiform
> cuyo
> dcadec
> dosemu
> dukpy
> dvblast
> easystroke
> enca
> eyeD3
> filechunkio
> flvstreamer
> fpconst
> gdata
> glestae
> gst0-python
> gtkimageview
> html5-parser
> http-parser
> irrlicht
> jag
> keychain
> kradio
> ldns
> libaacs
> libb64
> libbdplus
> libcec
> libdc1394
> libdivecomputer
> libdvbcsa
> libmodplug
> libmusicbrainz3
> libnfs
> libotf
> libunique
> lockdev
> meandmyshadow
> mechanize
> megaglest
> mini18n
> notification-daemon
> ois
> opensonic
> pasang-emas
> peg-e
> perl-Cstools
> perl-IO-CaptureOutput
> perl-Unicode-Map
> perl-Unicode-Map8
> perl-trayicon
> pidgin-toobars
> platform
> pydf
> pymysql
> pypoppler
> python-distutils-extra
> python-libnacl
> python-musicbrainz2
> python-sh
> python2-MarkupSafe
> python2-dateutil
> python2-keyczar
> qalculate-gtk
> qcad
> rezerwar
> rope
> s3cmd
> shotcut
> sigil
> simplejson
> soil
> speedcrunch
> subsurface
> sysdig
> t4k_common
> tinyxml
> tinyxml2
> tuxmath
> unrardll
> wxMaxima
> xmlcopyeditor
> xvst
> yabause
> yagf
> _______________________________________________
> 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/20240831/54b026e1/attachment-0001.htm>

From urchlay at slackware.uk  Sat Aug 31 22:33:26 2024
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 31 Aug 2024 18:33:26 -0400 (EDT)
Subject: [Slackbuilds-users] nginx maintenance
In-Reply-To: <D3UAILFQTHXF.3HLU8W785A1S7@caraus.de>
References: <D3UAILFQTHXF.3HLU8W785A1S7@caraus.de>
Message-ID: <3e6f56f2-1a4-1ac3-ad52-3c8ac72232d@slackware.uk>



On Sat, 31 Aug 2024, Eugen Wissner wrote:

> Larry Hajali (the maintainer) doesn't seem to be active anymore. I've
> found a commit message from 2022 about his other script,
> multimedia/kodi (commit bce52521d6):
>
>> Larry has not responded to several email messages and it seems no
>> others have been able to reach him as well.

I've got Larry on my private list of ex-maintainers. It probably
should become a public list at some point... will post it to the list
Real Soon Now.

> So I suppose I can take over the maintainence of nginx?

Yes, please do.

> Probably his other scripts need care too. The list is pretty long.

Maintainers: you should look at Larry's scripts, and see if any of
*your* builds depend on them. If so, you should consider taking over
the dependencies for your stuff, to avoid them being removed (and your
build, too, if its dependencies are removed...)

I would estimate that about 25% of our repo is effectively
unmaintained.  We really need folks to step up and take over anything
they need or are interested in.

From dominik.drobek at o2.pl  Sat Aug 31 23:47:47 2024
From: dominik.drobek at o2.pl (Dominik Drobek)
Date: Sun, 1 Sep 2024 01:47:47 +0200
Subject: [Slackbuilds-users] Orphaning my SlackBuilds
Message-ID: <268ec249-cd11-c4e9-51c3-b578419baa8c@o2.pl>

Hi everyone,

I'm moving away from Slackware, so please consider my SlackBuilds 
orphaned. Feel free to change the license if you wish.


audio/MP3Diags: can be updated to a stable QT5-based version.

desktop/xfce4-volumed-pulse: needs updating (it couldn't be updated in 
14.2).

games/OpenXcom: no stable version since ages, just nightlies.

graphics/gcolor2: obsolete, but I'm not aware of an equivalent GTK+3 
version.

network/aircrack-ng: at latest version.
network/cowpatty: at latest version, doesn't look like it's developed 
anymore.
network/macchanger: at latest version. Mature, hasn't been updated in years.
network/pidgin-extprefs: at latest version, not sure if this package is 
still useful.
network/skype4pidgin: at latest version, not sure if this package is 
still useful.
network/SoulseekQt: Linux version hasn't been updated since 2018. Better 
Linux clients are available.

office/latexdiff: needs updating.

perl/perl-Text-Iconv: at latest version. Mature, hasn't been updated in 
years.

python/GeoIP-Python: at latest version. Obsolete, but some software 
still depends on it.
python/pyotp: actively developed, needs updating.

system/hddtemp: no upstream development in years, but an active fork 
with a newer version exists.
system/pigz: needs updating.


Best regards,
Dominik

From mail at rbn.im  Sat Aug 24 15:04:44 2024
From: mail at rbn.im (Ruben Schuller)
Date: Sat, 24 Aug 2024 15:04:44 +0000
Subject: [Slackbuilds-users] Windows 32/64 apps without multilib
In-Reply-To: <5a9f4916-caaf-459e-9e5c-fbcf300e06aa@yahoo.com>
References: <5a9f4916-caaf-459e-9e5c-fbcf300e06aa.ref@yahoo.com>
 <5a9f4916-caaf-459e-9e5c-fbcf300e06aa@yahoo.com>
Message-ID: <26zu41.siq9w0.0-qmf@orgizm.net>

Hi!

The wine found on SBo now can run win32 applications on slackware64 without multilib! Wouldn't have known but someone recently told me as well :)

Cheers
Ruben

Am Samstag, 24. August 2024 schrieb Antonio Leal via SlackBuilds-users:
> In the spirit of true slackin' been playing around with AppImages and 
> build a couple in the form
> 
> of a slackbuild script. I think these not "publishable" in 
> SlackBuilds.org but could solve some of our members needs.
> 
> The idea is to take a wine AppImage, unpack, add a small windows app, 
> and repack it in a single file.
> 
> 
> The examples :
> 
> Notepad++ editor: 
> https://github.com/antonioleal/myslackbuilds/tree/main/development/notepad%2B%2B
> 
> ZOOM Edit&Share Guitar Pedal app: 
> https://github.com/antonioleal/myslackbuilds/tree/main/audio/zoom-edit-n-share
> 
> 
> These actually do an "install on first run", but it the app is portable 
> is also fine to run it from within the AppImage itself, and
> 
> not from the installed binary. Best of all runs win32 and win64 apps 
> without multilib...
> 
> The SlackBuild scritps are self explanatory.
> 
> 
> This nothing special and probably been achieved a million times, but 
> anyway here it is...re-done again.
> 
> Happy slacking holidays.
> 
> Ant?nio
> 
> _______________________________________________
> 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/
> 
>