From melikamp at melikamp.com  Wed Jul  1 00:12:40 2020
From: melikamp at melikamp.com (Ivan Zaigralin)
Date: Tue, 30 Jun 2020 17:12:40 -0700
Subject: [Slackbuilds-users] Erro compton
In-Reply-To: <70114dc1-f1be-f5dd-72e7-708dedd69879@slackbuilds.org>
References: <12f0790a-8355-e231-2486-703bf71ad05a@gmail.com>
 <3878390.eeyLu6hBFM@ithil>
 <70114dc1-f1be-f5dd-72e7-708dedd69879@slackbuilds.org>
Message-ID: <1750609.0dAxY6AeaC@ithil>

Like Willy says, this has to do with sbopkg behavior, and it's already fixed upstream, 
but perhaps I can patch it on my end as well. I need to figure out what exactly is the 
issue; I suspect it has something to do with the ugly package version.

On Tuesday, June 30, 2020 02:42:13 Willy Sudiarto Raharjo wrote:
> > I am not sure what this is. Is this a bug report? What exactly is the
> > issue?> 
> > On Monday, June 29, 2020 12:06:19 you wrote:
> >> melikamp
> >> 
> >> 
> >> # sbopkg -rco
> >> 
> >> compton:
> >>    POTENTIAL UPDATE
> >> 
> >> *  Installed version:
> >> compton-316eac0613bf342ff91cc645a6c3c80e6b9083fb-x86_64-1_SBo**
> >> **  Repo version:
> >> compton-316eac0613bf342ff91cc645a6c3c80e6b9083fb-x86_64-1_SBo*
> 
> It's a known bug in sbopkg 0.38.1
> it has been fixed in master branch in git, but no new releases will be
> made until SBo 15.0 repo is out.
> 
> If you want to patch it, you can apply this simple fix here
> https://github.com/sbopkg/sbopkg/commit/c24c2dd5d6917c05815f1b3f70f552424408
> bbb5
> 
> 
> --
> Willy Sudiarto Raharjo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200630/96694a64/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200630/96694a64/attachment-0001.asc>

From lenardrspencer at gmail.com  Wed Jul  1 01:31:34 2020
From: lenardrspencer at gmail.com (Lenard Spencer)
Date: Tue, 30 Jun 2020 21:31:34 -0400
Subject: [Slackbuilds-users] SBo submissions
Message-ID: <CANSA5-tMbuXW2FjpcjJ_UwNUhdKq0OyETpySS7jmDVRfTopdEg@mail.gmail.com>

Is it safe to upload new/updated scripts yet?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200630/d70bfbcd/attachment.htm>

From lenardrspencer at gmail.com  Wed Jul  1 01:48:37 2020
From: lenardrspencer at gmail.com (Lenard Spencer)
Date: Tue, 30 Jun 2020 21:48:37 -0400
Subject: [Slackbuilds-users] SBo submissions
In-Reply-To: <CANSA5-tMbuXW2FjpcjJ_UwNUhdKq0OyETpySS7jmDVRfTopdEg@mail.gmail.com>
References: <CANSA5-tMbuXW2FjpcjJ_UwNUhdKq0OyETpySS7jmDVRfTopdEg@mail.gmail.com>
Message-ID: <CANSA5-t=5L9YKAe9Nd4U7rxH2pvMHVURZj9tx6LPYwi8UKgsjQ@mail.gmail.com>

Disregard.  I saw it.


On Tue, Jun 30, 2020, 21:31 Lenard Spencer <lenardrspencer at gmail.com> wrote:

> Is it safe to upload new/updated scripts yet?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200630/83a10fad/attachment.htm>

From eric.b.pratt at gmail.com  Wed Jul  1 07:49:09 2020
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Wed, 1 Jul 2020 00:49:09 -0700
Subject: [Slackbuilds-users] Giving up my Slackbuilds
Message-ID: <CAPKhk4O-gQnAw1_2158P-TAfdrnot9foad2RrnBasVYG0_-a_g@mail.gmail.com>

I'm giving up my Slackbuilds.  I only have two.

  vice
  fwknop

Feel free to claim them however you see fit.

Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200701/74b154ed/attachment.htm>

From yalhcru at gmail.com  Wed Jul  1 07:53:45 2020
From: yalhcru at gmail.com (B Watson)
Date: Wed, 1 Jul 2020 03:53:45 -0400
Subject: [Slackbuilds-users] Giving up my Slackbuilds
In-Reply-To: <CAPKhk4O-gQnAw1_2158P-TAfdrnot9foad2RrnBasVYG0_-a_g@mail.gmail.com>
References: <CAPKhk4O-gQnAw1_2158P-TAfdrnot9foad2RrnBasVYG0_-a_g@mail.gmail.com>
Message-ID: <CAN1hMuD2hQXDoUXxu0buA0EQfhQC9RdT-2uUsGFXb_zbJwisUQ@mail.gmail.com>

On 7/1/20, Eric Pratt <eric.b.pratt at gmail.com> wrote:
> I'm giving up my Slackbuilds.  I only have two.
>
>   vice

I'll take vice, unless someone wants it really bad.

From Jim.Diamond at acadiau.ca  Wed Jul  1 16:17:28 2020
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Wed, 1 Jul 2020 13:17:28 -0300
Subject: [Slackbuilds-users] rubygem-gtk2 and friends
Message-ID: <20200701161728.GA26237@jdiamond-mb.acadiau.ca>

Hi all,

Dugan Chen is listed as the maintainer of a number of the rubygem
scripts, but he tells me he has given up all his slackbuilds.

Is there anyone who is keen to take them over?

(I ask not because I want to take them over, but because I am trying
to build rubygem-get2 on s64-current, where it crashes and burns.  And
yes, I know that I shouldn't really ask about slackware current issues
here.  But since there is an associated slackware 14.2 issue, I'll
mention it.)

Thanks.

                                Jim

From jdashiel at panix.com  Wed Jul  1 00:03:50 2020
From: jdashiel at panix.com (Jude DaShiell)
Date: Tue, 30 Jun 2020 20:03:50 -0400
Subject: [Slackbuilds-users] newsboat fun
In-Reply-To: <d623448c-0471-3037-8d6c-4a6cb936e38e@slint.fr>
References: <alpine.NEB.2.22.394.2006301403500.24948@panix1.panix.com>
 <20200630181414.GH30131@blackswan.r0t.uk>
 <alpine.NEB.2.22.394.2006301453480.26479@panix1.panix.com>
 <20200630190355.GI30131@blackswan.r0t.uk>
 <d623448c-0471-3037-8d6c-4a6cb936e38e@slint.fr>
Message-ID: <alpine.NEB.2.22.394.2006302002560.22629@panix1.panix.com>

successful build so far as I can tell.


-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build.zip
Type: application/zip
Size: 243810 bytes
Desc: 
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200630/004045f8/attachment-0001.zip>

From rworkman at slackbuilds.org  Wed Jul  1 22:32:28 2020
From: rworkman at slackbuilds.org (Robby Workman)
Date: Wed, 1 Jul 2020 17:32:28 -0500
Subject: [Slackbuilds-users] SBo web and git services migration
Message-ID: <20200701173228.22a531f5@home.rlworkman.net>

git.slackbuilds.org and www.slackbuilds.org are going to
be unreachable for a while later (git starting in just a
few minutes). Once all of the migration is complete, we'll
follow up with details on why and such...

-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/20200701/296014cb/attachment.asc>

From rworkman at slackbuilds.org  Thu Jul  2 13:06:50 2020
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 2 Jul 2020 08:06:50 -0500
Subject: [Slackbuilds-users] SBo service migration #1 complete
Message-ID: <20200702080650.52d4bf9c@home.rlworkman.net>

TLDR: Migration #1 complete

Pardon the temporary interruption of SBo services over the past
couple of days; due to impending closure of the data center in
which we are hosted (goodbye, onyxlight - y'all are awesome),
we have purchased a temporary dedicated server at another 
facility and have migrated git.slackbuilds.org, www.slackbuilds.org,
dance.slackbuilds.org (DNS slave), and slackwiki.com to it.
There will be another migration as soon as our physical hardware
is shipped to the new place and is set up, but we'll try to do
better about notification when that happens.

As an aside, we were fortunate to have Onyxlight provide free
colocation services for all these years, but our new location
will not be free. We are investigating options for collecting
needed funds for hosting (about $1500 per year), but we'll be
in touch with our historically awesome community once we settle
on how we want to pursue that. Yes, we have a paypal account,
but we can't keep a balance on that account unless we link it
to a bank account, and we don't want to do that because of 
potential tax liability to whomever's account gets linked. We
could transfer the balance to someone else's paypal account,
but then the tax liability question is still there, plus 
there is then the very real possibility of accidentally 
spending money from paypal balance instead of linked bank account
on personal transactions.  Long story short, we'll figure out
a way forward on that and follow up soon.

Sorry for the temporary downtime but thanks for your support!

-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/20200702/9bc2e30f/attachment.asc>

From gray at gnu.org  Fri Jul  3 07:31:17 2020
From: gray at gnu.org (Sergey Poznyakoff)
Date: Fri, 03 Jul 2020 10:31:17 +0300
Subject: [Slackbuilds-users] Giving up my Slackbuilds
In-Reply-To: Your message of Wed, 1 Jul 2020 00:49:09 -0700
 <CAPKhk4O-gQnAw1_2158P-TAfdrnot9foad2RrnBasVYG0_-a_g@mail.gmail.com>
References: <CAPKhk4O-gQnAw1_2158P-TAfdrnot9foad2RrnBasVYG0_-a_g@mail.gmail.com>
Message-ID: <20200703103117.31990@ulysses.gnu.org.ua>

Eric Pratt <eric.b.pratt at gmail.com> wrote:

> I'm giving up my Slackbuilds.  I only have two.
> 
>   vice
>   fwknop

I'll take fwknop, if there are no objections.

Best regards,
Sergey

From majek at w7i.pl  Fri Jul  3 12:02:18 2020
From: majek at w7i.pl (Marek Wodzinski)
Date: Fri, 3 Jul 2020 14:02:18 +0200 (CEST)
Subject: [Slackbuilds-users] SBo service migration #1 complete
In-Reply-To: <20200702080650.52d4bf9c@home.rlworkman.net>
References: <20200702080650.52d4bf9c@home.rlworkman.net>
Message-ID: <alpine.LNX.2.22.394.2007031253300.6520@toster2.pilczyce.net>

On Thu, 2 Jul 2020, Robby Workman wrote:

> and have migrated git.slackbuilds.org, www.slackbuilds.org,
> dance.slackbuilds.org (DNS slave), and slackwiki.com to it.

> will not be free. We are investigating options for collecting
> needed funds for hosting (about $1500 per year)

Have you thought about splitting services and migrate them to some hosted 
solutions?

For example git to Github or Gitlab, DNS to some free providers as 
dns.he.net, wiki to some inexpensive hosting or even migrate to 
readthedocs.org or Github pages?
I know that build machine, rsync and probably main site would be still 
main issue and I don't know numbers such as requests, i/o, cpu or monthly 
traffic, but maybe there is also some solution for it (like spin up one 
AWS instance to test build something and then kill it, or use some CI/CD 
solution)?
Splitting would also help to find friendly hosting/sponsor for other parts 
of site, like rsync could be handled by some of many Slackware mirrors.

$1500 is a real money and I believe that it would be better to get rid of 
these costs instead of worrying every year about paying it.

Anyway, thank you for your great work!


Marek
-- 
"If you want something done...do yourself!"
Jean-Baptiste Emmanuel Zorg

From nalumc at googlemail.com  Fri Jul  3 12:51:08 2020
From: nalumc at googlemail.com (Andrew Conway)
Date: Fri, 3 Jul 2020 13:51:08 +0100
Subject: [Slackbuilds-users] Protobuf3
Message-ID: <CAJRa=Rg8ODfj1Q15zqdHX3WSLtjPWjSovWt+Qu0eOJVF0-kEzw@mail.gmail.com>

Hi

I need to install protobuf3 as a dependency but I have packages that depend
on the original protobuf and the README for protobuf3 says:

"This package should NOT be installed alongside with protobuf.
        Protobuf3 introduced API incompatibility and upstream will
        continue to support protobuf version 2."

Any ideas for how I might be able to have both present? I'm on an
up-to-date slackware-current install.

thanks

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

From bifferos at gmail.com  Fri Jul  3 15:38:11 2020
From: bifferos at gmail.com (Biff Eros)
Date: Fri, 3 Jul 2020 15:38:11 +0000
Subject: [Slackbuilds-users] SBo service migration #1 complete
In-Reply-To: <alpine.LNX.2.22.394.2007031253300.6520@toster2.pilczyce.net>
References: <20200702080650.52d4bf9c@home.rlworkman.net>
 <alpine.LNX.2.22.394.2007031253300.6520@toster2.pilczyce.net>
Message-ID: <CAOcM_bmyedd-5=FET3M4m8udz9AJgNPujvCswXHpyEk1=OiYWg@mail.gmail.com>

On Fri, Jul 3, 2020 at 12:10 PM Marek Wodzinski <majek at w7i.pl> wrote:
> Have you thought about splitting services and migrate them to some hosted
> solutions?

I don't think you can write back-end code in a github website but I'm
sure you could fake the slackbuilds search interface by uploading the
compressed metadata (for dependencies and such) into some kind of
generated js script and do it all the in browser.  Submissions could
be via issue tracker.  I think there's an  API you can use to process
the information but I haven't looked at it yet.

So you're right, a lot could be done with some thought and effort.
Depends how much time people have free though :).

