Re: [Slackbuilds-users] Abandoning my SlackBuilds

[Andrzej Telszewski]

On 04/02/18 15:25, André Barboza wrote:

Hi guys,

Unfortunately I cannot maintain my SlackBuilds anymore.
So, here is the list. Please take care of them.



I'll take those:


development/qt-creator
development/qt-creator2




Thanks to all admins for helping me all these years.
A special thanks to Willy Sudiarto Raharjo and Robby Workman.



Thank you André for maintaning all of those.
Communicating with you has always been a pleasure.

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

Re: [Slackbuilds-users] intel-microcode version 'unbump'

[Andrzej Telszewski]

On 11/02/18 13:44, Konrad J Hambrick wrote:

Just a heads up ...

Intel has pulled intel-microcode Version 20180108 and they've reverted 
to version 20171117.


Hi,

I've just sent an update.

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

Re: [Slackbuilds-users] intel-microcode version 'unbump'

[Andrzej Telszewski]

On 11/02/18 18:49, Konrad J Hambrick wrote:

Maybe not.

The DOWNLOAD= URI always did a direct download.

But I don't know whether it was bypassing or if the license agreement is 
a new feature.


-- kjh


On Sun, Feb 11, 2018 at 8:07 AM, David Woodfall <d...@dawoodfall.net 
<mailto:d...@dawoodfall.net>> wrote:


Dang !

Sorry about the spam ...

I figured out how to extract the direct download URI from the
full URI thru
the License Agreement Page.


Should you really be bypassing the license agreement like that?


Hard to tell.

For me the border line works in the following way:
- if I can copy direct download URL from Firefox, I do it,
- otherwise, I put the link to license agreement in the DOWNLOAD=.

--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@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] uripareser requires graphviz

[Andrzej Telszewski]

Hi,

It looks that uripareser requires graphviz in order to build.

--
Best regards,
Andrzej Telszewski
diff --git a/libraries/uriparser/uriparser.info 
b/libraries/uriparser/uriparser.info
index 4499490d60..fc7a0829d8 100644
--- a/libraries/uriparser/uriparser.info
+++ b/libraries/uriparser/uriparser.info
@@ -5,6 +5,6 @@ 
DOWNLOAD="https://github.com/uriparser/uriparser/releases/download/uriparser-0.8
 MD5SUM="80c110ec22b70570ec124563a7a63075"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
-REQUIRES=""
+REQUIRES="graphviz"
 MAINTAINER="Matteo Bernardini"
 EMAIL="po...@slackbuilds.org"
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20180811.1

[Andrzej Telszewski]

On 13/08/2018 17:14, 414N wrote:

I can confirm that removing rust-1.26.x prior to building the 1.28
version works ok!



Count me in ;-)

Building 1.28.0 worked for me just fine, when bootstrapping using the 
previously built version 1.27.x.


Cheers.

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

Re: [Slackbuilds-users] libvirt 4.6.0 is a mess

[Andrzej Telszewski]

On 17/08/2018 18:35, Didier Spaier wrote:

Hi,

On 08/17/2018 06:20 PM, Andrzej Telszewski wrote:

Hi,

I've been contacting Robby, but since I haven't received any reply nor I see 
any correction in the git, I decided to come to the list, so you can take 
action before the next public update.

With version 4.6.0, libvirt has switched from yajl to Jansson.
Unfortunately, this switch comes with more problems than it solves:

https://bugzilla.redhat.com/show_bug.cgi?id=1614959
https://bugzilla.redhat.com/show_bug.cgi?id=1614569

I've actually experienced the bugs mentioned in the above threads.

libvirt team has already switched back for yajl for the next version.

What I propose is that you withdraw the 4.6.0 update.
Alternatively, you can update for version 4.5.0; the only change needed is 
changing back to yajl in REQUIRES and --with-yajl.


But the version in  https://slackbuilds.org/repository/14.2/libraries/libvirt/ 
is 4.0.O at time of writing so I don't understand what you request Robby to do, 
nor why there should be a correction in git.

Did you request an upgrade to 4.6.0 to Robby already, and want to withdraw this 
request?

Didier


I'd like those to be withdrawn:

https://git.slackbuilds.org/slackbuilds/commit/?id=dee223978
https://git.slackbuilds.org/slackbuilds/commit/?id=92f08be5b

before the public update.

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

Re: [Slackbuilds-users] New layout of https://slackbuilds.org/

[Andrzej Telszewski]

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@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] github doubling tarball name, again

[Andrzej Telszewski]

Hi,

When I try to download:
https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz

the suggested tarball name is:

"elementary-xfce-elementary-xfce-0.11.tar.gz"

Can someone knowledgeable (I know we have some here ;-)) tell me if it's 
possible to get the link in a way so that the tarball is actually:


"elementary-xfce-0.11.tar.gz"

?

Thanks!

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

Re: [Slackbuilds-users] github doubling tarball name, again

[Andrzej Telszewski]

On 25/03/18 18:56, Didier Spaier wrote:

Hi,

Le 25/03/2018 à 18:46, Andrzej Telszewski a écrit :

Hi,

When I try to download:
https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz

the suggested tarball name is:

"elementary-xfce-elementary-xfce-0.11.tar.gz"

Can someone knowledgeable (I know we have some here ;-)) tell me if it's 
possible to get the link in a way so that the tarball is actually:

"elementary-xfce-0.11.tar.gz"

No issue here, using wget-1.19.4-x86_64-2_slack14.2

Command:
wgethttps://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz

didier[~]$ ls -ltr elem*
-rw-r--r-- 1 didier users 7945508 mars  25 18:51 elementary-xfce-0.11.tar.gz


OK then.
wget works as expected, Firefox doesn't.
Shit. Again.

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

Re: [Slackbuilds-users] github doubling tarball name, again

[Andrzej Telszewski]

On 25/03/18 19:11, Matteo Bernardini wrote:

2018-03-25 18:46 GMT+02:00 Andrzej Telszewski <atelszew...@gmail.com>:

Hi,

When I try to download:
https://github.com/shimmerproject/elementary-xfce/archive/elementary-xfce-0.11.tar.gz

the suggested tarball name is:

"elementary-xfce-elementary-xfce-0.11.tar.gz"

Can someone knowledgeable (I know we have some here ;-)) tell me if it's
possible to get the link in a way so that the tarball is actually:

"elementary-xfce-0.11.tar.gz"

?


I suppose you are using a browser to download it or wget with the
parameter "--content-disposition", but it's not your or github's
fault: if you look at the release page you can see that they seem to
have tagged it wrong, compare the releases below or equal to v0.9 to
the subsequent

https://github.com/shimmerproject/elementary-xfce/releases

with proper tagging, prepending the name of the tag should let you
specify a consistent (not depending on the download type) naming for
the tarball, for example

https://github.com/shimmerproject/elementary-xfce/archive/v0.9/elementary-xfce-0.9.tar.gz

but as tagging for the following releases is broken I don't have a
solution for you apart for adding an alternate extraction routine,
like

tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf
$CWD/$PRGNAM-$PRGNAM-$VERSION.tar.gz

Matteo


Yep, I noticed this too.
curl shows that indeed that is the case:
Content-Disposition: attachment; 
filename=elementary-xfce-elementary-xfce-0.11.tar.gz


Maybe I'll open issue ticket there.

--
Best regards / Pozdrawiam,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@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] test

[Andrzej Telszewski]

Hi,

Can you see me? :-)

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

Re: [Slackbuilds-users] test

[Andrzej Telszewski]

On 18/03/18 13:10, Didier Spaier wrote:

Hi,

Le 18/03/2018 à 13:00, Andrzej Telszewski a écrit :

Hi,

Can you see me? :-)


No, there is no attached picture.

But at least we can hear you :-)


Fair enough ;-)

--
Best regards / Pozdrawiam,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Extend FAQ for UID/GID

[Andrzej Telszewski]

Hi,

"13. Do you keep a list of non-standard uid and gid numbers that we 
should use in our scripts?"


Could this point have somewhere words "group" and "user" added?
It took me a minute to think that I have to look for "UID" or "GID" to 
find the relevant info.


