Re: [Slackbuilds-users] Running rxvt-unicode

[Rich Shepard]

On Wed, 27 Mar 2024, marav wrote:


The executable is located here : /usr/bin/urxvt


Marav,

I learned that urxvt was not installed by the 15.0 installer while other xap
applications were. So I cd'd to the file tree and installed it. It's now up
and running.

Thanks very much,

Rich
___
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] Running rxvt-unicode

[Rich Shepard]

On Wed, 27 Mar 2024, B. Watson wrote:


Again, wrong list for this question. Absolutely nothing to do with SBo.
It's not even a Slackware-specific question.


B,

I found the information on the SBo repo.


Most likely, if you just do a google or duckduckgo search for something
like "set default terminal in xfce4", you will be illuminated.


I need to install it first. A new search on the laptop found it was not
installed from the 15.0 ap source. Will fix that.

Thanks,

Rich
___
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] Running rxvt-unicode

[Rich Shepard]

Setting up my laptop with a fully patched 15.0 and multilib. I've used the
urxvt terminal emulated in previous versions and the SBo repo says that rxvt
has been replaced in 15.0 with rxvt-unicode.

I find the file rxvt-unicode in /usr/share/terminfo/r/ but it's not
executable. How do I tell xfce4 to use rxvt-unicode as the terminal
emulator?

TIA,

Rich
___
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] Kernel upgrade question

[Rich Shepard]

On Fri, 22 Mar 2024, j+sbo-us...@maschinengott.de wrote:

Rich, this question has nothing to do with SlackBuilds.org. Please seek help 
elsewhere. (e.g. https://www.linuxquestions.org/questions/slackware-14/)


Well, while not SBo-specific I thought someone here had the answer.

Bye,

Rich
___
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] Kernel upgrade question

[Rich Shepard]

I'm setting up 15.0 on a desktop and need to run rsync_slackware_patches.sh.
Last December there was a kernel upgrade. It's been a very long time since I
last upgraded a kernel and I remember that it should be done manually rather
than allowing the patches upgrade script do it.

What I have forgotten is where there is an upgrade blacklist that will not
download and install kernels when other patches are upgraded by the script.
Please point me to the proper file so I can bring this host, and my laptop,
current with 15.0 patches, and separately the kernel.

TIA,

Rich
___
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] RFC updates for gdal slackbuild

[Rich Shepard]

On Sat, 2 Dec 2023, Greg Tourte wrote:


I have been looking at the gdal slackbuild for version 3.8. I have held off
for now as it had an issue with building when an older version was
installed. Since I reported the issue upstream and a patch has since then
been written, I can now work on it.

The new release is rather trivial although it bumps the shared library
version. However, the current script doesn't really specify most
dependencies and basically relies on what is already installed on the
system. Most other distro packages will build gdal with enforced
dependencies and I am very tempted to change the script to do so as well
(especially now that the circular libspatialite dependency is no longer an
issue).

What do people think. Do any one have any objections?


Greg,

I've always built the stack in this order: proj -> geos -> gdal -> pdal. I
support your suggested change to show required dependencies.

Thanks,

Rich
___
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] wmwebcam: window size [RESOLVED]

[Rich Shepard]

On Fri, 3 Nov 2023, Rich Shepard wrote:


Please advise me how to adjust the wmwebcam window for use on a 24" (or
21") monitor.


Please ignore this request. I built webcam instead and it works better than
wmwebcam did.

Rich
___
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] wmwebcam: window size

[Rich Shepard]

I'm using a 24" monitor. The default wmwebcam window size is 352x288 px.
It's a tiny square that displays one of my eyes and that's about all that
fits in there.

I modified customize.patch by setting the width to 800 and the height to
600, rebuilt, and reinstalled. The display window is the same size.

The customize.patch file notes that non-default sizes require changes to the
source; I assume that's done automatically. Apparently not.

Please advise me how to adjust the wmwebcam window for use on a 24" (or 21")
monitor.

TIA,

Rich
___
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] memtest86 vs memtest86+

[Rich Shepard]

On Thu, 5 Oct 2023, Rich Shepard wrote:


Thank you, B. That's excellent advice and I'll follow it.


Slight discrepancy between the source file number and the SlackBuild script.
The Debian version is 4.6.0-1 while the build script version is 4.6.0_1. I
changed the latter to match the filename.

Regards,

Rich
___
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] memtest86 vs memtest86+

[Rich Shepard]

On Thu, 5 Oct 2023, B. Watson wrote:


You also might want to install memtester. Unlike memtest86 and memtest86+,
it runs as a regular Linux process, meaning you don't have to reboot to
use it.

Its testing can't be as thorough (it can't test the memory that holds the
kernel + its modules for instance), but you can use it for a quick check.
Maybe even run it weekly from cron, if you're worried about flaky DIMMs.


Thank you, B. That's excellent advice and I'll follow it.

Regards,

Rich
___
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] memtest86 vs memtest86+

[Rich Shepard]

On Thu, 5 Oct 2023, J. Milgram wrote:

memtest86 hung just a little way into the test. No problems reported, just 
froze.


memtest86+ ran to the end (and found no problems.) So that's the one I kept. 
And system has been behaving fine.


Judah,

Thanks for sharing. When I re-read both SBo pages more carefully I saw that
the plus version had instructions for installation on EFI systems so that's
what I now have installed. This weekend I'll test both the installed DIMMs
and the new ones.

Regards,

Rich
___
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] memtest86 vs memtest86+ [RESOLVED]

[Rich Shepard]

On Wed, 4 Oct 2023, Rich Shepard wrote:


Looking at the SBo pages for memtest86 and memtest86+ I did not see how
the differ ... if the do so significantly.


Oh, wait! Reading more carefully I see the + version has installation
instructions for ELILO systems. That's me.

Rich
___
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] memtest86 vs memtest86+

[Rich Shepard]

Earlier this week my main desktop server/workstation hung about 01:00 and
needed to be rebooted. Twice (Sunday and Monday.) Yesterday and today it
stayed up as usual overnight.

I have replacement DIMMs but want to test the installed set first.

Looking at the SBo pages for memtest86 and memtest86+ I did not see how the
differ ... if the do so significantly.

I'd like recommendations for which one to build, install, and run.

TIA,

Rich
___
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] Happy 30 years Slackware !

[Rich Shepard]

On Mon, 17 Jul 2023, Dimitris Zlatanidis wrote:


Happy Birthday Slackware!

Thank you, Patrick!


+1

Rich
___
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] Brave-browser issues

[Rich Shepard]

On Wed, 24 May 2023, phala...@komputermatrix.com wrote:


Hi Rich, I maintain the SBo build of Brave and I can't understand what
you're describing.

The version on SBo is 1.51.118 which is (today) the current stable
release. The download links are ok, and once installed, the "about" window
shows the correct version. The version numbers match in the *info and
*SlackBuild files.


Andrew,

Thank you. I just upgraded the browser.

Regards,

Rich
___
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] Brave-browser issues

[Rich Shepard]

My desktop server/workstation (running -14.2 on an AMD Ryzen CPU) has
brave-browser-1.44.121-1 installed. It's stable, fast, and there are only a
very few sites it cannot fully access (but firefox can). When I download a
SBo package I can get both the build script .tar.gz and the source .rpm one
after the other.

My laptop (running -15.0 on an Intel i5 CPU) has brave-browser-1.50.121-1
installed while the SBo repo shows version 1.50.118-1 so I cannot tell you
why the downloaded version is newer than the one now listed there.

The laptop version stopped downloading the source files after the build
script tarball until I renewed the page. Can't figure out why.

Today, I tried to access github.com on the laptop and brave couldn't find
it. When I opened the firefox browser I had no issue accessing github.com.
And I have no issues accessing github.com using the brave-browser on the
desktop.

I'm curious if anyone else has experienced different behaviors with
brave-brower on different hosts.

Rich
___
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 TeXLive 2023

[Rich Shepard]

On Tue, 23 May 2023, Erich Ritz via SlackBuilds-users wrote:


Rich, building -current's texlive on 15.0 will fail:


Erich,

As I discovered.


I suggest you spend your efforts on finding why your document won't
compile using texlive 2021, rather than trying to get texlive 2023 working
on Slackware 14.2/15.0. Next suggestion would be to run Slackware-current
in a VM.


That's what I've been trying to do. The previous version had no issues, but
the regulator wants it to follow their specific format. That change broke
the build.

Thanks,

Rich
___
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 TeXLive 2023

[Rich Shepard]

On Tue, 23 May 2023, Rich Shepard wrote:


Well, it won't build in 14.2:
Makefile:977: recipe for target 'bibtexu-bibtex-1.o' failed
make[4]: *** [bibtexu-bibtex-1.o] Error 1
make[4]: Leaving directory '/tmp/texlive-20230311-source/build/texk/bibtex-x'
Makefile:732: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/tmp/texlive-20230311-source/build/texk/bibtex-x'
Makefile:907: recipe for target 'recurse' failed
make[2]: *** [recurse] Error 1
make[2]: Leaving directory '/tmp/texlive-20230311-source/build/texk'
Makefile:478: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/texlive-20230311-source/build/texk'
Makefile:571: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

I'll try it on the 15.0 laptop.


This is strange. On 14.2 it failed finding a Russian bibtex. Now on 15.0 it
fails not finding a different issue.

../../../texk/bibtex-x/bibtex-1.c: In function ‘add_out_pool’:
../../../texk/bibtex-x/bibtex-1.c:333:18: error: ‘UBLOCK_LATIN_EXTENDED_F’ 
undeclared (first use in this function); did you mean ‘UBLOCK_LATIN_EXTENDED_E’?
  333 | case UBLOCK_LATIN_EXTENDED_F:
  |  ^~~
  |  UBLOCK_LATIN_EXTENDED_E