regards,
Biff.

From erik at slackbuilds.org  Fri Jul  3 16:20:31 2020
From: erik at slackbuilds.org (Erik Hanson)
Date: Fri, 3 Jul 2020 11:20:31 -0500
Subject: [Slackbuilds-users] SBo service migration #1 complete
In-Reply-To: <alpine.LNX.2.22.394.2007031253300.6520@toster2.pilczyce.net>
References: <20200702080650.52d4bf9c@home.rlworkman.net>
 <alpine.LNX.2.22.394.2007031253300.6520@toster2.pilczyce.net>
Message-ID: <ca1c660c-f688-967a-0ebd-c26c15d6773b@slackbuilds.org>

On 7/3/20 7:02 AM, Marek Wodzinski wrote:
> Have you thought about splitting services and migrate them to some
> hosted solutions?
> 
> For example git to Github or Gitlab, DNS to some free providers as
> dns.he.net, wiki to some inexpensive hosting or even migrate to
> readthedocs.org or Github pages?
> I know that build machine, rsync and probably main site would be still
> main issue and I don't know numbers such as requests, i/o, cpu or
> monthly traffic, but maybe there is also some solution for it (like spin
> up one AWS instance to test build something and then kill it, or use
> some CI/CD solution)?
> Splitting would also help to find friendly hosting/sponsor for other
> parts of site, like rsync could be handled by some of many Slackware
> mirrors.
> 
> $1500 is a real money and I believe that it would be better to get rid
> of these costs instead of worrying every year about paying it.

To clarify, it's around $130 per month. Not a yearly lump sum.

On average, the website moves around 55GB/mo, ~530k pages/mo, the git
server around 42GB/mo, ftp around 32GB/mo, and our Slackware mirror
around 268GB/mo. DNS and email hosting are not affected by this move.

Things are fairly interconnected just due to the way we've grown over
the past 14 years. Splitting things out to other services would probably
require a ground-up rebuild and I'm not convinced we would save any
money in the end.

At our new home, the hardware remains ours so things like I/O, CPU time,
disk space, etc. are not a concern. No unpredictable AWS bills. We also
have plenty of bandwidth. I believe this move is the right decision.


-- 
Erik




Also, I would sooner shutter the project than migrate to Github.

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

From atelszewski at gmail.com  Sat Jul  4 18:45:50 2020
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 4 Jul 2020 20:45:50 +0200
Subject: [Slackbuilds-users] Protobuf3
In-Reply-To: <CAJRa=Rg8ODfj1Q15zqdHX3WSLtjPWjSovWt+Qu0eOJVF0-kEzw@mail.gmail.com>
References: <CAJRa=Rg8ODfj1Q15zqdHX3WSLtjPWjSovWt+Qu0eOJVF0-kEzw@mail.gmail.com>
Message-ID: <5e92549a-c31e-af2b-b903-a005a36b7850@gmail.com>

On 03/07/2020 14:51, Andrew Conway via SlackBuilds-users wrote:
> Hi
>
> I need to install protobuf3 as a dependency but I have packages that 
> depend on the original protobuf and the README for protobuf3 says:
>
> "This package should NOT be installed alongside with protobuf.
> ? ? ? ? Protobuf3 introduced API incompatibility and upstream will
> ? ? ? ? continue to support protobuf version 2."
>
> Any ideas for how I might be able to have both present? I'm on an 
> up-to-date slackware-current install.
>
Would embedding _protobuf3_ within the package you prepare be a viable 
solution?
It's very often possible, but at times the cost is a lot of headache.

Something to think of, anyways.

Cheers!

--
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Sat Jul  4 19:00:22 2020
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 4 Jul 2020 21:00:22 +0200
Subject: [Slackbuilds-users] SBo service migration #1 complete
In-Reply-To: <ca1c660c-f688-967a-0ebd-c26c15d6773b@slackbuilds.org>
References: <20200702080650.52d4bf9c@home.rlworkman.net>
 <alpine.LNX.2.22.394.2007031253300.6520@toster2.pilczyce.net>
 <ca1c660c-f688-967a-0ebd-c26c15d6773b@slackbuilds.org>
Message-ID: <0ed8f768-e795-433f-dec3-2eb0ce462178@gmail.com>

On 03/07/2020 18:20, Erik Hanson wrote:
> At our new home, the hardware remains ours so things like I/O, CPU time,
> disk space, etc. are not a concern. No unpredictable AWS bills. We also
> have plenty of bandwidth. I believe this move is the right decision.
I support this choice with all my heart.
Over the years you proved (i.e. the SBo crew) that you can deal well 
with all the networking infrastructure needed.

When it comes to funding SBo, I see only one problem.
Once you ask for the funds, one has to be very quick with making the 
transfer.
Otherwise, it's all already donated. ;-)
But I know that you have good use for extra money, so that's not a 
problem whatsoever.

Have a good weekend!

--
Best regards,
Andrzej Telszewski

From nalumc at gmail.com  Mon Jul  6 09:00:44 2020
From: nalumc at gmail.com (Andrew Conway)
Date: Mon, 6 Jul 2020 10:00:44 +0100
Subject: [Slackbuilds-users] Protobuf3
In-Reply-To: <5e92549a-c31e-af2b-b903-a005a36b7850@gmail.com>
References: <CAJRa=Rg8ODfj1Q15zqdHX3WSLtjPWjSovWt+Qu0eOJVF0-kEzw@mail.gmail.com>
 <5e92549a-c31e-af2b-b903-a005a36b7850@gmail.com>
Message-ID: <CAJRa=Rg0_wPNRVCs6aZhsAukdkgZ=31Bo5hbD9exYaUmtz8_dg@mail.gmail.com>

Thanks, that hadn't crossed my mind but I think that's my best option.

On Sat, 4 Jul 2020, 19:45 Andrzej Telszewski, <atelszewski at gmail.com> wrote:

> On 03/07/2020 14:51, Andrew Conway via SlackBuilds-users wrote:
> > Hi
> >
> > I need to install protobuf3 as a dependency but I have packages that
> > depend on the original protobuf and the README for protobuf3 says:
> >
> > "This package should NOT be installed alongside with protobuf.
> >         Protobuf3 introduced API incompatibility and upstream will
> >         continue to support protobuf version 2."
> >
> > Any ideas for how I might be able to have both present? I'm on an
> > up-to-date slackware-current install.
> >
> Would embedding _protobuf3_ within the package you prepare be a viable
> solution?
> It's very often possible, but at times the cost is a lot of headache.
>
> Something to think of, anyways.
>
> Cheers!
>
> --
> Best regards,
> Andrzej Telszewski
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200706/56333c4c/attachment.htm>

From yalhcru at gmail.com  Mon Jul  6 23:21:57 2020
From: yalhcru at gmail.com (B Watson)
Date: Mon, 6 Jul 2020 19:21:57 -0400
Subject: [Slackbuilds-users] Protobuf3
In-Reply-To: <CAJRa=Rg0_wPNRVCs6aZhsAukdkgZ=31Bo5hbD9exYaUmtz8_dg@mail.gmail.com>
References: <CAJRa=Rg8ODfj1Q15zqdHX3WSLtjPWjSovWt+Qu0eOJVF0-kEzw@mail.gmail.com>
 <5e92549a-c31e-af2b-b903-a005a36b7850@gmail.com>
 <CAJRa=Rg0_wPNRVCs6aZhsAukdkgZ=31Bo5hbD9exYaUmtz8_dg@mail.gmail.com>
Message-ID: <CAN1hMuDGedGTYi0UjVLPEicmvzU7Y+aMo7BCteodDQqVOK6csg@mail.gmail.com>

On 7/6/20, Andrew Conway <nalumc at gmail.com> wrote:
> Thanks, that hadn't crossed my mind but I think that's my best option.

Without having actually looked at protobuf much...

...one solution would be to leave the regular protobuf (2.x) as-is,
and have protobuf3 install itself to /opt/protobuf3. Then modify
all the builds that depend on protobuf3, to have them look in /opt/
protobuf3 instead of /usr.

How you'd have to modify them depends on what they use for a build
system and how that's written, e.g. if they use autotools and
pkg-config, it might be enough to add:

export PKG_CONFIG_PATH=/opt/protobuf3/lib$LIBDIRSUFFIX/pkg-conf:$PKG_CONFIG_PATH

...to each SlackBuild that requires protobuf3. Some stuff you'd
probably have to export LDFLAGS and CFLAGS with the correct paths.

Doing it this way, you'd still *have* a protobuf3 package that other
builds could depend on. The other alternative would be for each build
to build its own static protobuf3 and link with that, I guess.

From kingbeowulf at gmail.com  Tue Jul  7 02:09:59 2020
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 6 Jul 2020 19:09:59 -0700
Subject: [Slackbuilds-users] SBo service migration #1 complete
In-Reply-To: <20200702080650.52d4bf9c@home.rlworkman.net>
References: <20200702080650.52d4bf9c@home.rlworkman.net>
Message-ID: <4ed2a785-2134-5823-e93f-d21ae63373dd@gmail.com>

On 7/2/20 6:06 AM, Robby Workman wrote:
> TLDR: Migration #1 complete
> 
>....
> We are investigating options for collecting
> needed funds for hosting (about $1500 per year), but we'll be
> in touch with our historically awesome community once we settle
> on how we want to pursue that. Yes, we have a paypal account,
> but we can't keep a balance on that account unless we link it
> to a bank account, and we don't want to do that because of 
> potential tax liability to whomever's account gets linked. We
> could transfer the balance to someone else's paypal account,
> but then the tax liability question is still there, plus 
> there is then the very real possibility of accidentally 
> spending money from paypal balance instead of linked bank account
> on personal transactions.  Long story short, we'll figure out
> a way forward on that and follow up soon.
> 
> Sorry for the temporary downtime but thanks for your support!
> 
> -RW
> 

Thanks to all the SBo admins for all the work - and onyxlight for the
free hosting. I'm always happy to contribute in anyway I can.

Since SBo already has essentially a "board of directors", perhaps it's
time to consider formalizing as a board-only nonprofit organization
(NPO). This may simplify collection donations and avoiding tax
liabilities, as well as allowing those who donate to reap a tax
deduction. After all, why should only the 1% benefit from tax shelters!

True, SBo will need to pass the hat for some lawyers, legal fees, etc to
set up all the paperwork and determine if 501(c)(3) (or similar) status
as a public charity is feasible. Setting up as an NPO confers some real
financial and sustainability benefits.

https://en.wikipedia.org/wiki/Nonprofit_organization

Speaking of which, Wikimedia Foundation is a board-only NPO. I'm not
saying SBo needs to grow that big (who knows!), but they are one example.

Just a food for thought,
-Ed


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