Thanks!

--
Best regards / Pozdrawiam,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Invoicing application recommendation

[Andrzej Telszewski]

Hi,

Can anyone suggest an invoicing application?

Only something that you use personally and that works well.
Preferably no Java, web based is completely out of scope.

Preferably the application should have single functionality: making 
invoices, keeping clients and history.


Thanks!

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

Re: [Slackbuilds-users] Proposal for Slackware category in SBo

[Andrzej Telszewski]

On 22/03/18 19:27, kla...@mixedsignals.ml wrote:
Rich's recent question (from which I learned much) made me think that 
maybe there ought to be a "Slackware" category in the SBo repo.


A "Slackware" category would contain applications that are useful only 
in Slackware. That is to say: there are applications that are useful 
across Linux, and then there are tools that are designed exclusively for 
Slackware (usually package management, often based on either Slackpkg or 
SBo). Tools that are useful in BOTH Linux and Slackware would *not* 
appear in this category.


Here are some examples. See how many of them you knew existed, and how 
many you know about but think more people might need help finding:

* sbopkg
* sboui
* sbbdep
* slackpkg+
* sport
* sbotools
* [insert your favourite obscure Slackware/SBo script or app here]

It seems to me like hiding great Slackware-specific sys utils harms 
discoverability, and mixing them into other, broader categories serves 
no purpose anyway. Sure, sboui might be a System tool, but let's face 
it: it's a Slackware "addon" that nobody knows to look for, and it's not 
just a system tool, it's a Slackware tool. Why not create a category we 
can all go to when we have questions like Rich's, and see what cool 
script or application one of our colleagues has written to scratch the 
itch?


Can anyone think of a reason this would be harmful, or not helpful?



Well, I can actually think of a reason this wouldn't be harmful ;-)
Sounds good.

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

Re: [Slackbuilds-users] Notes on building against the new PyQt5-5.9.2

[Andrzej Telszewski]

On 23/09/2018 13:39, Daniel Prosser wrote:
Thanks to a David Woodfall and everyone involved in making this update 
happen.


+1

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

Re: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm

[Andrzej Telszewski]

On 16/12/2018 06:52, Jheengut Pritvi wrote:



On Fri, 14 Dec 2018, 23:23 Matteo Bernardini 
mailto:matteo.bernard...@gmail.com> wrote:


Il giorno ven 14 dic 2018 alle ore 16:13 Jheengut Pritvi
mailto:z.coldpla...@gmail.com>> ha scritto:
 > /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No
such file or directory
 >
 > I have been reading some forums and it seems this issue started
when there was a change in
 > gcc version bump as from 6.0.  Could you please confirm or  I
will make a new thread.
 >
 > I am using Slackware-current and sbopkg. Three times I compiled
and got the same error.

hi Pritvi,

just version-bump qbs to 1.12.2 and qt-creator to 4.8.0 using the
existing SlackBuilds and they will build fine also on current.

Matteo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
<mailto:SlackBuilds-users@slackbuilds.org>
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


Thanks for your reply,
This is what I am now doing .

This evening I will check if everything has built well.



Hi,

I'm in the process of updating the SlackBuilds.

So far, I successfully compiled Qbs (1.12.2) and Qt Creator (4.8).

I was also able to compile the LLVM/Clang (7.0) from 
https://code.qt.io/clang/llvm

This is the recommended version of Clang to be used with QtC 4.8+.

BUT, I haven't yet tested building QtC against this Clang version.

If all goes well, the updated SlackBuilds should land in SBo in a couple 
of days.


I'm building on 14.2.

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

Re: [Slackbuilds-users] borgbackup msgpack-python problem

[Andrzej Telszewski]

On 06/12/2018 18:53, Audrius Kažukauskas wrote:

On Wed, 2018-12-05 at 17:42:27 -0800, David O'Shaughnessy wrote:

I'm having trouble with borgbackup on 14.2_64. Here's the error message
upon running borg init .

<...>

pkg_resources.DistributionNotFound: The 'msgpack-
python!=0.5.0,!=0.5.1,!=0.5.2,!=0.5.3,!=0.5.4,!=0.5.5,<=0.5.6,>=0.4.6'
distribution was not found and is required by borgbackup>


I've tried uninstalling and reinstalling borgbackup and all
dependencies, but no luck yet. The msgpack-python installed is 0.5.6, so
that should be ok?


I was hit by this as well a week or two ago, but was too tired and
annoyed to investigate the root of this issue, so what I've done was a
stupid, yet effective workaround -- I commented out msgpack-python line
in 
/usr/lib64/python3.6/site-packages/borgbackup-1.1.7-py3.6.egg-info/requires.txt
file and things were functional again.

But now I got curious and looked around a bit.  Here's what I dug up:
the problem here is that borgbackup requires msgpack-python while
upstream of the latter switched its name to msgpack (without -python
suffix).  borgbackup devs are aware of this change and will fix it
eventually (if they haven't already), but what we can do right now is
add the following to borgbackup.SlackBuild somewhere before the line
that calls 'python3 setup.py install':

   sed -i 's/msgpack-python/msgpack/' setup.py



I'll try to look into it ASAP.

(I need to finally switch to borg from attic, that would have caught my 
attention much faster).


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

Re: [Slackbuilds-users] borgbackup msgpack-python problem

[Andrzej Telszewski]

On 06/12/2018 18:53, Audrius Kažukauskas wrote:

On Wed, 2018-12-05 at 17:42:27 -0800, David O'Shaughnessy wrote:

I'm having trouble with borgbackup on 14.2_64. Here's the error message
upon running borg init .

<...>

pkg_resources.DistributionNotFound: The 'msgpack-
python!=0.5.0,!=0.5.1,!=0.5.2,!=0.5.3,!=0.5.4,!=0.5.5,<=0.5.6,>=0.4.6'
distribution was not found and is required by borgbackup>


I've tried uninstalling and reinstalling borgbackup and all
dependencies, but no luck yet. The msgpack-python installed is 0.5.6, so
that should be ok?


I was hit by this as well a week or two ago, but was too tired and
annoyed to investigate the root of this issue, so what I've done was a
stupid, yet effective workaround -- I commented out msgpack-python line
in 
/usr/lib64/python3.6/site-packages/borgbackup-1.1.7-py3.6.egg-info/requires.txt
file and things were functional again.

But now I got curious and looked around a bit.  Here's what I dug up:
the problem here is that borgbackup requires msgpack-python while
upstream of the latter switched its name to msgpack (without -python
suffix).  borgbackup devs are aware of this change and will fix it
eventually (if they haven't already), but what we can do right now is
add the following to borgbackup.SlackBuild somewhere before the line
that calls 'python3 setup.py install':

   sed -i 's/msgpack-python/msgpack/' setup.py



I've just pushed an updated version.
Unfortunately, upstream have not yet fixed the problem.

All this being said, I included a patch to fix the msgpack rename problem.

In my limited testing, borg works as expected again.

Thanks Audrius for the hint.

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

Re: [Slackbuilds-users] Slackware and SlackBuilds.org cited in a scientific publication

[Andrzej Telszewski]

On 15/03/2019 18:11, David O'Shaughnessy wrote:

On Fri, 15 Mar 2019, at 8:44 AM, Petar Petrov wrote:

Dear All,

I am happy to let you know Slackware and SlackBuilds.org were cited in
the most recent publication of our group. The paper is called
"Computational analysis of the evolutionarily conserved Missing In
Metastasis/Metastasis Suppressor 1 gene predicts novel interactions,
regulatory regions and transcriptional control" and was published in
Scientific Reports:

https://www.nature.com/articles/s41598-019-40697-1


Very cool, thanks for sharing this :)



Really cool! :-)


--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@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] MarkupSafe README needs updating

[Andrzej Telszewski]

Hi,

Since Python 3 is now required and used unconditionally for MarkupSafe, 
the README should be cleaned-up of the details of enabling Python 3 support.


Cheers.

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

Re: [Slackbuilds-users] Updates - 20190518.1 - intel-microcode

[Andrzej Telszewski]