../../../texk/bibtex-x/bibtex-1.c:333:18: note: each undeclared identifier is 
reported only once for each function it appears in
../../../texk/bibtex-x/bibtex-1.c:334:18: error: ‘UBLOCK_LATIN_EXTENDED_G’ 
undeclared (first use in this function); did you mean ‘UBLOCK_LATIN_EXTENDED_E’?
  334 | case UBLOCK_LATIN_EXTENDED_G:
  |  ^~~
  |  UBLOCK_LATIN_EXTENDED_E
make[3]: *** [Makefile:977: bibtexu-bibtex-1.o] Error 1
make[3]: Leaving directory '/tmp/texlive-20230311-source/build/texk/bibtex-x'
make[2]: *** [Makefile:732: all] Error 2
make[2]: Leaving directory '/tmp/texlive-20230311-source/build/texk/bibtex-x'
make[1]: *** [Makefile:478: all-recursive] Error 1
make[1]: Leaving directory '/tmp/texlive-20230311-source/build/texk'
make: *** [Makefile:571: all-recursive] Error 1

Am I missing a dependency in the 15.0 laptop?

Rich
___
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 TeXLive 2023

[Rich Shepard]

On Tue, 23 May 2023, Rich Shepard wrote:


In the -curent texlive build tree there are three subdirectories. In the
texlive subdirectory is the file, texlive.SlackBuild.txt. Am I correct in
assuming that if I remove the terminal .txt and make the script executable
that's what I invoke to build the entire package?


Well, it won't build in 14.2:
Makefile:977: recipe for target 'bibtexu-bibtex-1.o' failed
make[4]: *** [bibtexu-bibtex-1.o] Error 1
make[4]: Leaving directory '/tmp/texlive-20230311-source/build/texk/bibtex-x'
Makefile:732: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/tmp/texlive-20230311-source/build/texk/bibtex-x'
Makefile:907: recipe for target 'recurse' failed
make[2]: *** [recurse] Error 1
make[2]: Leaving directory '/tmp/texlive-20230311-source/build/texk'
Makefile:478: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/texlive-20230311-source/build/texk'
Makefile:571: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

I'll try it on the 15.0 laptop.

Rich
___
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 TeXLive 2023

[Rich Shepard]

On Tue, 23 May 2023, Rich Shepard wrote:


I'll grab the -current build and see if it will build on the 14.2
libraries. If not, I'll have to compile this .lyx document on the laptop.


In the -curent texlive build tree there are three subdirectories. In the
texlive subdirectory is the file, texlive.SlackBuild.txt. Am I correct in
assuming that if I remove the terminal .txt and make the script executable
that's what I invoke to build the entire package?

Regards,

Rich
___
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 TeXLive 2023

[Rich Shepard]

On Tue, 23 May 2023, Arnaud wrote:


Texlive was a SlackBuild on 14.2, maybe you could start from this build
and upgrade it to 2023 ? Or you can also look at slackware's current
sources, get the SlackBuild here, it builds a 2023 package, could be that
it builds on a 15.0 box without further ado.
https://slackware.uk/slackware/slackware-current/source/t/texlive/


Arnaud,

I have 15.0 on my laptop, but 14.2 on the desktop with a larger monitor,
where it's much more comfortable to write.

I'll grab the -current build and see if it will build on the 14.2 libraries.
If not, I'll have to compile this .lyx document on the laptop.

Thanks,

Rich
___
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] Building TeXLive 2023

[Rich Shepard]

TeXLive 2021 is the current version for both Slackware64-14.2 and -15.0. I
have a document that will not build (using pdflatex) on that version, but it
does build on TeXLive 2023. Why this one document won't build is unknown;
Herbert Voss found it built on the 2023 version so he cannot help.

I did not find that version on AlienBOB's web site. I need suggestions on
how I can upgrade TeXLive to the 2023 version so I can provide this document
to my client.

Thanks in advance,

Rich
___
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] orphaned buildscripts

[Rich Shepard]

On Sat, 13 May 2023, Giancarlo Dessì wrote:

I reserve to take some more by the category gis or academic if remaining 
orphaned


I've used grass since 1997 (building from source) and am trying to use qgis.
I could take those with help learning how to maintain packages. I just
downloaded all the templates, yet need to learn how to diagnose and fix
issues when the build doesn't work as expected.

Now my qgis issue is that its plugin manager says the 'grass gis provider'
is installed, but using the qgis browser I cannot navigate to the grass
database to access my project maps.

With your patient understanding of my ignorance, I'll learn how to keep
grass and qgis up to date on the SBo repo.

Rich


___
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] How to add runtime option to application?

[Rich Shepard]

On Fri, 12 May 2023, Rich Shepard wrote:


The qgis version in the SBo repo is far out of date; I just wrote to the
maintainer asking for help compiling the latest version (3.30.2) so it
includes grass gis. The SBo build script has a stanza to include grass as a
compiled-in option, and my script modification didn't work (but I
sucessfully built 3.30.2 yesterday). I want to try adding it as a runtime
option. The command that xfce4 put in the panel launcher is `qgis %F'. Where
on that command line would I put a runtime option, and what is the syntax I
use?


I just learned that qgis is no longer being maintained. I have neither the
knowledge of cmake nor of maintaining a SBo package. I cannot figure out how
to have the build find grass in /usr/local/bin/.

Has anyone offered to resume maitenance of this tool?

Rich
___
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] How to add runtime option to application?

[Rich Shepard]

The qgis version in the SBo repo is far out of date; I just wrote to the
maintainer asking for help compiling the latest version (3.30.2) so it
includes grass gis. The SBo build script has a stanza to include grass as a
compiled-in option, and my script modification didn't work (but I
sucessfully built 3.30.2 yesterday). I want to try adding it as a runtime
option. The command that xfce4 put in the panel launcher is `qgis %F'. Where
on that command line would I put a runtime option, and what is the syntax I
use?

TIA,

Rich
___
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] obs-studio-29.0.0.b3 fails to build

[Rich Shepard]

On Mon, 27 Feb 2023, Christoph Willing wrote:


Looking more carefully at your first email which has your directory
contents, I see that the main tarball is missing. Check the info file
- you also need to wget
https://sourceforge.net/projects/slackbuildsdirectlinks/files/obs/obs-studio-409cfa43357c6296f53dc08e47e032284fc5fba2.tar.gz


chris,

Mea culpa! I didn't read the info file and so didn't recognize that I needed
both tarballs.

My apologies,

Rich
___
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] obs-studio-29.0.0.b3 fails to build

[Rich Shepard]

On Mon, 27 Feb 2023, Christoph Willing wrote:


I'm away from homebase so can't check in depth right now but I think you
have downloaded the DOWNLOAD files instead of DOWNLOAD_x86_64 files.


chris,

I downloaded the SlackBuild (obs-studio.tar.gz) and Source Downloads (64bit):
cef_binary_4638_linux64.tar.bz2 (34fb1c611b3e278ca4d0d1d50e7bfb9b).

Here, in /opt/slackbuilds/Multimedia/obs-studio/ is
cef_binary_4638_linux64.tar.bz2.

But, I agree that the build script appears to see, and use, Source Downloads 
(Arch-Independent):
obs-studio-409cfa43357c6296f53dc08e47e032284fc5fba2.tar.gz 
(7f47a6bef15436341d5108d6125b9ed7)

Thanks,

Rich
___
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] obs-studio-29.0.0.b3 fails to build

[Rich Shepard]

On Sun, 26 Feb 2023, Rich Shepard wrote:


The SlackBuild script is using the commit number rather than the source
directory name:

PRGNAM=obs-studio
VERSION=${VERSION:-29.0.0.b3}
COMMIT=409cfa43357c6296f53dc08e47e032284fc5fba2


Looking further in the build script I find this:

TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}

if [ "$ARCH" = "i586" ]; then
  SLKCFLAGS="-O2 -march=i586 -mtune=i686"
  LIBDIRSUFFIX=""
  CEF_ROOT=cef_binary_101.0.18+g367b4a0+chromium-101.0.4951.67_linux32_minimal
elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
  LIBDIRSUFFIX=""
  CEF_ROOT=cef_binary_101.0.18+g367b4a0+chromium-101.0.4951.67_linux32_minimal
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
  CEF_ROOT=cef_binary_4638_linux64
else
 ...

So it should be using the CEF_RTOOT=cef_binary_4638_linux64 rather than the
commit number.

Rich
___
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] obs-studio-29.0.0.b3 fails to build

[Rich Shepard]

I downloaded and installed a new directory tarball, then downloaded the
64-bit source (cef_binary_4638_linux64.tar.bz2).

When root tries to build it it immediately fails:
# ./obs-studio.SlackBuild 
tar: /opt/slackbuilds/Multimedia/obs-studio/obs-studio-409cfa43357c6296f53dc08e47e032284fc5fba2.tar.gz: Cannot open: No such file or directory

tar: Error is not recoverable: exiting now

The directory contents are: README, obs-studio.info,
cef_binary_4638_linux64.tar.bz2, obs-studio.SlackBuild*, slack-desc

The SlackBuild script is using the commit number rather than the source
directory name:

PRGNAM=obs-studio
VERSION=${VERSION:-29.0.0.b3}
COMMIT=409cfa43357c6296f53dc08e47e032284fc5fba2

How do I fix this?

Regards,

Rich


___
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] Issue building new lyx-2.3.7-1

[Rich Shepard]

On Sat, 7 Jan 2023, B. Watson wrote:


Note that Slackware package version numbers are not allowed to contain the
dash/hyphen character, so whatever you do will have to be a bit fancier
than setting VERSION="2.3.7-1". You'll have to set VERSION to something
like 2.3.7_1 and add a bit of code to the script to look for the tarball
with the - in the name.