From rshepard at appl-ecosys.com  Tue Jul  7 12:37:16 2020
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 7 Jul 2020 05:37:16 -0700 (PDT)
Subject: [Slackbuilds-users] SBo service migration #1 complete
In-Reply-To: <4ed2a785-2134-5823-e93f-d21ae63373dd@gmail.com>
References: <20200702080650.52d4bf9c@home.rlworkman.net>
 <4ed2a785-2134-5823-e93f-d21ae63373dd@gmail.com>
Message-ID: <alpine.LNX.2.20.2007070533550.26435@salmo.appl-ecosys.com>

On Mon, 6 Jul 2020, King Beowulf wrote:

> True, SBo will need to pass the hat for some lawyers, legal fees, etc to
> set up all the paperwork and determine if 501(c)(3) (or similar) status as
> a public charity is feasible. Setting up as an NPO confers some real
> financial and sustainability benefits.

An accountant could do all the advising and paperwork while costing less
than an attorney. If you want to explore this idea I've an excellent
accountant who could be of as much value to SBo as she's been to my business
over the past couple or so decades.

Rich

From majek at w7i.pl  Tue Jul  7 15:12:53 2020
From: majek at w7i.pl (Marek Wodzinski)
Date: Tue, 7 Jul 2020 17:12:53 +0200 (CEST)
Subject: [Slackbuilds-users] SBo service migration #1 complete
In-Reply-To: <ca1c660c-f688-967a-0ebd-c26c15d6773b@slackbuilds.org>
References: <20200702080650.52d4bf9c@home.rlworkman.net>
 <alpine.LNX.2.22.394.2007031253300.6520@toster2.pilczyce.net>
 <ca1c660c-f688-967a-0ebd-c26c15d6773b@slackbuilds.org>
Message-ID: <alpine.LNX.2.22.394.2007071442230.6520@toster2.pilczyce.net>

On Fri, 3 Jul 2020, Erik Hanson wrote:

> On 7/3/20 7:02 AM, Marek Wodzinski wrote:
>> Have you thought about splitting services and migrate them to some
>> hosted solutions?
>>
> To clarify, it's around $130 per month. Not a yearly lump sum.

$130 for hosting AFAIK 10 years old EOL server which could fail anytime.
Costs of renting modern dedicated server starts from half of that price, 
additionaly it's possible failure is not your problem in term of hardware 
replacements.

> On average, the website moves around 55GB/mo, ~530k pages/mo, the git
> server around 42GB/mo, ftp around 32GB/mo, and our Slackware mirror
> around 268GB/mo. DNS and email hosting are not affected by this move.

Such amount of data could be hosted for less than $5/month on linux vps 
with full root access. It could cost some dollars extra when more storage 
would be needed, but basically 1TB/mo of transfer data is common limit 
seen even on small vps servers.

> Things are fairly interconnected just due to the way we've grown over
> the past 14 years. Splitting things out to other services would probably
> require a ground-up rebuild and I'm not convinced we would save any
> money in the end.

Maintenance is also cost. Even if you do it for free and it's your 
hobby. You could just use saved time to do other cool things :-)

I've been in similar point some years ago with my personal 
infrastructure. Everything connected to everything, single point of 
failures, lot of custom configuration and mess growing through years.
Then I went into lxc containers to separate web servers, mail, wifi 
controller, database and so on. I migrated my personal svn repository to 
git and then to Gitlab to not worry about hosting it.
It took time, but it's much easier to maintain now, while there are still 
some things on my to do list.
That's my way, yours could be of course very different.

I perfectly know that it's not possible to change everything at once and 
now, and maybe there will be no short term benefits.

Purpose of my comment was to show that there are other ways of doing 
things and some of them are are even for free, so maybe you could use 
some of them to ease maintenance, maybe reduce costs, maybe just make 
some long term plans, or just ignore it. Your choice.
No pushing, just trying to help showing options. If you feel offended, I 
do apologize.

> Also, I would sooner shutter the project than migrate to Github.

Are you aware that Slackbuilds already got more than 500 updates via 
Github mirror? :-)


Best regards,
Marek
-- 
"If you want something done...do yourself!"
Jean-Baptiste Emmanuel Zorg

From erik at slackbuilds.org  Tue Jul  7 18:38:53 2020
From: erik at slackbuilds.org (Erik Hanson)
Date: Tue, 7 Jul 2020 13:38:53 -0500
Subject: [Slackbuilds-users] SBo service migration #1 complete
In-Reply-To: <alpine.LNX.2.22.394.2007071442230.6520@toster2.pilczyce.net>
References: <20200702080650.52d4bf9c@home.rlworkman.net>
 <alpine.LNX.2.22.394.2007031253300.6520@toster2.pilczyce.net>
 <ca1c660c-f688-967a-0ebd-c26c15d6773b@slackbuilds.org>
 <alpine.LNX.2.22.394.2007071442230.6520@toster2.pilczyce.net>
Message-ID: <4065bf17-d71a-df3e-dcbc-c40e04280bc5@slackbuilds.org>

On 7/7/20 10:12 AM, Marek Wodzinski wrote:
> Purpose of my comment was to show that there are other ways of doing
> things and some of them are are even for free, so maybe you could use
> some of them to ease maintenance, maybe reduce costs, maybe just make
> some long term plans, or just ignore it. Your choice.
> No pushing, just trying to help showing options. If you feel offended, I
> do apologize.

I appreciate that, it's clear that information is lacking. We're not in
a hurry to raise money and more information will be made available
before we start asking for any.

>> Also, I would sooner shutter the project than migrate to Github.
> 
> Are you aware that Slackbuilds already got more than 500 updates via
> Github mirror? :-)

I am aware that an unofficial mirror exists and some admins might accept
pull requests there. That is at individual admin discretion. It is
otherwise not affiliated and absolutely not endorsed by SBo.


-- 
Erik

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

From bifferos at gmail.com  Wed Jul  8 22:05:48 2020
From: bifferos at gmail.com (Biff Eros)
Date: Wed, 8 Jul 2020 22:05:48 +0000
Subject: [Slackbuilds-users] SBo service migration #1 complete
In-Reply-To: <alpine.LNX.2.22.394.2007071442230.6520@toster2.pilczyce.net>
References: <20200702080650.52d4bf9c@home.rlworkman.net>
 <alpine.LNX.2.22.394.2007031253300.6520@toster2.pilczyce.net>
 <ca1c660c-f688-967a-0ebd-c26c15d6773b@slackbuilds.org>
 <alpine.LNX.2.22.394.2007071442230.6520@toster2.pilczyce.net>
Message-ID: <CAOcM_bk-ZgdKF8EE_Yh=8WfmdP_ZEs+JKtQq1hHiWXavm5sORw@mail.gmail.com>

On Tue, Jul 7, 2020 at 3:13 PM Marek Wodzinski <majek at w7i.pl> wrote:
> Purpose of my comment was to show that there are other ways of doing
> things and some of them are are even for free, so maybe you could use
> some of them to ease maintenance, maybe reduce costs, maybe just make
> some long term plans, or just ignore it. Your choice.
> No pushing, just trying to help showing options. If you feel offended, I
> do apologize.

It seems there's been an explosion of free stuff for OS Projects in the last
few years I have trouble keeping track of it all:

https://github.com/velikanov/opensource-candies

From bifferos at gmail.com  Wed Jul  8 22:14:46 2020
From: bifferos at gmail.com (Biff Eros)
Date: Wed, 8 Jul 2020 22:14:46 +0000
Subject: [Slackbuilds-users] Python packages naming question
Message-ID: <CAOcM_bn9xmeUQiiyJeZP3vxzayaLso08p-WXiT83+ySBffwO1A@mail.gmail.com>

If a python package only has python3 code in it, does it need to have
the python3- prefix?
If it depends on python3- prefixed packages does that mean it should
in turn have a python3- prefix itself?

Hopefully these are not silly questions!

From yth at ythogtha.org  Wed Jul  8 22:17:00 2020
From: yth at ythogtha.org (Arnaud)
Date: Thu, 9 Jul 2020 00:17:00 +0200
Subject: [Slackbuilds-users] Python packages naming question
In-Reply-To: <CAOcM_bn9xmeUQiiyJeZP3vxzayaLso08p-WXiT83+ySBffwO1A@mail.gmail.com>
References: <CAOcM_bn9xmeUQiiyJeZP3vxzayaLso08p-WXiT83+ySBffwO1A@mail.gmail.com>
Message-ID: <20200709001700.4444f7f6466d5dcb63d78348@ythogtha.org>

> If a python package only has python3 code in it, does it need to have
> the python3- prefix?
> If it depends on python3- prefixed packages does that mean it should
> in turn have a python3- prefix itself?
> 
> Hopefully these are not silly questions!

Hi!

	short answer is no.


Longer one is that mostly python3-package is useful when there is a different
[python-]package and python3-package.
	Since python3 will be the default on slackware 15, python2 being
deprecated, EOL'ed, dead and buried, obsolete, and forgotten, it seems there is
not much of a reason to call a new package python3-truc.


-- 
Arnaud <yth at ythogtha.org>

From ricardo at palmtx.com.ar  Wed Jul  8 22:56:39 2020
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Wed, 8 Jul 2020 19:56:39 -0300
Subject: [Slackbuilds-users] RSS feeds for Slakware's changelogs
Message-ID: <202007081956.39602.ricardo@palmtx.com.ar>

Since the migration the RRS feeds from sSBo started failing, yesterday I 
noticed that e.g. http://slackbuilds.org/mirror/rss/slackware64-14.2.rss 
redirects to https://mirror.slackbuilds.org/rss/slackware64-14.2.rss, which 
says 404.

I never noticed the there was a redirection, so I'd like to ask:
Is this a real problem or just part of the migration and we'll have to wait 
till it's finished?

I've already setup an alternative RSS feed in my reader, so no biggie :)

Thanks,
-- 
Ricardo J. Barberis
Usuario Linux N? 250625: http://counter.li.org/
Usuario LFS N? 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com

From willysr at slackbuilds.org  Thu Jul  9 00:11:29 2020
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 9 Jul 2020 07:11:29 +0700
Subject: [Slackbuilds-users] RSS feeds for Slakware's changelogs
In-Reply-To: <202007081956.39602.ricardo@palmtx.com.ar>
References: <202007081956.39602.ricardo@palmtx.com.ar>
Message-ID: <492d2145-d688-8ef5-3030-b1b0f4064d75@slackbuilds.org>

> Since the migration the RRS feeds from sSBo started failing, yesterday I 
> noticed that e.g. http://slackbuilds.org/mirror/rss/slackware64-14.2.rss 
> redirects to https://mirror.slackbuilds.org/rss/slackware64-14.2.rss, which 
> says 404.
> 
> I never noticed the there was a redirection, so I'd like to ask:
> Is this a real problem or just part of the migration and we'll have to wait 
> till it's finished?
> 
> I've already setup an alternative RSS feed in my reader, so no biggie :)

Get it from https://slackbuilds.org/rss/ChangeLog.rss


-- 
Willy Sudiarto Raharjo

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

From fernando.lopezjr at gmail.com  Thu Jul  9 00:12:59 2020
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Wed, 8 Jul 2020 18:12:59 -0600
Subject: [Slackbuilds-users] makemkv not found :|
Message-ID: <CALrQ46DyWMZ3E12hFXGuf8z+OjvVwfpipuq6+pOeMg01iUNTnQ@mail.gmail.com>

makemkv:
makemkv not found in /var/cache/sbopkg.
--2020-07-08 18:12:25--
http://www.makemkv.com/download/makemkv-oss-1.14.4.tar.gz
Resolving www.makemkv.com (www.makemkv.com)... 172.67.195.244,
104.24.104.123, 104.24.105.123, ...
Connecting to www.makemkv.com (www.makemkv.com)|172.67.195.244|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
2020-07-08 18:12:25 ERROR 404: Not Found.

-- 

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

From willysr at slackbuilds.org  Thu Jul  9 00:17:13 2020
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 9 Jul 2020 07:17:13 +0700
Subject: [Slackbuilds-users] makemkv not found :|
In-Reply-To: <CALrQ46DyWMZ3E12hFXGuf8z+OjvVwfpipuq6+pOeMg01iUNTnQ@mail.gmail.com>
References: <CALrQ46DyWMZ3E12hFXGuf8z+OjvVwfpipuq6+pOeMg01iUNTnQ@mail.gmail.com>
Message-ID: <6b191a91-3373-b865-ddc3-23bf631d50b5@slackbuilds.org>