On 20/05/2019 22:17, Jheengut Pritvi wrote:

If you are a bit busy, next time I will CC the mailing list too


That's almost always a good idea :-)

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

Re: [Slackbuilds-users] Updates - 20190518.1 - intel-microcode

[Andrzej Telszewski]

On 21/05/2019 01:51, Willy Sudiarto Raharjo wrote:

You didn't use the correct URL for github, so i fixed it on my branch.
please make sure to grab the latest version after next public update


No worries, I will ;-)
Thank you for your support :-)

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

Re: [Slackbuilds-users] Source code tarball - where to host

[Andrzej Telszewski]

On 23/05/2019 07:49, Willy Sudiarto Raharjo wrote:

You can host it here
https://sourceforge.net/projects/slackbuildsdirectlinks/

it's used by some of our members to host tarball only
you can tell me your username and i will add yours to one of the
developers access


Hi Willy,

Thank you for the prompt answer :-)
I think what you propose is going to be the solution of choice :-)

My username is: atelszewski

Please add me in.

Thank you!

--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Source code tarball - where to host

[Andrzej Telszewski]

Hi,

I have a source code tarball that I would like to host somewhere.

What comes to my mind in the first place is SourceForge.
I kinda don't like it all that much, because it's not responsive quite 
often (relatively).

On the plus side is that I already have an account there.

If there's nothing much better, then SF be it.

But I would like to ask you for your suggestions.

I don't take github into account, because I want to share just plain 
source code tarball. I will NOT spent time on importing the source code 
and then tagging it or whatever.
However, if there is an easy way of just sharing the tarball, and also 
if it can be compatible with _sbopkg_ and other tools (when it comes to 
file names), then I would be happy to use it. I have an account there 
too :-)


Thanks in advance! :-)

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

Re: [Slackbuilds-users] Updates - 20190518.1 - intel-microcode

[Andrzej Telszewski]

Hi,

The script as I submitted it, worked for me fine under slackrepo.
I hope the updated one will work as well, but I'm too lazy to test it 
now :-)


Cheers.

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

Re: [Slackbuilds-users] Qemu-4.1.0

[Andrzej Telszewski]

On 24/08/2019 14:42, Willy Sudiarto Raharjo wrote:

The missing gbm_bo_map() and GBM_BO_TRANSFER_READ_WRITE are satisfied by a newer
version of mesa than comes with 14.2 (or Current which has the same version of
mesa)

I don't have time to pursue this further at present :(

I have just tested in my 14.2 VM and it built fine

SDL2:
   MD5SUM check for SDL2-2.0.9.tar.gz ... OK
   Building package SDL2-2.0.9-x86_64-1_SBo.tgz ... OK
   Installing package SDL2-2.0.9-x86_64-1_SBo.tgz ... OK

qemu:
   MD5SUM check for qemu-4.1.0.tar.xz ... OK
   Building package qemu-4.1.0-x86_64-1_SBo.tgz ... OK
   Installing package qemu-4.1.0-x86_64-1_SBo.tgz ... OK


-- Willy Sudiarto Raharjo


Hi,

Did you install any additional deps?

My wild guess is that if one of /spice/ or /virglrenderer/ is installed 
then the build will fail.


Haven't tested it though.

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

Re: [Slackbuilds-users] LibreOffice 6.2.5.2 fails to build at Expat

[Andrzej Telszewski]

On 17/10/2019 13:10, Christoph Willing wrote:

On 17/10/19 3:21 pm, Andrzej Telszewski wrote:

Hi,

I'm trying to build LibreOffice 6.2.5.2, but it fails.
(Excerpt from build log listed at the end of message).

My build environment variables are the following:
JAVA=jdk LOLANGS=en-US

I'm building against _jdk_ and not _openjdk7_.

I'm pretty sure this build has succeeded in the past.
(Unfortunately, I don't have the package any more).

Please advice.
Thanks!

The first error in the build log is the following:

[CXX] l10ntools/source/helper.cxx
[CXX] l10ntools/source/common.cxx
[CXX] l10ntools/source/merge.cxx
In file included from /usr/include/expat.h:37:0,
  from
/tmp/slackrepo-desktop/slackrepo.R9x3UX/build_LibreOffice/libreoffice-6.2.5.2/shell/inc/xml_parser.hxx:23,

  from
/tmp/slackrepo-desktop/slackrepo.R9x3UX/build_LibreOffice/libreoffice-6.2.5.2/shell/source/all/xml_parser.cxx:21:

/usr/include/expat_external.h:1:1: error: stray '\1' in program
  riptor  user ended reading - closing archive    long
option '%s' not supported  long option '%s' ambiguous
  ^
/usr/include/expat_external.h:1:1: error: stray '\2' in program
/usr/include/expat_external.h:1:1: error: stray '\3' in program
/usr/include/expat_external.h:1:1: error: stray '\4' in program



It builds OK here with jdk and using your options as above. In that part
of the build, I have:

[build XCU] en-US
[build ECH] CustomTarget/instsetoo_native/setup/unorc
[build ECH] CustomTarget/instsetoo_native/setup/fundamentalrc
[build ECH] CustomTarget/instsetoo_native/setup/lounorc
[build GPF] CustomTarget/filter/source/svg/tokens.gperf
[build PY ] CustomTarget/filter/source/svg/svgscript.hxx
[build ECH] CustomTarget/i18npool/collator/lrl_include.hxx
[build CXX] shell/source/all/xml_parser.cxx
[build GPF] CustomTarget/sdext/pdfimport/hash.cxx
[build CXX] l10ntools/source/helper.cxx
[build CXX] l10ntools/source/common.cxx
[build CXX] l10ntools/source/merge.cxx
[build CXX] l10ntools/source/po.cxx
[build CUS] extras/fonts
etc.


Maybe you could try reinstalling your expat package, since the error
seems to implicate the expat header files.



That did the trick!
Thank you!


chris
___
SlackBuilds-users mailing list
SlackBuilds-users@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 / Pozdrawiam,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@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] LibreOffice 6.2.5.2 fails to build at Expat

[Andrzej Telszewski]

Hi,

I'm trying to build LibreOffice 6.2.5.2, but it fails.
(Excerpt from build log listed at the end of message).

My build environment variables are the following:
JAVA=jdk LOLANGS=en-US

I'm building against _jdk_ and not _openjdk7_.

