From dchmelik at gmail.com  Thu Jun  1 10:53:07 2023
From: dchmelik at gmail.com (dchmelik at gmail.com)
Date: Thu, 1 Jun 2023 03:53:07 -0700
Subject: [Slackbuilds-users] Devuan debootstrap?
Message-ID: <e71cb8c9-873e-aeca-00f3-c6ba8cfa0612@gmail.com>

I tried sending this message to the maintainer and his email server 
rejected it as spam:
Can debootstrap be used for Devuan?? I hate Debian since they switched 
to systemd...


From j at lngn.net  Thu Jun  1 12:13:50 2023
From: j at lngn.net (J)
Date: Thu, 1 Jun 2023 08:13:50 -0400
Subject: [Slackbuilds-users] Devuan debootstrap?
In-Reply-To: <e71cb8c9-873e-aeca-00f3-c6ba8cfa0612@gmail.com>
References: <e71cb8c9-873e-aeca-00f3-c6ba8cfa0612@gmail.com>
Message-ID: <0570A8CB-2260-4D60-985C-8B3F104D4347@edison.tech>

      
  

 I just used debootstrap earlier today actually! But AFAIK it only supports Debian and Ubuntu. There was a way about 6 months ago about that you could setup sysvinit instead of systemd, I had it going on a few vms but it could only be done from the normal installer, there don?t appear to be a way (that I?m aware of) to install the sysvinit setup with debootstrap.   
  

  
But since the system isn?t running upon install, you should be able to remove systemd and install the ?elogind? and ?sysvinit-scripts? packages. There may be another one and deps may pull it in already, someone else may know if there?s more packages yet?
  
  
  
? Jay Lanagan
  
  
  

  
  
>   
> On Jun 1, 2023 at 6:53 AM,  <Dchmelik (mailto:dchmelik at gmail.com)>  wrote:
>   
>   
>   
>  I tried sending this message to the maintainer and his email server rejected it as spam: Can debootstrap be used for Devuan? I hate Debian since they switched to systemd... _______________________________________________ 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/20230601/5c3df917/attachment-0001.htm>

From bru.barwal at SDF.ORG  Thu Jun  1 18:28:33 2023
From: bru.barwal at SDF.ORG (Bru Barwal)
Date: Thu, 1 Jun 2023 18:28:33 +0000
Subject: [Slackbuilds-users] Devuan debootstrap?
In-Reply-To: <e71cb8c9-873e-aeca-00f3-c6ba8cfa0612@gmail.com>
References: <e71cb8c9-873e-aeca-00f3-c6ba8cfa0612@gmail.com>
Message-ID: <ZHjjUfE3c68Rv5S8@SDF.ORG>

On Thu, Jun 01, 2023 at 03:53:07AM -0700, dchmelik at gmail.com wrote:
> I tried sending this message to the maintainer and his email server rejected
> it as spam:
> Can debootstrap be used for Devuan??? I hate Debian since they switched to
> systemd...

As far as I can tell, the debian source for deboostrap doesn't have the 
proper scripts to install devuan, but I was able to get it working:

```
cd /usr/share/deboostrap/scripts
rm ceres
wget
https://git.devuan.org/devuan/debootstrap/raw/branch/suites/beowulf-proposed-updates/scripts/ceres
ln -s ceres chimaera
debootstrap --arch amd64 chimaera /mnt/devuan \
http://deb.devuan.org/merged/ chimaera
```

I guess the other option would be to tweak the slackbuild to use the
devuan debootstrap source. I believe it has the scripts for debian
and ubuntu as well as devuan.

Good luck!

-Matt

-- 
bru.barwal at sdf.org
SDF Public Access UNIX System - http://sdf.org

From willysr at slackbuilds.org  Sat Jun  3 04:03:09 2023
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 3 Jun 2023 11:03:09 +0700
Subject: [Slackbuilds-users] Updates - 20230603.1
Message-ID: <15475486-cc02-29f8-2125-9f872b046eac@slackbuilds.org>

Sat Jun  3 03:39:33 UTC 2023
academic/fet: Updated for version 6.9.1.
academic/gspiceui: Updated for version 1.2.87.
academic/mendeleydesktop: Fix ARCH.
academic/nco: Updated for version 5.1.6.
accessibility/magnus: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
audio/JDSP4Linux: Updated for version 2.4.
audio/clementine: Version bump to 1.4.0rc2
audio/flacon: Updated for version 11.1.0.
audio/gtklick: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
audio/mididings: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
audio/musikcube: Updated for version 3.0.1.
audio/sndio: Added (small audio and MIDI framework)
desktop/9menu: Get rid of unused LIBDIRSUFFIX.
desktop/BlockstreamGreen: Updated for version 1.2.0.
desktop/breath-gtk-theme: Change version format
desktop/calls: Added (GNOME Calls)
desktop/dapper: Added (Desktop Applications Autostarter)
desktop/gopsuinfo: Updated for version 0.1.4.
desktop/i3-easyfocus: Added (Focus and select windows in i3)
desktop/nwg-displays: Updated for version 0.3.3.
desktop/nwg-panel: Updated for version 0.9.4.
desktop/nwg-shell-config: Updated for version 0.5.0.
desktop/wlsunset: Updated for version 0.3.0.
development/acpica: Updated for version 20230331.
development/codespell: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
development/cutter: Added (FOSS Reverse Engineering Platform)
development/github-cli: Updated for version 2.30.0
development/gsoap: Updated for version 2.8.127.
development/hugo: Updated for version 0.112.7.
development/icdiff: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
development/jupyter-nbformat: Updated for version 5.9.0.
development/jupyter_server: Update for 2.6.0
development/kawa.bin: Added (Scheme implementation running on JVM)
development/kodespel: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
development/neovim: Updated for version 0.9.1.
development/ophis: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
development/premake5: Fix encoding of SlackBuild.
development/universal-ctags: Updated for version p6.0.20230528.0
games/SpaceCadetPinball: Added (3D Pinball for Windows- Space Cadet)
games/ZEsarUX: Updated for version 10.3.
games/clksignal: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
games/endless-sky: updated for version 0.10.1
games/eureka: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
games/nexuiz: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
games/puzzles: Updated for version 20230527.b6c842a.
games/sumeria: actually use SLKCFLAGS.
games/wolfmame: Updated for version 0.255.
games/yahtzee: Actually use SLKCFLAGS.
gis/eccodes: Updated for version 2.30.2.
gis/gdal: Updated for version 3.7.0.
gis/proj: Updated for version 9.2.1.
graphics/FotoKilof: Added (graphic interface for ImageMagick)
graphics/OpenSubdiv: Option for CUDA support
graphics/posterazor: Added (make poster printing patterns)
graphics/ueberzugpp: Updated for version 2.8.6.
graphics/vuescan: Updated for versino 9.8.03.
libraries/OpenSceneGraph: Ignore OpenCASCADE
libraries/ceres-solver: Added (Open Source Optimization Library)
libraries/dbus-cpp: Version bump to 5.0.3 and update homepage
libraries/kddockwidgets: Added (KDAB's Dock Widget Framework for Qt)
libraries/libcurl-gnutls: Updated for version 8.1.2.
libraries/libgrss: Added (rss parser for the tracker desktop search)
libraries/libspng: Added (Portable Network PNG C library)
libraries/libtins: Fix cmake support files.
libraries/process-cpp: Update homepage and src download locations,
libraries/properties-cpp: Version bump to 0.0.2 and update homepage
libraries/webkit2gtk4.1: Updated for version 2.40.2.
libraries/webkit2gtk: Updated for version 2.40.2.
misc/asterixInspector: Updated for version 0.13.2.
misc/bitwarden-desktop: Updated for version 2023.5.0.
misc/python3-random-username: Added (Generate random usernames)
misc/txt2tags: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
multimedia/filebot: Version bump to 5.0.3
multimedia/haruna: Updated for version 0.11.1.
multimedia/inputstream.adaptive: Version bump to 20.3.9
multimedia/plexmediaserver: Fix ARCH, .desktop, speed up build.
multimedia/spotify: Updated for version 1.2.11.916.
multimedia/winff: Fix ARCH, README grammar.
network/dublin-traceroute: Do not write to $CWD.
network/gallery-dl: Updated for version 1.25.5.
network/haproxy: Updated for version 2.8.0.
network/jitsi-meet-desktop: Update for 2023.5.3
network/prosody-mod-csi: Removed (part of prosody 0.11.x).
network/prosody-mod-smacks: Removed (part of prosody 0.12.x).
network/protonmail-bridge: Updated for version 3.2.0.
network/qbittorrent: Updated for version 4.5.3.
network/rtl8812bu: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
network/signal-desktop: Updated for version 6.20.0.
network/surl: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
network/tnfs-fuse: Remove unused SLKCFLAGS.
network/webex: Align with template.
office/calibre-bin: Updated for version 6.19.1.
office/calibre: Removed (Use calibre-bin).
office/epy: Updated for version 2023.2.8.
office/mupdf: Actually use SLKCFLAGS.
office/python3-proselint: Added (a stylistic checker spellchecker)
office/texlive-docs: Updated for version 2023.230322.
office/x_x: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
office/xlsx2csv: Removed (use python3 version).
perl/perl-GD: Updated for version 2.77.
perl/perl-IO-Tty: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
perl/perl-Term-ReadLine-Gnu: rm unused LIBDIRSUFFIX and SLKCFLAGS.
perl/perl-Unicode-LineBreak: rm unused LIBDIRSUFFIX and SLKCFLAGS.
perl/perl-audio-sndfile: rm unused LIBDIRSUFFIX and SLKCFLAGS.
perl/perl-data-dump: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
perl/perl-file-libmagic: rm unused LIBDIRSUFFIX and SLKCFLAGS.
perl/perl-xml-fast: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
python/google-apputils: Removed (No longer build).
python/huepy: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
python/huepy: New maintainer.
python/path.py: Remove junk file.
python/pyelftools: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
python/pyliblo: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
python/python-msal: Added (Microsoft Auth Library (MSAL) for Python)
python/python-wand: Added (ImageMagick binding for Python)
python/python2-pyasn1: Updated for version 0.5.0.
python/python3-anyio: Update README
python/python3-caldav: Added (CalDAV client library for Python)
python/python3-iniconfig: Added (ini file parsing)
python/python3-paramiko: Updated for version 3.2.0.
python/python3-pyasn1: Updated for version 0.5.0.
python/python3-pytest: Updated for version 7.3.1.
python/python3-sge: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
python/python3-sgmllib3k: rm unused LIBDIRSUFFIX and SLKCFLAGS.
python/python3-soundfile: Added (libsndfile/CFFI/NumPy Audio lib)
python/ttkbootstrap: Added (theme extension for tkinter)
system/a2tools: Fix compile warnings.
system/alacritty: Updated for version 0.12.1.
system/anything-sync-daemon: Install completions in right places.
system/archmage: Get rid of unused LIBDIRSUFFIX and SLKCFLAGS.
system/bubblewrap: Updated for version 0.8.0.
system/burp: Updated for version 2.4.0 by S Arcus.
system/bzip3: Added (Successor to BZip2)
system/dget: Updated for version 2.23.4.
system/fzf: Updated for version 0.41.1.
system/grub4dos: Fix ARCH.
system/jenkins: Updated for version 2.401.1.
system/kbfs: Removed.
system/slpkg: Updated for version 4.8.8.
system/unrar-free: Added (free version of the non-free unrar util)
system/virtualbox-addons: Updated for version 6.1.44.
system/virtualbox-extension-pack: Updated for version 6.1.44.
system/virtualbox-kernel: Updated for version 6.1.44.
system/virtualbox: Updated for version 6.1.44.
system/virtualxt: Added (IBM PC/XT emulator)
system/xdg-ninja: Added ($HOME Dir Cleaner)
+--------------------------+


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

From zsd+slackbuilds at jdvb.ca  Sat Jun  3 21:18:16 2023
From: zsd+slackbuilds at jdvb.ca (Jim)
Date: Sat, 3 Jun 2023 18:18:16 -0300
Subject: [Slackbuilds-users] mate-terminal
In-Reply-To: <ZGkfG85yNZHn704I@x360.localdomain>
References: <ZFvCu8EtDOD4Fa0x@x360.localdomain>
 <eb3aae47-6525-4b68-8137-fc3cc6f7447f@app.fastmail.com>
 <ZGkfG85yNZHn704I@x360.localdomain>
Message-ID: <ZHuuGPA938Wp4ULS@x360.localdomain>

The SlackBuild for mate-terminal lists no dependencies.

But when I try to run it, after installing the slackbuild, I get
        (mate-terminal:23450): GLib-GIO-ERROR **: 18:10:40.076: Settings schema 'org.mate.interface' is not installed

Should there be some information in the SlackBuild about what other
SlackBuild package(s) are required to make this work?

(Or, if no packages per se are required, what is needed to make
mate-terminal run?)

Thanks.
                                Jim

From marav8 at free.fr  Sat Jun  3 22:30:14 2023
From: marav8 at free.fr (marav)
Date: Sun, 4 Jun 2023 00:30:14 +0200
Subject: [Slackbuilds-users] mate-terminal
In-Reply-To: <ZHuuGPA938Wp4ULS@x360.localdomain>
References: <ZFvCu8EtDOD4Fa0x@x360.localdomain>
 <eb3aae47-6525-4b68-8137-fc3cc6f7447f@app.fastmail.com>
 <ZGkfG85yNZHn704I@x360.localdomain> <ZHuuGPA938Wp4ULS@x360.localdomain>
Message-ID: <067da2a2-d795-ba2f-7d25-48c217df765c@free.fr>

Le 03/06/2023 ? 23:18, Jim a ?crit?:
> The SlackBuild for mate-terminal lists no dependencies.
>
> But when I try to run it, after installing the slackbuild, I get
>          (mate-terminal:23450): GLib-GIO-ERROR **: 18:10:40.076: Settings schema 'org.mate.interface' is not installed
>
> Should there be some information in the SlackBuild about what other
> SlackBuild package(s) are required to make this work?
>
> (Or, if no packages per se are required, what is needed to make
> mate-terminal run?)
>
> Thanks.
>                                  Jim
> _______________________________________________
> 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/
>
It needs mate-desktop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230604/0c7170bd/attachment.htm>

From didier at slint.fr  Sat Jun  3 22:42:50 2023
From: didier at slint.fr (Didier Spaier)
Date: Sun, 4 Jun 2023 00:42:50 +0200
Subject: [Slackbuilds-users] mate-terminal
In-Reply-To: <067da2a2-d795-ba2f-7d25-48c217df765c@free.fr>
References: <ZFvCu8EtDOD4Fa0x@x360.localdomain>
 <eb3aae47-6525-4b68-8137-fc3cc6f7447f@app.fastmail.com>
 <ZGkfG85yNZHn704I@x360.localdomain> <ZHuuGPA938Wp4ULS@x360.localdomain>
 <067da2a2-d795-ba2f-7d25-48c217df765c@free.fr>
Message-ID: <2bd9df2b-d589-42c4-9cd7-a00bb7d41240@slint.fr>

Le 04/06/2023 ? 00:30, marav a ?crit?:
> It needs mate-desktop

mate-desktop does provide the file
/usr/share/glib-2.0/schemas/org.mate.interface.gschema.xml but mate terminal
works without that, I just checked (I have upgraded all mate components to their
latest version for Slint a few days ago).

From marav8 at free.fr  Sat Jun  3 22:46:25 2023
From: marav8 at free.fr (marav)
Date: Sun, 4 Jun 2023 00:46:25 +0200
Subject: [Slackbuilds-users] mate-terminal
In-Reply-To: <2bd9df2b-d589-42c4-9cd7-a00bb7d41240@slint.fr>
References: <ZFvCu8EtDOD4Fa0x@x360.localdomain>
 <eb3aae47-6525-4b68-8137-fc3cc6f7447f@app.fastmail.com>
 <ZGkfG85yNZHn704I@x360.localdomain> <ZHuuGPA938Wp4ULS@x360.localdomain>
 <067da2a2-d795-ba2f-7d25-48c217df765c@free.fr>
 <2bd9df2b-d589-42c4-9cd7-a00bb7d41240@slint.fr>
Message-ID: <9d839ca9-75de-14a0-74c8-5aa58741bac6@free.fr>

Le 04/06/2023 ? 00:42, Didier Spaier a ?crit?:
> Le 04/06/2023 ? 00:30, marav a ?crit?:
>> It needs mate-desktop
> mate-desktop does provide the file
> /usr/share/glib-2.0/schemas/org.mate.interface.gschema.xml but mate terminal
> works without that, I just checked (I have upgraded all mate components to their
> latest version for Slint a few days ago).
> _______________________________________________
> 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 here

plus, it is listed as running dependency by all others (arch, gentoo, 
fedora, ...)

ex: for Fedora

*# needed to get a gsettings schema, rhbz #908105
Requires:????? mate-desktop-libs
Requires:????? gsettings-desktop-schemas*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230604/fa688fba/attachment.htm>

From didier at slint.fr  Sat Jun  3 23:00:21 2023
From: didier at slint.fr (Didier Spaier)
Date: Sun, 4 Jun 2023 01:00:21 +0200
Subject: [Slackbuilds-users] mate-terminal
In-Reply-To: <9d839ca9-75de-14a0-74c8-5aa58741bac6@free.fr>
References: <ZFvCu8EtDOD4Fa0x@x360.localdomain>
 <eb3aae47-6525-4b68-8137-fc3cc6f7447f@app.fastmail.com>
 <ZGkfG85yNZHn704I@x360.localdomain> <ZHuuGPA938Wp4ULS@x360.localdomain>
 <067da2a2-d795-ba2f-7d25-48c217df765c@free.fr>
 <2bd9df2b-d589-42c4-9cd7-a00bb7d41240@slint.fr>
 <9d839ca9-75de-14a0-74c8-5aa58741bac6@free.fr>
Message-ID: <9f22c13a-c1d5-c75a-1658-7f71c7278bd1@slint.fr>



Le 04/06/2023 ? 00:46, marav a ?crit?:
> Le 04/06/2023 ? 00:42, Didier Spaier a ?crit?:
>> Le 04/06/2023 ? 00:30, marav a ?crit?:
>>> It needs mate-desktop
>> mate-desktop does provide the file
>> /usr/share/glib-2.0/schemas/org.mate.interface.gschema.xml but mate terminal
>> works without that, I just checked (I have upgraded all mate components to their
>> latest version for Slint a few days ago).
>> _______________________________________________
>>
> Not here
> 
> plus, it is listed as running dependency by all others (arch, gentoo, fedora, ...)
> 
> ex: for Fedora
> 
> *# needed to get a gsettings schema, rhbz #908105
> Requires:????? mate-desktop-libs
> Requires:????? gsettings-desktop-schemas*

didier[~]$ mate-terminal --version
Terminal MATE 1.26.1
didier[~]$ ldd /usr/bin/mate-terminal|grep mate
didier[~]$

As there are 88 sonames I refrained to post the full output of ldd ;)

From marav8 at free.fr  Sun Jun  4 00:39:38 2023
From: marav8 at free.fr (marav)
Date: Sun, 4 Jun 2023 02:39:38 +0200
Subject: [Slackbuilds-users] mate-terminal
In-Reply-To: <9f22c13a-c1d5-c75a-1658-7f71c7278bd1@slint.fr>
References: <ZFvCu8EtDOD4Fa0x@x360.localdomain>
 <eb3aae47-6525-4b68-8137-fc3cc6f7447f@app.fastmail.com>
 <ZGkfG85yNZHn704I@x360.localdomain> <ZHuuGPA938Wp4ULS@x360.localdomain>
 <067da2a2-d795-ba2f-7d25-48c217df765c@free.fr>
 <2bd9df2b-d589-42c4-9cd7-a00bb7d41240@slint.fr>
 <9d839ca9-75de-14a0-74c8-5aa58741bac6@free.fr>
 <9f22c13a-c1d5-c75a-1658-7f71c7278bd1@slint.fr>
Message-ID: <9b06820b-de93-c590-4f40-b268b5c290c4@free.fr>

Le 04/06/2023 ? 01:00, Didier Spaier a ?crit?:
>
> Le 04/06/2023 ? 00:46, marav a ?crit?:
>> Le 04/06/2023 ? 00:42, Didier Spaier a ?crit?:
>>> Le 04/06/2023 ? 00:30, marav a ?crit?:
>>>> It needs mate-desktop
>>> mate-desktop does provide the file
>>> /usr/share/glib-2.0/schemas/org.mate.interface.gschema.xml but mate terminal
>>> works without that, I just checked (I have upgraded all mate components to their
>>> latest version for Slint a few days ago).
>>> _______________________________________________
>>>
>> Not here
>>
>> plus, it is listed as running dependency by all others (arch, gentoo, fedora, ...)
>>
>> ex: for Fedora
>>
>> *# needed to get a gsettings schema, rhbz #908105
>> Requires:????? mate-desktop-libs
>> Requires:????? gsettings-desktop-schemas*
> didier[~]$ mate-terminal --version
> Terminal MATE 1.26.1
> didier[~]$ ldd /usr/bin/mate-terminal|grep mate
> didier[~]$
>
> As there are 88 sonames I refrained to post the full output of ldd ;)
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ -https://slackbuilds.org/faq/
>
https://bugzilla.redhat.com/show_bug.cgi?id=908105

More than 10 years old bug report, but it seems that all others include 
mate-desktop as a requirement

And, so far, mate-terminal is not working for Jim, as for me


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

From artourter at gmail.com  Sun Jun  4 00:57:59 2023
From: artourter at gmail.com (Greg Tourte)
Date: Sun, 4 Jun 2023 01:57:59 +0100
Subject: [Slackbuilds-users] pdal fails to compile with gdal 3.7
Message-ID: <CAK09-vmz_KXB-iYGPy1K71KHpAH-fEHRReQ8bGcH4NB1hs75Hw@mail.gmail.com>

Hi,

I would like to apologise as somehow I failed to test pdal when I updated
gdal to version 3.7 this week. I thought I had, but I made a mistake in the
testing process and pdal slipped through the crack.

anyway, the pdal version (2.5.3) currently in slackbuild (and the previous
one, i.e. 2.2.0) does not compile with gdal 3.7 (see
https://github.com/PDAL/PDAL/pull/4030).

As the ticket mentions, it was fixed in version 2.5.4. I have tested it by
simply changing the version in the slackbuild (md5sum =
3e559237458b763fffaa98648e906bdc).

I am going through the gdal dependees again to make sure I didn't miss any
others.

Cheers

Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230604/2b1625a7/attachment.htm>

From didier at slint.fr  Sun Jun  4 03:54:20 2023
From: didier at slint.fr (Didier Spaier)
Date: Sun, 4 Jun 2023 05:54:20 +0200
Subject: [Slackbuilds-users] mate-terminal
In-Reply-To: <9b06820b-de93-c590-4f40-b268b5c290c4@free.fr>
References: <ZFvCu8EtDOD4Fa0x@x360.localdomain>
 <eb3aae47-6525-4b68-8137-fc3cc6f7447f@app.fastmail.com>
 <ZGkfG85yNZHn704I@x360.localdomain> <ZHuuGPA938Wp4ULS@x360.localdomain>
 <067da2a2-d795-ba2f-7d25-48c217df765c@free.fr>
 <2bd9df2b-d589-42c4-9cd7-a00bb7d41240@slint.fr>
 <9d839ca9-75de-14a0-74c8-5aa58741bac6@free.fr>
 <9f22c13a-c1d5-c75a-1658-7f71c7278bd1@slint.fr>
 <9b06820b-de93-c590-4f40-b268b5c290c4@free.fr>
Message-ID: <9e062d17-2ec8-2893-87b8-73f670e1284a@slint.fr>

Le 04/06/2023 ? 02:39, marav a ?crit?:
> Le 04/06/2023 ? 01:00, Didier Spaier a ?crit?:
>> Le 04/06/2023 ? 00:46, marav a ?crit?:
>>> Le 04/06/2023 ? 00:42, Didier Spaier a ?crit?:
>>>> Le 04/06/2023 ? 00:30, marav a ?crit?:
>>>>> It needs mate-desktop
>>>> mate-desktop does provide the file
>>>> /usr/share/glib-2.0/schemas/org.mate.interface.gschema.xml but mate terminal
>>>> works without that, I just checked (I have upgraded all mate components to their
>>>> latest version for Slint a few days ago).
>>>> _______________________________________________
>>>>
>>> Not here
>>>
>>> plus, it is listed as running dependency by all others (arch, gentoo, fedora, ...)
>>>
>>> ex: for Fedora
>>>
>>> *# needed to get a gsettings schema, rhbz #908105
>>> Requires:????? mate-desktop-libs
>>> Requires:????? gsettings-desktop-schemas*
>> didier[~]$ mate-terminal --version
>> Terminal MATE 1.26.1
>> didier[~]$ ldd /usr/bin/mate-terminal|grep mate
>> didier[~]$
>>
>> As there are 88 sonames I refrained to post the full output of ldd ;)
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
> https://bugzilla.redhat.com/show_bug.cgi?id=908105
> 
> More than 10 years old bug report, but it seems that all others include
> mate-desktop as a requirement
> 
> And, so far, mate-terminal is not working for Jim, as for me

You made me curious.

When I removed the mate-desktop package I was (and still am) in the LXQt desktop.

So I typed "session-chooser mate", pressed Ctrl+Alt+F2, logged in then typed startx.

Not surprisingly MATE didn't start. I redirect the standard error to /tmp/$(id
-nu)/startx.err when running startx and found there a lot of errors.

So I ran (from LXQt still running) a small script which scans not found binaries
dependencies and the output (attached) indeed includes a lot of lines like this one:
libmate-desktop-2.so.17 => not found
although amazingly none while checking a binary file shipped in mate-terminal.

So even if mate-terminal per se does not require mate-desktop, it of course
doesn't make sense to start a MATE desktop without a mate-desktop package ;)

This not withstanding mate-terminal continue to work for me if started from
another graphical environment than MATE (at least mate-terminal version 1.26.1).
-------------- next part --------------
/usr/lib64/caja/extensions-2.0/libcaja-open-terminal.so
	libmate-desktop-2.so.17 => not found
/usr/lib64/eom/plugins/libfullscreen.so
	libmate-desktop-2.so.17 => not found
/usr/lib64/eom/plugins/libreload.so
	libmate-desktop-2.so.17 => not found
/usr/lib64/eom/plugins/libstatusbar-date.so
	libmate-desktop-2.so.17 => not found
/usr/lib64/window-manager-settings/libmarco.so
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/lib64/mate-settings-daemon/libbackground.so
	libmate-desktop-2.so.17 => not found
/usr/lib64/mate-settings-daemon/libxrandr.so
	libmate-desktop-2.so.17 => not found
/usr/bin/caja
	libmate-desktop-2.so.17 => not found
/usr/bin/caja-autorun-software
	libmate-desktop-2.so.17 => not found
/usr/bin/caja-connect-server
	libmate-desktop-2.so.17 => not found
/usr/bin/caja-file-management-properties
	libmate-desktop-2.so.17 => not found
/usr/bin/eom
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-about-me
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-appearance-properties
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-at-properties
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-control-center
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-default-applications-properties
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-display-properties
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-font-viewer
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-keybinding-properties
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-keyboard-properties
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-mouse-properties
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-network-properties
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-thumbnail-font
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-time-admin
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-typing-monitor
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-window-properties
	libmate-desktop-2.so.17 => not found
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-volume-control
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-volume-control-status-icon
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-screensaver
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-screensaver-preferences
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-settings-daemon
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-desktop-item-edit
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-panel
	libmate-desktop-2.so.17 => not found
/usr/bin/mate-panel-test-applets
	libmate-desktop-2.so.17 => not found
/usr/libexec/mate-volume-control-applet
	libmate-desktop-2.so.17 => not found
/usr/libexec/mate-screensaver-dialog
	libmate-desktop-2.so.17 => not found
/usr/libexec/mate-screensaver-gl-helper
	libmate-desktop-2.so.17 => not found

From slackbuilds at schoepfer.info  Sun Jun  4 04:55:27 2023
From: slackbuilds at schoepfer.info (Franzen)
Date: Sun, 04 Jun 2023 06:55:27 +0200
Subject: [Slackbuilds-users] mate-terminal
In-Reply-To: <9e062d17-2ec8-2893-87b8-73f670e1284a@slint.fr>
References: <ZFvCu8EtDOD4Fa0x@x360.localdomain>
 <eb3aae47-6525-4b68-8137-fc3cc6f7447f@app.fastmail.com>
 <ZGkfG85yNZHn704I@x360.localdomain> <ZHuuGPA938Wp4ULS@x360.localdomain>
 <067da2a2-d795-ba2f-7d25-48c217df765c@free.fr>
 <2bd9df2b-d589-42c4-9cd7-a00bb7d41240@slint.fr>
 <9d839ca9-75de-14a0-74c8-5aa58741bac6@free.fr>
 <9f22c13a-c1d5-c75a-1658-7f71c7278bd1@slint.fr>
 <9b06820b-de93-c590-4f40-b268b5c290c4@free.fr>
 <9e062d17-2ec8-2893-87b8-73f670e1284a@slint.fr>
Message-ID: <3D6D2898-4037-44F6-BE39-4BEFC78C1ACA@schoepfer.info>



Am 4. Juni 2023 05:54:20 MESZ schrieb Didier Spaier <didier at slint.fr>:
>Le 04/06/2023 ? 02:39, marav a ?crit?:
>> Le 04/06/2023 ? 01:00, Didier Spaier a ?crit?:
>>> Le 04/06/2023 ? 00:46, marav a ?crit?:
>>>> Le 04/06/2023 ? 00:42, Didier Spaier a ?crit?:
>>>>> Le 04/06/2023 ? 00:30, marav a ?crit?:
>>>>>> It needs mate-desktop
>>>>> mate-desktop does provide the file
>>>>> /usr/share/glib-2.0/schemas/org.mate.interface.gschema.xml but mate terminal
>>>>> works without that, I just checked (I have upgraded all mate components to their
>>>>> latest version for Slint a few days ago).
>>>>> _______________________________________________
>>>>>
>>>> Not here
>>>>
>>>> plus, it is listed as running dependency by all others (arch, gentoo, fedora, ...)
>>>>
>>>> ex: for Fedora
>>>>
>>>> *# needed to get a gsettings schema, rhbz #908105
>>>> Requires:????? mate-desktop-libs
>>>> Requires:????? gsettings-desktop-schemas*
>>> didier[~]$ mate-terminal --version
>>> Terminal MATE 1.26.1
>>> didier[~]$ ldd /usr/bin/mate-terminal|grep mate
>>> didier[~]$
>>>
>>> As there are 88 sonames I refrained to post the full output of ldd ;)
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=908105
>> 
>> More than 10 years old bug report, but it seems that all others include
>> mate-desktop as a requirement
>> 
>> And, so far, mate-terminal is not working for Jim, as for me
>
>You made me curious.
>
>When I removed the mate-desktop package I was (and still am) in the LXQt desktop.
>
>So I typed "session-chooser mate", pressed Ctrl+Alt+F2, logged in then typed startx.
>
>Not surprisingly MATE didn't start. I redirect the standard error to /tmp/$(id
>-nu)/startx.err when running startx and found there a lot of errors.
>
>So I ran (from LXQt still running) a small script which scans not found binaries
>dependencies and the output (attached) indeed includes a lot of lines like this one:
>libmate-desktop-2.so.17 => not found
>although amazingly none while checking a binary file shipped in mate-terminal.
>
>So even if mate-terminal per se does not require mate-desktop, it of course
>doesn't make sense to start a MATE desktop without a mate-desktop package ;)
>
>This not withstanding mate-terminal continue to work for me if started from
>another graphical environment than MATE (at least mate-terminal version 1.26.1).


Thanks for all the Info, i'll have a look in a few days when i'm home again. I did only check for build time requirements for mate-terminal, and using it in MATE, so i didn't notice.

Johannes 

From dev at iotib.net  Sun Jun  4 14:57:58 2023
From: dev at iotib.net (Charadon)
Date: Sun, 4 Jun 2023 14:57:58 +0000
Subject: [Slackbuilds-users] Abandoning Epiphany SlackBuild
Message-ID: <5c6b7fc1-8265-fd44-8d78-b919d28e341a@iotib.net>

I don't have any interest in maintaining Epiphany anymore as I don't use 
it, and upstream has been putting more emphasis on using the Flatpak 
version. If anyone wants it, you can have it =)

From j at lngn.net  Sun Jun  4 19:09:53 2023
From: j at lngn.net (J)
Date: Sun, 4 Jun 2023 15:09:53 -0400
Subject: [Slackbuilds-users] Abandoning Epiphany SlackBuild
In-Reply-To: <5c6b7fc1-8265-fd44-8d78-b919d28e341a@iotib.net>
References: <5c6b7fc1-8265-fd44-8d78-b919d28e341a@iotib.net>
Message-ID: <6BC7075A-2CC2-460E-BFDB-E42DA8D171FD@edison.tech>

      
  

 I actually do use it as epiphany is much lighter on aarch64 Slackware vs Firefox but I generally keep my own scripts since aarch64 isn?t targeted by most of SBo as of yet.   
  

  
I?m assuming 0xBOB may want this one to go with the rest of gnome, but if not, I?ll take it.   
  
  
  
? Jay Lanagan
  
  
  

  
  
>   
> On Jun 4, 2023 at 10:58 AM,  <Charadon via SlackBuilds-users (mailto:slackbuilds-users at slackbuilds.org)>  wrote:
>   
>   
>   
>  I don't have any interest in maintaining Epiphany anymore as I don't use it, and upstream has been putting more emphasis on using the Flatpak version. If anyone wants it, you can have it =) _______________________________________________ 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/20230604/b4fd1ff5/attachment.htm>

From isaacyu1 at isaacyu1.com  Sun Jun  4 23:34:23 2023
From: isaacyu1 at isaacyu1.com (=?utf-8?q?isaacyu1=40isaacyu1.com?=)
Date: Mon, 05 Jun 2023 01:34:23 +0200
Subject: [Slackbuilds-users] =?utf-8?q?Next_week=2C_I_will_no_longer_main?=
 =?utf-8?q?tain_and_update_SlackBuilds?=
Message-ID: <4520-647d1f80-d-6333f@58583900>


Hi everyone,

?????I now have 200+ SlackBuilds to maintain.
Given my part-time job and my coursework,?I am going to have a harder time maintaining it all.

This is the last week in which I will maintain and update SlackBuilds.

I will also switch my email address (on SlackBuilds) to isaacyu at protonmail.com:
https://github.com/SlackBuildsOrg/slackbuilds/pull/2898

I need to pay a small yearly subscription fee (to Gandi, the company) for the isaacyu1.com domain. However, the ProtonMail email service is free. Hence the email address change.

My SlackBuilds are available at the following link:
https://github.com/isaackwy/slackbuilds-15.0

I plan on switching to Debian.
Debian 12 (Bookworm) will be released in a few days, on June 10.

- Isaac
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230605/0cf91496/attachment.htm>

From bobfunk11 at gmail.com  Mon Jun  5 03:01:49 2023
From: bobfunk11 at gmail.com (Bob Funk)
Date: Sun, 4 Jun 2023 22:01:49 -0500
Subject: [Slackbuilds-users] Abandoning Epiphany SlackBuild
In-Reply-To: <6BC7075A-2CC2-460E-BFDB-E42DA8D171FD@edison.tech>
References: <5c6b7fc1-8265-fd44-8d78-b919d28e341a@iotib.net>
 <6BC7075A-2CC2-460E-BFDB-E42DA8D171FD@edison.tech>
Message-ID: <CAJOKJPbtvwYGbbQH4KhkWR8apjo+Ge_g6_fu41eThutubBWcxQ@mail.gmail.com>

I can take over maintaining epiphany and add it to the collection of gnome
core builds I've been building.

I'll look it over and submit an update to take over maintenance later this
week.

Bob

On Sun, Jun 4, 2023, 2:10 PM J via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> I actually do use it as epiphany is much lighter on aarch64 Slackware vs
> Firefox but I generally keep my own scripts since aarch64 isn?t targeted by
> most of SBo as of yet.
>
> I?m assuming 0xBOB may want this one to go with the rest of gnome, but if
> not, I?ll take it.
>
> ? Jay Lanagan
>
>
> On Jun 4, 2023 at 10:58 AM, <Charadon via SlackBuilds-users
> <slackbuilds-users at slackbuilds.org>> wrote:
>
> I don't have any interest in maintaining Epiphany anymore as I don't use
> it, and upstream has been putting more emphasis on using the Flatpak
> version. If anyone wants it, you can have it =)
> _______________________________________________
> SlackBuilds-users mailing listSlackBuilds-users at slackbuilds.orghttps://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/20230604/4b805424/attachment.htm>

From slackbuilds at schoepfer.info  Mon Jun  5 04:32:15 2023
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 05 Jun 2023 06:32:15 +0200
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <4520-647d1f80-d-6333f@58583900>
References: <4520-647d1f80-d-6333f@58583900>
Message-ID: <9712F8D4-DB39-43E3-87C4-053308B96834@schoepfer.info>



Am 5. Juni 2023 01:34:23 MESZ schrieb "isaacyu1 at isaacyu1.com" <isaacyu1 at isaacyu1.com>:
>
>Hi everyone,
>
>?????I now have 200+ SlackBuilds to maintain.
>Given my part-time job and my coursework,?I am going to have a harder time maintaining it all.
>
>This is the last week in which I will maintain and update SlackBuilds.
>
>I will also switch my email address (on SlackBuilds) to isaacyu at protonmail.com:
>https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
>
>I need to pay a small yearly subscription fee (to Gandi, the company) for the isaacyu1.com domain. However, the ProtonMail email service is free. Hence the email address change.
>
>My SlackBuilds are available at the following link:
>https://github.com/isaackwy/slackbuilds-15.0
>
>I plan on switching to Debian.
>Debian 12 (Bookworm) will be released in a few days, on June 10.
>
>- Isaac


I'd like to take 
 Tela-icon-theme

Johannes 

From belka at caraus.de  Mon Jun  5 04:47:53 2023
From: belka at caraus.de (Eugen Wissner)
Date: Mon, 5 Jun 2023 06:47:53 +0200
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <4520-647d1f80-d-6333f@58583900>
References: <4520-647d1f80-d-6333f@58583900>
Message-ID: <luve27zxthjtz6rryjirvqkrpc4vsxinsnqnup2zia22zo34in@xd234jxkvz7u>

I can take librsync and jitsi-meet-desktop.

On Mon, Jun 05, 2023 at 01:34:23AM +0200, isaacyu1 at isaacyu1.com wrote:
> 
> Hi everyone,
> 
> ?????I now have 200+ SlackBuilds to maintain.
> Given my part-time job and my coursework,?I am going to have a harder time maintaining it all.
> 
> This is the last week in which I will maintain and update SlackBuilds.
> 
> I will also switch my email address (on SlackBuilds) to isaacyu at protonmail.com:
> https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
> 
> I need to pay a small yearly subscription fee (to Gandi, the company) for the isaacyu1.com domain. However, the ProtonMail email service is free. Hence the email address change.
> 
> My SlackBuilds are available at the following link:
> https://github.com/isaackwy/slackbuilds-15.0
> 
> I plan on switching to Debian.
> Debian 12 (Bookworm) will be released in a few days, on June 10.
> 
> - Isaac

> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users 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 slackalaxy at gmail.com  Mon Jun  5 05:01:19 2023
From: slackalaxy at gmail.com (Petar Petrov)
Date: Mon, 5 Jun 2023 08:01:19 +0300
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <4520-647d1f80-d-6333f@58583900>
References: <4520-647d1f80-d-6333f@58583900>
Message-ID: <CAKXpWBcS8aD_-1aQoyMbHZcncp0XtWoZRh0V+TBfUJWTmnLuNQ@mail.gmail.com>

sorry to see you go!

I'd take rstudio-desktop

all the best,
-petar

On Mon, 5 Jun 2023 at 02:34, isaacyu1 at isaacyu1.com
<isaacyu1 at isaacyu1.com> wrote:
>
> Hi everyone,
>
> I now have 200+ SlackBuilds to maintain.
> Given my part-time job and my coursework, I am going to have a harder time maintaining it all.
>
> This is the last week in which I will maintain and update SlackBuilds.
>
> I will also switch my email address (on SlackBuilds) to isaacyu at protonmail.com:
> https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
>
> I need to pay a small yearly subscription fee (to Gandi, the company) for the isaacyu1.com domain. However, the ProtonMail email service is free. Hence the email address change.
>
> My SlackBuilds are available at the following link:
> https://github.com/isaackwy/slackbuilds-15.0
>
> I plan on switching to Debian.
> Debian 12 (Bookworm) will be released in a few days, on June 10.
>
> - Isaac _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users 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 jebrhansen+SBo at gmail.com  Mon Jun  5 05:22:52 2023
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sun, 4 Jun 2023 22:22:52 -0700
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <4520-647d1f80-d-6333f@58583900>
References: <4520-647d1f80-d-6333f@58583900>
Message-ID: <CANi9qSvDNzZ7t+NDPXVKRZnCmUBk+Sk-3qetoYNYWTdhdnAtRw@mail.gmail.com>

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

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

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

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

On Sun, Jun 4, 2023 at 4:34?PM isaacyu1 at isaacyu1.com <isaacyu1 at isaacyu1.com>
wrote:

> Hi everyone,
>
> ?????I now have 200+ SlackBuilds to maintain.
> Given my part-time job and my coursework, I am going to have a harder time
> maintaining it all.
>
> This is the last week in which I will maintain and update SlackBuilds.
>
> I will also switch my email address (on SlackBuilds) to
> isaacyu at protonmail.com:
> https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
>
> I need to pay a small yearly subscription fee (to Gandi, the company) for
> the isaacyu1.com domain. However, the ProtonMail email service is free.
> Hence the email address change.
>
> My SlackBuilds are available at the following link:
> https://github.com/isaackwy/slackbuilds-15.0
>
> I plan on switching to Debian.
> Debian 12 (Bookworm) will be released in a few days, on June 10.
>
> - Isaac _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users 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/20230604/42b6429e/attachment.htm>

From vlahavas at gmail.com  Mon Jun  5 08:20:14 2023
From: vlahavas at gmail.com (George Vlahavas)
Date: Mon, 5 Jun 2023 11:20:14 +0300
Subject: [Slackbuilds-users] mate-terminal
In-Reply-To: <3D6D2898-4037-44F6-BE39-4BEFC78C1ACA@schoepfer.info>
References: <ZFvCu8EtDOD4Fa0x@x360.localdomain>
 <eb3aae47-6525-4b68-8137-fc3cc6f7447f@app.fastmail.com>
 <ZGkfG85yNZHn704I@x360.localdomain> <ZHuuGPA938Wp4ULS@x360.localdomain>
 <067da2a2-d795-ba2f-7d25-48c217df765c@free.fr>
 <2bd9df2b-d589-42c4-9cd7-a00bb7d41240@slint.fr>
 <9d839ca9-75de-14a0-74c8-5aa58741bac6@free.fr>
 <9f22c13a-c1d5-c75a-1658-7f71c7278bd1@slint.fr>
 <9b06820b-de93-c590-4f40-b268b5c290c4@free.fr>
 <9e062d17-2ec8-2893-87b8-73f670e1284a@slint.fr>
 <3D6D2898-4037-44F6-BE39-4BEFC78C1ACA@schoepfer.info>
Message-ID: <CAJEH=oHdLUDAxBwYZTQB34130J0GWwJ2ze1fpMswoXc_UjnBSA@mail.gmail.com>

Hi,

mate-terminal doesn't really need mate-desktop. Only just some glib schemas
that are bundled with the mate-desktop package. To have mate-terminal
working without mate-desktop, just include the attached file in the
/usr/share/glib-2.0/schemas directory of the mate-terminal package.

George

On Sun, Jun 4, 2023 at 7:55?AM Franzen via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

>
>
> Am 4. Juni 2023 05:54:20 MESZ schrieb Didier Spaier <didier at slint.fr>:
> >Le 04/06/2023 ? 02:39, marav a ?crit :
> >> Le 04/06/2023 ? 01:00, Didier Spaier a ?crit :
> >>> Le 04/06/2023 ? 00:46, marav a ?crit :
> >>>> Le 04/06/2023 ? 00:42, Didier Spaier a ?crit :
> >>>>> Le 04/06/2023 ? 00:30, marav a ?crit :
> >>>>>> It needs mate-desktop
> >>>>> mate-desktop does provide the file
> >>>>> /usr/share/glib-2.0/schemas/org.mate.interface.gschema.xml but mate
> terminal
> >>>>> works without that, I just checked (I have upgraded all mate
> components to their
> >>>>> latest version for Slint a few days ago).
> >>>>> _______________________________________________
> >>>>>
> >>>> Not here
> >>>>
> >>>> plus, it is listed as running dependency by all others (arch, gentoo,
> fedora, ...)
> >>>>
> >>>> ex: for Fedora
> >>>>
> >>>> *# needed to get a gsettings schema, rhbz #908105
> >>>> Requires:      mate-desktop-libs
> >>>> Requires:      gsettings-desktop-schemas*
> >>> didier[~]$ mate-terminal --version
> >>> Terminal MATE 1.26.1
> >>> didier[~]$ ldd /usr/bin/mate-terminal|grep mate
> >>> didier[~]$
> >>>
> >>> As there are 88 sonames I refrained to post the full output of ldd ;)
> >>> _______________________________________________
> >>> SlackBuilds-users mailing list
> >>> SlackBuilds-users at slackbuilds.org
> >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >>> FAQ - https://slackbuilds.org/faq/
> >>>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=908105
> >>
> >> More than 10 years old bug report, but it seems that all others include
> >> mate-desktop as a requirement
> >>
> >> And, so far, mate-terminal is not working for Jim, as for me
> >
> >You made me curious.
> >
> >When I removed the mate-desktop package I was (and still am) in the LXQt
> desktop.
> >
> >So I typed "session-chooser mate", pressed Ctrl+Alt+F2, logged in then
> typed startx.
> >
> >Not surprisingly MATE didn't start. I redirect the standard error to
> /tmp/$(id
> >-nu)/startx.err when running startx and found there a lot of errors.
> >
> >So I ran (from LXQt still running) a small script which scans not found
> binaries
> >dependencies and the output (attached) indeed includes a lot of lines
> like this one:
> >libmate-desktop-2.so.17 => not found
> >although amazingly none while checking a binary file shipped in
> mate-terminal.
> >
> >So even if mate-terminal per se does not require mate-desktop, it of
> course
> >doesn't make sense to start a MATE desktop without a mate-desktop package
> ;)
> >
> >This not withstanding mate-terminal continue to work for me if started
> from
> >another graphical environment than MATE (at least mate-terminal version
> 1.26.1).
>
>
> Thanks for all the Info, i'll have a look in a few days when i'm home
> again. I did only check for build time requirements for mate-terminal, and
> using it in MATE, so i didn't notice.
>
> Johannes
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230605/3092fbcb/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: org.mate.interface.gschema.xml
Type: text/xml
Size: 10031 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230605/3092fbcb/attachment-0001.xml>

From arnaud.garcia-fernandez at laposte.net  Mon Jun  5 08:32:59 2023
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Mon, 5 Jun 2023 10:32:59 +0200
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <CANi9qSvDNzZ7t+NDPXVKRZnCmUBk+Sk-3qetoYNYWTdhdnAtRw@mail.gmail.com>
References: <4520-647d1f80-d-6333f@58583900>
 <CANi9qSvDNzZ7t+NDPXVKRZnCmUBk+Sk-3qetoYNYWTdhdnAtRw@mail.gmail.com>
Message-ID: <20230605103259.fe14f1e0f90d9415034f1695@laposte.net>

Sorry to see you go Isaac, and thanks for all the work !
Good luck with Debian, we'll welcome you back here whenever ;)

Now for the plunder.

Requirements of things I maintain are the following :
* The ones I'll take :
zeromq
cairocffi
python2-pyasn1
python3-pyasn1
python3-asn1crypto
* The ones already taken by Jeremy :
iniconfig
typing-extensions
python3-pluggy
python3-py
python3-pytest
python3-pytest-runner


Furthemore I use those ones, and I'm ok maintaining them :
office/focuswriter
python/python3-black
system/winetricks

Cheers,

	- Yth.

> Thanks for all your work, Isaac! Best of luck to your future.
> 
> I can take the following as they're all dependencies of other packages I'm
> maintaining:
> 
> cppy
> iniconfig
> ipython
> pickleshare
> python3-beniget
> python3-deprecation
> python3-executing
> python3-gast
> python3-iniconfig
> python3-jedi
> python3-joblib
> python3-kiwisolver
> python3-matplotlib-inline
> python3-pandas
> python3-pluggy
> python3-pure_eval
> python3-py
> python3-pytest
> python3-pytest-runner
> python3-scipy
> python3-stack_data
> python3-threadpoolctl
> python3-tornado
> scikit-learn
> traitlets
> typing-extensions
> xsimd
> 
> I can submit a pull request later this week to switch maintainership over.
> Jeremy
> 
> On Sun, Jun 4, 2023 at 4:34?PM isaacyu1 at isaacyu1.com <isaacyu1 at isaacyu1.com>
> wrote:
> 
> > Hi everyone,
> >
> > ?????I now have 200+ SlackBuilds to maintain.
> > Given my part-time job and my coursework, I am going to have a harder time
> > maintaining it all.
> >
> > This is the last week in which I will maintain and update SlackBuilds.
> >
> > I will also switch my email address (on SlackBuilds) to
> > isaacyu at protonmail.com:
> > https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
> >
> > I need to pay a small yearly subscription fee (to Gandi, the company) for
> > the isaacyu1.com domain. However, the ProtonMail email service is free.
> > Hence the email address change.
> >
> > My SlackBuilds are available at the following link:
> > https://github.com/isaackwy/slackbuilds-15.0
> >
> > I plan on switching to Debian.
> > Debian 12 (Bookworm) will be released in a few days, on June 10.
> >
> > - Isaac _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users 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 dev at iotib.net  Mon Jun  5 11:12:26 2023
From: dev at iotib.net (Charadon)
Date: Mon, 5 Jun 2023 11:12:26 +0000
Subject: [Slackbuilds-users] Abandoning Epiphany SlackBuild
In-Reply-To: <CAJOKJPbtvwYGbbQH4KhkWR8apjo+Ge_g6_fu41eThutubBWcxQ@mail.gmail.com>
References: <5c6b7fc1-8265-fd44-8d78-b919d28e341a@iotib.net>
 <6BC7075A-2CC2-460E-BFDB-E42DA8D171FD@edison.tech>
 <CAJOKJPbtvwYGbbQH4KhkWR8apjo+Ge_g6_fu41eThutubBWcxQ@mail.gmail.com>
Message-ID: <75849a7d-53b1-8523-f40a-c860aed386d7@iotib.net>

On 6/5/23 03:01, Bob Funk wrote:
> I can take over maintaining epiphany and add it to the collection of 
> gnome core builds I've been building.
> 
> I'll look it over and submit an update to take over maintenance later 
> this week.
> 
> Bob
> 
> On Sun, Jun 4, 2023, 2:10 PM J via SlackBuilds-users 
> <slackbuilds-users at slackbuilds.org 
> <mailto:slackbuilds-users at slackbuilds.org>> wrote:
> 
>     I actually do use it as epiphany is much lighter on aarch64
>     Slackware vs Firefox but I generally keep my own scripts since
>     aarch64 isn?t targeted by most of SBo as of yet.
> 
>     I?m assuming 0xBOB may want this one to go with the rest of gnome,
>     but if not, I?ll take it.
> 
>     ? Jay Lanagan
> 
> 
>>     On Jun 4, 2023 at 10:58 AM, <Charadon via SlackBuilds-users
>>     <mailto:slackbuilds-users at slackbuilds.org>> wrote:
>>
>>     I don't have any interest in maintaining Epiphany anymore as I don't use
>>     it, and upstream has been putting more emphasis on using the Flatpak
>>     version. If anyone wants it, you can have it =)
>>     _______________________________________________
>>     SlackBuilds-users mailing list
>>     SlackBuilds-users at slackbuilds.org  <mailto:SlackBuilds-users at slackbuilds.org>
>>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users  <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>>     Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/  <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>>     FAQ -https://slackbuilds.org/faq/  <https://slackbuilds.org/faq/>
>>
>>
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>     Archives -
>     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>     FAQ - https://slackbuilds.org/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/
> 

You *should* be able to update it now, since I think libportal's 
slackbuild finally got an update. That was the main reason it's been 
stuck on 43.0 for so long. =)

From zsd+slackbuilds at jdvb.ca  Mon Jun  5 12:41:42 2023
From: zsd+slackbuilds at jdvb.ca (Jim)
Date: Mon, 5 Jun 2023 09:41:42 -0300
Subject: [Slackbuilds-users] mate-terminal
In-Reply-To: <CAJEH=oHdLUDAxBwYZTQB34130J0GWwJ2ze1fpMswoXc_UjnBSA@mail.gmail.com>
References: <ZGkfG85yNZHn704I@x360.localdomain>
 <ZHuuGPA938Wp4ULS@x360.localdomain>
 <067da2a2-d795-ba2f-7d25-48c217df765c@free.fr>
 <2bd9df2b-d589-42c4-9cd7-a00bb7d41240@slint.fr>
 <9d839ca9-75de-14a0-74c8-5aa58741bac6@free.fr>
 <9f22c13a-c1d5-c75a-1658-7f71c7278bd1@slint.fr>
 <9b06820b-de93-c590-4f40-b268b5c290c4@free.fr>
 <9e062d17-2ec8-2893-87b8-73f670e1284a@slint.fr>
 <3D6D2898-4037-44F6-BE39-4BEFC78C1ACA@schoepfer.info>
 <CAJEH=oHdLUDAxBwYZTQB34130J0GWwJ2ze1fpMswoXc_UjnBSA@mail.gmail.com>
Message-ID: <ZH3YBv2uIuMyLdk3@x360.localdomain>

Hi George

On Mon, Jun  5, 2023 at 11:20 (+0300), George Vlahavas wrote:

> mate-terminal doesn't really need mate-desktop. Only just some glib schemas
> that are bundled with the mate-desktop package. To have mate-terminal
> working without mate-desktop, just include the attached file in the
> /usr/share/glib-2.0/schemas directory of the mate-terminal package.

Thanks very much for that.  My original question produced a lot more
discussion (and confusion?) than I originally imagined,

                                Jim

> On Sun, Jun 4, 2023 at 7:55?AM Franzen via SlackBuilds-users <
> slackbuilds-users at slackbuilds.org> wrote:



>> Am 4. Juni 2023 05:54:20 MESZ schrieb Didier Spaier <didier at slint.fr>:
>>>Le 04/06/2023 ? 02:39, marav a ?crit :
>>>> Le 04/06/2023 ? 01:00, Didier Spaier a ?crit :
>>>>> Le 04/06/2023 ? 00:46, marav a ?crit :
>>>>>> Le 04/06/2023 ? 00:42, Didier Spaier a ?crit :
>>>>>>> Le 04/06/2023 ? 00:30, marav a ?crit :
>>>>>>>> It needs mate-desktop
>>>>>>> mate-desktop does provide the file
>>>>>>> /usr/share/glib-2.0/schemas/org.mate.interface.gschema.xml but mate
>> terminal
>>>>>>> works without that, I just checked (I have upgraded all mate
>> components to their
>>>>>>> latest version for Slint a few days ago).
>>>>>>> _______________________________________________

>>>>>> Not here

>>>>>> plus, it is listed as running dependency by all others (arch, gentoo,
>> fedora, ...)

>>>>>> ex: for Fedora

>>>>>> *# needed to get a gsettings schema, rhbz #908105
>>>>>> Requires:      mate-desktop-libs
>>>>>> Requires:      gsettings-desktop-schemas*
>>>>> didier[~]$ mate-terminal --version
>>>>> Terminal MATE 1.26.1
>>>>> didier[~]$ ldd /usr/bin/mate-terminal|grep mate
>>>>> didier[~]$

>>>>> As there are 88 sonames I refrained to post the full output of ldd ;)
>>>>> _______________________________________________
>>>>> SlackBuilds-users mailing list
>>>>> SlackBuilds-users at slackbuilds.org
>>>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>>>> FAQ - https://slackbuilds.org/faq/

>>>> https://bugzilla.redhat.com/show_bug.cgi?id=908105

>>>> More than 10 years old bug report, but it seems that all others include
>>>> mate-desktop as a requirement

>>>> And, so far, mate-terminal is not working for Jim, as for me

>>>You made me curious.

>>>When I removed the mate-desktop package I was (and still am) in the LXQt
>> desktop.

>>>So I typed "session-chooser mate", pressed Ctrl+Alt+F2, logged in then
>> typed startx.

>>>Not surprisingly MATE didn't start. I redirect the standard error to
>> /tmp/$(id
>>>-nu)/startx.err when running startx and found there a lot of errors.

>>>So I ran (from LXQt still running) a small script which scans not found
>> binaries
>>>dependencies and the output (attached) indeed includes a lot of lines
>> like this one:
>>>libmate-desktop-2.so.17 => not found
>>>although amazingly none while checking a binary file shipped in
>> mate-terminal.

>>>So even if mate-terminal per se does not require mate-desktop, it of
>> course
>>>doesn't make sense to start a MATE desktop without a mate-desktop package
>> ;)

>>>This not withstanding mate-terminal continue to work for me if started
>> from
>>>another graphical environment than MATE (at least mate-terminal version
>> 1.26.1).


>> Thanks for all the Info, i'll have a look in a few days when i'm home
>> again. I did only check for build time requirements for mate-terminal, and
>> using it in MATE, so i didn't notice.

>> Johannes
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/



> <schemalist gettext-domain="mate-desktop">
>   <schema id="org.mate.interface" path="/org/mate/desktop/interface/">
>     <key name="accessibility" type="b">
>       <default>false</default>
>       <summary>Enable Accessibility</summary>
>       <description>Whether Applications should have accessibility support.</description>
>     </key>
>     <key name="enable-animations" type="b">
>       <default>true</default>
>       <summary>Enable Animations</summary>
>       <description>Whether animations should be displayed. Note: This is a global key, it changes the behaviour of the window manager, the panel etc.</description>
>     </key>
>     <key name="menus-have-tearoff" type="b">
>       <default>false</default>
>       <summary>Menus Have Tearoff</summary>
>       <description>Whether menus should have a tearoff.</description>
>     </key>
>     <key name="toolbar-style" type="s">
>       <default>'both-horiz'</default>
>       <summary>Toolbar Style</summary>
>       <description>Toolbar Style. Valid values are "both", "both-horiz", "icons", and "text".</description>
>     </key>
>     <key name="menus-have-icons" type="b">
>       <default>true</default>
>       <summary>Menus Have Icons</summary>
>       <description>Whether menus may display an icon next to a menu entry.</description>
>     </key>
>     <key name="buttons-have-icons" type="b">
>       <default>true</default>
>       <summary>Buttons Have Icons</summary>
>       <description>Whether buttons may display an icon in addition to the button text.</description>
>     </key>
>     <key name="menubar-detachable" type="b">
>       <default>false</default>
>       <summary>Menubar Detachable</summary>
>       <description>Whether the user can detach menubars and move them around.</description>
>     </key>
>     <key name="toolbar-detachable" type="b">
>       <default>false</default>
>       <summary>Toolbar Detachable</summary>
>       <description>Whether the user can detach toolbars and move them around.</description>
>     </key>
>     <key name="toolbar-icons-size" type="s">
>       <default>'large-toolbar'</default>
>       <summary>Toolbar Icon Size</summary>
>       <description>Size of icons in toolbars, either "small-toolbar" or "large-toolbar".</description>
>     </key>
>     <key name="cursor-blink" type="b">
>       <default>true</default>
>       <summary>Cursor Blink</summary>
>       <description>Whether the cursor should blink.</description>
>     </key>
>     <key name="cursor-blink-time" type="i">
>       <default>1200</default>
>       <summary>Cursor Blink Time</summary>
>       <description>Length of the cursor blink cycle, in milliseconds.</description>
>     </key>
>     <key name="icon-theme" type="s">
>       <default>'menta'</default>
>       <summary>Icon Theme</summary>
>       <description>Icon theme to use for the panel, Caja etc.</description>
>     </key>
>     <key name="gtk-theme" type="s">
>       <default>'Menta'</default>
>       <summary>Gtk+ Theme</summary>
>       <description>Basename of the default theme used by gtk+.</description>
>     </key>
>     <key name="gtk-key-theme" type="s">
>       <default>'Default'</default>
>       <summary>Gtk+ Theme</summary>
>       <description>Basename of the default theme used by gtk+.</description>
>     </key>
>     <key name="gtk-color-scheme" type="s">
>       <default>''</default>
>       <summary>List of symbolic names and color equivalents</summary>
>       <description>A '\n' separated list of "name:color" as defined by the 'gtk-color-scheme' setting</description>
>     </key>
>     <key name="font-name" type="s">
>       <default>'Sans 10'</default>
>       <summary>Default font</summary>
>       <description>Name of the default font used by gtk+.</description>
>     </key>
>     <key name="gtk-im-preedit-style" type="s">
>       <default>'callback'</default>
>       <summary>GTK IM Preedit Style</summary>
>       <description>Name of the GTK+ input method Preedit Style used by gtk+.</description>
>     </key>
>     <key name="gtk-im-status-style" type="s">
>       <default>'callback'</default>
>       <summary>GTK IM Status Style</summary>
>       <description>Name of the GTK+ input method Status Style used by gtk+.</description>
>     </key>
>     <key name="gtk-im-module" type="s">
>       <default>''</default>
>       <summary>GTK IM Module</summary>
>       <description>Name of the input method module used by GTK+.</description>
>     </key>
>     <key name="gtk-dialogs-use-header" type="b">
>       <default>false</default>
>       <summary>Use GTK3 header bar</summary>
>       <description>Whether builtin GTK+ dialogs such as the file chooser, the color chooser or the font chooser will use a header bar at the top to show action widgets, or an action area at the bottom. This setting does not affect custom dialogs using GtkDialog directly, or message dialogs.</description>
>     </key>
>     <key name="gtk-overlay-scrolling" type="b">
>       <default>false</default>
>       <summary>Use GTK3 overlay scrolling</summary>
>       <description>Whether built-in GTK+ scrolled windows will use overlay scrolling. Overlay scrolling hides and reduces the size of the scrollbar until it gets focus.</description>
>     </key>
>     <key name="gtk-enable-animations" type="b">
>       <default>true</default>
>       <summary>Enable Gtk toolkit-wide animations</summary>
>       <description>Whether to enable toolkit-wide animations.</description>
>     </key>
>     <key name="document-font-name" type="s">
>       <default>'Sans 10'</default>
>       <summary>Document font</summary>
>       <description>Name of the default font used for reading documents.</description>
>     </key>
>     <key name="monospace-font-name" type="s">
>       <default>'Monospace 10'</default>
>       <summary>Monospace font</summary>
>       <description>Name of a monospaced (fixed-width) font for use in locations like terminals.</description>
>     </key>
>     <key name="use-custom-font" type="b">
>       <default>false</default>
>       <summary>Use Custom Font</summary>
>       <description>Whether to use a custom font in gtk+ applications.</description>
>     </key>
>     <key name="status-bar-meter-on-right" type="b">
>       <default>false</default>
>       <summary>Status Bar on Right</summary>
>       <description>Whether to display a status bar meter on the right.</description>
>     </key>
>     <key name="file-chooser-backend" type="s">
>       <default>'gio'</default>
>       <summary>Module for GtkFileChooser</summary>
>       <description>Module to use as the filesystem model for the GtkFileChooser widget.  Possible values are "gio" and "gtk+".</description>
>     </key>
>     <key name="menubar-accel" type="s">
>       <default>'F10'</default>
>       <summary>Menubar accelerator</summary>
>       <description>Keyboard shortcut to open the menu bars.</description>
>     </key>
>     <key name="show-input-method-menu" type="b">
>       <default>true</default>
>       <summary>Show the 'Input Methods' menu</summary>
>       <description>Whether the context menus of entries and text views  should offer to change the input method.</description>
>     </key>
>     <key name="show-unicode-menu" type="b">
>       <default>true</default>
>       <summary>Show the 'Unicode Control Character' menu</summary>
>       <description>Whether the context menus of entries and text views  should offer to insert control characters.</description>
>     </key>
>     <key name="gtk-decoration-layout" type="s">
>       <default>'menu:minimize,maximize,close'</default>
>       <summary>Titlebar layout of GTK3 client-side decorated windows</summary>
>       <description>This setting determines which buttons should be put in the titlebar of client-side decorated windows, and whether they should be placed at the left of right. See https://developer.gnome.org/gtk3/stable/GtkSettings.html#GtkSettings--gtk-decoration-layout.</description>
>     </key>
>     <key name="gtk-shell-shows-app-menu" type="b">
>       <default>false</default>
>       <summary>Use a global menubar for displaying application menus</summary>
>       <description> This setting determines where application menu will be displayed - in a window or on a panel with MenuModel protocol. See https://developer.gnome.org/gtk3/stable/GtkSettings.html#GtkSettings--gtk-shell-shows-app-menu.</description>
>     </key>
>     <key name="gtk-shell-shows-menubar" type="b">
>       <default>false</default>
>       <summary>Use a global menubar for displaying window menubars</summary>
>       <description> This setting determines where window menubars will be displayed - in a window or on a panel with MenuModel protocol. See https://developer.gnome.org/gtk3/stable/GtkSettings.html#GtkSettings--gtk-shell-shows-menubar.</description>
>     </key>
>     <key name="automatic-mnemonics" type="b">
>       <default>true</default>
>       <summary>Only show mnemonics on when the Alt key is pressed</summary>
>       <description>Whether mnemonics should be automatically shown and hidden when the user presses the Alt key.</description>
>     </key>
>     <key name="window-scaling-factor" type="i">
>       <default>0</default>
>       <range min="0" max="2"/>
>       <summary>Window Scaling Factor</summary>
>       <description>This controls the GTK scale factor that maps from window coordinates to the actual device pixels. On traditional systems this is 1, but on very high density displays (e.g. HiDPI, Retina) this can be a higher value (often 2). Set to 0 to auto-detect.</description>
>     </key>
>     <key name="window-scaling-factor-qt-sync" type="b">
>       <default>true</default>
>       <summary>Scaling Factor for QT appllications</summary>
>       <description>This setting determines whether MATE controls the scale factor for QT applications. Enable to synchronize with the GTK scale factor when initializing the session, disable to control this value elsewhere. Requires restarting your session.</description>
>     </key>
>     <key name="gtk-enable-primary-paste" type="b">
>       <default>true</default>
>       <summary>Enable the primary paste selection</summary>
>       <description>
> If true, gtk+ uses the primary paste selection, usually triggered by a middle mouse button click.
>       </description>
>     </key>
>   </schema>
> </schemalist>

> _______________________________________________
> 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 slack at giand.it  Mon Jun  5 20:19:41 2023
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=)
Date: Mon, 5 Jun 2023 22:19:41 +0200
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <4520-647d1f80-d-6333f@58583900>
References: <4520-647d1f80-d-6333f@58583900>
Message-ID: <4ffa33df-cc34-b75e-0e0d-cfb7e12c05fb@giand.it>

Il 05/06/23 01:34, isaacyu1 at isaacyu1.com ha scritto:
> Hi everyone,
>
> ?????I now have 200+ SlackBuilds to maintain.
> Given my part-time job and my coursework,?I am going to have a harder 
> time maintaining it all.
>
> This is the last week in which I will maintain and update SlackBuilds.
>
> I will also switch my email address (on SlackBuilds) to 
> isaacyu at protonmail.com:
> https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
>
> I need to pay a small yearly subscription fee (to Gandi, the company) 
> for the isaacyu1.com domain. However, the ProtonMail email service is 
> free. Hence the email address change.
>
> My SlackBuilds are available at the following link:
> https://github.com/isaackwy/slackbuilds-15.0
>
> I plan on switching to Debian.
> Debian 12 (Bookworm) will be released in a few days, on June 10.

Thank for your great work Isaac, I use several your slackbuilds!

If anyone is interested I'll take libspatialindex for now

There are also various slackbuilds for python packages that I use, I can 
take a part of them, but I have to see what are already taken and what I 
can take. Next time...


>
> - Isaac
>
> _______________________________________________
> 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/
>
-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it

Slackware Linux... because it works!
*********************************************************


From fourtysixandtwo at sliderr.net  Mon Jun  5 23:11:00 2023
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Mon, 5 Jun 2023 17:11:00 -0600
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <4520-647d1f80-d-6333f@58583900>
References: <4520-647d1f80-d-6333f@58583900>
Message-ID: <CAAZ8Hai6ap1BAnT0rFQXNWtbh5X1msEkg_-_2SVVy-jARkT_3g@mail.gmail.com>

Thanks for the work you've put in Isaac.

At first glance I think anything I might have taken over is already spoken
for.

Cheers

On Sun, Jun 4, 2023 at 5:34?PM isaacyu1 at isaacyu1.com <isaacyu1 at isaacyu1.com>
wrote:

> Hi everyone,
>
> ?????I now have 200+ SlackBuilds to maintain.
> Given my part-time job and my coursework, I am going to have a harder time
> maintaining it all.
>
> This is the last week in which I will maintain and update SlackBuilds.
>
> I will also switch my email address (on SlackBuilds) to
> isaacyu at protonmail.com:
> https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
>
> I need to pay a small yearly subscription fee (to Gandi, the company) for
> the isaacyu1.com domain. However, the ProtonMail email service is free.
> Hence the email address change.
>
> My SlackBuilds are available at the following link:
> https://github.com/isaackwy/slackbuilds-15.0
>
> I plan on switching to Debian.
> Debian 12 (Bookworm) will be released in a few days, on June 10.
>
> - Isaac _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users 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/20230605/fa510905/attachment.htm>

From j at lngn.net  Tue Jun  6 05:42:49 2023
From: j at lngn.net (Jay Lanagan)
Date: Tue, 06 Jun 2023 01:42:49 -0400
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <4520-647d1f80-d-6333f@58583900>
References: <4520-647d1f80-d-6333f@58583900>
Message-ID: <b8fc2a6e6c4b0c6b7dbf1500373d1fb032277973.camel@lngn.net>

There is actually quite a few of your slackbuilds that I depend on for
the nwg-shell project. I?d need to make a list but I would happily take
them over. I couldn?t possibly take over all 200+ having never used
many of them personally. But here?s ones that I?m interested in taking:

Python3-aiohttp
Python3-aiosignal
Python3-async-timeout
Python3-frozenlist
python3-multidict
python3-pluggy
python3-pytest
Python3-yarl

If any of these have been previously taken and I missed it, then of
course I'll concede on taking them. But any not claimed (I think I
removed them all from my list) I'd like.

Sorry to lose you to Debian, though truth be told, my main box is
running sid as of late. Bookworm is going to be an excellent Linux
release. Debian has a few things right over the slack world and the
amount of available software is second to none. I totally understand
the need for one to move on and free up the time spent doing such
things.?

? Jay Lanagan


> On Jun 4, 2023 at 7:34 PM, <Isaacyu1> wrote:
> 
> Hi everyone,
> 
> ?????I now have 200+ SlackBuilds to maintain.
> Given my part-time job and my coursework,?I am going to have a harder
> time maintaining it all.
> 
> This is the last week in which I will maintain and update
> SlackBuilds.
> 
> I will also switch my email address (on SlackBuilds) to
> isaacyu at protonmail.com:
> https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
> 
> I need to pay a small yearly subscription fee (to Gandi, the company)
> for the isaacyu1.com domain. However, the ProtonMail email service is
> free. Hence the email address change.
> 
> My SlackBuilds are available at the following link:
> https://github.com/isaackwy/slackbuilds-15.0
> 
> I plan on switching to Debian.
> Debian 12 (Bookworm) will be released in a few days, on June 10.
> 
> - Isaac _______________________________________________ SlackBuilds-
> users mailing list SlackBuilds-users 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 slack at giand.it  Tue Jun  6 16:24:57 2023
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=)
Date: Tue, 6 Jun 2023 18:24:57 +0200
Subject: [Slackbuilds-users] pdal fails to compile with gdal 3.7
In-Reply-To: <CAK09-vmz_KXB-iYGPy1K71KHpAH-fEHRReQ8bGcH4NB1hs75Hw@mail.gmail.com>
References: <CAK09-vmz_KXB-iYGPy1K71KHpAH-fEHRReQ8bGcH4NB1hs75Hw@mail.gmail.com>
Message-ID: <815d323e-a4dd-5e98-7761-7bb686760f93@giand.it>


Il 04/06/23 02:57, Greg Tourte ha scritto:
> Hi,
>
> I would like to apologise as somehow I failed to test pdal when I 
> updated gdal to version 3.7 this week. I thought I had, but I made a 
> mistake in the testing process and pdal slipped through the crack.
>
> anyway, the pdal version (2.5.3) currently in slackbuild (and the 
> previous one, i.e. 2.2.0) does not compile with gdal 3.7 (see 
> https://github.com/PDAL/PDAL/pull/4030).
>
> As the ticket mentions, it was fixed in version 2.5.4. I have tested 
> it by simply changing the version in the slackbuild (md5sum = 
> 3e559237458b763fffaa98648e906bdc).
>
> I am going through the gdal dependees again to make sure I didn't miss 
> any others.
>
> Cheers
>
> Greg

Hi Greg, I missed your mail

I recently took pdal. I have not upgraded gdal still since last update. 
I have to check just now, if pdal has been released with a new version 
I'll update it.

Thanks for the report

-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it

Slackware Linux... because it works!
*********************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230606/0a3c7551/attachment.htm>

From slack at giand.it  Tue Jun  6 16:52:49 2023
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=)
Date: Tue, 6 Jun 2023 18:52:49 +0200
Subject: [Slackbuilds-users] pdal fails to compile with gdal 3.7
In-Reply-To: <815d323e-a4dd-5e98-7761-7bb686760f93@giand.it>
References: <CAK09-vmz_KXB-iYGPy1K71KHpAH-fEHRReQ8bGcH4NB1hs75Hw@mail.gmail.com>
 <815d323e-a4dd-5e98-7761-7bb686760f93@giand.it>
Message-ID: <a8a2e1ac-53e0-2177-0945-ee5b5051410a@giand.it>