> makemkv:
> makemkv not found in /var/cache/sbopkg.
> --2020-07-08 18:12:25--
> http://www.makemkv.com/download/makemkv-oss-1.14.4.tar.gz
> Resolving www.makemkv.com (www.makemkv.com)... 172.67.195.244,
> 104.24.104.123, 104.24.105.123, ...
> Connecting to www.makemkv.com (www.makemkv.com)|172.67.195.244|:80...
> connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2020-07-08 18:12:25 ERROR 404: Not Found.

Fixed in SBo website
Will push it to git as well

-- 
Willy Sudiarto Raharjo

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

From ricardo at palmtx.com.ar  Sat Jul 11 00:27:22 2020
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Fri, 10 Jul 2020 21:27:22 -0300
Subject: [Slackbuilds-users] RSS feeds for Slakware's changelogs
In-Reply-To: <492d2145-d688-8ef5-3030-b1b0f4064d75@slackbuilds.org>
References: <202007081956.39602.ricardo@palmtx.com.ar>
 <492d2145-d688-8ef5-3030-b1b0f4064d75@slackbuilds.org>
Message-ID: <202007102127.22890.ricardo@palmtx.com.ar>

El Mi?rcoles 08/07/2020 a las 21:11, Willy Sudiarto Raharjo escribi?:
> > Since the migration the RRS feeds from sSBo started failing, yesterday I
> > noticed that e.g. http://slackbuilds.org/mirror/rss/slackware64-14.2.rss
> > redirects to https://mirror.slackbuilds.org/rss/slackware64-14.2.rss,
> > which says 404.
> >
> > I never noticed the there was a redirection, so I'd like to ask:
> > Is this a real problem or just part of the migration and we'll have to
> > wait till it's finished?
> >
> > I've already setup an alternative RSS feed in my reader, so no biggie :)
>
> Get it from https://slackbuilds.org/rss/ChangeLog.rss

That's for SBo and it's working fine for me.

I meant the feeds generated from Slackware's changelogs, which used to live
at http://slackbuilds.org/mirror/rss/, like slackware64-14.2.rss,
slackware-14.2.rss, slackware64-current.rss, etc

Cheers,
-- 
Ricardo J. Barberis
Usuario Linux N? 250625: http://counter.li.org/
Usuario LFS N? 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com

From rworkman at slackbuilds.org  Sat Jul 11 17:48:22 2020
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sat, 11 Jul 2020 12:48:22 -0500
Subject: [Slackbuilds-users] RSS feeds for Slakware's changelogs
In-Reply-To: <202007081956.39602.ricardo@palmtx.com.ar>
References: <202007081956.39602.ricardo@palmtx.com.ar>
Message-ID: <20200711124822.6860a7a6@home.rlworkman.net>

On Wed, 8 Jul 2020 19:56:39 -0300
"Ricardo J. Barberis" <ricardo at palmtx.com.ar> wrote:

> Since the migration the RRS feeds from sSBo started failing,
> yesterday I noticed that e.g.
> http://slackbuilds.org/mirror/rss/slackware64-14.2.rss redirects to
> https://mirror.slackbuilds.org/rss/slackware64-14.2.rss, which says
> 404.
> 
> I never noticed the there was a redirection, so I'd like to ask:
> Is this a real problem or just part of the migration and we'll have
> to wait till it's finished?
> 
> I've already setup an alternative RSS feed in my reader, so no biggie
> :)


I think it's fixed now - try it and let us know.

-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/20200711/0e0860cc/attachment.asc>

From ricardo at palmtx.com.ar  Sat Jul 11 20:14:58 2020
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Sat, 11 Jul 2020 17:14:58 -0300
Subject: [Slackbuilds-users] RSS feeds for Slakware's changelogs
In-Reply-To: <20200711124822.6860a7a6@home.rlworkman.net>
References: <202007081956.39602.ricardo@palmtx.com.ar>
 <20200711124822.6860a7a6@home.rlworkman.net>
Message-ID: <3279f0972e311b60ac11c63795afe70c@palmtx.com.ar>

El 2020/07/11 14:48, Robby Workman escribi?:
> On Wed, 8 Jul 2020 19:56:39 -0300
> "Ricardo J. Barberis" <ricardo at palmtx.com.ar> wrote:
> 
>> Since the migration the RRS feeds from sSBo started failing,
>> yesterday I noticed that e.g.
>> http://slackbuilds.org/mirror/rss/slackware64-14.2.rss redirects to
>> https://mirror.slackbuilds.org/rss/slackware64-14.2.rss, which says
>> 404.
>> 
>> I never noticed the there was a redirection, so I'd like to ask:
>> Is this a real problem or just part of the migration and we'll have
>> to wait till it's finished?
>> 
>> I've already setup an alternative RSS feed in my reader, so no biggie
>> :)
> 
> 
> I think it's fixed now - try it and let us know.
> 
> -RW

Yep, working fine now :)

Thanks!
-- 
Living la vida Linux!

From davidnchmelik at gmail.com  Tue Jul 14 01:26:14 2020
From: davidnchmelik at gmail.com (David Chmelik)
Date: Mon, 13 Jul 2020 18:26:14 -0700
Subject: [Slackbuilds-users] fbpic SlackBuild is nothing
Message-ID: <8726fddd-4c7f-7f76-88dc-cdd0bc63d754@gmail.com>

The fbpic SlackBuild contains nothing.? How was that even accepted?! 
(yes, I did build it on Slackware-stable without using SBo-git, before.? 
It was the same.)

PACKAGE NAME:???? fbpic-0.0.2-x86_64-1ponce
COMPRESSED PACKAGE SIZE:???? 4.5K
UNCOMPRESSED PACKAGE SIZE:???? 10K
PACKAGE LOCATION: pkg64/fbpic-0.0.2-x86_64-1ponce.tgz
PACKAGE DESCRIPTION:
fbpic: fbpic (display an image on the framebuffer)
fbpic:
fbpic: A simple command line app to display an image on the framebuffer.
fbpic:
fbpic: Homepage: http://keithhedger.hostingsiteforfree.com
fbpic:
fbpic:
fbpic:
fbpic:
fbpic:
fbpic:
FILE LIST:
./
install/
install/doinst.sh
install/slack-desc
usr/
usr/doc/
usr/doc/fbpic-0.0.2/
usr/doc/fbpic-0.0.2/fbpic.SlackBuild


From yalhcru at gmail.com  Tue Jul 14 03:58:52 2020
From: yalhcru at gmail.com (B Watson)
Date: Mon, 13 Jul 2020 23:58:52 -0400
Subject: [Slackbuilds-users] fbpic SlackBuild is nothing
In-Reply-To: <8726fddd-4c7f-7f76-88dc-cdd0bc63d754@gmail.com>
References: <8726fddd-4c7f-7f76-88dc-cdd0bc63d754@gmail.com>
Message-ID: <CAN1hMuD7tO=q+7F0Fs4oGfrGJ1JGMM-HBe9Y3RepTsgJQwcDpA@mail.gmail.com>

On 7/13/20, David Chmelik <davidnchmelik at gmail.com> wrote:
> The fbpic SlackBuild contains nothing.  How was that even accepted?!

Confirmed, I get the same result. Looks like it's been broken since
2012...?

The build has multiple issues. Plus, fbpic itself is pretty useless:
it displays only PPM images, and only on consoles with 16bpp
colordepth (24bpp and 32bpp have been standard for ages now).

For displaying images on a framebuffer, you might try fbida or
fbv. Both support multiple file formats (e.g. jpg, png, gif) and both
support modern 32bpp framebuffers.

From dave at slackbuilds.org  Tue Jul 14 05:25:43 2020
From: dave at slackbuilds.org (Dave Woodfall)
Date: Tue, 14 Jul 2020 06:25:43 +0100
Subject: [Slackbuilds-users] fbpic SlackBuild is nothing
In-Reply-To: <CAN1hMuD7tO=q+7F0Fs4oGfrGJ1JGMM-HBe9Y3RepTsgJQwcDpA@mail.gmail.com>
References: <8726fddd-4c7f-7f76-88dc-cdd0bc63d754@gmail.com>
 <CAN1hMuD7tO=q+7F0Fs4oGfrGJ1JGMM-HBe9Y3RepTsgJQwcDpA@mail.gmail.com>
Message-ID: <20200714052543.GB17770@blackswan.r0t.uk>

On 13/07/20 23:58,
B Watson <yalhcru at gmail.com> put forth the proposition:
> On 7/13/20, David Chmelik <davidnchmelik at gmail.com> wrote:
> > The fbpic SlackBuild contains nothing.  How was that even accepted?!
> Confirmed, I get the same result. Looks like it's been broken since
> 2012...?
> The build has multiple issues. Plus, fbpic itself is pretty useless:
> it displays only PPM images, and only on consoles with 16bpp
> colordepth (24bpp and 32bpp have been standard for ages now).
> For displaying images on a framebuffer, you might try fbida or
> fbv. Both support multiple file formats (e.g. jpg, png, gif) and both
> support modern 32bpp framebuffers.

I would also add fim (Fbi IMproved) to that list.  It fixes the issue
when scrolling down with arrow keys goes off in a diagonal direction.

--
Dave
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200714/caca8d19/attachment-0001.asc>

From dickson.tim at googlemail.com  Fri Jul 17 10:53:53 2020
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Fri, 17 Jul 2020 11:53:53 +0100
Subject: [Slackbuilds-users] gloox slackbuild
Message-ID: <f6e56ab8-10ac-31c2-e6be-c07832bb874c@googlemail.com>

I noticed this gloox has been orphaned, and it is a dependency for 0ad 
so if no-one else wants it,
I'll look after it, and will update it with a current (1.0.23) version 
when submissions are open again.


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


From gen-bch at useyouresp.org.uk  Sun Jul 19 11:06:23 2020
From: gen-bch at useyouresp.org.uk (Habs)
Date: Sun, 19 Jul 2020 12:06:23 +0100 (BST)
Subject: [Slackbuilds-users] inkscape md5sum
Message-ID: <sr308s-1297-3064-8s7n-qs89qs28pos2@hfrlbherfc.bet.hx>

Hello Fernando

Today I am compiling inkscape and the  source md5sum does not match the 
one provided in the SBo info.

md5 of source gives: a6624720a925e7cc885e7df9927daffb

md5 from info: ac30f6d5747fd9c620c00dad500f414f


Thank you
Habs

--- Sent using Alpine/Pine, probably the best MUA ---

From dave at slackbuilds.org  Sun Jul 19 14:48:40 2020
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 19 Jul 2020 15:48:40 +0100
Subject: [Slackbuilds-users] inkscape md5sum
In-Reply-To: <sr308s-1297-3064-8s7n-qs89qs28pos2@hfrlbherfc.bet.hx>
References: <sr308s-1297-3064-8s7n-qs89qs28pos2@hfrlbherfc.bet.hx>
Message-ID: <20200719144840.GA21467@blackswan.r0t.uk>

On 19/07/20 12:06,
Habs <gen-bch at useyouresp.org.uk> put forth the proposition:
> Hello Fernando
> Today I am compiling inkscape and the  source md5sum does not match the one
> provided in the SBo info.
> md5 of source gives: a6624720a925e7cc885e7df9927daffb
> md5 from info: ac30f6d5747fd9c620c00dad500f414f
> Thank you
> Habs
> --- Sent using Alpine/Pine, probably the best MUA ---

I don't think the source download link is downloading the source.  Try
this:

https://inkscape.org/gallery/item/13330/inkscape-0.92.4.tar.bz2

You will need to remove the $PRGSUB part of the tar command line in
the slackbuild for it to work though.

--
Dave
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200719/75da0097/attachment.asc>

From gen-bch at useyouresp.org.uk  Sun Jul 19 16:58:57 2020
From: gen-bch at useyouresp.org.uk (Habs)
Date: Sun, 19 Jul 2020 17:58:57 +0100 (BST)
Subject: [Slackbuilds-users] inkscape md5sum
In-Reply-To: <20200719144840.GA21467@blackswan.r0t.uk>
References: <sr308s-1297-3064-8s7n-qs89qs28pos2@hfrlbherfc.bet.hx>
 <20200719144840.GA21467@blackswan.r0t.uk>