I'm pretty sure this build has succeeded in the past.
(Unfortunately, I don't have the package any more).

Please advice.
Thanks!

The first error in the build log is the following:

[CXX] l10ntools/source/helper.cxx
[CXX] l10ntools/source/common.cxx
[CXX] l10ntools/source/merge.cxx
In file included from /usr/include/expat.h:37:0,
 from 
/tmp/slackrepo-desktop/slackrepo.R9x3UX/build_LibreOffice/libreoffice-6.2.5.2/shell/inc/xml_parser.hxx:23,
 from 
/tmp/slackrepo-desktop/slackrepo.R9x3UX/build_LibreOffice/libreoffice-6.2.5.2/shell/source/all/xml_parser.cxx:21:

/usr/include/expat_external.h:1:1: error: stray '\1' in program
 riptor  user ended reading - closing archivelong 
option '%s' not supported  long option '%s' ambiguous

 ^
/usr/include/expat_external.h:1:1: error: stray '\2' in program
/usr/include/expat_external.h:1:1: error: stray '\3' in program
/usr/include/expat_external.h:1:1: error: stray '\4' in program


--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Wrong MD5SUM for libreoffice-6.2.8.2-srcs.tar.xz at SourceForge?

[Andrzej Telszewski]

Hi,

When downloading:
http://sourceforge.net/projects/slackbuildsdirectlinks/files/LibreOffice/libreoffice-6.2.8.2-srcs.tar.xz

I get the following md5sum:
b5d5e57832056d8a5625b1d5dc3aa024

whereas .info states the following one:
1fcf52003e0d3c514caf8bfd40b6b88e


Where lies the problem?

Thanks in advance!


P.S.
Bcc'd maintainer.

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

Re: [Slackbuilds-users] Qt5 Update to 5.12

[Andrzej Telszewski]

On 26/01/2020 14:07, Dave Woodfall wrote:

I have /usr/lib64/qt5/bin/qdoc3 so perhaps we just need a symlink?


Might be well worth a try.

Will you build and test it or should I do it?

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

Re: [Slackbuilds-users] Qt5 Update to 5.12

[Andrzej Telszewski]

Hi,


development/qbs


It seems that qbs would build fine provided that qt5 actually built fine 
with DOCS=yes.


On my machine, qt5.SlackBuild fails with:

cd corelib/ && ( test -e Makefile || 
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/bin/qmake 
-o Makefile 
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/src/corelib/corelib.pro 
) && make -f Makefile prepare_docs
make[4]: Entering directory 
'/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/qmake'
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/qmake/qtattributionsscanner_wrapper.sh 
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase 
--filter QDocModule=qmake -o 
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/qmake/codeattributions.qdoc
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/qmake/qdoc_wrapper.sh 
-outputdir 
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/doc/qmake 
-installdir /usr/doc/qt5-5.12.0 
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/qmake/doc/qmake.qdocconf 
-prepare -indexdir 
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/doc 
-no-link-errors -I. -I../mkspecs/linux-g++
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/qmake/qdoc_wrapper.sh: 
line 12: /usr/lib64/qt5/bin/qdoc: No such file or directory

Makefile.qmake-aux:1343: recipe for target 'prepare_docs' failed
make[4]: *** [prepare_docs] Error 127
make[4]: Leaving directory 
'/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/qmake'
Makefile:435: recipe for target 'sub-qmake-qmake-aux-pro-prepare_docs' 
failed

make[3]: *** [sub-qmake-qmake-aux-pro-prepare_docs] Error 2
make[3]: *** Waiting for unfinished jobs
make[5]: Entering directory 
'/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/src/corelib'
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/src/corelib/qtattributionsscanner_wrapper.sh 
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase 
--filter QDocModule=qtcore -o 
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/src/corelib/codeattributions.qdoc
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/src/corelib/qdoc_wrapper.sh 
-outputdir 
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/doc/qtcore 
-installdir /usr/doc/qt5-5.12.0 
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/src/corelib/doc/qtcore.qdocconf 
-prepare -no-link-errors -I. -Iglobal -I../3rdparty/harfbuzz/src 
-I../3rdparty/md5 -I../3rdparty/md4 -I../3rdparty/sha3 -I../3rdparty 
-I../3rdparty/double-conversion/include 
-I../3rdparty/double-conversion/include/double-conversion 
-I../3rdparty/forkfd -I../3rdparty/tinycbor/src -I../../include 
-I../../include/QtCore -I../../include/QtCore/5.12.0 
-I../../include/QtCore/5.12.0/QtCore -I.moc -I.tracegen 
-I../3rdparty/pcre2/src -isystem /usr/include/glib-2.0 
-I/usr/lib64/glib-2.0/include -I../../mkspecs/linux-g++
/tmp/slackrepo-desktop/slackrepo.H62zZI/build_qt5/qt-everywhere-src-5.12.0/qtbase/src/corelib/qdoc_wrapper.sh: 
line 12: /usr/lib64/qt5/bin/qdoc: No such file or directory

Makefile:2532: recipe for target 'prepare_docs' failed
make[5]: *** [prepare_docs] Error 127



Maybe changing in qt5.SlackBuild:

  make docs

into something like that:

  sleep 3
  make -j1 docs || make -j1 docs

would help?

I remember having this issue before with, AFAIR, qt-5.7.

I can test this solution, but compilation here takes some time.
So I would come back no earlier than tomorrow :)

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

Re: [Slackbuilds-users] Marcel Saegebarth's orphaned builds

[Andrzej Telszewski]

Hi,

I'll take:
- llfuse

Cheers.

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

Re: [Slackbuilds-users] Qt5 Update to 5.12

[Andrzej Telszewski]

On 25/01/2020 16:47, Dave Woodfall wrote:

To the maintainers of build scripts that depend on Qt5.

I've been testing Qt5 LTS version 5.12, and everything seems to build
apart from the following applications:

development/qbs


I'll try to take a look tomorrow.


Cheers.

--
Best regards / Pozdrawiam,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@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] netcat-openbsd not building

[Andrzej Telszewski]

Hi,

_netcat-openbsd_ is not building for me.

It seems that there are some duplicate patches, that should not be applied.

For example there are:
0002-connect-timeout.patch
0003-connect-timeout.patch

both trying to do the same, but they were designed for different 
versions of netcat-openbsd code base.


Hope this helps!


Bcc'd maintainer.

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

Re: [Slackbuilds-users] users and groups

[Andrzej Telszewski]

On 27/12/2019 20:36, Marcelo Caballero via SlackBuilds-users wrote:

Hello,

All of the SlackBuilds that required to have a user and group they 
implement a restriction that prevents the script to continue if the user 
or group is missing.
I searched the FAQ and the wiki but I was unavailable to find anything 
related about this.


For example from the avahi readme: "First, be sure you have an "avahi" 
user and group. Do this *before* you install the avahi package."
So that means that we can run the SlackBuild without a user and group 
and then before we install the package we can add the user and group.

But the SlackBuild will fail without user/group...

This prevents one to build the package in a different machine (without 
to worry about users and groups) and then transfer the package and 
install it to the preferred machine.
Also any custom script or tool for building packages it would fail 
without to modified the SlackBuild first and remove the user and group 
restriction.


Regards Marcelo





Hi Marcelo,

But even if you remove the restriction on the need to have the 
user/group present, you will encounter another problem.


That is, package creation will fail during the moment the SlackBuild 
wants to adjusts some paths (dirs, files) to be owned by the particular 
user/group.


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

Re: [Slackbuilds-users] intel-microcode

[Andrzej Telszewski]

But I agree, cc:ing the maintainer seems like a good idea.



Indeed. :-D

I'll take a look as soon as I can.

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Vim indent settings for SlackBuilds

[Andrzej Telszewski]

On 05/09/2020 16:10, Dave Woodfall wrote:

I'm not really bothered either way, since I already have vim setup
with an autocmd, but I'd like to point out that root's vim has
modeline execution turned off by default as a security measure,
so if you're in the habit of testing a slackbuild, then edit it, then
test again, you would need to keep logging in and out in-between all
the time.

I edit using Qt Creator as regular user.
I then test building in QEMU (libvirt).

If your hardware allows, I strongly suggest going this path.
There are more added benefits to this choice as well.

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Vim indent settings for SlackBuilds

[Andrzej Telszewski]

On 08/09/2020 17:04, Dave Woodfall wrote:

On 07/09/20 23:02,
Andrzej Telszewski  put forth the proposition:

I edit using Qt Creator as regular user.

You use that as a general purpose editor?  Isn't it rather slow
compared to plain vim, and doesn't it also need X11 running to use
it?

I guess I'm a bit younger than you. :->
I'm X11 guy, using plain Linux VT only for emergency tasks.

When it comes to speed, well, it doesn't matter.
The machine is fast enough and SlackBuilds are small enough.


I don't use X11 unless it's absolutely necessary - for example, to
use a GUI web browser to access some websites that either need
javascript support that I can't get in my usual browser (elinks), or
where having images makes life easier (for shopping mostly).  Or
sometimes to test something with a GUI to see if it actually works.


I then test building in QEMU (libvirt).
If your hardware allows, I strongly suggest going this path.
There are more added benefits to this choice as well.

There are some high spec VMs available for admin use,

What do you mean by VM _for admin_?
You mean VM that is not running on your PC, but rather somewhere else, 
e.g. in the SBo infrastructure?



but I only use
them for large builds that would take a long time and tie my PC up,
otherwise I use a chroot with an overlay filesystem mounted in RAM.
At the end of a test session I simple unmount and remount the overlay
and everything is reset back to a clean chroot.

That is an option.

But I prefer QEMU, since everything is running under regular user, no 
_root_ required.
In addition, except for scripts/packages directories, no real hardware 
(i.e. /dev /proc /sys) is shared, so the SlackBuild can go mad and it 
will not hurt me.


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Protobuf3