Yes, I changed the package name and build script version number to 2.3.7.
There were fatal errors much further in the build process.

Prior versions of lyx used only periods to separate release numbers, and the
build script had no issues with 2.3.6.1 so I assume the problem is in the
tarball.


Also, from your description, this isn't a bug in the script. The upstream
for lyx released a tarball with the wrong directory name inside it (or
anyway, "wrong" compared to how they've done things in the past; it's
their project, they can do what they want).


I'm not on the lyx dev list but I've passed the build error to one of the
lead developers. In the meantime, 2.3.6.1 works just fine for me ... except
it isn't building the index for a KOMA-Script book class document.

Thanks,

Rich
___
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] Issue building new lyx-2.3.7-1

[Rich Shepard]

On Sat, 7 Jan 2023, Μιχάλης Μιχαλούδης wrote:


or better change the version to 3.2.7


That's what I did. It generated errors later in the build so I'll pass the
logs to the lyx devs.

Thanks,

Rich
___
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] Issue building new lyx-2.3.7-1

[Rich Shepard]

The lyx.SlackBuild script has always worked just fine building new versions.
Until today. I downloaded lyx-2.3.7-1.tar.xz and modified lyx.SlackBuild for
that version number.

Running `lyx.SlackBuild` throws and error:
./lyx.SlackBuild: line 46: cd: lyx-2.3.7-1: No such file or directory

That line is:
cd $PRGNAM-$VERSION

which should be found in /tmp/SBo/lyx-2.3.7-1, but the directory is
/tmp/SBo/lyx-2.3.7. The contents of this directory look complete.

All prior minor patch versions used a dot rather than a dash for separation.
I change both the program name and the version in the build file to 2.3.7.1
but that made no difference.

All thoughts welcome,

Rich

___
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 gnumeric-1.2.49 fails to find python3.7

[Rich Shepard]

On Sat, 10 Sep 2022, Petar Petrov wrote:


are you on Chrome?


The browser I use Brave which is based on Chrome.

Thanks,

Rich
___
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 gnumeric-1.2.49 fails to find python3.7

[Rich Shepard]

On Fri, 9 Sep 2022, Erich Ritz wrote:


The 14.2 tree isn't updated but gnumeric is (was) available for it:
https://slackbuilds.org/repository/14.2/office/gnumeric/


Erich,

The source wouldn't download from the 14.2 link.

I upgraded python3 from the 15.0 souce and gnumeric is up and running here.

Thanks,

Rich
___
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 gnumeric-1.2.49 fails to find python3.7

[Rich Shepard]

On Fri, 9 Sep 2022, Erich Ritz wrote:


Slackware 15.0 ships with python 3.9, not python 3.7. Looks like your
custom python 3.7 installation is interfering with the build.


Erich,

Okay. This host is still running 14.2 (for my business needs) and there
isn't a 14.2 gnumeric source file available.

Thanks,

Rich
___
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] Building gnumeric-1.2.49 fails to find python3.7

[Rich Shepard]

Here python3.7 is found in ~/.local/lib/site-packages/, /usr/bin/python3.7m,
/usr/bin/python3.7m-config, usr/bin/python3.7-config, usr/bin/python3.7, and
virtua environments in /usr/lib64/.

Trying to build gnumeric (and goffice is installed) fails:
  CCLD python_loader.la
/usr/lib64/gcc/x86_64-slackware-linux/5.5.0/../../../../x86_64-slackware-linux/bin/ld:
 cannot find -lpython3.7
collect2: error: ld returned 1 exit status
Makefile:557: recipe for target 'python_loader.la' failed
make[3]: *** [python_loader.la] Error 1
make[3]: Leaving directory '/tmp/SBo/gnumeric-1.12.49/plugins/python-loader'
Makefile:504: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/tmp/SBo/gnumeric-1.12.49/plugins'
Makefile:662: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/gnumeric-1.12.49'
Makefile:521: recipe for target 'all' failed
make: *** [all] Error 2

I don't find an error or log file in /tmp/SBo/gnumeric-1.12.49.

Where do I look for the reason for this error?

TIA,

Rich
___
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] Running Office: ReText [RESOLVED]

[Rich Shepard]

On Thu, 1 Sep 2022, Erich Ritz wrote:


Then I typed
retext
at the command prompt and the ReText GUI opened up.  I then opened up 
/usr/doc/libjpeg-turbo-2.1.2/BUILDING.md (using the GUI) and it displays fine.


Erich,

Well, duh! The package and all references show it as ReText so that's what I
entered on the command line. Sigh.

Thanks,

Rich
___
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] Running Office: ReText

[Rich Shepard]

I have ReText installed here, in /usr/lib64/python3.7/site-packages/ReText.
How do I run it to view (and edit) a markdown file?

It doesn't run from the command line and if I start python and load ReText
I've no idea how to view an .md file in a specified directory.

Thanks in advance,

Rich
___
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] Has 15.0 dropped chromium?

[Rich Shepard]

On Sun, 13 Mar 2022, Jeremy Hansen wrote:


Chromium was rarely updated, so it was removed from SBo in 2018.


Jeremy,

I didn't know that.


If you want to continue to use chromium, Alien Bob keeps chromium packages
and his SlackBuild available on his repo.


Yes, and he has an ungoogled-chromium, too.


If you are fine with regular chrome, as already mentioned, Pat makes his
SlackBuild for it available in extra/, or ruario has his excellent
latest-chrome SlackBuild.


I've used chromium on my 14.2 desktop since that firefox version is not
supported by some web sites, mostly financial. I've avoided chrome. I'll use
the brave browser rather than chromium on 15.0.

Many thanks,

Rich
___
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] Has 15.0 dropped chromium?

[Rich Shepard]

On Sun, 13 Mar 2022, Didier Spaier wrote:


You can use on of the versions provided by Eric Hameleers, as mentioned on
his blog: https://alien.slackbook.org/blog/


Didier,

Thank you. I will.

Rich


___
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] Has 15.0 dropped chromium?

[Rich Shepard]

I could not find chromium in an SBo repository and it's not part of the core
distribution. Is it no longer available for use in 15.0?

TIA,

Rich
___
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] Slackbuilds Repository for Slackware 15.0

[Rich Shepard]

On Sat, 12 Mar 2022, Willy Sudiarto Raharjo wrote:


It's now official!!!
SlackBuilds Repository 15.0 is available to the public


Kudos and my thanks to everyone who devoted a lot of time and effort to
reach this point. As an end user who has run his professional services
consultantcy on Slackware since 2003 I am grateful to everyone who makes it
possible.

Stay healthy and prosper,

Rich

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

Re: [Slackbuilds-users] Is there a gnucash*.sbo for 15.0?

[Rich Shepard]

On Thu, 10 Mar 2022, Heiko Rosemann wrote:


yes, there is - from the git master:
https://git.slackbuilds.org/slackbuilds/tree/office/gnucash

The content of that repo will become the 15.0 web repo when it's ready.

I can confirm that gnucash from that repo works on 15.0 (and also updating it 
to 4.9 works when you remove the Changelog file from the documentation copy 
line).


Heiko,

Thanks!

Rich
___
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] Is there a gnucash*.sbo for 15.0?

[Rich Shepard]

Is there a Gnucash available for 15.0?

I don't know where to look other than the SBo web repos.

Rich
___
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] Concerning 15.0 and 14.2

[Rich Shepard]

On Tue, 1 Feb 2022, King Beowulf wrote:


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

Hopefully "real soon now!"


Ed,

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

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

Thanks,

Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@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] updating gis/proj?

[Rich Shepard]

On Fri, 15 Oct 2021, Greg' Ar Tourter wrote:


Rich, this is not really what I am asking.


Greg,

Okay. I didn't fully understand your original post. I incorrectly thought it
was a build sequence issue, not a removed capability that other packages
have not yet accommodated.

Stay well,

Rich
___
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] updating gis/proj?

[Rich Shepard]

On Fri, 15 Oct 2021, Greg' Ar Tourter wrote:


I am trying to update proj to the latest 8.x version after taking
maintainership.
I have tested the new version will all its first level dependees and most
of them compile without any modifications:
- cartopy (taking over as well and updating to 0.20.1 which requires proj
8.x)
- cdo
- gdal
- libgeotiff
- pyproj
- proj-data

however, a couple of the dependees fail to compile as is.
- libspatialite needs to be updated to version 5.x (tested with the latest
5.0.1)
- openorienteering-mapper fails to compile and even updating to the latest
version doesn't help

Should I hold off updating?


Greg' Ar,

I'm not an SBo package maintainer but I offer a thought I learned a long
time ago about the build sequence for spatial analyses packages. Perhaps
it's relavent to your question, perhaps not.

The stack proj -> geos -> gdal need to be built in that order. If proj is
updated then the other two must also be upgraded. If geos is upgraded then
gdal has to be rebuilt. Any other software depending on those need the stack
to be rebuilt before they are.

I've found this is needed with GRASS, R, and SAGA.

Regards,

Rich
___
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?

[Rich Shepard]

On Fri, 15 Oct 2021, David O'Shaughnessy wrote:


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,

I'll learn how to do this.

Thank you,

Rich
___
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?

[Rich Shepard]

On Fri, 15 Oct 2021, Franzen via SlackBuilds-users wrote:


Biber is in texlive-extra, so if you use the package from Didier, and
build
https://github.com/Ponce/slackbuilds/tree/current/office/texlive-extra you
should have a complete texlive2021 on 14.2


Thank you, Franzen.

There is a bug in the default 14.2 Biber that has been fixed in newer
versions. I downloaded a copy of Biber-3.16 and am looking for instructions
on how to use it to upgrade the installed version.

