Re: [Slackbuilds-users] Updates - 20240106.1

[David O'Shaughnessy]

On Sat, 6 Jan 2024, at 9:47 AM, Willy Sudiarto Raharjo wrote:
> Please note that all new submission MUST be submitted via normal 
> submisison form in order to get it populated in the database during 
> public update. Updates to existing scripts can be done in both ways (via 
> Github PR or Gitlab MR or normal submission form).

Thanks Willy. So does this mean that for regular version updates (not new 
scripts) we can submit using git? Are there any docs outlining the basic 
workflow for GitLab and/or GitHub with the SBo repo specifically?
___
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] sboinstall chromprint fails

[David O'Shaughnessy]

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

sbotools needs a new maintainer, the last commit was around 4 years ago. But 
yes, it should probably be mentioned on the SlackBuild README that it's not by 
default set up for 15.0.
___
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] sboinstall chromprint fails

[David O'Shaughnessy]

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

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

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

To put sbotools onto a 15.0 repo.

--
Dave
___
SlackBuilds-users mailing list
SlackBuilds-users@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] Virtualbox

[David O'Shaughnessy]

Hi Heinz, I'm pretty sure the version of VirtualBox on SBo (6.1.34) is borked 
for some particular Windows version, I had endless problems until I updated to 
virtualbox-6.1.40 from your repo. I think at a minimum the soon to be EOL(?) 
6.x branch should be updated to the latest, just for compatibility. As for 7.x, 
if you're not up for it right now then I suppose someone else could submit a 
VirtualBox 7.x build script if they really cared to.

--
Dave

On Sun, 21 May 2023, at 4:39 AM, Heinz Wiesinger wrote:
> Hi there! I'm still alive, but indeed rather busy. I was hoping things would 
> have cleared up by now, but alas...
>
> I updated to 6.1.44 in my repo just this week, doing the same for SBo is on 
> my 
> TODO list. However, can't provide any timeline :-/
>
> Is there a specific feature/bugfix you *need* from the newer version though? 
> Generally, the version on SBo should work "just fine". If it's just about 
> running the "latest and greatest", you should be able to fetch the SlackBuild 
> from my -current or 15.0 repo (or even the packages). I don't typically 
> update 
> my scripts on SBo anymore unless there's a specific reason.
>
> Grs,
> Heinz
> ___
> 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/
>
>
> Attachments:
> * signature.asc
___
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] Virtualbox