[Andrzej Telszewski]

On 03/07/2020 14:51, Andrew Conway via SlackBuilds-users wrote:

Hi

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


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

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


Would embedding _protobuf3_ within the package you prepare be a viable 
solution?

It's very often possible, but at times the cost is a lot of headache.

Something to think of, anyways.

Cheers!

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

Re: [Slackbuilds-users] SBo service migration #1 complete

[Andrzej Telszewski]

On 03/07/2020 18:20, Erik Hanson wrote:

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

I support this choice with all my heart.
Over the years you proved (i.e. the SBo crew) that you can deal well 
with all the networking infrastructure needed.


When it comes to funding SBo, I see only one problem.
Once you ask for the funds, one has to be very quick with making the 
transfer.

Otherwise, it's all already donated. ;-)
But I know that you have good use for extra money, so that's not a 
problem whatsoever.


Have a good weekend!

--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Dave, Andrzej and qt-creator

[Andrzej Telszewski]

Hi,

@Dave Woodfall, a few days ago I've sent you my reply about *qbs* and 
*qt-creator*.


I'd like to confirm if you have received it?

(I'm not asking for prompt answer for the subject now, just confirmation).

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

Re: [Slackbuilds-users] Clementine up for grabs

[Andrzej Telszewski]

On 06/11/2020 21:51, Dave Woodfall wrote:

Andrzej, have you tried the Strawberry fork, by the way?

http://slackbuilds.org/repository/14.2/multimedia/strawberry/

No, but I will!

Thank you for pointing me out at this puppy.
If it works out as a replacement for Clementine, then I'll surely make a 
switch.


Though it's not current on SBo, it looks that upstream updates the 
official code base.

Something that Clementine misses (for better or worse).

Thanks!

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Clementine up for grabs

[Andrzej Telszewski]

On 03/11/2020 06:29, Jeremy Hansen wrote:
On Mon, Nov 2, 2020, 12:21 PM Dave Woodfall > wrote:


I no longer want to maintain clementine.  I haven't used it for
a very long time.  There is still some development happening, as I
often get emails from github about commits etc.

If anyone would like to take it over, they are welcome to.  If not,
I'll mark it as orphaned.


I haven't used it before, but I was a big fan of the old amarok. If 
someone already uses it and wants to take over, I'm totally fine with 
that, but if no one else claims it by the end of the week, I'll take 
it over.


Jeremy




I'm actually using *Clementine* as my main music player.
I'll happily take it over.
I'm bold enough to say that I'm better fir than Jeremy, because I 
actually use it. :->


On the other hand, I use it to play local collection exclusively, I 
don't use services like Spotify.
And for that reason, I will not be able to reassure correct operation 
for networked services.


If you find me a good fit for the job, I'm ready to take it. :-)

Cheers!

--
Andrzej

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] problem building avr-gcc on current (32bit)

[Andrzej Telszewski]

On 14/01/2021 21:54, Frans-Pieter Vonck wrote:

Hi,
I tried the script for avr-gcc.
This was the error from the log:
Hope this information is pointing to the cause.
Any ideas?
Grts, F.P.

configure:3458: $? = 0
configure:3447: /tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/xgcc 
-B/tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/ -B/usr/avr/bin/ 
-B/usr/avr/lib/ -isystem /usr/avr/include -isystem 
/usr/avr/sys-include    -V >&5

xgcc: error: unrecognized command line option '-V'
xgcc: fatal error: no input files
compilation terminated.
configure:3458: $? = 1
configure:3447: /tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/xgcc 
-B/tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/ -B/usr/avr/bin/ 
-B/usr/avr/lib/ -isystem /usr/avr/include -isystem 
/usr/avr/sys-include    -qversion >&5
xgcc: error: unrecognized command line option '-qversion'; did you 
mean '--version'?

xgcc: fatal error: no input files
compilation terminated.
configure:3458: $? = 1
configure:3474: /tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/xgcc 
-B/tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/ -B/usr/avr/bin/ 
-B/usr/avr/lib/ -isystem /usr/avr/include -isystem 
/usr/avr/sys-include    -o conftest -O2 -march=i586 -mtune=i686 
conftest.c  >&5

xgcc: error: unrecognized command line option '-march=i586'
xgcc: error: unrecognized command line option '-mtune=i686'
configure:3477: $? = 1
configure:3665: checking for suffix of object files
configure:3687: /tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/xgcc 
-B/tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/ -B/usr/avr/bin/ 
-B/usr/avr/lib/ -isystem /usr/avr/include -isystem 
/usr/avr/sys-include    -c -O2 -march=i586 -mtune=i686  conftest.c >&5

xgcc: error: unrecognized command line option '-march=i586'
xgcc: error: unrecognized command line option '-mtune=i686'

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



The version on SlackBuilds.org is 4.9.2.

Haven't you manually bumped the version to 8.2.0?
This could cause the issues.

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] problem building avr-gcc on current (32bit)

[Andrzej Telszewski]

On 15/01/2021 09:55, Andrzej Telszewski wrote:



On 14/01/2021 21:54, Frans-Pieter Vonck wrote:

Hi,
I tried the script for avr-gcc.
This was the error from the log:
Hope this information is pointing to the cause.
Any ideas?
Grts, F.P.

configure:3458: $? = 0
configure:3447: /tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/xgcc 
-B/tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/ -B/usr/avr/bin/ 
-B/usr/avr/lib/ -isystem /usr/avr/include -isystem 
/usr/avr/sys-include    -V >&5

xgcc: error: unrecognized command line option '-V'
xgcc: fatal error: no input files
compilation terminated.
configure:3458: $? = 1
configure:3447: /tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/xgcc 
-B/tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/ -B/usr/avr/bin/ 
-B/usr/avr/lib/ -isystem /usr/avr/include -isystem 
/usr/avr/sys-include    -qversion >&5
xgcc: error: unrecognized command line option '-qversion'; did you 
mean '--version'?

xgcc: fatal error: no input files
compilation terminated.
configure:3458: $? = 1
configure:3474: /tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/xgcc 
-B/tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/ -B/usr/avr/bin/ 
-B/usr/avr/lib/ -isystem /usr/avr/include -isystem 
/usr/avr/sys-include    -o conftest -O2 -march=i586 -mtune=i686 
conftest.c  >&5

xgcc: error: unrecognized command line option '-march=i586'
xgcc: error: unrecognized command line option '-mtune=i686'
configure:3477: $? = 1
configure:3665: checking for suffix of object files
configure:3687: /tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/xgcc 
-B/tmp/SBo/avr-gcc/avr-gcc-build-8.2.0/./gcc/ -B/usr/avr/bin/ 
-B/usr/avr/lib/ -isystem /usr/avr/include -isystem 
/usr/avr/sys-include    -c -O2 -march=i586 -mtune=i686 conftest.c >&5

xgcc: error: unrecognized command line option '-march=i586'
xgcc: error: unrecognized command line option '-mtune=i686'

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



The version on SlackBuilds.org is 4.9.2.

Haven't you manually bumped the version to 8.2.0?
This could cause the issues.



Excerpt from https://www.nongnu.org/avr-libc/NEWS.txt notes:

General:

This is the first official release supporting AVR-GCC 5 (and above).

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [Slackware-current] zfs-on-linux

[Andrzej Telszewski]

On 01/01/2021 04:15, David Chmelik wrote:
On Slackware-current with the 5.10.n kernels, I get this error 
building zfs-on-linux.  I don't know if the ZFS project updated it for 
5.10.n.


      CC [M]  /tmp/SBo/zfs-0.8.5/module/zfs/vdev_disk.o
   In file included from /tmp/SBo/zfs-0.8.5/include/sys/dmu.h:848,
     from /tmp/SBo/zfs-0.8.5/include/sys/spa.h:44,
     from /tmp/SBo/zfs-0.8.5/include/sys/spa_impl.h:35,
     from /tmp/SBo/zfs-0.8.5/module/zfs/vdev_disk.c:30:
   /tmp/SBo/zfs-0.8.5/module/zfs/vdev_disk.c: In function 