The issue is when a record in the bibliographic database has a name value
with an apostrophe; e.g., '@Article{O'Conner,' because it has no closing
curley brace (that's at the end of the entire entry. Apostrophes in any
other key:value pair are accepted because the value is enclosed in curley
braces.

I'll take your advice and use Ponce's texlive-extra.

Regards,

Rich
___
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?

[Rich Shepard]

On Wed, 13 Oct 2021, Didier Spaier wrote:


It all dpends if you need the additional features provided by
texlive-extra. Only you know.


I'll see. :-)

Thanks,

Rich
___
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?

[Rich Shepard]

On Wed, 13 Oct 2021, Didier Spaier wrote:


Caveat: I didn't build texlive-doc and texlive-extra at the same version


Didier,

Does that make a difference?

I'm getting all sorts of errors when building documents for a client so I
need to fix them by upgrading ASAP.

Thanks,

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

[Rich Shepard]

My LaTeX/LyX documents throw a Biber/biblatex error when compiling with
pdflatex. The issue is having bibliographic database entry labels with
apostrophes, such as O'Conner. This was fixed in Biber 2.2 but the 14.2
version is 2.14. (Apostrophes in other value fields are okay as they're
enclosed in curley braces {}, but the cite key/label isn't.)

The latest biblatex and Biber (3.16, 2020-12-31) is included in TeXLive2021.

Could I build the -current TexLive2021 in 14.2? Or should I upgrade
biblatex/Biber to 3.16?

Rich
___
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] Issue building qgis

[Rich Shepard]

On Sat, 2 Oct 2021, King Beowulf wrote:


On 14.2, make sure you know which gt5 you have installed (and make sure to
compile with qtwebengine support). also, if you upgraded qt5, you need to
recompile qt5-webkit. You may also need to have libwebp installed before
compiling qt5.


Ed,

Ah, I have the latest qt5, but probably installed it without the web engine.
I guess I'll recompile qt5 and the webkit. Sigh. Takes hours even on my
comparatively fast host with 32G RAM.


on the SBo, qgis page, there is also a warning to be sure to compile
some dependencies in the correct order.



On Slackware Current, qgis may be a bit easier.
https://github.com/Ponce/slackbuilds/tree/current/gis/qgis


I need to get this project to a client before spending a day or so wiring
the new host and installing -current on it, then copying over /home, /opt,
and /data.

Thanks,

Rich
___
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] Issue building qgis

[Rich Shepard]

Installed here is qt5-webkit-5.212.0_alpha4-x86_64-3_SBo.

Building qgis fails with a qt5-webkit version error:
CMake Error at CMakeLists.txt:453 (find_package):
  Found package configuration file:

/usr/lib64/cmake/Qt5WebKit/Qt5WebKitConfig.cmake

  but it set Qt5WebKit_FOUND to FALSE so package "Qt5WebKit" is considered to
  be NOT FOUND.  Reason given by package:

  Qt5WebKit could not be found because dependency is required to have exact
  version 5.12.x.

Please advise me how to resolve this issue.

TIA,

Rich
___
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] sofastats questions

[Rich Shepard]

On Mon, 27 Sep 2021, Jude DaShiell wrote:


This is slackware version 14.2 specifically slint the international
version of slackware.  I get the following high level errors when using
spi -i sofastats this happens with sbopkg on lower levels too even when
each of the missing packages is run with sqg -p packagename first and then
sbopkg -i packagename.
The spi errors are:
No such package or SlackBuild: matplotlib pywebkitgtk wkhtmltopdf
python-requests pyPdf


Jude,

Have you considered R  for statistical analyses
and data modeling?

Rich
___
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] K-Line on Freenode

[Rich Shepard]

On Sun, 13 Jun 2021, Robby Workman wrote:


Apologies for the bad grammar -- it should read "between me and him" or
"between him and me"


That's okay, Robby. It seems to me that pronouns have become a major focus
of many people. Why, I don't know, but even LinkedIn offers an opportunity
for subscribers to express their preferred pronouns. Me? I could care less.
There are more important things in life.

Stay well,

Rich
___
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] Directory name

[Rich Shepard]

On Mon, 7 Jun 2021, Jostein Berntsen wrote:


There is a thread on this at this mailing list from last year that might
give some input:
http://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-April/thread.html#24464


Jostein,

My reading of the thread is that python3.7m/ is where things should go ...
as far as the PyQt5 version at that time was concerned. Unfortunately, the
newer versions of PyQt5 changed and are seeking a python3.7/ include
directory.

Thanks for the URL.

Rich

___
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] Directory name

[Rich Shepard]

I need to upgrade python3-PyQt5 because the current version cannot access
postgresql tables.

Attempting to build PyQt5-5.15.4 halts at this error:
configure.py: error: '/usr/include/python3.7' is not a directory

There is a /usr/include/python2.7/ but a /usr/include/python3.7m/. Why the
difference in directory names? Could I rename 3.7m to 3.7?

I need to upgrade to build my business tracking application and can't wait
for a 15.0.

Rich
___
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] Python (Again!)

[Rich Shepard]

On Tue, 20 Apr 2021, Barry J. Grundy wrote:


Since python2 is EOL and -current/15 ships with python3, is it good
practice now to build python packages with python3 by default?


Barry,

Yes.


If so, then what's the best way to handle the multiple versions?  This
discussion was had on the list back in Feb of '19, but I don't see
anything definitive.


I'm not an SBo package maintainer, but you'd be safe to stop any python2
upgrades. If there's python2 code that needs to be used with python3 run it
through 2to3. That's what I did to my code and hadn't to do any hand
tweaking.

Rich
___
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] Heads-up: rdiff-backup update to 2.0.5 - Incompatible with 1.2.8

[Rich Shepard]

On Sun, 21 Mar 2021, Ricardo J. Barberis wrote:


I'm not sure, I've been its maintainer for a very short time only.
Let's see what other people on the list say about this :)


Ricardo,

I've been using dirvish  for more than 20 years.
It's based on rsync and Just Works(TM). Looking at your rdiff-backup page it
does the same thing as dirvish. So I'm one Slacker who has no need for
rdiff-backup.

HTH,

Rich

___
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] Pitivi: now crashes loading file [RESOLVED]

[Rich Shepard]

On Mon, 8 Mar 2021, Rich Shepard wrote:


This morning I started it and tried loading a .mp4 file. Each time the
application crashed. I'm not sure where to find a file with information
about crashing.


This issue's been resolved. I restored the .mkv clips and loaded them. It
must be that pitivi doesn't like working with .mp4 clips. That'll work for
me.

And so far the CPU usage is near zero because I'm writing this message and
not working with pitivi.

Rich
___
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] Pitivi: now crashes loading file

[Rich Shepard]

I had pitivi-0.95-x86_64-3_SBo running last Friday with two files loaded. It
constantly had ~50% CPU usage even sitting there and would take minutes to
react to a mouse click or keyboard entry.

This morning I started it and tried loading a .mp4 file. Each time the
application crashed. I'm not sure where to find a file with information
about crashing.

There's no maillist or web forum for pitivi, but there is an IRC channel for
it. Would that be the appropriate place to seek help in resolving both
today's crashes and Friday's high CPU usage (on an 8-core Ryzen7) and long
delays responding to actions?

TIA,

Rich
___
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] Upgrading packages

[Rich Shepard]

On Sat, 27 Feb 2021, Jeremy Hansen wrote:


It's because you have build 1 installed and build 2 is what's on the repo
now. The build was incremented back in May 2020 with this commit.


Jeremy,

Thank you. I hadn't considered that until this morning when I let sbopkg
upgrade it.

Regards,

Rich
___
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] Another library question

[Rich Shepard]

I have OpenBLAS-0.3.12-x86_64-1_SBo installed. But both LAPACK and grass
cannot find BLAS installed. The BLAS SBo page suggests that OpenBLAS is a
viable substitute: "Note: If you want good performance, then use the BLAS
libraries provided by your CPU vendor, or OpenBLAS or atlas provided by
SlackBuilds.org."

I'd like to understand why OpenBLAS is not seen as an acceptable substitute
for BLAS. Anyone know?

TIA,

Rich

___
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] Upgrading packages

[Rich Shepard]

On Sat, 27 Feb 2021, Heiko Rosemann wrote:


the BUILD number was increased. sbopkg will install
python3-PyQt5-5.13.2-x86_64-2_SBo.


Heiko,

Ah, so I did miss the SlackBuild upgrade. That's why I let it upgrade today.

Thanks,

Rich
___
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] Upgrading packages

[Rich Shepard]

Installed here is python3-PyQt5--5.13.2-x86_64-1_SBo. I don't see an upgrade
to that package in the weekly list and wonder why sbopkg keeps suggesting I
upgrade since 5.13.2 is installed and the version in the repo.

Today I decided to let it run for the several hours it takes but am curious
why sbopkg offers to upgrade to the same version. Was there a SlackBuild
change I missed seeing?

TIA,

Rich
___
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] avahi cannot find installed pygobject

[Rich Shepard]

On Fri, 19 Feb 2021, Didier Spaier wrote:


   If you want to install all uninstalled Slackware packages onto
your system, use the following
   command instead of the install-new action:

# slackpkg install slackware.


Thank you.

Rich
___
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?

[Rich Shepard]

On Fri, 19 Feb 2021, Jeremy Hansen wrote:


There was one on SBo, but it was horribly outdated and was likely removed
because of security issues.


Jeremy,

Yes, the files are dated 2018. There are some websites that don't support
firefox but do support chromium/chrome so it's good to have as a backup.


The only place I'm aware of that offers it for Slackware now is from Alien
Bob.


Thank you. It's installed and I'll upgrade there, too.

Carpe weekend,

Rich

___
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] avahi cannot find installed pygobject

[Rich Shepard]

On Fri, 19 Feb 2021, Didier Spaier wrote:

So in the future please check that you have a full Slackware installation 
before asking for help in this list or on LQ.