[David O'Shaughnessy]

I'm not too sure why the maintainer is not pushing an update, probably busy?

There are some of the maintainer's build scripts here though that are updated:
https://repo.liwjatan.org/pprkut/15.0/source/
https://repo.liwjatan.org/pprkut/current/source/


On Thu, 11 May 2023, at 12:13 AM, Jim wrote:
> The current SlackBuild is for 6.1.34.
> 6.1.44 came out in April, but is EOL in December.
> V 7 is now up to 7.0.8.
>
> Does anyone know about any problems with upgrading to a newer version?
>
> Thanks.
> Jim
> ___
> 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/

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

[David O'Shaughnessy]

I wouldn't mind seeing binary repacks with -bin appended. I'd have to rename 
some of my own builds, but at least there's some information in the title. 
Differentiating by capitalization seems very arbitrary. 

On Sat, 8 Apr 2023, at 2:53 PM, B. Watson wrote:
> On Sat, 8 Apr 2023, Christoph Willing wrote:
>
>> Perhaps those *-bin SlackBuilds should have followed the existing 
>> convention provided 2 years earlier by Libreoffice/libreoffice - also 
>> Blender/blender 3 years earlier in Aug 2015.
>
> Gods, no. We'd have had even more confusion. Just because it was done
> doesn't make it a good idea to keep doing...
>
> I think having 2 builds with names that only differ in capitalization
> is a horrible idea. I'd even say it'd be a good idea to rename
> LibreOffice to libreoffice-bin and Blender to blender-bin.
> ___
> 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/

Re: [Slackbuilds-users] Updates - 20221223.1

[David O'Shaughnessy]

Looks like it breaks jbig2enc as well:

> checking for findFileFormatStream in -llept... no
> Error! Leptonica not detected.
> Failures:
>   jbig2enc: jbig2enc.SlackBuild return non-zero


On Fri, 23 Dec 2022, at 10:24 PM, Alexander Verbovetsky wrote:
> On Fri, Dec 23, 2022 at 10:28:04AM +0700, Willy Sudiarto Raharjo wrote:
>
>> libraries/leptopnica: Updated for version 1.83.0.
>
> This breaks graphics/tesseract. Can be fixed by straightforward bumping
> the tesseract version from 5.0.1 to 5.3.0 (the support for latest
> releases of leptonica is mentioned in the changelog for 5.2.0).
>
> Best regards,
> Alexander
___
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] SoulSeek?

[David O'Shaughnessy]

I think Linux development on the official client is dead, 2018 is the last 
Linux release:

https://www.slsknet.org/news/node/1

Nicotine+ is where it's at :)

On Tue, 26 Apr 2022, at 12:02 AM, Dominik Drobek wrote:
> W dniu 25.04.2022 o 02:15, David Chmelik pisze:
>> I'd still like to see the official client 
>> updated soon as I use it almost all the time.
>
> All right, I'll look into it.
>
> Regards,
> Dominik
___
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] abandoning all my slackbuilds

[David O'Shaughnessy]

I'll grab qbittorrent.

On Mon, 25 Apr 2022, at 1:34 AM, chytr...@sdf.org wrote:
> I've abandoned all my slackbuilds.
>
> anorack  [dependees]  Donald Cooley 
> bamf  [dependees]  Donald Cooley 
> bitrot  [dependees]  Donald Cooley 
> discount  [dependees]  Donald Cooley 
> dos2unix  [dependees]  Donald Cooley 
> dothost  [dependees]  Donald Cooley 
> dump  [dependees]  Donald Cooley 
> frostwire  [dependees]  Donald Cooley 
> gedit  [dependees]  Donald Cooley 
> gedit-plugins  [dependees]  Donald Cooley 
> gnome-menus  [dependees]  Donald Cooley 
> gprename  [dependees]  Donald Cooley 
> gtk-sharp  [dependees]  Donald Cooley 
> gtorrentviewer  [dependees]  Donald Cooley 
> hiawatha  [dependees]  Donald Cooley 
> leafpad  [dependees]  Donald Cooley 
> libtorrent-rasterbar  [dependees]  Donald Cooley 
> mosh  [dependees]  Donald Cooley 
> openoffice.org  [dependees]  Donald Cooley 
> perl-Cpanel-JSON-XS  [dependees]  Donald Cooley 
> perl-Data-Random  [dependees]  Donald Cooley 
> perl-Gtk2-Unique  [dependees]  Donald Cooley 
> perl-IO-HTML  [dependees]  Donald Cooley 
> perl-IO-Tty  [dependees]  Donald Cooley 
> perl-JSON-XS  [dependees]  Donald Cooley 
> perl-LWP-Protocol-socks  [dependees]  Donald Cooley 
> perl-Path-Class  [dependees]  Donald Cooley 
> perl-Proc-Simple  [dependees]  Donald Cooley 
> perl-Test-MockTime  [dependees]  Donald Cooley 
> perl-Types-Serialiser  [dependees]  Donald Cooley 
> perl-URI-Simple  [dependees]  Donald Cooley 
> perl-WebService-Gyazo-B  [dependees]  Donald Cooley 
> perl-common-sense  [dependees]  Donald Cooley 
> perl-gnome2  [dependees]  Donald Cooley 
> perl-gnome2-canvas  [dependees]  Donald Cooley 
> perl-gnome2-vfs  [dependees]  Donald Cooley 
> perl-gnome2-wnck  [dependees]  Donald Cooley 
> perl-goo-canvas  [dependees]  Donald Cooley 
> perl-gtk2-imageview  [dependees]  Donald Cooley 
> perl-html-form  [dependees]  Donald Cooley 
> perl-http-response-encoding  [dependees]  Donald Cooley 
> 
> perl-http-server-simple  [dependees]  Donald Cooley 
> perl-x11-protocol  [dependees]  Donald Cooley 
> plank  [dependees]  Donald Cooley 
> qbittorrent  [dependees]  Donald Cooley 
> qpdfview  [dependees]  Donald Cooley 
> qpdfview-qt5  [dependees]  Donald Cooley 
> quassel  [dependees]  Donald Cooley 
> quassel-qt5  [dependees]  Donald Cooley 
> sakura  [dependees]  Donald Cooley 
> shutter  [dependees]  Donald Cooley 
> smoffice2016  [dependees]  Donald Cooley 
> smoffice2018  [dependees]  Donald Cooley 
> smoffice2021  [dependees]  Donald Cooley 
> soundkonverter  [dependees]  Donald Cooley 
> tal  [dependees]  Donald Cooley 
> ___
> 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/

Re: [Slackbuilds-users] extra files in $PKG/install

[David O'Shaughnessy]

On Wed, 13 Apr 2022, at 12:57 PM, B. Watson wrote:
> The other possibility: if installpkg gets interrupted with ^C, it
> might leave the /installpkg- stuff lying around just because it
> got killed before it could remove it.

This is it, I just tested it out, and ctrl-c fast enough during installpkg 
leaves the directory behind in /
___
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] extra files in $PKG/install

[David O'Shaughnessy]

On Tue, 12 Apr 2022, at 1:55 PM, Ozan Türkyılmaz wrote:
> Do you remember what was inside? I just did a test build and install/
> only had slack-desc and doinst.sh.

Unfortunately not, but "libebml" was in there somewhere.

On Tue, 12 Apr 2022, at 2:30 PM, B. Watson wrote:
> Possibly an older version of libebml had the problem, and it's since
> been fixed? I checked just now, the version of libebml in the repo now
> is fine.

Probably yeah, it definitely doesn't happen now.
___
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] extra files in $PKG/install

[David O'Shaughnessy]

On Tue, 12 Apr 2022, at 1:55 AM, B. Watson wrote:
> How many of you have files named like these?
>
> $ ls -d /installpkg-*

Weirdly, I had one /installpkg-* type directory, with some libebml content. 
However, when I remove/rebuild/install libebml, I don't get the directory being 
created again, so I don't know what happened there.
___
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] GNU parallel

[David O'Shaughnessy]

It's in 15.0, and was added to -current (pre 15.0) back in 2018:

Wed Apr 25 04:38:51 UTC 2018
[...]
d/parallel-20180422-noarch-1.txz: Added.


On Thu, 31 Mar 2022, at 8:04 PM, Judah Milgram wrote:
> Hello,
>
> I got interested in trying GNU parallel:
>
> https://www.gnu.org/software/parallel/
>
> It doesn't seem to be in 14.2 (haven't upgraded yet) and I don't see a
> slackbuild for it. Which surprises me. So before downloading and
> building it (and writing a slackbuild) I thought I check here to see if
> it was already covered.
>
> Is it in 15.0? Or already in 14.2 hiding in plain sight?
>
> thanks!
>
> Judah
>
> ___
> 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] wire needs maintainer

[David O'Shaughnessy]

Hello,

Since I no longer use the program, I'm putting wire up for grabs. It's an easy 
one (binary repack), not often updated.

--
Dave
___
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] SlackBuild silently quitting - Cmake - make install

[David O'Shaughnessy]

On Mon, 28 Feb 2022, at 2:49 PM, B Watson wrote:
> I *do* see a problem with it, it's running
> glib-compile-schemas during the build, which means it overwrites
> /usr/share/glib-2.0/schemas/gschemas.compiled on the build system (AKA
> spamming the real filesystem). I'll patch it to avoid that...

On that topic, one easy way to check for this is with sbuild 
(https://gitlab.com/oshd/sbuild/). There are error codes for builds that write 
files outside of /tmp (even if they build properly).

--
Dave
___
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] Looking for new signal-desktop maintainer

[David O'Shaughnessy]

Thanks Greg!

On Thu, 17 Feb 2022, at 9:29 PM, Greg' Ar Tourter wrote:
> Hi David,
> 
> I am happy to take this one over. I will submit an updated version using the 
> binary build as a PR a bit later.
> 
> Cheers
> 
> Greg
> 
> On Thu, 17 Feb 2022 at 07:04, David O'Shaughnessy  wrote:
>> Hello all,
>> 
>> I'm looking to give up signal-desktop, as it's a fiddly source build, as 
>> well as suffering from binaries being frequently removed upstream (and I've 
>> started playing around with packaging it for my own repo). It's not the sort 
>> of package you can just leave without updates, as upstream will eventually 
>> disable old builds anyway.
>> 
>> That said, it's a great program/service. Would anyone be interested in 
>> taking it over?
>> 
>> --
>> Dave
___
SlackBuilds-users mailing list
SlackBuilds-users@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] New maintainer for olm

[David O'Shaughnessy]

Hello,

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

--
Dave

olm.tar.gz
Description: application/gzip
___
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] Looking for new signal-desktop maintainer

[David O'Shaughnessy]

Hello all,

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

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

--
Dave
___
SlackBuilds-users mailing list
SlackBuilds-users@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] pandoc-bin and `slackpkg clean-system`

[David O'Shaughnessy]

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

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

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

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

--
Dave
___
SlackBuilds-users mailing list
SlackBuilds-users@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] greenhorn greetings

[David O'Shaughnessy]

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

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

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

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

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

--
Dave
___
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] best way to mass-rebuild? (w/dependencies?)

[David O'Shaughnessy]

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

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

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

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

--
Dave
___
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 15.0 Released

[David O'Shaughnessy]

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

Great to see 15.0 finally out! To which git repo should we be sending updates?
___
SlackBuilds-users mailing list
SlackBuilds-users@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

[David O'Shaughnessy]

On Wed, 5 Jan 2022, at 5:39 AM, B Watson wrote:
> It'd take away the ability to override VERSION in the environment. A lot
> of us do this:
>
>   VERSION=1.2.3 sh foo.SlackBuild
>
> ...to attempt to build a new version of 'foo' with the existing
> script. Of course this doesn't always work, but it works often enough
> to be useful.

What about wrapping the original suggestion inside some simple logic, so that 
sourcing .info is only triggered if VERSION in the environment is empty?

--
Dave
___
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] Upgrade 14.2 to TexLive2021 or just biblatex?

[David O'Shaughnessy]

On Thu, 14 Oct 2021, at 1:24 AM, Rich Shepard wrote:
> Could I build the -current TexLive2021 in 14.2? Or should I upgrade
> biblatex/Biber to 3.16?

You can easily have the latest version of TeX Live installed if you use the 
official installer (it's non-intrusive and installs to /usr/local by default). 
Simply install and use tlmgr to keep up to date.

--
Dave
___
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] pdfstudio and pdfstudioviewer up for grabs

[David O'Shaughnessy]

On Sat, 31 Jul 2021, at 9:00 PM, Alexander Verbovetsky wrote:
> They (the pdfstudio upstream) changed their minds and published .debs
> for 64 bit version of pdfstudio and the viewer. (Probably, the Arch
> developers were able to convince them.)
>  
> Hence, I will continue to maintain pdfstudio and pdfstudioviewer
> SlackBuilds.

Great! (I emailed them too asking about an alternative packaging format rather 
than a point and click installer). Although, where exactly is the .deb? I can't 
see any link on the download page (https://www.qoppa.com/pdfstudio/download/) 
now that 2021 has been released.

--
Dave___
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 build scripts

[David O'Shaughnessy]

On Sat, 6 Mar 2021, at 4:11 AM, UpNort wrote:
> Hi All,
> 
> Proposal: SBo build scripts check locally for the downloaded sources and 
> validate the md5sum.

I have to agree with Erich on this one, I think that work should be left for 
the 3rd party SBo maintenance tools.

If you want something simple that will grab sources and compare md5s for manual 
SlackBuild work, you might find sbuild useful:

https://gitlab.com/oshd/sbuild/

--
Dave
___
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] haskell/shellcheck cannot build

[David O'Shaughnessy]

On Tue, 23 Feb 2021, at 10:56 AM, Jude DaShiell wrote:
> Many missing dependencies and this was after running sqg -p 
> haskell/shellcheck then building with that .sqf file.
> Are the missing dependencies not yet available in slackbuilds archive yet 
> or does the build script need improving?

It's a big build process, but `sboinstall haskell-ShellCheck` seems OK here (no 
builds are missing)? 

You may be interested in "ShellCheck-bin" though, zero dependencies.

--
Dave
___
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] Fresh soundkonverter download fails to buildx

[David O'Shaughnessy]

On Fri, 19 Feb 2021, at 7:58 AM, Rich Shepard wrote:
> If it's user error I must be at fault, right?

On a clean 14.2 (64-bit) install:

> sbocheck
> sboinstall soundkonverter

and it builds fine. You could check this on a clean install (say in a VM) 
before posting for help, at least then you could say that it's not a problem 
with the source/SlackBuild, but something local to your system.

--
Dave
___
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] geoclue2: wants optional dependencies [FIXED]

[David O'Shaughnessy]

On Thu, 18 Feb 2021, at 3:28 PM, B Watson wrote:
> On 2/17/21, Rich Shepard  wrote:
> >
> > The one that's been here since 2017 was modified in 2018 to include the
> > missing lines. I assumed that if the source tarballs were the same version
> > the build scripts would also be the same. That's been the case with other
> > packages but now we know, not with geoclue2.

Rich, I recommend using a tool to manage SBo builds and installs. Working off a 
random collection of scripts from however many years ago really is a recipe for 
all kinds of problems. sbotools is very easy to use and a simple:

sbocheck
sboinstall gnucash

would have sorted things out for you (with some user reading/input, of course). 
There is no special magic to it, so manual intervention is always possible if 
needed.

--
Dave
___
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] Docker command

[David O'Shaughnessy]

On Sun, 24 Jan 2021, at 1:32 PM, be...@caraus.de wrote:
> Check "docker-cli" package.

Ah, 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/

[Slackbuilds-users] Docker command

[David O'Shaughnessy]

After a recent upgrade to docker (20.10.2) on -current, it seems that the 
`docker` binary is no longer around. It used to be there.. am I missing 
something here?

--
Dave
___
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 - 20210123.1

[David O'Shaughnessy]

Looks like bat.info VERSION should 0.17.1 instead of 0.13.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] Fwd: ocaml Slackbuild on SBo

[David O'Shaughnessy]

On Thu, 19 Nov 2020, at 12:47 AM, Matteo Bernardini wrote:
> unfortunately many things depend on ocaml and it's not enough to
> update it to the latest version, you have to verify that whatever
> depends on it (as mandatory or optional) still works after the update:
> this is the work of a maintainer and ocaml needs one.
> for an idea on what depends on ocaml see this link (courtesy of Urchlay).
> 
> https://slackbuilds.org/advsearch.php?q=ocaml=revdep
> 
> is there anyone interested in stepping in with that role?

I use unison which depends on ocaml, so I might be able to do this (depending 
on what's actually required). I only run -current at the moment though.

--
Dave
___
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] FreeBASIC update fails

[David O'Shaughnessy]

On Wed, 23 Dec 2020, at 12:20 PM, Didier Spaier wrote:
> I don't know if this is an issue with the makefile, the SlackBuild
> or a difference between Slint and Slackware (which I assume
> unlikely, but I could be wrong). 

I don't have 14.2 to test any more, but building on regular Slackware -current 
throws the same error.
___
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] FreeBASIC update fails

[David O'Shaughnessy]

On Wed, 23 Dec 2020, at 11:10 AM, Jude DaShiell wrote:
> This may be useful it's a typescript file stripped of the ansi characters.
> 
> Script started on 2020-12-22 22:23:40-05:00 [TERM="linux" 
> TTY="/dev/tty1" COLUMNS="200" LINES="56"]

Hmm, that was nearly 1MB of text inline. IMO better to use Pastebin 
(https://pastebin.com/) or something for that kind of thing.
___
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] Add Autodetect to ffmpeg for Optional Dependencies

[David O'Shaughnessy]

On Sat, 24 Oct 2020, at 5:02 PM, Jeremy Hansen wrote:
> Heinz,
> 
> So I decided to add autodetection for those packages into the SlackBuild 
> script itself and update the variables passed to the ./configure based on 
> that autodetection. pkg-config is used for most of them, but there's 7 
> programs that don't support it, so I just checked for that program's header 
> file.

Awesome, IMO this is a big improvement over the "default: no" approach.

--
Dave___
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] Signal-Desktop obsolete

[David O'Shaughnessy]

Hello, just a heads up that Signal-Desktop-0.42.2 ought to be removed, it's 
from August 2017* and such a build will not function on the Signal network. In 
fact upstream now denies service after a client becomes too out of date (and 
three years is far beyond that limit).

--
Dave

* https://github.com/signalapp/Signal-Desktop/releases/tag/v0.42.2
___
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] Version bumping SlackBuilds (sbup)

[David O'Shaughnessy]

On Mon, 21 Sep 2020, at 10:49 PM, David O'Shaughnessy wrote:
> Hello all, here's a script I made for doing version bumps on 
> SlackBuilds (I get tired of doing this by hand). The idea is you can do 
> `sbup version` in a directory to version bump the .info and SlackBuild 
> (i.e., version, download, and md5s).

Forgot to say, if you have sbuild installed, it will offer to test build the 
new script in a chroot/overlayfs.

https://gitlab.com/oshd/sbuild

--
Dave
___
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] Version bumping SlackBuilds (sbup)

[David O'Shaughnessy]

Hello all, here's a script I made for doing version bumps on SlackBuilds (I get 
tired of doing this by hand). The idea is you can do `sbup version` in a 
directory to version bump the .info and SlackBuild (i.e., version, download, 
and md5s).

I'm only new to Python so I'd appreciate any comments, code, or ideas. I'm sure 
much of this can be done in a better way.

https://gitlab.com/oshd/sbup

--
Dave
___
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] JabRef 5.0 SlackBuild

[David O'Shaughnessy]

For the JabRef 5 people, here's 5.1.

On Fri, 24 Jul 2020, at 2:44 PM, David O'Shaughnessy wrote:
> SlackBuild for JabRef 5.0 attached, for those interested. The new version 
> does away with jdk dep (they now bundle in their own jre).
> 
> --
> Dave
> ___
> 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/
> 
> 
> 
> *Attachments:*
>  * jabref-5.0.tar


jabref.tar
Description: Unix tar archive
___
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] Last Update

[David O'Shaughnessy]

On Thu, 6 Aug 2020, at 7:38 PM, Robby Workman wrote:
> 06:16 <+rworkman> There was an unexpected hiccup in the shipping process. All 
> is well, or at least it will be, but the timeframe has been extended yet 
> again. 
> 06:16 <+rworkman> None of this is in our control. We don't like it either. 
> Nothing we can do about it.
> 06:16 <+rworkman> None of it is malicious, from any part of the process. 
> 06:17 <+rworkman> TLDR: people gave us hardware for free and hosted it for 
> free, and now that they're going out of business, they're shipping it for 
> free to another place for us. Some of the free services are slower than we'd 
> like. Tough shit.

It's all good.___
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] JabRef 5.0 SlackBuild

[David O'Shaughnessy]

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

--
Dave

jabref-5.0.tar
Description: Unix tar archive
___
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] newsboat fun

[David O'Shaughnessy]

On Tue, 30 Jun 2020, at 11:56 AM, Jude DaShiell wrote:
> Finally got this built.
> sbopkg can't build all of it though.
> I built stfl in sbopkg separately and needed to run gem install
> asciidoctor before sbopkg -i newsboat was able to build newsboat.
> No problem though, things like this make life interesting here.
> 
> There's no qui package for ruby/asciidoctor which is why gem had to be
> run.

Sounds like the problem's local to your setup. Both newsboat and stfl download 
and build fine for me with either sbopkg or sbotools (although sbopkg is very 
slow to run through the download list!), perhaps you could try clearing out 
sbopkg's download cache in /var/cache/sbopkg first?

--
Dave___
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] Dependency cleanup after package removal

[David O'Shaughnessy]

On Mon, 22 Jun 2020, at 7:56 PM, Dominik Drobek wrote:
> I was wondering how do people manage dependency cleanup when 
> uninstalling SBo packages?

sboremove from sbotools is one way to handle this. `sboremove foo` would offer 
to uninstall any dependencies of 'foo' that aren't required by other installed 
SBo builds. It's not foolproof however, since it's possible for example that 
some package is only a hard dependency of 'foo', but is also a 
soft/auto-detected dependency of another build. Still, I find it useful.

--
Dave
___
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 20200601

[David O'Shaughnessy]

On Mon, 1 Jun 2020, at 2:05 AM, Willy Sudiarto Raharjo wrote:
> we are a bit late on this update, but here's a good news:
> Heinz has pushed a new update on virtualbox to build the latest
> virtualbox 6.1.8 It's targetting for -current (or future 15.0
> repository), but for those who wanted to use them in 14.2 (-stable), you
> can still do so, but you need to install some new dependencies such as Qt5.

Awesome work on Virtualbox 6, I finally have it running on -current, thanks 
Heinz!

--
Dave___
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] Remove libaom...

[David O'Shaughnessy]

On Sun, 24 May 2020, at 12:14 AM, andrew wrote:
> Hi Dave,
> 
> Your detective work is amazing! As to your suggestion:

B Watson gets the credit for that! But I can't believe they create the archive 
on the fly, what exactly is the point of it? O_o

--
Dave
___
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] Remove libaom...

[David O'Shaughnessy]

On Sat, 23 May 2020, at 12:18 PM, D Woodfall wrote:
> On 23/05/20 20:00,
> andrew  put forth the proposition:
> >
> > The new 'aom' is the replacement / update for 'libaom', could libaom
> > be removed from SBo?
> >

>From aom.info:

https://aomedia.googlesource.com/aom/+archive/bb35ba9148543f22ba7d8642e4fbd29ae301f5dc.tar.gz
0b6d82f4b0f56c198e400ad829b27bba

md5sum fails here.

--
Dave___
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] aspell6-es

[David O'Shaughnessy]

Just found out that aspell6-es is redundant since it's already in /extra, so it 
can be dropped from SBo.

--
Dave
___
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] bat: failed build (newer rust required?)

[David O'Shaughnessy]

On Tue, 5 May 2020, at 12:05 AM, Erich Ritz via SlackBuilds-users wrote:
> Hi Benjamin and list,
> 
> Trying to build system/bat from a 64-bit chroot using sbopkg I get the 
> following error:
> 
> ...
>  Compiling git2 v0.13.3
> error: enum variants on type aliases are experimental
>  --> /tmp/SBo/bat-0.15.0/vendor/git2-0.13.3/src/apply.rs:24:48
>  |
> 24 | raw::GIT_APPLY_LOCATION_WORKDIR => Self::WorkDir,
>  | ^
> 

> 
> Does bat (actually in this case it looks like the git2 library (crate, 
> whatever)) require a newer rust?

I don't know about 0.15.0, but the version on SBo (0.13.0) builds for me on 
both -current and in 14.2. I'd test with the newer release, but the .info file 
looks like it must take some automation to prepare!

Had never heard of bat though, nice program (from the author of the excellent 
fd too). Seems to nicely replace both cat and less for cmd-line usage.

--
Dave___
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] BeautifulSoup4 not building

[David O'Shaughnessy]

On Sat, 11 Apr 2020, at 9:57 AM, Dave Woodfall wrote:
> Did you find a solution to this?
> 
> I get the same error when building in a chroot, but it builds fine on
> the host machine. It doesn't seem to matter it bs4 is already
> installed or not.

I can't get the build to fail on -current or 14.2 (without or without 
BeautifulSoup4 installed). Seems to build even in a chroot (with this 
https://gitlab.com/oshd/sbuild/ anyway).___
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 - 20200328.1

[David O'Shaughnessy]

On Sat, 28 Mar 2020, at 9:46 AM, Willy Sudiarto Raharjo wrote:
> > I just had an issue here with snappy. The build wasn't successful: it
> > stopped with a lot of errors when linking a unitttest.
> > 
> > I could find a solution googling a little and so I'm offering a patch
> > which hopefully may prevent this issue happening in other environments.
> 
> I had an issue as well when testing this under -current, but when being
> tested under -stable, it works just fine
> 

I can't get it to build on -current or 14.2, both fail at the unit test.

--
Dave___
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] Last Saturday's updates

[David O'Shaughnessy]

Another option is to follow the RSS feed:
https://slackbuilds.org/rss/ChangeLog.rss

--
Dave
___
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] JabRef-5.x

[David O'Shaughnessy]

On Mon, 24 Feb 2020, at 8:40 AM, Rich Shepard wrote:
> Mario, et al.:
> 
> SBo has version 2.9.2 of JabRef (the bibliographic reference database
> management system) which is so far past its best-used-by date that it has
> mold on it. :-)

JabRef 5.0 has now been released.

--
Dave
___
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] OpenJDK11/openJFX11 and JabRef5.x

[David O'Shaughnessy]

On Mon, 26 Aug 2019, at 7:28 AM, Rich Shepard wrote:
> JabRef-5.x requires JDK11. Oracle has split this into parts so the JavaFK
> part is now a separate package. A JabRef dev confirmed that it will run with
> openjdk11 and openjfx11. The SBo repository has a zulu-openjdk11-11.0.1-lts
> package, but the only openjfx package is version 8.
> 
> My request of the maintainers is to provide an openjfx package compatible
> with the zulu-openjdk-11.0.1 package, or any other openjdk11/openjfx11 pair,
> so JabRef on SBo can be upgraded from it's current very old version to 5.x.

The new beta version of JabRef 5 now bundles its own Java:
https://github.com/JabRef/jabref/releases

I can confirm that it runs on 14.2 as is (I extracted it to /opt/JabRef).

--
Dave
___
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] anyone have LukenShiro email address?

[David O'Shaughnessy]

Just out of interest, there's also jdupes  
which claims to have a big speed increase over fdupes (not a drop-in 
replacement though, commandline switches are different). 

--
Dave

On Sat, 1 Feb 2020, at 3:21 PM, Fernando Lopez wrote:
> thank you. ill take that one!
> 
> On Sat, Feb 1, 2020 at 4:21 PM Willy Sudiarto Raharjo 
>  wrote:
>> > i would like to request fdupes update...
>>  > 
>>  > this one is not working:
>>  > lukenshiro%20at%20ngi%20dot%20it
>> 
>>  If you are willing to step up as maintainer, please feel free to take
>>  his scripts.
>> 
>> 
>>  -- 
>>  Willy Sudiarto Raharjo
>> 
>>  ___
>>  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/
>> 
> 
> 
> -- 
> 
> 
> Regards,
>  Fernando Lopez Jr.
> ___
> 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/

Re: [Slackbuilds-users] building packages

[David O'Shaughnessy]

On Fri, 10 Jan 2020, at 12:42 PM, Ruben Schuller wrote:
> I'm interested in what you use to build packages and how you do it.
> I currently use slackrepo [1] for this. It seems to be a bit abandoned
> now, a pull request I've made 2018 wasn't reacted upon. So I'm kind-of
> looking for a replacement.

Just sbotools. It's command-line driven, supports stable or -current, resolves 
dependencies but you keep control of what's happening. I like it.

> Where you build packages is also of interest, somewhere on at home or
> on a rented server?

Home machine, nothing special.

--
Dave
___
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] Unmaintained builds - want any of these?

[David O'Shaughnessy]

On Thu, 2 Jan 2020, at 8:38 AM, David O'Shaughnessy wrote:
> 
> I didn't see anything in the list that I use, but I think office/org-mode can 
> just be dropped since org is included in Emacs by default now:
> 
> https://orgmode.org/manual/Installation.html
> 

I see network/tramp is in the list too, that one is also redundant by now since 
it's been bundled in Emacs since version 22:
https://www.gnu.org/software/tramp/#Installation

--
Dave___
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] Unmaintained builds - want any of these?

[David O'Shaughnessy]

On Thu, 2 Jan 2020, at 12:41 AM, Robby Workman wrote:
> TL;DR version: if you would like to see any of the scripts on the
> following list stay around, please step up to maintain them.
> 
> https://slackbuilds.org/DeadSBoBuilds
> 

I didn't see anything in the list that I use, but I think office/org-mode can 
just be dropped since org is included in Emacs by default now:

https://orgmode.org/manual/Installation.html

--
Dave___
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] apg-2.2.3 automated password generator

[David O'Shaughnessy]

On Wed, 20 Nov 2019, at 9:33 AM, Jude DaShiell wrote:
> One improvement that could be done to all of these password generators
> is to make sure every password starts with a letter and ends with a
> letter.  That makes passwords more difficult by a little to crack.  The
> reason for that is mathematics.  Numbers and special symbols have a set
> size of 42 32 special symbols and 10 digits.  Letters have a set size of
> 52 all lower-case and upper-case and the underscore.

It's hard to understand the logic of that:

a = 42 (numbers/symbols)
b = 52 (letters)
c = a + b = 94

a < b < c

So, draw from c.

--
Dave
___
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] signal-desktop: MD5sum problem

[David O'Shaughnessy]

On Sun, 15 Sep 2019, at 5:31 AM, Willy Sudiarto Raharjo wrote:
> it has been fixed in my branch since yesterday
> people need to look on the git page :)
> https://slackbuilds.org/ready/

Thanks, didn't know about that link.

--
Dave___
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] signal-desktop: MD5sum problem

[David O'Shaughnessy]

Yeah it's wrong, someone reported this in another thread too. I assume it will 
be fixed the next update. Upstream is:

https://updates.signal.org/desktop/apt/pool/main/s/signal-desktop/signal-desktop_1.27.2_amd64.deb

And the correct MD5 is 21d439b48746ac81c857c21228c37224

--
Dave

On Sun, 15 Sep 2019, at 8:01 AM, Eduardo Sanchez wrote:
> Hi there, I'm using -current but post here since I guess this is a
> broad problem.
> 
> The stated and the downloaded MD5sums for signal-desktop do not match:
> 
> > 019-09-15 10:58:47 (142 KB/s) - ‘signal-desktop_1.27.2_amd64.deb’
> > saved [85528588/85528588]
> > 
> > Found signal-desktop_1.27.2_amd64.deb in /var/cache/sbopkg.
> > Checking MD5SUM:
> > MD5SUM check for signal-desktop_1.27.2_amd64.deb ... FAILED!
> > Expected: c097682d171ba4d8ae9151bf8ac7c9db
> > Found: 21d439b48746ac81c857c21228c37224
> > 
> > Do you want to use the downloaded signal-desktop source:
> > signal-desktop_1.27.2_amd64.deb in /var/cache/sbopkg?
> 
> 
> Best regards,
> 
> 
> Eduardo
> 
> -- 
> Eduardo Sánchez Gauto, Abog., Th.M.
> Abogado - Traductor Público Matriculado Inglés - Español
> Oficina: https://goo.gl/maps/mccgBNM7Zw32
> Web: http://sombragris.org - Blog: http://shadow.sombragris.org
> TW: @thegreyshadow - FB: /thegreyshadow - 
> Teléfono: (0991) 755-355 - Asunción, Paraguay 
> ==
> 
> ___
> 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/

Re: [Slackbuilds-users] Updates - 20190914.1

[David O'Shaughnessy]

Sorry, I forgot to update it. It should be:

21d439b48746ac81c857c21228c37224

For verification upstream is:
https://updates.signal.org/desktop/apt/pool/main/s/signal-desktop/signal-desktop_1.27.2_amd64.deb

--
Dave

On Sat, 14 Sep 2019, at 1:18 AM, Cristiano Urban wrote:
> Hi, 
> there is a wrong md5sum in signal-desktop. I noticed it because sbotools 
> complains about it during download. 
> 
> Il 14 set 2019 2:52 AM, Willy Sudiarto Raharjo  ha 
> scritto:
> 
>> 

>> Sat Sep 14 04:59:07 UTC 2019 
>> academic/Gridcoin-Research: Updated for version 4.0.5.0. 
>> academic/STAR: Updated for version 2.7.2b. 
>> academic/ViennaRNA: Updated for version 2.4.14. 
>> academic/gwyddion: Updated for version 2.54. 
>> academic/locarna: Updated for version 1.9.2.3. 
>> academic/zotero: Updated for version 5.0.73. 
>> audio/mixxx: Added the dependency libmodplug. 
>> audio/pasystray: Updated for version 0.7.1. 
>> desktop/lumina: Updated for version 1.5.0. 
>> desktop/notion: Update HOMEPAGE url. 
>> desktop/tint2: Updated for version 16.7 + maintainer. 
>> desktop/wmbattery: Added (Laptop Battery Status). 
>> development/PhpStorm: Updated for version 2019.2.1. 
>> development/dart: Updated for version 2.5.0. 
>> development/google-go-lang: update to go1.11.9 
>> development/hub: Updated for version 2.12.4. 
>> development/perf: Updated for version 4.4.190. 
>> development/pycharm: Updated for version 2019.2.2. 
>> development/vscode-bin: Updated for version 1.38.1. 
>> games/ags: New maintainer 
>> games/assaultcube-reloaded: Updated for version 2.7. 
>> games/gargoyle: New maintainer 
>> games/warzone2100: Updated for version 3.3.0 
>> gis/opencpn-plugin-oesenc: Updated for version 3.3.0. 
>> gis/rasterio: Updated for version 1.0.27. 
>> graphics/dcraw: Update DOWNLOAD url. 
>> graphics/draw.io: Updated for version 11.2.5. 
>> ham/tqsl: Updated for version 2.4.7. 
>> libraries/DevIL: New maintainer 
>> libraries/PDCurses: Updated for version 3.8. 
>> libraries/dav1d: Add sed magic. 
>> libraries/enchant2: Updated for version 2.2.7. 
>> libraries/libcbor: Added (Schema-less binary data format). 
>> libraries/libmirage: Updated for version 3.2.3. 
>> libraries/libpqxx: Updated for version 6.4.5. 
>> libraries/libqb: Updated for version 1.0.5. 
>> libraries/libuv: Updated for version 1.32.0. 
>> libraries/libversion: Updated for version 2.9.1. 
>> libraries/ntl: Updated for version 11.3.4. 
>> misc/mosquitto: Updated for version 1.6.5 
>> multimedia/cinelerra: Fix DOWNLOAD url. 
>> multimedia/flashplayer-plugin: Updated for version 32.0.0.255. 
>> multimedia/pepperflash-plugin: Updated for version 32.0.0.255. 
>> network/SpiderOakONE: Added (backup system). 
>> network/TeamSpeak3: Updated for version 3.3.2. 
>> network/createrepo_c: Added (rpm repository metadata generator). 
>> network/emailrelay: Updated for version 2.0.1. 
>> network/httpie: Updated for version 1.0.3. 
>> network/nordvpn: Updated for version 3.3.1-3. 
>> network/open-iscsi: Patched to build on current. 
>> network/signal-desktop: Updated for version 1.27.2. 
>> network/skypeforlinux: Updated for version 8.51.0.92. 
>> network/telegram: Updated for version 1.8.8. 
>> network/tixati: Updated for version 2.63_1. 
>> network/wireshark: Updated for version 3.0.4. 
>> network/you-get: Updated for version 0.4.1347. 
>> office/calibre-bin: Updated for version 3.48.0. 
>> office/gnucash-docs: Updated for version 3.7. 
>> office/gnucash: Updated for version 3.7. 
>> office/lumina-calculator: Added (Scientific Calculator). 
>> office/lumina-pdf: Added (PDF Viewer). 
>> office/pdfstudio: Updated for version 2019.1.3. 
>> office/pdfstudioviewer: Updated for version 2019.1.3. 
>> office/zim: Fix DOWNLOAD url. 
>> office/zim:Updated for version 0.72.0. 
>> perl/perl-B-Hooks-EndOfScope: Updated for version 0.24. 
>> perl/perl-Clone: Updated for version 0.42. 
>> perl/perl-Moose: Updated for version 2.2011. 
>> perl/perl-Scalar-List-Utils: Updated for version 1.52. 
>> perl/perl-Scope-Upper: Updated for version 0.32. 
>> perl/perl-Test-CleanNamespaces: Updated for version 0.24. 
>> perl/perl-Test-Needs: Added (Perl module). 
>> python/pygame: Updated for version 1.9.6. 
>> python/pyglet: Updated for version 1.4.4. 
>> python/ruffus: Updated for version 2.8.3. 
>> python/thonny: Updated for version 3.2.1. 
>> system/aide: Add more parameters. 
>> system/asbt: Updated for version 2.0.0. 
>> system/cdemu-client: Updated for version 3.2.3. 
>> system/cdemu-daemon: Updated for version 3.2.3. 
>> system/ck4up: Added (Monitor Web Pages). 
>> system/gcdemu: Updated for version 3.2.3. 
>> system/netdata: Updated for version 1.17.1. 
>> system/nvidia-driver: Updated for version 430.50. 
>> system/nvidia-kernel: Updated for version 430.50. 
>> system/nvidia-legacy340-kernel: Updated for version 340.107. 
>> system/nvidia-legacy340-kernel: Updated for version 340.107. 
>> system/openrc-services: Updated for version 20190907. 
>> system/pspg: Updated for version 2.0.1. 
>> 

Re: [Slackbuilds-users] SOHO backup choices

[David O'Shaughnessy]

On Tue, 10 Sep 2019, at 7:41 AM, Rich Shepard wrote:
> The two packages that look appropriate for my SOHO needs (and I didn't look
> at all of them) are flexbackup and Attic. Both do daily incremental backups
> for single hosts or small LANs. Should I install and learn both to support a
> choice or might there be others for me to consider?

I've been happy with Borg for the past 5 years or so (it's the active version 
of Attic these days). 

https://www.borgbackup.org/

--
Dave
___
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] Feature request: add $NUMJOBS to SBo build scripts

[David O'Shaughnessy]

On Tue, 23 Jul 2019, at 12:04 PM, Fellype wrote:
> Dear SBo Admins,
> 
> Is it possible to add the $NUMJOBS variable to SBo build scripts by default? 
> At least for the next Slackware release?

I think that this can be more reliably handled by the user's interface to SBo. 
For example, sbotools lets you set JOBS in /etc/sbotools.conf (the value of 
which is passed to make's "-j" argument).

--
Dave___
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] gnucash 3.6

[David O'Shaughnessy]

Anyone having trouble building gnucash 3.6 after the latest updates on 
-current? I'm getting a failure on configure:

> -- Performing Test have_mod_mask
> -- Performing Test have_mod_mask - Success
> CMake Error at gnucash/register/register-gnome/CMakeLists.txt:4 
> (check_symbol_exists):
>  Unknown CMake command "check_symbol_exists".
> 
> -- Configuring incomplete, errors occurred!

___
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 - 20190427.1

[David O'Shaughnessy]

On Sun, 28 Apr 2019, at 2:17 PM, Cristiano Urban wrote:
> Hi, 
> there is an issue with the download URL for signal-desktop. The file seems to 
> be not present at the location pointed by that URL.
> 

I forgot to mirror the file, fixed now :)

--
Dave___
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

[David O'Shaughnessy]

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 :)

--
Dave
___
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] vlc slackbuild

[David O'Shaughnessy]

On Thu, 21 Feb 2019, at 3:38 PM, Lenard Spencer wrote:
> It's happening with me as well. I'll post a log as soon as I can.

Odd, I just re-built VLC on 14.2_64 and it runs without problem. Might be 
something to do with certain build options?

--
Dave___
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 - 20190217.1

[David O'Shaughnessy]

On Sun, 17 Feb 2019, at 7:07 AM, Willy Sudiarto Raharjo wrote:
> sorry for the delay for this batch, due to some real life work :)

No need to apologize Willy, thanks for your efforts :)

--
Dave___
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 (RPM's) runtime failure

[David O'Shaughnessy]

On Mon, 11 Feb 2019, at 4:08 PM, Duncan Roe wrote:
> I am getting the following error:
> 
> > 11:01:56$ libreoffice6.2 ~/calendar.ods
> > /opt/libreoffice6.2/program/soffice.bin: symbol lookup error: 
> > /opt/libreoffice6.2/program/libvclplug_gtk3lo.so: undefined symbol: 
> > gdk_wayland_display_get_type
> 

For your environment (~/.bash_profile, etc) you need: 
export SAL_USE_VCLPLUGIN=gtk

Or you can source it from: /etc/profile.d/libreoffice.sh

--
Dave
___
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] Chromium in Slackbuilds

[David O'Shaughnessy]

On Fri, 14 Dec 2018, at 5:44 PM, JCA wrote:
> The version of the Chromium from Slackbuilds is 53, whereas the latest is 71. 
> I.e. 53 is well over two years old. Why is it being kept that old, especially 
> bearing in mind that Slackware packages for the latest Chromium may be 
> downloaded from http://www.slackware.com/~alien/slackbuilds/chromium. I mean, 
> what is the point of keeping such an old version in Slackbuilds?

Hard to say, I also think that it should be dropped. For many packages it seems 
quite alright to be behind the latest version, but I don't think a web browser 
is one of those packages (security comes to mind).

--
Dave___
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] borgbackup msgpack-python problem

[David O'Shaughnessy]

I'm having trouble with borgbackup on 14.2_64. Here's the error message
upon running borg init .
> Traceback (most recent call last):
>   File "/usr/bin/borg", line 6, in 
> from pkg_resources import load_entry_point
>   File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py",
>   line 3088, in > @_call_aside
>   File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py",
>   line 3072, in _call_aside> f(*args, **kwargs)
>   File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py",
>   line 3101, in _initialize_master_working_set> working_set = 
> WorkingSet._build_master()
>   File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py",
>   line 574, in _build_master> ws.require(__requires__)
>   File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py",
>   line 892, in require> needed = 
> self.resolve(parse_requirements(requirements))
>   File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py",
>   line 778, in resolve> raise DistributionNotFound(req, requirers)
> 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?
--
Dave
___
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] Drop package (riot-web)

[David O'Shaughnessy]

Hi, I'd like to drop riot-web from the repo (unless someone else wants
to take over for it). There's some weird bug in the 0.17.0 branch which
stops the program from loading under some strange conditions (and which
didn't turn up on my system until just recently), and I don't really
have time for it.

--
Dave
___
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] Legacy Signal-Desktop to be retired

[David O'Shaughnessy]

Just a heads up that the Signal-Desktop SlackBuild (not signal-desktop)
will no longer work after 15th Nov 2018:

> After 380 days of extended support, the legacy Chrome version of
> Signal Desktop will stop working on November 15, 2018. The new
> standalone version of Signal Desktop is available now, and it has
> received regular updates in the past year -- including numerous
> feature enhancements and significant performance improvements.

https://github.com/signalapp/Signal-Desktop/releases/tag/v0.47.0

There's a built-in tool in the final release (0.47.0) to migrate from
legacy to the new stand-alone version (the signal-desktop binary
SlackBuild). So Signal-Desktop should probably be updated and the README
too to reflect the situation.

I've cc'd the maintainer.

--
Dave
___
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] MD5 hash sums

[David O'Shaughnessy]

On 08/23/2018 03:45 PM, T3 slider wrote:
> The download files do not necessarily have to be tar archives, and in
> some cases (generally those with multiple download files and therefore
> multiple checksums), individual files can be included for download.
> Intentional PDF collisions have been around for ages
> (see https://www.mscs.dal.ca/~selinger/md5collision/
>  ), so if a
> SlackBuild includes some documentation as a download link, and the
> upstream server has since been compromised, a user could definitely be
> stuck with a malicious file even if the SlackBuild maintainer did
> everything right and verified upstream signatures. It is probably more
> difficult to generate tarballs with collisions but I'm guessing it isn't
> quite as difficult as we're pretending it is, and it's irrelevant since
> unzipped files can be passed as download links.

I don't see how this works if each individual download (either archive
or single uncompressed file) has its own MD5. My understanding of
collisions is that one can easily create two differing files with
matching MD5 sums (so the original innocuous file A plus a malicious new
file B), but that this necessarily creates a new (shared) MD5 sum. If
the target MD5 is given beforehand (i.e., the one(s) in the info file),
then a preimage attack is required which is impractical.

> 
> Simply put, this is bad security. Anyone who disagrees doesn't
> understand the problem. Can't we just add an optional sha256sum in the
> .info file and maintainers can gradually add these checksums to their
> SlackBuilds, targeting some point in the future that these fields will
> be required (and possibly the md5s retired)?

An optional sha256sum field seems reasonable to me.

--
Dave
___
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] MD5 hash sums

[David O'Shaughnessy]

On 08/23/2018 12:55 AM, t...@airmail.cc wrote:
> Sorry, the question I had in mind was about MD5 sums inside it. Seems
> kind of strange that SlackBuild archive is protected by GPG signature,
> but the actual source tarball is not signed and is protected by
> (obsolete) MD5 checksum. Aren't this situation an opportunity to MITM
> the source tarball itself, since some DOWNLOAD links are provided trough
> plain HTTP?

Let's say the user has a SlackBuild + .info file, both of which have
been signed by the SBo dev team and are authentic (thus including the
MD5). The assumption here is that the maintainer actually checks
signatures upon downloading (and that upstream devs even sign in the
first place), so the stuff in the .info is "safe".

Now the user goes to download the source listed in .info, and unbeknown
to them it has been maliciously tampered with (either on the server or
MITM, so either TLS or not, it doesn't matter). The MD5 of that altered
archive will not match the authentic MD5 found in the .info file. For an
attacker to change the upstream source archive without changing the MD5
requires a 2nd preimage attack, which as far as I understand is not
computationally feasible at present. This is different to a much simpler
collision attack, where the attacker generates two _new_ archives with
new (and matching) MD5s.

So, as long as SlackBuild maintainers are actually verifying the
signatures on source archives and not blindly trusting checksums (of any
variety) published on upstream websites, then using MD5 in this way
seems OK. That said, I do think that it would be safer practice to just
use a stronger hash function anyway (https://blake2.net/ ?), as things
can change suddenly (who knows what's around the corner).

--
Dave
___
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] MD5 hash sums

[David O'Shaughnessy]

On 08/21/2018 09:32 PM, t...@airmail.cc wrote:
> Hello.
> 
> I have a question about DOWNLOAD and MD5SUM variables in the
> .info files.
> 
> As this page https://www.gnupg.org/faq/weak-digest-algos.html states:
> 
>> It is better to entirely avoid the MD5 algorithm and don't put any
>> value in signatures based on MD5.
> 
> Would that be a valid concern for the .info files?
> 
> A lot of DOWNLOAD links are plain http ones and thus are suspectible to
> MITM tinkering on the ISP side...

Each SlackBuild archive is signed by the SBo devs, so any modifications
on the server (or in-between) would fail subsequent verification. In
that case it's the GPG signature that you trust to verify the .info file
contents (and all the rest of the SlackBuild stuff), not the MD5 sum or
whatever else is inside it.

--
Dave
___
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] Retire MD5 for SHA256

[David O'Shaughnessy]

On 08/22/2018 12:46 AM, David O'Shaughnessy wrote:
> The problem then is that the MD5 cannot guarantee that a given (future)
> source archive is identical to the one that the maintainer originally
> downloaded, and that the SBo admin signed off on. Obviously though if
> the attacker has access to the upstream signing keys then it's busted
> from the start and the whole checksum thing is irrelevant anyway.

I've been doing some more reading on this and the scenario of an
attacker changing a file without the MD5 also changing is actually a 2nd
preimage attack (not a collision), and everything I've looked at says
that this is computationally infeasible using current methods. Therefore
it seems that an authentic (signed) MD5 is not broken as a file
verification method. Still, I think that switching to a stronger hash
function would be good long-term insurance.

--
Dave
___
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] Retire MD5 for SHA256

[David O'Shaughnessy]

On 08/10/2018 05:24 PM, B Watson wrote:
> This comes up from time to time... I personally am not opposed to it,
> theoretically it's a good idea, but it'd be a good bit of work for
> everyone (admins, maintainers, even users would be impacted).
> 
> What might be feasible: have each maintainer GPG sign the source files
> and include detached signatures (.asc) in the SlackBuild directory.
> Would require a way for users to get the maintainers' public keys,
> but there are public keyservers (and we could do the 'web of trust'
> thing by signing each others' pub keys).
> 
> The .info file format wouldn't have to change at all. We'd just start
> having one or more small .asc files included with the builds. Automated
> tools could check for them and verify the signatures after the download.
> If there's no signature, it would just say so, and continue the build.
> 
> Doing it this way puts the burden on the individual SlackBuild maintainers
> instead of adding *yet more* work to the admins' workload, and it'd stay
> backwards compatible...
> 
> Now that I think of it, this isn't at all my idea, someone on IRC was
> talking about it. Are you the same person? If so, congratulations, you
> sold me on the idea well enough that now I'm trying to sell it back to
> you :)

I wasn't the one who suggested this, but it seems like a pretty
reasonable solution!

--
Dave
___
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] Retire MD5 for SHA256

[David O'Shaughnessy]

On 08/10/2018 11:24 PM, Tim Dickson via SlackBuilds-users wrote:
> my 2cents worth...
> if it aint broke...
> well, the argument is that it is broke, but... using hash collisions 
> means either the source can be compromised, in which case it is not
> reliable, or the compromise is done on the network, in which case the
> network is not reliable.
>  If either network or source are not reliable, then the expected
> checksum - whatever method used could simply be set to match the
> interfered-with source code, so the attacker would not need to "crack"
> the checksum, they could just make what was visible match their version
> of the compromised source.

If SBo maintainers are generating authentic MD5 checksums in the first
place (i.e., GPG verifying the upstream signatures, assuming that they
exist), and SBo admins are then signing off on those checksums, then it
seems unlikely that an attacker could modify the source and the expected
checksums too. However, a subsequent malicious alteration that utilizes
hash collisions (which would seem to be an ideal situation for an
attacker, short of gaining access to signing keys) is undetectable since
the SBo user, in the end, is left with only an MD5 sum as their link to
archive integrity.

The problem then is that the MD5 cannot guarantee that a given (future)
source archive is identical to the one that the maintainer originally
downloaded, and that the SBo admin signed off on. Obviously though if
the attacker has access to the upstream signing keys then it's busted
from the start and the whole checksum thing is irrelevant anyway.

> In other words, as a basic download file corruption check, md5 is simple
> and convenient; any other assumptions about security depend on other
> variables far more than the type of checksum used.

True, it's convenient for that and there are many other variables, but
having the user rely on MD5 still seems like an unnecessary weak spot to me.

--
Dave
___
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] signal-desktop

[David O'Shaughnessy]

On 08/21/2018 04:22 PM, B Watson wrote:
> On 8/20/18, David O'Shaughnessy  wrote:
>> Do I need to do anything else after uploading an archive
>> to the sbodirectlinks site?
> 
> Yes. Actually change the download link in the .info file to point to
> the sbodirectlinks URL. Not much point uploading it there, otherwise...

Ah right, I misunderstood how it all works then. I thought there was
some kind of script running that archived stuff from sbodirectlinks to
sbosrcarch in case of failed downloads from upstream. I'll amend the
links then.

--
Dave
___
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] signal-desktop

[David O'Shaughnessy]

On 08/21/2018 05:20 AM, B Watson wrote:
> signal-desktop doesn't keep old versions, so the download link keeps
> breaking... but someone packages it for gentoo, so you could use their
> distfiles server as the download link in your .info file.

I noticed this problem and have been uploading archives to the
sbodirectlinks site (also for riot-web), but they didn't seem to be
propagating down to sbosrcarch for some reason.

I can see that signal-desktop_1.15.4_amd64.deb is on sbosrcarch now, but
I'm not sure if that was manual or it propagated from my upload to
sbodirectlinks. Do I need to do anything else after uploading an archive
to the sbodirectlinks site?

--
Dave
___
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] Retire MD5 for SHA256

[David O'Shaughnessy]

Hi everyone, since SBo relies on maintainers to individually verify the
authenticity of source archives (i.e., check the signature and provide a
checksum), the user's link to upstream verification rests on the SBo
published checksum. Given that MD5 is badly broken, would it not be more
prudent to publish a SHA256 instead?

I understand that MD5 is useful for checking for unintentionally
corrupted downloads, but it seems to leave open the possibility for a
subsequently maliciously altered archive (i.e., one that uses hash
collisions to produce the same MD5, but which would fail a GPG signature
check).

Perhaps something to consider for the 15.0 set?

https://en.wikipedia.org/wiki/MD5
http://www.stopusingmd5now.com/home

--
Dave
___
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] bad downloads, courtesy of sbosrcarch

[David O'Shaughnessy]

On 07/23/2018 03:57 PM, B Watson wrote:
> However, you could get yourself a sourceforge account and get added
> to the slackbuildsdirectlinks project, upload files that way. Not sure
> who's in charge of that (it isn't me) but it's someone on this list who
> will likely be replying to this message soon :)

This would be very handy, I'll sign up for a SourceForge account if
someone from SlackBuilds Direct Links could fill me in on what exactly I
need to do with it. My riot-web SlackBuild could also benefit from some
caching (new releases tend to come quite quickly, and disappear quickly
too!).

--
Dave
___
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] bad downloads, courtesy of sbosrcarch

[David O'Shaughnessy]

On 07/15/2018 06:06 PM, B Watson wrote:
> 404 Not Found:
> 
> network/signal-desktop

Ok thanks. They don't normally remove release files, but they must have
pulled 1.14.0 for some reason. The current version is 1.14.1 and I've
submitted an update for that.

> The entire website for signal-desktop's download
> (https://updates.signal.org/) is messed up, and I can't find the file
> elsewhere. Actually... why is signal-desktop using a .deb? There's
> source here:
> 
> https://github.com/signalapp/Signal-Desktop/releases
> 
> Is it one of those that's a bear to build, like palemoon or qt5?

I sync the binary releases to my machine using apt-mirror (from SBo). As
for building from source, last time I looked there weren't any clear
instructions for it, but if anyone wants to have a go, feel free.

--
Dave
___
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] [OT] Screen grabber ?

[David O'Shaughnessy]

On 06/27/2018 01:05 AM, Xavier Maillard wrote:
> I am debugging a tool which does not react correctly when trying to
> interrupt it. The project owner would like me to give him 1) the way
> to reproduce the problem and 2) a "screenshot".
> 
> I tried to look for a tool from the SBo repository but as far as I
> know, there is not such tool.

scrot is another option on SBo if you like command line stuff.

--
Dave
___
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] Rebuilding all SBo packages on new system

[David O'Shaughnessy]

On 06/08/2018 03:11 AM, Rich Shepard wrote:
> On Thu, 7 Jun 2018, Jeremy Hansen wrote:
> 
>> Sounds like David Spencer's slackrepo would be ideal for your situation.
>> http://idlemoor.github.io/slackrepo/
> 
> Jeremy,
> 
>   Thank you. I'll get a copy and learn how to use it.
> 
> Best regards,
> 
> Rich

I would get the list of packages from the old machine:
packages=$(ls /var/log/packages/*_SBo | cut -d'/' -f5 | rev | cut -d-
-f4- | rev)

and then feed that into slackrepo on the new machine:

slackrepo build $packages
(or slackrepo install if you want to install everything).

If there are any build customisations you've made then it would be
worthwhile looking at the HINTFILE system that slackrepo uses. A default
set for slackrepo can be found at:

https://github.com/idlemoor/slackrepo-hints

--
Dave
___
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 is sorely in need of an update

[David O'Shaughnessy]

On 06/04/2018 07:15 PM, Harald Achitz wrote:
> If it doesn’t work with 5.9.x than it has a problem and is not worth
> using it
> 
> On Mon, 4 Jun 2018 at 06:15, David Woodfall  > wrote:
> 
> On Sunday 3 June 2018 20:05,
> Harald Achitz  > put forth the proposition:
> > please do not got to an other developer version (5.10.x, 5.11.x) ,
> use a
> > LTS version, 5.6.x or, better , 5.9.x
> 
> I can see the need for a separate dev version for qutebrowser.
> 

Have to agree with Harald here. The whole ideology of Slackware and SBo
favours stability/reliability over features, and software that won't
compile with an active LTS version of Qt5 would seem to be more hassle
than it's worth.

--
Dave
___
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] firejail

[David O'Shaughnessy]

On 05/19/2018 11:28 PM, Willy Sudiarto Raharjo wrote:

Thanks for reporting

David, can you take this as well, sorry for troubling you again :(



I don't recall being asked to do anything recently :)


Er, I think Willy meant me :)
26 hours since my previous Multiple Dave Correction :)


Yes, i mean David (idlemoor)
Sorry if that confused you :)


No problem, thought it was a bit odd! :P

--
Dave
___
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] firejail

[David O'Shaughnessy]

On 05/19/2018 07:26 AM, Willy Sudiarto Raharjo wrote:

Thanks for reporting

David, can you take this as well, sorry for troubling you again :(



I don't recall being asked to do anything recently :) But if you are 
asking me to take over the Firejail SlackBuild I can do that, otherwise 
all good. Turns out Firefox 60 was a known issue that was fixed with 
profile updates: https://firejail.wordpress.com/support/#firefox60


--
Dave
___
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] firejail

[David O'Shaughnessy]

On 05/18/2018 10:17 PM, John wrote:

firejail chokes on latest firefox-60.0.1


I had a bunch of errors also, bumping Firejail to the latest version 
seems to fix it.


--
Dave
diff --git a/system/firejail/firejail.SlackBuild b/system/firejail/firejail.SlackBuild
index 8219295202..bc569525f9 100644
--- a/system/firejail/firejail.SlackBuild
+++ b/system/firejail/firejail.SlackBuild
@@ -24,7 +24,7 @@
 #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 PRGNAM=firejail
-VERSION=${VERSION:-0.9.52}
+VERSION=${VERSION:-0.9.54}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
diff --git a/system/firejail/firejail.info b/system/firejail/firejail.info
index 6d4152c2b6..31c61d7ff3 100644
--- a/system/firejail/firejail.info
+++ b/system/firejail/firejail.info
@@ -1,8 +1,8 @@
 PRGNAM="firejail"
-VERSION="0.9.52"
+VERSION="0.9.54"
 HOMEPAGE="https://firejail.wordpress.com/;
-DOWNLOAD="https://sourceforge.net/projects/firejail/files/firejail/firejail-0.9.52.tar.xz;
-MD5SUM="5cb973d645acf3d3e80e684e4f4f2d71"
+DOWNLOAD="https://sourceforge.net/projects/firejail/files/firejail/firejail-0.9.54.tar.xz;
+MD5SUM="0ca3bea349cf9b154f3cfa97e6483182"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES=""
___
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] Build failure: gnucash 2.6.19

[David O'Shaughnessy]

On 04/01/2018 06:00 PM, King Beowulf wrote:
> Did you first remove/uninstall the older version? Seems gnucash compile
> can fail otherwise.  This was mentioned in this list a year or so ago.

Thanks, that was the problem. The build completes when the old version
is removed beforehand.

Btw, it might be worth noting this potential problem in the README?

--
Dave
___
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] Build failure: gnucash 2.6.19

[David O'Shaughnessy]

I'm having trouble building the latest gnucash 2.6.19. The last bit of
error output is:

> libtool: link: gcc -Wdeclaration-after-statement -Wno-pointer-sign 
> -D_FORTIFY_SOURCE=2 -O2 -fPIC -std=gnu99 -Wall -Wunused -Wmissing-prototypes 
> -Wmissing-declarations -Wno-unused -o .libs/gnucash gnucash-bin.o -pthread 
> -Wl,--export-dynamic -pthread  
> ../../src/register/ledger-core/.libs/libgncmod-ledger-core.so 
> ../../src/report/report-gnome/.libs/libgncmod-report-gnome.so 
> ../../src/gnome/.libs/libgnc-gnome.so 
> ../../src/gnome-utils/.libs/libgncmod-gnome-utils.so 
> ../../src/app-utils/.libs/libgncmod-app-utils.so 
> ../../src/engine/.libs/libgncmod-engine.so 
> ../../src/gnc-module/.libs/libgnc-module.so 
> ../../src/core-utils/.libs/libgnc-core-utils.so 
> ../../src/libqof/qof/.libs/libgnc-qof.so 
> ../../src/report/report-system/.libs/libgncmod-report-system.so 
> /usr/lib64/libguile-2.0.so /usr/lib64/libgc.so /usr/lib64/libgthread-2.0.so 
> /usr/lib64/libgmodule-2.0.so /usr/lib64/libgtk-x11-2.0.so 
> /usr/lib64/libgdk-x11-2.0.so /usr/lib64/libpangocairo-1.0.so 
> /usr/lib64/libatk-1.0.so /usr/lib64/libcairo.so
  /usr/lib64/libgdk_pixbuf-2.0.so /usr/lib64/libgio-2.0.so 
/usr/lib64/libpangoft2-1.0.so /usr/lib64/libpango-1.0.so 
/usr/lib64/libgobject-2.0.so /usr/lib64/libglib-2.0.so 
/usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lm -pthread -Wl,-rpath 
-Wl,/usr/lib64/gnucash
> ../../src/register/ledger-core/.libs/libgncmod-ledger-core.so: undefined 
> reference to `gnc_recn_cell_set_read_only'
> collect2: error: ld returned 1 exit status
> make[4]: *** [gnucash] Error 1
> Makefile:700: recipe for target 'gnucash' failed
> make[4]: Leaving directory '/tmp/SBo/gnucash-2.6.19/src/bin'
> Makefile:801: recipe for target 'all-recursive' failed
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory '/tmp/SBo/gnucash-2.6.19/src/bin'
> make[2]: *** [all-recursive] Error 1
> Makefile:578: recipe for target 'all-recursive' failed
> make[2]: Leaving directory '/tmp/SBo/gnucash-2.6.19/src'
> make[1]: *** [all-recursive] Error 1
> Makefile:806: recipe for target 'all-recursive' failed
> make[1]: Leaving directory '/tmp/SBo/gnucash-2.6.19'
> make: *** [all] Error 2
> Makefile:660: recipe for target 'all' failed

I'm building in a proper root shell (with 'su -') and have tried
recompiling all the dependencies, but that doesn't help. Any clues?

--
Dave
___
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/

[David O'Shaughnessy]

On 02/05/2018 04:07 PM, Μιχάλης Μιχαλούδης wrote:
> I had *terrified* with some comments here so I was skeptical before visiting.
> 
> _I like the new site._ It's better for me.
> 
> Thank you guys.

I'm happy with it too, looks like a worthwhile update to me.

--
Dave
___
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] fzf 0.17.1 build failure

[David O'Shaughnessy]

On 11/03/2017 03:03 AM, Willy Sudiarto Raharjo wrote:
>> I don't think that is the problem, since I do all my SBo stuff with "su
>> -" these days (including for google-go-lang). Maybe I am missing
>> something else, but I have no idea what.
> 
> Well, i just tried to build fzf and it went fine
> after installing google-go-lang, have you logged out ?
> this ensures that the new environment is setup correctly in order to
> build fzf
> 

I just tried building fzf in a console (with Ctrl-Alt-F2 to get outside
of X), and it built. Thanks Willy.

--
Dave
___
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] fzf 0.17.1 build failure

[David O'Shaughnessy]

On 11/02/2017 09:46 PM, Willy Sudiarto Raharjo wrote:
> 
> please make sure you use "su -" instead of just regular su when building
> with google-go-lang since it needs to have correct environment variable.
> Other alternative is to log out and re-login before building
> 

I don't think that is the problem, since I do all my SBo stuff with "su
-" these days (including for google-go-lang). Maybe I am missing
something else, but I have no idea what.

--
Dave
___
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] fzf 0.17.1 build failure

[David O'Shaughnessy]

I'm having trouble building fzf 0.17.1 on Slack 14.2. I'm guessing this
has something to do with the google-go-lang dependency (which I've
installed). Some of the fzf errors look like:

> fatal: Not a git repository (or any parent up to mount point /)
> Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
> mkdir -p /tmp/SBo/fzf-0.17.1/gopath/src/github.com/junegunn/fzf
> ...
> gopath/src/github.com/junegunn/fzf/src/util/util.go:8:2: cannot find package 
> "github.com/mattn/go-isatty" in any of:
>   /usr/src/github.com/mattn/go-isatty (from $GOROOT)
>   /tmp/SBo/fzf-0.17.1/gopath/src/github.com/mattn/go-isatty (from $GOPATH)
> ...
> Failures:
>   fzf: fzf.SlackBuild return non-zero

Maybe this has something to do with GOPATH, but I have no idea what it's
meant to be set to. The readme for google-go-lang doesn't seem that
clear to me.

--
Dave
___
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] Very simple way of finding dependency

[David O'Shaughnessy]

On 09/14/2017 06:57 PM, Andreas Guldstrand wrote:
> As the maintainer of sbotools, I also agree, /var/lib/sbo would be a
> better place. It would have been moved there already, except for the
> need to maintain backwards compatibility. Once I manage to put
> together a new major version it'll likely change.

I'd prefer that also, /usr/sbo always struck me as somewhat odd.

--
Dave
___
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] Very simple way of finding dependency

[David O'Shaughnessy]

On 09/14/2017 02:06 AM, Sebastian Arcus wrote:
> Good call - I didn't think of that. I use sbotools. I suppose I could
> grep through /usr/sbo/repo for references to the package I am interested
> in.

I just tried out "Hoorex" (that someone else suggested), and it works well:
# hoorex vlc
# vlc vlsub sopcast-player kaffeine

# hoorex -i vlc
# vlc

By default it shows all the packages in SBo that depend on it, with the
-i flag it restricts the search to installed packages.

--
Dave
___
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] Very simple way of finding dependency

[David O'Shaughnessy]

On 09/13/2017 10:51 PM, Sebastian Arcus wrote:
> Thank you for the suggestion. At the moment I don't have a git clone of
> SBo - and I was hoping there is an easier way to search for a package
> than setting up a git repository :-)

If you use sbotools or sbopkg wouldn't you already have that though? Not
sure where sbopkg puts it, but sbotools has it in /usr/sbo/repo

--
Dave
___
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/