■vdev_disk_open■:

   /tmp/SBo/zfs-0.8.5/include/linux/blkdev_compat.h:378:37: error:
   implicit declaration of function ■check_disk_change■; did you mean
   ■bdev_disk_changed■? [-Werror=implicit-function-declaration]
      378 | #define vdev_bdev_reread_part(bdev) check_disk_change(bdev)
      | ^
   /tmp/SBo/zfs-0.8.5/module/zfs/vdev_disk.c:218:17: note: in expansion
   of macro ■vdev_bdev_reread_part■
      218 | int error = vdev_bdev_reread_part(bdev);
      | ^
   /tmp/SBo/zfs-0.8.5/module/zfs/vdev_disk.c: In function
   ■vdev_blkg_tryget■:
   /tmp/SBo/zfs-0.8.5/module/zfs/vdev_disk.c:506:37: error: ■struct
   percpu_ref■ has no member named ■count■
      506 |   rc = atomic_long_inc_not_zero(>count);
      | ^~
   cc1: some warnings being treated as errors
   make[5]: *** [scripts/Makefile.build:279:
   /tmp/SBo/zfs-0.8.5/module/zfs/vdev_disk.o] Error 1
   make[4]: *** [scripts/Makefile.build:496:
   /tmp/SBo/zfs-0.8.5/module/zfs] Error 2
   make[3]: *** [Makefile:1805: /tmp/SBo/zfs-0.8.5/module] Error 2
   make[3]: Leaving directory '/usr/src/linux-5.10.4'
   make[2]: *** [Makefile:30: modules] Error 2
   make[2]: Leaving directory '/tmp/SBo/zfs-0.8.5/module'
   make[1]: *** [Makefile:842: all-recursive] Error 1
   make[1]: Leaving directory '/tmp/SBo/zfs-0.8.5'
   make: *** [Makefile:711: all] Error 2




For 99% this is a change in the kernel's internal API.
So yes, ZFS project needs to adapt.

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] brace expansion

[Andrzej Telszewski]

On 6/17/21 12:56 AM, Jeremy Hansen wrote:
I'd prefer to allow bashisms and just use a /bin/bash shebang with the 
SlackBuilds.

I second that.

___
SlackBuilds-users mailing list
SlackBuilds-users@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] eagle: Rename to eagle7

[Andrzej Telszewski]

Hi,

for *-current*, please rename *eagle* to *eagle7*.

Version 7 is the last of it's kind (before Autodesk changed the 
licensing), so it makes sense to keep it.

But it also makes sense to have newer version, following Autodesk releases.
FYI, I don't plan on following, as I don't use Eagle anymore.

BTW, it served me well I spent significant amount of time with it.

Cheers.

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

Re: [Slackbuilds-users] Clementine up for grabs

[Andrzej Telszewski]

On 4/20/21 9:54 PM, Andrzej Telszewski wrote:

On 4/20/21 3:10 AM, Dave Woodfall wrote:

On 03/11/20 20:48,
Andrzej Telszewski  put forth the proposition:

If you find me a good fit for the job, I'm ready to take it. :-)
Cheers!
--
Andrzej

Andrzej, what did you decide?

I'll investigate over the coming weekend and come back to you.
Thank you for heads up.
I'm already on -current, so I'll test against it.


Hi Dave,

I've just given _Strawberry_ (0.9.3) a try and I'm switching to it.
I'm not going to be using _Clementine_ in the near future.

Please find _Clementine_ a more suitable maintainer, as I will not take 
it finally.


Thank you!

When it comes to _Strawberry_, the main selling points are:

- the code is being actively versioned and released,
- there is less code than in _Clementine_ and I'm not missing any features.

Should _Strawberry_ maintainer be not actively maintaining it anymore, 
I'll happily take it.


Cheers!

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

Re: [Slackbuilds-users] Clementine up for grabs

[Andrzej Telszewski]

On 4/20/21 3:10 AM, Dave Woodfall wrote:

On 03/11/20 20:48,
Andrzej Telszewski  put forth the proposition:

If you find me a good fit for the job, I'm ready to take it. :-)
Cheers!
--
Andrzej

Andrzej, what did you decide?

I'll investigate over the coming weekend and come back to you.
Thank you for heads up.
I'm already on -current, so I'll test against it.

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] acpi_call update

[Andrzej Telszewski]

On 8/31/21 18:16, Diego Borghetti via SlackBuilds-users wrote:

Hi all,

I hit this bug https://github.com/mkottman/acpi_call/issues/96 using acpi_call 
with tlp and notice that mkottman/acpi_call don't have any update in years.

Following the comments, there is a fork that ArchLinux seems to be using 
https://github.com/nix-community/acpi_call

I still didn't try this version (planning to do it tonight).
Is there any plan to use the fork of acpi_call in the future ?

I'll switch to the fork or alike soon.

Thanks for letting me know.

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

Re: [Slackbuilds-users] What if we `source`d the version number

[Andrzej Telszewski]

Jan 4, 2022 10:11:00 PM Klaatu :

> Why do we define the VERSION for a package in two separate files?
>  
> What if we replaced this line in foo.SlackBuild:
> VERSION={VERSION:-0.0.1}
>  
> with this instead:
> . ./$PRGNAM.info
>  
> The VERSION variable would get imported from a consolidated location (the 
> .info file).
>  
> It seems to make more sense to me, and it makes trivial upgrades (the ones 
> where I go in and just bump a version number to something I want to build) a 
> one-file task.
>  
> Thoughts?

You can source .info before executing .SlackBuild to get the same effect. No 
changes needed. :-)

> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@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@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] rtl8821ce: Reason for removal

[Andrzej Telszewski]

Hi,

I noticed that _network/rtl8821ce_ has been removed from master branch.
There is no info in the log why is it so.
Could you please explain?

Thank you! :-)

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

Re: [Slackbuilds-users] rtl8821ce: Reason for removal

[Andrzej Telszewski]

Mar 4, 2022 21:07:44 Dave Woodfall :
> I removed it because it failed to build when I tested it on 15.0.

I wonder, is it a general rule in preparation for 15.0 to remove what does not 
build?

I'm kind of concerned, because you didn't contact me about that.

> It looks like a header file was moved, but I'll try to make a patch for
> it.

I have a report from a user that some recent commit from the upstream repo 
builds fine on 15.0.
I'm not actively using this driver any more, so I cannot test it on real HW, 
but I surely can try building it.

Would you like me to try it out and report back?

Thank you for your effort! :-)

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] rtl8821ce: Reason for removal

[Andrzej Telszewski]

>> I have a report from a user that some recent commit from the upstream repo 
>> builds fine on 15.0.
>> I'm not actively using this driver any more, so I cannot test it on real HW, 
>> but I surely can try building it.
>> Would you like me to try it out and report back?
>
> Please do.

I reverted _83c64a3e52_, then applied the attached patch.
The driver builds and it can be loaded into the kernel (tested in VM).
Because recently I received a ping from one of the *rtl8821ce* driver users, I 
assume it is still in use by someone.

Please incorporate the attached patch.
Please note that it is slightly different from what _B Watson_ did in his 
branch (thanks for testing :-)).

Thank you! :-)
commit 91e6c50d221b074b3b45a2e2e7d0c10af5a54804
Author: Andrzej Telszewski 
Date:   Sun Mar 6 17:16:51 2022 +0100

network/rtl8821ce: Update to version 2029_ca204c6

diff --git a/network/rtl8821ce/rtl8821ce.SlackBuild b/network/rtl8821ce/rtl8821ce.SlackBuild
index 62df331dee..dc2164a399 100644
--- a/network/rtl8821ce/rtl8821ce.SlackBuild
+++ b/network/rtl8821ce/rtl8821ce.SlackBuild
@@ -2,7 +2,7 @@
 
 # Slackware build script for Realtek RTL8821CE Driver
 
-# Copyright 2020 Andrzej Telszewski, Szczecin
+# Copyright 2022 Andrzej Telszewski, Koszalin
 # All rights reserved.
 #
 # Redistribution and use of this script, with or without modification, is