This has been reminded many times.


Didier.

When I ran 'slackpkg --upgrade-all --install-new' I assumed it provided a
full installation. If that doesn't what options to slackpkg will?

Rich
___
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] Chromium?

[Rich Shepard]

I had an SBo chromium package installed. Now I don't find one in the SBo
repo or in the core distribution.

Is there one available?

Rich
___
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] avahi cannot find installed pygobject

[Rich Shepard]

On Fri, 19 Feb 2021, Didier Spaier wrote:

Is pygobject3-3.18.2 (included in Slacwkare64-14.2) installed as it should 
be?


Didier,

For some reason it wasn't installed. I have the SBo pygobject3 installed and
was unaware there was one in the core distribution.

It's now installed and avahi is now built.

Thank you very much,

Rich
___
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] avahi cannot find installed pygobject

[Rich Shepard]

Trying to build avahi fails here:
checking for PYGOBJECT... no
configure: error: Could not find Python GObject

Installed here are:
pygobject-2.28.6-x86_64-2
pygobject3-python3-3.18.2-x86_64-1_SBo

And I just re-installed pygobject-2.28.6. It's located in
/usr/share/gtk-doc/html/pygobject
/usr/share/pygobject

Where should I look for the reason avahi cannot find pygobject?

TIA,

Rich

avahi-build.log.gz
Description: GNU Zip compressed data
___
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 build [FIXED]

[Rich Shepard]

On Thu, 18 Feb 2021, Ricardo J. Barberis wrote:


Not necessarily your mistake, but something's definitely not quite right on
your system.


Ricardo,

That makes many of us.


/usr/local/include/cdda_interface.h:87:31: error: expected ‘:’ before ‘;’
token cdda_private_data_t *private;



In my system I have /usr/include/cdda/cdda_interface.h from
cdparanoia-III_10.2-x86_64-1

I'd suggest removing whatever you have installed in /usr/local and stick to
the official Slackware64 packages.


I saw the mention of /usr/local/ but ignored it since -- as far as my
actions go -- every package goes into /usr/ not /usr/local/.

Yes, somehow last April 9th cdda_interface,h and another cdda*h were
installed in both /usr/include and /usr/local/include/. They're now removed.

And that was the problem. I overlooked it because I've not intentionally
installed any core or SBo package in /usr/loca/.

Thank you,

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

[Rich Shepard]

On Thu, 18 Feb 2021, Rich Shepard wrote:

/usr/local/include/cdda_interface.h:87:31: error: expected ‘:’ before ‘;’ 
token

  cdda_private_data_t *private;
  ^
CMakeFiles/soundkonverter.dir/build.make:62: recipe for target 
'CMakeFiles/soundkonverter.dir/soundkonverter_automoc.o' failed

make[2]: *** [CMakeFiles/soundkonverter.dir/soundkonverter_automoc.o] Error 1
CMakeFiles/Makefile2:164: recipe for target 
'CMakeFiles/soundkonverter.dir/all' failed

make[1]: *** [CMakeFiles/soundkonverter.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

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

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


Didn't capture the rest:

+++
SUMMARY LOG
Using the SBo repository for Slackware 14.2
Queue Process:  Download, build, and install

soundkonverter:
  MD5SUM check for soundkonverter-2.2.2.tar.gz ... OK
  Error occurred with build.  Please check the log.

+++

###
  Queue process complete!
###

___
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

[Rich Shepard]

On Thu, 18 Feb 2021, Didier Spaier wrote:


I just typed this as root:
sbopkg -r
sbopkg -i soundkonverter

Took a few minutes to build and install on Slint, based on Slackware64-4.2


Didier,

If it's user error I must be at fault, right?

/usr/local/include/cdda_interface.h:87:31: error: expected ‘:’ before ‘;’ token
   cdda_private_data_t *private;
   ^
CMakeFiles/soundkonverter.dir/build.make:62: recipe for target 
'CMakeFiles/soundkonverter.dir/soundkonverter_automoc.o' failed
make[2]: *** [CMakeFiles/soundkonverter.dir/soundkonverter_automoc.o] Error 1
CMakeFiles/Makefile2:164: recipe for target 'CMakeFiles/soundkonverter.dir/all' 
failed
make[1]: *** [CMakeFiles/soundkonverter.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

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

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

Rich
___
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] Fresh soundkonverter download fails to build (fwd)

[Rich Shepard]

Downloaded both the SlackBuild and the source tarball for soundkonverter and
it fails to build. Looks to me like source code error. Compressed build log
attached.

Rich

soundkonverter-build.log.gz
Description: GNU Zip compressed data
___
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] Fresh soundkonverter download fails to build

[Rich Shepard]

Downloaded both the SlackBuild and the source tarball for soundkonverter and
it fails to build. Looks to me like source code error. Compressed build log
attached.

Rich
___
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 atlas

[Rich Shepard]

On Thu, 18 Feb 2021, Jeremy Hansen wrote:


This is likely something that's in the source tarball and resides in the
/tmp/SBo/atlas-$VERSION directory. It wouldn't be something on SBo if it's
referenced by the source itself.


Jeremy,

Which is another reason to ignore it since there is an alternative that does
build.

Regards,

Rich
___
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]

[Rich Shepard]

On Thu, 18 Feb 2021, Ricardo J. Barberis wrote:


If you already use sbopkg to update your packages, you can also use it to
install new packages:

$ sudo sbopkg -i "package-name"

It won't install dependencies (you can use sqg as suggested elsewhere) but at
least you won't have to manually download the slackbuild and sources, compile
and install.

This will not only save you some time, it'll also use your up-to-date SBo repo
copy from /var/lib/sbopkg/SBo so you won't have to maintain a second copy via
git/rsync.


Ricardo,

Something to think about.

Thanks,

Rich
___
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 atlas

[Rich Shepard]

On Thu, 18 Feb 2021, Erich Ritz wrote:


Perhaps it meant to reference this?
https://slackbuilds.org/slackbuilds/14.2/libraries/atlas/README.SLACKWARE
which instructs you to do:
/etc/rc.d/rc.cpufreq performance


Erich,

I saw the README.SLACKWARE file but was looking for the INSTALL.txt file the
build suggested.


If you can't get atlas to build, try OpenBLAS instead. I use OpenBLAS with
octave without a problem. Note that OpenBLAS can be used instead of atlas
(and also instead of blas+lapack). The README for octave explains the
situation quite clearly, in my opinion.


I've used OpenBLAS, too. After all these years I'm still not confident I
know the relationships of LAPACK, BLAS, ATLAS, and OpenBLAS. They seem to
overlap so much.

Since OpenBLAS seems to do all that octave, R, grass, and other applications
want done I'll remove LAPACK-ATLAS, and build only OpenBLAS.

Thanks for the insight!

Rich

___
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] Building atlas

[Rich Shepard]

The hardware has an AMD Ryzen7 2700 (8 cores/16 threads) and 32G RAM. I'm
trying to build atlas but it bails out because of throttling and references
its INSTALL.txt which I cannot find. The (compressed) build log is attached.
I don't overclock and I hesitate to mess with the clock speed.

I've had this issue before and used BLAS-ATLAS instead. I can do that again
if it's advisable.

I'd appreciate your advice on building atlas on this host.

TIA,

Rich

atlas-build.log.gz
Description: GNU Zip compressed data
___
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]

[Rich Shepard]

On Thu, 18 Feb 2021, Jeremy Hansen wrote:


All sbopkg's sync does is sync its local repo with SBo's online repo.


Jeremy,

I know that and have been using it that way for a long time.


However, since sbopkg itself doesn't track dependencies (that is kinda done
with sqg),


Aha! I knew there was something but forgot the name.

Thanks!

Rich


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

[Rich Shepard]

On Wed, 17 Feb 2021, Jeremy Hansen wrote:


If you're going to build packages manually, it would probably be good to
keep a local git repo of SBo and update that before running SlackBuilds.
You can create the repo by running:
git clone git://git.slackbuilds.org/slackbuilds.git sbo-repo
Then you can update it by going in the directory and running:
git pull


Thanks, Jeremy. I'm creating the clone now and will keep it updated weekly.

Rich
___
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]

[Rich Shepard]

On Thu, 18 Feb 2021, Tim Dickson via SlackBuilds-users wrote:

if you had run "sync" from within sbopkg as you just said, your 
geoclue2.SlackBuild would have been the most up-to-date one, and you would 
have avoided the problem you had, which makes it puzzling.


Tim,

Does sync find packages I need that are not already installed? I was under
the impression that when I ran sync it compared the SBo packages here with
those on the SBo repo.

see above comment. if you use sync from sbopkg, your sbopkg repo will always 
be as up to date as when you last ran sync.


I do run sbopkg, each week.

Rich
___
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]

[Rich Shepard]

On Thu, 18 Feb 2021, B Watson wrote:


*Please* try to avoid doing this. Before you send a mail to the list
asking for help with a problem, make sure the problem hasn't already
been fixed in the repo. We can't guess if you're using outdated stuff
from 3 years ago, so we collectively wasted however many man-hours
trying to help you with a non-problem.


In the 17 years I've run Slackware and SBo packages I've not before found a
package version with a different build script than the same version I have
here.


SlackBuild scripts can and do change, in between version updates.


And now I've learned this.


You might want to use git to track changes to the repo.


Every week after updates are posted I run sbopkg and update what's
installed. Now I'm installing removed packages which is not automated by
sbopkg.

I'm also now keeping all installed compressed tarballs. When those are
upgraded by sbopkg I'll update the local repo too.

Not knowing there was a potential problem by having an outdated build script
here for the same source version as on the SBo I couldn't avoid it.

Rich
___
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]

[Rich Shepard]

On Wed, 17 Feb 2021, Jeremy Hansen wrote:


Those are taken directly from the SlackBuild script. It's how the script
determines whether or not to pass --disable-nmea-source to the configure
script.


Jeremy,

Thanks for pointing me to the problem and its solution.

When I went to rebuild geoclue2 I checked the current SBo version with what
I have here; they're the same. So I used the existing build script.

Reading your message I downloaded the build script from the SBo repo and
diff'd it against the one here:

$ diff geoclue2.SlackBuild geoclue2/geoclue2.SlackBuild 
4c4

< # Copyright 2017 Aaditya Bagga 
---

# Copyright 2017-2018 Aaditya Bagga 

73,74c73,74
< # to avoid avahi as a dependency add --disable-nmea-source
< # to the configure options
---

avahi_opts='--disable-nmea-source'
[ "${AVAHI:-no}" != "no" ] && avahi_opts=''

85a86

  $avahi_opts \


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.

Thanks very much!

Best regards,

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

[Rich Shepard]

On Wed, 17 Feb 2021, Jeremy Hansen wrote:


I don't know what to tell you. The SlackBuild defaults to disabling nmea
unless the AVAHI variable is set to anything other than "no". If it is
left unset, nmea is disabled.



The only other thing to check would be running the script with bash -x to
see everything bash sees when it's running the script. This way it would be
able to tell you what happens with the above code block.


Jeremy,

geoclue2 was installed long ago with no problems, and upgraded since then.
Why it should now ask for a non-present file is puzzling.

If I could find an avahi something to install that would make geoclue2 happy
I'd do it. But I haven't found anything.

Running the script from bash yields the same results.


avahi_opts='--disable-nmea-source'
[ "${AVAHI:-no}" != "no" ] && avahi_opts=''


What should I do with these? Put them in the build script somewhere? A quick
web search suggests that 'nmea' is a software gps emulator. There ought to
be something that will tell the build script to ignore nmea, avahi, and all
similar optional inputs.

I need geoclue2 to build GnuCash which I use for my business as well as
personal bookkeeping so I need to get it installed somehow.

Thanks,

Rich+ PRGNAM=geoclue2
+ VERSION=2.4.7
+ BUILD=1
+ TAG=_SBo
+ SRCNAM=geoclue
+ '[' -z '' ']'
+ case "$( uname -m )" in
++ uname -m
++ uname -m
+ ARCH=x86_64
++ pwd
+ CWD=/opt/slackbuilds/System/geoclue2
+ TMP=/tmp/SBo
+ PKG=/tmp/SBo/package-geoclue2
+ OUTPUT=/tmp
+ '[' x86_64 = i586 ']'
+ '[' x86_64 = i686 ']'
+ '[' x86_64 = x86_64 ']'
+ SLKCFLAGS='-O2 -fPIC'
+ LIBDIRSUFFIX=64
+ set -e
+ rm -rf /tmp/SBo/package-geoclue2
+ mkdir -p /tmp/SBo /tmp/SBo/package-geoclue2 /tmp
+ cd /tmp/SBo
+ rm -rf geoclue-2.4.7
+ tar xvf /opt/slackbuilds/System/geoclue2/geoclue-2.4.7.tar.xz
geoclue-2.4.7/
geoclue-2.4.7/.version
geoclue-2.4.7/configure.ac
geoclue-2.4.7/po/
geoclue-2.4.7/po/POTFILES.in
geoclue-2.4.7/po/Makefile.in.in
geoclue-2.4.7/po/POTFILES.skip
geoclue-2.4.7/po/LINGUAS
geoclue-2.4.7/intltool-extract.in
geoclue-2.4.7/m4/
geoclue-2.4.7/m4/gnome-compiler-flags.m4
geoclue-2.4.7/m4/lt~obsolete.m4
geoclue-2.4.7/m4/ltoptions.m4
geoclue-2.4.7/m4/ltsugar.m4
geoclue-2.4.7/m4/libtool.m4
geoclue-2.4.7/m4/intltool.m4
geoclue-2.4.7/m4/ltversion.m4
geoclue-2.4.7/m4/gtk-doc.m4
geoclue-2.4.7/NEWS
geoclue-2.4.7/Makefile.decl
geoclue-2.4.7/src/
geoclue-2.4.7/src/gclue-web-source.c
geoclue-2.4.7/src/gclue-client-interface.c
geoclue-2.4.7/src/gclue-config.c
geoclue-2.4.7/src/gclue-service-manager.c
geoclue-2.4.7/src/gclue-client-info.c
geoclue-2.4.7/src/gclue-3g-tower.h
geoclue-2.4.7/src/geocode-glib/
geoclue-2.4.7/src/geocode-glib/geocode-forward.h
geoclue-2.4.7/src/geocode-glib/geocode-forward.c
geoclue-2.4.7/src/geocode-glib/geocode-glib-private.h
geoclue-2.4.7/src/geocode-glib/geocode-bounding-box.h
geoclue-2.4.7/src/geocode-glib/geocode-location.c
geoclue-2.4.7/src/geocode-glib/geocode-enum-types.c
geoclue-2.4.7/src/geocode-glib/geocode-error.c
geoclue-2.4.7/src/geocode-glib/Makefile.in
geoclue-2.4.7/src/geocode-glib/geocode-glib.h
geoclue-2.4.7/src/geocode-glib/geocode-glib.c
geoclue-2.4.7/src/geocode-glib/geocode-reverse.h
geoclue-2.4.7/src/geocode-glib/geocode-place.c
geoclue-2.4.7/src/geocode-glib/geocode-location.h
geoclue-2.4.7/src/geocode-glib/geocode-place.h
geoclue-2.4.7/src/geocode-glib/geocode-error.h
geoclue-2.4.7/src/geocode-glib/geocode-bounding-box.c
geoclue-2.4.7/src/geocode-glib/Makefile.am
geoclue-2.4.7/src/geocode-glib/geocode-enum-types.h
geoclue-2.4.7/src/geocode-glib/geocode-reverse.c
geoclue-2.4.7/src/gclue-config.h
geoclue-2.4.7/src/gclue-nmea-source.h
geoclue-2.4.7/src/gclue-error.c
geoclue-2.4.7/src/gclue-service-location.c
geoclue-2.4.7/src/gclue-location-interface.c
geoclue-2.4.7/src/gclue-3g.c
geoclue-2.4.7/src/gclue-client-info.h
geoclue-2.4.7/src/compass-interface.h
geoclue-2.4.7/src/net.hadess.SensorProxy.xml
geoclue-2.4.7/src/gclue-nmea-source.c
geoclue-2.4.7/src/wpa_supplicant-interface.h
geoclue-2.4.7/src/wpa_supplicant-interface.c
geoclue-2.4.7/src/gclue-service-client.c
geoclue-2.4.7/src/gclue-modem-gps.c
geoclue-2.4.7/src/gclue-location.c
geoclue-2.4.7/src/Makefile.in
geoclue-2.4.7/src/gclue-wifi.h
geoclue-2.4.7/src/gclue-3g.h
geoclue-2.4.7/src/fi.w1.wpa_supplicant1.xml
geoclue-2.4.7/src/gclue-locator.c
geoclue-2.4.7/src/gclue-compass.c
geoclue-2.4.7/src/gclue-modem-gps.h
geoclue-2.4.7/src/gclue-web-source.h
geoclue-2.4.7/src/gclue-wifi.c
geoclue-2.4.7/src/org.freedesktop.GeoClue2.Manager.xml
geoclue-2.4.7/src/gclue-location-source.c
geoclue-2.4.7/src/gclue-location-interface.h
geoclue-2.4.7/src/agent/
geoclue-2.4.7/src/agent/Makefile.in
geoclue-2.4.7/src/agent/geoclue-agent-interface.c
geoclue-2.4.7/src/agent/org.freedesktop.GeoClue2.Agent.xml
geoclue-2.4.7/src/agent/Makefile.am
geoclue-2.4.7/src/agent/geoclue-agent-interface.h
geoclue-2.4.7/src/gclue-service-location.h
geoclue-2.4.7/src/gclue-mozilla.h
geoclue-2.4.7/src/gclue-locator.h
geoclue-2.4.7/src/gclue-service-client.h

Re: [Slackbuilds-users] Saga-gis: cannot find wxcrtvararg.h

[Rich Shepard]

On Wed, 17 Feb 2021, B Watson wrote:


Since I don't use saga-gis, or even have a very clear idea what it does, I
have to ask... is it even useful to build saga-gis without postgresql
support? Is that a rarely-used feature, or is it something that would
basically cripple saga-gis if it were missing?


B,

I have postgres installed; it'a always been my default RDBMS and is used
constantly.

SAGA is a raster-based GIS developed by physical geographers that focuses on
terrain analyses. It complements GRASS and offers some different models so
it's good to have available.


Reason I ask is, the dead simple way to fix this would be to add
postgresql to REQUIRES in the .info file. But if most users aren't likely
to need the postgresql support, it'd be better to leave it optional and
fix the script so it works without it.


I've not thought about it because I've not used SAGA extensively, but I do
keep GRASS data in postgres databases and since the two tools can interact I
suppose SAGA looks for data in a postgres database if it's not in the
default GRASS sqlite3 database.

Perhaps postgres could be listed as an optional dependency?

Regards,

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

[Rich Shepard]

On Wed, 17 Feb 2021, B Watson wrote:


Are you sure you didn't run the script with the AVAHI variable set
in the environment?


B,

Yes.


From looking at the SlackBuild, it needs to be either unset, set to ""
(empty), or set to "no" (lowercase), to build without avahi. If it were
set to anything else (including for example "NO" or "false"), the
--disable-nmea-source option doesn't get passed to configure.


On the SBo page I read,

"avahi is an optional dependency, used for location sharing (by redshift,
for example).  To enable it, use the option AVAHI=yes

  AVAHI=yes ./geoclue2.Slackbuild"