Il 06/06/23 18:24, Giancarlo Dess? ha scritto:
>
>
> Il 04/06/23 02:57, Greg Tourte ha scritto:
>> Hi,
>>
>> I would like to apologise as somehow I failed to test pdal when I 
>> updated gdal to version 3.7 this week. I thought I had, but I made a 
>> mistake in the testing process and pdal slipped through the crack.
>>
>> anyway, the pdal version (2.5.3) currently in slackbuild (and the 
>> previous one, i.e. 2.2.0) does not compile with gdal 3.7 (see 
>> https://github.com/PDAL/PDAL/pull/4030).
>>
>> As the ticket mentions, it was fixed in version 2.5.4. I have tested 
>> it by simply changing the version in the slackbuild (md5sum = 
>> 3e559237458b763fffaa98648e906bdc).
>>
>> I am going through the gdal dependees again to make sure I didn't 
>> miss any others.
>>
>> Cheers
>>
>> Greg
>
> Hi Greg, I missed your mail
>
> I recently took pdal. I have not upgraded gdal still since last 
> update. I have to check just now, if pdal has been released with a new 
> version I'll update it.
>
> Thanks for the report
>
I've updated gdal to 3.7 and slackbuild for pdal to 2.5.4. I confirm, 
the build with the new version solves the issue and works fine against 
gdal 3.7

I tested just now in Slackware64 current, when I have tested also in 
Slackware 15.0 (32/64 bit) I'll submit the new version. It should be 
available in SBo next week, but if you don't want to wait you can use 
the current slackbuild script, it works: you have to change only the 
version of the package, no any other

Greetings


-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it

Slackware Linux... because it works!
*********************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230606/eeb583f6/attachment-0001.htm>

From slack at giand.it  Tue Jun  6 17:20:24 2023
From: slack at giand.it (=?UTF-8?Q?Giancarlo_Dess=c3=ac?=)
Date: Tue, 6 Jun 2023 19:20:24 +0200
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <4ffa33df-cc34-b75e-0e0d-cfb7e12c05fb@giand.it>
References: <4520-647d1f80-d-6333f@58583900>
 <4ffa33df-cc34-b75e-0e0d-cfb7e12c05fb@giand.it>
Message-ID: <342fb84b-e98a-0961-44d2-e8938e867666@giand.it>

Il 05/06/23 22:19, Giancarlo Dess? ha scritto:
> Il 05/06/23 01:34, isaacyu1 at isaacyu1.com ha scritto:
>> [cut]
>
> Thank for your great work Isaac, I use several your slackbuilds!
>
> If anyone is interested I'll take libspatialindex for now
>
> There are also various slackbuilds for python packages that I use, I 
> can take a part of them, but I have to see what are already taken and 
> what I can take. Next time...
>
I saw that the following slackbuilds are not taken by others still, so I 
can take them:

- BeautifulSoup4
- python2-BeautifulSoup4
- python2-soupsieve
- python3-soupsieve

and libspatialindex, already mentioned


-- 
*********************************************************
Giancarlo Dess?
https://www.giand.it

Slackware Linux... because it works!
*********************************************************


From julian at dotcore.co.il  Wed Jun  7 08:42:46 2023
From: julian at dotcore.co.il (Julian Grinblat)
Date: Wed, 7 Jun 2023 17:42:46 +0900
Subject: [Slackbuilds-users] xmlsec was reverted to 1.2.27
Message-ID: <CADnMSPLM4K6pcwbWP7eUqmrgVNi-mpxT0pudWZtY4-kBMnnDHg@mail.gmail.com>

For some reason, in 27504d39f215cb7a8a74b6a7edab9b0fd6768914 xmlsec was
reverted to 1.2.27. c5603f5d4cb83f82265772cb8b9f1ee0e521d398 upgraded to
1.3.0, and the changelog lists it as being upgraded to 1.3.0. Just reporting
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230607/2c026a41/attachment.htm>

From urchlay at slackware.uk  Wed Jun  7 09:11:31 2023
From: urchlay at slackware.uk (B. Watson)
Date: Wed, 7 Jun 2023 05:11:31 -0400 (EDT)
Subject: [Slackbuilds-users] xmlsec was reverted to 1.2.27
In-Reply-To: <CADnMSPLM4K6pcwbWP7eUqmrgVNi-mpxT0pudWZtY4-kBMnnDHg@mail.gmail.com>
References: <CADnMSPLM4K6pcwbWP7eUqmrgVNi-mpxT0pudWZtY4-kBMnnDHg@mail.gmail.com>
Message-ID: <3dc7ac6b-59b7-d6fc-433-1ae4766ed0b6@slackware.uk>



On Wed, 7 Jun 2023, Julian Grinblat wrote:

> For some reason, in 27504d39f215cb7a8a74b6a7edab9b0fd6768914 xmlsec was reverted to 1.2.27. c5603f5d4cb83f82265772cb8b9f1ee0e521d398 upgraded to
> 1.3.0, and the changelog lists it as being upgraded to 1.3.0. Just reporting

It was reverted to 1.2.37 because oath-toolkit won't build with 1.3.0
(and consequently glewlwyd and pass-otp won't build as they depend on
oath-toolkit).

The git log message for is incorrect (typo'ed) and should read
"Downgraded to 1.2.37" or such.

From jebrhansen+SBo at gmail.com  Wed Jun  7 14:07:27 2023
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Wed, 7 Jun 2023 07:07:27 -0700
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <b8fc2a6e6c4b0c6b7dbf1500373d1fb032277973.camel@lngn.net>
References: <4520-647d1f80-d-6333f@58583900>
 <b8fc2a6e6c4b0c6b7dbf1500373d1fb032277973.camel@lngn.net>
Message-ID: <CANi9qSsPm8StzvsAvxAadvY+Hd9hyquZtnDoiVZEQH4_9WCUDg@mail.gmail.com>

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

Jeremy

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

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

From j at lngn.net  Wed Jun  7 14:17:44 2023
From: j at lngn.net (J)
Date: Wed, 7 Jun 2023 10:17:44 -0400
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <CANi9qSsPm8StzvsAvxAadvY+Hd9hyquZtnDoiVZEQH4_9WCUDg@mail.gmail.com>
References: <4520-647d1f80-d-6333f@58583900>
 <b8fc2a6e6c4b0c6b7dbf1500373d1fb032277973.camel@lngn.net>
 <CANi9qSsPm8StzvsAvxAadvY+Hd9hyquZtnDoiVZEQH4_9WCUDg@mail.gmail.com>
Message-ID: <8FB80F10-B8D3-4F60-A46F-864119260F63@edison.tech>

      
  

 Not a problem, as long as someone is taking care of them going forward, that?s all I?m concerned about as well. I must have missed your mail in the shuffle, but if you have dibs on them, by all means? ;)
  

  
I do believe issac stated he?d be pushing one last update this week though for things. If that is the case, my plan was to hold off until to following week if the dust has settled on who has what before I submit anything myself.   
  

  
I don?t want to create a too many chefs in the kitchen scenario, so I figured I?d hold back (I?ve plenty of my own updates to process yet) but you are more than welcome to pluggy  &  pytest.   
  
  
  
? Jay Lanagan
  
  
  

  
  
>   
> On Jun 7, 2023 at 10:07 AM,  <Jeremy Hansen (mailto:jebrhansen+sbo at gmail.com)>  wrote:
>   
>   
>   
>   
> I had already claimed python3-pluggy and python3-pytest, but that was just because they were dependencies of a few of my scripts and I didn't want them abandoned. However, I'm in no way tied to them and if you'd like them, I'm fine with you taking them. I haven't submitted a pull request to update the maintainer info yet (probably do that tomorrow), so no harm done either way.
>   
>
>   
> Jeremy
>   
>   
>   
> On Mon, Jun 5, 2023, 10:43 PM Jay Lanagan via SlackBuilds-users  <slackbuilds-users at slackbuilds.org (mailto:slackbuilds-users at slackbuilds.org)>  wrote:
>   
> >  There is actually quite a few of your slackbuilds that I depend on for
> >  the nwg-shell project. I?d need to make a list but I would happily take
> >  them over. I couldn?t possibly take over all 200+ having never used
> >  many of them personally. But here?s ones that I?m interested in taking:
> >   
> >  Python3-aiohttp
> >  Python3-aiosignal
> >  Python3-async-timeout
> >  Python3-frozenlist
> >  python3-multidict
> >  python3-pluggy
> >  python3-pytest
> >  Python3-yarl
> >   
> >  If any of these have been previously taken and I missed it, then of
> >  course I'll concede on taking them. But any not claimed (I think I
> >  removed them all from my list) I'd like.
> >   
> >  Sorry to lose you to Debian, though truth be told, my main box is
> >  running sid as of late. Bookworm is going to be an excellent Linux
> >  release. Debian has a few things right over the slack world and the
> >  amount of available software is second to none. I totally understand
> >  the need for one to move on and free up the time spent doing such
> >  things.   
> >   
> >  ? Jay Lanagan
> >   
> >   
> >   >  On Jun 4, 2023 at 7:34 PM,  <Isaacyu1>  wrote:
> >   >
> >   >  Hi everyone,
> >   >
> >   >  ?????I now have 200+ SlackBuilds to maintain.
> >   >  Given my part-time job and my coursework,   I am going to have a harder
> >   >  time maintaining it all.
> >   >
> >   >  This is the last week in which I will maintain and update
> >   >  SlackBuilds.
> >   >
> >   >  I will also switch my email address (on SlackBuilds) to
> >   >   isaacyu at protonmail.com (mailto:isaacyu at protonmail.com):
> >   >   https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
> >   >
> >   >  I need to pay a small yearly subscription fee (to Gandi, the company)
> >   >  for the  isaacyu1.com (http://isaacyu1.com)  domain. However, the ProtonMail email service is
> >   >  free. Hence the email address change.
> >   >
> >   >  My SlackBuilds are available at the following link:
> >   >   https://github.com/isaackwy/slackbuilds-15.0
> >   >
> >   >  I plan on switching to Debian.
> >   >  Debian 12 (Bookworm) will be released in a few days, on June 10.
> >   >
> >   >  - Isaac _______________________________________________ SlackBuilds-
> >   >  users mailing list  SlackBuilds-users at slackbuilds.org (mailto: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 (mailto: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/20230607/ba08493f/attachment-0001.htm>

From willysr at slackbuilds.org  Wed Jun  7 18:13:00 2023
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 8 Jun 2023 01:13:00 +0700
Subject: [Slackbuilds-users] xmlsec was reverted to 1.2.27
In-Reply-To: <CADnMSPLM4K6pcwbWP7eUqmrgVNi-mpxT0pudWZtY4-kBMnnDHg@mail.gmail.com>
References: <CADnMSPLM4K6pcwbWP7eUqmrgVNi-mpxT0pudWZtY4-kBMnnDHg@mail.gmail.com>
Message-ID: <955deb0c-75de-aeea-a737-405382d77f06@slackbuilds.org>

> For some reason, in 27504d39f215cb7a8a74b6a7edab9b0fd6768914 xmlsec was
> reverted to 1.2.27. c5603f5d4cb83f82265772cb8b9f1ee0e521d398 upgraded to
> 1.3.0, and the changelog lists it as being upgraded to 1.3.0. Just reporting

it's being reverted because 1.3.0 introduced some ABI breakage

-- 
Willy Sudiarto Raharjo

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

From willysr at slackbuilds.org  Wed Jun  7 18:14:49 2023
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 8 Jun 2023 01:14:49 +0700
Subject: [Slackbuilds-users] xmlsec was reverted to 1.2.27
In-Reply-To: <955deb0c-75de-aeea-a737-405382d77f06@slackbuilds.org>
References: <CADnMSPLM4K6pcwbWP7eUqmrgVNi-mpxT0pudWZtY4-kBMnnDHg@mail.gmail.com>
 <955deb0c-75de-aeea-a737-405382d77f06@slackbuilds.org>
Message-ID: <5a19fda9-8892-7b2f-f671-01328958a43c@slackbuilds.org>

>> For some reason, in 27504d39f215cb7a8a74b6a7edab9b0fd6768914 xmlsec was
>> reverted to 1.2.27. c5603f5d4cb83f82265772cb8b9f1ee0e521d398 upgraded to
>> 1.3.0, and the changelog lists it as being upgraded to 1.3.0. Just 
>> reporting
> 
> it's being reverted because 1.3.0 introduced some ABI breakage

oh, i think i forgot to edit the VERSION back to 1.2.27
my bad


-- 
Willy Sudiarto Raharjo

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

From julian at dotcore.co.il  Thu Jun  8 01:48:37 2023
From: julian at dotcore.co.il (Julian Grinblat)
Date: Thu, 8 Jun 2023 10:48:37 +0900
Subject: [Slackbuilds-users] linux kernel slackbuild
Message-ID: <CADnMSPJPXQb=vXwj0yWcACWeE4ts6LFEdeD7H7J4WspQkcTBNQ@mail.gmail.com>

I was wondering if a slackbuild for packaging the linux kernel is something
that would be accepted into SlackBuilds, or if people would be interested
in it to begin with.
I put together a small script for building and packaging the kernel for
personal use, here: https://github.com/perrin4869/linux-kernel-slackbuild
The goal is to be able to install and remove and test kernels easily. The
repo follows the SlackBuild.org guidelines for the most part.
If this would be acceptable, is there anything that should be fixed?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230608/a9a046d2/attachment.htm>

From bobfunk11 at gmail.com  Thu Jun  8 02:54:09 2023
From: bobfunk11 at gmail.com (Bob Funk)
Date: Wed, 7 Jun 2023 21:54:09 -0500
Subject: [Slackbuilds-users] Abandoning Epiphany SlackBuild
In-Reply-To: <75849a7d-53b1-8523-f40a-c860aed386d7@iotib.net>
References: <5c6b7fc1-8265-fd44-8d78-b919d28e341a@iotib.net>
 <6BC7075A-2CC2-460E-BFDB-E42DA8D171FD@edison.tech>
 <CAJOKJPbtvwYGbbQH4KhkWR8apjo+Ge_g6_fu41eThutubBWcxQ@mail.gmail.com>
 <75849a7d-53b1-8523-f40a-c860aed386d7@iotib.net>
Message-ID: <CAJOKJPbArNARqjKvboF83ZFY_zgKgaNu9CQSjWhu5UcrVBx3XQ@mail.gmail.com>

Epiphany from the gnome 44 branch needs the webkit2gtk-6.0 api (the
libsoup3+gtk4 webkit build), and gcr-4, both of which are not on
slackbuilds.org yet. It also needs a newer libadwaita version than the one
on SBo, and newer gstreamer libraries than what slackware 15.0 provides, so
we're kind of roadblocked there regardless of the other missing
dependencies. It looks like Epiphany's going to be another gnome package
that gets stuck on a version that works with slackware-15.0. It'll have to
wait till -current rolls over to a new release before I can update Epiphany
and a number of other gnome builds to the 44 branch.

There was an Epiphany 43.1 release on the gnome 43 branch from Feb 2023
with some bug fixes so I updated to that and submitted a build to take over
maintenance.

-BF

On Mon, Jun 5, 2023 at 6:12?AM Charadon via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> On 6/5/23 03:01, Bob Funk wrote:
> > I can take over maintaining epiphany and add it to the collection of
> > gnome core builds I've been building.
> >
> > I'll look it over and submit an update to take over maintenance later
> > this week.
> >
> > Bob
> >
> > On Sun, Jun 4, 2023, 2:10 PM J via SlackBuilds-users
> > <slackbuilds-users at slackbuilds.org
> > <mailto:slackbuilds-users at slackbuilds.org>> wrote:
> >
> >     I actually do use it as epiphany is much lighter on aarch64
> >     Slackware vs Firefox but I generally keep my own scripts since
> >     aarch64 isn?t targeted by most of SBo as of yet.
> >
> >     I?m assuming 0xBOB may want this one to go with the rest of gnome,
> >     but if not, I?ll take it.
> >
> >     ? Jay Lanagan
> >
> >
> >>     On Jun 4, 2023 at 10:58 AM, <Charadon via SlackBuilds-users
> >>     <mailto:slackbuilds-users at slackbuilds.org>> wrote:
> >>
> >>     I don't have any interest in maintaining Epiphany anymore as I
> don't use
> >>     it, and upstream has been putting more emphasis on using the Flatpak
> >>     version. If anyone wants it, you can have it =)
> >>     _______________________________________________
> >>     SlackBuilds-users mailing list
> >>     SlackBuilds-users at slackbuilds.org  <mailto:
> SlackBuilds-users at slackbuilds.org>
> >>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users  <
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >>     Archives -
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/  <
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >>     FAQ -https://slackbuilds.org/faq/  <https://slackbuilds.org/faq/>
> >>
> >>
> >     _______________________________________________
> >     SlackBuilds-users mailing list
> >     SlackBuilds-users at slackbuilds.org
> >     <mailto:SlackBuilds-users at slackbuilds.org>
> >     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >     Archives -
> >     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >     FAQ - https://slackbuilds.org/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/
> >
>
> You *should* be able to update it now, since I think libportal's
> slackbuild finally got an update. That was the main reason it's been
> stuck on 43.0 for so long. =)
> _______________________________________________
> 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/20230607/8ef52aa9/attachment.htm>

From davidnchmelik at gmail.com  Thu Jun  8 05:10:09 2023
From: davidnchmelik at gmail.com (David Chmelik)
Date: Wed, 7 Jun 2023 22:10:09 -0700
Subject: [Slackbuilds-users] linux kernel slackbuild
In-Reply-To: <CADnMSPJPXQb=vXwj0yWcACWeE4ts6LFEdeD7H7J4WspQkcTBNQ@mail.gmail.com>
References: <CADnMSPJPXQb=vXwj0yWcACWeE4ts6LFEdeD7H7J4WspQkcTBNQ@mail.gmail.com>
Message-ID: <80e395d7-34d6-d655-425a-5ff38c6036f8@gmail.com>

I like the idea because sometime after/in Linux kernel v2, documentation 
on how to build a kernel disappeared from the main site or from The 
Linux Documentation Project (TLDP) and/or was outdated.? For a while 
there was no documentation or only informal/partial documentation, not 
always very good.? Sometime by v4 there was documentation elsewhere but 
I don't know that it's official... I don't recall if there is any 
official documentation anymore or if it's back in TLDP, so I'd just like 
to see how it's done again.? In the days of v2 I build kernels maybe 
200+ times trying to get a Matrox display/video card to work with dual 
monitors (as separate terminals) to no avail. I'd just like to see how 
it's done again and if we can be assured the SlackBuild does it right, 
that'd be something nice to see...

On 6/7/23 6:48 PM, Julian Grinblat wrote:
> I was wondering if a slackbuild for packaging the linux kernel is 
> something that would be accepted into SlackBuilds, or if people would 
> be interested in it to begin with.
> I put together a small script for building and packaging the kernel 
> for personal use, here: 
> https://github.com/perrin4869/linux-kernel-slackbuild 
> <https://github.com/perrin4869/linux-kernel-slackbuild>
> The goal is to be able to install and remove and test kernels easily. 
> The repo follows the SlackBuild.org guidelines for the most part.
> If this would be acceptable, is there anything that should be fixed?


From jebrhansen+SBo at gmail.com  Thu Jun  8 05:28:51 2023
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Wed, 7 Jun 2023 22:28:51 -0700
Subject: [Slackbuilds-users] linux kernel slackbuild
In-Reply-To: <80e395d7-34d6-d655-425a-5ff38c6036f8@gmail.com>
References: <CADnMSPJPXQb=vXwj0yWcACWeE4ts6LFEdeD7H7J4WspQkcTBNQ@mail.gmail.com>
 <80e395d7-34d6-d655-425a-5ff38c6036f8@gmail.com>
Message-ID: <CANi9qSsu5v1JnQa_uTNzWYNpEE0LAcP44zvhEY6WYWZ5kFKeVQ@mail.gmail.com>

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

The script might be of interest to some.

https://gitlab.com/idlemoor/dusk

On Wed, Jun 7, 2023, 10:10 PM David Chmelik <davidnchmelik at gmail.com> wrote:

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

From korgie at gmail.com  Thu Jun  8 06:01:13 2023
From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=)
Date: Thu, 8 Jun 2023 09:01:13 +0300
Subject: [Slackbuilds-users] linux kernel slackbuild
In-Reply-To: <80e395d7-34d6-d655-425a-5ff38c6036f8@gmail.com>
References: <80e395d7-34d6-d655-425a-5ff38c6036f8@gmail.com>
Message-ID: <0D990575-FA8A-4CA1-8F76-A8171E679C7C@gmail.com>


> 8 ???? 2023, 08:10, ? ??????? ?David Chmelik <davidnchmelik at gmail.com>? ??????:
> 
> I like the idea because sometime after/in Linux kernel v2, documentation on how to build a kernel disappeared from the main site or from The Linux Documentation Project (TLDP) and/or was outdated

I build my own kernels from 2008. I don?t remember something new. Only that compile times are more slow :)

I have a private kernel simple build script. You need ?make bzImage? and ?make modules? as always.

The real pain is the kernel configuration. For example I managed to not have a working memory card reader although I supposedly complied the appropriate driver.

All others systems work thankfully.

From slackbuilds at schoepfer.info  Thu Jun  8 09:43:23 2023
From: slackbuilds at schoepfer.info (Franzen)
Date: Thu, 08 Jun 2023 11:43:23 +0200
Subject: [Slackbuilds-users] mate-terminal
In-Reply-To: <ZH3YBv2uIuMyLdk3@x360.localdomain>
References: <ZGkfG85yNZHn704I@x360.localdomain>
 <ZHuuGPA938Wp4ULS@x360.localdomain>
 <067da2a2-d795-ba2f-7d25-48c217df765c@free.fr>
 <2bd9df2b-d589-42c4-9cd7-a00bb7d41240@slint.fr>
 <9d839ca9-75de-14a0-74c8-5aa58741bac6@free.fr>
 <9f22c13a-c1d5-c75a-1658-7f71c7278bd1@slint.fr>
 <9b06820b-de93-c590-4f40-b268b5c290c4@free.fr>
 <9e062d17-2ec8-2893-87b8-73f670e1284a@slint.fr>
 <3D6D2898-4037-44F6-BE39-4BEFC78C1ACA@schoepfer.info>
 <CAJEH=oHdLUDAxBwYZTQB34130J0GWwJ2ze1fpMswoXc_UjnBSA@mail.gmail.com>
 <ZH3YBv2uIuMyLdk3@x360.localdomain>
Message-ID: <92b50cbb7a8ab5d9b4919ca96f191663@schoepfer.info>

> On Mon, Jun  5, 2023 at 11:20 (+0300), George Vlahavas wrote:
> 
>> mate-terminal doesn't really need mate-desktop. Only just some glib 
>> schemas
>> that are bundled with the mate-desktop package. To have mate-terminal
>> working without mate-desktop, just include the attached file in the
>> /usr/share/glib-2.0/schemas directory of the mate-terminal package.

I've submitted the attached mate-terminal build, which incorporates the
xml-file to avoid the dependency on mate-desktop.

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mate-terminal.tar
Type: application/x-tar
Size: 20480 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230608/92a71352/attachment-0001.tar>

From didier at slint.fr  Thu Jun  8 20:24:26 2023
From: didier at slint.fr (Didier Spaier)
Date: Thu, 8 Jun 2023 22:24:26 +0200
Subject: [Slackbuilds-users] linux kernel slackbuild
In-Reply-To: <CADnMSPJPXQb=vXwj0yWcACWeE4ts6LFEdeD7H7J4WspQkcTBNQ@mail.gmail.com>
References: <CADnMSPJPXQb=vXwj0yWcACWeE4ts6LFEdeD7H7J4WspQkcTBNQ@mail.gmail.com>
Message-ID: <eeaacaa5-3072-3010-fd87-6b9b023953e8@slint.fr>

As an aside, SlackBuilds used to build the kernel packages shipped in Slackware
are available here: http://slackware.uk/slackware/slackware64-current/source/k/

For Slint and for what it's worth, as you can see here:
http://slackware.uk/slint/x86_64/slint-15.0/source/kernel/
I ship an all-in-one kernel package, including the kernel itself,the modules and
the sanitized headers. dracut is used to associate an intramfs with each kernel.


Le 08/06/2023 ? 03:48, Julian Grinblat a ?crit?:
> I was wondering if a slackbuild for packaging the linux kernel is something that
> would be accepted into SlackBuilds, or if people would be interested in it to
> begin with.
> I put together a small script for building and packaging the kernel for personal
> use, here: https://github.com/perrin4869/linux-kernel-slackbuild
> <https://github.com/perrin4869/linux-kernel-slackbuild>
> The goal is to be able to install and remove and test kernels easily. The repo
> follows the SlackBuild.org guidelines for the most part.

From arnaud.garcia-fernandez at laposte.net  Fri Jun  9 07:44:46 2023
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Fri, 9 Jun 2023 09:44:46 +0200
Subject: [Slackbuilds-users] [python3-setuptools] A Question about a
 SlackBuild.
Message-ID: <20230609094446.2a4c06ea578f4d05f6cd009a@laposte.net>

Hi everybody !

	I'm facing a slight problem.
I've updated python3-dulwich, apparently more than a month ago.
It is used by Kallithea and hg-git which I also maintain, I'm not using hg-git
often, but I have a working and updated Kallithea service around.
Well it seems I didn't test this update as throughly as I thought.
Or at all, for that matter.

The build is broken and produces those files :

/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/PKG-INFO
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/SOURCES.txt
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/dependency_links.txt
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/top_level.txt

That, obviously, doesn't work as expected.

The problem resides in the python-setuptools package of Slackware 15.0 which is
at version 57.5.0.
In dulwich/pyproject.toml lies the answer :
[build-system]
requires = ["setuptools>=61.2"]


Here I've got three solutions :

 * revert dulwich to earlier version, 0.21.3, and wait for Slackware 15.1.

 * create a python3-setuptools package which'll overwrite Slackware's stock
python-setuptools with a newer version. Could even name it python-setuptools for
obvious, and transparent, replacement. It'll probably be updated naturally when
Slackware releases 15.1 is out.
 -> I have it working with latest setuptools 67.8.0, and dulwich builds fine.

 * somehow prepare a local setuptools to use for building dulwich, adding the
source to dulwich's info file, and building both while installing only dulwich.


Does anyone have any advice on that ?
I mean, apart from the obvious ? test your friggin' SlackBuilds before
submitting them ?, I've got it in a loop between my ears, and in French...

 - Yth.

From fourtysixandtwo at sliderr.net  Fri Jun  9 09:23:04 2023
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Fri, 9 Jun 2023 03:23:04 -0600
Subject: [Slackbuilds-users] [python3-setuptools] A Question about a
 SlackBuild.
In-Reply-To: <20230609094446.2a4c06ea578f4d05f6cd009a@laposte.net>
References: <20230609094446.2a4c06ea578f4d05f6cd009a@laposte.net>
Message-ID: <CAAZ8Hag3U+Ki9SKZwOY4bmMSp61pLjFHkHD3mfkFb-vB11LwZg@mail.gmail.com>

Hi Yth,

I have a slackbuild for setuptools, using the same version (65.1.1) and
patch from current source that I've been thinking of uploading.  I've
tested it with a newer version as well, so I'm not set on using the one
from current.

I've attached the slackbuild if you want to give it a try.  It could use
another set of eyes and testing.  Let me know your thoughts.

Here's a snippet from the README on how to use it.

Installs to /opt/python3.9/site-packages.

Add the following before the python3 build commands in your
Slackbuild to use this version over the stock one in 15.0:

export PYTHONPATH=/opt/python3.9/site-packages/

Cheers

P.S. It's currently 26C in my house and I can't sleep so you're getting
this reply now instead of later

On Fri, Jun 9, 2023 at 1:44?AM Arnaud via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> Hi everybody !
>
>         I'm facing a slight problem.
> I've updated python3-dulwich, apparently more than a month ago.
> It is used by Kallithea and hg-git which I also maintain, I'm not using
> hg-git
> often, but I have a working and updated Kallithea service around.
> Well it seems I didn't test this update as throughly as I thought.
> Or at all, for that matter.
>
> The build is broken and produces those files :
>
> /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/
> /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/PKG-INFO
> /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/SOURCES.txt
>
> /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/dependency_links.txt
>
> /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/top_level.txt
>
> That, obviously, doesn't work as expected.
>
> The problem resides in the python-setuptools package of Slackware 15.0
> which is
> at version 57.5.0.
> In dulwich/pyproject.toml lies the answer :
> [build-system]
> requires = ["setuptools>=61.2"]
>
>
> Here I've got three solutions :
>
>  * revert dulwich to earlier version, 0.21.3, and wait for Slackware 15.1.
>
>  * create a python3-setuptools package which'll overwrite Slackware's stock
> python-setuptools with a newer version. Could even name it
> python-setuptools for
> obvious, and transparent, replacement. It'll probably be updated naturally
> when
> Slackware releases 15.1 is out.
>  -> I have it working with latest setuptools 67.8.0, and dulwich builds
> fine.
>
>  * somehow prepare a local setuptools to use for building dulwich, adding
> the
> source to dulwich's info file, and building both while installing only
> dulwich.
>
>
> Does anyone have any advice on that ?
> I mean, apart from the obvious ? test your friggin' SlackBuilds before
> submitting them ?, I've got it in a loop between my ears, and in French...
>
>  - Yth.
> _______________________________________________
> 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/20230609/e4c36060/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: python3-setuptools-opt.tar.gz
Type: application/gzip
Size: 3707 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230609/e4c36060/attachment.bin>

From dickson.tim at googlemail.com  Fri Jun  9 10:31:59 2023
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Fri, 9 Jun 2023 11:31:59 +0100
Subject: [Slackbuilds-users] [python3-setuptools] A Question about a
 SlackBuild.
In-Reply-To: <CAAZ8Hag3U+Ki9SKZwOY4bmMSp61pLjFHkHD3mfkFb-vB11LwZg@mail.gmail.com>
References: <20230609094446.2a4c06ea578f4d05f6cd009a@laposte.net>
 <CAAZ8Hag3U+Ki9SKZwOY4bmMSp61pLjFHkHD3mfkFb-vB11LwZg@mail.gmail.com>
Message-ID: <ff584016-95a4-4698-0c4f-75bff80d61cc@googlemail.com>

have you tried just sed'ing the version in the toml line to the version 
that ships with slackware 15.0? ?
quite often that works, and the only reason the requirement changed was 
that the system it was developed on had a newer setuptools, not that it 
actually used any new features.
regards, Tim

On 09/06/2023 10:23, fourtysixandtwo wrote:
> Hi Yth,
>
> I have a slackbuild for setuptools, using the same version (65.1.1) 
> and patch from current source that I've been thinking of uploading.? 
> I've tested it with a newer version as well, so I'm not set on using 
> the one from current.
>
> I've attached the slackbuild if you want to give it a try. It could 
> use another set of eyes and testing.? Let me know your thoughts.
>
> Here's a snippet from the README on how to use it.
>
> Installs to /opt/python3.9/site-packages.
>
> Add the following before the python3 build commands in your
> Slackbuild to use this version over the stock one in 15.0:
>
> export PYTHONPATH=/opt/python3.9/site-packages/
>
> Cheers
>
> P.S. It's currently 26C in my house and I can't sleep so you're 
> getting this reply now instead of later
>
> On Fri, Jun 9, 2023 at 1:44?AM Arnaud via SlackBuilds-users 
> <slackbuilds-users at slackbuilds.org> wrote:
>
>     Hi everybody !
>
>     ? ? ? ? I'm facing a slight problem.
>     I've updated python3-dulwich, apparently more than a month ago.
>     It is used by Kallithea and hg-git which I also maintain, I'm not
>     using hg-git
>     often, but I have a working and updated Kallithea service around.
>     Well it seems I didn't test this update as throughly as I thought.
>     Or at all, for that matter.
>
>     The build is broken and produces those files :
>
>     /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/
>     /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/PKG-INFO
>     /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/SOURCES.txt
>     /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/dependency_links.txt
>     /usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/top_level.txt
>
>     That, obviously, doesn't work as expected.
>
>     The problem resides in the python-setuptools package of Slackware
>     15.0 which is
>     at version 57.5.0.
>     In dulwich/pyproject.toml lies the answer :
>     [build-system]
>     requires = ["setuptools>=61.2"]
>
>
>     Here I've got three solutions :
>
>     ?* revert dulwich to earlier version, 0.21.3, and wait for
>     Slackware 15.1.
>
>     ?* create a python3-setuptools package which'll overwrite
>     Slackware's stock
>     python-setuptools with a newer version. Could even name it
>     python-setuptools for
>     obvious, and transparent, replacement. It'll probably be updated
>     naturally when
>     Slackware releases 15.1 is out.
>     ?-> I have it working with latest setuptools 67.8.0, and dulwich
>     builds fine.
>
>     ?* somehow prepare a local setuptools to use for building dulwich,
>     adding the
>     source to dulwich's info file, and building both while installing
>     only dulwich.
>
>
>     Does anyone have any advice on that ?
>     I mean, apart from the obvious ? test your friggin' SlackBuilds before
>     submitting them ?, I've got it in a loop between my ears, and in
>     French...
>
>     ?- Yth.
>     _______________________________________________
>     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/20230609/014f1987/attachment-0001.htm>

From arnaud.garcia-fernandez at laposte.net  Fri Jun  9 12:13:40 2023
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Fri, 9 Jun 2023 14:13:40 +0200
Subject: [Slackbuilds-users] [python3-setuptools] A Question about a
 SlackBuild.
In-Reply-To: <ff584016-95a4-4698-0c4f-75bff80d61cc@googlemail.com>
References: <20230609094446.2a4c06ea578f4d05f6cd009a@laposte.net>
 <CAAZ8Hag3U+Ki9SKZwOY4bmMSp61pLjFHkHD3mfkFb-vB11LwZg@mail.gmail.com>
 <ff584016-95a4-4698-0c4f-75bff80d61cc@googlemail.com>
Message-ID: <20230609141340.1696e51384fd31084f2c6143@laposte.net>

> have you tried just sed'ing the version in the toml line to the version 
> that ships with slackware 15.0? ?
> quite often that works, and the only reason the requirement changed was 
> that the system it was developed on had a newer setuptools, not that it 
> actually used any new features.
> regards, Tim

Well, this requirement is not enforced, the python3 setup.py command works
without complaining.
It just produces the wrong result with files in :
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/

This seems to mean that a newer setuptools is actually required.
As for the exact version, maybe it's something between 57.5.0 and 61.2, but that
doesn't matter much.

 - Yth.

From arnaud.garcia-fernandez at laposte.net  Fri Jun  9 12:20:35 2023
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Fri, 9 Jun 2023 14:20:35 +0200
Subject: [Slackbuilds-users] [python3-setuptools] A Question about a
 SlackBuild.
In-Reply-To: <CAAZ8Hag3U+Ki9SKZwOY4bmMSp61pLjFHkHD3mfkFb-vB11LwZg@mail.gmail.com>
References: <20230609094446.2a4c06ea578f4d05f6cd009a@laposte.net>
 <CAAZ8Hag3U+Ki9SKZwOY4bmMSp61pLjFHkHD3mfkFb-vB11LwZg@mail.gmail.com>
Message-ID: <20230609142035.1f26591829ff3485e902afc5@laposte.net>

> Hi Yth,
> 
> I have a slackbuild for setuptools, using the same version (65.1.1) and
> patch from current source that I've been thinking of uploading.  I've
> tested it with a newer version as well, so I'm not set on using the one
> from current.
> 
> I've attached the slackbuild if you want to give it a try.  It could use
> another set of eyes and testing.  Let me know your thoughts.
> 
> Here's a snippet from the README on how to use it.
> 
> Installs to /opt/python3.9/site-packages.
> 
> Add the following before the python3 build commands in your
> Slackbuild to use this version over the stock one in 15.0:
> 
> export PYTHONPATH=/opt/python3.9/site-packages/
> 
> Cheers
> 
> P.S. It's currently 26C in my house and I can't sleep so you're getting
> this reply now instead of later

I like the idea of installing it in /opt
I would become a requirement of python3-dulwich, and the Slackbuild itself would
set the right PYTHONPATH, while not altering the stock slackware's packages.

That does work, I've just removed my own updated setuptools and replaced the
proper slackware one, checked dulwich build still doesn't work, then installed
your slackbuild, and confirmed it builds fine when adding the proper PYTHONPATH
in the SlackBuild script.

In the absence of your package, the dulwich build ignores the PYTHONPATH,
meaning that on a -current box the SlackBuild will also work fine, without 
python3-setuptools-opt

Please, do submit your slackbuild, it works for me :)

	- Yth.

PS : Urk, where do you live to have such heat at night ? I'm almost suffering
with 26?C during the day already...

From spaceman at antispaceman.com  Fri Jun  9 16:40:39 2023
From: spaceman at antispaceman.com (spaceman)
Date: Fri, 09 Jun 2023 16:40:39 +0000
Subject: [Slackbuilds-users] libgsasl
Message-ID: <202306091641.359GftPb069664@mail.authsmtp.com>

libgsasl is out of date (1.8.0 --> 2.2.0) and over 10 years old. Is 
there any reason for this?

I am asking because it is a very optional dependency of mpop.

Regards,
spaceman

From urchlay at slackware.uk  Fri Jun  9 18:30:44 2023
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 9 Jun 2023 14:30:44 -0400 (EDT)
Subject: [Slackbuilds-users] libgsasl
In-Reply-To: <202306091641.359GftPb069664@mail.authsmtp.com>
References: <202306091641.359GftPb069664@mail.authsmtp.com>
Message-ID: <a9b28f36-94c1-3151-6f44-9feb6e8e2e1@slackware.uk>



On Fri, 9 Jun 2023, spaceman via SlackBuilds-users wrote:

> libgsasl is out of date (1.8.0 --> 2.2.0) and over 10 years old. Is
> there any reason for this?

Its maintainer abandoned all his slackbuilds a few years ago. libgsasl
is up for grabs.

> I am asking because it is a very optional dependency of mpop.

Feel free to take over maintenance, and submit an update.

However, before you send us the new version, test the builds
that depend on it:

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

An update shouldn't break anything else.

From fourtysixandtwo at sliderr.net  Fri Jun  9 19:05:37 2023
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Fri, 9 Jun 2023 13:05:37 -0600
Subject: [Slackbuilds-users] [python3-setuptools] A Question about a
 SlackBuild.
In-Reply-To: <20230609142035.1f26591829ff3485e902afc5@laposte.net>
References: <20230609094446.2a4c06ea578f4d05f6cd009a@laposte.net>
 <CAAZ8Hag3U+Ki9SKZwOY4bmMSp61pLjFHkHD3mfkFb-vB11LwZg@mail.gmail.com>
 <20230609142035.1f26591829ff3485e902afc5@laposte.net>
Message-ID: <CAAZ8HahJm61ZN6Bpfv6wK06x5Z3u6W7=D10ayX4nwPA+bjqAMw@mail.gmail.com>

On Fri, Jun 9, 2023 at 6:20?AM Arnaud via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

>
> I like the idea of installing it in /opt
> I would become a requirement of python3-dulwich, and the Slackbuild itself
> would
> set the right PYTHONPATH, while not altering the stock slackware's
> packages.
>
> That does work, I've just removed my own updated setuptools and replaced
> the
> proper slackware one, checked dulwich build still doesn't work, then
> installed
> your slackbuild, and confirmed it builds fine when adding the proper
> PYTHONPATH
> in the SlackBuild script.
>
> In the absence of your package, the dulwich build ignores the PYTHONPATH,
> meaning that on a -current box the SlackBuild will also work fine, without
> python3-setuptools-opt
>
> Please, do submit your slackbuild, it works for me :)
>
>         - Yth.
>
> PS : Urk, where do you live to have such heat at night ? I'm almost
> suffering
> with 26?C during the day already...
>

Thanks for testing, I'll get it finished up and submit it next week.

With that added I can get around to adding maturin.  That's the one missing
build system I've come across that we don't have yet.

Cheers

P.S. In southern Alberta and that was just in the house.  A/C has always
been very optional here, but it's quickly becoming necessary.  At least
it's humid.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230609/3f15789f/attachment.htm>

From willysr at slackbuilds.org  Sat Jun 10 07:33:12 2023
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 10 Jun 2023 14:33:12 +0700
Subject: [Slackbuilds-users] Updates - 20230610.1
Message-ID: <182f6485-18ec-c5c6-7b45-517b784ca0a5@slackbuilds.org>

Hi all,

this public update brings a lot of python2 removals since they have been 
ported to python3 or no longer used in any other scripts