@@ -25,7 +25,7 @@
 cd $(dirname $0) ; CWD=$(pwd)
 
 PRGNAM=rtl8821ce
-VERSION=${VERSION:-20201006_fe97b50}
+VERSION=${VERSION:-2029_ca204c6}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 PKGTYPE=${PKGTYPE:-tgz}
@@ -42,9 +42,6 @@ if [ -z "$ARCH" ]; then
   esac
 fi
 
-# If the variable PRINT_PACKAGE_NAME is set, then this script will report what
-# the name of the created package would be, and then exit. This information
-# could be useful to other scripts.
 if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
   echo "$PRGNAM-$PKG_VERS-$ARCH-$BUILD$TAG.$PKGTYPE"
   exit 0
diff --git a/network/rtl8821ce/rtl8821ce.info b/network/rtl8821ce/rtl8821ce.info
index a2c50137c9..268c53196f 100644
--- a/network/rtl8821ce/rtl8821ce.info
+++ b/network/rtl8821ce/rtl8821ce.info
@@ -1,10 +1,10 @@
 PRGNAM="rtl8821ce"
-VERSION="20201006_fe97b50"
+VERSION="2029_ca204c6"
 HOMEPAGE="https://github.com/tomaspinho/rtl8821ce/;
-DOWNLOAD="http://sourceforge.net/projects/slackbuildsdirectlinks/files/rtl8821ce/rtl8821ce-20201006_fe97b50.tar.gz;
-MD5SUM="f467f778f099b0f7a1634fe2f8bf0af4"
+DOWNLOAD="http://sourceforge.net/projects/slackbuildsdirectlinks/files/rtl8821ce/rtl8821ce-2029_ca204c6.tar.gz;
+MD5SUM="d40fb08c28810d00a26ed3498a85f2f3"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""
 MAINTAINER="Andrzej Telszewski"
-EMAIL="atelszew...@gmail.com"
+EMAIL="andr...@telszewski.com"
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Duplicates

[Andrzej Telszewski]

Hi,

and two different maintainers, one being me. ;-)

I will happily accept whatever decision SBo crew takes.
The version with underscores is longer on SBo.
On the other hand, version with hyphens is more _upstreamish_. :-)

-- 
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Slackware cited (again) in a scientific publication

[Andrzej Telszewski]

Hi,

thank you for the heads up!

In addition, I am always happy to hear about people being involved in science. 
:-)

All the best to you, and of course to our beloved Slackware (and the **one** 
and the **others** behind it. :-))


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

Re: [Slackbuilds-users] Edit suggested of intel-microcode.SlackBuild

[Andrzej Telszewski]

On 06/09/2023 14:29, fourtysixandtwo wrote:

I second Didier's suggestion.

Here's  a snippet from the grub docs, the default images it looks for 
are at the bottom:


'GRUB_EARLY_INITRD_LINUX_CUSTOM'
'GRUB_EARLY_INITRD_LINUX_STOCK'
     List of space-separated early initrd images to be loaded from
     '/boot'.  This is for loading things like CPU microcode, firmware,
     ACPI tables, crypto keys, and so on.  These early images will be
     loaded in the order declared, and all will be loaded before the
     actual functional initrd image.

     'GRUB_EARLY_INITRD_LINUX_STOCK' is for your distribution to declare
     images that are provided by the distribution.  It should not be
     modified without understanding the consequences.  They will be
     loaded first.

     'GRUB_EARLY_INITRD_LINUX_CUSTOM' is for your custom created images.

     The default stock images are as follows, though they may be
     overridden by your distribution:
          intel-uc.img intel-ucode.img amd-uc.img amd-ucode.img 
early_ucode.cpio microcode.cpio


Cheers


Still, I'm not that fast about changing the name.
This name is _kinda_ standard in Slackware for quite some time
and is used by default in _/etc/mkinitrd.conf_

Any suggestions?
Maybe a copy or configurable name of the output file in the SlackBuild?

Symlinking is out of scope, since the boot partition will often be 
FAT32, that does not support symlinks.


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Edit suggested of intel-microcode.SlackBuild

[Andrzej Telszewski]

On 06/09/2023 12:37, Didier Spaier wrote:

Hi Andrzej (in BCC) and all.,

I suggest to replae this line:
iucode_tool -v --write-earlyfw=$PKG/boot/intel-ucode.cpio \
by
iucode_tool -v --write-earlyfw=$PKG/boot/intel-ucode.img \


so that grub users running update-grub have this early initrd automatically
included in /grub.cfg, in a line like this one:

initrd  /@/boot/intel-ucode.img /@/boot/initramfs-6.1.46.img


Cheers,
Didier




Hi Didier,

looking for _intel-ucode.img_ on my system, I don't find anything 
interesting.


So, if it's not already _pre-configured_ in some of the _grub_ files, 
you could simple put

_intel-ucode.cpio_ instead of _intel-ucode.img_.

Or it wouldn't work, because grub does not like _*.cpio_?


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Edit suggested of intel-microcode.SlackBuild

[Andrzej Telszewski]

On 06/09/2023 21:20, Didier Spaier wrote:
I posted this suggestion to help users of genuine Slackware (most of 
them will use grub when 15.1 will be released) but will soon include 
the package intel-ucode in the Slint repositories with the name I 
proposed anyway, so am not personally in concern. Cheers, Didier


So is there anything that you would like me (the maintainer of the 
SlackBuild) to actually do as of today?


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Edit suggested of intel-microcode.SlackBuild

[Andrzej Telszewski]

> On the other hand one can propose a patch to append " intel-ucode.cpio" to
> GRUB_EARLY_INITRD_LINUX_STOCK

Isn't this path something that can be configured?
I use _syslinux_ and the path to additional images to load can be configured.

As I said, we have options, while keeping the current solution intact.

Is, at the SlackBuild level, a configurable output file name a solution that 
would satisfy you?


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Removing comments from borgbackup

[Andrzej Telszewski]

Hi,

I'm about to push a version update to _borgbackup_.

While doing that, I would like to remove and/ or reformat comments 
introduced to the SlackBuild by SBo admins.

(introduced when the SlackBuild was update by SBo, and not by me.)

Is that OK?

--
Best regards,
Andrzej Telszewski

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Removing comments from borgbackup

[Andrzej Telszewski]

On 19/10/2023 21:28, B. Watson wrote:



On Thu, 19 Oct 2023, Andrzej Telszewski wrote:


I'm about to push a version update to _borgbackup_.

While doing that, I would like to remove and/ or reformat comments 
introduced to the SlackBuild by SBo admins.

(introduced when the SlackBuild was update by SBo, and not by me.)

Is that OK?


Sure. The script has code in it that you didn't write. The comments
are there to explain to you why that code was added/changed and what
it's for. So long as you understand the code, you don't need the
comments.

The other answer is: It's your script, so yes you can remove the
comments if you want.


Thanks for the answer! :-)

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] sphinx-rtd-theme (Python) vs sphinx_rtd_theme (Development)

[Andrzej Telszewski]

*From: *King Beowulf 
*To: *SlackBuilds.org Users List 
*CC: *w...@eipg.fr; atelszew...@gmail.com
*Date: *15 Feb 2023 19:53:43
*Subject: *[Slackbuilds-users] sphinx-rtd-theme (Python) vs sphinx_rtd_theme 
(Development)

> Hello Admins,
>
> It appears that
>
> sphinx-rtd-theme Python 0.4.3    15.0
> sphinx_rtd_theme    Development    0.4.2    15.0
>
> are duplicates. sphinx-rtd-theme (Python) pypi link references the git
> repo for sphinx_rtd_theme (Development). Both project pages state that
> installation is via
>
> $ pip install sphinx-rtd-theme
>
> with current version at 1.2.0. I do not think we need both in SBo.
>
> This came up from a report that qemu now needs both Sphinx and
> sphinx-rtd-theme in order to build the documentation.
> -Ed

I suggest `Python/sphinx-rtd-theme` to be kept, and 
`Development/sphinx_rtd_theme` to be removed.

