From rcb at beco.cc  Tue Feb  1 02:01:45 2022
From: rcb at beco.cc (Beco)
Date: Mon, 31 Jan 2022 23:01:45 -0300
Subject: [Slackbuilds-users] Epson M105 printer with PPD on CUPS (it was Re:
 Howto for slackware tgz)
In-Reply-To: <e074c374-0aac-cda4-1e37-6b2662c28e76@linux.com>
References: <CALuYw2x+ay8n8s1txJrtDxM3CDCU9xUKU+cM36dabdY6fhRBGg@mail.gmail.com>
 <CANi9qSvX8Z1VDVuBuiL7DNTa66x=o_8LoEgszfWu8AtvPZVK6w@mail.gmail.com>
 <CAJ2_kYrLFsjK8i5YTioqnFxVFCWojW6c+V3Mzar1E9OD5aguMA@mail.gmail.com>
 <CALuYw2yuoOHf8xE-M52ngincDp3sqjRm_Q+GMf8RsTPcHoSiqg@mail.gmail.com>
 <e074c374-0aac-cda4-1e37-6b2662c28e76@linux.com>
Message-ID: <CALuYw2w28powecVLKxaD8ArDbt7tMXz13h0+UGsSSox5SVJidQ@mail.gmail.com>

Dear Donald Laster, Jeremy, Chris and Kris,


Sorry for the late reply, I was unable to test all the options you
gave, due to some health problems. I'm back trying to install the
printer.

To recap:

I have a epson M105 via wifi that I use with other multiple devices,
android, linux, etc. (all working.) Now I'm trying to add Slackware to
the pool.


----------

On Sat, 15 Jan 2022 , Donald R Laster Jr <laster at dlaster.com> wrote:
>
> B?co,
>
>   Regardless of how you have the printer attached, network or direct,
> you should be able to use CUPS to setup the printer if CUPS supports the printer.
> The first thing to do is to insure that you have CUPS running.  Make sure
> that /etc/rc.d/rc.cups is executable and you have started the CUPS daemon.
>
> [...cut...]
>
>   Sincerely,
>   Donald R Laster Jr

----------

On Wed, 12 Jan 2022 at 23:38, Christoph Willing <chris.willing at linux.com> wrote:
>
> On 13/1/22 11:39, Beco via SlackBuilds-users wrote:
> > Hi Jeremy, hi Chris,
> >
> > Thanks for the tips, guys.
> >
> > I'll take a look at every link.
> >
> > Currently I'm having trouble with my printer, Epson M105, and I'm
> > trying to adapt source code from drivers I've found in "src.rpm" to
> > slackware package format.
> >
>
> Have a look at:
>         https://slackbuilds.org/repository/14.2/system/epson-printer-utility/
>
> whose README.models claims to support the M105 Series (and is based on
> a src.rpm too).
>
>
> chris
----------



The Slackware experience for this specific printer is not the best.
I'm trying to configure a new server using Slackware and it is a first
attempt after a lifetime away from this distro that I love. (It was my
first distro in 1998/1999). So, lets give it a try.

I tried to install the "14.2 > System > epson-printer-utility (1.1.1)
" (I'm on Slackware Current), and it didn't compile. After some
tweeks, I got it to compile with errors but didn't work.

Anyway: I was not that much upset, since this is not the path I would
prefer to take. I don't need the utility, the monitor, ink levels,
nozzles checks, etc. I can skip all that.

In all my other linuxes, it is enough a PPD file that I have, and
CUPS. And that is it. so, i tried the other path I am more familiar,
just to install the printer with PPD.

CUPS detected it with a lpd://localhost:port and also I can connect
with socket://localhost:port. So, these 2 options can "see" the
printer and send "test pages", but all end up as garbage.

The PPD file I have that I used in many systems, passing from one to
another and it always worked, don't work anymore. I noticed that it
gives this error:


Idle - "File "/opt/epson-inkjet-printer-201215w/cups/lib/filter/epson_inkjet_printer_filter"
not available: No such file or directory"


I have tried to compile this filter from many sources, RPM, Debian,
Slackbuilds, but I can't find a way to make this filter work.

For now, my hope is that the maintainer of the Slackbuilds packages
that may offer this would make it updated for slackware-current.



Donald, I completely agree with you. Regardless how the printer is
connected, if CUPS is working, and I have the PPD, the printer should
work fine. I guess this PPD I have is not well suited to the PATH of
slackware filters. Maybe a small adjustment, or to find if the printer
can work with another filter that comes with CUPS , that could work.


Thanks for now, I'll keep trying and keep you guys posted.

Cordially,
B?co






-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not
sure you realize that what you heard is not what I meant" -- Alan
Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

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

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

From dickson.tim at googlemail.com  Tue Feb  1 10:02:07 2022
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Tue, 1 Feb 2022 10:02:07 +0000
Subject: [Slackbuilds-users] Epson M105 printer with PPD on CUPS (it was
 Re: Howto for slackware tgz)
In-Reply-To: <CALuYw2w28powecVLKxaD8ArDbt7tMXz13h0+UGsSSox5SVJidQ@mail.gmail.com>
References: <CALuYw2x+ay8n8s1txJrtDxM3CDCU9xUKU+cM36dabdY6fhRBGg@mail.gmail.com>
 <CANi9qSvX8Z1VDVuBuiL7DNTa66x=o_8LoEgszfWu8AtvPZVK6w@mail.gmail.com>
 <CAJ2_kYrLFsjK8i5YTioqnFxVFCWojW6c+V3Mzar1E9OD5aguMA@mail.gmail.com>
 <CALuYw2yuoOHf8xE-M52ngincDp3sqjRm_Q+GMf8RsTPcHoSiqg@mail.gmail.com>
 <e074c374-0aac-cda4-1e37-6b2662c28e76@linux.com>
 <CALuYw2w28powecVLKxaD8ArDbt7tMXz13h0+UGsSSox5SVJidQ@mail.gmail.com>
Message-ID: <53130961-832f-84c6-f094-5f3afa488559@googlemail.com>

the two printer packages at sbo are epson-inkjet-printer-escpr and 
epson-inkjet-printer-escpr2
and cater for printers that use the different protocol versions.
the m100 series was last supported in 2012, so it must be a really old 
model.
It is not listed in either of the current driver packages available.

you'll need to create a package based on 
epson-inkjet-printer-201215w-1.0.0-1lsb3.2.src.rpm from epson.
you can use rpm2tgz to convert the source package to something more useful.

If you look at either of the two epson printer packages available, it 
will give some pointers to getting epson source code to compile. If you 
are successful, you should end up with the ppd files and the back-end as 
well. Be prepared for an uphill task.
regards, Tim


On 01/02/2022 02:01, Beco via SlackBuilds-users wrote:
> Dear Donald Laster, Jeremy, Chris and Kris,
>
>
> Sorry for the late reply, I was unable to test all the options you
> gave, due to some health problems. I'm back trying to install the
> printer.
>
> To recap:
>
> I have a epson M105 via wifi that I use with other multiple devices,
> android, linux, etc. (all working.) Now I'm trying to add Slackware to
> the pool.
>
>
> ----------
>
> On Sat, 15 Jan 2022 , Donald R Laster Jr <laster at dlaster.com> wrote:
>> B?co,
>>
>>    Regardless of how you have the printer attached, network or direct,
>> you should be able to use CUPS to setup the printer if CUPS supports the printer.
>> The first thing to do is to insure that you have CUPS running.  Make sure
>> that /etc/rc.d/rc.cups is executable and you have started the CUPS daemon.
>>
>> [...cut...]
>>
>>    Sincerely,
>>    Donald R Laster Jr
> ----------
>
> On Wed, 12 Jan 2022 at 23:38, Christoph Willing <chris.willing at linux.com> wrote:
>> On 13/1/22 11:39, Beco via SlackBuilds-users wrote:
>>> Hi Jeremy, hi Chris,
>>>
>>> Thanks for the tips, guys.
>>>
>>> I'll take a look at every link.
>>>
>>> Currently I'm having trouble with my printer, Epson M105, and I'm
>>> trying to adapt source code from drivers I've found in "src.rpm" to
>>> slackware package format.
>>>
>> Have a look at:
>>          https://slackbuilds.org/repository/14.2/system/epson-printer-utility/
>>
>> whose README.models claims to support the M105 Series (and is based on
>> a src.rpm too).
>>
>>
>> chris
> ----------
>
>
>
> The Slackware experience for this specific printer is not the best.
> I'm trying to configure a new server using Slackware and it is a first
> attempt after a lifetime away from this distro that I love. (It was my
> first distro in 1998/1999). So, lets give it a try.
>
> I tried to install the "14.2 > System > epson-printer-utility (1.1.1)
> " (I'm on Slackware Current), and it didn't compile. After some
> tweeks, I got it to compile with errors but didn't work.
>
> Anyway: I was not that much upset, since this is not the path I would
> prefer to take. I don't need the utility, the monitor, ink levels,
> nozzles checks, etc. I can skip all that.
>
> In all my other linuxes, it is enough a PPD file that I have, and
> CUPS. And that is it. so, i tried the other path I am more familiar,
> just to install the printer with PPD.
>
> CUPS detected it with a lpd://localhost:port and also I can connect
> with socket://localhost:port. So, these 2 options can "see" the
> printer and send "test pages", but all end up as garbage.
>
> The PPD file I have that I used in many systems, passing from one to
> another and it always worked, don't work anymore. I noticed that it
> gives this error:
>
>
> Idle - "File "/opt/epson-inkjet-printer-201215w/cups/lib/filter/epson_inkjet_printer_filter"
> not available: No such file or directory"
>
>
> I have tried to compile this filter from many sources, RPM, Debian,
> Slackbuilds, but I can't find a way to make this filter work.
>
> For now, my hope is that the maintainer of the Slackbuilds packages
> that may offer this would make it updated for slackware-current.
>
>
>
> Donald, I completely agree with you. Regardless how the printer is
> connected, if CUPS is working, and I have the PPD, the printer should
> work fine. I guess this PPD I have is not well suited to the PATH of
> slackware filters. Maybe a small adjustment, or to find if the printer
> can work with another filter that comes with CUPS , that could work.
>
>
> Thanks for now, I'll keep trying and keep you guys posted.
>
> Cordially,
> B?co
>
>
>
>
>
>


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


From sb at rbn.im  Tue Feb  1 15:17:37 2022
From: sb at rbn.im (Ruben Schuller)
Date: Tue, 1 Feb 2022 16:17:37 +0100
Subject: [Slackbuilds-users] duplicated PRGNAM cryptography
Message-ID: <20220201161737.0d873134@kiwi.kuchen>

Hi list,

just wanted to drop a note about this, as it probably will generate
problems:

% grep -R 'PRGNAM="cryptography"'
python/cryptography/cryptography.info:PRGNAM="cryptography"
python/python2-cryptography/python2-cryptography.info:PRGNAM="cryptography"

Cheers
Ruben

From pprkut at slackbuilds.org  Tue Feb  1 20:32:07 2022
From: pprkut at slackbuilds.org (Heinz Wiesinger)
Date: Tue, 01 Feb 2022 21:32:07 +0100
Subject: [Slackbuilds-users] duplicated PRGNAM cryptography
In-Reply-To: <20220201161737.0d873134@kiwi.kuchen>
References: <20220201161737.0d873134@kiwi.kuchen>
Message-ID: <4511020.vXUDI8C0e8@amaterasu.liwjatan.org>

On Tuesday, 1 February 2022 16:17:37 CET Ruben Schuller wrote:
> Hi list,
> 
> just wanted to drop a note about this, as it probably will generate
> problems:
> 
> % grep -R 'PRGNAM="cryptography"'
> python/cryptography/cryptography.info:PRGNAM="cryptography"
> python/python2-cryptography/python2-cryptography.info:PRGNAM="cryptography"

Fixed in my branch. Thanks! :)

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220201/ba0a81a6/attachment.asc>

From 1.41421 at gmail.com  Tue Feb  1 20:44:03 2022
From: 1.41421 at gmail.com (Luveh Keraph)
Date: Tue, 1 Feb 2022 13:44:03 -0700
Subject: [Slackbuilds-users] Concerning 15.0 and 14.2
Message-ID: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>

There have been no updates to any Slackbuilds packages for 14.2 for many
months now - I guess that we all thought that 15.0 would be released
earlier than in fact it will, whenever that happens. My guess is that,
shortly after this release hits the street, normal updating activity will
start for Slackbuilds packages for 15.0. What happens to 14.2? No
Slackbuilds packages for 14.2 will be updated any more?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220201/752e7e71/attachment.htm>

From dave at slackbuilds.org  Tue Feb  1 20:47:37 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Tue, 1 Feb 2022 20:47:37 +0000
Subject: [Slackbuilds-users] Concerning 15.0 and 14.2
In-Reply-To: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>
References: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>
Message-ID: <20220201204737.GD8022@localhost>

On 01/02/22 13:44,
Luveh Keraph <1.41421 at gmail.com> put forth the proposition:
> There have been no updates to any Slackbuilds packages for 14.2 for many
> months now - I guess that we all thought that 15.0 would be released
> earlier than in fact it will, whenever that happens. My guess is that,
> shortly after this release hits the street, normal updating activity will
> start for Slackbuilds packages for 15.0. What happens to 14.2? No
> Slackbuilds packages for 14.2 will be updated any more?

Hi Luveh -  yeah, 14.2 is frozen now.  Updates and submissions will resume with the 15.0 release.

--
Dave

From yalhcru at gmail.com  Tue Feb  1 20:51:15 2022
From: yalhcru at gmail.com (B Watson)
Date: Tue, 1 Feb 2022 15:51:15 -0500
Subject: [Slackbuilds-users] Concerning 15.0 and 14.2
In-Reply-To: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>
References: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>
Message-ID: <CAN1hMuDRnwqNX7HeOpdr5eEEZHnZUBuYc7HX23jcsVb2ksRfPQ@mail.gmail.com>

On 2/1/22, Luveh Keraph <1.41421 at gmail.com> wrote:

> What happens to 14.2? No Slackbuilds packages for 14.2 will be updated any more?

Correct. 14.2 slackbuilds.org branch is already considered frozen,
not getting updated. We just don't have the time/energy/resources to
keep updating builds for previous versions. The same thing happened
before 14.2 was released, at some point we stopped updating for 14.1
and started gearing up for 14.2 (at which time, the submission form
was closed, just like it is now).

>From a user's perspective, it might look like we jumped the gun and
started updating everything for -current a bit too early... but it's
been (and still is) a lot of work to get everything ready for 15.0.

Remember we are a small team of unpaid volunteers...

From 1.41421 at gmail.com  Tue Feb  1 22:17:02 2022
From: 1.41421 at gmail.com (Luveh Keraph)
Date: Tue, 1 Feb 2022 15:17:02 -0700
Subject: [Slackbuilds-users] Concerning 15.0 and 14.2
In-Reply-To: <CAN1hMuDRnwqNX7HeOpdr5eEEZHnZUBuYc7HX23jcsVb2ksRfPQ@mail.gmail.com>
References: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>
 <CAN1hMuDRnwqNX7HeOpdr5eEEZHnZUBuYc7HX23jcsVb2ksRfPQ@mail.gmail.com>
Message-ID: <CAFy1yb1hQx+jv0=sMn97fxruLWwJZswCb3g_q8Zjj2J7W5mwEA@mail.gmail.com>

OK, thanks. No slur implied - it's just that I have a number of 14.2
systems, and I needed this information to decide if and when I will upgrade
them to 15.0 once it is available.

On Tue, Feb 1, 2022 at 1:51 PM B Watson <yalhcru at gmail.com> wrote:

> On 2/1/22, Luveh Keraph <1.41421 at gmail.com> wrote:
>
> > What happens to 14.2? No Slackbuilds packages for 14.2 will be updated
> any more?
>
> Correct. 14.2 slackbuilds.org branch is already considered frozen,
> not getting updated. We just don't have the time/energy/resources to
> keep updating builds for previous versions. The same thing happened
> before 14.2 was released, at some point we stopped updating for 14.1
> and started gearing up for 14.2 (at which time, the submission form
> was closed, just like it is now).
>
> From a user's perspective, it might look like we jumped the gun and
> started updating everything for -current a bit too early... but it's
> been (and still is) a lot of work to get everything ready for 15.0.
>
> Remember we are a small team of unpaid volunteers...
> _______________________________________________
> 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/20220201/4672539e/attachment-0001.htm>

From arnaud.garcia-fernandez at laposte.net  Tue Feb  1 22:34:35 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Tue, 1 Feb 2022 23:34:35 +0100
Subject: [Slackbuilds-users] Concerning 15.0 and 14.2
In-Reply-To: <CAFy1yb1hQx+jv0=sMn97fxruLWwJZswCb3g_q8Zjj2J7W5mwEA@mail.gmail.com>
References: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>
 <CAN1hMuDRnwqNX7HeOpdr5eEEZHnZUBuYc7HX23jcsVb2ksRfPQ@mail.gmail.com>
 <CAFy1yb1hQx+jv0=sMn97fxruLWwJZswCb3g_q8Zjj2J7W5mwEA@mail.gmail.com>
Message-ID: <20220201233435.d0e5b5ee5c637d7c57120041@laposte.net>

Well, Pat did write in this morning changelog ? The cave is now closed ?.
We are at 15.0 RC3.

We may have jumped ship a bit early last year, but it might not be long before
15.0 is out...

 - Yth.


> OK, thanks. No slur implied - it's just that I have a number of 14.2
> systems, and I needed this information to decide if and when I will upgrade
> them to 15.0 once it is available.
> 
> On Tue, Feb 1, 2022 at 1:51 PM B Watson <yalhcru at gmail.com> wrote:
> 
> > On 2/1/22, Luveh Keraph <1.41421 at gmail.com> wrote:
> >
> > > What happens to 14.2? No Slackbuilds packages for 14.2 will be updated
> > any more?
> >
> > Correct. 14.2 slackbuilds.org branch is already considered frozen,
> > not getting updated. We just don't have the time/energy/resources to
> > keep updating builds for previous versions. The same thing happened
> > before 14.2 was released, at some point we stopped updating for 14.1
> > and started gearing up for 14.2 (at which time, the submission form
> > was closed, just like it is now).
> >
> > From a user's perspective, it might look like we jumped the gun and
> > started updating everything for -current a bit too early... but it's
> > been (and still is) a lot of work to get everything ready for 15.0.
> >
> > Remember we are a small team of unpaid volunteers...
> > _______________________________________________
> > 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 kingbeowulf at gmail.com  Wed Feb  2 00:39:02 2022
From: kingbeowulf at gmail.com (King Beowulf)
Date: Tue, 1 Feb 2022 16:39:02 -0800
Subject: [Slackbuilds-users] Concerning 15.0 and 14.2
In-Reply-To: <20220201233435.d0e5b5ee5c637d7c57120041@laposte.net>
References: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>
 <CAN1hMuDRnwqNX7HeOpdr5eEEZHnZUBuYc7HX23jcsVb2ksRfPQ@mail.gmail.com>
 <CAFy1yb1hQx+jv0=sMn97fxruLWwJZswCb3g_q8Zjj2J7W5mwEA@mail.gmail.com>
 <20220201233435.d0e5b5ee5c637d7c57120041@laposte.net>
Message-ID: <e67ac27b-1588-8fc7-e3e7-a64c162fb5f5@gmail.com>

On 2/1/22 14:34, Arnaud via SlackBuilds-users wrote:
> Well, Pat did write in this morning changelog ? The cave is now closed ?.
> We are at 15.0 RC3.

After that message there was "Hey, my shiny brass lamp is almost out of
fuel!"

Hopefully "real soon now!"

-KB

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

From rshepard at appl-ecosys.com  Wed Feb  2 00:43:48 2022
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 1 Feb 2022 16:43:48 -0800 (PST)
Subject: [Slackbuilds-users] Concerning 15.0 and 14.2
In-Reply-To: <e67ac27b-1588-8fc7-e3e7-a64c162fb5f5@gmail.com>
References: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>
 <CAN1hMuDRnwqNX7HeOpdr5eEEZHnZUBuYc7HX23jcsVb2ksRfPQ@mail.gmail.com>
 <CAFy1yb1hQx+jv0=sMn97fxruLWwJZswCb3g_q8Zjj2J7W5mwEA@mail.gmail.com>
 <20220201233435.d0e5b5ee5c637d7c57120041@laposte.net>
 <e67ac27b-1588-8fc7-e3e7-a64c162fb5f5@gmail.com>
Message-ID: <473ecad4-e62c-e9de-c020-b244ce9eb2ec@appl-ecosys.com>

On Tue, 1 Feb 2022, King Beowulf wrote:

> After that message there was "Hey, my shiny brass lamp is almost out of
> fuel!"
>
> Hopefully "real soon now!"

Ed,

I saw that the cave was closed (is that the home of the Clan of the Cave
Bear?) and that his shiny brass lamp was low on fuel but they meant nothing
to me as I haven't followed the developer's jargon.

And chaning the output to pulse and killing the mics fixed the problem.

Thanks,

Rich

From ozan.turkyilmaz at gmail.com  Wed Feb  2 05:58:44 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Wed, 2 Feb 2022 08:58:44 +0300
Subject: [Slackbuilds-users] Concerning 15.0 and 14.2
In-Reply-To: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>
References: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>
Message-ID: <CA+da1oqHefipEJEn1pEpkzWxU4cD6291rgh-k8q=tbJ3mtUNhA@mail.gmail.com>

Luveh Keraph <1.41421 at gmail.com>, 1 ?ub 2022 Sal, 23:44 tarihinde ?unu
yazd?:

> There have been no updates to any Slackbuilds packages for 14.2 for many
> months now - I guess that we all thought that 15.0 would be released
> earlier than in fact it will, whenever that happens. My guess is that,
> shortly after this release hits the street, normal updating activity will
> start for Slackbuilds packages for 15.0. What happens to 14.2? No
> Slackbuilds packages for 14.2 will be updated any more?
>
>
14.2 will be frozen after 15's release. But that is not really official. As
others said, most of us won't have time to update. HOwever, I know a lot of
us will leave up to date 14.2 when the official freeze is lifted.

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

From willysr at slackbuilds.org  Wed Feb  2 11:13:40 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 2 Feb 2022 18:13:40 +0700
Subject: [Slackbuilds-users] uid/gid for flatpak
In-Reply-To: <72863b66-c860-587c-0e42-66ff5b80f5ce@linux.com>
References: <72863b66-c860-587c-0e42-66ff5b80f5ce@linux.com>
Message-ID: <834c31c9-1ac4-b1ed-20d8-c25d05cdd553@slackbuilds.org>

> Since building & running the Slackbuild for flatpak, I see the message:
>  ?? ? Warning: Failed to get revokefs-fuse socket from system-helper: 
> User flatpak does not exist in password file entry
> 
> Devs suggest a "flatpak" user & group should be added but I couldn't 
> find a flatpak entry in https://slackbuilds.org/uid_gid.txt.
> 
> Could we have one?

You can use flatpak with UID/GID 372


-- 
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/20220202/d637543b/attachment.asc>

From chris.willing at linux.com  Wed Feb  2 11:43:47 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Wed, 2 Feb 2022 21:43:47 +1000
Subject: [Slackbuilds-users] uid/gid for flatpak
In-Reply-To: <834c31c9-1ac4-b1ed-20d8-c25d05cdd553@slackbuilds.org>
References: <72863b66-c860-587c-0e42-66ff5b80f5ce@linux.com>
 <834c31c9-1ac4-b1ed-20d8-c25d05cdd553@slackbuilds.org>
Message-ID: <136ec05d-c964-52cb-8cd6-1519a2132a1a@linux.com>

On 2/2/22 21:13, Willy Sudiarto Raharjo wrote:
>> Since building & running the Slackbuild for flatpak, I see the message:
>> ??? ? Warning: Failed to get revokefs-fuse socket from system-helper:
>> User flatpak does not exist in password file entry
>>
>> Devs suggest a "flatpak" user & group should be added but I couldn't
>> find a flatpak entry in https://slackbuilds.org/uid_gid.txt.
>>
>> Could we have one?
> 
> You can use flatpak with UID/GID 372
>Thanks!

chris

From arnaud.garcia-fernandez at laposte.net  Wed Feb  2 17:52:51 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Wed, 02 Feb 2022 17:52:51 +0000
Subject: [Slackbuilds-users] Concerning 15.0 and 14.2
In-Reply-To: <473ecad4-e62c-e9de-c020-b244ce9eb2ec@appl-ecosys.com>
References: <CAFy1yb1oAjZEbH9_JM79L2JdaWDVeY3JV_KhEnyqoWjMPUBJ+A@mail.gmail.com>
 <CAN1hMuDRnwqNX7HeOpdr5eEEZHnZUBuYc7HX23jcsVb2ksRfPQ@mail.gmail.com>
 <CAFy1yb1hQx+jv0=sMn97fxruLWwJZswCb3g_q8Zjj2J7W5mwEA@mail.gmail.com>
 <20220201233435.d0e5b5ee5c637d7c57120041@laposte.net>
 <e67ac27b-1588-8fc7-e3e7-a64c162fb5f5@gmail.com>
 <473ecad4-e62c-e9de-c020-b244ce9eb2ec@appl-ecosys.com>
Message-ID: <FB23E6FF-5D86-4329-9393-6105DD215A79@laposte.net>

Today's message was : I will be finished tomorrow.
...
Can't wait... ??

 - Yth

Le 2 f?vrier 2022 00:43:48 UTC, Rich Shepard <rshepard at appl-ecosys.com> a ?crit?:
>On Tue, 1 Feb 2022, King Beowulf wrote:
>
>> After that message there was "Hey, my shiny brass lamp is almost out of
>> fuel!"
>>
>> Hopefully "real soon now!"
>
>Ed,
>
>I saw that the cave was closed (is that the home of the Clan of the Cave
>Bear?) and that his shiny brass lamp was low on fuel but they meant nothing
>to me as I haven't followed the developer's jargon.
>
>And chaning the output to pulse and killing the mics fixed the problem.
>
>Thanks,
>
>Rich
>_______________________________________________
>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/20220202/eefbe476/attachment-0001.htm>

From willysr at slackbuilds.org  Fri Feb  4 01:17:43 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 4 Feb 2022 08:17:43 +0700
Subject: [Slackbuilds-users] Slackware 15.0 Released
Message-ID: <1e26b81d-7046-4a65-26f2-b6e6116428d9@slackbuilds.org>

Big Kudos to Patrick, finally Slackware 15.0 is out now!!
You can read the official announcement here:
http://www.slackware.com/announce/15.0.php

So what about SBo 15.0 repo?
Well, we are still working on it at this moment and YOU can help us
making it faster to get released by testing scripts in our repository
against latest 15.0 installation (full installation is always
recommended). You can then report them on LQ
https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/
or directly send us pull request / merge request on github/gitlab or via
this mailing list (in .patch format would be better).

Hopefully we will see 15.0 repository ready in short time

We apologize for not able to make it sync with Slackware 15.0 release
this cycle

-- 
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/20220204/0ca51d98/attachment.asc>

From slackbuilds at schoepfer.info  Fri Feb  4 15:36:22 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 04 Feb 2022 16:36:22 +0100
Subject: [Slackbuilds-users] Slackware 15.0 Released
In-Reply-To: <1e26b81d-7046-4a65-26f2-b6e6116428d9@slackbuilds.org>
References: <1e26b81d-7046-4a65-26f2-b6e6116428d9@slackbuilds.org>
Message-ID: <e3854e4dcd357dc1865e05c93a0005e5@schoepfer.info>

> So what about SBo 15.0 repo?
> Well, we are still working on it at this moment and YOU can help us
> making it faster to get released by testing scripts in our repository
> against latest 15.0 installation (full installation is always
> recommended).

Is there a list of "not-testet-yet" or "known-as-failed/needing-a-fix" 
scripts?
Otherwise it's very random/inefficient what the community can do to help 
out.

Johannes

From z.coldplayer at gmail.com  Fri Feb  4 15:59:59 2022
From: z.coldplayer at gmail.com (Jheengut Pritvi)
Date: Fri, 4 Feb 2022 19:59:59 +0400
Subject: [Slackbuilds-users] Slackware 15.0 Released
In-Reply-To: <e3854e4dcd357dc1865e05c93a0005e5@schoepfer.info>
References: <1e26b81d-7046-4a65-26f2-b6e6116428d9@slackbuilds.org>
 <e3854e4dcd357dc1865e05c93a0005e5@schoepfer.info>
Message-ID: <CAEWL1_9q+34Kfmwbyj2qqkLtv76eWWEvSZOO-SA397kUkeGVhA@mail.gmail.com>

I don't think so.



On Fri, 4 Feb 2022 at 19:36, Franzen via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> > So what about SBo 15.0 repo?
> > Well, we are still working on it at this moment and YOU can help us
> > making it faster to get released by testing scripts in our repository
> > against latest 15.0 installation (full installation is always
> > recommended).
>
> Is there a list of "not-testet-yet" or "known-as-failed/needing-a-fix"
> scripts?
> Otherwise it's very random/inefficient what the community can do to help
> out.
>
> 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/20220204/36275395/attachment.htm>

From bgrundy at gmail.com  Fri Feb  4 16:53:06 2022
From: bgrundy at gmail.com (Barry J. Grundy)
Date: Fri, 4 Feb 2022 11:53:06 -0500
Subject: [Slackbuilds-users] Orphans
Message-ID: <ec3407bd-7c00-6214-0ddc-6ebaed9f44c0@gmail.com>

In the process of updating my SlackBuilds, I came across several 
packages that I no longer need.

If anyone would like to take them over, please do so.  Otherwise I'll 
likely abandon them.  As far as I can tell no other packages depend on 
these.

python/backports.lzma
python/binplist
python/biplist
python/construct
python/dotty
python/hachoir-core
python/hachoir-metadata
python/hachoir-parser
python/pysqlite (no longer maintained upstream)

Thanks,
Barry

From kingbeowulf at gmail.com  Fri Feb  4 17:39:20 2022
From: kingbeowulf at gmail.com (King Beowulf)
Date: Fri, 4 Feb 2022 09:39:20 -0800
Subject: [Slackbuilds-users] wxcam compile errors on Slackware 15.0
Message-ID: <220c73bc-d566-de3e-4c78-8352ce3bc4f4@gmail.com>

(oops sent this via the wrong email address)

Hello admins,

wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and
hasn't been updated upstream since 2011.  Since I switched to guvcview,
we can:

1. Drop it from SBo.
2. Put it up for grabs for someone to take over as maintainer.

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

From yalhcru at gmail.com  Fri Feb  4 18:56:24 2022
From: yalhcru at gmail.com (B Watson)
Date: Fri, 4 Feb 2022 13:56:24 -0500
Subject: [Slackbuilds-users] Orphans
In-Reply-To: <ec3407bd-7c00-6214-0ddc-6ebaed9f44c0@gmail.com>
References: <ec3407bd-7c00-6214-0ddc-6ebaed9f44c0@gmail.com>
Message-ID: <CAN1hMuBwDWJwfQAhXj=vSVRuKKZVRGB-29sDHv-kjAPn0QWQaA@mail.gmail.com>

On 2/4/22, Barry J. Grundy <bgrundy at gmail.com> wrote:
> In the process of updating my SlackBuilds, I came across several
> packages that I no longer need.
>
> If anyone would like to take them over, please do so.  Otherwise I'll
> likely abandon them.  As far as I can tell no other packages depend on
> these.
>
> python/backports.lzma
> python/binplist
> python/biplist
> python/construct
> python/dotty
> python/hachoir-core
> python/hachoir-metadata
> python/hachoir-parser
> python/pysqlite (no longer maintained upstream)

Most of these are dependencies for your own dfvfs and/or plaso builds.
Are you abandoning those, too?

From yalhcru at gmail.com  Fri Feb  4 19:30:27 2022
From: yalhcru at gmail.com (B Watson)
Date: Fri, 4 Feb 2022 14:30:27 -0500
Subject: [Slackbuilds-users] wxcam compile errors on Slackware 15.0
In-Reply-To: <220c73bc-d566-de3e-4c78-8352ce3bc4f4@gmail.com>
References: <220c73bc-d566-de3e-4c78-8352ce3bc4f4@gmail.com>
Message-ID: <CAN1hMuCm4O-xaPgjDN0AVBDFAiqeGx0+Z1obNizgcfCmQ76PjA@mail.gmail.com>

On 2/4/22, King Beowulf <kingbeowulf at gmail.com> wrote:
> (oops sent this via the wrong email address)
>
> Hello admins,
>
> wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and
> hasn't been updated upstream since 2011.  Since I switched to guvcview,
> we can:

Huh? It compiles just fine.

Most likely you've fallen victim to the wxPython vs. wxGTK3 brain
damage. To get wxcam to compile, (re)install wxPython. Whichever of
wxPython or wxGTK3 gets installed last "wins" the /usr/bin/wx-config
symlink.

> 1. Drop it from SBo.
> 2. Put it up for grabs for someone to take over as maintainer.

No need, if it actually works. I can compile it, but I don't have easy
access to any webcam to test it with.

From bgrundy at gmail.com  Fri Feb  4 19:49:44 2022
From: bgrundy at gmail.com (Barry Grundy)
Date: Fri, 4 Feb 2022 14:49:44 -0500
Subject: [Slackbuilds-users] Orphans
In-Reply-To: <CAN1hMuBwDWJwfQAhXj=vSVRuKKZVRGB-29sDHv-kjAPn0QWQaA@mail.gmail.com>
References: <ec3407bd-7c00-6214-0ddc-6ebaed9f44c0@gmail.com>
 <CAN1hMuBwDWJwfQAhXj=vSVRuKKZVRGB-29sDHv-kjAPn0QWQaA@mail.gmail.com>
Message-ID: <CAH74TFjhhGS6yeGkPQJYLOo1GnykBNsSbHuJigeukGWxBwgoSQ@mail.gmail.com>

On Fri, Feb 4, 2022 at 1:56 PM B Watson <yalhcru at gmail.com> wrote:

> On 2/4/22, Barry J. Grundy <bgrundy at gmail.com> wrote:
> > In the process of updating my SlackBuilds, I came across several
> > packages that I no longer need.
> >
> > If anyone would like to take them over, please do so.  Otherwise I'll
> > likely abandon them.  As far as I can tell no other packages depend on
> > these.
> >
> > python/backports.lzma
> > python/binplist
> > python/biplist
> > python/construct
> > python/dotty
> > python/hachoir-core
> > python/hachoir-metadata
> > python/hachoir-parser
> > python/pysqlite (no longer maintained upstream)
>
> Most of these are dependencies for your own dfvfs and/or plaso builds.
> Are you abandoning those, too?
> _______________________________________________
> 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/
>
>
No.  The dependencies changed.  I've updated plaso/dfvfs (which have gone
through significant changes) and added new dependencies.  These (above) are
orphaned because they are no longer required, I have no personal use for
them, and I do not see them needed elsewhere.

-- 
----
Barry Grundy
bgrundy at gmail.com
bgrundy at linuxleo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220204/2944994a/attachment-0001.htm>

From heiko.rosemann at web.de  Fri Feb  4 22:15:50 2022
From: heiko.rosemann at web.de (Heiko Rosemann)
Date: Fri, 4 Feb 2022 23:15:50 +0100
Subject: [Slackbuilds-users] Giving up libraries/openjfx
Message-ID: <4248578b-9e40-7272-ba31-324d4d784a18@web.de>

Hello everyone,

I'm ready to give up openjfx. For years, no upstream updates to the 
binary build I've been repackaging plus I don't need it any more (used 
to be a dependency of MediathekView, but they include their own JRE and 
JavaFX these days).

Considering it's years behind and all things java seem to have a 
tendency to create security issues I'll prepare a github PR next week to 
delete it, unless someone wants to take it over.

Although I'd suggest having a look at packaging an Azul JDK/JRE with FX 
instead: 
https://www.azul.com/downloads/?version=java-8-lts&os=linux&package=jdk-fx

Cheers,
Heiko

P.S: Just noticed someone is working on zulu-openjdk11. Thanks for that! 
I need that for an old 32bit machine...
-- 
eMails verschl?sseln mit PGP - privacy is your right!
Mein PGP-Key zur Verifizierung: http://pgp.mit.edu

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

From kingbeowulf at gmail.com  Sat Feb  5 01:43:23 2022
From: kingbeowulf at gmail.com (King Beowulf)
Date: Fri, 4 Feb 2022 17:43:23 -0800
Subject: [Slackbuilds-users] wxcam compile errors on Slackware 15.0
In-Reply-To: <CAN1hMuCm4O-xaPgjDN0AVBDFAiqeGx0+Z1obNizgcfCmQ76PjA@mail.gmail.com>
References: <220c73bc-d566-de3e-4c78-8352ce3bc4f4@gmail.com>
 <CAN1hMuCm4O-xaPgjDN0AVBDFAiqeGx0+Z1obNizgcfCmQ76PjA@mail.gmail.com>
Message-ID: <fa71f049-1afc-51a2-bfbe-e07f00114d8b@gmail.com>

On 2/4/22 11:30, B Watson wrote:
> On 2/4/22, King Beowulf <kingbeowulf at gmail.com> wrote:
>> (oops sent this via the wrong email address)
>>
>> Hello admins,
>>
>> wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and
>> hasn't been updated upstream since 2011.  Since I switched to guvcview,
>> we can:
> 
> Huh? It compiles just fine.
> 

Well slap me silly and call me a goof ball. I had forgotten to clean out
the VM image snapshot after updating qemu to 6.2 and compiling a few
other doodads when I tried to compile it again.  Silly me. 2 yrs of
current testing...

Heck it even works on the old laptop builtin webcam.

I'll continue to maintain, unless someone else is desperate to take it
over.

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

From duncan_roe at optusnet.com.au  Sat Feb  5 06:48:00 2022
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Sat, 5 Feb 2022 17:48:00 +1100
Subject: [Slackbuilds-users] [SlackBuildsOrg/slackbuilds] For s bo (PR
 #1143)
In-Reply-To: <SlackBuildsOrg/slackbuilds/pull/1143/c1029619350@github.com>
References: <SlackBuildsOrg/slackbuilds/pull/1143@github.com>
 <SlackBuildsOrg/slackbuilds/pull/1143/c1029619350@github.com>
Message-ID: <Yf4doLR7l1ypKi7i@slk1.local.net>

Hi Willy,

I must be doing something wrong but I don't know just what.

I forked the GitHub mirror https://github.com/SlackBuildsOrg/slackbuilds

I left Firefox on https://github.com/duncan-roe/slackbuilds-1/tree/for_SBo

Whenever I clicked "Fetch upstream" I got "This branch is not behind the
upstream SlackBuildsOrg:master.".

Just now I moved to
https://github.com/duncan-roe/slackbuilds-1/tree/for_SBo/academic and then
update fetched 420 changes.

Perhaps a GitHub bug?

Anyway, I'll fix up mkchroot ASAP.

Cheers ... Duncan.

On Thu, Feb 03, 2022 at 08:16:09PM -0800, Willy Sudiarto Raharjo wrote:
> mkchroot patch does not apply, probably it has been updated and you haven't rebased to latest changes in master?

From slackbuilds at schoepfer.info  Sat Feb  5 10:54:09 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 05 Feb 2022 11:54:09 +0100
Subject: [Slackbuilds-users] minitube patch
Message-ID: <2b79da0ccd27439597124be8edddeb71@schoepfer.info>

minitube patch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: minitube.patch
Type: text/x-diff
Size: 2897 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220205/3b333d8f/attachment.bin>

From lists at osh.id.au  Sat Feb  5 12:27:38 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Sat, 05 Feb 2022 20:27:38 +0800
Subject: [Slackbuilds-users] Slackware 15.0 Released
In-Reply-To: <1e26b81d-7046-4a65-26f2-b6e6116428d9@slackbuilds.org>
References: <1e26b81d-7046-4a65-26f2-b6e6116428d9@slackbuilds.org>
Message-ID: <8ed54738-74ab-43e0-af42-25a4b1c5dd70@www.fastmail.com>

On Fri, 4 Feb 2022, at 9:17 AM, Willy Sudiarto Raharjo wrote:
> or directly send us pull request / merge request on github/gitlab or via
> this mailing list (in .patch format would be better).

Great to see 15.0 finally out! To which git repo should we be sending updates?

From sbolokanov at abv.bg  Sat Feb  5 16:07:18 2022
From: sbolokanov at abv.bg (=?utf-8?B?0KEuINCR0L7Qu9C+0LrQsNC90LDRgNGK?=)
Date: Sat, 5 Feb 2022 18:07:18 +0200 (EET)
Subject: [Slackbuilds-users] Slackware 15.0 Released
In-Reply-To: <8ed54738-74ab-43e0-af42-25a4b1c5dd70@www.fastmail.com>
References: <1e26b81d-7046-4a65-26f2-b6e6116428d9@slackbuilds.org>
 <8ed54738-74ab-43e0-af42-25a4b1c5dd70@www.fastmail.com>
Message-ID: <1482181617.2057038.1644077238552@nm51.abv.bg>

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









 >-------- ?????????? ????? --------

 >??: "David O'Shaughnessy" lists at osh.id.au

 >???????: Re: [Slackbuilds-users] Slackware 15.0 Released

 >??: "SlackBuilds.org Users List"  

 >????????? ??: 05.02.2022 14:27


On Fri, 4 Feb 2022, at 9:17 AM, Willy Sudiarto Raharjo wrote:

> or directly send us pull request / merge request on github/gitlab or via

> this mailing list (in .patch format would be better).



Great to see 15.0 finally out! To which git repo should we be sending updates?

_______________________________________________

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/20220205/9778c734/attachment-0001.htm>

From slackbuilds at schoepfer.info  Sat Feb  5 16:55:08 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 05 Feb 2022 17:55:08 +0100
Subject: [Slackbuilds-users] stockfish patch
Message-ID: <2dbc68821898271aced7e13b70f1d487@schoepfer.info>

stockfish patch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: stockfish.patch
Type: text/x-diff
Size: 2929 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220205/1ed61ae8/attachment.bin>

From yalhcru at gmail.com  Sat Feb  5 17:21:15 2022
From: yalhcru at gmail.com (B Watson)
Date: Sat, 5 Feb 2022 12:21:15 -0500
Subject: [Slackbuilds-users] stockfish patch
In-Reply-To: <2dbc68821898271aced7e13b70f1d487@schoepfer.info>
References: <2dbc68821898271aced7e13b70f1d487@schoepfer.info>
Message-ID: <CAN1hMuBwnPbuO7cfMhuLDzr=hs6nnZpfstMPHunn6fXye7oDig@mail.gmail.com>

On 2/5/22, Franzen via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:
> stockfish patch

This patch, and the one you just sent for minitube... should probably
not be sent to the mailing list with no context. stockfish and
minitube are maintained by Johannes Schoepfer, you should send your
patches to him.

From slackbuilds at schoepfer.info  Sat Feb  5 17:53:40 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 05 Feb 2022 18:53:40 +0100
Subject: [Slackbuilds-users] stockfish patch
In-Reply-To: <CAN1hMuBwnPbuO7cfMhuLDzr=hs6nnZpfstMPHunn6fXye7oDig@mail.gmail.com>
References: <2dbc68821898271aced7e13b70f1d487@schoepfer.info>
 <CAN1hMuBwnPbuO7cfMhuLDzr=hs6nnZpfstMPHunn6fXye7oDig@mail.gmail.com>
Message-ID: <62f25ad0efec2de3412b25f49ccdffa4@schoepfer.info>

On 2022-02-05 18:21, B Watson wrote:
> On 2/5/22, Franzen via SlackBuilds-users
> <slackbuilds-users at slackbuilds.org> wrote:
>> stockfish patch
> 
> This patch, and the one you just sent for minitube... should probably
> not be sent to the mailing list with no context. stockfish and
> minitube are maintained by Johannes Schoepfer, you should send your
> patches to him.

Sorry for the confusion, i am Johannes ;-)
I Can't really prove it, but i think Robby knows.
Is it then ok to send further patches here? That's how i understood the 
mail from willy.

Johannes Sch?pfer aka franzen

From johannes at schoepfer.info  Sat Feb  5 18:04:14 2022
From: johannes at schoepfer.info (johannes at schoepfer.info)
Date: Sat, 05 Feb 2022 19:04:14 +0100
Subject: [Slackbuilds-users] stockfish patch
In-Reply-To: <62f25ad0efec2de3412b25f49ccdffa4@schoepfer.info>
References: <2dbc68821898271aced7e13b70f1d487@schoepfer.info>
 <CAN1hMuBwnPbuO7cfMhuLDzr=hs6nnZpfstMPHunn6fXye7oDig@mail.gmail.com>
 <62f25ad0efec2de3412b25f49ccdffa4@schoepfer.info>
Message-ID: <adb31cacf87511ac91ff2f67d9679a72@schoepfer.info>

>> This patch, and the one you just sent for minitube... should probably
>> not be sent to the mailing list with no context. stockfish and
>> minitube are maintained by Johannes Schoepfer, you should send your
>> patches to him.
> 
> Sorry for the confusion, i am Johannes ;-)
> I Can't really prove it, but i think Robby knows.

I hope proven this way(see mail-from), Johannes = Franzen.

Patch for asymptote attached, hope that's ok this way.

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: asymptote.patch
Type: text/x-diff
Size: 1925 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220205/9871070b/attachment.bin>

From yalhcru at gmail.com  Sat Feb  5 18:28:04 2022
From: yalhcru at gmail.com (B Watson)
Date: Sat, 5 Feb 2022 13:28:04 -0500
Subject: [Slackbuilds-users] stockfish patch
In-Reply-To: <62f25ad0efec2de3412b25f49ccdffa4@schoepfer.info>
References: <2dbc68821898271aced7e13b70f1d487@schoepfer.info>
 <CAN1hMuBwnPbuO7cfMhuLDzr=hs6nnZpfstMPHunn6fXye7oDig@mail.gmail.com>
 <62f25ad0efec2de3412b25f49ccdffa4@schoepfer.info>
Message-ID: <CAN1hMuDEJoZFkfT7Cf__mNW5sEnewvZPXCEv5vK0qPBM5CFOBA@mail.gmail.com>

On 2/5/22, Franzen via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:
>
> Sorry for the confusion, i am Johannes ;-)
> I Can't really prove it, but i think Robby knows.

Ah! Sorry, I didn't know that...

> Is it then ok to send further patches here? That's how i understood the
> mail from willy.

Yes, it's fine.

From duncan_roe at optusnet.com.au  Sun Feb  6 06:07:55 2022
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Sun, 6 Feb 2022 17:07:55 +1100
Subject: [Slackbuilds-users] [SlackBuildsOrg/slackbuilds] For s bo (PR
 #1143)
Message-ID: <Yf9luykcCYsstqxf@slk1.local.net>

Hi Willy,

You already have the latest mkchroot in master. You got an extra copy because I
didn't delete and recreate my for_SBo branch on GitHub.

Cheers ... Duncan.

On Thu, Feb 03, 2022 at 08:16:09PM -0800, Willy Sudiarto Raharjo wrote:
> mkchroot patch does not apply, probably it has been updated and you haven't rebased to latest changes in master?

From duncan_roe at optusnet.com.au  Sun Feb  6 06:37:13 2022
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Sun, 6 Feb 2022 17:37:13 +1100
Subject: [Slackbuilds-users] [SlackBuildsOrg/slackbuilds]
 academic/sage-bin: Updated for version 9.4 (PR #1160)
Message-ID: <Yf9smYNLs5wtatuQ@slk1.local.net>

Hi Willy,

On Sat, Feb 05, 2022 at 10:03:11PM -0800, Willy Sudiarto Raharjo wrote:
> Hi @duncan-roe is it possible to put the tar_xz files outside of the repository and put it in the .info files?

debian_binaries-11.2.tar_xz is <2K so not worth worrying about I'd suggest.

debian_libraries-11.2.tar_xz at 270K would add 25% to the repo size so
can we put it in the repo you have for big files? Then I could list it
on the DOWNLOAD line.
Cheers ... Duncan.

From willysr at slackbuilds.org  Sun Feb  6 06:37:47 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 6 Feb 2022 13:37:47 +0700
Subject: [Slackbuilds-users] wxcam compile errors on Slackware 15.0
In-Reply-To: <220c73bc-d566-de3e-4c78-8352ce3bc4f4@gmail.com>
References: <220c73bc-d566-de3e-4c78-8352ce3bc4f4@gmail.com>
Message-ID: <4b471c66-2b9e-b6ae-2af4-a81e3b1f7779@slackbuilds.org>

> wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and
> hasn't been updated upstream since 2011.  Since I switched to guvcview,
> we can:
> 
> 1. Drop it from SBo.
> 2. Put it up for grabs for someone to take over as maintainer.

Someone send a report in LQ and Ponce seems already fix it
https://git.slackbuilds.org/slackbuilds/commit/?id=b301029c1c7bd26b3f26cbcbd7a42d7b36a47b30


-- 
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/20220206/de45cd13/attachment.asc>

From willysr at slackbuilds.org  Sun Feb  6 06:39:08 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 6 Feb 2022 13:39:08 +0700
Subject: [Slackbuilds-users] [SlackBuildsOrg/slackbuilds] For s bo (PR
 #1143)
In-Reply-To: <Yf4doLR7l1ypKi7i@slk1.local.net>
References: <SlackBuildsOrg/slackbuilds/pull/1143@github.com>
 <SlackBuildsOrg/slackbuilds/pull/1143/c1029619350@github.com>
 <Yf4doLR7l1ypKi7i@slk1.local.net>
Message-ID: <604d762a-d77e-ea80-2d4b-dc1b97ba1479@slackbuilds.org>

> I must be doing something wrong but I don't know just what.
> 
> I forked the GitHub mirror https://github.com/SlackBuildsOrg/slackbuilds
> 
> I left Firefox on https://github.com/duncan-roe/slackbuilds-1/tree/for_SBo
> 
> Whenever I clicked "Fetch upstream" I got "This branch is not behind the
> upstream SlackBuildsOrg:master.".
> 
> Just now I moved to
> https://github.com/duncan-roe/slackbuilds-1/tree/for_SBo/academic and then
> update fetched 420 changes.
> 
> Perhaps a GitHub bug?

You need to do these steps:
fork a project
make a separate branch
make some commits
push your branch to your public repository
send a PR to the original repository


-- 
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/20220206/c22f1890/attachment.asc>

From willysr at slackbuilds.org  Sun Feb  6 06:42:13 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 6 Feb 2022 13:42:13 +0700
Subject: [Slackbuilds-users] minitube patch
In-Reply-To: <2b79da0ccd27439597124be8edddeb71@schoepfer.info>
References: <2b79da0ccd27439597124be8edddeb71@schoepfer.info>
Message-ID: <574b7e33-7bb2-8fe0-07a5-218fbf955966@slackbuilds.org>

> minitube patch

Thanks, pushed to my branch


-- 
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/20220206/befe48fa/attachment.asc>

From ozan.turkyilmaz at gmail.com  Sun Feb  6 07:32:50 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Sun, 6 Feb 2022 10:32:50 +0300
Subject: [Slackbuilds-users] aMule
Message-ID: <CA+da1oozOWFJdqchsv2F8=dYx3XHtF8Ewgpdqj9SBRwZPmYfRQ@mail.gmail.com>

Hello All,

I am dropping maintenance of aMule. I don't use it nor do I have time to
look after it.
ANyone who wants can get it.

Regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220206/41ef06c4/attachment.htm>

From slackbuilds at schoepfer.info  Sun Feb  6 10:06:18 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sun, 06 Feb 2022 11:06:18 +0100
Subject: [Slackbuilds-users] dropping ftgl, ultimatestunts build fix
Message-ID: <e3ad6229a713033d9e20889f79bafbfb@schoepfer.info>

Hi,

i have no use for ftgl, would someone listed here 
https://slackbuilds.org/advsearch.php?q=ftgl&stype=revdep1 want to take 
over?

Also, attached a buildfix for ultimatestunts.

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ultimatestunts.patch
Type: text/x-diff
Size: 1159 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220206/2561b488/attachment.bin>

From slackbuilds at schoepfer.info  Sun Feb  6 15:36:29 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sun, 06 Feb 2022 16:36:29 +0100
Subject: [Slackbuilds-users] Slackbuild CreateCloudMap of no use anymore
Message-ID: <d1b1d8b481b5af011cef8d4d44c2b48c@schoepfer.info>

Hi,

the service behind CreateCloudMap(http://www.sat.dundee.ac.uk/) was shut 
down some time ago.
The buildscript is of no use anymore imho.

From slackbuilds at schoepfer.info  Sun Feb  6 16:29:35 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sun, 06 Feb 2022 17:29:35 +0100
Subject: [Slackbuilds-users] simple-scan patch
In-Reply-To: <f32cb8b042c7a9401825703faf8512d8@schoepfer.info>
References: <20211021074042.97113932DD@mail2.0ur.de>
 <2234112fc1884b476d4d2e7e41c722aa@schoepfer.info>
 <CAPsDuS4QX1LOTw=U_F1p6SLHvt6E8P_DvObG=ieLbV5Hcf67ig@mail.gmail.com>
 <28ad500add78112cb8d242d632fa16ea@schoepfer.info>
 <f32cb8b042c7a9401825703faf8512d8@schoepfer.info>
Message-ID: <cb496a52e1dcb6ac7b7c0f237b0eecbe@schoepfer.info>

Here i resend the patch/maintenance takeover for simple-scan.
This fixes the build on slackware 15.0 and removes the dependency on 
packagekit(doesn't build here), which is then unused by any other 
buildscript as hard dependency.

Johannes

-------- Original Message --------
Subject: Re: [Slackbuilds-users] Fwd: Undelivered Mail Returned to 
Sender
Date: 2021-10-24 17:57
 From: Franzen <slackbuilds at schoepfer.info>
To: slackbuilds-users at slackbuilds.org

>> have you tried at his gmail address too?
> 
> No, thanks, i now mailed to him with the gmail account.

Here's the answer from Nishant, and a patch for simple-scan,
the other builds will follow some time later.

Johannes


-------- Original Message --------
Subject: Re: Slackbuilds and maintaining
Date: 2021-10-21 13:39
 From: Nishant Limbachia <xxx at gmail.com>
To: Franzen <slackbuilds at schoepfer.info>

Hi Johannes,

Yes you can take over the maintenance of the slackbuilds. I personally
don't use Slack that much these days.

Nishant Limbachia

On Thu, Oct 21, 2021, 3:08 AM Franzen <slackbuilds at schoepfer.info>
wrote:

> Hi Nishant,
> 
> since your last commit to SBo was two years ago, i wonder if you're
> still active.
> I'm particular interested in the following builds:
> -gocr
> -simple-scan
> -pflogsumm
> -clamav-unofficial-sigs
> 
> May i take over maintenance for these?
> 
> Btw. the mailadress xxx at mnspace.net listed in your various other
> packages didn't work for me.
> 
> johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: simple-scan.patch
Type: text/x-diff
Size: 4874 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220206/40159fd6/attachment-0001.bin>

From mab974 at gmail.com  Sun Feb  6 16:35:06 2022
From: mab974 at gmail.com (Michel BEGUE)
Date: Sun, 6 Feb 2022 20:35:06 +0400
Subject: [Slackbuilds-users] keepassx compile errors on 15.0
Message-ID: <CAC5LoF1--47PB6wndtdpTEnJGbyRSpjjtnyLAW46kghq0chJYQ@mail.gmail.com>

Hi,

Current version still requires Qt 4.x.
and keepassx has its development stopped on december 2021.

So I think we have to drop it.

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

From matteo.bernardini at gmail.com  Sun Feb  6 16:51:41 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sun, 6 Feb 2022 17:51:41 +0100
Subject: [Slackbuilds-users] simple-scan patch
In-Reply-To: <cb496a52e1dcb6ac7b7c0f237b0eecbe@schoepfer.info>
References: <20211021074042.97113932DD@mail2.0ur.de>
 <2234112fc1884b476d4d2e7e41c722aa@schoepfer.info>
 <CAPsDuS4QX1LOTw=U_F1p6SLHvt6E8P_DvObG=ieLbV5Hcf67ig@mail.gmail.com>
 <28ad500add78112cb8d242d632fa16ea@schoepfer.info>
 <f32cb8b042c7a9401825703faf8512d8@schoepfer.info>
 <cb496a52e1dcb6ac7b7c0f237b0eecbe@schoepfer.info>
Message-ID: <CAPsDuS5pyL0hzrPPQPNC-NzAgV8MU0TfxHQqfCZOTHFq2hywgw@mail.gmail.com>

thanks Johannes, pushed!

Matteo

Il giorno dom 6 feb 2022 alle ore 17:29 Franzen via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> ha scritto:
>
> Here i resend the patch/maintenance takeover for simple-scan.
> This fixes the build on slackware 15.0 and removes the dependency on
> packagekit(doesn't build here), which is then unused by any other
> buildscript as hard dependency.
>
> Johannes
>
> -------- Original Message --------
> Subject: Re: [Slackbuilds-users] Fwd: Undelivered Mail Returned to
> Sender
> Date: 2021-10-24 17:57
>  From: Franzen <slackbuilds at schoepfer.info>
> To: slackbuilds-users at slackbuilds.org
>
> >> have you tried at his gmail address too?
> >
> > No, thanks, i now mailed to him with the gmail account.
>
> Here's the answer from Nishant, and a patch for simple-scan,
> the other builds will follow some time later.
>
> Johannes
>
>
> -------- Original Message --------
> Subject: Re: Slackbuilds and maintaining
> Date: 2021-10-21 13:39
>  From: Nishant Limbachia <xxx at gmail.com>
> To: Franzen <slackbuilds at schoepfer.info>
>
> Hi Johannes,
>
> Yes you can take over the maintenance of the slackbuilds. I personally
> don't use Slack that much these days.
>
> Nishant Limbachia
>
> On Thu, Oct 21, 2021, 3:08 AM Franzen <slackbuilds at schoepfer.info>
> wrote:
>
> > Hi Nishant,
> >
> > since your last commit to SBo was two years ago, i wonder if you're
> > still active.
> > I'm particular interested in the following builds:
> > -gocr
> > -simple-scan
> > -pflogsumm
> > -clamav-unofficial-sigs
> >
> > May i take over maintenance for these?
> >
> > Btw. the mailadress xxx at mnspace.net listed in your various other
> > packages didn't work for me.
> >
> > 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/
>

From erich.public at protonmail.com  Sun Feb  6 22:36:38 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Sun, 06 Feb 2022 22:36:38 +0000
Subject: [Slackbuilds-users] games/puzzles Takeover request
Message-ID: <it4_HZJ0__a1gglcwedwBLLyWW9u3npTCh57GV5rp-r-_DgBX85DiQ299c3tLsQ09P8APvsPVc4omcJ6nPW-AddtbansaBGc55pVQ9G4Tdo=@protonmail.com>

Hi Steve,

I see you haven't touched games/puzzles in over 10 years (the last version bump was by Matteo in 2013).  I wonder if I could take over maintainership?

The build system has changed from autoconf to cmake.  See my changes here:

https://gitlab.com/ErichRitz/slackbuilds/-/commit/8e090859d088a3c288217acf06500c28cd5c6c3c

Otherwise, would you consider updating?

Erich

From erich.public at protonmail.com  Sun Feb  6 22:42:12 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Sun, 06 Feb 2022 22:42:12 +0000
Subject: [Slackbuilds-users] games/puzzles Takeover request
In-Reply-To: <it4_HZJ0__a1gglcwedwBLLyWW9u3npTCh57GV5rp-r-_DgBX85DiQ299c3tLsQ09P8APvsPVc4omcJ6nPW-AddtbansaBGc55pVQ9G4Tdo=@protonmail.com>
References: <it4_HZJ0__a1gglcwedwBLLyWW9u3npTCh57GV5rp-r-_DgBX85DiQ299c3tLsQ09P8APvsPVc4omcJ6nPW-AddtbansaBGc55pVQ9G4Tdo=@protonmail.com>
Message-ID: <MNVtklVYrJv82VLtfYWbnGzBT7bp4yvQ8y2NKD5BYfDS61aiSg0ZHEsIbzeS0Jzd-kwxNw4EoyZ5bSrGZTVc1qIcv7ww3ASxJmD6xF_DEdE=@protonmail.com>

------- Original Message -------

On Sunday, February 6th, 2022 at 4:36 PM, Erich Ritz via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:

> Hi Steve,
>
> I see you haven't touched games/puzzles in over 10 years (the last version bump was by Matteo in 2013). I wonder if I could take over maintainership?
>
> The build system has changed from autoconf to cmake. See my changes here:
>
> https://gitlab.com/ErichRitz/slackbuilds/-/commit/8e090859d088a3c288217acf06500c28cd5c6c3c
>
> Otherwise, would you consider updating?
>
> Erich
>
> 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/

Hello list,

My email to Steve returned undeliverable ("This mailbox is disabled.")  Does anyone else know how to reach him?

grepping for Steve Pledger and his yahoo email address show these packages:

development/bacon
games/gens-gs
games/puzzles
libraries/hug
system/flSynclient

I'm interested in taking over games/puzzles.

Erich

From kingbeowulf at gmail.com  Mon Feb  7 01:45:38 2022
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 6 Feb 2022 17:45:38 -0800
Subject: [Slackbuilds-users] wxcam compile errors on Slackware 15.0
In-Reply-To: <4b471c66-2b9e-b6ae-2af4-a81e3b1f7779@slackbuilds.org>
References: <220c73bc-d566-de3e-4c78-8352ce3bc4f4@gmail.com>
 <4b471c66-2b9e-b6ae-2af4-a81e3b1f7779@slackbuilds.org>
Message-ID: <ff5c136d-380b-c049-a0ac-fda0dfd623e3@gmail.com>

On 2/5/22 22:37, Willy Sudiarto Raharjo wrote:
>> wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and
>> hasn't been updated upstream since 2011.  Since I switched to guvcview,
>> we can:
>>
>> 1. Drop it from SBo.
>> 2. Put it up for grabs for someone to take over as maintainer.
> 
> Someone send a report in LQ and Ponce seems already fix it
> https://git.slackbuilds.org/slackbuilds/commit/?id=b301029c1c7bd26b3f26cbcbd7a42d7b36a47b30
> 
> 
 Sweet.  Forgot about that one.  My issue turn out to be the order of
wxPython and wxGTK3 install and that stupid wx-config symlink.

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

From ozan.turkyilmaz at gmail.com  Mon Feb  7 08:02:20 2022
From: ozan.turkyilmaz at gmail.com (Ozan Turkyilmaz)
Date: Mon,  7 Feb 2022 11:02:20 +0300
Subject: [Slackbuilds-users] [PATCH] Chatbot-Eliza: Updated to 1.08. Added
 license to the script with approval of original author.
Message-ID: <20220207080220.12145-1-ozan.turkyilmaz@gmail.com>

---
 games/Chatbot-Eliza/Chatbot-Eliza.SlackBuild | 26 +++++++++++++++++---
 games/Chatbot-Eliza/Chatbot-Eliza.info       |  6 ++---
 2 files changed, 25 insertions(+), 7 deletions(-)

diff --git a/games/Chatbot-Eliza/Chatbot-Eliza.SlackBuild b/games/Chatbot-Eliza/Chatbot-Eliza.SlackBuild
index 31f9e2a079..29debbd031 100644
--- a/games/Chatbot-Eliza/Chatbot-Eliza.SlackBuild
+++ b/games/Chatbot-Eliza/Chatbot-Eliza.SlackBuild
@@ -2,16 +2,34 @@
 
 # Slackware build script for Chatbot-Eliza
 
-# Written by (Marco Cecchetti) (mrc.ildp at gmail.com)
+# Copyright Marco Cecchetti
+# 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.
 
+# Written by (Marco Cecchetti) (mrc.ildp at gmail.com)
 # Modified by the SlackBuilds.org project.
-
 # Maintained by Ozan T??rky??lmaz ozan.turkyilmaz at gmail.com
 
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=Chatbot-Eliza
-VERSION=${VERSION:-1.04}
+VERSION=${VERSION:-1.08}
 BUILD=${BUILD:-2}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -67,7 +85,7 @@ cp -a README \
   $PKG/usr/doc/$PRGNAM-$VERSION
 
 cp -a \
-  simple doctor.txt deutsch* norsk* twobots *.cgi \
+  examples/* \
     $PKG/usr/doc/$PRGNAM-$VERSION/examples
 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
 
diff --git a/games/Chatbot-Eliza/Chatbot-Eliza.info b/games/Chatbot-Eliza/Chatbot-Eliza.info
index e6a77c32c0..a22455ca12 100644
--- a/games/Chatbot-Eliza/Chatbot-Eliza.info
+++ b/games/Chatbot-Eliza/Chatbot-Eliza.info
@@ -1,8 +1,8 @@
 PRGNAM="Chatbot-Eliza"
-VERSION="1.04"
+VERSION="1.08"
 HOMEPAGE="https://metacpan.org/pod/Chatbot::Eliza"
-DOWNLOAD="https://cpan.metacpan.org/authors/id/J/JN/JNOLAN/Chatbot-Eliza-1.04.tar.gz"
-MD5SUM="754199bbe591eaa11301aee108586fcd"
+DOWNLOAD="https://cpan.metacpan.org/authors/id/G/GR/GRANTG/Chatbot-Eliza-1.08.tar.gz"
+MD5SUM="163fb58b76a945368f49092147ffde83"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""
-- 
2.35.1


From nix at nixing.mx  Mon Feb  7 08:51:47 2022
From: nix at nixing.mx (nix)
Date: Mon, 7 Feb 2022 02:51:47 -0600
Subject: [Slackbuilds-users] profanity xmpp client and libstrophe
Message-ID: <5f7577da-96cf-48d8-a9c1-621f71ff5bc2@nixing.mx>

Hey all,

I have spoken to Pedro and he's looking to give up the profanity packages.

I need these packages so I'd like to pick this Slackbuild.

I see that submissions are not open right now for updates,

I thought I'd just mention it in either case and I'll submit the

updated Slackbuilds when submissions are open again.


Thanks,

Eric


From fellype at gmail.com  Mon Feb  7 13:06:21 2022
From: fellype at gmail.com (Fellype)
Date: Mon, 7 Feb 2022 10:06:21 -0300
Subject: [Slackbuilds-users] About academic/qucs in Slackware 15.0 - does
 not build against qt5
Message-ID: <CAJJ5XvH8scjTOPHrQ6Kg3bB0MuogMB+eg1D8VpjYgeXAcEF_6g@mail.gmail.com>

Hi SBo Admins,

I'm the current maintainer of academic/qucs and I have to say that
qucs-0.0.19 does not build against Qt5.

In a private message, Kemal Ilgar Ero?lu suggested that I replace
qucs-0.0.19 with qucs-qt5-git like in AUR repo [1]. I think it is a good
idea. However, I haven't had time to take a look at that yet. So, I think
we have the following options at the moment:
a- simply remove qucs from the SBo repo
b- someone provide a Qt4 SlackBuild and we keep qucs-0.0.19 at SBo
c- remove qucs for now until I have time to provide a build script for
qucs-qt5
d- someone provides a build script for qucs-qt5 this time and we remove
qucs-0.0.19

Note that qucs-qt5-git is not an official Qucs release.

If anyone has another suggestion, I'd like to hear it. From my side, I'll
chose option c.

Thanks, and best regards,

Fellype

[1] https://aur.archlinux.org/packages/qucs-qt5-git
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220207/9ddfddb2/attachment.htm>

From fellype at gmail.com  Mon Feb  7 14:28:01 2022
From: fellype at gmail.com (Fellype)
Date: Mon, 7 Feb 2022 11:28:01 -0300
Subject: [Slackbuilds-users] About academic/qucs in Slackware 15.0 -
 does not build against qt5
In-Reply-To: <CAJJ5XvH8scjTOPHrQ6Kg3bB0MuogMB+eg1D8VpjYgeXAcEF_6g@mail.gmail.com>
References: <CAJJ5XvH8scjTOPHrQ6Kg3bB0MuogMB+eg1D8VpjYgeXAcEF_6g@mail.gmail.com>
Message-ID: <CAJJ5XvEAO+hyheDyCCJ=o+rLETK5PnHYk68dQWTDBAYy81FyaA@mail.gmail.com>

Hi,

I'm the current maintainer of academic/qucs and I have to say that
> qucs-0.0.19 does not build against Qt5.
>
> In a private message, Kemal Ilgar Ero?lu suggested that I replace
> qucs-0.0.19 with qucs-qt5-git like in AUR repo [1]. I think it is a good
> idea. However, I haven't had time to take a look at that yet. So, I think
> we have the following options at the moment:
> a- simply remove qucs from the SBo repo
> b- someone provide a Qt4 SlackBuild and we keep qucs-0.0.19 at SBo
> c- remove qucs for now until I have time to provide a build script for
> qucs-qt5
> d- someone provides a build script for qucs-qt5 this time and we remove
> qucs-0.0.19
>
>
I just saw that qt4 was added to SBo repo (at github) a few days ago. So, I
guess the choice is now option b :)
I'll provide the required adjustments to qucs.Slackbuild and related files
as soon as possible.

Regards,

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

From dchmelik at gmail.com  Mon Feb  7 15:05:00 2022
From: dchmelik at gmail.com (David Chmelik)
Date: Mon, 7 Feb 2022 07:05:00 -0800
Subject: [Slackbuilds-users] sqg fails
Message-ID: <f97b6924-cec7-1280-8a13-191fb18a5a05@gmail.com>

It's about time for anyone who uses many SlackBuilds to rebuild them all 
for Slackware 15 and see what works.? So, I tried 'sqg -a' (a tool with 
sbopkg to build queues) and go the following error.

root at .cosmos:~# sqg -a
Processing all SlackBuilds in the SBo-git repository...parallel: invalid 
option -- '-'
parallel [OPTIONS] command -- arguments
 ??????? for each argument, run command with argument, in parallel
parallel [OPTIONS] -- commands
 ??????? run specified commands in parallel
Done.


From slackph at posteo.de  Mon Feb  7 15:15:25 2022
From: slackph at posteo.de (Philip Lacroix)
Date: Mon, 07 Feb 2022 15:15:25 +0000
Subject: [Slackbuilds-users] patch: coriander
Message-ID: <011f7938616c7c28c5dea3c523ac6639@posteo.de>

Hi

Here is a patch for coriander, based on slackbuilds-master.

Builds fine on stock Slackware 15.0 and 15.0_64. I had to
use the -fcommon flag (gcc >=10).

Cheers,
Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: coriander.patch
Type: text/x-diff
Size: 1196 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220207/fe2f5d21/attachment.bin>

From yalhcru at gmail.com  Mon Feb  7 15:56:55 2022
From: yalhcru at gmail.com (B Watson)
Date: Mon, 7 Feb 2022 10:56:55 -0500
Subject: [Slackbuilds-users] dropping ftgl, ultimatestunts build fix
In-Reply-To: <e3ad6229a713033d9e20889f79bafbfb@schoepfer.info>
References: <e3ad6229a713033d9e20889f79bafbfb@schoepfer.info>
Message-ID: <CAN1hMuAujT+CDA3r88dQKOouymYyLRG8QUumFpySF6a_cAdz9w@mail.gmail.com>

On 2/6/22, Franzen via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:

> i have no use for ftgl, would someone listed here
> https://slackbuilds.org/advsearch.php?q=ftgl&stype=revdep1 want to take
> over?

I can take this.

From yalhcru at gmail.com  Mon Feb  7 15:58:47 2022
From: yalhcru at gmail.com (B Watson)
Date: Mon, 7 Feb 2022 10:58:47 -0500
Subject: [Slackbuilds-users] wxcam compile errors on Slackware 15.0
In-Reply-To: <ff5c136d-380b-c049-a0ac-fda0dfd623e3@gmail.com>
References: <220c73bc-d566-de3e-4c78-8352ce3bc4f4@gmail.com>
 <4b471c66-2b9e-b6ae-2af4-a81e3b1f7779@slackbuilds.org>
 <ff5c136d-380b-c049-a0ac-fda0dfd623e3@gmail.com>
Message-ID: <CAN1hMuCDA79_TfbzrTb2sJ8BH_Kr8BBSt7PsTL+goK3-UyUYcg@mail.gmail.com>

On 2/6/22, King Beowulf <kingbeowulf at gmail.com> wrote:

>  Sweet.  Forgot about that one.  My issue turn out to be the order of
> wxPython and wxGTK3 install and that stupid wx-config symlink.

There are ways to write build scripts so they don't depend on the
symlink. How exactly you do it depends on how the build process
works. If you like, I'll patch your script to work that way, since
I've got experience doing it (all my wx(Python|GTK3) scripts are
written that way).

From yalhcru at gmail.com  Mon Feb  7 16:04:43 2022
From: yalhcru at gmail.com (B Watson)
Date: Mon, 7 Feb 2022 11:04:43 -0500
Subject: [Slackbuilds-users] sqg fails
In-Reply-To: <f97b6924-cec7-1280-8a13-191fb18a5a05@gmail.com>
References: <f97b6924-cec7-1280-8a13-191fb18a5a05@gmail.com>
Message-ID: <CAN1hMuCdY+4nFboJ9RZEDVH924Pe5meM-UhLDSe51QLHSc8mng@mail.gmail.com>

On 2/7/22, David Chmelik <dchmelik at gmail.com> wrote:

> root at .cosmos:~# sqg -a
> Processing all SlackBuilds in the SBo-git repository...parallel: invalid
> option -- '-'
> parallel [OPTIONS] command -- arguments
>          for each argument, run command with argument, in parallel
> parallel [OPTIONS] -- commands
>          run specified commands in parallel
> Done.

This means you have 'moreutils' installed, and you built it with
PARALLEL=yes. There are 2 completely different 'parallel' commands,
one is from the Slackware parallel package and the other is from
moreutils... you've got the wrong one.

To fix it, you can just 'slackpkg reinstall parallel'.

Interesting that sqg uses parallel, I didn't know that.

From yalhcru at gmail.com  Mon Feb  7 16:13:34 2022
From: yalhcru at gmail.com (B Watson)
Date: Mon, 7 Feb 2022 11:13:34 -0500
Subject: [Slackbuilds-users] dropping ftgl, ultimatestunts build fix
In-Reply-To: <e3ad6229a713033d9e20889f79bafbfb@schoepfer.info>
References: <e3ad6229a713033d9e20889f79bafbfb@schoepfer.info>
Message-ID: <CAN1hMuCcq+RVfq7_uFhe2rX5JsC9YEDMV4D0H44W_BOYGDMUJg@mail.gmail.com>

On 2/6/22, Franzen via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:

> i have no use for ftgl, would someone listed here
> https://slackbuilds.org/advsearch.php?q=ftgl&stype=revdep1 want to take
> over?

I should have asked...

When I take this over, do you mind if I replace your license with the
WTFPL, to match my other scripts?

From yalhcru at gmail.com  Mon Feb  7 16:18:36 2022
From: yalhcru at gmail.com (B Watson)
Date: Mon, 7 Feb 2022 11:18:36 -0500
Subject: [Slackbuilds-users] keepassx compile errors on 15.0
In-Reply-To: <CAC5LoF1--47PB6wndtdpTEnJGbyRSpjjtnyLAW46kghq0chJYQ@mail.gmail.com>
References: <CAC5LoF1--47PB6wndtdpTEnJGbyRSpjjtnyLAW46kghq0chJYQ@mail.gmail.com>
Message-ID: <CAN1hMuAQ=1YywrV2d6XjzeR+=5wE4=qO0=9cwunRVTEQH=ofhQ@mail.gmail.com>

On 2/6/22, Michel BEGUE <mab974 at gmail.com> wrote:

> Current version still requires Qt 4.x.
> and keepassx has its development stopped on december 2021.
> So I think we have to drop it.

We have qt4 for 15.0 now. I just tested it: if qt4 is installed,
keepassx.SlackBuild finds it without any modifications.

So all that's needed is to put REQUIRES="qt4" in keepassx.info (which
I've done in my git branch, so no need for you to do it).

Dec 2021 wasn't that long ago. Is the software still useful?

From slackbuilds at schoepfer.info  Mon Feb  7 16:29:28 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 07 Feb 2022 17:29:28 +0100
Subject: [Slackbuilds-users] dropping ftgl, ultimatestunts build fix
In-Reply-To: <CAN1hMuCcq+RVfq7_uFhe2rX5JsC9YEDMV4D0H44W_BOYGDMUJg@mail.gmail.com>
References: <e3ad6229a713033d9e20889f79bafbfb@schoepfer.info>
 <CAN1hMuCcq+RVfq7_uFhe2rX5JsC9YEDMV4D0H44W_BOYGDMUJg@mail.gmail.com>
Message-ID: <dfaadd42792afa7beba302dc9caac865@schoepfer.info>

On 2022-02-07 17:13, B Watson wrote:
> On 2/6/22, Franzen via SlackBuilds-users
> <slackbuilds-users at slackbuilds.org> wrote:
> 
>> i have no use for ftgl, would someone listed here
>> https://slackbuilds.org/advsearch.php?q=ftgl&stype=revdep1 want to 
>> take
>> over?
> 
> I should have asked...
> 
> When I take this over, do you mind if I replace your license with the
> WTFPL, to match my other scripts?

Sure, no problem.

From yalhcru at gmail.com  Mon Feb  7 16:51:26 2022
From: yalhcru at gmail.com (B Watson)
Date: Mon, 7 Feb 2022 11:51:26 -0500
Subject: [Slackbuilds-users] dropping ftgl, ultimatestunts build fix
In-Reply-To: <dfaadd42792afa7beba302dc9caac865@schoepfer.info>
References: <e3ad6229a713033d9e20889f79bafbfb@schoepfer.info>
 <CAN1hMuCcq+RVfq7_uFhe2rX5JsC9YEDMV4D0H44W_BOYGDMUJg@mail.gmail.com>
 <dfaadd42792afa7beba302dc9caac865@schoepfer.info>
Message-ID: <CAN1hMuDpr+qyJF9Nc96Se=XF7tt5MOPwcGMenLLYGMO2VCZr5g@mail.gmail.com>

On 2/7/22, Franzen via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:
>
> Sure, no problem.

Thanks.

From willysr at slackbuilds.org  Mon Feb  7 16:51:50 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 7 Feb 2022 23:51:50 +0700
Subject: [Slackbuilds-users] Slackbuild CreateCloudMap of no use anymore
In-Reply-To: <d1b1d8b481b5af011cef8d4d44c2b48c@schoepfer.info>
References: <d1b1d8b481b5af011cef8d4d44c2b48c@schoepfer.info>
Message-ID: <41f6fddc-52d7-ded4-5057-d8b23a2c1b79@slackbuilds.org>

> the service behind CreateCloudMap(http://www.sat.dundee.ac.uk/) was shut
> down some time ago.
> The buildscript is of no use anymore imho.

Thanks
pushed to my branch


-- 
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/20220207/dc6a4305/attachment.asc>

From willysr at slackbuilds.org  Mon Feb  7 16:53:06 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 7 Feb 2022 23:53:06 +0700
Subject: [Slackbuilds-users] games/puzzles Takeover request
In-Reply-To: <MNVtklVYrJv82VLtfYWbnGzBT7bp4yvQ8y2NKD5BYfDS61aiSg0ZHEsIbzeS0Jzd-kwxNw4EoyZ5bSrGZTVc1qIcv7ww3ASxJmD6xF_DEdE=@protonmail.com>
References: <it4_HZJ0__a1gglcwedwBLLyWW9u3npTCh57GV5rp-r-_DgBX85DiQ299c3tLsQ09P8APvsPVc4omcJ6nPW-AddtbansaBGc55pVQ9G4Tdo=@protonmail.com>
 <MNVtklVYrJv82VLtfYWbnGzBT7bp4yvQ8y2NKD5BYfDS61aiSg0ZHEsIbzeS0Jzd-kwxNw4EoyZ5bSrGZTVc1qIcv7ww3ASxJmD6xF_DEdE=@protonmail.com>
Message-ID: <131d7279-20fc-7d0f-bb76-0d95e71fcc34@slackbuilds.org>

> My email to Steve returned undeliverable ("This mailbox is disabled.")  Does anyone else know how to reach him?
> 
> grepping for Steve Pledger and his yahoo email address show these packages:
> 
> development/bacon
> games/gens-gs
> games/puzzles
> libraries/hug
> system/flSynclient
> 
> I'm interested in taking over games/puzzles.

Sure, send a patch or send PR/MR


-- 
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/20220207/a5af19b9/attachment.asc>

From willysr at slackbuilds.org  Mon Feb  7 17:01:16 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 8 Feb 2022 00:01:16 +0700
Subject: [Slackbuilds-users] patch: coriander
In-Reply-To: <011f7938616c7c28c5dea3c523ac6639@posteo.de>
References: <011f7938616c7c28c5dea3c523ac6639@posteo.de>
Message-ID: <4f66fc76-0527-cef4-ed82-85cd1e4083c0@slackbuilds.org>

> Here is a patch for coriander, based on slackbuilds-master.
> 
> Builds fine on stock Slackware 15.0 and 15.0_64. I had to
> use the -fcommon flag (gcc >=10).

Thanks
pushed to my branch


-- 
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/20220208/d16bfef7/attachment.asc>

From willysr at slackbuilds.org  Mon Feb  7 17:02:55 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 8 Feb 2022 00:02:55 +0700
Subject: [Slackbuilds-users] [PATCH] Chatbot-Eliza: Updated to 1.08.
 Added license to the script with approval of original author.
In-Reply-To: <20220207080220.12145-1-ozan.turkyilmaz@gmail.com>
References: <20220207080220.12145-1-ozan.turkyilmaz@gmail.com>
Message-ID: <a469e59d-8fbb-0770-4f49-3089009db5b6@slackbuilds.org>

Can you send in a patch format as attachment?

-- 
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/20220208/21ff14d0/attachment.asc>

From mab974 at gmail.com  Mon Feb  7 18:46:53 2022
From: mab974 at gmail.com (Michel BEGUE)
Date: Mon, 7 Feb 2022 22:46:53 +0400
Subject: [Slackbuilds-users] keepassx compile errors on 15.0
In-Reply-To: <CAN1hMuAQ=1YywrV2d6XjzeR+=5wE4=qO0=9cwunRVTEQH=ofhQ@mail.gmail.com>
References: <CAC5LoF1--47PB6wndtdpTEnJGbyRSpjjtnyLAW46kghq0chJYQ@mail.gmail.com>
 <CAN1hMuAQ=1YywrV2d6XjzeR+=5wE4=qO0=9cwunRVTEQH=ofhQ@mail.gmail.com>
Message-ID: <CAC5LoF01=zi7XnC-8mgJQUPBk9p2Bzj_K5WG=dnzeNjpepWYoA@mail.gmail.com>

Le lun. 7 f?vr. 2022 ? 20:18, B Watson <yalhcru at gmail.com> a ?crit :

> On 2/6/22, Michel BEGUE <mab974 at gmail.com> wrote:
>
> > Current version still requires Qt 4.x.
> > and keepassx has its development stopped on december 2021.
> > So I think we have to drop it.
>
> We have qt4 for 15.0 now. I just tested it: if qt4 is installed,
> keepassx.SlackBuild finds it without any modifications.
>
> So all that's needed is to put REQUIRES="qt4" in keepassx.info (which
> I've done in my git branch, so no need for you to do it).
>
> Dec 2021 wasn't that long ago. Is the software still useful?
>
>
We can do that for now.

On their site we are advised to switch to keepassxc. This many users have
already done. Even me on my main installation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220207/ac12949c/attachment-0001.htm>

From kingbeowulf at gmail.com  Mon Feb  7 23:13:41 2022
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 7 Feb 2022 15:13:41 -0800
Subject: [Slackbuilds-users] wxcam compile errors on Slackware 15.0
In-Reply-To: <CAN1hMuCDA79_TfbzrTb2sJ8BH_Kr8BBSt7PsTL+goK3-UyUYcg@mail.gmail.com>
References: <220c73bc-d566-de3e-4c78-8352ce3bc4f4@gmail.com>
 <4b471c66-2b9e-b6ae-2af4-a81e3b1f7779@slackbuilds.org>
 <ff5c136d-380b-c049-a0ac-fda0dfd623e3@gmail.com>
 <CAN1hMuCDA79_TfbzrTb2sJ8BH_Kr8BBSt7PsTL+goK3-UyUYcg@mail.gmail.com>
Message-ID: <1da08a15-c65e-aa07-f0ec-749f73ac8fba@gmail.com>

On 2/7/22 07:58, B Watson wrote:
> On 2/6/22, King Beowulf <kingbeowulf at gmail.com> wrote:
> 
>>  Sweet.  Forgot about that one.  My issue turn out to be the order of
>> wxPython and wxGTK3 install and that stupid wx-config symlink.
> 
> There are ways to write build scripts so they don't depend on the
> symlink. How exactly you do it depends on how the build process
> works. If you like, I'll patch your script to work that way, since
> I've got experience doing it (all my wx(Python|GTK3) scripts are
> written that way).

Thanks, that'll be spiffy.  All my other stuff is wxGTK3, so usually not
an issue there.  Only wxcam needs the older wxPython. pain in the rump
to keep track. If you could tweak wxcam so I can see how it's done
that'd be great.

-kb


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

From yalhcru at gmail.com  Mon Feb  7 23:58:05 2022
From: yalhcru at gmail.com (B Watson)
Date: Mon, 7 Feb 2022 18:58:05 -0500
Subject: [Slackbuilds-users] wxcam compile errors on Slackware 15.0
In-Reply-To: <1da08a15-c65e-aa07-f0ec-749f73ac8fba@gmail.com>
References: <220c73bc-d566-de3e-4c78-8352ce3bc4f4@gmail.com>
 <4b471c66-2b9e-b6ae-2af4-a81e3b1f7779@slackbuilds.org>
 <ff5c136d-380b-c049-a0ac-fda0dfd623e3@gmail.com>
 <CAN1hMuCDA79_TfbzrTb2sJ8BH_Kr8BBSt7PsTL+goK3-UyUYcg@mail.gmail.com>
 <1da08a15-c65e-aa07-f0ec-749f73ac8fba@gmail.com>
Message-ID: <CAN1hMuD_dO1foZToDt4T8vkihRqgd-cxwSgaObAPgZkXfwVtSA@mail.gmail.com>

On 2/7/22, King Beowulf <kingbeowulf at gmail.com> wrote:
>
> Thanks, that'll be spiffy.  All my other stuff is wxGTK3, so usually not
> an issue there.  Only wxcam needs the older wxPython. pain in the rump
> to keep track. If you could tweak wxcam so I can see how it's done
> that'd be great.

For wxcam, it was dead simple. I just added this ./configure argument:

--with-wx-config=/usr/lib$LIBDIRSUFFIX/wx/config/gtk2-unicode-release-2.8

Not everything is so obliging (sometimes it's a PITA to get it to use
the right path).

I pushed this to my git branch, so no need for you to mess with it
yourself.

From ozan.turkyilmaz at gmail.com  Tue Feb  8 05:31:05 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 8 Feb 2022 08:31:05 +0300
Subject: [Slackbuilds-users] keepassx compile errors on 15.0
In-Reply-To: <CAC5LoF01=zi7XnC-8mgJQUPBk9p2Bzj_K5WG=dnzeNjpepWYoA@mail.gmail.com>
References: <CAC5LoF1--47PB6wndtdpTEnJGbyRSpjjtnyLAW46kghq0chJYQ@mail.gmail.com>
 <CAN1hMuAQ=1YywrV2d6XjzeR+=5wE4=qO0=9cwunRVTEQH=ofhQ@mail.gmail.com>
 <CAC5LoF01=zi7XnC-8mgJQUPBk9p2Bzj_K5WG=dnzeNjpepWYoA@mail.gmail.com>
Message-ID: <CA+da1or-b+MCWvB-6WUUHkXA+bNkjPMAnd23kV5=VAUdPBF1tw@mail.gmail.com>

Michel BEGUE <mab974 at gmail.com>, 7 ?ub 2022 Pzt, 21:47 tarihinde ?unu yazd?:

>
> Le lun. 7 f?vr. 2022 ? 20:18, B Watson <yalhcru at gmail.com> a ?crit :
>
>> On 2/6/22, Michel BEGUE <mab974 at gmail.com> wrote:
>>
>> > Current version still requires Qt 4.x.
>> > and keepassx has its development stopped on december 2021.
>> > So I think we have to drop it.
>>
>> We have qt4 for 15.0 now. I just tested it: if qt4 is installed,
>> keepassx.SlackBuild finds it without any modifications.
>>
>> So all that's needed is to put REQUIRES="qt4" in keepassx.info (which
>> I've done in my git branch, so no need for you to do it).
>>
>> Dec 2021 wasn't that long ago. Is the software still useful?
>>
>>
> We can do that for now.
>
> On their site we are advised to switch to keepassxc. This many users have
> already done. Even me on my main installation.
>

Not really my place to butt in. HOwever we should state that in the README.
Maybe even add a link to a mitigation path.

Regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/51f4da30/attachment.htm>

From ozan.turkyilmaz at gmail.com  Tue Feb  8 05:48:03 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 8 Feb 2022 08:48:03 +0300
Subject: [Slackbuilds-users] [PATCH] Chatbot-Eliza: Updated to 1.08.
 Added license to the script with approval of original author.
In-Reply-To: <a469e59d-8fbb-0770-4f49-3089009db5b6@slackbuilds.org>
References: <20220207080220.12145-1-ozan.turkyilmaz@gmail.com>
 <a469e59d-8fbb-0770-4f49-3089009db5b6@slackbuilds.org>
Message-ID: <CA+da1oppqDqoF5HFmnmUzoDUP1ncBd+FVG+TwPnmzDmdtaDa1Q@mail.gmail.com>

Willy Sudiarto Raharjo <willysr at slackbuilds.org>, 7 ?ub 2022 Pzt, 20:03
tarihinde ?unu yazd?:

> Can you send in a patch format as attachment?
>
>
Here you go.

REgards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/6b02b991/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Chatbot-Eliza-Updated-to-1.08.-Added-license-to-the-.patch
Type: application/octet-stream
Size: 3167 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/6b02b991/attachment.obj>

From ozan.turkyilmaz at gmail.com  Tue Feb  8 06:24:41 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 8 Feb 2022 09:24:41 +0300
Subject: [Slackbuilds-users] kildclient
Message-ID: <CA+da1oq9h+LL8ePbfu+u_Er4u6P+kaWDYFbsX4zWRdXY-ubf1A@mail.gmail.com>

Hey All,

Patch for kildclient is here. I updated the version and added a new
dependency (gtkspell3) and removed perl-JSON dependency.

Regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/fe9c4a31/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-kildclient-Version-updated.-Added-new-dependency-for.patch
Type: application/octet-stream
Size: 1593 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/fe9c4a31/attachment-0001.obj>

From slackbuilds at schoepfer.info  Tue Feb  8 07:01:23 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 08 Feb 2022 08:01:23 +0100
Subject: [Slackbuilds-users] freealut patch .la-files
Message-ID: <5d6388752f97fae9d04fe22294607de2@schoepfer.info>

Hi,

not my buildscript, i made a patch anyway to remove the .la file from 
/usr/lib${LIBDIRSUFFIX}.

Are there plans to update the templates with something like this(what 
Pat does)?:
# Don't ship .la files:
rm -f $PKG/usr/lib${LIBDIRSUFFIX}/*.la

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: freealut.patch
Type: text/x-diff
Size: 1075 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/9a9f98c3/attachment.bin>

From ozan.turkyilmaz at gmail.com  Tue Feb  8 11:01:01 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 8 Feb 2022 14:01:01 +0300
Subject: [Slackbuilds-users] Mkvtoolnix Patch
Message-ID: <CA+da1opanwzm6tbMEcTHzbf-7dkLhoptW1DxVtCchXRx5kGQdA@mail.gmail.com>

Hey All,

I updated mkvtoolnix to 65.0.0 and changed the script a little bit. Patch
is attached.

Regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/7850be24/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-mkvtoolnix-Updated-to-65.0.0.-Made-GUI-build-by-defa.patch
Type: application/octet-stream
Size: 2565 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/7850be24/attachment.obj>

From ozan.turkyilmaz at gmail.com  Tue Feb  8 11:42:20 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 8 Feb 2022 14:42:20 +0300
Subject: [Slackbuilds-users] Libebml Patch
Message-ID: <CA+da1opmajDwkbOoOzuq3dT9oSa7v0Ygc0d21gfxH6tSj0=dBg@mail.gmail.com>

Hey All,
I updated to 1.4.2. Again needed an upstream patch to compile. Also, it
builds a static library only now.

Regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/3aa52edb/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-libebml-Updated-to-1.4.2.-Added-new-patch.-Updated-R.patch
Type: application/octet-stream
Size: 4296 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/3aa52edb/attachment.obj>

From ozan.turkyilmaz at gmail.com  Tue Feb  8 12:04:41 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 8 Feb 2022 15:04:41 +0300
Subject: [Slackbuilds-users] libmatroska patch
Message-ID: <CA+da1or_spDY6q1O9U+NdiL1bZni2FmNoRsQ1yrKQikAntMNFA@mail.gmail.com>

Hey All,

libmatroska is here. Version updated to 1.6.3. Patch is attached.
They moved to cmake as a build system and I updated the build script
accordingly.
Also it only builds a static library now. I know VLC and mkclean depend on
it.
Heads up.

Regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/f23d055b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-libmatroska-UPdated-to-1.6.3.-Build-system-changed-t.patch
Type: application/octet-stream
Size: 2910 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220208/f23d055b/attachment.obj>

From slackph at posteo.de  Tue Feb  8 13:26:15 2022
From: slackph at posteo.de (Philip Lacroix)
Date: Tue, 08 Feb 2022 13:26:15 +0000
Subject: [Slackbuilds-users] =?utf-8?q?Dropping_system/srm_=3F?=
Message-ID: <70dca4ed612713628fc6cc4c6f718d3b@posteo.de>

Hi

I'm currently the maintainer of the system/srm SlackBuild.

I wonder if dropping it from the 15.0 repo altogether might be
a good idea. It doesn't support most journaled file systems,
for example, and is unmaintained since 2015.

What do you suggest? Anyone still using it?

Cheers,
Philip

From arabusov at gmail.com  Tue Feb  8 21:03:29 2022
From: arabusov at gmail.com (Andrei Rabusov)
Date: Tue, 8 Feb 2022 22:03:29 +0100
Subject: [Slackbuilds-users] academic/root switch to cmake
Message-ID: <YgLaoXN7kOazOXde@r2-d2.localdomain>

Dear SBo users and maintainers,

I've prepared an update for the academic/root slackbuild. The
corresponding pull request is on github
(https://github.com/SlackBuildsOrg/slackbuilds/pull/1173). It works for
me, but last time when Ponce tried to run it there was a compile error
which I couldn't reproduce. Please, double-check my script, maybe I
missed something obvious (I'm relatively new in the Slackware world).

Best regards
Andrei

From christopher.duston at protonmail.com  Wed Feb  9 01:57:15 2022
From: christopher.duston at protonmail.com (Christopher L Duston)
Date: Wed, 09 Feb 2022 01:57:15 +0000
Subject: [Slackbuilds-users] [SlackBuildsOrg/slackbuilds]
 academic/sage-bin: Updated for version 9.4 (PR #1160)
In-Reply-To: <Yf9smYNLs5wtatuQ@slk1.local.net>
References: <Yf9smYNLs5wtatuQ@slk1.local.net>
Message-ID: <5RKvGzhkvN66ztlQ_2xK7_rlX8bC4qG8js26kgBuwMLNWaZUmR6frvqI7cBUJXlc8xOb2IdYNc3nWZKV6B3fLm-zQt_TWzNxoWEvJZhM_yc=@protonmail.com>

I have a question here - we have build packages for both sage (maintained by me, built from source and takes forever) and sage-bin (repackaged binary, presumably installs nearly instantly), both now updated to 9.4. Is there an obvious reason why one of these should continue and the other should not? Or is it of maximum benefit to have both?

I do have a second question - I've checked 9.4 on Slackware 15 and it installs fine, so no changes needed from 14.2 (github currently shows the 9.4 version). Do I need to submit patches for 15.0, or will it be included automatically?

Thanks.

CLD

Sent with ProtonMail Secure Email.

------- Original Message -------

On Sunday, February 6th, 2022 at 1:37 AM, Duncan Roe <duncan_roe at optusnet.com.au> wrote:

> Hi Willy,
>
> On Sat, Feb 05, 2022 at 10:03:11PM -0800, Willy Sudiarto Raharjo wrote:
>
> > Hi @duncan-roe is it possible to put the tar_xz files outside of the repository and put it in the .info files?
>
> debian_binaries-11.2.tar_xz is <2K so not worth worrying about I'd suggest.
>
> debian_libraries-11.2.tar_xz at 270K would add 25% to the repo size so
>
> can we put it in the repo you have for big files? Then I could list it
>
> on the DOWNLOAD line.
>
> Cheers ... Duncan.
>
> 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 sbo at linuxgalaxy.org  Wed Feb  9 04:36:03 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Wed, 09 Feb 2022 04:36:03 +0000
Subject: [Slackbuilds-users] new email - mumble 1.4 overlay issues
Message-ID: <4635e814-0eb6-2a8b-8046-6921f5799118@linuxgalaxy.org>

1.
Kingbeowulf has a new email for this list, so hopefully I was able to
follow the instructions!  List emails are coming in.

2.
I was hoping to update mumble/murmur to 1.4.0 for Slackware 15.0.
Upstream switched to cmake from qmake (yay!) but then did something weird.

Unlike mumble-1.3.4, it is not possible to build the overlay on
Slackware64 without multilib.  I've posted this issue on github.
Essentially,

Slackware32 - optional overlay.
Slackware64 - no overlay.
Slackware64 multilib - optional both 64- AND 32-bit overlay.

Seems kinda silly, and I don't have the energy to fix it.  I'm running
mumble/murmur-1.3.4 on Slackware64 15.0 (multilib and pure) just fine
with and without 32-bit overlay as appropriate - although I haven't
fully tested that functionality.

I'll push my branch up with what I have so far later this week.

I guess all those other distros are going multlib because there aren't
any 64-bit Linux games. Which is weird since many of mine are.

-kb,



From ozan.turkyilmaz at gmail.com  Wed Feb  9 06:57:04 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Wed, 9 Feb 2022 09:57:04 +0300
Subject: [Slackbuilds-users] Liboop patch
Message-ID: <CA+da1oqd6+4AEqHFxCFZKf53VTQ-mpvRPEg6dDrH08GW_wywoQ@mail.gmail.com>

Hey All,
THe patch for liboop is here. We dont ship *.la files anymore.

regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220209/a33d6277/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-liboop-Dont-ship-.la-files.patch
Type: application/octet-stream
Size: 866 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220209/a33d6277/attachment.obj>

From ozan.turkyilmaz at gmail.com  Wed Feb  9 07:18:32 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Wed, 9 Feb 2022 10:18:32 +0300
Subject: [Slackbuilds-users] libupnp version update
Message-ID: <CA+da1ooP=qHtP2o=0g-VC0XudutWMPo-u=DKAou2U+F+QV5W6g@mail.gmail.com>

Hey All,

here's the patch for libupnp: version update and dont ship *.la files.
I would like to hear OK from vlc and openclonk maintainers. Upnp burned us
one.

Regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220209/f9d1b4d8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-libupnp-UPdated-to-1.14.12.-Dont-ship-.la-files.patch
Type: application/octet-stream
Size: 2220 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220209/f9d1b4d8/attachment.obj>

From mab974 at gmail.com  Wed Feb  9 13:46:05 2022
From: mab974 at gmail.com (Michel BEGUE)
Date: Wed, 9 Feb 2022 17:46:05 +0400
Subject: [Slackbuilds-users] Locale::Language missing
Message-ID: <CAC5LoF0hABoVumd+FGzT33cfbMQw=6=5iSX2eChKyXRRXLaUcQ@mail.gmail.com>

It seems that 'Locale::Language' is no longer part of perl 5.34.
I need it for gscan2pdf. Shall I build perl-Locale-Codes ? does it exist
elsewhere ?
Regards.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220209/83aab5d9/attachment.htm>

From erich.public at protonmail.com  Wed Feb  9 16:36:27 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Wed, 09 Feb 2022 16:36:27 +0000
Subject: [Slackbuilds-users] games/puzzles: Upstream deletes old archives
Message-ID: <wtWPZp8ktpcg5o2wOj509hvr3DhcX_HVhpg1ppAi47PqsDCESFNSupkrgPHFk-UdmwU008SSyMHUDz9RucU3U1ErxrB_aSDWfkPb1VSaReo=@protonmail.com>

Hello list,

I just took over maintainership of games/puzzles and realized that upstream deletes old source archives.? I added a note in the README pointing to slackware.uk/sbosrcarch/ and also added automatic version detection (similar to what JOSM does) to the SlackBuild so the user can optionally download the latest source code from upstream and build.

My merge request is here: https://gitlab.com/SlackBuilds.org/slackbuilds/-/merge_requests/227/diffs?commit_id=32f406a868d44c710763a95613c78bd9b5362e9a
for you to review changes.

If I should do anything differently, please let me know.

I chose to keep the versioned download link in puzzles.info so users will know right away, rather than using the un-versioned download link and then getting a mismatched MD5SUM.

Erich

From yalhcru at gmail.com  Wed Feb  9 17:22:50 2022
From: yalhcru at gmail.com (B Watson)
Date: Wed, 9 Feb 2022 12:22:50 -0500
Subject: [Slackbuilds-users] Locale::Language missing
In-Reply-To: <CAC5LoF0hABoVumd+FGzT33cfbMQw=6=5iSX2eChKyXRRXLaUcQ@mail.gmail.com>
References: <CAC5LoF0hABoVumd+FGzT33cfbMQw=6=5iSX2eChKyXRRXLaUcQ@mail.gmail.com>
Message-ID: <CAN1hMuAH17SRD-B-QpYL7nY4e7iDfg_1y_gx+zZFzzr66fmhkg@mail.gmail.com>

On 2/9/22, Michel BEGUE <mab974 at gmail.com> wrote:
> It seems that 'Locale::Language' is no longer part of perl 5.34.
> I need it for gscan2pdf. Shall I build perl-Locale-Codes ? does it exist
> elsewhere ?
> Regards.
>

This looks like it:

https://metacpan.org/dist/Locale-Codes/view/lib/Locale/Language.pod

Should be no problem for you to create a SlackBuild for it.

From artourter at gmail.com  Wed Feb  9 21:45:09 2022
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Wed, 9 Feb 2022 21:45:09 +0000
Subject: [Slackbuilds-users] qtcurve
Message-ID: <CAK09-vnLTLYSvGL+CKnZe9zjpqxX+HUMyNG+xU-ixkbpwuQUZg@mail.gmail.com>

Hi,

I see that qtcurve has been removed from the git master for it requiring
KD4. I have been able to compile the latest master with QT5 and KF5 support
from upstream git repo on -15.0 *but*:
- I don't actually use it anymore
- there is no GTK-3 version of the theme

The lack of GTK-3 support is very much what made me stop using it since the
whole point for me at the time was the uniform look across applications.

If someone wants to take over they are welcome, I can share my script to
make it compile on -15.0 as a starting point. Otherwise we can leave it in
the removed pile but I thought I'd let the list know.

Cheers

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

From gerardo.zamudio at linux.com  Wed Feb  9 23:45:11 2022
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Wed, 09 Feb 2022 17:45:11 -0600
Subject: [Slackbuilds-users] new email - mumble 1.4 overlay issues
In-Reply-To: <4635e814-0eb6-2a8b-8046-6921f5799118@linuxgalaxy.org>
References: <4635e814-0eb6-2a8b-8046-6921f5799118@linuxgalaxy.org>
Message-ID: <7ad6a11fefd01f651936ecc864540c74@linux.com>

On 2022-02-08 10:36 pm, Slackbuilds wrote:
> 1.
> Kingbeowulf has a new email for this list, so hopefully I was able to
> follow the instructions!  List emails are coming in.
> 
> 2.
> I was hoping to update mumble/murmur to 1.4.0 for Slackware 15.0.
> Upstream switched to cmake from qmake (yay!) but then did something 
> weird.
> 
> Unlike mumble-1.3.4, it is not possible to build the overlay on
> Slackware64 without multilib.  I've posted this issue on github.
> Essentially,
> 
> Slackware32 - optional overlay.
> Slackware64 - no overlay.
> Slackware64 multilib - optional both 64- AND 32-bit overlay.
> 
> Seems kinda silly, and I don't have the energy to fix it.  I'm running
> mumble/murmur-1.3.4 on Slackware64 15.0 (multilib and pure) just fine
> with and without 32-bit overlay as appropriate - although I haven't
> fully tested that functionality.
> 
> I'll push my branch up with what I have so far later this week.
> 
> I guess all those other distros are going multlib because there aren't
> any 64-bit Linux games. Which is weird since many of mine are.
> 
> -kb,
> 

Thanks for your efforts! Eagerly awaiting your update. I use your 
SlackBuild for Mumble and I am planning to run Slackware64 15.0 multilib 
(isn't multilib required by Steam and a lot of games anyway?).

From willysr at slackbuilds.org  Thu Feb 10 01:37:13 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 10 Feb 2022 08:37:13 +0700
Subject: [Slackbuilds-users] [PATCH] Chatbot-Eliza: Updated to 1.08.
 Added license to the script with approval of original author.
In-Reply-To: <CA+da1oppqDqoF5HFmnmUzoDUP1ncBd+FVG+TwPnmzDmdtaDa1Q@mail.gmail.com>
References: <20220207080220.12145-1-ozan.turkyilmaz@gmail.com>
 <a469e59d-8fbb-0770-4f49-3089009db5b6@slackbuilds.org>
 <CA+da1oppqDqoF5HFmnmUzoDUP1ncBd+FVG+TwPnmzDmdtaDa1Q@mail.gmail.com>
Message-ID: <3365e8bc-74ec-a8b0-e1ce-6d66812f51a4@slackbuilds.org>

> Here you go.

Thanks
pushed to my branch


-- 
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/20220210/d67d2afb/attachment.asc>

From willysr at slackbuilds.org  Thu Feb 10 01:38:55 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 10 Feb 2022 08:38:55 +0700
Subject: [Slackbuilds-users] kildclient
In-Reply-To: <CA+da1oq9h+LL8ePbfu+u_Er4u6P+kaWDYFbsX4zWRdXY-ubf1A@mail.gmail.com>
References: <CA+da1oq9h+LL8ePbfu+u_Er4u6P+kaWDYFbsX4zWRdXY-ubf1A@mail.gmail.com>
Message-ID: <9440f78e-7ed0-3ae5-d002-ab2e805aeb27@slackbuilds.org>

> Patch for kildclient is here. I updated the version and added a new
> dependency (gtkspell3) and removed perl-JSON dependency.

Thanks
pushed to my branch


-- 
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/20220210/213db138/attachment.asc>

From willysr at slackbuilds.org  Thu Feb 10 01:41:20 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 10 Feb 2022 08:41:20 +0700
Subject: [Slackbuilds-users] freealut patch .la-files
In-Reply-To: <5d6388752f97fae9d04fe22294607de2@schoepfer.info>
References: <5d6388752f97fae9d04fe22294607de2@schoepfer.info>
Message-ID: <82618ae4-3186-1fbe-f73c-3fea086852f9@slackbuilds.org>

> not my buildscript, i made a patch anyway to remove the .la file from
> /usr/lib${LIBDIRSUFFIX}.

Thanks, pushed to my branch

> Are there plans to update the templates with something like this(what
> Pat does)?:
> # Don't ship .la files:
> rm -f $PKG/usr/lib${LIBDIRSUFFIX}/*.la

it has been updated but still in master branch, not yet in 15.0 branch
nor the website
You can see it here:
https://git.slackbuilds.org/templates/tree/


-- 
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/20220210/f720a0b1/attachment.asc>

From sbo at linuxgalaxy.org  Thu Feb 10 02:13:00 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Thu, 10 Feb 2022 02:13:00 +0000
Subject: [Slackbuilds-users] new email - mumble 1.4 overlay issues
In-Reply-To: <7ad6a11fefd01f651936ecc864540c74@linux.com>
References: <4635e814-0eb6-2a8b-8046-6921f5799118@linuxgalaxy.org>
 <7ad6a11fefd01f651936ecc864540c74@linux.com>
Message-ID: <622f37c7-0941-08f8-495b-ae1c517e62c0@linuxgalaxy.org>

On 2/9/22 15:45, Gerardo Zamudio wrote:
> On 2022-02-08 10:36 pm, Slackbuilds wrote:
...
>> Unlike mumble-1.3.4, it is not possible to build the overlay on
>> Slackware64 without multilib.  I've posted this issue on github.
>>
...
> Thanks for your efforts! Eagerly awaiting your update. I use your
> SlackBuild for Mumble and I am planning to run Slackware64 15.0 multilib
> (isn't multilib required by Steam and a lot of games anyway?).

Thanks!  We always enjoy hearing that people use our scripts.

As for the overlay issue, it was a stupid typographical error. Toggling
32-bit overlay for Slackware64 works.

Yes, Steam needs 32-bit libs, as do a lot of games on that platform.
There are also quite a few linux native 64-bit games that do require
Steam, quite a few of which are on SBo!

-kb





From willysr at slackbuilds.org  Thu Feb 10 02:15:27 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 10 Feb 2022 09:15:27 +0700
Subject: [Slackbuilds-users] Dropping system/srm ?
In-Reply-To: <70dca4ed612713628fc6cc4c6f718d3b@posteo.de>
References: <70dca4ed612713628fc6cc4c6f718d3b@posteo.de>
Message-ID: <eff899e0-526a-5259-daf8-7943b96e51bf@slackbuilds.org>

> I'm currently the maintainer of the system/srm SlackBuild.
> 
> I wonder if dropping it from the 15.0 repo altogether might be
> a good idea. It doesn't support most journaled file systems,
> for example, and is unmaintained since 2015.
> 
> What do you suggest? Anyone still using it?

If upstream no longer maintains it and lacking features we need, i would
suggest to drop it as well.


-- 
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/20220210/55482e6b/attachment-0001.asc>

From willysr at slackbuilds.org  Thu Feb 10 02:17:19 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 10 Feb 2022 09:17:19 +0700
Subject: [Slackbuilds-users] [SlackBuildsOrg/slackbuilds]
 academic/sage-bin: Updated for version 9.4 (PR #1160)
In-Reply-To: <5RKvGzhkvN66ztlQ_2xK7_rlX8bC4qG8js26kgBuwMLNWaZUmR6frvqI7cBUJXlc8xOb2IdYNc3nWZKV6B3fLm-zQt_TWzNxoWEvJZhM_yc=@protonmail.com>
References: <Yf9smYNLs5wtatuQ@slk1.local.net>
 <5RKvGzhkvN66ztlQ_2xK7_rlX8bC4qG8js26kgBuwMLNWaZUmR6frvqI7cBUJXlc8xOb2IdYNc3nWZKV6B3fLm-zQt_TWzNxoWEvJZhM_yc=@protonmail.com>
Message-ID: <f605b781-0db6-3509-6438-882102c955d0@slackbuilds.org>

> I have a question here - we have build packages for both sage (maintained by me, built from source and takes forever) and sage-bin (repackaged binary, presumably installs nearly instantly), both now updated to 9.4. Is there an obvious reason why one of these should continue and the other should not? Or is it of maximum benefit to have both?
> 
> I do have a second question - I've checked 9.4 on Slackware 15 and it installs fine, so no changes needed from 14.2 (github currently shows the 9.4 version). Do I need to submit patches for 15.0, or will it be included automatically?

We give people to choose whether they want to build from source or use
the binary repacks, just like what we have with LibreOffice.

If you changes are pushed, the one we have in 14.2 will be used for 15.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/20220210/3c9a7cf4/attachment.asc>

From sbo at linuxgalaxy.org  Fri Feb 11 03:56:22 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Fri, 11 Feb 2022 03:56:22 +0000
Subject: [Slackbuilds-users] Mumble-1.4 murmur is know murmur-server
Message-ID: <e1e89dbc-b746-6475-fb71-21ff9accf53f@linuxgalaxy.org>

Admins,

I've got most of the kinks worked out and just need to finish testing.
Upstream renamed murmurd (mumble server) to, heh, mumble-server.  The
mumble client remains the same.  Thus, we'll need to remove the old
murmur slackbuild.

For the update, do I just push up my branch, or wait until SBo goes live
to get everything sorted?  We'll have to drop murmur and add mumble-server.

For the voip curious, you can grab them here:
https://www.linuxgalaxy.org/files/sbo-testing/15.0/

The [mumble | murmur]-1.3.4 pair currently in git master works fine on
15.0, so there's no rush.

-kb


From davidnchmelik at gmail.com  Fri Feb 11 07:44:10 2022
From: davidnchmelik at gmail.com (David Chmelik)
Date: Thu, 10 Feb 2022 23:44:10 -0800
Subject: [Slackbuilds-users] best way to mass-rebuild? (w/dependencies?)
Message-ID: <17b323c3-7ab5-48cc-1f3b-09585a37e7a4@gmail.com>

Last year or two on LinuxQuestions:Slackware I wrote a thread discussing 
package/build tools, added more ones to the topic, which ended up filled 
with more appearing since then.?? For SBo I almost only use sbopkg & 
sbotools but looked into others that largely seemed to do what the rest 
already do, but am interested in learning more about them anyway.
 ??? If I want to mass-rebuild all my installed packages in one go ('at 
once') including w/queues, what's the best way?? I thought it was 
sbotools, but depending what I used for end of package name (_SBo or 
ponce,) sbotools seemed to replace some newer versions (I upgraded and 
some perhaps reverted in SBo-git, unsure) with old ones.? For sbokpg it 
seems you have to figure out everything which does or doesn't need 
queues then (after running sqg) load all queues and non-dependent 
packages separately, which I don't really feel like getting into (since 
I use several hundred packages)...
 ??? The last several versions of Slackware I try to rebuild everything 
as soon as I can, to make sure packages I maintain build fine, but also 
in case I need to report any that no one else did yet (depending whether 
SBo staff is checking everything themselves.)
 ??? It seems mine build fine (I think I mass-rebuilt everything but 
have done a fresh installation afterwards) but I just want to make sure 
I rebuild everything (easier in sbotools) but don't have to another mass 
rebuild after that (seems sbotools can handle SBo-git except still only 
ends package names with SBo... but I'll be staying on SBo-git on some, 
not all PCs/servers... and I haven't seen sbotools people on IRC so 
don't know where to ask them to fix that.)
 ??? I also found some bugs in sbopkg.? If I check for & load updates, 
then start removing some from the queue after going down a page, sbopkg 
stops showing names below that then no longer can edit queue, maybe even 
have to exit.

From lists at osh.id.au  Fri Feb 11 08:02:43 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Fri, 11 Feb 2022 16:02:43 +0800
Subject: [Slackbuilds-users] best way to mass-rebuild? (w/dependencies?)
In-Reply-To: <17b323c3-7ab5-48cc-1f3b-09585a37e7a4@gmail.com>
References: <17b323c3-7ab5-48cc-1f3b-09585a37e7a4@gmail.com>
Message-ID: <12ae616f-0bb0-4c25-bb24-554185da42db@www.fastmail.com>

On Fri, 11 Feb 2022, at 3:44 PM, David Chmelik wrote:
>  ??? If I want to mass-rebuild all my installed packages in one go ('at 
> once') including w/queues, what's the best way?? I thought it was 
> sbotools, but depending what I used for end of package name (_SBo or 
> ponce,) sbotools seemed to replace some newer versions (I upgraded and 
> some perhaps reverted in SBo-git, unsure) with old ones.

One quick way:
sboupgrade -fz $(ls /var/log/packages/*_SBo | cut -d'/' -f5 | rev | cut -d- -f4- | rev)

But as you said, at present sbotools doesn't do any smart version checking, so it will offer version downgrades for things you've manually updated. That would be a nice patch for sbotools actually (no downgrades by default).

I'm not sure what the full solution could be if you have a mix of custom build stuff.

--
Dave

From erich.public at protonmail.com  Fri Feb 11 14:03:44 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Fri, 11 Feb 2022 14:03:44 +0000
Subject: [Slackbuilds-users] best way to mass-rebuild? (w/dependencies?)
In-Reply-To: <12ae616f-0bb0-4c25-bb24-554185da42db@www.fastmail.com>
References: <17b323c3-7ab5-48cc-1f3b-09585a37e7a4@gmail.com>
 <12ae616f-0bb0-4c25-bb24-554185da42db@www.fastmail.com>
Message-ID: <swe0N3m406HpLGR9CpidJtBMLPDg2BFIOb_326RhoRgB0vgvBX1ROyzNVv-3mR-BF22bXikgOghg0CALVtKyS8v02nebO29NNugljf0xR2Y=@protonmail.com>



------- Original Message -------

On Friday, February 11th, 2022 at 2:02 AM, David O'Shaughnessy <lists at osh.id.au> wrote:

> On Fri, 11 Feb 2022, at 3:44 PM, David Chmelik wrote:
>
> >      If I want to mass-rebuild all my installed packages in one go ('at
> >
> >
> > once') including w/queues, what's the best way? I thought it was
> >
> > sbotools, but depending what I used for end of package name (_SBo or
> >
> > ponce,) sbotools seemed to replace some newer versions (I upgraded and
> >
> > some perhaps reverted in SBo-git, unsure) with old ones.
>
> One quick way:
>
> sboupgrade -fz $(ls /var/log/packages/*_SBo | cut -d'/' -f5 | rev | cut -d- -f4- | rev)
>
> But as you said, at present sbotools doesn't do any smart version checking, so it will offer version downgrades for things you've manually updated. That would be a nice patch for sbotools actually (no downgrades by default).
>
> I'm not sure what the full solution could be if you have a mix of custom build stuff.
>

Too late now, but perhaps use a different TAG for custom-built stuff (e.g. SBo_custom)?  I admit I don't do this myself...

Erich

> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Dave
>


From k22 at trixtar.org  Fri Feb 11 14:28:39 2022
From: k22 at trixtar.org (k22 at trixtar.org)
Date: Fri, 11 Feb 2022 09:28:39 -0500
Subject: [Slackbuilds-users] greenhorn greetings
Message-ID: <20220211092839.3b87a6149fb3e13d54fbdb4a@trixtar.org>


My first time here, at soon 78 I've kicked the 
Slackware tires a few times but the recent 
systemd plague is making me take Slackware more
seriously :-)  I'm also tinkering with Artix
and Devuan in addition to my Suse go2 twins. 

Brought up on Suse I never had to learn very much
so this 'build' stuff is a bit of a learning-curve
as I have just installed 15.0 on both my Asus-g73
laptop and my AMD desktop.

I would like to ask 3 questions for starters if I
may:

- about when can I expect sbo packages for Sylpheed
  and Librewolf, the two most pressing ones?

- are those two avalaible for 14.2 and also usable 
  with 15.0?

- where can I look every now and then to see what
  has become available for 15.0?

TIA


-- 
https://i.imgur.com/Mjrw9Wm.png



From dpross1100 at msn.com  Fri Feb 11 15:13:37 2022
From: dpross1100 at msn.com (Daniel Prosser)
Date: Fri, 11 Feb 2022 10:13:37 -0500
Subject: [Slackbuilds-users] best way to mass-rebuild? (w/dependencies?)
In-Reply-To: <swe0N3m406HpLGR9CpidJtBMLPDg2BFIOb_326RhoRgB0vgvBX1ROyzNVv-3mR-BF22bXikgOghg0CALVtKyS8v02nebO29NNugljf0xR2Y=@protonmail.com>
References: <17b323c3-7ab5-48cc-1f3b-09585a37e7a4@gmail.com>
 <12ae616f-0bb0-4c25-bb24-554185da42db@www.fastmail.com>
 <swe0N3m406HpLGR9CpidJtBMLPDg2BFIOb_326RhoRgB0vgvBX1ROyzNVv-3mR-BF22bXikgOghg0CALVtKyS8v02nebO29NNugljf0xR2Y=@protonmail.com>
Message-ID: <SN6PR03MB3536F4A9DB4D54ADE48D130DCC309@SN6PR03MB3536.namprd03.prod.outlook.com>

There's no reliable way to compare versions, since different projects 
use completely different version numbering paradigms, and even a single 
project may switch paradigms. Imagine trying to compare version "3.0" of 
something with version "git1e8fr49cx". Which one is the later version? 
As you said, the best way is to use a different tag for custom-built 
stuff. Another option with sboui in particular is to blacklist 
custom-built packages.

Dan

On 2/11/22 09:03, Erich Ritz via SlackBuilds-users wrote:
>
> ------- Original Message -------
>
> On Friday, February 11th, 2022 at 2:02 AM, David O'Shaughnessy <lists at osh.id.au> wrote:
>
>> On Fri, 11 Feb 2022, at 3:44 PM, David Chmelik wrote:
>>
>>>       If I want to mass-rebuild all my installed packages in one go ('at
>>>
>>>
>>> once') including w/queues, what's the best way? I thought it was
>>>
>>> sbotools, but depending what I used for end of package name (_SBo or
>>>
>>> ponce,) sbotools seemed to replace some newer versions (I upgraded and
>>>
>>> some perhaps reverted in SBo-git, unsure) with old ones.
>> One quick way:
>>
>> sboupgrade -fz $(ls /var/log/packages/*_SBo | cut -d'/' -f5 | rev | cut -d- -f4- | rev)
>>
>> But as you said, at present sbotools doesn't do any smart version checking, so it will offer version downgrades for things you've manually updated. That would be a nice patch for sbotools actually (no downgrades by default).
>>
>> I'm not sure what the full solution could be if you have a mix of custom build stuff.
>>
> Too late now, but perhaps use a different TAG for custom-built stuff (e.g. SBo_custom)?  I admit I don't do this myself...
>
> Erich
>
>> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> 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/
>

From slackbuilds at schoepfer.info  Fri Feb 11 16:18:02 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 11 Feb 2022 17:18:02 +0100
Subject: [Slackbuilds-users] brasero patch, remove .la-files and update
Message-ID: <520b08e7ac8e43c2b3d284be4b38783e@schoepfer.info>

Hi,

not my buildscript, version 3.12.2 doesn't build here(fails at building 
the docs),
but 3.12.3 does build fine

BTW, Dimitris Zlatanidis last submission is from 2017, are his builds 
orphaned officially?

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: brasero.patch
Type: text/x-diff
Size: 2243 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220211/5dab9b12/attachment.bin>

From erich.public at protonmail.com  Fri Feb 11 16:50:30 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Fri, 11 Feb 2022 16:50:30 +0000
Subject: [Slackbuilds-users] greenhorn greetings
In-Reply-To: <20220211092839.3b87a6149fb3e13d54fbdb4a@trixtar.org>
References: <20220211092839.3b87a6149fb3e13d54fbdb4a@trixtar.org>
Message-ID: <ELGcP83zyCeEcSNBZOr44cpfr8inQWuRI1rjg8qPRMAbqFyoaYGDCboo-DyVdPchfQXSGRrDOXcQ3izTxbUx9aWk45kDqpxCj6Yd_xx7mZo=@protonmail.com>

On Friday, February 11th, 2022 at 8:28 AM, <k22 at trixtar.org> wrote:

> My first time here, at soon 78 I've kicked the
> Slackware tires a few times but the recent
> systemd plague is making me take Slackware more
> seriously :-) I'm also tinkering with Artix
> and Devuan in addition to my Suse go2 twins.
> Brought up on Suse I never had to learn very much
> so this 'build' stuff is a bit of a learning-curve
> as I have just installed 15.0 on both my Asus-g73
> laptop and my AMD desktop.
>

Welcome!

> I would like to ask 3 questions for starters if I
> may:
>
> -   about when can I expect sbo packages for Sylpheed
>     and Librewolf, the two most pressing ones?

Sylpheed is already on SBo.  Librewolf is not.  You can add it yourself after submissions open when the 15.0 branch of SBo goes live.  There is no TODO list: if something you want is not already on SBo you are encouraged to submit it and be the maintainer.  Note that submitting a new package comes with the expectation that you will maintain it.

> -   are those two avalaible for 14.2 and also usable
>     with 15.0?

Sylpheed, yes.  Librewolf, no.  But see next question:

> -   where can I look every now and then to see what
>     has become available for 15.0?

The 15.0 branch hasn't been released yet, but you can see the ongoing development in the master branch at:

https://git.slackbuilds.org/slackbuilds/

The 14.2 branch is available from the same website, or of course you may browse at https://slackbuilds.org/

Erich

>
>     TIA
>

From slackbuilds at schoepfer.info  Fri Feb 11 17:40:32 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 11 Feb 2022 18:40:32 +0100
Subject: [Slackbuilds-users] brasero patch, remove .la-files and update
In-Reply-To: <520b08e7ac8e43c2b3d284be4b38783e@schoepfer.info>
References: <520b08e7ac8e43c2b3d284be4b38783e@schoepfer.info>
Message-ID: <e8d77b8f3cb1bbd53dd3eaaf4ee638bf@schoepfer.info>

> BTW, Dimitris Zlatanidis last submission is from 2017, are his builds
> orphaned officially?

Sorry, i somehow didn't look in right path in den git-log, seems 
Dimitris is very present ;-)

From rasp at spitzner.org  Fri Feb 11 18:18:19 2022
From: rasp at spitzner.org (Ralph Spitzner)
Date: Fri, 11 Feb 2022 19:18:19 +0100
Subject: [Slackbuilds-users] Slackbuild cloning source from git
Message-ID: <1d1d697a-885c-964b-41a2-5ce98aaad2cf@spitzner.org>

Hi all,
would a Slackbuild cloning the source of the project from github stand any chance of
being accepted (couldn't find any info on this)
The project in turn uses 'subprojects' which get cloned from git recursively.
There's no tar.gz containing everything and installing the subprojects wouldn't make any sense
as they are only needed to build this and don't install anything themselves....


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

From fernando.lopezjr at gmail.com  Fri Feb 11 18:41:28 2022
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Fri, 11 Feb 2022 11:41:28 -0700
Subject: [Slackbuilds-users] Slackbuild cloning source from git
In-Reply-To: <1d1d697a-885c-964b-41a2-5ce98aaad2cf@spitzner.org>
References: <1d1d697a-885c-964b-41a2-5ce98aaad2cf@spitzner.org>
Message-ID: <CALrQ46BDCMh8mTJysyi1kyW0aL5rD5sn5byC5ebApvN_6yLajA@mail.gmail.com>

git clone git://git.slackbuilds.org/slackbuilds.git

On Fri, Feb 11, 2022 at 11:40 AM Ralph Spitzner <rasp at spitzner.org> wrote:

> Hi all,
> would a Slackbuild cloning the source of the project from github stand any
> chance of
> being accepted (couldn't find any info on this)
> The project in turn uses 'subprojects' which get cloned from git
> recursively.
> There's no tar.gz containing everything and installing the subprojects
> wouldn't make any sense
> as they are only needed to build this and don't install anything
> themselves....
>
>
> regards
>      -rasp
> --
> "ich brauche keine Verschluesselung, mich versteht eh keiner"  -Icke
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users 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/20220211/471289e4/attachment.htm>

From belka at caraus.de  Fri Feb 11 19:35:29 2022
From: belka at caraus.de (Eugen Wissner)
Date: Fri, 11 Feb 2022 20:35:29 +0100
Subject: [Slackbuilds-users] Slackbuild cloning source from git
In-Reply-To: <1d1d697a-885c-964b-41a2-5ce98aaad2cf@spitzner.org>
References: <1d1d697a-885c-964b-41a2-5ce98aaad2cf@spitzner.org>
Message-ID: <20220211193529.wh6dxvwg6my77abh@desktop.caraus.net>

No, the packages should build without an internet connection. Such
sources should be cloned recursively and uploaded somewhere as a tar
archive for example.

Regards
Eugene

On Fri, Feb 11, 2022 at 07:18:19PM +0100, Ralph Spitzner wrote:
> Hi all,
> would a Slackbuild cloning the source of the project from github stand any chance of
> being accepted (couldn't find any info on this)
> The project in turn uses 'subprojects' which get cloned from git recursively.
> There's no tar.gz containing everything and installing the subprojects wouldn't make any sense
> as they are only needed to build this and don't install anything themselves....
> 
> 
> regards
>     -rasp
> -- 
> "ich brauche keine Verschluesselung, mich versteht eh keiner"  -Icke
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users 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 erich.public at protonmail.com  Fri Feb 11 20:21:55 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Fri, 11 Feb 2022 20:21:55 +0000
Subject: [Slackbuilds-users] Slackbuild cloning source from git
In-Reply-To: <20220211193529.wh6dxvwg6my77abh@desktop.caraus.net>
References: <1d1d697a-885c-964b-41a2-5ce98aaad2cf@spitzner.org>
 <20220211193529.wh6dxvwg6my77abh@desktop.caraus.net>
Message-ID: <mPPjYXU4efchgOolUDfVGMYtKON_cy1VIr16AEM5STIZCDhEwvgNtyLsjHSHN6T17dBBT2rqLWqF2S6xSQLD9UhPhHjqhdhDIroSpXoMN08=@protonmail.com>



------- Original Message -------

On Friday, February 11th, 2022 at 1:33 PM, Eugen Wissner <belka at caraus.de> wrote:

> No, the packages should build without an internet connection. Such
>
> sources should be cloned recursively and uploaded somewhere as a tar
>
> archive for example.
>
> Regards
>
> Eugene
>
> On Fri, Feb 11, 2022 at 07:18:19PM +0100, Ralph Spitzner wrote:
>
> > Hi all,
> >
> > would a Slackbuild cloning the source of the project from github stand any chance of
> >
> > being accepted (couldn't find any info on this)
> >
> > The project in turn uses 'subprojects' which get cloned from git recursively.
> >
> > There's no tar.gz containing everything and installing the subprojects wouldn't make any sense
> >
> > as they are only needed to build this and don't install anything themselves....
> >
> > regards
> >
> > -rasp
> > --------------

You can specify multiple source downloads.  So you'd have the main project and all submodules as separate source downloads.  See for example
https://git.slackbuilds.org/slackbuilds/tree/system/system76-power/system76-power.info
All the dependencies are build-time only and get compiled statically into the final executable.

Note also in system76-power it's downloading one tarball from github based on a named tag, and another tarball based on commit ID.

And to answer your original question: No, a SlackBuild is not allowed to do any network activity.

Erich

From d.zlatanidis at gmail.com  Fri Feb 11 20:40:19 2022
From: d.zlatanidis at gmail.com (Dimitris Zlatanidis)
Date: Fri, 11 Feb 2022 22:40:19 +0200
Subject: [Slackbuilds-users] brasero patch, remove .la-files and update
In-Reply-To: <e8d77b8f3cb1bbd53dd3eaaf4ee638bf@schoepfer.info>
References: <520b08e7ac8e43c2b3d284be4b38783e@schoepfer.info>
 <e8d77b8f3cb1bbd53dd3eaaf4ee638bf@schoepfer.info>
Message-ID: <3e4f7b54-c320-1c19-d3dc-c06098383bb6@gmail.com>

Thanks Franzen,

It's time for update :)

On 2/11/22 19:40, Franzen via SlackBuilds-users wrote:
>> BTW, Dimitris Zlatanidis last submission is from 2017, are his builds
>> orphaned officially?
>
> Sorry, i somehow didn't look in right path in den git-log, seems 
> Dimitris is very present ;-)
> _______________________________________________
> 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/
>

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


From rasp at spitzner.org  Fri Feb 11 20:57:36 2022
From: rasp at spitzner.org (Ralph Spitzner)
Date: Fri, 11 Feb 2022 21:57:36 +0100
Subject: [Slackbuilds-users] Slackbuild cloning source from git
In-Reply-To: <mPPjYXU4efchgOolUDfVGMYtKON_cy1VIr16AEM5STIZCDhEwvgNtyLsjHSHN6T17dBBT2rqLWqF2S6xSQLD9UhPhHjqhdhDIroSpXoMN08=@protonmail.com>
References: <1d1d697a-885c-964b-41a2-5ce98aaad2cf@spitzner.org>
 <20220211193529.wh6dxvwg6my77abh@desktop.caraus.net>
 <mPPjYXU4efchgOolUDfVGMYtKON_cy1VIr16AEM5STIZCDhEwvgNtyLsjHSHN6T17dBBT2rqLWqF2S6xSQLD9UhPhHjqhdhDIroSpXoMN08=@protonmail.com>
Message-ID: <ff9636f7-06ac-04a6-e380-7a429d4e60ce@spitzner.org>



Erich Ritz wrote on 2/11/22 9:21 PM:

> And to answer your original question: No, a SlackBuild is not allowed to do any network activity.
> 
> Erich
> 

Ah, ok I'll tar it :-)
thanks, topic done


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

From jebrhansen+SBo at gmail.com  Fri Feb 11 22:48:25 2022
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Fri, 11 Feb 2022 15:48:25 -0700
Subject: [Slackbuilds-users] Slackbuild cloning source from git
In-Reply-To: <1d1d697a-885c-964b-41a2-5ce98aaad2cf@spitzner.org>
References: <1d1d697a-885c-964b-41a2-5ce98aaad2cf@spitzner.org>
Message-ID: <CANi9qSugvrv_NLzW1eFenN=-i-eSNT1Nxv-zPhVN5yg2vKHEig@mail.gmail.com>

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

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

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

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

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

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

Hopefully these examples will help.

Jeremy

On Fri, Feb 11, 2022, 11:40 AM Ralph Spitzner <rasp at spitzner.org> wrote:

> Hi all,
> would a Slackbuild cloning the source of the project from github stand any
> chance of
> being accepted (couldn't find any info on this)
> The project in turn uses 'subprojects' which get cloned from git
> recursively.
> There's no tar.gz containing everything and installing the subprojects
> wouldn't make any sense
> as they are only needed to build this and don't install anything
> themselves....
>
>
> regards
>      -rasp
> --
> "ich brauche keine Verschluesselung, mich versteht eh keiner"  -Icke
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users 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/20220211/2a9674e9/attachment.htm>

From willysr at slackbuilds.org  Sat Feb 12 01:42:49 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 12 Feb 2022 08:42:49 +0700
Subject: [Slackbuilds-users] brasero patch, remove .la-files and update
In-Reply-To: <520b08e7ac8e43c2b3d284be4b38783e@schoepfer.info>
References: <520b08e7ac8e43c2b3d284be4b38783e@schoepfer.info>
Message-ID: <102d5733-b842-f7f7-fd88-26712237bbbd@slackbuilds.org>

> not my buildscript, version 3.12.2 doesn't build here(fails at building
> the docs),
> but 3.12.3 does build fine

merged
thanks


-- 
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/20220212/542d7b32/attachment.asc>

From lists at osh.id.au  Sat Feb 12 03:05:56 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Sat, 12 Feb 2022 11:05:56 +0800
Subject: [Slackbuilds-users] greenhorn greetings
In-Reply-To: <20220211092839.3b87a6149fb3e13d54fbdb4a@trixtar.org>
References: <20220211092839.3b87a6149fb3e13d54fbdb4a@trixtar.org>
Message-ID: <31d06238-1069-4ff7-9649-b43fa60699ea@www.fastmail.com>

On Fri, 11 Feb 2022, at 10:28 PM, k22 at trixtar.org wrote:
> - about when can I expect sbo packages for Sylpheed
>   and Librewolf, the two most pressing ones?

Welcome to Slack :) This is a community run effort, so for anything eligible that's not on SBo yet (and Sylpheed already is), the answer to "When can I expect it to be available?" is "When you add it." :D It's actually not so hard, just some shell scripting.

As for finding/managing packages, you might like to take a look at some interfaces to SBo. A few popular ones are:

sbopkg https://sbopkg.org/
sbotools https://pink-mist.github.io/sbotools/
sboui https://github.com/montagdude/sboui

The repo for 15.0 will be out at some point not too far away.

--
Dave

From k22 at trixtar.org  Sat Feb 12 13:47:56 2022
From: k22 at trixtar.org (k22 at trixtar.org)
Date: Sat, 12 Feb 2022 08:47:56 -0500
Subject: [Slackbuilds-users] greenhorn greetings
In-Reply-To: <31d06238-1069-4ff7-9649-b43fa60699ea@www.fastmail.com>
References: <20220211092839.3b87a6149fb3e13d54fbdb4a@trixtar.org>
 <31d06238-1069-4ff7-9649-b43fa60699ea@www.fastmail.com>
Message-ID: <20220212084756.431380561c443bedbfbda452@trixtar.org>

On Sat, 12 Feb 2022 11:05:56 +0800
"David O'Shaughnessy" <lists at osh.id.au> wrote:

> Welcome to Slack :) This is a community run effort, so for anything eligible that's not on SBo yet (and Sylpheed already is), the answer to "When can I expect it to be available?" is "When you add it." :D It's actually not so hard, just some shell scripting.
> 
> As for finding/managing packages, you might like to take a look at some interfaces to SBo. A few popular ones are:
> 
> sbopkg https://sbopkg.org/
> sbotools https://pink-mist.github.io/sbotools/
> sboui https://github.com/montagdude/sboui
> 
> The repo for 15.0 will be out at some point not too far away.


Thank you very much, for now I'm totally swamped by these legion package-tools, having been spoiled rotten by Suse Yast :-) 


From nix at nixing.mx  Sat Feb 12 17:50:13 2022
From: nix at nixing.mx (Nix)
Date: Sat, 12 Feb 2022 17:50:13 +0000 (UTC)
Subject: [Slackbuilds-users] greenhorn greetings
In-Reply-To: <20220212084756.431380561c443bedbfbda452@trixtar.org>
References: <20220211092839.3b87a6149fb3e13d54fbdb4a@trixtar.org>
 <31d06238-1069-4ff7-9649-b43fa60699ea@www.fastmail.com>
 <20220212084756.431380561c443bedbfbda452@trixtar.org>
Message-ID: <4fdd6620-95f8-40de-b860-c06e2241c67e@nixing.mx>


>> the answer to "When can I expect it to be available?" is "When you add 
>> it." :D It's actually not so hard, just some shell scripting.

I've found that this is the usual response and I understand why, yet for 
new comers it can be overwhelming.

Again I understand and i'm eagerly waiting for slackbuilds to open it's 
doors for the slackware stable 15? so I can submit updates for libstrophe 
and profanity, and add new slackbuilds for its crypto support.

> Thank you very much, for now I'm totally swamped by these legion 
> package-tools, having been spoiled rotten by Suse Yast :-)

I've been in your shoes? (and probably still am). I created a write-up 
where I tried my best to explain the "confusing" parts of Slackware 
package management. That may be of help to get you started.

I'd suggest to not feel discouraged by the overwhelming feeling that can 
sometimes appear when trying to get into using Slackware. In my 
experience it's worth the slight learning curve.

Write-up: https://nixing.mx/posts/exploring-slackware-slackbuilds.html


Eric

From kingbeowulf at linuxgalaxy.org  Fri Feb  4 05:52:43 2022
From: kingbeowulf at linuxgalaxy.org (King Beowulf)
Date: Fri, 04 Feb 2022 05:52:43 +0000
Subject: [Slackbuilds-users] wxcam compile errors on Slackware 15.0
Message-ID: <4cU3QmcAp8FOpSnTuNeZ83QUo0MpSxYUDHclt-0sE1DCMHCo16GQ4S76GO-BVUsEASnf2hLS6T-RhkdXN3MNm524OHFW4Zjfu7LFZ72msP4=@linuxgalaxy.org>

Hello admins,

wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and hasn't been updated upstream since 2011.  Since I switched to guvcview, we can:

1. Drop it from SBo.
2. Put it up for grabs for someone to take over maintainership.

-Ed
--------------------------------------------------------
The true sign of intelligence is not knowledge but imagination. --Albert Einstein

From marek at modweb.de  Sun Feb 13 10:21:52 2022
From: marek at modweb.de (=?UTF-8?Q?Marek_=c5=a0rejma?=)
Date: Sun, 13 Feb 2022 11:21:52 +0100
Subject: [Slackbuilds-users] Dropping packages
Message-ID: <11cec4d1-9cbc-4fab-ca3e-4a0785f1c9b1@modweb.de>

Hi all,

here's a list of packages I'm maintaining, but having issues building on 
15.0, so I will no longer maintain them:

 ? cclive????????? (not using it; fails building on 15.0; last updated 2013)
 ? quvi??????????? (dependency for cclive only; builds on 15.0)
 ? libquvi???????? (dependency for quvi only; builds on 15.0)
 ? simpleburn????? (source pkg no longer available)
 ? roger-router??? (not using it; sources availabe as flatpack only)
 ? spandsp???????? (dependency for roger-router only; builds on 15.0)
 ? libcapi20?????? (dependency for roger-router only; builds on 15.0)


Marek

From yalhcru at gmail.com  Sun Feb 13 21:11:39 2022
From: yalhcru at gmail.com (B Watson)
Date: Sun, 13 Feb 2022 16:11:39 -0500
Subject: [Slackbuilds-users] wxcam compile errors on Slackware 15.0
In-Reply-To: <4cU3QmcAp8FOpSnTuNeZ83QUo0MpSxYUDHclt-0sE1DCMHCo16GQ4S76GO-BVUsEASnf2hLS6T-RhkdXN3MNm524OHFW4Zjfu7LFZ72msP4=@linuxgalaxy.org>
References: <4cU3QmcAp8FOpSnTuNeZ83QUo0MpSxYUDHclt-0sE1DCMHCo16GQ4S76GO-BVUsEASnf2hLS6T-RhkdXN3MNm524OHFW4Zjfu7LFZ72msP4=@linuxgalaxy.org>
Message-ID: <CAN1hMuCCQwPjFMUyuJyhP24cdRrznCPx8gKagARsepO7yZf67A@mail.gmail.com>

On 2/4/22, King Beowulf <kingbeowulf at linuxgalaxy.org> wrote:
> Hello admins,
>
> wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and
> hasn't been updated upstream since 2011.  Since I switched to guvcview, we
> can:
>
> 1. Drop it from SBo.
> 2. Put it up for grabs for someone to take over maintainership.

I'm feeling a strong sense of deja vu here...

From yalhcru at gmail.com  Sun Feb 13 21:16:29 2022
From: yalhcru at gmail.com (B Watson)
Date: Sun, 13 Feb 2022 16:16:29 -0500
Subject: [Slackbuilds-users] Dropping packages
In-Reply-To: <11cec4d1-9cbc-4fab-ca3e-4a0785f1c9b1@modweb.de>
References: <11cec4d1-9cbc-4fab-ca3e-4a0785f1c9b1@modweb.de>
Message-ID: <CAN1hMuA=VUyarMsB7m5WyFsKZnZV6N8ziLZZBCf9heHZQfUo6Q@mail.gmail.com>

On 2/13/22, Marek `rejma <marek at modweb.de> wrote:

>    simpleburn      (source pkg no longer available)

There's a copy of the source here:

https://slackware.uk/~urchlay/src/simpleburn-1.8.3.1.tar.gz

...and it's trivial to fix the compile (already done, in my local git
tree, so you don't have to mess with it).

That said, do you want to continue to maintain it?

From chris.willing at linux.com  Sun Feb 13 22:20:00 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Mon, 14 Feb 2022 08:20:00 +1000
Subject: [Slackbuilds-users] Changelog.txt
Message-ID: <451f37cf-8f2b-e26e-253c-0bc251c59494@linux.com>

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

From chris.willing at linux.com  Sun Feb 13 23:07:30 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Mon, 14 Feb 2022 09:07:30 +1000
Subject: [Slackbuilds-users] libupnp version update
In-Reply-To: <CA+da1ooP=qHtP2o=0g-VC0XudutWMPo-u=DKAou2U+F+QV5W6g@mail.gmail.com>
References: <CA+da1ooP=qHtP2o=0g-VC0XudutWMPo-u=DKAou2U+F+QV5W6g@mail.gmail.com>
Message-ID: <f2786ca5-788c-34aa-9d79-b50c5785b45b@linux.com>

On 9/2/22 17:18, Ozan T?rky?lmaz wrote:
> Hey All,
> 
> here's the patch for libupnp: version update and dont ship *.la files.
> I would like to hear OK from vlc and openclonk maintainers. Upnp burned
> us one.
> 

It has just burned us again and same for libmatroska. I've just had to
update the vlc SlackBuild to remove both libupnp and libmatroska from
the REQUIRES list since the new versions both break vlc compilation.

In future it would be much better if you could test your updates with
the SlackBuilds which depend on them _before_ submitting. It's better to
have late updates, rather than updates which break other SlackBuilds.

Sometimes that's not easy when there are many dependent packages to
check. However vlc seems to be the only SlackBuild with hard dependency
on libmatroska and libupnp's only hard dependencies were vlc &
openclonk, so I would say that checking your updates with so few
dependent SlackBuilds is not a big task to expect.


chris

From marek at modweb.de  Sun Feb 13 22:28:10 2022
From: marek at modweb.de (=?UTF-8?Q?Marek_=c5=a0rejma?=)
Date: Sun, 13 Feb 2022 23:28:10 +0100
Subject: [Slackbuilds-users] Dropping packages
In-Reply-To: <CAN1hMuA=VUyarMsB7m5WyFsKZnZV6N8ziLZZBCf9heHZQfUo6Q@mail.gmail.com>
References: <11cec4d1-9cbc-4fab-ca3e-4a0785f1c9b1@modweb.de>
 <CAN1hMuA=VUyarMsB7m5WyFsKZnZV6N8ziLZZBCf9heHZQfUo6Q@mail.gmail.com>
Message-ID: <03bdaa39-b2ab-91b0-f309-2d524f094de2@modweb.de>

> ?That said, do you want to continue to maintain it? 
Thanks, but no, I don't want to maintain it. I don't use it.


B Watson wrote:
> On 2/13/22, Marek `rejma <marek at modweb.de> wrote:
>
>>     simpleburn      (source pkg no longer available)
> There's a copy of the source here:
>
> https://slackware.uk/~urchlay/src/simpleburn-1.8.3.1.tar.gz
>
> ...and it's trivial to fix the compile (already done, in my local git
> tree, so you don't have to mess with it).
>
> That said, do you want to continue to maintain 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/
>


From sbo at linuxgalaxy.org  Mon Feb 14 04:12:49 2022
From: sbo at linuxgalaxy.org (Slackbuilds)
Date: Mon, 14 Feb 2022 04:12:49 +0000
Subject: [Slackbuilds-users] wxcam compile errors on Slackware 15.0
In-Reply-To: <CAN1hMuCCQwPjFMUyuJyhP24cdRrznCPx8gKagARsepO7yZf67A@mail.gmail.com>
References: <4cU3QmcAp8FOpSnTuNeZ83QUo0MpSxYUDHclt-0sE1DCMHCo16GQ4S76GO-BVUsEASnf2hLS6T-RhkdXN3MNm524OHFW4Zjfu7LFZ72msP4=@linuxgalaxy.org>
 <CAN1hMuCCQwPjFMUyuJyhP24cdRrznCPx8gKagARsepO7yZf67A@mail.gmail.com>
Message-ID: <c7eaeb2e-c70b-0187-e6f9-e6d7741ca34e@linuxgalaxy.org>

On 2/13/22 13:11, B Watson wrote:
> On 2/4/22, King Beowulf <kingbeowulf at linuxgalaxy.org> wrote:
>> Hello admins,
>>
>> wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and
>> hasn't been updated upstream since 2011.  Since I switched to guvcview, we
>> can:
>>
>> 1. Drop it from SBo.
>> 2. Put it up for grabs for someone to take over maintainership.
>
> I'm feeling a strong sense of deja vu here...

LOL. I had posted that from my new email instead of the old email
(gmail). I forgot to revoke it after I reposted from gmail. My bad.

There shouldn't be any more danglers now that I updated the list email.

-kb


From ozan.turkyilmaz at gmail.com  Mon Feb 14 06:29:52 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Mon, 14 Feb 2022 09:29:52 +0300
Subject: [Slackbuilds-users] libupnp version update
In-Reply-To: <f2786ca5-788c-34aa-9d79-b50c5785b45b@linux.com>
References: <CA+da1ooP=qHtP2o=0g-VC0XudutWMPo-u=DKAou2U+F+QV5W6g@mail.gmail.com>
 <f2786ca5-788c-34aa-9d79-b50c5785b45b@linux.com>
Message-ID: <CA+da1opvHRF0ZaQCf9DUx6MPuMu3kmyEKmhNi_nBb3gaqV_mSw@mail.gmail.com>

Christoph Willing <chris.willing at linux.com>, 14 ?ub 2022 Pzt, 02:09
tarihinde ?unu yazd?:

> On 9/2/22 17:18, Ozan T?rky?lmaz wrote:
> > Hey All,
> >
> > here's the patch for libupnp: version update and dont ship *.la files.
> > I would like to hear OK from vlc and openclonk maintainers. Upnp burned
> > us one.
> >
>
> It has just burned us again and same for libmatroska. I've just had to
> update the vlc SlackBuild to remove both libupnp and libmatroska from
> the REQUIRES list since the new versions both break vlc compilation.
>
>
Let me check which version VLC would work with libmatroska and libupnp.
I still want to give an update to both packages, also I don't want to break
any other package.
mkvtoolnix can use only internal libraries anyway and I'll update it to
that way.

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

From davidnchmelik at gmail.com  Mon Feb 14 06:36:20 2022
From: davidnchmelik at gmail.com (David Chmelik)
Date: Sun, 13 Feb 2022 22:36:20 -0800
Subject: [Slackbuilds-users] sbopkg: line 72: ./lbench-3.4-x86_64ponce:
 Permission denied
Message-ID: <47a0ad9a-5171-60c2-8333-5400c428ed0d@gmail.com>

When I run SBo-git sbopkg sync it says the below.
sbopkg: line 72: ./lbench-3.4-x86_64ponce: Permission denied


From dchmelik at gmail.com  Mon Feb 14 08:02:24 2022
From: dchmelik at gmail.com (David Chmelik)
Date: Mon, 14 Feb 2022 00:02:24 -0800
Subject: [Slackbuilds-users] some SlackBuilds can't handle MAKEFLAGS other
 than -j1
Message-ID: <d9db2262-9d43-2b45-873b-a75f188c6173@gmail.com>

Some SlackBuilds can't handle MAKEFLAGS other than -j1.? Is it possible 
in future sbopkg will let you set MAKEFLAGS for multiple threads, and if 
a script can't handle it, reset to one?

From rworkman at slackbuilds.org  Mon Feb 14 08:09:55 2022
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 14 Feb 2022 02:09:55 -0600
Subject: [Slackbuilds-users] some SlackBuilds can't handle MAKEFLAGS
 other than -j1
In-Reply-To: <d9db2262-9d43-2b45-873b-a75f188c6173@gmail.com>
References: <d9db2262-9d43-2b45-873b-a75f188c6173@gmail.com>
Message-ID: <20220214020955.28ce94eb@home.rlworkman.net>

On Mon, 14 Feb 2022 00:02:24 -0800
David Chmelik <dchmelik at gmail.com> wrote:

> Some SlackBuilds can't handle MAKEFLAGS other than -j1.? Is it
> possible in future sbopkg will let you set MAKEFLAGS for multiple
> threads, and if a script can't handle it, reset to one?


If we are aware of it, we (if I recall correctly) usually do something along those lines in the script itself, e.g. 
  make || MAKEFLAGS="" make

Future sbopkg features should probably be debated in a different venue, though -- while the developer is on SBo admin, sbopkg is not controlled by SBo.

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

From rworkman at slackbuilds.org  Mon Feb 14 08:11:29 2022
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 14 Feb 2022 02:11:29 -0600
Subject: [Slackbuilds-users] Changelog.txt
In-Reply-To: <451f37cf-8f2b-e26e-253c-0bc251c59494@linux.com>
References: <451f37cf-8f2b-e26e-253c-0bc251c59494@linux.com>
Message-ID: <20220214021129.3ba6b5aa@home.rlworkman.net>

On Mon, 14 Feb 2022 08:20:00 +1000
Christoph Willing <chris.willing at linux.com> wrote:

> Is the Changelog.txt still supposed to be updated?
> 
> I ask because I'm wondering whether lack of Changelog.txt updates
> might be connected with recent times when I've done 'git pull origin
> master', then being asked to add comment for a merge request. That's
> never happened before (for last few years of updating).
> 
> Now I notice that the most recent entry in the Changelog.txt is Sat
> Apr 17 04:48:35 UTC 2021, yet most recent entry in the git log was
> committed just recently 2022-02-13 09:18:03 +0700.
> 
> So I'm now wondering if these things are connected somehow?


If you get asked to do a merge commit, then something went wrong in your local git checkout. There's almost surely a way to fix it, but when that happens here (it's rare, but it *has* happened a few times in various git repos of which I keep local copies), I just kill the repo and re-clone it.

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

From erich.public at protonmail.com  Mon Feb 14 13:49:11 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Mon, 14 Feb 2022 13:49:11 +0000
Subject: [Slackbuilds-users] some SlackBuilds can't handle MAKEFLAGS
 other than -j1
In-Reply-To: <20220214020955.28ce94eb@home.rlworkman.net>
References: <d9db2262-9d43-2b45-873b-a75f188c6173@gmail.com>
 <20220214020955.28ce94eb@home.rlworkman.net>
Message-ID: <umtsHj0-b2t3Y6hbx059r6uDVDaP0vKhFZTjvk9hU9os7f7Eum3YLGf5ejOXWgZ5EJVHLg-_89I7-wDeBVyRoznd6VkN2UIyXmLCjpc3MZ4=@protonmail.com>

------- Original Message -------

On Monday, February 14th, 2022 at 2:09 AM, Robby Workman <rworkman at slackbuilds.org> wrote:

> On Mon, 14 Feb 2022 00:02:24 -0800
>
> David Chmelik dchmelik at gmail.com wrote:
>
> > Some SlackBuilds can't handle MAKEFLAGS other than -j1. Is it
> >
> > possible in future sbopkg will let you set MAKEFLAGS for multiple
> > threads, and if a script can't handle it, reset to one?
>
> If we are aware of it, we (if I recall correctly) usually do something along those lines in the script itself, e.g.
>
> make || MAKEFLAGS="" make
>
> Future sbopkg features should probably be debated in a different venue, though -- while the developer is on SBo admin, sbopkg is not controlled by SBo.
>
> -RW
>

Another thing you can do is set it in your queue file (*.sqf) (you are using queue files, right?):
# cat somepackage.sqf
@dep1
@dep2
somepackage | MAKEFLAGS="-j1"

This would avoid wasting time on a failed "make" in "make || MAKEFLAGS="" make".

Other tools (at least slackrepo) support something similar (i.e., setting variables for individual packages' SlackBuilds).

Erich

From dave at slackbuilds.org  Mon Feb 14 15:20:48 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Mon, 14 Feb 2022 15:20:48 +0000
Subject: [Slackbuilds-users] some SlackBuilds can't handle MAKEFLAGS
 other than -j1
In-Reply-To: <d9db2262-9d43-2b45-873b-a75f188c6173@gmail.com>
References: <d9db2262-9d43-2b45-873b-a75f188c6173@gmail.com>
Message-ID: <20220214152048.GE4508@localhost>

On 14/02/22 00:02,
David Chmelik <dchmelik at gmail.com> put forth the proposition:
> Some SlackBuilds can't handle MAKEFLAGS other than -j1.? Is it possible in
> future sbopkg will let you set MAKEFLAGS for multiple threads, and if a
> script can't handle it, reset to one?

You can set MAKEFLAGS in the options box for the application, where
you would usually put options specific to the build.

--
Dave

From dchmelik at gmail.com  Tue Feb 15 02:02:12 2022
From: dchmelik at gmail.com (David Chmelik)
Date: Mon, 14 Feb 2022 18:02:12 -0800
Subject: [Slackbuilds-users] lbench
Message-ID: <34c3bcd2-4d79-18e3-f9f7-b36389c343b1@gmail.com>

The lbench benchmark program is one SlackBuild that doesn't compile for 
me on Slackware 15 or 15+current from SBo-git.? Here's what it says

    lbench-3.7/Makefile
    g++ -O2 -fPIC -Wall -g -rdynamic -O0 -Wno-format-truncation -c
    `pkg-config --cflags gtk+-3.0`? -o lbench.o lbench-3.7.cc
    lbench-3.7.cc: In function ?void* matrix_thread(void*)?:
    lbench-3.7.cc:1424:23: warning: empty parentheses were disambiguated
    as a function declaration [-Wvexing-parse]
     ?1424 |??? int matrix_function();
     ????? |?????????????????????? ^~
    lbench-3.7.cc:1424:23: note: remove parentheses to
    default-initialize a variable
     ?1424 |??? int matrix_function();
     ????? |?????????????????????? ^~
     ????? |?????????????????????? --
    lbench-3.7.cc:1424:23: note: or replace parentheses with braces to
    value-initialize a variable
    lbench-3.7.cc: In function ?void* linpack_thread(void*)?:
    lbench-3.7.cc:2189:27: warning: empty parentheses were disambiguated
    as a function declaration [-Wvexing-parse]
     ?2189 |??? double linpack_function();
     ????? |?????????????????????????? ^~
    lbench-3.7.cc:2189:27: note: remove parentheses to
    default-initialize a variable
     ?2189 |??? double linpack_function();
     ????? |?????????????????????????? ^~
     ????? |?????????????????????????? --
    lbench-3.7.cc:2189:27: note: or replace parentheses with braces to
    value-initialize a variable
    g++ -O2 -fPIC -Wall -g -rdynamic -O0 -Wno-format-truncation -c
    `pkg-config --cflags gtk+-3.0` zfuncs.cc??? \
     ????????? -D PREFIX=\"/usr\" -D DOCDIR=\"/usr/doc/lbench-3.7\"
    zfuncs.cc: In function ?int zinitapp(const char*, const char*)?:
    zfuncs.cc:5001:9: warning: ?int ftime(timeb*)? is deprecated: Use
    gettimeofday or clock_gettime instead [-Wdeprecated-declarations]
     ?5001 | ftime(&startime); //? app startup time
     ????? |??? ~~~~~^~~~~~~~~~~
    In file included from zfuncs.h:24,
     ???????????????? from zfuncs.cc:23:
    /usr/include/sys/timeb.h:29:12: note: declared here
     ?? 29 | extern int ftime (struct timeb *__timebuf)
     ????? |??????????? ^~~~~
    zfuncs.cc: At global scope:
    zfuncs.cc:10935:6: error: ambiguating new declaration of ?void
    popup_report_timeout(zdialog*)?
    10935 | void popup_report_timeout(zdialog *zd)
     ????? |????? ^~~~~~~~~~~~~~~~~~~~
    zfuncs.cc:10921:8: note: old declaration ?int
    popup_report_timeout(zdialog*)?
    10921 |??? int popup_report_timeout(zdialog *zd);
     ????? |??????? ^~~~~~~~~~~~~~~~~~~~
    make: *** [Makefile:34: zfuncs.o] Error 1

 ??? I hope it will be updated but I also hope to see a version that 
works on X/TWM, not only Wayland/GNOME.? The lbench author told me GNOME 
might take up 1% or 2% CPU system resources, but for me, that's too 
much.? When I run benchmarks I turn off all but certain hardware & 
logging daemons... I guess because I'm more interested in mathematics 
than engineering, that I want an accurate benchmark--to five numerical 
places (as in science and professional engineering) not an approximation 
to 98%.
 ??? Does the maintainer use this listserv, and what do they or anyone 
think about that?



From yalhcru at gmail.com  Tue Feb 15 03:49:38 2022
From: yalhcru at gmail.com (B Watson)
Date: Mon, 14 Feb 2022 22:49:38 -0500
Subject: [Slackbuilds-users] lbench
In-Reply-To: <34c3bcd2-4d79-18e3-f9f7-b36389c343b1@gmail.com>
References: <34c3bcd2-4d79-18e3-f9f7-b36389c343b1@gmail.com>
Message-ID: <CAN1hMuC4AEKTthv2i2+QVvw3mCto9potzq=C7GX8ZzuSfXbDHw@mail.gmail.com>

On 2/14/22, David Chmelik <dchmelik at gmail.com> wrote:
> The lbench benchmark program is one SlackBuild that doesn't compile for
> me on Slackware 15 or 15+current from SBo-git.  Here's what it says

Do a "git pull" or re-clone. This has been fixed for a couple of days,
for 15.0.

For 15+current? I'm gonna stop you right there. We don't even have
everything working on actual 15.0. Just because Pat branched off a
new -current doesn't mean we can (or should) start trying support
it. So run it if you like, but please don't even mention it here on
this mailing list. It's not on our radar at all, and won't be until
sometime after we've got things working for 15.0 (including the
submisison form).

From alcibiades at iprimus.com.au  Tue Feb 15 06:41:57 2022
From: alcibiades at iprimus.com.au (Peter Schmiedgen)
Date: Tue, 15 Feb 2022 17:41:57 +1100
Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 190, Issue 19
In-Reply-To: <mailman.333.1644890542.13901.slackbuilds-users@slackbuilds.org>
 (slackbuilds-users-request@slackbuilds.org's message of "Tue, 15 Feb
 2022 02:02:22 +0000")
References: <mailman.333.1644890542.13901.slackbuilds-users@slackbuilds.org>
Message-ID: <874k50oclm.fsf@iprimus.com.au>

Hello!

From ozan.turkyilmaz at gmail.com  Tue Feb 15 07:39:18 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 15 Feb 2022 10:39:18 +0300
Subject: [Slackbuilds-users] Libebml Patch
In-Reply-To: <CA+da1opmajDwkbOoOzuq3dT9oSa7v0Ygc0d21gfxH6tSj0=dBg@mail.gmail.com>
References: <CA+da1opmajDwkbOoOzuq3dT9oSa7v0Ygc0d21gfxH6tSj0=dBg@mail.gmail.com>
Message-ID: <CA+da1oo7t0NmbAVkmtm2Ti5PJYM4QYR85ktmXH23mbfQjJrKUQ@mail.gmail.com>

Hey All,

I got the shared libs build now. I am attaching the patches now.

Regards,
Ozan

Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>, 8 ?ub 2022 Sal, 14:42
tarihinde ?unu yazd?:

> Hey All,
> I updated to 1.4.2. Again needed an upstream patch to compile. Also, it
> builds a static library only now.
>
> Regards,
> Ozan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/6465260f/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-libebml-Updated-to-1.4.2.-Added-new-patch.-Updated-R.patch
Type: application/octet-stream
Size: 4300 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/6465260f/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-libebml-Added-shared-lib-build-to-cmake.-Thanks-to-D.patch
Type: application/octet-stream
Size: 764 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/6465260f/attachment-0001.obj>

From ozan.turkyilmaz at gmail.com  Tue Feb 15 07:45:29 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 15 Feb 2022 10:45:29 +0300
Subject: [Slackbuilds-users] libmatroska patch
In-Reply-To: <CA+da1or_spDY6q1O9U+NdiL1bZni2FmNoRsQ1yrKQikAntMNFA@mail.gmail.com>
References: <CA+da1or_spDY6q1O9U+NdiL1bZni2FmNoRsQ1yrKQikAntMNFA@mail.gmail.com>
Message-ID: <CA+da1oogRMTEtcBjzowWY7Ge3yJLWPtgN0yqzrc4B00c0wQ_sg@mail.gmail.com>

Hello All,

I added shared libs to the build.

REgards,
Ozan

Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com>, 8 ?ub 2022 Sal, 15:04
tarihinde ?unu yazd?:

> Hey All,
>
> libmatroska is here. Version updated to 1.6.3. Patch is attached.
> They moved to cmake as a build system and I updated the build script
> accordingly.
> Also it only builds a static library now. I know VLC and mkclean depend on
> it.
> Heads up.
>
> Regards,
> Ozan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/d18845f4/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-libmatroska-UPdated-to-1.6.3.-Build-system-changed-t.patch
Type: application/octet-stream
Size: 2914 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/d18845f4/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-libmatroska-Added-shared-libs-to-the-script.-Thanks-.patch
Type: application/octet-stream
Size: 843 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/d18845f4/attachment-0003.obj>

From ozan.turkyilmaz at gmail.com  Tue Feb 15 08:23:01 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Tue, 15 Feb 2022 11:23:01 +0300
Subject: [Slackbuilds-users] libupnp version update
In-Reply-To: <CA+da1opvHRF0ZaQCf9DUx6MPuMu3kmyEKmhNi_nBb3gaqV_mSw@mail.gmail.com>
References: <CA+da1ooP=qHtP2o=0g-VC0XudutWMPo-u=DKAou2U+F+QV5W6g@mail.gmail.com>
 <f2786ca5-788c-34aa-9d79-b50c5785b45b@linux.com>
 <CA+da1opvHRF0ZaQCf9DUx6MPuMu3kmyEKmhNi_nBb3gaqV_mSw@mail.gmail.com>
Message-ID: <CA+da1oqu8ORyzwxQuOSjnFDbvTN31f65iggQ14gFBnussf3RKg@mail.gmail.com>

Hello Chris,

I tested libupnp 1.8.7 and vlc compiled fine here. Small version update
would work.
Also the latest patches I sent for libebml and libmatroska works for vlc.
(Im attaching them)

Regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/595f940e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-libebml-Added-shared-lib-build-to-cmake.-Thanks-to-D.patch
Type: application/octet-stream
Size: 764 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/595f940e/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-libmatroska-Added-shared-libs-to-the-script.-Thanks-.patch
Type: application/octet-stream
Size: 843 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/595f940e/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-libebml-Updated-to-1.4.2.-Added-new-patch.-Updated-R.patch
Type: application/octet-stream
Size: 4300 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/595f940e/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-libmatroska-UPdated-to-1.6.3.-Build-system-changed-t.patch
Type: application/octet-stream
Size: 2914 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/595f940e/attachment-0003.obj>

From chris.willing at linux.com  Wed Feb 16 03:41:31 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Wed, 16 Feb 2022 13:41:31 +1000
Subject: [Slackbuilds-users] libupnp version update
In-Reply-To: <CA+da1oqu8ORyzwxQuOSjnFDbvTN31f65iggQ14gFBnussf3RKg@mail.gmail.com>
References: <CA+da1ooP=qHtP2o=0g-VC0XudutWMPo-u=DKAou2U+F+QV5W6g@mail.gmail.com>
 <f2786ca5-788c-34aa-9d79-b50c5785b45b@linux.com>
 <CA+da1opvHRF0ZaQCf9DUx6MPuMu3kmyEKmhNi_nBb3gaqV_mSw@mail.gmail.com>
 <CA+da1oqu8ORyzwxQuOSjnFDbvTN31f65iggQ14gFBnussf3RKg@mail.gmail.com>
Message-ID: <f7f562e7-0996-db09-e79e-0347d4125239@linux.com>

On 15/2/22 18:23, Ozan T?rky?lmaz wrote:
> Hello Chris,
> 
> I tested libupnp 1.8.7 and vlc compiled fine here. Small version update
> would work.
> Also the latest patches I sent for libebml and libmatroska works for
> vlc. (Im attaching them)
> 

The shared lib patches for libebml & libmatroska fixed the libmatroska
problem (the others seem to have already been included in the master
branch). When the shared lib changes land in master, libmatroska can be
included in vlc again.

I'm still confused about libupnp - you mention version 1.8.7 but the
latest in master (which I'm using) is version 1.14.12. Can you clarify?

chris

From chris.willing at linux.com  Wed Feb 16 04:48:45 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Wed, 16 Feb 2022 14:48:45 +1000
Subject: [Slackbuilds-users] vlc available for new maintainer
Message-ID: <46108216-cbe9-9027-3017-8abb75334303@linux.com>

Amongst other things, I've not used it for some time.

chris

From bkirkp at gmail.com  Wed Feb 16 05:18:28 2022
From: bkirkp at gmail.com (Bill Kirkpatrick)
Date: Tue, 15 Feb 2022 23:18:28 -0600
Subject: [Slackbuilds-users] vlc available for new maintainer
In-Reply-To: <46108216-cbe9-9027-3017-8abb75334303@linux.com>
References: <46108216-cbe9-9027-3017-8abb75334303@linux.com>
Message-ID: <CAH+Ft2qy=z8u6xtj=MLWgDeGHqtPYPt2oU0iM15yUF_hwcHkEg@mail.gmail.com>

I'll take it. I use it all the time.
Thanks,
Bill


On Tue, Feb 15, 2022, 10:51 PM Christoph Willing <chris.willing at linux.com>
wrote:

> Amongst other things, I've not used it for some time.
>
> chris
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220215/038e75c1/attachment.htm>

From ozan.turkyilmaz at gmail.com  Wed Feb 16 06:05:13 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Wed, 16 Feb 2022 09:05:13 +0300
Subject: [Slackbuilds-users] libupnp version update
In-Reply-To: <f7f562e7-0996-db09-e79e-0347d4125239@linux.com>
References: <CA+da1ooP=qHtP2o=0g-VC0XudutWMPo-u=DKAou2U+F+QV5W6g@mail.gmail.com>
 <f2786ca5-788c-34aa-9d79-b50c5785b45b@linux.com>
 <CA+da1opvHRF0ZaQCf9DUx6MPuMu3kmyEKmhNi_nBb3gaqV_mSw@mail.gmail.com>
 <CA+da1oqu8ORyzwxQuOSjnFDbvTN31f65iggQ14gFBnussf3RKg@mail.gmail.com>
 <f7f562e7-0996-db09-e79e-0347d4125239@linux.com>
Message-ID: <CA+da1oqNxHt4fOGq9_BaEkWxCE87v11EqbHmfyYgx0Kmi_MyOA@mail.gmail.com>

Christoph Willing <chris.willing at linux.com>, 16 ?ub 2022 ?ar, 06:43
tarihinde ?unu yazd?:


> I'm still confused about libupnp - you mention version 1.8.7 but the
> latest in master (which I'm using) is version 1.14.12. Can you clarify?
>
>
I have tested a lower version. I am sending a patch for it now.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220216/e158c848/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-libupnp-libupnp-broke-the-API-and-we-have-to-downgra.patch
Type: application/octet-stream
Size: 1441 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220216/e158c848/attachment-0001.obj>

From chris.willing at linux.com  Wed Feb 16 07:59:40 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Wed, 16 Feb 2022 17:59:40 +1000
Subject: [Slackbuilds-users] libupnp version update for vlc
In-Reply-To: <CA+da1oqNxHt4fOGq9_BaEkWxCE87v11EqbHmfyYgx0Kmi_MyOA@mail.gmail.com>
References: <CA+da1ooP=qHtP2o=0g-VC0XudutWMPo-u=DKAou2U+F+QV5W6g@mail.gmail.com>
 <f2786ca5-788c-34aa-9d79-b50c5785b45b@linux.com>
 <CA+da1opvHRF0ZaQCf9DUx6MPuMu3kmyEKmhNi_nBb3gaqV_mSw@mail.gmail.com>
 <CA+da1oqu8ORyzwxQuOSjnFDbvTN31f65iggQ14gFBnussf3RKg@mail.gmail.com>
 <f7f562e7-0996-db09-e79e-0347d4125239@linux.com>
 <CA+da1oqNxHt4fOGq9_BaEkWxCE87v11EqbHmfyYgx0Kmi_MyOA@mail.gmail.com>
Message-ID: <325fe29f-42d4-4492-e446-e38cb186abf9@linux.com>

On 16/2/22 16:05, Ozan T?rky?lmaz wrote:
> 
> Christoph Willing <chris.willing at linux.com
> <mailto:chris.willing at linux.com>>, 16 ?ub 2022 ?ar, 06:43 tarihinde ?unu
> yazd?:
> ?
> 
>     I'm still confused about libupnp - you mention version 1.8.7 but the
>     latest in master (which I'm using) is version 1.14.12. Can you clarify?
> 
> 
> I have tested a lower version. I am sending a patch for it now.?

Thanks Ozan,

That older version 1.8.7 of libupnp works fine with vlc.


Bill,

I explicitly cc'd you (as new vlc maintainer) in case you weren't aware
of the connection between this libupnp thread and vlc.

The current version of libupnp in master branch (1.14.12) causes build
failure of vlc so I removed it from vlc's REQUIRES. Ozan has ascertained
that an earlier version 1.8.7 enables a successful build of vlc - which
I have just confirmed. Therefore when the libupnp SlackBuild in master
is updated to use 1.8.7, libupnp can be restored to vlc's REQUIRES.

In a similar vein, I removed a recently updated libmatroska from vlc's
REQUIRES for the same reason. Again, Ozan has further updates to libebml
& libmatroska which I have tested succesfully, allowing them to be
restored to vlc's REQUIRES when Ozan's updates hit master.

You will see some unnecessary code about needing to compile without
libebml (which is required by libmatroska) that some admin has recently
added to the vlc.SlackBuild. I never experienced that problem with
libebml installed and as far as I'm concerned (not that I am anymore)
the unnecessary filtering of libebml should be nuked out of orbit.

chris

From k22 at trixtar.org  Wed Feb 16 13:35:36 2022
From: k22 at trixtar.org (k22 at trixtar.org)
Date: Wed, 16 Feb 2022 08:35:36 -0500
Subject: [Slackbuilds-users] greenhorn greetings
In-Reply-To: <4fdd6620-95f8-40de-b860-c06e2241c67e@nixing.mx>
References: <20220211092839.3b87a6149fb3e13d54fbdb4a@trixtar.org>
 <31d06238-1069-4ff7-9649-b43fa60699ea@www.fastmail.com>
 <20220212084756.431380561c443bedbfbda452@trixtar.org>
 <4fdd6620-95f8-40de-b860-c06e2241c67e@nixing.mx>
Message-ID: <20220216083536.fe155adc7e4dbcb2eceb2ef1@trixtar.org>

On Sat, 12 Feb 2022 17:50:13 +0000 (UTC)
Nix <nix at nixing.mx> wrote:

> 
> >> the answer to "When can I expect it to be available?" is "When you add 
> >> it." :D It's actually not so hard, just some shell scripting.
> 
> I've found that this is the usual response and I understand why, yet for 
> new comers it can be overwhelming.
> 
> Again I understand and i'm eagerly waiting for slackbuilds to open it's 
> doors for the slackware stable 15? so I can submit updates for libstrophe 
> and profanity, and add new slackbuilds for its crypto support.
> 
> > Thank you very much, for now I'm totally swamped by these legion 
> > package-tools, having been spoiled rotten by Suse Yast :-)
> 
> I've been in your shoes? (and probably still am). I created a write-up 
> where I tried my best to explain the "confusing" parts of Slackware 
> package management. That may be of help to get you started.
> 
> I'd suggest to not feel discouraged by the overwhelming feeling that can 
> sometimes appear when trying to get into using Slackware. In my 
> experience it's worth the slight learning curve.
> 
> Write-up: https://nixing.mx/posts/exploring-slackware-slackbuilds.html

Thank you very much, for now I'm tinkering with slkpkg as it 
does dependencies but it isn't on for 15.0 yet. I want to first 
of all get to a point where I can do my most frequent 'compuke' 
chores on Slackware as well with a semblance of comfort: email, 
some browsing, seamonkey-composer, gftp, usenet etc. I'm just 
about OK with these already except for sylpheed. After this 
phase-1 I will get into the more focused activities for guitar 
sessions with my 'studio' apps and Google-Earth. Eventually 
I want to do just about everything I do with a computer on 
any one of my computers, using any one of my OS'es and either 
KDE or XFCE, rotating these on a daily basis so as to build
and preserve familiarity and to never be captive of any monopoly :-)

 


 
> 
> 
> Eric
> _______________________________________________
> 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 khronosschoty at posteo.org  Wed Feb 16 23:19:21 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Wed, 16 Feb 2022 23:19:21 +0000
Subject: [Slackbuilds-users] 0001-updated-for-Pale-Moon-29.4.4.patch
Message-ID: <Yg2GeeLX6YXlWeIW@posteo.de>

Hi this is an update for Pale Moon
-------------- next part --------------
>From 88bb8a167bff0c8ba298e7b2c5f53a60def7d38c Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 16 Feb 2022 14:42:08 -0800
Subject: [PATCH] updated for Pale Moon 29.4.4

---
 .../palemoon/basilisk-include-limits.patch    | 34 +++++++++++++++++++
 network/palemoon/palemoon.SlackBuild          | 13 ++++---
 network/palemoon/palemoon.info                |  8 ++---
 3 files changed, 43 insertions(+), 12 deletions(-)
 create mode 100644 network/palemoon/basilisk-include-limits.patch

diff --git a/network/palemoon/basilisk-include-limits.patch b/network/palemoon/basilisk-include-limits.patch
new file mode 100644
index 0000000000..22a8dc2474
--- /dev/null
+++ b/network/palemoon/basilisk-include-limits.patch
@@ -0,0 +1,34 @@
+diff -Naur basilisk-2021.11.14-source_orig/platform/gfx/2d/BaseRect.h basilisk-2021.11.14-source/platform/gfx/2d/BaseRect.h
+--- basilisk-2021.11.14-source_orig/platform/gfx/2d/BaseRect.h	2021-11-12 17:10:16.000000000 -0500
++++ basilisk-2021.11.14-source/platform/gfx/2d/BaseRect.h	2021-11-15 17:32:59.411746189 -0500
+@@ -9,6 +9,7 @@
+ #include <algorithm>
+ #include <cmath>
+ #include <ostream>
++#include <limits>
+ 
+ #include "mozilla/Assertions.h"
+ #include "mozilla/FloatingPoint.h"
+diff -Naur basilisk-2021.11.14-source_orig/platform/media/webrtc/trunk/webrtc/modules/audio_coding/codecs/opus/audio_encoder_opus.cc basilisk-2021.11.14-source/platform/media/webrtc/trunk/webrtc/modules/audio_coding/codecs/opus/audio_encoder_opus.cc
+--- basilisk-2021.11.14-source_orig/platform/media/webrtc/trunk/webrtc/modules/audio_coding/codecs/opus/audio_encoder_opus.cc	2021-11-12 17:10:36.000000000 -0500
++++ basilisk-2021.11.14-source/platform/media/webrtc/trunk/webrtc/modules/audio_coding/codecs/opus/audio_encoder_opus.cc	2021-11-15 17:35:40.787737049 -0500
+@@ -7,7 +7,7 @@
+  *  in the file PATENTS.  All contributing project authors may
+  *  be found in the AUTHORS file in the root of the source tree.
+  */
+-
++#include <limits>
+ #include "webrtc/modules/audio_coding/codecs/opus/interface/audio_encoder_opus.h"
+ 
+ #include "webrtc/base/checks.h"
+diff -Naur basilisk-2021.11.14-source_orig/platform/netwerk/base/nsURLParsers.cpp basilisk-2021.11.14-source/platform/netwerk/base/nsURLParsers.cpp
+--- basilisk-2021.11.14-source_orig/platform/netwerk/base/nsURLParsers.cpp	2021-11-12 17:10:38.000000000 -0500
++++ basilisk-2021.11.14-source/platform/netwerk/base/nsURLParsers.cpp	2021-11-15 17:33:50.427743299 -0500
+@@ -4,6 +4,7 @@
+  * file, You can obtain one at http://mozilla.org/MPL/2.0/. */
+ 
+ #include <string.h>
++#include <limits>
+ 
+ #include "mozilla/RangedPtr.h"
+ 
diff --git a/network/palemoon/palemoon.SlackBuild b/network/palemoon/palemoon.SlackBuild
index e86e27814e..a6bc228142 100644
--- a/network/palemoon/palemoon.SlackBuild
+++ b/network/palemoon/palemoon.SlackBuild
@@ -28,10 +28,10 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=palemoon
-VERSION=${VERSION:-29.1.1}
-SRCNAM1=${SRCNAM1:-Pale-Moon-${VERSION}_Release}
-SRCNAM2=${SRCNAM2:-pale-moon}
-SRCNAM3=${SRCNAM3:-UXP-RELBASE_20210330}
+VERSION=${VERSION:-29.4.4}
+SRCNAM1=${SRCNAM1:-$PRGNAM-$VERSION.source}
+SRCNAM2=${SRCNAM2:-$PRGNAM-source}
+SRCNAM3=${SRCNAM3:-$PRGNAM-$VERSION.source}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -154,9 +154,8 @@ PATH=$TMP/autoconf-tmp/usr/bin:$PATH
 # Build Pale Moon
 cd $TMP
 rm -rf $SRCNAM2
-tar -xvf $CWD/$SRCNAM1.tar.gz
+tar -xvf $CWD/$SRCNAM1.tar.xz
 cd $SRCNAM2
-tar -xvf $CWD/$SRCNAM3.tar.gz -C platform --strip-components 1
 
 if [ "${ADNAUSEAM:-block}" = "unblock" ]; then
 	patch -p1 < $CWD/adNauseam-unblock.patch
@@ -166,6 +165,7 @@ fi
 if [ "${PATCH_GLIBC:-no}" = "yes" ]; then
 	patch -p0 < $CWD/glibc-2.30+.patch
 fi
+patch -p1 < $CWD/basilisk-include-limits.patch
 
 chown -R root:root .
 find -L . \
@@ -230,7 +230,6 @@ echo "ac_add_options --disable-pulseaudio" >> .mozconfig; fi
 if pkg-config --exists jack && [ "${BLACKLIST_JACK:-no}" != "yes" ]; then
 echo "ac_add_options --enable-jack" >> .mozconfig; fi
 
-sed -i 's/.\/platform\/mach/"python2\ .\/platform\/mach"/g' mach
 ./mach build
 
 ## Clean up; and package Pale Moon.
diff --git a/network/palemoon/palemoon.info b/network/palemoon/palemoon.info
index 080df02f4e..c28f1e3154 100644
--- a/network/palemoon/palemoon.info
+++ b/network/palemoon/palemoon.info
@@ -1,11 +1,9 @@
 PRGNAM="palemoon"
-VERSION="29.1.1"
+VERSION="29.4.4"
 HOMEPAGE="http://www.palemoon.org/"
-DOWNLOAD="http://repo.khronosschoty.org/Slackware/Pale-Moon/source/Pale-Moon-29.1.1_Release.tar.gz
-          http://repo.khronosschoty.org/Slackware/Pale-Moon/source/UXP-RELBASE_20210330.tar.gz \
+DOWNLOAD="http://archive.palemoon.org/source/palemoon-29.4.4.source.tar.xz
           http://ponce.cc/slackware/sources/repo/autoconf-2.13.tar.xz"
-MD5SUM="f522cab929ec62382dc30391a590b039 \
-        535724b8fbb0d791cdf48f456969df9f \
+MD5SUM="84aaa73e058742c0a0dfe3d7f42c9ef0 \
         f2994d302cf736e7e71974edfa51da3c"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-- 
2.35.1


From artourter at gmail.com  Wed Feb 16 23:27:04 2022
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Wed, 16 Feb 2022 23:27:04 +0000
Subject: [Slackbuilds-users] upstream name change from Shapely to shapely
Message-ID: <CAK09-vk=t8cC+WWrRbjHsg2UTO81ANzqS=vV_OH3krArA5LE3w@mail.gmail.com>

Just a heads-up that Shapely has been renamed shapely and the git repo has
also be moved from github.com/Toblerity/Shapely to github.com/shapely/
shapely

I was updating the script for 1.8.1 when I noticed the change.

I will update the info file of all the dependent packages and send a PR but
thought I'd give a heads up first. Thankfully the list is not very long.

Cheers

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

From khronosschoty at posteo.org  Wed Feb 16 23:27:49 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Wed, 16 Feb 2022 23:27:49 +0000
Subject: [Slackbuilds-users]
 0002-updated-for-bluez-alsa-added-rc-script.patch
Message-ID: <Yg2IdSwyNdOD7xbM@posteo.de>

Hi this is an update for bluez-alsa
-------------- next part --------------
>From 06be55b1a322c6ae02af3cecfb7abee7ec6e98e3 Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 16 Feb 2022 15:25:36 -0800
Subject: [PATCH 2/2] updated for bluez-alsa, added rc script

---
 libraries/bluez-alsa/README                | 11 +++++++---
 libraries/bluez-alsa/bluez-alsa.SlackBuild |  5 +++--
 libraries/bluez-alsa/rc.bluez-alsa         | 24 ++++++++++++++++++++++
 3 files changed, 35 insertions(+), 5 deletions(-)
 create mode 100644 libraries/bluez-alsa/rc.bluez-alsa

diff --git a/libraries/bluez-alsa/README b/libraries/bluez-alsa/README
index c30d02528e..07c24be1b4 100644
--- a/libraries/bluez-alsa/README
+++ b/libraries/bluez-alsa/README
@@ -6,7 +6,12 @@ party audio applications. From now on, Bluez acts as a middleware between an
 audio application, which implements Bluetooth audio profile, and a Bluetooth
 audio device.
 
-Note: you might want to "start" "/usr/bin/bluealsa" via rc.local --
-for example, add the following line to rc.local:
+NOTE: A sample "rc" script is included, and installed in the usual location
+i.e. /etc/rc.d -- to use this rc script do the usual:
+chmod +x /etc/rc.d/rc.bluez-alsa
 
-  /usr/bin/bluealsa &
+Then add the following to your rc.local:
+        # Start bluez-alsa
+	if [ -x /etc/rc.d/rc.bluez-alsa ]; then
+	  /etc/rc.d/rc.bluez-alsa start
+        fi
diff --git a/libraries/bluez-alsa/bluez-alsa.SlackBuild b/libraries/bluez-alsa/bluez-alsa.SlackBuild
index b426140ce7..f60fd6416e 100644
--- a/libraries/bluez-alsa/bluez-alsa.SlackBuild
+++ b/libraries/bluez-alsa/bluez-alsa.SlackBuild
@@ -2,7 +2,7 @@
 
 # Slackware build script for bluez-alsa
 
-# Copyright 2018 Vasily Sora USA
+# Copyright 2018,2022 Vasily Sora USA
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -105,9 +105,10 @@ find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | gr
   | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
 
 mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
+mkdir -p $PKG/etc/rc.d
 cp -a README.md $PKG/usr/doc/$PRGNAM-$VERSION
 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
-
+cat $CWD/rc.bluez-alsa > $PKG/etc/rc.d/rc.bluez-alsa
 rm -f $PKG/usr/lib*/*.la
 
 mkdir -p $PKG/install
diff --git a/libraries/bluez-alsa/rc.bluez-alsa b/libraries/bluez-alsa/rc.bluez-alsa
new file mode 100644
index 0000000000..94d83656a8
--- /dev/null
+++ b/libraries/bluez-alsa/rc.bluez-alsa
@@ -0,0 +1,24 @@
+#!/bin/sh
+#
+# /etc/rc.d/rc.bluez-alsa
+#
+
+case "$1" in
+  'start')
+    nohup /usr/bin/bluealsa > /dev/null 2>&1 &
+    echo $! > /var/run/bluealsa.pid 
+  ;;
+  'stop')
+    kill $(cat /var/run/bluealsa.pid)
+    rm -f /var/run/bluealsa.pid
+  ;;
+  'restart')
+    kill $(cat /var/run/bluealsa.pid)
+    nohup /usr/bin/bluealsa > /dev/null 2>&1 &
+    echo $! > /var/run/bluealsa.pid
+  ;;
+  *)
+    echo "Usage: $0 {start|stop|restart}"
+  ;;
+esac
+
-- 
2.35.1


From nix at nixing.mx  Thu Feb 17 00:09:23 2022
From: nix at nixing.mx (Nix)
Date: Thu, 17 Feb 2022 00:09:23 +0000 (UTC)
Subject: [Slackbuilds-users] greenhorn greetings
In-Reply-To: <20220216083536.fe155adc7e4dbcb2eceb2ef1@trixtar.org>
References: <20220211092839.3b87a6149fb3e13d54fbdb4a@trixtar.org>
 <31d06238-1069-4ff7-9649-b43fa60699ea@www.fastmail.com>
 <20220212084756.431380561c443bedbfbda452@trixtar.org>
 <4fdd6620-95f8-40de-b860-c06e2241c67e@nixing.mx>
 <20220216083536.fe155adc7e4dbcb2eceb2ef1@trixtar.org>
Message-ID: <4ba2cf52-cf55-4218-b295-aab14e92de84@nixing.mx>


> about OK with these already except for sylpheed.

I hadn't heard of slypheed, it looks interesting.

> Eventually
> I want to do just about everything I do with a computer on
> any one of my computers, using any one of my OS'es and either
> KDE or XFCE, rotating these on a daily basis so as to build
> and preserve familiarity and to never be captive of any monopoly :-)

FOSS on!

From slackbuilds at schoepfer.info  Thu Feb 17 00:21:27 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Thu, 17 Feb 2022 01:21:27 +0100
Subject: [Slackbuilds-users] Fix oolite, update/fix klavaro
Message-ID: <973043e5b08d5db2625e2abb1baccc11@schoepfer.info>

As said in the subject.

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oolite.patch
Type: text/x-diff
Size: 1535 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220217/5e7208bf/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: klavaro.patch
Type: text/x-diff
Size: 1980 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220217/5e7208bf/attachment-0001.bin>

From lists at osh.id.au  Thu Feb 17 01:59:05 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Thu, 17 Feb 2022 09:59:05 +0800
Subject: [Slackbuilds-users] pandoc-bin and `slackpkg clean-system`
Message-ID: <bce61056-b980-4a18-9b0f-74fd59963c37@www.fastmail.com>

I noticed recently that `slackpkg clean-system` is offering to remove pandoc-bin, even though I have "[0-9]+_SBo" in /etc/slackpkg/blacklist

After some testing, I found that the problem is the arch. Installed as (by default):
pandoc-bin-2.17.1.1-amd64-1_SBo.tgz

`slackpkg clean-system` will offer to remove it, irrespective of the blacklist. Whereas installed as:
pandoc-bin-2.17.1.1-x86_64-1_SBo.tgz

The blacklist is respected. Shouldn't "[0-9]+_SBo" match both of those package names? Or will slackpkg always try to remove packages with an unexpected arch?

--
Dave

From phalange at komputermatrix.com  Thu Feb 17 02:42:16 2022
From: phalange at komputermatrix.com (Andrew Payne)
Date: Wed, 16 Feb 2022 21:42:16 -0500
Subject: [Slackbuilds-users] pandoc-bin and `slackpkg clean-system`
In-Reply-To: <bce61056-b980-4a18-9b0f-74fd59963c37@www.fastmail.com>
References: <bce61056-b980-4a18-9b0f-74fd59963c37@www.fastmail.com>
Message-ID: <b80a42f011f7e9950ed009609d0a1e41.squirrel@email.fatcow.com>

Dave you're right it's the amd64 that's throwing it off.

SBo folks, I just pushed an update to github that fixes this.

-A

> I noticed recently that `slackpkg clean-system` is offering to remove
> pandoc-bin, even though I have "[0-9]+_SBo" in /etc/slackpkg/blacklist
>
> After some testing, I found that the problem is the arch. Installed as (by
> default):
> pandoc-bin-2.17.1.1-amd64-1_SBo.tgz
>
> `slackpkg clean-system` will offer to remove it, irrespective of the
> blacklist. Whereas installed as:
> pandoc-bin-2.17.1.1-x86_64-1_SBo.tgz
>
> The blacklist is respected. Shouldn't "[0-9]+_SBo" match both of those
> package names? Or will slackpkg always try to remove packages with an
> unexpected arch?
>
> --
> 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/
>
>



From khronosschoty at posteo.org  Thu Feb 17 03:44:42 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 17 Feb 2022 03:44:42 +0000
Subject: [Slackbuilds-users] 0003-updated-et-to-version-6.1.11.patch
Message-ID: <Yg3EqrBnUh0pStDe@posteo.de>

Update for et (eternal server) version 6.1.11
-------------- next part --------------
>From 46d2aa5f1cff806cd7991b3272b9672c22b15ccf Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 16 Feb 2022 19:38:53 -0800
Subject: [PATCH 3/3] updated et to version 6.1.11

---
 network/et/et.SlackBuild |  2 +-
 network/et/et.diff       | 19 +++++++++++++++++++
 network/et/et.info       |  6 +++---
 3 files changed, 23 insertions(+), 4 deletions(-)
 create mode 100644 network/et/et.diff

diff --git a/network/et/et.SlackBuild b/network/et/et.SlackBuild
index 9713745055..63548d5cce 100644
--- a/network/et/et.SlackBuild
+++ b/network/et/et.SlackBuild
@@ -25,7 +25,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=et
-VERSION=${VERSION:-5.1.8}
+VERSION=${VERSION:-6.1.11}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
diff --git a/network/et/et.diff b/network/et/et.diff
new file mode 100644
index 0000000000..9b72dad646
--- /dev/null
+++ b/network/et/et.diff
@@ -0,0 +1,19 @@
+*** et.SlackBuild	2022-02-16 14:07:13.409733750 -0800
+--- et/et.SlackBuild	2022-02-03 16:27:52.508707690 -0800
+***************
+*** 25,31 ****
+  cd $(dirname $0) ; CWD=$(pwd)
+  
+  PRGNAM=et
+! VERSION=${VERSION:-5.1.8}
+  BUILD=${BUILD:-1}
+  TAG=${TAG:-_SBo}
+  PKGTYPE=${PKGTYPE:-tgz}
+--- 25,31 ----
+  cd $(dirname $0) ; CWD=$(pwd)
+  
+  PRGNAM=et
+! VERSION=${VERSION:-6.1.11}
+  BUILD=${BUILD:-1}
+  TAG=${TAG:-_SBo}
+  PKGTYPE=${PKGTYPE:-tgz}
diff --git a/network/et/et.info b/network/et/et.info
index a5927bfd84..db255cb51b 100644
--- a/network/et/et.info
+++ b/network/et/et.info
@@ -1,8 +1,8 @@
 PRGNAM="et"
-VERSION="5.1.8"
+VERSION="6.1.11"
 HOMEPAGE="https://mistertea.github.io/EternalTerminal/"
-DOWNLOAD="https://github.com/MisterTea/EternalTerminal/archive/et-v5.1.8/EternalTerminal-et-v5.1.8.tar.gz"
-MD5SUM="27f5975561694bf27215332c158cb925"
+DOWNLOAD="https://github.com/MisterTea/EternalTerminal/archive/et-v6.1.11/EternalTerminal-et-v6.1.11.tar.gz"
+MD5SUM="41dd49bb7f2969727321fd961b0ff06d"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES="protobuf-c gflags"
-- 
2.35.1


From willysr at slackbuilds.org  Thu Feb 17 05:00:07 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 17 Feb 2022 12:00:07 +0700
Subject: [Slackbuilds-users] Dropping packages
In-Reply-To: <11cec4d1-9cbc-4fab-ca3e-4a0785f1c9b1@modweb.de>
References: <11cec4d1-9cbc-4fab-ca3e-4a0785f1c9b1@modweb.de>
Message-ID: <b2cbc584-4897-5208-477d-dfedb944799c@slackbuilds.org>

> here's a list of packages I'm maintaining, but having issues building on
> 15.0, so I will no longer maintain them:
> 
> ? cclive????????? (not using it; fails building on 15.0; last updated 2013)
> ? quvi??????????? (dependency for cclive only; builds on 15.0)
> ? libquvi???????? (dependency for quvi only; builds on 15.0)
> ? simpleburn????? (source pkg no longer available)
> ? roger-router??? (not using it; sources availabe as flatpack only)
> ? spandsp???????? (dependency for roger-router only; builds on 15.0)
> ? libcapi20?????? (dependency for roger-router only; builds on 15.0)

All removed in my branch


-- 
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/20220217/eae4c830/attachment.asc>

From willysr at slackbuilds.org  Thu Feb 17 05:14:42 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 17 Feb 2022 12:14:42 +0700
Subject: [Slackbuilds-users] Changelog.txt
In-Reply-To: <451f37cf-8f2b-e26e-253c-0bc251c59494@linux.com>
References: <451f37cf-8f2b-e26e-253c-0bc251c59494@linux.com>
Message-ID: <df136e87-95de-6d0b-c099-c2267aedacf5@slackbuilds.org>

> Is the Changelog.txt still supposed to be updated?
> 
> I ask because I'm wondering whether lack of Changelog.txt updates might be 
> connected with recent times when I've done 'git pull origin master', then being 
> asked to add comment for a merge request. That's never happened before (for last 
> few years of updating).
> 
> Now I notice that the most recent entry in the Changelog.txt is |Sat Apr 17 
> 04:48:35 UTC 2021, yet most recent entry in the git log was committed just 
> recently ||2022-02-13 09:18:03 +0700.
> 
> So I'm now wondering if these things are connected somehow?

The ChangeLog will be updated once 15.0 is out with all the changes
since last freeze (14.2). After that, we go with (hopefully) normal
weekly update as usual.

if you want to update your local master branch, just go
git checkout master
git pull

that will pull the latest master into your local copy


-- 
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/20220217/2db728e1/attachment-0001.asc>

From willysr at slackbuilds.org  Thu Feb 17 05:16:44 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 17 Feb 2022 12:16:44 +0700
Subject: [Slackbuilds-users] some SlackBuilds can't handle MAKEFLAGS
 other than -j1
In-Reply-To: <d9db2262-9d43-2b45-873b-a75f188c6173@gmail.com>
References: <d9db2262-9d43-2b45-873b-a75f188c6173@gmail.com>
Message-ID: <5282978d-4489-74ba-0e68-3348fa145c71@slackbuilds.org>

> Some SlackBuilds can't handle MAKEFLAGS other than -j1.? Is it possible
> in future sbopkg will let you set MAKEFLAGS for multiple threads, and if
> a script can't handle it, reset to one?

I would prefer to set the -j1 in the SlackBuild directly
If the manual build failed, then it should be fixed in the script, not
by third party tool.


-- 
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/20220217/a1928d00/attachment.asc>

From willysr at slackbuilds.org  Thu Feb 17 05:25:34 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 17 Feb 2022 12:25:34 +0700
Subject: [Slackbuilds-users] lbench
In-Reply-To: <34c3bcd2-4d79-18e3-f9f7-b36389c343b1@gmail.com>
References: <34c3bcd2-4d79-18e3-f9f7-b36389c343b1@gmail.com>
Message-ID: <8e1f6e98-dfed-8f2a-047f-2a2f4976180b@slackbuilds.org>

> The lbench benchmark program is one SlackBuild that doesn't compile for
> me on Slackware 15 or 15+current from SBo-git.? Here's what it says
> 
> ?? lbench-3.7/Makefile
> ?? g++ -O2 -fPIC -Wall -g -rdynamic -O0 -Wno-format-truncation -c
> ?? `pkg-config --cflags gtk+-3.0`? -o lbench.o lbench-3.7.cc
> ?? lbench-3.7.cc: In function ?void* matrix_thread(void*)?:
> ?? lbench-3.7.cc:1424:23: warning: empty parentheses were disambiguated
> ?? as a function declaration [-Wvexing-parse]
> ??? ?1424 |??? int matrix_function();
> ??? ????? |?????????????????????? ^~
> ?? lbench-3.7.cc:1424:23: note: remove parentheses to
> ?? default-initialize a variable
> ??? ?1424 |??? int matrix_function();
> ??? ????? |?????????????????????? ^~
> ??? ????? |?????????????????????? --
> ?? lbench-3.7.cc:1424:23: note: or replace parentheses with braces to
> ?? value-initialize a variable
> ?? lbench-3.7.cc: In function ?void* linpack_thread(void*)?:
> ?? lbench-3.7.cc:2189:27: warning: empty parentheses were disambiguated
> ?? as a function declaration [-Wvexing-parse]
> ??? ?2189 |??? double linpack_function();
> ??? ????? |?????????????????????????? ^~
> ?? lbench-3.7.cc:2189:27: note: remove parentheses to
> ?? default-initialize a variable
> ??? ?2189 |??? double linpack_function();
> ??? ????? |?????????????????????????? ^~
> ??? ????? |?????????????????????????? --
> ?? lbench-3.7.cc:2189:27: note: or replace parentheses with braces to
> ?? value-initialize a variable
> ?? g++ -O2 -fPIC -Wall -g -rdynamic -O0 -Wno-format-truncation -c
> ?? `pkg-config --cflags gtk+-3.0` zfuncs.cc??? \
> ??? ????????? -D PREFIX=\"/usr\" -D DOCDIR=\"/usr/doc/lbench-3.7\"
> ?? zfuncs.cc: In function ?int zinitapp(const char*, const char*)?:
> ?? zfuncs.cc:5001:9: warning: ?int ftime(timeb*)? is deprecated: Use
> ?? gettimeofday or clock_gettime instead [-Wdeprecated-declarations]
> ??? ?5001 | ftime(&startime); //? app startup time
> ??? ????? |??? ~~~~~^~~~~~~~~~~
> ?? In file included from zfuncs.h:24,
> ??? ???????????????? from zfuncs.cc:23:
> ?? /usr/include/sys/timeb.h:29:12: note: declared here
> ??? ?? 29 | extern int ftime (struct timeb *__timebuf)
> ??? ????? |??????????? ^~~~~
> ?? zfuncs.cc: At global scope:
> ?? zfuncs.cc:10935:6: error: ambiguating new declaration of ?void
> ?? popup_report_timeout(zdialog*)?
> ?? 10935 | void popup_report_timeout(zdialog *zd)
> ??? ????? |????? ^~~~~~~~~~~~~~~~~~~~
> ?? zfuncs.cc:10921:8: note: old declaration ?int
> ?? popup_report_timeout(zdialog*)?
> ?? 10921 |??? int popup_report_timeout(zdialog *zd);
> ??? ????? |??????? ^~~~~~~~~~~~~~~~~~~~
> ?? make: *** [Makefile:34: zfuncs.o] Error 1
> 
> ??? I hope it will be updated but I also hope to see a version that
> works on X/TWM, not only Wayland/GNOME.? The lbench author told me GNOME
> might take up 1% or 2% CPU system resources, but for me, that's too
> much.? When I run benchmarks I turn off all but certain hardware &
> logging daemons... I guess because I'm more interested in mathematics
> than engineering, that I want an accurate benchmark--to five numerical
> places (as in science and professional engineering) not an approximation
> to 98%.
> ??? Does the maintainer use this listserv, and what do they or anyone
> think about that?

It built fine on 15.0 VM also on my -current desktop


-- 
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/20220217/0ff3af2b/attachment.asc>

From dchmelik at gmail.com  Thu Feb 17 05:30:51 2022
From: dchmelik at gmail.com (David Chmelik)
Date: Wed, 16 Feb 2022 21:30:51 -0800
Subject: [Slackbuilds-users] lbench
In-Reply-To: <8e1f6e98-dfed-8f2a-047f-2a2f4976180b@slackbuilds.org>
References: <34c3bcd2-4d79-18e3-f9f7-b36389c343b1@gmail.com>
 <8e1f6e98-dfed-8f2a-047f-2a2f4976180b@slackbuilds.org>
Message-ID: <9eeeff74-262d-c6b9-f493-cbcc87f31837@gmail.com>

On 2/16/22 9:25 PM, Willy Sudiarto Raharjo wrote:
>> The lbench benchmark program is one SlackBuild that doesn't compile for
>> me on Slackware 15 or 15+current from SBo-git. [...]
>>
>>  ??? I hope it will be updated but I also hope to see a version that
>> works on X/TWM, not only Wayland/GNOME.? The lbench author told me GNOME
>> might take up 1% or 2% CPU system resources, but for me, that's too
>> much.? When I run benchmarks I turn off all but certain hardware &
>> logging daemons... I guess because I'm more interested in mathematics
>> than engineering, that I want an accurate benchmark--to five numerical
>> places (as in science and professional engineering) not an approximation
>> to 98%.
>>  ??? Does the maintainer use this listserv, and what do they or anyone
>> think about that?
> It built fine on 15.0 VM also on my -current desktop
A day or two ago it also built fine for me but now has several 
dependencies not in Slackware nor SBo but for some reason not required 
to compile, such as libclutter-gtk.

    "libclutter-gtk dependencies:
    libc6, libcairo2, libclutter, libcogl20, libgdk-pixbuf, libglib2,
    libgtk-3, libwayland"--Michael Cornelison (lbench creator.)


From willysr at slackbuilds.org  Thu Feb 17 05:35:06 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 17 Feb 2022 12:35:06 +0700
Subject: [Slackbuilds-users]
 0002-updated-for-bluez-alsa-added-rc-script.patch
In-Reply-To: <Yg2IdSwyNdOD7xbM@posteo.de>
References: <Yg2IdSwyNdOD7xbM@posteo.de>
Message-ID: <473266ad-e65c-a81c-5866-a41cde19c05b@slackbuilds.org>

> Hi this is an update for bluez-alsa

Somehow, this patch doesn't apply cleanly


-- 
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/20220217/6eac03b2/attachment.asc>

From willysr at slackbuilds.org  Thu Feb 17 05:36:37 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 17 Feb 2022 12:36:37 +0700
Subject: [Slackbuilds-users] lbench
In-Reply-To: <9eeeff74-262d-c6b9-f493-cbcc87f31837@gmail.com>
References: <34c3bcd2-4d79-18e3-f9f7-b36389c343b1@gmail.com>
 <8e1f6e98-dfed-8f2a-047f-2a2f4976180b@slackbuilds.org>
 <9eeeff74-262d-c6b9-f493-cbcc87f31837@gmail.com>
Message-ID: <e2800706-7dec-266a-9bed-302ed8f15a2b@slackbuilds.org>

> A day or two ago it also built fine for me but now has several
> dependencies not in Slackware nor SBo but for some reason not required
> to compile, such as libclutter-gtk.
> 
> ?? "libclutter-gtk dependencies:
> ?? libc6, libcairo2, libclutter, libcogl20, libgdk-pixbuf, libglib2,
> ?? libgtk-3, libwayland"--Michael Cornelison (lbench creator.)

I think it's an optional dependency
and also did you test them in a clean environment where no other
packages were installed?

testing on a polluted environment can bring more dependencies sometimes

-- 
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/20220217/37e5b239/attachment.asc>

From willysr at slackbuilds.org  Thu Feb 17 06:03:52 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 17 Feb 2022 13:03:52 +0700
Subject: [Slackbuilds-users] Mumble-1.4 murmur is know murmur-server
In-Reply-To: <e1e89dbc-b746-6475-fb71-21ff9accf53f@linuxgalaxy.org>
References: <e1e89dbc-b746-6475-fb71-21ff9accf53f@linuxgalaxy.org>
Message-ID: <51a7480f-c3ff-06f0-c91a-4dc29f6b928a@slackbuilds.org>

> I've got most of the kinks worked out and just need to finish testing.
> Upstream renamed murmurd (mumble server) to, heh, mumble-server.  The
> mumble client remains the same.  Thus, we'll need to remove the old
> murmur slackbuild.
> 
> For the update, do I just push up my branch, or wait until SBo goes live
> to get everything sorted?  We'll have to drop murmur and add mumble-server.
> 
> For the voip curious, you can grab them here:
> https://www.linuxgalaxy.org/files/sbo-testing/15.0/
> 
> The [mumble | murmur]-1.3.4 pair currently in git master works fine on
> 15.0, so there's no rush.

If you can push it to your branch, that would be great
renaming scripts once the stable repo takes more steps, so it's easier
to change the name during development cycle when everything is not yet
stored in database yet


-- 
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/20220217/e800e6a8/attachment-0001.asc>

From khronosschoty at posteo.org  Thu Feb 17 06:55:12 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 17 Feb 2022 06:55:12 +0000
Subject: [Slackbuilds-users] 0001-updated-for-Pale-Moon-29.4.4.patch
Message-ID: <Yg3xUPKxGc0c71xA@posteo.de>

Formatting errors on patch fixed, update for Pale Moon 29.4.4
-------------- next part --------------
>From 70e0b3af90debcb0e28a8230c7ac712b00e13dbe Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 16 Feb 2022 22:52:03 -0800
Subject: [PATCH] updated for Pale Moon 29.4.4

---
 .../palemoon/basilisk-include-limits.patch    | 33 +++++++++++++++++++
 network/palemoon/palemoon.SlackBuild          | 13 ++++----
 network/palemoon/palemoon.info                |  8 ++---
 3 files changed, 42 insertions(+), 12 deletions(-)
 create mode 100644 network/palemoon/basilisk-include-limits.patch

diff --git a/network/palemoon/basilisk-include-limits.patch b/network/palemoon/basilisk-include-limits.patch
new file mode 100644
index 0000000000..27ca825788
--- /dev/null
+++ b/network/palemoon/basilisk-include-limits.patch
@@ -0,0 +1,33 @@
+diff -Naur basilisk-2021.11.14-source_orig/platform/gfx/2d/BaseRect.h basilisk-2021.11.14-source/platform/gfx/2d/BaseRect.h
+--- basilisk-2021.11.14-source_orig/platform/gfx/2d/BaseRect.h	2021-11-12 17:10:16.000000000 -0500
++++ basilisk-2021.11.14-source/platform/gfx/2d/BaseRect.h	2021-11-15 17:32:59.411746189 -0500
+@@ -9,6 +9,7 @@
+ #include <algorithm>
+ #include <cmath>
+ #include <ostream>
++#include <limits>
+
+ #include "mozilla/Assertions.h"
+ #include "mozilla/FloatingPoint.h"
+diff -Naur basilisk-2021.11.14-source_orig/platform/media/webrtc/trunk/webrtc/modules/audio_coding/codecs/opus/audio_encoder_opus.cc basilisk-2021.11.14-source/platform/media/webrtc/trunk/webrtc/modules/audio_coding/codecs/opus/audio_encoder_opus.cc
+--- basilisk-2021.11.14-source_orig/platform/media/webrtc/trunk/webrtc/modules/audio_coding/codecs/opus/audio_encoder_opus.cc	2021-11-12 17:10:36.000000000 -0500
++++ basilisk-2021.11.14-source/platform/media/webrtc/trunk/webrtc/modules/audio_coding/codecs/opus/audio_encoder_opus.cc	2021-11-15 17:35:40.787737049 -0500
+@@ -7,7 +7,7 @@
+  *  in the file PATENTS.  All contributing project authors may
+  *  be found in the AUTHORS file in the root of the source tree.
+  */
+-
++#include <limits>
+ #include "webrtc/modules/audio_coding/codecs/opus/interface/audio_encoder_opus.h"
+
+ #include "webrtc/base/checks.h"
+diff -Naur basilisk-2021.11.14-source_orig/platform/netwerk/base/nsURLParsers.cpp basilisk-2021.11.14-source/platform/netwerk/base/nsURLParsers.cpp
+--- basilisk-2021.11.14-source_orig/platform/netwerk/base/nsURLParsers.cpp	2021-11-12 17:10:38.000000000 -0500
++++ basilisk-2021.11.14-source/platform/netwerk/base/nsURLParsers.cpp	2021-11-15 17:33:50.427743299 -0500
+@@ -4,6 +4,7 @@
+  * file, You can obtain one at http://mozilla.org/MPL/2.0/. */
+
+ #include <string.h>
++#include <limits>
+
+ #include "mozilla/RangedPtr.h"
diff --git a/network/palemoon/palemoon.SlackBuild b/network/palemoon/palemoon.SlackBuild
index e86e27814e..a6bc228142 100644
--- a/network/palemoon/palemoon.SlackBuild
+++ b/network/palemoon/palemoon.SlackBuild
@@ -28,10 +28,10 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=palemoon
-VERSION=${VERSION:-29.1.1}
-SRCNAM1=${SRCNAM1:-Pale-Moon-${VERSION}_Release}
-SRCNAM2=${SRCNAM2:-pale-moon}
-SRCNAM3=${SRCNAM3:-UXP-RELBASE_20210330}
+VERSION=${VERSION:-29.4.4}
+SRCNAM1=${SRCNAM1:-$PRGNAM-$VERSION.source}
+SRCNAM2=${SRCNAM2:-$PRGNAM-source}
+SRCNAM3=${SRCNAM3:-$PRGNAM-$VERSION.source}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -154,9 +154,8 @@ PATH=$TMP/autoconf-tmp/usr/bin:$PATH
 # Build Pale Moon
 cd $TMP
 rm -rf $SRCNAM2
-tar -xvf $CWD/$SRCNAM1.tar.gz
+tar -xvf $CWD/$SRCNAM1.tar.xz
 cd $SRCNAM2
-tar -xvf $CWD/$SRCNAM3.tar.gz -C platform --strip-components 1
 
 if [ "${ADNAUSEAM:-block}" = "unblock" ]; then
 	patch -p1 < $CWD/adNauseam-unblock.patch
@@ -166,6 +165,7 @@ fi
 if [ "${PATCH_GLIBC:-no}" = "yes" ]; then
 	patch -p0 < $CWD/glibc-2.30+.patch
 fi
+patch -p1 < $CWD/basilisk-include-limits.patch
 
 chown -R root:root .
 find -L . \
@@ -230,7 +230,6 @@ echo "ac_add_options --disable-pulseaudio" >> .mozconfig; fi
 if pkg-config --exists jack && [ "${BLACKLIST_JACK:-no}" != "yes" ]; then
 echo "ac_add_options --enable-jack" >> .mozconfig; fi
 
-sed -i 's/.\/platform\/mach/"python2\ .\/platform\/mach"/g' mach
 ./mach build
 
 ## Clean up; and package Pale Moon.
diff --git a/network/palemoon/palemoon.info b/network/palemoon/palemoon.info
index 080df02f4e..c28f1e3154 100644
--- a/network/palemoon/palemoon.info
+++ b/network/palemoon/palemoon.info
@@ -1,11 +1,9 @@
 PRGNAM="palemoon"
-VERSION="29.1.1"
+VERSION="29.4.4"
 HOMEPAGE="http://www.palemoon.org/"
-DOWNLOAD="http://repo.khronosschoty.org/Slackware/Pale-Moon/source/Pale-Moon-29.1.1_Release.tar.gz
-          http://repo.khronosschoty.org/Slackware/Pale-Moon/source/UXP-RELBASE_20210330.tar.gz \
+DOWNLOAD="http://archive.palemoon.org/source/palemoon-29.4.4.source.tar.xz
           http://ponce.cc/slackware/sources/repo/autoconf-2.13.tar.xz"
-MD5SUM="f522cab929ec62382dc30391a590b039 \
-        535724b8fbb0d791cdf48f456969df9f \
+MD5SUM="84aaa73e058742c0a0dfe3d7f42c9ef0 \
         f2994d302cf736e7e71974edfa51da3c"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-- 
2.35.1


From khronosschoty at posteo.org  Thu Feb 17 06:59:33 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 17 Feb 2022 06:59:33 +0000
Subject: [Slackbuilds-users]
 0001-updated-for-bluez-alsa-added-rc-script.patch
Message-ID: <Yg3yVQbL+KvcLllO@posteo.de>

removed trailing white spaces, new patch for update on bluez-alsa
-------------- next part --------------
>From fff0205e74140731a174704a81314597ed4a6a27 Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 16 Feb 2022 22:57:04 -0800
Subject: [PATCH] updated for bluez alsa added rc script

---
 libraries/bluez-alsa/README                | 11 ++++++++---
 libraries/bluez-alsa/bluez-alsa.SlackBuild |  5 +++--
 libraries/bluez-alsa/rc.bluez-alsa         | 23 ++++++++++++++++++++++
 3 files changed, 34 insertions(+), 5 deletions(-)
 create mode 100644 libraries/bluez-alsa/rc.bluez-alsa

diff --git a/libraries/bluez-alsa/README b/libraries/bluez-alsa/README
index c30d02528e..07c24be1b4 100644
--- a/libraries/bluez-alsa/README
+++ b/libraries/bluez-alsa/README
@@ -6,7 +6,12 @@ party audio applications. From now on, Bluez acts as a middleware between an
 audio application, which implements Bluetooth audio profile, and a Bluetooth
 audio device.
 
-Note: you might want to "start" "/usr/bin/bluealsa" via rc.local --
-for example, add the following line to rc.local:
+NOTE: A sample "rc" script is included, and installed in the usual location
+i.e. /etc/rc.d -- to use this rc script do the usual:
+chmod +x /etc/rc.d/rc.bluez-alsa
 
-  /usr/bin/bluealsa &
+Then add the following to your rc.local:
+        # Start bluez-alsa
+	if [ -x /etc/rc.d/rc.bluez-alsa ]; then
+	  /etc/rc.d/rc.bluez-alsa start
+        fi
diff --git a/libraries/bluez-alsa/bluez-alsa.SlackBuild b/libraries/bluez-alsa/bluez-alsa.SlackBuild
index b426140ce7..f60fd6416e 100644
--- a/libraries/bluez-alsa/bluez-alsa.SlackBuild
+++ b/libraries/bluez-alsa/bluez-alsa.SlackBuild
@@ -2,7 +2,7 @@
 
 # Slackware build script for bluez-alsa
 
-# Copyright 2018 Vasily Sora USA
+# Copyright 2018,2022 Vasily Sora USA
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -105,9 +105,10 @@ find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | gr
   | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
 
 mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
+mkdir -p $PKG/etc/rc.d
 cp -a README.md $PKG/usr/doc/$PRGNAM-$VERSION
 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
-
+cat $CWD/rc.bluez-alsa > $PKG/etc/rc.d/rc.bluez-alsa
 rm -f $PKG/usr/lib*/*.la
 
 mkdir -p $PKG/install
diff --git a/libraries/bluez-alsa/rc.bluez-alsa b/libraries/bluez-alsa/rc.bluez-alsa
new file mode 100644
index 0000000000..dd694165c0
--- /dev/null
+++ b/libraries/bluez-alsa/rc.bluez-alsa
@@ -0,0 +1,23 @@
+#!/bin/sh
+#
+# /etc/rc.d/rc.bluez-alsa
+#
+
+case "$1" in
+  'start')
+    nohup /usr/bin/bluealsa > /dev/null 2>&1 &
+    echo $! > /var/run/bluealsa.pid
+  ;;
+  'stop')
+    kill $(cat /var/run/bluealsa.pid)
+    rm -f /var/run/bluealsa.pid
+  ;;
+  'restart')
+    kill $(cat /var/run/bluealsa.pid)
+    nohup /usr/bin/bluealsa > /dev/null 2>&1 &
+    echo $! > /var/run/bluealsa.pid
+  ;;
+  *)
+    echo "Usage: $0 {start|stop|restart}"
+  ;;
+esac
-- 
2.35.1


From lists at osh.id.au  Thu Feb 17 07:04:28 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Thu, 17 Feb 2022 15:04:28 +0800
Subject: [Slackbuilds-users] Looking for new signal-desktop maintainer
Message-ID: <7ac62157-1259-45db-b8b4-798ea1ac04e7@www.fastmail.com>

Hello all,

I'm looking to give up signal-desktop, as it's a fiddly source build, as well as suffering from binaries being frequently removed upstream (and I've started playing around with packaging it for my own repo). It's not the sort of package you can just leave without updates, as upstream will eventually disable old builds anyway.

That said, it's a great program/service. Would anyone be interested in taking it over?

--
Dave

From khronosschoty at posteo.org  Thu Feb 17 07:26:43 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 17 Feb 2022 07:26:43 +0000
Subject: [Slackbuilds-users] 0003-updated-et-to-version-6.1.11.patch
Message-ID: <Yg34s0wJtITpJP5Q@posteo.de>

removed trialing white space from patch, and wrongly included diff, et updated to version 6.1.11
-------------- next part --------------
>From 77c9048c8a6d93a945982831b6581436ade0558b Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 16 Feb 2022 23:22:23 -0800
Subject: [PATCH 3/3] updated et to version 6.1.11

---
 network/et/et.SlackBuild | 2 +-
 network/et/et.info       | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/network/et/et.SlackBuild b/network/et/et.SlackBuild
index 9713745055..63548d5cce 100644
--- a/network/et/et.SlackBuild
+++ b/network/et/et.SlackBuild
@@ -25,7 +25,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=et
-VERSION=${VERSION:-5.1.8}
+VERSION=${VERSION:-6.1.11}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
diff --git a/network/et/et.info b/network/et/et.info
index a5927bfd84..db255cb51b 100644
--- a/network/et/et.info
+++ b/network/et/et.info
@@ -1,8 +1,8 @@
 PRGNAM="et"
-VERSION="5.1.8"
+VERSION="6.1.11"
 HOMEPAGE="https://mistertea.github.io/EternalTerminal/"
-DOWNLOAD="https://github.com/MisterTea/EternalTerminal/archive/et-v5.1.8/EternalTerminal-et-v5.1.8.tar.gz"
-MD5SUM="27f5975561694bf27215332c158cb925"
+DOWNLOAD="https://github.com/MisterTea/EternalTerminal/archive/et-v6.1.11/EternalTerminal-et-v6.1.11.tar.gz"
+MD5SUM="41dd49bb7f2969727321fd961b0ff06d"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES="protobuf-c gflags"
-- 
2.35.1


From lists at osh.id.au  Thu Feb 17 07:28:10 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Thu, 17 Feb 2022 15:28:10 +0800
Subject: [Slackbuilds-users] New maintainer for olm
Message-ID: <49d330da-49ce-41ac-bab7-b4ff7b2b05ce@www.fastmail.com>

Hello,

olm has a new maintainer, Roger Krowiak (cc'd). His updated SlackBuild is attached, thanks Roger!

--
Dave
-------------- next part --------------
A non-text attachment was scrubbed...
Name: olm.tar.gz
Type: application/gzip
Size: 2775 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220217/12a7f193/attachment-0001.bin>

From rogerkrowiak+slackbuilds at gmail.com  Thu Feb 17 08:57:07 2022
From: rogerkrowiak+slackbuilds at gmail.com (Roger Krowiak)
Date: Thu, 17 Feb 2022 09:57:07 +0100
Subject: [Slackbuilds-users] New maintainer for olm
In-Reply-To: <49d330da-49ce-41ac-bab7-b4ff7b2b05ce@www.fastmail.com>
References: <49d330da-49ce-41ac-bab7-b4ff7b2b05ce@www.fastmail.com>
Message-ID: <CAGpsf_GQHZ_seqZOm1RHeempJh3+noNTNbnHYbVT5Hk_zeXh9g@mail.gmail.com>

 Hello guys, reporting for duty!

On Thu, Feb 17, 2022 at 8:29 AM David O'Shaughnessy <lists at osh.id.au> wrote:

> Hello,
>
> olm has a new maintainer, Roger Krowiak (cc'd). His updated SlackBuild is
> attached, thanks Roger!
>
> --
> 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/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220217/ced0de66/attachment.htm>

From k22 at trixtar.org  Thu Feb 17 12:06:52 2022
From: k22 at trixtar.org (k22 at trixtar.org)
Date: Thu, 17 Feb 2022 07:06:52 -0500
Subject: [Slackbuilds-users] greenhorn greetings
In-Reply-To: <4ba2cf52-cf55-4218-b295-aab14e92de84@nixing.mx>
References: <20220211092839.3b87a6149fb3e13d54fbdb4a@trixtar.org>
 <31d06238-1069-4ff7-9649-b43fa60699ea@www.fastmail.com>
 <20220212084756.431380561c443bedbfbda452@trixtar.org>
 <4fdd6620-95f8-40de-b860-c06e2241c67e@nixing.mx>
 <20220216083536.fe155adc7e4dbcb2eceb2ef1@trixtar.org>
 <4ba2cf52-cf55-4218-b295-aab14e92de84@nixing.mx>
Message-ID: <20220217070652.698aa2ca55e356b5a46c691d@trixtar.org>

On Thu, 17 Feb 2022 00:09:23 +0000 (UTC)
Nix <nix at nixing.mx> wrote:

> > about OK with these already except for sylpheed.
> 
> I hadn't heard of slypheed, it looks interesting.

After years with kMail I wanted (like in most all
cases) in-the-clear .eml files and Sylpheed is as 
close as I got. 

I'm as outdated as kernel 1.9, and my preference 
tool is a file-manager which an app GUI should 
emulate in parallel, listing sub-folders that it 
FINDS after I put them there with files it FINDS
that I had moved there: no index files, no scrambling, 
no FLUFF. It's not even close to giving me everything 
I want BUT it's relatively simple and clean (similar 
to Claws, or so I hear).



-- 
Thursdays are generaly Leap days.
openSUSE Leap 15.3, Kernel=5.3.18-150300.59.49-preempt 
on x86_64, DM=sddm, DE=KDE, ST=x11,grub2, GPT, BIOS-boot



From artourter at gmail.com  Thu Feb 17 13:29:16 2022
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Thu, 17 Feb 2022 13:29:16 +0000
Subject: [Slackbuilds-users] Looking for new signal-desktop maintainer
In-Reply-To: <7ac62157-1259-45db-b8b4-798ea1ac04e7@www.fastmail.com>
References: <7ac62157-1259-45db-b8b4-798ea1ac04e7@www.fastmail.com>
Message-ID: <CAK09-v=VVPbwgyt0V39s1FZ+=v+T7KbjVpUHXaW=JG13RK=pGg@mail.gmail.com>

Hi David,

I am happy to take this one over. I will submit an updated version using
the binary build as a PR a bit later.

Cheers

Greg

On Thu, 17 Feb 2022 at 07:04, David O'Shaughnessy <lists at osh.id.au> wrote:

> Hello all,
>
> I'm looking to give up signal-desktop, as it's a fiddly source build, as
> well as suffering from binaries being frequently removed upstream (and I've
> started playing around with packaging it for my own repo). It's not the
> sort of package you can just leave without updates, as upstream will
> eventually disable old builds anyway.
>
> That said, it's a great program/service. Would anyone be interested in
> taking it over?
>
> --
> 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/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220217/97f367fe/attachment.htm>

From artourter at gmail.com  Thu Feb 17 15:24:40 2022
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Thu, 17 Feb 2022 15:24:40 +0000
Subject: [Slackbuilds-users] renaming python scripts
Message-ID: <CAK09-v=JX8Vkw1Z9LSvwVg_sN9mLC7zyk=vSx3E3NCQee3_RxA@mail.gmail.com>

Hi all,

Some of my python scripts, mostly inherited, tend to be a bit over the
place. Some are named with a python?- prefix, some aren't, some are not in
the python folder but in libraries (nltk and that one is my fault).

I know there has been a long discussion in the past on how to deal with
python naming  but I am sure where we are at.

This was vaguely prompted by me tracking my packages in repology which in
some cases doesn't add the python: prefix to some of the packages (xarray
and nltk).

Should I rename/relocate these?

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

From arnaud.garcia-fernandez at laposte.net  Thu Feb 17 15:57:27 2022
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Thu, 17 Feb 2022 16:57:27 +0100
Subject: [Slackbuilds-users] renaming python scripts
In-Reply-To: <CAK09-v=JX8Vkw1Z9LSvwVg_sN9mLC7zyk=vSx3E3NCQee3_RxA@mail.gmail.com>
References: <CAK09-v=JX8Vkw1Z9LSvwVg_sN9mLC7zyk=vSx3E3NCQee3_RxA@mail.gmail.com>
Message-ID: <20220217165727.e483354b50f8563d4d265296@laposte.net>

> Hi all,
> 
> Some of my python scripts, mostly inherited, tend to be a bit over the
> place. Some are named with a python?- prefix, some aren't, some are not in
> the python folder but in libraries (nltk and that one is my fault).
> 
> I know there has been a long discussion in the past on how to deal with
> python naming  but I am sure where we are at.
> 
> This was vaguely prompted by me tracking my packages in repology which in
> some cases doesn't add the python: prefix to some of the packages (xarray
> and nltk).
> 
> Should I rename/relocate these?
> 
> Greg

Hi !

I have a lot of work to do myself on that part.

I think the only thing that was mostly decided is that python2 only packages should be named python2-package

Hope that helps at least a little...

	- Yth.

From lists at osh.id.au  Fri Feb 18 00:35:17 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Fri, 18 Feb 2022 08:35:17 +0800
Subject: [Slackbuilds-users] Looking for new signal-desktop maintainer
In-Reply-To: <CAK09-v=VVPbwgyt0V39s1FZ+=v+T7KbjVpUHXaW=JG13RK=pGg@mail.gmail.com>
References: <7ac62157-1259-45db-b8b4-798ea1ac04e7@www.fastmail.com>
 <CAK09-v=VVPbwgyt0V39s1FZ+=v+T7KbjVpUHXaW=JG13RK=pGg@mail.gmail.com>
Message-ID: <1a72a037-8e3d-4d5e-95c8-b530f6170bf5@www.fastmail.com>

Thanks Greg!

On Thu, 17 Feb 2022, at 9:29 PM, Greg' Ar Tourter wrote:
> Hi David,
> 
> I am happy to take this one over. I will submit an updated version using the binary build as a PR a bit later.
> 
> Cheers
> 
> Greg
> 
> On Thu, 17 Feb 2022 at 07:04, David O'Shaughnessy <lists at osh.id.au> wrote:
>> Hello all,
>> 
>> I'm looking to give up signal-desktop, as it's a fiddly source build, as well as suffering from binaries being frequently removed upstream (and I've started playing around with packaging it for my own repo). It's not the sort of package you can just leave without updates, as upstream will eventually disable old builds anyway.
>> 
>> That said, it's a great program/service. Would anyone be interested in taking it over?
>> 
>> --
>> Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220218/c02a1857/attachment-0001.htm>

From andrew.david.strong at gmail.com  Fri Feb 18 07:04:08 2022
From: andrew.david.strong at gmail.com (andrew)
Date: Fri, 18 Feb 2022 18:04:08 +1100
Subject: [Slackbuilds-users] Updates for exhale (audio)
Message-ID: <Yg9E6N/CJAr8WIgy@ilium.andrews-corner.org>

Hi,

I have seen a few patches posted here to update applications for 15.0,
hopefully this is still an acceptable way to do things?

I attach a patch for exhale to update to latest version and remove an
un-needed compiler flag. Patched against latest git master. 

Andrew
-- 
You think that's air you're breathing now?
-------------- next part --------------
diff --git a/audio/exhale/exhale.SlackBuild b/audio/exhale/exhale.SlackBuild
index cdd57e607f..099bc3885a 100644
--- a/audio/exhale/exhale.SlackBuild
+++ b/audio/exhale/exhale.SlackBuild
@@ -2,7 +2,7 @@
 # ----------------------------------------------------------------------
 # Slackware build script for exhale
 #
-# Copyright (c) 2020 - 2021 Andrew Strong, Blue Mountains, Australia.
+# Copyright (c) 2020 - 2022 Andrew Strong, Blue Mountains, Australia.
 #
 #   Permission to use, copy, modify, and distribute this software for
 #   any purpose with or without fee is hereby granted, provided that
@@ -26,7 +26,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=exhale
-VERSION=${VERSION:-1.1.1}
+VERSION=${VERSION:-1.1.9}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -51,18 +51,14 @@ TMP=${TMP:-/tmp/SBo}
 PKG=$TMP/package-$PRGNAM
 OUTPUT=${OUTPUT:-/tmp}
 
-# The compiler flag '-std=c++11' is required for a succesful compile
-# under Slackware 14.2 and gcc 5.3.0. This flag is not required for
-# versions of Slackware > 14.2.
-
 if [ "$ARCH" = "i586" ]; then
-  SLKCFLAGS="-O2 -march=i586 -mtune=i686 -std=c++11"
+  SLKCFLAGS="-O2 -march=i586 -mtune=i686"
   LIBDIRSUFFIX=""
 elif [ "$ARCH" = "i686" ]; then
-  SLKCFLAGS="-O2 -march=i686 -mtune=i686 -std=c++11"
+  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
   LIBDIRSUFFIX=""
 elif [ "$ARCH" = "x86_64" ]; then
-  SLKCFLAGS="-O2 -fPIC -std=c++11"
+  SLKCFLAGS="-O2 -fPIC"
   LIBDIRSUFFIX="64"
 else
   SLKCFLAGS="-O2 -std=c++11"
diff --git a/audio/exhale/exhale.info b/audio/exhale/exhale.info
index 1c4fee3cc5..cc0a0ca163 100644
--- a/audio/exhale/exhale.info
+++ b/audio/exhale/exhale.info
@@ -1,8 +1,8 @@
 PRGNAM="exhale"
-VERSION="1.1.1"
+VERSION="1.1.9"
 HOMEPAGE="https://gitlab.com/ecodis/exhale"
-DOWNLOAD="https://gitlab.com/ecodis/exhale/-/archive/v1.1.1/exhale-v1.1.1.tar.gz"
-MD5SUM="432130dfbcd6b219268b235973dcca83"
+DOWNLOAD="https://gitlab.com/ecodis/exhale/-/archive/v1.1.9/exhale-v1.1.9.tar.gz"
+MD5SUM="735e595d0dd3defb02cc9d320dbb4253"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""

From slackbuilds at schoepfer.info  Fri Feb 18 14:16:43 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 18 Feb 2022 15:16:43 +0100
Subject: [Slackbuilds-users] Maintenance takeover pwgen, update DPF-Plugins,
 update amSynth
In-Reply-To: <20220218215832.68cc9ed1@elika.timp.com.au>
References: <a9ef3a9ed157ea8476f704a213cd6b95@schoepfer.info>
 <20220218215832.68cc9ed1@elika.timp.com.au>
Message-ID: <e4e38a538e2526be794a794e6271febc@schoepfer.info>

Hi,

as said in the subject.

-------- Original Message --------
Subject: Re: pwgen on SBo
Date: 2022-02-18 12:58
 From: "Timothy Pollard (SlackBuilds)" <sbo at timp.com.au>
To: Franzen <slackbuilds at schoepfer.info>

On Fri, 18 Feb 2022 08:40:43 +0100
Franzen <slackbuilds at schoepfer.info> wrote:
> Hi Timothy,
> 
> do you still maintain pwgen?
> There's an update to 2.08 available since 5 Years.
> I'd be interested in taking over maintenance.

G'day Johannes,

Go ahead an take it over if you want; I obviously haven't been keeping 
my eye
on it then.
> 
> Thanks for your reply,
> 
> Johannes

Cheers,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pwgen.patch
Type: text/x-diff
Size: 5450 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220218/e7447b4d/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DPF-Plugins.patch
Type: text/x-diff
Size: 2009 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220218/e7447b4d/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: amSynth.patch
Type: text/x-diff
Size: 1726 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220218/e7447b4d/attachment-0002.bin>

From jdashiel at panix.com  Fri Feb 18 15:24:23 2022
From: jdashiel at panix.com (Jude DaShiell)
Date: Fri, 18 Feb 2022 10:24:23 -0500
Subject: [Slackbuilds-users] Maintenance takeover pwgen,
 update DPF-Plugins, update amSynth
In-Reply-To: <e4e38a538e2526be794a794e6271febc@schoepfer.info>
References: <a9ef3a9ed157ea8476f704a213cd6b95@schoepfer.info>
 <20220218215832.68cc9ed1@elika.timp.com.au>
 <e4e38a538e2526be794a794e6271febc@schoepfer.info>
Message-ID: <f8c1f02b-921f-9a7-99aa-12af27116995@panix.com>

One of the recommendations I read somewhere for strong passwords in
addition to the others was to begin and end passwords with a letter not
symbols or numbers to increase the time needed to crack the passwords.  I
never found a Linux package that could do this but while working for the
Navy I wrote an excel workbook that could generate passwords and was able
to set rules like this and others for those passwords.



From ozan.turkyilmaz at gmail.com  Fri Feb 18 19:13:35 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Fri, 18 Feb 2022 22:13:35 +0300
Subject: [Slackbuilds-users] New submissions
Message-ID: <CA+da1or=HzhuKHfZHTa0Hv_aStQvtikUV3gzJx8s2wx-4d4stw@mail.gmail.com>

Hello All,

I have a question about submissions (when we eventually arrive there).
Are you going to do git patches or merge requests for submissions or
are we keeping uploading tarballs for new submissions?

Regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220218/546ec746/attachment.htm>

From willysr at slackbuilds.org  Sat Feb 19 04:08:48 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 19 Feb 2022 11:08:48 +0700
Subject: [Slackbuilds-users] New submissions
In-Reply-To: <CA+da1or=HzhuKHfZHTa0Hv_aStQvtikUV3gzJx8s2wx-4d4stw@mail.gmail.com>
References: <CA+da1or=HzhuKHfZHTa0Hv_aStQvtikUV3gzJx8s2wx-4d4stw@mail.gmail.com>
Message-ID: <bd35b38d-a079-21d8-5590-936be2354b02@slackbuilds.org>

> I have a question about submissions (when we eventually arrive there).
> Are you going to do git patches or merge requests for submissions or
> are we keeping uploading tarballs for new submissions?

It will be available when 15.0 is ready
We are still working on making sure all scripts in our repository is
working well with Slackware 15.0.
With the amount of scripts we have (7/8k+), low amounts of
admins/contributors working on the repository will take some time

Remember that we all have our own personal life (and many other issues
to tackle in real life), so we do this work in our spare time. We tried
our best, but there's no fixed schedule on when will it be ready.

Please be patient and if you need something from our repository, take a
look on master branch where all the fun thing happening.


-- 
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/20220219/f228bffa/attachment-0001.asc>

From willysr at slackbuilds.org  Sat Feb 19 04:12:52 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 19 Feb 2022 11:12:52 +0700
Subject: [Slackbuilds-users] Updates for exhale (audio)
In-Reply-To: <Yg9E6N/CJAr8WIgy@ilium.andrews-corner.org>
References: <Yg9E6N/CJAr8WIgy@ilium.andrews-corner.org>
Message-ID: <12e06271-b7bf-8a3e-0c8f-17feaf3c6396@slackbuilds.org>

> I have seen a few patches posted here to update applications for 15.0,
> hopefully this is still an acceptable way to do things?
> 
> I attach a patch for exhale to update to latest version and remove an
> un-needed compiler flag. Patched against latest git master. 

Pushed to my branch
thanks


-- 
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/20220219/11f67cab/attachment.asc>

From willysr at slackbuilds.org  Sat Feb 19 04:17:52 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 19 Feb 2022 11:17:52 +0700
Subject: [Slackbuilds-users] Maintenance takeover pwgen,
 update DPF-Plugins, update amSynth
In-Reply-To: <e4e38a538e2526be794a794e6271febc@schoepfer.info>
References: <a9ef3a9ed157ea8476f704a213cd6b95@schoepfer.info>
 <20220218215832.68cc9ed1@elika.timp.com.au>
 <e4e38a538e2526be794a794e6271febc@schoepfer.info>
Message-ID: <1102c3c0-05d4-ab72-cc42-660438896f38@slackbuilds.org>

> as said in the subject.

merged


-- 
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/20220219/15023206/attachment.asc>

From slackbuilds at schoepfer.info  Sat Feb 19 06:04:30 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 19 Feb 2022 07:04:30 +0100
Subject: [Slackbuilds-users] Maintenance takeover pwgen,
 update DPF-Plugins, update amSynth
In-Reply-To: <1102c3c0-05d4-ab72-cc42-660438896f38@slackbuilds.org>
References: <a9ef3a9ed157ea8476f704a213cd6b95@schoepfer.info>
 <20220218215832.68cc9ed1@elika.timp.com.au>
 <e4e38a538e2526be794a794e6271febc@schoepfer.info>
 <1102c3c0-05d4-ab72-cc42-660438896f38@slackbuilds.org>
Message-ID: <5aa722582a1dc9e8f0bea63890b66dad@schoepfer.info>

On 2022-02-19 05:17, Willy Sudiarto Raharjo wrote:
>> as said in the subject.
> 
> merged

Hi,

sorry, i messed up pwgen.info, here is again the patch for pwgen 
including a corrected pwgen.info.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pwgen.patch2
Type: text/x-diff
Size: 5520 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220219/41dec48b/attachment.bin>

From slackbuilds at schoepfer.info  Sat Feb 19 06:19:30 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 19 Feb 2022 07:19:30 +0100
Subject: [Slackbuilds-users] New submissions
In-Reply-To: <bd35b38d-a079-21d8-5590-936be2354b02@slackbuilds.org>
References: <CA+da1or=HzhuKHfZHTa0Hv_aStQvtikUV3gzJx8s2wx-4d4stw@mail.gmail.com>
 <bd35b38d-a079-21d8-5590-936be2354b02@slackbuilds.org>
Message-ID: <b4c06b8a2f22b1f05e31f3a2bbf15b71@schoepfer.info>

On 2022-02-19 05:08, Willy Sudiarto Raharjo wrote:
>> I have a question about submissions (when we eventually arrive there).
>> Are you going to do git patches or merge requests for submissions or
>> are we keeping uploading tarballs for new submissions?
> 
> It will be available when 15.0 is ready

I guess the question was more about if submissions(besides tarballs 
submissions)
will also be possible as git patches,PR when SBo is opened again for 
submissions.
E.g. upload a patch instead of a tarball.

> We are still working on making sure all scripts in our repository is
> working well with Slackware 15.0.
> With the amount of scripts we have (7/8k+), low amounts of
> admins/contributors working on the repository will take some time

There may be more help from the community if the showstoppers were 
known.
I can check my buildscripts, ok, and then randomly check from 8k+ 
scripts
without knowing if its already on someone's todo list.

From andrew.david.strong at gmail.com  Sat Feb 19 06:32:10 2022
From: andrew.david.strong at gmail.com (andrew)
Date: Sat, 19 Feb 2022 17:32:10 +1100
Subject: [Slackbuilds-users] Updates for exhale (audio)
In-Reply-To: <12e06271-b7bf-8a3e-0c8f-17feaf3c6396@slackbuilds.org>
References: <Yg9E6N/CJAr8WIgy@ilium.andrews-corner.org>
 <12e06271-b7bf-8a3e-0c8f-17feaf3c6396@slackbuilds.org>
Message-ID: <YhCO6nhOtNuzHKev@ilium.andrews-corner.org>

On Sat, Feb 19, 2022 at 11:12:52AM +0700, Willy Sudiarto Raharjo wrote:

> > I have seen a few patches posted here to update applications for 15.0,
> > hopefully this is still an acceptable way to do things?
> > 
> > I attach a patch for exhale to update to latest version and remove an
> > un-needed compiler flag. Patched against latest git master. 
> 
> Pushed to my branch
> thanks
 
Thanks for your trouble and thanks for all the work on SBo...

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

From willysr at slackbuilds.org  Sat Feb 19 14:49:58 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 19 Feb 2022 21:49:58 +0700
Subject: [Slackbuilds-users] New submissions
In-Reply-To: <b4c06b8a2f22b1f05e31f3a2bbf15b71@schoepfer.info>
References: <CA+da1or=HzhuKHfZHTa0Hv_aStQvtikUV3gzJx8s2wx-4d4stw@mail.gmail.com>
 <bd35b38d-a079-21d8-5590-936be2354b02@slackbuilds.org>
 <b4c06b8a2f22b1f05e31f3a2bbf15b71@schoepfer.info>
Message-ID: <574f169a-0cf7-379b-8dfd-64e6cdeb8207@slackbuilds.org>

> I guess the question was more about if submissions(besides tarballs
> submissions)
> will also be possible as git patches,PR when SBo is opened again for
> submissions.
> E.g. upload a patch instead of a tarball.

For new scripts, it should go through normal submission form, but for
following updates, it can go via github/gitlab PR/MR features.

If we consider the maintainer is active enough and proficient using GIT,
we might allow direct push to personal branch in SBo git server like
some maintainers who actively pushed their updates to their branches
shown in https://git.slackbuilds.org/slackbuilds/


-- 
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/20220219/77493277/attachment-0001.asc>

From willysr at slackbuilds.org  Sat Feb 19 14:51:26 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 19 Feb 2022 21:51:26 +0700
Subject: [Slackbuilds-users] Maintenance takeover pwgen,
 update DPF-Plugins, update amSynth
In-Reply-To: <5aa722582a1dc9e8f0bea63890b66dad@schoepfer.info>
References: <a9ef3a9ed157ea8476f704a213cd6b95@schoepfer.info>
 <20220218215832.68cc9ed1@elika.timp.com.au>
 <e4e38a538e2526be794a794e6271febc@schoepfer.info>
 <1102c3c0-05d4-ab72-cc42-660438896f38@slackbuilds.org>
 <5aa722582a1dc9e8f0bea63890b66dad@schoepfer.info>
Message-ID: <19f767fe-d5a0-e86d-2a5c-acaf4b777dfd@slackbuilds.org>

> sorry, i messed up pwgen.info, here is again the patch for pwgen
> including a corrected pwgen.info.

This patch is not based on latest master branch
please rebase from latest master branch


-- 
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/20220219/190896a6/attachment.asc>

From slackbuilds at schoepfer.info  Sat Feb 19 18:19:17 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 19 Feb 2022 19:19:17 +0100
Subject: [Slackbuilds-users] Maintenance takeover pwgen,
 update DPF-Plugins, update amSynth
In-Reply-To: <19f767fe-d5a0-e86d-2a5c-acaf4b777dfd@slackbuilds.org>
References: <a9ef3a9ed157ea8476f704a213cd6b95@schoepfer.info>
 <20220218215832.68cc9ed1@elika.timp.com.au>
 <e4e38a538e2526be794a794e6271febc@schoepfer.info>
 <1102c3c0-05d4-ab72-cc42-660438896f38@slackbuilds.org>
 <5aa722582a1dc9e8f0bea63890b66dad@schoepfer.info>
 <19f767fe-d5a0-e86d-2a5c-acaf4b777dfd@slackbuilds.org>
Message-ID: <edbb2c519d722c76fbfee6ede1910ddb@schoepfer.info>

On 2022-02-19 15:51, Willy Sudiarto Raharjo wrote:
>> sorry, i messed up pwgen.info, here is again the patch for pwgen
>> including a corrected pwgen.info.
> 
> This patch is not based on latest master branch
> please rebase from latest master branch


Attached.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pwgen.patch
Type: text/x-diff
Size: 906 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220219/1f6d360f/attachment.bin>

From khronosschoty at posteo.org  Sat Feb 19 21:59:32 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Sat, 19 Feb 2022 21:59:32 +0000
Subject: [Slackbuilds-users] gcclegacy494 SlackBuild
Message-ID: <YhFoRDp6sxWELEiv@posteo.de>

Greetings, 

The purpose of for which I created the gcclegacy494 SlackBuild was to
build a supported compiler for Pale Moon. Since the Pale Moon devs are
depreciating gcc 4.9.4 as an officially supported compiler, and newer
versions of gcc are being officially targeted, I see no reason to
continue maintenance of that SlackBuild. I wouldn't mind continuing to
maintain it, if for some reason other people find it useful. If no one
else, however, finds its useful, I suggest removing it from the repo for
Slackware 15. 
-------------- 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/20220219/9b74eff6/attachment.asc>

From khronosschoty at posteo.org  Sat Feb 19 23:21:37 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Sat, 19 Feb 2022 23:21:37 +0000
Subject: [Slackbuilds-users] 0001-gemrb-updated-for-version-0.9.0.patch
Message-ID: <YhF7gYQFsGF6I7OQ@posteo.de>

Hi, 

Update for gemrb version 0.9.0
-------------- next part --------------
From 2c7db475becd73207855e3dfb6f9ee998a69233b Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Sat, 19 Feb 2022 15:02:11 -0800
Subject: [PATCH] gemrb updated for version 0.9.0

---
 games/gemrb/gemrb.SlackBuild | 7 ++++---
 games/gemrb/gemrb.info       | 6 +++---
 2 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/games/gemrb/gemrb.SlackBuild b/games/gemrb/gemrb.SlackBuild
index bd51d86333..7dcdf1eb4b 100644
--- a/games/gemrb/gemrb.SlackBuild
+++ b/games/gemrb/gemrb.SlackBuild
@@ -26,7 +26,8 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=gemrb
-VERSION=${VERSION:-0.8.5}
+VERSION=${VERSION:-0.9.0}
+SRCNAM=${SRCNAM:-$PRGNAM-$VERSION-sources}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -71,7 +72,7 @@ rm -rf $PKG
 mkdir -p $TMP $PKG $OUTPUT
 cd $TMP
 rm -rf $PRGNAM-$VERSION
-tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
+tar xvf $CWD/$SRCNAM.tar.gz
 cd $PRGNAM-$VERSION
 chown -R root:root .
 find -L . \
@@ -101,7 +102,7 @@ find $PKG/usr/man -type f -exec gzip -9 {} \;
 for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done
 
 mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
-cp -a AUTHORS COPYING ChangeLog HACKING INSTALL NEWS README gemrb/GemRB.cfg.* $PKG/usr/doc/$PRGNAM-$VERSION
+cp -a AUTHORS COPYING INSTALL NEWS README.md CONTRIBUTING.md gemrb/GemRB.cfg.* $PKG/usr/doc/$PRGNAM-$VERSION
 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
 
 mkdir -p $PKG/install
diff --git a/games/gemrb/gemrb.info b/games/gemrb/gemrb.info
index 39b25ac1c1..974537cccf 100644
--- a/games/gemrb/gemrb.info
+++ b/games/gemrb/gemrb.info
@@ -1,8 +1,8 @@
 PRGNAM="gemrb"
-VERSION="0.8.5"
+VERSION="0.9.0"
 HOMEPAGE="http://www.gemrb.org"
-DOWNLOAD="https://tenet.dl.sourceforge.net/project/gemrb/GemRB%20Sources/GemRB%200.8.5%20Sources/gemrb-0.8.5.tar.gz"
-MD5SUM="ee81ef46367202dbe0569c7a9a29e2b1"
+DOWNLOAD="https://sourceforge.net/projects/gemrb/files/Releases//0.9.0/gemrb-0.9.0-sources.tar.gz"
+MD5SUM="53edd434d8a59fcce3c4bac3a8d4c315"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""
-- 
2.35.1

-------------- 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/20220219/41f73cd9/attachment.asc>

From khronosschoty at posteo.org  Sat Feb 19 23:56:11 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Sat, 19 Feb 2022 23:56:11 +0000
Subject: [Slackbuilds-users] beetle-psx-libretro SlackBuild
Message-ID: <YhGDm+oG5IHKXmNE@posteo.de>

Greetings, 

I'm not sure if anyone is currently maintaining  beetle-psx-libretro, but
if it hasn't found a new maintainer I would adopt it. 
-------------- 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/20220219/50d8504f/attachment.asc>

From khronosschoty at posteo.org  Sun Feb 20 00:09:00 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Sun, 20 Feb 2022 00:09:00 +0000
Subject: [Slackbuilds-users] Adopting orphaned SlackBuilds
Message-ID: <YhGGnAo9FVruEyVc@posteo.de>

In addition to beetle-psx-libretro I would also be interested in adopting the following 
(if they are still in need of a new maintainer):

libretro-reicast
4do-libretro
beetle-saturn-libretro
bsnes-mercury
libretro-desmume
libretro-yabause

-------------- 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/20220220/0f924bff/attachment.asc>

From khronosschoty at posteo.org  Sun Feb 20 00:16:52 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Sun, 20 Feb 2022 00:16:52 +0000
Subject: [Slackbuilds-users] Adopting orphaned SlackBuilds
Message-ID: <YhGIdINi6zgFa2NF@posteo.de>

Hi, 

Also I do not see pcsx2 in the master branch of SlackBuilds.org, so in
case that is also needs a new maintainer, I would take that one as well. 
-------------- 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/20220220/9032fa81/attachment.asc>

From willysr at slackbuilds.org  Sun Feb 20 02:40:58 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 20 Feb 2022 09:40:58 +0700
Subject: [Slackbuilds-users] 0001-gemrb-updated-for-version-0.9.0.patch
In-Reply-To: <YhF7gYQFsGF6I7OQ@posteo.de>
References: <YhF7gYQFsGF6I7OQ@posteo.de>
Message-ID: <f0c01a5e-73be-2f4c-428a-94b618bcea8f@slackbuilds.org>

> Update for gemrb version 0.9.0

merged


-- 
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/20220220/9dd5cac5/attachment-0001.asc>

From slackbuilds at schoepfer.info  Sun Feb 20 19:16:40 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sun, 20 Feb 2022 20:16:40 +0100
Subject: [Slackbuilds-users] pygame fix for build with new portimidi 2.0.2
Message-ID: <88011e8a3b6d69bd1b43d8e29a53af7c@schoepfer.info>

Hi,

not my buildscript, since portmidi 2.0.2(updated yesterday) libporttime 
is included in libportmidi
and pygame doesn't build anymore without this patch.

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pygame.patch
Type: text/x-diff
Size: 631 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220220/19ab4213/attachment.bin>

From d.zlatanidis at gmail.com  Sun Feb 20 19:36:27 2022
From: d.zlatanidis at gmail.com (Dimitris Zlatanidis)
Date: Sun, 20 Feb 2022 21:36:27 +0200
Subject: [Slackbuilds-users] pygame fix for build with new portimidi
 2.0.2
In-Reply-To: <88011e8a3b6d69bd1b43d8e29a53af7c@schoepfer.info>
References: <88011e8a3b6d69bd1b43d8e29a53af7c@schoepfer.info>
Message-ID: <b2e29459-02b0-8ef6-d753-2d4d274fc668@gmail.com>

Hi,
Thanks for sharing it, I'll test it!

Cheers,
Dimitris

On 2/20/22 21:16, Franzen via SlackBuilds-users wrote:
> Hi,
>
> not my buildscript, since portmidi 2.0.2(updated yesterday) 
> libporttime is included in libportmidi
> and pygame doesn't build anymore without this patch.
>
> 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/
>

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


From phalange at komputermatrix.com  Sun Feb 20 23:39:20 2022
From: phalange at komputermatrix.com (Andrew Payne)
Date: Sun, 20 Feb 2022 18:39:20 -0500 (EST)
Subject: [Slackbuilds-users] Nextcloud client
Message-ID: <e0f184f4-a0a9-e69a-c461-24689e4f23c8@imap.fatcow.com>

Hi folks, I reached out to the maintainer of Nextcloud Desktop Client two 
weeks ago, but no response.

I keep a current build of it, so I'd be willing to take over maintenance 
if no one objects.

-A


From willysr at slackbuilds.org  Mon Feb 21 03:00:50 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 21 Feb 2022 10:00:50 +0700
Subject: [Slackbuilds-users] Nextcloud client
In-Reply-To: <e0f184f4-a0a9-e69a-c461-24689e4f23c8@imap.fatcow.com>
References: <e0f184f4-a0a9-e69a-c461-24689e4f23c8@imap.fatcow.com>
Message-ID: <16fe41c8-e3a5-8fb6-95dd-f613b63e3efb@slackbuilds.org>

> Hi folks, I reached out to the maintainer of Nextcloud Desktop Client
> two weeks ago, but no response.
> 
> I keep a current build of it, so I'd be willing to take over maintenance
> if no one objects.

Go for it


-- 
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/20220221/b4321f08/attachment.asc>

From ozan.turkyilmaz at gmail.com  Mon Feb 21 07:49:18 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Mon, 21 Feb 2022 10:49:18 +0300
Subject: [Slackbuilds-users] libupnp and libupnp-legacy
Message-ID: <CA+da1op+1+7y5ZYJSHXxKYzy0PZ2b_qm_teK6ohFAS+zyJoZaA@mail.gmail.com>

Hello All,

I was looking into how I can get those two installed together. (It's shame
we can't install them together)
With thinkering with configure scripts, I decided to put it on /usr/legacy
prefix with /usr/lib/legacy. It's possible
to pass /usr/lib/legacy/pkgconfig to PKG_CONFIG_PATH during configuration
of other programs (R?ght now
it is only linphone needs libupnp-legacy as far as I can find).

Folder places are for testing only. Maybe putting the libupnp-legacy in
/opt/libupnp-legacy with all the libs is
a better idea.

Regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220221/4597f113/attachment.htm>

From slackbuilds at schoepfer.info  Mon Feb 21 07:53:45 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 21 Feb 2022 08:53:45 +0100
Subject: [Slackbuilds-users] xjadeo fix for build with new portimidi 2.0.2
Message-ID: <1789bfa5496c5d8ddf5cf29e2b8ae58c@schoepfer.info>

Hi,

not my buildscript, fix for build with new portmidi 2.0.2.

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xjadeo.patch
Type: text/x-diff
Size: 520 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220221/8e4bef3f/attachment.bin>

From slackbuilds at schoepfer.info  Mon Feb 21 09:06:32 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 21 Feb 2022 10:06:32 +0100
Subject: [Slackbuilds-users] ultimatestunts build fix
Message-ID: <354e48679f5b1b7426df740863633c5e@schoepfer.info>

Hi,

as said in the subject, patch attached.
Btw. my patches are sometimes committed with Name Frazen, but it is
Franzen.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ultimatestunts.patch
Type: text/x-diff
Size: 1102 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220221/8cbae74f/attachment.bin>

From matteo.bernardini at gmail.com  Mon Feb 21 13:15:15 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 21 Feb 2022 14:15:15 +0100
Subject: [Slackbuilds-users] xjadeo fix for build with new portimidi
 2.0.2
In-Reply-To: <1789bfa5496c5d8ddf5cf29e2b8ae58c@schoepfer.info>
References: <1789bfa5496c5d8ddf5cf29e2b8ae58c@schoepfer.info>
Message-ID: <CAPsDuS7DKDYnm7dQ-ttw5vL1i9npHT2K=LxXbYBB67LE1Dujhw@mail.gmail.com>

hi Johannes,

maybe I'm missing something I just tried but it seems to link to
porttime already if it finds portmidi installed...

Matteo

Il giorno lun 21 feb 2022 alle ore 08:53 Franzen via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> ha scritto:
>
> Hi,
>
> not my buildscript, fix for build with new portmidi 2.0.2.
>
> 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/
>

From matteo.bernardini at gmail.com  Mon Feb 21 13:24:13 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 21 Feb 2022 14:24:13 +0100
Subject: [Slackbuilds-users] ultimatestunts build fix
In-Reply-To: <354e48679f5b1b7426df740863633c5e@schoepfer.info>
References: <354e48679f5b1b7426df740863633c5e@schoepfer.info>
Message-ID: <CAPsDuS7wUTuqRWjxOFe_bn8Thd=G1L=bCN2p7wcjuOhQOxNH4Q@mail.gmail.com>

thanks, pushed!

Matteo

Il giorno lun 21 feb 2022 alle ore 10:06 Franzen via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> ha scritto:
>
> Hi,
>
> as said in the subject, patch attached.
> Btw. my patches are sometimes committed with Name Frazen, but it is
> Franzen._______________________________________________
> 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 fernando.lopezjr at gmail.com  Mon Feb 21 15:33:41 2022
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Mon, 21 Feb 2022 08:33:41 -0700
Subject: [Slackbuilds-users] Drivers for ACR122U
Message-ID: <CALrQ46D=iAxDvom7Q-B6-FX_24EA=LCg5kn+G3MCBR=dt6uW+Q@mail.gmail.com>

can you guys help me re-package this driver... i don't know the correct
paths/locations to place  the driver file... the rule file obviously goes
in the /etc/udev/rules.d folder but other than that i don't know where
everything goes.

https://www.acs.com.hk/download-driver-unified/12030/ACS-Unified-Driver-Lnx-Mac-118-P.zip

https://www.acs.com.hk/en/driver/3/acr122u-usb-nfc-reader/


thank you.

-- 

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

From matteo.bernardini at gmail.com  Mon Feb 21 15:45:34 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 21 Feb 2022 16:45:34 +0100
Subject: [Slackbuilds-users] Drivers for ACR122U
In-Reply-To: <CALrQ46D=iAxDvom7Q-B6-FX_24EA=LCg5kn+G3MCBR=dt6uW+Q@mail.gmail.com>
References: <CALrQ46D=iAxDvom7Q-B6-FX_24EA=LCg5kn+G3MCBR=dt6uW+Q@mail.gmail.com>
Message-ID: <CAPsDuS5MG19K5cg8VxHMwvnRRWKYYt3-W3V6Bn4kq0OTemMnQw@mail.gmail.com>

I confess I haven't had a look at that proprietary thingie but have
you had a look instead at what other distributions do?

arch, for example, packages acsccid

https://acsccid.sourceforge.io/

https://github.com/archlinux/svntogit-community/blob/packages/acsccid/trunk/PKGBUILD

Il giorno lun 21 feb 2022 alle ore 16:34 Fernando Lopez
<fernando.lopezjr at gmail.com> ha scritto:
>
> can you guys help me re-package this driver... i don't know the correct paths/locations to place  the driver file... the rule file obviously goes in the /etc/udev/rules.d folder but other than that i don't know where everything goes.
>
> https://www.acs.com.hk/download-driver-unified/12030/ACS-Unified-Driver-Lnx-Mac-118-P.zip
>
> https://www.acs.com.hk/en/driver/3/acr122u-usb-nfc-reader/
>
>
> thank you.
>
> --
>
> ------------
> Regards,
>     Fernando Lopez Jr.
> _______________________________________________
> 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 lramos.prof at yahoo.com.br  Mon Feb 21 16:14:30 2022
From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos)
Date: Mon, 21 Feb 2022 13:14:30 -0300
Subject: [Slackbuilds-users] Drivers for ACR122U
In-Reply-To: <CAPsDuS5MG19K5cg8VxHMwvnRRWKYYt3-W3V6Bn4kq0OTemMnQw@mail.gmail.com>
References: <CALrQ46D=iAxDvom7Q-B6-FX_24EA=LCg5kn+G3MCBR=dt6uW+Q@mail.gmail.com>
 <CAPsDuS5MG19K5cg8VxHMwvnRRWKYYt3-W3V6Bn4kq0OTemMnQw@mail.gmail.com>
Message-ID: <YhO6ZowdHvQFYKpy@giustizia.lan>

Hello all,

don't know if this is exactly about this question, but proprietary Linux
kernel drivers are usually placed at:

   /lib/modules/${kernel_version}/misc

you already know that ${kernel_version} can be extracted using:

   $(uname -r)

for the running kernel version.

It's advisable that after installation, one runs as root:

   depmod -a

to update some things in the kernel configuration (for instance, to
allow modprobe ${module_name} runs properly). Usually depmod -a can be
placed in the (post-)install script.

Hope it helps,

Luiz Ramos
Sao Paulo - Brazil
lramos dot prof at yahoo dot com dot br


On Mon, Feb 21, 2022 at 04:45:34PM +0100, Matteo Bernardini wrote:
> I confess I haven't had a look at that proprietary thingie but have
> you had a look instead at what other distributions do?
> 
> arch, for example, packages acsccid
> 
> https://acsccid.sourceforge.io/
> 
> https://github.com/archlinux/svntogit-community/blob/packages/acsccid/trunk/PKGBUILD
> 
> Il giorno lun 21 feb 2022 alle ore 16:34 Fernando Lopez
> <fernando.lopezjr at gmail.com> ha scritto:
> >
> > can you guys help me re-package this driver... i don't know the correct paths/locations to place  the driver file... the rule file obviously goes in the /etc/udev/rules.d folder but other than that i don't know where everything goes.
> >
> > https://www.acs.com.hk/download-driver-unified/12030/ACS-Unified-Driver-Lnx-Mac-118-P.zip
> >
> > https://www.acs.com.hk/en/driver/3/acr122u-usb-nfc-reader/
> >
> >
> > thank you.
> >
> > --
> >
> > ------------
> > Regards,
> >     Fernando Lopez Jr.
> > _______________________________________________
> > 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 slackbuilds at schoepfer.info  Mon Feb 21 16:56:13 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 21 Feb 2022 17:56:13 +0100
Subject: [Slackbuilds-users] xjadeo fix for build with new portimidi
 2.0.2
In-Reply-To: <CAPsDuS7DKDYnm7dQ-ttw5vL1i9npHT2K=LxXbYBB67LE1Dujhw@mail.gmail.com>
References: <1789bfa5496c5d8ddf5cf29e2b8ae58c@schoepfer.info>
 <CAPsDuS7DKDYnm7dQ-ttw5vL1i9npHT2K=LxXbYBB67LE1Dujhw@mail.gmail.com>
Message-ID: <e0374ee2b415a56ded88bcab14ce77e3@schoepfer.info>

Hi Matteo,

> maybe I'm missing something I just tried but it seems to link to
> porttime already if it finds portmidi installed...

This seems to be the case since this commit to portmidi: 
https://git.slackbuilds.org/slackbuilds/patch/?id=ea1c6894e221ed242ecd9308f0c5cf9779961463

I think it would be better to fix the apps to use libportmidi instead of 
rely on a compatibility link(and remove that link again) to libportmidi.
I grep'ed through the tree, following apps use portmidi as dep or 
optional:
MuseScore
hatari
hydrogen
mame
mixxx
odamex
pd
prboom-plus
pygame
seq24
xjadeo

 From these, following i have build sucessfully(because already patched, 
or because these don't look for libporttime) without the compatibility 
link: xjadeo,seq24,pygame,MuseScore,hatari.

My idea was to also check/patch 
hydrogen,mame,mixxx,odamex,pd,prboom-plus.
This is the best time to do this i think.

What do you think?

Johannes

From dave at slackbuilds.org  Mon Feb 21 18:07:30 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Mon, 21 Feb 2022 18:07:30 +0000
Subject: [Slackbuilds-users] xjadeo fix for build with new portimidi
 2.0.2
In-Reply-To: <e0374ee2b415a56ded88bcab14ce77e3@schoepfer.info>
References: <1789bfa5496c5d8ddf5cf29e2b8ae58c@schoepfer.info>
 <CAPsDuS7DKDYnm7dQ-ttw5vL1i9npHT2K=LxXbYBB67LE1Dujhw@mail.gmail.com>
 <e0374ee2b415a56ded88bcab14ce77e3@schoepfer.info>
Message-ID: <20220221180730.GI4508@localhost>

On 21/02/22 17:56,
Franzen via SlackBuilds-users <slackbuilds-users at slackbuilds.org> put forth the proposition:
> Hi Matteo,
> > maybe I'm missing something I just tried but it seems to link to
> > porttime already if it finds portmidi installed...
> This seems to be the case since this commit to portmidi: https://git.slackbuilds.org/slackbuilds/patch/?id=ea1c6894e221ed242ecd9308f0c5cf9779961463
> I think it would be better to fix the apps to use libportmidi instead of
> rely on a compatibility link(and remove that link again) to libportmidi.
> I grep'ed through the tree, following apps use portmidi as dep or optional:
> MuseScore
> hatari
> hydrogen
> mame
> mixxx
> odamex
> pd
> prboom-plus
> pygame
> seq24
> xjadeo

I pushed an update for hydrogen and there was also an update to
pygame recently.  Portmidi is one of mine so I'll go through the list
and see which fail.

--
Dave

From fernando.lopezjr at gmail.com  Mon Feb 21 18:33:36 2022
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Mon, 21 Feb 2022 11:33:36 -0700
Subject: [Slackbuilds-users] libnfc submission.
Message-ID: <CALrQ46CG71_9ue=iEtV78pGTwgObCMS+BZdUAgtkfOSWHCSHTw@mail.gmail.com>

can we add this to the repo? thank you.

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220221/76e50074/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libnfc.tar.xz
Type: application/x-xz
Size: 2696 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220221/76e50074/attachment-0001.xz>

From fernando.lopezjr at gmail.com  Mon Feb 21 21:21:24 2022
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Mon, 21 Feb 2022 14:21:24 -0700
Subject: [Slackbuilds-users] Drivers for ACR122U
In-Reply-To: <YhO6ZowdHvQFYKpy@giustizia.lan>
References: <CALrQ46D=iAxDvom7Q-B6-FX_24EA=LCg5kn+G3MCBR=dt6uW+Q@mail.gmail.com>
 <CAPsDuS5MG19K5cg8VxHMwvnRRWKYYt3-W3V6Bn4kq0OTemMnQw@mail.gmail.com>
 <YhO6ZowdHvQFYKpy@giustizia.lan>
Message-ID: <CALrQ46ACuTKVZYesj-cF9hK6t=bxY__9jYk1mQ=X9xM+_OyavA@mail.gmail.com>

thank you guys for the help... it was my libnfc that wasn't working.

On Mon, Feb 21, 2022 at 9:13 AM Luiz Carlos Ramos via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> Hello all,
>
> don't know if this is exactly about this question, but proprietary Linux
> kernel drivers are usually placed at:
>
>    /lib/modules/${kernel_version}/misc
>
> you already know that ${kernel_version} can be extracted using:
>
>    $(uname -r)
>
> for the running kernel version.
>
> It's advisable that after installation, one runs as root:
>
>    depmod -a
>
> to update some things in the kernel configuration (for instance, to
> allow modprobe ${module_name} runs properly). Usually depmod -a can be
> placed in the (post-)install script.
>
> Hope it helps,
>
> Luiz Ramos
> Sao Paulo - Brazil
> lramos dot prof at yahoo dot com dot br
>
>
> On Mon, Feb 21, 2022 at 04:45:34PM +0100, Matteo Bernardini wrote:
> > I confess I haven't had a look at that proprietary thingie but have
> > you had a look instead at what other distributions do?
> >
> > arch, for example, packages acsccid
> >
> > https://acsccid.sourceforge.io/
> >
> >
> https://github.com/archlinux/svntogit-community/blob/packages/acsccid/trunk/PKGBUILD
> >
> > Il giorno lun 21 feb 2022 alle ore 16:34 Fernando Lopez
> > <fernando.lopezjr at gmail.com> ha scritto:
> > >
> > > can you guys help me re-package this driver... i don't know the
> correct paths/locations to place  the driver file... the rule file
> obviously goes in the /etc/udev/rules.d folder but other than that i don't
> know where everything goes.
> > >
> > >
> https://www.acs.com.hk/download-driver-unified/12030/ACS-Unified-Driver-Lnx-Mac-118-P.zip
> > >
> > > https://www.acs.com.hk/en/driver/3/acr122u-usb-nfc-reader/
> > >
> > >
> > > thank you.
> > >
> > > --
> > >
> > > ------------
> > > Regards,
> > >     Fernando Lopez Jr.
> > > _______________________________________________
> > > 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/
>
>

-- 

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

From khronosschoty at posteo.org  Mon Feb 21 22:59:59 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Mon, 21 Feb 2022 22:59:59 +0000
Subject: [Slackbuilds-users] 0001-desktop-noice-updated-for-version-0.8.patch
Message-ID: <YhQZb9Jpx0Dfsvpc@posteo.de>

noice update to version 0.8
-------------- next part --------------
>From a03431c4dbcc534ae66848e7a7f3c49a416f1926 Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Mon, 21 Feb 2022 14:52:41 -0800
Subject: [PATCH 1/1] desktop/noice updated for version 0.8

---
 desktop/noice/noice.SlackBuild | 4 ++--
 desktop/noice/noice.info       | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/desktop/noice/noice.SlackBuild b/desktop/noice/noice.SlackBuild
index e53569ee53c..cd2f8770eb6 100644
--- a/desktop/noice/noice.SlackBuild
+++ b/desktop/noice/noice.SlackBuild
@@ -2,7 +2,7 @@
 
 # Slackware build script for noice
 
-# Copyright 2018 Vasily Sora USA
+# Copyright 2018,2022 Vasily Sora USA
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -25,7 +25,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=noice
-VERSION=${VERSION:-2018.04.09}
+VERSION=${VERSION:-0.8}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
diff --git a/desktop/noice/noice.info b/desktop/noice/noice.info
index 128489c05eb..1414d376eef 100644
--- a/desktop/noice/noice.info
+++ b/desktop/noice/noice.info
@@ -1,8 +1,8 @@
 PRGNAM="noice"
-VERSION="2018.04.09"
+VERSION="0.8"
 HOMEPAGE="http://git.2f30.org/noice/"
-DOWNLOAD="http://repo.khronosschoty.org/Slackware/stuff/noice/noice-2018.04.09.tar.gz"
-MD5SUM="a0b5a8b9eb4073d8ca5921d366c74f07"
+DOWNLOAD="http://repo.schotynet.org/sources/noice-0.8.tar.gz"
+MD5SUM="61becf0244af61c402a9a46a5dea8bea"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""
-- 
2.35.1


From rworkman at slackbuilds.org  Mon Feb 21 23:09:55 2022
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 21 Feb 2022 17:09:55 -0600
Subject: [Slackbuilds-users] libnfc submission.
In-Reply-To: <CALrQ46CG71_9ue=iEtV78pGTwgObCMS+BZdUAgtkfOSWHCSHTw@mail.gmail.com>
References: <CALrQ46CG71_9ue=iEtV78pGTwgObCMS+BZdUAgtkfOSWHCSHTw@mail.gmail.com>
Message-ID: <20220221170955.6e78141c@home.rlworkman.net>

On Mon, 21 Feb 2022 11:33:36 -0700
Fernando Lopez <fernando.lopezjr at gmail.com> wrote:

> can we add this to the repo? thank you.


It looks like it needs at least one dep that isn't documented: pcsc-lite

Re the move from $PKG/usr/lib to $PKG/usr/lib64, try adding this to the cmake options:

  -DCMAKE_INSTALL_LIBDIR=/usr/lib${LIBDIRSUFFIX}

Use /lib/udev instead of /etc/udev

Use /lib/modprobe.d instead of /etc/modprobe.d

This should be sufficient for the docs copying:

cp -a \
  AUTHORS COPYING ChangeLog HACKING.md NEWS.md README.md manual-test-results.txt \
  $PKG/usr/doc/$PRGNAM-$VERSION


Please address the above concerns and send an updated try :-)

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

From rworkman at slackbuilds.org  Mon Feb 21 23:13:03 2022
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 21 Feb 2022 17:13:03 -0600
Subject: [Slackbuilds-users]
 0001-desktop-noice-updated-for-version-0.8.patch
In-Reply-To: <YhQZb9Jpx0Dfsvpc@posteo.de>
References: <YhQZb9Jpx0Dfsvpc@posteo.de>
Message-ID: <20220221171303.57a6b298@home.rlworkman.net>

On Mon, 21 Feb 2022 22:59:59 +0000
khronosschoty <khronosschoty at posteo.org> wrote:

> noice update to version 0.8


Updated in my git branch; thanks!

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

From rasp at spitzner.org  Mon Feb 21 23:01:29 2022
From: rasp at spitzner.org (Ralph Spitzner)
Date: Tue, 22 Feb 2022 00:01:29 +0100
Subject: [Slackbuilds-users] submission
Message-ID: <9ee586ba-d881-756e-2ce4-44636b20fc7a@spitzner.org>

where do submissions go if:
Submissions are closed while we are working to prepare for Slackware 15.0.
?
The one i'd have is for 15.0 anyway...



     -rasp

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

From khronosschoty at posteo.org  Mon Feb 21 23:31:47 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Mon, 21 Feb 2022 23:31:47 +0000
Subject: [Slackbuilds-users] palemoon-bin SlackBuild
Message-ID: <YhQg43wz+tJ8of99@posteo.de>

hi,

palemoon binaries are provided in two flavors gtk2 and gtk3. I was
wondering what the best way to support both of them would be. Should I
just include downloads to both? or should these be spun out out into two
different SlackBuilds?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 870 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220221/88a12900/attachment.asc>

From fernando.lopezjr at gmail.com  Mon Feb 21 23:54:35 2022
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Mon, 21 Feb 2022 16:54:35 -0700
Subject: [Slackbuilds-users] libnfc submission.
In-Reply-To: <20220221170955.6e78141c@home.rlworkman.net>
References: <CALrQ46CG71_9ue=iEtV78pGTwgObCMS+BZdUAgtkfOSWHCSHTw@mail.gmail.com>
 <20220221170955.6e78141c@home.rlworkman.net>
Message-ID: <CALrQ46AvbWhAhduFoFx5w-LAg99tVeWyUC1C5XujbW764KFNtA@mail.gmail.com>

here you go! thanks! :)

On Mon, Feb 21, 2022 at 4:10 PM Robby Workman <rworkman at slackbuilds.org>
wrote:

> On Mon, 21 Feb 2022 11:33:36 -0700
> Fernando Lopez <fernando.lopezjr at gmail.com> wrote:
>
> > can we add this to the repo? thank you.
>
>
> It looks like it needs at least one dep that isn't documented: pcsc-lite
>
> Re the move from $PKG/usr/lib to $PKG/usr/lib64, try adding this to the
> cmake options:
>
>   -DCMAKE_INSTALL_LIBDIR=/usr/lib${LIBDIRSUFFIX}
>
> Use /lib/udev instead of /etc/udev
>
> Use /lib/modprobe.d instead of /etc/modprobe.d
>
> This should be sufficient for the docs copying:
>
> cp -a \
>   AUTHORS COPYING ChangeLog HACKING.md NEWS.md README.md
> manual-test-results.txt \
>   $PKG/usr/doc/$PRGNAM-$VERSION
>
>
> Please address the above concerns and send an updated try :-)
>
> -RW
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220221/4d054f4c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libnfc.tar.xz
Type: application/x-xz
Size: 2672 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220221/4d054f4c/attachment-0001.xz>

From fernando.lopezjr at gmail.com  Mon Feb 21 23:56:31 2022
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Mon, 21 Feb 2022 16:56:31 -0700
Subject: [Slackbuilds-users] submission
In-Reply-To: <9ee586ba-d881-756e-2ce4-44636b20fc7a@spitzner.org>
References: <9ee586ba-d881-756e-2ce4-44636b20fc7a@spitzner.org>
Message-ID: <CALrQ46CDBHi=cvDgs2u=k7L4+u24CCmFYzHg5DfwwF2GQhf6jw@mail.gmail.com>

they are closed at the moment. they will re-open once we fix all current
packages.

On Mon, Feb 21, 2022 at 4:15 PM Ralph Spitzner <rasp at spitzner.org> wrote:

> where do submissions go if:
> Submissions are closed while we are working to prepare for Slackware 15.0.
> ?
> The one i'd have is for 15.0 anyway...
>
>
>
>      -rasp
>
> --
> "ich brauche keine Verschluesselung, mich versteht eh keiner"  -Icke
> _______________________________________________
> 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/20220221/ffe12161/attachment.htm>

From rworkman at slackbuilds.org  Tue Feb 22 01:22:25 2022
From: rworkman at slackbuilds.org (Robby Workman)
Date: Mon, 21 Feb 2022 19:22:25 -0600
Subject: [Slackbuilds-users] libnfc submission.
In-Reply-To: <CALrQ46AvbWhAhduFoFx5w-LAg99tVeWyUC1C5XujbW764KFNtA@mail.gmail.com>
References: <CALrQ46CG71_9ue=iEtV78pGTwgObCMS+BZdUAgtkfOSWHCSHTw@mail.gmail.com>
 <20220221170955.6e78141c@home.rlworkman.net>
 <CALrQ46AvbWhAhduFoFx5w-LAg99tVeWyUC1C5XujbW764KFNtA@mail.gmail.com>
Message-ID: <20220221192225.6945605c@home.rlworkman.net>

Added in my git branch; thanks!

-RW

On Mon, 21 Feb 2022 16:54:35 -0700
Fernando Lopez <fernando.lopezjr at gmail.com> wrote:

> here you go! thanks! :)
> 
> On Mon, Feb 21, 2022 at 4:10 PM Robby Workman
> <rworkman at slackbuilds.org> wrote:
> 
> > On Mon, 21 Feb 2022 11:33:36 -0700
> > Fernando Lopez <fernando.lopezjr at gmail.com> wrote:
> >  
> > > can we add this to the repo? thank you.  
> >
> >
> > It looks like it needs at least one dep that isn't documented:
> > pcsc-lite
> >
> > Re the move from $PKG/usr/lib to $PKG/usr/lib64, try adding this to
> > the cmake options:
> >
> >   -DCMAKE_INSTALL_LIBDIR=/usr/lib${LIBDIRSUFFIX}
> >
> > Use /lib/udev instead of /etc/udev
> >
> > Use /lib/modprobe.d instead of /etc/modprobe.d
> >
> > This should be sufficient for the docs copying:
> >
> > cp -a \
> >   AUTHORS COPYING ChangeLog HACKING.md NEWS.md README.md
> > manual-test-results.txt \
> >   $PKG/usr/doc/$PRGNAM-$VERSION
> >
> >
> > Please address the above concerns and send an updated try :-)
> >
> > -RW
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives -
> > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ -
> > https://slackbuilds.org/faq/
> >
> >  
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220221/7a8586ae/attachment.asc>

From fernando.lopezjr at gmail.com  Tue Feb 22 01:53:29 2022
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Mon, 21 Feb 2022 18:53:29 -0700
Subject: [Slackbuilds-users] libnfc submission.
In-Reply-To: <20220221192225.6945605c@home.rlworkman.net>
References: <CALrQ46CG71_9ue=iEtV78pGTwgObCMS+BZdUAgtkfOSWHCSHTw@mail.gmail.com>
 <20220221170955.6e78141c@home.rlworkman.net>
 <CALrQ46AvbWhAhduFoFx5w-LAg99tVeWyUC1C5XujbW764KFNtA@mail.gmail.com>
 <20220221192225.6945605c@home.rlworkman.net>
Message-ID: <CALrQ46CgYe=7pxYS2YorzLO9-aT_RtLG6y_kxxK4jpSBcHRbCQ@mail.gmail.com>

thank you buddy! :)

On Mon, Feb 21, 2022 at 6:22 PM Robby Workman <rworkman at slackbuilds.org>
wrote:

> Added in my git branch; thanks!
>
> -RW
>
> On Mon, 21 Feb 2022 16:54:35 -0700
> Fernando Lopez <fernando.lopezjr at gmail.com> wrote:
>
> > here you go! thanks! :)
> >
> > On Mon, Feb 21, 2022 at 4:10 PM Robby Workman
> > <rworkman at slackbuilds.org> wrote:
> >
> > > On Mon, 21 Feb 2022 11:33:36 -0700
> > > Fernando Lopez <fernando.lopezjr at gmail.com> wrote:
> > >
> > > > can we add this to the repo? thank you.
> > >
> > >
> > > It looks like it needs at least one dep that isn't documented:
> > > pcsc-lite
> > >
> > > Re the move from $PKG/usr/lib to $PKG/usr/lib64, try adding this to
> > > the cmake options:
> > >
> > >   -DCMAKE_INSTALL_LIBDIR=/usr/lib${LIBDIRSUFFIX}
> > >
> > > Use /lib/udev instead of /etc/udev
> > >
> > > Use /lib/modprobe.d instead of /etc/modprobe.d
> > >
> > > This should be sufficient for the docs copying:
> > >
> > > cp -a \
> > >   AUTHORS COPYING ChangeLog HACKING.md NEWS.md README.md
> > > manual-test-results.txt \
> > >   $PKG/usr/doc/$PRGNAM-$VERSION
> > >
> > >
> > > Please address the above concerns and send an updated try :-)
> > >
> > > -RW
> > > _______________________________________________
> > > SlackBuilds-users mailing list
> > > SlackBuilds-users at slackbuilds.org
> > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > > Archives -
> > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ -
> > > https://slackbuilds.org/faq/
> > >
> > >
> >
> _______________________________________________
> 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/20220221/e8cb3ac5/attachment.htm>

From dave at slackbuilds.org  Tue Feb 22 03:30:38 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Tue, 22 Feb 2022 03:30:38 +0000
Subject: [Slackbuilds-users] xjadeo fix for build with new portimidi
 2.0.2
In-Reply-To: <20220221180730.GI4508@localhost>
References: <1789bfa5496c5d8ddf5cf29e2b8ae58c@schoepfer.info>
 <CAPsDuS7DKDYnm7dQ-ttw5vL1i9npHT2K=LxXbYBB67LE1Dujhw@mail.gmail.com>
 <e0374ee2b415a56ded88bcab14ce77e3@schoepfer.info>
 <20220221180730.GI4508@localhost>
Message-ID: <20220222033038.GJ4508@localhost>

MuseScore
hatari
hydrogen
mame
mixxx
odamex
pd
prboom-plus
pygame
seq24
xjadeo

All checked and working.

--
Dave

From andrew.david.strong at gmail.com  Tue Feb 22 06:02:42 2022
From: andrew.david.strong at gmail.com (andrew)
Date: Tue, 22 Feb 2022 17:02:42 +1100
Subject: [Slackbuilds-users] Update for aom (multimedia)
Message-ID: <YhR8gmgklaYZXCw3@ilium.andrews-corner.org>

Hi,

Attached is a patch against git master for aom (multimedia). A few
notes:

 1. I have again hosted the source tarball myself as previous
    experience has been that the automatic generation of a tarball by
    Googlesource results in differing md5sums. I see they stopped
    hosting actual tarballs in 2013...
 2. I have made some small changes to the install paths, an error that
    I made in old versions of the SlackBuild was generating a faulty
    pkconfig file. This may still be an issue in the script for 14.2
    which I will check when the dust settles with 15.0.

Please let me know of any issues...

Andrew Strong
-- 
You think that's air you're breathing now?
-------------- next part --------------
diff --git a/multimedia/aom/README b/multimedia/aom/README
index 40b686da..dbddf20c 100644
--- a/multimedia/aom/README
+++ b/multimedia/aom/README
@@ -3,8 +3,5 @@ video transmission over the Internet. AV1 is planned to surpass
 VP9 and also to eventually be a competitor with HEVC/H.265.
 
 This script builds the encoder aomenc, the decoder aomdec as well
-as shared libraries which can be utilised by recent versions of
+as shared libraries which can be utilised by suitable versions of
 both FFmpeg and vlc.
-
-Note: 'aom' replaces and upgrades 'libaom'; make sure 'libaom' is
-removed before using this SlackBuild.
diff --git a/multimedia/aom/aom.SlackBuild b/multimedia/aom/aom.SlackBuild
index b986c266..ac01eefa 100644
--- a/multimedia/aom/aom.SlackBuild
+++ b/multimedia/aom/aom.SlackBuild
@@ -2,7 +2,7 @@
 # ----------------------------------------------------------------------
 # Slackware build script for aom
 #
-# Copyright (c) 2018-2021 Andrew Strong, Blue Mountains, Australia.
+# Copyright (c) 2018-2022 Andrew Strong, Blue Mountains, Australia.
 #
 #   Permission to use, copy, modify, and distribute this software for
 #   any purpose with or without fee is hereby granted, provided that
@@ -27,10 +27,10 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=aom
-# The 'official' archive for the aom 2.0.1 release has the git commit in
+# The 'official' archive for the aom 3.3.0 release has the git commit in
 # the filename, so adjustments are required for a sane Slackware build:
-VERSION=${VERSION:-2.0.1}
-GITCOMMIT=${GITCOMMIT:-b52ee6d44adaef8a08f6984390de050d64df9faa}
+VERSION=${VERSION:-3.3.0}
+GITCOMMIT=${GITCOMMIT:-87460cef80fb03def7d97df1b47bad5432e5e2e4}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -88,7 +88,7 @@ find -L . \
 cd build
 
   # I don't build either the HTML or the Latex docs as IMHO at this stage
-  # of aom development they are not terribly useful for non-developers.
+  # of aom development they are still not terribly useful for non-developers.
   # To enable these docs change '-DENABLE_DOCS=0' below to '1' to build
   # the docs and then uncomment the 'extra docs' section below to install them...
 
@@ -97,8 +97,8 @@ cd build
     -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
     -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
     -DCMAKE_INSTALL_PREFIX=/usr \
-    -DCMAKE_INSTALL_LIBDIR=/lib${LIBDIRSUFFIX} \
-    -DCMAKE_INSTALL_INCLUDEDIR=/include \
+    -DCMAKE_INSTALL_LIBDIR=lib${LIBDIRSUFFIX} \
+    -DCMAKE_INSTALL_INCLUDEDIR=include \
     -DCMAKE_BUILD_TYPE=Release \
     -DENABLE_NASM=1 \
     -DENABLE_DOCS=0 \
diff --git a/multimedia/aom/aom.info b/multimedia/aom/aom.info
index 35375792..052e807d 100644
--- a/multimedia/aom/aom.info
+++ b/multimedia/aom/aom.info
@@ -1,8 +1,8 @@
 PRGNAM="aom"
-VERSION="2.0.1"
+VERSION="3.3.0"
 HOMEPAGE="https://aomedia.googlesource.com/aom"
-DOWNLOAD="http://www.andrews-corner.org/downloads/aom-b52ee6d44adaef8a08f6984390de050d64df9faa.tar.gz"
-MD5SUM="d37bf9cfe3353e661637c2b106ee1787"
+DOWNLOAD="http://www.andrews-corner.org/downloads/aom-87460cef80fb03def7d97df1b47bad5432e5e2e4.tar.gz"
+MD5SUM="8e722dae87dff97dfb98c3857fe38ee2"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""

From slackbuilds at schoepfer.info  Tue Feb 22 06:44:17 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 22 Feb 2022 07:44:17 +0100
Subject: [Slackbuilds-users] xjadeo fix for build with new portimidi
 2.0.2
In-Reply-To: <20220222033038.GJ4508@localhost>
References: <1789bfa5496c5d8ddf5cf29e2b8ae58c@schoepfer.info>
 <CAPsDuS7DKDYnm7dQ-ttw5vL1i9npHT2K=LxXbYBB67LE1Dujhw@mail.gmail.com>
 <e0374ee2b415a56ded88bcab14ce77e3@schoepfer.info>
 <20220221180730.GI4508@localhost> <20220222033038.GJ4508@localhost>
Message-ID: <ae809d979442ab57c7a66f5a86894d3b@schoepfer.info>

On 2022-02-22 04:30, Dave Woodfall wrote:
> MuseScore
> hatari
> hydrogen
> mame
> mixxx
> odamex
> pd
> prboom-plus
> pygame
> seq24
> xjadeo
> 
> All checked and working.

Thanks for checking.
xjadeo could have been fixed with the attached patch, but portmidi was 
changed for xjadeo with this patch 
https://git.slackbuilds.org/slackbuilds/patch/?id=933f7aee263bb498d206475a2fcfb0e4186c6653 
, the others don't need this patch to build.
That's what it boils down to.

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xjadeo.patch
Type: text/x-diff
Size: 520 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220222/895f04fd/attachment-0001.bin>

From slackbuilds at schoepfer.info  Tue Feb 22 06:56:30 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 22 Feb 2022 07:56:30 +0100
Subject: [Slackbuilds-users] pwgen download/homepage fix
Message-ID: <84f96a67edaf2ba42fa33dfee158282a@schoepfer.info>

Hi,

i already sent this, but seems it got under the wheels, as said in the 
subject, patch attached.
Meanwhile there is also this patch 
https://git.slackbuilds.org/slackbuilds/commit/?id=3fafa4c18b66c906b8dcb63305cce0454c135c28 
, but this does not fix HOMEPAGE in .info.

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pwgen.patch
Type: text/x-diff
Size: 906 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220222/411f8053/attachment.bin>

From s.arcus at open-t.co.uk  Tue Feb 22 13:27:57 2022
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Tue, 22 Feb 2022 13:27:57 +0000
Subject: [Slackbuilds-users] Is Ekiga being phased out of SBo
Message-ID: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>

I haven't been able to get Ekiga to work any more since end of March 
2021 after updating this machine to latest -current (at the time). I 
eventually managed to get it compiled and installed, but then when 
trying to connect to any sip account it crashes.

When trying to recompile it now I noticed that ponce's SBo git repo now 
doesn't have Ekiga or Opal any more. Do I take it that Ekiga is now 
being phased out from SBo? I guess it makes sense as the upstream code 
hasn't been updated for a few years.

I would be ok with switching to another SIP client - but haven't found 
any so far which actually work properly. Linphone installs fine, but 
when I try to add a SIP account, it just doesn't do it. No error, nothing.

Any suggestions for a SIP client, or how to get Ekiga to work again 
please? I would prefer a client which supports multiple accounts - but 
frankly at this stage I would try anything. Thank you.

From korgie at gmail.com  Tue Feb 22 14:26:58 2022
From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=)
Date: Tue, 22 Feb 2022 16:26:58 +0200
Subject: [Slackbuilds-users] Is Ekiga being phased out of SBo
In-Reply-To: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
References: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
Message-ID: <8A335D14-38A5-43B1-86D7-34871F06FE2E@gmail.com>


> 
> 22 ??? 2022, 15:28, ? ??????? ?Sebastian Arcus <s.arcus at open-t.co.uk>? ??????:
> 
> Any suggestions for a SIP client, or how to get Ekiga to work again please? I would prefer a client which supports multiple accounts - but frankly at this stage I would try anything. Thank you.

Latest version of Ekiga is from 2012.

Try Linphone. In 2008 I was using a freeware closed source, also available on Linux but I forgot the name.

I try now to fix yate 

From pprkut at slackbuilds.org  Tue Feb 22 15:17:01 2022
From: pprkut at slackbuilds.org (Heinz Wiesinger)
Date: Tue, 22 Feb 2022 16:17:01 +0100
Subject: [Slackbuilds-users] Is Ekiga being phased out of SBo
In-Reply-To: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
References: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
Message-ID: <4513049.vXUDI8C0e8@amaterasu.liwjatan.org>

On Tuesday, 22 February 2022 14:27:57 CET Sebastian Arcus wrote:
> I haven't been able to get Ekiga to work any more since end of March
> 2021 after updating this machine to latest -current (at the time). I
> eventually managed to get it compiled and installed, but then when
> trying to connect to any sip account it crashes.
> 
> When trying to recompile it now I noticed that ponce's SBo git repo now
> doesn't have Ekiga or Opal any more. Do I take it that Ekiga is now
> being phased out from SBo? I guess it makes sense as the upstream code
> hasn't been updated for a few years.
> 
> I would be ok with switching to another SIP client - but haven't found
> any so far which actually work properly. Linphone installs fine, but
> when I try to add a SIP account, it just doesn't do it. No error, nothing.
> 
> Any suggestions for a SIP client, or how to get Ekiga to work again
> please? I would prefer a client which supports multiple accounts - but
> frankly at this stage I would try anything. Thank you.

There is twinkle:

https://github.com/LubosD/twinkle

No SlackBuild for that in the repo, but it seems reasonably active/uptodate.

Grs,
Heinz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220222/73b9118d/attachment.asc>

From dave at slackbuilds.org  Tue Feb 22 15:38:58 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Tue, 22 Feb 2022 15:38:58 +0000
Subject: [Slackbuilds-users] Is Ekiga being phased out of SBo
In-Reply-To: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
References: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
Message-ID: <20220222153858.GL4508@localhost>

On 22/02/22 13:27,
Sebastian Arcus <s.arcus at open-t.co.uk> put forth the proposition:
> I haven't been able to get Ekiga to work any more since end of March 2021
> after updating this machine to latest -current (at the time). I eventually
> managed to get it compiled and installed, but then when trying to connect to
> any sip account it crashes.
> When trying to recompile it now I noticed that ponce's SBo git repo now
> doesn't have Ekiga or Opal any more. Do I take it that Ekiga is now being
> phased out from SBo? I guess it makes sense as the upstream code hasn't been
> updated for a few years.
> I would be ok with switching to another SIP client - but haven't found any
> so far which actually work properly. Linphone installs fine, but when I try
> to add a SIP account, it just doesn't do it. No error, nothing.
> Any suggestions for a SIP client, or how to get Ekiga to work again please?
> I would prefer a client which supports multiple accounts - but frankly at
> this stage I would try anything. Thank you.

Hi Sebastian

I have been down this road in the past too, and was surprised at the
lack of a good software phone that had any kind of contacts list, or
didn't they didn't support basic things like contact groups.

I found Ekiga to be the most user-friendly phone out there (if you
can get past some of the cryptic error messages), which is why I
began maintaining it, but now I use a hardware VOIP phone + local
asterisk PBX.

Unfortunately, the developers stopped working on Ekiga many years
ago.  The problem now is that one of the dependencies fails to build
in 15.0, which renders it useless.  Linphone is probably the most,
maybe only, maintained software phone at the moment, and has been
getting better over the years.

There is also a plugin for Pidgin called SIPE (an extended version of
SIP), but I have never tested it, and don't know how compatible it is
with normal SIP:

http://slackbuilds.org/repository/14.2/network/pidgin-sipe/

Most of the focus the past few years seems to be on hardware phones.
I recall that there were some quite good SIP apps for Android when I
used to use one, and some old Sony Ericsson feature phones can make
SIP calls and connect to the LAN by either USB or Bluetooth (like my
old Cybershot C702) if you can find a used one somewhere.

Gigaset make some fairly good SIP phones and base stations (n300)
that have all the features you'd expect from a phone, and can be
extended when combined with a local asterisk PBX running on your LAN.

I know this has drifted away from the subject, but user-friendly SIP
software have always been lacking for some reason, and proprietary
programs like skype have always been more popular unfortunately.

--
Dave

From s.arcus at open-t.co.uk  Tue Feb 22 16:10:01 2022
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Tue, 22 Feb 2022 16:10:01 +0000
Subject: [Slackbuilds-users] Is Ekiga being phased out of SBo
In-Reply-To: <20220222153858.GL4508@localhost>
References: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
 <20220222153858.GL4508@localhost>
Message-ID: <5baf69d4-c517-cde5-8ebc-4ea1673912be@open-t.co.uk>


On 22/02/2022 15:38, Dave Woodfall wrote:
> On 22/02/22 13:27,
> Sebastian Arcus <s.arcus at open-t.co.uk> put forth the proposition:
>> I haven't been able to get Ekiga to work any more since end of March 2021
>> after updating this machine to latest -current (at the time). I eventually
>> managed to get it compiled and installed, but then when trying to connect to
>> any sip account it crashes.
>> When trying to recompile it now I noticed that ponce's SBo git repo now
>> doesn't have Ekiga or Opal any more. Do I take it that Ekiga is now being
>> phased out from SBo? I guess it makes sense as the upstream code hasn't been
>> updated for a few years.
>> I would be ok with switching to another SIP client - but haven't found any
>> so far which actually work properly. Linphone installs fine, but when I try
>> to add a SIP account, it just doesn't do it. No error, nothing.
>> Any suggestions for a SIP client, or how to get Ekiga to work again please?
>> I would prefer a client which supports multiple accounts - but frankly at
>> this stage I would try anything. Thank you.

Hi David,

> 
> Hi Sebastian
> 
> I have been down this road in the past too, and was surprised at the
> lack of a good software phone that had any kind of contacts list, or
> didn't they didn't support basic things like contact groups.
> 
> I found Ekiga to be the most user-friendly phone out there (if you
> can get past some of the cryptic error messages), which is why I
> began maintaining it, but now I use a hardware VOIP phone + local
> asterisk PBX.

I found Ekiga reasonably good as well - until it stopped working. I 
actually use myself VoIP desk phone (mainly Grandstream and old Cisco 
stuff) + Asterisk PBX's at a number of sites. But I need a VoIP 
softphone on my laptop to troubleshoot and reconfigure remotely 
Asterisk servers.

> 
> Unfortunately, the developers stopped working on Ekiga many years
> ago.  The problem now is that one of the dependencies fails to build
> in 15.0, which renders it useless.  Linphone is probably the most,
> maybe only, maintained software phone at the moment, and has been
> getting better over the years.

I've just about managed to get Linphone working now. The trouble was 
that it expects a specific syntax when configuring a sip account 
(username in the format <sip: username at server>, and the proxy address 
needs to start with "sip:" as well) - but there were zero error messages 
in the GUI if you didn't follow that syntax - it just didn't add the 
account - so I was flummoxed for a while.

Thank you everyone for the suggestions. I plan to have a look at Twinkle 
and see if it will compile and install.


From dave at slackbuilds.org  Tue Feb 22 16:24:32 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Tue, 22 Feb 2022 16:24:32 +0000
Subject: [Slackbuilds-users] Is Ekiga being phased out of SBo
In-Reply-To: <5baf69d4-c517-cde5-8ebc-4ea1673912be@open-t.co.uk>
References: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
 <20220222153858.GL4508@localhost>
 <5baf69d4-c517-cde5-8ebc-4ea1673912be@open-t.co.uk>
Message-ID: <20220222162431.GM4508@localhost>

On 22/02/22 16:10,
Sebastian Arcus <s.arcus at open-t.co.uk> put forth the proposition:
> On 22/02/2022 15:38, Dave Woodfall wrote:
> > On 22/02/22 13:27,
> > Sebastian Arcus <s.arcus at open-t.co.uk> put forth the proposition:
> > > I haven't been able to get Ekiga to work any more since end of March 2021
> > > after updating this machine to latest -current (at the time). I eventually
> > > managed to get it compiled and installed, but then when trying to connect to
> > > any sip account it crashes.
> > > When trying to recompile it now I noticed that ponce's SBo git repo now
> > > doesn't have Ekiga or Opal any more. Do I take it that Ekiga is now being
> > > phased out from SBo? I guess it makes sense as the upstream code hasn't been
> > > updated for a few years.
> > > I would be ok with switching to another SIP client - but haven't found any
> > > so far which actually work properly. Linphone installs fine, but when I try
> > > to add a SIP account, it just doesn't do it. No error, nothing.
> > > Any suggestions for a SIP client, or how to get Ekiga to work again please?
> > > I would prefer a client which supports multiple accounts - but frankly at
> > > this stage I would try anything. Thank you.
> Hi David,
> >
> > Hi Sebastian
> >
> > I have been down this road in the past too, and was surprised at the
> > lack of a good software phone that had any kind of contacts list, or
> > didn't they didn't support basic things like contact groups.
> >
> > I found Ekiga to be the most user-friendly phone out there (if you
> > can get past some of the cryptic error messages), which is why I
> > began maintaining it, but now I use a hardware VOIP phone + local
> > asterisk PBX.
> I found Ekiga reasonably good as well - until it stopped working. I actually
> use myself VoIP desk phone (mainly Grandstream and old Cisco stuff) +
> Asterisk PBX's at a number of sites. But I need a VoIP softphone on my
> laptop to troubleshoot and reconfigure remotely Asterisk servers.
> >
> > Unfortunately, the developers stopped working on Ekiga many years
> > ago.  The problem now is that one of the dependencies fails to build
> > in 15.0, which renders it useless.  Linphone is probably the most,
> > maybe only, maintained software phone at the moment, and has been
> > getting better over the years.
> I've just about managed to get Linphone working now. The trouble was that it
> expects a specific syntax when configuring a sip account (username in the
> format <sip: username at server>, and the proxy address needs to start with
> "sip:" as well) - but there were zero error messages in the GUI if you
> didn't follow that syntax - it just didn't add the account - so I was
> flummoxed for a while.
> Thank you everyone for the suggestions. I plan to have a look at Twinkle and
> see if it will compile and install.

I used to use the CLI part of linphone for testing things: linphonec.
You may find the errors and warnings bit more verbose than the GUI,
but it worked fine.  I can't recall if it takes SIP address as a flag
when starting it though, which would be useful.  IIRC the syntax
it uses is sip:user/extension@<ip address>.  It keeps history between
sessions, so you only need to up-arrow a few times the next time you
use it.

--
Dave

From slackbuilds at schoepfer.info  Tue Feb 22 16:28:57 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 22 Feb 2022 17:28:57 +0100
Subject: [Slackbuilds-users] Is Ekiga being phased out of SBo
In-Reply-To: <4513049.vXUDI8C0e8@amaterasu.liwjatan.org>
References: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
 <4513049.vXUDI8C0e8@amaterasu.liwjatan.org>
Message-ID: <e0af55069b1bd0a6847f704d0d941e0a@schoepfer.info>


>> Any suggestions for a SIP client, or how to get Ekiga to work again
>> please? I would prefer a client which supports multiple accounts - but
>> frankly at this stage I would try anything. Thank you.
> 
> There is twinkle:
> 
> https://github.com/LubosD/twinkle
> 
> No SlackBuild for that in the repo, but it seems reasonably 
> active/uptodate.



There's also https://jami.net/ , no SlackBuild and i never tested it.

From dave at slackbuilds.org  Tue Feb 22 17:46:59 2022
From: dave at slackbuilds.org (Dave Woodfall)
Date: Tue, 22 Feb 2022 17:46:59 +0000
Subject: [Slackbuilds-users] Is Ekiga being phased out of SBo
In-Reply-To: <20220222153858.GL4508@localhost>
References: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
 <20220222153858.GL4508@localhost>
Message-ID: <20220222174659.GN4508@localhost>

> There is also a plugin for Pidgin called SIPE (an extended version of
> SIP), but I have never tested it, and don't know how compatible it is
> with normal SIP:
> http://slackbuilds.org/repository/14.2/network/pidgin-sipe/

I've just had a look at this and pushed an update to get it to build
on 15.0.

SIP shows in pidgin's "add account" menu as SIMPLE, and I
successfully managed to make an account and register it to my
asterisk PBX.

I added a buddy, which was my home phone, but it shows offline, so
"enable offline buddies" then configure the buddy to always show is
needed.

That's as far as I tested it, but I noticed some menu entries to
configure audio/video, so I imagine it ought to work.

--
Dave

From khronosschoty at posteo.org  Tue Feb 22 18:07:27 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Tue, 22 Feb 2022 18:07:27 +0000
Subject: [Slackbuilds-users] games/OpenRA Has a new dependency on msbuild
Message-ID: <YhUmX6rZ5PWE1jnA@posteo.de>

Apparently newer versions of mono no longer bundle msbuild. OpenRA
requires this. Therefore to update OpenRA or to even have it working
against the master branch, I need to satisfy this dependency. I will
submit a build script for this shortly. 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 870 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220222/8b25e700/attachment.asc>

From s.arcus at open-t.co.uk  Tue Feb 22 21:34:39 2022
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Tue, 22 Feb 2022 21:34:39 +0000
Subject: [Slackbuilds-users] Is Ekiga being phased out of SBo
In-Reply-To: <20220222174659.GN4508@localhost>
References: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
 <20220222153858.GL4508@localhost> <20220222174659.GN4508@localhost>
Message-ID: <b8de02e9-ef7f-a6f5-f435-aec60a071199@open-t.co.uk>


On 22/02/2022 17:46, Dave Woodfall wrote:
>> There is also a plugin for Pidgin called SIPE (an extended version of
>> SIP), but I have never tested it, and don't know how compatible it is
>> with normal SIP:
>> http://slackbuilds.org/repository/14.2/network/pidgin-sipe/
> 
> I've just had a look at this and pushed an update to get it to build
> on 15.0.
> 
> SIP shows in pidgin's "add account" menu as SIMPLE, and I
> successfully managed to make an account and register it to my
> asterisk PBX.
> 
> I added a buddy, which was my home phone, but it shows offline, so
> "enable offline buddies" then configure the buddy to always show is
> needed.
> 
> That's as far as I tested it, but I noticed some menu entries to
> configure audio/video, so I imagine it ought to work.

Thank you Dave - for Pidgin-sipe and the linphonec suggestion. At least 
least there are a few options available.

From s.arcus at open-t.co.uk  Tue Feb 22 22:50:02 2022
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Tue, 22 Feb 2022 22:50:02 +0000
Subject: [Slackbuilds-users] Is Ekiga being phased out of SBo
In-Reply-To: <4513049.vXUDI8C0e8@amaterasu.liwjatan.org>
References: <3bf14ace-2ef0-7d45-c9e5-d6ecaca404b6@open-t.co.uk>
 <4513049.vXUDI8C0e8@amaterasu.liwjatan.org>
Message-ID: <2cf1c143-a0b1-e621-6d26-2d6b36d0cb9d@open-t.co.uk>

On 22/02/2022 15:17, Heinz Wiesinger wrote:
> On Tuesday, 22 February 2022 14:27:57 CET Sebastian Arcus wrote:
>> I haven't been able to get Ekiga to work any more since end of March
>> 2021 after updating this machine to latest -current (at the time). I
>> eventually managed to get it compiled and installed, but then when
>> trying to connect to any sip account it crashes.
>>
>> When trying to recompile it now I noticed that ponce's SBo git repo now
>> doesn't have Ekiga or Opal any more. Do I take it that Ekiga is now
>> being phased out from SBo? I guess it makes sense as the upstream code
>> hasn't been updated for a few years.
>>
>> I would be ok with switching to another SIP client - but haven't found
>> any so far which actually work properly. Linphone installs fine, but
>> when I try to add a SIP account, it just doesn't do it. No error, nothing.
>>
>> Any suggestions for a SIP client, or how to get Ekiga to work again
>> please? I would prefer a client which supports multiple accounts - but
>> frankly at this stage I would try anything. Thank you.
> 
> There is twinkle:
> 
> https://github.com/LubosD/twinkle
> 
> No SlackBuild for that in the repo, but it seems reasonably active/uptodate.

Thank you for that. I didn't realise there is a new/current version of 
Twinkle. I can confirm I managed to compile and install it, and so far 
it appears to work well. I've added on a ToDo list to try and get a 
script done for SBo and upload it. It would most likely be useful to 
others as well.

From andrew.david.strong at gmail.com  Wed Feb 23 04:42:20 2022
From: andrew.david.strong at gmail.com (andrew)
Date: Wed, 23 Feb 2022 15:42:20 +1100
Subject: [Slackbuilds-users] Update for aom (multimedia)
In-Reply-To: <YhR8gmgklaYZXCw3@ilium.andrews-corner.org>
References: <YhR8gmgklaYZXCw3@ilium.andrews-corner.org>
Message-ID: <YhW7LP/JK+gzEH7N@ilium.andrews-corner.org>

On Tue, Feb 22, 2022 at 05:02:46PM +1100, andrew wrote:

>  2. I have made some small changes to the install paths, an error that
>     I made in old versions of the SlackBuild was generating a faulty
>     pkconfig file. This may still be an issue in the script for 14.2
>     which I will check when the dust settles with 15.0.

Sure enough I cranked up a VM for 14.2 and the SlackBuild for aom
(multimedia) creates a malformed pkgconfig file. The fix is pretty
straightforward and I have attached a patch that will make the small
correction required under 14.2.

Still kicking myself for this old error which was not noticed by me
for a looooong time.

Andrew Strong
-- 
You think that's air you're breathing now?
-------------- next part --------------
diff -Naur aom_orig/aom.SlackBuild aom_fixed/aom.SlackBuild
--- aom_orig/aom.SlackBuild	2021-01-09 18:35:49.000000000 +1100
+++ aom_fixed/aom.SlackBuild	2022-02-23 15:39:51.317340892 +1100
@@ -29,7 +29,7 @@
 # the filename, so adjustments are required for a sane Slackware build:
 VERSION=${VERSION:-2.0.1}
 GITCOMMIT=${GITCOMMIT:-b52ee6d44adaef8a08f6984390de050d64df9faa}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2}
 TAG=${TAG:-_SBo}
 
 if [ -z "$ARCH" ]; then
@@ -87,8 +87,8 @@
     -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
     -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
     -DCMAKE_INSTALL_PREFIX=/usr \
-    -DCMAKE_INSTALL_LIBDIR=/lib${LIBDIRSUFFIX} \
-    -DCMAKE_INSTALL_INCLUDEDIR=/include \
+    -DCMAKE_INSTALL_LIBDIR=lib${LIBDIRSUFFIX} \
+    -DCMAKE_INSTALL_INCLUDEDIR=include \
     -DCMAKE_BUILD_TYPE=Release \
     -DENABLE_NASM=1 \
     -DENABLE_DOCS=0 \

From ml at mareichelt.com  Wed Feb 23 14:24:43 2022
From: ml at mareichelt.com (Markus Reichelt)
Date: Wed, 23 Feb 2022 15:24:43 +0100
Subject: [Slackbuilds-users] Extundelete up for grabs
In-Reply-To: <CAKgO6XzGJ_QWa+c=XvLasD_R-6vzXQn1RORNga4eqK=dwLX3Uw@mail.gmail.com>
References: <CAKgO6XzGJ_QWa+c=XvLasD_R-6vzXQn1RORNga4eqK=dwLX3Uw@mail.gmail.com>
Message-ID: <YhZDqw8XPzEmhXHY@pc21.mareichelt.com>

Thanks for letting me know. I don't use extundelete anymore so it's
up for grabs.


* Dr Barrientos <ravagava14 at gmail.com> wrote:

> Date: Mon, 21 Feb 2022 18:55:33 -0300
> From: Dr Barrientos <ravagava14 at gmail.com>
> To: slackbuilds at mareichelt.de
> Subject: Extundelete compile errors
> 
> Greetings, I tried to compile your extundelete slackbuild on my system
> (slack 15) and unfortunately it didn't work because insertionops.cc: In
> function ?std::ostream& operator<<(std::ostream&, const ext2_inode&)?:
> insertionops.cc:36:36: error: ?const struct ext2_inode? has no member named
> ?i_dir_acl?; did you mean ?i_file_acl??
>   36 |   os << "Directory ACL: " << inode.i_dir_acl << std::endl;
>      |                                    ^~~~~~~~~
> 
> Basically comment that line and it compiles, it's probably unimportant
> since it's just printing that class to stdout. Consider applying that
> change if you can. Thanks

-- 

From ml at mareichelt.com  Wed Feb 23 14:48:58 2022
From: ml at mareichelt.com (Markus Reichelt)
Date: Wed, 23 Feb 2022 15:48:58 +0100
Subject: [Slackbuilds-users] SlackBuild templates (to make your scripts
 15.0-ready)
Message-ID: <YhZJWgcygSGI1DLB@pc21.mareichelt.com>

FYI, the up-to-date SlackBuild templates reside at

https://git.slackbuilds.org/templates/



From artourter at gmail.com  Wed Feb 23 16:41:20 2022
From: artourter at gmail.com (Greg' Ar Tourter)
Date: Wed, 23 Feb 2022 16:41:20 +0000
Subject: [Slackbuilds-users] wrong md5sum for protobuf-c 1.4.0 package
Message-ID: <CAK09-vmsyWW_uRw5ddXcYpmDwZcSS5vgH6xcSONd7kbfyTHkmQ@mail.gmail.com>

Hi

looks like the checksum wasn't updated in the 1.4.0 upgrade:

Found protobuf-c-1.4.0.tar.gz in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for protobuf-c-1.4.0.tar.gz ... FAILED!
    Expected: dabc05a5f11c21b96d8d6db4153f5343
    Found:    10e1103a012ce0877c32367949a2fa6e

Cheers

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

From fernando.lopezjr at gmail.com  Wed Feb 23 19:33:54 2022
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Wed, 23 Feb 2022 12:33:54 -0700
Subject: [Slackbuilds-users] SlackBuild templates (to make your scripts
 15.0-ready)
In-Reply-To: <YhZJWgcygSGI1DLB@pc21.mareichelt.com>
References: <YhZJWgcygSGI1DLB@pc21.mareichelt.com>
Message-ID: <CALrQ46DYem1L-+4Vcs_+qWo58BxLxmZCeUvSPJ-Ua5uMPPGCSA@mail.gmail.com>

thank you! appreciated. :)

On Wed, Feb 23, 2022 at 7:49 AM Markus Reichelt via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> FYI, the up-to-date SlackBuild templates reside at
>
> https://git.slackbuilds.org/templates/
>
>
> _______________________________________________
> 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/20220223/a2054314/attachment-0001.htm>

From fernando.lopezjr at gmail.com  Wed Feb 23 19:35:58 2022
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Wed, 23 Feb 2022 12:35:58 -0700
Subject: [Slackbuilds-users] Extundelete up for grabs
In-Reply-To: <YhZDqw8XPzEmhXHY@pc21.mareichelt.com>
References: <CAKgO6XzGJ_QWa+c=XvLasD_R-6vzXQn1RORNga4eqK=dwLX3Uw@mail.gmail.com>
 <YhZDqw8XPzEmhXHY@pc21.mareichelt.com>
Message-ID: <CALrQ46Bjn7nTB+ULz9HQCBcApDQ57BToyd6h=Rvqab0_PJNeBw@mail.gmail.com>

ill take it. thanks.

On Wed, Feb 23, 2022 at 7:24 AM Markus Reichelt via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> Thanks for letting me know. I don't use extundelete anymore so it's
> up for grabs.
>
>
> * Dr Barrientos <ravagava14 at gmail.com> wrote:
>
> > Date: Mon, 21 Feb 2022 18:55:33 -0300
> > From: Dr Barrientos <ravagava14 at gmail.com>
> > To: slackbuilds at mareichelt.de
> > Subject: Extundelete compile errors
> >
> > Greetings, I tried to compile your extundelete slackbuild on my system
> > (slack 15) and unfortunately it didn't work because insertionops.cc: In
> > function ?std::ostream& operator<<(std::ostream&, const ext2_inode&)?:
> > insertionops.cc:36:36: error: ?const struct ext2_inode? has no member
> named
> > ?i_dir_acl?; did you mean ?i_file_acl??
> >   36 |   os << "Directory ACL: " << inode.i_dir_acl << std::endl;
> >      |                                    ^~~~~~~~~
> >
> > Basically comment that line and it compiles, it's probably unimportant
> > since it's just printing that class to stdout. Consider applying that
> > change if you can. Thanks
>
> --
> _______________________________________________
> 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/20220223/bba7c0f2/attachment.htm>

From andrew.clemons at gmail.com  Wed Feb 23 23:45:01 2022
From: andrew.clemons at gmail.com (Andrew Clemons)
Date: Thu, 24 Feb 2022 12:45:01 +1300
Subject: [Slackbuilds-users] xjadeo fix for build with new portimidi
 2.0.2
In-Reply-To: <ae809d979442ab57c7a66f5a86894d3b@schoepfer.info>
References: <1789bfa5496c5d8ddf5cf29e2b8ae58c@schoepfer.info>
 <CAPsDuS7DKDYnm7dQ-ttw5vL1i9npHT2K=LxXbYBB67LE1Dujhw@mail.gmail.com>
 <e0374ee2b415a56ded88bcab14ce77e3@schoepfer.info>
 <20220221180730.GI4508@localhost> <20220222033038.GJ4508@localhost>
 <ae809d979442ab57c7a66f5a86894d3b@schoepfer.info>
Message-ID: <53b90b7c-c874-c91a-00cb-01aecfdba7a9@gmail.com>

Hi Johannes,

On 22/02/22 19:44, Franzen via SlackBuilds-users wrote:
> On 2022-02-22 04:30, Dave Woodfall wrote:
>> MuseScore
>> hatari
>> hydrogen
>> mame
>> mixxx
>> odamex
>> pd
>> prboom-plus
>> pygame
>> seq24
>> xjadeo
>>
>> All checked and working.
> 
> Thanks for checking.
> xjadeo could have been fixed with the attached patch, but portmidi was
> changed for xjadeo with this patch
> https://git.slackbuilds.org/slackbuilds/patch/?id=933f7aee263bb498d206475a2fcfb0e4186c6653
> , the others don't need this patch to build.
> That's what it boils down to.

I've applied this patch to xjadeo now and removed the compat symlink in
portmidi. Thanks.


From andrew.clemons at gmail.com  Wed Feb 23 23:51:56 2022
From: andrew.clemons at gmail.com (Andrew Clemons)
Date: Thu, 24 Feb 2022 12:51:56 +1300
Subject: [Slackbuilds-users] pwgen download/homepage fix
In-Reply-To: <84f96a67edaf2ba42fa33dfee158282a@schoepfer.info>
References: <84f96a67edaf2ba42fa33dfee158282a@schoepfer.info>
Message-ID: <22ee2e06-e93e-5a6f-c051-7e1a9d2601a5@gmail.com>

On 22/02/22 19:56, Franzen via SlackBuilds-users wrote:
> Hi,
> 
> i already sent this, but seems it got under the wheels, as said in the
> subject, patch attached.
> Meanwhile there is also this patch
> https://git.slackbuilds.org/slackbuilds/commit/?id=3fafa4c18b66c906b8dcb63305cce0454c135c28
> , but this does not fix HOMEPAGE in .info.

Done on my branch. Thanks

From khronosschoty at posteo.org  Thu Feb 24 00:37:06 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 24 Feb 2022 00:37:06 +0000
Subject: [Slackbuilds-users]
 0001-added-development-dotnet-sdk-6.0-dependency-for-openra.patch
Message-ID: <YhbTMu/nCnlvJse4@posteo.de>

hi OpenRA requires a more modern dotnet-sdk to build properly: here it
is. 
-------------- next part --------------
From df43eed7817e339ea55433bfd197d1e964de65e2 Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 23 Feb 2022 16:33:51 -0800
Subject: [PATCH 1/1] added development/dotnet-sdk-6.0: dependency for
 games/OpenRA

---
 development/dotnet-sdk-6.0/README             |  9 +++
 .../dotnet-sdk-6.0/dotnet-sdk-6.0.SlackBuild  | 80 +++++++++++++++++++
 .../dotnet-sdk-6.0/dotnet-sdk-6.0.info        | 10 +++
 development/dotnet-sdk-6.0/slack-desc         | 19 +++++
 4 files changed, 118 insertions(+)
 create mode 100644 development/dotnet-sdk-6.0/README
 create mode 100644 development/dotnet-sdk-6.0/dotnet-sdk-6.0.SlackBuild
 create mode 100644 development/dotnet-sdk-6.0/dotnet-sdk-6.0.info
 create mode 100644 development/dotnet-sdk-6.0/slack-desc

diff --git a/development/dotnet-sdk-6.0/README b/development/dotnet-sdk-6.0/README
new file mode 100644
index 00000000000..6f2f65b8bd3
--- /dev/null
+++ b/development/dotnet-sdk-6.0/README
@@ -0,0 +1,9 @@
+.NET Core is an open-source, general-purpose development platform
+maintained by Microsoft and the .NET community on GitHub.
+It's cross-platform (supporting Windows, macOS, and Linux)
+and can be used to build device, cloud, and IoT applications.
+
+Please run 'dotnet new' after installing to initiate the program
+and load all of the templates.
+
+Note: Conflicts with dotnet-sdk-3.1
diff --git a/development/dotnet-sdk-6.0/dotnet-sdk-6.0.SlackBuild b/development/dotnet-sdk-6.0/dotnet-sdk-6.0.SlackBuild
new file mode 100644
index 00000000000..3a845a45aac
--- /dev/null
+++ b/development/dotnet-sdk-6.0/dotnet-sdk-6.0.SlackBuild
@@ -0,0 +1,80 @@
+#!/bin/bash
+
+# Slackware build script for dotnet-sdk-6.0.
+#
+# Copyright 2019 Reza Talebi, Shahin Shahr, Iran.
+# Adapted by Vasily Sora for dotnet-sdk-6.0 Copyright 2022
+# 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=dotnet-sdk-6.0
+SRCNAM=dotnet-sdk
+VERSION=${VERSION:-6.0.200}
+BUILD=${BUILD:-1}
+TAG=${TAG:-_SBo}
+PKGTYPE=${PKGTYPE:-tgz}
+
+if [ -z "$ARCH" ]; then
+  ARCH=$( uname -m )
+fi
+
+if [ "$ARCH" = "x86_64" ]; then
+  ARCHITECTURE="x64"
+else
+  echo "Package for $ARCH architecture is not available."
+  exit 1
+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}
+
+set -e
+
+rm -rf $PKG
+mkdir -p $TMP $PKG $OUTPUT
+cd $TMP
+rm -rf $PRGNAM-${VERSION}-${BUILD}
+mkdir -p $PRGNAM-${VERSION}-${BUILD}
+cd $PKG
+mkdir -p usr/share/dotnet
+tar -zxf $CWD/$SRCNAM-${VERSION}-linux-${ARCHITECTURE}.tar.gz -C usr/share/dotnet
+chown -R root:root usr/share/dotnet
+
+mkdir -p usr/bin
+ln -s /usr/share/dotnet/dotnet usr/bin/dotnet
+
+mkdir -p 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
diff --git a/development/dotnet-sdk-6.0/dotnet-sdk-6.0.info b/development/dotnet-sdk-6.0/dotnet-sdk-6.0.info
new file mode 100644
index 00000000000..929d34e299f
--- /dev/null
+++ b/development/dotnet-sdk-6.0/dotnet-sdk-6.0.info
@@ -0,0 +1,10 @@
+PRGNAM="dotnet-sdk-6.0"
+VERSION="6.0.200"
+HOMEPAGE="https://dotnet.microsoft.com/"
+DOWNLOAD="UNSUPPORTED"
+MD5SUM=""
+DOWNLOAD_x86_64="https://download.visualstudio.microsoft.com/download/pr/807f9d72-4940-4b1a-aa4a-8dbb0f73f5d7/cb666c22a87bf9413f29615e0ba94500/dotnet-sdk-6.0.200-linux-x64.tar.gz"
+MD5SUM_x86_64="bd0d6472672d203d0482cc79981e34df"
+REQUIRES=""
+MAINTAINER="khronosschoty"
+EMAIL="khronosschoty at posteo.org"
diff --git a/development/dotnet-sdk-6.0/slack-desc b/development/dotnet-sdk-6.0/slack-desc
new file mode 100644
index 00000000000..b5fe1d7ec87
--- /dev/null
+++ b/development/dotnet-sdk-6.0/slack-desc
@@ -0,0 +1,19 @@
+# HOW TO EDIT THIS FILE:
+# The "handy ruler" below makes it easier to edit a package description.
+# Line up the first '|' above the ':' following the base package name, and
+# the '|' on the right side marks the last column you can put a character in.
+# You must make exactly 11 lines for the formatting to be correct.  It's also
+# customary to leave one space after the ':' except on otherwise blank lines.
+
+              |-----handy-ruler------------------------------------------------------|
+dotnet-6.0: dotnet-6.0 (Cross-platform development framework)
+dotnet-6.0:
+dotnet-6.0: .NET Core is an open-source, general-purpose development
+dotnet-6.0: platform maintained by Microsoft and the .NET community on
+dotnet-6.0: GitHub. It's cross-platform (supporting Windows, macOS, and Linux)
+dotnet-6.0: and can be used to build device, cloud, and IoT applications.
+dotnet-6.0: Please run 'dotnet new' after installing to initiate the program
+dotnet-6.0: and load all of the templates.
+dotnet-6.0:
+dotnet-6.0: https://dotnet.microsoft.com/
+dotnet-6.0:
-- 
2.35.1

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

From khronosschoty at posteo.org  Thu Feb 24 01:06:53 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 24 Feb 2022 01:06:53 +0000
Subject: [Slackbuilds-users]
 0001-games-OpenRA-updated-for-version-20210321.patch
Message-ID: <YhbaLSjqT0XPI1an@posteo.de>

hi, 

This was a complicated update which requires a newer dotnet-sdk then
what we have in the sbo master git branch. I tested this script against
dotnet-sdk-6.0. I changed the shabang to restrict internet access
while building. The included deps tarball will allow OpenRA to build;
however if it is missing those dependencies will be fetched from the
internet; restricting remote access prevents this. There is no other
sane alternative that I am aware of. 
-------------- next part --------------
From adaabfd1044cd320e2005653203852c5194a937c Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 23 Feb 2022 17:00:35 -0800
Subject: [PATCH 1/1] games/OpenRA: updated for version 20210321

---
 games/OpenRA/OpenRA.SlackBuild            | 32 +++++++++++++----------
 games/OpenRA/OpenRA.info                  | 16 ++++++------
 games/OpenRA/fetch-thirdparty-deps.sh.new | 18 -------------
 3 files changed, 26 insertions(+), 40 deletions(-)
 delete mode 100644 games/OpenRA/fetch-thirdparty-deps.sh.new

diff --git a/games/OpenRA/OpenRA.SlackBuild b/games/OpenRA/OpenRA.SlackBuild
index 060cdd3e65c..6191e0bea74 100644
--- a/games/OpenRA/OpenRA.SlackBuild
+++ b/games/OpenRA/OpenRA.SlackBuild
@@ -1,8 +1,8 @@
-#!/bin/bash
+#!/user/bin/unshare -n /bin/bash
 
 # Slackware build script for OpenRA
 
-# Copyright 2017 Vasily Sora USA
+# Copyright 2017,2022 Vasily Sora USA
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -25,7 +25,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=OpenRA
-VERSION=${VERSION:-20190314}
+VERSION=${VERSION:-20210321}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -49,6 +49,10 @@ fi
 TMP=${TMP:-/tmp/SBo}
 PKG=$TMP/package-$PRGNAM
 OUTPUT=${OUTPUT:-/tmp}
+HOME=$TMP/$PRGNAM-release-$VERSION-source
+DOTNET_CLI_TELEMETRY_OPTOUT=1
+export HOME DOTNET_CLI_TELEMETRY_OPTOUT
+
 
 if [ "$ARCH" = "i586" ]; then
   SLKCFLAGS="-O2 -march=i586 -mtune=i686"
@@ -71,15 +75,15 @@ rm -rf $TMP/$PRGNAM-release-$VERSION-source
 mkdir -p $TMP $PKG $OUTPUT $TMP/$PRGNAM-release-$VERSION-source
 cd $TMP/$PRGNAM-release-$VERSION-source
 tar xvf $CWD/$PRGNAM-release-$VERSION-source.tar.bz2
-cp $CWD/fetch-thirdparty-deps.sh.new thirdparty/fetch-thirdparty-deps.sh
-cp $CWD/download.tar.gz thirdparty
-mkdir thirdparty/download/
-cp $CWD/GeoLite2-Country.mmdb.gz thirdparty/download/
-rm thirdparty/fetch-geoip-db.sh
-touch thirdparty/fetch-geoip-db.sh
-echo "#!/bin/sh" >> thirdparty/fetch-geoip-db.sh
-echo 'echo "success"' >> thirdparty/fetch-geoip-db.sh
-chmod +x thirdparty/fetch-geoip-db.sh
+tar -xzvf $CWD/openra-deps.tar.gz
+cp $CWD/IP2LOCATION-LITE-DB1.IPV6.BIN.ZIP .
+rm fetch-geoip.sh
+touch fetch-geoip.sh
+echo "#!/bin/sh" >> fetch-geoip.sh
+echo 'echo "success"' >> fetch-geoip.sh
+chmod +x fetch-geoip.sh
+
+sed -i 's/msbuild/dotnet\ msbuild/g' ./Makefile ./packaging/functions.sh
 
 chown -R root:root .
 find -L . \
@@ -88,10 +92,10 @@ find -L . \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
-make dependencies
-make all
+make all TARGETPLATFORM=unix-generic  RUNTIME=mono MSBUILD='dotnet msbuild -verbosity:m -nologo'
 make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install DESTDIR=$PKG
 make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install-linux-shortcuts DESTDIR=$PKG
+make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install-linux-appdata DESTDIR=$PKG 
 
 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
diff --git a/games/OpenRA/OpenRA.info b/games/OpenRA/OpenRA.info
index ef12bb2ec9a..f2e1d45aef9 100644
--- a/games/OpenRA/OpenRA.info
+++ b/games/OpenRA/OpenRA.info
@@ -1,14 +1,14 @@
 PRGNAM="OpenRA"
-VERSION="20190314"
+VERSION="20210321"
 HOMEPAGE="http://www.openra.net/"
-DOWNLOAD="https://github.com/OpenRA/OpenRA/releases/download/release-20190314/OpenRA-release-20190314-source.tar.bz2 \
-          http://repo.khronosschoty.org/Slackware/stuff/OpenRA/20190314/download.tar.gz \
-          http://repo.khronosschoty.org/Slackware/stuff/OpenRA/20190314/GeoLite2-Country.mmdb.gz"
-MD5SUM="4ea1ba7d309bf0482979b5337677d2a3 \
-        e890273530c23cb8571a729d2aced59d \
-        3639895811efb10ad54bf6b40980224e"
+DOWNLOAD="https://github.com/OpenRA/OpenRA/releases/download/release-20210321/OpenRA-release-20210321-source.tar.bz2 \
+          http://repo.schotynet.org/sources/openra/openra-deps.tar.gz \
+	  http://repo.schotynet.org/sources/openra/IP2LOCATION-LITE-DB1.IPV6.BIN.ZIP
+MD5SUM="38593fbcdda629561d8c0bc8ac1af402 \
+        26b1855341dc15787c7b54945050095d \
+        ef52f92818ebc942ca98108e92a0b802"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES="lua mono"
+REQUIRES="lua mono dotnet-sdk-6.0"
 MAINTAINER="khronosschoty"
 EMAIL="khronosschoty at posteo.org"
diff --git a/games/OpenRA/fetch-thirdparty-deps.sh.new b/games/OpenRA/fetch-thirdparty-deps.sh.new
deleted file mode 100644
index c0f9ae9b5d7..00000000000
--- a/games/OpenRA/fetch-thirdparty-deps.sh.new
+++ /dev/null
@@ -1,18 +0,0 @@
-#!/bin/sh
-
-####
-# This file must stay /bin/sh and POSIX compliant for BSD portability.
-# Copy-paste the entire script into http://shellcheck.net to check.
-####
-
-# Die on any error for Travis CI to automatically retry:
-set -e
-
-download_dir="${0%/*}/download"
-
-mkdir -p "${download_dir}"
-cd "${download_dir}"
-cd ..
-
-tar -xvf download.tar.gz
-
-- 
2.35.1

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

From erich.public at protonmail.com  Thu Feb 24 02:43:23 2022
From: erich.public at protonmail.com (Erich Ritz)
Date: Thu, 24 Feb 2022 02:43:23 +0000
Subject: [Slackbuilds-users]
 0001-games-OpenRA-updated-for-version-20210321.patch
In-Reply-To: <YhbaLSjqT0XPI1an@posteo.de>
References: <YhbaLSjqT0XPI1an@posteo.de>
Message-ID: <PCJx4cC10zevQ9w_BMHVohrId-VVn1xPni5cdg_eHu77FOGZGVMvsIGzSN-g3uPGz4LR8KDZ85iqJDNOhsAkemTi7slygkeGxzRTIxN2YbQ=@protonmail.com>

------- Original Message -------

On Wednesday, February 23rd, 2022 at 7:06 PM, khronosschoty <khronosschoty at posteo.org> wrote:

> hi,
>
> This was a complicated update which requires a newer dotnet-sdk then
> what we have in the sbo master git branch. I tested this script against
> dotnet-sdk-6.0. I changed the shabang to restrict internet access
> while building. The included deps tarball will allow OpenRA to build;
> however if it is missing those dependencies will be fetched from the
> internet; restricting remote access prevents this. There is no other
> sane alternative that I am aware of.
>

Typo; shebang should be:

#!/usr/bin/unshare -n /bin/bash

instead of "user".

As to whether such a thing is allowed, I cannot answer that.

Erich

From khronosschoty at posteo.org  Thu Feb 24 03:02:59 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 24 Feb 2022 03:02:59 +0000
Subject: [Slackbuilds-users]
 0001-games-OpenRA-updated-for-version-20210321.patch
Message-ID: <Yhb1Y5xci205uaBE@posteo.de>

> Typo; shebang should be:
> #!/usr/bin/unshare -n /bin/bash
> instead of "user".
> As to whether such a thing is allowed, I cannot answer that.
> Erich

Thanks for catching that! fixed patch. 
-------------- next part --------------
From 014df4f4a1c4c8d39117e05726d5175c6e8a8b14 Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 23 Feb 2022 17:00:35 -0800
Subject: [PATCH 1/1] games/OpenRA: updated for version 20210321

---
 games/OpenRA/OpenRA.SlackBuild            | 32 +++++++++++++----------
 games/OpenRA/OpenRA.info                  | 16 ++++++------
 games/OpenRA/fetch-thirdparty-deps.sh.new | 18 -------------
 3 files changed, 26 insertions(+), 40 deletions(-)
 delete mode 100644 games/OpenRA/fetch-thirdparty-deps.sh.new

diff --git a/games/OpenRA/OpenRA.SlackBuild b/games/OpenRA/OpenRA.SlackBuild
index 060cdd3e65c..c47a508fc24 100644
--- a/games/OpenRA/OpenRA.SlackBuild
+++ b/games/OpenRA/OpenRA.SlackBuild
@@ -1,8 +1,8 @@
-#!/bin/bash
+#!/usr/bin/unshare -n /bin/bash
 
 # Slackware build script for OpenRA
 
-# Copyright 2017 Vasily Sora USA
+# Copyright 2017,2022 Vasily Sora USA
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -25,7 +25,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=OpenRA
-VERSION=${VERSION:-20190314}
+VERSION=${VERSION:-20210321}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -49,6 +49,10 @@ fi
 TMP=${TMP:-/tmp/SBo}
 PKG=$TMP/package-$PRGNAM
 OUTPUT=${OUTPUT:-/tmp}
+HOME=$TMP/$PRGNAM-release-$VERSION-source
+DOTNET_CLI_TELEMETRY_OPTOUT=1
+export HOME DOTNET_CLI_TELEMETRY_OPTOUT
+
 
 if [ "$ARCH" = "i586" ]; then
   SLKCFLAGS="-O2 -march=i586 -mtune=i686"
@@ -71,15 +75,15 @@ rm -rf $TMP/$PRGNAM-release-$VERSION-source
 mkdir -p $TMP $PKG $OUTPUT $TMP/$PRGNAM-release-$VERSION-source
 cd $TMP/$PRGNAM-release-$VERSION-source
 tar xvf $CWD/$PRGNAM-release-$VERSION-source.tar.bz2
-cp $CWD/fetch-thirdparty-deps.sh.new thirdparty/fetch-thirdparty-deps.sh
-cp $CWD/download.tar.gz thirdparty
-mkdir thirdparty/download/
-cp $CWD/GeoLite2-Country.mmdb.gz thirdparty/download/
-rm thirdparty/fetch-geoip-db.sh
-touch thirdparty/fetch-geoip-db.sh
-echo "#!/bin/sh" >> thirdparty/fetch-geoip-db.sh
-echo 'echo "success"' >> thirdparty/fetch-geoip-db.sh
-chmod +x thirdparty/fetch-geoip-db.sh
+tar -xzvf $CWD/openra-deps.tar.gz
+cp $CWD/IP2LOCATION-LITE-DB1.IPV6.BIN.ZIP .
+rm fetch-geoip.sh
+touch fetch-geoip.sh
+echo "#!/bin/sh" >> fetch-geoip.sh
+echo 'echo "success"' >> fetch-geoip.sh
+chmod +x fetch-geoip.sh
+
+sed -i 's/msbuild/dotnet\ msbuild/g' ./Makefile ./packaging/functions.sh
 
 chown -R root:root .
 find -L . \
@@ -88,10 +92,10 @@ find -L . \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
-make dependencies
-make all
+make all TARGETPLATFORM=unix-generic  RUNTIME=mono MSBUILD='dotnet msbuild -verbosity:m -nologo'
 make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install DESTDIR=$PKG
 make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install-linux-shortcuts DESTDIR=$PKG
+make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install-linux-appdata DESTDIR=$PKG 
 
 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
diff --git a/games/OpenRA/OpenRA.info b/games/OpenRA/OpenRA.info
index ef12bb2ec9a..4a9b84b8bb4 100644
--- a/games/OpenRA/OpenRA.info
+++ b/games/OpenRA/OpenRA.info
@@ -1,14 +1,14 @@
 PRGNAM="OpenRA"
-VERSION="20190314"
+VERSION="20210321"
 HOMEPAGE="http://www.openra.net/"
-DOWNLOAD="https://github.com/OpenRA/OpenRA/releases/download/release-20190314/OpenRA-release-20190314-source.tar.bz2 \
-          http://repo.khronosschoty.org/Slackware/stuff/OpenRA/20190314/download.tar.gz \
-          http://repo.khronosschoty.org/Slackware/stuff/OpenRA/20190314/GeoLite2-Country.mmdb.gz"
-MD5SUM="4ea1ba7d309bf0482979b5337677d2a3 \
-        e890273530c23cb8571a729d2aced59d \
-        3639895811efb10ad54bf6b40980224e"
+DOWNLOAD="https://github.com/OpenRA/OpenRA/releases/download/release-20210321/OpenRA-release-20210321-source.tar.bz2 \
+          http://repo.schotynet.org/sources/openra/openra-deps.tar.gz \
+	  http://repo.schotynet.org/sources/openra/IP2LOCATION-LITE-DB1.IPV6.BIN.ZIP"
+MD5SUM="38593fbcdda629561d8c0bc8ac1af402 \
+        26b1855341dc15787c7b54945050095d \
+        ef52f92818ebc942ca98108e92a0b802"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES="lua mono"
+REQUIRES="lua mono dotnet-sdk-6.0"
 MAINTAINER="khronosschoty"
 EMAIL="khronosschoty at posteo.org"
diff --git a/games/OpenRA/fetch-thirdparty-deps.sh.new b/games/OpenRA/fetch-thirdparty-deps.sh.new
deleted file mode 100644
index c0f9ae9b5d7..00000000000
--- a/games/OpenRA/fetch-thirdparty-deps.sh.new
+++ /dev/null
@@ -1,18 +0,0 @@
-#!/bin/sh
-
-####
-# This file must stay /bin/sh and POSIX compliant for BSD portability.
-# Copy-paste the entire script into http://shellcheck.net to check.
-####
-
-# Die on any error for Travis CI to automatically retry:
-set -e
-
-download_dir="${0%/*}/download"
-
-mkdir -p "${download_dir}"
-cd "${download_dir}"
-cd ..
-
-tar -xvf download.tar.gz
-
-- 
2.35.1

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

From khronosschoty at posteo.org  Thu Feb 24 03:26:19 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 24 Feb 2022 03:26:19 +0000
Subject: [Slackbuilds-users]
 0001-games-OpenRA-updated-for-version-20210321.patch
Message-ID: <Yhb62xcWUDvgEdr9@posteo.de>

and I just noticed, althought I tested the solution with unshare... my
tests using it with a shabang where less than accurate and my typo gave
me the false impression it worked. 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 870 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220224/bd6204d3/attachment.asc>

From khronosschoty at posteo.org  Thu Feb 24 03:39:51 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 24 Feb 2022 03:39:51 +0000
Subject: [Slackbuilds-users]
 0001-games-OpenRA-updated-for-version-20210321.patch
Message-ID: <Yhb+B8ZVQpAvYe86@posteo.de>

Okay, 

So using the shbang to invoke unshare was a bad idea and poorly tested.
So I fixed the shabang and just put unshare where its needed. Now
everything should work as intended.
-------------- next part --------------
From 98b7f1d873e889f4282e6b27ed243ff0db5054f0 Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 23 Feb 2022 17:00:35 -0800
Subject: [PATCH 1/1] games/OpenRA: updated for version 20210321

---
 games/OpenRA/OpenRA.SlackBuild            | 30 +++++++++++++----------
 games/OpenRA/OpenRA.info                  | 16 ++++++------
 games/OpenRA/fetch-thirdparty-deps.sh.new | 18 --------------
 3 files changed, 25 insertions(+), 39 deletions(-)
 delete mode 100644 games/OpenRA/fetch-thirdparty-deps.sh.new

diff --git a/games/OpenRA/OpenRA.SlackBuild b/games/OpenRA/OpenRA.SlackBuild
index 060cdd3e65c..889f3407afa 100644
--- a/games/OpenRA/OpenRA.SlackBuild
+++ b/games/OpenRA/OpenRA.SlackBuild
@@ -2,7 +2,7 @@
 
 # Slackware build script for OpenRA
 
-# Copyright 2017 Vasily Sora USA
+# Copyright 2017,2022 Vasily Sora USA
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -25,7 +25,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=OpenRA
-VERSION=${VERSION:-20190314}
+VERSION=${VERSION:-20210321}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -49,6 +49,10 @@ fi
 TMP=${TMP:-/tmp/SBo}
 PKG=$TMP/package-$PRGNAM
 OUTPUT=${OUTPUT:-/tmp}
+HOME=$TMP/$PRGNAM-release-$VERSION-source
+DOTNET_CLI_TELEMETRY_OPTOUT=1
+export HOME DOTNET_CLI_TELEMETRY_OPTOUT
+
 
 if [ "$ARCH" = "i586" ]; then
   SLKCFLAGS="-O2 -march=i586 -mtune=i686"
@@ -71,15 +75,15 @@ rm -rf $TMP/$PRGNAM-release-$VERSION-source
 mkdir -p $TMP $PKG $OUTPUT $TMP/$PRGNAM-release-$VERSION-source
 cd $TMP/$PRGNAM-release-$VERSION-source
 tar xvf $CWD/$PRGNAM-release-$VERSION-source.tar.bz2
-cp $CWD/fetch-thirdparty-deps.sh.new thirdparty/fetch-thirdparty-deps.sh
-cp $CWD/download.tar.gz thirdparty
-mkdir thirdparty/download/
-cp $CWD/GeoLite2-Country.mmdb.gz thirdparty/download/
-rm thirdparty/fetch-geoip-db.sh
-touch thirdparty/fetch-geoip-db.sh
-echo "#!/bin/sh" >> thirdparty/fetch-geoip-db.sh
-echo 'echo "success"' >> thirdparty/fetch-geoip-db.sh
-chmod +x thirdparty/fetch-geoip-db.sh
+tar -xzvf $CWD/openra-deps.tar.gz
+cp $CWD/IP2LOCATION-LITE-DB1.IPV6.BIN.ZIP .
+rm fetch-geoip.sh
+touch fetch-geoip.sh
+echo "#!/bin/sh" >> fetch-geoip.sh
+echo 'echo "success"' >> fetch-geoip.sh
+chmod +x fetch-geoip.sh
+
+sed -i 's/msbuild/dotnet\ msbuild/g' ./Makefile ./packaging/functions.sh
 
 chown -R root:root .
 find -L . \
@@ -88,10 +92,10 @@ find -L . \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
-make dependencies
-make all
+unshare -n make all TARGETPLATFORM=unix-generic  RUNTIME=mono MSBUILD='dotnet msbuild -verbosity:m -nologo'
 make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install DESTDIR=$PKG
 make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install-linux-shortcuts DESTDIR=$PKG
+make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install-linux-appdata DESTDIR=$PKG 
 
 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
diff --git a/games/OpenRA/OpenRA.info b/games/OpenRA/OpenRA.info
index ef12bb2ec9a..4a9b84b8bb4 100644
--- a/games/OpenRA/OpenRA.info
+++ b/games/OpenRA/OpenRA.info
@@ -1,14 +1,14 @@
 PRGNAM="OpenRA"
-VERSION="20190314"
+VERSION="20210321"
 HOMEPAGE="http://www.openra.net/"
-DOWNLOAD="https://github.com/OpenRA/OpenRA/releases/download/release-20190314/OpenRA-release-20190314-source.tar.bz2 \
-          http://repo.khronosschoty.org/Slackware/stuff/OpenRA/20190314/download.tar.gz \
-          http://repo.khronosschoty.org/Slackware/stuff/OpenRA/20190314/GeoLite2-Country.mmdb.gz"
-MD5SUM="4ea1ba7d309bf0482979b5337677d2a3 \
-        e890273530c23cb8571a729d2aced59d \
-        3639895811efb10ad54bf6b40980224e"
+DOWNLOAD="https://github.com/OpenRA/OpenRA/releases/download/release-20210321/OpenRA-release-20210321-source.tar.bz2 \
+          http://repo.schotynet.org/sources/openra/openra-deps.tar.gz \
+	  http://repo.schotynet.org/sources/openra/IP2LOCATION-LITE-DB1.IPV6.BIN.ZIP"
+MD5SUM="38593fbcdda629561d8c0bc8ac1af402 \
+        26b1855341dc15787c7b54945050095d \
+        ef52f92818ebc942ca98108e92a0b802"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES="lua mono"
+REQUIRES="lua mono dotnet-sdk-6.0"
 MAINTAINER="khronosschoty"
 EMAIL="khronosschoty at posteo.org"
diff --git a/games/OpenRA/fetch-thirdparty-deps.sh.new b/games/OpenRA/fetch-thirdparty-deps.sh.new
deleted file mode 100644
index c0f9ae9b5d7..00000000000
--- a/games/OpenRA/fetch-thirdparty-deps.sh.new
+++ /dev/null
@@ -1,18 +0,0 @@
-#!/bin/sh
-
-####
-# This file must stay /bin/sh and POSIX compliant for BSD portability.
-# Copy-paste the entire script into http://shellcheck.net to check.
-####
-
-# Die on any error for Travis CI to automatically retry:
-set -e
-
-download_dir="${0%/*}/download"
-
-mkdir -p "${download_dir}"
-cd "${download_dir}"
-cd ..
-
-tar -xvf download.tar.gz
-
-- 
2.35.1

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

From willysr at slackbuilds.org  Thu Feb 24 05:00:45 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 24 Feb 2022 12:00:45 +0700
Subject: [Slackbuilds-users] Update for aom (multimedia)
In-Reply-To: <YhW7LP/JK+gzEH7N@ilium.andrews-corner.org>
References: <YhR8gmgklaYZXCw3@ilium.andrews-corner.org>
 <YhW7LP/JK+gzEH7N@ilium.andrews-corner.org>
Message-ID: <5e78b5f2-8c47-a384-ae17-dca5d9efd7c4@slackbuilds.org>

>>  2. I have made some small changes to the install paths, an error that
>>     I made in old versions of the SlackBuild was generating a faulty
>>     pkconfig file. This may still be an issue in the script for 14.2
>>     which I will check when the dust settles with 15.0.
> 
> Sure enough I cranked up a VM for 14.2 and the SlackBuild for aom
> (multimedia) creates a malformed pkgconfig file. The fix is pretty
> straightforward and I have attached a patch that will make the small
> correction required under 14.2.
> 
> Still kicking myself for this old error which was not noticed by me
> for a looooong time.

Hi Andrew
We no longer provide support for 14.2 repo since Slackware 15.0 is out.
We are working on getting 15.0 repository, so can you test with
Slackware 15.0 instead?

Thanks


-- 
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/20220224/0757c85b/attachment.asc>

From willysr at slackbuilds.org  Thu Feb 24 05:02:48 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 24 Feb 2022 12:02:48 +0700
Subject: [Slackbuilds-users] wrong md5sum for protobuf-c 1.4.0 package
In-Reply-To: <CAK09-vmsyWW_uRw5ddXcYpmDwZcSS5vgH6xcSONd7kbfyTHkmQ@mail.gmail.com>
References: <CAK09-vmsyWW_uRw5ddXcYpmDwZcSS5vgH6xcSONd7kbfyTHkmQ@mail.gmail.com>
Message-ID: <0453d05a-46a0-8c20-a540-ed237e8f5a24@slackbuilds.org>

> looks like the checksum wasn't updated in the 1.4.0 upgrade:
> 
> Found protobuf-c-1.4.0.tar.gz in /var/cache/sbopkg.
> Checking MD5SUM:
>   MD5SUM check for protobuf-c-1.4.0.tar.gz ... FAILED!
>     Expected: dabc05a5f11c21b96d8d6db4153f5343
>     Found:    10e1103a012ce0877c32367949a2fa6e

Thanks,
pushed to my branch


-- 
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/20220224/4a3da356/attachment-0001.asc>

From willysr at slackbuilds.org  Thu Feb 24 05:08:21 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 24 Feb 2022 12:08:21 +0700
Subject: [Slackbuilds-users] palemoon-bin SlackBuild
In-Reply-To: <YhQg43wz+tJ8of99@posteo.de>
References: <YhQg43wz+tJ8of99@posteo.de>
Message-ID: <73bc2fc5-9c54-835d-d90f-4f3a063b7751@slackbuilds.org>

> palemoon binaries are provided in two flavors gtk2 and gtk3. I was
> wondering what the best way to support both of them would be. Should I
> just include downloads to both? or should these be spun out out into two
> different SlackBuilds?

It's up to you as maintainer
if you can support both, that's fine


-- 
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/20220224/cc97332c/attachment.asc>

From andrew.david.strong at gmail.com  Thu Feb 24 05:49:05 2022
From: andrew.david.strong at gmail.com (andrew)
Date: Thu, 24 Feb 2022 16:49:05 +1100
Subject: [Slackbuilds-users] Update for aom (multimedia)
In-Reply-To: <5e78b5f2-8c47-a384-ae17-dca5d9efd7c4@slackbuilds.org>
References: <YhR8gmgklaYZXCw3@ilium.andrews-corner.org>
 <YhW7LP/JK+gzEH7N@ilium.andrews-corner.org>
 <5e78b5f2-8c47-a384-ae17-dca5d9efd7c4@slackbuilds.org>
Message-ID: <YhccUWWNPTtuqZIQ@ilium.andrews-corner.org>

On Thu, Feb 24, 2022 at 12:00:45PM +0700, Willy Sudiarto Raharjo wrote:

> We no longer provide support for 14.2 repo since Slackware 15.0 is
> out.  We are working on getting 15.0 repository, so can you test
> with Slackware 15.0 instead?

Fair enough. The first email in this thread holds a patch for an
updated aom and Slackware 15.0.

Thanks,

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

From khronosschoty at posteo.org  Thu Feb 24 06:13:01 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 24 Feb 2022 06:13:01 +0000
Subject: [Slackbuilds-users]
 0001-network-palemoon-bin-updated-for-version-29.4.4.patch
Message-ID: <Yhch7Q5V8Hdf5GRJ@posteo.de>

palemoon-bin updated for version 29.4.4
-------------- next part --------------
From 54d0161bf3113c28309fd02ec816292a03f5945e Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 23 Feb 2022 22:11:41 -0800
Subject: [PATCH 1/1] network/palemoon-bin: updated for version 29.4.4

---
 network/palemoon-bin/palemoon-bin.SlackBuild | 4 ++--
 network/palemoon-bin/palemoon-bin.info       | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/network/palemoon-bin/palemoon-bin.SlackBuild b/network/palemoon-bin/palemoon-bin.SlackBuild
index b2d88a41639..89a00976747 100644
--- a/network/palemoon-bin/palemoon-bin.SlackBuild
+++ b/network/palemoon-bin/palemoon-bin.SlackBuild
@@ -4,7 +4,7 @@
 
 # Copyright 2015 pomfland
 # Copyright 2017-2018 Skaendo <skaendo at excite dot com>
-# Copyright 2018 Vasily Sora USA
+# Copyright 2018,2022 Vasily Sora USA
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -28,7 +28,7 @@ cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=palemoon-bin
 SRCNAM=palemoon
-VERSION=${VERSION:-29.1.1}
+VERSION=${VERSION:-29.4.4}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
diff --git a/network/palemoon-bin/palemoon-bin.info b/network/palemoon-bin/palemoon-bin.info
index db48f7cb3df..c72291571f2 100644
--- a/network/palemoon-bin/palemoon-bin.info
+++ b/network/palemoon-bin/palemoon-bin.info
@@ -1,10 +1,10 @@
 PRGNAM="palemoon-bin"
-VERSION="29.1.1"
+VERSION="29.4.4"
 HOMEPAGE="https://www.palemoon.org/"
 DOWNLOAD="UNSUPPORTED"
 MD5SUM=""
-DOWNLOAD_x86_64="http://linux.palemoon.org/datastore/release/palemoon-29.1.1.linux-x86_64-gtk2.tar.xz"
-MD5SUM_x86_64="1a39e784adcd7891c391195fabcbb06a"
+DOWNLOAD_x86_64="http://linux.palemoon.org/datastore/release/palemoon-29.4.4.linux-x86_64-gtk2.tar.xz"
+MD5SUM_x86_64="0e6295ed60fb1783e95f436a990adb47"
 REQUIRES=""
 MAINTAINER="khronosschoty"
 EMAIL="khronosschoty at posteo.org"
-- 
2.35.1

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

From khronosschoty at posteo.org  Thu Feb 24 06:20:28 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 24 Feb 2022 06:20:28 +0000
Subject: [Slackbuilds-users]
 0001-system-eltclsh-updated-for-version-1.18.patch
Message-ID: <YhcjrGASAe15rtwR@posteo.de>

eltclsh updated for version 1.18
-------------- next part --------------
From f3aa03163cf7580f4f10d97941202b7b8d0f5fd9 Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 23 Feb 2022 22:18:25 -0800
Subject: [PATCH 1/1] system/eltclsh: updated for version 1.18

---
 system/eltclsh/eltclsh.SlackBuild | 4 ++--
 system/eltclsh/eltclsh.info       | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/system/eltclsh/eltclsh.SlackBuild b/system/eltclsh/eltclsh.SlackBuild
index 553a43ec813..0bd090f2e42 100644
--- a/system/eltclsh/eltclsh.SlackBuild
+++ b/system/eltclsh/eltclsh.SlackBuild
@@ -2,7 +2,7 @@
 
 # Slackware build script for eltclsh
 
-# Copyright 2016,2018 Khronosschoty
+# Copyright 2016,2018,2022 Khronosschoty
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -25,7 +25,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=eltclsh
-VERSION=${VERSION:-1.17}
+VERSION=${VERSION:-1.18}
 BUILD=${BUILD:-2}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
diff --git a/system/eltclsh/eltclsh.info b/system/eltclsh/eltclsh.info
index 0fff1fea200..792aa8a6c82 100644
--- a/system/eltclsh/eltclsh.info
+++ b/system/eltclsh/eltclsh.info
@@ -1,8 +1,8 @@
 PRGNAM="eltclsh"
-VERSION="1.17"
+VERSION="1.18"
 HOMEPAGE="http://homepages.laas.fr/mallet/soft/shell/eltclsh"
-DOWNLOAD="http://distfiles.openrobots.org/eltclsh/eltclsh-1.17.tar.gz"
-MD5SUM="e698f5969970feafeff934b1294a37c0"
+DOWNLOAD="http://distfiles.openrobots.org/eltclsh/eltclsh-1.18.tar.gz"
+MD5SUM="f4d5982491b13072a90fffbf0bb37fd5"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""
-- 
2.35.1

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

From mrvladislavovich at gmail.com  Thu Feb 24 06:30:17 2022
From: mrvladislavovich at gmail.com (MyRequiem)
Date: Thu, 24 Feb 2022 10:30:17 +0400
Subject: [Slackbuilds-users] 15.0 branch
Message-ID: <Yhcl+XoN5cRjrANz@lenovo.myrequiem.net>

Hello friends. Why is there no 15.0 branch on slackbuilds.org ?

From khronosschoty at posteo.org  Thu Feb 24 06:37:59 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 24 Feb 2022 06:37:59 +0000
Subject: [Slackbuilds-users]
 0001-network-basilisk-bin-updated-for-version-2022.01.27.patch
Message-ID: <Yhcnx5A+XlQcC47e@posteo.de>

basilisk updated for version 2022.01.27
-------------- next part --------------
From 1107b8f498c948f590980a79eab1e6453744c102 Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Wed, 23 Feb 2022 22:36:48 -0800
Subject: [PATCH 1/1] network/basilisk-bin: updated for version 2022.01.27

---
 network/basilisk-bin/basilisk-bin.SlackBuild | 4 ++--
 network/basilisk-bin/basilisk-bin.info       | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/network/basilisk-bin/basilisk-bin.SlackBuild b/network/basilisk-bin/basilisk-bin.SlackBuild
index de72f568125..cb8c1af715d 100644
--- a/network/basilisk-bin/basilisk-bin.SlackBuild
+++ b/network/basilisk-bin/basilisk-bin.SlackBuild
@@ -2,7 +2,7 @@
 
 # Slackware build script for basilisk-bin
 # Copyright 2018 Skaendo <skaendo at excite dot com>
-# Copyright 2018 Vasily Sora USA
+# Copyright 2018,2022 Vasily Sora USA
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -26,7 +26,7 @@ cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=basilisk-bin
 SRCNAM=basilisk
-VERSION=${VERSION:-2021.03.17}
+VERSION=${VERSION:-2022.01.27}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
diff --git a/network/basilisk-bin/basilisk-bin.info b/network/basilisk-bin/basilisk-bin.info
index 1cf23772cb0..a9010df5341 100644
--- a/network/basilisk-bin/basilisk-bin.info
+++ b/network/basilisk-bin/basilisk-bin.info
@@ -1,10 +1,10 @@
 PRGNAM="basilisk-bin"
-VERSION="2021.03.17"
+VERSION="2022.01.27"
 HOMEPAGE="https://www.basilisk-browser.org"
 DOWNLOAD="UNSUPPORTED"
 MD5SUM=""
-DOWNLOAD_x86_64="http://repo.khronosschoty.org/Slackware/basilisk/basilisk-bin/basilisk-latest.linux64.tar.xz"
-MD5SUM_x86_64="5edda8852f40000a6a66848d2930c8a9"
+DOWNLOAD_x86_64="http://repo.schotynet.org/sources/basilisk-bin/basilisk-latest.linux64.tar.xz"
+MD5SUM_x86_64="9d3728f8fdea1f1a2174d5d5346aa807"
 REQUIRES=""
 MAINTAINER="khronosschoty"
 EMAIL="khronosschoty at posteo.org"
-- 
2.35.1

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

From khronosschoty at posteo.org  Thu Feb 24 06:40:52 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 24 Feb 2022 06:40:52 +0000
Subject: [Slackbuilds-users] 15.0 branch
Message-ID: <YhcodIBcfqWRX0X3@posteo.de>

The 15.0 branch is being prepared, and is not ready yet -- once its
ready, there will be a 15.0 branch. Untl then you can check out
git.slackbuilds.org, and use the master branch.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 870 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220224/7f893a8c/attachment-0001.asc>

From mrvladislavovich at gmail.com  Thu Feb 24 06:46:34 2022
From: mrvladislavovich at gmail.com (MyRequiem)
Date: Thu, 24 Feb 2022 10:46:34 +0400
Subject: [Slackbuilds-users] 15.0 branch
In-Reply-To: <YhcodIBcfqWRX0X3@posteo.de>
References: <YhcodIBcfqWRX0X3@posteo.de>
Message-ID: <YhcpymhODZGCS3vd@lenovo.myrequiem.net>

Re: khronosschoty 24.02.2022 <YhcodIBcfqWRX0X3 at posteo.de>
>The 15.0 branch is being prepared, and is not ready yet -- once its
>ready, there will be a 15.0 branch. Untl then you can check out
>git.slackbuilds.org, and use the master branch.



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

Oh, thank you friend :)

From duncan_roe at optusnet.com.au  Thu Feb 24 09:41:30 2022
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Thu, 24 Feb 2022 20:41:30 +1100
Subject: [Slackbuilds-users] afdko
Message-ID: <YhdSyoNwGTAcF4e1@slk1.local.net>

Hi,

I have an updated afdko.SlackBuild which builds under 15.0.

You need 2 new SlackBuilds to build afdko: python/wheel and python/scikit-build.

Admins, how do you want to handle this? I can put the new SBs in a pull request
with keywords in the comment box (f.i. scikit-build provides skbuild, but a
search on PyPi doesn't tell you that).

Type1_to_OTF exposes new afdko runtime dependencies, many not currently on SBo,
but I think that is best discussed in a separate thread.

Should I submit a pull request with updated afdko and the 2 new SBs?

Cheers ... Duncan.

From slackbuilds at schoepfer.info  Thu Feb 24 18:04:03 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Thu, 24 Feb 2022 19:04:03 +0100
Subject: [Slackbuilds-users] xjadeo fix for build with new portimidi
 2.0.2
In-Reply-To: <53b90b7c-c874-c91a-00cb-01aecfdba7a9@gmail.com>
References: <1789bfa5496c5d8ddf5cf29e2b8ae58c@schoepfer.info>
 <CAPsDuS7DKDYnm7dQ-ttw5vL1i9npHT2K=LxXbYBB67LE1Dujhw@mail.gmail.com>
 <e0374ee2b415a56ded88bcab14ce77e3@schoepfer.info>
 <20220221180730.GI4508@localhost> <20220222033038.GJ4508@localhost>
 <ae809d979442ab57c7a66f5a86894d3b@schoepfer.info>
 <53b90b7c-c874-c91a-00cb-01aecfdba7a9@gmail.com>
Message-ID: <8f93fecc97f6aee7473d849f9823c872@schoepfer.info>

On 2022-02-24 00:45, Andrew Clemons wrote:
> Hi Johannes,
> 
> On 22/02/22 19:44, Franzen via SlackBuilds-users wrote:
>> On 2022-02-22 04:30, Dave Woodfall wrote:
>>> MuseScore
>>> hatari
>>> hydrogen
>>> mame
>>> mixxx
>>> odamex
>>> pd
>>> prboom-plus
>>> pygame
>>> seq24
>>> xjadeo
>>> 
>>> All checked and working.
>> 
>> Thanks for checking.
>> xjadeo could have been fixed with the attached patch, but portmidi was
>> changed for xjadeo with this patch
>> https://git.slackbuilds.org/slackbuilds/patch/?id=933f7aee263bb498d206475a2fcfb0e4186c6653
>> , the others don't need this patch to build.
>> That's what it boils down to.
> 
> I've applied this patch to xjadeo now and removed the compat symlink in
> portmidi. Thanks.

Thank you, appreciated!

From khronosschoty at posteo.org  Thu Feb 24 20:58:32 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 24 Feb 2022 20:58:32 +0000
Subject: [Slackbuilds-users]
 0001-games-beetle-psx-libretro-update-for-version-2022.02.patch
Message-ID: <YhfxeGJXsx391pTr@posteo.de>

If there is no objections I'm adopting beetle-psx-libretro and here is
my first update
-------------- next part --------------
From 5dec6a9ffaf747a1a2f9f73c6ed428519cd4f493 Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Thu, 24 Feb 2022 12:55:51 -0800
Subject: [PATCH 1/1] games/beetle-psx-libretro: update for version
 2022.02.11_88929ae + new maintainer

---
 games/beetle-psx-libretro/README              | 39 ++++++++
 .../beetle-psx-libretro.SlackBuild            | 98 +++++++++++++++++++
 .../beetle-psx-libretro.info                  | 10 ++
 games/beetle-psx-libretro/slack-desc          | 19 ++++
 4 files changed, 166 insertions(+)
 create mode 100644 games/beetle-psx-libretro/README
 create mode 100755 games/beetle-psx-libretro/beetle-psx-libretro.SlackBuild
 create mode 100644 games/beetle-psx-libretro/beetle-psx-libretro.info
 create mode 100644 games/beetle-psx-libretro/slack-desc

diff --git a/games/beetle-psx-libretro/README b/games/beetle-psx-libretro/README
new file mode 100644
index 00000000000..8f9444318fe
--- /dev/null
+++ b/games/beetle-psx-libretro/README
@@ -0,0 +1,39 @@
+Mednafen PSX (Beetle PSX) is a Sony PlayStation1 video game system
+emulator that can be used as a libretro core. It is a libretro port of
+Mednafen PlayStation.
+
+Mednafen-PSX requires the following BIOS image files for operation:
+
+* scph5500.bin (MD5 sum: 8dd7d5296a650fac7319bce665a6a53c) NTSC-J
+* scph5501.bin (MD5 sum: 490f666e1afb15b7362b406ed1cea246) NTSC-U
+* scph5502.bin (MD5 sum: 32736f17079d0b2b7024407c39bd3050) PAL
+
+The bios names are case sensitive.
+
+The scph7003.bin BIOS image is the same as scph5501.bin, but will need
+to be renamed to scph5501.bin to be used.
+
+Mednafen can load CD-ROM games from a ripped/dumped copy of the
+disc such as CUE+BIN, CloneCD "CCD/IMG/SUB" rips and cdrdao "TOC"
+files. For games with more than one CD create a M3U file(plain-text,
+".m3u" extension) and enter the filenames of the CUE/TOC/CCD files.
+
+Beetle PSX can use an OpenGL or Vulkan renderer instead of the
+accurate software renderer. This will require support in the libretro
+frontend, video card and driver.
+
+To switch between OpenGL and Vulkan renderers configure the video
+driver in RetroArch. This can be done in the menu at 'Settings >
+Drivers > Video Driver'.
+
+To build the OpenGL renderer use:
+  OPENGL=1 ./beetle-psx-libretro.SlackBuild
+
+To build the Vulkan renderer use:
+  VULKAN=1 ./beetle-psx-libretro.SlackBuild
+
+To build both the OpenGL and Vulkan renderers use:
+  HW=1 ./beetle-psx-libretro.SlackBuild
+
+To build the debugging symbols use:
+  DEBUG=1 ./beetle-psx-libretro.SlackBuild
diff --git a/games/beetle-psx-libretro/beetle-psx-libretro.SlackBuild b/games/beetle-psx-libretro/beetle-psx-libretro.SlackBuild
new file mode 100755
index 00000000000..0be38ea3b48
--- /dev/null
+++ b/games/beetle-psx-libretro/beetle-psx-libretro.SlackBuild
@@ -0,0 +1,98 @@
+#!/bin/sh
+
+# Slackware build script for beetle-psx-libretro
+
+# Copyright 2016-2018 Hunter Sezen
+# Copyright 2022 Vasily Sora USA
+# 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.
+
+PRGNAM=beetle-psx-libretro
+LIBNAM=mednafen_psx_libretro
+VERSION=${VERSION:-2022.02.11_88929ae}
+BUILD=${BUILD:-1}
+TAG=${TAG:-_SBo}
+
+if [ -z "$ARCH" ]; then
+  case "$( uname -m )" in
+    i?86) ARCH=i586 ;;
+    arm*) ARCH=arm ;;
+       *) ARCH=$( uname -m ) ;;
+  esac
+fi
+
+CWD=$(pwd)
+TMP=${TMP:-/tmp/SBo}
+PKG=$TMP/package-$PRGNAM
+OUTPUT=${OUTPUT:-/tmp}
+
+LIBDIRSUFFIX=
+[ "$ARCH" = x86_64 ] && LIBDIRSUFFIX=64
+
+set -eu
+
+rm -rf $PKG
+mkdir -p $TMP $PKG $OUTPUT
+cd $TMP
+rm -rf $PRGNAM-$VERSION
+tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
+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 {} \;
+
+[ "${DEBUG:=0}" != 0 ] && DEBUG=1
+[ "${HW:-0}" != 0 ] && { OPENGL=1; VULKAN=1; }
+[ "${OPENGL:=0}" != 0 ] && OPENGL=1
+[ "${VULKAN:=0}" != 0 ] && VULKAN=1
+
+if [ $OPENGL != 0 ] || [ $VULKAN != 0 ]; then
+  LIBNAM="$(printf %s "$LIBNAM" | sed 's/psx/psx_hw/')"
+fi
+
+make \
+  DEBUG=$DEBUG \
+  VULKAN_DEBUG=$DEBUG \
+  HAVE_OPENGL=$OPENGL \
+  HAVE_VULKAN=$VULKAN \
+  GIT_VERSION="${VERSION#*_}"
+
+install -Dm0644 $LIBNAM.so $PKG/usr/lib${LIBDIRSUFFIX}/libretro/$LIBNAM.so
+
+if [ $DEBUG = 0 ]; then
+  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
+fi
+
+mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION/parallel-psx
+for DOCDIR in . parallel-psx; do
+  for DOC in COPYING README.md; do
+    cp -a $DOCDIR/$DOC $PKG/usr/doc/$PRGNAM-$VERSION/$DOCDIR
+  done
+done
+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:-tgz}
diff --git a/games/beetle-psx-libretro/beetle-psx-libretro.info b/games/beetle-psx-libretro/beetle-psx-libretro.info
new file mode 100644
index 00000000000..5e013141b36
--- /dev/null
+++ b/games/beetle-psx-libretro/beetle-psx-libretro.info
@@ -0,0 +1,10 @@
+PRGNAM="beetle-psx-libretro"
+VERSION="2022.02.11_88929ae"
+HOMEPAGE="https://www.libretro.com/"
+DOWNLOAD="http://repo.schotynet.org/sources/libretro/beetle-psx-libretro-2022.02.11_88929ae.tar.gz"
+MD5SUM="392b6e728b565c4f1cc4189e115868d5"
+DOWNLOAD_x86_64=""
+MD5SUM_x86_64=""
+REQUIRES="RetroArch"
+MAINTAINER="khronosschoty"
+EMAIL="khronosschoty at posteo.org"
diff --git a/games/beetle-psx-libretro/slack-desc b/games/beetle-psx-libretro/slack-desc
new file mode 100644
index 00000000000..c4d2bc1506a
--- /dev/null
+++ b/games/beetle-psx-libretro/slack-desc
@@ -0,0 +1,19 @@
+# HOW TO EDIT THIS FILE:
+# The "handy ruler" below makes it easier to edit a package description.
+# Line up the first '|' above the ':' following the base package name, and
+# the '|' on the right side marks the last column you can put a character in.
+# You must make exactly 11 lines for the formatting to be correct.  It's also
+# customary to leave one space after the ':' except on otherwise blank lines.
+
+                   |-----handy-ruler------------------------------------------------------|
+beetle-psx-libretro: beetle-psx-libretro (libretro fork of Mednafen PSX)
+beetle-psx-libretro:
+beetle-psx-libretro: Mednafen PSX (Beetle PSX) is a Sony PlayStation1 video game system
+beetle-psx-libretro: emulator that can be used as a libretro core. It is a libretro port
+beetle-psx-libretro: of Mednafen PlayStation.
+beetle-psx-libretro:
+beetle-psx-libretro: Homepage: https://www.libretro.com/
+beetle-psx-libretro:
+beetle-psx-libretro:
+beetle-psx-libretro:
+beetle-psx-libretro:
-- 
2.35.1

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

From khronosschoty at posteo.org  Thu Feb 24 21:06:28 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Thu, 24 Feb 2022 21:06:28 +0000
Subject: [Slackbuilds-users]
 0001-games-beetle-psx-libretro-update-for-version-2022.02.patch
Message-ID: <YhfzVGBznlIu89Nu@posteo.de>

forgot to do a few 15 template sytle changed / updates -- fixed
-------------- next part --------------
From a8abcab5e2aac73a37f40c424c314710c8ccafa8 Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Thu, 24 Feb 2022 12:55:51 -0800
Subject: [PATCH 1/1] games/beetle-psx-libretro: update for version
 2022.02.11_88929ae + new maintainer

---
 games/beetle-psx-libretro/README              |  39 +++++++
 .../beetle-psx-libretro.SlackBuild            | 108 ++++++++++++++++++
 .../beetle-psx-libretro.info                  |  10 ++
 games/beetle-psx-libretro/slack-desc          |  19 +++
 4 files changed, 176 insertions(+)
 create mode 100644 games/beetle-psx-libretro/README
 create mode 100755 games/beetle-psx-libretro/beetle-psx-libretro.SlackBuild
 create mode 100644 games/beetle-psx-libretro/beetle-psx-libretro.info
 create mode 100644 games/beetle-psx-libretro/slack-desc

diff --git a/games/beetle-psx-libretro/README b/games/beetle-psx-libretro/README
new file mode 100644
index 00000000000..8f9444318fe
--- /dev/null
+++ b/games/beetle-psx-libretro/README
@@ -0,0 +1,39 @@
+Mednafen PSX (Beetle PSX) is a Sony PlayStation1 video game system
+emulator that can be used as a libretro core. It is a libretro port of
+Mednafen PlayStation.
+
+Mednafen-PSX requires the following BIOS image files for operation:
+
+* scph5500.bin (MD5 sum: 8dd7d5296a650fac7319bce665a6a53c) NTSC-J
+* scph5501.bin (MD5 sum: 490f666e1afb15b7362b406ed1cea246) NTSC-U
+* scph5502.bin (MD5 sum: 32736f17079d0b2b7024407c39bd3050) PAL
+
+The bios names are case sensitive.
+
+The scph7003.bin BIOS image is the same as scph5501.bin, but will need
+to be renamed to scph5501.bin to be used.
+
+Mednafen can load CD-ROM games from a ripped/dumped copy of the
+disc such as CUE+BIN, CloneCD "CCD/IMG/SUB" rips and cdrdao "TOC"
+files. For games with more than one CD create a M3U file(plain-text,
+".m3u" extension) and enter the filenames of the CUE/TOC/CCD files.
+
+Beetle PSX can use an OpenGL or Vulkan renderer instead of the
+accurate software renderer. This will require support in the libretro
+frontend, video card and driver.
+
+To switch between OpenGL and Vulkan renderers configure the video
+driver in RetroArch. This can be done in the menu at 'Settings >
+Drivers > Video Driver'.
+
+To build the OpenGL renderer use:
+  OPENGL=1 ./beetle-psx-libretro.SlackBuild
+
+To build the Vulkan renderer use:
+  VULKAN=1 ./beetle-psx-libretro.SlackBuild
+
+To build both the OpenGL and Vulkan renderers use:
+  HW=1 ./beetle-psx-libretro.SlackBuild
+
+To build the debugging symbols use:
+  DEBUG=1 ./beetle-psx-libretro.SlackBuild
diff --git a/games/beetle-psx-libretro/beetle-psx-libretro.SlackBuild b/games/beetle-psx-libretro/beetle-psx-libretro.SlackBuild
new file mode 100755
index 00000000000..aef6506a6d0
--- /dev/null
+++ b/games/beetle-psx-libretro/beetle-psx-libretro.SlackBuild
@@ -0,0 +1,108 @@
+#!/bin/bash
+
+# Slackware build script for beetle-psx-libretro
+
+# Copyright 2016-2018 Hunter Sezen
+# Copyright 2022 Vasily Sora USA
+# 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=beetle-psx-libretro
+LIBNAM=mednafen_psx_libretro
+VERSION=${VERSION:-2022.02.11_88929ae}
+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}
+
+LIBDIRSUFFIX=
+[ "$ARCH" = x86_64 ] && LIBDIRSUFFIX=64
+
+set -eu
+
+rm -rf $PKG
+mkdir -p $TMP $PKG $OUTPUT
+cd $TMP
+rm -rf $PRGNAM-$VERSION
+tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
+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 {} \;
+
+[ "${DEBUG:=0}" != 0 ] && DEBUG=1
+[ "${HW:-0}" != 0 ] && { OPENGL=1; VULKAN=1; }
+[ "${OPENGL:=0}" != 0 ] && OPENGL=1
+[ "${VULKAN:=0}" != 0 ] && VULKAN=1
+
+if [ $OPENGL != 0 ] || [ $VULKAN != 0 ]; then
+  LIBNAM="$(printf %s "$LIBNAM" | sed 's/psx/psx_hw/')"
+fi
+
+make \
+  DEBUG=$DEBUG \
+  VULKAN_DEBUG=$DEBUG \
+  HAVE_OPENGL=$OPENGL \
+  HAVE_VULKAN=$VULKAN \
+  GIT_VERSION="${VERSION#*_}"
+
+install -Dm0644 $LIBNAM.so $PKG/usr/lib${LIBDIRSUFFIX}/libretro/$LIBNAM.so
+
+if [ $DEBUG = 0 ]; then
+  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
+fi
+
+mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION/parallel-psx
+for DOCDIR in . parallel-psx; do
+  for DOC in COPYING README.md; do
+    cp -a $DOCDIR/$DOC $PKG/usr/doc/$PRGNAM-$VERSION/$DOCDIR
+  done
+done
+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
diff --git a/games/beetle-psx-libretro/beetle-psx-libretro.info b/games/beetle-psx-libretro/beetle-psx-libretro.info
new file mode 100644
index 00000000000..5e013141b36
--- /dev/null
+++ b/games/beetle-psx-libretro/beetle-psx-libretro.info
@@ -0,0 +1,10 @@
+PRGNAM="beetle-psx-libretro"
+VERSION="2022.02.11_88929ae"
+HOMEPAGE="https://www.libretro.com/"
+DOWNLOAD="http://repo.schotynet.org/sources/libretro/beetle-psx-libretro-2022.02.11_88929ae.tar.gz"
+MD5SUM="392b6e728b565c4f1cc4189e115868d5"
+DOWNLOAD_x86_64=""
+MD5SUM_x86_64=""
+REQUIRES="RetroArch"
+MAINTAINER="khronosschoty"
+EMAIL="khronosschoty at posteo.org"
diff --git a/games/beetle-psx-libretro/slack-desc b/games/beetle-psx-libretro/slack-desc
new file mode 100644
index 00000000000..c4d2bc1506a
--- /dev/null
+++ b/games/beetle-psx-libretro/slack-desc
@@ -0,0 +1,19 @@
+# HOW TO EDIT THIS FILE:
+# The "handy ruler" below makes it easier to edit a package description.
+# Line up the first '|' above the ':' following the base package name, and
+# the '|' on the right side marks the last column you can put a character in.
+# You must make exactly 11 lines for the formatting to be correct.  It's also
+# customary to leave one space after the ':' except on otherwise blank lines.
+
+                   |-----handy-ruler------------------------------------------------------|
+beetle-psx-libretro: beetle-psx-libretro (libretro fork of Mednafen PSX)
+beetle-psx-libretro:
+beetle-psx-libretro: Mednafen PSX (Beetle PSX) is a Sony PlayStation1 video game system
+beetle-psx-libretro: emulator that can be used as a libretro core. It is a libretro port
+beetle-psx-libretro: of Mednafen PlayStation.
+beetle-psx-libretro:
+beetle-psx-libretro: Homepage: https://www.libretro.com/
+beetle-psx-libretro:
+beetle-psx-libretro:
+beetle-psx-libretro:
+beetle-psx-libretro:
-- 
2.35.1

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 870 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220224/54d6a6d5/attachment-0001.asc>

From andrew.david.strong at gmail.com  Fri Feb 25 05:05:28 2022
From: andrew.david.strong at gmail.com (andrew)
Date: Fri, 25 Feb 2022 16:05:28 +1100
Subject: [Slackbuilds-users] david (libraries) update for 15.0
Message-ID: <YhhjmPA1ScE2Emp7@ilium.andrews-corner.org>

Hi,

I attach a patch to update dav1d for Slackware 15.0, just a simple
version bump required for this one. Built against git master...

Andrew

-- 
You think that's air you're breathing now?
-------------- next part --------------
diff --git a/libraries/dav1d/dav1d.SlackBuild b/libraries/dav1d/dav1d.SlackBuild
index 524ce913..eeb0ad4e 100644
--- a/libraries/dav1d/dav1d.SlackBuild
+++ b/libraries/dav1d/dav1d.SlackBuild
@@ -2,7 +2,7 @@
 # ----------------------------------------------------------------------
 # Slackware build script for dav1d
 #
-# Copyright (c) 2019-2020 Andrew Strong, Blue Mountains, Australia.
+# Copyright (c) 2019-2022 Andrew Strong, Blue Mountains, Australia.
 #
 #   Permission to use, copy, modify, and distribute this software for
 #   any purpose with or without fee is hereby granted, provided that
@@ -26,7 +26,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=dav1d
-VERSION=${VERSION:-0.8.2}
+VERSION=${VERSION:-0.9.2}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
diff --git a/libraries/dav1d/dav1d.info b/libraries/dav1d/dav1d.info
index 9f6baa5c..e67889eb 100644
--- a/libraries/dav1d/dav1d.info
+++ b/libraries/dav1d/dav1d.info
@@ -1,8 +1,8 @@
 PRGNAM="dav1d"
-VERSION="0.8.2"
+VERSION="0.9.2"
 HOMEPAGE="https://code.videolan.org/videolan/dav1d"
-DOWNLOAD="http://downloads.videolan.org/pub/videolan/dav1d/0.8.2/dav1d-0.8.2.tar.xz"
-MD5SUM="985a5ba33c184e2884b7bb3e1b339438"
+DOWNLOAD="http://downloads.videolan.org/pub/videolan/dav1d/0.9.2/dav1d-0.9.2.tar.xz"
+MD5SUM="fa895eebf5619aaad50bba19a8b99c5c"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""

From willysr at slackbuilds.org  Fri Feb 25 06:24:40 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 25 Feb 2022 13:24:40 +0700
Subject: [Slackbuilds-users]
 0001-network-palemoon-bin-updated-for-version-29.4.4.patch
In-Reply-To: <Yhch7Q5V8Hdf5GRJ@posteo.de>
References: <Yhch7Q5V8Hdf5GRJ@posteo.de>
Message-ID: <808b4dea-c0e9-5660-3caf-924d79a907dc@slackbuilds.org>

> palemoon-bin updated for version 29.4.4

merged to my branch


-- 
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/20220225/dca2c607/attachment.asc>

From willysr at slackbuilds.org  Fri Feb 25 06:27:20 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 25 Feb 2022 13:27:20 +0700
Subject: [Slackbuilds-users]
 0001-system-eltclsh-updated-for-version-1.18.patch
In-Reply-To: <YhcjrGASAe15rtwR@posteo.de>
References: <YhcjrGASAe15rtwR@posteo.de>
Message-ID: <8e8c2a23-91f1-c5db-3bf1-9141b8c2f87c@slackbuilds.org>

> eltclsh updated for version 1.18

merged to my branch


-- 
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/20220225/e4eb9b6c/attachment.asc>

From willysr at slackbuilds.org  Fri Feb 25 06:28:27 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 25 Feb 2022 13:28:27 +0700
Subject: [Slackbuilds-users] david (libraries) update for 15.0
In-Reply-To: <YhhjmPA1ScE2Emp7@ilium.andrews-corner.org>
References: <YhhjmPA1ScE2Emp7@ilium.andrews-corner.org>
Message-ID: <1a80df89-3bea-c097-cf3e-ff86de2864e8@slackbuilds.org>

> I attach a patch to update dav1d for Slackware 15.0, just a simple
> version bump required for this one. Built against git master...

pushed to my branch


-- 
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/20220225/b35ad0b0/attachment.asc>

From willysr at slackbuilds.org  Fri Feb 25 06:30:53 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 25 Feb 2022 13:30:53 +0700
Subject: [Slackbuilds-users]
 0001-games-beetle-psx-libretro-update-for-version-2022.02.patch
In-Reply-To: <YhfzVGBznlIu89Nu@posteo.de>
References: <YhfzVGBznlIu89Nu@posteo.de>
Message-ID: <6e6f8075-a968-781a-aef8-befd7d0b9f19@slackbuilds.org>

> forgot to do a few 15 template sytle changed / updates -- fixed

this script was removed back in April 2021
please submit it later when 15.0 submission is open


-- 
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/20220225/18901438/attachment.asc>

From willysr at slackbuilds.org  Fri Feb 25 06:32:51 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 25 Feb 2022 13:32:51 +0700
Subject: [Slackbuilds-users] afdko
In-Reply-To: <YhdSyoNwGTAcF4e1@slk1.local.net>
References: <YhdSyoNwGTAcF4e1@slk1.local.net>
Message-ID: <670a758d-1608-cbae-7613-3514d58220ae@slackbuilds.org>

> I have an updated afdko.SlackBuild which builds under 15.0.
> 
> You need 2 new SlackBuilds to build afdko: python/wheel and python/scikit-build.
> 
> Admins, how do you want to handle this? I can put the new SBs in a pull request
> with keywords in the comment box (f.i. scikit-build provides skbuild, but a
> search on PyPi doesn't tell you that).
> 
> Type1_to_OTF exposes new afdko runtime dependencies, many not currently on SBo,
> but I think that is best discussed in a separate thread.
> 
> Should I submit a pull request with updated afdko and the 2 new SBs?

If it's a mandatory dependencies for existing scripts to build under 
15.0, then please send the PR for us to review


-- 
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/20220225/5d29cc88/attachment.asc>

From willysr at slackbuilds.org  Fri Feb 25 06:36:25 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 25 Feb 2022 13:36:25 +0700
Subject: [Slackbuilds-users]
 0001-network-basilisk-bin-updated-for-version-2022.01.27.patch
In-Reply-To: <Yhcnx5A+XlQcC47e@posteo.de>
References: <Yhcnx5A+XlQcC47e@posteo.de>
Message-ID: <ddd65817-84ff-d434-f343-0069a23eee60@slackbuilds.org>

> basilisk updated for version 2022.01.27

merged in my branch


-- 
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/20220225/3a1111d8/attachment.asc>

From ozan.turkyilmaz at gmail.com  Fri Feb 25 06:37:32 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Fri, 25 Feb 2022 09:37:32 +0300
Subject: [Slackbuilds-users] aMule Patch for freeze problem
Message-ID: <CA+da1oqpHR48rbgqBELka+fnfPL8JiE4NbdoE+dNe5BmXAQm3A@mail.gmail.com>

Hello All,

Upstream came up with a solution for freeze problems reported.
It is a simple fix: compile with boost support. I also checked that
it can compile with libupnp instead of linupnp-legacy. I updated
the README file accordingly.

REgards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220225/05a09323/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-network-aMule-Updated-the-README-for-information.patch
Type: application/octet-stream
Size: 856 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220225/05a09323/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-aMule-Compile-with-boost-to-solve-the-freezing-probl.patch
Type: application/octet-stream
Size: 777 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220225/05a09323/attachment-0003.obj>

From willysr at slackbuilds.org  Fri Feb 25 06:39:35 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 25 Feb 2022 13:39:35 +0700
Subject: [Slackbuilds-users] aMule Patch for freeze problem
In-Reply-To: <CA+da1oqpHR48rbgqBELka+fnfPL8JiE4NbdoE+dNe5BmXAQm3A@mail.gmail.com>
References: <CA+da1oqpHR48rbgqBELka+fnfPL8JiE4NbdoE+dNe5BmXAQm3A@mail.gmail.com>
Message-ID: <93138d04-6dd5-2424-6676-6bfcf9626e48@slackbuilds.org>

> Upstream came up with a solution for freeze problems reported.
> It is a simple fix: compile with boost support. I also checked that
> it can compile with libupnp instead of linupnp-legacy. I updated
> the README file accordingly.

Thanks
pushed


-- 
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/20220225/472c828e/attachment.asc>

From andrew.david.strong at gmail.com  Fri Feb 25 07:12:05 2022
From: andrew.david.strong at gmail.com (Andrew David)
Date: Fri, 25 Feb 2022 18:12:05 +1100
Subject: [Slackbuilds-users] david (libraries) update for 15.0
In-Reply-To: <1a80df89-3bea-c097-cf3e-ff86de2864e8@slackbuilds.org>
References: <YhhjmPA1ScE2Emp7@ilium.andrews-corner.org>
 <1a80df89-3bea-c097-cf3e-ff86de2864e8@slackbuilds.org>
Message-ID: <CAEpRkVOK7mZ1e6sLndGMXX_rD+YmpCL8kyfvK-gMYfngRROL-A@mail.gmail.com>

Thanks!

Andrew


On Fri, 25 Feb 2022, 17:28 Willy Sudiarto Raharjo, <willysr at slackbuilds.org>
wrote:

> > I attach a patch to update dav1d for Slackware 15.0, just a simple
> > version bump required for this one. Built against git master...
>
> pushed to my branch
>
>
> --
> Willy Sudiarto Raharjo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220225/d3dd0c04/attachment.htm>

From jebrhansen+SBo at gmail.com  Fri Feb 25 08:20:00 2022
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Fri, 25 Feb 2022 01:20:00 -0700
Subject: [Slackbuilds-users] Fwd: Picard maintainer updated without
 permission
In-Reply-To: <CANi9qSt5RUjsDrUim6CoNVVFh6OWUWDrvasU1iZvMC4W==WC3A@mail.gmail.com>
References: <CANi9qSt5RUjsDrUim6CoNVVFh6OWUWDrvasU1iZvMC4W==WC3A@mail.gmail.com>
Message-ID: <CANi9qSvTwxFH83-HE1_6dkQx1SrL7JOLzWGbd0DGTn-MXxTwDA@mail.gmail.com>

Pouria,

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

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

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

Thanks
Jeremy aka bassmadrigal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220225/9d986457/attachment.htm>

From matteo.bernardini at gmail.com  Fri Feb 25 08:55:29 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 25 Feb 2022 09:55:29 +0100
Subject: [Slackbuilds-users] Fwd: Picard maintainer updated without
 permission
In-Reply-To: <CANi9qSvTwxFH83-HE1_6dkQx1SrL7JOLzWGbd0DGTn-MXxTwDA@mail.gmail.com>
References: <CANi9qSt5RUjsDrUim6CoNVVFh6OWUWDrvasU1iZvMC4W==WC3A@mail.gmail.com>
 <CANi9qSvTwxFH83-HE1_6dkQx1SrL7JOLzWGbd0DGTn-MXxTwDA@mail.gmail.com>
Message-ID: <CAPsDuS7Zt442m0Oh074UbF5PQQoytFCe-mj1z5i4pMZWRxqu5w@mail.gmail.com>

I think there has been a bit of confusion

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

Jeremy, it's ok if you correct this.

Matteo

Il giorno ven 25 feb 2022 alle ore 09:20 Jeremy Hansen
<jebrhansen+SBo at gmail.com> ha scritto:
>
> Pouria,
>
> You took over maintainership of picard without notifying or requesting it from me. Was this an oversight? I was getting ready to submit my update for the 15.0 repo today only to find out you had replaced me as maintainer without ever notifying me.
>
> I did not intend to give up maintenance of this SlackBuild and would prefer to keep it myself.
>
> @SBo admins, are you ok with me submitting a PR correcting the info? Pouria also neglected to keep the picard-plugins SlackBuild up-to-date.
>
> Thanks
> Jeremy aka bassmadrigal
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users 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  Fri Feb 25 17:20:10 2022
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Fri, 25 Feb 2022 10:20:10 -0700
Subject: [Slackbuilds-users] Fwd: Picard maintainer updated without
 permission
In-Reply-To: <CAPsDuS7Zt442m0Oh074UbF5PQQoytFCe-mj1z5i4pMZWRxqu5w@mail.gmail.com>
References: <CANi9qSt5RUjsDrUim6CoNVVFh6OWUWDrvasU1iZvMC4W==WC3A@mail.gmail.com>
 <CANi9qSvTwxFH83-HE1_6dkQx1SrL7JOLzWGbd0DGTn-MXxTwDA@mail.gmail.com>
 <CAPsDuS7Zt442m0Oh074UbF5PQQoytFCe-mj1z5i4pMZWRxqu5w@mail.gmail.com>
Message-ID: <CANi9qSvL6NjV2m-hpDdMgdNpd7xYZ2mYqKbuK6R5CqhW6+Asrg@mail.gmail.com>

Thanks for the info Matteo!

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

I'll send in a new PR.

Jeremy

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

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

From matteo.bernardini at gmail.com  Fri Feb 25 17:34:42 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 25 Feb 2022 18:34:42 +0100
Subject: [Slackbuilds-users] Fwd: Picard maintainer updated without
 permission
In-Reply-To: <CANi9qSvL6NjV2m-hpDdMgdNpd7xYZ2mYqKbuK6R5CqhW6+Asrg@mail.gmail.com>
References: <CANi9qSt5RUjsDrUim6CoNVVFh6OWUWDrvasU1iZvMC4W==WC3A@mail.gmail.com>
 <CANi9qSvTwxFH83-HE1_6dkQx1SrL7JOLzWGbd0DGTn-MXxTwDA@mail.gmail.com>
 <CAPsDuS7Zt442m0Oh074UbF5PQQoytFCe-mj1z5i4pMZWRxqu5w@mail.gmail.com>
 <CANi9qSvL6NjV2m-hpDdMgdNpd7xYZ2mYqKbuK6R5CqhW6+Asrg@mail.gmail.com>
Message-ID: <CAPsDuS5uuU7E_=z5iXCFpHkSSiPjLgQQLaokp9HsFd--kDEPBw@mail.gmail.com>

who knows, maybe he dreamt about it! :-)

Matteo

Il giorno ven 25 feb 2022 alle ore 18:20 Jeremy Hansen
<jebrhansen+SBo at gmail.com> ha scritto:
>
> Thanks for the info Matteo!
>
> Wow... Pouria and I had a discussion about discord at the beginning of November with no indication that I'm stepping down from any of my SlackBuilds. Then he flat out lies saying he got in contact with me and that I'm no longer using Slackware (I'm very much continuing to use Slackware and there were no contact attempts after discord). That's a little messed up on his part.
>
> I'll send in a new PR.
>
> Jeremy
>
> On Fri, Feb 25, 2022 at 1:54 AM Matteo Bernardini <matteo.bernardini at gmail.com> wrote:
>>
>> I think there has been a bit of confusion
>>
>> https://github.com/SlackBuildsOrg/slackbuilds/pull/1057
>>
>> Jeremy, it's ok if you correct this.
>>
>> Matteo
>>
>> Il giorno ven 25 feb 2022 alle ore 09:20 Jeremy Hansen
>> <jebrhansen+SBo at gmail.com> ha scritto:
>> >
>> > Pouria,
>> >
>> > You took over maintainership of picard without notifying or requesting it from me. Was this an oversight? I was getting ready to submit my update for the 15.0 repo today only to find out you had replaced me as maintainer without ever notifying me.
>> >
>> > I did not intend to give up maintenance of this SlackBuild and would prefer to keep it myself.
>> >
>> > @SBo admins, are you ok with me submitting a PR correcting the info? Pouria also neglected to keep the picard-plugins SlackBuild up-to-date.
>> >
>> > Thanks
>> > Jeremy aka bassmadrigal
>> > _______________________________________________
>> > SlackBuilds-users mailing list
>> > SlackBuilds-users 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 andrew.david.strong at gmail.com  Fri Feb 25 22:35:19 2022
From: andrew.david.strong at gmail.com (andrew)
Date: Sat, 26 Feb 2022 09:35:19 +1100
Subject: [Slackbuilds-users] Update for aom (multimedia)
In-Reply-To: <YhccUWWNPTtuqZIQ@ilium.andrews-corner.org>
References: <YhR8gmgklaYZXCw3@ilium.andrews-corner.org>
 <YhW7LP/JK+gzEH7N@ilium.andrews-corner.org>
 <5e78b5f2-8c47-a384-ae17-dca5d9efd7c4@slackbuilds.org>
 <YhccUWWNPTtuqZIQ@ilium.andrews-corner.org>
Message-ID: <YhlZp7q2cvsQwXqo@ilium.andrews-corner.org>

On Thu, Feb 24, 2022 at 04:49:09PM +1100, andrew wrote:

> Fair enough. The first email in this thread holds a patch for an
> updated aom and Slackware 15.0.

But just in case it gets lost in the considerable traffic of this
mailing list I re-attach it to this email :).

Andrew
-- 
You think that's air you're breathing now?
-------------- next part --------------
diff --git a/multimedia/aom/README b/multimedia/aom/README
index 40b686da..dbddf20c 100644
--- a/multimedia/aom/README
+++ b/multimedia/aom/README
@@ -3,8 +3,5 @@ video transmission over the Internet. AV1 is planned to surpass
 VP9 and also to eventually be a competitor with HEVC/H.265.
 
 This script builds the encoder aomenc, the decoder aomdec as well
-as shared libraries which can be utilised by recent versions of
+as shared libraries which can be utilised by suitable versions of
 both FFmpeg and vlc.
-
-Note: 'aom' replaces and upgrades 'libaom'; make sure 'libaom' is
-removed before using this SlackBuild.
diff --git a/multimedia/aom/aom.SlackBuild b/multimedia/aom/aom.SlackBuild
index b986c266..ac01eefa 100644
--- a/multimedia/aom/aom.SlackBuild
+++ b/multimedia/aom/aom.SlackBuild
@@ -2,7 +2,7 @@
 # ----------------------------------------------------------------------
 # Slackware build script for aom
 #
-# Copyright (c) 2018-2021 Andrew Strong, Blue Mountains, Australia.
+# Copyright (c) 2018-2022 Andrew Strong, Blue Mountains, Australia.
 #
 #   Permission to use, copy, modify, and distribute this software for
 #   any purpose with or without fee is hereby granted, provided that
@@ -27,10 +27,10 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=aom
-# The 'official' archive for the aom 2.0.1 release has the git commit in
+# The 'official' archive for the aom 3.3.0 release has the git commit in
 # the filename, so adjustments are required for a sane Slackware build:
-VERSION=${VERSION:-2.0.1}
-GITCOMMIT=${GITCOMMIT:-b52ee6d44adaef8a08f6984390de050d64df9faa}
+VERSION=${VERSION:-3.3.0}
+GITCOMMIT=${GITCOMMIT:-87460cef80fb03def7d97df1b47bad5432e5e2e4}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -88,7 +88,7 @@ find -L . \
 cd build
 
   # I don't build either the HTML or the Latex docs as IMHO at this stage
-  # of aom development they are not terribly useful for non-developers.
+  # of aom development they are still not terribly useful for non-developers.
   # To enable these docs change '-DENABLE_DOCS=0' below to '1' to build
   # the docs and then uncomment the 'extra docs' section below to install them...
 
@@ -97,8 +97,8 @@ cd build
     -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
     -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
     -DCMAKE_INSTALL_PREFIX=/usr \
-    -DCMAKE_INSTALL_LIBDIR=/lib${LIBDIRSUFFIX} \
-    -DCMAKE_INSTALL_INCLUDEDIR=/include \
+    -DCMAKE_INSTALL_LIBDIR=lib${LIBDIRSUFFIX} \
+    -DCMAKE_INSTALL_INCLUDEDIR=include \
     -DCMAKE_BUILD_TYPE=Release \
     -DENABLE_NASM=1 \
     -DENABLE_DOCS=0 \
diff --git a/multimedia/aom/aom.info b/multimedia/aom/aom.info
index 35375792..052e807d 100644
--- a/multimedia/aom/aom.info
+++ b/multimedia/aom/aom.info
@@ -1,8 +1,8 @@
 PRGNAM="aom"
-VERSION="2.0.1"
+VERSION="3.3.0"
 HOMEPAGE="https://aomedia.googlesource.com/aom"
-DOWNLOAD="http://www.andrews-corner.org/downloads/aom-b52ee6d44adaef8a08f6984390de050d64df9faa.tar.gz"
-MD5SUM="d37bf9cfe3353e661637c2b106ee1787"
+DOWNLOAD="http://www.andrews-corner.org/downloads/aom-87460cef80fb03def7d97df1b47bad5432e5e2e4.tar.gz"
+MD5SUM="8e722dae87dff97dfb98c3857fe38ee2"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""

From willysr at slackbuilds.org  Sat Feb 26 04:46:20 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 26 Feb 2022 11:46:20 +0700
Subject: [Slackbuilds-users] Update for aom (multimedia)
In-Reply-To: <YhlZp7q2cvsQwXqo@ilium.andrews-corner.org>
References: <YhR8gmgklaYZXCw3@ilium.andrews-corner.org>
 <YhW7LP/JK+gzEH7N@ilium.andrews-corner.org>
 <5e78b5f2-8c47-a384-ae17-dca5d9efd7c4@slackbuilds.org>
 <YhccUWWNPTtuqZIQ@ilium.andrews-corner.org>
 <YhlZp7q2cvsQwXqo@ilium.andrews-corner.org>
Message-ID: <9a9fcc90-79f0-742a-f79b-a1570368532b@slackbuilds.org>

>> Fair enough. The first email in this thread holds a patch for an
>> updated aom and Slackware 15.0.
> 
> But just in case it gets lost in the considerable traffic of this
> mailing list I re-attach it to this email :).

Yes, i missed this one
now merged in my branch


-- 
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/20220226/7bab2a99/attachment.asc>

From andrew.david.strong at gmail.com  Sat Feb 26 04:52:10 2022
From: andrew.david.strong at gmail.com (Andrew David)
Date: Sat, 26 Feb 2022 15:52:10 +1100
Subject: [Slackbuilds-users] Update for aom (multimedia)
In-Reply-To: <9a9fcc90-79f0-742a-f79b-a1570368532b@slackbuilds.org>
References: <YhR8gmgklaYZXCw3@ilium.andrews-corner.org>
 <YhW7LP/JK+gzEH7N@ilium.andrews-corner.org>
 <5e78b5f2-8c47-a384-ae17-dca5d9efd7c4@slackbuilds.org>
 <YhccUWWNPTtuqZIQ@ilium.andrews-corner.org>
 <YhlZp7q2cvsQwXqo@ilium.andrews-corner.org>
 <9a9fcc90-79f0-742a-f79b-a1570368532b@slackbuilds.org>
Message-ID: <CAEpRkVM3TSQiRO6DUqH9OV+LTB2WKYZ-AFrQrFX8XL9a4MbYzw@mail.gmail.com>

Thank you,

Andrew

On Sat, 26 Feb 2022, 15:46 Willy Sudiarto Raharjo, <willysr at slackbuilds.org>
wrote:

> >> Fair enough. The first email in this thread holds a patch for an
> >> updated aom and Slackware 15.0.
> >
> > But just in case it gets lost in the considerable traffic of this
> > mailing list I re-attach it to this email :).
>
> Yes, i missed this one
> now merged in my branch
>
>
> --
> Willy Sudiarto Raharjo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220226/01f87130/attachment.htm>

From marek at modweb.de  Wed Feb 23 20:19:21 2022
From: marek at modweb.de (=?UTF-8?Q?Marek_=c5=a0rejma?=)
Date: Wed, 23 Feb 2022 21:19:21 +0100
Subject: [Slackbuilds-users] wrong md5sum for protobuf-c 1.4.0 package
In-Reply-To: <CAK09-vmsyWW_uRw5ddXcYpmDwZcSS5vgH6xcSONd7kbfyTHkmQ@mail.gmail.com>
References: <CAK09-vmsyWW_uRw5ddXcYpmDwZcSS5vgH6xcSONd7kbfyTHkmQ@mail.gmail.com>
Message-ID: <d84184f3-e83f-20cd-0df9-7f1dfcc59a80@modweb.de>

Sorry, my bad.
I missed updating the md5sum when pushing it to github.

Marek

Greg' Ar Tourter wrote:
> Hi
>
> looks like the checksum wasn't updated in the 1.4.0 upgrade:
>
> Found protobuf-c-1.4.0.tar.gz in /var/cache/sbopkg.
> Checking MD5SUM:
> ? MD5SUM check for protobuf-c-1.4.0.tar.gz ... FAILED!
> ? ? Expected: dabc05a5f11c21b96d8d6db4153f5343
> ? ? Found: ? ?10e1103a012ce0877c32367949a2fa6e
>
> Cheers
>
> Greg
>
> _______________________________________________
> 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 rworkman at slackbuilds.org  Sat Feb 26 22:24:47 2022
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 26 Feb 2022 16:24:47 -0600
Subject: [Slackbuilds-users] Adopting orphaned SlackBuilds
In-Reply-To: <YhGIdINi6zgFa2NF@posteo.de>
References: <YhGIdINi6zgFa2NF@posteo.de>
Message-ID: <20220226162447.0d8b3951@home.rlworkman.net>

On Sun, 20 Feb 2022 00:16:52 +0000
khronosschoty <khronosschoty at posteo.org> wrote:

> Also I do not see pcsx2 in the master branch of SlackBuilds.org, so in
> case that is also needs a new maintainer, I would take that one as
> well. 


I think all of these were removed already for lack of an active maintainer, so if you actually want to maintain them, we'll need a resubmit after the 15.0 repo goes live.

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

From rworkman at slackbuilds.org  Sat Feb 26 22:29:26 2022
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 26 Feb 2022 16:29:26 -0600
Subject: [Slackbuilds-users] New maintainer for olm
In-Reply-To: <49d330da-49ce-41ac-bab7-b4ff7b2b05ce@www.fastmail.com>
References: <49d330da-49ce-41ac-bab7-b4ff7b2b05ce@www.fastmail.com>
Message-ID: <20220226162926.0f8d2850@home.rlworkman.net>

On Thu, 17 Feb 2022 15:28:10 +0800
"David O'Shaughnessy" <lists at osh.id.au> wrote:

> olm has a new maintainer, Roger Krowiak (cc'd). His updated
> SlackBuild is attached, thanks Roger!


Committed in my branch; thanks!

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

From rworkman at slackbuilds.org  Sat Feb 26 23:00:36 2022
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 26 Feb 2022 17:00:36 -0600
Subject: [Slackbuilds-users] libupnp and libupnp-legacy
In-Reply-To: <CA+da1op+1+7y5ZYJSHXxKYzy0PZ2b_qm_teK6ohFAS+zyJoZaA@mail.gmail.com>
References: <CA+da1op+1+7y5ZYJSHXxKYzy0PZ2b_qm_teK6ohFAS+zyJoZaA@mail.gmail.com>
Message-ID: <20220226170036.257cbc53@home.rlworkman.net>

On Mon, 21 Feb 2022 10:49:18 +0300
Ozan T?rky?lmaz <ozan.turkyilmaz at gmail.com> wrote:

> I was looking into how I can get those two installed together. (It's
> shame we can't install them together)
> With thinkering with configure scripts, I decided to put it on
> /usr/legacy prefix with /usr/lib/legacy. It's possible
> to pass /usr/lib/legacy/pkgconfig to PKG_CONFIG_PATH during
> configuration of other programs (R?ght now
> it is only linphone needs libupnp-legacy as far as I can find).
> 
> Folder places are for testing only. Maybe putting the libupnp-legacy
> in /opt/libupnp-legacy with all the libs is
> a better idea.


If it's just linphone needing it, I'd be inclined to try to build it statically as part of the linphone build and link linphone to it there.

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

From nix at nixing.mx  Sat Feb 26 23:04:16 2022
From: nix at nixing.mx (nix)
Date: Sat, 26 Feb 2022 17:04:16 -0600
Subject: [Slackbuilds-users] NodeJS version in Slackbuild causing issues
Message-ID: <20220226230416.ygeehhkcfa2qnrid@epsilon>

Hello,

Not sure if this is where this type of thing is reported, apologies if
it's not.

The Node version in the repo 17.5.0 seems to be causing issues [1] when 
used with mongoose.

This version seems to be the latest and not the stable nodejs version.

Upon installing the LTS version of nodejs, simply changing the version
and downloading appropirate source, the issues with mongoose are noto
seen.

Maybe keeping the LTS version in the Slackbuild is a better choice?

[1] https://stackoverflow.com/questions/71073107/does-anyone-know-nay-fix-for-this-error-typeerror-cannot-assign-to-read-only-p

Eric,



From rworkman at slackbuilds.org  Sat Feb 26 23:28:42 2022
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 26 Feb 2022 17:28:42 -0600
Subject: [Slackbuilds-users] NodeJS version in Slackbuild causing issues
In-Reply-To: <20220226230416.ygeehhkcfa2qnrid@epsilon>
References: <20220226230416.ygeehhkcfa2qnrid@epsilon>
Message-ID: <20220226172842.7b00c14a@home.rlworkman.net>

On Sat, 26 Feb 2022 17:04:16 -0600
nix <nix at nixing.mx> wrote:

> Hello,
> 
> Not sure if this is where this type of thing is reported, apologies if
> it's not.
> 
> The Node version in the repo 17.5.0 seems to be causing issues [1]
> when used with mongoose.
> 
> This version seems to be the latest and not the stable nodejs version.
> 
> Upon installing the LTS version of nodejs, simply changing the version
> and downloading appropirate source, the issues with mongoose are noto
> seen.
> 
> Maybe keeping the LTS version in the Slackbuild is a better choice?
> 
> [1]
> https://stackoverflow.com/questions/71073107/does-anyone-know-nay-fix-for-this-error-typeerror-cannot-assign-to-read-only-p


The last post in that thread indicates to try upgrading nodejs to 17.6.0.
Try that -- it's been updated in the SBo master branch already.

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

From nix at nixing.mx  Sat Feb 26 23:41:33 2022
From: nix at nixing.mx (nix)
Date: Sat, 26 Feb 2022 17:41:33 -0600
Subject: [Slackbuilds-users] NodeJS version in Slackbuild causing issues
In-Reply-To: <20220226172842.7b00c14a@home.rlworkman.net>
References: <20220226230416.ygeehhkcfa2qnrid@epsilon>
 <20220226172842.7b00c14a@home.rlworkman.net>
Message-ID: <20220226234133.onuu4ckdxjkjlzrj@epsilon>

> 
> The last post in that thread indicates to try upgrading nodejs to 17.6.0.
> Try that -- it's been updated in the SBo master branch already.
> 
> -RW

Ah, I forgot to pull the latest version in the repo. Thanks for for
that. I will give it a try.

Eric

From duncan_roe at optusnet.com.au  Sun Feb 27 01:15:27 2022
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Sun, 27 Feb 2022 12:15:27 +1100
Subject: [Slackbuilds-users] lxml SlackBuild needs to be newer version
Message-ID: <YhrQr4Jc/4sGwyQu@slk1.local.net>

Hi Larry,

lxml SB is at version 4.6.3 but PyPi has 4.8.0.

afdko (that I maintain) requires at least 4.7.1.

For now, I built afdko using pip2tgz to get an up-to-date lxml,
but could you update your SB please?

Cheers ... Duncan.

From duncan_roe at optusnet.com.au  Sun Feb 27 01:24:37 2022
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Sun, 27 Feb 2022 12:24:37 +1100
Subject: [Slackbuilds-users] lxml SlackBuild needs to be newer version
In-Reply-To: <YhrQr4Jc/4sGwyQu@slk1.local.net>
References: <YhrQr4Jc/4sGwyQu@slk1.local.net>
Message-ID: <YhrS1SdDZPfHLfkr@slk1.local.net>

On Sun, Feb 27, 2022 at 12:15:27PM +1100, Duncan Roe wrote:
> Hi Larry,
>
> lxml SB is at version 4.6.3 but PyPi has 4.8.0.
>
> afdko (that I maintain) requires at least 4.7.1.
>
> For now, I built afdko using pip2tgz to get an up-to-date lxml,
> but could you update your SB please?

Some clarification: lxml is a *runtime* dependency of afdko. afdko *builds*
w/out lxml.

Type1_to_OTF uses afdko to build: I should have posted "I built Type1_to_OTF
using pip2tgz to get an up-to-date lxml".

Cheers ... Duncan.

From duncan_roe at optusnet.com.au  Sun Feb 27 01:31:17 2022
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Sun, 27 Feb 2022 12:31:17 +1100
Subject: [Slackbuilds-users] Where are keywords kept?
Message-ID: <YhrUZcwj9OWAi6Gb@slk1.local.net>

Hi admins,

Just curious - keywords are not in the slackbuilds git repo - are they kept
anywhere that is publically accessible?

Cheers ... Duncan.

From duncan_roe at optusnet.com.au  Sun Feb 27 01:57:28 2022
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Sun, 27 Feb 2022 12:57:28 +1100
Subject: [Slackbuilds-users] afdko
In-Reply-To: <670a758d-1608-cbae-7613-3514d58220ae@slackbuilds.org>
References: <YhdSyoNwGTAcF4e1@slk1.local.net>
 <670a758d-1608-cbae-7613-3514d58220ae@slackbuilds.org>
Message-ID: <YhraiJ0Obd0T6SkG@slk1.local.net>

On Fri, Feb 25, 2022 at 01:32:51PM +0700, Willy Sudiarto Raharjo wrote:
>
> If it's a mandatory dependencies for existing scripts to build under 15.0,
> then please send the PR for us to review
>
PR sent.

Cheers ... Duncan.

From peter at peter-dambier.de  Sun Feb 27 08:56:02 2022
From: peter at peter-dambier.de (Peter Dambier)
Date: Sun, 27 Feb 2022 09:56:02 +0100
Subject: [Slackbuilds-users] SlackBuild silently quitting - Cmake - make
 install
Message-ID: <20220227095602.128dad14.peter@peter-dambier.de>

Salve fellow SlackBuilders

I discovered CPU-X and other SlackBuilds

The X.SlackBuild did not finish in the way it used to
but there were no error messages either.

Autopilot off - walking on bare foot:

Cmake - fine.

make - fine.

make install ???

make install is leaving through the window, not through the door.
That is why I dont see a message about an SBo.tgz waiting in
/tmp for me to pick it up.

Easter time and egg hunting - there is an SBo.tgz after all
and CPU-X did install and is working.

I tried a lot of magic spells and have no clue what makes
SlackBuilds behave differently with 15.0

For me it looks like Cmake is one of the spirits but installing
Cmake from 14.2 made no difference.

There is more about Makefiles than meets the eye.

Happy Easter Egg hunting and dont take life too seriously - not today...

Cheers Peter

From willysr at slackbuilds.org  Sun Feb 27 17:07:32 2022
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 28 Feb 2022 00:07:32 +0700
Subject: [Slackbuilds-users] Where are keywords kept?
In-Reply-To: <YhrUZcwj9OWAi6Gb@slk1.local.net>
References: <YhrUZcwj9OWAi6Gb@slk1.local.net>
Message-ID: <1251d526-63ed-725b-b4b9-cf3a0f74f8b1@slackbuilds.org>

> Just curious - keywords are not in the slackbuilds git repo - are they kept
> anywhere that is publically accessible?

It's in the database used for the website



-- 
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/20220228/5a2837f1/attachment-0001.asc>

From spycrowsoft at gmail.com  Sun Feb 27 20:04:48 2022
From: spycrowsoft at gmail.com (Spycrowsoft)
Date: Sun, 27 Feb 2022 21:04:48 +0100
Subject: [Slackbuilds-users] Status of my slackbuilds for 15.0
Message-ID: <0edfb8e0-add4-c7ca-661a-c730e82e51a9@gmail.com>

Hi all,

I currently maintain the QuiteRSS, resilio-sync and yubioath-desktop 
slackbuilds and I'm writing you all to report on their readiness for 
Slackware 15.0.

QuiteRSS compiles and runs without any noticable problems on Slackware 
15.0 and Slackware64 15.0 and since there are no updates upstream 
either, that Slackbuild is ready to go "as it is" for 15.0.

The yubioath-desktop and resilio-sync slackbuilds are binary repacks.

The yubioath-desktop has an update upstream, is missing a template with 
udev-rules and the current version doesn't work with pin/password 
protected yubikeys. Apart from these caveats, it works fine, so you can 
simply use the current version and I'll send a version-update once the 
repository for 15.0 is finished.

The resilio-sync slackbuild also has an update upstream, but it also 
runs on both Slackware 15.0 and Slackware64 15.0. I'll also update those 
once the repository is done.

Kind regards,

Spycrowsoft


From bgrundy at gmail.com  Sun Feb 27 23:07:34 2022
From: bgrundy at gmail.com (Barry J. Grundy)
Date: Sun, 27 Feb 2022 18:07:34 -0500
Subject: [Slackbuilds-users] Any help?
Message-ID: <fbdc46c9-73d0-e43c-1377-00e3f6f5a4fd@gmail.com>

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

In the meantime I'm wondering if there is a list of SlackBuilds we can 
test or that need some attention. Any other way the larger community can 
help with the workload?

Thanks for all the hard work,
Barry

From jebrhansen+SBo at gmail.com  Sun Feb 27 23:37:59 2022
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sun, 27 Feb 2022 16:37:59 -0700
Subject: [Slackbuilds-users] Any help?
In-Reply-To: <fbdc46c9-73d0-e43c-1377-00e3f6f5a4fd@gmail.com>
References: <fbdc46c9-73d0-e43c-1377-00e3f6f5a4fd@gmail.com>
Message-ID: <CANi9qSseyVBX+3ReT0YtR5hP6e6reCpEZutE6c98oW7wOS0Ohg@mail.gmail.com>

On Sun, Feb 27, 2022, 4:07 PM Barry J. Grundy <bgrundy at gmail.com> wrote:

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

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

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

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

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

From khronosschoty at posteo.org  Mon Feb 28 02:17:31 2022
From: khronosschoty at posteo.org (khronosschoty)
Date: Mon, 28 Feb 2022 02:17:31 +0000
Subject: [Slackbuilds-users]
 0001-games-OpenRA-OpenRA-updated-for-version-20210321-fix.patch
Message-ID: <Yhwwu4TmrcmvwtI8@posteo.de>

Hi,

I noticed that my update to OpenRA hadn't been merged at all, and no one
mentioned anything, so I looked it over and noticed, there was some
trailing white space. So here is a new patch. The dotnet dependency I
added applied cleanly so no need to revisit that. 
-------------- next part --------------
From e4dd4e74817244eeae50dc341671553c964405c9 Mon Sep 17 00:00:00 2001
From: khronosschoty <khronosschoty at posteo.org>
Date: Sun, 27 Feb 2022 17:53:13 -0800
Subject: [PATCH 1/1] games/OpenRA OpenRA-updated-for-version-20210321 *fix*

---
 games/OpenRA/OpenRA.SlackBuild            | 30 +++++++++++++----------
 games/OpenRA/OpenRA.info                  | 16 ++++++------
 games/OpenRA/fetch-thirdparty-deps.sh.new | 18 --------------
 3 files changed, 25 insertions(+), 39 deletions(-)
 delete mode 100644 games/OpenRA/fetch-thirdparty-deps.sh.new

diff --git a/games/OpenRA/OpenRA.SlackBuild b/games/OpenRA/OpenRA.SlackBuild
index 060cdd3e65c..139b2188641 100644
--- a/games/OpenRA/OpenRA.SlackBuild
+++ b/games/OpenRA/OpenRA.SlackBuild
@@ -2,7 +2,7 @@
 
 # Slackware build script for OpenRA
 
-# Copyright 2017 Vasily Sora USA
+# Copyright 2017,2022 Vasily Sora USA
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -25,7 +25,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=OpenRA
-VERSION=${VERSION:-20190314}
+VERSION=${VERSION:-20210321}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -49,6 +49,10 @@ fi
 TMP=${TMP:-/tmp/SBo}
 PKG=$TMP/package-$PRGNAM
 OUTPUT=${OUTPUT:-/tmp}
+HOME=$TMP/$PRGNAM-release-$VERSION-source
+DOTNET_CLI_TELEMETRY_OPTOUT=1
+export HOME DOTNET_CLI_TELEMETRY_OPTOUT
+
 
 if [ "$ARCH" = "i586" ]; then
   SLKCFLAGS="-O2 -march=i586 -mtune=i686"
@@ -71,15 +75,15 @@ rm -rf $TMP/$PRGNAM-release-$VERSION-source
 mkdir -p $TMP $PKG $OUTPUT $TMP/$PRGNAM-release-$VERSION-source
 cd $TMP/$PRGNAM-release-$VERSION-source
 tar xvf $CWD/$PRGNAM-release-$VERSION-source.tar.bz2
-cp $CWD/fetch-thirdparty-deps.sh.new thirdparty/fetch-thirdparty-deps.sh
-cp $CWD/download.tar.gz thirdparty
-mkdir thirdparty/download/
-cp $CWD/GeoLite2-Country.mmdb.gz thirdparty/download/
-rm thirdparty/fetch-geoip-db.sh
-touch thirdparty/fetch-geoip-db.sh
-echo "#!/bin/sh" >> thirdparty/fetch-geoip-db.sh
-echo 'echo "success"' >> thirdparty/fetch-geoip-db.sh
-chmod +x thirdparty/fetch-geoip-db.sh
+tar -xzvf $CWD/openra-deps.tar.gz
+cp $CWD/IP2LOCATION-LITE-DB1.IPV6.BIN.ZIP .
+rm fetch-geoip.sh
+touch fetch-geoip.sh
+echo "#!/bin/sh" >> fetch-geoip.sh
+echo 'echo "success"' >> fetch-geoip.sh
+chmod +x fetch-geoip.sh
+
+sed -i 's/msbuild/dotnet\ msbuild/g' ./Makefile ./packaging/functions.sh
 
 chown -R root:root .
 find -L . \
@@ -88,10 +92,10 @@ find -L . \
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
-make dependencies
-make all
+unshare -n make all TARGETPLATFORM=unix-generic  RUNTIME=mono MSBUILD='dotnet msbuild -verbosity:m -nologo'
 make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install DESTDIR=$PKG
 make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install-linux-shortcuts DESTDIR=$PKG
+make prefix=/usr mandir=/usr/man bindir=/usr/games libdir=/usr/lib${LIBDIRSUFFIX} install-linux-appdata DESTDIR=$PKG
 
 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
diff --git a/games/OpenRA/OpenRA.info b/games/OpenRA/OpenRA.info
index ef12bb2ec9a..4a9b84b8bb4 100644
--- a/games/OpenRA/OpenRA.info
+++ b/games/OpenRA/OpenRA.info
@@ -1,14 +1,14 @@
 PRGNAM="OpenRA"
-VERSION="20190314"
+VERSION="20210321"
 HOMEPAGE="http://www.openra.net/"
-DOWNLOAD="https://github.com/OpenRA/OpenRA/releases/download/release-20190314/OpenRA-release-20190314-source.tar.bz2 \
-          http://repo.khronosschoty.org/Slackware/stuff/OpenRA/20190314/download.tar.gz \
-          http://repo.khronosschoty.org/Slackware/stuff/OpenRA/20190314/GeoLite2-Country.mmdb.gz"
-MD5SUM="4ea1ba7d309bf0482979b5337677d2a3 \
-        e890273530c23cb8571a729d2aced59d \
-        3639895811efb10ad54bf6b40980224e"
+DOWNLOAD="https://github.com/OpenRA/OpenRA/releases/download/release-20210321/OpenRA-release-20210321-source.tar.bz2 \
+          http://repo.schotynet.org/sources/openra/openra-deps.tar.gz \
+	  http://repo.schotynet.org/sources/openra/IP2LOCATION-LITE-DB1.IPV6.BIN.ZIP"
+MD5SUM="38593fbcdda629561d8c0bc8ac1af402 \
+        26b1855341dc15787c7b54945050095d \
+        ef52f92818ebc942ca98108e92a0b802"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES="lua mono"
+REQUIRES="lua mono dotnet-sdk-6.0"
 MAINTAINER="khronosschoty"
 EMAIL="khronosschoty at posteo.org"
diff --git a/games/OpenRA/fetch-thirdparty-deps.sh.new b/games/OpenRA/fetch-thirdparty-deps.sh.new
deleted file mode 100644
index c0f9ae9b5d7..00000000000
--- a/games/OpenRA/fetch-thirdparty-deps.sh.new
+++ /dev/null
@@ -1,18 +0,0 @@
-#!/bin/sh
-
-####
-# This file must stay /bin/sh and POSIX compliant for BSD portability.
-# Copy-paste the entire script into http://shellcheck.net to check.
-####
-
-# Die on any error for Travis CI to automatically retry:
-set -e
-
-download_dir="${0%/*}/download"
-
-mkdir -p "${download_dir}"
-cd "${download_dir}"
-cd ..
-
-tar -xvf download.tar.gz
-
-- 
2.35.1

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

From duncan_roe at optusnet.com.au  Mon Feb 28 03:07:11 2022
From: duncan_roe at optusnet.com.au (Duncan Roe)
Date: Mon, 28 Feb 2022 14:07:11 +1100
Subject: [Slackbuilds-users] Please update your pipdeptree SlackBuild
Message-ID: <Yhw8X/L01LzK7GFP@slk1.local.net>

Hi Dimitris,

pipdeptree on PyPi is at version 2.2.1, but your SB is installing 0.11.0.

Could you update your SB please? pip2tgz (that I maintain) lists pipdeptree as a
requirement (but only because the man page mentions pipdeptree).

Cheers ... Duncan.

From yalhcru at gmail.com  Mon Feb 28 06:49:37 2022
From: yalhcru at gmail.com (B Watson)
Date: Mon, 28 Feb 2022 01:49:37 -0500
Subject: [Slackbuilds-users] SlackBuild silently quitting - Cmake - make
 install
In-Reply-To: <20220227095602.128dad14.peter@peter-dambier.de>
References: <20220227095602.128dad14.peter@peter-dambier.de>
Message-ID: <CAN1hMuAZSkjpR=oMCq9OyqbSqF81Wf3LF-ni3ea6o-_ehKM_KQ@mail.gmail.com>

On 2/27/22, Peter Dambier <peter at peter-dambier.de> wrote:
>
> make install is leaving through the window, not through the door.
> That is why I dont see a message about an SBo.tgz waiting in
> /tmp for me to pick it up.

Huh? Saw this message so I built CPU-X to see what happens...

Slackware package /tmp/CPU-X-4.2.0-x86_64-1_SBo.tgz created.

I *do* see a problem with it, it's running
glib-compile-schemas during the build, which means it overwrites
/usr/share/glib-2.0/schemas/gschemas.compiled on the build system (AKA
spamming the real filesystem). I'll patch it to avoid that...

From slackbuilds at schoepfer.info  Mon Feb 28 07:02:37 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 28 Feb 2022 08:02:37 +0100
Subject: [Slackbuilds-users] Updates for mednafen and zynaddsubfx
Message-ID: <10fa7bcc1b14227d4ab8d74b4415bfba@schoepfer.info>

Hi,

as said in the subject, patches attached.

Johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zynaddsubfx.patch
Type: text/x-diff
Size: 2918 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220228/0bb36d01/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mednafen.patch
Type: text/x-diff
Size: 3210 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220228/0bb36d01/attachment-0001.bin>

From lists at osh.id.au  Mon Feb 28 11:11:09 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Mon, 28 Feb 2022 19:11:09 +0800
Subject: [Slackbuilds-users] SlackBuild silently quitting - Cmake - make
 install
In-Reply-To: <CAN1hMuAZSkjpR=oMCq9OyqbSqF81Wf3LF-ni3ea6o-_ehKM_KQ@mail.gmail.com>
References: <20220227095602.128dad14.peter@peter-dambier.de>
 <CAN1hMuAZSkjpR=oMCq9OyqbSqF81Wf3LF-ni3ea6o-_ehKM_KQ@mail.gmail.com>
Message-ID: <130bda48-26c9-459a-a8f8-b4acd7e37925@www.fastmail.com>

On Mon, 28 Feb 2022, at 2:49 PM, B Watson wrote:
> I *do* see a problem with it, it's running
> glib-compile-schemas during the build, which means it overwrites
> /usr/share/glib-2.0/schemas/gschemas.compiled on the build system (AKA
> spamming the real filesystem). I'll patch it to avoid that...

On that topic, one easy way to check for this is with sbuild (https://gitlab.com/oshd/sbuild/). There are error codes for builds that write files outside of /tmp (even if they build properly).

--
Dave

From matteo.bernardini at gmail.com  Mon Feb 28 13:50:56 2022
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 28 Feb 2022 14:50:56 +0100
Subject: [Slackbuilds-users] Updates for mednafen and zynaddsubfx
In-Reply-To: <10fa7bcc1b14227d4ab8d74b4415bfba@schoepfer.info>
References: <10fa7bcc1b14227d4ab8d74b4415bfba@schoepfer.info>
Message-ID: <CAPsDuS47XMJeU3Aci+Y8u-JNdmYT5QkDFGoJ5fa=9W3pcuQpiw@mail.gmail.com>

thanks, pushed!

Il giorno lun 28 feb 2022 alle ore 08:02 Franzen via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> ha scritto:
>
> Hi,
>
> as said in the subject, patches attached.
>
> 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/
>

From peter at peter-dambier.de  Mon Feb 28 19:01:27 2022
From: peter at peter-dambier.de (Peter Dambier)
Date: Mon, 28 Feb 2022 20:01:27 +0100
Subject: [Slackbuilds-users] SlackBuild silently quitting - Cmake - make
 install
In-Reply-To: <CAN1hMuAZSkjpR=oMCq9OyqbSqF81Wf3LF-ni3ea6o-_ehKM_KQ@mail.gmail.com>
References: <20220227095602.128dad14.peter@peter-dambier.de>
 <CAN1hMuAZSkjpR=oMCq9OyqbSqF81Wf3LF-ni3ea6o-_ehKM_KQ@mail.gmail.com>
Message-ID: <20220228200127.3a238d48.peter@peter-dambier.de>

On Mon, 28 Feb 2022 01:49:37 -0500
B Watson <yalhcru at gmail.com> wrote:

> On 2/27/22, Peter Dambier <peter at peter-dambier.de> wrote:
> >
> > make install is leaving through the window, not through the door.
> > That is why I dont see a message about an SBo.tgz waiting in
> > /tmp for me to pick it up.
>
> Huh? Saw this message so I built CPU-X to see what happens...
>
> Slackware package /tmp/CPU-X-4.2.0-x86_64-1_SBo.tgz created.
>
> I *do* see a problem with it, it's running
> glib-compile-schemas during the build, which means it overwrites
> /usr/share/glib-2.0/schemas/gschemas.compiled on the build system (AKA
> spamming the real filesystem). I'll patch it to avoid that...

I forgot Slackware 15.0 where SlackBuild is silently ...
with Slackware 14.2 everything looks unsuspicious.

Thankyou David and Watson
Cheers Peter