From skaendo at excite.com  Mon Jan  1 04:58:37 2018
From: skaendo at excite.com (Ed Ender)
Date: Sun, 31 Dec 2017 23:58:37 -0500
Subject: [Slackbuilds-users] A couple of requests to add to the
 Christmas wish list...
Message-ID: <20171231235837.8312@web006.roc2.bluetie.com>

Hi David, (and everyone else)

> or if you don't want to see the category
> tail -n +2 ChangeLog.txt | awk '/+--------------------------+/ {exit}
> {print substr($0,index($0,"/")+1)   }' | sort

Excellent, thanks!

> There are so many ways of getting part or all of the repo -- git,
> rsync, mirrors -- it's generally considered impossible to collect
> meaningful statistics.

I understand that because sometimes I download them from SBo for convenience and I also have a local mirror that I keep updated and use. I just thought it would be useful even if it was just for the times it has been downloaded from SBo. That way a maintainer can have at least a idea of the SlackBuilds "popularity".

Thanks again,
Ed

From dave at dawoodfall.net  Tue Jan  2 19:40:50 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Tue, 2 Jan 2018 19:40:50 +0000
Subject: [Slackbuilds-users] w3m
Message-ID: <20180102194050.GK5554@Blackswan>

I've tried to email Grigorios about this but got 'Recipient address
rejected. Not known' error back.

I'm hoping that he's watching the list.

I've noticed that w3m make install doesn't install w3mimgdisplay. This
is needed by ranger to display images in the terminal. I managed to fix
it by:

make install DESTDIR=$PKG
cp w3mimgdisplay $PKG/usr/bin

Also, if you change the termlib line to:

--with-termlib="terminfo ncurses" \

It will allow w3mimgdisplay to work in gnu-screen (if tic is used to
install the screen terminfo file).

Could you please add those options? Then I will update my ranger
slackbuild with some information on how to get images working in the
terminal.

Cheers

From arkadiusz at drabczyk.org  Tue Jan  2 19:53:08 2018
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Tue, 2 Jan 2018 20:53:08 +0100
Subject: [Slackbuilds-users] w3m
In-Reply-To: <20180102194050.GK5554@Blackswan>
References: <20180102194050.GK5554@Blackswan>
Message-ID: <20180102195308.GC8016@comp.lan>

On Tue, Jan 02, 2018 at 07:40:50PM +0000, David Woodfall wrote:
> I've tried to email Grigorios about this but got 'Recipient address
> rejected. Not known' error back.
> 
> I'm hoping that he's watching the list.
> 
> I've noticed that w3m make install doesn't install w3mimgdisplay. This
> is needed by ranger to display images in the terminal. I managed to fix
> it by:
> 
> make install DESTDIR=$PKG
> cp w3mimgdisplay $PKG/usr/bin
> 
> Also, if you change the termlib line to:
> 
> --with-termlib="terminfo ncurses" \
> 
> It will allow w3mimgdisplay to work in gnu-screen (if tic is used to
> install the screen terminfo file).
> 
> Could you please add those options? Then I will update my ranger
> slackbuild with some information on how to get images working in the
> terminal.

Are you sure w3mimgdisplay is not installed?  I think it is:

$ locate w3mimgdisplay
/usr/libexec/w3m/w3mimgdisplay
$ grep w3mimgdisplay /var/log/packages/*
/var/log/packages/w3m-0.5.3-x86_64-3_SBo:usr/libexec/w3m/w3mimgdisplay

I have not problems with displaying pdf documents as images in ranger.
I found this in
/usr/lib64/python2.7/site-packages/ranger/ext/img_display.py:

W3MIMGDISPLAY_PATHS = [
    '/usr/lib/w3m/w3mimgdisplay',
    '/usr/libexec/w3m/w3mimgdisplay',
    '/usr/lib64/w3m/w3mimgdisplay',
    '/usr/libexec64/w3m/w3mimgdisplay',
]

That would indicate that ranger does not really expect w3mimgdisplay
to be in $PATH.
-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From arkadiusz at drabczyk.org  Tue Jan  2 20:10:40 2018
From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk)
Date: Tue, 2 Jan 2018 21:10:40 +0100
Subject: [Slackbuilds-users] synergy is unavailable to download
In-Reply-To: <CAMt7G9RZgJFK2thi9K3LgYgLHTi3vqG-7XvVvA+XPgUUuEvLoA@mail.gmail.com>
References: <7d49aebe-6c20-c09b-2710-80337cd494d7@sdf.org>
 <20171229224619.GA18148@comp.lan>
 <CAMt7G9RZgJFK2thi9K3LgYgLHTi3vqG-7XvVvA+XPgUUuEvLoA@mail.gmail.com>
Message-ID: <20180102201040.GA22158@comp.lan>

On Sun, Dec 31, 2017 at 07:23:46PM +0000, David Spencer wrote:
> On 29 December 2017 at 22:46, Arkadiusz Drabczyk <arkadiusz at drabczyk.org> wrote:
> > On Thu, Dec 28, 2017 at 09:56:20PM -0600, Donald Cooley wrote:
> >> Hi,
> >> Synergy source files are unavailable for  download
> >
> > Indeed,
> > https://github.com/symless/synergy/archive/v1.7.6-stable.tar.gz is
> > gone.  There is
> > https://github.com/symless/synergy-core/archive/v1.7.6-stable.tar.gz
> > but it has a different checksum.  Package that has the correct
> > checksum can be found at:
> >
> > http://pkgs.fedoraproject.org/repo/pkgs/synergy/v1.7.6-stable.tar.gz/a324798a47445de739a7ed4baf12638f/v1.7.6-stable.tar.gz
> 
> Thanks Arkadiusz, fix applied.
> It's always a pleasure to leech off Fedora :)
> -D.

Coming back to this - OP also mentioned in an off-list conversation
that synergy package has not been updated for a long time.  In fact,
the last version upgrade was done in March 2016.  I used to use
synergy in one of my previous jobs and I know that controlling Windows
from Linux and vice versa is a common use case but as I don't have an
easy access to the Windows machine I'm not able to take this package
over and test it thoroughly but someone else may.
-- 
Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

From dave at dawoodfall.net  Tue Jan  2 20:52:53 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Tue, 2 Jan 2018 20:52:53 +0000
Subject: [Slackbuilds-users] w3m
In-Reply-To: <20180102195308.GC8016@comp.lan>
References: <20180102194050.GK5554@Blackswan> <20180102195308.GC8016@comp.lan>
Message-ID: <20180102205253.GL5554@Blackswan>

>On Tue, Jan 02, 2018 at 07:40:50PM +0000, David Woodfall wrote:
>> I've tried to email Grigorios about this but got 'Recipient address
>> rejected. Not known' error back.
>>
>> I'm hoping that he's watching the list.
>>
>> I've noticed that w3m make install doesn't install w3mimgdisplay. This
>> is needed by ranger to display images in the terminal. I managed to fix
>> it by:
>>
>> make install DESTDIR=$PKG
>> cp w3mimgdisplay $PKG/usr/bin
>>
>> Also, if you change the termlib line to:
>>
>> --with-termlib="terminfo ncurses" \
>>
>> It will allow w3mimgdisplay to work in gnu-screen (if tic is used to
>> install the screen terminfo file).
>>
>> Could you please add those options? Then I will update my ranger
>> slackbuild with some information on how to get images working in the
>> terminal.
>
>Are you sure w3mimgdisplay is not installed?  I think it is:
>
>$ locate w3mimgdisplay
>/usr/libexec/w3m/w3mimgdisplay
>$ grep w3mimgdisplay /var/log/packages/*
>/var/log/packages/w3m-0.5.3-x86_64-3_SBo:usr/libexec/w3m/w3mimgdisplay
>
>I have not problems with displaying pdf documents as images in ranger.
>I found this in
>/usr/lib64/python2.7/site-packages/ranger/ext/img_display.py:
>
>W3MIMGDISPLAY_PATHS = [
>    '/usr/lib/w3m/w3mimgdisplay',
>    '/usr/libexec/w3m/w3mimgdisplay',
>    '/usr/lib64/w3m/w3mimgdisplay',
>    '/usr/libexec64/w3m/w3mimgdisplay',
>]
>
>That would indicate that ranger does not really expect w3mimgdisplay
>to be in $PATH.

Ah, you correct. Well spotted.

I'd still like --with-termlib="terminfo ncurses" to make it work in
screen if possible though.

Dave


From fellype at gmail.com  Wed Jan  3 12:15:43 2018
From: fellype at gmail.com (Fellype do Nascimento)
Date: Wed, 3 Jan 2018 10:15:43 -0200
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <121141514304815@web20j.yandex.ru>
References: <121141514304815@web20j.yandex.ru>
Message-ID: <577a6714-ea5c-776c-85cb-6da1e37d7ce8@gmail.com>

I hope it's not too late to ask, and neither difficult to implement:

8. Add to each program page at SBo the date of the last time its 
SlackBuild script was updated.

Best regards,

Fellype
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180103/671b7b85/attachment.html>

From willysr at slackbuilds.org  Wed Jan  3 13:55:53 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 3 Jan 2018 20:55:53 +0700
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <577a6714-ea5c-776c-85cb-6da1e37d7ce8@gmail.com>
References: <121141514304815@web20j.yandex.ru>
 <577a6714-ea5c-776c-85cb-6da1e37d7ce8@gmail.com>
Message-ID: <fa077b0e-f680-e811-59f9-36b67877e95f@slackbuilds.org>

> 8. Add to each program page at SBo the date of the last time its
> SlackBuild script was updated.

It's easier to see the history in cgit :)
https://git.slackbuilds.org/slackbuilds/


-- 
Willy Sudiarto Raharjo

-------------- 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/20180103/91e60a65/attachment.asc>

From slackbuilds at schoepfer.info  Wed Jan  3 16:32:15 2018
From: slackbuilds at schoepfer.info (Franzen)
Date: Wed, 03 Jan 2018 17:32:15 +0100
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <fa077b0e-f680-e811-59f9-36b67877e95f@slackbuilds.org>
References: <121141514304815@web20j.yandex.ru>
 <577a6714-ea5c-776c-85cb-6da1e37d7ce8@gmail.com>
 <fa077b0e-f680-e811-59f9-36b67877e95f@slackbuilds.org>
Message-ID: <f7c8905a0d1d9611e1005a468175cf6b@schoepfer.info>

On 2018-01-03 14:55, Willy Sudiarto Raharjo wrote:
>> 8. Add to each program page at SBo the date of the last time its
>> SlackBuild script was updated.
> 
> It's easier to see the history in cgit :)
> https://git.slackbuilds.org/slackbuilds/

IMO it's not, i'm usually not browsing cgit parallel to slackbuilds.org 
for every script.
Sure spotting the date of the last change of a slackbuild doesn't mean 
much about what exactly was updated, it might be still outdated, but it 
would be a hint to investigate further(or not).

Johannes

From andreas.guldstrand at gmail.com  Wed Jan  3 16:45:44 2018
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Wed, 3 Jan 2018 17:45:44 +0100
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <f7c8905a0d1d9611e1005a468175cf6b@schoepfer.info>
References: <121141514304815@web20j.yandex.ru>
 <577a6714-ea5c-776c-85cb-6da1e37d7ce8@gmail.com>
 <fa077b0e-f680-e811-59f9-36b67877e95f@slackbuilds.org>
 <f7c8905a0d1d9611e1005a468175cf6b@schoepfer.info>
Message-ID: <CAEQ5t82Be-nzC6bATgV=p6VN4+_Vo_FZsuWz98Wc+iFC9i8ULQ@mail.gmail.com>

On 3 January 2018 at 17:32, Franzen <slackbuilds at schoepfer.info> wrote:
> On 2018-01-03 14:55, Willy Sudiarto Raharjo wrote:
>>>
>>> 8. Add to each program page at SBo the date of the last time its
>>> SlackBuild script was updated.
>>
>>
>> It's easier to see the history in cgit :)
>> https://git.slackbuilds.org/slackbuilds/
>
>
> IMO it's not, i'm usually not browsing cgit parallel to slackbuilds.org for
> every script.
> Sure spotting the date of the last change of a slackbuild doesn't mean much
> about what exactly was updated, it might be still outdated, but it would be
> a hint to investigate further(or not).

Perhaps it might be worthwhile to have a link to the cgit page for
each package on the package page?

That way you can easily find it and you'll be able to see exactly what
changed and when.

/ Andreas

From erik at slackbuilds.org  Wed Jan  3 19:04:36 2018
From: erik at slackbuilds.org (Erik Hanson)
Date: Wed, 3 Jan 2018 13:04:36 -0600
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <121141514304815@web20j.yandex.ru>
References: <121141514304815@web20j.yandex.ru>
Message-ID: <2ecf5c45-857a-ddb5-c637-5e2a06b889d9@slackbuilds.org>

On 12/26/2017 10:13 AM, evanton at tut.by wrote:
> I would really like to have a short, one line description of each program there,

This sounds a lot easier than it will be in practice.

That information is not in the DB. ~10 years ago I tried adding it to
the listings by having PHP scrape the slack-desc on page generation.
That didn't last, because not only was it a bad way to implement it, but
it placed heavy load on the server, even back then with a much smaller
repo and far fewer visitors.

For this to happen, an admin with the free time, interest, and php/mysql
skills will have to implement it. Importing everything into the existing
DB, modifying the website and back-end tools we use to deal with the new
information.


-- 
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/20180103/f1bf88a8/attachment-0001.asc>

From erik at slackbuilds.org  Wed Jan  3 19:06:39 2018
From: erik at slackbuilds.org (Erik Hanson)
Date: Wed, 3 Jan 2018 13:06:39 -0600
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <CAEQ5t82Be-nzC6bATgV=p6VN4+_Vo_FZsuWz98Wc+iFC9i8ULQ@mail.gmail.com>
References: <121141514304815@web20j.yandex.ru>
 <577a6714-ea5c-776c-85cb-6da1e37d7ce8@gmail.com>
 <fa077b0e-f680-e811-59f9-36b67877e95f@slackbuilds.org>
 <f7c8905a0d1d9611e1005a468175cf6b@schoepfer.info>
 <CAEQ5t82Be-nzC6bATgV=p6VN4+_Vo_FZsuWz98Wc+iFC9i8ULQ@mail.gmail.com>
Message-ID: <245ddfca-4101-40ee-be37-a0372c4d74e6@slackbuilds.org>

On 01/03/2018 10:45 AM, Andreas Guldstrand wrote:
> Perhaps it might be worthwhile to have a link to the cgit page for
> each package on the package page?
> 
> That way you can easily find it and you'll be able to see exactly what
> changed and when.

A quick glance suggests to me that this might be trivial to implement. I
will have a look soon-ish once some more important things clear my plate.


-- 
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/20180103/c7d4a10e/attachment.asc>

From erik at slackbuilds.org  Wed Jan  3 19:31:27 2018
From: erik at slackbuilds.org (Erik Hanson)
Date: Wed, 3 Jan 2018 13:31:27 -0600
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <b61aead5-9273-ed11-182a-276e42e846d5@gmail.com>
References: <CALrQ46B=MjQNYgJRCeh2bpMq=h7Zn6zHZwX63ki04y63kY0NwA@mail.gmail.com>
 <395c848c-b938-759c-f444-100c654629b1@gmail.com>
 <935c5dcf-5354-08b9-1bc9-0a2a55ad0644@slackbuilds.org>
 <b61aead5-9273-ed11-182a-276e42e846d5@gmail.com>
Message-ID: <00280cc5-7b20-3eac-869f-0ce150e7a5af@slackbuilds.org>

On 12/30/2017 12:18 PM, King Beowulf wrote:
> and refresh each FF window as needed.  I was thinking maybe a 1 row, 2
> column table (no CSS, web 1.0 is all we really need. damn kids! get off
> my lawn!) showing each list then only one link is needed for #4.

I can picture it and it doesn't seem like a terrible idea. Problem is
the data for these come from two different places. The approved list is
taken from git. The pending list is of the form-submitted files as they
exist on the file system, that information doesn't exist it git. I'm not
sure enough interest exists, or benefit gained, to combine the two.
Especially on the "has to do the work" side of things.


-- 
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/20180103/1252dd88/attachment.asc>

From yalhcru at gmail.com  Wed Jan  3 20:19:54 2018
From: yalhcru at gmail.com (B Watson)
Date: Wed, 3 Jan 2018 15:19:54 -0500
Subject: [Slackbuilds-users] Whoops...
Message-ID: <CAN1hMuAPmC3znEGY_qgQYi71N51mm5rjQNWdq3eiBLB5ZN9V+A@mail.gmail.com>

I got this mail from Luis Henrique Mello 3+ years ago and never got
around to forwarding it to the list. Basically, all his SlackBuilds are
up for grabs.

---------- Forwarded message ----------
From: Luis Henrique Mello <lmello.009 at gmail.com>
Date: Sun, 14 Sep 2014 22:35:10 -0300
Subject: Re: vamp-plugin-sdk
To: B Watson <yalhcru at gmail.com>

Hi,

My slack box simply 'died' :(

It was quite a 'long' time, I recall sending a message to the mailing
list about it before I signed out... anyway I'd would be proper to let
everybody know that *all* my contributions to slackbuilds.org are freely
available for anyone to do update and maintain them, since I cannot do
that myself anymore.

When I had my slack box working, there was something on the Submissions
Guidelines about Public Domain. I see that has changed...

Could you please forward this message?

- Luis

ps - I attached a simple 'ls' output from my slackbuilds backup folder,
the last modification was from late 2013... yep that's around the time
my old computer was still working. It could be of some use.

On Sun, 2014-09-14 at 14:40 -0400, B Watson wrote:
> Are you still maintaining vamp-plugin-sdk at SlackBuilds.org? I'm trying
> to update my sonic-visualiser build, and it needs vamp-plugin-sdk 2.5.
> The SBo repo has 2.4... upstream released 2.5 over a year ago, and
> I've built it with your SlackBuild (just by setting VERSION=2.5 in the
> environment).
>
> If you don't want to maintain the build, let me know. I'll be happy to
> take over as maintainer, since my build depends on it.
-------------- next part --------------
bakefile
bakefile.tar.gz
blassic
blassic.tar.gz
brasero
brasero-3.0.0.tar.bz2
configobj
configobj.tar.gz
dcd
dcd.tar.gz
deadbeef
deadbeef.tar.gz
dvdrip
fbida
fbida.tar.gz
feedparser
feedparser.tar.gz
gigolo
gtick
gtklp
hexedit
ht
ht.tar.gz
jeex
kde-gtk-config
kde-gtk-config.tar.gz
libunique
m64py
m64py.tar.gz
mac
mac.tar.gz
mfe
mfe.tar.gz
mktoc
mktoc.tar.gz
mygpoclient
mygpoclient.tar.gz
openmsx
openmsx-0.9.1
openmsx-catapult-0.9.1
opentyrian
oxygen-gtk3
oxygen-gtk3.tar.gz
pcsxr-svn
perl-event
perl-libintl
plotutils
plotutils.tar.gz
remmina
remmina.tar.gz
rubberband
rubberband.tar.gz
stella
stella.tar.gz
svp
svp.tar.gz
tkdvd
vamp-plugin-sdk
vamp-plugin-sdk.tar.gz
vkeybd
xmms-crossfade
xvid4conf
zgv
zgv.tar.gz

From yalhcru at gmail.com  Wed Jan  3 20:32:08 2018
From: yalhcru at gmail.com (B Watson)
Date: Wed, 3 Jan 2018 15:32:08 -0500
Subject: [Slackbuilds-users] Updated lmello list
Message-ID: <CAN1hMuCmOuR7bmY1AAJMekfTvw3rRLpheC=YR68vs_k7Rupaxw@mail.gmail.com>

Here's a current list of builds that list lmello as maintainer:

audio/dcd
audio/mac
audio/mktoc
development/bakefile
development/blassic
games/mfe
graphics/plotutils
graphics/svp
graphics/zgv
libraries/mygpoclient
multimedia/dvdrip
multimedia/vkeybd
multimedia/xmms-crossfade
multimedia/xvid4conf
perl/perl-event
perl/perl-libintl
system/gigolo
system/gtklp
system/tkdvd

I suppose these are up for grabs, except for:

libraries/mygpoclient - someone on IRC has already claimed this.
multimedia/vkeybd - I'll take this one since I use it occasionally.

From nastavs at gmail.com  Wed Jan  3 20:34:57 2018
From: nastavs at gmail.com (Shrivats)
Date: Wed, 3 Jan 2018 20:34:57 +0000
Subject: [Slackbuilds-users] Whoops...
In-Reply-To: <CAN1hMuAPmC3znEGY_qgQYi71N51mm5rjQNWdq3eiBLB5ZN9V+A@mail.gmail.com>
References: <CAN1hMuAPmC3znEGY_qgQYi71N51mm5rjQNWdq3eiBLB5ZN9V+A@mail.gmail.com>
Message-ID: <CAKgAtWAaGH8oh3eb=5iOw6j461J-rybxJPUvfxZW4GrjvYfPsQ@mail.gmail.com>

For some odd reason, repology doesn't list him as a maintainer. Have we
taken all his repos off him?

https://repology.org/maintainers/?search=Mello

In any case, it'd be a good idea to list slack builds still up for grabs.


Shrivats

On Jan 3, 2018 20:20, "B Watson" <yalhcru at gmail.com> wrote:

> I got this mail from Luis Henrique Mello 3+ years ago and never got
> around to forwarding it to the list. Basically, all his SlackBuilds are
> up for grabs.
>
> ---------- Forwarded message ----------
> From: Luis Henrique Mello <lmello.009 at gmail.com>
> Date: Sun, 14 Sep 2014 22:35:10 -0300
> Subject: Re: vamp-plugin-sdk
> To: B Watson <yalhcru at gmail.com>
>
> Hi,
>
> My slack box simply 'died' :(
>
> It was quite a 'long' time, I recall sending a message to the mailing
> list about it before I signed out... anyway I'd would be proper to let
> everybody know that *all* my contributions to slackbuilds.org are freely
> available for anyone to do update and maintain them, since I cannot do
> that myself anymore.
>
> When I had my slack box working, there was something on the Submissions
> Guidelines about Public Domain. I see that has changed...
>
> Could you please forward this message?
>
> - Luis
>
> ps - I attached a simple 'ls' output from my slackbuilds backup folder,
> the last modification was from late 2013... yep that's around the time
> my old computer was still working. It could be of some use.
>
> On Sun, 2014-09-14 at 14:40 -0400, B Watson wrote:
> > Are you still maintaining vamp-plugin-sdk at SlackBuilds.org? I'm trying
> > to update my sonic-visualiser build, and it needs vamp-plugin-sdk 2.5.
> > The SBo repo has 2.4... upstream released 2.5 over a year ago, and
> > I've built it with your SlackBuild (just by setting VERSION=2.5 in the
> > environment).
> >
> > If you don't want to maintain the build, let me know. I'll be happy to
> > take over as maintainer, since my build depends on it.
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180103/7ebea064/attachment.html>

From andreas.guldstrand at gmail.com  Wed Jan  3 20:39:45 2018
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Wed, 3 Jan 2018 21:39:45 +0100
Subject: [Slackbuilds-users] Whoops...
In-Reply-To: <CAKgAtWAaGH8oh3eb=5iOw6j461J-rybxJPUvfxZW4GrjvYfPsQ@mail.gmail.com>
References: <CAN1hMuAPmC3znEGY_qgQYi71N51mm5rjQNWdq3eiBLB5ZN9V+A@mail.gmail.com>
 <CAKgAtWAaGH8oh3eb=5iOw6j461J-rybxJPUvfxZW4GrjvYfPsQ@mail.gmail.com>
Message-ID: <CAEQ5t80wxfO2WSPnqr=EoL2Qw9-tMSJkjXsawp6KS1Hm=7wPwA@mail.gmail.com>

On 3 January 2018 at 21:34, Shrivats <nastavs at gmail.com> wrote:
> For some odd reason, repology doesn't list him as a maintainer. Have we
> taken all his repos off him?
>
> https://repology.org/maintainers/?search=Mello
>
> In any case, it'd be a good idea to list slack builds still up for grabs.
>

https://repology.org/maintainer/lmello.009%40gmail.com is the link
which shows his builds

From nastavs at gmail.com  Wed Jan  3 20:44:56 2018
From: nastavs at gmail.com (Shrivats)
Date: Wed, 3 Jan 2018 20:44:56 +0000
Subject: [Slackbuilds-users] Whoops...
In-Reply-To: <CAEQ5t80wxfO2WSPnqr=EoL2Qw9-tMSJkjXsawp6KS1Hm=7wPwA@mail.gmail.com>
References: <CAN1hMuAPmC3znEGY_qgQYi71N51mm5rjQNWdq3eiBLB5ZN9V+A@mail.gmail.com>
 <CAKgAtWAaGH8oh3eb=5iOw6j461J-rybxJPUvfxZW4GrjvYfPsQ@mail.gmail.com>
 <CAEQ5t80wxfO2WSPnqr=EoL2Qw9-tMSJkjXsawp6KS1Hm=7wPwA@mail.gmail.com>
Message-ID: <CAKgAtWAeYFsuow6jnW3TAokXjvGktudQ0uVGZAwAqcy9yK7K4w@mail.gmail.com>

Ah, thanks! Didn't think of searching by email ID...

Shrivats

On 3 January 2018 at 20:39, Andreas Guldstrand <andreas.guldstrand at gmail.com
> wrote:

> On 3 January 2018 at 21:34, Shrivats <nastavs at gmail.com> wrote:
> > For some odd reason, repology doesn't list him as a maintainer. Have we
> > taken all his repos off him?
> >
> > https://repology.org/maintainers/?search=Mello
> >
> > In any case, it'd be a good idea to list slack builds still up for grabs.
> >
>
> https://repology.org/maintainer/lmello.009%40gmail.com is the link
> which shows his builds
> _______________________________________________
> 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/20180103/3244338e/attachment.html>

From ricardo at palmtx.com.ar  Wed Jan  3 20:48:55 2018
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Wed, 3 Jan 2018 17:48:55 -0300
Subject: [Slackbuilds-users] Whoops...
In-Reply-To: <CAKgAtWAaGH8oh3eb=5iOw6j461J-rybxJPUvfxZW4GrjvYfPsQ@mail.gmail.com>
References: <CAN1hMuAPmC3znEGY_qgQYi71N51mm5rjQNWdq3eiBLB5ZN9V+A@mail.gmail.com>
 <CAKgAtWAaGH8oh3eb=5iOw6j461J-rybxJPUvfxZW4GrjvYfPsQ@mail.gmail.com>
Message-ID: <201801031748.55822.ricardo@palmtx.com.ar>

FWIW, it seems you have to search the maintainer's email address:

https://repology.org/maintainers/?search=lmello.009%40gmail.com
https://repology.org/metapackages/?maintainer=lmello.009%40gmail.com

El Mi?rcoles 03/01/2018 a las 17:34, Shrivats escribi?:
> For some odd reason, repology doesn't list him as a maintainer. Have we
> taken all his repos off him?
>
> https://repology.org/maintainers/?search=Mello
>
> In any case, it'd be a good idea to list slack builds still up for grabs.
>
>
> Shrivats
>
> On Jan 3, 2018 20:20, "B Watson" <yalhcru at gmail.com> wrote:
> > I got this mail from Luis Henrique Mello 3+ years ago and never got
> > around to forwarding it to the list. Basically, all his SlackBuilds are
> > up for grabs.
> >
> > ---------- Forwarded message ----------
> > From: Luis Henrique Mello <lmello.009 at gmail.com>
> > Date: Sun, 14 Sep 2014 22:35:10 -0300
> > Subject: Re: vamp-plugin-sdk
> > To: B Watson <yalhcru at gmail.com>
> >
> > Hi,
> >
> > My slack box simply 'died' :(
> >
> > It was quite a 'long' time, I recall sending a message to the mailing
> > list about it before I signed out... anyway I'd would be proper to let
> > everybody know that *all* my contributions to slackbuilds.org are freely
> > available for anyone to do update and maintain them, since I cannot do
> > that myself anymore.
> >
> > When I had my slack box working, there was something on the Submissions
> > Guidelines about Public Domain. I see that has changed...
> >
> > Could you please forward this message?
> >
> > - Luis
> >
> > ps - I attached a simple 'ls' output from my slackbuilds backup folder,
> > the last modification was from late 2013... yep that's around the time
> > my old computer was still working. It could be of some use.
> >
> > On Sun, 2014-09-14 at 14:40 -0400, B Watson wrote:
> > > Are you still maintaining vamp-plugin-sdk at SlackBuilds.org? I'm
> > > trying to update my sonic-visualiser build, and it needs
> > > vamp-plugin-sdk 2.5. The SBo repo has 2.4... upstream released 2.5 over
> > > a year ago, and I've built it with your SlackBuild (just by setting
> > > VERSION=2.5 in the environment).
> > >
> > > If you don't want to maintain the build, let me know. I'll be happy to
> > > take over as maintainer, since my build depends on it.
-- 
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 ricardo at palmtx.com.ar  Wed Jan  3 20:50:30 2018
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Wed, 3 Jan 2018 17:50:30 -0300
Subject: [Slackbuilds-users] Whoops...
In-Reply-To: <201801031748.55822.ricardo@palmtx.com.ar>
References: <CAN1hMuAPmC3znEGY_qgQYi71N51mm5rjQNWdq3eiBLB5ZN9V+A@mail.gmail.com>
 <CAKgAtWAaGH8oh3eb=5iOw6j461J-rybxJPUvfxZW4GrjvYfPsQ@mail.gmail.com>
 <201801031748.55822.ricardo@palmtx.com.ar>
Message-ID: <201801031750.30723.ricardo@palmtx.com.ar>

Nop, it's case sensitive :)

https://repology.org/maintainers/?search=mello

El Mi?rcoles 03/01/2018 a las 17:48, Ricardo J. Barberis escribi?:
> FWIW, it seems you have to search the maintainer's email address:
>
> https://repology.org/maintainers/?search=lmello.009%40gmail.com
> https://repology.org/metapackages/?maintainer=lmello.009%40gmail.com
>
> El Mi?rcoles 03/01/2018 a las 17:34, Shrivats escribi?:
> > For some odd reason, repology doesn't list him as a maintainer. Have we
> > taken all his repos off him?
> >
> > https://repology.org/maintainers/?search=Mello
> >
> > In any case, it'd be a good idea to list slack builds still up for grabs.
> >
> >
> > Shrivats
> >
> > On Jan 3, 2018 20:20, "B Watson" <yalhcru at gmail.com> wrote:
> > > I got this mail from Luis Henrique Mello 3+ years ago and never got
> > > around to forwarding it to the list. Basically, all his SlackBuilds are
> > > up for grabs.
> > >
> > > ---------- Forwarded message ----------
> > > From: Luis Henrique Mello <lmello.009 at gmail.com>
> > > Date: Sun, 14 Sep 2014 22:35:10 -0300
> > > Subject: Re: vamp-plugin-sdk
> > > To: B Watson <yalhcru at gmail.com>
> > >
> > > Hi,
> > >
> > > My slack box simply 'died' :(
> > >
> > > It was quite a 'long' time, I recall sending a message to the mailing
> > > list about it before I signed out... anyway I'd would be proper to let
> > > everybody know that *all* my contributions to slackbuilds.org are
> > > freely available for anyone to do update and maintain them, since I
> > > cannot do that myself anymore.
> > >
> > > When I had my slack box working, there was something on the Submissions
> > > Guidelines about Public Domain. I see that has changed...
> > >
> > > Could you please forward this message?
> > >
> > > - Luis
> > >
> > > ps - I attached a simple 'ls' output from my slackbuilds backup folder,
> > > the last modification was from late 2013... yep that's around the time
> > > my old computer was still working. It could be of some use.
> > >
> > > On Sun, 2014-09-14 at 14:40 -0400, B Watson wrote:
> > > > Are you still maintaining vamp-plugin-sdk at SlackBuilds.org? I'm
> > > > trying to update my sonic-visualiser build, and it needs
> > > > vamp-plugin-sdk 2.5. The SBo repo has 2.4... upstream released 2.5
> > > > over a year ago, and I've built it with your SlackBuild (just by
> > > > setting VERSION=2.5 in the environment).
> > > >
> > > > If you don't want to maintain the build, let me know. I'll be happy
> > > > to take over as maintainer, since my build depends on it.

-- 
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 dave at dawoodfall.net  Wed Jan  3 20:59:26 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Wed, 3 Jan 2018 20:59:26 +0000
Subject: [Slackbuilds-users] w3m
In-Reply-To: <20180102195308.GC8016@comp.lan>
References: <20180102194050.GK5554@Blackswan> <20180102195308.GC8016@comp.lan>
Message-ID: <20180103205925.GN5554@Blackswan>

>On Tue, Jan 02, 2018 at 07:40:50PM +0000, David Woodfall wrote:
>> I've tried to email Grigorios about this but got 'Recipient address
>> rejected. Not known' error back.
>>
>> I'm hoping that he's watching the list.
>>
>> I've noticed that w3m make install doesn't install w3mimgdisplay. This
>> is needed by ranger to display images in the terminal. I managed to fix
>> it by:
>>
>> make install DESTDIR=$PKG
>> cp w3mimgdisplay $PKG/usr/bin
>>
>> Also, if you change the termlib line to:
>>
>> --with-termlib="terminfo ncurses" \
>>
>> It will allow w3mimgdisplay to work in gnu-screen (if tic is used to
>> install the screen terminfo file).
>>
>> Could you please add those options? Then I will update my ranger
>> slackbuild with some information on how to get images working in the
>> terminal.
>
>Are you sure w3mimgdisplay is not installed?  I think it is:
>
>$ locate w3mimgdisplay
>/usr/libexec/w3m/w3mimgdisplay
>$ grep w3mimgdisplay /var/log/packages/*
>/var/log/packages/w3m-0.5.3-x86_64-3_SBo:usr/libexec/w3m/w3mimgdisplay
>
>I have not problems with displaying pdf documents as images in ranger.
>I found this in
>/usr/lib64/python2.7/site-packages/ranger/ext/img_display.py:
>
>W3MIMGDISPLAY_PATHS = [
>    '/usr/lib/w3m/w3mimgdisplay',
>    '/usr/libexec/w3m/w3mimgdisplay',
>    '/usr/lib64/w3m/w3mimgdisplay',
>    '/usr/libexec64/w3m/w3mimgdisplay',
>]
>
>That would indicate that ranger does not really expect w3mimgdisplay
>to be in $PATH.
>-- 
>Arkadiusz Drabczyk <arkadiusz at drabczyk.org>

After some trying out various options I found that the w3m source
maintained by debian works in termite, and probably other terminals (I
mean the display of inline images in ranger and other terminal apps).
The slackbuild source was released in 2011, whereas debian released
0.5.3-35 11 days ago.

I'd like to take this if nobody objects and bring it up-to-date. I
suppose it'd be better to wait a few more days to see if the
maintainer checks the list.

Dave

From yalhcru at gmail.com  Wed Jan  3 21:14:13 2018
From: yalhcru at gmail.com (B Watson)
Date: Wed, 3 Jan 2018 16:14:13 -0500
Subject: [Slackbuilds-users] w3m
In-Reply-To: <20180103205925.GN5554@Blackswan>
References: <20180102194050.GK5554@Blackswan> <20180102195308.GC8016@comp.lan>
 <20180103205925.GN5554@Blackswan>
Message-ID: <CAN1hMuABrC4m30Av3UJ3e8=RcOM_FN32TzADWBGt-b-c3yZvwA@mail.gmail.com>

On 1/3/18, David Woodfall <dave at dawoodfall.net> wrote:

> I'd like to take this if nobody objects and bring it up-to-date. I
> suppose it'd be better to wait a few more days to see if the
> maintainer checks the list.

I wouldn't hold my breath: according to the git log, he hasn't updated
w3m since 2011, and he hasn't updated anything at all since April 2014.

From kingbeowulf at gmail.com  Thu Jan  4 05:10:06 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Wed, 3 Jan 2018 21:10:06 -0800
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <00280cc5-7b20-3eac-869f-0ce150e7a5af@slackbuilds.org>
References: <CALrQ46B=MjQNYgJRCeh2bpMq=h7Zn6zHZwX63ki04y63kY0NwA@mail.gmail.com>
 <395c848c-b938-759c-f444-100c654629b1@gmail.com>
 <935c5dcf-5354-08b9-1bc9-0a2a55ad0644@slackbuilds.org>
 <b61aead5-9273-ed11-182a-276e42e846d5@gmail.com>
 <00280cc5-7b20-3eac-869f-0ce150e7a5af@slackbuilds.org>
Message-ID: <23e1945f-779e-665b-966a-06ee8dbea331@gmail.com>

On 01/03/2018 11:31 AM, Erik Hanson wrote:
> On 12/30/2017 12:18 PM, King Beowulf wrote:
>> and refresh each FF window as needed.  I was thinking maybe a 1 row, 2
>> column table (no CSS, web 1.0 is all we really need. damn kids! get off
>> my lawn!) showing each list then only one link is needed for #4.
> 
> I can picture it and it doesn't seem like a terrible idea. Problem is
> the data for these come from two different places. The approved list is
> taken from git. The pending list is of the form-submitted files as they
> exist on the file system, that information doesn't exist it git. I'm not
> sure enough interest exists, or benefit gained, to combine the two.
> Especially on the "has to do the work" side of things.
> 

Oh heck, after emailing erik with possible solution, I added it to the
menu on my hobby server, www.linuxgalaxy.org.  If admins are offended, I
will remove that page/link.  The html code is:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
   "http://www.w3.org/TR/html4/frameset.dtd">
<HTML>
<HEAD>
<TITLE>SBo Pending and Ready Queue</TITLE>
</HEAD>
<FRAMESET cols="50%,50%">
  <FRAME src="http://www.slackbuilds.org/pending/">
  <FRAME src="http://www.slackbuilds.org/ready/">
</FRAMESET>
</HTML>

It should be stable unless you validate to HTML 5.0

Enjoy.
Ed

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

From yalhcru at gmail.com  Thu Jan  4 06:36:42 2018
From: yalhcru at gmail.com (B Watson)
Date: Thu, 4 Jan 2018 01:36:42 -0500
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <23e1945f-779e-665b-966a-06ee8dbea331@gmail.com>
References: <CALrQ46B=MjQNYgJRCeh2bpMq=h7Zn6zHZwX63ki04y63kY0NwA@mail.gmail.com>
 <395c848c-b938-759c-f444-100c654629b1@gmail.com>
 <935c5dcf-5354-08b9-1bc9-0a2a55ad0644@slackbuilds.org>
 <b61aead5-9273-ed11-182a-276e42e846d5@gmail.com>
 <00280cc5-7b20-3eac-869f-0ce150e7a5af@slackbuilds.org>
 <23e1945f-779e-665b-966a-06ee8dbea331@gmail.com>
Message-ID: <CAN1hMuDBCknsMFvzcbxdT-nZD_6W0annB+R+k7eN+m5C5HbCmA@mail.gmail.com>

On 1/4/18, King Beowulf <kingbeowulf at gmail.com> wrote:

>   <FRAME src="http://www.slackbuilds.org/pending/">
>   <FRAME src="http://www.slackbuilds.org/ready/">

Nice & simple solution, if it stays on your site I'll be using it.

From kingbeowulf at gmail.com  Thu Jan  4 07:49:32 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Wed, 3 Jan 2018 23:49:32 -0800
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <CAN1hMuDBCknsMFvzcbxdT-nZD_6W0annB+R+k7eN+m5C5HbCmA@mail.gmail.com>
References: <CALrQ46B=MjQNYgJRCeh2bpMq=h7Zn6zHZwX63ki04y63kY0NwA@mail.gmail.com>
 <395c848c-b938-759c-f444-100c654629b1@gmail.com>
 <935c5dcf-5354-08b9-1bc9-0a2a55ad0644@slackbuilds.org>
 <b61aead5-9273-ed11-182a-276e42e846d5@gmail.com>
 <00280cc5-7b20-3eac-869f-0ce150e7a5af@slackbuilds.org>
 <23e1945f-779e-665b-966a-06ee8dbea331@gmail.com>
 <CAN1hMuDBCknsMFvzcbxdT-nZD_6W0annB+R+k7eN+m5C5HbCmA@mail.gmail.com>
Message-ID: <3a19738a-bf36-af52-e011-b1bfeb72c3a0@gmail.com>

On 01/03/2018 10:36 PM, B Watson wrote:
> On 1/4/18, King Beowulf <kingbeowulf at gmail.com> wrote:
> 
>>   <FRAME src="http://www.slackbuilds.org/pending/">
>>   <FRAME src="http://www.slackbuilds.org/ready/">
> 
> Nice & simple solution, if it stays on your site I'll be using it.

It will stay. I might rename the file to something other than
"SBO_frameset_example.html" (or not) and may fancy the site up a bit. I
own "linuxgalaxy.org" and that domain will be my linux fan site, whether
hosted on this antique HP P4 box or elsewhere. Only strict HTML 5 could
break it as that evolves and everyone switches, or if SBo refactors the
their site.

-Ed



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

From willysr at slackbuilds.org  Thu Jan  4 09:51:46 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 4 Jan 2018 16:51:46 +0700
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <CANi9qStcjOw0oU_YxnBswhBtyYJeb4p7==a1xSZSfwXOfuarRA@mail.gmail.com>
References: <CALrQ46B=MjQNYgJRCeh2bpMq=h7Zn6zHZwX63ki04y63kY0NwA@mail.gmail.com>
 <395c848c-b938-759c-f444-100c654629b1@gmail.com>
 <20171226003538.GA28126@comp.lan>
 <6f6afce8-d52f-5fe2-67d0-703950be9557@slackbuilds.org>
 <CANi9qStcjOw0oU_YxnBswhBtyYJeb4p7==a1xSZSfwXOfuarRA@mail.gmail.com>
Message-ID: <CAJ+QsaJ3CpeoU3DJHkras7hnviz=_sQ171nMSSFdp-97AO+n_g@mail.gmail.com>

> 7. Make it so the cursor defaults to the search box on the SBo homepage. So
> many times I'll type out the address (or start typing and let autocomplete
> finish it), hit enter to load the page, then start typing the program name
> only to remember I need to grab the mouse and click on the search box before
> I can type again.
>
> A quick local test on my server with your homework code shows you can just
> add autofocus="autofocus" inside the input tag for the search box.
>
> Thanks for everyone involved with SBo, both the admins and maintainers.
> Merry Christmas to all!

Hi Jeremy

I'm afraid, autofocus="autofocus" is only for HTML5, while we are
still using XHTML 1.0 Strict for the document type.
When we tried to validate on W3C, it returns some errors, so we
changed the solution, but you get the same results.


-- 
Willy Sudiarto Raharjo

From willysr at slackbuilds.org  Thu Jan  4 09:55:54 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 4 Jan 2018 16:55:54 +0700
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <CAEQ5t82Be-nzC6bATgV=p6VN4+_Vo_FZsuWz98Wc+iFC9i8ULQ@mail.gmail.com>
References: <121141514304815@web20j.yandex.ru>
 <577a6714-ea5c-776c-85cb-6da1e37d7ce8@gmail.com>
 <fa077b0e-f680-e811-59f9-36b67877e95f@slackbuilds.org>
 <f7c8905a0d1d9611e1005a468175cf6b@schoepfer.info>
 <CAEQ5t82Be-nzC6bATgV=p6VN4+_Vo_FZsuWz98Wc+iFC9i8ULQ@mail.gmail.com>
Message-ID: <CAJ+Qsa+-ep5O0Fi6NSQL5bYFLdF62Th5=2txD4KOaFZMFPoJjA@mail.gmail.com>

> Perhaps it might be worthwhile to have a link to the cgit page for
> each package on the package page?
>
> That way you can easily find it and you'll be able to see exactly what
> changed and when.

This has been implemented by Erik
However, there's a caveat: it will NOT list history belonging to old
category, due to category changes (eg. library -> python), it will
only see the log since it has been moved to python category. You can
use cgit to see the complete history though.
That's why personally i prefer not to change category once a script
has been approved.

-- 
Willy Sudiarto Raharjo

From gerardo.zamudio at linux.com  Thu Jan  4 13:17:03 2018
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Thu, 4 Jan 2018 08:17:03 -0500
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <CAJ+Qsa+-ep5O0Fi6NSQL5bYFLdF62Th5=2txD4KOaFZMFPoJjA@mail.gmail.com>
References: <121141514304815@web20j.yandex.ru>
 <577a6714-ea5c-776c-85cb-6da1e37d7ce8@gmail.com>
 <fa077b0e-f680-e811-59f9-36b67877e95f@slackbuilds.org>
 <f7c8905a0d1d9611e1005a468175cf6b@schoepfer.info>
 <CAEQ5t82Be-nzC6bATgV=p6VN4+_Vo_FZsuWz98Wc+iFC9i8ULQ@mail.gmail.com>
 <CAJ+Qsa+-ep5O0Fi6NSQL5bYFLdF62Th5=2txD4KOaFZMFPoJjA@mail.gmail.com>
Message-ID: <18edf257-bcd2-fc35-44f5-9fa1f1efcd3b@linux.com>



On 01/04/2018 04:55 AM, Willy Sudiarto Raharjo wrote:
> 
> This has been implemented by Erik
> However, there's a caveat: it will NOT list history belonging to old
> category, due to category changes (eg. library -> python), it will
> only see the log since it has been moved to python category. You can
> use cgit to see the complete history though.
> That's why personally i prefer not to change category once a script
> has been approved.
> 

Can you please add a line break before 'ChangeLog'? It kind of gets lost
with the Keywords and Maintainer information.

I actually think it would go best in the middle section. Something like:

Homepage
Source Downloads
Download SlackBuild
Git ChangeLog

Regards,

-- 
Gerardo Zamudio


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

From jebrhansen+SBo at gmail.com  Thu Jan  4 14:06:27 2018
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Thu, 04 Jan 2018 14:06:27 +0000
Subject: [Slackbuilds-users] for christmas.... i would like...
In-Reply-To: <CAJ+QsaJ3CpeoU3DJHkras7hnviz=_sQ171nMSSFdp-97AO+n_g@mail.gmail.com>
References: <CALrQ46B=MjQNYgJRCeh2bpMq=h7Zn6zHZwX63ki04y63kY0NwA@mail.gmail.com>
 <395c848c-b938-759c-f444-100c654629b1@gmail.com>
 <20171226003538.GA28126@comp.lan>
 <6f6afce8-d52f-5fe2-67d0-703950be9557@slackbuilds.org>
 <CANi9qStcjOw0oU_YxnBswhBtyYJeb4p7==a1xSZSfwXOfuarRA@mail.gmail.com>
 <CAJ+QsaJ3CpeoU3DJHkras7hnviz=_sQ171nMSSFdp-97AO+n_g@mail.gmail.com>
Message-ID: <CANi9qSsVEwtHBDTykdyYSU1KqBR5DK57iqRW+a+xAbkhzkn=VQ@mail.gmail.com>

On Thu, Jan 4, 2018, 4:51 AM Willy Sudiarto Raharjo <willysr at slackbuilds.org>
wrote:

> > 7. Make it so the cursor defaults to the search box on the SBo homepage.
> So
> > many times I'll type out the address (or start typing and let
> autocomplete
> > finish it), hit enter to load the page, then start typing the program
> name
> > only to remember I need to grab the mouse and click on the search box
> before
> > I can type again.
> >
> > A quick local test on my server with your homework code shows you can
> just
> > add autofocus="autofocus" inside the input tag for the search box.
> >
> > Thanks for everyone involved with SBo, both the admins and maintainers.
> > Merry Christmas to all!
>
> Hi Jeremy
>
> I'm afraid, autofocus="autofocus" is only for HTML5, while we are
> still using XHTML 1.0 Strict for the document type.
> When we tried to validate on W3C, it returns some errors, so we
> changed the solution, but you get the same results.
>

I didn't even think about checking validation. I haven't done web
development in quite a few years. I saw it was an HTML5 thing and so I
checked it on my server to see if it'd work, but I forgot about validating
it.

Thanks for finding an alternate.
Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180104/3208bdb2/attachment.html>

From slacker6896 at gmail.com  Fri Jan  5 15:54:35 2018
From: slacker6896 at gmail.com (Sebastien BALLET)
Date: Fri, 5 Jan 2018 16:54:35 +0100
Subject: [Slackbuilds-users] [libreoffice] The lack of symlinks loxxx
 prevent opening of documents with Xfe
Message-ID: <CAA2+phGbi6ruD2-Q7CeT6X5p6385RmJQ_GHfeTEHe6OibyAVTw@mail.gmail.com>

Hello,

Xfe file manager includes file associations to open documents supported by
libreoffice with programs named: lobase, localc, lodraw, loimpress, lomath
and lowriter.

However, the libreoffice package (the one which repackage official binary)
does not include binaries/symlinks/wrappers with those names, which force
user to create new file associations to be able to directly open documents
supported by libreoffice with Xfe.

The patch below (also in attachment) fixes this issue:

8<-------------------------------------------------------------------------------------
--- libreoffice.SlackBuild.orig    2018-01-05 16:05:48.350088453 +0100
+++ libreoffice.SlackBuild    2018-01-05 16:34:16.348164664 +0100
@@ -119,6 +119,17 @@
       rm -f $FILE
       ln -sf ../../opt/libreoffice$SRCSHORT/program/$FILE $FILE ;
   done
+
+  # The symlinks below are required to (directly) open documents
+  # supported by libreoffice with Xfe file manager.
+
+  ln -sf ../../opt/libreoffice$SRCSHORT/program/sbase    lobase
+  ln -sf ../../opt/libreoffice$SRCSHORT/program/scalc    localc
+  ln -sf ../../opt/libreoffice$SRCSHORT/program/sdraw    lodraw
+  ln -sf ../../opt/libreoffice$SRCSHORT/program/simpress loimpress
+  ln -sf ../../opt/libreoffice$SRCSHORT/program/smath    lomath
+  ln -sf ../../opt/libreoffice$SRCSHORT/program/swriter  lowriter
+
 cd -

 # Remove DejaVu and Liberation fonts - these are included in other packages
8<-------------------------------------------------------------------------------------

-- 
SeB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180105/7e7a1607/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libreoffice.SlackBuild.patch
Type: text/x-patch
Size: 855 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180105/7e7a1607/attachment.bin>

From matteo.bernardini at gmail.com  Fri Jan  5 19:00:09 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 5 Jan 2018 20:00:09 +0100
Subject: [Slackbuilds-users] libass ABI changes
Message-ID: <CAPsDuS5-ZS-AfRu5NiPTVRK7FD-bHzL3HOLbqE1DYTCRqC6ZnQ@mail.gmail.com>

Hi fellows!

I have received multiple requests to update libass to the new 0.14.0 version.

The thing is that with versions greater than 0.13.5 (the one on SBo)
the ABI changes at this might break whatever depends on libass, as a
mandatory or optional dependency: I'll wait a couple of weeks before
merging to let you check compatibility with the scripts you are
maintaining (libass.SlackBuild just needs a version bump).

the interested scripts are:
SDL_kitchensink
HandBrake
OpenPHT
QMPlay2
aegisub
bino
gst-plugins-bad
gst0-plugins-bad
kodi
mpv
mythtv
plex-home-theater
vlc

Matteo

From willysr at slackbuilds.org  Fri Jan  5 22:56:30 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 6 Jan 2018 05:56:30 +0700
Subject: [Slackbuilds-users] [libreoffice] The lack of symlinks loxxx
 prevent opening of documents with Xfe
In-Reply-To: <CAA2+phGbi6ruD2-Q7CeT6X5p6385RmJQ_GHfeTEHe6OibyAVTw@mail.gmail.com>
References: <CAA2+phGbi6ruD2-Q7CeT6X5p6385RmJQ_GHfeTEHe6OibyAVTw@mail.gmail.com>
Message-ID: <cf6f48be-5714-7a33-a767-98121e47b33e@slackbuilds.org>

> Xfe file manager includes file associations to open documents supported by
> libreoffice with programs named: lobase, localc, lodraw, loimpress, lomath
> and lowriter.
> 
> However, the libreoffice package (the one which repackage official binary)
> does not include binaries/symlinks/wrappers with those names, which force
> user to create new file associations to be able to directly open documents
> supported by libreoffice with Xfe.
> 
> The patch below (also in attachment) fixes this issue:

Thanks
i have applied it on my branch


-- 
Willy Sudiarto Raharjo

-------------- 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/20180106/264fe88c/attachment.asc>

From willysr at slackbuilds.org  Sat Jan  6 00:18:34 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 6 Jan 2018 07:18:34 +0700
Subject: [Slackbuilds-users] Updates - 20180106.1
Message-ID: <f4e66175-8ba2-aaf2-80c3-3f1f681d0f3a@slackbuilds.org>

Welcome to 2018!!

Our first batch of update this year consist of 199 commits

We added more python3 support on some scripts which should ease the
transition to next stable release, some fixes with meson 0.44, added
vala as hard dep on libgusb, google-go-lang updated into 1.9.x,
darktable to 2.4.0, R to 3.4.3, rust to 1.23.0, and finally we pushed
the teamviewer to version 13. This new teamviewer is now a native
package, so no multilib is required, but it comes with a new hard dep,
qt5-webkit.

Thanks to all maintainers for the hard work!!

Happy weekend


Sat Jan  6 00:00:01 UTC 2018
academic/R: Updated for version 3.4.3.
academic/units: Updated for version 2.16.
audio/drumkv1: Updated for version 0.8.6.
audio/samplv1: Updated for version 0.8.6.
audio/sayonara-player: Updated for version 1.0.0.
audio/synthv1: Updated for version 0.8.6.
desktop/awesome-appmenu: Updated for version 0.4.
desktop/gtkhash: Updated for version 1.1.1.
desktop/qtpass: Updated for version 1.2.1.
desktop/tint2: Updated for version 16.1.
desktop/zenity: Updated for version 3.26.0.
development/VisUAL: Added (visual ARM emulator).
development/asl: Updated for version 142_bld123.
development/bmake: Fix for exported TAG variable.
development/cc65: Updated for version 2.16_20180102.
development/composer: Updated for version 1.5.6
development/d-tools: Updated for version 2.078.0
development/diffoscope: Updated for version 90.
development/dmd: Updated for version 2.078.0
development/eclim: Updated for version 2.7.1.
development/eclipse-cpp: Updated for version 4.7.2.
development/eclipse-java: Updated for version 4.7.2.
development/eclipse-jee: Updated for version 4.7.2.
development/eovim: Added (Neovim client).
development/google-go-lang: Updated for version 1.9.2.
development/hhvm: Updated for version 3.23.3
development/hugo: Added (static HTML and CSS website generator).
development/ioncube-loader: Updated for version 10.1.0
development/jupyter-ipywidgets: Updated for version 7.1.0.
development/jupyter_client: Updated for version 5.2.1.
development/komodo-edit: Updated for version 11.0.2.
development/komodo-ide: Updated for version 11.0.2.
development/neovim: Run update-desktop-database in doinst.sh.
development/pkgconf: Updated for version 1.4.0.
development/radare2: Updated for version 2.2.0.
development/rust: Updated for version 1.23.0.
development/sqlcl: Updated for version 17.4.0.354.2224.
development/tcc: Updated for version 0.9.27.
development/tiled: Updated for version 1.1.0.
development/universal-ctags: Updated for version c3373c1
development/vstudio: Updated for version 7.5.7.
games/angband: Updated for version 4.1.2.
games/chocolate-doom: Updated for version 3.0.0.
games/commandergenius: Updated for version 2.0.0.0.
games/edgar: Updated for version 1.28.
games/gargoyle: Fix tarball handling + switch to i586.
games/gzdoom: Updated for version 3.2.5.
games/mame: Updated for version 0.193.
games/oblige: Fixed md5sum.
games/pacman: Added (an arcade game).
games/redeclipse: Updated for version 1.6.0.
games/tome: Fix for exported ARCH variable.
games/vkQuake: Updated for version 0.97.3.
gis/GMT: Updated for version 5.4.3.
graphics/asciiquarium: Updated for version 1.1.
graphics/darktable: Updated for version 2.4.0.
graphics/imgp: Added (Multi-core batch image resizer and rotator).
graphics/mozjpeg: Updated for version 3.3.1.
graphics/simple-scan: Updated for version 3.25.1.
libraries/Nevow: Updated for version 0.14.3.
libraries/SlowAES: Add python3 support.
libraries/girara: Updated for version 0.2.8.
libraries/jbig2dec: Fix MD5SUM.
libraries/libfaketime: Updated for version 0.9.7.
libraries/libgusb: Add vala as hard dep.
libraries/libupnp: Updated for version 1.8.3.
libraries/libuv: Fixed DOWNLOAD.
libraries/libvirt: Note additional optional deps
libraries/mygpoclient: Updated for version 1.8.
libraries/nltk: Updated for version 3.2.5.
libraries/python3-Jinja2: Added (python3 template engine).
libraries/python3-PyQt5: Updated for version 5.9.2.
libraries/qt5-webkit-annulen: Added (annulen's fork of qt5-webkit.)
libraries/tclap: Updated for version 1.2.2.
libraries/xml-security-c: Fixed DOWNLOAD.
libraries/zziplib: Fix for exported BUILD variable.
misc/fbcat: Updated for version 0.5.1.
misc/hashkill: Fix for exported BUILD variable.
misc/klibc: Fix for exported ARCH variable.
misc/protobuf3: Updated for version 3.5.1.1, add python3 support.
multimedia/QMPlay2: Updated for version 17.12.31.
multimedia/get_iplayer: Updated for version 3.09.
multimedia/gpodder: Updated for version 3.10.0.
multimedia/mkvtoolnix: Updated for version 19.0.0.
multimedia/podcastparser: Updated for version 0.6.2.
multimedia/smplayer: Updated for version 17.12.0.
multimedia/vkeybd: Updated for version 0.1.18d, new maintainer.
multimedia/youtube-viewer: Updated for version 3.3.2.
network/PySocks: Updated for version 1.6.8.
network/broadcom-sta: Fix for exported ARCH variable.
network/davmail: Updated for version 4.8.1.1.
network/ddgr: Fix zsh completion path.
network/elinks: Patched to fix gopher link issues.
network/gnome-bluetooth: Added (GNOME Bluetooth support).
network/gofiche: Updated for version 1.0.3.
network/googler: Fix zsh completion path.
network/iptv-analyzer: Fix for exported ARCH variable.
network/krb5: Added krb5kdc and kadmind init scripts.
network/nextcloud-server: Updated for version 12.0.4.
network/opera: Updated for version 50.0.2762.45.
network/owncloud-client: Updated for version 2.4.0.
network/plowshare-modules: Updated for version e94a905.
network/qutebrowser: Added (qt5 keyboard driven webbrowser).
network/r8168: Fix for exported ARCH variable.
network/retroshare: Updated for version 0.6.3.
network/rtl8188eu: Fix for exported ARCH variable.
network/shorewall-core: Updated for version 5.1.10.2.
network/shorewall6: Updated for version 5.1.10.2.
network/shorewall: Updated for version 5.1.10.2.
network/sickrage: Updated for version 2017.12.19_1.
network/sslscan: Updated for version 1.11.11.
network/stride: Updated for version 1.8.18.
network/synergy: Fixed DOWNLOAD.
network/teamviewer: Updated for version 13.0.6634.
network/telegram: Updated for version 1.2.6.
network/transgui: Updated for version 5.13.0.
network/uget-chrome-wrapper: this should not be 'noarch'
network/w3m: Updated for version git20170104 + new maintainer.
network/waterfox: Added (Web browser).
network/wput: Updated for version 0.6.2.
network/xdman: Updated for version 2018.7.0.3.
network/xtables-addons: Fix for exported ARCH variable.
network/you-get: Fixed md5sum.
office/alot: Removed.
office/djvusmooth: Updated for version 0.2.19.
office/kbibtex: Updated for version 0.7.
office/kmymoney: Updated for version 4.8.1.1.
office/libreoffice: Add loxxx symlinks.
office/mupdf: Updated for version 1.12.0.
office/sofastats: Updated for version 1.4.6.
office/zathura-cb: Updated for version 0.1.7.
office/zathura-djvu: Updated for version 0.2.7.
office/zathura-pdf-mupdf: Updated for version 0.3.2.
office/zathura-ps: Updated for version 0.2.5.
office/zathura: Updated for version 0.3.8.
perl/perl-CGI: Updated for version 4.38.
perl/perl-Math-MPFR: Updated for version 4.0.
python/Automat: Updated for version 0.6.0.
python/Unidecode: Updated for version 0.04.21.
python/asn1crypto: Updated for version 0.24.0.
python/attrs: Updated for version 17.4.0.
python/cryptography: Updated for version 2.1.4.
python/ecdsa: Add python3 support.
python/foolscap: Updated for version 0.13.1.
python/hyperlink: Updated for version 17.3.1.
python/idna: Updated for version 2.6.
python/incremental: Updated for version 17.5.0.
python/pyOpenSSL: Updated for version 17.5.0.
python/pyaes: Add python3 support.
python/pyasn1-modules: Updated for version 0.2.1.
python/pyasn1: Updated for version 0.4.2.
python/pyta-lib: Fixed tarball handling.
python/python-fonttools: Updated for version 3.21.1.
python/python-jsonrpclib: Updated for version 0.3.1.
python/python-klein: Updated for version 17.10.0.
python/python-pbkdf2: Add python3 support.
python/python-qrcode: Add python3 support.
python/python-twisted: Updated for version 17.9.0.
python/python3-attrs: Added (Classes Without Boilerplate).
python/python3-jupyter_client: Updated for version 5.2.1.
python/python3-sip: Updated for version 4.19.6.
python/service_identity: Updated for version 17.0.0.
python/thonny: Added (simple Python IDE).
python/txi2p: Updated for version 0.3.2.
python/websocket-client: Updated for version 0.45.0.
ruby/ruby-build: Updated for version 20171226.
system/alacritty: Updated for version git7b4ba80.
system/colord-gtk: Enable vala.
system/colord: Add vala detection automatically.
system/compsize: Added (btrfs compression report).
system/dosbox-dev: Updated for version 0.74.r4068.
system/evdi-kernel: Fix for exported ARCH variable.
system/fd: Updated for version 6.2.0.
system/fwupd: Unbreak build with meson-0.44.0.
system/hungrycat: Updated for version 0.4.1.
system/inxi: Updated for version 2.3.53.
system/lynis: Updated for version 2.5.8.
system/netatop: Fix for exported ARCH variable.
system/noto-emoji: Updated for version 20180102.
system/nvme-cli: Updated for version 1.5.
system/pspg: Updated for version 0.9.1.
system/python3-urwid: Added (python3 console UI module).
system/ranger: Updated for version 1.9.0b6.
system/rmw: Updated for version 0.4.03.
system/sleuthkit: Updated for version 4.5.0.
system/slpkg: Updated for version 3.3.3.
system/softhsm: Updated for version 2.3.0.
system/spl-solaris: Updated for version 0.7.4.
system/spl-solaris: Updated for version 0.7.5.
system/spl-solaris: Use /lib/modules/${KERN}/source
system/steamos-xpad: Fix for exported ARCH variable.
system/sysdig: Fix for exported ARCH variable.
system/tracker: Fix for exported BUILD variable.
system/upass: Added (Console UI for pass).
system/vbindiff: Updated for version 3.0_beta5.
system/xfburn: Updated for version 0.5.5.
system/zfs-on-linux: Create /var/lock/zfs before lockfile
system/zfs-on-linux: Updated for version 0.7.4.
system/zfs-on-linux: Updated for version 0.7.5.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- 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/20180106/a7bc4599/attachment-0001.asc>

From willysr at slackbuilds.org  Sat Jan  6 07:12:44 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 6 Jan 2018 14:12:44 +0700
Subject: [Slackbuilds-users] libass ABI changes
In-Reply-To: <CAPsDuS5-ZS-AfRu5NiPTVRK7FD-bHzL3HOLbqE1DYTCRqC6ZnQ@mail.gmail.com>
References: <CAPsDuS5-ZS-AfRu5NiPTVRK7FD-bHzL3HOLbqE1DYTCRqC6ZnQ@mail.gmail.com>
Message-ID: <d4394adf-8ca1-7d8d-cd5f-78e6fd17d283@slackbuilds.org>

> The thing is that with versions greater than 0.13.5 (the one on SBo)
> the ABI changes at this might break whatever depends on libass, as a
> mandatory or optional dependency: I'll wait a couple of weeks before
> merging to let you check compatibility with the scripts you are
> maintaining (libass.SlackBuild just needs a version bump).
> 
> the interested scripts are:
> aegisub

aegisub works fine with new libass


-- 
Willy Sudiarto Raharjo

-------------- 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/20180106/e3da91e7/attachment.asc>

From atelszewski at gmail.com  Sat Jan  6 08:48:31 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 6 Jan 2018 09:48:31 +0100
Subject: [Slackbuilds-users] spice-0.14.0 causes BSOD on Windows 7 when
 starting from managedsave
Message-ID: <9dd88533-c7c3-bfd4-533d-8da21eb0bc73@gmail.com>

Hi,

Just to let you know, this has caused me headache for a couple of days ;-)

Upgrading to spice-0.14.0, causes immediate crash (BSOD) of Windows 7 
guest, when starting from managedsave state.
This has probably something to do with QXL graphics.

I downgraded spice to 0.13.3, and things work as expected again.

I had quite some fun, because in the meantime, I upgraded many of the 
packages (qemu, libvirt, kernel) so I started to suspect the problem was 
one of those. But it turned out to be not ;-)

All this should be told to upstream.
I'll have to yet figure out the proper place.

-- 
Best regards,
Andrzej Telszewski

From yth at ythogtha.org  Sat Jan  6 13:49:11 2018
From: yth at ythogtha.org (Ythogtha)
Date: Sat, 6 Jan 2018 14:49:11 +0100
Subject: [Slackbuilds-users] libass ABI changes
In-Reply-To: <d4394adf-8ca1-7d8d-cd5f-78e6fd17d283@slackbuilds.org>
References: <CAPsDuS5-ZS-AfRu5NiPTVRK7FD-bHzL3HOLbqE1DYTCRqC6ZnQ@mail.gmail.com>
 <d4394adf-8ca1-7d8d-cd5f-78e6fd17d283@slackbuilds.org>
Message-ID: <20180106144911.2a9d6b700d638745ea46b048@ythogtha.org>

> > The thing is that with versions greater than 0.13.5 (the one on SBo)
> > the ABI changes at this might break whatever depends on libass, as a
> > mandatory or optional dependency: I'll wait a couple of weeks before
> > merging to let you check compatibility with the scripts you are
> > maintaining (libass.SlackBuild just needs a version bump).
> > 
> > the interested scripts are:
> > aegisub
> > SDL_kitchensink
> 
> aegisub works fine with new libass

SDL_kitchensink works fine too with the new libass !

-- 
Arnaud <yth at ythogtha.org>

From matteo.bernardini at gmail.com  Sat Jan  6 15:55:53 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 6 Jan 2018 16:55:53 +0100
Subject: [Slackbuilds-users] spice-0.14.0 causes BSOD on Windows 7 when
 starting from managedsave
In-Reply-To: <9dd88533-c7c3-bfd4-533d-8da21eb0bc73@gmail.com>
References: <9dd88533-c7c3-bfd4-533d-8da21eb0bc73@gmail.com>
Message-ID: <CAPsDuS4EPKAc0_jssRF2tnDja1zy8kzzY83SscmV4NXOb79c=Q@mail.gmail.com>

Il 06 gen 2018 9:47 AM, "Andrzej Telszewski" <atelszewski at gmail.com> ha
scritto:

Hi,

Just to let you know, this has caused me headache for a couple of days ;-)

Upgrading to spice-0.14.0, causes immediate crash (BSOD) of Windows 7
guest, when starting from managedsave state.
This has probably something to do with QXL graphics.

I downgraded spice to 0.13.3, and things work as expected again.

I had quite some fun, because in the meantime, I upgraded many of the
packages (qemu, libvirt, kernel) so I started to suspect the problem was
one of those. But it turned out to be not ;-)

All this should be told to upstream.
I'll have to yet figure out the proper place.

-- 
Best regards,
Andrzej Telszewski
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users at slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


https://www.spice-space.org/contact.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180106/024ec827/attachment.html>

From slacker6896 at gmail.com  Sat Jan  6 15:56:42 2018
From: slacker6896 at gmail.com (Sebastien BALLET)
Date: Sat, 6 Jan 2018 16:56:42 +0100
Subject: [Slackbuilds-users] [libreoffice] The lack of symlinks loxxx
 prevent opening of documents with Xfe
In-Reply-To: <cf6f48be-5714-7a33-a767-98121e47b33e@slackbuilds.org>
References: <CAA2+phGbi6ruD2-Q7CeT6X5p6385RmJQ_GHfeTEHe6OibyAVTw@mail.gmail.com>
 <cf6f48be-5714-7a33-a767-98121e47b33e@slackbuilds.org>
Message-ID: <CAA2+phHODf2uT+SABpm+sU+ByD_LyzoBZwtYB5QuT2Ua1BNaPg@mail.gmail.com>

Hello,

It seems you didn't applied the patch I sent properly. The symlinks are
created in / instead of /usr/bin :

$ cat /tmp/SBo/package-libreoffice/install/doinst.sh|grep lo[a-z]
( cd . ; rm -rf loimpress )
( cd . ; ln -sf ../../opt/libreoffice5.4/program/simpress loimpress )
( cd . ; rm -rf lowriter )
( cd . ; ln -sf ../../opt/libreoffice5.4/program/swriter lowriter )
( cd . ; rm -rf lomath )
( cd . ; ln -sf ../../opt/libreoffice5.4/program/smath lomath )
( cd . ; rm -rf lodraw )
( cd . ; ln -sf ../../opt/libreoffice5.4/program/sdraw lodraw )
( cd . ; rm -rf localc )
( cd . ; ln -sf ../../opt/libreoffice5.4/program/scalc localc )
( cd . ; rm -rf lobase )
( cd . ; ln -sf ../../opt/libreoffice5.4/program/sbase lobase )

That's because you put the commands 'ln ...' after the command 'cd -' :

$ grep -A 7 -B 10 Xfe libreoffice.SlackBuild

# Create symlinks in /usr/bin to actual binaries
cd $PKG/usr/bin
  for FILE in \
    sbase scalc sdraw simpress smath soffice swriter unopkg ; do
      rm -f $FILE
      ln -sf ../../opt/libreoffice$SRCSHORT/program/$FILE $FILE ;
  done
*cd -* # <=== Error: This should be run after the ln commands below

# The symlinks below are required to (directly) open documents
# supported by libreoffice with Xfe file manager.
ln -sf ../../opt/libreoffice$SRCSHORT/program/sbase    lobase
ln -sf ../../opt/libreoffice$SRCSHORT/program/scalc    localc
ln -sf ../../opt/libreoffice$SRCSHORT/program/sdraw    lodraw
ln -sf ../../opt/libreoffice$SRCSHORT/program/simpress loimpress
ln -sf ../../opt/libreoffice$SRCSHORT/program/smath    lomath
ln -sf ../../opt/libreoffice$SRCSHORT/program/swriter  lowriter

-- 
SeB


2018-01-05 23:56 GMT+01:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:

> > Xfe file manager includes file associations to open documents supported
> by
> > libreoffice with programs named: lobase, localc, lodraw, loimpress,
> lomath
> > and lowriter.
> >
> > However, the libreoffice package (the one which repackage official
> binary)
> > does not include binaries/symlinks/wrappers with those names, which force
> > user to create new file associations to be able to directly open
> documents
> > supported by libreoffice with Xfe.
> >
> > The patch below (also in attachment) fixes this issue:
>
> Thanks
> i have applied it on 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/20180106/8c786e0a/attachment.html>

From hba.nihilismus at gmail.com  Sat Jan  6 16:03:07 2018
From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=)
Date: Sat, 6 Jan 2018 10:03:07 -0600
Subject: [Slackbuilds-users] SBo: dbeaver new version
In-Reply-To: <alpine.LNX.2.20.1801041540110.32160@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801041540110.32160@salmo.appl-ecosys.com>
Message-ID: <CAJx2MoFYSijdr6PPFRcHymDgVidgYHgA3OJ-eMMx5r8xSmmYvw@mail.gmail.com>

Hi Rich.

Two years ago I stopped being an Slackware user and I'm not maintaining
any SlackBuild since then so feel free to be dbeaver's maintainer ;-)

- Cheers


On Thu, Jan 4, 2018 at 5:47 PM, Rich Shepard <rshepard at appl-ecosys.com>
wrote:

> Antonio,
>
>   The SBo repository has version 3.5.8 and version 4.3.1 was released last
> month. I want to upgrade my community edition from 3.5.8 to 4.3.1 but the
> build script is not finding a file and directory that exist.
>
>   I modified the build script to build in /opt/ rather than /tmp/ because
> the former has more space. I also changed SRCNAM to dbeaver-ce from
> dbeaver-ee.
>
>   When I run the script (as root, of course) I get this result:
> dbeaver/plugins/org.w3c.dom.svg_1.1.0.v201011041433.jar
> dbeaver/readme.txt
> dbeaver/dbeaver
> cp: cannot stat '/opt/SBo/package-dbeaver/opt/dbeaver/readme.txt': No
> such file or directory
> cp: cannot stat '/opt/SBo/package-dbeaver/opt/dbeaver/licenses/*': No
> such file or directory
>
>   When I untar the source tarball I find the readme.txt file and the
> licenses/ directory in:
>
> /opt/slackbuilds/Databases/dbeaver/dbeaver]$ ls
> artifacts.xml   dbeaver.desktop  features/  p2/
> configuration/  dbeaver.ini      icon.xpm   plugins/
> dbeaver*        dbeaver.png      licenses/  readme.txt
>
> which is an additional subdirectory below the top level one. I suppose I
> can
> move that entire subdirectory up one level. Is this what you'd recommend?
>
> Regards,
>
> Rich
>



-- 
Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx.
https://github.com/nihilismus | https://bitbucket.org/nihilismus |
https://twitter.com/nihilipster
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180106/b4274002/attachment-0001.html>

From Jim.Diamond at acadiau.ca  Sat Jan  6 16:08:08 2018
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Sat, 6 Jan 2018 12:08:08 -0400
Subject: [Slackbuilds-users] skypeforlinux
Message-ID: <20180106160808.GA16181@jdiamond-mb.acadiau.ca>

Hi,

the SBo version is 8.11.0.4 but there are 5 newer versions at
repo.skype.com/deb/pool/main/s/skypeforlinux/.

Time for a bump?

Cheers.
                                Jim

From willysr at slackbuilds.org  Sat Jan  6 16:21:30 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 6 Jan 2018 23:21:30 +0700
Subject: [Slackbuilds-users] [libreoffice] The lack of symlinks loxxx
 prevent opening of documents with Xfe
In-Reply-To: <CAA2+phHODf2uT+SABpm+sU+ByD_LyzoBZwtYB5QuT2Ua1BNaPg@mail.gmail.com>
References: <CAA2+phGbi6ruD2-Q7CeT6X5p6385RmJQ_GHfeTEHe6OibyAVTw@mail.gmail.com>
 <cf6f48be-5714-7a33-a767-98121e47b33e@slackbuilds.org>
 <CAA2+phHODf2uT+SABpm+sU+ByD_LyzoBZwtYB5QuT2Ua1BNaPg@mail.gmail.com>
Message-ID: <ab798d36-5d7f-54e5-57bb-228846c39217@slackbuilds.org>

> That's because you put the commands 'ln ...' after the command 'cd -' :
> 
> $ grep -A 7 -B 10 Xfe libreoffice.SlackBuild
> 
> # Create symlinks in /usr/bin to actual binaries
> cd $PKG/usr/bin
> ? for FILE in \
> ??? sbase scalc sdraw simpress smath soffice swriter unopkg ; do
> ????? rm -f $FILE
> ????? ln -sf ../../opt/libreoffice$SRCSHORT/program/$FILE $FILE ;
> ? done
> *cd -* # <=== Error: This should be run after the ln commands below
> 
> # The symlinks below are required to (directly) open documents
> # supported by libreoffice with Xfe file manager.
> ln -sf ../../opt/libreoffice$SRCSHORT/program/sbase??? lobase
> ln -sf ../../opt/libreoffice$SRCSHORT/program/scalc??? localc
> ln -sf ../../opt/libreoffice$SRCSHORT/program/sdraw??? lodraw
> ln -sf ../../opt/libreoffice$SRCSHORT/program/simpress loimpress
> ln -sf ../../opt/libreoffice$SRCSHORT/program/smath??? lomath
> ln -sf ../../opt/libreoffice$SRCSHORT/program/swriter? lowriter

Hi  SeB

thanks for noticing
i have applied the fix on my branch


-- 
Willy Sudiarto Raharjo

-------------- 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/20180106/44fd86f9/attachment.asc>

From rshepard at appl-ecosys.com  Sat Jan  6 16:28:34 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 6 Jan 2018 08:28:34 -0800 (PST)
Subject: [Slackbuilds-users] atlas3.10.3 build issues
Message-ID: <alpine.LNX.2.20.1801060823270.21540@salmo.appl-ecosys.com>

   Just ran sbopkg and encountered an error:

qgis:
Found qgis-2.10.1.tar.bz2 in /var/cache/sbopkg.
...skipping...
Found atlas3.10.3.tar.bz2 in /var/cache/sbopkg.
Checking MD5SUM:
   MD5SUM check for atlas3.10.3.tar.bz2 ... OK
Building package for atlas...
ERROR: Improper LAPACK source archive!
        Please check /usr/share/lapack-atlas/lapack.tgz
        and set it properly!

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

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

   Installed here are atlas-3.8.3-i486-2_SBo, lapack-3.8.0-i586-1_SBo, and
qgis-2.18.15-i586-1_SBo. I do not have lapack-atlas installed.

   Would like advice on how to correct this error. Do I remove the separate
atlas and lapack packages and install lapack-atlas in their stead?

Regards,

Rich


From willysr at slackbuilds.org  Sat Jan  6 16:30:59 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 6 Jan 2018 23:30:59 +0700
Subject: [Slackbuilds-users] atlas3.10.3 build issues
In-Reply-To: <alpine.LNX.2.20.1801060823270.21540@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801060823270.21540@salmo.appl-ecosys.com>
Message-ID: <00b687ea-a3a7-08de-41bb-147e74df672c@slackbuilds.org>

> ? Just ran sbopkg and encountered an error:
> 
> qgis:
> Found qgis-2.10.1.tar.bz2 in /var/cache/sbopkg.
> ...skipping...
> Found atlas3.10.3.tar.bz2 in /var/cache/sbopkg.
> Checking MD5SUM:
> ? MD5SUM check for atlas3.10.3.tar.bz2 ... OK
> Building package for atlas...
> ERROR: Improper LAPACK source archive!
> ?????? Please check /usr/share/lapack-atlas/lapack.tgz
> ?????? and set it properly!
> 
> atlas:
> Would you like to continue processing the rest of the
> queue or would you like to abort?? If this failed
> package is a dependency of another package in the queue
> then it may not make sense to continue.
> 
> (Y)es to continue, (N)o to abort, (R)etry the build?: y
> 
> ? Installed here are atlas-3.8.3-i486-2_SBo, lapack-3.8.0-i586-1_SBo, and
> qgis-2.18.15-i586-1_SBo. I do not have lapack-atlas installed.
> 
> ? Would like advice on how to correct this error. Do I remove the separate
> atlas and lapack packages and install lapack-atlas in their stead?

You don't seems to have atlas-lapack which is the dependency for atlas?

-- 
Willy Sudiarto Raharjo

-------------- 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/20180106/07715286/attachment.asc>

From rshepard at appl-ecosys.com  Sat Jan  6 16:38:23 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 6 Jan 2018 08:38:23 -0800 (PST)
Subject: [Slackbuilds-users] atlas3.10.3 build issues [FIXED]
In-Reply-To: <00b687ea-a3a7-08de-41bb-147e74df672c@slackbuilds.org>
References: <alpine.LNX.2.20.1801060823270.21540@salmo.appl-ecosys.com>
 <00b687ea-a3a7-08de-41bb-147e74df672c@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.1801060836530.21540@salmo.appl-ecosys.com>

On Sat, 6 Jan 2018, Willy Sudiarto Raharjo wrote:

> You don't seems to have atlas-lapack which is the dependency for atlas?

   Thanks, Willy. I did not realize that lapack-atlas was required for atlas
(until I re-read the description today). I thought having lapack installed
was sufficient.

   Fixed.

Rich

From yth at ythogtha.org  Sat Jan  6 17:01:22 2018
From: yth at ythogtha.org (Ythogtha)
Date: Sat, 6 Jan 2018 18:01:22 +0100
Subject: [Slackbuilds-users] Kodi error with DL'ed file
Message-ID: <20180106180122.11b426a507273e244740a9ef@ythogtha.org>

Hi,

	I've got a problem building kodi here.
The file xbmc-17.4-Krypton.tar.gz seems to downlod fine, but has a wrong md5sum
and when tar-xvf'ed it says :
tar: Skipping to next header
tar: Exiting with failure status due to previous errors

	Just gunzipping it does not work saying :
gzip: xbmc-17.4-Krypton.tar.gz: invalid compressed data--crc error
gzip: xbmc-17.4-Krypton.tar.gz: invalid compressed data--length error

It's not related to the wget "feature" which gzip or gunzip file without telling
us, but seems to be related to github.
There's no error in the download, it seems to go fine, but the file is obviously
corrupted.

I don't really know wether the problem comes from me, but bumping to
xbmc-17.6-Krypton.tar.gz and FFmpeg-3.1.11-Krypton.tar.gz
resolves the problem, there are no download hiccups, and everything builds fine.

Cheers :)

-- 
Arnaud <yth at ythogtha.org>

From willysr at slackbuilds.org  Sat Jan  6 17:02:26 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Jan 2018 00:02:26 +0700
Subject: [Slackbuilds-users] Kodi error with DL'ed file
In-Reply-To: <20180106180122.11b426a507273e244740a9ef@ythogtha.org>
References: <20180106180122.11b426a507273e244740a9ef@ythogtha.org>
Message-ID: <8cc0093d-43b8-4c49-ac15-73422c29d9f3@slackbuilds.org>

> Hi,
> 
> 	I've got a problem building kodi here.
> The file xbmc-17.4-Krypton.tar.gz seems to downlod fine, but has a wrong md5sum
> and when tar-xvf'ed it says :
> tar: Skipping to next header
> tar: Exiting with failure status due to previous errors
> 
> 	Just gunzipping it does not work saying :
> gzip: xbmc-17.4-Krypton.tar.gz: invalid compressed data--crc error
> gzip: xbmc-17.4-Krypton.tar.gz: invalid compressed data--length error
> 
> It's not related to the wget "feature" which gzip or gunzip file without telling
> us, but seems to be related to github.
> There's no error in the download, it seems to go fine, but the file is obviously
> corrupted.
> 
> I don't really know wether the problem comes from me, but bumping to
> xbmc-17.6-Krypton.tar.gz and FFmpeg-3.1.11-Krypton.tar.gz
> resolves the problem, there are no download hiccups, and everything builds fine.

I just built kodi few hours ago and it went fine
can you try to re-download xbmc's source?


-- 
Willy Sudiarto Raharjo

-------------- 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/20180107/a8a4e96f/attachment-0001.asc>

From willysr at slackbuilds.org  Sat Jan  6 17:13:07 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Jan 2018 00:13:07 +0700
Subject: [Slackbuilds-users] libass ABI changes
In-Reply-To: <CAPsDuS5-ZS-AfRu5NiPTVRK7FD-bHzL3HOLbqE1DYTCRqC6ZnQ@mail.gmail.com>
References: <CAPsDuS5-ZS-AfRu5NiPTVRK7FD-bHzL3HOLbqE1DYTCRqC6ZnQ@mail.gmail.com>
Message-ID: <45cddfd0-95d8-5244-763e-93c3bd41faf6@slackbuilds.org>

These scripts built fine with new libass, but i didn't test the runtime
functionality though.

> SDL_kitchensink> HandBrake> QMPlay2> aegisub> bino> gst-plugins-bad> gst0-plugins-bad>
kodi> mpv> mythtv
I haven't test this two
> OpenPHT
> plex-home-theater

> vlc
It failed to build, but i guess it's caused by newer libupnp
https://pastebin.com/dq8CKh1n


-- 
Willy Sudiarto Raharjo

-------------- 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/20180107/a16a5105/attachment.asc>

From willysr at slackbuilds.org  Sat Jan  6 17:15:34 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Jan 2018 00:15:34 +0700
Subject: [Slackbuilds-users] libass ABI changes
In-Reply-To: <CAPsDuS5-ZS-AfRu5NiPTVRK7FD-bHzL3HOLbqE1DYTCRqC6ZnQ@mail.gmail.com>
References: <CAPsDuS5-ZS-AfRu5NiPTVRK7FD-bHzL3HOLbqE1DYTCRqC6ZnQ@mail.gmail.com>
Message-ID: <8058bec6-e8e5-3151-ab06-4e0aa33aac39@slackbuilds.org>

These scripts built fine with new libass, but i didn't test the runtime
functionality though.

> SDL_kitchensink
> HandBrake
> QMPlay2
> aegisub
> bino
> gst-plugins-bad
> gst0-plugins-bad
> kodi
> mpv
> mythtv

> OpenPHT
> plex-home-theater

I haven't test this two

> vlc

It failed to build, but i guess it's caused by newer libupnp
https://pastebin.com/dq8CKh1n

Sorry for double post
it seems the first one got is messed up

-- 
Willy Sudiarto Raharjo

-------------- 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/20180107/a878d1f1/attachment.asc>

From matteo.bernardini at gmail.com  Sat Jan  6 17:22:46 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 6 Jan 2018 18:22:46 +0100
Subject: [Slackbuilds-users] libass ABI changes
In-Reply-To: <8058bec6-e8e5-3151-ab06-4e0aa33aac39@slackbuilds.org>
References: <CAPsDuS5-ZS-AfRu5NiPTVRK7FD-bHzL3HOLbqE1DYTCRqC6ZnQ@mail.gmail.com>
 <8058bec6-e8e5-3151-ab06-4e0aa33aac39@slackbuilds.org>
Message-ID: <CAPsDuS7iHayhKyckkQCrRJn1ecGU9k6+RiS+ogKP+w9_o_80Gw@mail.gmail.com>

2018-01-06 18:15 GMT+01:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:
> These scripts built fine with new libass, but i didn't test the runtime
> functionality though.
>
>> SDL_kitchensink
>> HandBrake
>> QMPlay2
>> aegisub
>> bino
>> gst-plugins-bad
>> gst0-plugins-bad
>> kodi
>> mpv
>> mythtv
>
>> OpenPHT
>> plex-home-theater
>
> I haven't test this two
>
>> vlc
>
> It failed to build, but i guess it's caused by newer libupnp
> https://pastebin.com/dq8CKh1n

thanks Willy!

I found that support for the newer libupnp has been added to vlc in august

http://git.videolan.org/?p=vlc/vlc-3.0.git;a=commit;h=3eb4e03512f45c1fa27c7f9a6759e8e7d3905720

so I'll let Chris decide in which way he likes to proceed (get in
touch with me directly or via the list, either is ok): looks like vlc
3.0 is near but if a more recent git snapshot of the 3.0 branch is
needed I can host it.

Matteo

From yth at ythogtha.org  Sat Jan  6 17:52:07 2018
From: yth at ythogtha.org (Ythogtha)
Date: Sat, 6 Jan 2018 18:52:07 +0100
Subject: [Slackbuilds-users] Kodi error with DL'ed file
In-Reply-To: <8cc0093d-43b8-4c49-ac15-73422c29d9f3@slackbuilds.org>
References: <20180106180122.11b426a507273e244740a9ef@ythogtha.org>
 <8cc0093d-43b8-4c49-ac15-73422c29d9f3@slackbuilds.org>
Message-ID: <20180106185207.15e54e7f2547b73de745600c@ythogtha.org>

> > Hi,
> > 
> > 	I've got a problem building kodi here.
> > The file xbmc-17.4-Krypton.tar.gz seems to downlod fine, but has a wrong
> > md5sum and when tar-xvf'ed it says :
> > tar: Skipping to next header
> > tar: Exiting with failure status due to previous errors
> > 
> > 	Just gunzipping it does not work saying :
> > gzip: xbmc-17.4-Krypton.tar.gz: invalid compressed data--crc error
> > gzip: xbmc-17.4-Krypton.tar.gz: invalid compressed data--length error
> > 
> > It's not related to the wget "feature" which gzip or gunzip file without
> > telling us, but seems to be related to github.
> > There's no error in the download, it seems to go fine, but the file is
> > obviously corrupted.
> > 
> > I don't really know wether the problem comes from me, but bumping to
> > xbmc-17.6-Krypton.tar.gz and FFmpeg-3.1.11-Krypton.tar.gz
> > resolves the problem, there are no download hiccups, and everything builds
> > fine.
> 
> I just built kodi few hours ago and it went fine
> can you try to re-download xbmc's source?

Ok, I tried downloading the file through another internet access and everything
went fine. Though with my internet access it failed three times.
My own connexion isn't very fast so maybe that's the problem, but the 17.6 is as
big as the 17.4 and it downloaded fine.

Well, another computer science mystery that'll go to the X-Files cold cases ;)

Sorry for the noise !

-- 
Arnaud <yth at ythogtha.org>

From alik at ejik.org  Sat Jan  6 19:37:25 2018
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sat, 06 Jan 2018 22:37:25 +0300
Subject: [Slackbuilds-users] skypeforlinux
In-Reply-To: <20180106160808.GA16181@jdiamond-mb.acadiau.ca>
References: <20180106160808.GA16181@jdiamond-mb.acadiau.ca>
Message-ID: <1515267445.3653554.1226464720.3B3B44E4@webmail.messagingengine.com>

Hello,

> the SBo version is 8.11.0.4 but there are 5 newer versions at
> repo.skype.com/deb/pool/main/s/skypeforlinux/.
> 
> Time for a bump?

There are "stable" versions listed here:
https://repo.skype.com/deb/dists/stable/main/binary-amd64/Packages

and "unstable" ones listed here:
https://repo.skype.com/deb/dists/unstable/main/binary-amd64/Packages

8.11.0.4 is the latest stable version. Also, this is the version
distributed via https://www.skype.com/en/get-skype/.

Best regards,
Alexander

From alleytrotter at gmail.com  Sat Jan  6 20:35:20 2018
From: alleytrotter at gmail.com (John Yost)
Date: Sat, 6 Jan 2018 15:35:20 -0500
Subject: [Slackbuilds-users] kmymoney
Message-ID: <01d048f8-9f33-390f-f2d0-f1800a51ca4c@gmail.com>

the kymoney.desktop file seems to have disappeared with todays update
thanks

-- 
John David Yost
AlleyTrotter
pub   2048D/F3BDEB55 2014-05-23 [expires: Never]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xF3BDEB55.asc
Type: application/pgp-keys
Size: 2312 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180106/a63230e7/attachment.bin>

From alleytrotter at gmail.com  Sat Jan  6 20:41:04 2018
From: alleytrotter at gmail.com (John Yost)
Date: Sat, 6 Jan 2018 15:41:04 -0500
Subject: [Slackbuilds-users] kmymoney
Message-ID: <ac6e4a6e-6653-a1c2-c0f5-8772bc6109c2@gmail.com>

the kymoney.desktop file seems to have disappeared with today's update
to kmymoney-4.8.1.1

A reinstall of 4.8.0 returns the missing file
sorry for the double email

thanks
John

-- 
John David Yost
AlleyTrotter
pub   2048D/F3BDEB55 2014-05-23 [expires: Never]

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xF3BDEB55.asc
Type: application/pgp-keys
Size: 2313 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180106/4da989e0/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xF3BDEB55.asc
Type: application/pgp-keys
Size: 2312 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180106/4da989e0/attachment-0003.bin>

From alik at ejik.org  Sat Jan  6 20:58:21 2018
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sat, 06 Jan 2018 23:58:21 +0300
Subject: [Slackbuilds-users] gajim
Message-ID: <1515272301.3677189.1226508384.3EC2A72D@webmail.messagingengine.com>

Hello,

Today update broke gajim. The simplest way to repair is to bump the
gajim version to 0.16.9 and the python-nbxmpp version to 0.6.2.

Best regards,
Alexander

From edps.mundognu at gmail.com  Sat Jan  6 23:12:47 2018
From: edps.mundognu at gmail.com (Edinaldo)
Date: Sat, 06 Jan 2018 21:12:47 -0200
Subject: [Slackbuilds-users] libass ABI changes
Message-ID: <op.zcfz3l1l9z09aw@localhost>


Hi people,

For your knowledge, QMPlay2 builds and works fine with libass 1.4.0.

Cheers,

Edinaldo.

From willysr at slackbuilds.org  Sat Jan  6 23:56:31 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Jan 2018 06:56:31 +0700
Subject: [Slackbuilds-users] gajim
In-Reply-To: <1515272301.3677189.1226508384.3EC2A72D@webmail.messagingengine.com>
References: <1515272301.3677189.1226508384.3EC2A72D@webmail.messagingengine.com>
Message-ID: <c00a14f4-2c11-fa3c-66da-b91b29759dae@slackbuilds.org>

> Today update broke gajim. The simplest way to repair is to bump the
> gajim version to 0.16.9 and the python-nbxmpp version to 0.6.2.

Which part of gajim is broken after the update?
is it build time or run time?


-- 
Willy Sudiarto Raharjo

-------------- 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/20180107/f9a7a2b4/attachment.asc>

From willysr at slackbuilds.org  Sun Jan  7 00:06:05 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Jan 2018 07:06:05 +0700
Subject: [Slackbuilds-users] Scripts for grab
Message-ID: <556a4a8e-0608-e48b-fb70-8964aab46a75@slackbuilds.org>

Hi

Following Antonio's confirmation about not maintaining his SlackBuilds
anymore, here are all his scripts up for grab

system/hdapsd
system/ibam
system/cpuid
system/tp_smapi
network/thttpd
network/hiawatha
network/pgbouncer
misc/discount
office/NME
audio/ices-cc
libraries/hoedown
development/dbeaver
development/polyml


-- 
Willy Sudiarto Raharjo

-------------- 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/20180107/0f316444/attachment.asc>

From fernando.lopezjr at gmail.com  Sun Jan  7 00:06:55 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sat, 6 Jan 2018 17:06:55 -0700
Subject: [Slackbuilds-users] Scripts for grab
In-Reply-To: <556a4a8e-0608-e48b-fb70-8964aab46a75@slackbuilds.org>
References: <556a4a8e-0608-e48b-fb70-8964aab46a75@slackbuilds.org>
Message-ID: <CALrQ46DRC4-QM3YRcHE=HMdr4vScUddCF_unZftDsWPkq_PsMA@mail.gmail.com>

cpuid please.

On Sat, Jan 6, 2018 at 5:06 PM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> Hi
>
> Following Antonio's confirmation about not maintaining his SlackBuilds
> anymore, here are all his scripts up for grab
>
> system/hdapsd
> system/ibam
> system/cpuid
> system/tp_smapi
> network/thttpd
> network/hiawatha
> network/pgbouncer
> misc/discount
> office/NME
> audio/ices-cc
> libraries/hoedown
> development/dbeaver
> development/polyml
>
>
> --
> 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/20180106/5faef8a5/attachment.html>

From chytraeu at sdf.org  Sun Jan  7 00:14:27 2018
From: chytraeu at sdf.org (Donald Cooley)
Date: Sat, 06 Jan 2018 18:14:27 -0600
Subject: [Slackbuilds-users] Scripts for grab
In-Reply-To: <556a4a8e-0608-e48b-fb70-8964aab46a75@slackbuilds.org>
References: <556a4a8e-0608-e48b-fb70-8964aab46a75@slackbuilds.org>
Message-ID: <CD9D5E59-AA6D-443F-A44C-5B86A1E5E4FA@sdf.org>

On January 6, 2018 6:06:05 PM CST, Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:
>Hi
>
>Following Antonio's confirmation about not maintaining his SlackBuilds
>anymore, here are all his scripts up for grab
>
>system/hdapsd
>system/ibam
>system/cpuid
>system/tp_smapi
>network/thttpd
>network/hiawatha
>network/pgbouncer
>misc/discount
>office/NME
>audio/ices-cc
>libraries/hoedown
>development/dbeaver
>development/polyml

Network/ Hiawatha please
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

From yth at ythogtha.org  Sun Jan  7 00:29:58 2018
From: yth at ythogtha.org (Ythogtha)
Date: Sun, 7 Jan 2018 01:29:58 +0100
Subject: [Slackbuilds-users] Scripts for grab
In-Reply-To: <556a4a8e-0608-e48b-fb70-8964aab46a75@slackbuilds.org>
References: <556a4a8e-0608-e48b-fb70-8964aab46a75@slackbuilds.org>
Message-ID: <20180107012958.4236ce811da7d513b3402737@ythogtha.org>

> Hi
> 
> Following Antonio's confirmation about not maintaining his SlackBuilds
> anymore, here are all his scripts up for grab
> 
> system/hdapsd
> system/ibam
> system/cpuid
> system/tp_smapi
> network/thttpd
> network/hiawatha
> network/pgbouncer
> misc/discount
> office/NME
> audio/ices-cc
> libraries/hoedown
> development/dbeaver
> development/polyml

I'll happily take network/thttpd !

-- 
Arnaud <yth at ythogtha.org>

From chytraeu at sdf.org  Sun Jan  7 01:10:25 2018
From: chytraeu at sdf.org (Donald Cooley)
Date: Sat, 06 Jan 2018 19:10:25 -0600
Subject: [Slackbuilds-users] Scripts for grab
In-Reply-To: <556a4a8e-0608-e48b-fb70-8964aab46a75@slackbuilds.org>
References: <556a4a8e-0608-e48b-fb70-8964aab46a75@slackbuilds.org>
Message-ID: <1B2170A0-599B-4263-8FD4-3DBABAFFA5AD@sdf.org>

On January 6, 2018 6:06:05 PM CST, Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:
>Hi
>
>Following Antonio's confirmation about not maintaining his SlackBuilds
>anymore, here are all his scripts up for grab
>
>system/hdapsd
>system/ibam
>system/cpuid
>system/tp_smapi
>network/thttpd
>network/hiawatha
>network/pgbouncer
>misc/discount
>office/NME
>audio/ices-cc
>libraries/hoedown
>development/dbeaver
>development/polyml

I'll take misc/discount
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

From willysr at slackbuilds.org  Sun Jan  7 01:33:12 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Jan 2018 08:33:12 +0700
Subject: [Slackbuilds-users] fpc and ptop conflict
In-Reply-To: <CAN1hMuCL1zfGce2t5UarDvd4GxtwH_PSGdQ1e39--5MkHXxBtQ@mail.gmail.com>
References: <CAN1hMuCL1zfGce2t5UarDvd4GxtwH_PSGdQ1e39--5MkHXxBtQ@mail.gmail.com>
Message-ID: <e84f7693-7875-dd9a-d6f0-b75e70626d50@slackbuilds.org>

> development/fpc and system/ptop both install a /usr/bin/ptop file.
> 
> Easiest solution is to add a note to the READMEs of both builds, saying
> they conflict, and to only install one or the other.
> 
> Fancier solution would be for ptop (the smaller/simpler of the two)
> to be installed as /usr/bin/ptop.py, or else /opt/ptop/bin/ptop, and
> add a note to its README explaining how to run it.

It's now done on my branch

sorry that it got lost on my inbox


-- 
Willy Sudiarto Raharjo

-------------- 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/20180107/54b3aa77/attachment-0001.asc>

From mchagas at riseup.net  Sun Jan  7 02:14:48 2018
From: mchagas at riseup.net (Maykon Chagas)
Date: Sun, 7 Jan 2018 00:14:48 -0200
Subject: [Slackbuilds-users] Scripts for grab
In-Reply-To: <556a4a8e-0608-e48b-fb70-8964aab46a75@slackbuilds.org>
References: <556a4a8e-0608-e48b-fb70-8964aab46a75@slackbuilds.org>
Message-ID: <5e579d70-0d8c-3427-e8b1-09df9f05bd86@riseup.net>

Hi Willy,

I'll take tp_smapi and hdapsd.

Thank you.

Em 01/06/2018 10:06 PM, Willy Sudiarto Raharjo escreveu:
> Hi
> 
> Following Antonio's confirmation about not maintaining his SlackBuilds
> anymore, here are all his scripts up for grab
> 
> system/hdapsd
> system/ibam
> system/cpuid
> system/tp_smapi
> network/thttpd
> network/hiawatha
> network/pgbouncer
> misc/discount
> office/NME
> audio/ices-cc
> libraries/hoedown
> development/dbeaver
> development/polyml
> 
> 
> 
> 
> _______________________________________________
> 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/
> 

-- 
Maykon Chagas

GPG: 1E1A 2C79 8C53 FA4E

-------------- 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/20180107/4cc7f98b/attachment.asc>

From novalazy at gmail.com  Sun Jan  7 02:33:07 2018
From: novalazy at gmail.com (Peter Wang)
Date: Sun, 7 Jan 2018 13:33:07 +1100
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
Message-ID: <20180107133307.GB1245@hili.localdomain>

Hi,

I am giving up maintainership of my scripts:

desktop/xfce4-cpugraph-plugin
development/latrace
development/valgrind
libraries/allegro4
misc/tal
office/pandoc
system/oldschool-pc-fonts

Please take care of my babies.

Peter

From willysr at slackbuilds.org  Sun Jan  7 02:36:05 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 7 Jan 2018 09:36:05 +0700
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <20180107133307.GB1245@hili.localdomain>
References: <20180107133307.GB1245@hili.localdomain>
Message-ID: <8aa7eee8-a146-2d54-de5d-3d875d85fe7f@slackbuilds.org>

> development/valgrind

I'll take this one


-- 
Willy Sudiarto Raharjo

-------------- 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/20180107/955cbea5/attachment.asc>

From chytraeu at sdf.org  Sun Jan  7 03:04:19 2018
From: chytraeu at sdf.org (Donald Cooley)
Date: Sat, 06 Jan 2018 21:04:19 -0600
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <20180107133307.GB1245@hili.localdomain>
References: <20180107133307.GB1245@hili.localdomain>
Message-ID: <1C71B1C1-D9FB-471F-A0B0-79EF66335F8B@sdf.org>

On January 6, 2018 8:33:07 PM CST, Peter Wang <novalazy at gmail.com> wrote:
>Hi,
>
>I am giving up maintainership of my scripts:
>
>desktop/xfce4-cpugraph-plugin
>development/latrace
>development/valgrind
>libraries/allegro4
>misc/tal
>office/pandoc
>system/oldschool-pc-fonts
>
>Please take care of my babies.
>
>Peter
>_______________________________________________
>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/

I'll take misc/tal and system/oldschool-pc-fonts
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

From kingbeowulf at gmail.com  Sun Jan  7 07:06:38 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 6 Jan 2018 23:06:38 -0800
Subject: [Slackbuilds-users] Frostwire is orphaned
Message-ID: <ed9bf21f-ae7a-676d-f442-263faf5a7fa8@gmail.com>

FYI, just another reminder: I have dropped support for Frostwire.  I'm
not interested in another bittorrent client with wiz-bang multimedia
features. Anyone interested in keeping it alive is welcome to take it over.

Admins, please remove me from the frostwire.info file. Thanks

diff --git a/network/frostwire/frostwire.info
b/network/frostwire/frostwire.info
index a19319940c..2f30deb3ec 100644
--- a/network/frostwire/frostwire.info
+++ b/network/frostwire/frostwire.info
@@ -6,5 +6,5 @@ MD5SUM="908dfffbd4b82255d5d1f40cea1f7d2b"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES="jdk"
-MAINTAINER="Edward W. Koenig"
-EMAIL="kingbeowulf at gmail.com"
+MAINTAINER="none"
+EMAIL="none"



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

From chytraeu at sdf.org  Sun Jan  7 07:40:29 2018
From: chytraeu at sdf.org (Donald Cooley)
Date: Sun, 7 Jan 2018 01:40:29 -0600
Subject: [Slackbuilds-users] Frostwire is orphaned
In-Reply-To: <ed9bf21f-ae7a-676d-f442-263faf5a7fa8@gmail.com>
References: <ed9bf21f-ae7a-676d-f442-263faf5a7fa8@gmail.com>
Message-ID: <3ae4505e-deac-1265-677e-ad3917238d9d@sdf.org>

On 01/07/2018 01:06 AM, King Beowulf wrote:
> FYI, just another reminder: I have dropped support for Frostwire.  I'm
> not interested in another bittorrent client with wiz-bang multimedia
> features. Anyone interested in keeping it alive is welcome to take it over.
> 
> Admins, please remove me from the frostwire.info file. Thanks
> 
> diff --git a/network/frostwire/frostwire.info
> b/network/frostwire/frostwire.info
> index a19319940c..2f30deb3ec 100644
> --- a/network/frostwire/frostwire.info
> +++ b/network/frostwire/frostwire.info
> @@ -6,5 +6,5 @@ MD5SUM="908dfffbd4b82255d5d1f40cea1f7d2b"
>  DOWNLOAD_x86_64=""
>  MD5SUM_x86_64=""
>  REQUIRES="jdk"
> -MAINTAINER="Edward W. Koenig"
> -EMAIL="kingbeowulf at gmail.com"
> +MAINTAINER="none"
> +EMAIL="none"
> 
> 
> 
> 
> 
> _______________________________________________
> 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/
> 

I'll take this one

From yalhcru at gmail.com  Sun Jan  7 07:53:51 2018
From: yalhcru at gmail.com (B Watson)
Date: Sun, 7 Jan 2018 02:53:51 -0500
Subject: [Slackbuilds-users] fpc and ptop conflict
In-Reply-To: <e84f7693-7875-dd9a-d6f0-b75e70626d50@slackbuilds.org>
References: <CAN1hMuCL1zfGce2t5UarDvd4GxtwH_PSGdQ1e39--5MkHXxBtQ@mail.gmail.com>
 <e84f7693-7875-dd9a-d6f0-b75e70626d50@slackbuilds.org>
Message-ID: <CAN1hMuBYArE8P+dkTQbp39AkGa3NKzeDM41WGF=Q1eri+zp=vg@mail.gmail.com>

On 1/6/18, Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:
>
> It's now done on my branch
>
> sorry that it got lost on my inbox

I'm impressed at your attention span, 2 months is forever :)

From kingbeowulf at gmail.com  Sun Jan  7 08:07:29 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 7 Jan 2018 00:07:29 -0800
Subject: [Slackbuilds-users] Frostwire is orphaned
In-Reply-To: <3ae4505e-deac-1265-677e-ad3917238d9d@sdf.org>
References: <ed9bf21f-ae7a-676d-f442-263faf5a7fa8@gmail.com>
 <3ae4505e-deac-1265-677e-ad3917238d9d@sdf.org>
Message-ID: <a524a359-eb7b-18ae-76ba-71a140b7134c@gmail.com>

On 01/06/2018 11:40 PM, Donald Cooley wrote:
> On 01/07/2018 01:06 AM, King Beowulf wrote:
>> FYI, just another reminder: I have dropped support for Frostwire. 

 ...
> 
> I'll take this one

SOLD!

-Ed

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

From cnguyenminhtan at free.fr  Sun Jan  7 08:23:43 2018
From: cnguyenminhtan at free.fr (Christophe Nguyen)
Date: Sun, 7 Jan 2018 09:23:43 +0100
Subject: [Slackbuilds-users] kmymoney
In-Reply-To: <ac6e4a6e-6653-a1c2-c0f5-8772bc6109c2@gmail.com>
References: <ac6e4a6e-6653-a1c2-c0f5-8772bc6109c2@gmail.com>
Message-ID: <51308443-025e-2e56-d070-f4a693d67441@free.fr>

Le 06/01/2018 ? 21:41, John Yost a ?crit?:
> the kymoney.desktop file seems to have disappeared with today's update
> to kmymoney-4.8.1.1
>
> A reinstall of 4.8.0 returns the missing file
> sorry for the double email
>
> thanks
> John
>
>
>
> _______________________________________________
> 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/
>
John,

In the new version, the Kmymoney desktop file was renamed from 
kmymoney.desktop to org.kde.kmymoney.desktop.

If you have a shortcut on your desktop or your dashboard, delete it and 
recreate it using the KDE menu entry (Kmymoney is still in Office sub-menu).

Regards,

Christophe Nguyen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180107/9c7dc407/attachment.html>

From yalhcru at gmail.com  Sun Jan  7 08:34:30 2018
From: yalhcru at gmail.com (B Watson)
Date: Sun, 7 Jan 2018 03:34:30 -0500
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <20180107133307.GB1245@hili.localdomain>
References: <20180107133307.GB1245@hili.localdomain>
Message-ID: <CAN1hMuCQHs3JEJ5LhfKbg2E4wVwFvfdY1hJvnbCTqWqnjFDOew@mail.gmail.com>

On 1/6/18, Peter Wang <novalazy at gmail.com> wrote:

> libraries/allegro4

I'll take this one, 2 of my builds depend on it.

> system/oldschool-pc-fonts

I'll take this one because 'retro' is kind of an interest of mine.

From yth at ythogtha.org  Sun Jan  7 08:47:58 2018
From: yth at ythogtha.org (Arnaud)
Date: Sun, 07 Jan 2018 09:47:58 +0100
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <20180107133307.GB1245@hili.localdomain>
References: <20180107133307.GB1245@hili.localdomain>
Message-ID: <18E264C1-7511-43E1-A15A-9A84A18CA699@ythogtha.org>

Le 7 janvier 2018 03:33:07 GMT+01:00, Peter Wang <novalazy at gmail.com> a ?crit :
>Hi,
>
>I am giving up maintainership of my scripts:
>
>desktop/xfce4-cpugraph-plugin
>development/latrace
>development/valgrind
>libraries/allegro4
>misc/tal
>office/pandoc
>system/oldschool-pc-fonts
>
>Please take care of my babies.
>
>Peter
>_______________________________________________
>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/

I'll take allegro4 since I already maintain allegro5.

Yth
-- 
Envoy? de mon appareil Android avec K-9 Mail. Veuillez excuser ma bri?vet?.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180107/de401bad/attachment.html>

From yth at ythogtha.org  Sun Jan  7 08:49:25 2018
From: yth at ythogtha.org (Arnaud)
Date: Sun, 07 Jan 2018 09:49:25 +0100
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <CAN1hMuCQHs3JEJ5LhfKbg2E4wVwFvfdY1hJvnbCTqWqnjFDOew@mail.gmail.com>
References: <20180107133307.GB1245@hili.localdomain>
 <CAN1hMuCQHs3JEJ5LhfKbg2E4wVwFvfdY1hJvnbCTqWqnjFDOew@mail.gmail.com>
Message-ID: <04120402-9CC6-4686-93F8-26A1F7A9DD3A@ythogtha.org>

Le 7 janvier 2018 09:34:30 GMT+01:00, B Watson <yalhcru at gmail.com> a ?crit :
>On 1/6/18, Peter Wang <novalazy at gmail.com> wrote:
>
>> libraries/allegro4
>
>I'll take this one, 2 of my builds depend on it.
>
>> system/oldschool-pc-fonts
>
>I'll take this one because 'retro' is kind of an interest of mine.
>_______________________________________________
>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/

Ok, I'll leave allegro4 to you ??

Yth.
-- 
Envoy? de mon appareil Android avec K-9 Mail. Veuillez excuser ma bri?vet?.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180107/a48cdbeb/attachment.html>

From baildon.research at googlemail.com  Sun Jan  7 10:54:55 2018
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 7 Jan 2018 10:54:55 +0000
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <20180107133307.GB1245@hili.localdomain>
References: <20180107133307.GB1245@hili.localdomain>
Message-ID: <CAMt7G9R778f4V8=aKmMrYr2ibxLRnQEZkcXtd_m-eFKk3xw2nw@mail.gmail.com>

On 7 January 2018 at 02:33, Peter Wang <novalazy at gmail.com> wrote:
> Hi,
>
> I am giving up maintainership of my scripts:
>
> Please take care of my babies.
>
> Peter

Someone should say, thank you for your babies :)

-D.

From alik at ejik.org  Sun Jan  7 11:00:31 2018
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sun, 07 Jan 2018 14:00:31 +0300
Subject: [Slackbuilds-users] gajim
In-Reply-To: <c00a14f4-2c11-fa3c-66da-b91b29759dae@slackbuilds.org>
References: <1515272301.3677189.1226508384.3EC2A72D@webmail.messagingengine.com>
 <c00a14f4-2c11-fa3c-66da-b91b29759dae@slackbuilds.org>
Message-ID: <1515322831.3905178.1226877248.2876C942@webmail.messagingengine.com>

On Sun, Jan 7, 2018, at 02:56, Willy Sudiarto Raharjo wrote:
> > Today update broke gajim. The simplest way to repair is to bump the
> > gajim version to 0.16.9 and the python-nbxmpp version to 0.6.2.
> 
> Which part of gajim is broken after the update?
> is it build time or run time?

Run time. I didn't preserve the error message, but it was about "OpenSSL.rand"
and the gajim changelog for 0.16.9 reads:
Remove usage of deprecated OpenSSL.rand

Maybe the problem is that "the deprecated OpenSSL.rand module" was
removed from pyOpenSSL (in ver. 17.3.0).

Best regards,
Alexander

From Jim.Diamond at acadiau.ca  Sun Jan  7 11:07:36 2018
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Sun, 7 Jan 2018 07:07:36 -0400
Subject: [Slackbuilds-users] skypeforlinux
In-Reply-To: <1515267445.3653554.1226464720.3B3B44E4@webmail.messagingengine.com>
References: <20180106160808.GA16181@jdiamond-mb.acadiau.ca>
 <1515267445.3653554.1226464720.3B3B44E4@webmail.messagingengine.com>
Message-ID: <20180107110736.GA7895@jdiamond-mb.acadiau.ca>

On Sat, Jan  6, 2018 at 22:37 (+0300), Alexander Verbovetsky wrote:

> Hello,

>> the SBo version is 8.11.0.4 but there are 5 newer versions at
>> repo.skype.com/deb/pool/main/s/skypeforlinux/.

>> Time for a bump?

> There are "stable" versions listed here:
> https://repo.skype.com/deb/dists/stable/main/binary-amd64/Packages

> and "unstable" ones listed here:
> https://repo.skype.com/deb/dists/unstable/main/binary-amd64/Packages

> 8.11.0.4 is the latest stable version. Also, this is the version
> distributed via https://www.skype.com/en/get-skype/.

Alexander,

thanks very much for that information.

                                Jim

From sb at rbn.im  Sun Jan  7 12:54:21 2018
From: sb at rbn.im (Ruben Schuller)
Date: Sun, 7 Jan 2018 13:54:21 +0100
Subject: [Slackbuilds-users] gajim
In-Reply-To: <1515322831.3905178.1226877248.2876C942@webmail.messagingengine.com>
References: <1515272301.3677189.1226508384.3EC2A72D@webmail.messagingengine.com>
 <c00a14f4-2c11-fa3c-66da-b91b29759dae@slackbuilds.org>
 <1515322831.3905178.1226877248.2876C942@webmail.messagingengine.com>
Message-ID: <20180107135421.592f2b1a@kiwi.kuchen>

Hi!

2018-01-07 14:00 Alexander Verbovetsky <alik at ejik.org>

> On Sun, Jan 7, 2018, at 02:56, Willy Sudiarto Raharjo wrote:
> > > Today update broke gajim. The simplest way to repair is to bump
> > > the gajim version to 0.16.9 and the python-nbxmpp version to
> > > 0.6.2.  
> > 
> > Which part of gajim is broken after the update?
> > is it build time or run time?  
> 
> Run time. I didn't preserve the error message, but it was about
> "OpenSSL.rand" and the gajim changelog for 0.16.9 reads:
> Remove usage of deprecated OpenSSL.rand
> 
> Maybe the problem is that "the deprecated OpenSSL.rand module" was
> removed from pyOpenSSL (in ver. 17.3.0).

Thanks for the notice! I haven't updated pyOpenSSL yet, so I missed
this error.
 
I've just prepared an updated version of gajim and python-nbxmpp and
submitted it.

Ruben

From alanians at telus.net  Sun Jan  7 13:20:39 2018
From: alanians at telus.net (Alan Ianson)
Date: Sun, 7 Jan 2018 05:20:39 -0800
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
Message-ID: <20180107052039.48ec2f3263bc844cf9f969db@telus.net>

On Sun, 7 Jan 2018 13:33:07 +1100
Peter Wang <novalazy at gmail.com> wrote:

> Hi,
> 
> I am giving up maintainership of my scripts:
> 
> desktop/xfce4-cpugraph-plugin

I'll take this one.

> Please take care of my babies.

I will do my best.. :)

From atelszewski at gmail.com  Sun Jan  7 21:16:08 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 7 Jan 2018 22:16:08 +0100
Subject: [Slackbuilds-users] intel-microcode
Message-ID: <9b787114-be51-e741-d934-7422a5330c65@gmail.com>

Hi,

I see the rush in updating Intel microcode all over the place.
Yet, I can only find version 20171117 on Intel site.

Has anyone any idea what is happening?

I'm happy to update intel-microcode.SlackBuild as soon as the update is 
available upstream.

Thanks!

-- 
Best regards,
Andrzej Telszewski

From kingbeowulf at gmail.com  Sun Jan  7 22:13:07 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 7 Jan 2018 14:13:07 -0800
Subject: [Slackbuilds-users] trying to fix sage-8.1 build script - advice
 needed
Message-ID: <ec86788b-9932-38cb-5217-c2a69bd8c727@gmail.com>

I'm attempting to upgrade and fix a few issue with the sage build.
However, upstream seems to think that no one wants to compile a
redistributable install package.  The way sage works is:

1. Download prebuilt binary, extract it somewhere, rename directory if
desired, set a few shell variables, symlink, run.  Once run and the
binaries patched, you can't move it.

2. Download source, compile somewhere, AND DON'T MOVE IT!

In other words, upstream does not support moving to a new directory
after compiling.  SAGEROOT seems to get hard coded.  Thus, our normal
procedure of building in /tmp/SBo/sage-x.y.z creates binaries that can
only be run from /tmp/SBo/sage-x.y.z and moving the tree to /opt/sage
results in an error message

ERROR: The Sage installation tree has moved
from /tmp/SBO/sage-8,1
  to /opt/sage

stating that you cannot move the compiled tree to a new location -
either use prebuilt binaries or recompile.

Now, the question is: How does upstream create relocatable binaries?
What is the patch process?

Otherwise, we will have to compile in /opt/sage and then create a
package from that tree location.

If anyone has any ideas, let me know.
-Ed

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

From rworkman at slackbuilds.org  Sun Jan  7 22:53:12 2018
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 7 Jan 2018 16:53:12 -0600
Subject: [Slackbuilds-users] trying to fix sage-8.1 build script -
 advice needed
In-Reply-To: <ec86788b-9932-38cb-5217-c2a69bd8c727@gmail.com>
References: <ec86788b-9932-38cb-5217-c2a69bd8c727@gmail.com>
Message-ID: <20180107165312.42ebe0d6@home.rlworkman.net>

On Sun, 7 Jan 2018 14:13:07 -0800
King Beowulf <kingbeowulf at gmail.com> wrote:

> I'm attempting to upgrade and fix a few issue with the sage build.
> However, upstream seems to think that no one wants to compile a
> redistributable install package.  The way sage works is:
> 
> 1. Download prebuilt binary, extract it somewhere, rename directory if
> desired, set a few shell variables, symlink, run.  Once run and the
> binaries patched, you can't move it.
> 
> 2. Download source, compile somewhere, AND DON'T MOVE IT!
> 
> In other words, upstream does not support moving to a new directory
> after compiling.  SAGEROOT seems to get hard coded.  Thus, our normal
> procedure of building in /tmp/SBo/sage-x.y.z creates binaries that can
> only be run from /tmp/SBo/sage-x.y.z and moving the tree to /opt/sage
> results in an error message
> 
> ERROR: The Sage installation tree has moved
> from /tmp/SBO/sage-8,1
>   to /opt/sage
> 
> stating that you cannot move the compiled tree to a new location -
> either use prebuilt binaries or recompile.
> 
> Now, the question is: How does upstream create relocatable binaries?
> What is the patch process?
> 
> Otherwise, we will have to compile in /opt/sage and then create a
> package from that tree location.
> 
> If anyone has any ideas, let me know.
> -Ed


If you can figure out where/how it's hardcode, patchelf could
perhaps fix that.

-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/20180107/a60065b8/attachment.asc>

From kingbeowulf at gmail.com  Sun Jan  7 23:28:20 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 7 Jan 2018 15:28:20 -0800
Subject: [Slackbuilds-users] trying to fix sage-8.1 build script -
 advice needed
In-Reply-To: <20180107165312.42ebe0d6@home.rlworkman.net>
References: <ec86788b-9932-38cb-5217-c2a69bd8c727@gmail.com>
 <20180107165312.42ebe0d6@home.rlworkman.net>
Message-ID: <43d4f712-3680-dfa8-c803-864c64309e6e@gmail.com>

On 01/07/2018 02:53 PM, Robby Workman wrote:
> On Sun, 7 Jan 2018 14:13:07 -0800
> King Beowulf <kingbeowulf at gmail.com> wrote:
> 
>> I'm attempting to upgrade and fix a few issue with the sage build.
>> However, upstream seems to think that no one wants to compile a
>> redistributable install package.  The way sage works is:
>>
>> 1. Download prebuilt binary, extract it somewhere, rename directory if
>> desired, set a few shell variables, symlink, run.  Once run and the
>> binaries patched, you can't move it.
>>
>> 2. Download source, compile somewhere, AND DON'T MOVE IT!
>>
>> In other words, upstream does not support moving to a new directory
>> after compiling.  SAGEROOT seems to get hard coded.  Thus, our normal
>> procedure of building in /tmp/SBo/sage-x.y.z creates binaries that can
>> only be run from /tmp/SBo/sage-x.y.z and moving the tree to /opt/sage
>> results in an error message
>>
>> ERROR: The Sage installation tree has moved
>> from /tmp/SBO/sage-8,1
>>   to /opt/sage
>>
>> stating that you cannot move the compiled tree to a new location -
>> either use prebuilt binaries or recompile.
>>
>> Now, the question is: How does upstream create relocatable binaries?
>> What is the patch process?
>>
>> Otherwise, we will have to compile in /opt/sage and then create a
>> package from that tree location.
>>
>> If anyone has any ideas, let me know.
>> -Ed
> 
> 
> If you can figure out where/how it's hardcode, patchelf could
> perhaps fix that.
> 
> -RW
> 

There are dozens of files.  the 'sage' start up script refers to a
relocate-once.py that is not included in the source but is included with
the pre-built binaries.  I haven't figured out how to get it to run yet.
It patches a few files then errors out. The search for string of length
"/tmp/SBo/sage-8.1' may be too short to hold the new paths?

(btw, my python-fu is weak...)

-Ed


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

From willysr at slackbuilds.org  Mon Jan  8 01:10:47 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 8 Jan 2018 08:10:47 +0700
Subject: [Slackbuilds-users] trying to fix sage-8.1 build script -
 advice needed
In-Reply-To: <ec86788b-9932-38cb-5217-c2a69bd8c727@gmail.com>
References: <ec86788b-9932-38cb-5217-c2a69bd8c727@gmail.com>
Message-ID: <9ae27dfa-dcdd-6943-738c-d3a36cfec58b@slackbuilds.org>

> I'm attempting to upgrade and fix a few issue with the sage build.
> However, upstream seems to think that no one wants to compile a
> redistributable install package.  The way sage works is:
> 
> 1. Download prebuilt binary, extract it somewhere, rename directory if
> desired, set a few shell variables, symlink, run.  Once run and the
> binaries patched, you can't move it.
> 
> 2. Download source, compile somewhere, AND DON'T MOVE IT!
> 
> In other words, upstream does not support moving to a new directory
> after compiling.  SAGEROOT seems to get hard coded.  Thus, our normal
> procedure of building in /tmp/SBo/sage-x.y.z creates binaries that can
> only be run from /tmp/SBo/sage-x.y.z and moving the tree to /opt/sage
> results in an error message
> 
> ERROR: The Sage installation tree has moved
> from /tmp/SBO/sage-8,1
>   to /opt/sage
> 
> stating that you cannot move the compiled tree to a new location -
> either use prebuilt binaries or recompile.
> 
> Now, the question is: How does upstream create relocatable binaries?
> What is the patch process?
> 
> Otherwise, we will have to compile in /opt/sage and then create a
> package from that tree location.

During my time as a maintainer for sage, it does built everything into
/tmp/SBo/sage-xx and then during installation, it would move everything
from /tmp/SBo to /op/sage because the script in doinst.sh will do so.
I have tested the installation and it worked fine.

I don't know about 8.1 because i haven't tried it yet


-- 
Willy Sudiarto Raharjo

-------------- 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/20180108/a3986903/attachment-0001.asc>

From dchmelik at gmail.com  Mon Jan  8 01:31:36 2018
From: dchmelik at gmail.com (David Melik)
Date: Sun, 7 Jan 2018 17:31:36 -0800
Subject: [Slackbuilds-users] intel-microcode
Message-ID: <d3465bd2-6c41-6908-c0fd-88b23e9b757e@gmail.com>

On Sun, 07 Jan 2018 22:16:08 +0100, Andrzej Telszewski wrote:
 > [...]? I see the rush in updating Intel microcode all over the place.
 > Yet, I can only find version 20171117 on Intel site.
 >
 > Has anyone any idea what is happening?
 >
 > I'm happy to update intel-microcode.SlackBuild as soon as the update is
 > available upstream. [...]

Probably recent serious (insecurity) hardware bugs discovered in CPUs 
from last decades.

If I install intel-microcode (CPU from a year or two ago) can I still 
use Management Engine Cleaner? ( https://github.com/corna/me_cleaner .)? 
Now that the truth about Intel running a secret entire other CPU with 
operating system in your CPU has come out, not sure they're going to 
still let ME Cleaner work, and also, if ME Cleaner is not perfected yet, 
what a potential side effects may be.

Another topic, but as a subscriber, can't I still post (same email 
address) here on Gmane, or I have to email now?



From dchmelik at gmail.com  Mon Jan  8 01:55:30 2018
From: dchmelik at gmail.com (David Melik)
Date: Sun, 7 Jan 2018 17:55:30 -0800
Subject: [Slackbuilds-users] trying to fix sage-8.1 build script -
 advice needed
Message-ID: <866f9df1-6995-9706-419b-1b8bb98b4a63@gmail.com>

On Sun, 07 Jan 2018 14:13:07 -0800, King Beowulf wrote:

 > I'm attempting to upgrade and fix a few issue with the sage build.
 > However, upstream seems to think that no one wants to compile a
 > redistributable install package.? The way sage works is:
 >
 > 1. Download prebuilt binary, extract it somewhere, rename directory if
 > desired, set a few shell variables, symlink, run.? Once run and the
 > binaries patched, you can't move it.
 >
 > 2. Download source, compile somewhere, AND DON'T MOVE IT!
 >
 > In other words, upstream does not support moving to a new directory
 > after compiling.? SAGEROOT seems to get hard coded.? Thus, our normal
 > procedure of building in /tmp/SBo/sage-x.y.z creates binaries that can
 > only be run from /tmp/SBo/sage-x.y.z and moving the tree to /opt/sage
 > results in an error message
 >
 > ERROR: The Sage installation tree has moved from /tmp/SBO/sage-8,1
 >?? to /opt/sage
 >
 > stating that you cannot move the compiled tree to a new location -
 > either use prebuilt binaries or recompile.
 >
 > Now, the question is: How does upstream create relocatable binaries?
 > What is the patch process?
 >
 > Otherwise, we will have to compile in /opt/sage and then create a
 > package from that tree location.
 >
 > If anyone has any ideas, let me know.
 > -Ed

SAGE really has many issues, and I'd still like to use it, but am 
skeptical whether it's worth anyone making a SlackBuild until the SAGE 
programmers take most users into consideration.

One of my mathematics professors suggested it years ago as a FLOSS 
alternative to Mathematica.? I installed it (maybe beforehand,) noticed 
SAGE could only be set up as if you're running it on some 
organization's/company's server, i.e., runs as a daemon with a password, 
so I didn't use it.

If SAGE programmers think even 99.9% (roughly 1/1000 university students 
major in math) of mathematicians are going to use it that way, its 
programmers seem to have a significant mental challenge (debilitating 
usability) thinking how most people will use it: as curious/student 
people, etc. (including before college, and before majoring, then 
probably fewer than 1/1000 get a minor/AS, fewer BS, fewer MS but may or 
not start instructing/teaching, and even fewer may get PhD and be a 
professor.)? I'd estimate almost no one in the percentage of users will 
want to be running it as a software server on a hardware server for an 
organization, than just a PC application.

I know SAGE once was the most powerful FLOSS alternative, if you went 
through the hassle of installing it.? Now, there are others, but I'd 
still like to try SAGE.? They just need to realize, not just people 
doing research in private at mathematics departments, nor companies 
doing secret research & development, are going to even be most the 
users, whom most don't want to have to use password, let alone leave it 
on (system resources) or (re)start daemon just to access interface.? 
Also, for people wanting to run open public math software servers, it's 
a hassle preventing most curious people wanting to try.

Seems to be why the rest of the setup is way it is also.? If someone 
else hadn't, maybe I thought of making a SAGE SlackBuild five or more 
years ago, then thought, I'm not going to bother; made Mathics one 
instead... which probably isn't as powerful, but at least user-friendly 
(unlike SAGE.)

You could try doing/documenting an alternative build that may or not be 
able to be automated.? One that can't is Oracle's Java, because they're 
being copyright trolls (can't download source code with wget, can't run 
in sbopkg.)? Maybe you could do something like chroot or similar easiest 
things (overlayfs(?)... haven't tried it,) not harder/overcomplicated 
things (virtual machines, Docker) and maybe there'd be an easy way for 
everyone to install.? Even something such as they setup/install a 
particular thing (chroot) and you run a script, but I forgot if extra 
scripts are allowed.? But, if it's chroot, I guess you can build in 
there, won't necessarily need another script.


From atelszewski at gmail.com  Mon Jan  8 02:00:42 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 8 Jan 2018 03:00:42 +0100
Subject: [Slackbuilds-users] intel-microcode
In-Reply-To: <d3465bd2-6c41-6908-c0fd-88b23e9b757e@gmail.com>
References: <d3465bd2-6c41-6908-c0fd-88b23e9b757e@gmail.com>
Message-ID: <ba537195-31bc-84d5-dda6-266491f3ddea@gmail.com>

On 08/01/18 02:31, David Melik wrote:
> On Sun, 07 Jan 2018 22:16:08 +0100, Andrzej Telszewski wrote:
>  > [...]? I see the rush in updating Intel microcode all over the place.
>  > Yet, I can only find version 20171117 on Intel site.
>  >
>  > Has anyone any idea what is happening?
>  >
>  > I'm happy to update intel-microcode.SlackBuild as soon as the update is
>  > available upstream. [...]
> 
> Probably recent serious (insecurity) hardware bugs discovered in CPUs 
> from last decades.

That I know ;-)

I just don't know where they get the updated microcode file from.
I saw Intel released BIOS update for my machine, with the only change 
being the microcode updated.
But I haven't seen any microcode file update on Intel site.

> 
> If I install intel-microcode (CPU from a year or two ago) can I still 
> use Management Engine Cleaner? ( https://github.com/corna/me_cleaner .) 
> Now that the truth about Intel running a secret entire other CPU with 
> operating system in your CPU has come out, not sure they're going to 
> still let ME Cleaner work, and also, if ME Cleaner is not perfected yet, 
> what a potential side effects may be.
> 

I don't think the two are related.
If you remove ME and apply microcode from Linux, then the microcode 
would have to somehow enable back the ME. Which might be hard if you 
removed the ME code physically from the Flash chip ;)

There's also possibility of disabling ME by flipping a bit responsible 
for it - in that case you don't physically remove the code from the 
chip, but you tell the system to disable ME.

If I remember correctly, this bit is located in the Flash chip for the 
BIOS/UEFI.

Microcode update has no possibility of programming the Flash.
Microcode is code that is sent to the CPU to basically perform CPU 
reconfiguration. And microcode is volatile, meaning it has to be sent to 
the CPU every boot. It is done either by BIOS/UEFI or Linux.


> Another topic, but as a subscriber, can't I still post (same email 
> address) here on Gmane, or I have to email now?
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 


-- 
Best regards,
Andrzej Telszewski

From fernando.lopezjr at gmail.com  Mon Jan  8 03:04:44 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sun, 7 Jan 2018 20:04:44 -0700
Subject: [Slackbuilds-users] HELP! with new package.
Message-ID: <CALrQ46BaZV9+76kyQbYEDKaNqEznmyOiTH3dUtsQU0R2OdiUpQ@mail.gmail.com>

can you guys check my .SlackBuild file and tell me everything i did wrong!


thank you. =)

*git repo:*
https://github.com/openvizsla/ov_ftdi/tree/master/software/host

*dropbox download links:*
https://www.dropbox.com/s/qvjs0t8wwmhsyv4/ov_ftdi-master.tar.gz?dl=0

https://www.dropbox.com/s/kt9qlfw1k6wrine/ov_ftdi-1f980e821659d87bb0ed704e54ebb256a0547d92.tar.gz?dl=0

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180107/66190722/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ov-ftdi.tar.bz2
Type: application/x-bzip2
Size: 2564 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180107/66190722/attachment.bz2>

From kingbeowulf at gmail.com  Mon Jan  8 04:01:45 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 7 Jan 2018 20:01:45 -0800
Subject: [Slackbuilds-users] trying to fix sage-8.1 build script -
 advice needed
In-Reply-To: <9ae27dfa-dcdd-6943-738c-d3a36cfec58b@slackbuilds.org>
References: <ec86788b-9932-38cb-5217-c2a69bd8c727@gmail.com>
 <9ae27dfa-dcdd-6943-738c-d3a36cfec58b@slackbuilds.org>
Message-ID: <a46dd44e-0a42-7099-41c2-94f549c7eed2@gmail.com>

On 01/07/2018 05:10 PM, Willy Sudiarto Raharjo wrote:
>> I'm attempting to upgrade and fix a few issue with the sage build.
>> However, upstream seems to think that no one wants to compile a
>> redistributable install package.  The way sage works is:
>>
>> 1. Download prebuilt binary, extract it somewhere, rename directory if
>> desired, set a few shell variables, symlink, run.  Once run and the
>> binaries patched, you can't move it.
>>
>> 2. Download source, compile somewhere, AND DON'T MOVE IT!
>>
>> In other words, upstream does not support moving to a new directory
>> after compiling.  SAGEROOT seems to get hard coded.  Thus, our normal
>> procedure of building in /tmp/SBo/sage-x.y.z creates binaries that can
>> only be run from /tmp/SBo/sage-x.y.z and moving the tree to /opt/sage
>> results in an error message
>>
>> ERROR: The Sage installation tree has moved
>> from /tmp/SBO/sage-8,1
>>   to /opt/sage
>>
>> stating that you cannot move the compiled tree to a new location -
>> either use prebuilt binaries or recompile.
>>
>> Now, the question is: How does upstream create relocatable binaries?
>> What is the patch process?
>>
>> Otherwise, we will have to compile in /opt/sage and then create a
>> package from that tree location.
> 
> During my time as a maintainer for sage, it does built everything into
> /tmp/SBo/sage-xx and then during installation, it would move everything
> from /tmp/SBo to /op/sage because the script in doinst.sh will do so.
> I have tested the installation and it worked fine.
> 
> I don't know about 8.1 because i haven't tried it yet
> 

That's what I thought as well and it worked for 8.0. 8.1 seems to hard
code all SAGEROOT everywhere.  Running from doinst.sh as root to have
sage reset the paths no longer works.

-Ed



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

From kingbeowulf at gmail.com  Mon Jan  8 04:16:23 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 7 Jan 2018 20:16:23 -0800
Subject: [Slackbuilds-users] trying to fix sage-8.1 build script -
 advice needed
In-Reply-To: <866f9df1-6995-9706-419b-1b8bb98b4a63@gmail.com>
References: <866f9df1-6995-9706-419b-1b8bb98b4a63@gmail.com>
Message-ID: <987de6a5-928a-05ca-44aa-37b84c9cfa9b@gmail.com>

On 01/07/2018 05:55 PM, David Melik wrote:
> On Sun, 07 Jan 2018 14:13:07 -0800, King Beowulf wrote:
> 
>> I'm attempting to upgrade and fix a few issue with the sage build.
>> However, upstream seems to think that no one wants to compile a
>> redistributable install package. 
 ...snip---
>>
>> If anyone has any ideas, let me know.
>> -Ed
> 
> SAGE really has many issues, and I'd still like to use it, but am
> skeptical whether it's worth anyone making a SlackBuild until the SAGE
> programmers take most users into consideration.
> 
---snip---

I'm glad I'm not the only one who thinks upstream has been drinking the
wrong cool-aid. 'forking' 'rump' holes....

Compiling and packaging worked before with a bit of gyration, but
upstream changed somnthing, especially with this non-root compile fetish
of theirs.  Now, in the the prebuilt binaries, they have a python script
that will patch all the dozens of hard coded files:

p = SearchAndReplace(ROOT_PATH,
'/mnt/disk/home/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeq',
DESTINATION)

Maybe I have to just set SAGEROOT to /tmp/SBo/sage-8.1BLAHBLABLAH.... to
match the number of bytes they use so that the script won't crash.

Or extact and compile in '/opt/sage' and create a package there then
delete, but that might upset some of our more sensitive and pedantic admins!

-Ed


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

From jebrhansen+SBo at gmail.com  Mon Jan  8 04:41:43 2018
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Mon, 08 Jan 2018 04:41:43 +0000
Subject: [Slackbuilds-users] trying to fix sage-8.1 build script -
 advice needed
In-Reply-To: <987de6a5-928a-05ca-44aa-37b84c9cfa9b@gmail.com>
References: <866f9df1-6995-9706-419b-1b8bb98b4a63@gmail.com>
 <987de6a5-928a-05ca-44aa-37b84c9cfa9b@gmail.com>
Message-ID: <CANi9qSuOd6gmAMHH1ZnPELZQK2eDMRSBe8CZd3-KkGAYSzG2dA@mail.gmail.com>

On Sun, Jan 7, 2018, 11:16 PM King Beowulf <kingbeowulf at gmail.com> wrote:

> On 01/07/2018 05:55 PM, David Melik wrote:
> > On Sun, 07 Jan 2018 14:13:07 -0800, King Beowulf wrote:
> >
> >> I'm attempting to upgrade and fix a few issue with the sage build.
> >> However, upstream seems to think that no one wants to compile a
> >> redistributable install package.
>  ...snip---
> >>
> >> If anyone has any ideas, let me know.
> >> -Ed
> >
> > SAGE really has many issues, and I'd still like to use it, but am
> > skeptical whether it's worth anyone making a SlackBuild until the SAGE
> > programmers take most users into consideration.
> >
> ---snip---
>
> I'm glad I'm not the only one who thinks upstream has been drinking the
> wrong cool-aid. 'forking' 'rump' holes....
>
> Compiling and packaging worked before with a bit of gyration, but
> upstream changed somnthing, especially with this non-root compile fetish
> of theirs.  Now, in the the prebuilt binaries, they have a python script
> that will patch all the dozens of hard coded files:
>
> p = SearchAndReplace(ROOT_PATH,
>
> '/mnt/disk/home/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeq',
> DESTINATION)
>
> Maybe I have to just set SAGEROOT to /tmp/SBo/sage-8.1BLAHBLABLAH.... to
> match the number of bytes they use so that the script won't crash.
>
> Or extact and compile in '/opt/sage' and create a package there then
> delete, but that might upset some of our more sensitive and pedantic
> admins!
>

I don't really have much experience with this (and don't use sage at all),
but could you set up the directories as needed under /tmp/SBo/package-sage/
and then just chroot it? Maybe with a bind mount for the needed system
directories (assuming it doesn't need the whole system, since that'd be a
little excessive to bind mount)? That way, once the bind mounts are
removed, the directory can be packaged up as normal.

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180108/df0b80e2/attachment.html>

From rworkman at slackbuilds.org  Mon Jan  8 05:23:56 2018
From: rworkman at slackbuilds.org (Robby Workman)
Date: Sun, 7 Jan 2018 23:23:56 -0600
Subject: [Slackbuilds-users] trying to fix sage-8.1 build script -
 advice needed
In-Reply-To: <987de6a5-928a-05ca-44aa-37b84c9cfa9b@gmail.com>
References: <866f9df1-6995-9706-419b-1b8bb98b4a63@gmail.com>
 <987de6a5-928a-05ca-44aa-37b84c9cfa9b@gmail.com>
Message-ID: <20180107232356.1fd8e153@home.rlworkman.net>

On Sun, 7 Jan 2018 20:16:23 -0800
King Beowulf <kingbeowulf at gmail.com> wrote:

> ...  Now, in the the prebuilt binaries, they have a
> python script that will patch all the dozens of hard coded files:
> 
> p = SearchAndReplace(ROOT_PATH,
> '/mnt/disk/home/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeq',
> DESTINATION)


Can you attach that entire script, please?

-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/20180107/98bfa704/attachment.asc>

From kingbeowulf at gmail.com  Mon Jan  8 06:51:44 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 7 Jan 2018 22:51:44 -0800
Subject: [Slackbuilds-users] trying to fix sage-8.1 build script -
 advice needed
In-Reply-To: <20180107232356.1fd8e153@home.rlworkman.net>
References: <866f9df1-6995-9706-419b-1b8bb98b4a63@gmail.com>
 <987de6a5-928a-05ca-44aa-37b84c9cfa9b@gmail.com>
 <20180107232356.1fd8e153@home.rlworkman.net>
Message-ID: <510d7a1c-24d5-fd4e-e63e-e1745e3228b8@gmail.com>

On 01/07/2018 09:23 PM, Robby Workman wrote:
> On Sun, 7 Jan 2018 20:16:23 -0800
> King Beowulf <kingbeowulf at gmail.com> wrote:
> 
>> ...  Now, in the the prebuilt binaries, they have a
>> python script that will patch all the dozens of hard coded files:
>>
>> p = SearchAndReplace(ROOT_PATH,
>> '/mnt/disk/home/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeq',
>> DESTINATION)
> 
> 
> Can you attach that entire script, please?
> 
> -RW
> 

It's pretty hefty at 1.6MB - relocate-once.py, so here is a link of the
build script WIP location:

http://www.linuxgalaxy.org/files/sbo-testing/14.2/academic/sage/

The script appears to patch the 1st 5 files then fails on
'/opt/sage/local/bin/ESingular' with an "AssertionError"

The package at 1.6GB, case you don't want to wait several hours for the
compile:

http://www.linuxgalaxy.org/files/sbo-testing/14.2/packages/

note that I haven't added relocate-once.py to the slackbuild yet but it
is part of the package.  Also, as long as SAGEROOT=/tmp/SBo/sage-8.1 the
program runs fine.  Once installed, just move it to that directory.

Have fun.  I'll be traveling for work next week so not sure when I can
respond.

Thanks
-Ed

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

From dchmelik at gmail.com  Mon Jan  8 11:01:37 2018
From: dchmelik at gmail.com (David Melik)
Date: Mon, 8 Jan 2018 03:01:37 -0800
Subject: [Slackbuilds-users] Elvio Basello? (SlackBuilds no longer updated)
Message-ID: <279551fb-8106-2e37-160b-8ed9ed9eed9d@gmail.com>

A couple times the last few years I tried to use Elvio Basello's 
kvirc.SlackBuild ( 
https://slackbuilds.org/repository/14.2/network/kvirc/ .)? I think I 
emailed him before, and just a few minutes ago, and this (and last?) 
time, slackware.it says something like that user doesn't exist.

His KVIRC build is now seven years old, after which a new stable version 
was released that year.

I'm wondering what happened, and, as an alternative/second IRC client, 
would like to try KVIRC again... but it's not clear Elvio is even active 
for SBo for years...

I don't like KVIRC enough that I'd attempt to continue the build if it 
became too difficult.? It's nice it has avatars, and a huge list of 
servers/networks, but most the rest of it wasn't that good, and it's 
definitely worse (one of the worst?) for IRC operator usage compared to 
HexChat and maybe others.


From baildon.research at googlemail.com  Mon Jan  8 16:09:52 2018
From: baildon.research at googlemail.com (David Spencer)
Date: Mon, 8 Jan 2018 16:09:52 +0000
Subject: [Slackbuilds-users] intel-microcode
In-Reply-To: <9b787114-be51-e741-d934-7422a5330c65@gmail.com>
References: <9b787114-be51-e741-d934-7422a5330c65@gmail.com>
Message-ID: <CAMt7G9TuCMm30UnkDg6v_ObkzCDde8k5y6xhvnFUnaQd0jfiLw@mail.gmail.com>

> I see the rush in updating Intel microcode all over the place.
> Yet, I can only find version 20171117 on Intel site.
>
> Has anyone any idea what is happening?

Some distros seem to have mysteriously got a 20171215 release, it must
have come from Intel but it is not available from Intel's page. Maybe
a bit more information is below, from the Debian bugreport.

Gentoo:
https://gitweb.gentoo.org/repo/gentoo.git/log/sys-firmware/intel-microcode

Mageia:
http://svnweb.mageia.org/packages/cauldron/microcode/

Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886367
https://sources.debian.org/src/intel-microcode/3.20171215.1/supplementary-ucode-CVE-2017-5715.d/

In particular see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886367#37
"The current plans are for stable to wait for Intel's official microcode
update pack. It is not like this set of microcode updates will get you anything
without the kernel IBRS and IPBP support, which is still being
stabilized. These updates are currently necessary for people doing the
kernel work
and for testing and stabilization.  Ditto for AMD microcode updates,
which I will upload soon now that the kernel support for loading them
has made it to Linux mainline."

So I hope this is a partial answer -- there is a supplementary set of
20171215 files circulating amongst the kernel devs so they can prepare
kernel fixes that depend on them. Those kernel fixes are not yet
ready, and 20171215 isn't useful on its own.

?\_(?)_/?
-D.

From atelszewski at gmail.com  Mon Jan  8 16:23:57 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 8 Jan 2018 17:23:57 +0100
Subject: [Slackbuilds-users] intel-microcode
In-Reply-To: <CAMt7G9TuCMm30UnkDg6v_ObkzCDde8k5y6xhvnFUnaQd0jfiLw@mail.gmail.com>
References: <9b787114-be51-e741-d934-7422a5330c65@gmail.com>
 <CAMt7G9TuCMm30UnkDg6v_ObkzCDde8k5y6xhvnFUnaQd0jfiLw@mail.gmail.com>
Message-ID: <c275f2cc-0591-0c70-7c50-608e25d9e0a6@gmail.com>

On 08/01/18 17:09, David Spencer wrote:
>> I see the rush in updating Intel microcode all over the place.
>> Yet, I can only find version 20171117 on Intel site.
>>
>> Has anyone any idea what is happening?
> 
> Some distros seem to have mysteriously got a 20171215 release, it must
> have come from Intel but it is not available from Intel's page. Maybe
> a bit more information is below, from the Debian bugreport.
> 
> Gentoo:
> https://gitweb.gentoo.org/repo/gentoo.git/log/sys-firmware/intel-microcode
> 
> Mageia:
> http://svnweb.mageia.org/packages/cauldron/microcode/
> 
> Debian:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886367
> https://sources.debian.org/src/intel-microcode/3.20171215.1/supplementary-ucode-CVE-2017-5715.d/
> 
> In particular see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886367#37
> "The current plans are for stable to wait for Intel's official microcode
> update pack. It is not like this set of microcode updates will get you anything
> without the kernel IBRS and IPBP support, which is still being
> stabilized. These updates are currently necessary for people doing the
> kernel work
> and for testing and stabilization.  Ditto for AMD microcode updates,
> which I will upload soon now that the kernel support for loading them
> has made it to Linux mainline."
> 
> So I hope this is a partial answer -- there is a supplementary set of
> 20171215 files circulating amongst the kernel devs so they can prepare
> kernel fixes that depend on them. Those kernel fixes are not yet
> ready, and 20171215 isn't useful on its own.
> 
> ?\_(?)_/?
> -D.

Well appreciated David, thanks!

-- 
Best regards,
Andrzej Telszewski

From yalhcru at gmail.com  Tue Jan  9 01:40:17 2018
From: yalhcru at gmail.com (B Watson)
Date: Mon, 8 Jan 2018 20:40:17 -0500
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <04120402-9CC6-4686-93F8-26A1F7A9DD3A@ythogtha.org>
References: <20180107133307.GB1245@hili.localdomain>
 <CAN1hMuCQHs3JEJ5LhfKbg2E4wVwFvfdY1hJvnbCTqWqnjFDOew@mail.gmail.com>
 <04120402-9CC6-4686-93F8-26A1F7A9DD3A@ythogtha.org>
Message-ID: <CAN1hMuD_jB5ftofVNOZeOZw9Hay7-GQNT0pap_boSYG=Fri2Gw@mail.gmail.com>

On 1/7/18, Arnaud <yth at ythogtha.org> wrote:
>
> Ok, I'll leave allegro4 to you

Thanks. Just pushed update to git, all I did was change the maintainer
stuff in the .info file and s/i486/i586/ in the script.

From yalhcru at gmail.com  Tue Jan  9 01:52:09 2018
From: yalhcru at gmail.com (B Watson)
Date: Mon, 8 Jan 2018 20:52:09 -0500
Subject: [Slackbuilds-users] lmello's svgalib stuff
Message-ID: <CAN1hMuA5OvMwHG2-v1ZvfSX0Y-rNzFLzw4A_bv0pPeX8_AUSdA@mail.gmail.com>

Looking at the list of abandoned builds, I see these two:

graphics/svp: svp (A ghostscript front end for svgalib)
graphics/zgv: zgv (svgalib picture viewer)

I have memories of using zgv in the 90s, but I haven't gotten svgalib
to do anything but crash with any video card made this century.

Does anyone have a working svgalib setup on fairly modern hardware? Is
it even possible?

zgv can be built for SDL instead of svgalib, which might allow it to
work with the framebuffer console. If this actually works, would there
be any benefit in converting the zgv build to use it instead of svgalib?
We already have some decent framebuffer image viewers, including fbi.

From rshepard at appl-ecosys.com  Tue Jan  9 15:32:03 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 9 Jan 2018 07:32:03 -0800 (PST)
Subject: [Slackbuilds-users] How best to contact Slackware devs?
Message-ID: <alpine.LNX.2.20.1801090725160.25400@salmo.appl-ecosys.com>

   Since upgrading to 14.2 I've had an issue with my MUA, alpine-2.20. When a
message is forwarded the subject line is not copied from the original
message to the one to be forwarded. This does not affect replying to
messages.

   A subscriber to the alpine-info mail list found the problem and is fixed by
replacing strncpy by memmove. I'd like to make Pat and crew aware of this
issue.

   Test case using strncpy:

$ ./forward 
1: Test Subject
2: Test Subject
3: Test Subject
4: 
5:

   Test case using memmove:

$ ./forward 
1: Test Subject
2: Test Subject
3: Test Subject
4: Test Subject (fwd)
5: Test Subject (fwd)

   Source code for both sent upon request.

Rich

From dave at dawoodfall.net  Tue Jan  9 15:37:21 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Tue, 9 Jan 2018 15:37:21 +0000
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <alpine.LNX.2.20.1801090725160.25400@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801090725160.25400@salmo.appl-ecosys.com>
Message-ID: <20180109153721.GR5554@Blackswan>

>  Since upgrading to 14.2 I've had an issue with my MUA, alpine-2.20. When a
>message is forwarded the subject line is not copied from the original
>message to the one to be forwarded. This does not affect replying to
>messages.
>
>  A subscriber to the alpine-info mail list found the problem and is fixed by
>replacing strncpy by memmove. I'd like to make Pat and crew aware of this
>issue.
>
>  Test case using strncpy:
>
>$ ./forward 1: Test Subject
>2: Test Subject
>3: Test Subject
>4: 5:
>
>  Test case using memmove:
>
>$ ./forward 1: Test Subject
>2: Test Subject
>3: Test Subject
>4: Test Subject (fwd)
>5: Test Subject (fwd)
>
>  Source code for both sent upon request.
>
>Rich

This sounds more like an issue for the alpine devs. Have you looked to
see if a fix has been made for this issue? If not then it's worth
opening a bug report with them.

Dave

From rshepard at appl-ecosys.com  Tue Jan  9 16:16:35 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 9 Jan 2018 08:16:35 -0800 (PST)
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <20180109153721.GR5554@Blackswan>
References: <alpine.LNX.2.20.1801090725160.25400@salmo.appl-ecosys.com>
 <20180109153721.GR5554@Blackswan>
Message-ID: <alpine.LNX.2.20.1801090814510.27204@salmo.appl-ecosys.com>

On Tue, 9 Jan 2018, David Woodfall wrote:

> This sounds more like an issue for the alpine devs. Have you looked to see
> if a fix has been made for this issue? If not then it's worth opening a
> bug report with them.

Dave,

   I thought it more appropriate for the alpine devs but I've not seen anyone
on a different distribution with the same issue. Of course, most folks now
seem to use gmail rather than alpine or mutt so others around here might not
notice the issue. I'll contact UDub about it.

Thanks,

Rich

From rshepard at appl-ecosys.com  Tue Jan  9 16:29:07 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 9 Jan 2018 08:29:07 -0800 (PST)
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <20180109153721.GR5554@Blackswan>
References: <alpine.LNX.2.20.1801090725160.25400@salmo.appl-ecosys.com>
 <20180109153721.GR5554@Blackswan>
Message-ID: <alpine.LNX.2.20.1801090823380.27204@salmo.appl-ecosys.com>

On Tue, 9 Jan 2018, David Woodfall wrote:

> This sounds more like an issue for the alpine devs. Have you looked to see
> if a fix has been made for this issue? If not then it's worth opening a
> bug report with them.

Dave,

   Sent them a bug report, but they do not respond to anyone outside the
university. Also,

"Obtaining Alpine software

Source Download

Software and source code is no longer available from the University of
Washington. It is recommended to evaluate one of the alternative versions of
this software supported by the community. A wikipedia page that tracks
continued community development, and provides links to patched versions of
the software is available here."

   Looking at the Wikipedia page I see that the current developer is Eduardo Chappa
and he's the one with whom I've been communicating. I'll ask him if version
2.21.9 has this change. If so, I'll download the source and use the
Slackware script to build it and upgrade.

Rich


From rshepard at appl-ecosys.com  Tue Jan  9 17:36:59 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 9 Jan 2018 09:36:59 -0800 (PST)
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <20180109153721.GR5554@Blackswan>
References: <alpine.LNX.2.20.1801090725160.25400@salmo.appl-ecosys.com>
 <20180109153721.GR5554@Blackswan>
Message-ID: <alpine.LNX.2.20.1801090933270.2007@salmo.appl-ecosys.com>

On Tue, 9 Jan 2018, David Woodfall wrote:

> This sounds more like an issue for the alpine devs. Have you looked to see
> if a fix has been made for this issue? If not then it's worth opening a
> bug report with them.

Dave,

   Downloaded the git tree for 2.21.9 (had to rename it from his numbering
system) and all the files from the 14.2 source directory.

   Untarred source, changed directory name to alpine-2.21.9/, tarred and xz'd
it. Changed version number in alpine.SlackBuild. This error appeared:

alpine-2.21.9/pico/estruct.h
chmod: cannot operate on dangling symlink './web/cgi/detach'
chmod: cannot operate on dangling symlink './web/cgi/alpine/2.0/lib/yui'
chmod: cannot operate on dangling symlink './web/detach'
Hmm...  Looks like a unified diff to me...
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- ./doc/alpine.1.orig	2008-03-14 18:53:39.000000000 -0500
|+++ ./doc/alpine.1	2008-08-06 20:00:13.000000000 -0500
--------------------------
File to patch:

   Please suggest how I should proceed.

Regards,

Rich

From jebrhansen+SBo at gmail.com  Tue Jan  9 17:38:36 2018
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Tue, 09 Jan 2018 17:38:36 +0000
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <alpine.LNX.2.20.1801090933270.2007@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801090725160.25400@salmo.appl-ecosys.com>
 <20180109153721.GR5554@Blackswan>
 <alpine.LNX.2.20.1801090933270.2007@salmo.appl-ecosys.com>
Message-ID: <CANi9qSvon3AMCRsQmdnyt976==VzRU=FouBOn4mPWGakAKNyCg@mail.gmail.com>

On Tue, Jan 9, 2018, 12:37 PM Rich Shepard <rshepard at appl-ecosys.com> wrote:

> On Tue, 9 Jan 2018, David Woodfall wrote:
>
> > This sounds more like an issue for the alpine devs. Have you looked to
> see
> > if a fix has been made for this issue? If not then it's worth opening a
> > bug report with them.
>
> Dave,
>
>    Downloaded the git tree for 2.21.9 (had to rename it from his numbering
> system) and all the files from the 14.2 source directory.
>
>    Untarred source, changed directory name to alpine-2.21.9/, tarred and
> xz'd
> it. Changed version number in alpine.SlackBuild. This error appeared:
>
> alpine-2.21.9/pico/estruct.h
> chmod: cannot operate on dangling symlink './web/cgi/detach'
> chmod: cannot operate on dangling symlink './web/cgi/alpine/2.0/lib/yui'
> chmod: cannot operate on dangling symlink './web/detach'
> Hmm...  Looks like a unified diff to me...
> can't find file to patch at input line 3
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |--- ./doc/alpine.1.orig        2008-03-14 18:53:39.000000000 -0500
> |+++ ./doc/alpine.1     2008-08-06 20:00:13.000000000 -0500
> --------------------------
> File to patch:
>
>    Please suggest how I should proceed.
>

You can likely remove or comment out the line containing the patch. I'm in
mobile or I'd try and find the specific line.

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180109/453a13b3/attachment-0001.html>

From rshepard at appl-ecosys.com  Tue Jan  9 18:47:34 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 9 Jan 2018 10:47:34 -0800 (PST)
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <CANi9qSvon3AMCRsQmdnyt976==VzRU=FouBOn4mPWGakAKNyCg@mail.gmail.com>
References: <alpine.LNX.2.20.1801090725160.25400@salmo.appl-ecosys.com>
 <20180109153721.GR5554@Blackswan>
 <alpine.LNX.2.20.1801090933270.2007@salmo.appl-ecosys.com>
 <CANi9qSvon3AMCRsQmdnyt976==VzRU=FouBOn4mPWGakAKNyCg@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.1801091044570.2007@salmo.appl-ecosys.com>

On Tue, 9 Jan 2018, Jeremy Hansen wrote:

> You can likely remove or comment out the line containing the patch. I'm in
> mobile or I'd try and find the specific line.

Jeremy,

   I'm not seeing the patch here:

$ grep -R alpine.1 *
alpine-2.21.9/doc/man1/pilot.1:alpine(1)
alpine-2.21.9/doc/man1/pico.1:alpine(1)
alpine-2.21.9/doc/man1/alpine.1:.TH alpine 1 "Version 2.21.9"
alpine-2.21.9/packages/alpine.spec:install -D -m644 doc/man1/alpine.1 $RPM_BUILD_ROOT%{_mandir}/man1/alpine.1
alpine-2.21.9/packages/alpine.spec:%{_mandir}/man1/alpine.1*
alpine-2.21.9/packages/debian/rules:	install -D -m644 doc/alpine.1 debian/tmp/usr/share/man/man1/alpine.1
grep: alpine-2.21.9/web/cgi/detach: No such file or directory
grep: alpine-2.21.9/web/cgi/alpine/2.0/lib/yui: No such file or directory
grep: alpine-2.21.9/web/detach: No such file or directory
alpine-2.21.9/Makefile.in:man_MANS = doc/man1/alpine.1 doc/man1/pico.1 doc/man1/pilot.1 doc/man1/rpdump.1 doc/man1/rpload.1
alpine-2.21.9/Makefile.am:man_MANS = doc/man1/alpine.1 doc/man1/pico.1 doc/man1/pilot.1 doc/man1/rpdump.1 doc/man1/rpload.1
Binary file alpine-2.21.9.tar matches

   I need to focus on business the rest of the day so I won't be futzing with
this until much later.

Thanks,

Rich

From rshepard at appl-ecosys.com  Tue Jan  9 18:51:20 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 9 Jan 2018 10:51:20 -0800 (PST)
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <alpine.LNX.2.20.1801091044570.2007@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801090725160.25400@salmo.appl-ecosys.com>
 <20180109153721.GR5554@Blackswan>
 <alpine.LNX.2.20.1801090933270.2007@salmo.appl-ecosys.com>
 <CANi9qSvon3AMCRsQmdnyt976==VzRU=FouBOn4mPWGakAKNyCg@mail.gmail.com>
 <alpine.LNX.2.20.1801091044570.2007@salmo.appl-ecosys.com>
Message-ID: <alpine.LNX.2.20.1801091050280.2007@salmo.appl-ecosys.com>

On Tue, 9 Jan 2018, Rich Shepard wrote:

>  I'm not seeing the patch here:
>
> $ grep -R alpine.1 *

   Looking for 'patch' results in many hits but nothing I recognize as
relevant.

Rich

From alik at ejik.org  Tue Jan  9 19:42:52 2018
From: alik at ejik.org (Alexander Verbovetsky)
Date: Tue, 09 Jan 2018 22:42:52 +0300
Subject: [Slackbuilds-users] skypeforlinux
In-Reply-To: <20180107110736.GA7895@jdiamond-mb.acadiau.ca>
References: <20180106160808.GA16181@jdiamond-mb.acadiau.ca>
 <1515267445.3653554.1226464720.3B3B44E4@webmail.messagingengine.com>
 <20180107110736.GA7895@jdiamond-mb.acadiau.ca>
Message-ID: <1515526972.711545.1229688704.2A0D4BEB@webmail.messagingengine.com>

On Sun, Jan 7, 2018, at 14:07, Jim Diamond wrote:
> On Sat, Jan  6, 2018 at 22:37 (+0300), Alexander Verbovetsky wrote:
> 
> > Hello,
> 
> >> the SBo version is 8.11.0.4 but there are 5 newer versions at
> >> repo.skype.com/deb/pool/main/s/skypeforlinux/.
> 
> >> Time for a bump?
> 
> > There are "stable" versions listed here:
> > https://repo.skype.com/deb/dists/stable/main/binary-amd64/Packages
> 
> > and "unstable" ones listed here:
> > https://repo.skype.com/deb/dists/unstable/main/binary-amd64/Packages
> 
> > 8.11.0.4 is the latest stable version. Also, this is the version
> > distributed via https://www.skype.com/en/get-skype/.
> 
> Alexander,
> 
> thanks very much for that information.

And today the latest stable version is up to 8.13.0.2.

Best regards,
Alexander

From fernando.lopezjr at gmail.com  Tue Jan  9 19:56:26 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Tue, 9 Jan 2018 12:56:26 -0700
Subject: [Slackbuilds-users] skypeforlinux
In-Reply-To: <1515526972.711545.1229688704.2A0D4BEB@webmail.messagingengine.com>
References: <20180106160808.GA16181@jdiamond-mb.acadiau.ca>
 <1515267445.3653554.1226464720.3B3B44E4@webmail.messagingengine.com>
 <20180107110736.GA7895@jdiamond-mb.acadiau.ca>
 <1515526972.711545.1229688704.2A0D4BEB@webmail.messagingengine.com>
Message-ID: <CALrQ46DX4BEf3AR6eBr2fCqcxgbDV=VK0Ucq0C4Dx+8tbC_Mkw@mail.gmail.com>

md5 mismatch.


skypeforlinux:
skypeforlinux not found in /var/cache/sbopkg.
--2018-01-09 12:52:46--
https://repo.skype.com/deb/pool/main/s/skypeforlinux/skypeforlinux_8.11.0.4_amd64.deb
Resolving repo.skype.com (repo.skype.com)... 23.40.17.81,
2600:1404:18:58a::1263, 2600:1404:18:591::1263
Connecting to repo.skype.com (repo.skype.com)|23.40.17.81|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 72424690 (69M) [application/x-debian-package]
Saving to: ?skypeforlinux_8.11.0.4_amd64.deb?

skypeforlinux_8.11. 100%[===================>]  69.07M  1.35MB/s    in 37s


2018-01-09 12:53:23 (1.85 MB/s) - ?skypeforlinux_8.11.0.4_amd64.deb? saved
[72424690/72424690]

Found skypeforlinux_8.11.0.4_amd64.deb in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for skypeforlinux_8.11.0.4_amd64.deb ... FAILED!
    Expected: 70a34a452c9d8cd8c841c0409d368174
    Found:    4359322cb2710c4eb748b173c7204624

Do you want to use the downloaded skypeforlinux source:
skypeforlinux_8.11.0.4_amd64.deb 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.


On Tue, Jan 9, 2018 at 12:42 PM, Alexander Verbovetsky <alik at ejik.org>
wrote:

> On Sun, Jan 7, 2018, at 14:07, Jim Diamond wrote:
> > On Sat, Jan  6, 2018 at 22:37 (+0300), Alexander Verbovetsky wrote:
> >
> > > Hello,
> >
> > >> the SBo version is 8.11.0.4 but there are 5 newer versions at
> > >> repo.skype.com/deb/pool/main/s/skypeforlinux/.
> >
> > >> Time for a bump?
> >
> > > There are "stable" versions listed here:
> > > https://repo.skype.com/deb/dists/stable/main/binary-amd64/Packages
> >
> > > and "unstable" ones listed here:
> > > https://repo.skype.com/deb/dists/unstable/main/binary-amd64/Packages
> >
> > > 8.11.0.4 is the latest stable version. Also, this is the version
> > > distributed via https://www.skype.com/en/get-skype/.
> >
> > Alexander,
> >
> > thanks very much for that information.
>
> And today the latest stable version is up to 8.13.0.2.
>
> Best regards,
> Alexander
> _______________________________________________
> 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/20180109/679aacd5/attachment.html>

From rshepard at appl-ecosys.com  Tue Jan  9 20:11:53 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 9 Jan 2018 12:11:53 -0800 (PST)
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <alpine.LNX.2.20.1801090933270.2007@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801090725160.25400@salmo.appl-ecosys.com>
 <20180109153721.GR5554@Blackswan>
 <alpine.LNX.2.20.1801090933270.2007@salmo.appl-ecosys.com>
Message-ID: <alpine.LNX.2.20.1801091135480.2007@salmo.appl-ecosys.com>

On Tue, 9 Jan 2018, Rich Shepard wrote:

> Downloaded the git tree for 2.21.9 (had to rename it from his numbering
> system) and all the files from the 14.2 source directory.

   The source code has been fixed, replacing strncpy with memmove in the
forward code.

   I cloned the git repository and followed Eduardo's explicit instructions
to get the latest code from this morning. Then I made alpine-2.21.99.tar.xz
from the source.

   Still have the patch error; it must be with the SlackBuild code and I
don't know enough to fix it. Here are the error report and what I have from
the Slackware-14.2 source directory:

...
alpine-2.21.99/pico/estruct.h
chmod: cannot operate on dangling symlink './web/cgi/detach'
chmod: cannot operate on dangling symlink './web/cgi/alpine/2.0/lib/yui'
chmod: cannot operate on dangling symlink './web/detach'
Hmm...  Looks like a unified diff to me...
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- ./doc/alpine.1.orig	2008-03-14 18:53:39.000000000 -0500
|+++ ./doc/alpine.1	2008-08-06 20:00:13.000000000 -0500
--------------------------
File to patch: 
Skip this patch? [y] y
Skipping patch.
Hunk #1 ignored at 305.
1 out of 1 hunk ignored
done

   And in /opt/slackbuilds/alpine/:

alpine-2.21.99.tar.xz                    pinepgp-0.18.0.tar.gz.sig
alpine.SlackBuild*                       pinepgp.pinegpgp.in.diff.gz
alpine.manpage.diff.gz                   slack-desc.alpine
doinst.sh.alpine                         slack-desc.imapd
pinepgp-0.18.0-makefile-sed-fix.diff.gz  source-repo/
pinepgp-0.18.0.tar.gz

   More help needed.

Regards,

Rich

From rshepard at appl-ecosys.com  Tue Jan  9 21:47:33 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 9 Jan 2018 13:47:33 -0800 (PST)
Subject: [Slackbuilds-users] How best to contact Slackware devs?
Message-ID: <alpine.LNX.2.20.1801091343170.2007@salmo.appl-ecosys.com>

On Tue, 9 Jan 2018, Didier Spaier wrote:

> At least one of the patches is not relevant with the new source files.

Didier,

   I assume this to be the case. Since I'm not a slackware (or SBo) package
builder I don't have the experience to figour out what corrections are
needed in the 2.20 directory so that 2.21.99 (and the forthcoming 2.22)
build properly.

> You need to check if these files are still necessary, and if they are find
> which modifications are needed. Maybe a kind soul reading this is willing
> to do that for you?

   Renaming all three diff files so they are not seen allowed the
configuration to complete, then the make failed a different reason:

Building with SSL
ln -s ssl_unix.c osdepssl.c
echo -I/usr/include -I/usr/include/openssl -DSSL_CERT_DIRECTORY=\"/etc/ssl/certs\" -DSSL_KEY_DIRECTORY=\"/etc/ssl/certs\" >> OSCFLAGS
echo "  ssl_onceonlyinit ();" >> linkage.c
echo -L/usr/lib -lssl -lcrypto  >> LDFLAGS
cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c
Building OS-dependent module
If you get No such file error messages for files x509.h, ssl.h,
pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL
is not installed on your system. Either install OpenSSL first
or build with command: make slx SSLTYPE=none
`cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c
In file included from auths.c:1:0,
                  from env_unix.c:259,
                  from osdep.c:47:
kerb_mit.c:30:35: fatal error: gssapi/gssapi_generic.h: No such file or directory
compilation terminated.
Makefile:932: recipe for target 'osdep.o' failed
make[4]: *** [osdep.o] Error 1
make[4]: Leaving directory '/opt/alpine-2.21.99/imap/c-client'
Makefile:685: recipe for target 'slx' failed
make[3]: *** [slx] Error 2
make[3]: Leaving directory '/opt/alpine-2.21.99/imap/c-client'
Makefile:691: recipe for target 'OSTYPE' failed
make[2]: *** [OSTYPE] Error 2
make[2]: Leaving directory '/opt/alpine-2.21.99/imap'
Makefile:312: recipe for target 'slx' failed
make[1]: *** [slx] Error 2
make[1]: Leaving directory '/opt/alpine-2.21.99/imap'
Makefile:957: recipe for target 'c-client' failed
make: *** [c-client] Error 2

   The header file is installed here:
/usr/kerberos/include/gssapi/gssapi_generic.h

   Also looked at the build script without seeing where this might be
addressed.

Best regards,

Rich

From mario at slackware.hr  Tue Jan  9 22:15:28 2018
From: mario at slackware.hr (Mario)
Date: Tue, 9 Jan 2018 23:15:28 +0100
Subject: [Slackbuilds-users] skypeforlinux
In-Reply-To: <1515526972.711545.1229688704.2A0D4BEB@webmail.messagingengine.com>
References: <20180106160808.GA16181@jdiamond-mb.acadiau.ca>
 <1515267445.3653554.1226464720.3B3B44E4@webmail.messagingengine.com>
 <20180107110736.GA7895@jdiamond-mb.acadiau.ca>
 <1515526972.711545.1229688704.2A0D4BEB@webmail.messagingengine.com>
Message-ID: <b47ce85c-06d7-acb2-2249-08acb1f51dc6@slackware.hr>

On 01/09/2018 08:42 PM, Alexander Verbovetsky wrote:
> And today the latest stable version is up to 8.13.0.2.
>

Updated in my branch.
Not sure what changed since the last release, annoying little bugs are 
still there, but since its basically just another browser... oh well, 
enjoy! :-)

-- 
Mario


From didier at slint.fr  Tue Jan  9 22:26:25 2018
From: didier at slint.fr (Didier Spaier)
Date: Tue, 9 Jan 2018 23:26:25 +0100
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <alpine.LNX.2.20.1801091343170.2007@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801091343170.2007@salmo.appl-ecosys.com>
Message-ID: <9da5fe80-aecc-90ae-477e-0272d736d965@slint.fr>

Le 09/01/2018 ? 22:47, Rich Shepard a ?crit?:
<snip>
> kerb_mit.c:30:35: fatal error: gssapi/gssapi_generic.h: No such file or directory
<snip>
> ? The header file is installed here:
> /usr/kerberos/include/gssapi/gssapi_generic.h
> 
> ? Also looked at the build script without seeing where this might be
> addressed.
My guess is that this header is not where it is looked for.

As a reminder, kerberos is not shipped in Slackware.

If kerberos is a hard dependency, you are on your own as far as I am in
concern. 

Maybe check with configure --help in the new source tree if it can
optionally be built without kerberos.

Didier

PS Please continue this conversation on this mailing list only.

Best,

Didier

From willysr at slackbuilds.org  Tue Jan  9 23:23:35 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 10 Jan 2018 06:23:35 +0700
Subject: [Slackbuilds-users] Electrum Advisory
Message-ID: <4c9e78ab-1331-6442-6318-6fb342a668d7@slackbuilds.org>

Hi

One user came to me to warn that current Electrum in SBo is vulnerable
to JSONRPC bug
(https://github.com/spesmilo/electrum-docs/blob/master/cve.rst). This
affect all Electrum 2.x and 3.x until 3.0.4. Version 3.0.5 fixed this
completely.

Unfortunately upgrading to Electrum 3.x is not that easy as upstream
moved to Python 3 and Qt5 completely. Some scripts doesn't have Python3
support so this is an on-progress work of adding Python3 support in some
scripts and when it's done, i can test for 3.x. Until then, we are stuck
with Electrum 2.9.3.

Meanwhile, users who are using Electrum should use the following advice:

Users who did not protect their wallet with a password should create a
new wallet, and move their funds to that wallet. Even if it never
received any funds, a wallet without password should not be used
anymore, because its seed might have been compromised.

In addition, users should review their settings, and delete all contacts
from their contacts list, because the Bitcoin addresses of their
contacts might have been modified.

If Electrum 3.0.5 (or any later version) cannot be installed or does not
work on your computer, stop using Electrum on that computer, and access
your funds from a device that can run Electrum 3.0.5. If you really need
to use an older version of Electrum, for example in order to access
wallet seed, make sure that your computer is offline, and that no web
browser is running on the computer at the same time.


-- 
Willy Sudiarto Raharjo

-------------- 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/20180110/944d9c2b/attachment.asc>

From rshepard at appl-ecosys.com  Tue Jan  9 23:35:58 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 9 Jan 2018 15:35:58 -0800 (PST)
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <9da5fe80-aecc-90ae-477e-0272d736d965@slint.fr>
References: <alpine.LNX.2.20.1801091343170.2007@salmo.appl-ecosys.com>
 <9da5fe80-aecc-90ae-477e-0272d736d965@slint.fr>
Message-ID: <alpine.LNX.2.20.1801091531130.2007@salmo.appl-ecosys.com>

On Tue, 9 Jan 2018, Didier Spaier wrote:

> If kerberos is a hard dependency, you are on your own as far as I am in
> concern.

Didier,

   I added '--without-krb5 \' to the SlackBuild script's configure section;
this fixed this issue. Now I get an issue with pinegpg and don't see just
where in the untarred pinepgp-0.18.0.tar.gz this occurs.

...
creating ./config.status
creating Makefile
/usr/bin/cat pinegpgp.in | /usr/bin/sed -e 's%\@SED\@%/usr/bin/sed%;\
 	s%\@CAT\@%/usr/bin/cat%;\
 	s%\@RM\@%/usr/bin/rm%;\
 	s%\@MKTEMP\@%/usr/bin/mktemp%;\
 	s%\@BASH\@%/bin/sh%;\
 	s%\@bindir\@%/usr/bin%;\
 	s%\@tmpdir\@%~/.pinepgp%' > pinegpgp
/usr/bin/sed: -e expression #1, char 185: unterminated address regex
Makefile:48: recipe for target 'pinegpgp' failed
make: *** [pinegpgp] Error 1

   A pointer to where the error might be would be appreciated.

Thanks,

Rich

From didier at slint.fr  Tue Jan  9 23:51:42 2018
From: didier at slint.fr (Didier Spaier)
Date: Wed, 10 Jan 2018 00:51:42 +0100
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <alpine.LNX.2.20.1801091531130.2007@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801091343170.2007@salmo.appl-ecosys.com>
 <9da5fe80-aecc-90ae-477e-0272d736d965@slint.fr>
 <alpine.LNX.2.20.1801091531130.2007@salmo.appl-ecosys.com>
Message-ID: <aa3e7730-4a6e-fa49-fd2b-8968d31b7bac@slint.fr>

Le 10/01/2018 ? 00:35, Rich Shepard a ?crit?:
> On Tue, 9 Jan 2018, Didier Spaier wrote:
> 
>> If kerberos is a hard dependency, you are on your own as far as I am in
>> concern.
> 
> Didier,
> 
> ? I added '--without-krb5 \' to the SlackBuild script's configure section;
> this fixed this issue. Now I get an issue with pinegpg and don't see just
> where in the untarred pinepgp-0.18.0.tar.gz this occurs.
> 
> ...
> creating ./config.status
> creating Makefile
> /usr/bin/cat pinegpgp.in | /usr/bin/sed -e 's%\@SED\@%/usr/bin/sed%;\
> ????s%\@CAT\@%/usr/bin/cat%;\
> ????s%\@RM\@%/usr/bin/rm%;\
> ????s%\@MKTEMP\@%/usr/bin/mktemp%;\
> ????s%\@BASH\@%/bin/sh%;\
> ????s%\@bindir\@%/usr/bin%;\
> ????s%\@tmpdir\@%~/.pinepgp%' > pinegpgp
> /usr/bin/sed: -e expression #1, char 185: unterminated address regex
> Makefile:48: recipe for target 'pinegpgp' failed
> make: *** [pinegpgp] Error 1

Probably one of the patches you discarded would help. 

I would bet a bitcoin for: 
pinepgp-0.18.0-makefile-sed-fix.diff.gz
 
> ? A pointer to where the error might be would be appreciated.

I suggest that you learn a bit a few things like:
1) shell scripting
2) SlackBuilds
3) A few commands like diff and patch
etc.

I'd prefer baby feed my grandson Lucas than you ;)

Best,

Didier 

From jebrhansen+SBo at gmail.com  Wed Jan 10 00:10:22 2018
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Tue, 9 Jan 2018 19:10:22 -0500
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <alpine.LNX.2.20.1801091531130.2007@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801091343170.2007@salmo.appl-ecosys.com>
 <9da5fe80-aecc-90ae-477e-0272d736d965@slint.fr>
 <alpine.LNX.2.20.1801091531130.2007@salmo.appl-ecosys.com>
Message-ID: <CANi9qSv5hSo6CJ=r4Mwok0EFcmega-2614tb9bv-3P5zrU-2DQ@mail.gmail.com>

On Tue, Jan 9, 2018 at 6:35 PM, Rich Shepard <rshepard at appl-ecosys.com>
wrote:
>
> On Tue, 9 Jan 2018, Didier Spaier wrote:
>
>> If kerberos is a hard dependency, you are on your own as far as I am in
>> concern.
>
>
> Didier,
>
>   I added '--without-krb5 \' to the SlackBuild script's configure section;
> this fixed this issue. Now I get an issue with pinegpg and don't see just
> where in the untarred pinepgp-0.18.0.tar.gz this occurs.
>
> ...
> creating ./config.status
> creating Makefile
> /usr/bin/cat pinegpgp.in | /usr/bin/sed -e 's%\@SED\@%/usr/bin/sed%;\
>         s%\@CAT\@%/usr/bin/cat%;\
>         s%\@RM\@%/usr/bin/rm%;\
>         s%\@MKTEMP\@%/usr/bin/mktemp%;\
>         s%\@BASH\@%/bin/sh%;\
>         s%\@bindir\@%/usr/bin%;\
>         s%\@tmpdir\@%~/.pinepgp%' > pinegpgp
> /usr/bin/sed: -e expression #1, char 185: unterminated address regex
> Makefile:48: recipe for target 'pinegpgp' failed
> make: *** [pinegpgp] Error 1
>
>   A pointer to where the error might be would be appreciated.


I was able to build it after commenting out the patch in the SlackBuild and
then switching the SSLTYPE from unix to unix.pwd

Here's a patch for the 14.2 SlackBuild. You'll need to rename your alpine
download to: alpine-f2246f7.tar.xz

diff --git a/alpine.SlackBuild b/alpine.SlackBuild
index 9f2a91c..3a16381 100755
--- a/alpine.SlackBuild
+++ b/alpine.SlackBuild
@@ -22,7 +22,7 @@


 PKGNAM=alpine
-VERSION=${VERSION:-2.20}
+VERSION=${VERSION:-f2246f7}
 ALPINEBUILD=${ALPINEBUILD:-2}
 IMAPDBUILD=${IMAPDBUILD:-2}
 PINEPGP=${PINEPGP:-0.18.0}
@@ -67,7 +67,7 @@ find . \
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm
400 \) \
  -exec chmod 644 {} \;

-zcat $CWD/alpine.manpage.diff.gz | patch -p1 --verbose || exit 1
+#zcat $CWD/alpine.manpage.diff.gz | patch -p1 --verbose || exit 1

 # Configure:
 CFLAGS="$SLKCFLAGS" \
@@ -96,9 +96,9 @@ CFLAGS="$SLKCFLAGS" \

 # Build and install:
 # Since we build non-compliant to RFC3501 we have to answer 'y' half-way:
-echo y | make EXTRACFLAGS="-fPIC" SSLTYPE=unix || exit 1
+echo y | make EXTRACFLAGS="-fPIC" SSLTYPE=unix.nopwd || exit 1

-make install SSLTYPE=unix DESTDIR=$PKG || exit 1
+make install SSLTYPE=unix.nopwd DESTDIR=$PKG || exit 1

 # Add default config file:
 ./alpine/alpine -conf > $PKG/etc/pine.conf.new
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180109/6d5fa917/attachment.html>

From rshepard at appl-ecosys.com  Wed Jan 10 00:17:09 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 9 Jan 2018 16:17:09 -0800 (PST)
Subject: [Slackbuilds-users] How best to contact Slackware devs?
 [RESOLVED]
In-Reply-To: <aa3e7730-4a6e-fa49-fd2b-8968d31b7bac@slint.fr>
References: <alpine.LNX.2.20.1801091343170.2007@salmo.appl-ecosys.com>
 <9da5fe80-aecc-90ae-477e-0272d736d965@slint.fr>
 <alpine.LNX.2.20.1801091531130.2007@salmo.appl-ecosys.com>
 <aa3e7730-4a6e-fa49-fd2b-8968d31b7bac@slint.fr>
Message-ID: <alpine.LNX.2.20.1801091616170.2007@salmo.appl-ecosys.com>

On Wed, 10 Jan 2018, Didier Spaier wrote:

> Probably one of the patches you discarded would help.

   Yep. I removed the pinegpg diff file too soon. It's building now.

Rich

From atelszewski at gmail.com  Wed Jan 10 06:40:23 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 10 Jan 2018 07:40:23 +0100
Subject: [Slackbuilds-users] qemu-guest-agent not in pending nor ready queue
Message-ID: <89a07586-9550-c589-0a80-9233afa3aaee@gmail.com>

Hi,

On 08/01/2018 I sent update for qemu-guest-agent.
But as of now, it's not in pending nor ready queue.

Has someone forgotten to push it further? ;-)

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Wed Jan 10 06:42:03 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 10 Jan 2018 07:42:03 +0100
Subject: [Slackbuilds-users] intel-microcode updated
Message-ID: <7c426a8f-a5e4-2019-51eb-c71afc0e3258@gmail.com>

Hi,

I've just sent update for intel-microcode.

You might consider having SBo public update sooner this round.

-- 
Best regards,
Andrzej Telszewski

From chris.willing at linux.com  Wed Jan 10 09:06:34 2018
From: chris.willing at linux.com (Christoph Willing)
Date: Wed, 10 Jan 2018 19:06:34 +1000
Subject: [Slackbuilds-users] vlc & libupnp (was: libass ABI changes)
In-Reply-To: <CAPsDuS7iHayhKyckkQCrRJn1ecGU9k6+RiS+ogKP+w9_o_80Gw@mail.gmail.com>
References: <CAPsDuS5-ZS-AfRu5NiPTVRK7FD-bHzL3HOLbqE1DYTCRqC6ZnQ@mail.gmail.com>
 <8058bec6-e8e5-3151-ab06-4e0aa33aac39@slackbuilds.org>
 <CAPsDuS7iHayhKyckkQCrRJn1ecGU9k6+RiS+ogKP+w9_o_80Gw@mail.gmail.com>
Message-ID: <dd7cc47f-0962-2249-90ad-ca45d4a0d8d6@linux.com>

On 07/01/18 03:22, Matteo Bernardini wrote:
> 2018-01-06 18:15 GMT+01:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:
[snip]
>>
>>> vlc
>>
>> It failed to build, but i guess it's caused by newer libupnp
>> https://pastebin.com/dq8CKh1n
> 
> thanks Willy!
> 
> I found that support for the newer libupnp has been added to vlc in august
> 
> http://git.videolan.org/?p=vlc/vlc-3.0.git;a=commit;h=3eb4e03512f45c1fa27c7f9a6759e8e7d3905720
> 
> so I'll let Chris decide in which way he likes to proceed (get in
> touch with me directly or via the list, either is ok): looks like vlc
> 3.0 is near but if a more recent git snapshot of the 3.0 branch is
> needed I can host it.
> 

Firstly, I'm sorry for the late response; I recently returned from a
holiday and had a lot of catching up to do first.

I tried building the latest code in the vlc git repo (which would
include the commit mentioned by Matteo) but there were a few problems
which I didn't feel like delving into.

Instead, I've added a patch using that commit. It all builds & runs
fine, although I don't have a simple test to exercise the patched code.
I don't expect any problems though since the patch only changes some
function arguments.

chris

From atelszewski at gmail.com  Wed Jan 10 10:26:38 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 10 Jan 2018 11:26:38 +0100
Subject: [Slackbuilds-users] qemu-guest-agent not in pending nor ready
 queue
In-Reply-To: <89a07586-9550-c589-0a80-9233afa3aaee@gmail.com>
References: <89a07586-9550-c589-0a80-9233afa3aaee@gmail.com>
Message-ID: <45211b44-e56e-e873-3822-ec47613187dc@gmail.com>

On 10/01/18 07:40, Andrzej Telszewski wrote:
> Hi,
> 
> On 08/01/2018 I sent update for qemu-guest-agent.
> But as of now, it's not in pending nor ready queue.
> 
> Has someone forgotten to push it further? ;-)
> 

https://git.slackbuilds.org/slackbuilds/commit/?id=684732b86

Thanks :-)

-- 
Best regards,
Andrzej Telszewski

From baildon.research at googlemail.com  Wed Jan 10 15:14:57 2018
From: baildon.research at googlemail.com (David Spencer)
Date: Wed, 10 Jan 2018 15:14:57 +0000
Subject: [Slackbuilds-users] qemu-guest-agent not in pending nor ready
 queue
In-Reply-To: <45211b44-e56e-e873-3822-ec47613187dc@gmail.com>
References: <89a07586-9550-c589-0a80-9233afa3aaee@gmail.com>
 <45211b44-e56e-e873-3822-ec47613187dc@gmail.com>
Message-ID: <CAMt7G9SbLpcRNxprdnT_f1X0JfAdVugect+YXM+Yrty9E04LtA@mail.gmail.com>

>> Hi,
>>
>> On 08/01/2018 I sent update for qemu-guest-agent.
>> But as of now, it's not in pending nor ready queue.
>>
>> Has someone forgotten to push it further? ;-)
>>
>
> https://git.slackbuilds.org/slackbuilds/commit/?id=684732b86
>
> Thanks :-)

Hi Andrzej, yes that was me, I forgot to push it, sorry :(
and you did exactly the right thing to email us :D

Thanks :)
-D.

From rshepard at appl-ecosys.com  Wed Jan 10 15:39:19 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 10 Jan 2018 07:39:19 -0800 (PST)
Subject: [Slackbuilds-users] How best to contact Slackware devs?
In-Reply-To: <CANi9qSv5hSo6CJ=r4Mwok0EFcmega-2614tb9bv-3P5zrU-2DQ@mail.gmail.com>
References: <alpine.LNX.2.20.1801091343170.2007@salmo.appl-ecosys.com>
 <9da5fe80-aecc-90ae-477e-0272d736d965@slint.fr>
 <alpine.LNX.2.20.1801091531130.2007@salmo.appl-ecosys.com>
 <CANi9qSv5hSo6CJ=r4Mwok0EFcmega-2614tb9bv-3P5zrU-2DQ@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.1801100738250.1470@salmo.appl-ecosys.com>

On Tue, 9 Jan 2018, Jeremy Hansen wrote:

> I was able to build it after commenting out the patch in the SlackBuild
> and then switching the SSLTYPE from unix to unix.pwd Here's a patch for
> the 14.2 SlackBuild. You'll need to rename your alpine download to:
> alpine-f2246f7.tar.xz

Jeremy,

   Thank you.

Rich

From willysr at slackbuilds.org  Wed Jan 10 17:16:36 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 11 Jan 2018 00:16:36 +0700
Subject: [Slackbuilds-users] Updates - 20180110.1
Message-ID: <d4527c52-4ab9-add2-ec61-ae9cdf4839d7@slackbuilds.org>

Hi

We pushed this update sooner than the usual update schedule, mainly
because of the whole Spectre/Meltdown issue and new intel-microcode is
now included in this batch so please update as soon as possible.

libupnp update seems to broke vlc but it got fixed in this batch as
well. As in my previous email, there is a work-in-progress of adding
Python 3 support for some scripts. One of the reason is because next
Slackware ships Python 3 by default and other thing is to smoothen the
transition for some scripts that is ported to Python 3 exclusively (eg.
Electrum).

Wine is still in pending because although it built fine on x86_64, it
stucked on David's 32 bit VM twice. We are looking into it and hopefully
it can be merged in the next update.

We are happy to announce a new maintainer who gets a privilege for git
write commit in SBo, Andrew Clemons. He has done a wonderful job on
Rust-related scripts.


Wed Jan 10 16:57:35 UTC 2018
academic/pcb: Updated for version 4.0.2.
academic/suitesparse: Updated for version 5.1.2
audio/audacity: Updated for version 2.2.1.
audio/mac: Updated for version 3.99_u4_b5_s7, new maintainer.
audio/speex: Update download url.
audio/transcribe: Updated for version 8.71.
desktop/QtCurve-Gtk2: Removed (merged in qtcurve).
desktop/QtCurve-KDE4: Removed (merged in qtcurve).
desktop/i3lock: Updated for version 2.10.
desktop/jgmenu: Updated for version 0.8.
desktop/menutray: Updated for version 0.52.
desktop/qtcurve: Added (Style engine for Qt).
desktop/wmclock: Fix homepage and download URLs.
development/CImg: Updated for version 2.1.8.
development/Sphinx: Updated for version 1.6.6.
development/arm-binutils: Change to cortex-m3.
development/arm-gcc: Removed C++.
development/blassic: Updated for version 0.10.3, new maintainer.
development/fpc: Add conflict note.
development/hugo: Updated for version 0.32.2.
development/mads: Updated for version 2.0.7.
development/python3-matplotlib: Switch to https.
development/rustfmt: Removed (included in rust).
development/sbcl: Updated for version 1.4.3.
development/tiled: Updated for version 1.1.1.
development/valgrind: New maintainer.
games/residualvm: Updated for version 0.3.0.
games/scummvm: Updated for version 2.0.0.
graphics/SweetHome3D: Updated for version 5.6.
graphics/feh: Updated for version 2.23.
graphics/gifsicle: Updated for version 1.91.
libraries/SDL_kitchensink: Fix script.
libraries/allegro4: New maintainer.
libraries/libburn: Updated for version 1.4.8.
libraries/libfilezilla: Updated for version 0.11.2.
libraries/libisoburn: Updated for version 1.4.8.
libraries/libisofs: Updated for version 1.4.8.
libraries/libvirt: Bugfix to net-destroy in rc.libvirt
libraries/lua-mpack: Updated for version 1.0.7.
libraries/qgnomeplatform: Added (Platform Theme for Qt5 apps).
libraries/unarr: Updated for version 1.0.1.
misc/bdfresize: Fix homepage and download URLs.
misc/heyu: Updated for version 2.10.1.
misc/moreutils: Updated for version 0.62.
misc/yapet: Switch to https.
multimedia/opera-developer-ffmpeg-codecs: Updated for version 64.0.
multimedia/vlc: Patched to support libupnp-1.8
network/MEGAsync: Updated for version 3.5.3.0.
network/TeamSpeak3: Updated for version 3.1.7.
network/c-toxcore: Updated for version 0.1.11.
network/filezilla: Updated for version 3.30.0.
network/gajim: Updated for version 0.16.9.
network/opera-developer: Updated for version 51.0.2830.0.
network/retroshare: Update README.
network/skypeforlinux: Updated for version 8.13.0.2.
network/thttpd: Updated for version 2.27 + new maintainer.
network/tor: Updated for version 0.3.2.9.
network/viber: Updated for version 7.0.0.1035.
office/LibreOffice: Updated for version 5.4.4.2
office/libreoffice: Fix symlink creation.
office/org-mode: Switch to https.
perl/perl-GD: Updated for version 2.67.
perl/perl-file-libmagic: Updated for version 1.16.
perl/perl-xml-fast: Updated for version 0.17.
python/Paver: Updated for version 1.3.4.
python/Scrapy: Updated for version 1.5.0.
python/blessings: Updated for version 1.6.1.
python/crcmod: Added (python CRC Generator)
python/google-apputils: Add python3 support.
python/migen: Updated for version 0.6.
python/networkx: Added (create and manipulate networks).
python/pyasn1-modules: Add python3 support.
python/pyasn1: Add python3 support.
python/python-fonttools: Updated for version 3.21.2.
python/python-gflags: Add python3 support.
python/python-nbxmpp: Updated for version 0.6.2.
python/python-tlslite: Add python3 support.
python/selenium: Updated for version 3.8.1.
python/websocket-client: Updated for version 0.46.0.
ruby/ruby-gist: Updated for version 4.6.2.
system/dosbox: Switch to i586.
system/forkstat: Updated for version 0.02.01.
system/fwupd: Updated for version 1.0.3.
system/guake: Updated for version 0.8.12.
system/intel-microcode: Updated for version 20180108.
system/oldschool-pc-fonts: New maintainer, optional console fonts.
system/open-vm-tools: Updated for version 10.2.0-7253323.
system/posh: Updated for version 0.13.1.
system/ptop: Add conflict note.
system/qemu-guest-agent: Updated for version 2.10.2.
system/qemu: Updated for version 2.10.2.
system/spice-vdagent: Fix pid killing when stopping the service.
system/tomb: Updated for version 2.5.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- 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/20180111/1968163c/attachment.asc>

From fellype at gmail.com  Wed Jan 10 17:44:50 2018
From: fellype at gmail.com (Fellype do Nascimento)
Date: Wed, 10 Jan 2018 15:44:50 -0200
Subject: [Slackbuilds-users] What is the best way to add a tag to the
 version of a program?
Message-ID: <a4bfc252-7aaa-b38c-61ce-8b9b7970a583@gmail.com>

Hi all!

At the moment I am the maintainer of sayonara-player.SlackBuild [1]. The 
version numbering structure of Sayonara Player (SP) is:

x.y.z-gitX-YYYYMMDD where x=major release, y=minor release, z=bugfix 
release and gitX-YYYYMMDD = "small adjustments" release.

Sometimes the SP developers make only some small adjustments and release it.
Currently the VERSION variable in sayonara-player.SlackBuild is set only 
as x.y.z (following the way that the previous maintainer - Edinaldo P. 
Silva - wrote it), and another variable, SRCVER, with gitX-YYYYMMDD is 
used in the 'tar' step. Then, when sayonara-player.SlackBuild is updated 
due to a small adjustments release, SBo users that use sbotools and run 
sbocheck do not notice that it was updated, even if the BUILD variable 
is changed.
For this reason, I would like to change the version number structure of 
SP in sayonara-player.SlackBuild from

VERSION=${VERSION:-x.y.z}

to

VERSION=${VERSION:-x.y.z-gitX-YYYYMMDD} (FYI, the latest version of SP 
is 1.0.0-git1-20171231)

and to discard the SRCVER variable.

I know, from a test, that it works. But I would like to know if there is 
a more "correct" way to do this change?

Best regards,

Fellype

[1] 
https://slackbuilds.org/slackbuilds/14.2/audio/sayonara-player/sayonara-player.SlackBuild

-- 

Dr. Fellype do Nascimento - fellype (at) gmail.com
Center for Semiconductor Components and Nanotechnologies / Laborat?rio de Plasmas
State University of Campinas, C.P. 6101,
Rua Jo?o Pandia Calogeras, No.90,
Cidade Universit?ria Zeferino Vaz,
Campinas, SP, 13083-870, Brazil
Fone/Phone: +55 19 35217321


From atelszewski at gmail.com  Wed Jan 10 17:56:13 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 10 Jan 2018 18:56:13 +0100
Subject: [Slackbuilds-users] What is the best way to add a tag to the
 version of a program?
In-Reply-To: <a4bfc252-7aaa-b38c-61ce-8b9b7970a583@gmail.com>
References: <a4bfc252-7aaa-b38c-61ce-8b9b7970a583@gmail.com>
Message-ID: <c53c4c94-45e0-66be-42f1-6662d96a77c9@gmail.com>

On 10/01/18 18:44, Fellype do Nascimento wrote:
> Hi all!
> 
> At the moment I am the maintainer of sayonara-player.SlackBuild [1]. The 
> version numbering structure of Sayonara Player (SP) is:
> 
> x.y.z-gitX-YYYYMMDD where x=major release, y=minor release, z=bugfix 
> release and gitX-YYYYMMDD = "small adjustments" release.
> 
> Sometimes the SP developers make only some small adjustments and release 
> it.
> Currently the VERSION variable in sayonara-player.SlackBuild is set only 
> as x.y.z (following the way that the previous maintainer - Edinaldo P. 
> Silva - wrote it), and another variable, SRCVER, with gitX-YYYYMMDD is 
> used in the 'tar' step. Then, when sayonara-player.SlackBuild is updated 
> due to a small adjustments release, SBo users that use sbotools and run 
> sbocheck do not notice that it was updated, even if the BUILD variable 
> is changed.
> For this reason, I would like to change the version number structure of 
> SP in sayonara-player.SlackBuild from
> 
> VERSION=${VERSION:-x.y.z}
> 
> to
> 
> VERSION=${VERSION:-x.y.z-gitX-YYYYMMDD} (FYI, the latest version of SP 
> is 1.0.0-git1-20171231)
> 
> and to discard the SRCVER variable.
> 
> I know, from a test, that it works. But I would like to know if there is 
> a more "correct" way to do this change?
> 
> Best regards,
> 
> Fellype
> 
> [1] 
> https://slackbuilds.org/slackbuilds/14.2/audio/sayonara-player/sayonara-player.SlackBuild 
> 
> 

I think your reasoning is not exactly correct, but the outcome result is 
good ;-)

What I mean is that BUILD should not mimic in any way the upstream 
versioning schema.

The only thing you have to change is that you cannot use "-" in version 
string.
Common practice here is to replace it with "_" (underscore).
Then your SlackBuild should somehow deal with "_" is VERSION but with 
"-" in source tarball name.

Something like:
SRCVER=$(echo $VERSION | tr _ -)


-- 
Best regards,
Andrzej Telszewski

From fellype at gmail.com  Wed Jan 10 18:12:44 2018
From: fellype at gmail.com (Fellype do Nascimento)
Date: Wed, 10 Jan 2018 16:12:44 -0200
Subject: [Slackbuilds-users] What is the best way to add a tag to the
 version of a program?
In-Reply-To: <c53c4c94-45e0-66be-42f1-6662d96a77c9@gmail.com>
References: <a4bfc252-7aaa-b38c-61ce-8b9b7970a583@gmail.com>
 <c53c4c94-45e0-66be-42f1-6662d96a77c9@gmail.com>
Message-ID: <64ae2c62-b625-e23e-07f3-bf04649801c7@gmail.com>

On 01/10/2018 03:56 PM, Andrzej Telszewski wrote:
>
> I think your reasoning is not exactly correct, but the outcome result 
> is good ;-)
>
> What I mean is that BUILD should not mimic in any way the upstream 
> versioning schema.
>
> The only thing you have to change is that you cannot use "-" in 
> version string.
> Common practice here is to replace it with "_" (underscore).
> Then your SlackBuild should somehow deal with "_" is VERSION but with 
> "-" in source tarball name.
>
> Something like:
> SRCVER=$(echo $VERSION | tr _ -)
>
>
Hi Andrzej!

Thank you for your tip. I got it.

Best regards,

Fellype


From dpross1100 at msn.com  Wed Jan 10 23:12:54 2018
From: dpross1100 at msn.com (Daniel Prosser)
Date: Wed, 10 Jan 2018 23:12:54 +0000
Subject: [Slackbuilds-users] What is the best way to add a tag to the
 version of a program?
In-Reply-To: <64ae2c62-b625-e23e-07f3-bf04649801c7@gmail.com>
References: <a4bfc252-7aaa-b38c-61ce-8b9b7970a583@gmail.com>
 <c53c4c94-45e0-66be-42f1-6662d96a77c9@gmail.com>
 <64ae2c62-b625-e23e-07f3-bf04649801c7@gmail.com>
Message-ID: <CY4PR22MB0294CF570EC38EA80FF4F731CC110@CY4PR22MB0294.namprd22.prod.outlook.com>

Fellype,

A couple comments here.

1. I agree with Andrzej that if you update your SlackBuild because of a
new version of the source code available, that should constitute a
change in the VERSION variable, not the BUILD. BUILD is more for
adjustments to the SlackBuild script itself (or other things unique to
SBo) for the same version of the source code. As Andrzej said, replacing
the dashes in the source version string with underscores is a typical
way to handle your situation.

2. That said, sbotools should check the BUILD as well as the VERSION
when determining whether a package should be upgraded. I recently went
through this with sboui, too. Perhaps an issue should be filed upstream
if sbotools does not do that.

Dan

On Wed, Jan 10, 2018 at 04:12:44PM -0200, Fellype do Nascimento wrote:
> On 01/10/2018 03:56 PM, Andrzej Telszewski wrote:
> > 
> > I think your reasoning is not exactly correct, but the outcome result is
> > good ;-)
> > 
> > What I mean is that BUILD should not mimic in any way the upstream
> > versioning schema.
> > 
> > The only thing you have to change is that you cannot use "-" in version
> > string.
> > Common practice here is to replace it with "_" (underscore).
> > Then your SlackBuild should somehow deal with "_" is VERSION but with
> > "-" in source tarball name.
> > 
> > Something like:
> > SRCVER=$(echo $VERSION | tr _ -)
> > 
> > 
> Hi Andrzej!
> 
> Thank you for your tip. I got it.
> 
> Best regards,
> 
> Fellype
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From didier at slint.fr  Wed Jan 10 23:46:26 2018
From: didier at slint.fr (Didier Spaier)
Date: Thu, 11 Jan 2018 00:46:26 +0100
Subject: [Slackbuilds-users] What is the best way to add a tag to the
 version of a program?
In-Reply-To: <CY4PR22MB0294CF570EC38EA80FF4F731CC110@CY4PR22MB0294.namprd22.prod.outlook.com>
References: <a4bfc252-7aaa-b38c-61ce-8b9b7970a583@gmail.com>
 <c53c4c94-45e0-66be-42f1-6662d96a77c9@gmail.com>
 <64ae2c62-b625-e23e-07f3-bf04649801c7@gmail.com>
 <CY4PR22MB0294CF570EC38EA80FF4F731CC110@CY4PR22MB0294.namprd22.prod.outlook.com>
Message-ID: <0824e52e-9210-08bd-455b-b0b66d04e77b@slint.fr>

Le 11/01/2018 ? 00:12, Daniel Prosser a ?crit?:
> 2. That said, sbotools should check the BUILD as well as the VERSION
> when determining whether a package should be upgraded.

I agree, and think that pretty much every tools do (or should do) the
same, considering that a "well formed" Slackware package name has the
following form (without the trailing .t?z of the file name):
<package short name>-<version>-<arch>-<build>

There only requirement for <version> and <build> is not to contain any
hyphen, so that the package short name can always be determined as:
printf <package full name> | sed s/-[^-]*-[^-]*-[^-]*$//

So any change in <version> or <build> should trigger a proposal to
replace the currently installed package.

At least that's how I see it.

Didier

From rworkman at slackbuilds.org  Thu Jan 11 22:51:10 2018
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 11 Jan 2018 16:51:10 -0600
Subject: [Slackbuilds-users] VM Host Reboot
Message-ID: <20180111165110.59a1f2af@home.rlworkman.net>

We're rebooting the VM host for www.slackbuilds.org,
git.slackbuilds.org, and slackwiki.com at the moment.

Stuff will be inaccessible for a few minutes while we
get that process underway and completed.

-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/20180111/f87b7387/attachment.asc>

From rworkman at slackbuilds.org  Thu Jan 11 23:14:28 2018
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 11 Jan 2018 17:14:28 -0600
Subject: [Slackbuilds-users] VM Host Reboot
In-Reply-To: <20180111165110.59a1f2af@home.rlworkman.net>
References: <20180111165110.59a1f2af@home.rlworkman.net>
Message-ID: <20180111171425.182d49c0@home.rlworkman.net>

On Thu, 11 Jan 2018 16:51:10 -0600
Robby Workman <rworkman at slackbuilds.org> wrote:

> We're rebooting the VM host for www.slackbuilds.org,
> git.slackbuilds.org, and slackwiki.com at the moment.
> 
> Stuff will be inaccessible for a few minutes while we
> get that process underway and completed.


Everything should be back up now. 

Let us know if you see any issues.

For what it's worth, there's quite possibly going to be more
not-as-planned-as-we'd-like reboots in the coming days/weeks
or even months due to the recent processor bugs...

-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/20180111/6bc4d2e3/attachment.asc>

From atelszewski at gmail.com  Thu Jan 11 23:50:58 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Fri, 12 Jan 2018 00:50:58 +0100
Subject: [Slackbuilds-users] VM Host Reboot
In-Reply-To: <20180111171425.182d49c0@home.rlworkman.net>
References: <20180111165110.59a1f2af@home.rlworkman.net>
 <20180111171425.182d49c0@home.rlworkman.net>
Message-ID: <7b609d7b-6d43-137c-42b4-8ee1805fc764@gmail.com>

On 12/01/18 00:14, Robby Workman wrote:
> On Thu, 11 Jan 2018 16:51:10 -0600
> Robby Workman <rworkman at slackbuilds.org> wrote:
> 
>> We're rebooting the VM host for www.slackbuilds.org,
>> git.slackbuilds.org, and slackwiki.com at the moment.
>>
>> Stuff will be inaccessible for a few minutes while we
>> get that process underway and completed.
> 
> 
> Everything should be back up now.
> 
> Let us know if you see any issues.
> 
> For what it's worth, there's quite possibly going to be more
> not-as-planned-as-we'd-like reboots in the coming days/weeks
> or even months due to the recent processor bugs...
> 
> -RW
> 

I don't think this concerns you, but just in case:

libvirt/QEMU memory ballooning does not work as expected with host 
kernel version 4.14.12:
https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/libvirt-qemu-memory-ballooning-does-not-work-as-expected-with-host-kernel-version-4-14-12-a-4175621195/

-- 
Best regards,
Andrzej Telszewski

From rworkman at slackbuilds.org  Thu Jan 11 23:58:47 2018
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 11 Jan 2018 17:58:47 -0600
Subject: [Slackbuilds-users] VM Host Reboot
In-Reply-To: <7b609d7b-6d43-137c-42b4-8ee1805fc764@gmail.com>
References: <20180111165110.59a1f2af@home.rlworkman.net>
 <20180111171425.182d49c0@home.rlworkman.net>
 <7b609d7b-6d43-137c-42b4-8ee1805fc764@gmail.com>
Message-ID: <20180111175847.6205b8fd@home.rlworkman.net>

On Fri, 12 Jan 2018 00:50:58 +0100
Andrzej Telszewski <atelszewski at gmail.com> wrote:

> On 12/01/18 00:14, Robby Workman wrote:
> > On Thu, 11 Jan 2018 16:51:10 -0600
> > Robby Workman <rworkman at slackbuilds.org> wrote:
> >   
> >> We're rebooting the VM host for www.slackbuilds.org,
> >> git.slackbuilds.org, and slackwiki.com at the moment.
> >>
> >> Stuff will be inaccessible for a few minutes while we
> >> get that process underway and completed.  
> > 
> > 
> > Everything should be back up now.
> > 
> > Let us know if you see any issues.
> > 
> > For what it's worth, there's quite possibly going to be more
> > not-as-planned-as-we'd-like reboots in the coming days/weeks
> > or even months due to the recent processor bugs...
> > 
> > -RW
> >   
> 
> I don't think this concerns you, but just in case:
> 
> libvirt/QEMU memory ballooning does not work as expected with host 
> kernel version 4.14.12:
> https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/libvirt-qemu-memory-ballooning-does-not-work-as-expected-with-host-kernel-version-4-14-12-a-4175621195/


It does not, but thanks for the heads-up anyway.

It *does* affect me at home, unless it's fixed on 4.4.13.
( didn't read the link yet, but I will)

-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/20180111/f1f9c171/attachment.asc>

From yalhcru at gmail.com  Fri Jan 12 04:37:32 2018
From: yalhcru at gmail.com (B Watson)
Date: Thu, 11 Jan 2018 23:37:32 -0500
Subject: [Slackbuilds-users] lmello's svgalib stuff
In-Reply-To: <CAN1hMuA5OvMwHG2-v1ZvfSX0Y-rNzFLzw4A_bv0pPeX8_AUSdA@mail.gmail.com>
References: <CAN1hMuA5OvMwHG2-v1ZvfSX0Y-rNzFLzw4A_bv0pPeX8_AUSdA@mail.gmail.com>
Message-ID: <CAN1hMuCmrcYo5=OG=sFFD4U5xj4CnQki0qjv5mz8bTPn0hNkwg@mail.gmail.com>

On 1/8/18, B Watson <yalhcru at gmail.com> wrote:
>
> zgv can be built for SDL instead of svgalib, which might allow it to
> work with the framebuffer console. If this actually works, would there
> be any benefit in converting the zgv build to use it instead of svgalib?
> We already have some decent framebuffer image viewers, including fbi.

Update: zgv built for SDL doesn't work on my system, it compiles (with
a one-line patch) but at runtime complains:

zgv: a 640x480, 800x600, 1024x768, or 1280x1024 mode is required.

...my console is 1920x1080, which is the native res of my LCD panel. So
this doesn't look very useful, especially as fbi works fine on my system,
if I want to view images in the console.

I played around with the svgalib zgv, and was unable to get it to
work on my system... I've got a fairly old (2009 or so) PCI Express
NVidia card, using the nouveau driver. Tried changing the chipset in
/etc/vga/libvga.config to VGA, VESA, NV3, and FBDEV, none of them work
(zgv segfaulted and/or produced no graphics display).

All the supported chipsets listed in libvga.config are outdated and
unlikely to still be in use today...

So, anyone got a working svgalib setup, and wants to maintain zgv and/or
svp? Does anyone actually use either of these successfully at all?

If not... normally I don't argue for removing stuff from the repo, but if
it's unmaintained *and* completely useless for any purpose, why keep it?

If someone does want to take over zgv, I know at least one change that
needs to be made: the kernel module svgalib_helper mentioned in the
README has changed its name, it's now called just svgalib.

From willysr at slackbuilds.org  Fri Jan 12 10:28:27 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 12 Jan 2018 17:28:27 +0700
Subject: [Slackbuilds-users] letsencrypt security issue
Message-ID: <517f0fde-a7ec-3986-edb9-b3970ad9b2c7@slackbuilds.org>

Hi,

For those who are using letsencrypt, please read their security page
https://community.letsencrypt.org/t/solution-client-with-the-currently-selected-authenticator-does-not-support-any-combination-of-challenges-that-will-satisfy-the-ca/49983

in short, tls-sni-01 challenge is disabled for now due to security
reason and if you need to renew the certificates for your domain, you
can use one the solutions provided in the article.

Once you run the command (assuming it completed normally), certbot will
remember your settings so you can use "certbot renew" command in the future


-- 
Willy Sudiarto Raharjo

-------------- 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/20180112/d22b8565/attachment.asc>

From kristofru at gmail.com  Fri Jan 12 14:48:26 2018
From: kristofru at gmail.com (Chris Abela)
Date: Fri, 12 Jan 2018 15:48:26 +0100
Subject: [Slackbuilds-users] audacity build fails due to the inconsistent
 VERSION of the help file
Message-ID: <CAJ2_kYo-Hj5gGEBa2Y9ym1Yo0apXEBTpPwt8hjvi_=1mhkDKXA@mail.gmail.com>

Audacity will not build:

make[2]: Leaving directory '/tmp/SBo/audacity-Audacity-2.2.1'
make[1]: Leaving directory '/tmp/SBo/audacity-Audacity-2.2.1'
unzip:  cannot find or open
/var/lib/sbopkg/SBo/14.2/audio/audacity/audacity-help-*2.2.1*.zip,
/var/lib/sbopkg/SBo/14.2/audio/audacity/audacity-help-2.2.1.zip.zip or
/var/lib/sbopkg/SBo/14.2/audio/audacity/audacity-help-2.2.1.zip.ZIP.

This is because we have this in audacity.info:

DOWNLOAD="https://github.com/audacity/audacity/archive/Audacity-2.2.1.tar.gz
\
          http://ponce.cc/slackware/sources/repo/audacity-help-*2.1.3*.zip"

and this in audacity.Slackbuid:

VERSION=${VERSION:-*2.2.1*}

and then:

  unzip $CWD/$PRGNAM-help-$*VERSION*.zip -d
$PKG/usr/share/$PRGNAM/help/manual
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180112/68b5d790/attachment.html>

From matteo.bernardini at gmail.com  Fri Jan 12 16:32:48 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 12 Jan 2018 17:32:48 +0100
Subject: [Slackbuilds-users] audacity build fails due to the
 inconsistent VERSION of the help file
In-Reply-To: <CAJ2_kYo-Hj5gGEBa2Y9ym1Yo0apXEBTpPwt8hjvi_=1mhkDKXA@mail.gmail.com>
References: <CAJ2_kYo-Hj5gGEBa2Y9ym1Yo0apXEBTpPwt8hjvi_=1mhkDKXA@mail.gmail.com>
Message-ID: <CAPsDuS6EdKX-WGGSwSg-LOKrNf14PyY6h+=AsPcfj3=fN-HBKA@mail.gmail.com>

2018-01-12 15:48 GMT+01:00 Chris Abela <kristofru at gmail.com>:
> Audacity will not build:
>
> make[2]: Leaving directory '/tmp/SBo/audacity-Audacity-2.2.1'
> make[1]: Leaving directory '/tmp/SBo/audacity-Audacity-2.2.1'
> unzip:  cannot find or open
> /var/lib/sbopkg/SBo/14.2/audio/audacity/audacity-help-2.2.1.zip,
> /var/lib/sbopkg/SBo/14.2/audio/audacity/audacity-help-2.2.1.zip.zip or
> /var/lib/sbopkg/SBo/14.2/audio/audacity/audacity-help-2.2.1.zip.ZIP.
>
> This is because we have this in audacity.info:
>
> DOWNLOAD="https://github.com/audacity/audacity/archive/Audacity-2.2.1.tar.gz
> \
>           http://ponce.cc/slackware/sources/repo/audacity-help-2.1.3.zip"
>
> and this in audacity.Slackbuid:
>
> VERSION=${VERSION:-2.2.1}
>
> and then:
>
>   unzip $CWD/$PRGNAM-help-$VERSION.zip -d $PKG/usr/share/$PRGNAM/help/manual

hi Chris,

I'll just pushed a fix for this, it will be merged at the next update.
In the meantime, if you want to build it, just avoid passing the
script the MANUAL=yes parameter (by default the variable MANUAL is set
to "no").

Matteo

From willysr at slackbuilds.org  Sat Jan 13 00:24:06 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 13 Jan 2018 07:24:06 +0700
Subject: [Slackbuilds-users] Updates - 20180113.1
Message-ID: <ab3c285e-97ce-38db-1ca9-fed87fc6cb93@slackbuilds.org>

Hi

Back to our usual weekend updates and we have more security updates on
several package that is corellated with Spectre vulnerabilities,
including webkit2gtk and wireshark. We also managed to fix the wine
build issue on 32 bit machine.

Chris is pushing the new VTK 8.1.0 and this requires some other scripts
to be patched in order to support it. Please make sure you rebuilt other
scripts that depends on VTK.

Happy weekend

Sat Jan 13 00:13:51 UTC 2018
academic/RepeatMasker: Added (Screen DNA sequence).
academic/bedtools: Updated for version 2.27.1.
academic/bwa: Updated for version 0.7.17.
academic/hyphy: Updated for version 2.3.8.
academic/mafft: Updated for version 7.313.
academic/ncbi-blast-plus: Updated for version 2.7.1.
academic/ncbi-rmblastn: Added (NCBI RMBlast).
academic/pal2nal: Updated for version 14.1.
academic/paml: Updated for version 4.9g.
academic/pamlX: Updated for paml-4.9g compatibility.
academic/seaview: Updated for version 4.6.3.
academic/snpEff: Updated for version 4.3t.
academic/trfind: Added (Tandem repeats finder: analyze DNA seqs).
academic/ugene: Updated for version 1.29.0.
academic/zotero: Updated for version 5.0.33.
audio/audacity: Fix for the newer manual version.
audio/mktoc: New maintainer, add man page.
desktop/fehlstart: Added (desktop application launcher).
desktop/gxkb: Updated for version 0.8.0.
desktop/j4-dmenu-desktop: Updated for version 2.16.
desktop/thunar-sendto-clamtk: Updated for version 0.06.
development/composer: Updated for version 1.6.2
development/hhvm: Updated for version 3.23.4
development/universal-ctags: Updated for version 796684b
games/stone_soup: Updated for version 0.20.1.
gis/saga-gis: Updated for version 6.2.0.
graphics/OpenCASCADE: Patched for VTK-8.1.0 compatibility.
graphics/psftools: Install sample fonts.
libraries/VTK: Updated for version 8.1.0
libraries/webkit2gtk: Updated for version 2.18.5.
misc/KeePass: Updated for version 2.38.
multimedia/smplayer: Updated for version 18.1.0.
multimedia/smtube: Updated for version 18.1.0.
multimedia/xmms-crossfade: New maintainer.
multimedia/youtube-viewer: Updated for version 3.3.3.
network/discord: Updated for version 0.0.4.
network/opera: Updated for version 50.0.2762.58.
network/tornado: Updated for version 4.5.3.
network/uget: Updated for version 2.2.0.
network/verm: Updated for version 1.3.0.
network/waterfox: Updated for version 56.0.2.
network/wireshark: Updated for version 2.4.4.
network/youtube-dl: Updated for version 2018.01.07.
office/cups-pdf: Switch to https.
office/libreoffice-helppack: Switch to https.
office/libreoffice-langpack: Switch to https.
office/libreoffice: Switch to https.
office/texmacs: Updated for version 1.99.6.
perl/perl-Text-Soundex: Added (Text::Soundex).
python/python3-tornado: Updated for version 4.5.3.
system/alacritty: Updated for version git8aa8422.
system/i2c-tools: Updated for version 4.0, changed homepage.
system/qjoypad: Added (convert gamepad buttons to keystrokes).
system/slpkg: Updated for version 3.3.4.
system/wine: Updated for version 2.0.4.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- 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/20180113/98909b46/attachment.asc>

From willysr at slackbuilds.org  Sat Jan 13 03:37:37 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 13 Jan 2018 10:37:37 +0700
Subject: [Slackbuilds-users] nodejs changes
Message-ID: <5669375b-bf77-0e43-dfd9-bcccd0a8048e@slackbuilds.org>

Hi all,

I'm going to push nodejs to LTS 8 (Carbon) for next public update.

For those who still use the LTS 6 (Boron), i will upload a new script
nodejs6 and i will maintain this until it's EOL'ed in April 2019. By
then it will be removed from the repository and we expect all packages
has been patched to support nodejs 8.x.

Based on early testing with nodejs8, only vstudio failed to build
properly. Other script built successfully or need a bump (eg. atom).



-- 
Willy Sudiarto Raharjo

-------------- 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/20180113/ab51b2b5/attachment-0001.asc>

From dchmelik at gmail.com  Sat Jan 13 04:37:12 2018
From: dchmelik at gmail.com (David Melik)
Date: Fri, 12 Jan 2018 20:37:12 -0800
Subject: [Slackbuilds-users] sbo-templates
Message-ID: <d649d126-97ad-2906-d3ac-dc5a17b04b72@gmail.com>

On Tue, 19 Dec 2017 10:16:32 +0100, Dimitris Zlatanidis wrote:

 > One more tool for everyone who creates SlackBuilds scripts:
 >
 > https://github.com/dslackw/sbo-templates

Looks great, but can one use to update scripts/etc. one already has?


From willysr at slackbuilds.org  Sat Jan 13 06:25:07 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 13 Jan 2018 13:25:07 +0700
Subject: [Slackbuilds-users] nodejs changes
In-Reply-To: <5669375b-bf77-0e43-dfd9-bcccd0a8048e@slackbuilds.org>
References: <5669375b-bf77-0e43-dfd9-bcccd0a8048e@slackbuilds.org>
Message-ID: <8ca6ed12-d008-952e-8056-546224355840@slackbuilds.org>

> Based on early testing with nodejs8, only vstudio failed to build
> properly. Other script built successfully or need a bump (eg. atom).

Sorry, it wasn't vstudio but vscode that wasn't built properly with nodejs8.


-- 
Willy Sudiarto Raharjo

-------------- 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/20180113/d16efa5c/attachment.asc>

From alex at dcclost.com  Sat Jan 13 16:43:15 2018
From: alex at dcclost.com (Alexander Grotewohl)
Date: Sat, 13 Jan 2018 11:43:15 -0500
Subject: [Slackbuilds-users] Wishful thinking
Message-ID: <432c6c57-72c0-ca88-36ad-debdc2026068@dcclost.com>

So I was thinking it'd be kind of neat if it were possible to log in on 
the slackbuilds site and check off software I've installed, and perhaps 
get a list of items that have changed since I last checked. Yeah, 
wishful thinking indeed :)

BUT, on a separate, related note, what do you guys & gals use to keep 
track? I currently keep a Changelog file and list off everything I do 
and the date, as well as read through the list of items on the weekly 
email list. I do miss one once in a while though, or in the case of some 
deps that get significantly less updates, I'll forget I use them entirely.

Sorry if this email is a bit of an incomplete thought.. just hoping for 
a few tips and tricks :)

Alex


From rshepard at appl-ecosys.com  Sat Jan 13 16:58:32 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 13 Jan 2018 08:58:32 -0800 (PST)
Subject: [Slackbuilds-users] Wishful thinking
In-Reply-To: <432c6c57-72c0-ca88-36ad-debdc2026068@dcclost.com>
References: <432c6c57-72c0-ca88-36ad-debdc2026068@dcclost.com>
Message-ID: <alpine.LNX.2.20.1801130854550.25094@salmo.appl-ecosys.com>

On Sat, 13 Jan 2018, Alexander Grotewohl wrote:

> So I was thinking it'd be kind of neat if it were possible to log in on
> the slackbuilds site and check off software I've installed, and perhaps
> get a list of items that have changed since I last checked. Yeah, wishful
> thinking indeed :)
>
> BUT, on a separate, related note, what do you guys & gals use to keep track?

Alex,

   Not sure this answers both your wish and your question but I use sbopkg
<https://sbopkg.org/>. After it starts I re-sync my local repository to the
SBo repository, check for upgrades, view the queue to see what I want to
upgrade, then process the queue. Works very well unless there's a mis-match
between the checksum on SBo and the actual downloaded source.

   Try it. You'll like it.

Rich


From atelszewski at gmail.com  Sat Jan 13 17:02:34 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 13 Jan 2018 18:02:34 +0100
Subject: [Slackbuilds-users] Wishful thinking
In-Reply-To: <432c6c57-72c0-ca88-36ad-debdc2026068@dcclost.com>
References: <432c6c57-72c0-ca88-36ad-debdc2026068@dcclost.com>
Message-ID: <bd96b685-293d-70de-81fd-67a3b505899a@gmail.com>

On 13/01/18 17:43, Alexander Grotewohl wrote:
> So I was thinking it'd be kind of neat if it were possible to log in on 
> the slackbuilds site and check off software I've installed, and perhaps 
> get a list of items that have changed since I last checked. Yeah, 
> wishful thinking indeed :)
> 
> BUT, on a separate, related note, what do you guys & gals use to keep 
> track? I currently keep a Changelog file and list off everything I do 
> and the date, as well as read through the list of items on the weekly 
> email list. I do miss one once in a while though, or in the case of some 
> deps that get significantly less updates, I'll forget I use them entirely.
> 
> Sorry if this email is a bit of an incomplete thought.. just hoping for 
> a few tips and tricks :)
> 
> Alex
> 
> _______________________________________________
> 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/
> 
> 

If you don't use any of the available SBo package managers, you're 
making your life unnecessarily complicated ;-)

Also, use of git can be handy (since SBo is git -enabled).
I actually started using git, because one of SBo package managers, 
namely _slackrepo_, uses it.

So in general, I use slackrepo to be up to date, and then git, to 
maintain my local modifications.

-- 
Best regards,
Andrzej Telszewski

From yalhcru at gmail.com  Sat Jan 13 19:29:26 2018
From: yalhcru at gmail.com (B Watson)
Date: Sat, 13 Jan 2018 14:29:26 -0500
Subject: [Slackbuilds-users] Wishful thinking
In-Reply-To: <432c6c57-72c0-ca88-36ad-debdc2026068@dcclost.com>
References: <432c6c57-72c0-ca88-36ad-debdc2026068@dcclost.com>
Message-ID: <CAN1hMuCrSpw6rt875ncO+4Qko2wG1b93R+vKeDjeVS-t1zQefw@mail.gmail.com>

On 1/13/18, Alexander Grotewohl <alex at dcclost.com> wrote:
> So I was thinking it'd be kind of neat if it were possible to log in on
> the slackbuilds site and check off software I've installed, and perhaps
> get a list of items that have changed since I last checked. Yeah,
> wishful thinking indeed :)

Doing that on a website, manually, by checking boxes... would be tedious
indeed. The computer already knows the information, better to automate it.

sbopkg isn't my favorite thing in the world, but it does a good job of
finding locally-installed packages that are outdated (have new versions
on SBo).

I've never used sbotools, but surely it has the same functionality. I'm
tempted to say "if it doesn't, I'll eat my hat", but I'm running low on
hats lately...

From eric.b.pratt at gmail.com  Sat Jan 13 20:53:33 2018
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Sat, 13 Jan 2018 12:53:33 -0800
Subject: [Slackbuilds-users] Wishful thinking
In-Reply-To: <CAN1hMuCrSpw6rt875ncO+4Qko2wG1b93R+vKeDjeVS-t1zQefw@mail.gmail.com>
References: <432c6c57-72c0-ca88-36ad-debdc2026068@dcclost.com>
 <CAN1hMuCrSpw6rt875ncO+4Qko2wG1b93R+vKeDjeVS-t1zQefw@mail.gmail.com>
Message-ID: <CAPKhk4PoKaNHMNdDsCraCb2nxsAUUaTMTqsyM4=0-gZtq4tvdQ@mail.gmail.com>

I also use sbopkg.  But if you're looking for something less automated to
find the list of packages you've installed, you could run this:

  ls /var/log/packages/*SBo | sort -f | cut -d/ -f5

That will show all packages installed from slackbuilds.org on your system
without showing any other packages.  You can also add to the pipeline to
further edit the listing if you only wish to see only the name of each
package or only the name and version of each package, for instance.

If you want to get a list of the packages and their dates of installation,
you could do this:

  for i in $(ls /var/log/packages/*SBo | sort -f | cut -d/ -f5); do echo -n
"$i: "; stat -c %y $i | cut -d\  -f1; done

If you want to get a list of packages that have changed since you last
installed them, you'll need to use git to sync up the repo on your system.
Then you'll have to iterate through the list of package names on your
system, checking your local git repo for the latest version of the package
and comparing it to your own.  You could almost certainly do that as a one
liner too, but a small script would probably be better.

Unless you're really interested in rolling your own script(s) for this, I
really do recommend using a more fully automated tool that's already been
written.  I can't really recommend one over the others since I've only used
sbopkg.  I really should try out the other tools to see what they can do.
But as others have said, there are multiple options for what you're trying
to do and at least one of them is probably what you're looking for.


On Sat, Jan 13, 2018 at 11:29 AM, B Watson <yalhcru at gmail.com> wrote:

> On 1/13/18, Alexander Grotewohl <alex at dcclost.com> wrote:
> > So I was thinking it'd be kind of neat if it were possible to log in on
> > the slackbuilds site and check off software I've installed, and perhaps
> > get a list of items that have changed since I last checked. Yeah,
> > wishful thinking indeed :)
>
> Doing that on a website, manually, by checking boxes... would be tedious
> indeed. The computer already knows the information, better to automate it.
>
> sbopkg isn't my favorite thing in the world, but it does a good job of
> finding locally-installed packages that are outdated (have new versions
> on SBo).
>
> I've never used sbotools, but surely it has the same functionality. I'm
> tempted to say "if it doesn't, I'll eat my hat", but I'm running low on
> hats lately...
> _______________________________________________
> 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/20180113/2bc61d3b/attachment-0001.html>

From dpross1100 at msn.com  Sat Jan 13 22:23:40 2018
From: dpross1100 at msn.com (Daniel Prosser)
Date: Sat, 13 Jan 2018 22:23:40 +0000
Subject: [Slackbuilds-users] Wishful thinking
In-Reply-To: <CAPKhk4PoKaNHMNdDsCraCb2nxsAUUaTMTqsyM4=0-gZtq4tvdQ@mail.gmail.com>
References: <432c6c57-72c0-ca88-36ad-debdc2026068@dcclost.com>
 <CAN1hMuCrSpw6rt875ncO+4Qko2wG1b93R+vKeDjeVS-t1zQefw@mail.gmail.com>
 <CAPKhk4PoKaNHMNdDsCraCb2nxsAUUaTMTqsyM4=0-gZtq4tvdQ@mail.gmail.com>
Message-ID: <CY4PR22MB02943BBDDA79FC9C003661C8CC140@CY4PR22MB0294.namprd22.prod.outlook.com>

I'm partial to sboui myself (well, probably because I wrote it :)). It
makes it really fast to see what's installed or upgradable, as well as
several other useful filters. Just hit f then i for installed or f then
u for upgradable, and you will have a list sorted by group and name.
Select one and hit enter to see what else it can do. It does require a
separate tool like sbopkg or sbotools to do the package management part,
but in the next release it will get a built-in package manager that can
be used instead if desired.

They are all good though, and I'm sure that sbopkg, sbotools, slackrepo,
or sboui will all do the job equally well albeit somewhat differently. I
have used all except slackrepo, just because I don't have a desire to
keep a local repository of packages. Any of them will certainly be
better than trying to keep track of everything manually.

Dan

From sbolokanov at abv.bg  Sun Jan 14 12:13:06 2018
From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvdGKINCR0L7Qu9C+0LrQsNC90L7QstGK?=)
Date: Sun, 14 Jan 2018 14:13:06 +0200 (EET)
Subject: [Slackbuilds-users] Update for dunst
Message-ID: <619367895.194081.1515931986452.JavaMail.apache@nm52.abv.bg>

Hello,
 
  here is update for dunst:  https://github.com/sbolokanov/sbopush7/commit/180be1481249cfa874ce8fcbe8d44a62f51e83b0 
 
Regards,
-- ?????? ?. ??????????
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180114/88d37627/attachment.html>

From willysr at slackbuilds.org  Sun Jan 14 13:12:11 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 14 Jan 2018 20:12:11 +0700
Subject: [Slackbuilds-users] Update for dunst
In-Reply-To: <619367895.194081.1515931986452.JavaMail.apache@nm52.abv.bg>
References: <619367895.194081.1515931986452.JavaMail.apache@nm52.abv.bg>
Message-ID: <16955458-567a-e744-565e-8c705961d3f4@slackbuilds.org>

> here is update for dunst:
> https://github.com/sbolokanov/sbopush7/commit/180be1481249cfa874ce8fcbe8d44a62f51e83b0

Hi

Can you send a PR instead?


-- 
Willy Sudiarto Raharjo

-------------- 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/20180114/bdfa9ff8/attachment.asc>

From sbolokanov at abv.bg  Sun Jan 14 14:00:02 2018
From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvdGKINCR0L7Qu9C+0LrQsNC90L7QstGK?=)
Date: Sun, 14 Jan 2018 16:00:02 +0200 (EET)
Subject: [Slackbuilds-users] Update for dunst
In-Reply-To: <16955458-567a-e744-565e-8c705961d3f4@slackbuilds.org>
References: <619367895.194081.1515931986452.JavaMail.apache@nm52.abv.bg>
 <16955458-567a-e744-565e-8c705961d3f4@slackbuilds.org>
Message-ID: <675388821.199214.1515938402902.JavaMail.apache@nm52.abv.bg>

Done

-- ?????? ?. ??????????









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

 >??: Willy Sudiarto Raharjo willysr at slackbuilds.org

 >???????: Re: [Slackbuilds-users] Update for dunst

 >??: slackbuilds-users at slackbuilds.org

 >????????? ??: 14.01.2018 15:12


> here is update for dunst:

>  https://github.com/sbolokanov/sbopush7/commit/180be1481249cfa874ce8fcbe8d44a62f51e83b0 



Hi



Can you send a PR instead?





-- 

Willy Sudiarto Raharjo



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180114/7b20a81f/attachment.html>

From slackalaxy at gmail.com  Sun Jan 14 17:20:06 2018
From: slackalaxy at gmail.com (Petar Petrov)
Date: Sun, 14 Jan 2018 19:20:06 +0200
Subject: [Slackbuilds-users] bpp-phyl build fail
Message-ID: <CAKXpWBdfd6gausPnF50v8q1TfZqZAZLkA_gP08TaSzxdHYL_Mg@mail.gmail.com>

hi guys,

i am planning a minor update of bppsuite and its deps. Everything
compiles fine on Slackware64, however, compilation of bpp-phyl breaks
on 32bit. Here's the build log:

https://www.dropbox.com/s/23gel6zmv6ot91g/bpp-phyl.log?dl=0

I contacted the developers and they said it is probably a compiler
problem. Any ideas?

here are all slackbuilds, if someone is interested:

https://www.dropbox.com/sh/12cmeyv3qp0sjtm/AABofXi4ZR7VmqQoZNvO_dw2a?dl=0

-petar

From rshepard at appl-ecosys.com  Sun Jan 14 21:50:03 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sun, 14 Jan 2018 13:50:03 -0800 (PST)
Subject: [Slackbuilds-users] SBo: psycopg2
Message-ID: <alpine.LNX.2.20.1801141348120.5312@salmo.appl-ecosys.com>

   The SBo version of psycopg2 is 2.5.1 and the latest version of django
(2.0.1) requires psycopg2-2.5.4 at a minimum. The current version of
psycopg2 is 2.7.3.2 and I built is with the existing script with 3 changes:

   In the source tree I copied README.rst to README and in doc/ I added (by
using 'touch') two files: HACKING and html.

   Builds just fine.

   I wrote this message to Carlos and he responded that he's no longer
maintaining the script so I'm passing what I learned to the list.

Regards,

Rich

From baildon.research at googlemail.com  Sun Jan 14 23:16:11 2018
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 14 Jan 2018 23:16:11 +0000
Subject: [Slackbuilds-users] bpp-phyl build fail
In-Reply-To: <CAKXpWBdfd6gausPnF50v8q1TfZqZAZLkA_gP08TaSzxdHYL_Mg@mail.gmail.com>
References: <CAKXpWBdfd6gausPnF50v8q1TfZqZAZLkA_gP08TaSzxdHYL_Mg@mail.gmail.com>
Message-ID: <CAMt7G9SOhqpep3oCYpswkahOyeXdwsKGFp+_93RnQ3d3yi6y-A@mail.gmail.com>

Hi Petar,

> i am planning a minor update of bppsuite and its deps. Everything
> compiles fine on Slackware64, however, compilation of bpp-phyl breaks
> on 32bit. Here's the build log:
>
> https://www.dropbox.com/s/23gel6zmv6ot91g/bpp-phyl.log?dl=0
>
> I contacted the developers and they said it is probably a compiler
> problem. Any ideas?

Ok I reproduced your problem here.
So, I tried replacing g++ with clang [1], and it failed.

The clang error messages are more helpful than the gcc error messages.
It looks like this is a coding error, *not* a compiler error. For
example:

In file included from
/tmp/SBo/bpp-phyl-2.3.2a/src/Bpp/Phyl/Io/BppOSubstitutionModelFormat.cpp:113:
/tmp/SBo/bpp-phyl-2.3.2a/src/Bpp/Phyl/Io/../Model/RegisterRatesSubstitutionModel.h:154:36:
error: virtual function 'getModelStates' has a different return type
      ('vector<unsigned long>') than the function it overrides (which
has return type 'vector<size_t>')
    std::vector<long unsigned int> getModelStates(int i) const
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
/tmp/SBo/bpp-phyl-2.3.2a/src/Bpp/Phyl/Io/../Model/AbstractWrappedModel.h:77:25:
note: overridden virtual function is here
    std::vector<size_t> getModelStates(int code) const { return
getModel().getModelStates(code); }
    ~~~~~~~~~~~~~~~~~~~ ^

and

In file included from
/tmp/SBo/bpp-phyl-2.3.2a/src/Bpp/Phyl/Io/BppOSubstitutionModelFormat.cpp:113:
/tmp/SBo/bpp-phyl-2.3.2a/src/Bpp/Phyl/Io/../Model/RegisterRatesSubstitutionModel.h:156:14:
error: no viable conversion from returned value of type
'vector<size_t>' to function
      return type 'vector<unsigned long>'
      return AbstractWrappedSubstitutionModel::getModelStates(i);
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/bin/../lib/gcc/i586-slackware-linux/5.3.0/../../../../include/c++/5.3.0/bits/stl_vector.h:318:7:
note: candidate constructor not viable: no known conversion from
      'std::vector<size_t>' (aka 'vector<unsigned int>') to 'const
std::vector<unsigned long, std::allocator<unsigned long> > &' for 1st
argument
      vector(const vector& __x)
      ^

Full log at https://pastebin.com/RXbpNcSN
Thanks for testing on 32 bit :-)
-D.

[1] 'export CXX=clang' before the cmake command

From larryhaja at gmail.com  Mon Jan 15 17:48:19 2018
From: larryhaja at gmail.com (Larry Hajali)
Date: Mon, 15 Jan 2018 09:48:19 -0800
Subject: [Slackbuilds-users] libass ABI changes
In-Reply-To: <op.zcfz3l1l9z09aw@localhost>
References: <op.zcfz3l1l9z09aw@localhost>
Message-ID: <CAAZPBMghpjwSw9qYRKJLcwtTSidYaRuEv9W1-2QPyUM5gv8vgQ@mail.gmail.com>

I updated kodi to 17.6 and it built fine against libass 0.14.0.

--Larry

On Sat, Jan 6, 2018 at 3:12 PM, Edinaldo <edps.mundognu at gmail.com> wrote:

>
> Hi people,
>
> For your knowledge, QMPlay2 builds and works fine with libass 1.4.0.
>
> Cheers,
>
> Edinaldo.
>
> _______________________________________________
> 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/20180115/30d3f4c5/attachment-0001.html>

From rshepard at appl-ecosys.com  Mon Jan 15 18:18:59 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Mon, 15 Jan 2018 10:18:59 -0800 (PST)
Subject: [Slackbuilds-users] SQLAlchemy upgrade today
Message-ID: <alpine.LNX.2.20.1801151015390.23067@salmo.appl-ecosys.com>

   Yesterday I informed Dimitris that SQLAlchemy was at version 1.2.0 while
the SBo repository shows 1.1.14. He wrote back that he changed the version
in his repository. Well, today the SA devs released version 1.2.1 if that
can be used for the next changes release.

Regards,

Rich

From skaendo at excite.com  Tue Jan 16 08:26:05 2018
From: skaendo at excite.com (Ed Ender)
Date: Tue, 16 Jan 2018 03:26:05 -0500
Subject: [Slackbuilds-users] New SlackBuild submission concerns (cmark)
Message-ID: <20180116032605.16832@web003.roc2.bluetie.com>

I have a new submission for the repo, but I am a unsure if it is common to another SlackBuild in the repo, or if there will be any conflicts.

What I need to add is cmark. from here: https://github.com/commonmark/cmark

Why I need it is because mkvtoolnix from version 20.0.0 forward will require this package.

I have a SlackBuild all ready to go, (https://github.com/Skaendo/slackbuilds/tree/master/cmark), I just want to make sure that it wont bother haskell-cmark (https://slackbuilds.org/repository/14.2/haskell/haskell-cmark/).

Ed

From willysr at slackbuilds.org  Tue Jan 16 12:07:58 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 16 Jan 2018 19:07:58 +0700
Subject: [Slackbuilds-users] Electrum Advisory
In-Reply-To: <4c9e78ab-1331-6442-6318-6fb342a668d7@slackbuilds.org>
References: <4c9e78ab-1331-6442-6318-6fb342a668d7@slackbuilds.org>
Message-ID: <c6bd7545-67d9-0fdf-a0f3-136e2fb9ec08@slackbuilds.org>

> If Electrum 3.0.5 (or any later version) cannot be installed or does not
> work on your computer, stop using Electrum on that computer, and access
> your funds from a device that can run Electrum 3.0.5. If you really need
> to use an older version of Electrum, for example in order to access
> wallet seed, make sure that your computer is offline, and that no web
> browser is running on the computer at the same time.

Good news!

Upstream has decided to backport the fixes in 3.0.5 into a new releases
2.9.4. It has been pushed into my branch and it will be included in the
next public update:
https://git.slackbuilds.org/slackbuilds/commit/?h=willysr&id=ccd874d0ca59e0aaf030bebf86758f920e78325a


-- 
Willy Sudiarto Raharjo

-------------- 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/20180116/1f3f3df1/attachment.asc>

From klaatu at member.fsf.org  Tue Jan 16 10:20:58 2018
From: klaatu at member.fsf.org (Klaatu)
Date: Tue, 16 Jan 2018 23:20:58 +1300
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <18E264C1-7511-43E1-A15A-9A84A18CA699@ythogtha.org>
References: <20180107133307.GB1245@hili.localdomain>
 <18E264C1-7511-43E1-A15A-9A84A18CA699@ythogtha.org>
Message-ID: <8a9860d3-8637-8e95-73ab-81df76f279a9@member.fsf.org>

I use pandoc frequently.

But I cheat, and steal a few RPMs from Fedora and use those. It's a
statically-compiled version of pandoc and some stylesheets. Simple.

If no one else takes pandoc, I'll take it. But it'll be Pandoc and it'll
just rpm2tgz packages from Fedora.

Everybody cool with that?

-klaatu





On 01/07/2018 09:47 PM, Arnaud wrote:
> Le 7 janvier 2018 03:33:07 GMT+01:00, Peter Wang <novalazy at gmail.com> a
> ?crit :
> 
>     Hi,
> 
>     I am giving up maintainership of my scripts:
> 
>     desktop/xfce4-cpugraph-plugin
>     development/latrace
>     development/valgrind
>     libraries/allegro4
>     misc/tal
>     office/pandoc
>     system/oldschool-pc-fonts
> 
>     Please take care of my babies.
> 
>     Peter
>     ------------------------------------------------------------------------
> 
>     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/
> 
> 
> I'll take allegro4 since I already maintain allegro5.
> 
> Yth
> -- 
> Envoy? de mon appareil Android avec K-9 Mail. Veuillez excuser ma bri?vet?.
> 
> 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 


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

From yalhcru at gmail.com  Tue Jan 16 23:45:46 2018
From: yalhcru at gmail.com (B Watson)
Date: Tue, 16 Jan 2018 18:45:46 -0500
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <8a9860d3-8637-8e95-73ab-81df76f279a9@member.fsf.org>
References: <20180107133307.GB1245@hili.localdomain>
 <18E264C1-7511-43E1-A15A-9A84A18CA699@ythogtha.org>
 <8a9860d3-8637-8e95-73ab-81df76f279a9@member.fsf.org>
Message-ID: <CAN1hMuC2nOw+3xDbLzWqCyBN1LUnCo-_BpJxWJbim=opoXF=ow@mail.gmail.com>

On 1/16/18, Klaatu <klaatu at member.fsf.org> wrote:
>
> If no one else takes pandoc, I'll take it. But it'll be Pandoc and it'll
> just rpm2tgz packages from Fedora.
>
> Everybody cool with that?

I can see why you'd do it that way. The existing pandoc build has 106
dependencies in its tree!

$ sbodeps -qi pandoc
ghc
haskell-foundation
haskell-memory
haskell-hourglass
haskell-extensible-exceptions
haskell-transformers-compat
haskell-text
haskell-stm
haskell-primitive
haskell-mtl
haskell-byteable
haskell-asn1-types
haskell-vector
haskell-transformers-base
haskell-securemem
haskell-hashable
haskell-cryptonite
haskell-base64-bytestring
haskell-asn1-encoding
haskell-unordered-containers
haskell-tagged
haskell-pem
haskell-monad-control
haskell-cryptohash
haskell-crypto-random
haskell-crypto-pubkey-types
haskell-asn1-parse
haskell-x509
haskell-text-icu
haskell-semigroups
haskell-parsec
haskell-old-locale
haskell-mmorph
haskell-lifted-base
haskell-exceptions
haskell-dlist
haskell-data-default-class
haskell-crypto-numbers
haskell-cereal
haskell-x509-store
haskell-void
haskell-stringprep
haskell-scientific
haskell-resourcet
haskell-punycode
haskell-network
haskell-data-default-instances-old-locale
haskell-data-default-instances-dlist
haskell-data-default-instances-containers
haskell-data-default-instances-base
haskell-crypto-pubkey
haskell-crypto-cipher-types
haskell-zlib
haskell-x509-validation
haskell-utf8-string
haskell-syb
haskell-random
haskell-idna
haskell-data-default
haskell-conduit
haskell-cipher-rc4
haskell-cipher-des
haskell-cipher-aes
haskell-case-insensitive
haskell-blaze-builder
haskell-attoparsec
haskell-async
haskell-x509-system
haskell-tls
haskell-streaming-commons
haskell-socks
haskell-regex-base
haskell-publicsuffixlist
haskell-network-uri
haskell-mime-types
haskell-http-types
haskell-deepseq-generics
haskell-cookie
haskell-blaze-markup
haskell-aeson
haskell-xml
haskell-unix-compat
haskell-regex-pcre-builtin
haskell-pandoc-types
haskell-old-time
haskell-mmap
haskell-http-client
haskell-enclosed-exceptions
haskell-digest
haskell-connection
haskell-blaze-html
haskell-zip-archive
haskell-yaml
haskell-texmath
haskell-temporary
haskell-tagsoup
haskell-http-client-tls
haskell-hslua
haskell-highlighting-kate
haskell-haddock-library
haskell-filemanip
haskell-cmark
haskell-SHA
haskell-JuicyPixels
haskell-HTTP
pandoc

From thedoogster at gmail.com  Tue Jan 16 23:59:24 2018
From: thedoogster at gmail.com (Doogster)
Date: Tue, 16 Jan 2018 15:59:24 -0800
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <CAN1hMuC2nOw+3xDbLzWqCyBN1LUnCo-_BpJxWJbim=opoXF=ow@mail.gmail.com>
References: <20180107133307.GB1245@hili.localdomain>
 <18E264C1-7511-43E1-A15A-9A84A18CA699@ythogtha.org>
 <8a9860d3-8637-8e95-73ab-81df76f279a9@member.fsf.org>
 <CAN1hMuC2nOw+3xDbLzWqCyBN1LUnCo-_BpJxWJbim=opoXF=ow@mail.gmail.com>
Message-ID: <CAE5oDabfvRx+scZac2hmBfvt8d1zBtr61BvQJYH+bOuFkFfYHQ@mail.gmail.com>

Here's an easier Pandoc SlackBuild. The only drawback is that it's x86_64-only.

https://www.linuxquestions.org/questions/slackware-14/installing-pandoc-on-current-x86_64-the-easy-way-4175620166/

On Tue, Jan 16, 2018 at 3:45 PM, B Watson <yalhcru at gmail.com> wrote:
> On 1/16/18, Klaatu <klaatu at member.fsf.org> wrote:
>>
>> If no one else takes pandoc, I'll take it. But it'll be Pandoc and it'll
>> just rpm2tgz packages from Fedora.
>>
>> Everybody cool with that?
>
> I can see why you'd do it that way. The existing pandoc build has 106
> dependencies in its tree!
>
> $ sbodeps -qi pandoc
> ghc
> haskell-foundation
> haskell-memory
> haskell-hourglass
> haskell-extensible-exceptions
> haskell-transformers-compat
> haskell-text
> haskell-stm
> haskell-primitive
> haskell-mtl
> haskell-byteable
> haskell-asn1-types
> haskell-vector
> haskell-transformers-base
> haskell-securemem
> haskell-hashable
> haskell-cryptonite
> haskell-base64-bytestring
> haskell-asn1-encoding
> haskell-unordered-containers
> haskell-tagged
> haskell-pem
> haskell-monad-control
> haskell-cryptohash
> haskell-crypto-random
> haskell-crypto-pubkey-types
> haskell-asn1-parse
> haskell-x509
> haskell-text-icu
> haskell-semigroups
> haskell-parsec
> haskell-old-locale
> haskell-mmorph
> haskell-lifted-base
> haskell-exceptions
> haskell-dlist
> haskell-data-default-class
> haskell-crypto-numbers
> haskell-cereal
> haskell-x509-store
> haskell-void
> haskell-stringprep
> haskell-scientific
> haskell-resourcet
> haskell-punycode
> haskell-network
> haskell-data-default-instances-old-locale
> haskell-data-default-instances-dlist
> haskell-data-default-instances-containers
> haskell-data-default-instances-base
> haskell-crypto-pubkey
> haskell-crypto-cipher-types
> haskell-zlib
> haskell-x509-validation
> haskell-utf8-string
> haskell-syb
> haskell-random
> haskell-idna
> haskell-data-default
> haskell-conduit
> haskell-cipher-rc4
> haskell-cipher-des
> haskell-cipher-aes
> haskell-case-insensitive
> haskell-blaze-builder
> haskell-attoparsec
> haskell-async
> haskell-x509-system
> haskell-tls
> haskell-streaming-commons
> haskell-socks
> haskell-regex-base
> haskell-publicsuffixlist
> haskell-network-uri
> haskell-mime-types
> haskell-http-types
> haskell-deepseq-generics
> haskell-cookie
> haskell-blaze-markup
> haskell-aeson
> haskell-xml
> haskell-unix-compat
> haskell-regex-pcre-builtin
> haskell-pandoc-types
> haskell-old-time
> haskell-mmap
> haskell-http-client
> haskell-enclosed-exceptions
> haskell-digest
> haskell-connection
> haskell-blaze-html
> haskell-zip-archive
> haskell-yaml
> haskell-texmath
> haskell-temporary
> haskell-tagsoup
> haskell-http-client-tls
> haskell-hslua
> haskell-highlighting-kate
> haskell-haddock-library
> haskell-filemanip
> haskell-cmark
> haskell-SHA
> haskell-JuicyPixels
> haskell-HTTP
> pandoc
> _______________________________________________
> 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 klaatu at member.fsf.org  Tue Jan 16 11:39:07 2018
From: klaatu at member.fsf.org (Klaatu)
Date: Wed, 17 Jan 2018 00:39:07 +1300
Subject: [Slackbuilds-users] Abandoning my SlackBuilds
In-Reply-To: <CAE5oDabfvRx+scZac2hmBfvt8d1zBtr61BvQJYH+bOuFkFfYHQ@mail.gmail.com>
References: <20180107133307.GB1245@hili.localdomain>
 <18E264C1-7511-43E1-A15A-9A84A18CA699@ythogtha.org>
 <8a9860d3-8637-8e95-73ab-81df76f279a9@member.fsf.org>
 <CAN1hMuC2nOw+3xDbLzWqCyBN1LUnCo-_BpJxWJbim=opoXF=ow@mail.gmail.com>
 <CAE5oDabfvRx+scZac2hmBfvt8d1zBtr61BvQJYH+bOuFkFfYHQ@mail.gmail.com>
Message-ID: <8911963b-e169-47b0-a8e4-f8e0ef993f08@member.fsf.org>

On 01/17/2018 12:59 PM, Doogster wrote:
> Here's an easier Pandoc SlackBuild. The only drawback is that it's x86_64-only.
> 
> https://www.linuxquestions.org/questions/slackware-14/installing-pandoc-on-current-x86_64-the-easy-way-4175620166/
> 

Heck, that IS easier. Especially since I just noticed that Fedora has
lately stopped doing the static build.

Thanks for the tip!

-klaatu





> On Tue, Jan 16, 2018 at 3:45 PM, B Watson <yalhcru at gmail.com> wrote:
>> On 1/16/18, Klaatu <klaatu at member.fsf.org> wrote:
>>>
>>> If no one else takes pandoc, I'll take it. But it'll be Pandoc and it'll
>>> just rpm2tgz packages from Fedora.
>>>
>>> Everybody cool with that?
>>
>> I can see why you'd do it that way. The existing pandoc build has 106
>> dependencies in its tree!
>>
>> $ sbodeps -qi pandoc
>> ghc
>> haskell-foundation
>> haskell-memory
>> haskell-hourglass
>> haskell-extensible-exceptions
>> haskell-transformers-compat
>> haskell-text
>> haskell-stm
>> haskell-primitive
>> haskell-mtl
>> haskell-byteable
>> haskell-asn1-types
>> haskell-vector
>> haskell-transformers-base
>> haskell-securemem
>> haskell-hashable
>> haskell-cryptonite
>> haskell-base64-bytestring
>> haskell-asn1-encoding
>> haskell-unordered-containers
>> haskell-tagged
>> haskell-pem
>> haskell-monad-control
>> haskell-cryptohash
>> haskell-crypto-random
>> haskell-crypto-pubkey-types
>> haskell-asn1-parse
>> haskell-x509
>> haskell-text-icu
>> haskell-semigroups
>> haskell-parsec
>> haskell-old-locale
>> haskell-mmorph
>> haskell-lifted-base
>> haskell-exceptions
>> haskell-dlist
>> haskell-data-default-class
>> haskell-crypto-numbers
>> haskell-cereal
>> haskell-x509-store
>> haskell-void
>> haskell-stringprep
>> haskell-scientific
>> haskell-resourcet
>> haskell-punycode
>> haskell-network
>> haskell-data-default-instances-old-locale
>> haskell-data-default-instances-dlist
>> haskell-data-default-instances-containers
>> haskell-data-default-instances-base
>> haskell-crypto-pubkey
>> haskell-crypto-cipher-types
>> haskell-zlib
>> haskell-x509-validation
>> haskell-utf8-string
>> haskell-syb
>> haskell-random
>> haskell-idna
>> haskell-data-default
>> haskell-conduit
>> haskell-cipher-rc4
>> haskell-cipher-des
>> haskell-cipher-aes
>> haskell-case-insensitive
>> haskell-blaze-builder
>> haskell-attoparsec
>> haskell-async
>> haskell-x509-system
>> haskell-tls
>> haskell-streaming-commons
>> haskell-socks
>> haskell-regex-base
>> haskell-publicsuffixlist
>> haskell-network-uri
>> haskell-mime-types
>> haskell-http-types
>> haskell-deepseq-generics
>> haskell-cookie
>> haskell-blaze-markup
>> haskell-aeson
>> haskell-xml
>> haskell-unix-compat
>> haskell-regex-pcre-builtin
>> haskell-pandoc-types
>> haskell-old-time
>> haskell-mmap
>> haskell-http-client
>> haskell-enclosed-exceptions
>> haskell-digest
>> haskell-connection
>> haskell-blaze-html
>> haskell-zip-archive
>> haskell-yaml
>> haskell-texmath
>> haskell-temporary
>> haskell-tagsoup
>> haskell-http-client-tls
>> haskell-hslua
>> haskell-highlighting-kate
>> haskell-haddock-library
>> haskell-filemanip
>> haskell-cmark
>> haskell-SHA
>> haskell-JuicyPixels
>> haskell-HTTP
>> pandoc
>> _______________________________________________
>> 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 --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180117/b3ea0df2/attachment-0001.asc>

From willysr at slackbuilds.org  Wed Jan 17 11:54:39 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 17 Jan 2018 18:54:39 +0700
Subject: [Slackbuilds-users] SBo: psycopg2
In-Reply-To: <alpine.LNX.2.20.1801141348120.5312@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801141348120.5312@salmo.appl-ecosys.com>
Message-ID: <8dafd3d3-6a8b-f913-b603-817a3dc6896a@slackbuilds.org>

> ? The SBo version of psycopg2 is 2.5.1 and the latest version of django
> (2.0.1) requires psycopg2-2.5.4 at a minimum. The current version of
> psycopg2 is 2.7.3.2 and I built is with the existing script with 3 changes:
> 
> ? In the source tree I copied README.rst to README and in doc/ I added (by
> using 'touch') two files: HACKING and html.
> 
> ? Builds just fine.
> 
> ? I wrote this message to Carlos and he responded that he's no longer
> maintaining the script so I'm passing what I learned to the list.

If you are using it and interested to take over, feel free to submit an
update for that.


-- 
Willy Sudiarto Raharjo

-------------- 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/20180117/3f4bf85d/attachment.asc>

From willysr at slackbuilds.org  Wed Jan 17 12:58:44 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 17 Jan 2018 19:58:44 +0700
Subject: [Slackbuilds-users] Updates - 20180117.1
Message-ID: <4e7d73e9-730f-e228-b732-c2ea3c5c4831@slackbuilds.org>

Hi all

we have another unscheduled update due to several security fixes that's
included in this batch: jdk, Electrum, pepperflash-plugins, and
transmission. We have some browsers update in this batch as well and
since some of those are based on Firefox, they might contains security
fixes as well.

As promised, we move on with nodejs to use latest LTS 8.x while nodejs6
is now available for those not compatible with nodejs 8.x yet. Ponce
also pushed libass to 0.14.0 since everything is working well with this
version.


Wed Jan 17 12:47:21 UTC 2018
academic/libqalculate: Updated for version 2.2.0
academic/qalculate-gtk: Updated for version 2.2.0
academic/speedcrunch: Updated for version 0.12.0
academic/sword-data-kjv: Updated for version 1.8.1.
academic/sword: Updated for version 1.8.1.
academic/trfind: Fix executable for use with RepeatMasker.
audio/sayonara-player: Updated for version 1.0.0_git5_20180115.
desktop/candle: Added (G-Code visualizer).
desktop/dunst: Updated for version 1.3.0.
desktop/flatpak: Update README.
desktop/lxhotkey: Added (a keyboard shortcuts configurator).
development/SQLAlchemy: Updated for version 1.2.0.
development/atom: Updated for version 1.23.3.
development/bvi: Updated for version 1.4.0
development/hhvm: Updated for version 3.24.0
development/jdk: Updated for version 8u162.
development/jupyter-notebook: Updated for version 5.3.1.
development/nodejs6: Added (JavaScript runtime).
development/nodejs: Updated for version 8.9.4.
development/perf: Updated for version 4.4.111.
development/sassc: Updated for version 3.4.8.
development/tea: Updated for version 44.1.1 + new maintainer.
development/universal-ctags: Updated for version 1620c63
development/vscode: Switch to nodejs6.
development/yarn: Added (Secure Dependency Management).
games/open-adventure: Updated for version 1.4.
games/stone_soup: Fixed VERSION.
gis/postgis: Updated for version 2.4.3.
graphics/opencollada: Updated for version 1.6.62
libraries/SDL_kitchensink: Fixed download & script.
libraries/cmark: Added (C Reference libraries).
libraries/libass: Updated for version 0.14.0.
libraries/libsass: Updated for version 3.4.8.
libraries/qml-material: Added (Material Design).
libraries/uriparser: Fix docs installation errors.
misc/par2cmdline: Updated for version 0.8.0.
misc/sbo-templates: Updated for version 1.0.2.
multimedia/gpodder: Fix the download url.
multimedia/kodi: Updated for version 17.6
multimedia/pepperflash-plugin: Updated for version 28.0.0.137.
network/Electrum: Updated for version 2.9.4.
network/PaleMoon: Updated for version 27.7.0.
network/brave: Added (web browser).
network/netsniff-ng: Updated for version 0.6.4.
network/opensmtpd: Updated for version 6.0.3p1.
network/palemoon: Updated for version 27.7.0.
network/qutebrowser: Updated for version 1.1.0.
network/transmission: Security fix.
network/waterfox: Updated for version 56.0.3.
python/decorator: Updated for version 4.2.1.
python/dnspython: Added python3 support
python/python-keyring: Updated for version 10.6.0.
python/python3-decorator: Updated for version 4.2.1.
python/send2trash: Added (send files to trash).
system/guake: Updated for version 0.8.13.
system/hh: Updated for version 1.24.
system/joyce: Added (Amstrad PCW emulator).
system/ksh-openbsd: Updated for version 20180115.
system/lynis: Updated for version 2.5.9.
system/lz4: Updated for version 1.8.1.2.
system/netatop: Bump BUILD for kernel changes.
system/open-vm-tools: Fixed VERSION.
system/pspg: Updated for version 0.9.2.
system/ranger: Updated for version 1.9.0b6.
system/slpkg: Fixed md5sum.
system/vbindiff: Update md5sum.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- 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/20180117/8e59f49f/attachment.asc>

From rshepard at appl-ecosys.com  Wed Jan 17 13:58:16 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Wed, 17 Jan 2018 05:58:16 -0800 (PST)
Subject: [Slackbuilds-users] SBo: psycopg2
In-Reply-To: <8dafd3d3-6a8b-f913-b603-817a3dc6896a@slackbuilds.org>
References: <alpine.LNX.2.20.1801141348120.5312@salmo.appl-ecosys.com>
 <8dafd3d3-6a8b-f913-b603-817a3dc6896a@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.1801170556360.6541@salmo.appl-ecosys.com>

On Wed, 17 Jan 2018, Willy Sudiarto Raharjo wrote:

> If you are using it and interested to take over, feel free to submit an
> update for that.

Willy,

   I do not know how to create or fix build scripts. A tool like psycopg2 is
used only infrequently and not regularly.

Rich

From s.arcus at open-t.co.uk  Wed Jan 17 17:02:01 2018
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Wed, 17 Jan 2018 17:02:01 +0000
Subject: [Slackbuilds-users] MTA used by submission form doesn't use FQDN in
 HELO
Message-ID: <ce23ec50-962b-8334-3708-4fd05fb874b8@open-t.co.uk>

The submission form at SBo does a check on the email address to the 
originating MTA when a package is uploaded. However, the MTA used by the 
submission form uses just "slackbuilds.org" as HELO name. I know the RFC 
only recommends, not requires, a FQDN for smtp HELO names, but the vast 
majority of reputable SMTP servers use an FQDN nowadays. So much so 
that, as an email server admin, you are pretty safe rejecting 
connections presenting any other type of HELO, as they are 99.9% spam 
from trojan bots.

I just tried to upload a package update at SBo, and had my email address 
rejected, as my own email server, in turn, rejected the connection 
attempt from SBo. I temporarily disabled the relevant check in my 
config, but would it be possible to reconfigure the MTA at SBo's end at 
some point, to present a FQDN, not just "slackbuilds.org"? The mailing 
list comes from a different MTA, I presume, as it presents a proper 
HELO. Only a suggestion.

From slackbuilds at jaxartes.net  Wed Jan 17 17:12:16 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Wed, 17 Jan 2018 09:12:16 -0800
Subject: [Slackbuilds-users] SBo: psycopg2
In-Reply-To: <alpine.LNX.2.20.1801170556360.6541@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801141348120.5312@salmo.appl-ecosys.com>
 <8dafd3d3-6a8b-f913-b603-817a3dc6896a@slackbuilds.org>
 <alpine.LNX.2.20.1801170556360.6541@salmo.appl-ecosys.com>
Message-ID: <8b62231f-7699-2e86-df2d-95a2cb1c7fe9@jaxartes.net>

On 2018-01-17 05:58 AM, Rich Shepard wrote:
> On Wed, 17 Jan 2018, Willy Sudiarto Raharjo wrote:
> 
>> If you are using it and interested to take over, feel free to submit an
>> update for that.
> 
> Willy,
> 
>  ? I do not know how to create or fix build scripts. A tool like 
> psycopg2 is
> used only infrequently and not regularly.

I'll take over psycopg2 as it's a QGIS dependency.

Best, Ben


From kjhambrick at gmail.com  Wed Jan 17 20:52:11 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Wed, 17 Jan 2018 14:52:11 -0600
Subject: [Slackbuilds-users] Proper Procedure for updating an existing
 SlackBuild
Message-ID: <CANBHt+Mb-fd_PiuBGjGU7PpMVDUfrK=s0Es+kU=MXd2rj4Hv0g@mail.gmail.com>

All --

I am the maintainer of a few SlackBuilds.

I would like to submit an update for my fswatch.SlackBuild

What is the proper procedure ?

Thank you.

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180117/c6c74f99/attachment.html>

From kjhambrick at gmail.com  Wed Jan 17 21:14:37 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Wed, 17 Jan 2018 15:14:37 -0600
Subject: [Slackbuilds-users] Proper Procedure for updating an existing
 SlackBuild
In-Reply-To: <CANBHt+Mb-fd_PiuBGjGU7PpMVDUfrK=s0Es+kU=MXd2rj4Hv0g@mail.gmail.com>
References: <CANBHt+Mb-fd_PiuBGjGU7PpMVDUfrK=s0Es+kU=MXd2rj4Hv0g@mail.gmail.com>
Message-ID: <CANBHt+PN_4xEBJb4mexQEimWZKW4kQLgQK_i+OTJcZ0UZP9vfA@mail.gmail.com>

Never mind.

I believe I figured it out and I was able to submit an update for fswatch
to version 1.11.2

Sorry about the moise ...

-- kjh

On Wed, Jan 17, 2018 at 2:52 PM, Konrad J Hambrick <kjhambrick at gmail.com>
wrote:

> All --
>
> I am the maintainer of a few SlackBuilds.
>
> I would like to submit an update for my fswatch.SlackBuild
>
> What is the proper procedure ?
>
> Thank you.
>
> -- kjh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180117/235c8c2d/attachment.html>

From rob0 at slackbuilds.org  Wed Jan 17 23:57:36 2018
From: rob0 at slackbuilds.org (Rob McGee)
Date: Wed, 17 Jan 2018 17:57:36 -0600
Subject: [Slackbuilds-users] MTA used by submission form doesn't use
 FQDN in HELO
In-Reply-To: <ce23ec50-962b-8334-3708-4fd05fb874b8@open-t.co.uk>
References: <ce23ec50-962b-8334-3708-4fd05fb874b8@open-t.co.uk>
Message-ID: <20180117235735.GO2027@harrier.slackbuilds.org>

On Wed, Jan 17, 2018 at 05:02:01PM +0000, Sebastian Arcus wrote:
> The submission form at SBo does a check on the email address to the
> originating MTA when a package is uploaded.

The check is done at the MX for the domain, specifically.

> However, the MTA used by the submission form uses just 
> "slackbuilds.org" as HELO name. I know the RFC only recommends,
> not requires, a FQDN for smtp HELO names,

(Note, there is no MTA involved.  This is just a simple PHP form 
attempting to validate the email addresses it is given.)

FQDN as HELO is required, but indeed "slackbuilds.org" is a FQDN.  If 
you're using Postfix, note that the smtpd restriction, 
"reject_non_fqdn_helo_hostname", would not reject that.  Neither 
would "reject_invalid_helo_hostname"; it's a perfectly valid HELO 
hostname in accordance with RFC5321 and related standards.

Note also that the host has forward-confirmed reverse DNS as 
"slackbuilds.org", so that HELO name really is the most appropriate 
choice.  We're also listed in DNSWL.org, and spam complaints would 
have us removed from that list.

> ... but the vast majority of reputable SMTP servers use an FQDN 
> nowadays. So much so that, as an email server admin, you are pretty 
> safe rejecting connections presenting any other type of HELO, as 
> they are 99.9% spam from trojan bots.

I think there are usually safer indications of spam zombies than 
a FQDN HELO hostname consisting of only two labels.  But I'll concede 
your point, that the vast majority of good mailers have three or more 
labels in their hostname.

> I just tried to upload a package update at SBo, and had my email 
> address rejected, as my own email server, in turn, rejected the 
> connection attempt from SBo. I temporarily disabled the relevant 
> check in my config,

Would you mind telling me what you did that rejected this?  Also 
please share your MTA logs of the rejection.  Offlist is fine if 
you're shy about posting logs here.

> ... but would it be possible to reconfigure the MTA at SBo's end
> at some point, to present a FQDN, not just "slackbuilds.org"?

Thank you for the suggestion.  While I disagree with the details, 
such as what constitutes a FQDN, we are not [yet?] rejecting the 
idea.  It's possible that this has been the reason for other sites 
rejecting our email address probes.

> The mailing list comes from a different
> MTA, I presume, as it presents a proper HELO. Only a suggestion.

Yes, the list is from a MTA at a different site.
-- 
    Rob McGee - /dev/rob0 - rob0 at slackbuilds.org

From willysr at slackbuilds.org  Thu Jan 18 02:09:49 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 18 Jan 2018 09:09:49 +0700
Subject: [Slackbuilds-users] Electrum 3 for review
Message-ID: <a5861e8e-593c-0ef0-fa89-f3bf8e9d31e0@slackbuilds.org>

Hi,

I have pushed a new branch Electrum3-review for those interested to get
Electrum 3.x.

It's a big change since it now exclusively use Python 3 and Qt5
(actually PyQt5, but it depends on qt5 -> qt5-webkit -> python-PyQt5).

You need to install Python3 first before (re) building all deps as we
need the Python 3 bindings. Most of the scripts have Python 3 supports,
except for 4 scripts that exclusively have python3-xxx naming
(python3-PyQt5, python3-dateutil, python3-sip, python3-sip).

It would be a good idea to test them on a clean environment to make sure
we don't get an overlap or missing dependencies.

Thanks

-- 
Willy Sudiarto Raharjo

-------------- 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/20180118/f93fee89/attachment.asc>

From s.arcus at open-t.co.uk  Thu Jan 18 09:10:57 2018
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Thu, 18 Jan 2018 09:10:57 +0000
Subject: [Slackbuilds-users] MTA used by submission form doesn't use
 FQDN in HELO
In-Reply-To: <20180117235735.GO2027@harrier.slackbuilds.org>
References: <ce23ec50-962b-8334-3708-4fd05fb874b8@open-t.co.uk>
 <20180117235735.GO2027@harrier.slackbuilds.org>
Message-ID: <e04f6284-4abb-9630-4e74-f37d6d98bf47@open-t.co.uk>


On 17/01/18 23:57, Rob McGee wrote:
> On Wed, Jan 17, 2018 at 05:02:01PM +0000, Sebastian Arcus wrote:
>> The submission form at SBo does a check on the email address to the
>> originating MTA when a package is uploaded.
> 
> The check is done at the MX for the domain, specifically.
> 
>> However, the MTA used by the submission form uses just
>> "slackbuilds.org" as HELO name. I know the RFC only recommends,
>> not requires, a FQDN for smtp HELO names,
> 
> (Note, there is no MTA involved.  This is just a simple PHP form
> attempting to validate the email addresses it is given.)
> 
> FQDN as HELO is required, but indeed "slackbuilds.org" is a FQDN. 

I might be misinterpreting things, but all docs I looked up so far seem 
to imply that a FQDN should include the hostname - and whenever FQDN is 
mentioned, usually it includes the hostname. After all, FQDN's are used 
to identify hosts. "slackbuilds.org" is just the domain part. But maybe 
there is a nuance which I'm missing here. Or you could take the view 
that a domain name can be used as a hostname at the same time.

>> I just tried to upload a package update at SBo, and had my email
>> address rejected, as my own email server, in turn, rejected the
>> connection attempt from SBo. I temporarily disabled the relevant
>> check in my config,
> 
> Would you mind telling me what you did that rejected this?  Also
> please share your MTA logs of the rejection.  Offlist is fine if
> you're shy about posting logs here.

I use Exim with a custom ACL, which checks the HELO for a full FQDN, 
including a hostname, not just the domain. As stated in my original 
post, the script/form is not technically breaking any standards - it was 
just a suggestion.


From willysr at slackbuilds.org  Thu Jan 18 13:50:35 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 18 Jan 2018 20:50:35 +0700
Subject: [Slackbuilds-users] letsencrypt updates
Message-ID: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>

Hi

If anyone wondered why there aren't any update to letsencrypt even
though new version gets released already, the answer is because there
has been a change upstream so it broke letsencrypt when deployed in
Slackware since 0.20.0 (https://github.com/certbot/certbot/issues/5332).

in short, they are checking for apache2ctl command instead of apachectl
which is by default used in Slackware. While they provided override
classes for other distributions, none for Slackware at this moment.

there are some solutions:
- ask for Patrick to add symlink in -stable (and -current)
- wait for upstream to fix the issue
- add the symlink manually
- someone make override class for Slackware and send PR to upstream

for those who prefer to try the third method, i have pushed a new branch
letsencrypt-review
(https://git.slackbuilds.org/slackbuilds/log/?h=letsencrypt-review) that
can be used to test the new version of letsencrypt, but please read the
README. You will also need josepy which is still in pending as a new
dependency for letsencrypt 0.21.0. Hopefully it can be merged in the
next public update.

I have tested 0.21.0 on a production machine with a manual symlink +
josepy and it worked fine for certificate renewals.


-- 
Willy Sudiarto Raharjo

-------------- 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/20180118/8a87ef0f/attachment.asc>

From yalhcru at gmail.com  Thu Jan 18 19:45:36 2018
From: yalhcru at gmail.com (B Watson)
Date: Thu, 18 Jan 2018 14:45:36 -0500
Subject: [Slackbuilds-users] statifier
Message-ID: <CAN1hMuAM=L+z8hH6FWLMExf+zndAzo5XLvAF+nGp0EwhSFSqEQ@mail.gmail.com>

Unless someone objects, I'm taking over statifier. Niels Horn, the current
maintainer, said in an email that he's not maintaining it any more.

Actually, looking at the git log, it doesn't look like he's maintaining
anything, his last update was in April 2014.

From eric.b.pratt at gmail.com  Thu Jan 18 19:51:18 2018
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Thu, 18 Jan 2018 11:51:18 -0800
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
Message-ID: <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>

On Thu, Jan 18, 2018 at 5:50 AM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> Hi
>
> If anyone wondered why there aren't any update to letsencrypt even
> though new version gets released already, the answer is because there
> has been a change upstream so it broke letsencrypt when deployed in
> Slackware since 0.20.0 (https://github.com/certbot/certbot/issues/5332).
>
> in short, they are checking for apache2ctl command instead of apachectl
> which is by default used in Slackware. While they provided override
> classes for other distributions, none for Slackware at this moment.
>
> there are some solutions:
> - ask for Patrick to add symlink in -stable (and -current)
> - wait for upstream to fix the issue
> - add the symlink manually
> - someone make override class for Slackware and send PR to upstream
>
>
?I think the correct solution is for Patrick to add a symlink in the
distro.  Since apachectl is the default, I don't know why we would want
that changed in slackware.  Making apache2ctl a symlink to apachectl would
seem to be the right solution.  However, I don't really think it matters
which one is the symlink.?

I suspect it was called apache2ctl originally so you could have apache 1.x
and 2.x installed side-by-side on the same box.  The only real problem this
would create would be a conflict if someone is actually still running
apache 1.x on modern Slackware distros.  I doubt that's the case, but it's
not beyond the realm of possibility.  In that case, I would rather see the
apachectl for apache 1.x be renamed to apache1ctl or something like that
than to see the one from apache 2.x renamed.

Although, I think the best solution would be a combination of 1 and 4.  We
should try to get the override class in place, but we should also try to
stick with the apache default as much as possible even if letsencrypt
weren't an issue here.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180118/f4ecb6a2/attachment.html>

From francois.gingras at gmail.com  Thu Jan 18 20:40:50 2018
From: francois.gingras at gmail.com (Francois Gingras)
Date: Thu, 18 Jan 2018 15:40:50 -0500
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
Message-ID: <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>

On Thu, Jan 18, 2018 at 2:51 PM, Eric Pratt <eric.b.pratt at gmail.com> wrote:

> On Thu, Jan 18, 2018 at 5:50 AM, Willy Sudiarto Raharjo <
> willysr at slackbuilds.org> wrote:
>
>> Hi
>>
>> If anyone wondered why there aren't any update to letsencrypt even
>> though new version gets released already, the answer is because there
>> has been a change upstream so it broke letsencrypt when deployed in
>> Slackware since 0.20.0 (https://github.com/certbot/certbot/issues/5332).
>>
>> in short, they are checking for apache2ctl command instead of apachectl
>> which is by default used in Slackware. While they provided override
>> classes for other distributions, none for Slackware at this moment.
>>
>> there are some solutions:
>> - ask for Patrick to add symlink in -stable (and -current)
>> - wait for upstream to fix the issue
>> - add the symlink manually
>> - someone make override class for Slackware and send PR to upstream
>>
>>
> ?I think the correct solution is for Patrick to add a symlink in the
> distro.  Since apachectl is the default, I don't know why we would want
> that changed in slackware.  Making apache2ctl a symlink to apachectl would
> seem to be the right solution.  However, I don't really think it matters
> which one is the symlink.?
>
> I suspect it was called apache2ctl originally so you could have apache 1.x
> and 2.x installed side-by-side on the same box.  The only real problem this
> would create would be a conflict if someone is actually still running
> apache 1.x on modern Slackware distros.  I doubt that's the case, but it's
> not beyond the realm of possibility.  In that case, I would rather see the
> apachectl for apache 1.x be renamed to apache1ctl or something like that
> than to see the one from apache 2.x renamed.
>
> Although, I think the best solution would be a combination of 1 and 4.  We
> should try to get the override class in place, but we should also try to
> stick with the apache default as much as possible even if letsencrypt
> weren't an issue here.
>
>
> _______________________________________________
> 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/
>
>
>
I'm -1 on renaming the apachectl script - the script is called as such
upstream, and I can't see a single valid reason to rename it.

Just because other debian-based distros did that doesn't mean it's the sane
approach.

Now, I do realize that we do have to "play ball" with other distro's
quirks, unfortunately. As such, creating a symlink from apache2ctl ->
apachectl is probably the least disruptive approach.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180118/0f85913c/attachment-0001.html>

From jgraha8 at gmail.com  Thu Jan 18 21:01:08 2018
From: jgraha8 at gmail.com (Jason Graham)
Date: Thu, 18 Jan 2018 16:01:08 -0500
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
Message-ID: <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>

Can we just patch the OS_DEFAULTS in the configurator until an OS override
can be added upstream?

Jason

On Jan 18, 2018 3:40 PM, "Francois Gingras" <francois.gingras at gmail.com>
wrote:

>
> On Thu, Jan 18, 2018 at 2:51 PM, Eric Pratt <eric.b.pratt at gmail.com>
> wrote:
>
>> On Thu, Jan 18, 2018 at 5:50 AM, Willy Sudiarto Raharjo <
>> willysr at slackbuilds.org> wrote:
>>
>>> Hi
>>>
>>> If anyone wondered why there aren't any update to letsencrypt even
>>> though new version gets released already, the answer is because there
>>> has been a change upstream so it broke letsencrypt when deployed in
>>> Slackware since 0.20.0 (https://github.com/certbot/certbot/issues/5332).
>>>
>>> in short, they are checking for apache2ctl command instead of apachectl
>>> which is by default used in Slackware. While they provided override
>>> classes for other distributions, none for Slackware at this moment.
>>>
>>> there are some solutions:
>>> - ask for Patrick to add symlink in -stable (and -current)
>>> - wait for upstream to fix the issue
>>> - add the symlink manually
>>> - someone make override class for Slackware and send PR to upstream
>>>
>>>
>> ?I think the correct solution is for Patrick to add a symlink in the
>> distro.  Since apachectl is the default, I don't know why we would want
>> that changed in slackware.  Making apache2ctl a symlink to apachectl would
>> seem to be the right solution.  However, I don't really think it matters
>> which one is the symlink.?
>>
>> I suspect it was called apache2ctl originally so you could have apache
>> 1.x and 2.x installed side-by-side on the same box.  The only real problem
>> this would create would be a conflict if someone is actually still running
>> apache 1.x on modern Slackware distros.  I doubt that's the case, but it's
>> not beyond the realm of possibility.  In that case, I would rather see the
>> apachectl for apache 1.x be renamed to apache1ctl or something like that
>> than to see the one from apache 2.x renamed.
>>
>> Although, I think the best solution would be a combination of 1 and 4.
>> We should try to get the override class in place, but we should also try to
>> stick with the apache default as much as possible even if letsencrypt
>> weren't an issue here.
>>
>>
>> _______________________________________________
>> 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/
>>
>>
>>
> I'm -1 on renaming the apachectl script - the script is called as such
> upstream, and I can't see a single valid reason to rename it.
>
> Just because other debian-based distros did that doesn't mean it's the
> sane approach.
>
> Now, I do realize that we do have to "play ball" with other distro's
> quirks, unfortunately. As such, creating a symlink from apache2ctl ->
> apachectl is probably the least disruptive approach.
>
> _______________________________________________
> 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/20180118/eb8e88ad/attachment.html>

From rworkman at slackbuilds.org  Thu Jan 18 22:02:01 2018
From: rworkman at slackbuilds.org (Robby Workman)
Date: Thu, 18 Jan 2018 16:02:01 -0600
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
Message-ID: <20180118160201.5045858c@home.rlworkman.net>

On Thu, 18 Jan 2018 16:01:08 -0500
Jason Graham <jgraha8 at gmail.com> wrote:

> Can we just patch the OS_DEFAULTS in the configurator until an OS
> override can be added upstream?


+1 here.

-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/20180118/50c78100/attachment.asc>

From willysr at slackbuilds.org  Thu Jan 18 22:39:47 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 19 Jan 2018 05:39:47 +0700
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <20180118160201.5045858c@home.rlworkman.net>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
Message-ID: <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>

>> Can we just patch the OS_DEFAULTS in the configurator until an OS
>> override can be added upstream?
> 
> 
> +1 here.

I tried to patch the OS_DEFAULTS and i confirmed that it works on my
machines for renewal, but i haven't tried for new cert requests.

any volunteer to help would be helpful

the changes are force-pushed to my letsencrypt-review branch

-- 
Willy Sudiarto Raharjo

-------------- 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/20180119/0d951dc4/attachment.asc>

From eric.b.pratt at gmail.com  Thu Jan 18 22:49:10 2018
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Thu, 18 Jan 2018 14:49:10 -0800
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
 <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
Message-ID: <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>

On Thu, Jan 18, 2018 at 2:39 PM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> >> Can we just patch the OS_DEFAULTS in the configurator until an OS
> >> override can be added upstream?
> >
> >
> > +1 here.
>
> I tried to patch the OS_DEFAULTS and i confirmed that it works on my
> machines for renewal, but i haven't tried for new cert requests.
>
> any volunteer to help would be helpful
>
> the changes are force-pushed to my letsencrypt-review branch
>
>
?This is already in the existing slackbuild:

  sed -i 's/apache2ctl/apachectl/'
certbot-apache/certbot_apache/constants.py?

?Is this not doing what needs to be done??  If not, I can take a look at it
tonight after work to see what can be done to fix it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180118/355e4dfb/attachment.html>

From willysr at slackbuilds.org  Thu Jan 18 22:50:50 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 19 Jan 2018 05:50:50 +0700
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
 <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
 <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>
Message-ID: <97854e91-5941-a4e2-0de5-567bbf2d0a84@slackbuilds.org>

> ?This is already in the existing slackbuild:
> 
> ? sed -i 's/apache2ctl/apachectl/'
> certbot-apache/certbot_apache/constants.py?
> 
> ?Is this not doing what needs to be done??? If not, I can take a look at
> it tonight after work to see what can be done to fix it.

No, it needs to be done in the certbot-apache/certbot_apache/configurator.py


-- 
Willy Sudiarto Raharjo

-------------- 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/20180119/8f70955d/attachment.asc>

From eric.b.pratt at gmail.com  Thu Jan 18 22:56:54 2018
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Thu, 18 Jan 2018 14:56:54 -0800
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <97854e91-5941-a4e2-0de5-567bbf2d0a84@slackbuilds.org>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
 <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
 <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>
 <97854e91-5941-a4e2-0de5-567bbf2d0a84@slackbuilds.org>
Message-ID: <CAPKhk4N15498B-T+_Ao0R5pVO1L43++EzWO=YyR7Bqy4rPnBMg@mail.gmail.com>

On Thu, Jan 18, 2018 at 2:50 PM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > ?This is already in the existing slackbuild:
> >
> >   sed -i 's/apache2ctl/apachectl/'
> > certbot-apache/certbot_apache/constants.py?
> >
> > ?Is this not doing what needs to be done??  If not, I can take a look at
> > it tonight after work to see what can be done to fix it.
>
> No, it needs to be done in the certbot-apache/certbot_apache/
> configurator.py
>

?I see.  I just downloaded the .21 source and grepped for it.  It changed
locations.  So we just need to change the sed line in the slackbuild and
test??
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180118/90c66f45/attachment-0001.html>

From willysr at slackbuilds.org  Thu Jan 18 23:11:41 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 19 Jan 2018 06:11:41 +0700
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <CAPKhk4N15498B-T+_Ao0R5pVO1L43++EzWO=YyR7Bqy4rPnBMg@mail.gmail.com>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
 <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
 <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>
 <97854e91-5941-a4e2-0de5-567bbf2d0a84@slackbuilds.org>
 <CAPKhk4N15498B-T+_Ao0R5pVO1L43++EzWO=YyR7Bqy4rPnBMg@mail.gmail.com>
Message-ID: <d80eec06-0223-35c3-c210-3a19212660ff@slackbuilds.org>

> ?I see.? I just downloaded the .21 source and grepped for it.? It
> changed locations.? So we just need to change the sed line in the
> slackbuild and test??

See my changes here
https://git.slackbuilds.org/slackbuilds/commit/?h=letsencrypt-review&id=9abf7d8542cc0237903252bbc34b8f0ee8015e0a


-- 
Willy Sudiarto Raharjo

-------------- 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/20180119/3077314e/attachment.asc>

From eric.b.pratt at gmail.com  Thu Jan 18 23:15:48 2018
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Thu, 18 Jan 2018 15:15:48 -0800
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <d80eec06-0223-35c3-c210-3a19212660ff@slackbuilds.org>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
 <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
 <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>
 <97854e91-5941-a4e2-0de5-567bbf2d0a84@slackbuilds.org>
 <CAPKhk4N15498B-T+_Ao0R5pVO1L43++EzWO=YyR7Bqy4rPnBMg@mail.gmail.com>
 <d80eec06-0223-35c3-c210-3a19212660ff@slackbuilds.org>
Message-ID: <CAPKhk4OG6E4qw+eEefxN62+_ftz8cQGLCW3VM_xSeG8g2m1STA@mail.gmail.com>

On Thu, Jan 18, 2018 at 3:11 PM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > ?I see.  I just downloaded the .21 source and grepped for it.  It
> > changed locations.  So we just need to change the sed line in the
> > slackbuild and test??
>
> See my changes here
> https://git.slackbuilds.org/slackbuilds/commit/?h=letsencrypt-review&id=
> 9abf7d8542cc0237903252bbc34b8f0ee8015e0a


?I already saw those.  But what I mean is that the patch is not necessary.
Since the constants.py file no longer contains apache2ctl references, you
don't need the new patch file and can just change the sed line to point to
configurator.py instead of constants.py, right??
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180118/e98b6ad0/attachment.html>

From willysr at slackbuilds.org  Thu Jan 18 23:40:18 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 19 Jan 2018 06:40:18 +0700
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <CAPKhk4OG6E4qw+eEefxN62+_ftz8cQGLCW3VM_xSeG8g2m1STA@mail.gmail.com>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
 <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
 <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>
 <97854e91-5941-a4e2-0de5-567bbf2d0a84@slackbuilds.org>
 <CAPKhk4N15498B-T+_Ao0R5pVO1L43++EzWO=YyR7Bqy4rPnBMg@mail.gmail.com>
 <d80eec06-0223-35c3-c210-3a19212660ff@slackbuilds.org>
 <CAPKhk4OG6E4qw+eEefxN62+_ftz8cQGLCW3VM_xSeG8g2m1STA@mail.gmail.com>
Message-ID: <82592b96-54fe-f3c9-3b17-ecce8cb33167@slackbuilds.org>

>     See my changes here
>     https://git.slackbuilds.org/slackbuilds/commit/?h=letsencrypt-review&id=9abf7d8542cc0237903252bbc34b8f0ee8015e0a
> 
> ?I already saw those.? But what I mean is that the patch is not
> necessary.? Since the constants.py file no longer contains apache2ctl
> references, you don't need the new patch file and can just change the
> sed line to point to configurator.py instead of constants.py, right??

There are other paths needs to be changed as well because the default
location refers to Debian/Ubuntu.

I tested new cert request and it's still working fine here


-- 
Willy Sudiarto Raharjo

-------------- 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/20180119/cfd0cc95/attachment.asc>

From eric.b.pratt at gmail.com  Thu Jan 18 23:45:41 2018
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Thu, 18 Jan 2018 15:45:41 -0800
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <82592b96-54fe-f3c9-3b17-ecce8cb33167@slackbuilds.org>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
 <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
 <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>
 <97854e91-5941-a4e2-0de5-567bbf2d0a84@slackbuilds.org>
 <CAPKhk4N15498B-T+_Ao0R5pVO1L43++EzWO=YyR7Bqy4rPnBMg@mail.gmail.com>
 <d80eec06-0223-35c3-c210-3a19212660ff@slackbuilds.org>
 <CAPKhk4OG6E4qw+eEefxN62+_ftz8cQGLCW3VM_xSeG8g2m1STA@mail.gmail.com>
 <82592b96-54fe-f3c9-3b17-ecce8cb33167@slackbuilds.org>
Message-ID: <CAPKhk4MPy_G4Jem=RKmVPZW9dHndCEpHc=UVLkrmyf9eEU5abQ@mail.gmail.com>

On Thu, Jan 18, 2018 at 3:40 PM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> >     See my changes here
> >     https://git.slackbuilds.org/slackbuilds/commit/?h=
> letsencrypt-review&id=9abf7d8542cc0237903252bbc34b8f0ee8015e0a
> >
> > ?I already saw those.  But what I mean is that the patch is not
> > necessary.  Since the constants.py file no longer contains apache2ctl
> > references, you don't need the new patch file and can just change the
> > sed line to point to configurator.py instead of constants.py, right??
>
> There are other paths needs to be changed as well because the default
> location refers to Debian/Ubuntu.
>
> I tested new cert request and it's still working fine here


I see.  The /apache2 ?/httpd modification is already done in the slackbuild
as well in the for loop containing the sed command for that.  The only
changes to configurator.py not handled by changing the sed target are:

vhost_files="httpd-vhosts.conf",

le_vhost_ext="-le-ssl.conf",

The le_vhost_ext is of no consequence because I can specify that on the
command line.

But the "vhost_files" one breaks things for me.  I've been maintaining web
servers since the '90s and like almost every other web admin I've ever met,
i maintain vhosts configs in separate files per vhost.  Since certbot
doesn't provide a method for changing this option via the command line,
this forces everyone to use the example vhost file as the only place to put
vhosted domains they wish to be renewed by certbot in that one file.

Honestly, I think just changing the one sed line to configurator.py and
removing the patch would be the best way to go.  Not only would it not
break things for anybody, but it would also prevent you from having to
maintain a patch file that will likely change more often than the filename
where the apache2ctl string needs to be changed.  Even then, if you really
wanted to and since this build is only for slackware, you could encapsulate
the apache2ctl/apachectl sed line in its own for loop like the
apache2/httpd loop and then you never have to worry about it.?

for i in $(grep -ri apache2ctl * | cut -d: -f1 | sort -u)
do
  sed -i 's/apache2ctl/apachectl/' $i
done
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180118/383fd27e/attachment.html>

From willysr at slackbuilds.org  Thu Jan 18 23:56:29 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 19 Jan 2018 06:56:29 +0700
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <CAPKhk4MPy_G4Jem=RKmVPZW9dHndCEpHc=UVLkrmyf9eEU5abQ@mail.gmail.com>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
 <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
 <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>
 <97854e91-5941-a4e2-0de5-567bbf2d0a84@slackbuilds.org>
 <CAPKhk4N15498B-T+_Ao0R5pVO1L43++EzWO=YyR7Bqy4rPnBMg@mail.gmail.com>
 <d80eec06-0223-35c3-c210-3a19212660ff@slackbuilds.org>
 <CAPKhk4OG6E4qw+eEefxN62+_ftz8cQGLCW3VM_xSeG8g2m1STA@mail.gmail.com>
 <82592b96-54fe-f3c9-3b17-ecce8cb33167@slackbuilds.org>
 <CAPKhk4MPy_G4Jem=RKmVPZW9dHndCEpHc=UVLkrmyf9eEU5abQ@mail.gmail.com>
Message-ID: <1fbb3e39-eb80-cdd6-84ab-80ea9e574287@slackbuilds.org>

> I see.? The /apache2 ?/httpd modification is already done in the
> slackbuild as well in the for loop containing the sed command for that.?
> The only changes to configurator.py?not handled by changing the sed
> target are:
> 
> vhost_files="httpd-vhosts.conf",
> 
> le_vhost_ext="-le-ssl.conf",
> 
> The le_vhost_ext is of no consequence because I can specify that on the
> command line.
> 
> But the "vhost_files" one breaks things for me.? I've been maintaining
> web servers since the '90s and like almost every other web admin I've
> ever met, i maintain vhosts configs in separate files per vhost.? Since
> certbot doesn't provide a method for changing this option via the
> command line, this forces everyone to use the example vhost file as the
> only place to put vhosted domains they wish to be renewed by certbot in
> that one file.

The default value for vhost_files is "*"
probably you can try to change it back to default and see if it works on
your setup?

I think it's quite safe to use the default value instead of specific
file (httpd-vhosts.conf)


-- 
Willy Sudiarto Raharjo

-------------- 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/20180119/443a0ccc/attachment-0001.asc>

From eric.b.pratt at gmail.com  Fri Jan 19 00:15:24 2018
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Thu, 18 Jan 2018 16:15:24 -0800
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <1fbb3e39-eb80-cdd6-84ab-80ea9e574287@slackbuilds.org>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
 <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
 <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>
 <97854e91-5941-a4e2-0de5-567bbf2d0a84@slackbuilds.org>
 <CAPKhk4N15498B-T+_Ao0R5pVO1L43++EzWO=YyR7Bqy4rPnBMg@mail.gmail.com>
 <d80eec06-0223-35c3-c210-3a19212660ff@slackbuilds.org>
 <CAPKhk4OG6E4qw+eEefxN62+_ftz8cQGLCW3VM_xSeG8g2m1STA@mail.gmail.com>
 <82592b96-54fe-f3c9-3b17-ecce8cb33167@slackbuilds.org>
 <CAPKhk4MPy_G4Jem=RKmVPZW9dHndCEpHc=UVLkrmyf9eEU5abQ@mail.gmail.com>
 <1fbb3e39-eb80-cdd6-84ab-80ea9e574287@slackbuilds.org>
Message-ID: <CAPKhk4P6MEzt9DCVf5XPh21UVcWnsvj97=wO0KbeVAV_ms36dg@mail.gmail.com>

On Thu, Jan 18, 2018 at 3:56 PM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

>
> The default value for vhost_files is "*"
> probably you can try to change it back to default and see if it works on
> your setup?
>
> I think it's quite safe to use the default value instead of specific
> file (httpd-vhosts.conf)
>

?Yeah, I saw that in the patch file too.  I'll try it out when I get off
work tonight and let you know.  I'm sure it will work because that really
just tells certbot what files to search for vhost configs within the
server_root (/etc/httpd/) directory structure.  So I suspect it will work
as advertised with the default.

I actually wish they did it in the opposite way, providing a filter to
refuse to search certain files for vhosts.  A lot of distros have log
directory symlinks configured in their /etc/httpd directories and having
certbot scan all the log files on larger web servers would really be a
waste of time and system resources.  Oh well.
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180118/de016bd8/attachment.html>

From eric.b.pratt at gmail.com  Fri Jan 19 07:20:58 2018
From: eric.b.pratt at gmail.com (Eric Pratt)
Date: Thu, 18 Jan 2018 23:20:58 -0800
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <CAPKhk4P6MEzt9DCVf5XPh21UVcWnsvj97=wO0KbeVAV_ms36dg@mail.gmail.com>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAPKhk4Mt=9ixgC5yMwobXAMLrF25QZmgZ7n9_j6A20irXWpbhQ@mail.gmail.com>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
 <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
 <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>
 <97854e91-5941-a4e2-0de5-567bbf2d0a84@slackbuilds.org>
 <CAPKhk4N15498B-T+_Ao0R5pVO1L43++EzWO=YyR7Bqy4rPnBMg@mail.gmail.com>
 <d80eec06-0223-35c3-c210-3a19212660ff@slackbuilds.org>
 <CAPKhk4OG6E4qw+eEefxN62+_ftz8cQGLCW3VM_xSeG8g2m1STA@mail.gmail.com>
 <82592b96-54fe-f3c9-3b17-ecce8cb33167@slackbuilds.org>
 <CAPKhk4MPy_G4Jem=RKmVPZW9dHndCEpHc=UVLkrmyf9eEU5abQ@mail.gmail.com>
 <1fbb3e39-eb80-cdd6-84ab-80ea9e574287@slackbuilds.org>
 <CAPKhk4P6MEzt9DCVf5XPh21UVcWnsvj97=wO0KbeVAV_ms36dg@mail.gmail.com>
Message-ID: <CAPKhk4OouBi+mkfa89iGRRt-Rju3-1b6DU9OVzk=g5HvYy0DNg@mail.gmail.com>

I'm just now getting to this.  I don't know how to get the pending
slackbuilds.  I can see the queue but can't get a download anywhere.  I was
hoping to get your josepy slackbuild since it is a dependency.  Can you
point me in the right direction?

On Thu, Jan 18, 2018 at 4:15 PM, Eric Pratt <eric.b.pratt at gmail.com> wrote:

> On Thu, Jan 18, 2018 at 3:56 PM, Willy Sudiarto Raharjo <
> willysr at slackbuilds.org> wrote:
>
>>
>> The default value for vhost_files is "*"
>> probably you can try to change it back to default and see if it works on
>> your setup?
>>
>> I think it's quite safe to use the default value instead of specific
>> file (httpd-vhosts.conf)
>>
>
> ?Yeah, I saw that in the patch file too.  I'll try it out when I get off
> work tonight and let you know.  I'm sure it will work because that really
> just tells certbot what files to search for vhost configs within the
> server_root (/etc/httpd/) directory structure.  So I suspect it will work
> as advertised with the default.
>
> I actually wish they did it in the opposite way, providing a filter to
> refuse to search certain files for vhosts.  A lot of distros have log
> directory symlinks configured in their /etc/httpd directories and having
> certbot scan all the log files on larger web servers would really be a
> waste of time and system resources.  Oh well.
> ?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180118/e633bfd4/attachment.html>

From willysr at slackbuilds.org  Fri Jan 19 11:01:30 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 19 Jan 2018 18:01:30 +0700
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <CAPKhk4OouBi+mkfa89iGRRt-Rju3-1b6DU9OVzk=g5HvYy0DNg@mail.gmail.com>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <CAOY50mt2TMkvJQpL6VEbF3nwZeNKCcW7p7-h3pwT7oLhMT3PWQ@mail.gmail.com>
 <CALDF-3yA=YcWz27f037Xo6csXpqLrOtPUiU2UTArPaoCBzU4Wg@mail.gmail.com>
 <20180118160201.5045858c@home.rlworkman.net>
 <afa0c1ab-2d9c-1deb-7d42-f4c651dfb96c@slackbuilds.org>
 <CAPKhk4NF_JfusJktdNSM4_1pns1W_iY0reGsPGnv-45_0_CqyA@mail.gmail.com>
 <97854e91-5941-a4e2-0de5-567bbf2d0a84@slackbuilds.org>
 <CAPKhk4N15498B-T+_Ao0R5pVO1L43++EzWO=YyR7Bqy4rPnBMg@mail.gmail.com>
 <d80eec06-0223-35c3-c210-3a19212660ff@slackbuilds.org>
 <CAPKhk4OG6E4qw+eEefxN62+_ftz8cQGLCW3VM_xSeG8g2m1STA@mail.gmail.com>
 <82592b96-54fe-f3c9-3b17-ecce8cb33167@slackbuilds.org>
 <CAPKhk4MPy_G4Jem=RKmVPZW9dHndCEpHc=UVLkrmyf9eEU5abQ@mail.gmail.com>
 <1fbb3e39-eb80-cdd6-84ab-80ea9e574287@slackbuilds.org>
 <CAPKhk4P6MEzt9DCVf5XPh21UVcWnsvj97=wO0KbeVAV_ms36dg@mail.gmail.com>
 <CAPKhk4OouBi+mkfa89iGRRt-Rju3-1b6DU9OVzk=g5HvYy0DNg@mail.gmail.com>
Message-ID: <c5b80e58-8d15-e465-8b77-a907786e1630@slackbuilds.org>

> I'm just now getting to this.? I don't know how to get the pending
> slackbuilds.? I can see the queue but can't get a download anywhere.? I
> was hoping to get your josepy slackbuild since it is a dependency.? Can
> you point me in the right direction?

David has just approved this on his branch
https://git.slackbuilds.org/slackbuilds/commit/?id=0cb741c70


-- 
Willy Sudiarto Raharjo

-------------- 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/20180119/8812d67b/attachment.asc>

From dchmelik at gmail.com  Fri Jan 19 12:58:24 2018
From: dchmelik at gmail.com (David Melik)
Date: Fri, 19 Jan 2018 04:58:24 -0800
Subject: [Slackbuilds-users] mbootpack build fail from Perl5
Message-ID: <cf00edc1-c879-6458-fbb8-9b41ad17aecc@gmail.com>

Processing mbootpack

mbootpack:
Found mbootpack-0.6a.tar.gz in /var/cache/sbopkg.
Checking MD5SUM:
 ? MD5SUM check for mbootpack-0.6a.tar.gz ... OK
Building package for mbootpack...
mbootpack-0.6a
mbootpack-0.6a/mkhex
mbootpack-0.6a/mbootpack.h
mbootpack-0.6a/mbootpack.c
mbootpack-0.6a/mb_info.h
mbootpack-0.6a/mb_header.h
mbootpack-0.6a/buildimage.c
mbootpack-0.6a/bootsect.S
mbootpack-0.6a/README
mbootpack-0.6a/Makefile
mbootpack-0.6a/GPL
mbootpack-0.6a/Changes
mbootpack-0.6a/setup.S
patching file Makefile
patching file buildimage.c
patching file mbootpack.c
patching file mbootpack.h
gcc -Wall -Wpointer-arith -Wcast-qual -Wno-unused -Wno-format 
-Wmissing-prototypes -pipe -O3? -Wp,-MD,mbootpack.o.d -I. -I- 
-DVERSION=\"0.6a\" -c mbootpack.c -o mbootpack.o
gcc -m32 -Wall -Wpointer-arith -Wcast-qual -Wno-unused -Wno-format 
-Wmissing-prototypes -pipe -O3? -I. -I-? -DVERSION=\"0.6a\" -D__MB_ASM 
-c bootsect.S -o bootsect.o
gcc -m32 -Wall -Wpointer-arith -Wcast-qual -Wno-unused -Wno-format 
-Wmissing-prototypes -pipe -O3? -I. -I-? -DVERSION=\"0.6a\" -D__MB_ASM 
-c setup.S -o setup.o
cc1: note: obsolete option -I- used, please use -iquote instead
cc1: note: obsolete option -I- used, please use -iquote instead
cc1: note: obsolete option -I- used, please use -iquote instead
ld -m elf_i386 -Ttext 0x0 -s --oformat binary bootsect.o -o bootsect
ld -m elf_i386 -Ttext 0x0 -s --oformat binary setup.o -o setup
sh ./mkhex bzimage_bootsect bootsect > bzimage_header.c
sh ./mkhex bzimage_setup setup >> bzimage_header.c
gcc -Wall -Wpointer-arith -Wcast-qual -Wno-unused -Wno-format 
-Wmissing-prototypes -pipe -O3? -Wp,-MD,buildimage.o.d -I. -I- 
-DVERSION=\"0.6a\" -c buildimage.c -o buildimage.o
cc1: note: obsolete option -I- used, please use -iquote instead
gcc -Wall -Wpointer-arith -Wcast-qual -Wno-unused -Wno-format 
-Wmissing-prototypes -pipe -O3?? -DVERSION=\"0.6a\" -o mbootpack 
mbootpack.o buildimage.o
help2man -n "packages a multiboot kernel and modules as a single file" 
-s 1 -N ./mbootpack > mbootpack.man
/usr/bin/perl: symbol lookup error: 
/usr/lib64/perl5/vendor_perl/auto/Locale/gettext/gettext.so: undefined 
symbol: Perl_xs_apiversion_bootcheck
Makefile:54: recipe for target 'mbootpack.man' failed
make: *** [mbootpack.man] Error 127


From matteo.bernardini at gmail.com  Fri Jan 19 13:09:35 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Fri, 19 Jan 2018 14:09:35 +0100
Subject: [Slackbuilds-users] mbootpack build fail from Perl5
In-Reply-To: <cf00edc1-c879-6458-fbb8-9b41ad17aecc@gmail.com>
References: <cf00edc1-c879-6458-fbb8-9b41ad17aecc@gmail.com>
Message-ID: <CAPsDuS4mSu0c0-2DVBNCeCjK8dcrRPesN9eYCfVo27mgB9+dbg@mail.gmail.com>

2018-01-19 13:58 GMT+01:00 David Melik <dchmelik at gmail.com>:
> help2man -n "packages a multiboot kernel and modules as a single file" -s 1
> -N ./mbootpack > mbootpack.man
> /usr/bin/perl: symbol lookup error:
> /usr/lib64/perl5/vendor_perl/auto/Locale/gettext/gettext.so: undefined
> symbol: Perl_xs_apiversion_bootcheck
> Makefile:54: recipe for target 'mbootpack.man' failed
> make: *** [mbootpack.man] Error 127

Hi David,

this builds fine here, on stable and current.

the error you got seem related to a non-standard installation of the
gettext.so perl library, included in the Slackware perl package: maybe
reinstalling the perl package that comes with Slackware should fix it
(it should overwrite it).

Matteo

From dchmelik at gmail.com  Fri Jan 19 13:26:27 2018
From: dchmelik at gmail.com (David Melik)
Date: Fri, 19 Jan 2018 05:26:27 -0800
Subject: [Slackbuilds-users] using SlackBuilds listserv/newsgroup and sbopkg?
Message-ID: <0992c78d-3cdf-54bd-9e1c-908c7604416d@gmail.com>

After big changes to Gmane last year or two, I rejoined this listserv, 
but unsubscribed, just reading in the newsgroup and archives.? I also 
preferred to post in the newsgroup, but is that now impossible 
(read-only?)? I'd like to have cross-posted to the next part to 
news://gmane.linux.slackware.sbopkg and maybe some general Slackware 
news-/discussion-group (well, I still use the Usenet one, not usually as 
much as Linux Questions web-forum.)

Some years ago I told an older friend (who got me into IBM-compatible 
PCs, now incorrectly a.k.a. 'PCs,' as also Apples/etc., laptops, pads, 
phones are grouped under the term) how I hate how installation 
(Slackware installer, sbopkg, etc.) with GNU Dialog looks like 1980s 
versions of DOS on 80x25 screen but with the text box fit within to 
'look nice' (actually look like Windows windows, perhaps, which should 
be criticized) but is just super-small.? It was fine for me 21 years 
ago, not now.? He commented, he knows how he could easily alter 
installers so they fit or even automatically resize to largest VESA text 
modes and newer screens, but said he's 'too busy slacking' (yet deals 
with this in the installer and sbopkg, agrees with me) then switched to 
avoiding computers except at work, and using some newer garbage systemd 
distro.? After he told me, I spent hours looking in the sbopkg code 
(maybe even Slackware installer,) reading about Dialog, maybe even tried 
a couple things (didn't work,) but it was just too difficult for me to 
be able to resize.? Would anyone else be able to try that and submit 
patches?

Surely at least some other text mode is considered standard now, or even 
if not necessarily resizable, wouldn't passing a size 
argument/flag/switch option be better?? Also really, the current case of 
maybe 8/9 the screen just being blue background is almost useless.? I 
like the large background option in Slackware's installer (as long as I 
'install all,' since one must, to get help on freenode IRC ##slackware, 
but there are other installation situations) but not in sbopkg.? Even 
Slackware's installer, I think, resizes text boxes for huge descriptions 
of packages.

Many/most software descriptions just go past the end of the small line 
in sbopkg, yet every few weeks/months, I love just going through entire 
software categories in sbopkg to double-check what else I want to 
install.? Usually I find several or 10+ things (if you don't even count 
dependencies,) but sometimes it's impossible to read or becomes to 
stressful (reading hundreds of lines fast in a small area) to get to the 
end, so I know I also miss many things I'd have installed or had been 
spending months looking for.? So, the state of being able to install 
nowadays, it's just almost unusable.


From dchmelik at gmail.com  Fri Jan 19 13:45:16 2018
From: dchmelik at gmail.com (David Melik)
Date: Fri, 19 Jan 2018 05:45:16 -0800
Subject: [Slackbuilds-users] mbootpack build fail from Perl5
Message-ID: <f75cf5e5-ae58-62da-6b3f-b9745bf97cb7@gmail.com>

On Fri, 19 Jan 2018 14:09:35 +0100, Matteo Bernardini wrote:

 > [...] this builds fine here, on stable and current.
 >
 > the error you got seem related to a non-standard installation of the
 > gettext.so perl library, included in the Slackware perl package: maybe
 > reinstalling the perl package that comes with Slackware should fix it
 > (it should overwrite it).

Seems correct; worked after I reinstalled Slackware's Perl packages; thanks!


From ricardo at palmtx.com.ar  Fri Jan 19 14:48:56 2018
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Fri, 19 Jan 2018 11:48:56 -0300
Subject: [Slackbuilds-users] letsencrypt updates
In-Reply-To: <CAPKhk4MPy_G4Jem=RKmVPZW9dHndCEpHc=UVLkrmyf9eEU5abQ@mail.gmail.com>
References: <1d43e700-24f9-3a7b-52c2-f10c4584dc4d@slackbuilds.org>
 <82592b96-54fe-f3c9-3b17-ecce8cb33167@slackbuilds.org>
 <CAPKhk4MPy_G4Jem=RKmVPZW9dHndCEpHc=UVLkrmyf9eEU5abQ@mail.gmail.com>
Message-ID: <201801191148.57058.ricardo@palmtx.com.ar>

El Jueves 18/01/2018 a las 20:45, Eric Pratt escribi?:
> for i in $(grep -ri apache2ctl * | cut -d: -f1 | sort -u)
> do
>   sed -i 's/apache2ctl/apachectl/' $i
> done

Just nitpicking, but that for can be simplified with grep's -l option:

for i in $(grep -ril apache2ctl *)
do
  sed -i 's/apache2ctl/apachectl/' $i
done


Or, if you want to include possible hidden directories/files (which * doesn't 
expand):

for i in $(grep -ril apache2ctl .)
do
  sed -i 's/apache2ctl/apachectl/' $i
done


Fixing it for paths with spaces is left as an excercise for the reader :)

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 didier at slint.fr  Fri Jan 19 14:53:22 2018
From: didier at slint.fr (Didier Spaier)
Date: Fri, 19 Jan 2018 15:53:22 +0100
Subject: [Slackbuilds-users] using SlackBuilds listserv/newsgroup and
 sbopkg?
In-Reply-To: <0992c78d-3cdf-54bd-9e1c-908c7604416d@gmail.com>
References: <0992c78d-3cdf-54bd-9e1c-908c7604416d@gmail.com>
Message-ID: <b3acc6a1-fadf-aca7-b153-a8a85b5ff9b7@slint.fr>

Quoted lines from David Melik:
> He commented, he knows how he could easily alter installers so they fit or even automatically resize to largest VESA text modes and newer screens, but said he's 'too busy slacking' (yet deals with this in the installer and sbopkg, agrees with me) then switched to avoiding computers except at work, and using some newer garbage systemd distro.? After he told me, I spent hours looking in the sbopkg code (maybe even Slackware installer,) reading about Dialog, maybe even tried a couple things
> (didn't work,) but it was just too difficult for me to be able to resize.? Would anyone else be able to try that and submit patches?

No need to patch anything

Just run sbopkg or any other dialog based (or not) application in fbterm or in mlterm-fb.
If you have an x86_64 system you will find packages here:
http://slackware.uk/slint/x86_64/slint-14.2.1/slint/
Else the sources are in these directories:
http://slackware.uk/slint/x86_64/slint-14.2.1/source/fbterm/
http://slackware.uk/slint/x86_64/slint-14.2.1/source/mlterm/

A SlackBuild for fbterm from B. Watson is available @ SBo (that's the one I use in Slint):
https://slackbuilds.org/repository/14.2/system/fbterm/

The simplest to use is fbterm. For a font size 40 (huge!), just type in a tty (NOT in a terminal for X, that won't work):
fbterm -s 40
then run sbopkg or any other dialog application like pkgtool or xwmconfig, you will have huge and beautiful ttf fonts.

If you get a "freezed" terminal after the fbterm command it can be because the "good" framebuffer is /dev/fb1 instead of /dev/fb0. Then exit with Ctrl+d and type:
FRAMEBUFFER=/dev/fb1 fbterm -s 40

Check that you have a proper framebuffer to use fbterm with this command, typed in a tty:
checkfb
this command is included in the fbterm package.

The same apply to mlterm-fb.
Read the docs in /usr/doc/fbtrem-1.8 and /usr/doc/mlterm-1.8.4 after installation.

For the previous Slint version (14.1) I modified the installer to automatically adapt the font size to the screen's dimensions, using fbterm.
You can get a full ISO here:
https://sourceforge.net/projects/slint/files/14.1/
Or just the installer there:
http://slint.fr/installers/

I can't answer to your issues about sbopkg, that I don't use.

Greetings,

Didier

From willysr at slackbuilds.org  Sat Jan 20 00:17:32 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 20 Jan 2018 07:17:32 +0700
Subject: [Slackbuilds-users] Updates - 20180120.1
Message-ID: <a9098e03-5c86-2280-2615-80785d415c5a@slackbuilds.org>

Hi

here goes another update:
- flashplayer-plugin is now sync with pepperflash-plugins
- another browser updates
- letsencrypt gets bumped to 0.21.0 (new dep: josepy)
  I have tested this on two production machines and it's working fine
here, but i'm  open to suggestion to improve letsencrypt for more
general usage on your machines. The reason why i push this forward is
because upstream have disabled tls-sni-01 permanently and switching to
http-01. I have also adjusted the README.Slackware and things should
gets easier for new or existing users.

Electrum 3.0.x is now ready in Electrum3-review branch and i would like
to push it forward for next public update, so if you happen to use
Electrum 2.9.x, it would be a good idea to start testing the new version
as upstream decided not to maintain 2.9.x branch any more. They just
provided 2.9.4 for backporting the urgent security fixes. Electrum 3 is
using Python 3 exclusively, so you need to rebuilt every deps with
Python 3 installed first.

Sat Jan 20 00:01:52 UTC 2018
academic/ZeGrapher: Added (math graphing).
academic/reduce-algebra: Updated for version 20180117svn4372.
desktop/flatwoken-icon-theme: Added (icon theme).
development/codeblocks: Updated for version 17.12.
development/cppcms: Updated for version 1.2.0.
development/jupyter-ipykernel: Updated for version 4.8.0.
development/notepadqq: Added (Notepad++-like editor).
development/psycopg2: Updated for version 2.7.3.2 and new maintainer.
development/tanya: Added (General purpose D library).
gis/qgis: Updated for version 2.18.16.
ham/svxlink: Updated for version 17.12.1.
libraries/efivar: Add patch to make efi_guid_ux_capsule work.
libraries/libuv: Updated for version 1.19.0.
misc/goldencheetah: Added (analysis tools for cycling performance).
multimedia/flashplayer-plugin: Updated for version 28.0.0.137.
network/Electrum: Fix build.
network/PaleMoon: Updated for version 27.7.1.
network/WireGuard: Updated for version 0.0.20180118.
network/palemoon: Updated for version 27.7.1.
network/slimjet: Updated for version 17.0.6.0.
network/syncthing: Updated for version 0.14.43.
network/vivaldi: Updated for version 1.13.1008.44.
office/pdfstudio11: Update DOWNLOAD urls.
python/josepy: Added (JOSE protocol).
python/python3-jupyter-ipykernel: Updated for version 4.8.0.
system/dina-font: Updated for version 2.93.
system/fswatch: Updated for version 1.11.2.
system/fwupdate: Updated for version 10.
system/letsencrypt: Updated for version 0.21.0.
system/luckybackup: Updated for version 0.4.9.
system/open-vm-tools: Update script.
system/ranger: Update README.
system/statifier: Updated for version 1.7.4, new maintainer.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- 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/20180120/ba5ba6c7/attachment.asc>

From willysr at slackbuilds.org  Sat Jan 20 00:19:42 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 20 Jan 2018 07:19:42 +0700
Subject: [Slackbuilds-users] SlackBuild script for grab from Ryan
Message-ID: <3073d57b-c24f-c392-7855-51469d4a3ea6@slackbuilds.org>

Hi

Ryan is no longer maintaining his scripts, so anyone is granted to take
these scripts:
graphics/brlcad
graphics/mirage
misc/stardict
office/openoffice.org
audio/patchage
libraries/ganv
development/leiningen


-- 
Willy Sudiarto Raharjo

-------------- 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/20180120/cbae8b07/attachment.asc>

From chytraeu at sdf.org  Sat Jan 20 01:04:38 2018
From: chytraeu at sdf.org (Donald Cooley)
Date: Fri, 19 Jan 2018 19:04:38 -0600
Subject: [Slackbuilds-users] SlackBuild script for grab from Ryan
In-Reply-To: <3073d57b-c24f-c392-7855-51469d4a3ea6@slackbuilds.org>
References: <3073d57b-c24f-c392-7855-51469d4a3ea6@slackbuilds.org>
Message-ID: <6BECF989-F1BB-4A2F-B672-CEF4032895FA@sdf.org>

On January 19, 2018 6:19:42 PM CST, Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:
>Hi
>
>Ryan is no longer maintaining his scripts, so anyone is granted to take
>these scripts:
>graphics/brlcad
>graphics/mirage
>misc/stardict
>office/openoffice.org
>audio/patchage
>libraries/ganv
>development/leiningen

I'll take OpenOffice

Regards,
Donald Cooley
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

From yth at ythogtha.org  Sat Jan 20 10:40:40 2018
From: yth at ythogtha.org (Ythogtha)
Date: Sat, 20 Jan 2018 11:40:40 +0100
Subject: [Slackbuilds-users] SlackBuild script for grab from Ryan
In-Reply-To: <6BECF989-F1BB-4A2F-B672-CEF4032895FA@sdf.org>
References: <3073d57b-c24f-c392-7855-51469d4a3ea6@slackbuilds.org>
 <6BECF989-F1BB-4A2F-B672-CEF4032895FA@sdf.org>
Message-ID: <20180120114040.d41070c4ea5622c84ba4c9b2@ythogtha.org>

> On January 19, 2018 6:19:42 PM CST, Willy Sudiarto Raharjo
> <willysr at slackbuilds.org> wrote:
> >Hi
> >
> >Ryan is no longer maintaining his scripts, so anyone is granted to take
> >these scripts:
> >graphics/brlcad
> >graphics/mirage
> >misc/stardict
> >office/openoffice.org
> >audio/patchage
> >libraries/ganv
> >development/leiningen
> 
> I'll take OpenOffice

I'm ok taking over :
graphics/mirage

And if nobody wants it, I could also take :
graphics/brlcad

-- 
Arnaud <yth at ythogtha.org>

From pprkut at liwjatan.at  Sat Jan 20 13:35:52 2018
From: pprkut at liwjatan.at (Heinz Wiesinger)
Date: Sat, 20 Jan 2018 14:35:52 +0100
Subject: [Slackbuilds-users] Audio SlackBuilds
Message-ID: <2061442.gaO3zonlXd@titania.liwjatan.org>

Hi everyone,

This is a bit difficult for me, but the reality is that although I tried to 
keep my audio related SlackBuilds up-to-date, since I no longer really use any 
of them they always ended up getting pushed down the priority list. That's a 
shame and I feel like they deserve better. So, if anyone of you thinks he can 
give some of those a better home, feel free to adopt them :)

This is not a general "up for grabs" email though. If SlackBuilds from this 
list in the end remain with me as their maintainer I'll keep them on my TODO 
list, and if there are bugs I will naturally take a look at them. Just don't 
expect regular updates :)

So, without further ado, here's the list, roughly grouped by what I think 
would be best maintained by the same maintainer:

audio/ardour
libraries/aubio

audio/jack-audio-connection-kit
audio/celt
libraries/libdbus-c++
libraries/libffado

audio/fluidsynth

audio/rosegarden

libraries/liblo

libraries/liblrdf

audio/ladspa_sdk

libraries/slv2

audio/lv2
libraries/lilv
libraries/serd
libraries/sord
libraries/sratom
libraries/suil

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/20180120/9e2e1e53/attachment.asc>

From rshepard at appl-ecosys.com  Sat Jan 20 13:47:56 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 20 Jan 2018 05:47:56 -0800 (PST)
Subject: [Slackbuilds-users] Audio SlackBuilds
In-Reply-To: <2061442.gaO3zonlXd@titania.liwjatan.org>
References: <2061442.gaO3zonlXd@titania.liwjatan.org>
Message-ID: <alpine.LNX.2.20.1801200542210.12240@salmo.appl-ecosys.com>

On Sat, 20 Jan 2018, Heinz Wiesinger wrote:

> This is a bit difficult for me, but the reality is that although I tried to
> keep my audio related SlackBuilds up-to-date, since I no longer really use any
> of them they always ended up getting pushed down the priority list.

Heinz, et al.:

   I don't use any of these tools nor do I know how to create or maintain
slackbuild scripts, but I have a question raised by your situation. I ask
only because I'm curious.

   Could a script using curl and run by cron.weekly (for example) search
source URLs, check whether the downloadable version differs from the local
version, download it if it is, and send a message to the user that an
updated version has been collected?

   All of you spend a lot of time maintaining packages and I'm not the only
one who appreciates your efforts.

Regards,

Rich

From alik at ejik.org  Sat Jan 20 14:21:46 2018
From: alik at ejik.org (Alexander Verbovetsky)
Date: Sat, 20 Jan 2018 17:21:46 +0300
Subject: [Slackbuilds-users] Audio SlackBuilds
In-Reply-To: <alpine.LNX.2.20.1801200542210.12240@salmo.appl-ecosys.com>
References: <2061442.gaO3zonlXd@titania.liwjatan.org>
 <alpine.LNX.2.20.1801200542210.12240@salmo.appl-ecosys.com>
Message-ID: <1516458106.1780397.1242075944.5DF7033F@webmail.messagingengine.com>

Hello,

> Could a script using curl and run by cron.weekly (for example) search
> source URLs, check whether the downloadable version differs from the
> local version, download it if it is, and send a message to the user
> that an updated version has been collected?

I use a few such scripts, for example:

-----
#!/bin/bash
source <(curl -s https://slackbuilds.org/slackbuilds/14.2/system/isdct/isdct.info | grep "VERSION\|HOMEPAGE")
cat /usr/doc/isdct-*/isdct.SlackBuild |grep "VERSION=\${VERSION:-$VERSION}" > /dev/null || exit 0
s=$(curl -s "$HOMEPAGE" | grep -c "Version:.*Latest")
[ $s -eq 1 ] && exit 0
>&2 echo "New version of isdct, see $HOMEPAGE"
-----
or
-----
#!/bin/sh
s=$(ls /var/log/packages/krop* | grep -c $(curl -s http://arminstraub.com/software/krop | grep -A1000000 "Changelog" | grep -m1 -o "krop [0-9\.]*" | grep -m1 -o "[0-9\.]*"))
[ $s -eq 1 ] && exit 0
>&2 echo "New release of krop, see http://arminstraub.com/software/krop"
-----

IMO, better to use cron.daily, because .weekly only delays the
information, not reduces the amount of job.

Fortunately, in case of sourceforge one can simply subscribe for
information on new releases, and in case of github there is rss (which
can be checked via rss2email).

Best regards,
Alexander

From baildon.research at googlemail.com  Sat Jan 20 14:29:45 2018
From: baildon.research at googlemail.com (David Spencer)
Date: Sat, 20 Jan 2018 14:29:45 +0000
Subject: [Slackbuilds-users] Audio SlackBuilds
In-Reply-To: <alpine.LNX.2.20.1801200542210.12240@salmo.appl-ecosys.com>
References: <2061442.gaO3zonlXd@titania.liwjatan.org>
 <alpine.LNX.2.20.1801200542210.12240@salmo.appl-ecosys.com>
Message-ID: <CAMt7G9SdTK14ksj=omP9D73W_Zo9OF0TMvriy4vDz=-7shL8aw@mail.gmail.com>

Sorry for the thread-drift, and of course thank you for the music Heinz :)

>   Could a script using curl and run by cron.weekly (for example) search
> source URLs, check whether the downloadable version differs from the local
> version, download it if it is, and send a message to the user that an
> updated version has been collected?

This is fundamentally flawed, because the existing URL is (hopefully)
version specific, so to find a new version you'd have to guess the URL
template and guess the next version number. It's futile. So of course
Fedora tries to do it this way with Anitya
https://release-monitoring.org/about

A different approach is Repology https://repology.org/ which uses the
many eyes of multiple distros and catalogues the available versions --
of course the above Fedora method is included by reference ;)

But a really good maintainer will subscribe to the upstream projects'
mailing lists.

Cheers
-D.

From matteo.bernardini at gmail.com  Sat Jan 20 14:51:02 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 20 Jan 2018 15:51:02 +0100
Subject: [Slackbuilds-users] Audio SlackBuilds
In-Reply-To: <2061442.gaO3zonlXd@titania.liwjatan.org>
References: <2061442.gaO3zonlXd@titania.liwjatan.org>
Message-ID: <CAPsDuS5nKHCC51bH4V7JAU5JBU9knqbWWL20iHibk41y2DHu-g@mail.gmail.com>

2018-01-20 14:35 GMT+01:00 Heinz Wiesinger <pprkut at liwjatan.at>:
> audio/ardour
> libraries/aubio
>
> audio/jack-audio-connection-kit
> audio/celt
> libraries/libdbus-c++
> libraries/libffado

> audio/ladspa_sdk
>
> libraries/slv2
>
> audio/lv2
> libraries/lilv
> libraries/serd
> libraries/sord
> libraries/sratom
> libraries/suil

Hi Heinz,

if noone else wants them badly for whatever reason I'll get those as
most of them are optional dependencies of audacity and I also always
wanted to play with ardour!
Thanks for having maintained those until now!

Matteo

From slackbuilds at jaxartes.net  Sat Jan 20 16:15:05 2018
From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany)
Date: Sat, 20 Jan 2018 08:15:05 -0800
Subject: [Slackbuilds-users] Audio SlackBuilds
In-Reply-To: <CAMt7G9SdTK14ksj=omP9D73W_Zo9OF0TMvriy4vDz=-7shL8aw@mail.gmail.com>
References: <2061442.gaO3zonlXd@titania.liwjatan.org>
 <alpine.LNX.2.20.1801200542210.12240@salmo.appl-ecosys.com>
 <CAMt7G9SdTK14ksj=omP9D73W_Zo9OF0TMvriy4vDz=-7shL8aw@mail.gmail.com>
Message-ID: <9749816.r9jqNt3Qht@wintermute.sprawl.net>

On Saturday, 20 January 2018 06:29:45 PST David Spencer wrote:
> Sorry for the thread-drift, and of course thank you for the music Heinz :)
> 
> >   Could a script using curl and run by cron.weekly (for example) search
> > 
> > source URLs, check whether the downloadable version differs from the local
> > version, download it if it is, and send a message to the user that an
> > updated version has been collected?
> 
> But a really good maintainer will subscribe to the upstream projects'
> mailing lists.

Or their RSS feed. For GitHub, you can track releases with URLs of the following style: 
https://github.com/neovim/neovim/releases.atom

Ben

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180120/cd754e02/attachment.html>

From rshepard at appl-ecosys.com  Sat Jan 20 16:14:31 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 20 Jan 2018 08:14:31 -0800 (PST)
Subject: [Slackbuilds-users] krb5 not finding header: verto.h
Message-ID: <alpine.LNX.2.20.1801200806560.12240@salmo.appl-ecosys.com>

   Building krb5 fails here:

make[2]: Entering directory '/tmp/SBo/krb5-1.15.2/src/lib/apputils'
gcc -DHAVE_CONFIG_H  -I../../include -I../../include  -DKRB5_DEPRECATED=1 -DKRB5_PRIVATE -I/usr/include/et -O2 -march=i586 -mtune=i686 -Wall -Wcast-align -Wshadow -Wmissing-prototypes -Wno-format-zero-length -Woverflow -Wstrict-overflow -Wmissing-format-attribute -Wmissing-prototypes -Wreturn-type -Wmissing-braces -Wparentheses -Wswitch -Wunused-function -Wunused-label -Wunused-variable -Wunused-value -Wunknown-pragmas -Wsign-compare -Werror=uninitialized -Werror=pointer-arith -Werror=int-conversion -Werror=incompatible-pointer-types -Werror=discarded-qualifiers -Werror=declaration-after-statement -Werror-implicit-function-declaration -pthread  -c net-server.c
In file included from net-server.c:61:0:
../../include/net-server.h:32:19: fatal error: verto.h: No such file or directory
compilation terminated.
Makefile:490: recipe for target 'net-server.o' failed
make[2]: *** [net-server.o] Error 1
make[2]: Leaving directory '/tmp/SBo/krb5-1.15.2/src/lib/apputils'
Makefile:987: recipe for target 'all-recurse' failed
make[1]: *** [all-recurse] Error 1
make[1]: Leaving directory '/tmp/SBo/krb5-1.15.2/src/lib'
Makefile:1523: recipe for target 'all-recurse' failed
make: *** [all-recurse] Error 1

   The only verto.h is in

# find / -name verto.h
/tmp/SBo/krb5-1.15.2/src/util/verto/verto.h

   I'm not seeing why the build script isn't finding verto.h and would
appreciate guidance on how to remove this error.

Rich


From rshepard at appl-ecosys.com  Sat Jan 20 16:18:08 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 20 Jan 2018 08:18:08 -0800 (PST)
Subject: [Slackbuilds-users] Audio SlackBuilds
In-Reply-To: <1516458106.1780397.1242075944.5DF7033F@webmail.messagingengine.com>
References: <2061442.gaO3zonlXd@titania.liwjatan.org>
 <alpine.LNX.2.20.1801200542210.12240@salmo.appl-ecosys.com>
 <1516458106.1780397.1242075944.5DF7033F@webmail.messagingengine.com>
Message-ID: <alpine.LNX.2.20.1801200816080.12240@salmo.appl-ecosys.com>

On Sat, 20 Jan 2018, Alexander Verbovetsky wrote:

> I use a few such scripts, for example:

   Thanks, Alexander. I thought such automation was being used.

Regards,

Rich

From rshepard at appl-ecosys.com  Sat Jan 20 16:20:55 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 20 Jan 2018 08:20:55 -0800 (PST)
Subject: [Slackbuilds-users] Audio SlackBuilds
In-Reply-To: <CAMt7G9SdTK14ksj=omP9D73W_Zo9OF0TMvriy4vDz=-7shL8aw@mail.gmail.com>
References: <2061442.gaO3zonlXd@titania.liwjatan.org>
 <alpine.LNX.2.20.1801200542210.12240@salmo.appl-ecosys.com>
 <CAMt7G9SdTK14ksj=omP9D73W_Zo9OF0TMvriy4vDz=-7shL8aw@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.1801200819220.12240@salmo.appl-ecosys.com>

On Sat, 20 Jan 2018, David Spencer wrote:

> This is fundamentally flawed, because the existing URL is (hopefully)
> version specific, so to find a new version you'd have to guess the URL
> template and guess the next version number. It's futile.

David,

   It appears that automation works for some upstream sources but not all.

Thanks for your insights,

Rich




From willysr at slackbuilds.org  Sat Jan 20 17:20:54 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 21 Jan 2018 00:20:54 +0700
Subject: [Slackbuilds-users] krb5 not finding header: verto.h
In-Reply-To: <alpine.LNX.2.20.1801200806560.12240@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801200806560.12240@salmo.appl-ecosys.com>
Message-ID: <09fad926-09a0-484f-1f2e-cb6d8856ed1a@slackbuilds.org>

> make[2]: Entering directory '/tmp/SBo/krb5-1.15.2/src/lib/apputils'
> gcc -DHAVE_CONFIG_H? -I../../include -I../../include?
> -DKRB5_DEPRECATED=1 -DKRB5_PRIVATE -I/usr/include/et -O2 -march=i586
> -mtune=i686 -Wall -Wcast-align -Wshadow -Wmissing-prototypes
> -Wno-format-zero-length -Woverflow -Wstrict-overflow
> -Wmissing-format-attribute -Wmissing-prototypes -Wreturn-type
> -Wmissing-braces -Wparentheses -Wswitch -Wunused-function -Wunused-label
> -Wunused-variable -Wunused-value -Wunknown-pragmas -Wsign-compare
> -Werror=uninitialized -Werror=pointer-arith -Werror=int-conversion
> -Werror=incompatible-pointer-types -Werror=discarded-qualifiers
> -Werror=declaration-after-statement
> -Werror-implicit-function-declaration -pthread? -c net-server.c
> In file included from net-server.c:61:0:
> ../../include/net-server.h:32:19: fatal error: verto.h: No such file or
> directory
> compilation terminated.
> Makefile:490: recipe for target 'net-server.o' failed
> make[2]: *** [net-server.o] Error 1
> make[2]: Leaving directory '/tmp/SBo/krb5-1.15.2/src/lib/apputils'
> Makefile:987: recipe for target 'all-recurse' failed
> make[1]: *** [all-recurse] Error 1
> make[1]: Leaving directory '/tmp/SBo/krb5-1.15.2/src/lib'
> Makefile:1523: recipe for target 'all-recurse' failed
> make: *** [all-recurse] Error 1
> 
> ? The only verto.h is in
> 
> # find / -name verto.h
> /tmp/SBo/krb5-1.15.2/src/util/verto/verto.h
> 
> ? I'm not seeing why the build script isn't finding verto.h and would
> appreciate guidance on how to remove this error.

I just built krb5 and it worked fine on a clean VM

krb5:
  MD5SUM check for krb5-1.15.2.tar.gz ... OK
  Building package krb5-1.15.2-x86_64-1_SBo.tgz ... OK

did you have a custom MAKEFLAGS variable or a custom installation?

-- 
Willy Sudiarto Raharjo

-------------- 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/20180121/28cfda90/attachment.asc>

From rshepard at appl-ecosys.com  Sat Jan 20 17:51:47 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 20 Jan 2018 09:51:47 -0800 (PST)
Subject: [Slackbuilds-users] krb5 not finding header: verto.h
In-Reply-To: <09fad926-09a0-484f-1f2e-cb6d8856ed1a@slackbuilds.org>
References: <alpine.LNX.2.20.1801200806560.12240@salmo.appl-ecosys.com>
 <09fad926-09a0-484f-1f2e-cb6d8856ed1a@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.1801200944290.12240@salmo.appl-ecosys.com>

On Sun, 21 Jan 2018, Willy Sudiarto Raharjo wrote:

> I just built krb5 and it worked fine on a clean VM
>
> krb5:
>  MD5SUM check for krb5-1.15.2.tar.gz ... OK
>  Building package krb5-1.15.2-x86_64-1_SBo.tgz ... OK
>
> did you have a custom MAKEFLAGS variable or a custom installation?

Willy,

   Not as far as I know. I downloaded the tar.gz SlackBuild files in
/opt/slackbuilds/Network/, then krb5-1.15.2.tar.gz was downloaded to krb5/.
The md5sums match. I did nothing to the build script. This is a 32-bit
system.

   There are no other copies of krb5 or kerberos on the system.

Rich

From rshepard at appl-ecosys.com  Sat Jan 20 18:11:08 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Sat, 20 Jan 2018 10:11:08 -0800 (PST)
Subject: [Slackbuilds-users] krb5 not finding header: verto.h [RESOLVED]
In-Reply-To: <alpine.LNX.2.20.1801200944290.12240@salmo.appl-ecosys.com>
References: <alpine.LNX.2.20.1801200806560.12240@salmo.appl-ecosys.com>
 <09fad926-09a0-484f-1f2e-cb6d8856ed1a@slackbuilds.org>
 <alpine.LNX.2.20.1801200944290.12240@salmo.appl-ecosys.com>
Message-ID: <alpine.LNX.2.20.1801201009170.12240@salmo.appl-ecosys.com>

On Sat, 20 Jan 2018, Rich Shepard wrote:

>  There are no other copies of krb5 or kerberos on the system.

   Never mind, Willy. The patched alpine halted with an error and I thought
that alpine needed Kerberos, but it doesn't. Kerberos/krb5 are not included
in the distribution so the error source must be elsewhere. I'll keep looking
for it.

Regards,

Rich

From xavier at maillard.im  Sat Jan 20 20:57:43 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Sat, 20 Jan 2018 21:57:43 +0100
Subject: [Slackbuilds-users] Can't build spotify
Message-ID: <871sik1cru.fsf@smugg>

Hello,

I just want to tell that spotify-client can't be built with 
current SBo repo. The download link is either obsolete or false 
(it is getting a 404 error when tryin to get the .deb file).

Thank you for all the (still) very good stuff here !

Cheers
Xavier

From willysr at slackbuilds.org  Sat Jan 20 23:48:09 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 21 Jan 2018 06:48:09 +0700
Subject: [Slackbuilds-users] Can't build spotify
In-Reply-To: <871sik1cru.fsf@smugg>
References: <871sik1cru.fsf@smugg>
Message-ID: <e04254f7-b459-9d19-7c6a-33713a678df3@slackbuilds.org>

> I just want to tell that spotify-client can't be built with current SBo
> repo. The download link is either obsolete or false (it is getting a 404
> error when tryin to get the .deb file).

try here
http://slackware.uk/sbosrcarch/by-name/multimedia/spotify/

Spotify upstream has a bad habit of deleting the old sources when they
release a new one and only keep 1 version behind


-- 
Willy Sudiarto Raharjo

-------------- 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/20180121/78a1177f/attachment.asc>

From chytraeu at sdf.org  Sun Jan 21 06:44:50 2018
From: chytraeu at sdf.org (Donald Cooley)
Date: Sun, 21 Jan 2018 00:44:50 -0600
Subject: [Slackbuilds-users] openoffice.org.SlackBuild does not install
 menu icons
In-Reply-To: <6ceb0d8b-4382-4290-9d9b-e87e846567ee@gmail.com>
References: <6ceb0d8b-4382-4290-9d9b-e87e846567ee@gmail.com>
Message-ID: <55f5fcd9-bbe4-fc01-b993-24bbecf864c8@sdf.org>

On 05/11/2017 08:36 AM, Ekin Akoglu wrote:
> Dear all and Ryan as being the maintainer of openoffice.org,
> 
> The openoffice.org.Slackbuild does not install the necessary menu icons
> to /usr/share/icons. I propose a patch as attached. I also did a little
> bit of arbitrary clean up in the script (you may disregard them). Please
> feel free to comment.
> 
> Kind regards,
> 
> Ekin
> 

Hello,
I'm incorporating this patch and updating OpenOffice.org to version
4.1.5 as I'm now maintaining OpenOffice.org. I've tried to give you
credit in the build script.


From kingbeowulf at gmail.com  Sun Jan 21 20:35:24 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 21 Jan 2018 12:35:24 -0800
Subject: [Slackbuilds-users] Teamviewer13 duplicate menu entries
Message-ID: <17a8d10e-2270-2903-1314-8e2e7e9dceed@gmail.com>

Willy,

When you unpack the deb archive, a desktop entry already exists as a
symlink that gets recreated in doinst.sh.
-------------
ls -l /usr/share/applications/ |grep teamviewer
lrwxrwxrwx 1 root root    64 Jan 15 16:22
com.teamviewer.TeamViewer.desktop ->
/opt/teamviewer/tv_bin/desktop/com.teamviewer.TeamViewer.desktop
-rw-r--r-- 1 root root   208 Jan 15 16:21 teamviewer.desktop
-------------

Thus, the stanza in the script:
-------------
# Make a .desktop file
mkdir -p $PKG/usr/share/applications
cat $PKG/opt/teamviewer/tv_bin/desktop/com.teamviewer.TeamViewer.desktop \
  | sed -e 's/EXEC/teamviewer/' -e 's/ICON/teamviewer/' \
  > $PKG/usr/share/applications/teamviewer.desktop
---------

is redundant. Also the 'sed' seems a leftover since there is nothing to
replace.

-Ed


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

From willysr at slackbuilds.org  Mon Jan 22 00:00:27 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 22 Jan 2018 07:00:27 +0700
Subject: [Slackbuilds-users] Teamviewer13 duplicate menu entries
In-Reply-To: <17a8d10e-2270-2903-1314-8e2e7e9dceed@gmail.com>
References: <17a8d10e-2270-2903-1314-8e2e7e9dceed@gmail.com>
Message-ID: <d0f02efc-a45f-4ce9-1c3f-bb57efa4018c@slackbuilds.org>

> When you unpack the deb archive, a desktop entry already exists as a
> symlink that gets recreated in doinst.sh.
> -------------
> ls -l /usr/share/applications/ |grep teamviewer
> lrwxrwxrwx 1 root root    64 Jan 15 16:22
> com.teamviewer.TeamViewer.desktop ->
> /opt/teamviewer/tv_bin/desktop/com.teamviewer.TeamViewer.desktop
> -rw-r--r-- 1 root root   208 Jan 15 16:21 teamviewer.desktop
> -------------
> 
> Thus, the stanza in the script:
> -------------
> # Make a .desktop file
> mkdir -p $PKG/usr/share/applications
> cat $PKG/opt/teamviewer/tv_bin/desktop/com.teamviewer.TeamViewer.desktop \
>   | sed -e 's/EXEC/teamviewer/' -e 's/ICON/teamviewer/' \
>   > $PKG/usr/share/applications/teamviewer.desktop
> ---------
> 
> is redundant. Also the 'sed' seems a leftover since there is nothing to
> replace.

Thanks, i have pushed this on my branch


-- 
Willy Sudiarto Raharjo

-------------- 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/20180122/e4a21ad5/attachment-0001.asc>

From didier at slint.fr  Tue Jan 23 10:04:04 2018
From: didier at slint.fr (Didier Spaier)
Date: Tue, 23 Jan 2018 11:04:04 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
Message-ID: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>

Hello,

I like the new layout of the website with the new style sheet, clean and easy to read. Thanks!

Greetings,

Didier  

From fellype at gmail.com  Tue Jan 23 11:13:07 2018
From: fellype at gmail.com (Fellype do Nascimento)
Date: Tue, 23 Jan 2018 09:13:07 -0200
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
Message-ID: <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>

On 01/23/2018 08:04 AM, Didier Spaier wrote:
> I like the new layout of the website with the new style sheet, clean and easy to read. Thanks!
>
Yes, the new layout is much better now.
I thank the SBo admins!

Fellype

From slackalaxy at gmail.com  Tue Jan 23 14:14:19 2018
From: slackalaxy at gmail.com (Petar Petrov)
Date: Tue, 23 Jan 2018 16:14:19 +0200
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
Message-ID: <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>

with all due respect, I don't like it. It looks squashed.

What's the point of having a wide layout, when the description of each
entry is still limited to 72 characters per line?

-petar

2018-01-23 13:13 GMT+02:00 Fellype do Nascimento <fellype at gmail.com>:
> On 01/23/2018 08:04 AM, Didier Spaier wrote:
>>
>> I like the new layout of the website with the new style sheet, clean and
>> easy to read. Thanks!
>>
> Yes, the new layout is much better now.
> I thank the SBo admins!
>
> Fellype
> _______________________________________________
> 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 gerardo.zamudio at linux.com  Tue Jan 23 14:18:56 2018
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Tue, 23 Jan 2018 09:18:56 -0500
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
Message-ID: <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>



On 01/23/2018 09:14 AM, Petar Petrov wrote:
> with all due respect, I don't like it. It looks squashed.
> 
> What's the point of having a wide layout, when the description of each
> entry is still limited to 72 characters per line?
> 
> -petar
> 


My thoughts as well. Lots of wasted white space on the right when you
view a SlackBuild's individual page. It's not a responsive layout so the
wasted space is there on mobile too.

-- 
Gerardo Zamudio


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

From rshepard at appl-ecosys.com  Tue Jan 23 14:28:40 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 23 Jan 2018 06:28:40 -0800 (PST)
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
Message-ID: <alpine.LNX.2.20.1801230626330.32286@salmo.appl-ecosys.com>

On Tue, 23 Jan 2018, Gerardo Zamudio wrote:

> My thoughts as well. Lots of wasted white space on the right when you view
> a SlackBuild's individual page. It's not a responsive layout so the wasted
> space is there on mobile too.

   +1 Not as easy to read as the page content is much wider than the previous
layout.

Rich

From didier at slint.fr  Tue Jan 23 14:45:28 2018
From: didier at slint.fr (Didier Spaier)
Date: Tue, 23 Jan 2018 15:45:28 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
Message-ID: <d21ea0ac-bf2d-5193-5273-c7e3dce26b34@slint.fr>

Le 23/01/2018 ? 15:14, Petar Petrov a ?crit :
> with all due respect, I don't like it. It looks squashed.
> 
> What's the point of having a wide layout, when the description of each
> entry is still limited to 72 characters per line?

I see in the source pages that the README is formatted with each
line-feed converted to a <br /> tag.

Maybe just removing all line-feed and tagging the paragraphs inside
<p>...</p> or <div>...<div> could do the trick.

Anyway I think that this issue can be solved while keeping a wide and
fluid layout. 

Didier

From Jim.Diamond at acadiau.ca  Tue Jan 23 16:55:53 2018
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Tue, 23 Jan 2018 12:55:53 -0400
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
Message-ID: <20180123165553.GC19058@jdiamond-mb.acadiau.ca>

On Tue, Jan 23, 2018 at 16:14 (+0200), Petar Petrov wrote:

> with all due respect, I don't like it. It looks squashed.

> What's the point of having a wide layout, when the description of each
> entry is still limited to 72 characters per line?

Also, I looked at www.slackbuilds.org/contributors/ and the
line-breaking is weird, so I looked at the source and I see explicit
<br />s after some names, which makes the line breaking weird unless
my window is just the correct width for my font size.

Of course, the joy of web pages is that getting them to look right on
all sorts of different systems and all sorts of browsers is
practically impossible.  I avoid making web pages at all costs :-)

Cheers.

                                Jim

From Jim.Diamond at acadiau.ca  Tue Jan 23 17:09:54 2018
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Tue, 23 Jan 2018 13:09:54 -0400
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <d21ea0ac-bf2d-5193-5273-c7e3dce26b34@slint.fr>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <d21ea0ac-bf2d-5193-5273-c7e3dce26b34@slint.fr>
Message-ID: <20180123170954.GF19058@jdiamond-mb.acadiau.ca>

On Tue, Jan 23, 2018 at 15:45 (+0100), Didier Spaier wrote:

> Le 23/01/2018 ? 15:14, Petar Petrov a ?crit :
>> with all due respect, I don't like it. It looks squashed.

>> What's the point of having a wide layout, when the description of each
>> entry is still limited to 72 characters per line?

> I see in the source pages that the README is formatted with each
> line-feed converted to a <br /> tag.

> Maybe just removing all line-feed and tagging the paragraphs inside
> <p>...</p> or <div>...<div> could do the trick.

You are right that turning line feeds into <br /> seems like a bad idea.

But why remove the line feeds?  Unless they are in pre-formatted text
are they not just white-space to HTML?

                                Jim

From yalhcru at gmail.com  Tue Jan 23 17:20:46 2018
From: yalhcru at gmail.com (B Watson)
Date: Tue, 23 Jan 2018 12:20:46 -0500
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180123170954.GF19058@jdiamond-mb.acadiau.ca>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <d21ea0ac-bf2d-5193-5273-c7e3dce26b34@slint.fr>
 <20180123170954.GF19058@jdiamond-mb.acadiau.ca>
Message-ID: <CAN1hMuD88xS_AT6YPvJa+X5w=kXsYAg09ag+ALLZg3rsL8D=2A@mail.gmail.com>

On 1/23/18, Jim Diamond <Jim.Diamond at acadiau.ca> wrote:
> You are right that turning line feeds into <br /> seems like a bad idea.

The descriptions are plain text, and sometimes have things like bulleted
or numbered lists, done in text.

  - Like this
  - And this

Some of them even have ASCII art... I shot myself in the foot on this
issue with a script that reformatted all the READMEs to make them
"better".

> But why remove the line feeds?  Unless they are in pre-formatted text
> are they not just white-space to HTML?

IIRC, the descriptions used to be inside a <pre> tag.

Now they're not, so there has to be a way to preserve the formatting. What
else is there besides <pre> or adding a <br> at the end of each line?

(That's not a rhetorical question, I haven't paid attention to HTML
standards for the last 15 or so years, so maybe there's a proper solution
I never heard of?)

From rshepard at appl-ecosys.com  Tue Jan 23 17:52:13 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 23 Jan 2018 09:52:13 -0800 (PST)
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CAN1hMuD88xS_AT6YPvJa+X5w=kXsYAg09ag+ALLZg3rsL8D=2A@mail.gmail.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <d21ea0ac-bf2d-5193-5273-c7e3dce26b34@slint.fr>
 <20180123170954.GF19058@jdiamond-mb.acadiau.ca>
 <CAN1hMuD88xS_AT6YPvJa+X5w=kXsYAg09ag+ALLZg3rsL8D=2A@mail.gmail.com>
Message-ID: <alpine.LNX.2.20.1801230946240.32286@salmo.appl-ecosys.com>

On Tue, 23 Jan 2018, B Watson wrote:

> Now they're not, so there has to be a way to preserve the formatting. What
> else is there besides <pre> or adding a <br> at the end of each line?

   In what version of html is the site written?

   I'm not a web developer (but have written and re-writtem my company web
site many times over the past 25 years). Now it's in html5 and css3. For the
latest revision (last last autumn) I found this site very helpful:
<https://developer.mozilla.org/en-US/docs/Learn/HTML/Introduction_to_HTML>.

HTH,

Rich

From Jim.Diamond at acadiau.ca  Tue Jan 23 17:54:43 2018
From: Jim.Diamond at acadiau.ca (Jim Diamond)
Date: Tue, 23 Jan 2018 13:54:43 -0400
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CAN1hMuD88xS_AT6YPvJa+X5w=kXsYAg09ag+ALLZg3rsL8D=2A@mail.gmail.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <d21ea0ac-bf2d-5193-5273-c7e3dce26b34@slint.fr>
 <20180123170954.GF19058@jdiamond-mb.acadiau.ca>
 <CAN1hMuD88xS_AT6YPvJa+X5w=kXsYAg09ag+ALLZg3rsL8D=2A@mail.gmail.com>
Message-ID: <20180123175443.GA26123@jdiamond-mb.acadiau.ca>

On Tue, Jan 23, 2018 at 12:20 (-0500), B Watson wrote:

> On 1/23/18, Jim Diamond wrote:
>> You are right that turning line feeds into <br /> seems like a bad idea.

> The descriptions are plain text, and sometimes have things like bulleted
> or numbered lists, done in text.

>   - Like this
>   - And this

> Some of them even have ASCII art... I shot myself in the foot on this
> issue with a script that reformatted all the READMEs to make them
> "better".

>> But why remove the line feeds?  Unless they are in pre-formatted text
>> are they not just white-space to HTML?

> IIRC, the descriptions used to be inside a <pre> tag.

> Now they're not, so there has to be a way to preserve the formatting. What
> else is there besides <pre> or adding a <br> at the end of each line?

I see that (some) are inside a <pre> tag.  Here is the start of qt5's blurb:

    <h2>
      <a href="/repository/14.2/">14.2</a> &gt;
      <a href="/repository/14.2/libraries/">Libraries</a> &gt;
      qt5 (5.7.1)    </h2>
    <pre>Qt is a cross-platform C++ application framework. Qt&#039;s
    primary feature<br />is its rich set of widgets that provide
    standard GUI functionality.<br /><br />Optional dependencies:
    unixodbc, freetds, OpenAL, libwebp, opus, snappy,<br />wayland,
    and postgresql<br /><br />Optional
...

> (That's not a rhetorical question, I haven't paid attention to HTML
> standards for the last 15 or so years, so maybe there's a proper solution
> I never heard of?)
Maybe there is some web page whizz who can answer your question.  I
occasionally do things like
        <ul>
            <li>unnumbered list item 1</li>
            <li>unnumbered list item 2</li>
            <li>unnumbered list item 3</li>
            <li>unnumbered list item 4</li>
        </ul>
but since I avoid writing HTML like the plague, this is probably some
old-fashioned, pooh-poohed way of doing things.

                                Ji
                                



From didier at slint.fr  Tue Jan 23 18:04:33 2018
From: didier at slint.fr (Didier Spaier)
Date: Tue, 23 Jan 2018 19:04:33 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <alpine.LNX.2.20.1801230946240.32286@salmo.appl-ecosys.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <d21ea0ac-bf2d-5193-5273-c7e3dce26b34@slint.fr>
 <20180123170954.GF19058@jdiamond-mb.acadiau.ca>
 <CAN1hMuD88xS_AT6YPvJa+X5w=kXsYAg09ag+ALLZg3rsL8D=2A@mail.gmail.com>
 <alpine.LNX.2.20.1801230946240.32286@salmo.appl-ecosys.com>
Message-ID: <f1a4e67f-febe-6a96-caee-c7a5202a34a8@slint.fr>



Le 23/01/2018 ? 18:52, Rich Shepard a ?crit?:
> ? In what version of html is the site written?

Ctrl+u in Firefox would have given you the answer: 

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">

Didier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x60C03EEA.asc
Type: application/pgp-keys
Size: 1718 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180123/610229cf/attachment-0001.bin>

From rshepard at appl-ecosys.com  Tue Jan 23 18:09:19 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Tue, 23 Jan 2018 10:09:19 -0800 (PST)
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180123175443.GA26123@jdiamond-mb.acadiau.ca>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <d21ea0ac-bf2d-5193-5273-c7e3dce26b34@slint.fr>
 <20180123170954.GF19058@jdiamond-mb.acadiau.ca>
 <CAN1hMuD88xS_AT6YPvJa+X5w=kXsYAg09ag+ALLZg3rsL8D=2A@mail.gmail.com>
 <20180123175443.GA26123@jdiamond-mb.acadiau.ca>
Message-ID: <alpine.LNX.2.20.1801231003590.32286@salmo.appl-ecosys.com>

On Tue, 23 Jan 2018, Jim Diamond wrote:

> I see that (some) are inside a <pre> tag.  Here is the start of qt5's blurb:
>
>    <h2>
>      <a href="/repository/14.2/">14.2</a> &gt;
>      <a href="/repository/14.2/libraries/">Libraries</a> &gt;
>      qt5 (5.7.1)    </h2>
>    <pre>Qt is a cross-platform C++ application framework. Qt&#039;s
>    primary feature<br />is its rich set of widgets that provide
>    standard GUI functionality.<br /><br />Optional dependencies:
>    unixodbc, freetds, OpenAL, libwebp, opus, snappy,<br />wayland,
>    and postgresql<br /><br />Optional

   Not sure this will help, but I offer it anyway. This is how the body of my
web site's 'markets served' page begins:

<main>
       <section class="main">
         <header>
           <h1>Markets Served</h1>
         </header>
         <br>
         <header>
           <h2>Introduction</h2>
         </header>
         <br>
         <p>
           Natural resource industries interact intimately with natural
           ecosystems, and sometimes their operations cause adverse impacts on
           these environments and the plants and animals living in them; at
           times there are also potential impacts to humans. These conditions
           raise concerns by regulators that need to be avoided or efficiently
           and effectively resolved.
         </p>
         <br>
         <p>
           Natural resource operations are also frequent targets of citizen
           groups and organizations. Their objections can have many origins,
           such as not in my backyard, or the idea that natural ecosystems are
           static and do not change with change being bad and man-caused change
           unacceptable, or not understanding that society depends on these
           operations and that they can be operated in an
           environmentally-responsible manner.
         </p>
       </section>
       <br><br>

   The css3 script holds the formatting for each tag; e.g.,
.main p {
     width: 60%;
     padding: 0% 10% 0% 19%;
     margin: 0% 10% 0% 2.5%;
}

HTH,

Rich

From skaendo at excite.com  Tue Jan 23 18:56:25 2018
From: skaendo at excite.com (Ed Ender)
Date: Tue, 23 Jan 2018 13:56:25 -0500
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
Message-ID: <20180123135625.30865@web008.roc2.bluetie.com>

The layout looks pretty much the same for me. (Pale Moon 27.7.1)
The only thing that I see weird is the search.
	#1 I have to manually wipe out the word 'Search' and enter my search term now.
	#2 the 'enter' button is slightly off. https://imgur.com/a/591tm



-----Original Message-----
From: "Rich Shepard" [rshepard at appl-ecosys.com]
Date: 01/23/2018 12:09 PM
To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
Subject: Re: [Slackbuilds-users] New layout of https://slackbuilds.org/

On Tue, 23 Jan 2018, Jim Diamond wrote:

> I see that (some) are inside a <pre> tag.  Here is the start of qt5's blurb:
>
>    <h2>
>      <a href="/repository/14.2/">14.2</a> >
>      <a href="/repository/14.2/libraries/">Libraries</a> >
>      qt5 (5.7.1)    </h2>
>    <pre>Qt is a cross-platform C++ application framework. Qt's
>    primary feature<br />is its rich set of widgets that provide
>    standard GUI functionality.<br /><br />Optional dependencies:
>    unixodbc, freetds, OpenAL, libwebp, opus, snappy,<br />wayland,
>    and postgresql<br /><br />Optional

   Not sure this will help, but I offer it anyway. This is how the body of my
web site's 'markets served' page begins:

<main>
       <section class="main">
         <header>
           <h1>Markets Served</h1>
         </header>
         

         <header>
           <h2>Introduction</h2>
         </header>
         

         <p>
           Natural resource industries interact intimately with natural
           ecosystems, and sometimes their operations cause adverse impacts on
           these environments and the plants and animals living in them; at
           times there are also potential impacts to humans. These conditions
           raise concerns by regulators that need to be avoided or efficiently
           and effectively resolved.
         </p>
         

         <p>
           Natural resource operations are also frequent targets of citizen
           groups and organizations. Their objections can have many origins,
           such as not in my backyard, or the idea that natural ecosystems are
           static and do not change with change being bad and man-caused change
           unacceptable, or not understanding that society depends on these
           operations and that they can be operated in an
           environmentally-responsible manner.
         </p>
       </section>
       



   The css3 script holds the formatting for each tag; e.g.,
.main p {
     width: 60%;
     padding: 0% 10% 0% 19%;
     margin: 0% 10% 0% 2.5%;
}

HTH,

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/




From fernando.lopezjr at gmail.com  Tue Jan 23 22:54:47 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Tue, 23 Jan 2018 15:54:47 -0700
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180123135625.30865@web008.roc2.bluetie.com>
References: <20180123135625.30865@web008.roc2.bluetie.com>
Message-ID: <CALrQ46C1-uAi7sjwapKP2nZYFT0PoQJGgUUJdDwOnMnNNhwG_Q@mail.gmail.com>

what button!!????

https://imgur.com/a/taoJa

On Tue, Jan 23, 2018 at 11:56 AM, Ed Ender <skaendo at excite.com> wrote:

> The layout looks pretty much the same for me. (Pale Moon 27.7.1)
> The only thing that I see weird is the search.
>         #1 I have to manually wipe out the word 'Search' and enter my
> search term now.
>         #2 the 'enter' button is slightly off. https://imgur.com/a/591tm
>
>
>
> -----Original Message-----
> From: "Rich Shepard" [rshepard at appl-ecosys.com]
> Date: 01/23/2018 12:09 PM
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] New layout of https://slackbuilds.org/
>
> On Tue, 23 Jan 2018, Jim Diamond wrote:
>
> > I see that (some) are inside a <pre> tag.  Here is the start of qt5's
> blurb:
> >
> >    <h2>
> >      <a href="/repository/14.2/">14.2</a> >
> >      <a href="/repository/14.2/libraries/">Libraries</a> >
> >      qt5 (5.7.1)    </h2>
> >    <pre>Qt is a cross-platform C++ application framework. Qt's
> >    primary feature<br />is its rich set of widgets that provide
> >    standard GUI functionality.<br /><br />Optional dependencies:
> >    unixodbc, freetds, OpenAL, libwebp, opus, snappy,<br />wayland,
> >    and postgresql<br /><br />Optional
>
>    Not sure this will help, but I offer it anyway. This is how the body of
> my
> web site's 'markets served' page begins:
>
> <main>
>        <section class="main">
>          <header>
>            <h1>Markets Served</h1>
>          </header>
>
>
>          <header>
>            <h2>Introduction</h2>
>          </header>
>
>
>          <p>
>            Natural resource industries interact intimately with natural
>            ecosystems, and sometimes their operations cause adverse
> impacts on
>            these environments and the plants and animals living in them; at
>            times there are also potential impacts to humans. These
> conditions
>            raise concerns by regulators that need to be avoided or
> efficiently
>            and effectively resolved.
>          </p>
>
>
>          <p>
>            Natural resource operations are also frequent targets of citizen
>            groups and organizations. Their objections can have many
> origins,
>            such as not in my backyard, or the idea that natural ecosystems
> are
>            static and do not change with change being bad and man-caused
> change
>            unacceptable, or not understanding that society depends on these
>            operations and that they can be operated in an
>            environmentally-responsible manner.
>          </p>
>        </section>
>
>
>
>
>    The css3 script holds the formatting for each tag; e.g.,
> .main p {
>      width: 60%;
>      padding: 0% 10% 0% 19%;
>      margin: 0% 10% 0% 2.5%;
> }
>
> HTH,
>
> 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/
>
>
>
> _______________________________________________
> 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/20180123/e2812c99/attachment.html>

From aubreylegendre at gmail.com  Wed Jan 24 02:46:54 2018
From: aubreylegendre at gmail.com (Aubrey Legendre)
Date: Tue, 23 Jan 2018 20:46:54 -0600
Subject: [Slackbuilds-users] VLC build for Slackware 14.2
Message-ID: <9a8e6635-0c4c-846b-fe59-a37ba8e2085e@gmail.com>

Hey guys, I hope I'm not sending this to the wrong group, please excuse 
me if it's not correct.

I have installed full version of all software for Slackware 14.2, not 
added anything other than what's on the install disk.? Then I came to 
slackbuilds.org to get everything needed to build VLC.? In the list of 
dependencies is QT5.? I compiled it (and it's dependencies) and I think 
it breaks something for QT4 that's already installed, and this disables 
VLC from compiling.? Once I removed the QT5 package, then reinstalled 
the QT4 package from install disk, and re-compiled VLC again, it works.


It may be worth mentioning that building QT5 took a little over 12 hours.


Thank you for all that you do!

-Aubrey Legendre


From fernando.lopezjr at gmail.com  Wed Jan 24 03:54:42 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Tue, 23 Jan 2018 20:54:42 -0700
Subject: [Slackbuilds-users] VLC build for Slackware 14.2
In-Reply-To: <9a8e6635-0c4c-846b-fe59-a37ba8e2085e@gmail.com>
References: <9a8e6635-0c4c-846b-fe59-a37ba8e2085e@gmail.com>
Message-ID: <CALrQ46CvXe4ZsFcUTNyNe6CjiMZ52hjEZbMwi8Q1Wc9_9+4Otg@mail.gmail.com>

I always get alienbob packages for VLC... i mainly use mpv... but latest
version needs newer ffmpeg...

https://www.videolan.org/vlc/download-slackware.html

On Tue, Jan 23, 2018 at 7:46 PM, Aubrey Legendre <aubreylegendre at gmail.com>
wrote:

> Hey guys, I hope I'm not sending this to the wrong group, please excuse me
> if it's not correct.
>
> I have installed full version of all software for Slackware 14.2, not
> added anything other than what's on the install disk.  Then I came to
> slackbuilds.org to get everything needed to build VLC.  In the list of
> dependencies is QT5.  I compiled it (and it's dependencies) and I think it
> breaks something for QT4 that's already installed, and this disables VLC
> from compiling.  Once I removed the QT5 package, then reinstalled the QT4
> package from install disk, and re-compiled VLC again, it works.
>
>
> It may be worth mentioning that building QT5 took a little over 12 hours.
>
>
> Thank you for all that you do!
>
> -Aubrey Legendre
>
> _______________________________________________
> 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/20180123/a563fa46/attachment-0001.html>

From dave at dawoodfall.net  Wed Jan 24 08:37:03 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Wed, 24 Jan 2018 08:37:03 +0000
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
Message-ID: <20180124083703.GD26225@Blackswan>

>On 01/23/2018 09:14 AM, Petar Petrov wrote:
>> with all due respect, I don't like it. It looks squashed.
>>
>> What's the point of having a wide layout, when the description of each
>> entry is still limited to 72 characters per line?
>>
>> -petar
>>
>
>
>My thoughts as well. Lots of wasted white space on the right when you
>view a SlackBuild's individual page. It's not a responsive layout so the
>wasted space is there on mobile too.
>
>-- 
>Gerardo Zamudio

Hi

The readme info is generated from the supplied README for the
slackbuild by reading it in php, formatting it, and then printing
between <pre> tags.

I've had a look to see if/how the wrapping amount could be changed to
help fill out the page width, but I'm afraid it's not really possible
to tell if two adjacent lines should be wrapped together, or whether
the next line should be on a newline, such as in a list for example.

Dave

From dave at dawoodfall.net  Wed Jan 24 08:44:32 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Wed, 24 Jan 2018 08:44:32 +0000
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180123135625.30865@web008.roc2.bluetie.com>
References: <20180123135625.30865@web008.roc2.bluetie.com>
Message-ID: <20180124084432.GE26225@Blackswan>

>The layout looks pretty much the same for me. (Pale Moon 27.7.1)
>The only thing that I see weird is the search.
>	#1 I have to manually wipe out the word 'Search' and enter my search term now.
>	#2 the 'enter' button is slightly off. https://imgur.com/a/591tm

Hi

I've just fixed the 'search' box so it shouldn't print the text now.

I took out the search button some time ago, so that shouldn't show for
you.  Perhaps you need to do a ctrl-F5 to force a refresh.

Dave

>-----Original Message-----
>From: "Rich Shepard" [rshepard at appl-ecosys.com]
>Date: 01/23/2018 12:09 PM
>To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
>Subject: Re: [Slackbuilds-users] New layout of https://slackbuilds.org/
>
>On Tue, 23 Jan 2018, Jim Diamond wrote:
>
>> I see that (some) are inside a <pre> tag.  Here is the start of qt5's blurb:
>>
>>    <h2>
>>      <a href="/repository/14.2/">14.2</a> >
>>      <a href="/repository/14.2/libraries/">Libraries</a> >
>>      qt5 (5.7.1)    </h2>
>>    <pre>Qt is a cross-platform C++ application framework. Qt's
>>    primary feature<br />is its rich set of widgets that provide
>>    standard GUI functionality.<br /><br />Optional dependencies:
>>    unixodbc, freetds, OpenAL, libwebp, opus, snappy,<br />wayland,
>>    and postgresql<br /><br />Optional
>
>   Not sure this will help, but I offer it anyway. This is how the body of my
>web site's 'markets served' page begins:
>
><main>
>       <section class="main">
>         <header>
>           <h1>Markets Served</h1>
>         </header>
>
>
>         <header>
>           <h2>Introduction</h2>
>         </header>
>
>
>         <p>
>           Natural resource industries interact intimately with natural
>           ecosystems, and sometimes their operations cause adverse impacts on
>           these environments and the plants and animals living in them; at
>           times there are also potential impacts to humans. These conditions
>           raise concerns by regulators that need to be avoided or efficiently
>           and effectively resolved.
>         </p>
>
>
>         <p>
>           Natural resource operations are also frequent targets of citizen
>           groups and organizations. Their objections can have many origins,
>           such as not in my backyard, or the idea that natural ecosystems are
>           static and do not change with change being bad and man-caused change
>           unacceptable, or not understanding that society depends on these
>           operations and that they can be operated in an
>           environmentally-responsible manner.
>         </p>
>       </section>
>
>
>
>
>   The css3 script holds the formatting for each tag; e.g.,
>.main p {
>     width: 60%;
>     padding: 0% 10% 0% 19%;
>     margin: 0% 10% 0% 2.5%;
>}
>
>HTH,
>
>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/
>
>
>
>_______________________________________________
>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 yth at ythogtha.org  Wed Jan 24 09:05:49 2018
From: yth at ythogtha.org (Ythogtha)
Date: Wed, 24 Jan 2018 10:05:49 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180124084432.GE26225@Blackswan>
References: <20180123135625.30865@web008.roc2.bluetie.com>
 <20180124084432.GE26225@Blackswan>
Message-ID: <20180124100549.6f35a2099d15ad44ad4b12a1@ythogtha.org>

> >The layout looks pretty much the same for me. (Pale Moon 27.7.1)
> >The only thing that I see weird is the search.
> >	#1 I have to manually wipe out the word 'Search' and enter my search
> >	#term now. 2 the 'enter' button is slightly off.
> >	#https://imgur.com/a/591tm
> 
> Hi
> 
> I've just fixed the 'search' box so it shouldn't print the text now.
> 
> I took out the search button some time ago, so that shouldn't show for
> you.  Perhaps you need to do a ctrl-F5 to force a refresh.
> 
> Dave

Hi !

	I'm a web developer, amongst other things but nowadays I teach people
how to write websites, so maybe I could help ?
I know about HTML5, CSS3, responsive design, and a whole lot more of them
modern web buzzwords.
	And I have some time at hand for a few months.

So if you want any help, I'd be pleased to !

-- 
Arnaud <yth at ythogtha.org>

From skaendo at excite.com  Wed Jan 24 09:22:07 2018
From: skaendo at excite.com (Ed Ender)
Date: Wed, 24 Jan 2018 04:22:07 -0500
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
Message-ID: <20180124042207.7718@web003.roc2.bluetie.com>

Yep, there it goes. now I got the new layout.
Now I am wondering if the searchbox was ok and it was just me needing that forced refresh.


-----Original Message-----
From: "David Woodfall" [dave at dawoodfall.net]
Date: 01/24/2018 02:45 AM
To: slackbuilds-users at slackbuilds.org
Subject: Re: [Slackbuilds-users] New layout of https://slackbuilds.org/

>The layout looks pretty much the same for me. (Pale Moon 27.7.1)
>The only thing that I see weird is the search.
>	#1 I have to manually wipe out the word 'Search' and enter my search term now.
>	#2 the 'enter' button is slightly off. https://imgur.com/a/591tm

Hi

I've just fixed the 'search' box so it shouldn't print the text now.

I took out the search button some time ago, so that shouldn't show for
you.  Perhaps you need to do a ctrl-F5 to force a refresh.

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 atelszewski at gmail.com  Wed Jan 24 09:59:07 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 24 Jan 2018 10:59:07 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180124042207.7718@web003.roc2.bluetie.com>
References: <20180124042207.7718@web003.roc2.bluetie.com>
Message-ID: <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>

Hi,

Just a quick note.

You have to keep READMEs format and mono spaced font.
Without it, bullet lists or other indentations won't work.

-- 
Best regards,
Andrzej Telszewski

From harald.achitz at gmail.com  Wed Jan 24 12:04:21 2018
From: harald.achitz at gmail.com (Harald Achitz)
Date: Wed, 24 Jan 2018 13:04:21 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
Message-ID: <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>

And I thought this change was an accidental temporary thing.
Why a new site layout that is not tested on mobile?

Can you switch back please?

send from my fairphone

On Jan 24, 2018 10:57, "Andrzej Telszewski" <atelszewski at gmail.com> wrote:

> Hi,
>
> Just a quick note.
>
> You have to keep READMEs format and mono spaced font.
> Without it, bullet lists or other indentations won't work.
>
> --
> Best regards,
> Andrzej Telszewski
> _______________________________________________
> 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/20180124/dc1e9ac3/attachment.html>

From chris.willing at iinet.net.au  Wed Jan 24 12:11:07 2018
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Wed, 24 Jan 2018 22:11:07 +1000
Subject: [Slackbuilds-users] VLC build for Slackware 14.2
In-Reply-To: <9a8e6635-0c4c-846b-fe59-a37ba8e2085e@gmail.com>
References: <9a8e6635-0c4c-846b-fe59-a37ba8e2085e@gmail.com>
Message-ID: <ff01f756-75fd-554a-ae7f-84acc135b910@iinet.net.au>

On 24/01/18 12:46, Aubrey Legendre wrote:
> Hey guys, I hope I'm not sending this to the wrong group, please excuse
> me if it's not correct.
> 
> I have installed full version of all software for Slackware 14.2, not
> added anything other than what's on the install disk

Hi Aubrey,

I hope you also installed the numerous patches issued since the install
disk was released so that your system is fully up to date. Many of these
patches address security issues.

Apart from the security issues,
    "All of our scripts are written and tested for usage on the latest
stable release of Slackware with full installation and updated with
latest patches; ..."
(from: https://slackbuilds.org/howto/).


> Then I came to
> slackbuilds.org to get everything needed to build VLC.? In the list of
> dependencies is QT5.? I compiled it (and it's dependencies) and I think
> it breaks something for QT4 that's already installed, and this disables
> VLC from compiling.? Once I removed the QT5 package, then reinstalled
> the QT4 package from install disk, and re-compiled VLC again, it works.
> 
Some sensitivity to Qt versions is already mentioned in the vlc
SlackBuild's README and the SlackBuild uses Qt5 by default, not Qt4, so
it's unclear why anything to do with Qt4 is affecting your build of vlc.
However I'm reluctant to delve too deeply until we know the problem
still exists even when your system is fully up to date.

chris

From didier at slint.fr  Wed Jan 24 12:31:21 2018
From: didier at slint.fr (Didier Spaier)
Date: Wed, 24 Jan 2018 13:31:21 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
Message-ID: <05b442f1-53a1-409f-7ef8-7fd369b533d4@slint.fr>

Hello,

Le 24/01/2018 ? 13:04, Harald Achitz a ?crit?:
> And I thought this change was an accidental temporary thing.?
> Why a new site layout that is not tested on mobile?
> 
> Can you switch back please?

I would prefer to keep the new layout with enhancements,
part of which can be brought modifying the style sheet,
maybe providing alternate ones for specific viewports.

Didier

From matteo.bernardini at gmail.com  Wed Jan 24 13:30:15 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 24 Jan 2018 14:30:15 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
Message-ID: <CAPsDuS7pRVPbRqk=fsF+fdVb6ThZiMVXvqXqUFYbG4eytMHh5Q@mail.gmail.com>

2018-01-23 11:04 GMT+01:00 Didier Spaier <didier at slint.fr>:
> Hello,
>
> I like the new layout of the website with the new style sheet, clean and easy to read. Thanks!

thanks also from me, David!
nice work!

Matteo

From dave at dawoodfall.net  Wed Jan 24 15:09:40 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Wed, 24 Jan 2018 15:09:40 +0000
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
Message-ID: <20180124150940.GF26225@Blackswan>

>And I thought this change was an accidental temporary thing.
>Why a new site layout that is not tested on mobile?
>
>Can you switch back please?
>
>send from my fairphone

Hi

What problems are you experiencing?

>On Jan 24, 2018 10:57, "Andrzej Telszewski" <atelszewski at gmail.com> wrote:
>
>> Hi,
>>
>> Just a quick note.
>>
>> You have to keep READMEs format and mono spaced font.
>> Without it, bullet lists or other indentations won't work.
>>
>> --
>> Best regards,
>> Andrzej Telszewski
>> _______________________________________________
>> 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 ricardo at palmtx.com.ar  Wed Jan 24 15:25:19 2018
From: ricardo at palmtx.com.ar (Ricardo J. Barberis)
Date: Wed, 24 Jan 2018 12:25:19 -0300
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180124084432.GE26225@Blackswan>
References: <20180123135625.30865@web008.roc2.bluetie.com>
 <20180124084432.GE26225@Blackswan>
Message-ID: <201801241225.20076.ricardo@palmtx.com.ar>

El Mi?rcoles 24/01/2018 a las 05:44, David Woodfall escribi?:
> >The layout looks pretty much the same for me. (Pale Moon 27.7.1)
> >The only thing that I see weird is the search.
> >	#1 I have to manually wipe out the word 'Search' and enter my search term
> > now. #2 the 'enter' button is slightly off. https://imgur.com/a/591tm
>
> Hi
>
> I've just fixed the 'search' box so it shouldn't print the text now.
>
> I took out the search button some time ago, so that shouldn't show for
> you.  Perhaps you need to do a ctrl-F5 to force a refresh.
>
> Dave

Wow, I had to Ctrl+F5 too or I'd never have seen the new website :)
Strangely, Ctrl+R and Shift+F5 (which I usually use to refresh my browser's 
cache) didn't have any effect.

BTW, wasn't HTTPS supposed to NOT cache web resources?

I have to say that I like the new look very much, but I agree with most that 
the layout is too wide to my taste. If it can be made a little narrower I 
think it'd be perfect :)

Oh, and +1 to monospaced font for the READMEs!

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 dave at dawoodfall.net  Wed Jan 24 15:36:45 2018
From: dave at dawoodfall.net (David Woodfall)
Date: Wed, 24 Jan 2018 15:36:45 +0000
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <201801241225.20076.ricardo@palmtx.com.ar>
References: <20180123135625.30865@web008.roc2.bluetie.com>
 <20180124084432.GE26225@Blackswan>
 <201801241225.20076.ricardo@palmtx.com.ar>
Message-ID: <20180124153645.GG26225@Blackswan>

>El Mi?rcoles 24/01/2018 a las 05:44, David Woodfall escribi?:
>> >The layout looks pretty much the same for me. (Pale Moon 27.7.1)
>> >The only thing that I see weird is the search.
>> >	#1 I have to manually wipe out the word 'Search' and enter my search term
>> > now. #2 the 'enter' button is slightly off. https://imgur.com/a/591tm
>>
>> Hi
>>
>> I've just fixed the 'search' box so it shouldn't print the text now.
>>
>> I took out the search button some time ago, so that shouldn't show for
>> you.  Perhaps you need to do a ctrl-F5 to force a refresh.
>>
>> Dave
>
>Wow, I had to Ctrl+F5 too or I'd never have seen the new website :)
>Strangely, Ctrl+R and Shift+F5 (which I usually use to refresh my browser's
>cache) didn't have any effect.
>
>BTW, wasn't HTTPS supposed to NOT cache web resources?
>
>I have to say that I like the new look very much, but I agree with most that
>the layout is too wide to my taste. If it can be made a little narrower I
>think it'd be perfect :)
>
>Oh, and +1 to monospaced font for the READMEs!

Done.

>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
>_______________________________________________
>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 harald.achitz at gmail.com  Wed Jan 24 18:33:25 2018
From: harald.achitz at gmail.com (Harald Achitz)
Date: Wed, 24 Jan 2018 19:33:25 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180124150940.GF26225@Blackswan>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
 <20180124150940.GF26225@Blackswan>
Message-ID: <CAPh+tzPzK+yU9PDn5sd2ns1Ee56f-hKCj9fELZLHiAAi53dA8Q@mail.gmail.com>

with firefox and the tree style tab the new site gives me a scroll bar on
botton of the page
very irritating, the old page did not do this

on mobile, the menu bar + the search field  is super very small, unreadable
for me

2018-01-24 16:09 GMT+01:00 David Woodfall <dave at dawoodfall.net>:

> And I thought this change was an accidental temporary thing.
>> Why a new site layout that is not tested on mobile?
>>
>> Can you switch back please?
>>
>> send from my fairphone
>>
>
> Hi
>
> What problems are you experiencing?
>
>
> On Jan 24, 2018 10:57, "Andrzej Telszewski" <atelszewski at gmail.com> wrote:
>>
>> Hi,
>>>
>>> Just a quick note.
>>>
>>> You have to keep READMEs format and mono spaced font.
>>> Without it, bullet lists or other indentations won't work.
>>>
>>> --
>>> Best regards,
>>> Andrzej Telszewski
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>>
>>>
> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180124/7f672b00/attachment-0001.html>

From fernando.lopezjr at gmail.com  Thu Jan 25 00:40:55 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Wed, 24 Jan 2018 17:40:55 -0700
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CAPh+tzPzK+yU9PDn5sd2ns1Ee56f-hKCj9fELZLHiAAi53dA8Q@mail.gmail.com>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
 <20180124150940.GF26225@Blackswan>
 <CAPh+tzPzK+yU9PDn5sd2ns1Ee56f-hKCj9fELZLHiAAi53dA8Q@mail.gmail.com>
Message-ID: <CALrQ46DQarsqh2jwiAAhVf8oEC4S1+u0LKqMTWWi1VkHruTerw@mail.gmail.com>

where is the search
box!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

On Wed, Jan 24, 2018 at 11:33 AM, Harald Achitz <harald.achitz at gmail.com>
wrote:

> with firefox and the tree style tab the new site gives me a scroll bar on
> botton of the page
> very irritating, the old page did not do this
>
> on mobile, the menu bar + the search field  is super very small,
> unreadable for me
>
> 2018-01-24 16:09 GMT+01:00 David Woodfall <dave at dawoodfall.net>:
>
>> And I thought this change was an accidental temporary thing.
>>> Why a new site layout that is not tested on mobile?
>>>
>>> Can you switch back please?
>>>
>>> send from my fairphone
>>>
>>
>> Hi
>>
>> What problems are you experiencing?
>>
>>
>> On Jan 24, 2018 10:57, "Andrzej Telszewski" <atelszewski at gmail.com>
>>> wrote:
>>>
>>> Hi,
>>>>
>>>> Just a quick note.
>>>>
>>>> You have to keep READMEs format and mono spaced font.
>>>> Without it, bullet lists or other indentations won't work.
>>>>
>>>> --
>>>> Best regards,
>>>> Andrzej Telszewski
>>>> _______________________________________________
>>>> SlackBuilds-users mailing list
>>>> SlackBuilds-users at slackbuilds.org
>>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>>> FAQ - https://slackbuilds.org/faq/
>>>>
>>>>
>>>>
>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>


-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180124/b8b7ffd9/attachment-0001.html>

From fernando.lopezjr at gmail.com  Thu Jan 25 00:56:41 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Wed, 24 Jan 2018 17:56:41 -0700
Subject: [Slackbuilds-users] i would like to take over kicad-library
 kicad-doc.
Message-ID: <CALrQ46BqdgVRG_9YahVEsVaepNdk_m7tUkGjf=v7=jYKbMs1ow@mail.gmail.com>

I am the current maintainer of kicad and i would like to take this two
packages since they belong to kicad and they havent been updated in a
while...

https://slackbuilds.org/repository/14.2/development/kicad-library/
https://slackbuilds.org/repository/14.2/development/kicad-doc/

thank you!

-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180124/3c194c35/attachment.html>

From willysr at slackbuilds.org  Thu Jan 25 01:05:01 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 25 Jan 2018 08:05:01 +0700
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CALrQ46DQarsqh2jwiAAhVf8oEC4S1+u0LKqMTWWi1VkHruTerw@mail.gmail.com>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
 <20180124150940.GF26225@Blackswan>
 <CAPh+tzPzK+yU9PDn5sd2ns1Ee56f-hKCj9fELZLHiAAi53dA8Q@mail.gmail.com>
 <CALrQ46DQarsqh2jwiAAhVf8oEC4S1+u0LKqMTWWi1VkHruTerw@mail.gmail.com>
Message-ID: <236a4e3f-28d8-7169-9ef9-5c7513cef9cc@slackbuilds.org>

> where is the search
> box!

https://slackbuilds.org/search/


-- 
Willy Sudiarto Raharjo

-------------- 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/20180125/c65ff4ec/attachment.asc>

From willysr at slackbuilds.org  Thu Jan 25 01:05:52 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 25 Jan 2018 08:05:52 +0700
Subject: [Slackbuilds-users] i would like to take over kicad-library
 kicad-doc.
In-Reply-To: <CALrQ46BqdgVRG_9YahVEsVaepNdk_m7tUkGjf=v7=jYKbMs1ow@mail.gmail.com>
References: <CALrQ46BqdgVRG_9YahVEsVaepNdk_m7tUkGjf=v7=jYKbMs1ow@mail.gmail.com>
Message-ID: <7f6d4bfa-ad92-ed61-018a-6dc402bc763d@slackbuilds.org>

> I am the current maintainer of kicad and i would like to take this two
> packages since they belong to kicad and they havent been updated in a
> while...
> 
> https://slackbuilds.org/repository/14.2/development/kicad-library/
> https://slackbuilds.org/repository/14.2/development/kicad-doc/

Sure, feel free to take over


-- 
Willy Sudiarto Raharjo

-------------- 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/20180125/090d004c/attachment.asc>

From fernando.lopezjr at gmail.com  Thu Jan 25 01:06:33 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Wed, 24 Jan 2018 18:06:33 -0700
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <236a4e3f-28d8-7169-9ef9-5c7513cef9cc@slackbuilds.org>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
 <20180124150940.GF26225@Blackswan>
 <CAPh+tzPzK+yU9PDn5sd2ns1Ee56f-hKCj9fELZLHiAAi53dA8Q@mail.gmail.com>
 <CALrQ46DQarsqh2jwiAAhVf8oEC4S1+u0LKqMTWWi1VkHruTerw@mail.gmail.com>
 <236a4e3f-28d8-7169-9ef9-5c7513cef9cc@slackbuilds.org>
Message-ID: <CALrQ46AtKOGpxwtBuZ2TEJQZg1fA2RVS482sb2Vic1uRiWsb9Q@mail.gmail.com>

i know... but why to remove it from the search bar... now i have to do an
extra step...

On Wed, Jan 24, 2018 at 6:05 PM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > where is the search
> > box!
>
> https://slackbuilds.org/search/
>
>
> --
> 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/20180124/5b6ad4bf/attachment.html>

From fernando.lopezjr at gmail.com  Thu Jan 25 01:06:48 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Wed, 24 Jan 2018 18:06:48 -0700
Subject: [Slackbuilds-users] i would like to take over kicad-library
 kicad-doc.
In-Reply-To: <7f6d4bfa-ad92-ed61-018a-6dc402bc763d@slackbuilds.org>
References: <CALrQ46BqdgVRG_9YahVEsVaepNdk_m7tUkGjf=v7=jYKbMs1ow@mail.gmail.com>
 <7f6d4bfa-ad92-ed61-018a-6dc402bc763d@slackbuilds.org>
Message-ID: <CALrQ46CTo33fx1KEc5kqYaumP-Bz3D=F88-cr-qreC8QaOKiQA@mail.gmail.com>

thank you.

On Wed, Jan 24, 2018 at 6:05 PM, Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > I am the current maintainer of kicad and i would like to take this two
> > packages since they belong to kicad and they havent been updated in a
> > while...
> >
> > https://slackbuilds.org/repository/14.2/development/kicad-library/
> > https://slackbuilds.org/repository/14.2/development/kicad-doc/
>
> Sure, feel free to take over
>
>
> --
> 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/20180124/01d0a202/attachment.html>

From skaendo at excite.com  Thu Jan 25 01:53:16 2018
From: skaendo at excite.com (Ed Ender)
Date: Wed, 24 Jan 2018 20:53:16 -0500
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
Message-ID: <20180124205316.17063@web002.roc2.bluetie.com>

+1
Yea, having the searchbox on the frontpage was a lot more useful than having it anywhere else.

-----Original Message-----
From: "Fernando Lopez" [fernando.lopezjr at gmail.com]
Date: 01/24/2018 07:06 PM
To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
Subject: Re: [Slackbuilds-users] New layout of https://slackbuilds.org/

i know... but why to remove it from the search bar... now i have to do an extra step...

On Wed, Jan 24, 2018 at 6:05 PM, Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:
> where is the search
> box!

https://slackbuilds.org/search/


--
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.



From brian at barcus.org  Thu Jan 25 02:02:54 2018
From: brian at barcus.org (Brian Barcus)
Date: Wed, 24 Jan 2018 20:02:54 -0600
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180124205316.17063@web002.roc2.bluetie.com>
References: <20180124205316.17063@web002.roc2.bluetie.com>
Message-ID: <CAMW18pfT7fXzmg+n+GnXufbtN7-8hSgTW45iMdWpJdfbS+EWiw@mail.gmail.com>

The narrow format doesn't bother me at all.  I kinda like it.  Often I use
the site with a terminal window open next to it and the narrow browser
window is gentle on screen space.

The extra step to get to the search is a little bit of a bother but that's
more about being different than bad.

Kudos for being perfectly usable without javascript or any sort of
questionable stuff found on most modern web pages.


On Wed, Jan 24, 2018 at 7:53 PM, Ed Ender <skaendo at excite.com> wrote:

> +1
> Yea, having the searchbox on the frontpage was a lot more useful than
> having it anywhere else.
>
> -----Original Message-----
> From: "Fernando Lopez" [fernando.lopezjr at gmail.com]
> Date: 01/24/2018 07:06 PM
> To: "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> Subject: Re: [Slackbuilds-users] New layout of https://slackbuilds.org/
>
> i know... but why to remove it from the search bar... now i have to do an
> extra step...
>
> On Wed, Jan 24, 2018 at 6:05 PM, Willy Sudiarto Raharjo <
> willysr at slackbuilds.org> wrote:
> > where is the search
> > box!
>
> https://slackbuilds.org/search/
>
>
> --
> 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.
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


-- 
The pipe smoker?s equivalent to a riot:  a bunch of guys raising their
eyebrows and temporarily engaging in a paroxysm of heavy puffing.  --G. L.
Pease

https://google.com/+BrianBarcus
<https://plus.google.com/u/0/+BrianBarcus/about>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180124/24cac9cc/attachment-0001.html>

From erik at slackbuilds.org  Thu Jan 25 06:01:38 2018
From: erik at slackbuilds.org (Erik Hanson)
Date: Thu, 25 Jan 2018 00:01:38 -0600
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <CALrQ46AtKOGpxwtBuZ2TEJQZg1fA2RVS482sb2Vic1uRiWsb9Q@mail.gmail.com>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
 <20180124150940.GF26225@Blackswan>
 <CAPh+tzPzK+yU9PDn5sd2ns1Ee56f-hKCj9fELZLHiAAi53dA8Q@mail.gmail.com>
 <CALrQ46DQarsqh2jwiAAhVf8oEC4S1+u0LKqMTWWi1VkHruTerw@mail.gmail.com>
 <236a4e3f-28d8-7169-9ef9-5c7513cef9cc@slackbuilds.org>
 <CALrQ46AtKOGpxwtBuZ2TEJQZg1fA2RVS482sb2Vic1uRiWsb9Q@mail.gmail.com>
Message-ID: <2fc5592b-0d78-30e4-e65e-b04ebfbd5aac@slackbuilds.org>

On 01/24/2018 07:06 PM, Fernando Lopez wrote:
> i know... but why to remove it from the search bar... now i have to do
> an extra step...

Add a search bookmark to your browser, and then you have one less step
from before. For years I've had it so I can type "sbo whatever" in the
address field and it goes straight to the search results, in Chrome,
Firefox, etc. You've been given tools to make life easier, you should
use them.

That aside, the search box caused broken layout for many people, for as
long as it existed. It's neigh-on-impossible to wedge a form element
into an existing layout, because apparently every browser has some
slightly different way of rendering things, and there's just no good way
around it. Many attempts were made, and it could look good for one
person in a specific browser, but broken/ugly for everyone else. The
move to a separate search page is, in my opinion, a necessary compromise.

For anyone confused or angry about the recent changes, let me explain
the motivation. The old CSS used a fixed width, a mix of scaled and
fixed font sizes, .gif files for graphics, and these things caused it to
not render correctly for a lot of people. The search box was
frankensteined in at some point, and it never really "fit in" in a lot
of use cases. For me, it always seemed to hang off the right side.

The CSS changes are meant to fix these issues, making the site render
consistently across browsers, mobile or desktop, minimum font sizes,
zoom levels, large and small displays with low or high DPIs, etc. This
is an attempt to make things better for everyone, and I genuinely hope
people can see that.


-- 
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/20180125/6335d5fc/attachment.asc>

From skaendo at excite.com  Thu Jan 25 06:37:51 2018
From: skaendo at excite.com (Ed Ender)
Date: Thu, 25 Jan 2018 01:37:51 -0500
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
Message-ID: <20180125013751.11080@web006.roc2.bluetie.com>

I don't want to offend or tell anyone how to do what their doing, whatever you guys do the rest of us will just have to deal with. I just want to throw an idea at you, how hard would it be to do something like this: https://i.imgur.com/fzhSzvC.png

-----Original Message-----
From: "Erik Hanson" [erik at slackbuilds.org]
Date: 01/25/2018 12:12 AM
To: slackbuilds-users at slackbuilds.org
Subject: Re: [Slackbuilds-users] New layout of https://slackbuilds.org/

On 01/24/2018 07:06 PM, Fernando Lopez wrote:
> i know... but why to remove it from the search bar... now i have to do
> an extra step...

Add a search bookmark to your browser, and then you have one less step
from before. For years I've had it so I can type "sbo whatever" in the
address field and it goes straight to the search results, in Chrome,
Firefox, etc. You've been given tools to make life easier, you should
use them.

That aside, the search box caused broken layout for many people, for as
long as it existed. It's neigh-on-impossible to wedge a form element
into an existing layout, because apparently every browser has some
slightly different way of rendering things, and there's just no good way
around it. Many attempts were made, and it could look good for one
person in a specific browser, but broken/ugly for everyone else. The
move to a separate search page is, in my opinion, a necessary compromise.

For anyone confused or angry about the recent changes, let me explain
the motivation. The old CSS used a fixed width, a mix of scaled and
fixed font sizes, .gif files for graphics, and these things caused it to
not render correctly for a lot of people. The search box was
frankensteined in at some point, and it never really "fit in" in a lot
of use cases. For me, it always seemed to hang off the right side.

The CSS changes are meant to fix these issues, making the site render
consistently across browsers, mobile or desktop, minimum font sizes,
zoom levels, large and small displays with low or high DPIs, etc. This
is an attempt to make things better for everyone, and I genuinely hope
people can see that.


-- 
Erik




From fernando.lopezjr at gmail.com  Thu Jan 25 06:47:34 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Wed, 24 Jan 2018 23:47:34 -0700
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180125013751.11080@web006.roc2.bluetie.com>
References: <20180125013751.11080@web006.roc2.bluetie.com>
Message-ID: <CALrQ46D190AWF2MGhzJP-s0P1DUuB14CJEX3MJX2yD3F_+7GNg@mail.gmail.com>

i thought excite was dead.

On Wed, Jan 24, 2018 at 11:37 PM, Ed Ender <skaendo at excite.com> wrote:

> I don't want to offend or tell anyone how to do what their doing, whatever
> you guys do the rest of us will just have to deal with. I just want to
> throw an idea at you, how hard would it be to do something like this:
> https://i.imgur.com/fzhSzvC.png
>
> -----Original Message-----
> From: "Erik Hanson" [erik at slackbuilds.org]
> Date: 01/25/2018 12:12 AM
> To: slackbuilds-users at slackbuilds.org
> Subject: Re: [Slackbuilds-users] New layout of https://slackbuilds.org/
>
> On 01/24/2018 07:06 PM, Fernando Lopez wrote:
> > i know... but why to remove it from the search bar... now i have to do
> > an extra step...
>
> Add a search bookmark to your browser, and then you have one less step
> from before. For years I've had it so I can type "sbo whatever" in the
> address field and it goes straight to the search results, in Chrome,
> Firefox, etc. You've been given tools to make life easier, you should
> use them.
>
> That aside, the search box caused broken layout for many people, for as
> long as it existed. It's neigh-on-impossible to wedge a form element
> into an existing layout, because apparently every browser has some
> slightly different way of rendering things, and there's just no good way
> around it. Many attempts were made, and it could look good for one
> person in a specific browser, but broken/ugly for everyone else. The
> move to a separate search page is, in my opinion, a necessary compromise.
>
> For anyone confused or angry about the recent changes, let me explain
> the motivation. The old CSS used a fixed width, a mix of scaled and
> fixed font sizes, .gif files for graphics, and these things caused it to
> not render correctly for a lot of people. The search box was
> frankensteined in at some point, and it never really "fit in" in a lot
> of use cases. For me, it always seemed to hang off the right side.
>
> The CSS changes are meant to fix these issues, making the site render
> consistently across browsers, mobile or desktop, minimum font sizes,
> zoom levels, large and small displays with low or high DPIs, etc. This
> is an attempt to make things better for everyone, and I genuinely hope
> people can see that.
>
>
> --
> Erik
>
>
>
> _______________________________________________
> 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/20180124/42749323/attachment.html>

From rshepard at appl-ecosys.com  Thu Jan 25 13:55:01 2018
From: rshepard at appl-ecosys.com (Rich Shepard)
Date: Thu, 25 Jan 2018 05:55:01 -0800 (PST)
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <2fc5592b-0d78-30e4-e65e-b04ebfbd5aac@slackbuilds.org>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
 <20180124150940.GF26225@Blackswan>
 <CAPh+tzPzK+yU9PDn5sd2ns1Ee56f-hKCj9fELZLHiAAi53dA8Q@mail.gmail.com>
 <CALrQ46DQarsqh2jwiAAhVf8oEC4S1+u0LKqMTWWi1VkHruTerw@mail.gmail.com>
 <236a4e3f-28d8-7169-9ef9-5c7513cef9cc@slackbuilds.org>
 <CALrQ46AtKOGpxwtBuZ2TEJQZg1fA2RVS482sb2Vic1uRiWsb9Q@mail.gmail.com>
 <2fc5592b-0d78-30e4-e65e-b04ebfbd5aac@slackbuilds.org>
Message-ID: <alpine.LNX.2.20.1801250553310.26469@salmo.appl-ecosys.com>

On Thu, 25 Jan 2018, Erik Hanson wrote:

> That aside, the search box caused broken layout for many people, for as
> long as it existed. It's neigh-on-impossible to wedge a form element into
> an existing layout, because apparently every browser has some slightly
> different way of rendering things, and there's just no good way around it.
> Many attempts were made, and it could look good for one person in a
> specific browser, but broken/ugly for everyone else. The move to a
> separate search page is, in my opinion, a necessary compromise.

Erik,

   Thanks for the explanation ... and for the efforts all of you put into
making the site work universally.

Best regards,

Rich

From kingbeowulf at gmail.com  Thu Jan 25 17:39:11 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 25 Jan 2018 09:39:11 -0800
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <236a4e3f-28d8-7169-9ef9-5c7513cef9cc@slackbuilds.org>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
 <20180124150940.GF26225@Blackswan>
 <CAPh+tzPzK+yU9PDn5sd2ns1Ee56f-hKCj9fELZLHiAAi53dA8Q@mail.gmail.com>
 <CALrQ46DQarsqh2jwiAAhVf8oEC4S1+u0LKqMTWWi1VkHruTerw@mail.gmail.com>
 <236a4e3f-28d8-7169-9ef9-5c7513cef9cc@slackbuilds.org>
Message-ID: <6b6f11fd-ea32-3212-4407-99d0e705837a@gmail.com>

On 01/24/2018 05:05 PM, Willy Sudiarto Raharjo wrote:
>> where is the search
>> box!
> 
> https://slackbuilds.org/search/
> 
> 

*giggle* It took me a moment to find the search as well.  I was grumpy
about the move at 1st but got used to it as the new location works
better on iOS.


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

From kingbeowulf at gmail.com  Thu Jan 25 17:40:45 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Thu, 25 Jan 2018 09:40:45 -0800
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <2fc5592b-0d78-30e4-e65e-b04ebfbd5aac@slackbuilds.org>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
 <20180124150940.GF26225@Blackswan>
 <CAPh+tzPzK+yU9PDn5sd2ns1Ee56f-hKCj9fELZLHiAAi53dA8Q@mail.gmail.com>
 <CALrQ46DQarsqh2jwiAAhVf8oEC4S1+u0LKqMTWWi1VkHruTerw@mail.gmail.com>
 <236a4e3f-28d8-7169-9ef9-5c7513cef9cc@slackbuilds.org>
 <CALrQ46AtKOGpxwtBuZ2TEJQZg1fA2RVS482sb2Vic1uRiWsb9Q@mail.gmail.com>
 <2fc5592b-0d78-30e4-e65e-b04ebfbd5aac@slackbuilds.org>
Message-ID: <7fef2d6f-f94b-f695-7683-30103e1a5a3c@gmail.com>

On 01/24/2018 10:01 PM, Erik Hanson wrote:
> On 01/24/2018 07:06 PM, Fernando Lopez wrote:
>> i know... but why to remove it from the search bar... now i have to do
>> an extra step...
> 
> Add a search bookmark to your browser, and then you have one less step
> from before. For years I've had it so I can type "sbo whatever" in the
> address field and it goes straight to the search results, in Chrome,
> Firefox, etc. You've been given tools to make life easier, you should
> use them.
> 
> That aside, the search box caused broken layout for many people, for as
> long as it existed. It's neigh-on-impossible to wedge a form element
> into an existing layout, because apparently every browser has some
> slightly different way of rendering things, and there's just no good way
> around it. Many attempts were made, and it could look good for one
> person in a specific browser, but broken/ugly for everyone else. The
> move to a separate search page is, in my opinion, a necessary compromise.
> 
> For anyone confused or angry about the recent changes, let me explain
> the motivation. The old CSS used a fixed width, a mix of scaled and
> fixed font sizes, .gif files for graphics, and these things caused it to
> not render correctly for a lot of people. The search box was
> frankensteined in at some point, and it never really "fit in" in a lot
> of use cases. For me, it always seemed to hang off the right side.
> 
> The CSS changes are meant to fix these issues, making the site render
> consistently across browsers, mobile or desktop, minimum font sizes,
> zoom levels, large and small displays with low or high DPIs, etc. This
> is an attempt to make things better for everyone, and I genuinely hope
> people can see that.
> 
> 

+1

-Ed


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

From atelszewski at gmail.com  Thu Jan 25 18:41:50 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 25 Jan 2018 19:41:50 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <7fef2d6f-f94b-f695-7683-30103e1a5a3c@gmail.com>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
 <20180124150940.GF26225@Blackswan>
 <CAPh+tzPzK+yU9PDn5sd2ns1Ee56f-hKCj9fELZLHiAAi53dA8Q@mail.gmail.com>
 <CALrQ46DQarsqh2jwiAAhVf8oEC4S1+u0LKqMTWWi1VkHruTerw@mail.gmail.com>
 <236a4e3f-28d8-7169-9ef9-5c7513cef9cc@slackbuilds.org>
 <CALrQ46AtKOGpxwtBuZ2TEJQZg1fA2RVS482sb2Vic1uRiWsb9Q@mail.gmail.com>
 <2fc5592b-0d78-30e4-e65e-b04ebfbd5aac@slackbuilds.org>
 <7fef2d6f-f94b-f695-7683-30103e1a5a3c@gmail.com>
Message-ID: <8300c67c-46d6-157c-ccc5-09fb61020a5b@gmail.com>

Hi,

(Nitpicking evening, because I actually never look there ;-)).

I would rearrange https://slackbuilds.org/contributors/ in the following 
way:

Hosting and Hardware
text

Donations
text

Contributions toward new hardware
text

with every contributor on a separate line (i.e. in un-ordered list or 
using line breaks).

-- 
Best regards,
Andrzej Telszewski

From zhu.qunying at gmail.com  Thu Jan 25 20:03:59 2018
From: zhu.qunying at gmail.com (Qun-Ying)
Date: Thu, 25 Jan 2018 12:03:59 -0800
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180125013751.11080@web006.roc2.bluetie.com>
References: <20180125013751.11080@web006.roc2.bluetie.com>
Message-ID: <CAHiy0bTiMLCs3LV=a8JmKQMt0FU8ST54=SpCO=bV-CT2xaQRgA@mail.gmail.com>

On 1/24/18, Ed Ender <skaendo at excite.com> wrote:
> I don't want to offend or tell anyone how to do what their doing, whatever
> you guys do the rest of us will just have to deal with. I just want to throw
> an idea at you, how hard would it be to do something like this:
> https://i.imgur.com/fzhSzvC.png

+1, this is good. The search bar should always visible.
Think about google's home page, the first page should be as simple as possible.

-- 
Qun-Ying

From erik at slackbuilds.org  Thu Jan 25 20:49:29 2018
From: erik at slackbuilds.org (Erik Hanson)
Date: Thu, 25 Jan 2018 14:49:29 -0600
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <alpine.LNX.2.20.1801250553310.26469@salmo.appl-ecosys.com>
References: <20180124042207.7718@web003.roc2.bluetie.com>
 <d605fea6-8112-a7a6-7ce3-4eba26d860b2@gmail.com>
 <CAPh+tzNzCVV1Vjs9bBF_0sot-TwLTV8S-iNx73kWTWR8k5FHbQ@mail.gmail.com>
 <20180124150940.GF26225@Blackswan>
 <CAPh+tzPzK+yU9PDn5sd2ns1Ee56f-hKCj9fELZLHiAAi53dA8Q@mail.gmail.com>
 <CALrQ46DQarsqh2jwiAAhVf8oEC4S1+u0LKqMTWWi1VkHruTerw@mail.gmail.com>
 <236a4e3f-28d8-7169-9ef9-5c7513cef9cc@slackbuilds.org>
 <CALrQ46AtKOGpxwtBuZ2TEJQZg1fA2RVS482sb2Vic1uRiWsb9Q@mail.gmail.com>
 <2fc5592b-0d78-30e4-e65e-b04ebfbd5aac@slackbuilds.org>
 <alpine.LNX.2.20.1801250553310.26469@salmo.appl-ecosys.com>
Message-ID: <2a49aac2-36b0-a9d4-beca-83f395cc37d8@slackbuilds.org>

On 01/25/2018 07:55 AM, Rich Shepard wrote:
> On Thu, 25 Jan 2018, Erik Hanson wrote:
> 
>> That aside, the search box caused broken layout for many people, for as
>> long as it existed. It's neigh-on-impossible to wedge a form element into
>> an existing layout, because apparently every browser has some slightly
>> different way of rendering things, and there's just no good way around
>> it.
>> Many attempts were made, and it could look good for one person in a
>> specific browser, but broken/ugly for everyone else. The move to a
>> separate search page is, in my opinion, a necessary compromise.
> 
> Erik,
> 
> ? Thanks for the explanation ... and for the efforts all of you put into
> making the site work universally.

For what it's worth, I am not putting any effort in beyond some
suggestions, the heavy lifting is being done by David Woodfall. I am
happy to take the criticism and angry feedback people have, however.


-- 
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/20180125/cef0eb78/attachment.asc>

From skaendo at excite.com  Thu Jan 25 21:05:55 2018
From: skaendo at excite.com (Ed Ender)
Date: Thu, 25 Jan 2018 16:05:55 -0500
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
Message-ID: <20180125160555.6239@web007.roc2.bluetie.com>

That looks great to me now. I like how the search is on every page! Thanks!!!

From didier at slint.fr  Thu Jan 25 21:11:13 2018
From: didier at slint.fr (Didier Spaier)
Date: Thu, 25 Jan 2018 22:11:13 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <20180124083703.GD26225@Blackswan>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
 <20180124083703.GD26225@Blackswan>
Message-ID: <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>

Hello,

Le 24/01/2018 ? 09:37, David Woodfall a ?crit?:
> The readme info is generated from the supplied README for the
> slackbuild by reading it in php, formatting it, and then printing
> between <pre> tags.
> 
> I've had a look to see if/how the wrapping amount could be changed to
> help fill out the page width, but I'm afraid it's not really possible
> to tell if two adjacent lines should be wrapped together, or whether
> the next line should be on a newline, such as in a list for example.
> 
> Dave

I downloaded the slackbuilds-14.2-20180120.1 from git to figure out and
I agree with you, that's not as simple as I hoped it could be.

So, short of finding a volunteer to review 6918 READMEs one by one
(anyone?), I suggest that maintainers edit manually their READMEs if
they want, on the occasion of an update for instance.

Again, thanks for your work, Dave.

Greetings,

Didier

From atelszewski at gmail.com  Thu Jan 25 21:46:09 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 25 Jan 2018 22:46:09 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
 <20180124083703.GD26225@Blackswan>
 <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>
Message-ID: <d57df62a-7e37-5316-4d15-b4de4d1fba5c@gmail.com>

On 25/01/18 22:11, Didier Spaier wrote:
> So, short of finding a volunteer to review 6918 READMEs one by one
> (anyone?), I suggest that maintainers edit manually their READMEs if
> they want, on the occasion of an update for instance.

That will not happen ;-)

The READMEs are standardized:
https://slackbuilds.org/templates/README

-- 
Best regards,
Andrzej Telszewski

From didier at slint.fr  Thu Jan 25 21:59:08 2018
From: didier at slint.fr (Didier Spaier)
Date: Thu, 25 Jan 2018 22:59:08 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <d57df62a-7e37-5316-4d15-b4de4d1fba5c@gmail.com>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
 <20180124083703.GD26225@Blackswan>
 <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>
 <d57df62a-7e37-5316-4d15-b4de4d1fba5c@gmail.com>
Message-ID: <fc7df8f9-db14-272a-918c-fa2591ce9604@slint.fr>

Le 25/01/2018 ? 22:46, Andrzej Telszewski a ?crit?:
> On 25/01/18 22:11, Didier Spaier wrote:
>> So, short of finding a volunteer to review 6918 READMEs one by one
>> (anyone?), I suggest that maintainers edit manually their READMEs if
>> they want, on the occasion of an update for instance.
> 
> That will not happen ;-)
> 
> The READMEs are standardized:
> https://slackbuilds.org/templates/README


Until/unless the admins accept longer lines.

From alik at ejik.org  Thu Jan 25 22:07:18 2018
From: alik at ejik.org (Alexander Verbovetsky)
Date: Fri, 26 Jan 2018 01:07:18 +0300
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <fc7df8f9-db14-272a-918c-fa2591ce9604@slint.fr>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
 <20180124083703.GD26225@Blackswan>
 <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>
 <d57df62a-7e37-5316-4d15-b4de4d1fba5c@gmail.com>
 <fc7df8f9-db14-272a-918c-fa2591ce9604@slint.fr>
Message-ID: <1516918038.1343806.1248403224.6DB68942@webmail.messagingengine.com>

Hello,

> Until/unless the admins accept longer lines.

For my enlarged font size, lines now are perfect. And everything in the
new site is perfect. Thanks a lot!

Best regards,
Alexander

From matteo.bernardini at gmail.com  Thu Jan 25 22:08:58 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 25 Jan 2018 23:08:58 +0100
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <fc7df8f9-db14-272a-918c-fa2591ce9604@slint.fr>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
 <20180124083703.GD26225@Blackswan>
 <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>
 <d57df62a-7e37-5316-4d15-b4de4d1fba5c@gmail.com>
 <fc7df8f9-db14-272a-918c-fa2591ce9604@slint.fr>
Message-ID: <CAPsDuS5Xc1NLm6RfSGfidYRr=Nj-NcpGM1QvL3sFWubJf1_tqw@mail.gmail.com>

2018-01-25 22:59 GMT+01:00 Didier Spaier <didier at slint.fr>:
> Le 25/01/2018 ? 22:46, Andrzej Telszewski a ?crit :
>> On 25/01/18 22:11, Didier Spaier wrote:
>>> So, short of finding a volunteer to review 6918 READMEs one by one
>>> (anyone?), I suggest that maintainers edit manually their READMEs if
>>> they want, on the occasion of an update for instance.
>>
>> That will not happen ;-)
>>
>> The READMEs are standardized:
>> https://slackbuilds.org/templates/README
>
>
> Until/unless the admins accept longer lines.

as READMEs should be readable also in consoles (80x25), IMHO, they
should be fine with the present standard.

Matteo

From yalhcru at gmail.com  Thu Jan 25 22:48:24 2018
From: yalhcru at gmail.com (B Watson)
Date: Thu, 25 Jan 2018 17:48:24 -0500
Subject: [Slackbuilds-users] New layout of https://slackbuilds.org/
In-Reply-To: <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>
References: <b560f4fa-c15a-f720-5182-ee96227468ea@slint.fr>
 <d5b57ab5-fdc2-ab68-b0d1-2f6cc07cfc85@gmail.com>
 <CAKXpWBeBVkz4x+bADK6ZJ_JEJqsNKV43oeiy6cf-=QbjK6RWJg@mail.gmail.com>
 <c2d0bf85-5fb2-9efd-15cc-2fc4b05efb39@linux.com>
 <20180124083703.GD26225@Blackswan>
 <36a7a43f-3407-300a-1366-96f7918d6a37@slint.fr>
Message-ID: <CAN1hMuATYrBfk1RqM9BU1Q1EQAiNEb5ZRXDSL1AUGtuU63qmqg@mail.gmail.com>

On 1/25/18, Didier Spaier <didier at slint.fr> wrote:
>
> So, short of finding a volunteer to review 6918 READMEs one by one
> (anyone?), I suggest that maintainers edit manually their READMEs if
> they want, on the occasion of an update for instance.

Edit them how?

Getting rid of line breaks, so a paragraph is on one line, might fix the
wrapping issue on the website, but the README isn't exclusively used by
the site (if it were, we could just decree that it has to be written in
HTML instead of plain text). Extra-long lines would probably cause problems
with tools like sbopkg and sbotools.

It would also at least be annoying for anyone running SlackBuilds
manually: I usually use "cat README", and it comes out nicely
word-wrapped, with whatever list/etc formatting the author used looking
like it's supposed to look.

From willysr at slackbuilds.org  Sat Jan 27 01:11:59 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 27 Jan 2018 08:11:59 +0700
Subject: [Slackbuilds-users] Updates - 20180127.1
Message-ID: <24d5b60f-f942-e166-060b-5d7055e51f11@slackbuilds.org>

Hi

It's been another busy week with more than 100 commits

As many of you may have seen, we have slightly redesigned the SBo
web pages to accomodate mobile users and to support users using high
resolutions. It utilized the whole screen instead of just a fixed width.
Big thanks to dive (David Woodfall) for working on this alongside with
Erik and for all users who have given a constructive ideas on how to
improve the user experience and testing in different environments. The
site has been validated as XHTML 1.0 Strict and CSS level 3 + SVG
compliance.

Electrum is now bumped to 3.0.5 as promised and we also have some
updates on Graphical tool such as Blender, darktable, nomacs.

vimb is also bumped to 3.1.0 and it abandon webkit for webkit2. It's
still in transition state, so some extra functionality might not be
there yet, but basic functionality is already usable.

ardour has got a new maintainer and it has been bumped to 5.12.0. I
believe it would be a good news for Linux musicians. So does
openoffice.org which is also got a new maintainer and bumped to 4.1.5.

webkit2gtk is bumped to 2.18.6 for another round of security updates.

Have a pleasant weekend


Sat Jan 27 00:44:42 UTC 2018
academic/fet: Updated for version 5.35.1.
academic/novocraft: Updated for version 3.08.02.
academic/pysam: Updated for version 0.13.0.
academic/speedcrunch: Fixed tarball handling.
accessibility/unclutter-xfixes: Updated for version 1.3.
audio/ardour: Updated for version 5.12.0, changed maintainer.
audio/mp3gain: Updated for version 1.6.1.
desktop/dbgl: Added (a Java frontend for DOSBox).
desktop/docfetcher: Added (Java desktop search application).
desktop/kupfer: Added (a smart, quick launcher).
desktop/tint2: Updated for version 16.2.
development/SQLAlchemy: Updated for version 1.2.1.
development/beautysh: Added (A Bash beautifier).
development/d-tools: Updated for version 2.078.1
development/dmd: Updated for version 2.078.1
development/dpkg: Updated for version 1.19.0.5.
development/ioncube-loader: Updated for version 10.1.1
development/jupyter-ipywidgets: Updated for version 7.1.1.
development/jupyter_client: Updated for version 5.2.2.
development/kicad-library: Updated for v. 4.0.7, new maintainer.
development/mutagen: Updated for version 1.40.0.
development/pkgconf: Updated for version 1.4.1.
development/universal-ctags: Updated for version 66c7915
games/ZEsarUX: Added (Machines Emulator).
games/adl: Updated for version 20110628.
games/chessx: Added an icon and a desktop file.
games/gemrb: Updated for version 0.8.5 + new maintainer.
games/libretro-ppsspp: Updated for version 2018.01.23_af33ca2.
games/steem: Add 64-bit support.
games/z26: Add 64-bit support.
games/zsnes: Partial 64-bit support.
gis/Shapely: Updated for version 1.6.4.
gis/mapnik: Updated for version 3.0.18.
graphics/Blender: Support latest openimageio (1.8.7)
graphics/GraphicsMagick: Updated for version 1.3.28.
graphics/PureRef: Added (Organize Image).
graphics/darktable: Updated for version 2.4.1.
graphics/nomacs: Updated for version 3.8.0.
graphics/openimageio: Updated for version 1.8.7
graphics/vuescan: Updated for version 9.6.05.
libraries/appstream-glib: Updated for version 0.7.5.
libraries/aubio: Updated for version 0.4.6, changed maintainer.
libraries/liblo: Updated for version 0.29, changed maintainer.
libraries/liblrdf: Updated for version 0.6.1, changed maintainer.
libraries/libseccomp: Updated for version 2.3.3.
libraries/libuv: Updated for version 1.19.1.
libraries/libversion: Updated for version 2.4.0.
libraries/libvirt-python: Updated for version 4.0.0.
libraries/libvirt: Updated for version 4.0.0.
libraries/live555: Updated for version 2018.01.24
libraries/med: Added (Data Modelization and Exchanges).
libraries/webkit2gtk: Updated for version 2.18.6.
misc/tal: New maintainer.
multimedia/MediathekView: Updated for version 13.0.6.
multimedia/obs-studio: Updated for version 21.0.2
multimedia/opera-developer-ffmpeg-codecs: Updated for version 65.0.
multimedia/spotify: Updated for version 1.0.70.
network/Electrum: Updated for version 3.0.5.
network/brave: Updated for version 0.19.139.
network/claws-mail: Updated for version 3.16.0.
network/etherape: Updated for version 0.9.16.
network/lighttpd: Updated for version 1.4.48.
network/opera-developer: Updated for version 52.0.2845.0.
network/opera: Updated for version 50.0.2762.67.
network/prosody-mod-cloud-notify: Added (Push Notification).
network/prosody-mod-csi: Added (Client State Indication).
network/prosody-mod-filter-chatstates: Added (Prosody modules).
network/prosody-mod-http-upload: Added (lient HTTP File Upload).
network/prosody-mod-mam-muc: Added (Message Archive Management).
network/prosody-mod-smacks-offline: Added (Stream Management).
network/prosody-mod-smacks: Added (Stream Management).
network/prosody-mod-throttle-presence: Added (Prosody modules).
network/slimjet: Updated for version 17.0.7.0.
network/teamviewer: Remove redundant desktop file.
network/tor-browser: Updated for version 7.5.
network/vimb: Updated for version 3.1.0.
network/waterfox: Only support x86_64.
network/xtables-addons: Updated for version 2.14.
office/MasterPDFEditor: Updated for versoin 4.3.80.
office/openoffice-langpack: Updated for version 4.1.5.
office/openoffice.org: Updated for version 4.1.5 + new maintainer.
office/qpdfview-qt5: Added (tabbed document viewer).
office/qpdfview: Switch to i586.
perl/perl-Gtk2-Unique: Switch to i586.
perl/perl-IO-Socket-SSL: Updated for version 2.054.
perl/perl-Math-MPC: Updated for version 1.08.
perl/perl-Proc-Simple: Update email address.
python/python3-jupyter_client: Updated for version 5.2.2.
python/python3-pyzmq: Updated for version 16.0.4
python/pyzmq: Updated for version 16.0.4.
python/requests-futures: Updated for version 0.9.7.
ruby/ruby-faraday: Updated for version 0.14.0.
system/CNS11643-font: Updated for version 20180105.
system/alacritty: Updated for version git59b561b.
system/clamav: Updated for version 0.99.3.
system/conky: Updated for version 1.10.7.
system/early-ssh: Added (SSH server during boot).
system/fwupd: Updated for version 1.0.4.
system/lynis: Updated for version 2.6.0.
system/passwordsafe: Updated for version 1.04BETA.
system/slackroll: Updated for version v47.
system/spl-solaris: Fixed VERSION + fix for exported ARCH.
system/statifier: Allow 64-bit build.
system/vtcol: Updated README.
system/zfs-on-linux: Fixed VERSION + fix for exported ARCH.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- 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/20180127/5f752061/attachment.asc>

From roy.lanek at yandex.com  Sat Jan 27 07:19:15 2018
From: roy.lanek at yandex.com (Roy Lanek)
Date: Sat, 27 Jan 2018 14:19:15 +0700
Subject: [Slackbuilds-users] conky-1.10.7 breaks i3's conkybar
Message-ID: <20180127071915.GA26526@sirih.local.host>

conky-1.10.7 compiles and builds fine on slackware64-curr
up-to-date; conky runs perfectly, a pity that conkybar for i3
[v4.14.1 = last] crashes. Reverting to conky-1.10.6.

Cheers,

/Roy Lanek
-- 
555555555555555555555555555555555   berat sama dipikul, ringan sama dijinjing
55555 . 5 l 4 c K W 4 r 3  555555       heavy we shoulder together, light
55555 +------------ L1NuX  555555            we hand-carry together
555555555555555555555555555555555

From fernando.lopezjr at gmail.com  Sat Jan 27 07:39:01 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sat, 27 Jan 2018 00:39:01 -0700
Subject: [Slackbuilds-users] conky-1.10.7 breaks i3's conkybar
In-Reply-To: <20180127071915.GA26526@sirih.local.host>
References: <20180127071915.GA26526@sirih.local.host>
Message-ID: <CALrQ46BnqDmHV9q2yYTxUvNqafQH__2SqyaRosh2-UUVazXu8w@mail.gmail.com>

hmm they are going to tell you that current is not supported.... pff...
bah...

On Sat, Jan 27, 2018 at 12:19 AM, Roy Lanek <roy.lanek at yandex.com> wrote:

> conky-1.10.7 compiles and builds fine on slackware64-curr
> up-to-date; conky runs perfectly, a pity that conkybar for i3
> [v4.14.1 = last] crashes. Reverting to conky-1.10.6.
>
> Cheers,
>
> /Roy Lanek
> --
> 555555555555555555555555555555555   berat sama dipikul, ringan sama
> dijinjing
> 55555 . 5 l 4 c K W 4 r 3  555555       heavy we shoulder together, light
> 55555 +------------ L1NuX  555555            we hand-carry together
> 555555555555555555555555555555555
> _______________________________________________
> 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/20180127/1cedf1d6/attachment.html>

From matteo.bernardini at gmail.com  Sat Jan 27 08:03:02 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 27 Jan 2018 09:03:02 +0100
Subject: [Slackbuilds-users] conky-1.10.7 breaks i3's conkybar
In-Reply-To: <20180127071915.GA26526@sirih.local.host>
References: <20180127071915.GA26526@sirih.local.host>
Message-ID: <CAPsDuS5Z6e6bj9e8-UiuvMGbY3Lk96iBTZRLfUrm5u67E=ONhQ@mail.gmail.com>

2018-01-27 8:19 GMT+01:00 Roy Lanek <roy.lanek at yandex.com>:
> conky-1.10.7 compiles and builds fine on slackware64-curr
> up-to-date; conky runs perfectly, a pity that conkybar for i3
> [v4.14.1 = last] crashes. Reverting to conky-1.10.6.

sorry, what is "conkybar for i3"?

Matteo

From roy.lanek at yandex.com  Sat Jan 27 08:27:29 2018
From: roy.lanek at yandex.com (Roy Lanek)
Date: Sat, 27 Jan 2018 15:27:29 +0700
Subject: [Slackbuilds-users] conky-1.10.7 breaks i3's conkybar
In-Reply-To: <CAPsDuS5Z6e6bj9e8-UiuvMGbY3Lk96iBTZRLfUrm5u67E=ONhQ@mail.gmail.com>
References: <20180127071915.GA26526@sirih.local.host>
 <CAPsDuS5Z6e6bj9e8-UiuvMGbY3Lk96iBTZRLfUrm5u67E=ONhQ@mail.gmail.com>
Message-ID: <20180127082729.GA18319@sirih.local.host>

> what is "conkybar for i3"?

Using conky with i3bar
https://i3wm.org/docs/user-contributed/conky-i3bar.html

/Roy
-- 
555555555555555555555555555555555   tak ada rotan, akar pun jadi
55555 . 5 l 4 c K W 4 r 3  555555   no rattans, roots will do [if you are
55555 +------------ L1NuX  555555   desperate, you must not be choosy]
555555555555555555555555555555555

From fernando.lopezjr at gmail.com  Sat Jan 27 08:30:28 2018
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sat, 27 Jan 2018 01:30:28 -0700
Subject: [Slackbuilds-users] conky-1.10.7 breaks i3's conkybar
In-Reply-To: <20180127082729.GA18319@sirih.local.host>
References: <20180127071915.GA26526@sirih.local.host>
 <CAPsDuS5Z6e6bj9e8-UiuvMGbY3Lk96iBTZRLfUrm5u67E=ONhQ@mail.gmail.com>
 <20180127082729.GA18319@sirih.local.host>
Message-ID: <CALrQ46BeQDqfgK_boooAHbSm3YmUSbDxE9S0259z+AhQ=e1cwQ@mail.gmail.com>

i3 is DE

screenshot of conkybar

On Jan 27, 2018 1:27 AM, "Roy Lanek" <roy.lanek at yandex.com> wrote:

> > what is "conkybar for i3"?
>
> Using conky with i3bar
> https://i3wm.org/docs/user-contributed/conky-i3bar.html
>
> /Roy
> --
> 555555555555555555555555555555555   tak ada rotan, akar pun jadi
> 55555 . 5 l 4 c K W 4 r 3  555555   no rattans, roots will do [if you are
> 55555 +------------ L1NuX  555555   desperate, you must not be choosy]
> 555555555555555555555555555555555
> _______________________________________________
> 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/20180127/953e797c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: conkybar___conky_config__conky_1_10__by_n00by4ever-d6mw9x3.jpg
Type: image/jpeg
Size: 130447 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180127/953e797c/attachment-0001.jpg>

From matteo.bernardini at gmail.com  Sat Jan 27 08:37:07 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 27 Jan 2018 09:37:07 +0100
Subject: [Slackbuilds-users] conky-1.10.7 breaks i3's conkybar
In-Reply-To: <20180127082729.GA18319@sirih.local.host>
References: <20180127071915.GA26526@sirih.local.host>
 <CAPsDuS5Z6e6bj9e8-UiuvMGbY3Lk96iBTZRLfUrm5u67E=ONhQ@mail.gmail.com>
 <20180127082729.GA18319@sirih.local.host>
Message-ID: <CAPsDuS6w3zFt0tTTgdZWeXGjMHnkg+3Qv7HSdfbSyY_qh-eMOQ@mail.gmail.com>

2018-01-27 9:27 GMT+01:00 Roy Lanek <roy.lanek at yandex.com>:
>> what is "conkybar for i3"?
>
> Using conky with i3bar
> https://i3wm.org/docs/user-contributed/conky-i3bar.html

IMHO, you should show your configuration file to the conky people
asking them for any changes in the output with the new version.

Matteo

From roy.lanek at yandex.com  Sat Jan 27 09:07:20 2018
From: roy.lanek at yandex.com (Roy Lanek)
Date: Sat, 27 Jan 2018 16:07:20 +0700
Subject: [Slackbuilds-users] conky-1.10.7 breaks i3's conkybar
In-Reply-To: <CAPsDuS6w3zFt0tTTgdZWeXGjMHnkg+3Qv7HSdfbSyY_qh-eMOQ@mail.gmail.com>
References: <20180127071915.GA26526@sirih.local.host>
 <CAPsDuS5Z6e6bj9e8-UiuvMGbY3Lk96iBTZRLfUrm5u67E=ONhQ@mail.gmail.com>
 <20180127082729.GA18319@sirih.local.host>
 <CAPsDuS6w3zFt0tTTgdZWeXGjMHnkg+3Qv7HSdfbSyY_qh-eMOQ@mail.gmail.com>
Message-ID: <20180127090719.GA14767@sirih.local.host>

> IMHO, you should show your configuration file to the conky people
> asking them for any changes in the output with the new version.

Could also do that, but it worked till now, i.e. since years
inclusive the to lua formatting which is now 01+ years old if I
am not mistaken. What did differentially change WITHIN conky with
the last upgrade?

It would bring you zero, in fact, as an aside, I have quickly
tried already [will have more time later, now not so much] with a
trivially *empty* configuration, thinking to then incrementally
add entries to the file, but no changes, even an *empty* config
is rejected => conky's problem 99%.

/Roy
-- 
555555555555555555555555555555555   keluar mulut harimau, masuk mulut
55555 . 5 l 4 c K W 4 r 3  555555   buaya--out from the tiger's mouth,
55555 +------------ L1NuX  555555   into the crocodile's mouth
555555555555555555555555555555555

From matteo.bernardini at gmail.com  Sat Jan 27 09:14:07 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 27 Jan 2018 10:14:07 +0100
Subject: [Slackbuilds-users] conky-1.10.7 breaks i3's conkybar
In-Reply-To: <20180127090719.GA14767@sirih.local.host>
References: <20180127071915.GA26526@sirih.local.host>
 <CAPsDuS5Z6e6bj9e8-UiuvMGbY3Lk96iBTZRLfUrm5u67E=ONhQ@mail.gmail.com>
 <20180127082729.GA18319@sirih.local.host>
 <CAPsDuS6w3zFt0tTTgdZWeXGjMHnkg+3Qv7HSdfbSyY_qh-eMOQ@mail.gmail.com>
 <20180127090719.GA14767@sirih.local.host>
Message-ID: <CAPsDuS5qvD3Urjv8QXARKtTHRDhc-h=zYYp0NX8R42BtEtn6NQ@mail.gmail.com>

2018-01-27 10:07 GMT+01:00 Roy Lanek <roy.lanek at yandex.com>:
>> IMHO, you should show your configuration file to the conky people
>> asking them for any changes in the output with the new version.
>
> Could also do that, but it worked till now, i.e. since years
> inclusive the to lua formatting which is now 01+ years old if I
> am not mistaken. What did differentially change WITHIN conky with
> the last upgrade?
>
> It would bring you zero, in fact, as an aside, I have quickly
> tried already [will have more time later, now not so much] with a
> trivially *empty* configuration, thinking to then incrementally
> add entries to the file, but no changes, even an *empty* config
> is rejected => conky's problem 99%.

a reason more to ask the conky people, isn't it?
I think they are the most qualified to solve this.

Matteo

From roy.lanek at yandex.com  Sat Jan 27 10:00:23 2018
From: roy.lanek at yandex.com (Roy Lanek)
Date: Sat, 27 Jan 2018 17:00:23 +0700
Subject: [Slackbuilds-users] conky-1.10.7 breaks i3's conkybar
In-Reply-To: <CAPsDuS5qvD3Urjv8QXARKtTHRDhc-h=zYYp0NX8R42BtEtn6NQ@mail.gmail.com>
References: <20180127071915.GA26526@sirih.local.host>
 <CAPsDuS5Z6e6bj9e8-UiuvMGbY3Lk96iBTZRLfUrm5u67E=ONhQ@mail.gmail.com>
 <20180127082729.GA18319@sirih.local.host>
 <CAPsDuS6w3zFt0tTTgdZWeXGjMHnkg+3Qv7HSdfbSyY_qh-eMOQ@mail.gmail.com>
 <20180127090719.GA14767@sirih.local.host>
 <CAPsDuS5qvD3Urjv8QXARKtTHRDhc-h=zYYp0NX8R42BtEtn6NQ@mail.gmail.com>
Message-ID: <20180127100023.GA25803@sirih.local.host>

> a reason more to ask the conky people, isn't it?
> I think they are the most qualified to solve this.

Will take a look this night, maybe, time permitting. Have quickly
seen some 20 source files have changed. Must be something banal,
maybe even just make dependent. Can live with the previous
version till problem fixed anyway.

Thank you very much, you guys rock.

/Roy
-- 
555555555555555555555555555555555   sudah jatuh, tertimpa tangga pula--a
55555 . 5 l 4 c K W 4 r 3  555555   person slips, and a ladder falls on him
55555 +------------ L1NuX  555555   [all the bad things seems to happen at
555555555555555555555555555555555   the same time]

From n0nb at n0nb.us  Sat Jan 27 13:25:35 2018
From: n0nb at n0nb.us (Nate Bargmann)
Date: Sat, 27 Jan 2018 07:25:35 -0600
Subject: [Slackbuilds-users] 'AC_CHECK_LIB([readline]' fails on 14.2
Message-ID: <20180127132535.GN3615@n0nb.us>

Just to be clear, I am working with Slackware 14.2 32 bit.

I am working on putting together a SlackBuild script for lxi-tools 1.16
(BTW, the script works perfectly on Current).  The problem isn't in the
script but rather in the 'configure' script.  Here is how the package
searches for libreadline in configure.ac:

AC_CHECK_LIB([readline], [readline], [], [AC_MSG_ERROR(libreadline not
found)])


And the failure when running 'configure':

checking whether the gcc linker (/usr/i586-slackware-linux/bin/ld)
supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for readline in -lreadline... no
configure: error: libreadline not found


Here is what is recorded in 'config.log':

configure:12811: checking for readline in -lreadline
configure:12836: gcc -o conftest -g -O2   conftest.c -lreadline   >&5
/usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so: undefined reference to `tputs'
/usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so: undefined reference to `tgoto'
/usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so: undefined reference to `tgetflag'
/usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so: undefined reference to `UP'
/usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so: undefined reference to `tgetent'
/usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so: undefined reference to `tgetnum'
/usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so: undefined reference to `PC'
/usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so: undefined reference to `tgetstr'
/usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so: undefined reference to `BC'
collect2: error: ld returned 1 exit status
configure:12836: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "lxi-tools"
| #define PACKAGE_TARNAME "lxi-tools"
| #define PACKAGE_VERSION "1.16"
| #define PACKAGE_STRING "lxi-tools 1.16"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL "https://lxi-tools.github.io"
| #define PACKAGE "lxi-tools"
| #define VERSION "1.16"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR ".libs/"
| /* end confdefs.h.  */
|
| /* Override any GCC internal prototype to avoid an error.
|    Use char because int might match the return type of a GCC
|    builtin and then its argument prototype would still apply.  */
| #ifdef __cplusplus
| extern "C"
| #endif
| char readline ();
| int
| main ()
| {
| return readline ();
|   ;
|   return 0;
| }
configure:12845: result: no
configure:12855: error: libreadline not found


The /usr/lib/libreadline.so symbolic link points to
/usr/lib/libreadline.so.6 which itself is a symlink to
/usr/lib/libreadline.so.6.3.  

Using 'readelf', I can confirm what is in 'config.log':

    83: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tputs
   144: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tgoto
   248: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tgetflag
   268: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND UP
   274: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tgetent
   307: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tgetnum
   547: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND PC
   618: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tgetstr
   750: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND BC

It doesn't look like libreadline has a missing dependent library:

$ ldd /usr/lib/libreadline.so
  linux-gate.so.1 (0xb77a2000)
  libc.so.6 => /lib/libc.so.6 (0xb759b000)
  /lib/ld-linux.so.2 (0xb77a3000)


What puzzles me is that this package built cleanly on an up-to-date
Current 64 system, but fails here.  I don't see a remarkable difference
between the symbol tables, so I at a loss.  Hopefully someone has met
this before and can provide some clues.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180127/c7ff3106/attachment.asc>

From ml at mareichelt.com  Sat Jan 27 13:36:22 2018
From: ml at mareichelt.com (Markus Reichelt)
Date: Sat, 27 Jan 2018 14:36:22 +0100
Subject: [Slackbuilds-users] 'AC_CHECK_LIB([readline]' fails on 14.2
In-Reply-To: <20180127132535.GN3615@n0nb.us>
References: <20180127132535.GN3615@n0nb.us>
Message-ID: <20180127133622.GA4432@pc21.mareichelt.com>

* Nate Bargmann <n0nb at n0nb.us> wrote:

> I am working on putting together a SlackBuild script for lxi-tools
> 1.16 (BTW, the script works perfectly on Current).  The problem
> isn't in the script but rather in the 'configure' script.  Here is
> how the package searches for libreadline in configure.ac:

FWIW, when I tried on -current to recompile a patched
util-linux-2.31.1, I had to add the following to the buildscript
right before the invocation of ./configure 

autoreconf -f -i

HTH

-- 
Tahoe-LAFS for the masses.
-------------- 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/20180127/98d12762/attachment.asc>

From n0nb at n0nb.us  Sat Jan 27 14:46:04 2018
From: n0nb at n0nb.us (Nate Bargmann)
Date: Sat, 27 Jan 2018 08:46:04 -0600
Subject: [Slackbuilds-users] 'AC_CHECK_LIB([readline]' fails on 14.2
In-Reply-To: <20180127133622.GA4432@pc21.mareichelt.com>
References: <20180127132535.GN3615@n0nb.us>
 <20180127133622.GA4432@pc21.mareichelt.com>
Message-ID: <20180127144604.GO3615@n0nb.us>

* On 2018 27 Jan 07:37 -0600, Markus Reichelt wrote:

> FWIW, when I tried on -current to recompile a patched
> util-linux-2.31.1, I had to add the following to the buildscript
> right before the invocation of ./configure 
> 
> autoreconf -f -i
> 
> HTH

Sorry, made no difference even though 'configure' and other files were
rebuilt from the source distribution versions.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180127/de2626c6/attachment-0001.asc>

From roy.lanek at yandex.com  Sat Jan 27 15:08:17 2018
From: roy.lanek at yandex.com (Roy Lanek)
Date: Sat, 27 Jan 2018 22:08:17 +0700
Subject: [Slackbuilds-users] conky-1.10.7 breaks i3's conkybar
In-Reply-To: <20180127100023.GA25803@sirih.local.host>
References: <20180127071915.GA26526@sirih.local.host>
 <CAPsDuS5Z6e6bj9e8-UiuvMGbY3Lk96iBTZRLfUrm5u67E=ONhQ@mail.gmail.com>
 <20180127082729.GA18319@sirih.local.host>
 <CAPsDuS6w3zFt0tTTgdZWeXGjMHnkg+3Qv7HSdfbSyY_qh-eMOQ@mail.gmail.com>
 <20180127090719.GA14767@sirih.local.host>
 <CAPsDuS5qvD3Urjv8QXARKtTHRDhc-h=zYYp0NX8R42BtEtn6NQ@mail.gmail.com>
 <20180127100023.GA25803@sirih.local.host>
Message-ID: <20180127150817.GA9386@sirih.local.host>

> Will take a look this night, maybe, time permitting. Have quickly
> seen some 20 source files have changed. Must be something banal,
> maybe even just make dependent.

It's not some conflict of dependencies either, have recompiled
from zero the PREVIOUS conky--and it works--it's really that last
version which doesn't. Okay, so that's it, looking into the
source.

/Roy
-- 
555555555555555555555555555555555       tak ada gading yang tak retak
55555 . 5 l 4 c K W 4 r 3  555555   there are no ivory that is not cracked
55555 +------------ L1NuX  555555     [nothing is perfect in this world]
555555555555555555555555555555555

From roy.lanek at yandex.com  Sat Jan 27 16:02:16 2018
From: roy.lanek at yandex.com (Roy Lanek)
Date: Sat, 27 Jan 2018 23:02:16 +0700
Subject: [Slackbuilds-users] conky-1.10.7 breaks i3's conkybar [SOLVED]
In-Reply-To: <20180127150817.GA9386@sirih.local.host>
References: <20180127071915.GA26526@sirih.local.host>
 <CAPsDuS5Z6e6bj9e8-UiuvMGbY3Lk96iBTZRLfUrm5u67E=ONhQ@mail.gmail.com>
 <20180127082729.GA18319@sirih.local.host>
 <CAPsDuS6w3zFt0tTTgdZWeXGjMHnkg+3Qv7HSdfbSyY_qh-eMOQ@mail.gmail.com>
 <20180127090719.GA14767@sirih.local.host>
 <CAPsDuS5qvD3Urjv8QXARKtTHRDhc-h=zYYp0NX8R42BtEtn6NQ@mail.gmail.com>
 <20180127100023.GA25803@sirih.local.host>
 <20180127150817.GA9386@sirih.local.host>
Message-ID: <20180127160216.GA24779@sirih.local.host>

> Okay, so that's it, looking into the source.

SOLVED, was something banal indeed:

replaced conky-1.10.7/cmake/ConkyBuildOptions.cmake with
conky-1.10.6/cmake/ConkyBuildOptions.cmake

/Roy
-- 
555555555555555555555555555555555   kacang lupa kulitnya--a nut forgets
55555 . 5 l 4 c K W 4 r 3  555555   its shell [illustrates who forgets
55555 +------------ L1NuX  555555   where he comes from]
555555555555555555555555555555555

From n0nb at n0nb.us  Sat Jan 27 19:40:00 2018
From: n0nb at n0nb.us (Nate Bargmann)
Date: Sat, 27 Jan 2018 13:40:00 -0600
Subject: [Slackbuilds-users] 'AC_CHECK_LIB([readline]' fails on 14.2
In-Reply-To: <20180127132535.GN3615@n0nb.us>
References: <20180127132535.GN3615@n0nb.us>
Message-ID: <20180127194000.GQ3615@n0nb.us>

I've now tried the package in the Slackware64 14.2 VM after all updates
and am getting the same failure as with Slackware 14.2.

Going to have to give this a rest for a while, I guess.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180127/3d73e033/attachment.asc>

From mickski56 at hotmail.com  Sat Jan 27 20:07:47 2018
From: mickski56 at hotmail.com (mickski 56)
Date: Sat, 27 Jan 2018 20:07:47 +0000
Subject: [Slackbuilds-users] 'AC_CHECK_LIB([readline]' fails on 14.2
In-Reply-To: <20180127132535.GN3615@n0nb.us>
References: <20180127132535.GN3615@n0nb.us>
Message-ID: <AM4PR07MB3074EAC74F662AA42A3490BFB1E70@AM4PR07MB3074.eurprd07.prod.outlook.com>

>Just to be clear, I am working with Slackware 14.2 32 bit.
>
>I am working on putting together a SlackBuild script for lxi-tools 1.16
>(BTW, the script works perfectly on Current).  The problem isn't in the
>script but rather in the 'configure' script.  Here is how the package
>searches for libreadline in configure.ac:
>
>AC_CHECK_LIB([readline], [readline], [], [AC_MSG_ERROR(libreadline not
>found)])
>
>
>And the failure when running 'configure':
>
>checking whether the gcc linker (/usr/i586-slackware-linux/bin/ld)
>supports shared libraries... yes
>checking whether -lc should be explicitly linked in... no
>checking dynamic linker characteristics... GNU/Linux ld.so
>checking how to hardcode library paths into programs... immediate
>checking whether stripping libraries is possible... yes
>checking if libtool supports shared libraries... yes
>checking whether to build shared libraries... yes
>checking whether to build static libraries... yes
>checking for readline in -lreadline... no
>configure: error: libreadline not found
>
>
>Here is what is recorded in 'config.log':
>
>configure:12811: checking for readline in -lreadline
>configure:12836: gcc -o conftest -g -O2   conftest.c -lreadline   >&5
>/usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so:
>undefined reference to
>`tputs' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so:
>undefined reference to
>`tgoto' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so:
>undefined reference to
>`tgetflag' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so:
>undefined reference to
>`UP' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so:
>undefined reference to
>`tgetent' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so:
>undefined reference to
>`tgetnum' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so:
>undefined reference to
>`PC' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so:
>undefined reference to
>`tgetstr' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so:
>undefined reference to `BC' collect2: error: ld returned 1 exit status
>configure:12836: $? = 1 configure: failed program was: | /* confdefs.h
>*/ | #define PACKAGE_NAME "lxi-tools" | #define PACKAGE_TARNAME
>"lxi-tools" | #define PACKAGE_VERSION "1.16" | #define PACKAGE_STRING
>"lxi-tools 1.16" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL
>"https://lxi-tools.github.io" | #define PACKAGE "lxi-tools" | #define
>VERSION "1.16" | #define STDC_HEADERS 1 | #define HAVE_SYS_TYPES_H 1 |
>#define HAVE_SYS_STAT_H 1 | #define HAVE_STDLIB_H 1
>| #define HAVE_STRING_H 1
>| #define HAVE_MEMORY_H 1
>| #define HAVE_STRINGS_H 1
>| #define HAVE_INTTYPES_H 1
>| #define HAVE_STDINT_H 1
>| #define HAVE_UNISTD_H 1
>| #define HAVE_DLFCN_H 1
>| #define LT_OBJDIR ".libs/"
>| /* end confdefs.h.  */
>|
>| /* Override any GCC internal prototype to avoid an error.
>|    Use char because int might match the return type of a GCC
>|    builtin and then its argument prototype would still apply.  */
>| #ifdef __cplusplus
>| extern "C"
>| #endif
>| char readline ();
>| int
>| main ()
>| {
>| return readline ();
>|   ;
>|   return 0;
>| }
>configure:12845: result: no
>configure:12855: error: libreadline not found
>
>
>The /usr/lib/libreadline.so symbolic link points to
>/usr/lib/libreadline.so.6 which itself is a symlink to
>/usr/lib/libreadline.so.6.3.  
>
>Using 'readelf', I can confirm what is in 'config.log':
>
>    83: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tputs
>   144: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tgoto
>   248: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tgetflag
>   268: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND UP
>   274: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tgetent
>   307: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tgetnum
>   547: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND PC
>   618: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND tgetstr
>   750: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND BC
>
>It doesn't look like libreadline has a missing dependent library:
>
>$ ldd /usr/lib/libreadline.so
>  linux-gate.so.1 (0xb77a2000)
>  libc.so.6 => /lib/libc.so.6 (0xb759b000)
>  /lib/ld-linux.so.2 (0xb77a3000)
>
>
>What puzzles me is that this package built cleanly on an up-to-date
>Current 64 system, but fails here.  I don't see a remarkable difference
>between the symbol tables, so I at a loss.  Hopefully someone has met
>this before and can provide some clues.
>
>- Nate
>
>-- 
>
>"The optimist proclaims that we live in the best of all
>possible worlds.  The pessimist fears this is true."
>
>Ham radio, Linux, bikes, and more: http://www.n0nb.us

If I recall correctly it's necessary to also link in ncurses "-lncurses"
Probably I'd use LDFLAGS="-lncurses" ./configure ........

From yalhcru at gmail.com  Sat Jan 27 20:09:08 2018
From: yalhcru at gmail.com (B Watson)
Date: Sat, 27 Jan 2018 15:09:08 -0500
Subject: [Slackbuilds-users] 'AC_CHECK_LIB([readline]' fails on 14.2
In-Reply-To: <20180127132535.GN3615@n0nb.us>
References: <20180127132535.GN3615@n0nb.us>
Message-ID: <CAN1hMuCmxq4aT3t+eMNhP69aMgWJrp4AtPU8W9QpokZ57H5KkA@mail.gmail.com>

On 1/27/18, Nate Bargmann <n0nb at n0nb.us> wrote:
> checking for readline in -lreadline... no
> configure: error: libreadline not found
>
>
> Here is what is recorded in 'config.log':
>
> configure:12811: checking for readline in -lreadline
> configure:12836: gcc -o conftest -g -O2   conftest.c -lreadline   >&5
> /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so: undefined
> reference to `tputs'
> /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libreadline.so: undefined
> reference to `tgoto'
> <....>

These symbols are defined in libncurses. Normally when anything links
with readline, it also links with ncurses... you could probably have
figured this out yourself, by reading the man page for tputs (it tells
you it's part of curses anyway, which would have been a strong hint).

(I just re-read what I wrote above, and it sounds kinda smarmy... it
isn't meant that way, it's supposed to be helpful & educational. I hate
just giving an answer, would rather give the reasoning behind it.)

You can fix the problem in lxi-tools by adding LIBS="-lncurses" to the
configure command. With standard SBo template, it would look like:

LIBS="-lncurses"
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
  --prefix=/usr \
  <...other options here...>

When I run configure this way, I still can't build lxi-tools since I
don't have the lxi library it depends on, but I do get:

<...>
checking for readline in -lreadline... yes
checking for lxi_connect in -llxi... no
configure: error: liblxi not found

...so it'll probably build fine if liblxi is installed.

Interestingly, this isn't just a problem for lxi-tools. Anything that
tries to link with -lreadline but not -lncurses will fail in the same
way on 14.2:

$ cat hello.c
#include <stdio.h>

int main(int argc, char **argv) {
	printf("hello world\n");
	return 0;
}
$ gcc -lreadline -ohello hello.c
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libreadline.so:
undefined reference to `tputs'
/usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libreadline.so:
undefined reference to `tgoto'
<...>
$ gcc -lreadline -lncurses -ohello hello.c
$ ./hello
hello world

If you look at libreadline:

$ ldd /usr/lib64/libreadline.so
	linux-vdso.so.1 (0x00007ffdb9fc3000)
	libc.so.6 => /lib64/libc.so.6 (0x00002b79a2820000)
	/lib64/ld-linux-x86-64.so.2 (0x000055581e85b000)

...libncurses isn't a hard dependency (though I suspect it should be).

On -current, libncurses has been split in two (libncurses and libtinfo), and
readline is linked with libtinfo:

# ldd /usr/lib/libreadline.so
	linux-gate.so.1 (0xb7fa9000)
	libtinfo.so.6 => /usr/lib/libtinfo.so.6 (0xb7f3b000)
	libc.so.6 => /lib/libc.so.6 (0xb7d4c000)
	/lib/ld-linux.so.2 (0xb7fab000)

...and using -lreadline without -lncurses (or -ltinfo) works fine:

# gcc -lreadline -ohello hello.c
# ./hello
hello world
# ldd ./hello
	linux-gate.so.1 (0xb7f2a000)
	libreadline.so.7 => /usr/lib/libreadline.so.7 (0xb7ea8000)
	libc.so.6 => /lib/libc.so.6 (0xb7cf1000)
	libtinfo.so.6 => /usr/lib/libtinfo.so.6 (0xb7ccd000)
	/lib/ld-linux.so.2 (0xb7f2c000)

Clear as mud, yes?

From kingbeowulf at gmail.com  Sun Jan 28 00:17:13 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 27 Jan 2018 16:17:13 -0800
Subject: [Slackbuilds-users] ANNOUNCE: Qemu SBo script follows even branch
 stable releases
Message-ID: <bf003c9b-c4d0-1e55-d93f-efdc20500b60@gmail.com>

FYI:
I'm following the qemu even number stable release schedule. Trying to
keep up with interleaved odd and even branches is nuts.  I also can't
find any information of why qemu devs do this, since all development in
in git master not a "dev branch". If anyone knows why qemu does this,
please let me know.

As of now, qemu-2.10.2 is newest and prefers SDL2 and GTK3 if available
at build time.  The qemu.slackbuild should build both versions
succesfully.  If not, then use 2.10.2!

Both 2.10.2 ad 2.11.0 have the same basic feature set with differences
outlined in the respective change./release logs.

-Ed



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

From n0nb at n0nb.us  Sun Jan 28 00:47:05 2018
From: n0nb at n0nb.us (Nate Bargmann)
Date: Sat, 27 Jan 2018 18:47:05 -0600
Subject: [Slackbuilds-users] 'AC_CHECK_LIB([readline]' fails on 14.2
In-Reply-To: <CAN1hMuCmxq4aT3t+eMNhP69aMgWJrp4AtPU8W9QpokZ57H5KkA@mail.gmail.com>
References: <20180127132535.GN3615@n0nb.us>
 <CAN1hMuCmxq4aT3t+eMNhP69aMgWJrp4AtPU8W9QpokZ57H5KkA@mail.gmail.com>
Message-ID: <20180128004705.GS3615@n0nb.us>

* On 2018 27 Jan 14:10 -0600, B Watson wrote:

> These symbols are defined in libncurses. Normally when anything links
> with readline, it also links with ncurses... you could probably have
> figured this out yourself, by reading the man page for tputs (it tells
> you it's part of curses anyway, which would have been a strong hint).
> 
> (I just re-read what I wrote above, and it sounds kinda smarmy... it
> isn't meant that way, it's supposed to be helpful & educational. I hate
> just giving an answer, would rather give the reasoning behind it.)

Not a problem.  :-)

I've had more experience in the Debian world, and I recognized that
tputs probably had to do with terminfo but since Slackware uses termcap,
I mentally stopped there.

> You can fix the problem in lxi-tools by adding LIBS="-lncurses" to the
> configure command. With standard SBo template, it would look like:
> 
> LIBS="-lncurses"
> CFLAGS="$SLKCFLAGS" \
> CXXFLAGS="$SLKCFLAGS" \
> ./configure \
>   --prefix=/usr \
>   <...other options here...>

That will be far more elegant than the solution I arrived at which was
to patch configure.ac and Makefile.am, make an m4 directory and copy the
ax_lib_readline.m4 into the m4 directory, and rerun autoreconf -f -i
which did actually work!  Passing LIBS this way is much better.

> When I run configure this way, I still can't build lxi-tools since I
> don't have the lxi library it depends on, but I do get:

Using my convoluted method above, I did get lxi-tools to build and was
able to discover and grab a screenshot from my oscilloscope.

> Interestingly, this isn't just a problem for lxi-tools. Anything that
> tries to link with -lreadline but not -lncurses will fail in the same
> way on 14.2:

I package Hamlib and in it we use readline, but also use the
ax_lib_readline.m4 macro as part of our upstream so I didn't hit this
problem last year.  That threw me for a bit of a curve as well.

> Clear as mud, yes?

Oh yeah.  ;-)

I hadn't made the connection of the tie in between ncurses and tinfo
although I know they are closely related.  Next time I can RTFM a bit
more!

Anyway, thanks much for the thorough explanation.  Sometimes a refresher
is needed no matter how much we think we know!

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180127/3e9cc883/attachment.asc>

From yalhcru at gmail.com  Sun Jan 28 02:58:22 2018
From: yalhcru at gmail.com (B Watson)
Date: Sat, 27 Jan 2018 21:58:22 -0500
Subject: [Slackbuilds-users] 'AC_CHECK_LIB([readline]' fails on 14.2
In-Reply-To: <20180128004705.GS3615@n0nb.us>
References: <20180127132535.GN3615@n0nb.us>
 <CAN1hMuCmxq4aT3t+eMNhP69aMgWJrp4AtPU8W9QpokZ57H5KkA@mail.gmail.com>
 <20180128004705.GS3615@n0nb.us>
Message-ID: <CAN1hMuCy=y=b4DZ-ohyiizJyDS+sEbSBdGpfnhV+=S7sypKQUQ@mail.gmail.com>

On 1/27/18, Nate Bargmann <n0nb at n0nb.us> wrote:

> I've had more experience in the Debian world, and I recognized that
> tputs probably had to do with terminfo but since Slackware uses termcap,
> I mentally stopped there.

Slackware uses both actually. Not really an optimal situation, but we've
got both /usr/share/terminfo and /etc/termcap. Also in /usr/include
there's both term.h and termcap.h.

Main difference I see is that in Slackware 14.2 and older, the terminfo
functions are included in libncurses... and in Debian (and Slack-current)
they're split out into libtinfo, which is "the new way". I've never been
sure why it's "better". I've had to hack up some Makefiles to get rid
of references to -ltinfo to get them to work on 14.2.

> That will be far more elegant than the solution I arrived at which was
> to patch configure.ac and Makefile.am, make an m4 directory and copy the
> ax_lib_readline.m4 into the m4 directory, and rerun autoreconf -f -i
> which did actually work!  Passing LIBS this way is much better.

Ouch, yeah, that's more autoconf twiddling than I could stand. Congrats
on your persistence.

From n0nb at n0nb.us  Sun Jan 28 03:48:09 2018
From: n0nb at n0nb.us (Nate Bargmann)
Date: Sat, 27 Jan 2018 21:48:09 -0600
Subject: [Slackbuilds-users] 'AC_CHECK_LIB([readline]' fails on 14.2
In-Reply-To: <CAN1hMuCy=y=b4DZ-ohyiizJyDS+sEbSBdGpfnhV+=S7sypKQUQ@mail.gmail.com>
References: <20180127132535.GN3615@n0nb.us>
 <CAN1hMuCmxq4aT3t+eMNhP69aMgWJrp4AtPU8W9QpokZ57H5KkA@mail.gmail.com>
 <20180128004705.GS3615@n0nb.us>
 <CAN1hMuCy=y=b4DZ-ohyiizJyDS+sEbSBdGpfnhV+=S7sypKQUQ@mail.gmail.com>
Message-ID: <20180128034809.GU3615@n0nb.us>

* On 2018 27 Jan 20:59 -0600, B Watson wrote:
> Ouch, yeah, that's more autoconf twiddling than I could stand. Congrats
> on your persistence.

Oh, I had a "fun" time getting my head around Autoconf and Automake
several years ago.  I'm ruined for life.  ;-)

Anyway, thanks for the help.. The new packages are in the pending queue.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180127/5c328bf1/attachment.asc>

From chytraeu at sdf.org  Sun Jan 28 07:31:07 2018
From: chytraeu at sdf.org (Donald Cooley)
Date: Sun, 28 Jan 2018 01:31:07 -0600
Subject: [Slackbuilds-users] remove cryptoki
Message-ID: <56bb3bf8-efdd-ceeb-2e44-6651bbb56b8d@sdf.org>

Is cryptoki used by anything now that truecrypt has been replaced by
veracrypt some time ago?
Can we remove it? Thank you.

Regards,
Donald Cooley

From falsetti at clansco.org  Sun Jan 28 16:53:43 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Sun, 28 Jan 2018 17:53:43 +0100
Subject: [Slackbuilds-users] can't build libupnp
Message-ID: <20180128175343.ab7fc0020388f9ded71e5f72@clansco.org>


In file included from ../../upnp/inc/upnp.h:402:0,
                 from common/sample_util.h:49,
                 from common/sample_util.c:42:
../../upnp/inc/FileInfo.h:22:2: error: #error libupnp uses large file support, so users must do that, too
 #error libupnp uses large file support, so users must do that, too
  ^
Makefile:613: recipe for target 'common/tv_ctrlpt-sample_util.o' failed
make[3]: *** [common/tv_ctrlpt-sample_util.o] 

thanks for help...

Regards, ff

From willysr at slackbuilds.org  Sun Jan 28 16:55:39 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 28 Jan 2018 23:55:39 +0700
Subject: [Slackbuilds-users] can't build libupnp
In-Reply-To: <20180128175343.ab7fc0020388f9ded71e5f72@clansco.org>
References: <20180128175343.ab7fc0020388f9ded71e5f72@clansco.org>
Message-ID: <abe497ba-3bc1-3a93-f856-104e2b32de19@slackbuilds.org>

> In file included from ../../upnp/inc/upnp.h:402:0,
>                  from common/sample_util.h:49,
>                  from common/sample_util.c:42:
> ../../upnp/inc/FileInfo.h:22:2: error: #error libupnp uses large file support, so users must do that, too
>  #error libupnp uses large file support, so users must do that, too
>   ^
> Makefile:613: recipe for target 'common/tv_ctrlpt-sample_util.o' failed
> make[3]: *** [common/tv_ctrlpt-sample_util.o] 


Is it on 32 bit machine?
It works fine on 64 here


-- 
Willy Sudiarto Raharjo

-------------- 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/20180128/5631fe60/attachment.asc>

From falsetti at clansco.org  Sun Jan 28 17:58:25 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Sun, 28 Jan 2018 18:58:25 +0100
Subject: [Slackbuilds-users] can't build libupnp
In-Reply-To: <abe497ba-3bc1-3a93-f856-104e2b32de19@slackbuilds.org>
References: <20180128175343.ab7fc0020388f9ded71e5f72@clansco.org>
 <abe497ba-3bc1-3a93-f856-104e2b32de19@slackbuilds.org>
Message-ID: <20180128185825.a8c28b049e6505c77e4c94c8@clansco.org>

On Sun, 28 Jan 2018 23:55:39 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> > In file included from ../../upnp/inc/upnp.h:402:0,
> >                  from common/sample_util.h:49,
> >                  from common/sample_util.c:42:
> > ../../upnp/inc/FileInfo.h:22:2: error: #error libupnp uses large file support, so users must do that, too
> >  #error libupnp uses large file support, so users must do that, too
> >   ^
> > Makefile:613: recipe for target 'common/tv_ctrlpt-sample_util.o' failed
> > make[3]: *** [common/tv_ctrlpt-sample_util.o] 
> 
> 
> Is it on 32 bit machine?

yes it is

> It works fine on 64 here
> 
> 
> -- 
> Willy Sudiarto Raharjo
> 

From willysr at slackbuilds.org  Sun Jan 28 18:01:30 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 29 Jan 2018 01:01:30 +0700
Subject: [Slackbuilds-users] can't build libupnp
In-Reply-To: <20180128185825.a8c28b049e6505c77e4c94c8@clansco.org>
References: <20180128175343.ab7fc0020388f9ded71e5f72@clansco.org>
 <abe497ba-3bc1-3a93-f856-104e2b32de19@slackbuilds.org>
 <20180128185825.a8c28b049e6505c77e4c94c8@clansco.org>
Message-ID: <9a62694f-bf0c-9311-7529-d75e4600d321@slackbuilds.org>

>> Is it on 32 bit machine?
> 
> yes it is

Can you try to add this parameter to the configure line and rebuild?
--disable-largefile


-- 
Willy Sudiarto Raharjo

-------------- 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/20180129/900c15ad/attachment.asc>

From falsetti at clansco.org  Sun Jan 28 18:11:32 2018
From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti)
Date: Sun, 28 Jan 2018 19:11:32 +0100
Subject: [Slackbuilds-users] can't build libupnp
In-Reply-To: <9a62694f-bf0c-9311-7529-d75e4600d321@slackbuilds.org>
References: <20180128175343.ab7fc0020388f9ded71e5f72@clansco.org>
 <abe497ba-3bc1-3a93-f856-104e2b32de19@slackbuilds.org>
 <20180128185825.a8c28b049e6505c77e4c94c8@clansco.org>
 <9a62694f-bf0c-9311-7529-d75e4600d321@slackbuilds.org>
Message-ID: <20180128191132.9f22b8aadc595a0af329dd99@clansco.org>

On Mon, 29 Jan 2018 01:01:30 +0700
Willy Sudiarto Raharjo <willysr at slackbuilds.org> wrote:

> >> Is it on 32 bit machine?
> > 
> > yes it is
> 
> Can you try to add this parameter to the configure line and rebuild?
> --disable-largefile

Slackware package /tmp/libupnp-1.8.3-i586-1_SBo.tgz created.

thanks !!

> 
> 
> -- 
> Willy Sudiarto Raharjo
> 

From willysr at slackbuilds.org  Sun Jan 28 18:12:08 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 29 Jan 2018 01:12:08 +0700
Subject: [Slackbuilds-users] can't build libupnp
In-Reply-To: <20180128191132.9f22b8aadc595a0af329dd99@clansco.org>
References: <20180128175343.ab7fc0020388f9ded71e5f72@clansco.org>
 <abe497ba-3bc1-3a93-f856-104e2b32de19@slackbuilds.org>
 <20180128185825.a8c28b049e6505c77e4c94c8@clansco.org>
 <9a62694f-bf0c-9311-7529-d75e4600d321@slackbuilds.org>
 <20180128191132.9f22b8aadc595a0af329dd99@clansco.org>
Message-ID: <623ab3e4-0536-b067-e38a-5d3719208b6d@slackbuilds.org>

>> Can you try to add this parameter to the configure line and rebuild?
>> --disable-largefile
> 
> Slackware package /tmp/libupnp-1.8.3-i586-1_SBo.tgz created.
> 
> thanks !!

Thanks
a fix has been pushed on my branch as well, thanks to Ponce


-- 
Willy Sudiarto Raharjo

-------------- 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/20180129/a71775e7/attachment.asc>

From atelszewski at gmail.com  Sun Jan 28 21:10:03 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 28 Jan 2018 22:10:03 +0100
Subject: [Slackbuilds-users] ANNOUNCE: Qemu SBo script follows even
 branch stable releases
In-Reply-To: <bf003c9b-c4d0-1e55-d93f-efdc20500b60@gmail.com>
References: <bf003c9b-c4d0-1e55-d93f-efdc20500b60@gmail.com>
Message-ID: <117a3614-543c-1a9f-320d-d95062ea0ca4@gmail.com>

On 28/01/18 01:17, King Beowulf wrote:
> FYI:
> I'm following the qemu even number stable release schedule. Trying to
> keep up with interleaved odd and even branches is nuts.  I also can't
> find any information of why qemu devs do this, since all development in
> in git master not a "dev branch". If anyone knows why qemu does this,
> please let me know.

Ed, I don't exactly understand what you mean? ;-)

I always grab the latest versioned tarball from:
https://www.qemu.org/download/#source

(as of now, 2.11.0) and build from it.

Is there any info on what is considered to be stable and what 
development release?

-- 
Best regards,
Andrzej Telszewski

From kingbeowulf at gmail.com  Mon Jan 29 00:39:44 2018
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sun, 28 Jan 2018 16:39:44 -0800
Subject: [Slackbuilds-users] ANNOUNCE: Qemu SBo script follows even
 branch stable releases
In-Reply-To: <117a3614-543c-1a9f-320d-d95062ea0ca4@gmail.com>
References: <bf003c9b-c4d0-1e55-d93f-efdc20500b60@gmail.com>
 <117a3614-543c-1a9f-320d-d95062ea0ca4@gmail.com>
Message-ID: <debec4f5-2f7b-4df9-1347-529e3d85755e@gmail.com>

On 01/28/2018 01:10 PM, Andrzej Telszewski wrote:
> On 28/01/18 01:17, King Beowulf wrote:
>> FYI:
>> I'm following the qemu even number stable release schedule. Trying to
>> keep up with interleaved odd and even branches is nuts.? I also can't
>> find any information of why qemu devs do this, since all development in
>> in git master not a "dev branch". If anyone knows why qemu does this,
>> please let me know.
> 
> Ed, I don't exactly understand what you mean? ;-)
> 
> I always grab the latest versioned tarball from:
> https://www.qemu.org/download/#source
> 
> (as of now, 2.11.0) and build from it.
> 
> Is there any info on what is considered to be stable and what
> development release?
> 
No idea. 2.11.0 was released Dec 13th 2017.  By date 2.10.2 (Dec 18th
2017) is "newest" and from what I can gather so far git master is
development and both 2.10.x and 2.11.x are the stable branches (or
tags...).  Reading the changelogs and planning/2.1x just confuses as it
looks almost as though 2 different groups pull from the same master but
go their own path. There's no explanation as far as I can find.

2.11.0 2017-11-07 hard feature freeze
2.10.0 2017-07-25 hard feature freeze

BUT, they don't seem to stick with that as 2.10.2 lists a lot of
additions/deletions... The only thing that makes sense is if they are
patching a release for those that can't upgrade qemu as much and need
more code stability?

I just got tired of leapfrogging back and forth...

-Ed

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

From gerardo.zamudio at linux.com  Mon Jan 29 01:48:12 2018
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Sun, 28 Jan 2018 20:48:12 -0500
Subject: [Slackbuilds-users] ANNOUNCE: Qemu SBo script follows even
 branch stable releases
In-Reply-To: <bf003c9b-c4d0-1e55-d93f-efdc20500b60@gmail.com>
References: <bf003c9b-c4d0-1e55-d93f-efdc20500b60@gmail.com>
Message-ID: <e7f1ab73-1be3-565f-0f42-9c40975eec3e@linux.com>



On 01/27/2018 07:17 PM, King Beowulf wrote:
> FYI:
> I'm following the qemu even number stable release schedule. Trying to
> keep up with interleaved odd and even branches is nuts.  I also can't
> find any information of why qemu devs do this, since all development in
> in git master not a "dev branch". If anyone knows why qemu does this,
> please let me know.
> 


Have you tried asking the Qemu devs directly via mailing list, chat, or
some other contact method?

-- 
Gerardo Zamudio


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

From atelszewski at gmail.com  Mon Jan 29 09:21:19 2018
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 29 Jan 2018 10:21:19 +0100
Subject: [Slackbuilds-users] ANNOUNCE: Qemu SBo script follows even
 branch stable releases
In-Reply-To: <debec4f5-2f7b-4df9-1347-529e3d85755e@gmail.com>
References: <bf003c9b-c4d0-1e55-d93f-efdc20500b60@gmail.com>
 <117a3614-543c-1a9f-320d-d95062ea0ca4@gmail.com>
 <debec4f5-2f7b-4df9-1347-529e3d85755e@gmail.com>
Message-ID: <8b4c1544-979a-7a42-d078-89f566a34058@gmail.com>

On 29/01/18 01:39, King Beowulf wrote:
> BUT, they don't seem to stick with that as 2.10.2 lists a lot of
> additions/deletions... The only thing that makes sense is if they are
> patching a release for those that can't upgrade qemu as much and need
> more code stability?

This is exactly what I think they do.
If I recall correctly, 2.10.{1,2} fixed some more or less serious bugs.

-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Mon Jan 29 20:16:03 2018
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 29 Jan 2018 21:16:03 +0100
Subject: [Slackbuilds-users] ANNOUNCE: Qemu SBo script follows even
 branch stable releases
In-Reply-To: <8b4c1544-979a-7a42-d078-89f566a34058@gmail.com>
References: <bf003c9b-c4d0-1e55-d93f-efdc20500b60@gmail.com>
 <117a3614-543c-1a9f-320d-d95062ea0ca4@gmail.com>
 <debec4f5-2f7b-4df9-1347-529e3d85755e@gmail.com>
 <8b4c1544-979a-7a42-d078-89f566a34058@gmail.com>
Message-ID: <CAPsDuS7qGNBU0cVK6=388kT1jVF1BrAgWteMJ-gb5_c1py9pSA@mail.gmail.com>

2018-01-29 10:21 GMT+01:00 Andrzej Telszewski <atelszewski at gmail.com>:
> On 29/01/18 01:39, King Beowulf wrote:
>>
>> BUT, they don't seem to stick with that as 2.10.2 lists a lot of
>> additions/deletions... The only thing that makes sense is if they are
>> patching a release for those that can't upgrade qemu as much and need
>> more code stability?
>
>
> This is exactly what I think they do.
> If I recall correctly, 2.10.{1,2} fixed some more or less serious bugs.

I think those bugs were addressed in the 2.11.0 release first. I think
they updated 2.10.x for whoever can't update it, but reading the
following statement on their blogs I assume 2.11.x is the latest
stable release

https://www.qemu.org/2018/01/04/spectre/

Matteo

From ts at websafe.pl  Tue Jan 30 11:30:58 2018
From: ts at websafe.pl (Thomas Szteliga)
Date: Tue, 30 Jan 2018 12:30:58 +0100
Subject: [Slackbuilds-users] KeePass-2.38 installed in wrong directory
Message-ID: <fa171c77-6a33-390a-7df3-7f1315c1a396@websafe.pl>

Hello,

is there a real reason why KeePass-2.38 is being installed
in /usr/lib/KeePass-2.38  and not in /usr/lib/KeePass?

AFAIR few months ago I've submitted a patch and this was corrected,
but now I see KeePass is again installed in /usr/lib/KeePass-${VERSION}.

IMHO this is wrong, because this makes it harder to create packages
for KeePass plugins, like KeePassHttp, every time KeePass gets an update,
the plugin Slackbuilds need to be upgraded too, even if the plugin
was not changed. Plugins are compatible from one version to another,
and they are "recompiled" (by KeePass) at runtime.

I don't see any other program in /usr/lib/ which is installed
to /usr/lib/${PRGNAM}-${VERSION}, all go to /usr/lib/${PRGNAM}.


Can we maybe fix this once and for all? ;-)


https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-August/016939.html


-- 
Thomas Szteliga


From nastavs at gmail.com  Tue Jan 30 12:01:45 2018
From: nastavs at gmail.com (Shrivats)
Date: Tue, 30 Jan 2018 12:01:45 +0000
Subject: [Slackbuilds-users] KeePass-2.38 installed in wrong directory
In-Reply-To: <fa171c77-6a33-390a-7df3-7f1315c1a396@websafe.pl>
References: <fa171c77-6a33-390a-7df3-7f1315c1a396@websafe.pl>
Message-ID: <CAKgAtWAeGgJ5GkDyZwpRHfFOL_Oa8EGOKLTo6kCWorgQS=3xuA@mail.gmail.com>

Heh, I thought that was fixed a while ago. Anyway, I'll take a look at it
tonight

Thanks for letting be know!

On Jan 30, 2018 11:31, "Thomas Szteliga" <ts at websafe.pl> wrote:

> Hello,
>
> is there a real reason why KeePass-2.38 is being installed
> in /usr/lib/KeePass-2.38  and not in /usr/lib/KeePass?
>
> AFAIR few months ago I've submitted a patch and this was corrected,
> but now I see KeePass is again installed in /usr/lib/KeePass-${VERSION}.
>
> IMHO this is wrong, because this makes it harder to create packages
> for KeePass plugins, like KeePassHttp, every time KeePass gets an update,
> the plugin Slackbuilds need to be upgraded too, even if the plugin
> was not changed. Plugins are compatible from one version to another,
> and they are "recompiled" (by KeePass) at runtime.
>
> I don't see any other program in /usr/lib/ which is installed
> to /usr/lib/${PRGNAM}-${VERSION}, all go to /usr/lib/${PRGNAM}.
>
>
> Can we maybe fix this once and for all? ;-)
>
>
> https://lists.slackbuilds.org/pipermail/slackbuilds-users/20
> 16-August/016939.html
>
>
> --
> Thomas Szteliga
>
> _______________________________________________
> 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/20180130/101e00be/attachment.html>

From kjhambrick at gmail.com  Tue Jan 30 12:46:04 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Tue, 30 Jan 2018 06:46:04 -0600
Subject: [Slackbuilds-users] DOWNLOAD= in Several Flask-* SlackBuilds
Message-ID: <CANBHt+MDwZ580Oo9+2D8xy306mtBhzz2Kq6fUfyfWirA_Q5KsA@mail.gmail.com>

Mikos --

I stumbled over the DOWNLOAD= Lines in the following SlackBuilds when I
tried to `wget` the quoted URLs:


   python/Flask-Principal/Flask-Principal.info
   python/Flask-WTF/Flask-WTF.info
   python/Flask-Mail/Flask-Mail.info
   python/Flask-HTMLmin/Flask-HTMLmin.info

Note that each of the URL's includes a trailing '#md5=' string inside
the double-quoted DOWNLOAD= Value.

Also note that I only downloaded what I needed to build pgadmin4 so I
didn't look at all of the Flask-* SlackBuilds.

Maybe this is OK ?

Thanks for all the SlackBuilds and all your effort !

-- kjh

attached: diff -Naur listing createc vis:

# for i in `find python -type f -iname "*~01*"`; do j="$(echo $i |sed -e
's/~01//')"; diff -Naur $i $j; done
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180130/8c26a503/attachment.html>
-------------- next part --------------
--- python/Flask-Principal/Flask-Principal~01.info	2017-03-04 23:29:58.636277473 -0600
+++ python/Flask-Principal/Flask-Principal.info	2018-01-29 10:57:56.054321426 -0600
@@ -1,7 +1,7 @@
 PRGNAM="Flask-Principal"
 VERSION="0.4.0"
 HOMEPAGE="http://packages.python.org/Flask-Principal/"
-DOWNLOAD="https://pypi.python.org/packages/14/c7/2531aca6ab7baa3774fde2dfc9c9dd6d5a42576a1013a93701bfdc402fdd/Flask-Principal-0.4.0.tar.gz#md5=462d1345c9ddaddbec33a743e5821e2c"
+DOWNLOAD="https://pypi.python.org/packages/14/c7/2531aca6ab7baa3774fde2dfc9c9dd6d5a42576a1013a93701bfdc402fdd/Flask-Principal-0.4.0.tar.gz"
 MD5SUM="462d1345c9ddaddbec33a743e5821e2c"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
--- python/Flask-WTF/Flask-WTF~01.info	2017-03-04 23:29:58.636277473 -0600
+++ python/Flask-WTF/Flask-WTF.info	2018-01-29 11:03:22.375303924 -0600
@@ -1,7 +1,7 @@
 PRGNAM="Flask-WTF"
 VERSION="0.14.2"
 HOMEPAGE="https://github.com/lepture/flask-wtf"
-DOWNLOAD="https://pypi.python.org/packages/ba/15/00a9693180f214225a2c0b1bb9077f3b0b21f2e86522cbba22e8ad6e570c/Flask-WTF-0.14.2.tar.gz#md5=586f50f233926cade42e3d744aca3e8f"
+DOWNLOAD="https://pypi.python.org/packages/ba/15/00a9693180f214225a2c0b1bb9077f3b0b21f2e86522cbba22e8ad6e570c/Flask-WTF-0.14.2.tar.gz"
 MD5SUM="586f50f233926cade42e3d744aca3e8f"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
--- python/Flask-Mail/Flask-Mail~01.info	2017-03-04 23:29:58.636277473 -0600
+++ python/Flask-Mail/Flask-Mail.info	2018-01-29 10:49:45.490347738 -0600
@@ -1,7 +1,7 @@
 PRGNAM="Flask-Mail"
 VERSION="0.9.1"
 HOMEPAGE="https://github.com/rduplain/flask-mail"
-DOWNLOAD="https://pypi.python.org/packages/05/2f/6a545452040c2556559779db87148d2a85e78a26f90326647b51dc5e81e9/Flask-Mail-0.9.1.tar.gz#md5=04b35a42a44ec7aa724ec8ce55e2e08e"
+DOWNLOAD="https://pypi.python.org/packages/05/2f/6a545452040c2556559779db87148d2a85e78a26f90326647b51dc5e81e9/Flask-Mail-0.9.1.tar.gz"
 MD5SUM="04b35a42a44ec7aa724ec8ce55e2e08e"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
--- python/Flask-HTMLmin/Flask-HTMLmin~01.info	2017-03-10 18:54:50.378873556 -0600
+++ python/Flask-HTMLmin/Flask-HTMLmin.info	2018-01-29 13:25:19.773847082 -0600
@@ -1,7 +1,7 @@
 PRGNAM="Flask-HTMLmin"
 VERSION="1.2"
 HOMEPAGE="https://github.com/hamidfzm/Flask-HTMLmin"
-DOWNLOAD="https://pypi.python.org/packages/dd/2e/9f2d797d2ac59549fb3f493ab4716f2dbe538802d2c172fcc6f39eb079bf/Flask-HTMLmin-1.2.tar.gz#md5=c50ea7b1fcb6eae4b44e96d00671e2ea"
+DOWNLOAD="https://pypi.python.org/packages/dd/2e/9f2d797d2ac59549fb3f493ab4716f2dbe538802d2c172fcc6f39eb079bf/Flask-HTMLmin-1.2.tar.gz"
 MD5SUM="c50ea7b1fcb6eae4b44e96d00671e2ea"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""

From kjhambrick at gmail.com  Tue Jan 30 14:36:56 2018
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Tue, 30 Jan 2018 08:36:56 -0600
Subject: [Slackbuilds-users] Postfx version 3.2.5 is available
Message-ID: <CANBHt+OgHMg91yRFZONhL=2v+Qpwndg7ZVVwp=3K9XoNKO9baQ@mail.gmail.com>

Mario --

Saw on LQ that postfix version 3.2.5 is now available.

Builds and installs and runs fine on Slackware64 14.2 with 'the usual'
changes.

new DOWNLOAD="
http://cdn.postfix.johnriley.me/mirrors/postfix-release/official/postfix-3.2.5.tar.gz
"

new MD5SUM="d32f51b7178b12a87f2ac249e376ad38"

MD5SUM was set after checking Weitse's PGP Key at:
http://cdn.postfix.johnriley.me/mirrors/postfix-release/wietse.pgp

Thanks for the SlackBuild !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180130/3c4ba08c/attachment.html>

From rvnues at tesco.net  Tue Jan 30 14:23:56 2018
From: rvnues at tesco.net (rob van nues)
Date: Tue, 30 Jan 2018 14:23:56 +0000 (UTC)
Subject: [Slackbuilds-users] Fwd: Rstudio 0.98 no longer runs/compiles on
 Slackware current
In-Reply-To: <1322538004.304855.1494070485017.JavaMail.root@md02.topaz.synacor.com>
Message-ID: <1640175705.336217.1517322236960.JavaMail.root@md02.topaz.synacor.com>



----- Forwarded Message -----
From: "rob van nues" <rvnues at tesco.net>
To: "michael stewart" <michael.stewart at sydney.edu.au>
Sent: Saturday, 6 May, 2017 12:34:45 PM
Subject: Rstudio 0.98 no longer runs/compiles on Slackware current

Hi Michael,

Since the recent upgrade of boost, Rstudio 0.98 on SBo won't run:

"bash-4.4$ rstudio
rstudio: error while loading shared libraries: libboost_date_time.so.1.61.0: cannot open shared object file: No such file or directory
"

nor compile. Maybe the latter is due to gcc 7 or other dependencies (please see below remarks on LQ)

https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/page38.html#post5706804

I myself am not using R or R-studio at the moment (but have had some tutorials in the past on R and still keep it in case I'll need to use it again).

Cheers,


Rob

----- Forwarded Message -----
From: "LinuxQuestions.org" <forum at linuxquestions.org>
To: rvnues at tesco.net
Sent: Saturday, 6 May, 2017 10:19:20 AM
Subject: Reply to thread 'SBo scripts not building on current (read 1st post, pls)'

Dear brobr,

ponce has just replied to a thread you have subscribed to entitled - SBo scripts not building on current (read 1st post, pls) - in the Slackware forum of LinuxQuestions.org.

This thread is located at:
http://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999-new/

Here is the message that has just been posted:
***************
rstudio-desktop script will need a little refactoring to work with the new 1.0.143 version (there will also be additional dependencies, like qt5-webki
***************


There may also be other replies, but you will not receive any more notifications until you visit the forum again.

All the best,
LinuxQuestions.org

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Unsubscription information:

To unsubscribe from this thread, please visit this page:
http://www.linuxquestions.org/questions/subscription.php?do=removesubscription&type=thread&subscriptionid=2475606&auth=3b499537cfbf333cb6c497c27cd53a3f

To unsubscribe from ALL threads, please visit this page:
http://www.linuxquestions.org/questions/subscription.php?do=viewsubscription&folderid=all

From xavier at maillard.im  Tue Jan 30 19:32:01 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Tue, 30 Jan 2018 20:32:01 +0100
Subject: [Slackbuilds-users] Package as a whole or in different parts
Message-ID: <87inbjnnwu.fsf@smugg>

Hello,

I am willing to submit a new SBo for a project I am supporting and 
I have a few questions.
The project is SaT -i.e. Salut a Toi, an XMPP client.

It comes with a daemon, sat (the backend) and a few frontend 
clients (primitivus, jp, etc.)

As I do not want to go the wrong way and I want to stick with the 
KISS philosophy, I am just asking here: how would you package this 
? As a whole sat SBo build script, as 2 SBo (one for the backend 
and one for the frontends), as many different SBo scripts (one for 
the backend and one per frontend) ?

What's your opinion on this ?

Regards
--
Xavier

From yalhcru at gmail.com  Tue Jan 30 19:43:42 2018
From: yalhcru at gmail.com (B Watson)
Date: Tue, 30 Jan 2018 14:43:42 -0500
Subject: [Slackbuilds-users] Package as a whole or in different parts
In-Reply-To: <87inbjnnwu.fsf@smugg>
References: <87inbjnnwu.fsf@smugg>
Message-ID: <CAN1hMuAs_k9U2dbC9r-Xp2fCJGa-oOseqeArhiRFEcwVRs4f2A@mail.gmail.com>

On 1/30/18, Xavier Maillard <xavier at maillard.im> wrote:

> As I do not want to go the wrong way and I want to stick with the
> KISS philosophy, I am just asking here: how would you package this
> ? As a whole sat SBo build script, as 2 SBo (one for the backend
> and one for the frontends), as many different SBo scripts (one for
> the backend and one per frontend) ?

Does the source for all of the above come as a single tarball?

If so, I might do a single SlackBuild, that builds the backend and
all the frontends by default, with environment variables to disable
parts of it.

Example: the transmission SlackBuild. I maintain that one, though I
didn't write it from scratch (took it over from previous maintainer a
while back).

If the sources ship separately, it makes more sense to do separate builds
for the different parts.

From jebrhansen+SBo at gmail.com  Tue Jan 30 21:19:26 2018
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Tue, 30 Jan 2018 21:19:26 +0000
Subject: [Slackbuilds-users] Package as a whole or in different parts
In-Reply-To: <CAN1hMuAs_k9U2dbC9r-Xp2fCJGa-oOseqeArhiRFEcwVRs4f2A@mail.gmail.com>
References: <87inbjnnwu.fsf@smugg>
 <CAN1hMuAs_k9U2dbC9r-Xp2fCJGa-oOseqeArhiRFEcwVRs4f2A@mail.gmail.com>
Message-ID: <CANi9qStOJYWTU7Oy-6ngzmVPYqq5V+U4sG5fnvAybrNTaR4inQ@mail.gmail.com>

On Tue, Jan 30, 2018, 1:43 PM B Watson <yalhcru at gmail.com> wrote:

> On 1/30/18, Xavier Maillard <xavier at maillard.im> wrote:
>
> > As I do not want to go the wrong way and I want to stick with the
> > KISS philosophy, I am just asking here: how would you package this
> > ? As a whole sat SBo build script, as 2 SBo (one for the backend
> > and one for the frontends), as many different SBo scripts (one for
> > the backend and one per frontend) ?
>
> Does the source for all of the above come as a single tarball?
>
> If so, I might do a single SlackBuild, that builds the backend and
> all the frontends by default, with environment variables to disable
> parts of it.
>
> Example: the transmission SlackBuild. I maintain that one, though I
> didn't write it from scratch (took it over from previous maintainer a
> while back).
>
> If the sources ship separately, it makes more sense to do separate builds
> for the different parts.
>

I do a similar thing for mediainfo. It is the same source for both the CLI
and GUI versions, so I have the CLI enabled by default (but can be disabled
if desired) and the GUI optional by passing GUI=yes.

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180130/ed49c45f/attachment.html>

From xavier at maillard.im  Wed Jan 31 13:47:53 2018
From: xavier at maillard.im (Xavier Maillard)
Date: Wed, 31 Jan 2018 14:47:53 +0100
Subject: [Slackbuilds-users] Package as a whole or in different parts
In-Reply-To: <CANi9qStOJYWTU7Oy-6ngzmVPYqq5V+U4sG5fnvAybrNTaR4inQ@mail.gmail.com>
References: <87inbjnnwu.fsf@smugg>
 <CAN1hMuAs_k9U2dbC9r-Xp2fCJGa-oOseqeArhiRFEcwVRs4f2A@mail.gmail.com>
 <CANi9qStOJYWTU7Oy-6ngzmVPYqq5V+U4sG5fnvAybrNTaR4inQ@mail.gmail.com>
Message-ID: <87efm6p2ba.fsf@smugg>


Jeremy Hansen <jebrhansen+SBo at gmail.com> writes:

>> If the sources ship separately, it makes more sense to do 
>> separate builds
>> for the different parts.
>>
>
> I do a similar thing for mediainfo. It is the same source for 
> both the CLI
> and GUI versions, so I have the CLI enabled by default (but can 
> be disabled
> if desired) and the GUI optional by passing GUI=yes.

It makes sense. Thank you.

My project ships in different parts actually, one big part 
(including both the backend and a few frontends) and another 
source tarball for a specific "GUI" project (a webapp client).

After some deep thinking, I am not sure I will build as many 
packages. "sat" with no frontend is pretty useless AFAIK. I will 
do a unique package and another one for the libervia frontend (the 
webapp).

Regards
--
Xavier

From willysr at slackbuilds.org  Wed Jan 31 22:56:41 2018
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 1 Feb 2018 05:56:41 +0700
Subject: [Slackbuilds-users] DOWNLOAD= in Several Flask-* SlackBuilds
In-Reply-To: <CANBHt+MDwZ580Oo9+2D8xy306mtBhzz2Kq6fUfyfWirA_Q5KsA@mail.gmail.com>
References: <CANBHt+MDwZ580Oo9+2D8xy306mtBhzz2Kq6fUfyfWirA_Q5KsA@mail.gmail.com>
Message-ID: <a96ecd37-9640-be2b-55d4-358936b5a566@slackbuilds.org>

> I stumbled over the DOWNLOAD= Lines in the following SlackBuilds when I
> tried to `wget` the quoted URLs:
> 
> 
> ?? python/Flask-Principal/Flask-Principal.info
> ?? python/Flask-WTF/Flask-WTF.info
> ?? python/Flask-Mail/Flask-Mail.info
> ?? python/Flask-HTMLmin/Flask-HTMLmin.info
> 
> Note that each of the URL's includes a trailing '#md5=' string inside
> the double-quoted DOWNLOAD= Value.
> 
> Also note that I only downloaded what I needed to build pgadmin4 so I
> didn't look at all of the Flask-* SlackBuilds.
> 
> Maybe this is OK ?
> 
> Thanks for all the SlackBuilds and all your effort !
> 
> -- kjh
> 
> attached: diff -Naur listing createc vis:

Thanks
fixed this on my branch


-- 
Willy Sudiarto Raharjo

-------------- 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/20180201/87c73a2f/attachment.asc>

From mario at slackware.hr  Wed Jan 31 23:31:39 2018
From: mario at slackware.hr (Mario)
Date: Thu, 1 Feb 2018 00:31:39 +0100
Subject: [Slackbuilds-users] Postfx version 3.2.5 is available
In-Reply-To: <CANBHt+OgHMg91yRFZONhL=2v+Qpwndg7ZVVwp=3K9XoNKO9baQ@mail.gmail.com>
References: <CANBHt+OgHMg91yRFZONhL=2v+Qpwndg7ZVVwp=3K9XoNKO9baQ@mail.gmail.com>
Message-ID: <cf0df6a7-8654-c2a1-f25f-a64848b94bcb@slackware.hr>

On 01/30/2018 03:36 PM, Konrad J Hambrick wrote:
> Mario --
> 
> Saw on LQ that postfix version 3.2.5 is now available.
> 
> Builds and installs and runs fine on Slackware64 14.2 with 'the usual' 
> changes.
> 
> new 
> DOWNLOAD="http://cdn.postfix.johnriley.me/mirrors/postfix-release/official/postfix-3.2.5.tar.gz"
> 
> new MD5SUM="d32f51b7178b12a87f2ac249e376ad38"
> 
> MD5SUM was set after checking Weitse's PGP Key at: 
> http://cdn.postfix.johnriley.me/mirrors/postfix-release/wietse.pgp
> 
> Thanks for the SlackBuild !
> 
> -- kjh

Updated in my branch.

Regards,

-- 
Mario