The name with hyphens seems to be more _official_ one.


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague)

[Andrzej Telszewski]

*From: *Konrad J Hambrick 
*To: *SlackBuilds.org Users List 
*Date: *8 Apr 2023 12:56:36
*Subject: *Re: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too 
vague)

> On Sat, Apr 8, 2023 at 4:54 AM marav  wrote:
>> 
>> I for one, I think all binary packages should be renamed with *-bin
>> 
>> It gives the most important information that the slackbuild is not a 
>> compiled version, directly in the name
>> No matter if there is a compiled version or not
>> 
> All --
> 
> Thinking out loud here ...
> 
> I agree with marav but would there not need to be special, one-time 
> instructions to `removepkg old-package-without-dash-bin` before doing an 
> `upgradepkg --install-nre new-package-with-bin` ?
> 
> Othewise, wouldn't upgradepkg be confused ? 
> 
> And would /var/log/packages/ be 'corrupted' ?
> 
> -- kjh


`pkgtools` are (specifically) designed in a way that if one package 
over-installs another, there is no corruption in the database.

You just need to uninstall the old package, which can be safely done after the 
new package is installed.

Actually, this is how the `upgradepkg` works under the hood.
It over-installs one package on the other, then removes the old one.


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] non-stripped binaries

[Andrzej Telszewski]

On 25/05/2023 10:18, B. Watson wrote:



On Thu, 25 May 2023, Andrzej Telszewski wrote:


On 25/05/2023 06:59, B. Watson wrote:

If that doesn't work, leave it unstripped. sbopkglint's supposed to
help you, not control you. 


Maybe `sbopkglint` supports annotation to tell it to treat some code 
as correct event though it thinks it is incorrect?


I've thought about that. "Magic comment" syntax in the SlackBuild
(which sbopkglint will find in /usr/doc/$PRGNAM-$VERSION).

The trouble is, we don't want it to be overused/abused. If every test
can be disabled, inevitably someone will start submitting builds with
all the tests disabled, which sorta defeats the purpose of having
sbopkglint.

But if only a few tests can be disabled, it might work out OK.


Aye, that is a generally known problem.
But it could be solved at submission review time.
(FYI, I'm in software engineering industry.)

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] non-stripped binaries

[Andrzej Telszewski]

On 25/05/2023 06:59, B. Watson wrote:

If that doesn't work, leave it unstripped. sbopkglint's supposed to
help you, not control you. 


Maybe `sbopkglint` supports annotation to tell it to treat some code as 
correct event though it thinks it is incorrect?


___
SlackBuilds-users mailing list
SlackBuilds-users@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] LibreOffice, Macro Security and libxml

[Andrzej Telszewski]

Hi,

this is just a heads up and a food to feed web search engines with a 
solution.


Recently, after a long time, I've updated my LibreOffice installation 
(build from source.)


I found myself in a situation where macros in Calc wouldn't work.
Even worse, pressing Options -> Security -> Macro Security... button did 
not make _any_ window to appear.

I was unable to fix the issue in the GUI.
I ended up editing 
`.config/libreoffice/4/user/registrymodifications.xcu` by hand and that 
finally allowed me to run macros.


But the proper solution came with the latest update (git commit 
758b22928) to the LibreOffice.SlackBuild.

This commit switches the build to use the _internal_ version of `libxml`.
And that change fixes that issue with macros, furthermore, pressing the 
_Macro Security..._ button shows

the macro security configuration window properly again.

Hope this helps someone, cheers! :-)

--
Best regards,
Andrzej Telszewski

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] gerbv slackbuilds

[Andrzej Telszewski]

On 15/12/2023 22:22, Felix Pfeifer wrote:

On 12/15/23 19:50, Ricardo Ramiro Peña wrote:

Dear Felix,

I am writing to ask you to update the gerb package to version 2.7.0. 
I recently reinstalled my Linux Slackware and used your slackbuilds 
to build the package with the new version. Just modify the version in 
the gerbv file.SlackBuild and download the 2.7.0 source code and I 
didn't have any problems.


Thank you for building for a package for Slackware Linux!


Best regards.



Hi all,

I am trying to forward this to the slackbuilds mailing list.
I don't know if this will work, since I cancelled my subscription
because I did quit Slackware and abandon my scripts. So that is
why I also addressed Willy directly. On my last post on the list
I announced my abandoning and named all scripts. This one might
have slipped through somehow.

@Willy could you please have a look at this? Is there a way of
marking a package "not maintained"? At FreeBSD if you install
a port which has no maintainer, it is always announced. I like
that feature a lot. ;)

Cheers,
Felix


Hi,

I was sort of thinking of taking up the SlackBuild, but it sits on the 
queue of stuff pending for SBo.

Anyways, for start, I would pick the sources from here:

https://github.com/gerbv/gerbv

which looks like actively maintained fork of the original.

All the best during this holidays period! :-)

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] LibreOffice, Macro Security and libxml

[Andrzej Telszewski]

On 17/12/2023 20:33, Luiz Carlos Ramos wrote:

Just out of curiosity... which libxml2 version is installed in your
machine?


I'm currently at `libxml2-2.11.6-x86_64-1_slack15.0`, but I think that when
I was compiling LibreOffice, I was at `libxml2-2.12.3-x86_64-1_slack15.0`.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it possible to test build packages using chroot?

[Andrzej Telszewski]

On 27/01/2024 18:37, Sebastian Arcus wrote:
As per title, is it possible to use chroot to test build packages 
against a different version of Slackware? For example if I have 
slackware -current on my machine, instead of setting up a full virtual 
machine, could I have a Slackware 15.0 install in a directory, and 
just chroot to it to test build a package? I confess I only have a 
general understanding of how chroot works - so there might be a reason 
why this can't work.


Sure it is! :-)

You might want to give `slackrepo` a chance.
It has capability to build in chroot, exactly what you want.

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] tracking down SBo "dependencies"

[Andrzej Telszewski]

*From: *Jim 
*To: *slackbuilds-users@slackbuilds.org
*Date: *29 Feb 2024 17:12:58
*Subject: *[Slackbuilds-users] tracking down SBo "dependencies"

> I recently upgraded the SBo dav1d, which upgraded the library from
> libdav1d.so.6 to libdav1d.so.7.
>
> Unfortunately, a couple of other SBo packages (libheif and vlc) had
> references to (specifically) libdav1d.so.6, which caused them to whine a
> bit.
>
> It was easy enough to recompile libheif and vlc after I found the problem,
> but this got me wondering...
>
> Does anyone have an easy way of tracking down this sort of "breakage" which
> might happen when upgrading an SBo package?
>
> Thanks.
>

Please consider tool like _slackrepo_.
It will rebuild a package in question should its dependiences be updated.


signature.asc
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@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] audacity fails to build if wxWidgets is built with STL=yes

[Andrzej Telszewski]

Hi,

it turns out that _audacity_ fails to build if _wxWidgets_ is built with 
`STL=yes`.


The error is:

```
error: cannot convert ‘wxString’ to ‘const char*’
```

Maybe add a note in the wxWidgets' README about that?

Bcc'd maintainer. :-)

--
Best regards,
Andrzej Telszewski

___
SlackBuilds-users mailing list
SlackBuilds-users@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] android-tools requires google-go-lang?

[Andrzej Telszewski]

Hi,

in order to build _android-tools_ I needed to install _google-go-lang_,
but it's not in `REQUIRES`.

Isn't that incorrect?

Bcc'd maintainer.

--
Best regards,
Andrzej Telszewski

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] android-tools requires google-go-lang?

[Andrzej Telszewski]

On 09/03/2024 11:15, Philip van der Hoeven wrote:

Hi,

google-go-lang should not be necessary, because android-tools can be 
build with gcc-go.
Are you sure you have gcc-go installed? It's included with Slackware 
in the d series.


Philip



Hello,

the issue was that, that `GOROOT` variable was slipping from my host to 
the `slackrepo`'s

build environment.

Unsetting it fixed the issue.
I need to pay some more attention to what enters the build environment 
in `slackrepo`.


Thank you for your assistance! :-)

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/