Since I don't want to enable it I did not add AVAHI=yes.

That's also in the README file. I didn't see anything about setting AVAHI=no
or anything else.


If you're using 'export AVAHI=', you might have a leftover
value in your environment. Use 'unset AVAHI' to clear it out.


There's no AVAHI here to export.

If AVAHI is not on the system how would it be in the environment?

My web search showed me that AVAHI is a networking implentation which
enables programs to publish and discover services and hosts running on a
local network. If it's part of core Slackware then it's missing here after
my running 'slackpkg upgrade-all'.


In general, when the README says 'set VARIABLE=value in the
environment', the script specifically looks for 'value',
case-sensitive. 'Value' or 'VALUE' won't match.


When package maintainers write 'to add this option use this in front of the
build script' and I don't want to add it I've always left it off.


Also, you can try forcing the issue with AVAHI="no" in the env. That
should work.


Worth a try. Command line: AVAHI=no ./geoclue2.SlackBuild &> geoclue2-build.log

Same results. Build log attached.

Thanks,

Rich
geoclue-2.4.7/
geoclue-2.4.7/.version
geoclue-2.4.7/configure.ac
geoclue-2.4.7/po/
geoclue-2.4.7/po/POTFILES.in
geoclue-2.4.7/po/Makefile.in.in
geoclue-2.4.7/po/POTFILES.skip
geoclue-2.4.7/po/LINGUAS
geoclue-2.4.7/intltool-extract.in
geoclue-2.4.7/m4/
geoclue-2.4.7/m4/gnome-compiler-flags.m4
geoclue-2.4.7/m4/lt~obsolete.m4
geoclue-2.4.7/m4/ltoptions.m4
geoclue-2.4.7/m4/ltsugar.m4
geoclue-2.4.7/m4/libtool.m4
geoclue-2.4.7/m4/intltool.m4
geoclue-2.4.7/m4/ltversion.m4
geoclue-2.4.7/m4/gtk-doc.m4
geoclue-2.4.7/NEWS
geoclue-2.4.7/Makefile.decl
geoclue-2.4.7/src/
geoclue-2.4.7/src/gclue-web-source.c
geoclue-2.4.7/src/gclue-client-interface.c
geoclue-2.4.7/src/gclue-config.c
geoclue-2.4.7/src/gclue-service-manager.c
geoclue-2.4.7/src/gclue-client-info.c
geoclue-2.4.7/src/gclue-3g-tower.h
geoclue-2.4.7/src/geocode-glib/
geoclue-2.4.7/src/geocode-glib/geocode-forward.h
geoclue-2.4.7/src/geocode-glib/geocode-forward.c
geoclue-2.4.7/src/geocode-glib/geocode-glib-private.h
geoclue-2.4.7/src/geocode-glib/geocode-bounding-box.h
geoclue-2.4.7/src/geocode-glib/geocode-location.c
geoclue-2.4.7/src/geocode-glib/geocode-enum-types.c
geoclue-2.4.7/src/geocode-glib/geocode-error.c
geoclue-2.4.7/src/geocode-glib/Makefile.in
geoclue-2.4.7/src/geocode-glib/geocode-glib.h
geoclue-2.4.7/src/geocode-glib/geocode-glib.c
geoclue-2.4.7/src/geocode-glib/geocode-reverse.h
geoclue-2.4.7/src/geocode-glib/geocode-place.c
geoclue-2.4.7/src/geocode-glib/geocode-location.h
geoclue-2.4.7/src/geocode-glib/geocode-place.h
geoclue-2.4.7/src/geocode-glib/geocode-error.h
geoclue-2.4.7/src/geocode-glib/geocode-bounding-box.c
geoclue-2.4.7/src/geocode-glib/Makefile.am
geoclue-2.4.7/src/geocode-glib/geocode-enum-types.h
geoclue-2.4.7/src/geocode-glib/geocode-reverse.c
geoclue-2.4.7/src/gclue-config.h
geoclue-2.4.7/src/gclue-nmea-source.h
geoclue-2.4.7/src/gclue-error.c
geoclue-2.4.7/src/gclue-service-location.c
geoclue-2.4.7/src/gclue-location-interface.c
geoclue-2.4.7/src/gclue-3g.c
geoclue-2.4.7/src/gclue-client-info.h
geoclue-2.4.7/src/compass-interface.h
geoclue-2.4.7/src/net.hadess.SensorProxy.xml
geoclue-2.4.7/src/gclue-nmea-source.c
geoclue-2.4.7/src/wpa_supplicant-interface.h
geoclue-2.4.7/src/wpa_supplicant-interface.c
geoclue-2.4.7/src/gclue-service-client.c
geoclue-2.4.7/src/gclue-modem-gps.c
geoclue-2.4.7/src/gclue-location.c
geoclue-2.4.7/src/Makefile.in
geoclue-2.4.7/src/gclue-wifi.h
geoclue-2.4.7/src/gclue-3g.h
geoclue-2.4.7/src/fi.w1.wpa_supplicant1.xml
geoclue-2.4.7/src/gclue-locator.c
geoclue-2.4.7/src/gclue-compass.c
geoclue-2.4.7/src/gclue-modem-gps.h
geoclue-2.4.7/src/gclue-web-source.h
geoclue-2.4.7/src/gclue-wifi.c
geoclue-2.4.7/src/org.freedesktop.GeoClue2.Manager.xml
geoclue-2.4.7/src/gclue-location-source.c
geoclue-2.4.7/src/gclue-location-interface.h
geoclue-2.4.7/src/agent/
geoclue-2.4.7/src/agent/Makefile.in
geoclue-2.4.7/src/agent/geoclue-agent-interface.c
geoclue-2.4.7/src/agent/org.freedesktop.GeoClue2.Agent.xml
geoclue-2.4.7/src/agent/Makefile.am
geoclue-2.4.7/src/agent/geoclue-agent-interface.h
geoclue-2.4.7/src/gclue-service-location.h
geoclue-2.4.7/src/gclue-mozilla.h
geoclue-2.4.7/src/gclue-locator.h
geoclue-2.4.7/src/gclue-service-client.h
geoclue-2.4.7/src/gclue-compass.h

Re: [Slackbuilds-users] Saga-gis: cannot find wxcrtvararg.h

[Rich Shepard]

On Wed, 17 Feb 2021, Erich Ritz wrote:


# grep wxcrtvararg.h /var/log/packages/*
/var/log/packages/wxGTK3-3.0.5-x86_64-1_SBo:usr/include/wx-3.0/wx/wxcrtvararg.h


Erich,

Mea culpa! I built the package last evening and obvousily forgot to install
it. Sigh.

Thanks,

Rich
___
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 [RESOLVED]

[Rich Shepard]

On Tue, 16 Feb 2021, B Watson wrote:


This is wrong. "tee" won't capture the standard error stream, only
standard output. Since we're asking to see *error* messages, we need
the stderr.


A build log with STDOUT and STDERR redirected to it is attached. While
geoclue built geoclue2 still will not. It's still looking for:
configure: error: Package requirements (
avahi-client >= 0.6.10
avahi-glib >= 0.6.10) were not met
Rich

geoclue2-build.log.gz
Description: GNU Zip compressed data
___
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] Saga-gis: cannot find wxcrtvararg.h

[Rich Shepard]

The saga-gis page shows wxGTK3 as a requirement. With that installed saga
requested a unicode wxGTK. Installed that one, too. Now with both installed
(and I no longer use wxPython so there's no conflict with wxGTK) the saga
build fails to find wxcrtvararg.h because it is missing.

What other package might contain that header?

The compressed build log (with STDOUT and STDERR redirected to the log file)
is attached.

Rich

saga-build.log.gz
Description: GNU Zip compressed data
___
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 [RESOLVED]

[Rich Shepard]

On Tue, 16 Feb 2021, Jeremy Hansen wrote:


Your attached build.log (which isn't an actual build log, just the output
from the configure script -- config.log from the build directory would be
more beneficial) showed it ended on:


Jeremy,

I capture what's on the screen using ' tee .log'. I didn't compare the
geoclue build log with the screen before sending it.

Anyway, I just tried building it and it worked. There may have been a
missing dependency I didn't see on the SBo page that's now installed.

Regards,

Rich

___
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] hdf5 md5sums don't match

[Rich Shepard]

On Tue, 16 Feb 2021, Jeremy Hansen wrote:


I just tested it on my system and it downloaded fine and the md5sum
matched SBo's. It might've been a temporary outage from the server and
caused you to download a text file.


Jeremy,

'file' showed it to be a compresse tarball.

I downloaded it from the UK site and it's building.

Thanks,

Rich
___
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] hdf5 md5sums don't match

[Rich Shepard]

On Tue, 16 Feb 2021, B Watson wrote:


Maybe you could run "file hdf5-1.10.6.tar.gz" and see what it actually is
that you downloaded? I bet it's an HTML page... possibly one that contains
an error message from the web server.


# file hdf5-1.10.6.tar.gz 
hdf5-1.10.6.tar.gz: gzip compressed data, from Unix, original size 12188967



Use wget to download the file. I just did, and its md5sum matches (and
tar doesn't complain about it, either).


I click on the filename on the SBo page; don't know which tool is used.
Looking at the HDF group's web site they have 1.12.0 available; prior
releases are not shown there.


Alternatively, learn to use sbosrcarch. If you look for the file at:
https://slackware.uk/sbosrcarch/by-name/libraries/hdf5/
...you should see it there.


Yes, that has the same checksum.

Most tarballs are downloaded by clicking on the filename on their SBo page.
I've not before had this issue.

Thanks,

Rich

___
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] hdf5 md5sums don't match

[Rich Shepard]

Bringing my system back to only -14.2 packages and no multilib/compat32 I
mistakenly ran 'slackpkg clean-system' and uninstalled all 582 SBo packages.
Long days ahead.