Sat Jun 10 07:02:09 UTC 2023
academic/copasi: Updated for version 4.40.278.
academic/gcompris-qt: Updated for version 3.3.
academic/mathjax2: Update maintainer's email
academic/python3-scipy: Update maintainer's email
academic/qucs-s: Updated for version 1.1.0.
academic/xsimd: Update maintainer's email
audio/abcde: New maintainer.
audio/alsamixergui: New download links.
audio/cd-discid: New maintainer.
audio/mkcue: New maintainer.
audio/puddletag: Version bump to 2.2.0
audio/tagtool: Version bump to 0.14.2 and switch to newer upstream
desktop/Matcha-gtk-theme: Update maintainer's email
desktop/SwayNotificationCenter: Updated for version 0.9.0.
desktop/Tela-icon-theme: Update maintainer's email
desktop/artix-backgrounds: Update maintainer's email
desktop/breath-gtk-theme: Update maintainer's email
desktop/breeze-snow-cursor-theme: Update maintainer's email
desktop/dwmblocks: Update maintainer's email
desktop/libqtxdg: Update maintainer's email
desktop/lxqt-panel: Update maintainer's email
desktop/lxqt-themes: Update maintainer's email
desktop/mate-terminal: Fix schema.
desktop/nitrogen: Update maintainer's email
desktop/nwg-panel: Updated for version 0.9.6.
desktop/nwg-shell-config: Updated for version 0.5.2.
desktop/papirus-icon-theme: Updated for version 20230601.
desktop/plasma5-themes-breath-migration: Update maintainer's email
desktop/plasma5-themes-breath: Update maintainer's email
desktop/qtile: Update maintainer's email
desktop/sddm-theme-artix: Update maintainer's email
desktop/slbar: Update maintainer's email
desktop/sun: Updated for version 1.5.2.
desktop/vertex-maia-icon-theme: Update maintainer's email
desktop/xsecurelock: Update maintainer's email
development/QtPy: Update maintainer's email
development/avr-binutils: Use https download URL.
development/bazel: Update maintainer's email
development/cloc: Version bump to 1.96.1
development/cproc: Added (small C11 compiler).
development/electron: Update maintainer's email
development/ghidra: Updated for version 10.3
development/jupyter-ipykernel: Update maintainer's email
development/jupyter-nbclassic: Update maintainer's email
development/jupyter-nbclient: Update maintainer's email
development/jupyter-nbconvert: Update maintainer's email
development/jupyter-nbformat: Update maintainer's email
development/jupyter-notebook: Update maintainer's email
development/jupyter-notebook_shim: Update maintainer's email
development/jupyter-qtconsole: Update maintainer's email
development/jupyter_client: Update maintainer's email
development/jupyter_console: Update maintainer's email
development/jupyter_core: Update maintainer's email
development/jupyter_events: Update maintainer's email
development/jupyter_packaging: Update maintainer's email
development/jupyter_server: Update maintainer's email
development/jupyter_server_terminals: Update maintainer's email
development/jupyterlab: Update maintainer's email
development/jupyterlab_pygments: Update maintainer's email
development/jupyterlab_server: Update maintainer's email
development/kotlin: Updated for version 1.8.22.
development/nodejs: Updated for version 20.3.0.
development/pyqt-distutils: Removed (replaced by python3-pyqt-distutils)
development/python3-spyder-kernels: Update maintainer's email
development/rstudio-desktop-legacy: Update maintainer's email
development/rstudio-desktop: Update maintainer's email
development/rstudio-desktop: Updated for version 2023.06.0+421.
development/sasm: Added (IDE for NASM,MASM, GAS, and FASM assembly).
development/sbcl: Updated for version 2.3.5
development/uncrustify: Updated for version 0.77.1
development/universal-ctags: Updated for version p6.0.20230604.0
development/vscode-bin: Updated for version 1.79.0.
development/wheel: Removed: (replaced by python3-wheel)
games/Mindustry: Added (hybrid tower-defense sandbox factory game)
games/PrismLauncher: Updated for version 7.0.
games/ags: updated for version 3.6.0.49
games/desmume: Updated for version 0.9.13, new maintainer.
gis/libspatialindex: Update maintainer's email
gis/pdal: Updated for version 2.5.4.
gis/proj-data: Updated for version 1.14.
gis/saga-gis: Updated for version 9.0.2.
graphics/FotoKilof: Updated for version 4.3.3.
graphics/maim: Update maintainer's email
graphics/qiv: Updated for version 2.3.3.
graphics/vimiv-qt: Update maintainer's email
graphics/webp-pixbuf-loader: Updated for version 0.2.4.
libraries/CherryPy: Removed: (replaced by python3-CherryPy)
libraries/QDarkStyle: Update maintainer's email
libraries/googlebenchmark: Added (Google tiny benchmarking library)
libraries/libfm-qt: Update maintainer's email
libraries/libgusb: Updated for version 0.4.6.
libraries/liblxqt: Update maintainer's email
libraries/liblzf: Update maintainer's email
libraries/libmirage: Update maintainer's email
libraries/libopenraw: Updated for version 0.3.5.
libraries/librsync: Update maintainer's email
libraries/libtorrent-rasterbar: Update for 1.2.19
libraries/lua53-filesystem: Added (lua filesystem library)
libraries/lxqt-build-tools: Update maintainer's email
libraries/lxqt-notificationd: Update maintainer's email
libraries/lxqt-qtplugin: Update maintainer's email
libraries/lxqt-sudo: Update maintainer's email
libraries/plumbum: Removed: (replaced by python3-plumbum)
libraries/rpyc: Removed: (replaced by python3-rpyc)
libraries/soci: Update maintainer's email
libraries/zc.lockfile: Removed: (replaced by python3-zc.lockfile)
libraries/zeromq: Update maintainer's email
libraries/zziplib: Updated for version 0.13.72, new maintainer.
misc/KeePass: Updated for version 2.54.
misc/simh-classic: Updated for version 3.12_4.
multimedia/makemkv: Updated for version 1.17.4.
multimedia/picard-plugins: Version bump to c03c7f1
multimedia/picard: Version bump to 2.8.5
multimedia/pitivi: Correct md5sum
multimedia/pitivi: Version bump to 2023.03
multimedia/plexmediaserver: Updated for v 1.32.3.
network/AdGuardHome: Updated for version 0.107.31.
network/CherryMusic: Removed: (replaced by python3-CherryMusic)
network/PyRSS2Gen: Removed: (replaced by python3-PyRSS2Gen)
network/brave-browser: update 1.52.117
network/dropbox: Updated for version 175.4.5569.
network/element-desktop: Updated for version 1.11.33.
network/epiphany: Updated for version 43.1.
network/jitsi-meet-desktop: Update maintainer's email
network/qbittorrent: Adjust desktop file.
network/sfeed: Update maintainer's email
network/telegram: Updated for version 4.8.3.
network/tor-browser: Updated for version 12.0.7.
network/vivaldi: Updated for version 6.1.3035.75.
network/whalebird: Update maintainer's email
network/zoom-linux: Updated for version 5.14.10.3738
office/LibreOffice: Updated for version 7.5.4.2
office/asymptote: Added missing files.
office/asymptote: Updated for version 2.85.
office/calibre-bin: Updated for version 6.20.0.
office/focuswriter: Update maintainer's email
office/hunspell-en: Update maintainer's email
office/libreoffice-helppack: Updated for version 7.5.4.
office/libreoffice-langpack: Updated for version 7.5.4.
office/libreoffice: Updated for version 7.5.4.
perl/perl-DBD-Pg: Updated for version 3.16.3. New maintainer.
perl/perl-Date-Manip: Updated for version 6.92.
python/APScheduler: Removed: (replaced by python3-APScheduler)
python/BeautifulSoup4: Update maintainer's email
python/PyPDF2: Update source.
python/WTForms: Removed: (replaced by python3-WTForms)
python/argon2-cffi-bindings: Update maintainer's email
python/argon2-cffi: Update maintainer's email
python/babelfish: Removed: (replaced by python3-babelfish)
python/blinker: Removed: (replaced by python3-blinker)
python/cairocffi: Update maintainer's email
python/cheroot: Removed: (replaced by python3-cheroot)
python/cppy: Update maintainer's email
python/docopt: Removed (split into python2/3)
python/entrypoints: Update maintainer's email
python/esptool: Updated for version 4.6.1.
python/et_xmlfile: Update maintainer's email
python/guessit: Removed: (replaced by python3-guessit)
python/iniconfig: Remove iniconfig
python/ipython: Update maintainer's email
python/ipython_genutils: Update maintainer's email
python/itsdangerous: Removed: (replaced by python3-itsdangerous)
python/jaraco.classes: Removed: (replaced by python3-jaraco.classes)
python/jsonpointer: Update maintainer's email
python/jsonschema: Removed: (replaced by python3-jsonschema)
python/nest_asyncio: Update maintainer's email
python/netifaces: Removed: (replaced by python3-netifaces)
python/pandocfilters: Update maintainer's email
python/pickleshare: Update maintainer's email
python/pluggy: Update maintainer's email
python/portend: Removed: (replaced by python3-portend)
python/pynzb: Removed: (replaced by python3-pynzb)
python/python-augeas: Removed: (replaced by python3-augeas)
python/python-evdev: Update maintainer's email
python/python-iso3166: Removed: (replaced by python3-iso3166)
python/python-iso639: Removed: (replaced by python3-iso639)
python/python2-BeautifulSoup4: Update maintainer's email
python/python2-asn1crypto: Update maintainer's email
python/python2-atomicwrites: Update maintainer's email
python/python2-py: Update maintainer's email
python/python2-pyasn1: Update maintainer's email
python/python2-soupsieve: Update maintainer's email
python/python3-aiohttp-oauthlib: Added (aiohttp requests-oauthlib)
python/python3-aiohttp-socks: Update maintainer's email
python/python3-aiohttp: Update maintainer's email
python/python3-aiorpcX-legacy: Remove python3-aiorpcX-legacy
python/python3-aiorpcX: Update maintainer's email
python/python3-aiosignal: Update maintainer's email
python/python3-anyio: Update maintainer's email
python/python3-arrow: Update maintainer's email
python/python3-asn1crypto: Update maintainer's email
python/python3-async-timeout: Update maintainer's email
python/python3-atomicwrites: Update maintainer's email
python/python3-autobahn: updated for version 23.6.1
python/python3-beniget: Update maintainer's email
python/python3-black: Update maintainer's email
python/python3-boto3: Update maintainer's email
python/python3-comm: Update maintainer's email
python/python3-cookiecutter: Update maintainer's email
python/python3-dbus-next: Update maintainer's email
python/python3-debugpy: Update maintainer's email
python/python3-defusedxml: Update maintainer's email
python/python3-deprecation: Update maintainer's email
python/python3-diff-match-patch: Update maintainer's email
python/python3-executing: Update maintainer's email
python/python3-fastjsonschema: Update maintainer's email
python/python3-flit: Updated for version 3.9.0.
python/python3-flit_core: Updated for version 3.9.0.
python/python3-fqdn: Update maintainer's email
python/python3-frozenlist: Update maintainer's email
python/python3-gast: Update maintainer's email
python/python3-gensim: Update maintainer's email
python/python3-glances: Updated for version 3.4.0.3.
python/python3-h5py: Update maintainer's email
python/python3-hatch-nodejs-version: Update maintainer's email
python/python3-hatch_fancy_pypi_readme: Updated for version 23.1.0.
python/python3-hatch_jupyter_builder: Update maintainer's email
python/python3-hatchling: Updated for version 1.17.1.
python/python3-helpdev: Update maintainer's email
python/python3-inflection: Update maintainer's email
python/python3-iniconfig: Update maintainer's email
python/python3-intervaltree: Update maintainer's email
python/python3-ipython-sql: Update maintainer's email
python/python3-isoduration: Update maintainer's email
python/python3-jedi: Update maintainer's email
python/python3-jinja2-time: Update maintainer's email
python/python3-joblib: Update maintainer's email
python/python3-json-logger: Update maintainer's email
python/python3-json5: Update maintainer's email
python/python3-kiwisolver: Update maintainer's email
python/python3-lazy_loader: Added (Load subpackages and functions)
python/python3-llvmlite: Added (Lightweight LLVM python binding).
python/python3-lsp-black: Update maintainer's email
python/python3-lsp-jsonrpc: Update maintainer's email
python/python3-lsp-server: Update maintainer's email
python/python3-matplotlib-inline: Update maintainer's email
python/python3-mir_eval: Added (Music/audio processing algorithms)
python/python3-mistune: Update maintainer's email
python/python3-multidict: Update maintainer's email
python/python3-openpyxl: Update maintainer's email
python/python3-overrides: Update maintainer's email
python/python3-pandas: Update maintainer's email
python/python3-patsy: Update maintainer's email
python/python3-pep517: Removed: (replaced by python3-pyproject-hooks)
python/python3-pluggy: Update maintainer's email
python/python3-pooch: Added (A friend to fetch your data files).
python/python3-presets: Added (Manipulate params of module function)
python/python3-prometheus_client: Update maintainer's email
python/python3-pure_eval: Update maintainer's email
python/python3-py: Update maintainer's email
python/python3-pyasn1: Update maintainer's email
python/python3-pydocstyle: Update maintainer's email
python/python3-pylint-venv: Update maintainer's email
python/python3-pyls-spyder: Update maintainer's email
python/python3-pypandoc: Update maintainer's email
python/python3-pypng: Update maintainer's email
python/python3-pyrsistent: Update maintainer's email
python/python3-pytest-runner: Update maintainer's email
python/python3-pytest: Update maintainer's email
python/python3-pythran: Update maintainer's email
python/python3-pywayland: Update maintainer's email
python/python3-pywlroots: Update maintainer's email
python/python3-qstylizer: Update maintainer's email
python/python3-qtawesome: Update maintainer's email
python/python3-regex: Update for 2023.6.3
python/python3-regex: Update maintainer's email
python/python3-requests-unixsocket: Update maintainer's email
python/python3-rfc3339_validator: Update maintainer's email
python/python3-rfc3986_validator: Update maintainer's email
python/python3-rope: Update maintainer's email
python/python3-rtree: Update maintainer's email
python/python3-seaborn: Update maintainer's email
python/python3-shtab: Update maintainer's email
python/python3-slugify: Update maintainer's email
python/python3-smart_open: Update maintainer's email
python/python3-sniffio: Update maintainer's email
python/python3-socks: Update maintainer's email
python/python3-sortedcontainers: Update maintainer's email
python/python3-soupsieve: Update maintainer's email
python/python3-soxr: Added (Sample-rate conversion library)
python/python3-stack_data: Update maintainer's email
python/python3-statsmodels: Update maintainer's email
python/python3-text-unidecode: Update maintainer's email
python/python3-textdistance: Update maintainer's email
python/python3-threadpoolctl: Update maintainer's email
python/python3-three-merge: Update maintainer's email
python/python3-tomlkit: Update maintainer's email
python/python3-tornado: Update maintainer's email
python/python3-trove-classifiers: Updated for version 2023.5.24.
python/python3-uri_template: Update maintainer's email
python/python3-videohash: Added (detecting identical videos).
python/python3-watchdog: Update maintainer's email
python/python3-webcolors: Update maintainer's email
python/python3-wurlitzer: Update maintainer's email
python/python3-xcffib: Update for 1.4.0
python/python3-xcffib: Update maintainer's email
python/python3-xkbcommon: Update maintainer's email
python/python3-yarl: Update maintainer's email
python/pyudev: Update maintainer's email
python/rebulk: Removed: (replaced by python3-rebulk)
python/scikit-learn: Update maintainer's email
python/send2trash: Update maintainer's email
python/tempora: Removed: (replaced by python3-tempora)
python/terminado: Update maintainer's email
python/testpath: Update maintainer's email
python/thonny: Updated for version 4.1.0.
python/traitlets: Update maintainer's email
python/typing-extensions: Update for 4.6.3
python/typing-extensions: Update maintainer's email
python/zxcvbn-python: Removed: (replaced by python3-zxcvbn-python)
system/FontAwesome: Update for 6.4.0
system/Iosevka-aile: Updated for version 24.1.0.
system/Iosevka-etoile: Updated for version 24.1.0.
system/Iosevka-slab: Updated for version 24.1.1
system/Iosevka: Updated for version 24.1.1
system/android-file-transfer: Update maintainer's email
system/arqiver: Update maintainer's email
system/cdemu-client: Update maintainer's email
system/cdemu-daemon: Update maintainer's email
system/docker-compose: Removed: (replaced by python3-docker-compose)
system/gcdemu: Update maintainer's email
system/hyperfine: Updated for version 1.17.0.
system/image-analyzer: Update maintainer's email
system/libratbag: Update maintainer's email
system/libtrash: Update maintainer's email
system/libwmf-type1-fonts: Added (postscript fonts for libwmf)
system/lxqt-config: Update maintainer's email
system/lxqt-globalkeys: Update maintainer's email
system/lxqt-policykit: Update maintainer's email
system/lxqt-session: Update maintainer's email
system/nnn: Update maintainer's email
system/nvidia-driver: Updated for version 525.116.04.
system/nvidia-kernel: Updated for version 525.116.04.
system/nvidia-legacy390-driver: Fix nvidia-persistenced.
system/nvidia-legacy470-driver: Fix nvidia-persistenced.
system/nvidia-open-kernel: Updated for version 525.116.04.
system/openzfs: Updated for version 2.1.12.
system/pass-import: Update maintainer's email
system/pbzx: Added (pbzx stream parser)
system/pcmanfm-qt: Update maintainer's email
system/piper: Update maintainer's email
system/powerline-fonts: Update maintainer's email
system/qps: Update maintainer's email
system/qtxdg-tools: Update maintainer's email
system/sarasa-gothic: Updated for version 0.41.0.
system/sbo-create: Updated for version 2.0.6.
system/sbo-maintainer-tools: Updated for version 0.8.2.
system/slpkg: Updated for version 4.8.9.
system/tbsm: Update maintainer's email
system/trash-cli: Update maintainer's email
system/vhba-module: Update maintainer's email
system/vim-airline-themes: Update maintainer's email
system/vim-airline: Update maintainer's email
system/winetricks: Update maintainer's email
+--------------------------+


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

From fernando.lopezjr at gmail.com  Sun Jun 11 11:40:38 2023
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sun, 11 Jun 2023 06:40:38 -0500
Subject: [Slackbuilds-users] argyllcms tarball not found 404.
Message-ID: <CALrQ46AAD=EHFAEN+S8EKgMSnE7Q3wVgtu+AcuATcEj27E2wVQ@mail.gmail.com>

--2023-06-11 06:38:46--  http://argyllcms.com/Argyll_V2.0.1_src.zip
Resolving argyllcms.com (argyllcms.com)... 43.250.142.86
Connecting to argyllcms.com (argyllcms.com)|43.250.142.86|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-06-11 06:38:47 ERROR 404: Not Found.

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230611/efd18bfa/attachment.htm>

From jebrhansen+SBo at gmail.com  Sun Jun 11 23:55:13 2023
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sun, 11 Jun 2023 16:55:13 -0700
Subject: [Slackbuilds-users] Replacement for broken network/sickrage
Message-ID: <CANi9qSu1LJ9yUWyXSegVo83TVtzeGrTxVUMOzYd-k1sg6ihETg@mail.gmail.com>

SBo admins,

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

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

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

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

Sorry for the wall of text.

Thanks!
Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230611/ae9abc38/attachment.htm>

From slackbuilds at schoepfer.info  Mon Jun 12 05:57:52 2023
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 12 Jun 2023 07:57:52 +0200
Subject: [Slackbuilds-users] Fwd: jhead on SBo
In-Reply-To: <13961b787226630a7e30c89a0583da1a@schoepfer.info>
References: <13961b787226630a7e30c89a0583da1a@schoepfer.info>
Message-ID: <2de88079fe3899661cdc30d14f7e13f3@schoepfer.info>

Forwarding to this list, since i got no reply from the maintainer.
Somewhere i saw that he's not active, but i'm not sure if taking over 
maintenance
is ok without feedback.


-------- Originalnachricht --------
Betreff: jhead on SBo
Datum: 2023-05-17 08:36
Von: Franzen <slackbuilds at schoepfer.info>
An: baildon.research at googlemail.com

Hi,

the jhead version on SBo is a few years behind, the project has moved to
https://github.com/Matthias-Wandel/jhead

Do you plan to update?

Cheers,

Johannes

From slackbuilds at schoepfer.info  Tue Jun 13 05:42:52 2023
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 13 Jun 2023 07:42:52 +0200
Subject: [Slackbuilds-users] unmaintained SlackBuilds
Message-ID: <667591f64ad036a6a7e3d03353c757d1@schoepfer.info>

Hi,

dear SBo-admins,
may I assume that Steven King is not maintaining his builds anymore, and 
that anybody may take these? Since over 6 years no commit. A few months 
ago a asked him via mail and got no response.
https://git.slackbuilds.org/slackbuilds/log/?h=15.0&qt=author&q=kingrst%40gmail.com

Cheers,
Johannes

From urchlay at slackware.uk  Tue Jun 13 06:19:24 2023
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 13 Jun 2023 02:19:24 -0400 (EDT)
Subject: [Slackbuilds-users] unmaintained SlackBuilds
In-Reply-To: <667591f64ad036a6a7e3d03353c757d1@schoepfer.info>
References: <667591f64ad036a6a7e3d03353c757d1@schoepfer.info>
Message-ID: <c0f1416f-839e-5bc7-124-aa4c96a886@slackware.uk>



On Tue, 13 Jun 2023, Franzen via SlackBuilds-users wrote:

> may I assume that Steven King is not maintaining his builds anymore, and that 
> anybody may take these? Since over 6 years no commit. A few months ago a 
> asked him via mail and got no response.

Yes, feel free to take them over. This goes for anyone else who wants
any of them, too.

The full list:

libraries/iniparser
libraries/log4c
network/aiccu
network/csync
network/dkimproxy
network/httping
network/mailman
network/webalizer
python/python2-pydns
python/python2-pypolicyd-spf
python/python2-pyspf
system/newrelic-sysmond

From j at lngn.net  Tue Jun 13 06:22:45 2023
From: j at lngn.net (J)
Date: Tue, 13 Jun 2023 02:22:45 -0400
Subject: [Slackbuilds-users] Fwd:  unmaintained SlackBuilds
In-Reply-To: <c0f1416f-839e-5bc7-124-aa4c96a886@slackware.uk>
References: <667591f64ad036a6a7e3d03353c757d1@schoepfer.info>
 <c0f1416f-839e-5bc7-124-aa4c96a886@slackware.uk>
Message-ID: <AEC17C33-B3A4-4FD6-A393-D02220A4420A@edison.tech>

      
  

 Just want to point out that from this list ?iniparser? 4.1 is included in -current for any would-be taker-overs.   
  
  
  
? Jay Lanagan
  
  
  

  
 Begin forwarded message:
  
  
>   
> From:  B. Watson  <urchlay at slackware.uk (mailto:urchlay at slackware.uk)>
>   Date:  Jun 13, 2023 at 2:19 AM
>   To:  Franzen via SlackBuilds-users  <slackbuilds-users at slackbuilds.org (mailto:slackbuilds-users at slackbuilds.org)>
>   Subject: Re: [Slackbuilds-users] unmaintained SlackBuilds
>   
>   
>   
>  On Tue, 13 Jun 2023, Franzen via SlackBuilds-users wrote:  >  may I assume that Steven King is not maintaining his builds anymore, and that  >  anybody may take these? Since over 6 years no commit. A few months ago a  >  asked him via mail and got no response. Yes, feel free to take them over. This goes for anyone else who wants any of them, too. The full list: libraries/iniparser libraries/log4c network/aiccu network/csync network/dkimproxy network/httping network/mailman network/webalizer python/python2-pydns python/python2-pypolicyd-spf python/python2-pyspf system/newrelic-sysmond _______________________________________________ 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/20230613/d68455de/attachment.htm>

From slackbuilds at schoepfer.info  Tue Jun 13 08:20:58 2023
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 13 Jun 2023 10:20:58 +0200
Subject: [Slackbuilds-users] unmaintained SlackBuilds
In-Reply-To: <c0f1416f-839e-5bc7-124-aa4c96a886@slackware.uk>
References: <667591f64ad036a6a7e3d03353c757d1@schoepfer.info>
 <c0f1416f-839e-5bc7-124-aa4c96a886@slackware.uk>
Message-ID: <5A12161A-64B5-4C53-AE91-F1FDB66AC553@schoepfer.info>

Then i'll take webalizer

Am 13. Juni 2023 08:19:24 MESZ schrieb "B. Watson" <urchlay at slackware.uk>:
>
>
>On Tue, 13 Jun 2023, Franzen via SlackBuilds-users wrote:
>
>> may I assume that Steven King is not maintaining his builds anymore, and that anybody may take these? Since over 6 years no commit. A few months ago a asked him via mail and got no response.
>
>Yes, feel free to take them over. This goes for anyone else who wants
>any of them, too.
>
>The full list:
>
>libraries/iniparser
>libraries/log4c
>network/aiccu
>network/csync
>network/dkimproxy
>network/httping
>network/mailman
>network/webalizer
>python/python2-pydns
>python/python2-pypolicyd-spf
>python/python2-pyspf
>system/newrelic-sysmond
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230613/de555512/attachment-0001.htm>

From arnaud.garcia-fernandez at laposte.net  Tue Jun 13 08:33:15 2023
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Tue, 13 Jun 2023 10:33:15 +0200
Subject: [Slackbuilds-users] unmaintained SlackBuilds
In-Reply-To: <5A12161A-64B5-4C53-AE91-F1FDB66AC553@schoepfer.info>
References: <667591f64ad036a6a7e3d03353c757d1@schoepfer.info>
 <c0f1416f-839e-5bc7-124-aa4c96a886@slackware.uk>
 <5A12161A-64B5-4C53-AE91-F1FDB66AC553@schoepfer.info>
Message-ID: <20230613103315.4c853bd8c6ac2c6870f4a2f9@laposte.net>

I am very ok to take over dkimproxy, since I use it, mailman also.

Cheers,

	- Yth.


> Then i'll take webalizer
> 
> Am 13. Juni 2023 08:19:24 MESZ schrieb "B. Watson" <urchlay at slackware.uk>:
> >
> >
> >On Tue, 13 Jun 2023, Franzen via SlackBuilds-users wrote:
> >
> >> may I assume that Steven King is not maintaining his builds anymore, and
> >> that anybody may take these? Since over 6 years no commit. A few months ago
> >> a asked him via mail and got no response.
> >
> >Yes, feel free to take them over. This goes for anyone else who wants
> >any of them, too.
> >
> >The full list:
> >
> >libraries/iniparser
> >libraries/log4c
> >network/aiccu
> >network/csync
> >network/dkimproxy
> >network/httping
> >network/mailman
> >network/webalizer
> >python/python2-pydns
> >python/python2-pypolicyd-spf
> >python/python2-pyspf
> >system/newrelic-sysmond



From jebrhansen+SBo at gmail.com  Tue Jun 13 16:50:16 2023
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Tue, 13 Jun 2023 09:50:16 -0700
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <4520-647d1f80-d-6333f@58583900>
References: <4520-647d1f80-d-6333f@58583900>
Message-ID: <CANi9qSuprT01p1xjOuh0kmka-2q94GJgiaokkW6kd-6zq6rDPg@mail.gmail.com>

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

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

Jeremy

On Sun, Jun 4, 2023 at 4:34?PM isaacyu1 at isaacyu1.com <isaacyu1 at isaacyu1.com>
wrote:

> Hi everyone,
>
> ?????I now have 200+ SlackBuilds to maintain.
> Given my part-time job and my coursework, I am going to have a harder time
> maintaining it all.
>
> This is the last week in which I will maintain and update SlackBuilds.
>
> I will also switch my email address (on SlackBuilds) to
> isaacyu at protonmail.com:
> https://github.com/SlackBuildsOrg/slackbuilds/pull/2898
>
> I need to pay a small yearly subscription fee (to Gandi, the company) for
> the isaacyu1.com domain. However, the ProtonMail email service is free.
> Hence the email address change.
>
> My SlackBuilds are available at the following link:
> https://github.com/isaackwy/slackbuilds-15.0
>
> I plan on switching to Debian.
> Debian 12 (Bookworm) will be released in a few days, on June 10.
>
> - Isaac _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users 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/20230613/7b95c4ee/attachment.htm>

From urchlay at slackware.uk  Tue Jun 13 22:19:35 2023
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 13 Jun 2023 18:19:35 -0400 (EDT)
Subject: [Slackbuilds-users] wterm
Message-ID: <a78ee07e-8858-58b0-65e2-d7daf1344c36@slackware.uk>


Does anyone here use wterm?

Its maintainer has been inactive for ~5 years (for all of his builds,
not just wterm). Upstream hasn't done a release, so we have the latest
version of wterm...

If you build it, you'll notice it doesn't actually build correctly:
the compile fails (but doesn't kill the script) and you end up with a
package consisting only of man pages and documentation.

It's trivial to fix. But, it's been broken since 15.0 released (about
a year and a half now) and nobody's complained.

Does anyone want this build? I can update it with my fixes and put
your name as maintainer in the .info file.

From jebrhansen+SBo at gmail.com  Thu Jun 15 17:01:20 2023
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Thu, 15 Jun 2023 10:01:20 -0700
Subject: [Slackbuilds-users] Submission pending approval after removal
Message-ID: <CANi9qSsUAOxn=Z09kDBfVpQnT7JLpLZNCusEt=C5W=W=E=6fTg@mail.gmail.com>

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

I got the following error:

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

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

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

Thanks!
Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230615/b5c08348/attachment.htm>

From majors at majors.email  Thu Jun 15 17:29:56 2023
From: majors at majors.email (Majors)
Date: Thu, 15 Jun 2023 10:29:56 -0700
Subject: [Slackbuilds-users] Next week,
 I will no longer maintain and update SlackBuilds
In-Reply-To: <CANi9qSuprT01p1xjOuh0kmka-2q94GJgiaokkW6kd-6zq6rDPg@mail.gmail.com>
Message-ID: <68d06e21-1c72-4480-bca8-d15721d5c02d@email.android.com>

An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230615/45ef8cc8/attachment.htm>

From willysr at slackbuilds.org  Thu Jun 15 18:21:55 2023
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 16 Jun 2023 01:21:55 +0700
Subject: [Slackbuilds-users] Submission pending approval after removal
In-Reply-To: <CANi9qSsUAOxn=Z09kDBfVpQnT7JLpLZNCusEt=C5W=W=E=6fTg@mail.gmail.com>
References: <CANi9qSsUAOxn=Z09kDBfVpQnT7JLpLZNCusEt=C5W=W=E=6fTg@mail.gmail.com>
Message-ID: <6ce9ffb4-d127-edee-2778-ab71efd13282@slackbuilds.org>

> I removed the submission of python3-tus.py after I realized I used a poorly
> formatted download url. It was still sitting in the pending queue, so I
> removed it following the instructions in the submission email, corrected
> the .info file, recreated the tarball and tried to upload it again.
> 
> I got the following error:
> 
> File exists; a submission by the name 'python3-tus.py' is already pending
> approval.
> 
> This should not be a dependency of any other programs that were submitted
> (but it is a dependency of a program I'm working to submit later this week
> or next).
> 
> Can an admin please do their thing so I can reupload this tarball?

done

-- 
Willy Sudiarto Raharjo

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

From for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net  Fri Jun 16 06:00:52 2023
From: for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net (Lockywolf)
Date: Fri, 16 Jun 2023 14:00:52 +0800
Subject: [Slackbuilds-users] LanguageTool SlackBuild
Message-ID: <87bkhg3pxh.fsf@laptop.lockywolf.net>

Hello, everyone,

Dimitris Zlatanidis agreed that I take over the maintenance of the
LanguageTool Slackbuild.


-- 
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)

From tonus1 at free.fr  Fri Jun 16 20:54:33 2023
From: tonus1 at free.fr (Tonus)
Date: Fri, 16 Jun 2023 22:54:33 +0200
Subject: [Slackbuilds-users] spyder missing deps
Message-ID: <4g5yoh3zm3ev3364w54lq5esrpay6neqrtjhiy5g33skjyixhl@ss7vbob5cx5e>

Hi list,

In my tests for yapf downgrade, I had to build and try to run spyder.
I hited a few missing deps when tried to run it on clean and up-to-date 
Slackware64-15 : 
python3-textdistance,python3-pydocstyle,QDarkStyle,jupyter-qtconsole,ipython-genutils

I've cc'ed the maintainer.

If I'm not mistaken, hope that helps.

-- 
Regards,

Tonus

From willysr at slackbuilds.org  Sat Jun 17 00:25:01 2023
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 17 Jun 2023 07:25:01 +0700
Subject: [Slackbuilds-users] argyllcms tarball not found 404.
In-Reply-To: <CALrQ46AAD=EHFAEN+S8EKgMSnE7Q3wVgtu+AcuATcEj27E2wVQ@mail.gmail.com>
References: <CALrQ46AAD=EHFAEN+S8EKgMSnE7Q3wVgtu+AcuATcEj27E2wVQ@mail.gmail.com>
Message-ID: <50068a1a-5f1b-d874-db77-57de32b926b3@slackbuilds.org>

> --2023-06-11 06:38:46--  http://argyllcms.com/Argyll_V2.0.1_src.zip
> Resolving argyllcms.com (argyllcms.com)... 43.250.142.86
> Connecting to argyllcms.com (argyllcms.com)|43.250.142.86|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2023-06-11 06:38:47 ERROR 404: Not Found.

Fixed it on my branch by bumping to 2.3.1
the maintainers seems inactive, so if you are using argyllcms, please 
step up to be maintainer


-- 
Willy Sudiarto Raharjo

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

From fernando.lopezjr at gmail.com  Sat Jun 17 04:06:32 2023
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Fri, 16 Jun 2023 23:06:32 -0500
Subject: [Slackbuilds-users] argyllcms tarball not found 404.
In-Reply-To: <50068a1a-5f1b-d874-db77-57de32b926b3@slackbuilds.org>
References: <CALrQ46AAD=EHFAEN+S8EKgMSnE7Q3wVgtu+AcuATcEj27E2wVQ@mail.gmail.com>
 <50068a1a-5f1b-d874-db77-57de32b926b3@slackbuilds.org>
Message-ID: <CALrQ46CVdkAyyh__jThxJcKr6xhK-zJdR9j7GO_J2CZORs2MTQ@mail.gmail.com>

sure, I would like to maintain this package. thank you.

On Fri, Jun 16, 2023 at 7:25?PM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > --2023-06-11 06:38:46--  http://argyllcms.com/Argyll_V2.0.1_src.zip
> > Resolving argyllcms.com (argyllcms.com)... 43.250.142.86
> > Connecting to argyllcms.com (argyllcms.com)|43.250.142.86|:80...
> connected.
> > HTTP request sent, awaiting response... 404 Not Found
> > 2023-06-11 06:38:47 ERROR 404: Not Found.
>
> Fixed it on my branch by bumping to 2.3.1
> the maintainers seems inactive, so if you are using argyllcms, please
> step up to be maintainer
>
>
> --
> 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/
>
>

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230616/d886be10/attachment.htm>

From willysr at slackbuilds.org  Sat Jun 17 10:38:02 2023
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 17 Jun 2023 17:38:02 +0700
Subject: [Slackbuilds-users] Updates - 20230617.1
Message-ID: <704b196b-3bf8-11e6-fa79-8580f4985c8d@slackbuilds.org>

Hi all

Just heads up that next week public update will be pushed 1 day earlier
Also reminder to all maintainers to check their scripts using 
sbo-maintainer-tools before submitting new version.


Sat Jun 17 10:19:43 UTC 2023
academic/FreeFem: Updated for version 4.13.
academic/python3-scipy: New maintainer
academic/xsimd: New maintainer
audio/ncspot: Updated for version 0.13.3.
desktop/Tela-icon-theme: Update script.
desktop/qtile: updated REQUIRES
desktop/recoll: Updated for version 1.34.4.
desktop/sun: Updated homepage.
development/composer: Updated for version 2.5.8
development/csmith: Added (generates random C programs).
development/hhvm: Updated for version 4.168.2
development/hugo: Updated for version 0.113.0
development/jdk: Updated for version 8u371.
development/php82: Updated for version 8.2.7
development/rust16: Updated for version 1.69.0.
development/universal-ctags: Updated for version p6.0.20230611.0
development/vscode-bin: Updated for version 1.79.2.
development/vscodium: Updated for version 1.79.0.23159.
games/PrismLauncher: Updated for version 7.1.
graphics/CairoSVG: updated REQUIRES
graphics/blockbench: Added (3D Model Editor).
graphics/jhead: Updated for version 3.08.
graphics/libplacebo: README correction
graphics/vuescan: Updated for version 9.8.03.
ham/hackrf: Updated for version 2023.01.1, moved from development.
libraries/VTK: Patch for gcc13
libraries/libde265: Updated for version 1.0.12.
libraries/pymediainfo: Updated for version 6.0.1.
libraries/qt-jpegxl-image-plugin: Updated for version 0.4.3.
libraries/rarfile: Updated for version 4.0.
libraries/webrtc-audio-processing: Update source.
libraries/zeromq: New maintainer
misc/open-simh: Updated for version 8b6c0b6.
multimedia/QMPlay2: Updated for version 23.06.04.
multimedia/makemkv: Update DOWNLOAD urls.
network/AdGuardHome: Updated for version 0.107.32.
network/Electrum: Updated for version 4.4.4
network/brave-browser: Updated for version 1.52.126.
network/dkimproxy: New maintainer
network/dropbox: Updated for version 176.4.5108.
network/ejabberd: Fix rc.ejabberd.
network/mailman: Switched to Python3. New maintainer.
network/microsoft-edge: update 114.0.1823.43
network/nextcloud-desktop: updated for version 3.9.0
network/signal-desktop: Updated for version 6.21.0.
network/slack: Updated for version 4.32.127.
network/telegram: Updated for version 4.8.4.
network/vivaldi: Updated for version 6.1.3035.84.
network/webalizer: new maintainer.
office/LanguageTool: Updated for version 6.1.
office/asymptote: Updated for version 2.86.
office/calibre-bin: Updated for version 6.21.0.
office/focuswriter-qt6: Added (distraction-free word processor).
office/focuswriter: New maintainer
office/lotus123: Added (Lotus 1-2-3 for Linux).
office/onlyoffice-desktopeditors: Updated for version 7.4.0.
office/pandoc-bin: Updated for version 3.1.3.
perl/perl-Mojolicious: Updated for version 9.33.
python/BeautifulSoup4: Updated for version 2.4.1.
python/breathe: Updated for version 4.35.0.
python/cairocffi: Removed (renamed to python3-cairocffi).
python/click-didyoumean: Removed (renamed to python3-click-didyoumean)
python/cppy: New maintainer
python/esptool: Updated for version 4.6.2.
python/freetype-py: Added (High level Python API).
python/insipid-sphinx-theme: Updated for version 0.4.1.
python/ipython: New maintainer
python/pallets-sphinx-theme: Updated for version 2.1.1.
python/pickleshare: New maintainer
python/python-cachetools: Added (Extensible memoizing collections)
python/python-gntp: Added (GNTP Python Library)
python/python2-pyasn1: New maintainer
python/python3-PyGithub: Added (Typed interactions with github).
python/python3-asn1crypto: New maintainer
python/python3-atomicwrites: New maintainer
python/python3-autobahn: updated for version 23.6.2
python/python3-beekeeper-alt: Added (generate RESTful interfaces)
python/python3-beniget: New maintainer
python/python3-black: updated for version 23.3.0. New maintainer
python/python3-cacheyou: Added (httplib2 caching algorithms).
python/python3-cairocffi: Added (cffi-based cairo for Python).
python/python3-celery: updated for version 5.3.0
python/python3-cinemagoer: Added (retrieve and manage IMDb data).
python/python3-click-didyoumean: Added (python module).
python/python3-colorlog: Added (Log formatting with colors).
python/python3-deluge-client: Added (Deluge RPC Client).
python/python3-deprecated: Added (deprecated decorators).
python/python3-deprecation: New maintainer
python/python3-dnspython: Added (Python API for DNS).
python/python3-dogpile.cache: Added (caching interfacce).
python/python3-dulwich: fix wrong build using updated setuptools
python/python3-enzyme: Added (Python video metadata parser).
python/python3-executing: New maintainer
python/python3-fanart: Added (fanart.tv API client).
python/python3-gast: New maintainer
python/python3-ifaddr: Added (Enumerate all interfaces).
python/python3-iniconfig: New maintainer
python/python3-jedi: New maintainer
python/python3-joblib: New maintainer
python/python3-kiwisolver: New maintainer
python/python3-kodipydent: Added (client for kodi json-rpc api).
python/python3-kombu: updated for version 5.3.0
python/python3-librosa: Added (python audio and music library).
python/python3-matplotlib-inline: New maintainer
python/python3-new-rtorrent: Added (rTorrent interface).
python/python3-pandas: New maintainer
python/python3-pdm-backend: Added (Backend for PDM projects).
python/python3-pdm: Added (python package manager).
python/python3-pluggy: New maintainer
python/python3-pure_eval: New maintainer
python/python3-putio.py: Added (wrapper for put.io APIv2).
python/python3-py: New maintainer
python/python3-pyasn1: New maintainer
python/python3-pynma: Added (Python NotifyMyAndroid notification).
python/python3-pyproject-api: Added (api for pyproject.toml).
python/python3-pysrt: Added (Parser for srt files).
python/python3-pytest-runner: New maintainer
python/python3-pytest: New maintainer
python/python3-qbittorrent-api: Added (client for qbittorent).
python/python3-reportlab: Updated for 3.6.13, moved from libraries.
python/python3-service-identity: updated for version 23.1.0
python/python3-setuptools-opt: Added (setuptools from -current).
python/python3-setuptools-rust-opt: Added (plugin for setuptools).
python/python3-slugify: New maintainer
python/python3-soupsieve: Updated for version 2.4.1.
python/python3-stack_data: New maintainer
python/python3-stevedore: Added (Manage dynamic plugins).
python/python3-text-unidecode: New maintainer
python/python3-threadpoolctl: New maintainer
python/python3-timeago: Added (format datetime).
python/python3-tmdbsimple: Added (Wrapper for TMDB v3).
python/python3-tornado: New maintainer
python/python3-tox: Added (task automation tool).
python/python3-tus.py: Added (tus client for python).
python/python3-ufolib2: Added (UFO library and API).
python/python3-uharfbuzz: Added (Cython bindings for HarfBuzz).
python/python3-validators: Added (Data Validations).
python/python3-xmltodict: Added (XML feel like JSON).
python/rst2pdf: Updated for version 0.100.
python/scikit-learn: New maintainer
python/send2trash: New maintainer
python/sphinx-last-updated-by-git: Updated for version 0.3.5.
python/subliminal: Added (subtitle library).
python/thonny: Updated for version 4.1.1.
python/traitlets: New maintainer
python/typing-extensions: New maintainer
python/yapf: downgrade to keep sync with Slackware's tomli version
system/B-em: Added (BBC Microcomputer Emulator).
system/DisplayCAL: Added (display calibration and profiling).
system/argyllcms: Updated for version 2.3.1.
system/bottom: Updated for version 0.9.2.
system/fzf: Updated for version 0.42.0.
system/gimp-help: Updated for version 2.10.34.
system/image-analyzer: updated REQUIRES
system/jdupes: updated for version 1.24.0
system/netdata: Updated for version 1.40.0.
system/nvidia-driver: Updated for version 535.54.03.
system/nvidia-kernel: Updated for version 535.54.03.
system/nvidia-open-kernel: Updated for version 535.54.03.
system/rxvt: Added (terminal emulator).
system/sbo-create: Updated homepage.
system/tewi-font: Added (small bitmap font).
system/unrtf: Updated for version 0.21.10.
system/winetricks: New maintainer
system/xen-nox: Updated for version 4.17.0.
+--------------------------+


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