Message-ID: <noon98q-oq9o-127-9q9q-2r78op29qr85@hfrlbherfc.bet.hx>

On Sun, 19 Jul 2020, Dave Woodfall wrote:

> On 19/07/20 12:06,
> Habs <gen-bch at useyouresp.org.uk> put forth the proposition:
>> Hello Fernando
>> Today I am compiling inkscape and the  source md5sum does not match the one
>> provided in the SBo info.
>> md5 of source gives: a6624720a925e7cc885e7df9927daffb
>> md5 from info: ac30f6d5747fd9c620c00dad500f414f
>> Thank you
>> Habs
>> --- Sent using Alpine/Pine, probably the best MUA ---
>
> I don't think the source download link is downloading the source.  Try
> this:
>
> https://inkscape.org/gallery/item/13330/inkscape-0.92.4.tar.bz2
>
> You will need to remove the $PRGSUB part of the tar command line in
> the slackbuild for it to work though.
>
> --
> Dave
>

Thank you for the link.  I do not know what has gone on there with that 
SBo build package, or why the PRGSUB addition etc. I will try compile it 
later.

Regards
Habs

--- Sent using Alpine/Pine, probably the best MUA ---

From dave at slackbuilds.org  Sun Jul 19 17:01:23 2020
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 19 Jul 2020 18:01:23 +0100
Subject: [Slackbuilds-users] inkscape md5sum
In-Reply-To: <noon98q-oq9o-127-9q9q-2r78op29qr85@hfrlbherfc.bet.hx>
References: <sr308s-1297-3064-8s7n-qs89qs28pos2@hfrlbherfc.bet.hx>
 <20200719144840.GA21467@blackswan.r0t.uk>
 <noon98q-oq9o-127-9q9q-2r78op29qr85@hfrlbherfc.bet.hx>
Message-ID: <20200719170123.GB21467@blackswan.r0t.uk>

On 19/07/20 17:58,
Habs <gen-bch at useyouresp.org.uk> put forth the proposition:
> On Sun, 19 Jul 2020, Dave Woodfall wrote:
> > On 19/07/20 12:06,
> > Habs <gen-bch at useyouresp.org.uk> put forth the proposition:
> > > Hello Fernando
> > > Today I am compiling inkscape and the  source md5sum does not match the one
> > > provided in the SBo info.
> > > md5 of source gives: a6624720a925e7cc885e7df9927daffb
> > > md5 from info: ac30f6d5747fd9c620c00dad500f414f
> > > Thank you
> > > Habs
> > > --- Sent using Alpine/Pine, probably the best MUA ---
> >
> > I don't think the source download link is downloading the source.  Try
> > this:
> >
> > https://inkscape.org/gallery/item/13330/inkscape-0.92.4.tar.bz2
> >
> > You will need to remove the $PRGSUB part of the tar command line in
> > the slackbuild for it to work though.
> >
> > --
> > Dave
> >
> Thank you for the link.  I do not know what has gone on there with that SBo
> build package, or why the PRGSUB addition etc. I will try compile it later.
> Regards
> Habs
> --- Sent using Alpine/Pine, probably the best MUA ---

I've fixed it in my branch.

--
Dave
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200719/0afb0864/attachment.asc>

From ld.jay at protonmail.com  Mon Jul 20 16:42:27 2020
From: ld.jay at protonmail.com (ld.jay)
Date: Mon, 20 Jul 2020 16:42:27 +0000
Subject: [Slackbuilds-users] RTL8192 driver: source link broken.
Message-ID: <eyImr3wrZOo68InO8lqhBJHfazyJZ_57TAV8-2TygZQ9URG96thtEhHZwEaPCT0eDf-pFkAWlh3YIMfBmf_FUKm4qNZPDM77b2R_CXkTTc0=@protonmail.com>

It has come to my attention that the source download link provided for my SlackBuild of this wifi driver is no longer working...

It appears that TP-Link has decided to disallow direct linking to the source archive, because the ZIP file is still there (the link is the same,) but now you have to go through their web-page to actually get the source. (Linking directly to the ZIP archive results in "Visit our homepage" message.)

So, the new link should be:
https://www.tp-link.com/us/support/download/tl-wn823n/#Driver
then click on "[TL-WN823N(US)_V3_180508_Linux_beta](https://static.tp-link.com/2018/201805/20180514/TP-Link_Driver_Linux_series8_beta.zip)" to get the source.

Being relatively new to SBo, I'm not sure about the proper procedure for fixing this. Since submissions are closed now, I'm hoping one of the SBo admins will see this message and just update the .info and/or the README included with my slackbuild. If there is any further action I should take, just let me know.

Thanks,
Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200720/076040ae/attachment.htm>

From yalhcru at gmail.com  Wed Jul 22 03:02:05 2020
From: yalhcru at gmail.com (B Watson)
Date: Tue, 21 Jul 2020 23:02:05 -0400
Subject: [Slackbuilds-users] RTL8192 driver: source link broken.
In-Reply-To: <eyImr3wrZOo68InO8lqhBJHfazyJZ_57TAV8-2TygZQ9URG96thtEhHZwEaPCT0eDf-pFkAWlh3YIMfBmf_FUKm4qNZPDM77b2R_CXkTTc0=@protonmail.com>
References: <eyImr3wrZOo68InO8lqhBJHfazyJZ_57TAV8-2TygZQ9URG96thtEhHZwEaPCT0eDf-pFkAWlh3YIMfBmf_FUKm4qNZPDM77b2R_CXkTTc0=@protonmail.com>
Message-ID: <CAN1hMuBCOV7ZMDMDXZUG+oHDCjYeg+3Yf8wf9iYqpHJ0WOLZhA@mail.gmail.com>

On 7/20/20, ld.jay via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:
> It has come to my attention that the source download link provided for my
> SlackBuild of this wifi driver is no longer working...

Have I got the right link?

https://static.tp-link.com/2018/201805/20180514/TP-Link_Driver_Linux_series8_beta.zip

> It appears that TP-Link has decided to disallow direct linking to the source
> archive, because the ZIP file is still there (the link is the same,) but now
> you have to go through their web-page to actually get the source. (Linking
> directly to the ZIP archive results in "Visit our homepage" message.)

Hm. I just downloaded it with wget, with no problem.

And downloaded it again, with curl. And with PaleMoon, and elinks...

> If there is any further action I should take,
> just let me know.

Well, one of us could add a note in the README about how to download
the file, but from my testing I can't find the problem.

What were you using that failed to download the file? If wget works
for you, the README could be updated to say "If you have trouble
downloading the source file, try using wget instead of a browser",
something like that.

If you're using a browser, see what happens if you disable JavaScript.
If that turns out to fix it, the README can mention JS.

From dickson.tim at googlemail.com  Wed Jul 22 11:04:22 2020
From: dickson.tim at googlemail.com (Tim Dickson)
Date: Wed, 22 Jul 2020 12:04:22 +0100
Subject: [Slackbuilds-users] wsdd2
Message-ID: <757680ce-cdd4-ced6-b32c-cb14d74fa48b@googlemail.com>

hi all, I'm creating a slackbuild for wsdd2. this provides device and 
samba share browsing when netbios is not used.
As this includes ip6, it is pretty essential in a lan unless you disable 
ip6 on all the windows clients, as it allows autodiscovery. (you do need 
to make sure you allow ip6 addresses in smb.conf as well)

There isn't an rc.wsdd2 file with the source, so I was thinking of 
creating one. What I am not sure is the preferred way of adding it to 
rc.M and rc.K or similar in the doinst.sh
It would be nice if the package was activated when it was installed. It 
could always be de-activated by removing the executable bit from it's rc 
file.
i could grep for it, and if not there, then add it, but that doesn't 
handle removing it if someone removes the package.

I was surprised it hadn't been added to samba already, but looking at 
the samba mailing list, it has been sitting around but not added for 4 
years. assuming it does eventually get added, then there will be no need 
for a separate package, but until that time, it is pretty essential with 
windows 10 these days.

are there recommended ways of adding rc files so that they are run on 
startup. ?
thanks, Tim
regards, Tim

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


From matteo.bernardini at gmail.com  Wed Jul 22 11:23:27 2020
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 22 Jul 2020 13:23:27 +0200
Subject: [Slackbuilds-users] wsdd2
In-Reply-To: <757680ce-cdd4-ced6-b32c-cb14d74fa48b@googlemail.com>
References: <757680ce-cdd4-ced6-b32c-cb14d74fa48b@googlemail.com>
Message-ID: <CAPsDuS448zA34BjRS1vbPVk0GQOVf4qUQzEoLO+McTiRCMmhrQ@mail.gmail.com>

Il giorno mer 22 lug 2020 alle ore 13:04 Tim Dickson via
SlackBuilds-users <slackbuilds-users at slackbuilds.org> ha scritto:
>
> hi all, I'm creating a slackbuild for wsdd2. this provides device and
> samba share browsing when netbios is not used.
> As this includes ip6, it is pretty essential in a lan unless you disable
> ip6 on all the windows clients, as it allows autodiscovery. (you do need
> to make sure you allow ip6 addresses in smb.conf as well)
>
> There isn't an rc.wsdd2 file with the source, so I was thinking of
> creating one. What I am not sure is the preferred way of adding it to
> rc.M and rc.K or similar in the doinst.sh
> It would be nice if the package was activated when it was installed. It
> could always be de-activated by removing the executable bit from it's rc
> file.
> i could grep for it, and if not there, then add it, but that doesn't
> handle removing it if someone removes the package.
>
> I was surprised it hadn't been added to samba already, but looking at
> the samba mailing list, it has been sitting around but not added for 4
> years. assuming it does eventually get added, then there will be no need
> for a separate package, but until that time, it is pretty essential with
> windows 10 these days.
>
> are there recommended ways of adding rc files so that they are run on
> startup. ?
> thanks, Tim
> regards, Tim