Rebuilding packages and ensuring I have the current versions (because sbopkg
upgraded many but left the local version as-is) and am finding packages that
don't build which surprises me.

Now it's hdf5:
# time ./hdf5.SlackBuild 
tar: This does not look like a tar archive

tar: Skipping to next header
tar: Exiting with failure status due to previous errors

I just downloaded hdf5-1.10.6.tar.gz so I compared the downloaded md5sum
with that on the SBo page:
$ md5sum hdf5-1.10.6.tar.gz 
de8a3ac2682b95f918dd19d61748ddb2  hdf5-1.10.6.tar.gz

$ 37f3089e7487daf0890baf3d3328e54a (from SBo)

Please advise.

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

[Rich Shepard]

On Tue, 16 Feb 2021, Jeremy Hansen wrote:


I don't know that I need it so I tried building without it:



It works fine on my 14.2 system without avahi installed. Did you pass
AVAHI=yes to the script?


Jeremy,

As I wrote, no. I've no need for avahi so I tried building without it.
That's why I was surprised when the build script asked for it.

I've a clean 14.2 so I don't know why it didn't build.

Thanks,

Rich
___
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] geoclue2: wants optional dependencies

[Rich Shepard]

I need to rebuild/re-install geoclue2. The SBo page says that,
avahi is an optional dependency, used for location sharing (by redshift,
for example).  To enable it, use the option AVAHI=yes

  AVAHI=yes ./geoclue2.Slackbuild

I don't know that I need it so I tried building without it:

configure: error: Package requirements (
avahi-client >= 0.6.10
avahi-glib >= 0.6.10) were not met:

No package 'avahi-client' found
No package 'avahi-glib' found

Full build log attached.

Richgeoclue-2.4.7/
geoclue-2.4.7/.version
geoclue-2.4.7/configure.ac
geoclue-2.4.7/po/
geoclue-2.4.7/po/POTFILES.in
geoclue-2.4.7/po/Makefile.in.in
geoclue-2.4.7/po/POTFILES.skip
geoclue-2.4.7/po/LINGUAS
geoclue-2.4.7/intltool-extract.in
geoclue-2.4.7/m4/
geoclue-2.4.7/m4/gnome-compiler-flags.m4
geoclue-2.4.7/m4/lt~obsolete.m4
geoclue-2.4.7/m4/ltoptions.m4
geoclue-2.4.7/m4/ltsugar.m4
geoclue-2.4.7/m4/libtool.m4
geoclue-2.4.7/m4/intltool.m4
geoclue-2.4.7/m4/ltversion.m4
geoclue-2.4.7/m4/gtk-doc.m4
geoclue-2.4.7/NEWS
geoclue-2.4.7/Makefile.decl
geoclue-2.4.7/src/
geoclue-2.4.7/src/gclue-web-source.c
geoclue-2.4.7/src/gclue-client-interface.c
geoclue-2.4.7/src/gclue-config.c
geoclue-2.4.7/src/gclue-service-manager.c
geoclue-2.4.7/src/gclue-client-info.c
geoclue-2.4.7/src/gclue-3g-tower.h
geoclue-2.4.7/src/geocode-glib/
geoclue-2.4.7/src/geocode-glib/geocode-forward.h
geoclue-2.4.7/src/geocode-glib/geocode-forward.c
geoclue-2.4.7/src/geocode-glib/geocode-glib-private.h
geoclue-2.4.7/src/geocode-glib/geocode-bounding-box.h
geoclue-2.4.7/src/geocode-glib/geocode-location.c
geoclue-2.4.7/src/geocode-glib/geocode-enum-types.c
geoclue-2.4.7/src/geocode-glib/geocode-error.c
geoclue-2.4.7/src/geocode-glib/Makefile.in
geoclue-2.4.7/src/geocode-glib/geocode-glib.h
geoclue-2.4.7/src/geocode-glib/geocode-glib.c
geoclue-2.4.7/src/geocode-glib/geocode-reverse.h
geoclue-2.4.7/src/geocode-glib/geocode-place.c
geoclue-2.4.7/src/geocode-glib/geocode-location.h
geoclue-2.4.7/src/geocode-glib/geocode-place.h
geoclue-2.4.7/src/geocode-glib/geocode-error.h
geoclue-2.4.7/src/geocode-glib/geocode-bounding-box.c
geoclue-2.4.7/src/geocode-glib/Makefile.am
geoclue-2.4.7/src/geocode-glib/geocode-enum-types.h
geoclue-2.4.7/src/geocode-glib/geocode-reverse.c
geoclue-2.4.7/src/gclue-config.h
geoclue-2.4.7/src/gclue-nmea-source.h
geoclue-2.4.7/src/gclue-error.c
geoclue-2.4.7/src/gclue-service-location.c
geoclue-2.4.7/src/gclue-location-interface.c
geoclue-2.4.7/src/gclue-3g.c
geoclue-2.4.7/src/gclue-client-info.h
geoclue-2.4.7/src/compass-interface.h
geoclue-2.4.7/src/net.hadess.SensorProxy.xml
geoclue-2.4.7/src/gclue-nmea-source.c
geoclue-2.4.7/src/wpa_supplicant-interface.h
geoclue-2.4.7/src/wpa_supplicant-interface.c
geoclue-2.4.7/src/gclue-service-client.c
geoclue-2.4.7/src/gclue-modem-gps.c
geoclue-2.4.7/src/gclue-location.c
geoclue-2.4.7/src/Makefile.in
geoclue-2.4.7/src/gclue-wifi.h
geoclue-2.4.7/src/gclue-3g.h
geoclue-2.4.7/src/fi.w1.wpa_supplicant1.xml
geoclue-2.4.7/src/gclue-locator.c
geoclue-2.4.7/src/gclue-compass.c
geoclue-2.4.7/src/gclue-modem-gps.h
geoclue-2.4.7/src/gclue-web-source.h
geoclue-2.4.7/src/gclue-wifi.c
geoclue-2.4.7/src/org.freedesktop.GeoClue2.Manager.xml
geoclue-2.4.7/src/gclue-location-source.c
geoclue-2.4.7/src/gclue-location-interface.h
geoclue-2.4.7/src/agent/
geoclue-2.4.7/src/agent/Makefile.in
geoclue-2.4.7/src/agent/geoclue-agent-interface.c
geoclue-2.4.7/src/agent/org.freedesktop.GeoClue2.Agent.xml
geoclue-2.4.7/src/agent/Makefile.am
geoclue-2.4.7/src/agent/geoclue-agent-interface.h
geoclue-2.4.7/src/gclue-service-location.h
geoclue-2.4.7/src/gclue-mozilla.h
geoclue-2.4.7/src/gclue-locator.h
geoclue-2.4.7/src/gclue-service-client.h
geoclue-2.4.7/src/gclue-compass.h
geoclue-2.4.7/src/gclue-mozilla.c
geoclue-2.4.7/src/gclue-modem-manager.h
geoclue-2.4.7/src/gclue-error.h
geoclue-2.4.7/src/gclue-cdma.h
geoclue-2.4.7/src/compass-interface.c
geoclue-2.4.7/src/gclue-manager-interface.c
geoclue-2.4.7/src/gclue-marshal.list
geoclue-2.4.7/src/Makefile.am
geoclue-2.4.7/src/gclue-marshal.h
geoclue-2.4.7/src/gclue-client-interface.h
geoclue-2.4.7/src/org.freedesktop.GeoClue2.Client.xml
geoclue-2.4.7/src/gclue-modem.h
geoclue-2.4.7/src/gclue-service-manager.h
geoclue-2.4.7/src/gclue-location-source.h
geoclue-2.4.7/src/gclue-marshal.c
geoclue-2.4.7/src/geoclue.pc.in
geoclue-2.4.7/src/org.freedesktop.GeoClue2.Location.xml
geoclue-2.4.7/src/gclue-location.h
geoclue-2.4.7/src/gclue-modem-manager.c
geoclue-2.4.7/src/gclue-modem.c
geoclue-2.4.7/src/gclue-manager-interface.h
geoclue-2.4.7/src/gclue-cdma.c
geoclue-2.4.7/src/gclue-main.c
geoclue-2.4.7/public-api/
geoclue-2.4.7/public-api/gclue-enum-types.c
geoclue-2.4.7/public-api/gclue-enums.h
geoclue-2.4.7/public-api/Makefile.in
geoclue-2.4.7/public-api/gclue-enum-types.h
geoclue-2.4.7/public-api/Makefile.am
geoclue-2.4.7/config.h.in
geoclue-2.4.7/aclocal.m4
geoclue-2.4.7/Makefile.in
geoclue-2.4.7/demo/
geoclue-2.4.7/demo/where-am-i.c

Re: [Slackbuilds-users] Finding why build fails

[Rich Shepard]

On Mon, 15 Feb 2021, Erich Ritz via SlackBuilds-users wrote:


Actually since Slackware-current ships Python 3.9.1 and -current also
ships pygobject3, I would suggest grabbing Pat's SlackBuild and running it
on your machine. Note, do not just install the -current package! Or at
least manually inspect the difference's between Pat's SlackBuild and SBo's
SlackBuild to try to get a clue as to why your build is failing.


Erich,

What I saw of the differences between the two build scripts should not
adversely affect their operation. The -current version is in Libraries now
instead of in SBo's Python. And pygobject3-3.38.0-x86_64-3.txz and is the
only pygobject3 installed.

Now I'll go back to building pitivi dependencies.

Thanks for the suggestion,

Rich
___
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] Finding why build fails

[Rich Shepard]

On Mon, 15 Feb 2021, Erich Ritz wrote:


What about your setup is not standard?


Erich,

I'm running python-3.9.1 rather than 3.7.2. I think that's it.

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