From slackbuilds at schoepfer.info  Sat Jun 17 18:05:36 2023
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 17 Jun 2023 20:05:36 +0200
Subject: [Slackbuilds-users]
 icon-theme.cache/doinst.sh(template)/sbo-maintainer-tools
Message-ID: <cb2ce7039580df15f423aa0aab8b6634@schoepfer.info>

Hi all,

the content of a icon-file-cache(icon-theme.cache) like
/usr/share/icons/ICON_DIRECTORY/icon-theme.cache
depends on the tool "gtk-update-icon-cache".
Also all present icon caches like
/usr/share/icons/{ICON_DIRECTORY1,ICON_DIECTORY2}/icon-theme.cache
are regenerated at boot by /etc/rc.d/rc.M.
So, i think icon-theme.cache in the icon-directory should never be 
present in a package.

-> sbo-maintainer-tools might check that presence
-> sbo-maintainer-tools might warn if /usr/share/icons/ICON_DIRECTORY/
is present, but doinst.sh does not call gtk-update-icon-cache

The SBo doinst.sh-template says:
if [ -e usr/share/icons/hicolor/icon-theme.cache ]; then
   if [ -x /usr/bin/gtk-update-icon-cache ]; then
     /usr/bin/gtk-update-icon-cache -f usr/share/icons/hicolor >/dev/null 
2>&1
   fi
fi

The logic to regenerate the cache if the cache is present does not make 
sense to me,
the cache should simply be (re)generated on installation.
->
if [ -x /usr/bin/gtk-update-icon-cache ]; then
   /usr/bin/gtk-update-icon-cache -f usr/share/icons/ICON_DIRECTORY 
 >/dev/null 2>&1
fi

That said, it seems a lot of builds use the example from doinst.sh with
usr/share/icons/hicolor, which does not make sense at all if there is no 
icon
in usr/share/icons/hicolor in the package.
Maybe sbo-maintainer-tools should also check for that.

What do you think? Feedback is welcome, thanks!

Cheers,

Johannes

From urchlay at slackware.uk  Sat Jun 17 19:20:37 2023
From: urchlay at slackware.uk (B. Watson)
Date: Sat, 17 Jun 2023 15:20:37 -0400 (EDT)
Subject: [Slackbuilds-users]
 icon-theme.cache/doinst.sh(template)/sbo-maintainer-tools
In-Reply-To: <cb2ce7039580df15f423aa0aab8b6634@schoepfer.info>
References: <cb2ce7039580df15f423aa0aab8b6634@schoepfer.info>
Message-ID: <4a7a43a8-502e-1e55-92c8-b39dd832172@slackware.uk>



On Sat, 17 Jun 2023, Franzen via SlackBuilds-users wrote:

> Hi all,
>
> the content of a icon-file-cache(icon-theme.cache) like
> /usr/share/icons/ICON_DIRECTORY/icon-theme.cache
> depends on the tool "gtk-update-icon-cache".
> Also all present icon caches like
> /usr/share/icons/{ICON_DIRECTORY1,ICON_DIECTORY2}/icon-theme.cache
> are regenerated at boot by /etc/rc.d/rc.M.

Almost right. The caches only get regenerated if they already exist.
The code:

if find /usr/share/icons -maxdepth 2 2> /dev/null | grep -q icon-theme.cache ; then
   for theme_dir in /usr/share/icons/* ; do
     if [ -r ${theme_dir}/icon-theme.cache ]; then
       echo "Updating icon-theme.cache in ${theme_dir}..."
       /usr/bin/gtk-update-icon-cache -t -f ${theme_dir} 1> /dev/null 2> /dev/null &
     fi
   done

...and, by default, the caches *don't* exist, on a fresh
Slackware install. They only get created if the user manually runs
gtk-update-icon-cache to create them the first time [*].

That's why our doinst.sh has the "if [ -e usr/share/icons/hicolor/icon-theme.cache ];"

[*] We do have some builds which unconditionally create the icon
cache. These are errors, and should be fixed (and will be, this
week). One of them is games/steam, if you want an example. Probably I
will add a check to sbolint for this, too.

> So, i think icon-theme.cache in the icon-directory should never be present in 
> a package.

Correct. sbopkglint already checks for this, in predoinst.sh.

> -> sbo-maintainer-tools might check that presence
> -> sbo-maintainer-tools might warn if /usr/share/icons/ICON_DIRECTORY/
> is present, but doinst.sh does not call gtk-update-icon-cache

It does this, but only for hicolor.

> The logic to regenerate the cache if the cache is present does not make sense 
> to me,
> the cache should simply be (re)generated on installation.

Nope, see above.

> That said, it seems a lot of builds use the example from doinst.sh with
> usr/share/icons/hicolor, which does not make sense at all if there is no icon
> in usr/share/icons/hicolor in the package.
> Maybe sbo-maintainer-tools should also check for that.

sbopkglint does check this. Again, only for hicolor.

> What do you think? Feedback is welcome, thanks!

It might be worthwhile to have it check all icon dirs it finds,
rather than just hicolor. The vast majority of our packages only
install icons in hicolor (exceptions being *-icon-theme packages), so
I haven't worried too much about it...

From slackbuilds at schoepfer.info  Sun Jun 18 08:18:58 2023
From: slackbuilds at schoepfer.info (Franzen)
Date: Sun, 18 Jun 2023 10:18:58 +0200
Subject: [Slackbuilds-users]
 icon-theme.cache/doinst.sh(template)/sbo-maintainer-tools
In-Reply-To: <4a7a43a8-502e-1e55-92c8-b39dd832172@slackware.uk>
References: <cb2ce7039580df15f423aa0aab8b6634@schoepfer.info>
 <4a7a43a8-502e-1e55-92c8-b39dd832172@slackware.uk>
Message-ID: <593f427245966eef1d446c09186d6b5f@schoepfer.info>

Thanks B. Watson for the clarifications, and for the very helpful 
sbo-maintainer-tools.

I found a post from Robby which explains why the cache is not used by 
default:
https://www.linuxquestions.org/questions/slackware-14/xfce-complains-about-missing-cache-file-for-icon-themes-pkgtool-does-not-help-4175667481/#post6077375

I then wonder why the cache is checked on every boot, as this seems only 
needed once when systemwide icons are added(ususally by a package).
And why does the slackware-installer then deals with the cache, as there 
can't be one
on a fresh installation, 
/var/lib/pkgtools/setup/setup.08.gtk-update-icon-cache
But that's better asked at LQ i guess.

Johannes

From urchlay at slackware.uk  Sun Jun 18 08:36:23 2023
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 18 Jun 2023 04:36:23 -0400 (EDT)
Subject: [Slackbuilds-users]
 icon-theme.cache/doinst.sh(template)/sbo-maintainer-tools
In-Reply-To: <593f427245966eef1d446c09186d6b5f@schoepfer.info>
References: <cb2ce7039580df15f423aa0aab8b6634@schoepfer.info>
 <4a7a43a8-502e-1e55-92c8-b39dd832172@slackware.uk>
 <593f427245966eef1d446c09186d6b5f@schoepfer.info>
Message-ID: <6bbe7fbc-ed9d-117f-66c4-1c3ef61eb0b@slackware.uk>



On Sun, 18 Jun 2023, Franzen wrote:

> And why does the slackware-installer then deals with the cache, as there 
> can't be one
> on a fresh installation, 
> /var/lib/pkgtools/setup/setup.08.gtk-update-icon-cache

Look at the comments in that file:

# This is needed since XFce adds a few hicolor icons that would
# not otherwise be cached.  Really, I'm not sure the idea of
# caching icons is a good one -- the use of gtk-update-icon-cache
# could disappear from future install scripts.

...a bit lower down:

if [ -e usr/share/icons/hicolor/icon-theme.cache ]; then # ONLY run this is there's already a cache!!!

Not sure if that clarifies anything or further confuses the issue.

From thymkal at gmx.com  Sun Jun 18 09:24:14 2023
From: thymkal at gmx.com (=?UTF-8?Q?=CE=95=CF=85=CE=B8=CF=8D=CE=BC=CE=B9=CE=BF=CF=82_?= =?UTF-8?Q?=CE=9A=CE=B1=CE=BB=CE=BF=CE=BC=CE=BF=CE=AF=CF=81?= =?UTF-8?Q?=CE=B7=CF=82?=)
Date: Sun, 18 Jun 2023 09:24:14 +0000
Subject: [Slackbuilds-users] Fwd: rawtherapee newer version
In-Reply-To: <31a018d0-4465-3f04-2e7b-0bfe5aa79805@gmx.com>
References: <31a018d0-4465-3f04-2e7b-0bfe5aa79805@gmx.com>
Message-ID: <1687080086705.67425425.1887787024@gmx.com>

Hi,
maybe consider the following upgrade (rawtherapee 5.8 --> 5.9). 


(Forwarding to this list, since i got no reply from the maintainer)


Thank you

----- ?????????? ?????? -----
???: Efthymis Kalomoiris <thymkal at gmx.com>
????: hostmaster at slackonly.com
????: rawtherapee newer version
??????????: ?????? 23 ??????? 2023 09:16:49 ?? (+02:00)




Hi,

just a suggestion for using the newest version (namely 5.9, https://rawtherapee.com/shared/source/rawtherapee-5.9.tar.xz ).

I have built it myself based on your slackbuild, several weeks ago, and it works fine.


(5.8 was released ~3 years ago. New version brings some long anticipated features.)


Thank you


Efthymis





--


Sent from my Slackware

https://docs.slackware.com/

using thunderbird

https://www.thunderbird.net/el/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230618/0420ed05/attachment.htm>

From sbo at linuxgalaxy.org  Mon Jun 19 02:46:26 2023
From: sbo at linuxgalaxy.org (KB_SBo)
Date: Mon, 19 Jun 2023 02:46:26 +0000
Subject: [Slackbuilds-users] Solaar gui fails to run
Message-ID: <307fbc38-ad45-27a0-b27b-19dd43085bfa@linuxgalaxy.org>

Hello all,

I'm trying to an old logitech keyboard paired to another receiver - lost 
the original.  When running the GUI version the negative result is

$ solaar
solaar: error: Traceback (most recent call last):
   File "/usr/lib64/python3.9/site-packages/solaar/gtk.py", line 165, in 
main
     import solaar.listener as listener
   File "/usr/lib64/python3.9/site-packages/solaar/listener.py", line 
34, in <module>
     from logitech_receiver import notifications as _notifications
   File 
"/usr/lib64/python3.9/site-packages/logitech_receiver/notifications.py", 
line 27, in <module>
     from . import diversion as _diversion
   File 
"/usr/lib64/python3.9/site-packages/logitech_receiver/diversion.py", 
line 33, in <module>
     import psutil
   File "/usr/lib64/python3.9/site-packages/psutil/__init__.py", line 
102, in <module>
     from . import _pslinux as _psplatform
   File "/usr/lib64/python3.9/site-packages/psutil/_pslinux.py", line 
87, in <module>
     PAGESIZE = cext_posix.getpagesize()
AttributeError: module 'psutil._psutil_posix' has no attribute 'getpagesize'


I used 'slpkg' and it looks like all was built in the right order 
(unless I missed something):

   ? python3-flit_core.SlackBuild ??
   ? python3-flit_core-3.9.0-x86_64-1_SBo.tgz ??
   ? python3-installer.SlackBuild ??
   ? python3-installer-0.7.0-x86_64-1_SBo.tgz ??
   ? python3-pyproject-hooks.SlackBuild ??
   ? python3-pyproject-hooks-1.0.0-x86_64-1_SBo.tgz ??
   ? python3-wheel.SlackBuild ??
   ? python3-wheel-0.40.0-x86_64-1_SBo.tgz ??
   ? python3-build.SlackBuild ??
   ? python3-build-0.10.0-x86_64-1_SBo.tgz ??
   ? python3-psutil.SlackBuild ??
   ? python3-psutil-5.9.5-x86_64-1_SBo.tgz ??
   ? python3-xlib.SlackBuild ??
   ? python3-xlib-0.33-x86_64-1_SBo.tgz ??
   ? pyudev.SlackBuild ??
   ? pyudev-0.24.1-x86_64-1_SBo.tgz ??
   ? python-evdev.SlackBuild ??
   ? python-evdev-1.6.1-x86_64-1_SBo.tgz ??
   ? Solaar.SlackBuild ??
   ? Solaar-1.1.9-x86_64-1_SBo.tgz ??

Command line work exit for "pair" (did not test "config")

$ solaar pair
solaar: error: Traceback (most recent call last):
   File "/usr/lib64/python3.9/site-packages/solaar/cli/__init__.py", 
line 208, in run
     m = import_module('.' + action, package=__name__)
   File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in 
import_module
     return _bootstrap._gcd_import(name[level:], package, level)
   File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
   File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
   File "<frozen importlib._bootstrap>", line 986, in 
_find_and_load_unlocked
   File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
   File "<frozen importlib._bootstrap_external>", line 850, in exec_module
   File "<frozen importlib._bootstrap>", line 228, in 
_call_with_frames_removed
   File "/usr/lib64/python3.9/site-packages/solaar/cli/pair.py", line 
23, in <module>
     from logitech_receiver import notifications as _notifications
   File 
"/usr/lib64/python3.9/site-packages/logitech_receiver/notifications.py", 
line 27, in <module>
     from . import diversion as _diversion
   File 
"/usr/lib64/python3.9/site-packages/logitech_receiver/diversion.py", 
line 33, in <module>
     import psutil
   File "/usr/lib64/python3.9/site-packages/psutil/__init__.py", line 
102, in <module>
     from . import _pslinux as _psplatform
   File "/usr/lib64/python3.9/site-packages/psutil/_pslinux.py", line 
87, in <module>
     PAGESIZE = cext_posix.getpagesize()
AttributeError: module 'psutil._psutil_posix' has no attribute 'getpagesize'

-kb








From fourtysixandtwo at sliderr.net  Mon Jun 19 06:21:33 2023
From: fourtysixandtwo at sliderr.net (fourtysixandtwo)
Date: Mon, 19 Jun 2023 00:21:33 -0600
Subject: [Slackbuilds-users] Solaar gui fails to run
In-Reply-To: <307fbc38-ad45-27a0-b27b-19dd43085bfa@linuxgalaxy.org>
References: <307fbc38-ad45-27a0-b27b-19dd43085bfa@linuxgalaxy.org>
Message-ID: <CAAZ8Hahk5UpYvbSBiPceXC4B7q4WO5cFvmMJXVJ-9Z5e3Z6e=w@mail.gmail.com>

Doing a bit of digging I see Willy reported a similar issue back in Nov.
Maybe he can chime in?  But it seems to have fixed itself.
https://github.com/giampaolo/psutil/issues/2181

The author talks about it possibly finding "_psutil_posix.so" in the path,
but it's only installed in the python2 version.  Do you have python2-psutil
or the old psutil slackbuild still installed?  I would try removing them
and reinstalling python3-psutil.  I would also check if you have any pip
installed packages.

I can't get anything to fail here, both solaar and locust build and run
without errors.


On Sun, Jun 18, 2023 at 8:46?PM KB_SBo <sbo at linuxgalaxy.org> wrote:

> Hello all,
>
> I'm trying to an old logitech keyboard paired to another receiver - lost
> the original.  When running the GUI version the negative result is
>
> $ solaar
> solaar: error: Traceback (most recent call last):
>    File "/usr/lib64/python3.9/site-packages/solaar/gtk.py", line 165, in
> main
>      import solaar.listener as listener
>    File "/usr/lib64/python3.9/site-packages/solaar/listener.py", line
> 34, in <module>
>      from logitech_receiver import notifications as _notifications
>    File
> "/usr/lib64/python3.9/site-packages/logitech_receiver/notifications.py",
> line 27, in <module>
>      from . import diversion as _diversion
>    File
> "/usr/lib64/python3.9/site-packages/logitech_receiver/diversion.py",
> line 33, in <module>
>      import psutil
>    File "/usr/lib64/python3.9/site-packages/psutil/__init__.py", line
> 102, in <module>
>      from . import _pslinux as _psplatform
>    File "/usr/lib64/python3.9/site-packages/psutil/_pslinux.py", line
> 87, in <module>
>      PAGESIZE = cext_posix.getpagesize()
> AttributeError: module 'psutil._psutil_posix' has no attribute
> 'getpagesize'
>
>
> I used 'slpkg' and it looks like all was built in the right order
> (unless I missed something):
>
>    ? python3-flit_core.SlackBuild ??
>    ? python3-flit_core-3.9.0-x86_64-1_SBo.tgz ??
>    ? python3-installer.SlackBuild ??
>    ? python3-installer-0.7.0-x86_64-1_SBo.tgz ??
>    ? python3-pyproject-hooks.SlackBuild ??
>    ? python3-pyproject-hooks-1.0.0-x86_64-1_SBo.tgz ??
>    ? python3-wheel.SlackBuild ??
>    ? python3-wheel-0.40.0-x86_64-1_SBo.tgz ??
>    ? python3-build.SlackBuild ??
>    ? python3-build-0.10.0-x86_64-1_SBo.tgz ??
>    ? python3-psutil.SlackBuild ??
>    ? python3-psutil-5.9.5-x86_64-1_SBo.tgz ??
>    ? python3-xlib.SlackBuild ??
>    ? python3-xlib-0.33-x86_64-1_SBo.tgz ??
>    ? pyudev.SlackBuild ??
>    ? pyudev-0.24.1-x86_64-1_SBo.tgz ??
>    ? python-evdev.SlackBuild ??
>    ? python-evdev-1.6.1-x86_64-1_SBo.tgz ??
>    ? Solaar.SlackBuild ??
>    ? Solaar-1.1.9-x86_64-1_SBo.tgz ??
>
> Command line work exit for "pair" (did not test "config")
>
> $ solaar pair
> solaar: error: Traceback (most recent call last):
>    File "/usr/lib64/python3.9/site-packages/solaar/cli/__init__.py",
> line 208, in run
>      m = import_module('.' + action, package=__name__)
>    File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in
> import_module
>      return _bootstrap._gcd_import(name[level:], package, level)
>    File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
>    File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
>    File "<frozen importlib._bootstrap>", line 986, in
> _find_and_load_unlocked
>    File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
>    File "<frozen importlib._bootstrap_external>", line 850, in exec_module
>    File "<frozen importlib._bootstrap>", line 228, in
> _call_with_frames_removed
>    File "/usr/lib64/python3.9/site-packages/solaar/cli/pair.py", line
> 23, in <module>
>      from logitech_receiver import notifications as _notifications
>    File
> "/usr/lib64/python3.9/site-packages/logitech_receiver/notifications.py",
> line 27, in <module>
>      from . import diversion as _diversion
>    File
> "/usr/lib64/python3.9/site-packages/logitech_receiver/diversion.py",
> line 33, in <module>
>      import psutil
>    File "/usr/lib64/python3.9/site-packages/psutil/__init__.py", line
> 102, in <module>
>      from . import _pslinux as _psplatform
>    File "/usr/lib64/python3.9/site-packages/psutil/_pslinux.py", line
> 87, in <module>
>      PAGESIZE = cext_posix.getpagesize()
> AttributeError: module 'psutil._psutil_posix' has no attribute
> 'getpagesize'
>
> -kb
>
>
>
>
>
>
>
> _______________________________________________
> 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/20230619/8d487ea5/attachment-0001.htm>

From erich.public at protonmail.com  Mon Jun 19 13:02:31 2023
From: erich.public at protonmail.com (Erich Ritz)
Date: Mon, 19 Jun 2023 13:02:31 +0000
Subject: [Slackbuilds-users] Solaar gui fails to run
In-Reply-To: <CAAZ8Hahk5UpYvbSBiPceXC4B7q4WO5cFvmMJXVJ-9Z5e3Z6e=w@mail.gmail.com>
References: <307fbc38-ad45-27a0-b27b-19dd43085bfa@linuxgalaxy.org>
 <CAAZ8Hahk5UpYvbSBiPceXC4B7q4WO5cFvmMJXVJ-9Z5e3Z6e=w@mail.gmail.com>
Message-ID: <Cj3KogMnKJhADZcAx3_XkA9ULOCXFiT__QCbK_O-JKpNd9s_qLFXIvDGLzBNpHel_LxzqhsPlz0H26_RT2D6LXeVtoDLt3irjI2owX8NyhM=@protonmail.com>

------- Original Message -------
On Monday, June 19th, 2023 at 1:21 AM, fourtysixandtwo <fourtysixandtwo at sliderr.net> wrote:


> Doing a bit of digging I see Willy reported a similar issue back in Nov. Maybe he can chime in? But it seems to have fixed itself.
> https://github.com/giampaolo/psutil/issues/2181
> 
> The author talks about it possibly finding "_psutil_posix.so" in the path, but it's only installed in the python2 version. Do you have python2-psutil or the old psutil slackbuild still installed? I would try removing them and reinstalling python3-psutil. I would also check if you have any pip installed packages.
> 
> I can't get anything to fail here, both solaar and locust build and run without errors.
> 
> 
> On Sun, Jun 18, 2023 at 8:46?PM KB_SBo <sbo at linuxgalaxy.org> wrote:
> 
> > Hello all,
> > 
> > I'm trying to an old logitech keyboard paired to another receiver - lost
> > the original. When running the GUI version the negative result is
> > 
> > $ solaar
> > solaar: error: Traceback (most recent call last):
> > File "/usr/lib64/python3.9/site-packages/solaar/gtk.py", line 165, in
> > main
> > import solaar.listener as listener
> > File "/usr/lib64/python3.9/site-packages/solaar/listener.py", line
> > 34, in <module>
> > from logitech_receiver import notifications as _notifications
> > File
> > "/usr/lib64/python3.9/site-packages/logitech_receiver/notifications.py",
> > line 27, in <module>
> > from . import diversion as _diversion
> > File
> > "/usr/lib64/python3.9/site-packages/logitech_receiver/diversion.py",
> > line 33, in <module>
> > import psutil
> > File "/usr/lib64/python3.9/site-packages/psutil/__init__.py", line
> > 102, in <module>
> > from . import _pslinux as _psplatform
> > File "/usr/lib64/python3.9/site-packages/psutil/_pslinux.py", line
> > 87, in <module>
> > PAGESIZE = cext_posix.getpagesize()
> > AttributeError: module 'psutil._psutil_posix' has no attribute 'getpagesize'
> > 
> > 
> > I used 'slpkg' and it looks like all was built in the right order
> > (unless I missed something):
> > 
> > ? python3-flit_core.SlackBuild ??
> > ? python3-flit_core-3.9.0-x86_64-1_SBo.tgz ??
> > ? python3-installer.SlackBuild ??
> > ? python3-installer-0.7.0-x86_64-1_SBo.tgz ??
> > ? python3-pyproject-hooks.SlackBuild ??
> > ? python3-pyproject-hooks-1.0.0-x86_64-1_SBo.tgz ??
> > ? python3-wheel.SlackBuild ??
> > ? python3-wheel-0.40.0-x86_64-1_SBo.tgz ??
> > ? python3-build.SlackBuild ??
> > ? python3-build-0.10.0-x86_64-1_SBo.tgz ??
> > ? python3-psutil.SlackBuild ??
> > ? python3-psutil-5.9.5-x86_64-1_SBo.tgz ??
> > ? python3-xlib.SlackBuild ??
> > ? python3-xlib-0.33-x86_64-1_SBo.tgz ??
> > ? pyudev.SlackBuild ??
> > ? pyudev-0.24.1-x86_64-1_SBo.tgz ??
> > ? python-evdev.SlackBuild ??
> > ? python-evdev-1.6.1-x86_64-1_SBo.tgz ??
> > ? Solaar.SlackBuild ??
> > ? Solaar-1.1.9-x86_64-1_SBo.tgz ??
> > 
> > Command line work exit for "pair" (did not test "config")
> > 
> > $ solaar pair
> > solaar: error: Traceback (most recent call last):
> > File "/usr/lib64/python3.9/site-packages/solaar/cli/__init__.py",
> > line 208, in run
> > m = import_module('.' + action, package=__name__)
> > File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in
> > import_module
> > return _bootstrap._gcd_import(name[level:], package, level)
> > File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
> > File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
> > File "<frozen importlib._bootstrap>", line 986, in
> > _find_and_load_unlocked
> > File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
> > File "<frozen importlib._bootstrap_external>", line 850, in exec_module
> > File "<frozen importlib._bootstrap>", line 228, in
> > _call_with_frames_removed
> > File "/usr/lib64/python3.9/site-packages/solaar/cli/pair.py", line
> > 23, in <module>
> > from logitech_receiver import notifications as _notifications
> > File
> > "/usr/lib64/python3.9/site-packages/logitech_receiver/notifications.py",
> > line 27, in <module>
> > from . import diversion as _diversion
> > File
> > "/usr/lib64/python3.9/site-packages/logitech_receiver/diversion.py",
> > line 33, in <module>
> > import psutil
> > File "/usr/lib64/python3.9/site-packages/psutil/__init__.py", line
> > 102, in <module>
> > from . import _pslinux as _psplatform
> > File "/usr/lib64/python3.9/site-packages/psutil/_pslinux.py", line
> > 87, in <module>
> > PAGESIZE = cext_posix.getpagesize()
> > AttributeError: module 'psutil._psutil_posix' has no attribute 'getpagesize'
> > 
> > -kb
> > 


Feeding off the last reply (Solaar works for me):

$ locate _psutil_posix
/usr/lib64/python3.9/site-packages/psutil/_psutil_posix.abi3.so

But more versions of it existed in older packages:

$ grep psutil_posix /var/log/pkgtools/removed_packages/*
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-1_SBo:usr/lib64/python2.7/site-packages/psutil/_psutil_posix.so
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-1_SBo:usr/lib64/python3.9/site-packages/psutil/_psutil_posix.cpython-39-x86_64-linux-gnu.so
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-1_SBo-upgraded-2021-08-16,15:43:21:usr/lib64/python2.7/site-packages/psutil/_psutil_posix.so
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-1_SBo-upgraded-2021-08-16,15:43:21:usr/lib64/python3.9/site-packages/psutil/_psutil_posix.cpython-39-x86_64-linux-gnu.so
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-1_SBo-upgraded-2022-02-07,13:09:02:usr/lib64/python2.7/site-packages/psutil/_psutil_posix.so
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-1_SBo-upgraded-2022-02-07,13:09:02:usr/lib64/python3.9/site-packages/psutil/_psutil_posix.cpython-39-x86_64-linux-gnu.so
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-1_SBo-upgraded-2022-03-15,13:44:42:usr/lib64/python2.7/site-packages/psutil/_psutil_posix.so
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-1_SBo-upgraded-2022-03-15,13:44:42:usr/lib64/python3.9/site-packages/psutil/_psutil_posix.cpython-39-x86_64-linux-gnu.so
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-1_SBo-upgraded-2022-04-11,13:49:11:usr/lib64/python2.7/site-packages/psutil/_psutil_posix.so
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-1_SBo-upgraded-2022-04-11,13:49:11:usr/lib64/python3.9/site-packages/psutil/_psutil_posix.cpython-39-x86_64-linux-gnu.so
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-2_SBo:usr/lib64/python2.7/site-packages/psutil/_psutil_posix.so
/var/log/pkgtools/removed_packages/psutil-5.6.7-x86_64-2_SBo:usr/lib64/python3.9/site-packages/psutil/_psutil_posix.cpython-39-x86_64-linux-gnu.so
/var/log/pkgtools/removed_packages/python3-psutil-5.9.4-x86_64-1_SBo-upgraded-2023-05-01,13:44:35:usr/lib64/python3.9/site-packages/psutil/_psutil_posix.abi3.so
/var/log/pkgtools/removed_packages/python3-psutil-5.9.4-x86_64-2_SBo-upgraded-2023-05-16,08:54:02:usr/lib64/python3.9/site-packages/psutil/_psutil_posix.abi3.so
/var/log/pkgtools/removed_packages/python3-psutil-5.9.4-x86_64-3_SBo-upgraded-2023-05-23,12:55:37:usr/lib64/python3.9/site-packages/psutil/_psutil_posix.abi3.so


Can you try to remove any and all versions of psutil packages you have, make sure you don't have non-Slackware packages of psutil installed, and then rebuild psutil and all dependent packages?

Erich

From sbo at linuxgalaxy.org  Tue Jun 20 00:31:22 2023
From: sbo at linuxgalaxy.org (KB_SBo)
Date: Tue, 20 Jun 2023 00:31:22 +0000
Subject: [Slackbuilds-users] Solaar gui fails to run
In-Reply-To: <Cj3KogMnKJhADZcAx3_XkA9ULOCXFiT__QCbK_O-JKpNd9s_qLFXIvDGLzBNpHel_LxzqhsPlz0H26_RT2D6LXeVtoDLt3irjI2owX8NyhM=@protonmail.com>
References: <307fbc38-ad45-27a0-b27b-19dd43085bfa@linuxgalaxy.org>
 <CAAZ8Hahk5UpYvbSBiPceXC4B7q4WO5cFvmMJXVJ-9Z5e3Z6e=w@mail.gmail.com>
 <Cj3KogMnKJhADZcAx3_XkA9ULOCXFiT__QCbK_O-JKpNd9s_qLFXIvDGLzBNpHel_LxzqhsPlz0H26_RT2D6LXeVtoDLt3irjI2owX8NyhM=@protonmail.com>
Message-ID: <4c8b72b9-e502-726e-dbc0-49a9f53ae880@linuxgalaxy.org>

On 6/19/23 06:02, Erich Ritz via SlackBuilds-users wrote:
> ------- Original Message -------
>...
> 
> Can you try to remove any and all versions of psutil packages you have, make sure you don't have non-Slackware packages of psutil installed, and then rebuild psutil and all dependent packages?
> 
>

Well...fudge.  I only have psutil-5.6.7-x86_64-1_SBo from 29-Jan-2022, 
and from the current reverse deps, I have no idea what it was a dep for 
back then.

I see that was removed for the pythonX-psutil version specific builds.

All worked as expected on the clean qemu VM and once I cleaned out the 
stale psutil package on my main box. Silly me.

-kb




From dickson.tim at googlemail.com  Tue Jun 20 21:39:41 2023
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Tue, 20 Jun 2023 22:39:41 +0100
Subject: [Slackbuilds-users] OpenCASCADE build issue
Message-ID: <abfffb58-0a36-451d-5353-4ec585d2cdb7@googlemail.com>

Hi all, I'm getting build failure with the error

[100%] Linking CXX executable ../../lin64/gcc/bin/DRAWEXE
/usr/bin/ld: /usr/lib64/libldb.so.2: undefined reference to 
`rep_memset_s at SAMBA_4.15.13'
collect2: error: ld returned 1 exit status
make[2]: *** [src/DRAWEXE/CMakeFiles/DRAWEXE.dir/build.make:118: 
lin64/gcc/bin/DRAWEXE-7.7.0] Error 1
make[1]: *** [CMakeFiles/Makefile2:3747: 
src/DRAWEXE/CMakeFiles/DRAWEXE.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

I am using the following build flags/options
FREEIMAGE=yes TTB=yes GL2PS=yes

( VTK was built with IMAGING=yes MPI=yes )

any ideas?
regards, Tim

From urchlay at slackware.uk  Tue Jun 20 21:54:08 2023
From: urchlay at slackware.uk (B. Watson)
Date: Tue, 20 Jun 2023 17:54:08 -0400 (EDT)
Subject: [Slackbuilds-users] OpenCASCADE build issue
In-Reply-To: <abfffb58-0a36-451d-5353-4ec585d2cdb7@googlemail.com>
References: <abfffb58-0a36-451d-5353-4ec585d2cdb7@googlemail.com>
Message-ID: <24af2f7d-384e-7f55-aba7-44c08629372@slackware.uk>



On Tue, 20 Jun 2023, Tim Dickson via SlackBuilds-users wrote:

> Hi all, I'm getting build failure with the error
>
> [100%] Linking CXX executable ../../lin64/gcc/bin/DRAWEXE
> /usr/bin/ld: /usr/lib64/libldb.so.2: undefined reference to 
> `rep_memset_s at SAMBA_4.15.13'

What happens if you run this?

ldd /usr/lib64/libldb.so.2

I bet you get a 'libreplace-samba4.so => not found' error.

If so, try reinstalling samba.

From dickson.tim at googlemail.com  Wed Jun 21 19:12:29 2023
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Wed, 21 Jun 2023 20:12:29 +0100
Subject: [Slackbuilds-users] OpenCASCADE build issue
In-Reply-To: <24af2f7d-384e-7f55-aba7-44c08629372@slackware.uk>
References: <abfffb58-0a36-451d-5353-4ec585d2cdb7@googlemail.com>
 <24af2f7d-384e-7f55-aba7-44c08629372@slackware.uk>
Message-ID: <5c58f052-2657-1d38-7560-8a1b9313e30a@googlemail.com>

On 20/06/2023 22:54, B. Watson wrote:
>
>
> On Tue, 20 Jun 2023, Tim Dickson via SlackBuilds-users wrote:
>
>> Hi all, I'm getting build failure with the error
>>
>> [100%] Linking CXX executable ../../lin64/gcc/bin/DRAWEXE
>> /usr/bin/ld: /usr/lib64/libldb.so.2: undefined reference to 
>> `rep_memset_s at SAMBA_4.15.13'
>
> What happens if you run this?
>
> ldd /usr/lib64/libldb.so.2
>
> I bet you get a 'libreplace-samba4.so => not found' error.
>
> If so, try reinstalling samba.
you hit it on the nail. for some reason I needed to reinstall it.
thanks for the pointer.
Tim


From dchmelik at gmail.com  Thu Jun 22 10:02:49 2023
From: dchmelik at gmail.com (dchmelik at gmail.com)
Date: Thu, 22 Jun 2023 03:02:49 -0700
Subject: [Slackbuilds-users] so-called terminal image viewers
Message-ID: <9165ae3a-29f2-eed7-1920-8df3045780fb@gmail.com>

Recent years there have been a few so-called 'terminal image viewers' 
SlackBuilds uploaded but in these descriptions people are lying through 
their teeth: when I tried these on pure (non-X) terminals (/dev/tty*) 
they don't work at all.? They were made for X terminals (xterms) or 
maybe even newer similar stuff many don't use yet like Wayland.? I ask 
that the descriptions be updated and if they're in system or graphics 
categories they be moved to desktop category.
????????What is the world coming to when people SlackBuilding believe 
that 'terminal' automatically means 'xterm' for an OS that doesn't even 
boot to X, just boots to the console terminal (/dev/tty1) non-X default?!

From dchmelik at gmail.com  Thu Jun 22 10:21:12 2023
From: dchmelik at gmail.com (dchmelik at gmail.com)
Date: Thu, 22 Jun 2023 03:21:12 -0700
Subject: [Slackbuilds-users] so-called terminal image viewers
In-Reply-To: <9165ae3a-29f2-eed7-1920-8df3045780fb@gmail.com>
References: <9165ae3a-29f2-eed7-1920-8df3045780fb@gmail.com>
Message-ID: <11ecfec2-30bd-2e60-bda2-33e460e06fe8@gmail.com>

I recall there's the graphics category has some X stuff, so that's 
probably okay... just the one-line & longer/README descriptions should 
say /X/ terminal image viewer, or whatever desktop type they're for... 
not misleading people looking for pure (/dev/tty*) command-line stuff 
then getting an error X isn't running or whatever!

On 6/22/23 3:02 AM, dchmelik at gmail.com wrote:
> Recent years there have been a few so-called 'terminal image viewers' 
> SlackBuilds uploaded but in these descriptions people are lying 
> through their teeth: when I tried these on pure (non-X) terminals 
> (/dev/tty*) they don't work at all.? They were made for X terminals 
> (xterms) or maybe even newer similar stuff many don't use yet like 
> Wayland.? I ask that the descriptions be updated and if they're in 
> system or graphics categories they be moved to desktop category.
> ????????What is the world coming to when people SlackBuilding believe 
> that 'terminal' automatically means 'xterm' for an OS that doesn't 
> even boot to X, just boots to the console terminal (/dev/tty1) non-X 
> default?!


From dchmelik at gmail.com  Thu Jun 22 11:05:56 2023
From: dchmelik at gmail.com (dchmelik at gmail.com)
Date: Thu, 22 Jun 2023 04:05:56 -0700
Subject: [Slackbuilds-users] so-called terminal image viewers
In-Reply-To: <dec0952f-9bbd-f27c-9577-47200a51f3cf@spitzner.org>
References: <9165ae3a-29f2-eed7-1920-8df3045780fb@gmail.com>
 <dec0952f-9bbd-f27c-9577-47200a51f3cf@spitzner.org>
Message-ID: <f1968145-59b6-7675-8449-99355e4ba934@gmail.com>

On 6/22/23 3:47 AM, Ralph Spitzner wrote:
> dchmelik at gmail.com wrote on 6/22/23 12:02 PM:
>> Recent years there have been a few so-called 'terminal image viewers' 
>> SlackBuilds uploaded but in these descriptions people are lying through 
>
> slackware has fbv....

No; Slackware has seejpeg (which hasn't worked in years on newer 
hardware).? SlackBuilds.org (SBo, which isn't (official) Slackware) has 
fbida & fbv, neither which can go to previous or next images anymore, 
apparently, which I reported years ago to the maintainers and one or 
more of the programmers but never heard back.? That's why I'm looking 
for new stuff, and they're all called terminal image viewers but aren't: 
only X terminal viewers!? There are a couple other framebuffer ones, but 
they don't seem to take input after you display an image.

From rasp at spitzner.org  Thu Jun 22 10:47:24 2023
From: rasp at spitzner.org (Ralph Spitzner)
Date: Thu, 22 Jun 2023 12:47:24 +0200
Subject: [Slackbuilds-users] so-called terminal image viewers
In-Reply-To: <9165ae3a-29f2-eed7-1920-8df3045780fb@gmail.com>
References: <9165ae3a-29f2-eed7-1920-8df3045780fb@gmail.com>
Message-ID: <dec0952f-9bbd-f27c-9577-47200a51f3cf@spitzner.org>



dchmelik at gmail.com wrote on 6/22/23 12:02 PM:
> Recent years there have been a few so-called 'terminal image viewers' 
> SlackBuilds uploaded but in these descriptions people are lying through 

slackware has fbv....


-- 
Chaos ist die h?chste form der Ordnung.....


From dickson.tim at googlemail.com  Thu Jun 22 16:42:50 2023
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Thu, 22 Jun 2023 17:42:50 +0100
Subject: [Slackbuilds-users] so-called terminal image viewers
In-Reply-To: <f1968145-59b6-7675-8449-99355e4ba934@gmail.com>
References: <9165ae3a-29f2-eed7-1920-8df3045780fb@gmail.com>
 <dec0952f-9bbd-f27c-9577-47200a51f3cf@spitzner.org>
 <f1968145-59b6-7675-8449-99355e4ba934@gmail.com>
Message-ID: <17652a7b-c21d-3c1b-7bf5-17e8f8b4cd4c@googlemail.com>

fbida works just fine.
pass it the list of images and then use pageup/pagedown to navigate, and 
q or esc to quit. (h for help)
eg.
fbi smiley.png party.jpg game.bmp
or for viewing all files in the current dir
fbi *

regards, Tim

On 22/06/2023 12:05, dchmelik at gmail.com wrote:
> On 6/22/23 3:47 AM, Ralph Spitzner wrote:
>> dchmelik at gmail.com wrote on 6/22/23 12:02 PM:
>>> Recent years there have been a few so-called 'terminal image 
>>> viewers' SlackBuilds uploaded but in these descriptions people are 
>>> lying through 
>>
>> slackware has fbv....
>
> No; Slackware has seejpeg (which hasn't worked in years on newer 
> hardware).? SlackBuilds.org (SBo, which isn't (official) Slackware) 
> has fbida & fbv, neither which can go to previous or next images 
> anymore, apparently, which I reported years ago to the maintainers and 
> one or more of the programmers but never heard back.? That's why I'm 
> looking for new stuff, and they're all called terminal image viewers 
> but aren't: only X terminal viewers!? There are a couple other 
> framebuffer ones, but they don't seem to take input after you display 
> an image.
> _______________________________________________
> 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 jdashiel at panix.com  Thu Jun 22 18:49:52 2023
From: jdashiel at panix.com (Jude DaShiell)
Date: Thu, 22 Jun 2023 14:49:52 -0400
Subject: [Slackbuilds-users] so-called terminal image viewers
In-Reply-To: <17652a7b-c21d-3c1b-7bf5-17e8f8b4cd4c@googlemail.com>
References: <17652a7b-c21d-3c1b-7bf5-17e8f8b4cd4c@googlemail.com>
Message-ID: <82E0875D-8F45-4246-8667-16CFB3CEF029@panix.com>

For people without vision, chafa can help.  The view can be shown with symbols for a linux terminal and there?s even a braille mode and that needs either a braille printer with graphics capability or a refreshable braille graphics display both expensive for people but organizations buy most of those for that reason anyway.

Sent from my iPhone

> On Jun 22, 2023, at 12:42 PM, Tim Dickson via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:
> 
> ?fbida works just fine.
> pass it the list of images and then use pageup/pagedown to navigate, and q or esc to quit. (h for help)
> eg.
> fbi smiley.png party.jpg game.bmp
> or for viewing all files in the current dir
> fbi *
> 
> regards, Tim
> 
>> On 22/06/2023 12:05, dchmelik at gmail.com wrote:
>>> On 6/22/23 3:47 AM, Ralph Spitzner wrote:
>>> dchmelik at gmail.com wrote on 6/22/23 12:02 PM:
>>>> Recent years there have been a few so-called 'terminal image viewers' SlackBuilds uploaded but in these descriptions people are lying through 
>>> 
>>> slackware has fbv....
>> 
>> No; Slackware has seejpeg (which hasn't worked in years on newer hardware).  SlackBuilds.org (SBo, which isn't (official) Slackware) has fbida & fbv, neither which can go to previous or next images anymore, apparently, which I reported years ago to the maintainers and one or more of the programmers but never heard back.  That's why I'm looking for new stuff, and they're all called terminal image viewers but aren't: only X terminal viewers!  There are a couple other framebuffer ones, but they don't seem to take input after you display an image.
>> _______________________________________________
>> 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/
> 

From didier at slint.fr  Thu Jun 22 19:58:49 2023
From: didier at slint.fr (Didier Spaier)
Date: Thu, 22 Jun 2023 21:58:49 +0200
Subject: [Slackbuilds-users] so-called terminal image viewers
In-Reply-To: <82E0875D-8F45-4246-8667-16CFB3CEF029@panix.com>
References: <17652a7b-c21d-3c1b-7bf5-17e8f8b4cd4c@googlemail.com>
 <82E0875D-8F45-4246-8667-16CFB3CEF029@panix.com>
Message-ID: <20356980-1211-e788-f35e-84a27380e607@slint.fr>

You made me curious, Jude.

I assume that the braille mode is possible because chafa outputs discrete
characters. Rendering is not good for a sighted user in most terminals and in a
Linux console, however having read
https://hpjansson.org/blag/2021/09/16/chafa-1-8-terminal-graphics-with-a-side-of-everything/
I installed Kitty then from kitty ran "chafa <someimage.png>" and the output
looks as detailed as if the image were viewed in atril or eom or lx-image, for
instance

If you have the needed hardware, please try this:
1. Install Kitty. In slint: slapt-get -i kitty (it's in the repo salix-15.0)
2. Install chafa (if not yet done): slapt-src -i chafa
3. Start kitty (you will need to be in graphical environment like mate)
4. From kitty try to render an image in braille using chafa
Please let us know if that works.

Cheers,
Didier


Le 22/06/2023 ? 20:49, Jude DaShiell a ?crit?:
> For people without vision, chafa can help.  The view can be shown with symbols for a linux terminal and there?s even a braille mode and that needs either a braille printer with graphics capability or a refreshable braille graphics display both expensive for people but organizations buy most of those for that reason anyway.
> 
> Sent from my iPhone
> 
>> On Jun 22, 2023, at 12:42 PM, Tim Dickson via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:
>>
>> ?fbida works just fine.
>> pass it the list of images and then use pageup/pagedown to navigate, and q or esc to quit. (h for help)
>> eg.
>> fbi smiley.png party.jpg game.bmp
>> or for viewing all files in the current dir
>> fbi *
>>
>> regards, Tim
>>
>>> On 22/06/2023 12:05, dchmelik at gmail.com wrote:
>>>> On 6/22/23 3:47 AM, Ralph Spitzner wrote:
>>>> dchmelik at gmail.com wrote on 6/22/23 12:02 PM:
>>>>> Recent years there have been a few so-called 'terminal image viewers' SlackBuilds uploaded but in these descriptions people are lying through 
>>>>
>>>> slackware has fbv....
>>>
>>> No; Slackware has seejpeg (which hasn't worked in years on newer hardware).  SlackBuilds.org (SBo, which isn't (official) Slackware) has fbida & fbv, neither which can go to previous or next images anymore, apparently, which I reported years ago to the maintainers and one or more of the programmers but never heard back.  That's why I'm looking for new stuff, and they're all called terminal image viewers but aren't: only X terminal viewers!  There are a couple other framebuffer ones, but they don't seem to take input after you display an image.
>>> _______________________________________________
>>> 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/
> 

From didier at slint.fr  Thu Jun 22 21:14:33 2023
From: didier at slint.fr (Didier Spaier)
Date: Thu, 22 Jun 2023 23:14:33 +0200
Subject: [Slackbuilds-users] so-called terminal image viewers
In-Reply-To: <20356980-1211-e788-f35e-84a27380e607@slint.fr>
References: <17652a7b-c21d-3c1b-7bf5-17e8f8b4cd4c@googlemail.com>
 <82E0875D-8F45-4246-8667-16CFB3CEF029@panix.com>
 <20356980-1211-e788-f35e-84a27380e607@slint.fr>
Message-ID: <7f38944c-ef31-dc60-7479-571c1b06f34a@slint.fr>

On second thought no need to try as it won't work, because kitty is not
accessible with speech. If I start it with orca running and type something the
text is not spoken :(

Cheers,
Didier

Le 22/06/2023 ? 21:58, Didier Spaier a ?crit?:
> You made me curious, Jude.
> 
> I assume that the braille mode is possible because chafa outputs discrete
> characters. Rendering is not good for a sighted user in most terminals and in a
> Linux console, however having read
> https://hpjansson.org/blag/2021/09/16/chafa-1-8-terminal-graphics-with-a-side-of-everything/
> I installed Kitty then from kitty ran "chafa <someimage.png>" and the output
> looks as detailed as if the image were viewed in atril or eom or lx-image, for
> instance
> 
> If you have the needed hardware, please try this:
> 1. Install Kitty. In slint: slapt-get -i kitty (it's in the repo salix-15.0)
> 2. Install chafa (if not yet done): slapt-src -i chafa
> 3. Start kitty (you will need to be in graphical environment like mate)
> 4. From kitty try to render an image in braille using chafa
> Please let us know if that works.
> 
> Cheers,
> Didier
> 
> 
> Le 22/06/2023 ? 20:49, Jude DaShiell a ?crit?:
>> For people without vision, chafa can help.  The view can be shown with symbols for a linux terminal and there?s even a braille mode and that needs either a braille printer with graphics capability or a refreshable braille graphics display both expensive for people but organizations buy most of those for that reason anyway.
>>
>> Sent from my iPhone
>>
>>> On Jun 22, 2023, at 12:42 PM, Tim Dickson via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:
>>>
>>> ?fbida works just fine.
>>> pass it the list of images and then use pageup/pagedown to navigate, and q or esc to quit. (h for help)
>>> eg.
>>> fbi smiley.png party.jpg game.bmp
>>> or for viewing all files in the current dir
>>> fbi *
>>>
>>> regards, Tim
>>>
>>>> On 22/06/2023 12:05, dchmelik at gmail.com wrote:
>>>>> On 6/22/23 3:47 AM, Ralph Spitzner wrote:
>>>>> dchmelik at gmail.com wrote on 6/22/23 12:02 PM:
>>>>>> Recent years there have been a few so-called 'terminal image viewers' SlackBuilds uploaded but in these descriptions people are lying through 
>>>>>
>>>>> slackware has fbv....
>>>>
>>>> No; Slackware has seejpeg (which hasn't worked in years on newer hardware).  SlackBuilds.org (SBo, which isn't (official) Slackware) has fbida & fbv, neither which can go to previous or next images anymore, apparently, which I reported years ago to the maintainers and one or more of the programmers but never heard back.  That's why I'm looking for new stuff, and they're all called terminal image viewers but aren't: only X terminal viewers!  There are a couple other framebuffer ones, but they don't seem to take input after you display an image.
>>>> _______________________________________________
>>>> 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/
>>
> _______________________________________________
> 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 jdashiel at panix.com  Thu Jun 22 21:29:43 2023
From: jdashiel at panix.com (Jude DaShiell)
Date: Thu, 22 Jun 2023 17:29:43 -0400
Subject: [Slackbuilds-users] so-called terminal image viewers
In-Reply-To: <20356980-1211-e788-f35e-84a27380e607@slint.fr>
References: <20356980-1211-e788-f35e-84a27380e607@slint.fr>
Message-ID: <74D005A7-6CD7-4550-9DEC-52C97FD79A42@panix.com>

Hi, can?t do it since I haven?t got the needed hardware.  It may be sent out for diagnosis and repair quote eventually.  Good you could test chafa with eyes as a comparative test.  I have a chromebook and would have to download slint direct to a usb disk and then find out how to replace chromium with slint on installation.  Lots of problems with chromevox I?ll not relay to the group since no interest exists here for that.  My niece has a box and styrofoam but unfortunately though she recovered she got covid from her husband.

Sent from my iPhone

> On Jun 22, 2023, at 3:59 PM, Didier Spaier <didier at slint.fr> wrote:
> 
> ?You made me curious, Jude.
> 
> I assume that the braille mode is possible because chafa outputs discrete
> characters. Rendering is not good for a sighted user in most terminals and in a
> Linux console, however having read
> https://hpjansson.org/blag/2021/09/16/chafa-1-8-terminal-graphics-with-a-side-of-everything/
> I installed Kitty then from kitty ran "chafa <someimage.png>" and the output
> looks as detailed as if the image were viewed in atril or eom or lx-image, for
> instance
> 
> If you have the needed hardware, please try this:
> 1. Install Kitty. In slint: slapt-get -i kitty (it's in the repo salix-15.0)
> 2. Install chafa (if not yet done): slapt-src -i chafa
> 3. Start kitty (you will need to be in graphical environment like mate)
> 4. From kitty try to render an image in braille using chafa
> Please let us know if that works.
> 
> Cheers,
> Didier
> 
> 
>> Le 22/06/2023 ? 20:49, Jude DaShiell a ?crit :
>> For people without vision, chafa can help.  The view can be shown with symbols for a linux terminal and there?s even a braille mode and that needs either a braille printer with graphics capability or a refreshable braille graphics display both expensive for people but organizations buy most of those for that reason anyway.
>> 
>> Sent from my iPhone
>> 
>>>> On Jun 22, 2023, at 12:42 PM, Tim Dickson via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:
>>> 
>>> ?fbida works just fine.
>>> pass it the list of images and then use pageup/pagedown to navigate, and q or esc to quit. (h for help)
>>> eg.
>>> fbi smiley.png party.jpg game.bmp
>>> or for viewing all files in the current dir
>>> fbi *
>>> 
>>> regards, Tim
>>> 
>>>> On 22/06/2023 12:05, dchmelik at gmail.com wrote:
>>>>> On 6/22/23 3:47 AM, Ralph Spitzner wrote:
>>>>> dchmelik at gmail.com wrote on 6/22/23 12:02 PM:
>>>>>> Recent years there have been a few so-called 'terminal image viewers' SlackBuilds uploaded but in these descriptions people are lying through 
>>>>> 
>>>>> slackware has fbv....
>>>> 
>>>> No; Slackware has seejpeg (which hasn't worked in years on newer hardware).  SlackBuilds.org (SBo, which isn't (official) Slackware) has fbida & fbv, neither which can go to previous or next images anymore, apparently, which I reported years ago to the maintainers and one or more of the programmers but never heard back.  That's why I'm looking for new stuff, and they're all called terminal image viewers but aren't: only X terminal viewers!  There are a couple other framebuffer ones, but they don't seem to take input after you display an image.
>>>> _______________________________________________
>>>> 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/
>> 
> _______________________________________________
> 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 urchlay at slackware.uk  Thu Jun 22 21:44:15 2023
From: urchlay at slackware.uk (B. Watson)
Date: Thu, 22 Jun 2023 17:44:15 -0400 (EDT)
Subject: [Slackbuilds-users] so-called terminal image viewers
In-Reply-To: <9165ae3a-29f2-eed7-1920-8df3045780fb@gmail.com>
References: <9165ae3a-29f2-eed7-1920-8df3045780fb@gmail.com>
Message-ID: <53d1b7b-4eee-19fb-8b7-57706e9c726d@slackware.uk>



On Thu, 22 Jun 2023, dchmelik at gmail.com wrote:

> Recent years there have been a few so-called 'terminal image viewers' 
> SlackBuilds uploaded but in these descriptions people are lying through 
> their teeth: when I tried these on pure (non-X) terminals (/dev/tty*) 
> they don't work at all.? They were made for X terminals (xterms) or

The trouble is, the word 'terminal' is ill-defined and
overloaded. When I say "this runs in a terminal", I might mean an X
terminal emulator (xterm, urxvt, konsole, etc), or I might mean the
Linux console, or I might (unlikely but possible) mean a real piece of
hardware like a Wyse or a DEC VT220, plugged into an RS232 port. Or,
a piece of software like minicom (also with RS232).

Other replies to this thread talk about framebuffer image viewers. I
personally wouldn't call those "terminal" image viewers, I'd actually
use the word "framebuffer".

I agree that the descriptions in the READMEs should be more
specific. But aggressively calling people liars isn't likely to win
them over to your point of view...

From ed at fletcher.ca  Thu Jun 22 21:53:30 2023
From: ed at fletcher.ca (Ed Fletcher)
Date: Thu, 22 Jun 2023 14:53:30 -0700
Subject: [Slackbuilds-users] sboinstall chromprint fails
Message-ID: <b6c1bb64-6bea-a220-6710-9b530d5322f4@fletcher.ca>

While using sbo to put vlc on a freshly installed and updated 
Slackware64-15.0 (sboinstall vlc), the process failed on chromaprint.  I 
tried chromaprint by itself (sboinstall chromaprint) but it failed with 
the same error:

In file included from 
/tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18,
                  from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7:
/usr/include/libavcodec/avcodec.h:3047:5: note: declared here
  3047 | int avcodec_decode_audio4(AVCodecContext *avctx, AVFrame *frame,
       |     ^~~~~~~~~~~~~~~~~~~~~
make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/build.make:76: 
src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:244: 
src/cmd/CMakeFiles/fpcalc.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
Failures:
   chromaprint: chromaprint.SlackBuild return non-zero

What I find strange is that downloading the source and the slackbuild 
let me install it successfully.  This let sboinstall finish installing 
vlc.  So I have everything working, just left with a puzzle.

Ed
-- 
Ed Fletcher

"When I became a man I put away childish things, including the fear of 
childishness and the desire to be very grown up.?
? C.S. Lewis

From willysr at slackbuilds.org  Fri Jun 23 01:01:54 2023
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 23 Jun 2023 08:01:54 +0700
Subject: [Slackbuilds-users] Updates - 20230623.1
Message-ID: <de28fcc1-948d-e246-ac22-b3c6d4e0e7d8@slackbuilds.org>

Fri Jun 23 00:48:58 UTC 2023
academic/bedtools: Updated for version 2.31.0.
academic/gwyddion: Updated for version 2.63.
academic/iqtree: Updated for version 2.2.2.6.
academic/ncbi-blast+: Updated for version 2.14.0.
academic/primer3: Updated for version 2.6.1.
academic/ugene: Updated for version 47.0.
audio/volctl: Updated for version 0.9.4
business/binance-desktop: Fix doinst.sh.
business/bisq: Fix doinst.sh.
desktop/ComixCursors: Updated for version 0.9.2.
desktop/ccsm: Fix doinst.sh.
desktop/gnome-icon-theme-stock: Fix doinst.sh.
desktop/gnome-icon-theme: Fix doinst.sh.
desktop/gopsuinfo: Updated for version 0.1.5.
desktop/nwg-panel: Updated for version 0.9.7.
desktop/nwg-shell-config: Updated for version 0.5.7.
desktop/nwg-shell: Updated for version 0.5.6.
desktop/rss-guard: Remove unused patches.
desktop/sun: Wrap README at 72 columns.
desktop/thunar-sendto-clamtk: Updated for version 0.07.
development/QtPy: New maintainer
development/emsdk: Added (Emscripten SDK).
development/ghidra: Updated for version 10.3.1
development/mongodb-compass: Updated for version 1.38.0.
development/postman: Updated for version 10.15.0
development/pycharm: Updated for version 2023.1.3.231.9161.41.
development/robotframework: Updated for version 6.1.
development/spyder: Add missing dependencies.
development/universal-ctags: Updated for version p6.0.20230618.0
games/Mindustry: updated for version 145.1
games/endless-sky: updated for version 0.10.2
games/manaplus: Fix doinst.sh.
games/starfighter: Fix doinst.sh.
games/steam: Fix doinst.sh.
games/tbftss: Fix doinst.sh.
gis/pdal: Updated for version 2.5.5.
gis/therion: Updated for version 1.25.6.
graphics/CairoSVG: Updated for version 2.7.0.
graphics/blockbench: Fix doinst.sh.
graphics/povray: Fix doinst.sh.
graphics/qimgv: allow disabling KDE integration
graphics/synfigstudio: Fix doinst.sh.
libraries/QDarkStyle: New maintainer
libraries/fltk: No +x on static libs.
libraries/libloc: Added (location library).
libraries/librsync: new maintainer.
misc/bitwarden-desktop: Updated for version 2023.5.1.
multimedia/freetube: Fix doinst.sh.
multimedia/plexmediaserver: Updated for v 1.32.4.7195_7c8f9d3b6.
multimedia/spot: Fix doinst.sh.
network/Electrum: Updated for version 4.4.5
network/armcord: Fix doinst.sh.
network/castor: Fix doinst.sh.
network/choqok: Fix doinst.sh.
network/eiskaltdcpp: Fix doinst.sh.
network/element-desktop: Updated for version 1.11.34.
network/gallery-dl: Updated for version 1.25.6.
network/host-sflow: Fix init scrupt and doinst.
network/i2pd: Updated for version 2.48.0.
network/jitsi-meet-desktop: new maintainer.
network/mailspring: Fix doinst.sh.
network/mumble-server: Wrap README at 72 columns.
network/open-iscsi: Fix doinst, install headers -x.
network/open-isns: Use template config().
network/opensmtpd: Updated for version 7.3.0p0.
network/signal-desktop: Updated for version 6.22.0.
network/tor-browser: Updated for version 12.5.
network/vivaldi: Updated for version 6.1.3035.100.
network/webhook: Fix doinst.sh.
network/yle-dl: Updated for version 20230611.
network/youtube-dl: Updated for version 2021.12.17+20230618_07af47960.
network/zoom-linux: Updated for version 5.15.0.4063
office/gocr: Updated for version 0.52.
office/hebcal: Updated for version 5.8.0.
office/homebank: Updated for version 5.6.5.
office/krop: Updated for version 0.6.1_e96d42b.
office/semantik: Fix doinst.sh.
perl/perl-Lingua-EN-Syllable: Fix slack-desc.
python/BeautifulSoup4: Fix dep.
python/PyPDF2: Update source.
python/PyPy3: updated for version 7.3.12
python/PyPy: updated for version 7.3.12
python/certbot-dns-cloudflare: Updated for version 2.6.0
python/freetype-py: Fix dep.
python/pypy3: updated for version 7.3.12
python/pypy: updated for version 7.3.12
python/python3-PdPDF3: Added (Python PDF Toolkit).
python/python3-PyMuPDF: Added (Python binding for mupdf).
python/python3-PySimpleGUI: Added (python library for GUIs).
python/python3-aiohttp-socks: New maintainer
python/python3-aiohttp: New maintainer.
python/python3-aiorpcX: New maintainer
python/python3-aiosignal: New maintainer.
python/python3-async-timeout: New maintainer.
python/python3-black: reverted to version 22.12.0
python/python3-bottle: Added (Python Web Framework).
python/python3-celery: updated for version 5.3.1
python/python3-frozenlist: New maintainer.
python/python3-helpdev: New maintainer
python/python3-kombu: updated for version 5.3.1
python/python3-multidict: New maintainer.
python/python3-pypng: New maintainer
python/python3-socks: New maintainer
python/python3-soupsieve: Fix dep.
python/python3-soupsieve: Updated dep.
python/python3-ufolib2: Fix dep.
python/python3-uharfbuzz: Fix dep.
python/python3-yarl: New maintainer.
ruby/ruby-build: Updated for version 20230615.
system/clamtk: Updated for version 6.16.
system/epson-printer-utility: Fix doinst.sh.
system/hplip-plugin: updated for version 3.20.5. New maintainer.
system/jdupes: updated for version 1.25.1
system/rewise: Added (Reverse Engineering WISE).
system/telegraf: Updated for version 1.27.0
system/thinkfan: Fix path to the binary in rc.thinkfan.
system/watchdog: Fix doinst.sh.
system/wterm: Fix compile, install terminfo, new maintainer.
+--------------------------+


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

From matteo.bernardini at gmail.com  Fri Jun 23 06:35:31 2023
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 23 Jun 2023 08:35:31 +0200
Subject: [Slackbuilds-users] sboinstall chromprint fails
In-Reply-To: <b6c1bb64-6bea-a220-6710-9b530d5322f4@fletcher.ca>
References: <b6c1bb64-6bea-a220-6710-9b530d5322f4@fletcher.ca>
Message-ID: <CAPsDuS6cdfKqHPZZQJTyGO0zu6C_XEVahBVnU+Fn0VZx-p+OvA@mail.gmail.com>

hi Ed,

could it be that you have configured with sbotools a repository for
Slackware current while you are running slackware 15.0?

Matteo

Il giorno gio 22 giu 2023 alle ore 23:59 Ed Fletcher <ed at fletcher.ca> ha
scritto:

> While using sbo to put vlc on a freshly installed and updated
> Slackware64-15.0 (sboinstall vlc), the process failed on chromaprint.  I
> tried chromaprint by itself (sboinstall chromaprint) but it failed with
> the same error:
>
> In file included from
> /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18,
>                   from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7:
> /usr/include/libavcodec/avcodec.h:3047:5: note: declared here
>   3047 | int avcodec_decode_audio4(AVCodecContext *avctx, AVFrame *frame,
>        |     ^~~~~~~~~~~~~~~~~~~~~
> make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/build.make:76:
> src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1
> make[1]: *** [CMakeFiles/Makefile2:244:
> src/cmd/CMakeFiles/fpcalc.dir/all] Error 2
> make: *** [Makefile:136: all] Error 2
> Failures:
>    chromaprint: chromaprint.SlackBuild return non-zero
>
> What I find strange is that downloading the source and the slackbuild
> let me install it successfully.  This let sboinstall finish installing
> vlc.  So I have everything working, just left with a puzzle.
>
> Ed
> --
> Ed Fletcher
>
> "When I became a man I put away childish things, including the fear of
> childishness and the desire to be very grown up.?
> ? C.S. Lewis
> _______________________________________________
> 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/20230623/db7f829f/attachment-0001.htm>

From erich.public at protonmail.com  Fri Jun 23 15:22:07 2023
From: erich.public at protonmail.com (Erich Ritz)
Date: Fri, 23 Jun 2023 15:22:07 +0000
Subject: [Slackbuilds-users] slackrepo fails to build youtube-dl due to URL
 encoding
Message-ID: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>

Hello Dimitris and Andrew and list,

I don't know if this message is more appropriate for the slackrepo maintainer or the youtube-dl maintainer.

When trying to build youtube-dl with slackrepo it fails with:

Building network/youtube-dl (update for version 2021.12.17+20230618_07af47960) 2023-06-23 14:25:18
Removing old source files ... 
Downloading source files ...
Verifying source files ... 
Running youtube-dl.SlackBuild ...                                   ETA 14:26:??
env MAKEFLAGS='-j176 -l89' nice -n 5 bash ./youtube-dl.SlackBuild
tar: /tmp/slackrepo/etr/slackrepo.MOV0A0/slackbuild_youtube-dl/youtube-dl-2021.12.17+20230618_07af47960.tar.xz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
network/youtube-dl: youtube-dl.SlackBuild failed (status 2)             14:25:20
Unmounting chroot ... 
:-( network/youtube-dl FAILED )-:

slackrepo downloads the source file, but it is saved with a "%2B" instead of "+" in the filename.  This is due to curl not doing URL decoding.  Note these (partial) excerpts from curl's man page:

       -J, --remote-header-name
              There's no attempt to decode %-sequences (yet) in the provided file name,
              so this option may provide you with rather unexpected file names.
       -O, --remote-name
              There  is  no  URL decoding done on the file name. If it has %20 or other
              URL encoded parts of the name, they will end up as-is as file name.

But I can see why slackrepo chooses to use curl instead of wget for sourceforge (as pointed out by a comment in srcfunctions.sh of slackrepo):

$ wget --content-disposition https://downloads.sourceforge.net/project/dslackw/src/youtube-dl-2021.12.17%2B20230618_07af47960.tar.xz
2023-06-23 10:14:19 (1.09 MB/s) - ?youtube-dl-2021.12.17+20230618_07af47960.tar.xz?viasf=1? saved [1172376/1172376]

sourceforge "helpfully" tacks on "?viasf=1" to the filename.

What's the best way forward?  If I remember correctly SBo policy allows for (if not encourages) the use of the "--content-disposition" flag for wget and similarly the "-J" flag for curl.  However, these break the filename in this case.  Should slackrepo do its own URL decoding when using curl?  Should slackrepo use wget for sourceforge and rename the files (stripping off "?viasf=1")?  Should SBo discourage URL encoding in filenames?

Erich

From urchlay at slackware.uk  Fri Jun 23 17:50:04 2023
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 23 Jun 2023 13:50:04 -0400 (EDT)
Subject: [Slackbuilds-users] slackrepo fails to build youtube-dl due to
 URL encoding
In-Reply-To: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>
References: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>
Message-ID: <186b4e2a-2e6-564-e16a-c9326c54934a@slackware.uk>



On Fri, 23 Jun 2023, Erich Ritz via SlackBuilds-users wrote:

> What's the best way forward?  If I remember correctly SBo policy allows for (if not encourages) the use of the "--content-disposition" flag for wget and similarly the "-J" flag for curl.  However, these break the filename in this case.  Should slackrepo do its own URL decoding when using curl?  Should slackrepo use wget for sourceforge and rename the files (stripping off "?viasf=1")?  Should SBo discourage URL encoding in filenames?

I don't use slackrepo, but from looking at its output, it's not
checking for the source file itself: the error comes from tar, when
the SlackBuild tries to extract the source.

Probably the best solution is to have the SlackBuild handle all the
possible filenames the source might be saved as. The '?viasf=1' part
could be handled by putting a * at the end (.tar.xz*)

From didier at slint.fr  Fri Jun 23 19:03:31 2023
From: didier at slint.fr (Didier Spaier)
Date: Fri, 23 Jun 2023 21:03:31 +0200
Subject: [Slackbuilds-users] slackrepo fails to build youtube-dl due to
 URL encoding
In-Reply-To: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>
References: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>
Message-ID: <914605c5-4bd8-17c3-8ad8-62399009ee50@slint.fr>

IMHO yt-dlp can replace youtube-dl with more features. A new version has been
released yesterday.
Didier

From ml at mareichelt.com  Fri Jun 23 19:43:34 2023
From: ml at mareichelt.com (Markus Reichelt)
Date: Fri, 23 Jun 2023 21:43:34 +0200
Subject: [Slackbuilds-users] slackrepo fails to build youtube-dl due to
 URL encoding
In-Reply-To: <914605c5-4bd8-17c3-8ad8-62399009ee50@slint.fr>
References: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>
 <914605c5-4bd8-17c3-8ad8-62399009ee50@slint.fr>
Message-ID: <20230623194334.GC3975@pc21.mareichelt.com>

* Didier Spaier <didier at slint.fr> wrote:

> IMHO yt-dlp can replace youtube-dl with more features. A new version has been
> released yesterday.

Ack. I have been happily using it for quite some time.


From urchlay at slackware.uk  Fri Jun 23 20:26:06 2023
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 23 Jun 2023 16:26:06 -0400 (EDT)
Subject: [Slackbuilds-users] slackrepo fails to build youtube-dl due to
 URL encoding
In-Reply-To: <914605c5-4bd8-17c3-8ad8-62399009ee50@slint.fr>
References: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>
 <914605c5-4bd8-17c3-8ad8-62399009ee50@slint.fr>
Message-ID: <42256d2f-3dd8-7d67-684-6c6b65d73497@slackware.uk>



On Fri, 23 Jun 2023, Didier Spaier wrote:

> IMHO yt-dlp can replace youtube-dl with more features. A new version has been
> released yesterday.

We already have yt-dlp... and now that you mentioned it's been
updated, I've just updated the version on SBo :)

From urchlay at slackware.uk  Fri Jun 23 21:00:07 2023
From: urchlay at slackware.uk (B. Watson)
Date: Fri, 23 Jun 2023 17:00:07 -0400 (EDT)
Subject: [Slackbuilds-users] slackrepo fails to build youtube-dl due to
 URL encoding
In-Reply-To: <20230623194334.GC3975@pc21.mareichelt.com>
References: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>
 <914605c5-4bd8-17c3-8ad8-62399009ee50@slint.fr>
 <20230623194334.GC3975@pc21.mareichelt.com>
Message-ID: <8681777e-ca56-6f4a-c4b1-6f31e0ada5e@slackware.uk>



On Fri, 23 Jun 2023, Markus Reichelt via SlackBuilds-users wrote:

> * Didier Spaier <didier at slint.fr> wrote:
>
>> IMHO yt-dlp can replace youtube-dl with more features. A new version has been
>> released yesterday.
>
> Ack. I have been happily using it for quite some time.

Nothing wrong with having them both in the repo.

We have both vlc and mpv, and Slackware has both gcc and clang...

From jebrhansen+SBo at gmail.com  Fri Jun 23 23:40:48 2023
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Fri, 23 Jun 2023 16:40:48 -0700
Subject: [Slackbuilds-users] slackrepo fails to build youtube-dl due to
 URL encoding
In-Reply-To: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>
References: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>
Message-ID: <CANi9qSte0G2kXVA5yRXt-k+He8H3mpMoUrQDtUyNbaSBgCdKbg@mail.gmail.com>

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

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


Have you tried the download_basename pragma in your hintfile?

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

Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230623/74f5b47f/attachment-0001.htm>

From ed at fletcher.ca  Sat Jun 24 00:37:11 2023
From: ed at fletcher.ca (Ed Fletcher)
Date: Fri, 23 Jun 2023 17:37:11 -0700
Subject: [Slackbuilds-users] sboinstall chromprint fails
In-Reply-To: <CAPsDuS6cdfKqHPZZQJTyGO0zu6C_XEVahBVnU+Fn0VZx-p+OvA@mail.gmail.com>
References: <b6c1bb64-6bea-a220-6710-9b530d5322f4@fletcher.ca>
 <CAPsDuS6cdfKqHPZZQJTyGO0zu6C_XEVahBVnU+Fn0VZx-p+OvA@mail.gmail.com>
Message-ID: <dd88e954-0441-29d7-c9cc-ddd9b9ec7fba@fletcher.ca>

I don't think so.  I've got sbotools v2.7 and didn't make any 
configuration changes.  My understanding is that sbo gets the version of 
slackware from the system it's running on and uses that to get the 
correct packages.  Perhaps from /etc/slackware-version?  Mine says 
Slackware 15.0 and doesn't mention 64.

The only place I can find current mentioned is in the README in 
/usr/sbo/repo, which points to https://github.com/Ponce/slackbuilds/wiki

That page mentions configuring the current repository with sbopkg in 
/etc/sbopkg/sbopkg.conf but that page is old, from before 15.0.

I don't have that directory in /etc so I don't see where to point 
sbotools to current.

Thanks for looking at this Matteo.  I was hoping it was an easy fix.  I 
don't need it for chromaprint or vlc but I thought it might help me with 
my printer.

Ed

On 6/22/23 23:35, Matteo Bernardini wrote:
> hi Ed,
> 
> could it be that you have configured with sbotools a repository for 
> Slackware current while you are running slackware 15.0?
> 
> Matteo
> 
> Il giorno gio 22 giu 2023 alle ore 23:59 Ed Fletcher <ed at fletcher.ca 
> <mailto:ed at fletcher.ca>> ha scritto:
> 
>     While using sbo to put vlc on a freshly installed and updated
>     Slackware64-15.0 (sboinstall vlc), the process failed on
>     chromaprint.? I
>     tried chromaprint by itself (sboinstall chromaprint) but it failed with
>     the same error:
> 
>     In file included from
>     /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18,
>      ? ? ? ? ? ? ? ? ? from /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7:
>     /usr/include/libavcodec/avcodec.h:3047:5: note: declared here
>      ? 3047 | int avcodec_decode_audio4(AVCodecContext *avctx, AVFrame
>     *frame,
>      ? ? ? ?|? ? ?^~~~~~~~~~~~~~~~~~~~~
>     make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/build.make:76:
>     src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1
>     make[1]: *** [CMakeFiles/Makefile2:244:
>     src/cmd/CMakeFiles/fpcalc.dir/all] Error 2
>     make: *** [Makefile:136: all] Error 2
>     Failures:
>      ? ?chromaprint: chromaprint.SlackBuild return non-zero
> 
>     What I find strange is that downloading the source and the slackbuild
>     let me install it successfully.? This let sboinstall finish installing
>     vlc.? So I have everything working, just left with a puzzle.
> 
>     Ed
>     -- 
>     Ed Fletcher
> 
>     "When I became a man I put away childish things, including the fear of
>     childishness and the desire to be very grown up.?
>     ? C.S. Lewis
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>     Archives -
>     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>     FAQ - https://slackbuilds.org/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/
> 

-- 
Ed Fletcher

"When I became a man I put away childish things, including the fear of 
childishness and the desire to be very grown up.?
? C.S. Lewis

From erich.public at protonmail.com  Sat Jun 24 01:01:13 2023
From: erich.public at protonmail.com (Erich Ritz)
Date: Sat, 24 Jun 2023 01:01:13 +0000
Subject: [Slackbuilds-users] slackrepo fails to build youtube-dl due to
 URL encoding
In-Reply-To: <CANi9qSte0G2kXVA5yRXt-k+He8H3mpMoUrQDtUyNbaSBgCdKbg@mail.gmail.com>
References: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>
 <CANi9qSte0G2kXVA5yRXt-k+He8H3mpMoUrQDtUyNbaSBgCdKbg@mail.gmail.com>
Message-ID: <4L1r_ngg1NClzSeFmMVTJY-Kr5_fJmPN_bg1-gNTsJezWrI3vmKpdgUR4FdeIopmzjLDGKrW3_mrdGgB5BWz6uCx-_6a1DBiQzl7Nt2zsPQ=@protonmail.com>

------- Original Message -------
On Friday, June 23rd, 2023 at 6:40 PM, Jeremy Hansen <jebrhansen+SBo at gmail.com> wrote:


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

Thank you!  I had to specify both PRAGMA and DOWNLOAD (use "+" in the download URL):

$ cat /var/lib/slackrepo/etr/hintfiles/youtube-dl.hint 
PRAGMA="download_basename"
DOWNLOAD="https://downloads.sourceforge.net/project/dslackw/src/youtube-dl-2021.12.17+20230618_07af47960.tar.xz"

Now I'll just have to remember to update the DOWNLOAD URL in my hintfile next time it is updated...

Maybe a new PRAGMA could be added to replace DOWNLOAD URLs with decoded versions?

Erich

From matteo.bernardini at gmail.com  Sat Jun 24 05:04:19 2023
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 24 Jun 2023 07:04:19 +0200
Subject: [Slackbuilds-users] sboinstall chromprint fails
In-Reply-To: <dd88e954-0441-29d7-c9cc-ddd9b9ec7fba@fletcher.ca>
References: <b6c1bb64-6bea-a220-6710-9b530d5322f4@fletcher.ca>
 <CAPsDuS6cdfKqHPZZQJTyGO0zu6C_XEVahBVnU+Fn0VZx-p+OvA@mail.gmail.com>
 <dd88e954-0441-29d7-c9cc-ddd9b9ec7fba@fletcher.ca>
Message-ID: <CAPsDuS7Qs_dTOW8pFpN19xr_+gfZJTVrAexafa_mcgz3BW9vMA@mail.gmail.com>

Hi Ed,

I start by saying that I don't use sbotools so I don't know how it works.

if you have the possibility to paste the content of chromaprint.SlackBuild
as cointained in your local repository used by sbotools (not the one you
downloaded manually) it might help.

FWIW let me say that chromaprint has nothing to do with printers (please
have a look at its README)...

Matteo

Il giorno sab 24 giu 2023 alle ore 02:43 Ed Fletcher <ed at fletcher.ca> ha
scritto:

> I don't think so.  I've got sbotools v2.7 and didn't make any
> configuration changes.  My understanding is that sbo gets the version of
> slackware from the system it's running on and uses that to get the
> correct packages.  Perhaps from /etc/slackware-version?  Mine says
> Slackware 15.0 and doesn't mention 64.
>
> The only place I can find current mentioned is in the README in
> /usr/sbo/repo, which points to https://github.com/Ponce/slackbuilds/wiki
>
> That page mentions configuring the current repository with sbopkg in
> /etc/sbopkg/sbopkg.conf but that page is old, from before 15.0.
>
> I don't have that directory in /etc so I don't see where to point
> sbotools to current.
>
> Thanks for looking at this Matteo.  I was hoping it was an easy fix.  I
> don't need it for chromaprint or vlc but I thought it might help me with
> my printer.
>
> Ed
>
> On 6/22/23 23:35, Matteo Bernardini wrote:
> > hi Ed,
> >
> > could it be that you have configured with sbotools a repository for
> > Slackware current while you are running slackware 15.0?
> >
> > Matteo
> >
> > Il giorno gio 22 giu 2023 alle ore 23:59 Ed Fletcher <ed at fletcher.ca
> > <mailto:ed at fletcher.ca>> ha scritto:
> >
> >     While using sbo to put vlc on a freshly installed and updated
> >     Slackware64-15.0 (sboinstall vlc), the process failed on
> >     chromaprint.  I
> >     tried chromaprint by itself (sboinstall chromaprint) but it failed
> with
> >     the same error:
> >
> >     In file included from
> >     /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18,
> >                        from
> /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7:
> >     /usr/include/libavcodec/avcodec.h:3047:5: note: declared here
> >        3047 | int avcodec_decode_audio4(AVCodecContext *avctx, AVFrame
> >     *frame,
> >             |     ^~~~~~~~~~~~~~~~~~~~~
> >     make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/build.make:76:
> >     src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1
> >     make[1]: *** [CMakeFiles/Makefile2:244:
> >     src/cmd/CMakeFiles/fpcalc.dir/all] Error 2
> >     make: *** [Makefile:136: all] Error 2
> >     Failures:
> >         chromaprint: chromaprint.SlackBuild return non-zero
> >
> >     What I find strange is that downloading the source and the slackbuild
> >     let me install it successfully.  This let sboinstall finish
> installing
> >     vlc.  So I have everything working, just left with a puzzle.
> >
> >     Ed
> >     --
> >     Ed Fletcher
> >
> >     "When I became a man I put away childish things, including the fear
> of
> >     childishness and the desire to be very grown up.?
> >     ? C.S. Lewis
> >     _______________________________________________
> >     SlackBuilds-users mailing list
> >     SlackBuilds-users at slackbuilds.org
> >     <mailto:SlackBuilds-users at slackbuilds.org>
> >     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >     Archives -
> >     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >     FAQ - https://slackbuilds.org/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/
> >
>
> --
> Ed Fletcher
>
> "When I became a man I put away childish things, including the fear of
> childishness and the desire to be very grown up.?
> ? C.S. Lewis
> _______________________________________________
> 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/20230624/db1916cd/attachment.htm>

From ed at fletcher.ca  Sat Jun 24 06:43:25 2023
From: ed at fletcher.ca (Ed Fletcher)
Date: Fri, 23 Jun 2023 23:43:25 -0700
Subject: [Slackbuilds-users] sboinstall chromprint fails
In-Reply-To: <CAPsDuS7Qs_dTOW8pFpN19xr_+gfZJTVrAexafa_mcgz3BW9vMA@mail.gmail.com>
References: <b6c1bb64-6bea-a220-6710-9b530d5322f4@fletcher.ca>
 <CAPsDuS6cdfKqHPZZQJTyGO0zu6C_XEVahBVnU+Fn0VZx-p+OvA@mail.gmail.com>
 <dd88e954-0441-29d7-c9cc-ddd9b9ec7fba@fletcher.ca>
 <CAPsDuS7Qs_dTOW8pFpN19xr_+gfZJTVrAexafa_mcgz3BW9vMA@mail.gmail.com>
Message-ID: <ba91286b-745b-53c5-2f13-86ff5447817c@fletcher.ca>

Hi Matteo:

Yes, but I was hoping that having a .current repo might explain my 
printer problem.  Oh well.

This might be a pointless exercise and I don't want to waste your time. 
VLC is working for me, which is what depends on chromaprint.  Just had 
to install chromaprint the old way.  I only posted this originally in 
case someone involved with sbotools might be interested.

diff shows the two files to be identical.  So I don't think the problem 
is here.  Regardless, this is the file
/tmp/SBo/package-chromaprint/usr/doc/chromaprint-1.5.1/chromaprint.SlackBuild

#!/bin/bash

# Slackware build script for chromaprint

# Copyright 2012-2022 Matteo Bernardini <ponce at slackbuilds.org>, Pisa, Italy
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR 
IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 
LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 
PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

cd $(dirname $0) ; CWD=$(pwd)

PRGNAM=chromaprint
VERSION=${VERSION:-1.5.1}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}
PKGTYPE=${PKGTYPE:-tgz}

if [ -z "$ARCH" ]; then
   case "$( uname -m )" in
     i?86) ARCH=i586 ;;
     arm*) ARCH=arm ;;
        *) ARCH=$( uname -m ) ;;
   esac
fi

# If the variable PRINT_PACKAGE_NAME is set, then this script will 
report what
# the name of the created package would be, and then exit. This information
# could be useful to other scripts.
if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
   echo "$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE"
   exit 0
fi

TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}

if [ "$ARCH" = "i586" ]; then
   SLKCFLAGS="-O2 -march=i586 -mtune=i686"
   LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
   SLKCFLAGS="-O2 -march=i686 -mtune=i686"
   LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
   LIBDIRSUFFIX="64"
else
   SLKCFLAGS="-O2"
   LIBDIRSUFFIX=""
fi

if pkg-config --exists libavcodec; then tools="-DBUILD_TOOLS=ON"; else 
tools=""; fi

DOCS="LICENSE.md NEWS.txt README.md"

set -e

rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$VERSION
tar xvf $CWD/$PRGNAM-$VERSION.tar.?z*
cd $PRGNAM-$VERSION
chown -R root:root .
find -L . \
  \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
  -o -perm 511 \) -exec chmod 755 {} \; -o \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

mkdir -p build
cd build
   cmake \
     -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
     -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
     -DCMAKE_INSTALL_PREFIX=/usr \
     -DLIB_SUFFIX=${LIBDIRSUFFIX} \
     $tools \
     -DCMAKE_BUILD_TYPE=Release ..
   make
   make install DESTDIR=$PKG
cd ..

find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared 
object" | grep ELF \
   | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true

mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a $DOCS $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > 
$PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild

mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE


There's a third copy here
/usr/doc/chromaprint-1.5.1/chromaprint.SlackBuild
diff shows it as identical to the other two.

Ed

On 6/23/23 22:04, Matteo Bernardini wrote:
> Hi Ed,
> 
> I start by saying that I don't use sbotools so I don't know how it works.
> 
> if you have the possibility to paste the content of 
> chromaprint.SlackBuild as cointained in your local repository used by 
> sbotools (not the one you downloaded manually) it might help.
> 
> FWIW let me say that chromaprint has nothing to do with printers (please 
> have a look at its README)...
> 
> Matteo
> 
> Il giorno sab 24 giu 2023 alle ore 02:43 Ed Fletcher <ed at fletcher.ca 
> <mailto:ed at fletcher.ca>> ha scritto:
> 
>     I don't think so.? I've got sbotools v2.7 and didn't make any
>     configuration changes.? My understanding is that sbo gets the
>     version of
>     slackware from the system it's running on and uses that to get the
>     correct packages.? Perhaps from /etc/slackware-version?? Mine says
>     Slackware 15.0 and doesn't mention 64.
> 
>     The only place I can find current mentioned is in the README in
>     /usr/sbo/repo, which points to
>     https://github.com/Ponce/slackbuilds/wiki
>     <https://github.com/Ponce/slackbuilds/wiki>
> 
>     That page mentions configuring the current repository with sbopkg in
>     /etc/sbopkg/sbopkg.conf but that page is old, from before 15.0.
> 
>     I don't have that directory in /etc so I don't see where to point
>     sbotools to current.
> 
>     Thanks for looking at this Matteo.? I was hoping it was an easy fix.? I
>     don't need it for chromaprint or vlc but I thought it might help me
>     with
>     my printer.
> 
>     Ed
> 
>     On 6/22/23 23:35, Matteo Bernardini wrote:
>      > hi Ed,
>      >
>      > could it be that you have configured with sbotools a repository for
>      > Slackware current while you are running slackware 15.0?
>      >
>      > Matteo
>      >
>      > Il giorno gio 22 giu 2023 alle ore 23:59 Ed Fletcher
>     <ed at fletcher.ca <mailto:ed at fletcher.ca>
>      > <mailto:ed at fletcher.ca <mailto:ed at fletcher.ca>>> ha scritto:
>      >
>      >? ? ?While using sbo to put vlc on a freshly installed and updated
>      >? ? ?Slackware64-15.0 (sboinstall vlc), the process failed on
>      >? ? ?chromaprint.? I
>      >? ? ?tried chromaprint by itself (sboinstall chromaprint) but it
>     failed with
>      >? ? ?the same error:
>      >
>      >? ? ?In file included from
>      >? ? ?/tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18,
>      >? ? ? ? ? ? ? ? ? ? ? ? from
>     /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7:
>      >? ? ?/usr/include/libavcodec/avcodec.h:3047:5: note: declared here
>      >? ? ? ? 3047 | int avcodec_decode_audio4(AVCodecContext *avctx,
>     AVFrame
>      >? ? ?*frame,
>      >? ? ? ? ? ? ?|? ? ?^~~~~~~~~~~~~~~~~~~~~
>      >? ? ?make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/build.make:76:
>      >? ? ?src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1
>      >? ? ?make[1]: *** [CMakeFiles/Makefile2:244:
>      >? ? ?src/cmd/CMakeFiles/fpcalc.dir/all] Error 2
>      >? ? ?make: *** [Makefile:136: all] Error 2
>      >? ? ?Failures:
>      >? ? ? ? ?chromaprint: chromaprint.SlackBuild return non-zero
>      >
>      >? ? ?What I find strange is that downloading the source and the
>     slackbuild
>      >? ? ?let me install it successfully.? This let sboinstall finish
>     installing
>      >? ? ?vlc.? So I have everything working, just left with a puzzle.
>      >
>      >? ? ?Ed
>      >? ? ?--
>      >? ? ?Ed Fletcher
>      >
>      >? ? ?"When I became a man I put away childish things, including
>     the fear of
>      >? ? ?childishness and the desire to be very grown up.?
>      >? ? ?? C.S. Lewis
>      >? ? ?_______________________________________________
>      >? ? ?SlackBuilds-users mailing list
>      > SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>      >? ? ?<mailto:SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>>
>      > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>      >   
>      ?<https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>>
>      >? ? ?Archives -
>      > https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>      >? ? ?<https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>>
>      >? ? ?FAQ - https://slackbuilds.org/faq/
>     <https://slackbuilds.org/faq/> <https://slackbuilds.org/faq/
>     <https://slackbuilds.org/faq/>>
>      >
>      >
>      > _______________________________________________
>      > SlackBuilds-users mailing list
>      > SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>      > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>      > Archives -
>     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>      > FAQ - https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/>
>      >
> 
>     -- 
>     Ed Fletcher
> 
>     "When I became a man I put away childish things, including the fear of
>     childishness and the desire to be very grown up.?
>     ? C.S. Lewis
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>     Archives -
>     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>     FAQ - https://slackbuilds.org/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/
> 

-- 
Ed Fletcher

"When I became a man I put away childish things, including the fear of 
childishness and the desire to be very grown up.?
? C.S. Lewis

From matteo.bernardini at gmail.com  Sat Jun 24 10:39:56 2023
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 24 Jun 2023 12:39:56 +0200
Subject: [Slackbuilds-users] sboinstall chromprint fails
In-Reply-To: <ba91286b-745b-53c5-2f13-86ff5447817c@fletcher.ca>
References: <b6c1bb64-6bea-a220-6710-9b530d5322f4@fletcher.ca>
 <CAPsDuS6cdfKqHPZZQJTyGO0zu6C_XEVahBVnU+Fn0VZx-p+OvA@mail.gmail.com>
 <dd88e954-0441-29d7-c9cc-ddd9b9ec7fba@fletcher.ca>
 <CAPsDuS7Qs_dTOW8pFpN19xr_+gfZJTVrAexafa_mcgz3BW9vMA@mail.gmail.com>
 <ba91286b-745b-53c5-2f13-86ff5447817c@fletcher.ca>
Message-ID: <CAPsDuS7Y11spAT92vG=B+bHbC80w1m0Sdkd8CsMDG8v63E_drw@mail.gmail.com>

Hi Ed,

I'm not sure where sbotools keeps the local copy of the repo, maybe
/usr/sbo or something similar.
The two SlackBuild you've found are the one in the working directory
generated when you built it manually and the one installed from the
generated package (so not the one in the local repo).

Matteo


Il sab 24 giu 2023, 08:49 Ed Fletcher <ed at fletcher.ca> ha scritto:

> Hi Matteo:
>
> Yes, but I was hoping that having a .current repo might explain my
> printer problem.  Oh well.
>
> This might be a pointless exercise and I don't want to waste your time.
> VLC is working for me, which is what depends on chromaprint.  Just had
> to install chromaprint the old way.  I only posted this originally in
> case someone involved with sbotools might be interested.
>
> diff shows the two files to be identical.  So I don't think the problem
> is here.  Regardless, this is the file
>
> /tmp/SBo/package-chromaprint/usr/doc/chromaprint-1.5.1/chromaprint.SlackBuild
>
> #!/bin/bash
>
> # Slackware build script for chromaprint
>
> # Copyright 2012-2022 Matteo Bernardini <ponce at slackbuilds.org>, Pisa,
> Italy
> # All rights reserved.
> #
> # Redistribution and use of this script, with or without modification, is
> # permitted provided that the following conditions are met:
> #
> # 1. Redistributions of this script must retain the above copyright
> #    notice, this list of conditions and the following disclaimer.
> #
> #  THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR
> IMPLIED
> #  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
> #  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
> IN NO
> #  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
> #  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
> LIMITED TO,
> #  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
> PROFITS;
> #  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
> #  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
> #  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
> #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>
> cd $(dirname $0) ; CWD=$(pwd)
>
> PRGNAM=chromaprint
> VERSION=${VERSION:-1.5.1}
> BUILD=${BUILD:-1}
> TAG=${TAG:-_SBo}
> PKGTYPE=${PKGTYPE:-tgz}
>
> if [ -z "$ARCH" ]; then
>    case "$( uname -m )" in
>      i?86) ARCH=i586 ;;
>      arm*) ARCH=arm ;;
>         *) ARCH=$( uname -m ) ;;
>    esac
> fi
>
> # If the variable PRINT_PACKAGE_NAME is set, then this script will
> report what
> # the name of the created package would be, and then exit. This information
> # could be useful to other scripts.
> if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
>    echo "$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE"
>    exit 0
> fi
>
> TMP=${TMP:-/tmp/SBo}
> PKG=$TMP/package-$PRGNAM
> OUTPUT=${OUTPUT:-/tmp}
>
> if [ "$ARCH" = "i586" ]; then
>    SLKCFLAGS="-O2 -march=i586 -mtune=i686"
>    LIBDIRSUFFIX=""
> elif [ "$ARCH" = "i686" ]; then
>    SLKCFLAGS="-O2 -march=i686 -mtune=i686"
>    LIBDIRSUFFIX=""
> elif [ "$ARCH" = "x86_64" ]; then
>    SLKCFLAGS="-O2 -fPIC"
>    LIBDIRSUFFIX="64"
> else
>    SLKCFLAGS="-O2"
>    LIBDIRSUFFIX=""
> fi
>
> if pkg-config --exists libavcodec; then tools="-DBUILD_TOOLS=ON"; else
> tools=""; fi
>
> DOCS="LICENSE.md NEWS.txt README.md"
>
> set -e
>
> rm -rf $PKG
> mkdir -p $TMP $PKG $OUTPUT
> cd $TMP
> rm -rf $PRGNAM-$VERSION
> tar xvf $CWD/$PRGNAM-$VERSION.tar.?z*
> cd $PRGNAM-$VERSION
> chown -R root:root .
> find -L . \
>   \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
>   -o -perm 511 \) -exec chmod 755 {} \; -o \
>   \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
>   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
>
> mkdir -p build
> cd build
>    cmake \
>      -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
>      -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
>      -DCMAKE_INSTALL_PREFIX=/usr \
>      -DLIB_SUFFIX=${LIBDIRSUFFIX} \
>      $tools \
>      -DCMAKE_BUILD_TYPE=Release ..
>    make
>    make install DESTDIR=$PKG
> cd ..
>
> find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared
> object" | grep ELF \
>    | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
>
> mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
> cp -a $DOCS $PKG/usr/doc/$PRGNAM-$VERSION
> cat $CWD/$PRGNAM.SlackBuild >
> $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
>
> mkdir -p $PKG/install
> cat $CWD/slack-desc > $PKG/install/slack-desc
>
> cd $PKG
> /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE
>
>
> There's a third copy here
> /usr/doc/chromaprint-1.5.1/chromaprint.SlackBuild
> diff shows it as identical to the other two.
>
> Ed
>
> On 6/23/23 22:04, Matteo Bernardini wrote:
> > Hi Ed,
> >
> > I start by saying that I don't use sbotools so I don't know how it works.
> >
> > if you have the possibility to paste the content of
> > chromaprint.SlackBuild as cointained in your local repository used by
> > sbotools (not the one you downloaded manually) it might help.
> >
> > FWIW let me say that chromaprint has nothing to do with printers (please
> > have a look at its README)...
> >
> > Matteo
> >
> > Il giorno sab 24 giu 2023 alle ore 02:43 Ed Fletcher <ed at fletcher.ca
> > <mailto:ed at fletcher.ca>> ha scritto:
> >
> >     I don't think so.  I've got sbotools v2.7 and didn't make any
> >     configuration changes.  My understanding is that sbo gets the
> >     version of
> >     slackware from the system it's running on and uses that to get the
> >     correct packages.  Perhaps from /etc/slackware-version?  Mine says
> >     Slackware 15.0 and doesn't mention 64.
> >
> >     The only place I can find current mentioned is in the README in
> >     /usr/sbo/repo, which points to
> >     https://github.com/Ponce/slackbuilds/wiki
> >     <https://github.com/Ponce/slackbuilds/wiki>
> >
> >     That page mentions configuring the current repository with sbopkg in
> >     /etc/sbopkg/sbopkg.conf but that page is old, from before 15.0.
> >
> >     I don't have that directory in /etc so I don't see where to point
> >     sbotools to current.
> >
> >     Thanks for looking at this Matteo.  I was hoping it was an easy
> fix.  I
> >     don't need it for chromaprint or vlc but I thought it might help me
> >     with
> >     my printer.
> >
> >     Ed
> >
> >     On 6/22/23 23:35, Matteo Bernardini wrote:
> >      > hi Ed,
> >      >
> >      > could it be that you have configured with sbotools a repository
> for
> >      > Slackware current while you are running slackware 15.0?
> >      >
> >      > Matteo
> >      >
> >      > Il giorno gio 22 giu 2023 alle ore 23:59 Ed Fletcher
> >     <ed at fletcher.ca <mailto:ed at fletcher.ca>
> >      > <mailto:ed at fletcher.ca <mailto:ed at fletcher.ca>>> ha scritto:
> >      >
> >      >     While using sbo to put vlc on a freshly installed and updated
> >      >     Slackware64-15.0 (sboinstall vlc), the process failed on
> >      >     chromaprint.  I
> >      >     tried chromaprint by itself (sboinstall chromaprint) but it
> >     failed with
> >      >     the same error:
> >      >
> >      >     In file included from
> >      >     /tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18,
> >      >                        from
> >     /tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7:
> >      >     /usr/include/libavcodec/avcodec.h:3047:5: note: declared here
> >      >        3047 | int avcodec_decode_audio4(AVCodecContext *avctx,
> >     AVFrame
> >      >     *frame,
> >      >             |     ^~~~~~~~~~~~~~~~~~~~~
> >      >     make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/build.make:76:
> >      >     src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1
> >      >     make[1]: *** [CMakeFiles/Makefile2:244:
> >      >     src/cmd/CMakeFiles/fpcalc.dir/all] Error 2
> >      >     make: *** [Makefile:136: all] Error 2
> >      >     Failures:
> >      >         chromaprint: chromaprint.SlackBuild return non-zero
> >      >
> >      >     What I find strange is that downloading the source and the
> >     slackbuild
> >      >     let me install it successfully.  This let sboinstall finish
> >     installing
> >      >     vlc.  So I have everything working, just left with a puzzle.
> >      >
> >      >     Ed
> >      >     --
> >      >     Ed Fletcher
> >      >
> >      >     "When I became a man I put away childish things, including
> >     the fear of
> >      >     childishness and the desire to be very grown up.?
> >      >     ? C.S. Lewis
> >      >     _______________________________________________
> >      >     SlackBuilds-users mailing list
> >      > SlackBuilds-users at slackbuilds.org
> >     <mailto:SlackBuilds-users at slackbuilds.org>
> >      >     <mailto:SlackBuilds-users at slackbuilds.org
> >     <mailto:SlackBuilds-users at slackbuilds.org>>
> >      > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >      >
> >       <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>>
> >      >     Archives -
> >      > https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >      >     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>>
> >      >     FAQ - https://slackbuilds.org/faq/
> >     <https://slackbuilds.org/faq/> <https://slackbuilds.org/faq/
> >     <https://slackbuilds.org/faq/>>
> >      >
> >      >
> >      > _______________________________________________
> >      > SlackBuilds-users mailing list
> >      > SlackBuilds-users at slackbuilds.org
> >     <mailto:SlackBuilds-users at slackbuilds.org>
> >      > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >      > Archives -
> >     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >      > FAQ - https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/>
> >      >
> >
> >     --
> >     Ed Fletcher
> >
> >     "When I became a man I put away childish things, including the fear
> of
> >     childishness and the desire to be very grown up.?
> >     ? C.S. Lewis
> >     _______________________________________________
> >     SlackBuilds-users mailing list
> >     SlackBuilds-users at slackbuilds.org
> >     <mailto:SlackBuilds-users at slackbuilds.org>
> >     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >     Archives -
> >     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >     FAQ - https://slackbuilds.org/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/
> >
>
> --
> Ed Fletcher
>
> "When I became a man I put away childish things, including the fear of
> childishness and the desire to be very grown up.?
> ? C.S. Lewis
> _______________________________________________
> 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/20230624/2fb80b21/attachment-0001.htm>

From lists at osh.id.au  Sat Jun 24 13:28:49 2023
From: lists at osh.id.au (David O'Shaughnessy)
Date: Sat, 24 Jun 2023 21:28:49 +0800
Subject: [Slackbuilds-users] sboinstall chromprint fails
In-Reply-To: <dd88e954-0441-29d7-c9cc-ddd9b9ec7fba@fletcher.ca>
References: <b6c1bb64-6bea-a220-6710-9b530d5322f4@fletcher.ca>
 <CAPsDuS6cdfKqHPZZQJTyGO0zu6C_XEVahBVnU+Fn0VZx-p+OvA@mail.gmail.com>
 <dd88e954-0441-29d7-c9cc-ddd9b9ec7fba@fletcher.ca>
Message-ID: <f0a5adbf-a439-4662-b2d5-df28a3674100@app.fastmail.com>

On Sat, 24 Jun 2023, at 8:37 AM, Ed Fletcher wrote:
> I don't think so.  I've got sbotools v2.7 and didn't make any 
> configuration changes.  My understanding is that sbo gets the version of 
> slackware from the system it's running on and uses that to get the 
> correct packages.  Perhaps from /etc/slackware-version?  Mine says 
> Slackware 15.0 and doesn't mention 64.

By default sbotools will not be set up for 15.0 though. You can check with:
grep "url = " /usr/sbo/repo/.git/config

In /etc/sbotools/sbotools.conf I've got:
REPO=https://gitlab.com/SlackBuilds.org/slackbuilds.git

To put sbotools onto a 15.0 repo.

--
Dave

From andrew.clemons at gmail.com  Sun Jun 25 11:10:24 2023
From: andrew.clemons at gmail.com (Andrew Clemons)
Date: Sun, 25 Jun 2023 20:10:24 +0900
Subject: [Slackbuilds-users] slackrepo fails to build youtube-dl due to
 URL encoding
In-Reply-To: <4L1r_ngg1NClzSeFmMVTJY-Kr5_fJmPN_bg1-gNTsJezWrI3vmKpdgUR4FdeIopmzjLDGKrW3_mrdGgB5BWz6uCx-_6a1DBiQzl7Nt2zsPQ=@protonmail.com>
References: <ES9_9RtkipNowGSV_OZYmQrj3ffqh3Q7zkmOGqBQq5tA0zOKbNgEutxRrAjezLlPQrQ_0WeHYkTnqqYUX_fgP9qSFI9f62_a5gTABgj6DQg=@protonmail.com>
 <CANi9qSte0G2kXVA5yRXt-k+He8H3mpMoUrQDtUyNbaSBgCdKbg@mail.gmail.com>
 <4L1r_ngg1NClzSeFmMVTJY-Kr5_fJmPN_bg1-gNTsJezWrI3vmKpdgUR4FdeIopmzjLDGKrW3_mrdGgB5BWz6uCx-_6a1DBiQzl7Nt2zsPQ=@protonmail.com>
Message-ID: <4bfc3b51-afa0-ee4a-c7d7-809b83820623@gmail.com>

On 24/06/23 10:01, Erich Ritz via SlackBuilds-users wrote:
> [..]
> Thank you!  I had to specify both PRAGMA and DOWNLOAD (use "+" in the download URL):
> 
> $ cat /var/lib/slackrepo/etr/hintfiles/youtube-dl.hint
> PRAGMA="download_basename"
> DOWNLOAD="https://downloads.sourceforge.net/project/dslackw/src/youtube-dl-2021.12.17+20230618_07af47960.tar.xz"
> 
> Now I'll just have to remember to update the DOWNLOAD URL in my hintfile next time it is updated...
> 
> Maybe a new PRAGMA could be added to replace DOWNLOAD URLs with decoded versions?

This seems reasonable to me. I opened an issue for this in the slackrepo 
git repo. Let's take this discussion over there.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230625/dfeeea42/attachment.asc>

From fernando.lopezjr at gmail.com  Sun Jun 25 19:54:35 2023
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sun, 25 Jun 2023 14:54:35 -0500
Subject: [Slackbuilds-users] argyllcms owner.
Message-ID: <CALrQ46DdXaMsAcMtQ7cqEdzLW+Qfir4s=atoFC-fqTNJEUJdnQ@mail.gmail.com>

Can you guys change owner to me on argyllcms sbo. It was approved a week
ago (or two).

thank you.

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230625/82229a49/attachment.htm>

From urchlay at slackware.uk  Sun Jun 25 20:12:23 2023
From: urchlay at slackware.uk (B. Watson)
Date: Sun, 25 Jun 2023 16:12:23 -0400 (EDT)
Subject: [Slackbuilds-users] argyllcms owner.
In-Reply-To: <CALrQ46DdXaMsAcMtQ7cqEdzLW+Qfir4s=atoFC-fqTNJEUJdnQ@mail.gmail.com>
References: <CALrQ46DdXaMsAcMtQ7cqEdzLW+Qfir4s=atoFC-fqTNJEUJdnQ@mail.gmail.com>
Message-ID: <2ee44fca-e4a9-e093-22e8-6e8338e41894@slackware.uk>



On Sun, 25 Jun 2023, Fernando Lopez wrote:

> Can you guys change owner to me on?argyllcms sbo. It was approved?a week ago (or two).
> thank you.

Done, on my branch. Will be merged in the next weekly update.

From fernando.lopezjr at gmail.com  Sun Jun 25 20:14:22 2023
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sun, 25 Jun 2023 15:14:22 -0500
Subject: [Slackbuilds-users] argyllcms owner.
In-Reply-To: <2ee44fca-e4a9-e093-22e8-6e8338e41894@slackware.uk>
References: <CALrQ46DdXaMsAcMtQ7cqEdzLW+Qfir4s=atoFC-fqTNJEUJdnQ@mail.gmail.com>
 <2ee44fca-e4a9-e093-22e8-6e8338e41894@slackware.uk>
Message-ID: <CALrQ46Be80N8yzefFNarDuvvdoVYwjHSyyf1rXi0T9zZbq2ZcQ@mail.gmail.com>

thank you sir!

On Sun, Jun 25, 2023 at 3:12?PM B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Sun, 25 Jun 2023, Fernando Lopez wrote:
>
> > Can you guys change owner to me on argyllcms sbo. It was approved a week
> ago (or two).
> > thank you.
>
> Done, on my branch. Will be merged in the next weekly
> update._______________________________________________
> 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/
>
>

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230625/f80375b1/attachment.htm>

From ed at fletcher.ca  Mon Jun 26 03:23:54 2023
From: ed at fletcher.ca (Ed Fletcher)
Date: Sun, 25 Jun 2023 20:23:54 -0700
Subject: [Slackbuilds-users] sboinstall chromprint fails
In-Reply-To: <CAPsDuS7Y11spAT92vG=B+bHbC80w1m0Sdkd8CsMDG8v63E_drw@mail.gmail.com>
References: <b6c1bb64-6bea-a220-6710-9b530d5322f4@fletcher.ca>
 <CAPsDuS6cdfKqHPZZQJTyGO0zu6C_XEVahBVnU+Fn0VZx-p+OvA@mail.gmail.com>
 <dd88e954-0441-29d7-c9cc-ddd9b9ec7fba@fletcher.ca>
 <CAPsDuS7Qs_dTOW8pFpN19xr_+gfZJTVrAexafa_mcgz3BW9vMA@mail.gmail.com>
 <ba91286b-745b-53c5-2f13-86ff5447817c@fletcher.ca>
 <CAPsDuS7Y11spAT92vG=B+bHbC80w1m0Sdkd8CsMDG8v63E_drw@mail.gmail.com>
Message-ID: <56147763-7abb-8f71-3392-0075c5989fb1@fletcher.ca>

Hi Matteo:

I found a third copy in /usr/doc/chromaprint-1.5.1/ but that was 
identical to the other two.

The problem was indeed that sbotools was configured for current.  You 
had the right idea from the start.

Thanks again for your help,
Ed

On 6/24/23 03:39, Matteo Bernardini wrote:
> Hi Ed,
> 
> I'm not sure where sbotools keeps the local copy of the repo, maybe 
> /usr/sbo or something similar.
> The two SlackBuild you've found are the one in the working directory 
> generated when you built it manually and the one installed from the 
> generated package (so not the one in the local repo).
> 
> Matteo
> 
> 
> Il sab 24 giu 2023, 08:49 Ed Fletcher <ed at fletcher.ca 
> <mailto:ed at fletcher.ca>> ha scritto:
> 
>     Hi Matteo:
> 
>     Yes, but I was hoping that having a .current repo might explain my
>     printer problem.? Oh well.
> 
>     This might be a pointless exercise and I don't want to waste your time.
>     VLC is working for me, which is what depends on chromaprint.? Just had
>     to install chromaprint the old way.? I only posted this originally in
>     case someone involved with sbotools might be interested.
> 
>     diff shows the two files to be identical.? So I don't think the problem
>     is here.? Regardless, this is the file
>     /tmp/SBo/package-chromaprint/usr/doc/chromaprint-1.5.1/chromaprint.SlackBuild
> 
>     #!/bin/bash
> 
>     # Slackware build script for chromaprint
> 
>     # Copyright 2012-2022 Matteo Bernardini <ponce at slackbuilds.org
>     <mailto:ponce at slackbuilds.org>>, Pisa, Italy
>     # All rights reserved.
>     #
>     # Redistribution and use of this script, with or without
>     modification, is
>     # permitted provided that the following conditions are met:
>     #
>     # 1. Redistributions of this script must retain the above copyright
>     #? ? notice, this list of conditions and the following disclaimer.
>     #
>     #? THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR
>     IMPLIED
>     #? WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
>     #? MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
>     IN NO
>     #? EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
>     INCIDENTAL,
>     #? SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
>     LIMITED TO,
>     #? PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
>     PROFITS;
>     #? OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
>     LIABILITY,
>     #? WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
>     NEGLIGENCE OR
>     #? OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
>     EVEN IF
>     #? ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> 
>     cd $(dirname $0) ; CWD=$(pwd)
> 
>     PRGNAM=chromaprint
>     VERSION=${VERSION:-1.5.1}
>     BUILD=${BUILD:-1}
>     TAG=${TAG:-_SBo}
>     PKGTYPE=${PKGTYPE:-tgz}
> 
>     if [ -z "$ARCH" ]; then
>      ? ?case "$( uname -m )" in
>      ? ? ?i?86) ARCH=i586 ;;
>      ? ? ?arm*) ARCH=arm ;;
>      ? ? ? ? *) ARCH=$( uname -m ) ;;
>      ? ?esac
>     fi
> 
>     # If the variable PRINT_PACKAGE_NAME is set, then this script will
>     report what
>     # the name of the created package would be, and then exit. This
>     information
>     # could be useful to other scripts.
>     if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
>      ? ?echo "$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE"
>      ? ?exit 0
>     fi
> 
>     TMP=${TMP:-/tmp/SBo}
>     PKG=$TMP/package-$PRGNAM
>     OUTPUT=${OUTPUT:-/tmp}
> 
>     if [ "$ARCH" = "i586" ]; then
>      ? ?SLKCFLAGS="-O2 -march=i586 -mtune=i686"
>      ? ?LIBDIRSUFFIX=""
>     elif [ "$ARCH" = "i686" ]; then
>      ? ?SLKCFLAGS="-O2 -march=i686 -mtune=i686"
>      ? ?LIBDIRSUFFIX=""
>     elif [ "$ARCH" = "x86_64" ]; then
>      ? ?SLKCFLAGS="-O2 -fPIC"
>      ? ?LIBDIRSUFFIX="64"
>     else
>      ? ?SLKCFLAGS="-O2"
>      ? ?LIBDIRSUFFIX=""
>     fi
> 
>     if pkg-config --exists libavcodec; then tools="-DBUILD_TOOLS=ON"; else
>     tools=""; fi
> 
>     DOCS="LICENSE.md NEWS.txt README.md"
> 
>     set -e
> 
>     rm -rf $PKG
>     mkdir -p $TMP $PKG $OUTPUT
>     cd $TMP
>     rm -rf $PRGNAM-$VERSION
>     tar xvf $CWD/$PRGNAM-$VERSION.tar.?z*
>     cd $PRGNAM-$VERSION
>     chown -R root:root .
>     find -L . \
>      ? \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
>      ? -o -perm 511 \) -exec chmod 755 {} \; -o \
>      ? \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
>      ? -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
> 
>     mkdir -p build
>     cd build
>      ? ?cmake \
>      ? ? ?-DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
>      ? ? ?-DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
>      ? ? ?-DCMAKE_INSTALL_PREFIX=/usr \
>      ? ? ?-DLIB_SUFFIX=${LIBDIRSUFFIX} \
>      ? ? ?$tools \
>      ? ? ?-DCMAKE_BUILD_TYPE=Release ..
>      ? ?make
>      ? ?make install DESTDIR=$PKG
>     cd ..
> 
>     find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared
>     object" | grep ELF \
>      ? ?| cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
> 
>     mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
>     cp -a $DOCS $PKG/usr/doc/$PRGNAM-$VERSION
>     cat $CWD/$PRGNAM.SlackBuild >
>     $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
> 
>     mkdir -p $PKG/install
>     cat $CWD/slack-desc > $PKG/install/slack-desc
> 
>     cd $PKG
>     /sbin/makepkg -l y -c n
>     $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE
> 
> 
>     There's a third copy here
>     /usr/doc/chromaprint-1.5.1/chromaprint.SlackBuild
>     diff shows it as identical to the other two.
> 
>     Ed
> 
>     On 6/23/23 22:04, Matteo Bernardini wrote:
>      > Hi Ed,
>      >
>      > I start by saying that I don't use sbotools so I don't know how
>     it works.
>      >
>      > if you have the possibility to paste the content of
>      > chromaprint.SlackBuild as cointained in your local repository
>     used by
>      > sbotools (not the one you downloaded manually) it might help.
>      >
>      > FWIW let me say that chromaprint has nothing to do with printers
>     (please
>      > have a look at its README)...
>      >
>      > Matteo
>      >
>      > Il giorno sab 24 giu 2023 alle ore 02:43 Ed Fletcher
>     <ed at fletcher.ca <mailto:ed at fletcher.ca>
>      > <mailto:ed at fletcher.ca <mailto:ed at fletcher.ca>>> ha scritto:
>      >
>      >? ? ?I don't think so.? I've got sbotools v2.7 and didn't make any
>      >? ? ?configuration changes.? My understanding is that sbo gets the
>      >? ? ?version of
>      >? ? ?slackware from the system it's running on and uses that to
>     get the
>      >? ? ?correct packages.? Perhaps from /etc/slackware-version?? Mine
>     says
>      >? ? ?Slackware 15.0 and doesn't mention 64.
>      >
>      >? ? ?The only place I can find current mentioned is in the README in
>      >? ? ?/usr/sbo/repo, which points to
>      > https://github.com/Ponce/slackbuilds/wiki
>     <https://github.com/Ponce/slackbuilds/wiki>
>      >? ? ?<https://github.com/Ponce/slackbuilds/wiki
>     <https://github.com/Ponce/slackbuilds/wiki>>
>      >
>      >? ? ?That page mentions configuring the current repository with
>     sbopkg in
>      >? ? ?/etc/sbopkg/sbopkg.conf but that page is old, from before 15.0.
>      >
>      >? ? ?I don't have that directory in /etc so I don't see where to point
>      >? ? ?sbotools to current.
>      >
>      >? ? ?Thanks for looking at this Matteo.? I was hoping it was an
>     easy fix.? I
>      >? ? ?don't need it for chromaprint or vlc but I thought it might
>     help me
>      >? ? ?with
>      >? ? ?my printer.
>      >
>      >? ? ?Ed
>      >
>      >? ? ?On 6/22/23 23:35, Matteo Bernardini wrote:
>      >? ? ? > hi Ed,
>      >? ? ? >
>      >? ? ? > could it be that you have configured with sbotools a
>     repository for
>      >? ? ? > Slackware current while you are running slackware 15.0?
>      >? ? ? >
>      >? ? ? > Matteo
>      >? ? ? >
>      >? ? ? > Il giorno gio 22 giu 2023 alle ore 23:59 Ed Fletcher
>      >? ? ?<ed at fletcher.ca <mailto:ed at fletcher.ca>
>     <mailto:ed at fletcher.ca <mailto:ed at fletcher.ca>>
>      >? ? ? > <mailto:ed at fletcher.ca <mailto:ed at fletcher.ca>
>     <mailto:ed at fletcher.ca <mailto:ed at fletcher.ca>>>> ha scritto:
>      >? ? ? >
>      >? ? ? >? ? ?While using sbo to put vlc on a freshly installed and
>     updated
>      >? ? ? >? ? ?Slackware64-15.0 (sboinstall vlc), the process failed on
>      >? ? ? >? ? ?chromaprint.? I
>      >? ? ? >? ? ?tried chromaprint by itself (sboinstall chromaprint)
>     but it
>      >? ? ?failed with
>      >? ? ? >? ? ?the same error:
>      >? ? ? >
>      >? ? ? >? ? ?In file included from
>      >? ? ? >   
>      ?/tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18,
>      >? ? ? >? ? ? ? ? ? ? ? ? ? ? ? from
>      >? ? ?/tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7:
>      >? ? ? >? ? ?/usr/include/libavcodec/avcodec.h:3047:5: note:
>     declared here
>      >? ? ? >? ? ? ? 3047 | int avcodec_decode_audio4(AVCodecContext *avctx,
>      >? ? ?AVFrame
>      >? ? ? >? ? ?*frame,
>      >? ? ? >? ? ? ? ? ? ?|? ? ?^~~~~~~~~~~~~~~~~~~~~
>      >? ? ? >? ? ?make[2]: *** [src/cmd/CMakeFiles/fpcalc.dir/build.make:76:
>      >? ? ? >? ? ?src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1
>      >? ? ? >? ? ?make[1]: *** [CMakeFiles/Makefile2:244:
>      >? ? ? >? ? ?src/cmd/CMakeFiles/fpcalc.dir/all] Error 2
>      >? ? ? >? ? ?make: *** [Makefile:136: all] Error 2
>      >? ? ? >? ? ?Failures:
>      >? ? ? >? ? ? ? ?chromaprint: chromaprint.SlackBuild return non-zero
>      >? ? ? >
>      >? ? ? >? ? ?What I find strange is that downloading the source and the
>      >? ? ?slackbuild
>      >? ? ? >? ? ?let me install it successfully.? This let sboinstall
>     finish
>      >? ? ?installing
>      >? ? ? >? ? ?vlc.? So I have everything working, just left with a
>     puzzle.
>      >? ? ? >
>      >? ? ? >? ? ?Ed
>      >? ? ? >? ? ?--
>      >? ? ? >? ? ?Ed Fletcher
>      >? ? ? >
>      >? ? ? >? ? ?"When I became a man I put away childish things, including
>      >? ? ?the fear of
>      >? ? ? >? ? ?childishness and the desire to be very grown up.?
>      >? ? ? >? ? ?? C.S. Lewis
>      >? ? ? >? ? ?_______________________________________________
>      >? ? ? >? ? ?SlackBuilds-users mailing list
>      >? ? ? > SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>      >? ? ?<mailto:SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>>
>      >? ? ? >? ? ?<mailto:SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>      >? ? ?<mailto:SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>>>
>      >? ? ? >
>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>      >   
>      ?<https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>>
>      >? ? ? >
>      >     
>      ?<https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>      >   
>      ?<https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>>>
>      >? ? ? >? ? ?Archives -
>      >? ? ? > https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>      >? ? ?<https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>>
>      >? ? ? >   
>      ?<https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>      >? ? ?<https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>>>
>      >? ? ? >? ? ?FAQ - https://slackbuilds.org/faq/
>     <https://slackbuilds.org/faq/>
>      >? ? ?<https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/>>
>     <https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/>
>      >? ? ?<https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/>>>
>      >? ? ? >
>      >? ? ? >
>      >? ? ? > _______________________________________________
>      >? ? ? > SlackBuilds-users mailing list
>      >? ? ? > SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>      >? ? ?<mailto:SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>>
>      >? ? ? >
>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>      >   
>      ?<https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>>
>      >? ? ? > Archives -
>      > https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>      >? ? ?<https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>>
>      >? ? ? > FAQ - https://slackbuilds.org/faq/
>     <https://slackbuilds.org/faq/> <https://slackbuilds.org/faq/
>     <https://slackbuilds.org/faq/>>
>      >? ? ? >
>      >
>      >? ? ?--
>      >? ? ?Ed Fletcher
>      >
>      >? ? ?"When I became a man I put away childish things, including
>     the fear of
>      >? ? ?childishness and the desire to be very grown up.?
>      >? ? ?? C.S. Lewis
>      >? ? ?_______________________________________________
>      >? ? ?SlackBuilds-users mailing list
>      > SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>      >? ? ?<mailto:SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>>
>      > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>      >   
>      ?<https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>>
>      >? ? ?Archives -
>      > https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>      >? ? ?<https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>>
>      >? ? ?FAQ - https://slackbuilds.org/faq/
>     <https://slackbuilds.org/faq/> <https://slackbuilds.org/faq/
>     <https://slackbuilds.org/faq/>>
>      >
>      >
>      > _______________________________________________
>      > SlackBuilds-users mailing list
>      > SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>      > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>      > Archives -
>     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>      > FAQ - https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/>
>      >
> 
>     -- 
>     Ed Fletcher
> 
>     "When I became a man I put away childish things, including the fear of
>     childishness and the desire to be very grown up.?
>     ? C.S. Lewis
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
>     Archives -
>     https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
>     FAQ - https://slackbuilds.org/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/
> 

-- 
Ed Fletcher

"When I became a man I put away childish things, including the fear of 
childishness and the desire to be very grown up.?
? C.S. Lewis

From ed at fletcher.ca  Mon Jun 26 03:26:11 2023
From: ed at fletcher.ca (Ed Fletcher)
Date: Sun, 25 Jun 2023 20:26:11 -0700
Subject: [Slackbuilds-users] sboinstall chromprint fails
In-Reply-To: <f0a5adbf-a439-4662-b2d5-df28a3674100@app.fastmail.com>
References: <b6c1bb64-6bea-a220-6710-9b530d5322f4@fletcher.ca>
 <CAPsDuS6cdfKqHPZZQJTyGO0zu6C_XEVahBVnU+Fn0VZx-p+OvA@mail.gmail.com>
 <dd88e954-0441-29d7-c9cc-ddd9b9ec7fba@fletcher.ca>
 <f0a5adbf-a439-4662-b2d5-df28a3674100@app.fastmail.com>
Message-ID: <410ef14d-30df-3f08-e61a-313515fdd8d3@fletcher.ca>

Thanks David.  Yes, sbotools was pointed at current.  I did another 
clean install, because I had no idea what had been pulled from current. 
chromaprint (and vlc) installed cleanly.  And my printer now works 
again; only on cups and not with hplip but that's life.

I was surprised that sbotools defaults to current.  It's not mentioned 
anywhere that I could find.  Maybe that could be included on the 
SlackBuilds page, with what to change it to for 15.0?

Thanks for your assistance,
Ed

On 6/24/23 06:28, David O'Shaughnessy wrote:
> On Sat, 24 Jun 2023, at 8:37 AM, Ed Fletcher wrote:
>> I don't think so.  I've got sbotools v2.7 and didn't make any
>> configuration changes.  My understanding is that sbo gets the version of
>> slackware from the system it's running on and uses that to get the
>> correct packages.  Perhaps from /etc/slackware-version?  Mine says
>> Slackware 15.0 and doesn't mention 64.
> 
> By default sbotools will not be set up for 15.0 though. You can check with:
> grep "url = " /usr/sbo/repo/.git/config
> 
> In /etc/sbotools/sbotools.conf I've got:
> REPO=https://gitlab.com/SlackBuilds.org/slackbuilds.git
> 
> To put sbotools onto a 15.0 repo.
> 
> --
> Dave
> _______________________________________________
> 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/
> 

-- 
Ed Fletcher

"When I became a man I put away childish things, including the fear of 
childishness and the desire to be very grown up.?
? C.S. Lewis

From jh-gilmour at bigpond.com  Wed Jun 28 04:53:22 2023
From: jh-gilmour at bigpond.com (jh-gilmour at bigpond.com)
Date: Wed, 28 Jun 2023 14:53:22 +1000
Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 206, Issue 23
In-Reply-To: <mailman.3651.1687750214.31924.slackbuilds-users@slackbuilds.org>
References: <mailman.3651.1687750214.31924.slackbuilds-users@slackbuilds.org>
Message-ID: <7df183f0-9225-4f77-a655-ccdc26a90adb@localhost>

Please remove us from your mailing list . We are too old to have need and don't understand what you are about? Helen Gilmour

> 
> On ,Mon Jun 26 2023 13:30:14 GMT+1000 (Australian Eastern Standard Time),
> <slackbuilds-users-request at slackbuilds.org> wrote:
> 
> ---------- Original Message ----------
> 
> Send SlackBuilds-users mailing list submissions to
> 
> slackbuilds-users at slackbuilds.org
> 
> To subscribe or unsubscribe via the
> World Wide Web, visit
> 
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> or, via
> email, send a message with subject or body 'help' to
> 
> slackbuilds-users-request at slackbuilds.org
> 
> You can reach the person
> managing the list at
> 	slackbuilds-users-owner at slackbuilds.org
> 
> When
> replying, please edit your Subject line so it is more specific
> than "Re:
> Contents of SlackBuilds-users digest..."
> 
> 
> Today's Topics:
> 
>    1. Re:
> sboinstall chromprint fails (David O'Shaughnessy)
>    2. Re: slackrepo
> fails to build youtube-dl due to URL encoding
>       (Andrew Clemons)
>    3.
> argyllcms owner. (Fernando Lopez)
>    4. Re: argyllcms owner. (B. Watson)
>  
> 5. Re: argyllcms owner. (Fernando Lopez)
>    6. Re: sboinstall chromprint
> fails (Ed Fletcher)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sat, 24 Jun 2023 21:28:49 +0800
> From: "David
> O'Shaughnessy" <lists at osh.id.au>
> To: "SlackBuilds.org Users List"
> <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users]
> sboinstall chromprint fails
> Message-ID:
> <f0a5adbf-a439-4662-b2d5-df28a3674100 at app.fastmail.com>
> Content-Type:
> text/plain
> 
> On Sat, 24 Jun 2023, at 8:37 AM, Ed Fletcher wrote:
> > I don't
> think so.  I've got sbotools v2.7 and didn't make any 
> > configuration
> changes.  My understanding is that sbo gets the version of 
> > slackware
> from the system it's running on and uses that to get the 
> > correct
> packages.  Perhaps from /etc/slackware-version?  Mine says 
> > Slackware
> 15.0 and doesn't mention 64.
> 
> By default sbotools will not be set up for
> 15.0 though. You can check with:
> grep "url = " /usr/sbo/repo/.git/config
> 
> In /etc/sbotools/sbotools.conf I've got:
> REPO=https://gitlab.com/SlackBuilds.org/slackbuilds.git
> 
> To put sbotools
> onto a 15.0 repo.
> 
> --
> Dave
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Sun, 25 Jun 2023 20:10:24 +0900
> From: Andrew Clemons
> <andrew.clemons at gmail.com>
> To: slackbuilds-users at slackbuilds.org
> Subject:
> Re: [Slackbuilds-users] slackrepo fails to build youtube-dl
> 	due to URL
> encoding
> Message-ID: <4bfc3b51-afa0-ee4a-c7d7-809b83820623 at gmail.com>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
> 
> On 24/06/23
> 10:01, Erich Ritz via SlackBuilds-users wrote:
> > [..]
> > Thank you!  I had
> to specify both PRAGMA and DOWNLOAD (use "+" in the download URL):
> > 
> > $
> cat /var/lib/slackrepo/etr/hintfiles/youtube-dl.hint
> >
> PRAGMA="download_basename"
> >
> DOWNLOAD="https://downloads.sourceforge.net/project/dslackw/src/youtube-dl-2021.12.17+20230618_07af47960.tar.xz"
> > 
> > Now I'll just have to remember to update the DOWNLOAD URL in my
> hintfile next time it is updated...
> > 
> > Maybe a new PRAGMA could be added
> to replace DOWNLOAD URLs with decoded versions?
> 
> This seems reasonable to
> me. I opened an issue for this in the slackrepo 
> git repo. Let's take this
> discussion over there.
> -------------- next part --------------
> A non-text
> attachment was scrubbed...
> Name: OpenPGP_signature
> Type:
> application/pgp-signature
> Size: 840 bytes
> Desc: OpenPGP digital signature
> URL:
> <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230625/dfeeea42/attachment-0001.asc>
> ------------------------------
> 
> Message: 3
> Date: Sun, 25 Jun 2023 14:54:35
> -0500
> From: Fernando Lopez <fernando.lopezjr at gmail.com>
> To:
> "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject:
> [Slackbuilds-users] argyllcms owner.
> Message-ID:
> 
> <CALrQ46DdXaMsAcMtQ7cqEdzLW+Qfir4s=atoFC-fqTNJEUJdnQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Can you guys change owner to me
> on argyllcms sbo. It was approved a week
> ago (or two).
> 
> thank you.
> 
> -- 
> 
> ------------
> Regards,
>     Fernando Lopez Jr.
> -------------- next part
> --------------
> An HTML attachment was scrubbed...
> URL:
> <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230625/82229a49/attachment-0001.htm>
> ------------------------------
> 
> Message: 4
> Date: Sun, 25 Jun 2023 16:12:23
> -0400 (EDT)
> From: "B. Watson" <urchlay at slackware.uk>
> To: "SlackBuilds.org
> Users List" <slackbuilds-users at slackbuilds.org>
> Subject: Re:
> [Slackbuilds-users] argyllcms owner.
> Message-ID:
> <2ee44fca-e4a9-e093-22e8-6e8338e41894 at slackware.uk>
> Content-Type:
> text/plain; charset="utf-8"; Format="flowed"
> 
> 
> 
> On Sun, 25 Jun 2023,
> Fernando Lopez wrote:
> 
> > Can you guys change owner to me on?argyllcms sbo.
> It was approved?a week ago (or two).
> > thank you.
> 
> Done, on my branch.
> Will be merged in the next weekly update.
> 
> ------------------------------
> 
> Message: 5
> Date: Sun, 25 Jun 2023 15:14:22 -0500
> From: Fernando Lopez
> <fernando.lopezjr at gmail.com>
> To: "SlackBuilds.org Users List"
> <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users]
> argyllcms owner.
> Message-ID:
> 
> <CALrQ46Be80N8yzefFNarDuvvdoVYwjHSyyf1rXi0T9zZbq2ZcQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> thank you sir!
> 
> On Sun, Jun 25,
> 2023 at 3:12?PM B. Watson <urchlay at slackware.uk> wrote:
> 
> >
> >
> > On Sun, 25
> Jun 2023, Fernando Lopez wrote:
> >
> > > Can you guys change owner to me on
> argyllcms sbo. It was approved a week
> > ago (or two).
> > > thank you.
> >
> >
> Done, on my branch. Will be merged in the next weekly
> >
> update._______________________________________________
> > 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/
> >
> >
> 
> -- 
> 
> ------------
> Regards,
>    
> Fernando Lopez Jr.
> -------------- next part --------------
> An HTML
> attachment was scrubbed...
> URL:
> <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230625/f80375b1/attachment-0001.htm>
> ------------------------------
> 
> Message: 6
> Date: Sun, 25 Jun 2023 20:23:54
> -0700
> From: Ed Fletcher <ed at fletcher.ca>
> To: "SlackBuilds.org Users List"
> <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users]
> sboinstall chromprint fails
> Message-ID:
> <56147763-7abb-8f71-3392-0075c5989fb1 at fletcher.ca>
> Content-Type:
> text/plain; charset=UTF-8; format=flowed
> 
> Hi Matteo:
> 
> I found a third copy
> in /usr/doc/chromaprint-1.5.1/ but that was 
> identical to the other two.
> 
> The problem was indeed that sbotools was configured for current.  You 
> had
> the right idea from the start.
> 
> Thanks again for your help,
> Ed
> 
> On 6/24/23
> 03:39, Matteo Bernardini wrote:
> > Hi Ed,
> > 
> > I'm not sure where sbotools
> keeps the local copy of the repo, maybe 
> > /usr/sbo or something similar.
> > The two SlackBuild you've found are the one in the working directory 
> >
> generated when you built it manually and the one installed from the 
> >
> generated package (so not the one in the local repo).
> > 
> > Matteo
> > 
> > 
> >
> Il sab 24 giu 2023, 08:49 Ed Fletcher <ed at fletcher.ca 
> >
> <mailto:ed at fletcher.ca>> ha scritto:
> > 
> >     Hi Matteo:
> > 
> >     Yes, but
> I was hoping that having a .current repo might explain my
> >     printer
> problem.? Oh well.
> > 
> >     This might be a pointless exercise and I don't
> want to waste your time.
> >     VLC is working for me, which is what
> depends on chromaprint.? Just had
> >     to install chromaprint the old
> way.? I only posted this originally in
> >     case someone involved with
> sbotools might be interested.
> > 
> >     diff shows the two files to be
> identical.? So I don't think the problem
> >     is here.? Regardless, this
> is the file
> >    
> /tmp/SBo/package-chromaprint/usr/doc/chromaprint-1.5.1/chromaprint.SlackBuild
> > 
> >     #!/bin/bash
> > 
> >     # Slackware build script for chromaprint
> > 
> >     # Copyright 2012-2022 Matteo Bernardini <ponce at slackbuilds.org
> >    
> <mailto:ponce at slackbuilds.org>>, Pisa, Italy
> >     # All rights reserved.
> >     #
> >     # Redistribution and use of this script, with or without
> >  
> modification, is
> >     # permitted provided that the following conditions
> are met:
> >     #
> >     # 1. Redistributions of this script must retain the
> above copyright
> >     #? ? notice, this list of conditions and the
> following disclaimer.
> >     #
> >     #? THIS SOFTWARE IS PROVIDED BY THE
> AUTHOR "AS IS" AND ANY EXPRESS OR
> >     IMPLIED
> >     #? WARRANTIES,
> INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
> >     #?
> MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
> >    
> IN NO
> >     #? EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
> >     INCIDENTAL,
> >     #? SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT
> >     LIMITED TO,
> >     #? PROCUREMENT OF SUBSTITUTE
> GOODS OR SERVICES; LOSS OF USE, DATA, OR
> >     PROFITS;
> >     #? OR
> BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
> >    
> LIABILITY,
> >     #? WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING
> >     NEGLIGENCE OR
> >     #? OTHERWISE) ARISING IN ANY WAY OUT
> OF THE USE OF THIS SOFTWARE,
> >     EVEN IF
> >     #? ADVISED OF THE
> POSSIBILITY OF SUCH DAMAGE.
> > 
> >     cd $(dirname $0) ; CWD=$(pwd)
> > 
> >   
> PRGNAM=chromaprint
> >     VERSION=${VERSION:-1.5.1}
> >     BUILD=${BUILD:-1}
> >     TAG=${TAG:-_SBo}
> >     PKGTYPE=${PKGTYPE:-tgz}
> > 
> >     if [ -z
> "$ARCH" ]; then
> >      ? ?case "$( uname -m )" in
> >      ? ? ?i?86)
> ARCH=i586 ;;
> >      ? ? ?arm*) ARCH=arm ;;
> >      ? ? ? ? *) ARCH=$( uname
> -m ) ;;
> >      ? ?esac
> >     fi
> > 
> >     # If the variable
> PRINT_PACKAGE_NAME is set, then this script will
> >     report what
> >     #
> the name of the created package would be, and then exit. This
> >    
> information
> >     # could be useful to other scripts.
> >     if [ ! -z
> "${PRINT_PACKAGE_NAME}" ]; then
> >      ? ?echo
> "$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE"
> >      ? ?exit 0
> >     fi
> > 
> >     TMP=${TMP:-/tmp/SBo}
> >     PKG=$TMP/package-$PRGNAM
> >    
> OUTPUT=${OUTPUT:-/tmp}
> > 
> >     if [ "$ARCH" = "i586" ]; then
> >      ?
> ?SLKCFLAGS="-O2 -march=i586 -mtune=i686"
> >      ? ?LIBDIRSUFFIX=""
> >    
> elif [ "$ARCH" = "i686" ]; then
> >      ? ?SLKCFLAGS="-O2 -march=i686
> -mtune=i686"
> >      ? ?LIBDIRSUFFIX=""
> >     elif [ "$ARCH" = "x86_64" ];
> then
> >      ? ?SLKCFLAGS="-O2 -fPIC"
> >      ? ?LIBDIRSUFFIX="64"
> >    
> else
> >      ? ?SLKCFLAGS="-O2"
> >      ? ?LIBDIRSUFFIX=""
> >     fi
> > 
> >    
> if pkg-config --exists libavcodec; then tools="-DBUILD_TOOLS=ON"; else
> >  
> tools=""; fi
> > 
> >     DOCS="LICENSE.md NEWS.txt README.md"
> > 
> >     set -e
> > 
> >     rm -rf $PKG
> >     mkdir -p $TMP $PKG $OUTPUT
> >     cd $TMP
> >    
> rm -rf $PRGNAM-$VERSION
> >     tar xvf $CWD/$PRGNAM-$VERSION.tar.?z*
> >    
> cd $PRGNAM-$VERSION
> >     chown -R root:root .
> >     find -L . \
> >      ?
> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
> >     
> ? -o -perm 511 \) -exec chmod 755 {} \; -o \
> >      ? \( -perm 666 -o
> -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
> >      ? -o -perm 440
> -o -perm 400 \) -exec chmod 644 {} \;
> > 
> >     mkdir -p build
> >     cd
> build
> >      ? ?cmake \
> >      ? ? ?-DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
> >      ? ? ?-DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
> >      ? ?
> ?-DCMAKE_INSTALL_PREFIX=/usr \
> >      ? ? ?-DLIB_SUFFIX=${LIBDIRSUFFIX} \
> >      ? ? ?$tools \
> >      ? ? ?-DCMAKE_BUILD_TYPE=Release ..
> >      ?
> ?make
> >      ? ?make install DESTDIR=$PKG
> >     cd ..
> > 
> >     find $PKG
> -print0 | xargs -0 file | grep -e "executable" -e "shared
> >     object" |
> grep ELF \
> >      ? ?| cut -f 1 -d : | xargs strip --strip-unneeded 2>
> /dev/null || true
> > 
> >     mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
> >     cp
> -a $DOCS $PKG/usr/doc/$PRGNAM-$VERSION
> >     cat $CWD/$PRGNAM.SlackBuild >
> >     $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
> > 
> >     mkdir -p
> $PKG/install
> >     cat $CWD/slack-desc > $PKG/install/slack-desc
> > 
> >    
> cd $PKG
> >     /sbin/makepkg -l y -c n
> >    
> $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE
> > 
> > 
> >     There's a
> third copy here
> >     /usr/doc/chromaprint-1.5.1/chromaprint.SlackBuild
> > 
> diff shows it as identical to the other two.
> > 
> >     Ed
> > 
> >     On
> 6/23/23 22:04, Matteo Bernardini wrote:
> >      > Hi Ed,
> >      >
> >      >
> I start by saying that I don't use sbotools so I don't know how
> >     it
> works.
> >      >
> >      > if you have the possibility to paste the content
> of
> >      > chromaprint.SlackBuild as cointained in your local repository
> >     used by
> >      > sbotools (not the one you downloaded manually) it
> might help.
> >      >
> >      > FWIW let me say that chromaprint has nothing
> to do with printers
> >     (please
> >      > have a look at its README)...
> >
> >
> >      > Matteo
> >      >
> >      > Il giorno sab 24 giu 2023 alle ore
> 02:43 Ed Fletcher
> >     <ed at fletcher.ca <mailto:ed at fletcher.ca>
> >      >
> <mailto:ed at fletcher.ca <mailto:ed at fletcher.ca>>> ha scritto:
> >      >
> >   
> >? ? ?I don't think so.? I've got sbotools v2.7 and didn't make any
> >     
> >? ? ?configuration changes.? My understanding is that sbo gets the
> >     
> >? ? ?version of
> >      >? ? ?slackware from the system it's running on
> and uses that to
> >     get the
> >      >? ? ?correct packages.? Perhaps
> from /etc/slackware-version?? Mine
> >     says
> >      >? ? ?Slackware 15.0
> and doesn't mention 64.
> >      >
> >      >? ? ?The only place I can find
> current mentioned is in the README in
> >      >? ? ?/usr/sbo/repo, which
> points to
> >      > https://github.com/Ponce/slackbuilds/wiki
> >    
> <https://github.com/Ponce/slackbuilds/wiki>
> >      >? ?
> ?<https://github.com/Ponce/slackbuilds/wiki
> >    
> <https://github.com/Ponce/slackbuilds/wiki>>
> >      >
> >      >? ? ?That
> page mentions configuring the current repository with
> >     sbopkg in
> >   
> >? ? ?/etc/sbopkg/sbopkg.conf but that page is old, from before 15.0.
> >   
> >
> >      >? ? ?I don't have that directory in /etc so I don't see where to
> point
> >      >? ? ?sbotools to current.
> >      >
> >      >? ? ?Thanks for
> looking at this Matteo.? I was hoping it was an
> >     easy fix.? I
> >     
> >? ? ?don't need it for chromaprint or vlc but I thought it might
> >    
> help me
> >      >? ? ?with
> >      >? ? ?my printer.
> >      >
> >      >? ?
> ?Ed
> >      >
> >      >? ? ?On 6/22/23 23:35, Matteo Bernardini wrote:
> >    
> >? ? ? > hi Ed,
> >      >? ? ? >
> >      >? ? ? > could it be that you have
> configured with sbotools a
> >     repository for
> >      >? ? ? > Slackware
> current while you are running slackware 15.0?
> >      >? ? ? >
> >      >? ?
> ? > Matteo
> >      >? ? ? >
> >      >? ? ? > Il giorno gio 22 giu 2023 alle
> ore 23:59 Ed Fletcher
> >      >? ? ?<ed at fletcher.ca <mailto:ed at fletcher.ca>
> >     <mailto:ed at fletcher.ca <mailto:ed at fletcher.ca>>
> >      >? ? ? >
> <mailto:ed at fletcher.ca <mailto:ed at fletcher.ca>
> >    
> <mailto:ed at fletcher.ca <mailto:ed at fletcher.ca>>>> ha scritto:
> >      >? ?
> ? >
> >      >? ? ? >? ? ?While using sbo to put vlc on a freshly installed
> and
> >     updated
> >      >? ? ? >? ? ?Slackware64-15.0 (sboinstall vlc),
> the process failed on
> >      >? ? ? >? ? ?chromaprint.? I
> >      >? ? ? >?
> ? ?tried chromaprint by itself (sboinstall chromaprint)
> >     but it
> >    
> >? ? ?failed with
> >      >? ? ? >? ? ?the same error:
> >      >? ? ? >
> >   
> >? ? ? >? ? ?In file included from
> >      >? ? ? >   
> >     
> ?/tmp/SBo/chromaprint-1.5.1/src/audio/ffmpeg_audio_reader.h:18,
> >      >?
> ? ? >? ? ? ? ? ? ? ? ? ? ? ? from
> >      >? ?
> ?/tmp/SBo/chromaprint-1.5.1/src/cmd/fpcalc.cpp:7:
> >      >? ? ? >? ?
> ?/usr/include/libavcodec/avcodec.h:3047:5: note:
> >     declared here
> >    
> >? ? ? >? ? ? ? 3047 | int avcodec_decode_audio4(AVCodecContext *avctx,
> > 
> >? ? ?AVFrame
> >      >? ? ? >? ? ?*frame,
> >      >? ? ? >? ? ? ? ? ? ?|? ?
> ?^~~~~~~~~~~~~~~~~~~~~
> >      >? ? ? >? ? ?make[2]: ***
> [src/cmd/CMakeFiles/fpcalc.dir/build.make:76:
> >      >? ? ? >? ?
> ?src/cmd/CMakeFiles/fpcalc.dir/fpcalc.cpp.o] Error 1
> >      >? ? ? >? ?
> ?make[1]: *** [CMakeFiles/Makefile2:244:
> >      >? ? ? >? ?
> ?src/cmd/CMakeFiles/fpcalc.dir/all] Error 2
> >      >? ? ? >? ? ?make: ***
> [Makefile:136: all] Error 2
> >      >? ? ? >? ? ?Failures:
> >      >? ? ? >?
> ? ? ? ?chromaprint: chromaprint.SlackBuild return non-zero
> >      >? ? ? >
> >      >? ? ? >? ? ?What I find strange is that downloading the source and
> the
> >      >? ? ?slackbuild
> >      >? ? ? >? ? ?let me install it
> successfully.? This let sboinstall
> >     finish
> >      >? ? ?installing
> > 
> >? ? ? >? ? ?vlc.? So I have everything working, just left with a
> >    
> puzzle.
> >      >? ? ? >
> >      >? ? ? >? ? ?Ed
> >      >? ? ? >? ? ?--
> >   
> >? ? ? >? ? ?Ed Fletcher
> >      >? ? ? >
> >      >? ? ? >? ? ?"When I
> became a man I put away childish things, including
> >      >? ? ?the fear
> of
> >      >? ? ? >? ? ?childishness and the desire to be very grown up.?
> >
> >? ? ? >? ? ?? C.S. Lewis
> >      >? ? ? >? ?
> ?_______________________________________________
> >      >? ? ? >? ?
> ?SlackBuilds-users mailing list
> >      >? ? ? >
> SlackBuilds-users at slackbuilds.org
> >    
> <mailto:SlackBuilds-users at slackbuilds.org>
> >      >? ?
> ?<mailto:SlackBuilds-users at slackbuilds.org
> >    
> <mailto:SlackBuilds-users at slackbuilds.org>>
> >      >? ? ? >? ?
> ?<mailto:SlackBuilds-users at slackbuilds.org
> >    
> <mailto:SlackBuilds-users at slackbuilds.org>
> >      >? ?
> ?<mailto:SlackBuilds-users at slackbuilds.org
> >    
> <mailto:SlackBuilds-users at slackbuilds.org>>>
> >      >? ? ? >
> >    
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >    
> <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >     
> >   
> >     
> ?<https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >    
> <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>>
> >     
> >? ? ? >
> >      >     
> >     
> ?<https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >    
> <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >     
> >   
> >     
> ?<https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >    
> <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>>>
> >    
> >? ? ? >? ? ?Archives -
> >      >? ? ? >
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >    
> <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >      >? ?
> ?<https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >    
> <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>>
> >      >? ?
> ? >   
> >      ?<https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >     <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >     
> >? ? ?<https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >    
> <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>>>
> >      >? ?
> ? >? ? ?FAQ - https://slackbuilds.org/faq/
> >    
> <https://slackbuilds.org/faq/>
> >      >? ? ?<https://slackbuilds.org/faq/
> <https://slackbuilds.org/faq/>>
> >     <https://slackbuilds.org/faq/
> <https://slackbuilds.org/faq/>
> >      >? ? ?<https://slackbuilds.org/faq/
> <https://slackbuilds.org/faq/>>>
> >      >? ? ? >
> >      >? ? ? >
> >      >?
> ? ? > _______________________________________________
> >      >? ? ? >
> SlackBuilds-users mailing list
> >      >? ? ? >
> SlackBuilds-users at slackbuilds.org
> >    
> <mailto:SlackBuilds-users at slackbuilds.org>
> >      >? ?
> ?<mailto:SlackBuilds-users at slackbuilds.org
> >    
> <mailto:SlackBuilds-users at slackbuilds.org>>
> >      >? ? ? >
> >    
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >    
> <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >     
> >   
> >     
> ?<https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >    
> <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>>
> >     
> >? ? ? > Archives -
> >      >
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >    
> <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >      >? ?
> ?<https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >    
> <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>>
> >      >? ?
> ? > FAQ - https://slackbuilds.org/faq/
> >    
> <https://slackbuilds.org/faq/> <https://slackbuilds.org/faq/
> >    
> <https://slackbuilds.org/faq/>>
> >      >? ? ? >
> >      >
> >      >? ? ?--
> >
> >? ? ?Ed Fletcher
> >      >
> >      >? ? ?"When I became a man I put away
> childish things, including
> >     the fear of
> >      >? ? ?childishness and
> the desire to be very grown up.?
> >      >? ? ?? C.S. Lewis
> >      >? ?
> ?_______________________________________________
> >      >? ?
> ?SlackBuilds-users mailing list
> >      > SlackBuilds-users at slackbuilds.org
> >     <mailto:SlackBuilds-users at slackbuilds.org>
> >      >? ?
> ?<mailto:SlackBuilds-users at slackbuilds.org
> >    
> <mailto:SlackBuilds-users at slackbuilds.org>>
> >      >
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >    
> <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >     
> >   
> >     
> ?<https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >    
> <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>>
> >     
> >? ? ?Archives -
> >      >
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >    
> <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >      >? ?
> ?<https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >    
> <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>>
> >      >? ?
> ?FAQ - https://slackbuilds.org/faq/
> >     <https://slackbuilds.org/faq/>
> <https://slackbuilds.org/faq/
> >     <https://slackbuilds.org/faq/>>
> >     
> >
> >      >
> >      > _______________________________________________
> >     
> > SlackBuilds-users mailing list
> >      >
> SlackBuilds-users at slackbuilds.org
> >    
> <mailto:SlackBuilds-users at slackbuilds.org>
> >      >
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >    
> <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >     
> > Archives -
> >    
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >    
> <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >      > FAQ
> - https://slackbuilds.org/faq/ <https://slackbuilds.org/faq/>
> >      >
> > 
> >     -- 
> >     Ed Fletcher
> > 
> >     "When I became a man I put away
> childish things, including the fear of
> >     childishness and the desire
> to be very grown up.?
> >     ? C.S. Lewis
> >    
> _______________________________________________
> >     SlackBuilds-users
> mailing list
> >     SlackBuilds-users at slackbuilds.org
> >    
> <mailto:SlackBuilds-users at slackbuilds.org>
> >    
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> >    
> <https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users>
> >    
> Archives -
> >    
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> >    
> <https://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> >     FAQ -
> https://slackbuilds.org/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/
> > 
> 
> -- 
> Ed Fletcher
> 
> "When I became a
> man I put away childish things, including the fear of 
> childishness and
> the desire to be very grown up.?
> ? C.S. Lewis
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> SlackBuilds-users mailing
> list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> 
> 
> ------------------------------
> 
> End of SlackBuilds-users Digest, Vol 206,
> Issue 23
> **************************************************
> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230628/f41f14b8/attachment-0001.htm>

From vbatts at hashbangbash.com  Thu Jun 29 14:56:55 2023
From: vbatts at hashbangbash.com (Vincent Batts)
Date: Thu, 29 Jun 2023 10:56:55 -0400
Subject: [Slackbuilds-users] podman up for adoption
Message-ID: <ZJ2bt7XdaG1q3uJq@weasel.>

Hey all,

I realize the podman build is woefully out of date.
Are there any volunteers to adopt this SlackBuild (and it's couple of
deps)?

vb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230629/ffd8335e/attachment.asc>

From lists at osh.id.au  Thu Jun 29 15:30:54 2023
From: lists at osh.id.au (David O'Shaughnessy)
Date: Thu, 29 Jun 2023 23:30:54 +0800
Subject: [Slackbuilds-users] sboinstall chromprint fails
In-Reply-To: <410ef14d-30df-3f08-e61a-313515fdd8d3@fletcher.ca>
References: <b6c1bb64-6bea-a220-6710-9b530d5322f4@fletcher.ca>
 <CAPsDuS6cdfKqHPZZQJTyGO0zu6C_XEVahBVnU+Fn0VZx-p+OvA@mail.gmail.com>
 <dd88e954-0441-29d7-c9cc-ddd9b9ec7fba@fletcher.ca>
 <f0a5adbf-a439-4662-b2d5-df28a3674100@app.fastmail.com>
 <410ef14d-30df-3f08-e61a-313515fdd8d3@fletcher.ca>
Message-ID: <ed04a2a1-7f23-412e-95a8-2a69312f328f@app.fastmail.com>

On Mon, 26 Jun 2023, at 11:26 AM, Ed Fletcher wrote:
> I was surprised that sbotools defaults to current.  It's not mentioned 
> anywhere that I could find.  Maybe that could be included on the 
> SlackBuilds page, with what to change it to for 15.0?

sbotools needs a new maintainer, the last commit was around 4 years ago. But yes, it should probably be mentioned on the SlackBuild README that it's not by default set up for 15.0.

From klaatu at mixedsignals.ml  Thu Jun 29 19:41:12 2023
From: klaatu at mixedsignals.ml (Klaatu)
Date: Fri, 30 Jun 2023 07:41:12 +1200
Subject: [Slackbuilds-users] podman up for adoption
In-Reply-To: <ZJ2bt7XdaG1q3uJq@weasel.>
References: <ZJ2bt7XdaG1q3uJq@weasel.>
Message-ID: <2106531.9o76ZdvQCi@beast.slackermedia.local>

On Friday, June 30, 2023 2:56:55 AM NZST Vincent Batts via SlackBuilds-users 
wrote:
> Hey all,
> 
> I realize the podman build is woefully out of date.
> Are there any volunteers to adopt this SlackBuild (and it's couple of
> deps)?
> 
> vb

I've actually been working on updating it locally. I use Podman a lot at work, 
so I'd be happy to take this and its deps.

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

From vbatts at hashbangbash.com  Thu Jun 29 19:51:47 2023
From: vbatts at hashbangbash.com (Vincent Batts)
Date: Thu, 29 Jun 2023 15:51:47 -0400
Subject: [Slackbuilds-users] podman up for adoption
In-Reply-To: <2106531.9o76ZdvQCi@beast.slackermedia.local>
References: <ZJ2bt7XdaG1q3uJq@weasel.>
 <2106531.9o76ZdvQCi@beast.slackermedia.local>
Message-ID: <ZJ3g02+HXurhi1UB@weasel.>

On 30/06/23 07:41 +1200, Klaatu wrote:
>On Friday, June 30, 2023 2:56:55 AM NZST Vincent Batts via SlackBuilds-users
>wrote:
>> Hey all,
>>
>> I realize the podman build is woefully out of date.
>> Are there any volunteers to adopt this SlackBuild (and it's couple of
>> deps)?
>>
>> vb
>
>I've actually been working on updating it locally. I use Podman a lot at work,
>so I'd be happy to take this and its deps.
>
>-klaatu

right on! thanks, klaatu.

vb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230629/822b18eb/attachment.asc>

From slackbuilds at schoepfer.info  Fri Jun 30 17:09:42 2023
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 30 Jun 2023 19:09:42 +0200
Subject: [Slackbuilds-users] Fwd: leafpad on SBo
In-Reply-To: <f40e5d00079162c01e4367e726a1e67c@schoepfer.info>
References: <f40e5d00079162c01e4367e726a1e67c@schoepfer.info>
Message-ID: <aac12847db7fa8fa1a27bbe0d11998d5@schoepfer.info>

Hi,

i didn't hear back from the leafpad maintainer over two weeks, may i 
take over?
Maintainer cc'ed

-------- Originalnachricht --------
Betreff: leafpad on SBo
Datum: 2023-06-12 07:50
Von: Franzen <slackbuilds at schoepfer.info>
An: b.pribs11 at gmail.com

Hi,

after 12 years, there is a new version of leafpad at
https://download.savannah.gnu.org/releases/leafpad/

Do you plan to update?

Cheers,

Johannes