silently modifying Slackware startup scripts in the doinst.sh isn't
allowed (as it's considered dangerous) but you can add a note to the
README with details on the modificatiions to apply: here is an example

https://slackbuilds.org/slackbuilds/14.2/system/lxdm/README.SLACKWARE

Matteo

From ld.jay at protonmail.com  Wed Jul 22 07:09:29 2020
From: ld.jay at protonmail.com (ld.jay)
Date: Wed, 22 Jul 2020 07:09:29 +0000
Subject: [Slackbuilds-users] RTL8192 driver: source link broken.
In-Reply-To: <CAN1hMuBCOV7ZMDMDXZUG+oHDCjYeg+3Yf8wf9iYqpHJ0WOLZhA@mail.gmail.com>
References: <eyImr3wrZOo68InO8lqhBJHfazyJZ_57TAV8-2TygZQ9URG96thtEhHZwEaPCT0eDf-pFkAWlh3YIMfBmf_FUKm4qNZPDM77b2R_CXkTTc0=@protonmail.com>
 <CAN1hMuBCOV7ZMDMDXZUG+oHDCjYeg+3Yf8wf9iYqpHJ0WOLZhA@mail.gmail.com>
Message-ID: <y7JdWONzvDIV8qBjllsv0Rg5tDktSUPvQLAl7G59sZG4mwcbiCNiA5SAUYVLfKi2vtgGinBW1HkmsUMWbOLpTYkP3K85-oivH9JoRb3obZ0=@protonmail.com>

??????? Original Message ???????
On Tuesday, July 21, 2020 8:02 PM, B Watson <yalhcru at gmail.com> wrote:

>
> Have I got the right link?
>
> https://static.tp-link.com/2018/201805/20180514/TP-Link_Driver_Linux_series8_beta.zip
>

Yes, that's the right link.

>
> Hm. I just downloaded it with wget, with no problem.
>
> And downloaded it again, with curl. And with PaleMoon, and elinks...
>

Strange.  I'm using Palemoon, too, and for me, clicking the above link takes me to a page that says:
"Please go to TP-Link Offical Website to get products, software and services for your region."

But wget of the same link works like a charm.

I tried it in Palemoon w/ JS on and off, and even tried switching from "native" palemoon user-agent mode to "firefox compatibility" mode--no dice.

> ... If wget works
> for you, the README could be updated to say "If you have trouble
> downloading the source file, try using wget instead of a browser",
> something like that.

I think that's exactly what I'll do: I'll add such a line to the README.  In the mean time, since the link seems to be working for most, I won't lose any sleep over it.  (The user who alerted me to the "Please visit our homepage" message could just as easily click the HOMEPAGE link provided on SBo right above the source link and then download the source ZIP from there.)

Thanks for your feedback,
Jay

From don_sfw at dlaster.com  Thu Jul 23 01:29:12 2020
From: don_sfw at dlaster.com (Donald R Laster Jr)
Date: Wed, 22 Jul 2020 21:29:12 -0400
Subject: [Slackbuilds-users] wsdd2
In-Reply-To: <CAPsDuS448zA34BjRS1vbPVk0GQOVf4qUQzEoLO+McTiRCMmhrQ@mail.gmail.com>
References: <757680ce-cdd4-ced6-b32c-cb14d74fa48b@googlemail.com>
 <CAPsDuS448zA34BjRS1vbPVk0GQOVf4qUQzEoLO+McTiRCMmhrQ@mail.gmail.com>
Message-ID: <bbce498d-87da-3bce-ba29-7971c57a4ba4@dlaster.com>


Matteo Bernardini wrote on 07/22/2020 07:23 AM:
> Il giorno mer 22 lug 2020 alle ore 13:04 Tim Dickson via
> SlackBuilds-users <slackbuilds-users at slackbuilds.org> ha scritto:
>>
>> hi all, I'm creating a slackbuild for wsdd2. this provides device and
>> samba share browsing when netbios is not used.
>> As this includes ip6, it is pretty essential in a lan unless you disable
>> ip6 on all the windows clients, as it allows autodiscovery. (you do need
>> to make sure you allow ip6 addresses in smb.conf as well)
>>
>> There isn't an rc.wsdd2 file with the source, so I was thinking of
>> creating one. What I am not sure is the preferred way of adding it to
>> rc.M and rc.K or similar in the doinst.sh
>> It would be nice if the package was activated when it was installed. It
>> could always be de-activated by removing the executable bit from it's rc
>> file.
>> i could grep for it, and if not there, then add it, but that doesn't
>> handle removing it if someone removes the package.
>>
>> I was surprised it hadn't been added to samba already, but looking at
>> the samba mailing list, it has been sitting around but not added for 4
>> years. assuming it does eventually get added, then there will be no need
>> for a separate package, but until that time, it is pretty essential with
>> windows 10 these days.
>>
>> are there recommended ways of adding rc files so that they are run on
>> startup. ?
>> thanks, Tim
>> regards, Tim
> 
> silently modifying Slackware startup scripts in the doinst.sh isn't
> allowed (as it's considered dangerous) but you can add a note to the
> README with details on the modificatiions to apply: here is an example
> 
> https://slackbuilds.org/slackbuilds/14.2/system/lxdm/README.SLACKWARE
> 
> Matteo
> _______________________________________________
> 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/
> 

Tim,

   Create the rc.wsdd2 and then document something that says to active the program add the following lines to the /etc/rc.d/rc.local file:

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

The rc.local file is for local things to be done at startup.  Then indicate that the following lines should be added to the /etc/rc.d/rc.local_shutdown file:

   if [ -x /etc/rc.d/rc.wsdd2 ] ; then
           /etc/rc.d/rc.wsdd2 stop
   fi

   Obviously, the rc.wsdd2 script would need to support a "start" and "stop" option. You should probably also support a "restart" and "status" in the rc.wsdd2 script.

   The rc.local_shutdown file is for local things to be done at shutdown. It does not exist by default.

    The rc.local and rc.local_shutdown scripts are invoked from the rc.M and rc.6/rc.0 scripts at the appropriate time.  This is the rc.local file from Slackware 14.2:

   #!/bin/sh
   #
   # /etc/rc.d/rc.local:  Local system initialization script.
   #
   # Put any local startup commands in here.  Also, if you have
   # anything that needs to be run at shutdown time you can
   # make an /etc/rc.d/rc.local_shutdown script and put those
   # commands in there.

   As Matteo pointed out you do not want to make changes to the /etc/rc.d/rc.M or the /etc/rc.d/rc.S  files.  Documents the needed changes in the appropriate README file.

   Don


From fernando.lopezjr at gmail.com  Thu Jul 23 16:41:08 2020
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Thu, 23 Jul 2020 10:41:08 -0600
Subject: [Slackbuilds-users] wxPython3 invalid md5sum
Message-ID: <CALrQ46ALqd7QN8P+f96OkZ1Jxq8aXSKaTYiXVLvCCntQ5FBEFA@mail.gmail.com>

Processing wxPython3

wxPython3:
wxPython3 not found in /var/cache/sbopkg.
--2020-07-23 10:39:56--
https://sourceforge.net/projects/wxpython/files/wxPython/3.0.2.0/wxPython-src-3.0.2.0.tar.bz2
Resolving sourceforge.net (sourceforge.net)... 99.84.191.125,
99.84.191.126, 99.84.191.36, ...
Connecting to sourceforge.net (sourceforge.net)|99.84.191.125|:443...
connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location:
https://sourceforge.net/#!/projects/wxpython/files/wxPython/3.0.2.0/wxPython-src-3.0.2.0.tar.bz2
[following]
--2020-07-23 10:39:57--  https://sourceforge.net/
Reusing existing connection to sourceforge.net:443.
HTTP request sent, awaiting response... 200 OK
Length: 746 [text/html]
Saving to: ?wxPython-src-3.0.2.0.tar.bz2?

wxPython-src-3.0.2. 100%[===================>]     746  --.-KB/s    in 0s


2020-07-23 10:39:58 (106 MB/s) - ?wxPython-src-3.0.2.0.tar.bz2? saved
[746/746]

Found wxPython-src-3.0.2.0.tar.bz2 in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for wxPython-src-3.0.2.0.tar.bz2 ... FAILED!
    Expected: 922b02ff2c0202a7bf1607c98bbbbc04
    Found:    afd33cb888461aae3bfd05b80c9e42a8

Do you want to use the downloaded wxPython3 source:
wxPython-src-3.0.2.0.tar.bz2 in /var/cache/sbopkg?

You can choose among the following options:
 - (Y)es, keep the source and continue the build process;
 - (N)o, delete the source and abort the build process;
 - (R)etry download and continue the build process; or
 - (A)ttempt to download from third party source repository.
(Y)es, (N)o, (R)etry, (A)lternative ?:

-- 

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

From mrvladislavovich at gmail.com  Thu Jul 23 16:58:21 2020
From: mrvladislavovich at gmail.com (MyRequiem)
Date: Thu, 23 Jul 2020 20:58:21 +0400
Subject: [Slackbuilds-users] Last Update
Message-ID: <20200723165821.GA23197@lenovo.myrequiem.net>

Hello slackware users.
Do I understand correctly that the last update on the slackbuilds.org
was Sun Jun 28 01:18:06 UTC 2020?

From hello at matthewgraybosch.com  Thu Jul 23 17:40:13 2020
From: hello at matthewgraybosch.com (Matthew Graybosch)
Date: Thu, 23 Jul 2020 13:40:13 -0400
Subject: [Slackbuilds-users] Last Update
In-Reply-To: <20200723165821.GA23197@lenovo.myrequiem.net>
References: <20200723165821.GA23197@lenovo.myrequiem.net>
Message-ID: <20200723134013.8d5d404d38824c8dd16f923a@matthewgraybosch.com>

On Thu, 23 Jul 2020 20:58:21 +0400
MyRequiem <mrvladislavovich at gmail.com> wrote:

> Hello slackware users.
> Do I understand correctly that the last update on the slackbuilds.org

I think there's a server migration in progress, so updates have been on
hold.

-- 
Matthew Graybosch		https://matthewgraybosch.com
#include <disclaimer.h>		gemini://starbreaker.org
	 			gemini://tanelorn.city
"Out of order?! Even in the future nothing works."

From mrvladislavovich at gmail.com  Thu Jul 23 17:52:49 2020
From: mrvladislavovich at gmail.com (MyRequiem)
Date: Thu, 23 Jul 2020 21:52:49 +0400
Subject: [Slackbuilds-users] Last Update
In-Reply-To: <20200723134013.8d5d404d38824c8dd16f923a@matthewgraybosch.com>
References: <20200723165821.GA23197@lenovo.myrequiem.net>
 <20200723134013.8d5d404d38824c8dd16f923a@matthewgraybosch.com>
Message-ID: <20200723175249.GB23197@lenovo.myrequiem.net>

Re: Matthew Graybosch 23.07.2020 <20200723134013.8d5d404d38824c8dd16f923a at matthewgraybosch.com>
>On Thu, 23 Jul 2020 20:58:21 +0400
>MyRequiem <mrvladislavovich at gmail.com> wrote:
>
>> Hello slackware users.
>> Do I understand correctly that the last update on the slackbuilds.org
>
>I think there's a server migration in progress, so updates have been on
>hold.
>
>-- 
>Matthew Graybosch		https://matthewgraybosch.com
>#include <disclaimer.h>		gemini://starbreaker.org
>	 			gemini://tanelorn.city
>"Out of order?! Even in the future nothing works."
>_______________________________________________
>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/
>

Thanks I got it:)

From willysr at slackbuilds.org  Fri Jul 24 00:34:59 2020
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 24 Jul 2020 07:34:59 +0700
Subject: [Slackbuilds-users] wxPython3 invalid md5sum
In-Reply-To: <CALrQ46ALqd7QN8P+f96OkZ1Jxq8aXSKaTYiXVLvCCntQ5FBEFA@mail.gmail.com>
References: <CALrQ46ALqd7QN8P+f96OkZ1Jxq8aXSKaTYiXVLvCCntQ5FBEFA@mail.gmail.com>
Message-ID: <026c2314-8014-f938-0e5b-d4b67463abc0@slackbuilds.org>

> Processing wxPython3
> 
> wxPython3:
> wxPython3 not found in /var/cache/sbopkg.
> --2020-07-23 10:39:56--
> https://sourceforge.net/projects/wxpython/files/wxPython/3.0.2.0/wxPython-src-3.0.2.0.tar.bz2
> Resolving sourceforge.net (sourceforge.net)... 99.84.191.125,
> 99.84.191.126, 99.84.191.36, ...
> Connecting to sourceforge.net (sourceforge.net)|99.84.191.125|:443...
> connected.
> HTTP request sent, awaiting response... 302 Moved Temporarily
> Location:
> https://sourceforge.net/#!/projects/wxpython/files/wxPython/3.0.2.0/wxPython-src-3.0.2.0.tar.bz2
> [following]
> --2020-07-23 10:39:57--  https://sourceforge.net/
> Reusing existing connection to sourceforge.net:443.
> HTTP request sent, awaiting response... 200 OK
> Length: 746 [text/html]
> Saving to: ?wxPython-src-3.0.2.0.tar.bz2?
> 
> wxPython-src-3.0.2. 100%[===================>]     746  --.-KB/s    in 0s

It seems some mirrors close to your location are outdated and didn't get
updated, since i tried to download it from here and it pointed me to
https://tenet.dl.sourceforge.net/project/wxpython/wxPython/3.0.2.0/wxPython-src-3.0.2.0.tar.bz2
and it's working fine.


-- 
Willy Sudiarto Raharjo

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

From fernando.lopezjr at gmail.com  Fri Jul 24 01:26:47 2020
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Thu, 23 Jul 2020 19:26:47 -0600
Subject: [Slackbuilds-users] wxPython3 invalid md5sum
In-Reply-To: <026c2314-8014-f938-0e5b-d4b67463abc0@slackbuilds.org>
References: <CALrQ46ALqd7QN8P+f96OkZ1Jxq8aXSKaTYiXVLvCCntQ5FBEFA@mail.gmail.com>
 <026c2314-8014-f938-0e5b-d4b67463abc0@slackbuilds.org>
Message-ID: <CALrQ46AxuNxxc+Mxz1Wve=dryj+zMisULycnFBuwUigywZUe4A@mail.gmail.com>

thanks :)

On Thu, Jul 23, 2020 at 6:35 PM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > Processing wxPython3
> >
> > wxPython3:
> > wxPython3 not found in /var/cache/sbopkg.
> > --2020-07-23 10:39:56--
> >
> https://sourceforge.net/projects/wxpython/files/wxPython/3.0.2.0/wxPython-src-3.0.2.0.tar.bz2
> > Resolving sourceforge.net (sourceforge.net)... 99.84.191.125,
> > 99.84.191.126, 99.84.191.36, ...
> > Connecting to sourceforge.net (sourceforge.net)|99.84.191.125|:443...
> > connected.
> > HTTP request sent, awaiting response... 302 Moved Temporarily
> > Location:
> >
> https://sourceforge.net/#!/projects/wxpython/files/wxPython/3.0.2.0/wxPython-src-3.0.2.0.tar.bz2
> > [following]
> > --2020-07-23 10:39:57--  https://sourceforge.net/
> > Reusing existing connection to sourceforge.net:443.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 746 [text/html]
> > Saving to: ?wxPython-src-3.0.2.0.tar.bz2?
> >
> > wxPython-src-3.0.2. 100%[===================>]     746  --.-KB/s    in 0s
>
> It seems some mirrors close to your location are outdated and didn't get
> updated, since i tried to download it from here and it pointed me to
>
> https://tenet.dl.sourceforge.net/project/wxpython/wxPython/3.0.2.0/wxPython-src-3.0.2.0.tar.bz2
> and it's working fine.
>
>
> --
> Willy Sudiarto Raharjo
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>

-- 

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

From ricardo at palmtx.com.ar  Fri Jul 24 02:14:18 2020
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Thu, 23 Jul 2020 23:14:18 -0300
Subject: [Slackbuilds-users] wxPython3 invalid md5sum
In-Reply-To: <026c2314-8014-f938-0e5b-d4b67463abc0@slackbuilds.org>
References: <CALrQ46ALqd7QN8P+f96OkZ1Jxq8aXSKaTYiXVLvCCntQ5FBEFA@mail.gmail.com>
 <026c2314-8014-f938-0e5b-d4b67463abc0@slackbuilds.org>
Message-ID: <202007232314.19002.ricardo@palmtx.com.ar>

El Jueves 23/07/2020 a las 21:34, Willy Sudiarto Raharjo escribi?:
> > Processing wxPython3
> >
> > wxPython3:
> > wxPython3 not found in /var/cache/sbopkg.
> > --2020-07-23 10:39:56--
> > https://sourceforge.net/projects/wxpython/files/wxPython/3.0.2.0/wxPython
> >-src-3.0.2.0.tar.bz2 Resolving sourceforge.net (sourceforge.net)...
> > 99.84.191.125,
> > 99.84.191.126, 99.84.191.36, ...
> > Connecting to sourceforge.net (sourceforge.net)|99.84.191.125|:443...
> > connected.
> > HTTP request sent, awaiting response... 302 Moved Temporarily
> > Location:
> > https://sourceforge.net/#!/projects/wxpython/files/wxPython/3.0.2.0/wxPyt
> >hon-src-3.0.2.0.tar.bz2 [following]
> > --2020-07-23 10:39:57--  https://sourceforge.net/
> > Reusing existing connection to sourceforge.net:443.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 746 [text/html]
> > Saving to: ?wxPython-src-3.0.2.0.tar.bz2?
> >
> > wxPython-src-3.0.2. 100%[===================>]     746  --.-KB/s    in 0s
>
> It seems some mirrors close to your location are outdated and didn't get
> updated, since i tried to download it from here and it pointed me to
> https://tenet.dl.sourceforge.net/project/wxpython/wxPython/3.0.2.0/wxPython
>-src-3.0.2.0.tar.bz2 and it's working fine.

Also, notice this line, you seem to be downloading a small html file instead 
of a tar.bz2:

> Length: 746 [text/html]

-- 
Ricardo J. Barberis
Usuario Linux N? 250625: http://counter.li.org/
Usuario LFS N? 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com

From fernando.lopezjr at gmail.com  Fri Jul 24 02:28:15 2020
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Thu, 23 Jul 2020 20:28:15 -0600
Subject: [Slackbuilds-users] wxPython3 invalid md5sum
In-Reply-To: <202007232314.19002.ricardo@palmtx.com.ar>
References: <CALrQ46ALqd7QN8P+f96OkZ1Jxq8aXSKaTYiXVLvCCntQ5FBEFA@mail.gmail.com>
 <026c2314-8014-f938-0e5b-d4b67463abc0@slackbuilds.org>
 <202007232314.19002.ricardo@palmtx.com.ar>
Message-ID: <CALrQ46Bag7sfVHrUVXTHo9Cnoa5sjBEQu=DnkZPEujdMumtcOw@mail.gmail.com>

yeah, probably the 404 response...

On Thu, Jul 23, 2020 at 8:14 PM Ricardo J. Barberis <ricardo at palmtx.com.ar>
wrote:

> El Jueves 23/07/2020 a las 21:34, Willy Sudiarto Raharjo escribi?:
> > > Processing wxPython3
> > >
> > > wxPython3:
> > > wxPython3 not found in /var/cache/sbopkg.
> > > --2020-07-23 10:39:56--
> > >
> https://sourceforge.net/projects/wxpython/files/wxPython/3.0.2.0/wxPython
> > >-src-3.0.2.0.tar.bz2 Resolving sourceforge.net (sourceforge.net)...
> > > 99.84.191.125,
> > > 99.84.191.126, 99.84.191.36, ...
> > > Connecting to sourceforge.net (sourceforge.net)|99.84.191.125|:443...
> > > connected.
> > > HTTP request sent, awaiting response... 302 Moved Temporarily
> > > Location:
> > >
> https://sourceforge.net/#!/projects/wxpython/files/wxPython/3.0.2.0/wxPyt
> > >hon-src-3.0.2.0.tar.bz2 [following]
> > > --2020-07-23 10:39:57--  https://sourceforge.net/
> > > Reusing existing connection to sourceforge.net:443.
> > > HTTP request sent, awaiting response... 200 OK
> > > Length: 746 [text/html]
> > > Saving to: ?wxPython-src-3.0.2.0.tar.bz2?
> > >
> > > wxPython-src-3.0.2. 100%[===================>]     746  --.-KB/s    in
> 0s
> >
> > It seems some mirrors close to your location are outdated and didn't get
> > updated, since i tried to download it from here and it pointed me to
> >
> https://tenet.dl.sourceforge.net/project/wxpython/wxPython/3.0.2.0/wxPython
> >-src-3.0.2.0.tar.bz2 and it's working fine.
>
> Also, notice this line, you seem to be downloading a small html file
> instead
> of a tar.bz2:
>
> > Length: 746 [text/html]
>
> --
> Ricardo J. Barberis
> Usuario Linux N? 250625: http://counter.li.org/
> Usuario LFS N? 5121: http://www.linuxfromscratch.org/
> Senior SysAdmin / IT Architect - www.DonWeb.com
> _______________________________________________
> 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/20200723/bac43d77/attachment.htm>

From yalhcru at gmail.com  Fri Jul 24 06:18:56 2020
From: yalhcru at gmail.com (B Watson)
Date: Fri, 24 Jul 2020 02:18:56 -0400
Subject: [Slackbuilds-users] wxPython3 invalid md5sum
In-Reply-To: <CALrQ46ALqd7QN8P+f96OkZ1Jxq8aXSKaTYiXVLvCCntQ5FBEFA@mail.gmail.com>
References: <CALrQ46ALqd7QN8P+f96OkZ1Jxq8aXSKaTYiXVLvCCntQ5FBEFA@mail.gmail.com>
Message-ID: <CAN1hMuDnJ6qXijaBKiO9MhmFaSDr275CLQjQ+4bR1rykGGRvTw@mail.gmail.com>

On 7/23/20, Fernando Lopez <fernando.lopezjr at gmail.com> wrote:

> Length: 746 [text/html]

Do you by chance have /etc/wgetrc or ~/.wgetrc setting the user-agent
to Firefox (or Chrome, IE, etc)? Sourceforge downloads try to be
clever and redirect to an ad-laden download page if the user-agent
looks like a browser and there's no HTTP Referer.

If that's the case, you can fix it by getting rid of the wgetrc or
adding "--user-agent wget" to the wget command.

From jeff+SBo at sh0.xyz  Fri Jul 24 21:06:10 2020
From: jeff+SBo at sh0.xyz (Jeff Parent)
Date: Fri, 24 Jul 2020 16:06:10 -0500
Subject: [Slackbuilds-users] Is development/racket still abandoned?
Message-ID: <35ca10a67367d72a785b752814848c46@sh0.xyz>



I saw the last discussion was in 2018. I tried contacting Markus with no 
response. If racket is still abandoned I have updated my local copy to 
7.7 (up from 6.4) and will submit once they are open again.

Jeff

From lists at osh.id.au  Fri Jul 24 21:44:34 2020
From: lists at osh.id.au (David O'Shaughnessy)
Date: Fri, 24 Jul 2020 14:44:34 -0700
Subject: [Slackbuilds-users] JabRef 5.0 SlackBuild
Message-ID: <4af63987-bb3e-4b19-be5e-4783f1d539fc@www.fastmail.com>

SlackBuild for JabRef 5.0 attached, for those interested. The new version does away with jdk dep (they now bundle in their own jre).

--
Dave
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jabref-5.0.tar
Type: application/x-tar
Size: 10240 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200724/fb4a4827/attachment-0001.tar>

From pacho.torres.reyes at gmail.com  Sun Jul 26 10:12:22 2020
From: pacho.torres.reyes at gmail.com (Pacho t)
Date: Sun, 26 Jul 2020 05:12:22 -0500
Subject: [Slackbuilds-users] Fwd: Slackware Slackbuilds tvheadend ver
 3.4patch1 Compilation error.
In-Reply-To: <CAEdZ0ADhAW_S-qxdoAbQ8TnBD=1FDO2UonENGHU1ZLnQ=56DcA@mail.gmail.com>
References: <CAEdZ0ADhAW_S-qxdoAbQ8TnBD=1FDO2UonENGHU1ZLnQ=56DcA@mail.gmail.com>
Message-ID: <CAEdZ0ADJO+J4eh8ZGuagi3sMbPYt6DJdzDGZVYMZUJAqZE0W=A@mail.gmail.com>

Thanks in advance for reviewing this.

---------- Forwarded message ---------
From: Pacho t <pacho.torres.reyes at gmail.com>
Date: Sun, Jul 26, 2020 at 5:09 AM
Subject: Slackware Slackbuilds tvheadend ver 3.4patch1 Compilation error.
To: <w_calandrini at hotmail.com>


Hi William.

I was trying to install this tvheadend on my box.

I got this compilation error:

-----
Tvheadend Data Directory:
  /usr/share/tvheadend

CC              build.linux/src/main.o
/tmp/SBo/tvheadend-3.4patch1/src/main.c: In function ?tvhlogv?:
/tmp/SBo/tvheadend-3.4patch1/src/main.c:805:38: error: ?%s? directive
output may be truncated writing up to 2047 bytes into a region of size
between 1984 and 2047 [-Werror=format-truncation=]
  805 |     snprintf(buf2, sizeof(buf2), "%s %s", t, buf);
      |                                      ^~      ~~~
/tmp/SBo/tvheadend-3.4patch1/src/main.c:805:5: note: ?snprintf? output
between 2 and 2112 bytes into a destination of size 2048
  805 |     snprintf(buf2, sizeof(buf2), "%s %s", t, buf);
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make: *** [Makefile:255: build.linux/src/main.o] Error 1
----

Seems to be a warning treated as error. I was including:  -Wno-error
directive to avoid this in SLKCFLAGS in tvheadend.SlackBuild and other
possible places with no sucess.

I do not have experience in compiling C source code. Please review this and
let me know If I can do something from my side.

Thanks in advance for your help.

Francisco.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200726/3fcbb639/attachment.htm>

From dave at slackbuilds.org  Sun Jul 26 15:55:31 2020
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 26 Jul 2020 16:55:31 +0100
Subject: [Slackbuilds-users] Fwd: Slackware Slackbuilds tvheadend ver
 3.4patch1 Compilation error.
In-Reply-To: <CAEdZ0ADJO+J4eh8ZGuagi3sMbPYt6DJdzDGZVYMZUJAqZE0W=A@mail.gmail.com>
References: <CAEdZ0ADhAW_S-qxdoAbQ8TnBD=1FDO2UonENGHU1ZLnQ=56DcA@mail.gmail.com>
 <CAEdZ0ADJO+J4eh8ZGuagi3sMbPYt6DJdzDGZVYMZUJAqZE0W=A@mail.gmail.com>
Message-ID: <20200726155531.GA1819@blackswan.r0t.uk>

On 26/07/20 05:12,
Pacho t <pacho.torres.reyes at gmail.com> put forth the proposition:
> Thanks in advance for reviewing this.
> ---------- Forwarded message ---------
> From: Pacho t <pacho.torres.reyes at gmail.com>
> Date: Sun, Jul 26, 2020 at 5:09 AM
> Subject: Slackware Slackbuilds tvheadend ver 3.4patch1 Compilation error.
> To: <w_calandrini at hotmail.com>
> Hi William.
> I was trying to install this tvheadend on my box.
> I got this compilation error:
> -----
> Tvheadend Data Directory:
>   /usr/share/tvheadend
> CC              build.linux/src/main.o
> /tmp/SBo/tvheadend-3.4patch1/src/main.c: In function ?tvhlogv?:
> /tmp/SBo/tvheadend-3.4patch1/src/main.c:805:38: error: ?%s? directive
> output may be truncated writing up to 2047 bytes into a region of size
> between 1984 and 2047 [-Werror=format-truncation=]
>   805 |     snprintf(buf2, sizeof(buf2), "%s %s", t, buf);
>       |                                      ^~      ~~~
> /tmp/SBo/tvheadend-3.4patch1/src/main.c:805:5: note: ?snprintf? output
> between 2 and 2112 bytes into a destination of size 2048
>   805 |     snprintf(buf2, sizeof(buf2), "%s %s", t, buf);
>       |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
> make: *** [Makefile:255: build.linux/src/main.o] Error 1
> ----
> Seems to be a warning treated as error. I was including:  -Wno-error
> directive to avoid this in SLKCFLAGS in tvheadend.SlackBuild and other
> possible places with no sucess.
> I do not have experience in compiling C source code. Please review this and
> let me know If I can do something from my side.
> Thanks in advance for your help.
> Francisco.

Hi,

I cannot replicate this.  It builds OK for me in a clean 14.2 chroot,
with or without the optional deps.

Can you get hold of a full build log plus some info on his OS?

--
Dave
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200726/1c1d8bf2/attachment.asc>

From dave at slackbuilds.org  Sun Jul 26 16:27:05 2020
From: dave at slackbuilds.org (Dave Woodfall)
Date: Sun, 26 Jul 2020 17:27:05 +0100
Subject: [Slackbuilds-users] Fwd: Slackware Slackbuilds tvheadend ver
 3.4patch1 Compilation error.
In-Reply-To: <20200726155531.GA1819@blackswan.r0t.uk>
References: <CAEdZ0ADhAW_S-qxdoAbQ8TnBD=1FDO2UonENGHU1ZLnQ=56DcA@mail.gmail.com>
 <CAEdZ0ADJO+J4eh8ZGuagi3sMbPYt6DJdzDGZVYMZUJAqZE0W=A@mail.gmail.com>
 <20200726155531.GA1819@blackswan.r0t.uk>
Message-ID: <20200726162705.GB1819@blackswan.r0t.uk>

On 26/07/20 16:55,
Dave Woodfall <dave at slackbuilds.org> put forth the proposition:
> On 26/07/20 05:12,
> Pacho t <pacho.torres.reyes at gmail.com> put forth the proposition:
> > Thanks in advance for reviewing this.
> > ---------- Forwarded message ---------
> > From: Pacho t <pacho.torres.reyes at gmail.com>
> > Date: Sun, Jul 26, 2020 at 5:09 AM
> > Subject: Slackware Slackbuilds tvheadend ver 3.4patch1 Compilation error.
> > To: <w_calandrini at hotmail.com>
> > Hi William.
> > I was trying to install this tvheadend on my box.
> > I got this compilation error:
> > -----
> > Tvheadend Data Directory:
> >   /usr/share/tvheadend
> > CC              build.linux/src/main.o
> > /tmp/SBo/tvheadend-3.4patch1/src/main.c: In function ?tvhlogv?:
> > /tmp/SBo/tvheadend-3.4patch1/src/main.c:805:38: error: ?%s? directive
> > output may be truncated writing up to 2047 bytes into a region of size
> > between 1984 and 2047 [-Werror=format-truncation=]
> >   805 |     snprintf(buf2, sizeof(buf2), "%s %s", t, buf);
> >       |                                      ^~      ~~~
> > /tmp/SBo/tvheadend-3.4patch1/src/main.c:805:5: note: ?snprintf? output
> > between 2 and 2112 bytes into a destination of size 2048
> >   805 |     snprintf(buf2, sizeof(buf2), "%s %s", t, buf);
> >       |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > cc1: all warnings being treated as errors
> > make: *** [Makefile:255: build.linux/src/main.o] Error 1
> > ----
> > Seems to be a warning treated as error. I was including:  -Wno-error
> > directive to avoid this in SLKCFLAGS in tvheadend.SlackBuild and other
> > possible places with no sucess.
> > I do not have experience in compiling C source code. Please review this and
> > let me know If I can do something from my side.
> > Thanks in advance for your help.
> > Francisco.
> Hi,
> I cannot replicate this.  It builds OK for me in a clean 14.2 chroot,
> with or without the optional deps.
> Can you get hold of a full build log plus some info on his OS?
> --
> Dave

I should add that I used the following for deps:

libav=>ffmpeg
dvbcsa=>libdvbcsa

I couldn't find an equivalent for bundle.

It also needs a working network connection to build, which would be
nice to fix.  The last update was back in 2018, and I didn't check to
see if there was a newer release available.

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

From w_calandrini at hotmail.com  Mon Jul 27 19:41:50 2020
From: w_calandrini at hotmail.com (William PC)
Date: Mon, 27 Jul 2020 19:41:50 +0000
Subject: [Slackbuilds-users] Fwd: Slackware Slackbuilds tvheadend ver
 3.4patch1 Compilation error.
In-Reply-To: <CAEdZ0ADJO+J4eh8ZGuagi3sMbPYt6DJdzDGZVYMZUJAqZE0W=A@mail.gmail.com>
References: <CAEdZ0ADhAW_S-qxdoAbQ8TnBD=1FDO2UonENGHU1ZLnQ=56DcA@mail.gmail.com>,
 <CAEdZ0ADJO+J4eh8ZGuagi3sMbPYt6DJdzDGZVYMZUJAqZE0W=A@mail.gmail.com>
Message-ID: <AM6PR03MB5557524BE5A96420957EC79DFE720@AM6PR03MB5557.eurprd03.prod.outlook.com>

Hi,

I installed it some two months ago without compiling problems. The only issue that I knew is the configurating files for new installations.
Can you tell me the Slackware version including architecture that you are using ?

Regards,

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: Pacho t<mailto:pacho.torres.reyes at gmail.com>
Sent: Sunday, July 26, 2020 5:47 AM
To: slackbuilds-users at slackbuilds.org<mailto:slackbuilds-users at slackbuilds.org>
Subject: [Slackbuilds-users] Fwd: Slackware Slackbuilds tvheadend ver 3.4patch1 Compilation error.

Thanks in advance for reviewing this.

---------- Forwarded message ---------
From: Pacho t <pacho.torres.reyes at gmail.com<mailto:pacho.torres.reyes at gmail.com>>
Date: Sun, Jul 26, 2020 at 5:09 AM
Subject: Slackware Slackbuilds tvheadend ver 3.4patch1 Compilation error.
To: <w_calandrini at hotmail.com<mailto:w_calandrini at hotmail.com>>

Hi William.

I was trying to install this tvheadend on my box.

I got this compilation error:

-----
Tvheadend Data Directory:
  /usr/share/tvheadend

CC              build.linux/src/main.o
/tmp/SBo/tvheadend-3.4patch1/src/main.c: In function ?tvhlogv?:
/tmp/SBo/tvheadend-3.4patch1/src/main.c:805:38: error: ?%s? directive output may be truncated writing up to 2047 bytes into a region of size between 1984 and 2047 [-Werror=format-truncation=]
  805 |     snprintf(buf2, sizeof(buf2), "%s %s", t, buf);
      |                                      ^~      ~~~
/tmp/SBo/tvheadend-3.4patch1/src/main.c:805:5: note: ?snprintf? output between 2 and 2112 bytes into a destination of size 2048
  805 |     snprintf(buf2, sizeof(buf2), "%s %s", t, buf);
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make: *** [Makefile:255: build.linux/src/main.o] Error 1
----

Seems to be a warning treated as error. I was including:  -Wno-error  directive to avoid this in SLKCFLAGS in tvheadend.SlackBuild and other possible places with no sucess.

I do not have experience in compiling C source code. Please review this and let me know If I can do something from my side.

Thanks in advance for your help.

Francisco.



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

From richard at aaazen.com  Fri Jul 31 19:44:55 2020
From: richard at aaazen.com (Richard Narron)
Date: Fri, 31 Jul 2020 12:44:55 -0700 (PDT)
Subject: [Slackbuilds-users] audio/mpd 0.21.22 does not build on Slackware
 14.2
Message-ID: <alpine.LNX.2.20.2007311227510.10263@thursday.test>


The latest version of audio/mpd 0.21.22 does not actually build on
Slackware 14.2

The build stops soon with this error:

  mpd.SlackBuild: line 81: meson: command not found

meson and ninja are included in Slackware current but not on 14.2

From rshepard at appl-ecosys.com  Fri Jul 31 20:03:44 2020
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Fri, 31 Jul 2020 13:03:44 -0700 (PDT)
Subject: [Slackbuilds-users] audio/mpd 0.21.22 does not build on
 Slackware 14.2
In-Reply-To: <alpine.LNX.2.20.2007311227510.10263@thursday.test>
References: <alpine.LNX.2.20.2007311227510.10263@thursday.test>
Message-ID: <alpine.LNX.2.20.2007311302520.2030@salmo.appl-ecosys.com>

On Fri, 31 Jul 2020, Richard Narron wrote:

> The latest version of audio/mpd 0.21.22 does not actually build on
> Slackware 14.2
>
> The build stops soon with this error:
>  mpd.SlackBuild: line 81: meson: command not found
> meson and ninja are included in Slackware current but not on 14.2

Richard,

Both can be installed from SBo:

$ ls /var/log/packages/ | grep meson
meson-0.52.1-x86_64-1_SBo
$ ls /var/log/packages/ | grep ninja
ninja-1.10.0-x86_64-1_SBo

Carpe weekend,

Rich


From didier at slint.fr  Fri Jul 31 20:22:52 2020
From: didier at slint.fr (Didier Spaier)
Date: Fri, 31 Jul 2020 22:22:52 +0200
Subject: [Slackbuilds-users] audio/mpd 0.21.22 does not build on
 Slackware 14.2
In-Reply-To: <alpine.LNX.2.20.2007311302520.2030@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.2007311227510.10263@thursday.test>
 <alpine.LNX.2.20.2007311302520.2030@salmo.appl-ecosys.com>
Message-ID: <80d1fbba-f147-398a-4cc5-c8f38e93564b@slint.fr>

Le 31/07/2020 ? 22:03, Rich Shepard a ?crit?:
> On Fri, 31 Jul 2020, Richard Narron wrote:
> 
>> The latest version of audio/mpd 0.21.22 does not actually build on
>> Slackware 14.2
>>
>> The build stops soon with this error:
>> ?mpd.SlackBuild: line 81: meson: command not found
>> meson and ninja are included in Slackware current but not on 14.2
> 
> Richard,
> 
> Both can be installed from SBo:

Yes, but these build dependencies are not
mentionned in the README and in the .info

Didier