Re: [Slackbuilds-users] All-writable directory under /opt

[Daniel Prosser]

> Hm. You mean, if the copy was created by running it as root, it
> *still* tries to make a new copy, if run without a config file?

Yes, it still tries to make a new copy if the config file isn't already 
present or if using a config file from a previous version that doesn't 
include that setting. Actually, upon further review, the file 
stockfish-16.1-64 is already there when LucasChess is first installed, 
but it apparently copies over it or at least modifies it in some way 
during the detection process. So my initial idea of simply providing 
this file is definitely not enough to avoid this process.


> That could work. Go with a lowercase group name though, lucaschess or
> just lucas.
>
> For that matter, you could go with the system games group. Ask
> user to join that group. Though, it would also let the user edit
> the high scores for games that save high scores as the games
> group. Realistically I don't think this matters much.

Thanks, I think I'll go with the approach of creating a new group. It 
seems like the most straightforward way of dealing with the problem, and 
there are a good number of existing scripts that do something like this.


Dan

On 5/4/24 23:09, B. Watson wrote:



On Sat, 4 May 2024, Daniel Prosser wrote:

Thanks for the ideas. I like the idea of using the setgid bit, but 
I'm having trouble getting it to work. First, the main executable is 
a wrapper script, which may be a problem, but even applying the 
setguid bit to the binary file and foregoing the wrapper script 
(doing the stuff the wrapper script would have done manually in the 
shell for testing purposes) results in library import errors. I 
assume this is due to permissions somehow, but I don't really 
understand why.


Because the wrapper script exports LD_LIBRARY_PATH (to tell the
executable where to find the libs), and glibc deliberately ignores
that variable on binaries with the setuid or setgid bits set.

So that approach wouldn't work.

Asking the user to run as root the first time would work, but I would 
also have to tell them to then copy the configuration directory from 
/root to their user directory and set permissions accordingly, which 
seems rather unwieldy and inconvenient.


Hm. You mean, if the copy was created by running it as root, it
*still* tries to make a new copy, if run without a config file?

In a related idea, what about installing the program with some group 
ownership (say "LucasChess") and asking the user to join that group 
before running?


That could work. Go with a lowercase group name though, lucaschess or
just lucas.

For that matter, you could go with the system games group. Ask
user to join that group. Though, it would also let the user edit
the high scores for games that save high scores as the games
group. Realistically I don't think this matters much.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


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

Re: [Slackbuilds-users] All-writable directory under /opt

[Daniel Prosser]

Thanks for the ideas. I like the idea of using the setgid bit, but I'm 
having trouble getting it to work. First, the main executable is a 
wrapper script, which may be a problem, but even applying the setguid 
bit to the binary file and foregoing the wrapper script (doing the stuff 
the wrapper script would have done manually in the shell for testing 
purposes) results in library import errors. I assume this is due to 
permissions somehow, but I don't really understand why.


After some more testing, I don't think that having the SlackBuild script 
copy or symlink one of the stockfish executables will solve the problem. 
There is apparently also a setting in the user config directory that it 
looks for, and if that isn't present, it will try to go through the 
copying process anyway.


Asking the user to run as root the first time would work, but I would 
also have to tell them to then copy the configuration directory from 
/root to their user directory and set permissions accordingly, which 
seems rather unwieldy and inconvenient. In a related idea, what about 
installing the program with some group ownership (say "LucasChess") and 
asking the user to join that group before running?


Dan

On 5/4/24 00:55, B. Watson wrote:



On Fri, 3 May 2024, Daniel Prosser wrote:

The copy it makes is called stockfish-16.1-64. On my machine, it 
seems to have copied the bmi2 version, but maybe the plain -x86-64 
version would be more universal. (For that matter, if I take this 
approach, I'll probably just make a symbolic link instead of wasting 
disk space with a copy.)


I can think of one more approach... assuming the stockfish-16.1-x86-64
binary will run on anything x86_64 (because it doesn't have
fancy CPU-specific optimizations), pre-create the symlink to that
one. Advise the user that the other engines exist (in the README)
and give a short set of instructions on how to choose the right one
(basically as simple as, rm the symlink, run the engine as root once).

This way, people who just install it without paying much attention
will at least get a working (if unoptimized) package.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


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

[Slackbuilds-users] All-writable directory under /opt

[Daniel Prosser]

Hello,

I am in the process of updating my LucasChess SlackBuild to the latest 
version. Something new in this version is that when you first start it 
up and click Play, it goes through some process where it decides which 
build of stockfish (the analysis engine) is appropriate for your machine 
and makes a copy of it. This means the directory 
/opt/LucasChess-$VERSION/bin/OS/linux/Engines/stockfish needs to be 
writable by regular users, or else it will just hang. Is this acceptable?


An alternative potential solution that I think would work would be to 
have the SlackBuild script copy the file, selecting a build that would 
work for everyone. For those who may know more about that sort of thing, 
the available builds are:


stockfish-16.1-x86-64
stockfish-16.1-x86-64-avx2
stockfish-16.1-x86-64-avx512
stockfish-16.1-x86-64-avxvnni
stockfish-16.1-x86-64-bmi2
stockfish-16.1-x86-64-sse3-popcnt
stockfish-16.1-x86-64-sse41-popcnt
stockfish-16.1-x86-64-ssse3
stockfish-16.1-x86-64-vnni256
stockfish-16.1-x86-64-vnni512

The copy it makes is called stockfish-16.1-64. On my machine, it seems 
to have copied the bmi2 version, but maybe the plain -x86-64 version 
would be more universal. (For that matter, if I take this approach, I'll 
probably just make a symbolic link instead of wasting disk space with a 
copy.)


Thanks,
Dan

___
SlackBuilds-users mailing list
SlackBuilds-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] Dos line endings in patch file

[Daniel Prosser]

Okay, thanks all for the recommendations. I will use the gzip approach and submit it for the next SBo update.Regards,DanOn Dec 22, 2023 8:27 PM, "B. Watson"  wrote:

On Fri, 22 Dec 2023, Daniel Prosser wrote:

> I recently updated xflr5 to the latest version. The SlackBuild includes a 
> patch which is supposed to have dos line endings, since the source file also 
> has dos line endings. The patch file I uploaded had dos line endings (and I 
> tested before uploading), but now in the repo, it has unix line endings,

This is an ongoing issue. The best way we've found to handle it, is
to gzip the patch, then use "zcat $CWD/whatever.diff.gz | patch -p1"
or similar. For examples, see games/oblige and system/unage.

If you're wondering, the problem is caused by git. It tries to
"correct" the line endings for whatever system it's running on.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


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

[Slackbuilds-users] Dos line endings in patch file

[Daniel Prosser]

Hi,

I recently updated xflr5 to the latest version. The SlackBuild includes 
a patch which is supposed to have dos line endings, since the source 
file also has dos line endings. The patch file I uploaded had dos line 
endings (and I tested before uploading), but now in the repo, it has 
unix line endings, which causes the SlackBuild to fail. I'm wondering if 
the line endings got changed in the upload process somehow and what the 
preferred way to deal with this situation is. Should I convert the 
source file to unix line endings in the SlackBuild prior to applying the 
patch? If so, what's the best way to do that? I could make dos2unix a 
required dependency and use that, but I'd prefer not to add a dependency 
if there's a better approach.


Regards,
Dan

___
SlackBuilds-users mailing list
SlackBuilds-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] Missing submission

[Daniel Prosser]

All,

Disregard, I see it actually made it into the last update. Must have 
been a last-minute inclusion. Thank you!


Dan

On 9/5/23 12:25, Daniel Prosser wrote:

Hello,

A few days ago I submitted a version bump for one of my SlackBuilds, 
graphics/ART. I don't see it in pending or approved, and I didn't 
receive an email about a problem with it. Submission md5 is 
1faaf29896ebd6989911b3e3e00d1ce7. Could someone let me know what 
happened to it? I can resubmit if needed.


Thanks,
Dan

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


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

[Slackbuilds-users] Missing submission

[Daniel Prosser]

Hello,

A few days ago I submitted a version bump for one of my SlackBuilds, 
graphics/ART. I don't see it in pending or approved, and I didn't 
receive an email about a problem with it. Submission md5 is 
1faaf29896ebd6989911b3e3e00d1ce7. Could someone let me know what 
happened to it? I can resubmit if needed.


Thanks,
Dan

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

Re: [Slackbuilds-users] Updates - 20230513.1

[Daniel Prosser]

I'm getting an md5sum mismatch for system/v4l2loopback.

> md5sum v4l2loopback-0.12.7.tar.gz
c3f043931e4d196754ad61346496ccde

> echo $MD5SUM
4b0aaae5dd8c4f5dd0f9e2142e92e390

Dan

On 5/13/23 11:01, Willy Sudiarto Raharjo wrote:

Sat May 13 12:28:22 UTC 2023
.mailmap updated
academic/boinc: Fix rc.boinc variables, remove extraneous characters
academic/hyphy: Updated for version 2.5.50.
academic/io_lib: Updated for version 1.15.0.
academic/mafft: Updated for version 7.520.
academic/meme-suite: Updated for version 5.5.2.
academic/staden: A few enhancements.
accessibility/xsel: Updated for version 1.2.1.
audio/whipper: Update REQUIRES.
audio/yabridge: Updated for version 5.0.5
desktop/UltimateDailyWallpaper: Updated for version 3.2.3.
desktop/caja: Added (file manager for the MATE desktop)
desktop/cheese: Update REQUIRES.
desktop/dbgl: Updated for version 0.97, new maintainer.
desktop/gkrellm-themes: New maintainer
desktop/gnome-control-center: Updated for version 41.7.
desktop/marco: Added (window manager for the MATE desktop)
desktop/mate-desktop: Added (libmate-desktop library for MATE)
desktop/mate-menus: Added (menu library and files for MATE)
desktop/mate-panel: Added (panel for the MATE desktop)
desktop/mate-screensaver: Added (screensaver for the MATE desktop)
desktop/mate-session-manager: Added (session manager for MATE)
desktop/mate-settings-daemon: Added (settings daemon for MATE)
desktop/mint-l-icons: Added (Mint Linux icon theme).
desktop/mint-l-theme: Added (Linux Mint theme).
desktop/mint-themes: Updated for version 2.0.9.
desktop/mint-y-icons: Updated for version 1.6.4.
desktop/nwg-look: Updated for version 0.2.2.
desktop/nwg-panel: Updated for version 0.9.2.
desktop/nwg-shell: Update REQUIRES.
development/CImg: Updated for version 3.2.4
development/apache-maven: Updated for version 3.9.2.
development/bas55: Updated for version 2.0.
development/bascat: Added (detokenizer for BBC BASIC programs)
development/beautysh: Updated for version 6.2.1, new maintainer.
development/cgdb: Updated for version 0.8.0. New maintainer.
development/dfsimage: Added (BBC micro floppy disk images utility)
development/gdb-dashboard: Added (An advanced gdb python interface)
development/github-cli: Updated for version 2.29.0.
development/hhvm: Updated for version 4.153.4
development/jupyter-ipykernel: Updated for version 6.23.0.
development/jupyter-nbclassic: Updated for version 1.0.0.
development/jupyter-nbconvert: Updated for version 7.4.0.
development/kakoune: Updated for version 2022.10.31, new maintainer.
development/ltrace: Updated for version 0.7.3_6.4.
development/neovim: Updated for version 0.9.0.
development/nodeenv: Added (Node.js virtual environment)
development/php82: Updated for version 8.2.6
development/poedit: Updated for version 3.3.
development/python3-pyqt-distutils: Added (distutils extension)
development/rarian: Updated for version 0.8.4.
development/rstudio-desktop: Move /usr/lib to /usr/lib64
development/rust16: Updated for version 1.68.1.
development/universal-ctags: Updated for version p6.0.20230507.0
development/vscode-bin: Updated for version 1.78.2.
development/xxd-standalone: Updated for version 9.0.1383.
games/chessx: Fix GUI issues.
games/pipewalker: New maintainer
git/ignore: Ignore AppImages
graphics/SweetHome3D: Updated for version 7.1.
graphics/chafa: Updated for version 1.12.4.
graphics/darktable: Use cmake rpath support.
graphics/lensfun03: Remove ld.so.conf.d.
graphics/pqiv: Updated for version 2.12, new maintainer.
graphics/tikzit: Added (a graphical tool for creating TikZ graphics)
graphics/ueberzug: Updated for version 18.1.9, new maintainer.
graphics/ueberzugpp: Added (replacement for ueberzug written in C++)
libraries/configobj: Updated for version 5.0.8.
libraries/dpdk: Added (libs and drivers for fast packet processing)
libraries/ghc_filesystem: Fix tests
libraries/goffice: Updated for version 0.10.55. New maintainer.
libraries/granite: Added (Granite is a companion for GTK and GLib.)
libraries/imlib2: Updated for version 1.11.1.
libraries/libbpf: Added (kernel-agnostic library for BPF programs)
libraries/libjodycode: Updated for version 2.0.
libraries/libmatekbd: Added (fork of libgnomekbd for MATE desktop)
libraries/libmatemixer: Added (mixer library)
libraries/libmateweather: Added (fork of libgnomeweather for MATE)
libraries/libmediainfo: Updated for version 23.04.
libraries/libopenshot-audio: Updated for version 0.3.2
libraries/libopenshot: Updated for version 0.3.2
libraries/libowfat: Updated for version 0.33.
libraries/libsoup3: Updated for version 3.4.2.
libraries/nDPI: Added (deep packet inspection library)
libraries/python-ruamel.yaml: Removed at maintainer's request.
libraries/qt-avif-image-plugin: Updated for version 0.5.3.
libraries/tomlplusplus:Fix tests
libraries/webrtc-audio-processing: Added (AudioProcessing module)
misc/KeePass: Updated for version 2.53.1.
misc/gprename: Updated for version 20230429.
misc/pokemon-colorscripts: Added (Pokemon terminal 

[Slackbuilds-users] Need to remove approved submission

[Daniel Prosser]

Admins,

Last night I submitted ART.tar.gz, an update from 1.17.2 to 1.18.1. I 
must have been tired, because evidently I forgot to actually test that 
it works, and it turns out this version segfaults on launch. It's 
already in the approved queue, so I can't use the automated form to 
remove it. Can someone revert this commit for me?


Thanks,
Dan

___
SlackBuilds-users mailing list
SlackBuilds-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] office/when has [moved]

[Daniel Prosser]

If we can't find the source tarball, maybe the name should be changed to 
"where" instead of "when".


Apologies for the bad joke.

On 1/29/23 16:41, B. Watson wrote:



On Sun, 29 Jan 2023, j+sbo-us...@maschinengott.de wrote:


https://bitbucket.org/ben-crowell/when

found via: https://github.com/bcrowell/
Because of Microsoft's harmful activities in AI, I am moving my 
software 

from github to https://bitbucket.org/ben-crowell/ .


Good deal.

However, it doesn't help with the SlackBuild: I don't see any release
tarballs at bitbucket either, so the script and .info file still will
have to be changed. Rather the maintainer do that, but I will do it
eventually if we don't hear back from him...
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


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

Re: [Slackbuilds-users] KiCad not loading symbols

[Daniel Prosser]

Hi Tim,

I think the trick was that I had to delete ~/.config/kicad, and then the 
next time I started it up, it gave me the option to copy over the global 
symbols table. Thanks for the pointers!


Dan

On 5/8/22 03:02, Tim Dickson via SlackBuilds-users wrote:
Hi Dan, when you first run kicad you need to create a project (this is 
directory and main file). then you need to start with the schematic 
editor, and kicad will ask for the locations of the files, giving you 
the option to copy the default global symbol table, which you should 
do (because the slackware packages install global data files, and 
kicad expects each user to use their own copy)


Now you can place devices on the schematic, and power rails and 
connections between them. (that works fine on mine)
then you need to set the footprints for each device (the physical 
sizes of the devices). Finally, you can open the pcb editor, and load 
in your schematic. you can then place the devices, and sort out the 
routing etc.
If you did the kicad-packages-3D then you are also able to view a 
preview of your circuit board in 3d.


I didn't have to set any environment variables or do anything special. 
(at least to get as far as the schematic editor and adding parts from 
the library)


Regards, Tim

On 08/05/2022 04:25, Daniel Prosser wrote:

Hello,


Hopefully someone knows something about KiCad and can tell me what 
I'm doing wrong. I am a complete novice trying to learn how to use 
it. I installed it from SBo along with all dependencies as well as 
most of the extra packages (kicad-symbols, kicad-templates, 
kicad-footprints, skipped kicad-packages3D because it's so huge), but 
when I go to insert a symbol in the schematic editor, there are none 
available. I checked in the preferences and it does have the relevant 
environment variable pointing to /usr/share/kicad/library, where 
kicad-symbols installs the files, but it still doesn't "see" them 
there. Also, there were no symbols installed by the base kicad 
package; I'm not sure if that is expected or not.


Am I missing some simple step to load the symbols library, or did 
something go wrong with the build?



Thanks,

Dan


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





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

[Slackbuilds-users] KiCad not loading symbols

[Daniel Prosser]

Hello,


Hopefully someone knows something about KiCad and can tell me what I'm 
doing wrong. I am a complete novice trying to learn how to use it. I 
installed it from SBo along with all dependencies as well as most of the 
extra packages (kicad-symbols, kicad-templates, kicad-footprints, 
skipped kicad-packages3D because it's so huge), but when I go to insert 
a symbol in the schematic editor, there are none available. I checked in 
the preferences and it does have the relevant environment variable 
pointing to /usr/share/kicad/library, where kicad-symbols installs the 
files, but it still doesn't "see" them there. Also, there were no 
symbols installed by the base kicad package; I'm not sure if that is 
expected or not.


Am I missing some simple step to load the symbols library, or did 
something go wrong with the build?



Thanks,

Dan


___
SlackBuilds-users mailing list
SlackBuilds-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] Hosting source tarballs

[Daniel Prosser]

Willy,

Thanks. That wasn't really clear to me, but I remembered how to upload 
to slackbuildsdirectlinks on SourceForge. For anyone wondering:


1. You need a SourceForge account and Willy to give you appropriate
   permissions to the slackbuildsdirectlinks project.
2. Use sftp to connect to @frs.sourceforge.net
3. Navigate to /home/frs/project/slackbuildsdirectlinks and create a
   directory there for your SlackBuild if it doesn't already exist.
4. Upload the file.

Note: mc can handle connecting and uploading the file with SFTP.

Dan

On 4/14/22 09:25, Willy Sudiarto Raharjo wrote:

My username on SourceForge is montagdp. I think I may already have
access to upload sources there, but I don't remember where or how.

Then you can connect to web.sourceforge.net using your SF account and
you can create directory according to your script name and upload it there



___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ -https://slackbuilds.org/faq/
___
SlackBuilds-users mailing list
SlackBuilds-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] Hosting source tarballs

[Daniel Prosser]

Hey Willy,

My username on SourceForge is montagdp. I think I may already have 
access to upload sources there, but I don't remember where or how.


Thanks,

Dan

On 4/13/22 19:01, Willy Sudiarto Raharjo wrote:

I would like to submit an update for one of my SlackBuilds, xflr5. The
source code for this is only available via a per-request snapshot from
the project's "Code" section on SourceForge, which can't be obtained by
a direct link in a repeatable way. It's been awhile since I updated
this, and I forgot how I uploaded a source tarball the last time. It
looks like the current one is hosted on sbosrcarch. I also recall
uploading things to an SBo source code repository on SourceForge in the
past with ftp, but I can't remember the details of how that worked
either. Can someone help me out?

Send me your SourceForge account (username) and i will add you to list
of members who can upload sources there



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


___
SlackBuilds-users mailing list
SlackBuilds-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] Hosting source tarballs

[Daniel Prosser]

I would like to submit an update for one of my SlackBuilds, xflr5. The 
source code for this is only available via a per-request snapshot from 
the project's "Code" section on SourceForge, which can't be obtained by 
a direct link in a repeatable way. It's been awhile since I updated 
this, and I forgot how I uploaded a source tarball the last time. It 
looks like the current one is hosted on sbosrcarch. I also recall 
uploading things to an SBo source code repository on SourceForge in the 
past with ftp, but I can't remember the details of how that worked 
either. Can someone help me out?


Regards,

Dan

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

Re: [Slackbuilds-users] best way to mass-rebuild? (w/dependencies?)

[Daniel Prosser]

There's no reliable way to compare versions, since different projects 
use completely different version numbering paradigms, and even a single 
project may switch paradigms. Imagine trying to compare version "3.0" of 
something with version "git1e8fr49cx". Which one is the later version? 
As you said, the best way is to use a different tag for custom-built 
stuff. Another option with sboui in particular is to blacklist 
custom-built packages.


Dan

On 2/11/22 09:03, Erich Ritz via SlackBuilds-users wrote:


--- Original Message ---

On Friday, February 11th, 2022 at 2:02 AM, David O'Shaughnessy 
 wrote:


On Fri, 11 Feb 2022, at 3:44 PM, David Chmelik wrote:


  If I want to mass-rebuild all my installed packages in one go ('at


once') including w/queues, what's the best way? I thought it was

sbotools, but depending what I used for end of package name (_SBo or

ponce,) sbotools seemed to replace some newer versions (I upgraded and

some perhaps reverted in SBo-git, unsure) with old ones.

One quick way:

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

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

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


Too late now, but perhaps use a different TAG for custom-built stuff (e.g. 
SBo_custom)?  I admit I don't do this myself...

Erich


---

Dave


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


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

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

[Daniel Prosser]

I believe the suggestion was to make life easier for package maintainers, not builders. On Jan 4, 2022 4:48 PM, Andrzej Telszewski  wrote:
Jan 4, 2022 10:11:00 PM Klaatu :
> Why do we define the VERSION for a package in two separate files?
>  
> What if we replaced this line in foo.SlackBuild:
> VERSION={VERSION:-0.0.1}
>  
> with this instead:
> . ./$PRGNAM.info
>  
> The VERSION variable would get imported from a consolidated location (the .info file).
>  
> It seems to make more sense to me, and it makes trivial upgrades (the ones where I go in and just bump a version number to something I want to build) a one-file task.
>  
> Thoughts?
You can source .info before executing .SlackBuild to get the same effect. No changes needed. :-)
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
___
SlackBuilds-users mailing list
SlackBuilds-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] Bug in matplotlib setupext.py

[Daniel Prosser]

Hi,

Matplotlib has a custom setupext.py script designed to stop the build 
when a dependency is not installed. However, it seems to have a bug 
which makes it crash with this error:


Traceback (most recent call last):  File "setup.py", line 172, in 
    result = package.check()  File 
"/tmp/SBo/matplotlib-2.2.3/setupext.py", line 1480, in check    
print_status(package.name, req_fail_msg)NameError: global name 'package' 
is not defined


Is this the expected behavior? The following patch will avoid the error 
and still stop the build if there is a missing dependency, with an 
actual helpful list of dependencies that have not been installed:


--- setupext.py 2020-03-16 10:02:52.376214282 -0400
+++ setupext.py.new 2020-03-16 10:03:34.462812966 -0400
@@ -1477,7 +1477,7 @@
 req_fail_msg += (os.linesep.join(not_available) +
 os.linesep*(2*sp_mult)) * min(1, 
len(not_available))
 req_fail_msg += (os.linesep*2).join(wrong_version)
- print_status(package.name, req_fail_msg)
+ print_status(pack_name, req_fail_msg)
 raise CheckFailed("missing or faulty third-party python packages")
 return "all third-party python packages are present"

Regards,

Dan

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

Re: [Slackbuilds-users] Updates - 20200118.1

[Daniel Prosser]

Thanks, I got it.

On 1/19/20 3:10 PM, Lenard Spencer wrote:

downloads.sourceforge.net <http://downloads.sourceforge.net>


On Sun, Jan 19, 2020, 15:09 Lenard Spencer <mailto:lenardrspen...@gmail.com>> wrote:


url should be downloads.spouceforge.net
<http://downloads.spouceforge.net>.
I have just sent the corrected SBo package, should be in the next
update.

On Sun, Jan 19, 2020, 14:20 Daniel Prosser mailto:dpross1...@msn.com>> wrote:

Getting 404 on
https://sourceforge.net/flightgear/FlightGear-2019.1.2-data-rc.tar.bz2.

Dan

On 1/18/20 12:56 AM, Willy Sudiarto Raharjo wrote:

Hello everyone

You did another amazing job this week.
Lots of new scripts, version update, and also some removal.

Urchlay is going to work on jack-audio-connection-kit > jack2 transition
and i will be working on letsencrypt transition. Upstream is now moving
towards Python3 only for future letsencrypt/certbot and as this script
is used in many production systems, i need some time to make sure it
works. Almost all of the deps need to be rebuilt against Python 3, but i
will post more information for next public update.

Urchlay is also working on some mini project to improve our website
functionality. Stay tune for more updates :)


Sat Jan 18 05:26:22 UTC 2020
academic/WordNet: Assume maintainership
academic/antiprism: Assume maintainership
academic/coq: Updated for version 8.9.0.
academic/tabix: Removed.
academic/wehi-weasel: Updated for version 3.6.11.8.
academic/xcircuit: Assume maintainership
academic/zotero: Updated for version 5.0.81.
audio/alsa-plugin-jack: Fix README.
audio/alsa-plugin-jack: Fix download link.
audio/audioconvert: Assume maintainership
audio/azr3: Convert slack-desc to ASCII.
audio/calf: Demote lash from required to optional dep.
audio/deezer-desktop-for-linux: Removed (No longer maintained upstream).
audio/drumkv1: Updated for version 0.9.12.
audio/ecasound: Updated for version 2.9.3.
audio/faac: Updated for version 1.30.
audio/faad2: Updated for version 2.9.1.
audio/horgand: Fix first-time startup.
audio/jack2: Remove --profile build option.
audio/ngjackspa: Fix homepage and download.
audio/padthv1: Updated for version 0.9.12.
audio/samplv1: Updated for version 0.9.12.
audio/synthv1: Updated for version 0.9.12.
audio/tapiir: Fix homepage and download.
audio/tta: Assume maintainership
audio/tuxguitar: Make .desktop file validate.
audio/xcfa: Assume maintainership
desktop/Buku: Assume maintainership.
desktop/draco: Convert slack-desc to ASCII.
desktop/gnome-menus: New maintainer.
desktop/xfce4-datetime-plugin: Updated for version 0.8.0.
development/Fennel: Updated for version 0.3.2.
development/android-studio: Make .desktop file validate.
development/atom-amd64: Convert slack-desc to ASCII.
development/avr-binutils: Assume maintainership
development/avra: Assume maintainership
development/avrdude: Assume maintainership
development/bless: Convert slack-desc to ASCII.
development/cgit: Updated for version 1.2.2.
development/composer: Updated for version 1.9.2
development/gambas3: Updated for version 3.14.3.
development/google-go-lang: Updated to version go1.13.5.
development/kakoune: Convert slack-desc to ASCII.
development/kotlin: Convert slack-desc to ASCII.
development/neovim: Convert slack-desc to ASCII.
development/netbeans: Make .desktop file validate.
development/nwjs: Convert slack-desc to ASCII.
development/portaudio: Fix builds with jack/jack2.
development/re2c: Updated for version 1.3.
development/setedit: Added (a friendly text editor).
development/smartsvn: Make .desktop file validate.
development/snappy: Return to original maintainer.
development/sublime_merge: Make .desktop file validate.
development/swi-prolog: Updated for version 8.0.3.
development/textadept: Updated for version 10.8.
development/tidy-html5: Convert slack-desc to ASCII.
development/vscode-bin: Make .desktop file validate.
development/zope.interface: Add python3 support.
games/abuse: Assume maintainership
games/antares: Moved from graphics.
games/lbreakout2: Assume maintainership
games/smokinguns: Assume maintainership
games/vkQuake: Updated for version 1.04.0.
graphics/icc_profiles: Added (Rec709 and ITU color management).
graphics/icc_profiles_from_eci: Added (ECI ICC profiles).
graphics/iccprofiles: Removed (see icc_profi

Re: [Slackbuilds-users] Updates - 20200118.1

[Daniel Prosser]

Getting 404 on 
https://sourceforge.net/flightgear/FlightGear-2019.1.2-data-rc.tar.bz2.


Dan

On 1/18/20 12:56 AM, Willy Sudiarto Raharjo wrote:

Hello everyone

You did another amazing job this week.
Lots of new scripts, version update, and also some removal.

Urchlay is going to work on jack-audio-connection-kit > jack2 transition
and i will be working on letsencrypt transition. Upstream is now moving
towards Python3 only for future letsencrypt/certbot and as this script
is used in many production systems, i need some time to make sure it
works. Almost all of the deps need to be rebuilt against Python 3, but i
will post more information for next public update.

Urchlay is also working on some mini project to improve our website
functionality. Stay tune for more updates :)


Sat Jan 18 05:26:22 UTC 2020
academic/WordNet: Assume maintainership
academic/antiprism: Assume maintainership
academic/coq: Updated for version 8.9.0.
academic/tabix: Removed.
academic/wehi-weasel: Updated for version 3.6.11.8.
academic/xcircuit: Assume maintainership
academic/zotero: Updated for version 5.0.81.
audio/alsa-plugin-jack: Fix README.
audio/alsa-plugin-jack: Fix download link.
audio/audioconvert: Assume maintainership
audio/azr3: Convert slack-desc to ASCII.
audio/calf: Demote lash from required to optional dep.
audio/deezer-desktop-for-linux: Removed (No longer maintained upstream).
audio/drumkv1: Updated for version 0.9.12.
audio/ecasound: Updated for version 2.9.3.
audio/faac: Updated for version 1.30.
audio/faad2: Updated for version 2.9.1.
audio/horgand: Fix first-time startup.
audio/jack2: Remove --profile build option.
audio/ngjackspa: Fix homepage and download.
audio/padthv1: Updated for version 0.9.12.
audio/samplv1: Updated for version 0.9.12.
audio/synthv1: Updated for version 0.9.12.
audio/tapiir: Fix homepage and download.
audio/tta: Assume maintainership
audio/tuxguitar: Make .desktop file validate.
audio/xcfa: Assume maintainership
desktop/Buku: Assume maintainership.
desktop/draco: Convert slack-desc to ASCII.
desktop/gnome-menus: New maintainer.
desktop/xfce4-datetime-plugin: Updated for version 0.8.0.
development/Fennel: Updated for version 0.3.2.
development/android-studio: Make .desktop file validate.
development/atom-amd64: Convert slack-desc to ASCII.
development/avr-binutils: Assume maintainership
development/avra: Assume maintainership
development/avrdude: Assume maintainership
development/bless: Convert slack-desc to ASCII.
development/cgit: Updated for version 1.2.2.
development/composer: Updated for version 1.9.2
development/gambas3: Updated for version 3.14.3.
development/google-go-lang: Updated to version go1.13.5.
development/kakoune: Convert slack-desc to ASCII.
development/kotlin: Convert slack-desc to ASCII.
development/neovim: Convert slack-desc to ASCII.
development/netbeans: Make .desktop file validate.
development/nwjs: Convert slack-desc to ASCII.
development/portaudio: Fix builds with jack/jack2.
development/re2c: Updated for version 1.3.
development/setedit: Added (a friendly text editor).
development/smartsvn: Make .desktop file validate.
development/snappy: Return to original maintainer.
development/sublime_merge: Make .desktop file validate.
development/swi-prolog: Updated for version 8.0.3.
development/textadept: Updated for version 10.8.
development/tidy-html5: Convert slack-desc to ASCII.
development/vscode-bin: Make .desktop file validate.
development/zope.interface: Add python3 support.
games/abuse: Assume maintainership
games/antares: Moved from graphics.
games/lbreakout2: Assume maintainership
games/smokinguns: Assume maintainership
games/vkQuake: Updated for version 1.04.0.
graphics/icc_profiles: Added (Rec709 and ITU color management).
graphics/icc_profiles_from_eci: Added (ECI ICC profiles).
graphics/iccprofiles: Removed (see icc_profiles).
graphics/vuescan: Updated for version 9.7.20.
ham/direwolf: Updated for version 1.5.
ham/hamlib: New maintainer.
ham/qrq: New maintainer.
ham/tlf: New maintainer.
ham/wsjtx: New maintainer.
ham/xdemorse: Make .desktop file validate.
ham/xdx: New maintainer.
ham/xlog: New maintainer.
haskell/haskell-microlens: Convert slack-desc to ASCII.
haskell/haskell-pipes: Added (stream processing library).
lbraries/librhtv: Fix build.
libraries/SimGear: Fix DOWNLOAD url.
libraries/antlr4: Updated for version 4.8.
libraries/configobj: Updated for version 5.0.6, python3 support.
libraries/ftgl: Disable docs to avoid texlive.
libraries/hdf5: Updated for version 1.8.21.
libraries/leptonica: Updated for version 1.79.0.
libraries/libdbusmenu: Updated for version 18.10.20180917~bzr492.
libraries/libmp4v2: Updated for version 20191108_9084868.
libraries/libthai: Convert slack-desc to ASCII.
libraries/libxml++3: Updated for version 3.2.0.
libraries/live555: Updated for version 2020.01.11
libraries/ntl: Updated for version 11.4.3.
libraries/pyPEG2: Assume maintainership
libraries/zope.component: Add python3 support.
libraries/zope.event: Add python3 

Re: [Slackbuilds-users] portaudio

[Daniel Prosser]

I updated last night and it worked for me.

Dan

On Aug 18, 2019 9:37 AM, Alexander Verbovetsky  wrote:

Hello,

On Sun, 18 Aug 2019, at 04:17, Willy Sudiarto Raharjo wrote:
> development/portaudio: Updated for version v190600_20161030.

For me it fails:

-
...
mv -f .deps/StreamParameters.Tpo .deps/StreamParameters.Plo
mv -f .deps/SystemDeviceIterator.Tpo .deps/SystemDeviceIterator.Plo
mv -f .deps/SystemHostApiIterator.Tpo .deps/SystemHostApiIterator.Plo
mv -f .deps/System.Tpo .deps/System.Plo
make[2]: Leaving directory 
'/tmp/SBo/slackrepo.VsP4rm/build_portaudio/portaudio/bindings/cpp/lib'
Makefile:431: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
'/tmp/SBo/slackrepo.VsP4rm/build_portaudio/portaudio/bindings/cpp'
Makefile:251: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 2
make: *** Waiting for unfinished jobs
-

Is it just me?

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


___
SlackBuilds-users mailing list
SlackBuilds-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] scipy3: cannot find numpy3 when building [RESOLVED]

[Daniel Prosser]

Hm, I doubt it. I checked Rich's original email, and this was the actual 
error message when he tried to build scipy3:

Traceback (most recent call last):
   File "setup.py", line 474, in 
     setup_package()
   File "setup.py", line 450, in setup_package
     from numpy.distutils.core import setup
ModuleNotFoundError: No module named 'numpy'

On 8/8/19 10:32 PM, Duncan Roe wrote:
> On Fri, Aug 09, 2019 at 01:44:02AM +, Daniel Prosser wrote:
>> That's because the software itself is just called numpy. The package was 
>> named numpy3 to distinguish it from the Python 2 version. The numpy stuff in 
>> /usr/lib64/python3.7 comes from the numpy3 package.
>>
>> Dan
>>
> So the original message, "scipy3: cannot find numpy3 when building" is output
> by an SBo script when it sees REQUIRES="numpy3 ..." and
> /var/log/packages/numpy3-1.14.3-x86_64-1P_SBo does not exist.
>
> Could that be the underlying problem?
>
> Cheers ... Duncan.
>> On Aug 8, 2019 9:22 PM, Duncan Roe  wrote:
>>
>> Hey Rich,
>>
>> On Thu, Aug 08, 2019 at 02:06:36PM -0700, Rich Shepard wrote:
>>> On Thu, 8 Aug 2019, Didier Spaier wrote:
>>>
>>>> Please run from the systems in concern as root: updateb
>>> Didier,
>>>
>>> updatedb runs automatically overnight. The system is not turned off when I
>>> log out.
>>>
>>>> then provide the full output of this command:
>>>> locate numpy.py
>>> # locate numpy.py
>>> /usr/share/apps/kdevpythonsupport/documentation_files/numpy.py
>>> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.pyc
>>> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.py
>>> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.py
>>> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.pyc
>>> /home/rshepard/gis/grass/grass_dev/lib/python/pygrass/raster/testsuite/test_numpy.py
>>>
>>> But, ...
>>>
>>> # find / -name numpy
>>> /usr/lib64/python2.7/site-packages/numpy
>>> /usr/lib64/python2.7/site-packages/pandas/compat/numpy
>>> /usr/lib64/python2.7/site-packages/Cython/Includes/numpy
>>> /usr/lib64/R/library/BH/include/boost/python/numpy
>>> /usr/lib64/python3.7/site-packages/numpy
>>> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy
>>> /var/lib/sbopkg/SBo/14.2/development/numpy
>>> /opt/slackbuilds/Development/numpy
>> These are all directories. If you try again with "-tye f" you won't see them.
>> (Quick check: find /usr/lib64 -type f -name numpy).
>>> Rich
>>> ___
>> I tried this:
>>
>> 09:12:16# find /usr/lib64 /usr/src/slackbuilds -type f -name '*numpy*'
>> /usr/lib64/python3.7/site-packages/numpy/core/__pycache__/generate_numpy_api.cpython-37.pyc
>> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
>> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy/numpyconfig.h
>> /usr/lib64/python3.7/site-packages/numpy/core/generate_numpy_api.py
>> /usr/lib64/python3.7/site-packages/numpy/distutils/__pycache__/numpy_distribution.cpython-37.pyc
>> /usr/lib64/python3.7/site-packages/numpy/distutils/numpy_distribution.py
>> /usr/lib64/python3.7/site-packages/numpy/tests/test_numpy_version.py
>> /usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.pyc
>> /usr/lib64/python2.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
>> /usr/lib64/python2.7/site-packages/numpy/core/include/numpy/numpyconfig.h
>> /usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.py
>> /usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.pyc
>> /usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.py
>> /usr/lib64/python2.7/site-packages/numpy/tests/test_numpy_version.py
>> /usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.py
>> /usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.pyc
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.pyc
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.py
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.py
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.pyc
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.py
>> /usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.pyc
>> /usr/lib64/python2.7/site-packages/vtk/util/numpy_support.py
>> /usr/lib

Re: [Slackbuilds-users] scipy3: cannot find numpy3 when building [RESOLVED]

[Daniel Prosser]

That's because the software itself is just called numpy. The package was named 
numpy3 to distinguish it from the Python 2 version. The numpy stuff in 
/usr/lib64/python3.7 comes from the numpy3 package.

Dan


On Aug 8, 2019 9:22 PM, Duncan Roe  wrote:

Hey Rich,

On Thu, Aug 08, 2019 at 02:06:36PM -0700, Rich Shepard wrote:
> On Thu, 8 Aug 2019, Didier Spaier wrote:
>
> > Please run from the systems in concern as root: updateb
>
> Didier,
>
> updatedb runs automatically overnight. The system is not turned off when I
> log out.
>
> > then provide the full output of this command:
> > locate numpy.py
>
> # locate numpy.py
> /usr/share/apps/kdevpythonsupport/documentation_files/numpy.py
> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.pyc
> /usr/lib64/python2.7/site-packages/astroid/tests/unittest_brain_numpy.py
> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.py
> /usr/lib64/python2.7/site-packages/astroid/brain/brain_numpy.pyc
> /home/rshepard/gis/grass/grass_dev/lib/python/pygrass/raster/testsuite/test_numpy.py
>
> But, ...
>
> # find / -name numpy
> /usr/lib64/python2.7/site-packages/numpy
> /usr/lib64/python2.7/site-packages/pandas/compat/numpy
> /usr/lib64/python2.7/site-packages/Cython/Includes/numpy
> /usr/lib64/R/library/BH/include/boost/python/numpy
> /usr/lib64/python3.7/site-packages/numpy
> /usr/lib64/python3.7/site-packages/numpy/core/include/numpy
> /var/lib/sbopkg/SBo/14.2/development/numpy
> /opt/slackbuilds/Development/numpy

These are all directories. If you try again with "-tye f" you won't see them.
(Quick check: find /usr/lib64 -type f -name numpy).
>
> Rich
> ___
I tried this:

09:12:16# find /usr/lib64 /usr/src/slackbuilds -type f -name '*numpy*'
/usr/lib64/python3.7/site-packages/numpy/core/__pycache__/generate_numpy_api.cpython-37.pyc
/usr/lib64/python3.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
/usr/lib64/python3.7/site-packages/numpy/core/include/numpy/numpyconfig.h
/usr/lib64/python3.7/site-packages/numpy/core/generate_numpy_api.py
/usr/lib64/python3.7/site-packages/numpy/distutils/__pycache__/numpy_distribution.cpython-37.pyc
/usr/lib64/python3.7/site-packages/numpy/distutils/numpy_distribution.py
/usr/lib64/python3.7/site-packages/numpy/tests/test_numpy_version.py
/usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.pyc
/usr/lib64/python2.7/site-packages/numpy/core/include/numpy/_numpyconfig.h
/usr/lib64/python2.7/site-packages/numpy/core/include/numpy/numpyconfig.h
/usr/lib64/python2.7/site-packages/numpy/core/generate_numpy_api.py
/usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.pyc
/usr/lib64/python2.7/site-packages/numpy/distutils/numpy_distribution.py
/usr/lib64/python2.7/site-packages/numpy/tests/test_numpy_version.py
/usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.py
/usr/lib64/python2.7/site-packages/scipy/_lib/_numpy_compat.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_utils.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.pyc
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle.py
/usr/lib64/python2.7/site-packages/sklearn/externals/joblib/numpy_pickle_compat.pyc
/usr/lib64/python2.7/site-packages/vtk/util/numpy_support.py
/usr/lib64/python2.7/site-packages/vtk/util/numpy_support.pyc
/usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.py
/usr/lib64/python2.7/site-packages/statsmodels/compat/numpy.pyc
/usr/src/slackbuilds/python/numpydoc/numpydoc.SlackBuild
/usr/src/slackbuilds/python/numpydoc/numpydoc.info
/usr/src/slackbuilds/development/numpy3/numpy3.SlackBuild
/usr/src/slackbuilds/development/numpy3/numpy3.info
/usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.info
/usr/src/slackbuilds/development/numpy-legacy3/numpy-legacy3.SlackBuild
/usr/src/slackbuilds/development/numpy/numpy.info
/usr/src/slackbuilds/development/numpy/numpy.SlackBuild
/usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.info
/usr/src/slackbuilds/development/numpy-legacy/numpy-legacy.SlackBuild

Here's the rub: I *do* have numpy3 installed. But no files named '*numpy3*'
anywhere in the system except /var/log/packages/numpy3-1.14.3-x86_64-1P_SBo

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


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

Re: [Slackbuilds-users] Merging python / python3 packages

[Daniel Prosser]

I like the idea of having a single script for both Python 2 and Python 3 
versions of each module (or as many as possible), but I don't think a lot of 
work should be done to enforce uniformity for 14.2. When Slackware 15 comes 
out, Python 3 will be included and the issue of dependencies will be moot for 
most scripts. For now, I can deal with maintainers taking different approaches.
___
SlackBuilds-users mailing list
SlackBuilds-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] MD5sum wrong for kodi

[Daniel Prosser]

Actually, you can ignore that last email. Seems I just had a bad
download. Sorry for the noise.

Dan

On Wed, Feb 06, 2019 at 03:46:56PM +, Daniel Prosser wrote:
> Hi,
> 
> I'm not sure if the upstream source has changed, but this is the md5sum
> I get for kodi:
> 
> # md5sum xbmc-17.6-Krypton.tar.gz
> 17a0aaf77d641a2cd52c8728bddaf898  xbmc-17.6-Krypton.tar.gz
> 
> The .info file has
> a64c2fc56ddc41b9b0dded55eaabf170
> 
> Dan
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] MD5sum wrong for kodi

[Daniel Prosser]

Hi,

I'm not sure if the upstream source has changed, but this is the md5sum
I get for kodi:

# md5sum xbmc-17.6-Krypton.tar.gz
17a0aaf77d641a2cd52c8728bddaf898  xbmc-17.6-Krypton.tar.gz

The .info file has
a64c2fc56ddc41b9b0dded55eaabf170

Dan
___
SlackBuilds-users mailing list
SlackBuilds-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] git clone instead of downloading a source tarball

[Daniel Prosser]

To add to what Willy said, SlackBuilds on SBo don't download source tarballs 
either. That is up to the user or the tool used.
___
SlackBuilds-users mailing list
SlackBuilds-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] ZoneMinder build fails if ffmpeg is not installed

[Daniel Prosser]

Willy,

Here are three patches. The first one you should be able to apply to
ZoneMinder in the SBo git. The second two are patches executed by the
SlackBuild. fix_video_file_format.patch is the one I mentioned
previously that was needed on my system for ZoneMinder to encode mp4
videos for events. fix_zone_area_calc.patch applies upstream commits
4937a686 and 4da95369. I also added ffmpeg, libmp4v2, and x264 as
dependencies and noted php-apcu as an optional dependency. Hopefully
the maintainer will also weigh in on these changes.

Dan

On Fri, Jan 25, 2019 at 08:33:46PM +0700, Willy Sudiarto Raharjo wrote:
> > One final (I think) note: if you want to use the ZoneMinder API, you also
> > need to have  php-apcu installed. It would be good to document these things
> > so that users don't have to dig to find it.
> 
> >> Thanks Willy. A couple more notes/issues/fixes for this new version:
> >>
> >> 1. By default, ZoneMinder now saves events as mp4 videos instead of
> >> frames. For this to work, x264 and libmp4v2 must be installed prior to
> >> building. It's still possible to just use image frames as before, but I
> >> think x264 and libmp4v2 need to be at least optional dependencies.
> >> Personally, I think they should be required, as otherwise the user will
> >> have to switch to saving image frames only.
> >>
> >> 2. Even with x264 and libmp4v2 installed, ZoneMinder was still unable to
> >> save videos for me. I had to apply the attached patch for it to work.
> >> I'm not really sure why that's the case, since I didn't find any other
> >> reports of it not working as is. GenoBob, perhaps you and/or any other
> >> Slackware ZoneMinder users can report whether it works for you (and add
> >> this patch to the SlackBuild if appropriate)?
> >>
> >> 3. This version stores events and other data in ZM_CONTENTDIR, which
> >> defaults to /var/lib/zoneminder. However, the SlackBuild script doesn't
> >> create this directory, so there are initially errors when running until
> >> the user manually creates it. (It needs to be owned by apache:apache). I
> >> recommend having the SlackBuild script create this directory as part of the
> >> package, and make it a build option so it can be changed at build time.
> >>
> >> Don't take these comments as a criticism. I am really grateful for the
> >> script and I'm glad that it's basically working for me now. I was actually
> >> procrastinating upgrading to 1.32.x because of all the changes. I just
> >> want to help make the installation process as smooth as possible for
> >> others.
> 
> Hi Dan
> 
> Thanks for this investigations
> 
> would you mind sending me the patch for this improvements?
> 
> 
> 
> -- 
> Willy Sudiarto Raharjo
> 



From 71bb0f053b55f52de819efb46040d679d25236cd Mon Sep 17 00:00:00 2001
From: Daniel Prosser 
Date: Mon, 28 Jan 2019 16:22:29 -0500
Subject: [PATCH] Add ZoneMinder patches, CONTENTDIR, and update requires

---
 system/ZoneMinder/README  | 10 
 system/ZoneMinder/ZoneMinder.SlackBuild   | 12 +++--
 system/ZoneMinder/ZoneMinder.info |  2 +-
 system/ZoneMinder/fix_video_file_format.patch | 11 +
 system/ZoneMinder/fix_zone_area_calc.patch| 35 +++
 5 files changed, 62 insertions(+), 8 deletions(-)
 create mode 100644 system/ZoneMinder/fix_video_file_format.patch
 create mode 100644 system/ZoneMinder/fix_zone_area_calc.patch

diff --git a/system/ZoneMinder/README b/system/ZoneMinder/README
index d96eb97904..44db1da50e 100644
--- a/system/ZoneMinder/README
+++ b/system/ZoneMinder/README
@@ -7,10 +7,10 @@ be controlled via web or semi-automatically using a variety of
 protocols. It can also be integrated into a home automation system
 via X.10 or other protocols.  This build includes cambozola and jscalendar.
 
-Optional dependencies are ffmpeg (video streaming and recoding support),
-perl-Archive-Zip (automatic event uploading), perl-X10
-(integration with X10-based home automation), perl-Device-SerialPort
-(RS232/RS485 PTZ camera control), perl-MIME-Lite, and perl-MIME-Entity
-(automatic event mail notification).
+Optional dependencies are php-apcu (to enable the ZoneMinder API),
+perl-Archive-Zip (automatic event uploading), perl-X10 (integration with
+X10-based home automation), perl-Device-SerialPort (RS232/RS485 PTZ camera
+control), perl-MIME-Lite, and perl-MIME-Entity (automatic event mail
+notification).
 
 See README.SLACKWARE for configuration information.
diff --git a/system/ZoneMinder/ZoneMinder.SlackBuild 
b/system/ZoneMinder/ZoneMinder.SlackBuild
index 1423b69fc4..222d092dc5 100644
--- a/system/ZoneMinder/ZoneMinder.SlackBuild
+++ b/system/ZoneMinder/

Re: [Slackbuilds-users] ZoneMinder build fails if ffmpeg is not installed

[Daniel Prosser]

Certainly. It might take me a few days to get around to it, but I'll try to 
have it in before next week's update.

Dan


On Jan 25, 2019 8:33 AM, Willy Sudiarto Raharjo  wrote:

> One final (I think) note: if you want to use the ZoneMinder API, you also
> need to have  php-apcu installed. It would be good to document these things
> so that users don't have to dig to find it.

>> Thanks Willy. A couple more notes/issues/fixes for this new version:
>>
>> 1. By default, ZoneMinder now saves events as mp4 videos instead of
>> frames. For this to work, x264 and libmp4v2 must be installed prior to
>> building. It's still possible to just use image frames as before, but I
>> think x264 and libmp4v2 need to be at least optional dependencies.
>> Personally, I think they should be required, as otherwise the user will
>> have to switch to saving image frames only.
>>
>> 2. Even with x264 and libmp4v2 installed, ZoneMinder was still unable to
>> save videos for me. I had to apply the attached patch for it to work.
>> I'm not really sure why that's the case, since I didn't find any other
>> reports of it not working as is. GenoBob, perhaps you and/or any other
>> Slackware ZoneMinder users can report whether it works for you (and add
>> this patch to the SlackBuild if appropriate)?
>>
>> 3. This version stores events and other data in ZM_CONTENTDIR, which
>> defaults to /var/lib/zoneminder. However, the SlackBuild script doesn't
>> create this directory, so there are initially errors when running until
>> the user manually creates it. (It needs to be owned by apache:apache). I
>> recommend having the SlackBuild script create this directory as part of the
>> package, and make it a build option so it can be changed at build time.
>>
>> Don't take these comments as a criticism. I am really grateful for the
>> script and I'm glad that it's basically working for me now. I was actually
>> procrastinating upgrading to 1.32.x because of all the changes. I just
>> want to help make the installation process as smooth as possible for
>> others.

Hi Dan

Thanks for this investigations

would you mind sending me the patch for this improvements?



--
Willy Sudiarto Raharjo


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

Re: [Slackbuilds-users] ZoneMinder build fails if ffmpeg is not installed

[Daniel Prosser]

GenoBob,

One final (I think) note: if you want to use the ZoneMinder API, you also
need to have  php-apcu installed. It would be good to document these things
so that users don't have to dig to find it.

Dan

On Tue, Jan 22, 2019 at 04:46:22AM +, Daniel Prosser wrote:
> Thanks Willy. A couple more notes/issues/fixes for this new version:
> 
> 1. By default, ZoneMinder now saves events as mp4 videos instead of
> frames. For this to work, x264 and libmp4v2 must be installed prior to
> building. It's still possible to just use image frames as before, but I
> think x264 and libmp4v2 need to be at least optional dependencies.
> Personally, I think they should be required, as otherwise the user will
> have to switch to saving image frames only.
> 
> 2. Even with x264 and libmp4v2 installed, ZoneMinder was still unable to
> save videos for me. I had to apply the attached patch for it to work.
> I'm not really sure why that's the case, since I didn't find any other
> reports of it not working as is. GenoBob, perhaps you and/or any other
> Slackware ZoneMinder users can report whether it works for you (and add
> this patch to the SlackBuild if appropriate)?
> 
> 3. This version stores events and other data in ZM_CONTENTDIR, which
> defaults to /var/lib/zoneminder. However, the SlackBuild script doesn't
> create this directory, so there are initially errors when running until
> the user manually creates it. (It needs to be owned by apache:apache). I
> recommend having the SlackBuild script create this directory as part of the
> package, and make it a build option so it can be changed at build time.
> 
> Don't take these comments as a criticism. I am really grateful for the
> script and I'm glad that it's basically working for me now. I was actually
> procrastinating upgrading to 1.32.x because of all the changes. I just
> want to help make the installation process as smooth as possible for
> others.
> 
> Dan
> 
> On Mon, Jan 21, 2019 at 06:56:13AM +0700, Willy Sudiarto Raharjo wrote:
> > > ffmpeg is listed as an optional dependency for ZoneMinder, but in a
> > > clean Slackware64-14.2 container, if ffmpeg isn't installed, I get the
> > > attached errors. Should ffmpeg be listed as a required dependency now?
> > 
> > Thanks Dan
> > 
> > I have added ffmpeg into the REQUIRES line now
> > 
> > Thanks
> > 
> > 
> > -- 
> > Willy Sudiarto Raharjo
> > 
> 
> 
> 

> --- src/zm_event.cpp2019-01-21 23:17:19.881961455 -0500
> +++ src/zm_event.cpp.new2019-01-21 23:17:38.452315254 -0500
> @@ -196,7 +196,7 @@
> 
>if ( monitor->GetOptVideoWriter() != 0 ) {
>  snprintf(video_name, sizeof(video_name), "%" PRIu64 "-%s", id, 
> "video.mp4");
> -snprintf(video_file, sizeof(video_file), staticConfig.video_file_format, 
> path, video_name);
> +snprintf(video_file, sizeof(video_file), "%s/%s", path, video_name);
>  Debug(1,"Writing video file to %s", video_file );
> 
>  /* X264 MP4 video writer */

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

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

Re: [Slackbuilds-users] ZoneMinder build fails if ffmpeg is not installed

[Daniel Prosser]

Thanks Willy. A couple more notes/issues/fixes for this new version:

1. By default, ZoneMinder now saves events as mp4 videos instead of
frames. For this to work, x264 and libmp4v2 must be installed prior to
building. It's still possible to just use image frames as before, but I
think x264 and libmp4v2 need to be at least optional dependencies.
Personally, I think they should be required, as otherwise the user will
have to switch to saving image frames only.

2. Even with x264 and libmp4v2 installed, ZoneMinder was still unable to
save videos for me. I had to apply the attached patch for it to work.
I'm not really sure why that's the case, since I didn't find any other
reports of it not working as is. GenoBob, perhaps you and/or any other
Slackware ZoneMinder users can report whether it works for you (and add
this patch to the SlackBuild if appropriate)?

3. This version stores events and other data in ZM_CONTENTDIR, which
defaults to /var/lib/zoneminder. However, the SlackBuild script doesn't
create this directory, so there are initially errors when running until
the user manually creates it. (It needs to be owned by apache:apache). I
recommend having the SlackBuild script create this directory as part of the
package, and make it a build option so it can be changed at build time.

Don't take these comments as a criticism. I am really grateful for the
script and I'm glad that it's basically working for me now. I was actually
procrastinating upgrading to 1.32.x because of all the changes. I just
want to help make the installation process as smooth as possible for
others.

Dan

On Mon, Jan 21, 2019 at 06:56:13AM +0700, Willy Sudiarto Raharjo wrote:
> > ffmpeg is listed as an optional dependency for ZoneMinder, but in a
> > clean Slackware64-14.2 container, if ffmpeg isn't installed, I get the
> > attached errors. Should ffmpeg be listed as a required dependency now?
> 
> Thanks Dan
> 
> I have added ffmpeg into the REQUIRES line now
> 
> Thanks
> 
> 
> -- 
> Willy Sudiarto Raharjo
> 



--- src/zm_event.cpp2019-01-21 23:17:19.881961455 -0500
+++ src/zm_event.cpp.new2019-01-21 23:17:38.452315254 -0500
@@ -196,7 +196,7 @@

   if ( monitor->GetOptVideoWriter() != 0 ) {
 snprintf(video_name, sizeof(video_name), "%" PRIu64 "-%s", id, 
"video.mp4");
-snprintf(video_file, sizeof(video_file), staticConfig.video_file_format, 
path, video_name);
+snprintf(video_file, sizeof(video_file), "%s/%s", path, video_name);
 Debug(1,"Writing video file to %s", video_file );

 /* X264 MP4 video writer */
___
SlackBuilds-users mailing list
SlackBuilds-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] ZoneMinder build fails if ffmpeg is not installed

[Daniel Prosser]

ffmpeg is listed as an optional dependency for ZoneMinder, but in a
clean Slackware64-14.2 container, if ffmpeg isn't installed, I get the
attached errors. Should ffmpeg be listed as a required dependency now?

Thanks,
Dan
In file included from /tmp/SBo/ZoneMinder-1.32.2/src/zm_image.h:35:0,
 from /tmp/SBo/ZoneMinder-1.32.2/src/zm_camera.h:26,
 from /tmp/SBo/ZoneMinder-1.32.2/src/zm_camera.cpp:21:
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:298:29: error: missing binary 
operator before token "("
 #if LIBAVCODEC_VERSION_CHECK(57, 64, 0, 64, 0)
 ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:302:29: error: missing binary 
operator before token "("
 #if LIBAVCODEC_VERSION_CHECK(56, 8, 0, 60, 100)
 ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:309:29: error: missing binary 
operator before token "("
 #if LIBAVCODEC_VERSION_CHECK(52, 23, 0, 23, 0)
 ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:315:29: error: missing binary 
operator before token "("
 #if LIBAVCODEC_VERSION_CHECK(55, 28, 1, 45, 101)
 ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:321:31: error: missing binary 
operator before token "("
 #if ! LIBAVCODEC_VERSION_CHECK(55, 28, 1, 45, 101)
   ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:267:41: error: ‘AVFormatContext’ 
was not declared in this scope
 int hacked_up_context2_for_older_ffmpeg(AVFormatContext **avctx, 
AVOutputFormat *oformat, const char *format, const char *filename);
 ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:267:59: error: ‘avctx’ was not 
declared in this scope
 int hacked_up_context2_for_older_ffmpeg(AVFormatContext **avctx, 
AVOutputFormat *oformat, const char *format, const char *filename);
   ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:267:66: error: ‘AVOutputFormat’ 
was not declared in this scope
 int hacked_up_context2_for_older_ffmpeg(AVFormatContext **avctx, 
AVOutputFormat *oformat, const char *format, const char *filename);
  ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:267:82: error: ‘oformat’ was not 
declared in this scope
 int hacked_up_context2_for_older_ffmpeg(AVFormatContext **avctx, 
AVOutputFormat *oformat, const char *format, const char *filename);

  ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:267:91: error: expected 
primary-expression before ‘const’
 int hacked_up_context2_for_older_ffmpeg(AVFormatContext **avctx, 
AVOutputFormat *oformat, const char *format, const char *filename);

   ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:267:111: error: expected 
primary-expression before ‘const’
 int hacked_up_context2_for_older_ffmpeg(AVFormatContext **avctx, 
AVOutputFormat *oformat, const char *format, const char *filename);

   ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:267:131: error: expression list 
treated as compound expression in initializer [-fpermissive]
 int hacked_up_context2_for_older_ffmpeg(AVFormatContext **avctx, 
AVOutputFormat *oformat, const char *format, const char *filename);

   ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:275:26: error: ‘AVRational’ was 
not declared in this scope
 int64_t av_rescale_delta(AVRational in_tb, int64_t in_ts,  AVRational fs_tb, 
int duration, int64_t *last, AVRational out_tb);
  ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:275:52: error: expected 
primary-expression before ‘in_ts’
 int64_t av_rescale_delta(AVRational in_tb, int64_t in_ts,  AVRational fs_tb, 
int duration, int64_t *last, AVRational out_tb);
^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:275:60: error: ‘AVRational’ was 
not declared in this scope
 int64_t av_rescale_delta(AVRational in_tb, int64_t in_ts,  AVRational fs_tb, 
int duration, int64_t *last, AVRational out_tb);
^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:275:78: error: expected 
primary-expression before ‘int’
 int64_t av_rescale_delta(AVRational in_tb, int64_t in_ts,  AVRational fs_tb, 
int duration, int64_t *last, AVRational out_tb);
  ^
/tmp/SBo/ZoneMinder-1.32.2/src/zm_ffmpeg.h:275:100: error: expected 
primary-expression before ‘*’ token
 int64_t av_rescale_delta(AVRational in_tb, int64_t in_ts,  

Re: [Slackbuilds-users] updates/matplotlib SlackBuilds-users Digest, Vol 151, Issue 2

[Daniel Prosser]

No problem upgrading matplotlib here, either.

On Sun, Nov 04, 2018 at 03:19:49PM +, sborg63 wrote:
> On Sun, 04 Nov 2018 07:06:28 +
> slackbuilds-users-requ...@slackbuilds.org wrote:
> 
> > From: Daniil Bratashov 
> > To: "SlackBuilds.org Users List" 
> > Subject: Re: [Slackbuilds-users] Updates - 20181103.1
> > Message-ID:
> > 
> > Content-Type: text/plain; charset="utf-8"
> > 
> > matplotlib has wrong md5sum probably and failed to build.
> 
> Hi Daniil, 
> 
> No md5sum-error or build- problem here; did your download complete
> corrcetly? Also, notice the novel  sbo packages that are
> needed for matplotlib:
> > academic/kiwisolver: Added (Cassowary algorithm).
> > python/subprocess32: Added (subprocess module).
> 
> This will show up when using sbopkg queue-generator ("sqg  -p
> matplotlib").
> 
> hth
> 
> rob
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] conflict

[Daniel Prosser]

Wow, two packages installing the sam file.

(Sorry, couldn't help it.)


On Oct 19, 2018 6:01 PM, B Watson  wrote:

audio/SAM and development/sam both install a /usr/bin/sam. At minimum,
both READMEs should mention this. Or possibly audio/SAM could rename
its binary to /usr/bin/SAM.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


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

Re: [Slackbuilds-users] 3 Slackbuilds looking for new maintainer

[Daniel Prosser]

I can take sbbdep. Thanks for your contributions.

Dan

On Sunday, October 07, 2018 11:15:08 PM Harald Achitz wrote:
> Hi,
> 
> as a result of temporarily bans (several days) for nearly each post on LQ I
> did in the last months, I decided to cancel my paid LQ subscription. Now
> the LQ mod has banned me for ever.
> I knew already how horrible LQ is moderated from several mods, but this
> tells me the very rest I need to know about LQ.
> Since Slackware has decided to use this place, that I can not follow
> anymore, as it's community platform I have to wish Slackware all the best
> for it's future.
> No more development,or financial support from me for Slackware, Slackware
> developers or Slackware related projects.
> 
> For Slackware this will not make any difference, other OS project and I can
> be happy about the resources available.
> 
> However, one side effect is that the 3 Slackbuilds I maintain needs new
> maintainers.
> 
> These are:
> 
> slack
> https://slackbuilds.org/repository/14.2/network/slack/
> slack desktop client
> I haven't updated this for a while since it's change to GTK3, and because
> if imho it uses insane amount of CPU/memory resources and the web client
> works much better.
> 
> kcov
> https://slackbuilds.org/repository/14.2/development/kcov/
> a code ocverage tool for C/C++, python and bash scripts
> nice talk from the author:
> https://www.youtube.com/watch?v=1QMHbp5LUKg
> 
> sbbdep
> https://slackbuilds.org/repository/14.2/system/sbbdep/
> The tool for exploring binary runtime dependencies on Slackware and
> Slackware based system.
> This build will barely ever change since what it does is final and works, I
> do not think that I now will ever finalise or release the features I have
> in the queue.
> 
> 
> All 3 builds are super simple, so there should not be any problems with
> them.
> If there are questions to them, I will for some time have a look at this
> thread and help if I can.
> 
> 
> Regards and all the best!

___
SlackBuilds-users mailing list
SlackBuilds-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] pavucontrol incompatible with new zuki-themes

[Daniel Prosser]

Hello,

Today I upgraded to zuki-themes 3.28.3 that was included in the latest public 
update. Unfortunately, pavucontrol is garbled with the Zukitre theme included 
in this package, and also pasystray's menu is not displayed correctly. A 
screenshot of the pavucontrol window is attached. For my part, I have reverted 
back to 3.18.1. Is there a reason this was upgraded other than to have the 
latest and greatest? I am wondering if it is truly compatible with Slackware's 
version of gtk+3.

Dan___
SlackBuilds-users mailing list
SlackBuilds-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] Fontforge build error

[Daniel Prosser]

Did you try following the instructions in the FAQ yet?

http://slackbuilds.org/faq/#multilib

It that doesn't work, building in a VM or LXC container is much less disruptive 
than reinstalling the OS on your "production" machine.

Dan
___
SlackBuilds-users mailing list
SlackBuilds-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] Small change to kodi.desktop

[Daniel Prosser]

Hi,

I just installed Kodi for the first time in awhile, and I noticed that when 
using plank (a dock), I am not able to keep the Kodi icon in the dock as a 
launcher. Additionally, a generic icon is displayed in the dock when it is 
running, rather than the icon provided by the theme. It turns out that if you 
add this line:

TryExec=kodi

to kodi.desktop, both problems are resolved. Based on the freedesktop.org 
standards for desktop entries, TryExec seems pretty important, and therefore 
leaving it out may cause other applications in addition to plank to not handle 
it optimally. Can the SlackBuild be patched to add that line to kodi.desktop?

https://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#idm140676267060848

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

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

[Daniel Prosser]

Thanks to a David Woodfall and everyone involved in making this update happen.

Dan
___
SlackBuilds-users mailing list
SlackBuilds-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] Skypeforlinux not compiling

[Daniel Prosser]

Looks like they removed the 8.18.0.6 release from that site, but there are a 
bunch of newer ones available.

https://repo.skype.com/deb/pool/main/s/skypeforlinux/

On Wednesday, September 12, 2018 05:08:09 PM Jostein Berntsen wrote:
> I get this error:
> 
> Processing skypeforlinux
> 
> skypeforlinux:
> skypeforlinux not found in /var/cache/sbopkg.
> --2018-09-12 17:01:00--
> https://repo.skype.com/deb/pool/main/s/skypeforlinux/skypeforlinux_8.18.0.6_
> amd64.deb Slår opp vertsnavn repo.skype.com … 23.52.33.92,
> 2a02:26f0:e2:48d::1263, 2a02:26f0:e2:48a::1263
> Kobler til repo.skype.com|23.52.33.92|:443 …tilkoblet.
> HTTP-forespørsel sendt. Venter på svar … 404 Not Found
> 2018-09-12 17:01:01 PROGRAMFEIL 404: Not Found.
> RY LOG
> Using the SBo repository for Slackware 14.2
> Queue Process:  Download, build, and install
> 
> skypeforlinux:
>   Download failed.
> 
> Error occurred with build.  Please check the log.
> 
> 
> skypeforlinux:
> Would you like to continue processing the rest of the
> queue or would you like to abort?  If this failed
> package is a dependency of another package in the queue
> then it may not make sense to continue.
> 
> (Y)es to continue, (N)o to abort, (R)etry the build?: y
> 
> 
> 
> Mvh,
> Jostein Berntsen
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/

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

Re: [Slackbuilds-users] sage up for grabs UNMAINTAINED

[Daniel Prosser]

Perhaps if upstream is fighting so hard to make it *not* possible to package 
sage, the best course of action is just to honor their intent and stop trying 
(take it off SBo). Just my two cents as someone who does not use it anyway (so 
maybe it's actually only worth one cent).

Dan

On Thursday, August 09, 2018 10:52:29 AM King Beowulf wrote:
> On 08/09/2018 07:37 AM, Fellype do Nascimento wrote:
> ..snip...
> 
> > Just a tip for anyone interested in take over maintenance for sage:
> > The AUR guys have made efforts to get the latest version (git) working
> > on Arch Linux (https://aur.archlinux.org/packages/sagemath-git/).
> > Well... there are up to 16 patches applied in order to get sage working
> > :-P
> > Good look for the next sage maintainer...
> 
> ...snip...
> 
> 16? That's double from last I checked.  It just doesn't make any sense
> to me do go to that trouble.  It takes 4+ hrs on my best box to compile
> - too long a cycle for me to test patches.  To have to patch in order to
> make a relocatable binary is just insane.
> 
> Here's another tip for my successor - never could get this to work:
> https://github.com/sagemath/binary-pkg
> 
> Just to clarify:
> 
> Sagemath compile does work fine on Slackware stable and current as long
> as you build in the final target directory.
> 
> I'm just a simple country chemist.

___
SlackBuilds-users mailing list
SlackBuilds-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] pcsc-lite - download url not working

[Daniel Prosser]

I can confirm this issue. The tarball on github (https://github.com/Lud
ovicRousseau/PCSC/archive/pcsc-1.8.14.tar.gz) works if you autoreconf
before running configure.

Dan

On Wed, 2018-06-13 at 17:43 +0200, Thomas Szteliga wrote:
> Hello,
> 
> there's a problem with
>  .tar.bz2>
> which is unavailable.
> 
> Maybe https://pcsclite.apdu.fr/files/ will be a better mirror?
> 
> 
___
SlackBuilds-users mailing list
SlackBuilds-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] Atom 1.23.3 fails to build

[Daniel Prosser]

Willy,

Thanks for testing. I did read the README, but the old version did not
work for me even in multiple attempts. Same with the OP in the thread 
I linked. 1.27.2 worked on the first try. So I'm not sure what the
difference is there, but my system is definitely not clean. If I get a
chance, I will test it on a clean VM.

Dan

On Mon, 2018-06-04 at 09:20 +0700, Willy Sudiarto Raharjo wrote:
> > One correction - I changed the default $TAG and $TMP in the
> > SlackBuild
> > for my own build and forgot to change them back before creating the
> > patch. Please disregard those changes.
> > I found an issue on Github related to this problem, which was
> > resolved
> > after the 1.23.3 release:
> > 
> > https://github.com/atom/atom/issues/16777
> > 
> > Based on that information, I tried building 1.27.2 instead, and it
> > worked without issue; all I did was change the version number. So
> > can we
> > get atom updated to that version? A patch is attached, though it is
> > quite trivial. I did make one small change to the .desktop file,
> > however.
> 
> Hi Daniel
> 
> Thanks for the patch
> I tested and it seems to have the same issue as before
> It need to run it twice before it built normally and it's already
> covered in the README
> 
> 
___
SlackBuilds-users mailing list
SlackBuilds-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] Atom 1.23.3 fails to build

[Daniel Prosser]

One correction - I changed the default $TAG and $TMP in the SlackBuild for my 
own build and forgot to change them back before creating the patch. Please 
disregard those changes.


From: SlackBuilds-users  on behalf 
of Daniel Prosser 
Sent: Sunday, June 3, 2018 6:45 PM
To: slack.dha...@gmail.com
Cc: slackbuilds-users@slackbuilds.org
Subject: [Slackbuilds-users] Atom 1.23.3 fails to build

Hi,

I am unable to build Atom 1.23.3 on Slackware64 14.2. While it is
generating API docs, memory usage goes out of control until the build is
aborted. Apparently I am not alone, based on this thread:

https://www.linuxquestions.org/questions/slackware-14/atom-installation-fatal-error-call_and_retry_last-allocation-failed-javascript-heap-out-of-memory-4175628885/
[http://images.linuxquestions.org/lqthumb.png]<https://www.linuxquestions.org/questions/slackware-14/atom-installation-fatal-error-call_and_retry_last-allocation-failed-javascript-heap-out-of-memory-4175628885/>

Atom Installation - FATAL ERROR: CALL_AND_RETRY_LAST 
...<https://www.linuxquestions.org/questions/slackware-14/atom-installation-fatal-error-call_and_retry_last-allocation-failed-javascript-heap-out-of-memory-4175628885/>
www.linuxquestions.org
Hello, tried to install the Atom text editor. I did that via sboui (sbopkg). 
The two build options i set: Code: DISABLE_METRICS=yes DELETE_CACHE=yes I



I found an issue on Github related to this problem, which was resolved
after the 1.23.3 release:

https://github.com/atom/atom/issues/16777

Based on that information, I tried building 1.27.2 instead, and it
worked without issue; all I did was change the version number. So can we
get atom updated to that version? A patch is attached, though it is
quite trivial. I did make one small change to the .desktop file,
however.

Regards,
Dan
___
SlackBuilds-users mailing list
SlackBuilds-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] Atom 1.23.3 fails to build

[Daniel Prosser]

Hi,

I am unable to build Atom 1.23.3 on Slackware64 14.2. While it is
generating API docs, memory usage goes out of control until the build is
aborted. Apparently I am not alone, based on this thread:

https://www.linuxquestions.org/questions/slackware-14/atom-installation-fatal-error-call_and_retry_last-allocation-failed-javascript-heap-out-of-memory-4175628885/

I found an issue on Github related to this problem, which was resolved
after the 1.23.3 release:

https://github.com/atom/atom/issues/16777

Based on that information, I tried building 1.27.2 instead, and it
worked without issue; all I did was change the version number. So can we
get atom updated to that version? A patch is attached, though it is
quite trivial. I did make one small change to the .desktop file,
however.

Regards,
Dan
From 47c6f76a34b568467f09c0d4a10a8069c2c12baf Mon Sep 17 00:00:00 2001
From: Daniel Prosser 
Date: Sun, 3 Jun 2018 16:35:33 -0400
Subject: [PATCH 1/1] Update atom for version 1.27.2

---
 development/atom/atom.SlackBuild | 6 +++---
 development/atom/atom.desktop| 1 +
 development/atom/atom.info   | 6 +++---
 3 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/development/atom/atom.SlackBuild b/development/atom/atom.SlackBuild
index 4b37a523e6..8b3843cdab 100644
--- a/development/atom/atom.SlackBuild
+++ b/development/atom/atom.SlackBuild
@@ -23,9 +23,9 @@
 # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 PRGNAM=atom
-VERSION=${VERSION:-1.23.3}
+VERSION=${VERSION:-1.27.2}
 BUILD=${BUILD:-1}
-TAG=${TAG:-_SBo}
+TAG=${TAG:-_mntg}
 
 #Disable send metrics to Google Analytics module
 DISABLE_METRICS=${DISABLE_METRICS:-no}
@@ -43,7 +43,7 @@ if [ -z "$ARCH" ]; then
 fi
 
 CWD=$(pwd)
-TMP=${TMP:-/tmp/SBo}
+TMP=${TMP:-/tmp/mntg}
 PKG=$TMP/package-$PRGNAM
 OUTPUT=${OUTPUT:-/tmp}
 
diff --git a/development/atom/atom.desktop b/development/atom/atom.desktop
index 9c7fc4b640..3682702347 100644
--- a/development/atom/atom.desktop
+++ b/development/atom/atom.desktop
@@ -9,6 +9,7 @@ Exec=/usr/bin/atom %U
 Icon=atom
 Type=Application
 StartupNotify=true
+StartupWMClass=atom
 Terminal=false
 Categories=GNOME;GTK;Utility;TextEditor;Development;
 MimeType=text/plain;
diff --git a/development/atom/atom.info b/development/atom/atom.info
index 2f69bc17d7..5ed61f243b 100644
--- a/development/atom/atom.info
+++ b/development/atom/atom.info
@@ -1,8 +1,8 @@
 PRGNAM="atom"
-VERSION="1.23.3"
+VERSION="1.27.2"
 HOMEPAGE="https://atom.io/;
-DOWNLOAD="https://github.com/atom/atom/archive/v1.23.3/atom-1.23.3.tar.gz;
-MD5SUM="1dfc819b29c910daaed20c11a629b28f"
+DOWNLOAD="https://github.com/atom/atom/archive/v1.27.2/atom-1.27.2.tar.gz;
+MD5SUM="20d69fb3463bd01f755646989ec682f9"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES="nodejs"
-- 
2.14.1

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

Re: [Slackbuilds-users] Updates - 20180519.1

[Daniel Prosser]

Makes sense, then. Thanks!

On Sat, 2018-05-19 at 03:27 +0100, David Woodfall wrote:
> On Saturday 19 May 2018 01:56,
> Daniel Prosser <dpross1...@msn.com> put forth the proposition:
> > Hi,
> > 
> > Can someone explain why wine was downgraded from 3.1 to 3.0.1?
> > 
> > Regards,
> > Dan
> 
> I did it because wine is meant to follow the stable branch and I had
> a bit of a brainfart and updated it to an (old) dev version the last
> time I updated it.
> 
> wine-staging follows the dev branch.
> 
> Best,
> 
> -Dave
> 
> --
> 
> Please don't reply directly to me or CC me.
> 
> /*
>  * [...] Note that 120 sec is defined in the protocol as the maximum
>  * possible RTT.  I guess we'll have to use something other than TCP
>  * to talk to the University of Mars.
>  * PAWS allows us longer timeouts and large windows, so once
> implemented
>  * ftp to mars will work nicely.
>  */
>   -- from /usr/src/linux/net/inet/tcp.c, concerning RTT [round trip
> time]
> 
> oo  .--.
>  \\()
>   `
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20180519.1

[Daniel Prosser]

Hi,

Can someone explain why wine was downgraded from 3.1 to 3.0.1?

Regards,
Dan

On Sat, 2018-05-19 at 01:33 +0100, David Spencer wrote:
> Hi everybody,
> 
> Here's this week's public update. Thanks to all our contributors!
> 
> Please note that there is a small problem with the .info file for
> prosody, we'll fix this in another update very soon.
> 
> Sat May 19 00:00:01 UTC 2018
> academic/STAR: Added (Spliced Transcripts Alignment to a Reference).
> academic/calc: Updated for version 2.12.6.5.
> academic/flexbar: Updated for version 3.1.0.
> academic/pysam: Updated for version 0.14.1.
> audio/clockchimes: Updated for version 0.2.
> audio/pd: Updated for version 0.48_1.
> desktop/Zafiro-icons: Updated for version 0.1.8.
> desktop/mh5000: Updated for version 1.3.4.
> desktop/murrine: Fix build with slibtool.
> desktop/neofetch: Updated for version 4.0.0.
> desktop/oranchelo-icon-theme: Updated for version 0.7.9.
> desktop/xpenguins_themes: Added (addon for xpenguins).
> development/atom-amd64: Updated for version 1.27.0.
> development/byacc: Updated for version 20180510.
> development/cargo-vendor: Updated for version 0.1.14.
> development/extra-cmake-modules: Updated for version 5.46.0.
> development/jupyter-nbdime: Updated for version 1.0.0.
> development/mlton: Updated for version 20180207 + new maintainer.
> development/p4: Updated for version 2018.1.1660568.
> development/p4d: Updated for version 2018.1.1660568.
> games/doomretro: Updated for version 2.6.9.
> games/javacpc: Updated for version 2.9.6d.
> games/nethack: Updated for version 3.6.1.
> games/oolite: Updated for version 1.86.
> games/pcsx2: Updated for version 2018.05.16_290397d.
> gis/gdal: Updated for version 2.3.0.
> gis/geopy: Updated for version 1.14.0.
> gis/gpxsee: Updated for version 5.11.
> gis/pdal: Updated for version 1.7.2.
> graphics/feh: Updated for version 2.26.2.
> graphics/viewnior: Updated for version 1.7.
> libraries/VTK: Updated for version 8.1.1
> libraries/libinput: Updated for version 1.10.7.
> libraries/liblxi: Updated for version 1.13
> libraries/msgpack-c: Updated for version 3.0.1.
> libraries/ulfius: Updated for version 2.3.5.
> libraries/wxSQLite3: Updated for version 4.0.3.
> misc/KeePass: Updated for version 2.39.1.
> misc/xdelta: Fixed download.
> multimedia/devedeng: Updated for version 4.11.0.
> multimedia/get_iplayer: Updated for version 3.14.
> multimedia/obs-studio: Updated for version 21.1.2
> multimedia/opera-ffmpeg-codecs: Updated for version 66.0.3359.170.
> multimedia/plexmediaserver: Updated for version 1.13.0.
> network/WireGuard: Updated for version 0.0.20180514.
> network/aria2: Updated for version 1.34.0.
> network/basilisk-src: Updated for version 2018.05.15.
> network/basilisk: Updated for version 2018.05.15.
> network/liferea: Updated for version 1.12.3 + new maintainer.
> network/lxi-tools: Updated for version 1.20
> network/offlineimap: Updated for version 7.2.0.
> network/opera-developer: Updated for version 55.0.2955.0.
> network/opera: Updated for version 53.0.2907.57.
> network/palemoon: Updated for version 27.9.2.
> network/phpmyadmin: Updated for version 4.8.0.1.
> network/postfix: Retain license files.
> network/prosody: Updated for version 0.10.1
> network/qbittorrent-qt5: Updated for version 4.1.0.
> network/qbittorrent: Update to rc init file.
> network/qutebrowser: Updated for version 1.3.0.
> network/riot-web: Updated for version 0.14.2.
> network/shorewall-core: Updated for version 5.2.0.3.
> network/shorewall6: Updated for version 5.2.0.3.
> network/shorewall: Updated for version 5.2.0.3.
> network/strongswan: Updated for version 5.6.2 + new maintainer.
> network/verm: Updated for version 1.5.0.
> network/vivaldi: Updated for version 1.15.1147.42.
> network/youtube-dl: Updated for version 2018.05.09.
> office/texlive: Fix download.
> perl/perl-ExtUtils-ModuleMaker: Updated for version 0.62.
> python/invoke: Updated for version 1.0.0..
> python/python-autobahn: Updated for version 18.5.1.
> python/ruffus: Updated for version 2.6.3.
> system/ansible: Updated for version 2.5.2.
> system/cronie: Updated for version 1.5.2.
> system/dar: Updated for version 2.5.15.
> system/dosbox-dev: Updated for version 0.74.r4101.
> system/firejail: Updated for version 0.9.54.
> system/geoclue2: Updated for version 2.4.10.
> system/inxi: Updated for version 3.0.09.
> system/jdupes: Added (taking action upon duplicate files).
> system/lynis: Update DOWNLOAD url.
> system/nano-syntax-highlighting: Updated for version 20180508.
> system/pytrash: Updated for version 1.1.1.
> system/sbbdep: Updated for version 0.3.2.
> system/spman: Updated for version 1.5.2.
> system/thin-provisioning-tools: Updated for version 0.7.6.
> system/wine: Updated for version 3.0.1.
> system/xen: Updated for version 4.10.1.
> +--+
> 
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> 

Re: [Slackbuilds-users] qt5 + pulseaudio

[Daniel Prosser]

>> Hint to alsa-enthusiasts: suggest your alsa-tested switch arrangement 
>> directly to the relevant maintainers. I'm sure such suggestions would mostly 
>> be adopted provided They don't adversely affect normal systems.

Isn't that exactly what Hunter has done?

On May 9, 2018 5:53 PM, Christoph Willing  wrote:

On 10/05/18 06:53, Richard Narron wrote:
> On Tue, 8 May 2018, Matteo Bernardini wrote:
>
>> 2018-05-07 23:36 GMT+02:00 or...@fredslev.dk :
>>> That assumption is irrelevant and if a maintainer is not willing to
>>> respond to bug reports then it should be possible to implement fixes
>>> without the maintainer.
>>>
>>> The bottom line is that this patch would make the qt5.SlackBuild more
>>> fail proof and the only reason to not accept it is to spite people who
>>> do not use pulseaudio. This can only have a negative effect on the
>>> usefulness and reliability of SBo...
>>
>> we have different opinion on what is a bug an what are legit
>> maintainer decisions.
>> optional pulseaudio support is surely not a bug: pulseaudio is not
>> optional at all in slackware 14.2 and I explained why we cannot
>> consider it optional even in the next Slackware release: stuff in
>> /extra is not part of a Slackware full installation and we support
>> just that.
>> that said, is up to the maintainer if they want to add a switch in
>> their SlackBuilds to make pulseaudio optional (with pulseaudio enabled
>> by default, of course), and it's up to the users to use it (under
>> their own responsibility) or not.
>
> I would suggest that the alsa files in /extra are not actually "extra".
> They are replacements for standard pulseaudio Slackware current packages.
>
> It would be hard for someone with with pulseaudio to test the alsa side of
> things and hard for someone with alsa to test the pulseaudio side of
> things.
>
> So instead of an alsa-pulseaudio switch perhaps we should allow two sets
> of packages, the standard ones with pulseaudio and another set with alsa.
>

How would that make testing any easier for a maintainer - or are you
suggesting having multiple maintainers too? It sounds like a lot of
complication just for the sake of the few SlackBuilds that would
actually be involved.

No doubt alsa enthusiasts are smart enough to make their own changes in
cases where the maintainer hasn't adopted some pulseaudio/alsa switch
arrangement.

Hint to alsa-enthusiasts:
suggest your alsa-tested switch arrangement directly to the relevant
maintainers. I'm sure such suggestions would mostly be adopted provided
they don't adversely affect normal systems.

chris

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


___
SlackBuilds-users mailing list
SlackBuilds-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] Problems upgrading ZoneMinder

[Daniel Prosser]

Bob,

Thank you for helping me try to sort this out. I was able to use the
upgrade dbs in /usr/share/zoneminder/db to incrementally upgrade my
database to 1.31.1. At least, the commands completed without reporting
any errors. Before I could do that, I did have to grant alter permission
to zmuser, which wasn't mentioned in README.SLACKWARE, FYI. However,
after upgrading I'm getting a bunch of errors in the logs about not
having proper permissions on directories, sockets not existing, etc.
Those logs recommend running zmupdate.pl -f, which I am still unable to
do. So I'm not really sure if the database was actually upgraded
correctly. These errors may be fixable with some hand editing of the
paths through the web interface, but I need to do more research to find
out.

B Watson, aka Urchlay, ank youthay orfay explainingay erewhay ethay
ourcesay amecay omfray. (Pardon my poor pig latin.)

Dan

On Sun, May 06, 2018 at 09:25:21PM -0700, Geno Bob wrote:
>I apologize, no. Anytime you upgrade Zoneminder from any version to
>another newer version, you have to upgrade the database incrementally.
>My easiest method is no not use the zmupdate tool (it works great if
>you are working with incremental versions, but anything more and I like
>to do it the old fashioned way), but instead to access mysql directly.
>In this case run:
>mysql -u zmuser -p databasename <
>/usr/share/zoneminder/db/zm_update-1.31.0.sql
>and
>mysql -u zmuser -p databasename <
>/usr/share/zoneminder/db/zm_update-1.31.1.sql
>replacing zmuser with your database username and databasename with your
>db name (probably just zm ?)
>This will also give us some more info as to what issue you are having
>with the db files, and which file it is having the issue with.
>Let me know if this works for you or not.
>Thank you,
>GenoBob
> 
>On Sun, May 6, 2018 at 8:47 PM, Daniel Prosser <[1]dpross1...@msn.com>
>wrote:
> 
>  If I get time, I will give that a try. But seeing as how upstream
>  still
>  has 1.30.4 as the latest source, I'm not exactly sure where I'm
>  supposed
>  to get 1.31.0. I'm guessing the same urchlay site, but just adjust
>  the
>  download URL?
>  I guess I'm just ignorant, but I have been active on the Slackware
>  forum
>  on Linuxquestions.org for a couple years and never remember coming
>  across someone named Urchlay. But that aside, I'm not sure why being
>  a
>  well-known Slackware user makes him the correct upstream for
>  ZoneMinder.
>  Is he a ZoneMinder dev also? Why does the official upstream still
>  have
>  1.30.4 as the latest stable release? I need a better reason for the
>  upgrade than what you have provided, and I'm sure the rest of the
>  ZoneMinder users on SBo would appreciate one too. (Please don't get
>  me
>  wrong -- I'm very appreciative of your maintainership efforts.)
>  Regards,
>  Dan
>  On Sun, May 06, 2018 at 12:11:37AM -0700, Geno Bob wrote:
>  >If you get a few minutes, you might try updating the database
>  one step
>  >at a time. You are going from 1.30.4 right to 1.31.1, however
>  there is
>  >a decent amount of updates in the 1.31.0 db file. Try updating
>  the db
>  >to 1.31.0 and then to 1.31.1 and see if it makes a difference.
>  When I
>  >get a chance I will spin up a VM with 1.30.4 and see if I cant
>  >replicate your issue.
>  >Also, Urchlay is THE urchlay. If you ever go onto a slackware
>  forum or
>  >IRC, he will be there.
>  >Thank you,
>  >GenoBob
>  >
>  >On Sat, May 5, 2018 at 8:12 PM, Daniel Prosser
>  <[1][2]dpross1...@msn.com>
>  >wrote:
>  >
>  >  I failed to reply all in my previous message, but anyway it
>  wasn't
>  >  very
>  >  important. The long and short of it was that I changed the
>  password
>  >  for
>  >  the "zmuser" DB user, but I think I needed to regrant
>  permission to
>  >  the
>  >  zm database after that. However, after taking care of that
>  and
>  >  ensuring
>  >  I can log in to mysql as zmuser, I am right back to the
>  original
>  >  error
>  >  when I try to run [2][3]zmupdate.pl.
>  >  But anyway, as far as I'm concerned, I'm not going to upgrade
>  to a
>  >  new
>  >  version until it's actually released by upstream. Hopefully
>  the
>  >

Re: [Slackbuilds-users] Problems upgrading ZoneMinder

[Daniel Prosser]

If I get time, I will give that a try. But seeing as how upstream still
has 1.30.4 as the latest source, I'm not exactly sure where I'm supposed
to get 1.31.0. I'm guessing the same urchlay site, but just adjust the
download URL?

I guess I'm just ignorant, but I have been active on the Slackware forum
on Linuxquestions.org for a couple years and never remember coming
across someone named Urchlay. But that aside, I'm not sure why being a
well-known Slackware user makes him the correct upstream for ZoneMinder.
Is he a ZoneMinder dev also? Why does the official upstream still have
1.30.4 as the latest stable release? I need a better reason for the
upgrade than what you have provided, and I'm sure the rest of the
ZoneMinder users on SBo would appreciate one too. (Please don't get me
wrong -- I'm very appreciative of your maintainership efforts.)

Regards,
Dan

On Sun, May 06, 2018 at 12:11:37AM -0700, Geno Bob wrote:
>If you get a few minutes, you might try updating the database one step
>at a time. You are going from 1.30.4 right to 1.31.1, however there is
>a decent amount of updates in the 1.31.0 db file. Try updating the db
>to 1.31.0 and then to 1.31.1 and see if it makes a difference. When I
>get a chance I will spin up a VM with 1.30.4 and see if I cant
>replicate your issue.
>Also, Urchlay is THE urchlay. If you ever go onto a slackware forum or
>IRC, he will be there.
>Thank you,
>GenoBob
> 
>On Sat, May 5, 2018 at 8:12 PM, Daniel Prosser <[1]dpross1...@msn.com>
>wrote:
> 
>  I failed to reply all in my previous message, but anyway it wasn't
>  very
>  important. The long and short of it was that I changed the password
>  for
>  the "zmuser" DB user, but I think I needed to regrant permission to
>  the
>  zm database after that. However, after taking care of that and
>  ensuring
>  I can log in to mysql as zmuser, I am right back to the original
>  error
>  when I try to run [2]zmupdate.pl.
>  But anyway, as far as I'm concerned, I'm not going to upgrade to a
>  new
>  version until it's actually released by upstream. Hopefully the
>  zmupdate
>  script will work when that happens.
>  Dan
>  On Sat, May 05, 2018 at 03:51:08PM -0700, Geno Bob wrote:
>  >Daniel,
>  >According to your error, your credentials are incorrect for
>  your SQL
>  >database. Try signing into your database using mysql -u zmuser
>  -p
>  >when it asks for a password put in your password (the same
>  credentials
>  >you used in the '[1][3]zmupdate.pl' command above).
>  >Thank you,
>  >
>  >On Sat, May 5, 2018 at 6:35 AM, Daniel Prosser
>  <[2][4]dpross1...@msn.com>
>  >wrote:
>  >
>  >  Hi,
>  >  ZoneMinder was upgraded to version 1.31.1 in the last update.
>  The
>  >  new
>  >  version builds fine, but I am having trouble running the
>  >  [3][5]zmupdate.pl
>  >  script to update my database. Using this command:
>  >  /usr/bin/[4][6]zmupdate.pl --version=1.30.4 --user={dbuser}
> 
>>  --pass={dbpass}
>>  I get this result:
>>  --
>>  Initiating database upgrade to version 1.31.1 from version
>1.30.4
>>  Please ensure that ZoneMinder is stopped on your system prior to
>>  upgrading the database.
>>  Press enter to continue or ctrl-C to stop :
>>  Do you wish to take a backup of your database prior to
>upgrading?
>>  This may result in a large file in /var/tmp/zm if you have a lot
>of
>>  events.
>>  Press 'y' for a backup or 'n' to continue : n
>>  Upgrading database to version 1.31.1
>>  Loading config from DBNo option 'ZM_DIR_EVENTS' found, removing.
>>  No option 'ZM_DIR_IMAGES' found, removing.
>>  No option 'ZM_DIR_SOUNDS' found, removing.
>>  No option 'ZM_FRAME_SOCKET_SIZE' found, removing.
>>  No option 'ZM_OPT_FRAME_SERVER' found, removing.
>>  No option 'ZM_PATH_ARP' found, removing.
>>  No option 'ZM_PATH_LOGS' found, removing.
>>  No option 'ZM_PATH_MAP' found, removing.
>>  No option 'ZM_PATH_SOCKS' found, removing.
>>  No option 'ZM_PATH_SWAP' found, removing.
>>  No option 'ZM_PATH_ZMS' found, removing.
>>   207 entries
>>  Saving config to DB 207 entries
>>  DBD::mysql::db do failed: Access denied for user
>>   

Re: [Slackbuilds-users] Problems upgrading ZoneMinder

[Daniel Prosser]

I failed to reply all in my previous message, but anyway it wasn't very
important. The long and short of it was that I changed the password for
the "zmuser" DB user, but I think I needed to regrant permission to the
zm database after that. However, after taking care of that and ensuring
I can log in to mysql as zmuser, I am right back to the original error
when I try to run zmupdate.pl.

But anyway, as far as I'm concerned, I'm not going to upgrade to a new
version until it's actually released by upstream. Hopefully the zmupdate
script will work when that happens.

Dan

On Sat, May 05, 2018 at 03:51:08PM -0700, Geno Bob wrote:
>Daniel,
>According to your error, your credentials are incorrect for your SQL
>database. Try signing into your database using mysql -u zmuser -p
>when it asks for a password put in your password (the same credentials
>you used in the '[1]zmupdate.pl' command above).
>Thank you,
> 
>    On Sat, May 5, 2018 at 6:35 AM, Daniel Prosser <[2]dpross1...@msn.com>
>wrote:
> 
>  Hi,
>  ZoneMinder was upgraded to version 1.31.1 in the last update. The
>  new
>  version builds fine, but I am having trouble running the
>  [3]zmupdate.pl
>  script to update my database. Using this command:
>  /usr/bin/[4]zmupdate.pl --version=1.30.4 --user={dbuser}
>  --pass={dbpass}
>  I get this result:
>  --
>  Initiating database upgrade to version 1.31.1 from version 1.30.4
>  Please ensure that ZoneMinder is stopped on your system prior to
>  upgrading the database.
>  Press enter to continue or ctrl-C to stop :
>  Do you wish to take a backup of your database prior to upgrading?
>  This may result in a large file in /var/tmp/zm if you have a lot of
>  events.
>  Press 'y' for a backup or 'n' to continue : n
>  Upgrading database to version 1.31.1
>  Loading config from DBNo option 'ZM_DIR_EVENTS' found, removing.
>  No option 'ZM_DIR_IMAGES' found, removing.
>  No option 'ZM_DIR_SOUNDS' found, removing.
>  No option 'ZM_FRAME_SOCKET_SIZE' found, removing.
>  No option 'ZM_OPT_FRAME_SERVER' found, removing.
>  No option 'ZM_PATH_ARP' found, removing.
>  No option 'ZM_PATH_LOGS' found, removing.
>  No option 'ZM_PATH_MAP' found, removing.
>  No option 'ZM_PATH_SOCKS' found, removing.
>  No option 'ZM_PATH_SWAP' found, removing.
>  No option 'ZM_PATH_ZMS' found, removing.
>   207 entries
>  Saving config to DB 207 entries
>  DBD::mysql::db do failed: Access denied for user
>  'zmuser'@'localhost' to
>  database 'zm' at /usr/share/perl5/vendor_perl/ZoneMinder/Config.pm
>  line
>  214,  line 2.
>  Can't lock Config table: Access denied for user 'zmuser'@'localhost'
>  to
>  database 'zm' at /usr/bin/[5]zmupdate.pl line 464.
>  --
>  I have also tried without specifying --user and --pass, but I get
>  the
>  same error. For now I have gone back to my old version and restored
>  the
>  backup database. I can also ask on the ZoneMinder forums, but I'm
>  not
>  sure if the issue lies with [6]zmupdate.pl or with the way
>  ZoneMinder is
>  configured by the SBo package. Seems like pretty much everyone over
>  there uses Ubuntu, CentOS, or Debian.
>  Dan
> 
> References
> 
>1. http://zmupdate.pl/
>2. mailto:dpross1...@msn.com
>3. http://zmupdate.pl/
>4. http://zmupdate.pl/
>5. http://zmupdate.pl/
>6. http://zmupdate.pl/
___
SlackBuilds-users mailing list
SlackBuilds-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] Problems upgrading ZoneMinder

[Daniel Prosser]

Interesting. I didn't catch that. In that case, I will just stick with
1.30.4. It would be nice to hear from the maintainer why it was updated
in the first place.

Dan

On Sat, May 05, 2018 at 09:13:30PM +0700, Willy Sudiarto Raharjo wrote:
> > ZoneMinder was upgraded to version 1.31.1 in the last update. The new
> > version builds fine, but I am having trouble running the zmupdate.pl
> > script to update my database. Using this command:
> > 
> > /usr/bin/zmupdate.pl --version=1.30.4 --user={dbuser} --pass={dbpass}
> > 
> > I get this result:
> > 
> > --
> > Initiating database upgrade to version 1.31.1 from version 1.30.4
> > 
> > Please ensure that ZoneMinder is stopped on your system prior to
> > upgrading the database.
> > Press enter to continue or ctrl-C to stop : 
> > 
> > Do you wish to take a backup of your database prior to upgrading?
> > This may result in a large file in /var/tmp/zm if you have a lot of
> > events.
> > Press 'y' for a backup or 'n' to continue : n
> > 
> > Upgrading database to version 1.31.1
> > Loading config from DBNo option 'ZM_DIR_EVENTS' found, removing.
> > No option 'ZM_DIR_IMAGES' found, removing.
> > No option 'ZM_DIR_SOUNDS' found, removing.
> > No option 'ZM_FRAME_SOCKET_SIZE' found, removing.
> > No option 'ZM_OPT_FRAME_SERVER' found, removing.
> > No option 'ZM_PATH_ARP' found, removing.
> > No option 'ZM_PATH_LOGS' found, removing.
> > No option 'ZM_PATH_MAP' found, removing.
> > No option 'ZM_PATH_SOCKS' found, removing.
> > No option 'ZM_PATH_SWAP' found, removing.
> > No option 'ZM_PATH_ZMS' found, removing.
> >  207 entries
> > Saving config to DB 207 entries
> > DBD::mysql::db do failed: Access denied for user 'zmuser'@'localhost' to
> > database 'zm' at /usr/share/perl5/vendor_perl/ZoneMinder/Config.pm line
> > 214,  line 2.
> > Can't lock Config table: Access denied for user 'zmuser'@'localhost' to
> > database 'zm' at /usr/bin/zmupdate.pl line 464.
> > --
> > 
> > I have also tried without specifying --user and --pass, but I get the
> > same error. For now I have gone back to my old version and restored the
> > backup database. I can also ask on the ZoneMinder forums, but I'm not
> > sure if the issue lies with zmupdate.pl or with the way ZoneMinder is
> > configured by the SBo package. Seems like pretty much everyone over
> > there uses Ubuntu, CentOS, or Debian.
> 
> After looking at the last commit, it seems a mystery for me as the
> sources are taken NOT from upstream but from third party repository. The
> latest release by upstream is still at 1.30.4 as well.
> 
> 
> 
> -- 
> Willy Sudiarto Raharjo
> 




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

___
SlackBuilds-users mailing list
SlackBuilds-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] Problems upgrading ZoneMinder

[Daniel Prosser]

Hi,

ZoneMinder was upgraded to version 1.31.1 in the last update. The new
version builds fine, but I am having trouble running the zmupdate.pl
script to update my database. Using this command:

/usr/bin/zmupdate.pl --version=1.30.4 --user={dbuser} --pass={dbpass}

I get this result:

--
Initiating database upgrade to version 1.31.1 from version 1.30.4

Please ensure that ZoneMinder is stopped on your system prior to
upgrading the database.
Press enter to continue or ctrl-C to stop : 

Do you wish to take a backup of your database prior to upgrading?
This may result in a large file in /var/tmp/zm if you have a lot of
events.
Press 'y' for a backup or 'n' to continue : n

Upgrading database to version 1.31.1
Loading config from DBNo option 'ZM_DIR_EVENTS' found, removing.
No option 'ZM_DIR_IMAGES' found, removing.
No option 'ZM_DIR_SOUNDS' found, removing.
No option 'ZM_FRAME_SOCKET_SIZE' found, removing.
No option 'ZM_OPT_FRAME_SERVER' found, removing.
No option 'ZM_PATH_ARP' found, removing.
No option 'ZM_PATH_LOGS' found, removing.
No option 'ZM_PATH_MAP' found, removing.
No option 'ZM_PATH_SOCKS' found, removing.
No option 'ZM_PATH_SWAP' found, removing.
No option 'ZM_PATH_ZMS' found, removing.
 207 entries
Saving config to DB 207 entries
DBD::mysql::db do failed: Access denied for user 'zmuser'@'localhost' to
database 'zm' at /usr/share/perl5/vendor_perl/ZoneMinder/Config.pm line
214,  line 2.
Can't lock Config table: Access denied for user 'zmuser'@'localhost' to
database 'zm' at /usr/bin/zmupdate.pl line 464.
--

I have also tried without specifying --user and --pass, but I get the
same error. For now I have gone back to my old version and restored the
backup database. I can also ask on the ZoneMinder forums, but I'm not
sure if the issue lies with zmupdate.pl or with the way ZoneMinder is
configured by the SBo package. Seems like pretty much everyone over
there uses Ubuntu, CentOS, or Debian.

Dan
___
SlackBuilds-users mailing list
SlackBuilds-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] Missing Noto Sans in latest noto-fonts

[Daniel Prosser]

Hi Edinaldo,

I'm not sure if this is expected or not, but when I installed the latest
update of noto-fonts, it was missing Noto Sans. It had the million
variations of Noto Sans, like Noto Sans Adlam, Noto Sans Arabic, Noto
Sans Hebrew, etc., but not plain Noto Sans.


Regards,
Dan
___
SlackBuilds-users mailing list
SlackBuilds-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] Wishful thinking

[Daniel Prosser]

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

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

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

Re: [Slackbuilds-users] What is the best way to add a tag to the version of a program?

[Daniel Prosser]

Fellype,

A couple comments here.

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

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

Dan

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

Re: [Slackbuilds-users] Problems with libev source

[Daniel Prosser]

After discussing this with the libev maintainer, he decided to change
his server configuration to avoid the issue with wget-1.19.2 and Firefox
57. The download now comes in with the right MD5sum and untars
correctly, but let me know if anyone experiences otherwise. After this
experience, I decided to switch the tool I use to manage SBo packages to
use curl instead of wget.
___
SlackBuilds-users mailing list
SlackBuilds-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] Problems with libev source

[Daniel Prosser]

Thank you for the information. I have forwarded this discussion on to
the libev developer along with your explanation of the problem. I will
leave it up to him to decide whether he wants to make any changes on his
end or just write it off as a wget problem (I would probably do that
latter, based on your explanation).

Dan

On Mon, Dec 25, 2017 at 07:12:51AM -0500, B Watson wrote:
> On 12/24/17, Daniel Prosser <dpross1...@msn.com> wrote:
> > Okay, fair enough. Just to be clear though, it makes sense to you that
> > this problem does not occur for every tar archive downloaded with wget
> > (or the browser), hosted at any site? I've only encountered the problem
> > with files from the libev download page, so there seems to be something
> > different about those files that causes wget and the browser to compress
> > them when downloading, if that is indeed what's going on.
> 
> I can name 2 more SBo examples: audio/alsacap and games/gtklife. These two
> are different from yours (the saved file is un-gzipped, not double-gzipped
> like libev) but the cause and workaround are the same.
> 
> It's not the file itself, it's the server that's serving the file. It's
> sending a 'Content-encoding: gzip' header, which is redundant (the actual
> file is already gzipped). The old version of wget disregards this header,
> and the new version acts on it by default.
> 
> It also sends a Content-type header, as usual... if the Content-type is
> application/x-tar, wget and your browser "helpfully" decompress the file.
> If it's application/x-gzip, wget and your browser (sometimes, not sure
> what else is happening) will "helpfully" gzip the file, even though it's
> already gzipped.
> 
> You could argue that this means the server is misconfigured, and you
> might be right... but the fact remains, the old wget did one thing when
> talking to these servers, and the new one defaults to doing a different
> thing. Slackware 14.2 is supposed to be a stable release, meaning that
> patches aren't supposed to cause major changes in behaviour (which is
> exactly what we're seeing here). The wget devs acknowledge this is a
> bug, too:
> 
> http://lists.gnu.org/archive/html/bug-wget/2017-11/msg00059.html
> 
> If it were just me, I'd switch to curl and forget about it. But tools like
> sbopkg and sbotools use wget... also, so does slackpkg (some Slackware
> mirror might cause this same problem).
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Problems with libev source

[Daniel Prosser]

Okay, fair enough. Just to be clear though, it makes sense to you that
this problem does not occur for every tar archive downloaded with wget
(or the browser), hosted at any site? I've only encountered the problem
with files from the libev download page, so there seems to be something
different about those files that causes wget and the browser to compress
them when downloading, if that is indeed what's going on.

Dan

On Sun, Dec 24, 2017 at 05:27:41PM -0500, B Watson wrote:
> On 12/24/17, Daniel Prosser <dpross1...@msn.com> wrote:
> > Could this compression also happen when it's downloaded through the browser?
> > Because I tried that and had the same problem.
> 
> Yes, but that's a lost battle already: it's been established for many
> years that browsers do whatever they want to downloaded files... which
> is why most of us use wget for source downloads. Now wget is acting like
> the browsers do, and that's definitely a bad thing & something that can &
> should be fixed before it becomes an established fact of life.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Problems with libev source

[Daniel Prosser]

Could this compression also happen when it's downloaded through the browser? 
Because I tried that and had the same problem.
___
SlackBuilds-users mailing list
SlackBuilds-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] Problems with libev source

[Daniel Prosser]

Hi all,

When trying to install libev, I first got an error about an MD5sum
mismatch. Ignoring that, I get this error:

tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors

So something has happened with the libev source code. I get the same
error with any version that I have tried to download from the libev
website (http://dist.schmorp.de/libev). For now, it seems like it's
necessary to use sbosrcarch.

I am going to email the libev author as well.

Regards,
Dan
___
SlackBuilds-users mailing list
SlackBuilds-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] zim md5sum mis-match

[Daniel Prosser]

I also checked. Downloading the source with wget works and gives the right 
md5sum, but clicking the link on the SBo website to download the file results 
in the error Rich reported.

Dan
___
SlackBuilds-users mailing list
SlackBuilds-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] Change needed in ZoneMinder README

[Daniel Prosser]

Hi,

The ZoneMinder README says that perl-MIME-Entity is an optional
dependency for automatic event mail notification. However, there is no
such SlackBuild in the repo. I believe the correct one is
perl-MIME-tools.

Regards,
Dan
___
SlackBuilds-users mailing list
SlackBuilds-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] perl-MailTools source download 404

[Daniel Prosser]

Hi,

The source download for perl-MailTools seems to have disappeared.
However, a newer version is available and the SlackBuild at least
completes with a simple version bump. Here are patches to the .info and
SlackBuild files for consideration.

Regards,
Dan
--- perl-MailTools.SlackBuild.orig  2017-11-06 22:52:48.767413569 -0500
+++ perl-MailTools.SlackBuild   2017-11-06 22:50:47.150417162 -0500
@@ -28,7 +28,7 @@
 # Modified by the SlackBuilds.org project.
 
 PRGNAM="perl-MailTools"
-VERSION=${VERSION:-2.18}
+VERSION=${VERSION:-2.19}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
--- perl-MailTools.info.orig2017-11-06 22:53:41.518412010 -0500
+++ perl-MailTools.info 2017-11-06 22:42:27.258431933 -0500
@@ -1,8 +1,8 @@
 PRGNAM="perl-MailTools"
-VERSION="2.18"
+VERSION="2.19"
 HOMEPAGE="https://metacpan.org/release/MailTools;
-DOWNLOAD="http://www.cpan.org/authors/id/M/MA/MARKOV/MailTools-2.18.tar.gz;
-MD5SUM="972468ab5207b90398d77bed4ffc361d"
+DOWNLOAD="http://www.cpan.org/authors/id/M/MA/MARKOV/MailTools-2.19.tar.gz;
+MD5SUM="a00b9d3c3dec64bd15de8c50f1b73d05"
 DOWNLOAD_x86_64=""
 MD5SUM_x86_64=""
 REQUIRES="perl-TimeDate"
___
SlackBuilds-users mailing list
SlackBuilds-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] Email rejected during submission

[Daniel Prosser]

Well, in the meantime I submitted it with my alternate email address.
I'll try to remember to do that in the future unless I hear otherwise.
Thanks for looking into it.

Dan

On Wed, Nov 01, 2017 at 10:09:18PM -0500, Robby Workman wrote:
> Top-posting to keep the pattern, even if I don't like it...
> 
> Sorry, I have no idea what's wrong there - rob0?
> 
> -RW
> 
> 
> On Wed, 1 Nov 2017 04:27:56 +
> Daniel Prosser <dpross1...@msn.com> wrote:
> 
> > Anyone? I see Jorge Giner Cordero had the exact same problem on
> > October 1, but no one posted a solution. Actually, one person posted a
> > suggestion to use (applying it to my case) "dpross1100 at msn.com,"
> > but that doesn't work. I would like to be able to update my scripts.
> > 
> > Dan
> > 
> > On Tue, Oct 31, 2017 at 03:43:20AM +, Daniel Prosser wrote:
> > > Trying to submit an update to one of my SlackBuilds, I get this
> > > error:
> > > 
> > > *
> > > [my email address] was rejected by mx2.hotmail.com.
> > > Go back and enter a valid E-Mail address.
> > > 
> > > If your mailserver uses Greylisting you may want to Whitelist
> > > slackbuilds-users@slackbuilds.org.
> > > *
> > > 
> > > I have added slackbuilds-users@slackbuilds.org and also the
> > > slackbuilds.org domain to my safe senders list. Anything else I can
> > > do? This has never happened to me in the past.
> > > 
> > > Dan
> > > ___
> > > SlackBuilds-users mailing list
> > > SlackBuilds-users@slackbuilds.org
> > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > > Archives -
> > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ -
> > > https://slackbuilds.org/faq/ 
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@slackbuilds.org
> > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> > 



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

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

Re: [Slackbuilds-users] Email rejected during submission

[Daniel Prosser]

Anyone? I see Jorge Giner Cordero had the exact same problem on October
1, but no one posted a solution. Actually, one person posted a
suggestion to use (applying it to my case) "dpross1100 at msn.com," but 
that doesn't work. I would like to be able to update my scripts.

Dan

On Tue, Oct 31, 2017 at 03:43:20AM +0000, Daniel Prosser wrote:
> Trying to submit an update to one of my SlackBuilds, I get this error:
> 
> *
> [my email address] was rejected by mx2.hotmail.com.
> Go back and enter a valid E-Mail address.
> 
> If your mailserver uses Greylisting you may want to Whitelist
> slackbuilds-users@slackbuilds.org.
> *
> 
> I have added slackbuilds-users@slackbuilds.org and also the
> slackbuilds.org domain to my safe senders list. Anything else I can do?
> This has never happened to me in the past.
> 
> Dan
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Email rejected during submission

[Daniel Prosser]

Trying to submit an update to one of my SlackBuilds, I get this error:

*
[my email address] was rejected by mx2.hotmail.com.
Go back and enter a valid E-Mail address.

If your mailserver uses Greylisting you may want to Whitelist
slackbuilds-users@slackbuilds.org.
*

I have added slackbuilds-users@slackbuilds.org and also the
slackbuilds.org domain to my safe senders list. Anything else I can do?
This has never happened to me in the past.

Dan
___
SlackBuilds-users mailing list
SlackBuilds-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] opencv md5sum error

[Daniel Prosser]

Alright, thanks for the explanation. I went ahead and built it anyway,
and it seems to be fine.

Dan

On Sat, Sep 23, 2017 at 02:24:24PM +1000, Christoph Willing wrote:
> On 23/09/17 13:09, Daniel Prosser wrote:
> > Hi,
> > 
> > Trying to install opencv, I'm getting an md5sum mismatch for
> > opencv-3.1.0.tar.gz. The .info file says the md5sum should be:
> > 
> > 70e1dd07f0aa06606f1bc0e3fa15abd3
> > 
> That is the correct one for my locally cached copy.
> 
> 
> > but I'm getting:
> > 
> > a0669e22172dfc3225835b180744c9f0
> Yes, looks like it has changed.
> 
> > 
> > I'm afraid to ignore the md5sum error and continue with the build
> > without knowing the reason for it. Did github change something behind
> > the scenes like seems to happen sometimes?
> 
> Yes, well 
> 
> It turns out that our expectation that Github tarballs never change is
> not well founded. There is some discussion about it here:
> https://github.com/libgit2/libgit2/issues/4343#issuecomment-328631745
> 
> 
> chris
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-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] opencv md5sum error

[Daniel Prosser]

Hi,

Trying to install opencv, I'm getting an md5sum mismatch for
opencv-3.1.0.tar.gz. The .info file says the md5sum should be:

70e1dd07f0aa06606f1bc0e3fa15abd3

but I'm getting:

a0669e22172dfc3225835b180744c9f0

I'm afraid to ignore the md5sum error and continue with the build
without knowing the reason for it. Did github change something behind
the scenes like seems to happen sometimes? Maybe just a packaging
oversight?

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

Re: [Slackbuilds-users] Very simple way of finding dependency

[Daniel Prosser]

If you use the sboui frontend for sbopkg and sbotools, it has a function to 
show "inverse dependencies" -- every SBo package installed on your system that 
depends on another one that you choose.
___
SlackBuilds-users mailing list
SlackBuilds-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] http://www.hyperrealm.com/libconfig/

[Daniel Prosser]

The hyperrealm site is still down, FYI. The source is available on
GitHub (https://github.com/hyperrealm/libconfig/archive/v1.5.tar.gz),
but it has a different md5sum and requires an autoreconf to build.
There's also a version 1.6 available. Maybe switching to the GitHub link
would be more reliable?
On Fri, Aug 04, 2017 at 11:31:39AM +0200, Matteo Bernardini wrote:
> 2017-08-04 11:28 GMT+02:00 Habs :
> >
> > Hello good morning all
> >
> > Server error @ http://www.hyperrealm.com/libconfig/
> >
> > libconfig-1.5.tar.gz
> >
> >
> > Is there an alternative link for now please ?
> 
> http://slackware.uk/sbosrcarch/by-name/libraries/libconfig/libconfig-1.5.tar.gz
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] virtualbox drv

[Daniel Prosser]

Did you also rebuild virtualbox-kernel?

(Actually, you only have to rebuild virtualbox-kernel after a kernel
upgrade, not virtualbox itself.)

Dan

On Sat, Jul 01, 2017 at 09:00:58PM +0200, Dimitris Zlatanidis wrote:
> After the new kernel 4.4.75 installed and rebuild virtualbox I can't
> start vboxdrv, any suggestion ?
> 
> Thanks
> 
> -- 
> Dimitris Zlatanidis
> 
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Descriptive list of packages

[Daniel Prosser]

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

Re: [Slackbuilds-users] Descriptive list of packages

[Daniel Prosser]

I guess I'm not sure what exactly you're looking for, then. Are you planning to 
read the entire descriptive list you mentioned? Because unless you plan to read 
everything, there is always the need to select search terms. And if you don't 
plan to read the whole thing, then you might as well just search the full 
READMEs (there would be no reason for the shortened descriptive list).

Dan

On Jun 25, 2017 10:00 AM, Rich Shepard <rshep...@appl-ecosys.com> wrote:

On Sun, 25 Jun 2017, Daniel Prosser wrote:

> If you have mirrored the repo locally you can just use find and grep, ie:
> find $REPO_ROOT -maxdepth 3 -mindepth 3 -name "README" | xargs grep -i 
> searchterm

Dan,

   Like a web search, sometimes the term we use is not the term used in the
package so we don't find what we want even if it exists.

> I think some of the SBO package management tools might also have a
> function built in to search in READMEs. sboui (which I wrote) has it at
> least.

   I tried using sbopkg's 'view README' but it dumped me back to the list of
packages.

Thanks for the reply,

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


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

Re: [Slackbuilds-users] Descriptive list of packages

[Daniel Prosser]

If you have mirrored the repo locally you can just use find and grep, ie:

find $REPO_ROOT -maxdepth 3 -mindepth 3 -name "README" | xargs grep -i 
searchterm

I think some of the SBO package management tools might also have a function 
built in to search in READMEs. sboui (which I wrote) has it at least.

Dan


On Jun 25, 2017 9:21 AM, Rich Shepard  wrote:

   Is there a list of packages with the descriptive contents of their README
files? It would be useful to know what's available since it's difficult to
look for a tool without knowing its name. Has anyone tried extracting this
from the repository?

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


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

Re: [Slackbuilds-users] gpsbabel, long list of errors

[Daniel Prosser]

I can confirm that the gpsbabel fails to build if you have Qt5
installed. Add this line in the SlackBuild, right before `autoreconf
-vif` to make sure it uses Qt4 instead:

sed -i 's/qmake-qt5 qmake-qt4 qmake/qmake qmake-qt4 qmake-qt5/g' configure.in

I have tested this and it works here.

Dan

On Mon, Jun 12, 2017 at 09:16:34PM -0500, Kyle Guinn wrote:
> On 6/12/17, Frédéric Falsetti  wrote:
> > Hi, anybody can build gpsbabel ?
> >
> > error Qt requires a C++11 compiler and yours does not seem to be that.
> > a long list of errors and
> >
> > In file included from /usr/include/qt5/QtCore/qshareddata.h:46:0,
> >  from /usr/include/qt5/QtCore/qdatetime.h:45,
> >  from /usr/include/qt5/QtCore/QDateTime:1,
> >  from src/core/datetime.h:27,
> >  from defs.h:39,
> >  from main.cc:22:
> > /usr/include/qt5/QtCore/qhash.h: Dans la fonction membre 'QPair > V>::iterator, QHash::iterator> QHash::equal_range(const Key&)':
> > /usr/include/qt5/QtCore/qhash.h:957:5: attention : 'auto' changes meaning in
> > C++11; please remove it [-Wc++0x-compat]
> >  auto pair = qAsConst(*this).equal_range(akey);
> >  ^
> > /usr/include/qt5/QtCore/qhash.h:957:10: erreur: 'pair' does not name a type
> >  auto pair = qAsConst(*this).equal_range(akey);
> >   ^
> > /usr/include/qt5/QtCore/qhash.h:958:31: erreur: 'pair' was not declared in
> > this scope
> >  return qMakePair(iterator(pair.first.i), iterator(pair.second.i));
> >^
> > /usr/include/qt5/QtCore/qhash.h:958:31: note: suggested alternative:
> > In file included from /usr/include/c++/5.3.0/utility:70:0,
> >  from /usr/include/qt5/QtCore/qcompilerdetection.h:1001,
> >  from /usr/include/qt5/QtCore/qglobal.h:83,
> >  from /usr/include/qt5/QtCore/qchar.h:43,
> >  from /usr/include/qt5/QtCore/qstring.h:48,
> >  from /usr/include/qt5/QtCore/qtextcodec.h:43,
> >  from /usr/include/qt5/QtCore/QTextCodec:1,
> >  from main.cc:20:
> > /usr/include/c++/5.3.0/bits/stl_pair.h:96:12: note:   'std::pair'
> >  struct pair
> > ^
> > Makefile:128: recipe for target 'main.o' failed
> > make: *** [main.o] Error 1
> 
> Looks like it's trying to build against Qt5.  I've only tested against Qt4.
> 
> Also there is a newer version, 1.5.4, but I've held back at 1.5.3
> since 1.5.4 requires Qt5.  Can you try a simple version bump and see
> if the errors go away with 1.5.4?
> 
> -Kyle
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] pass / password-store

[Daniel Prosser]

Well that's good, but I still think it's better not to change the name
unless there's a good reason for it. And the reason for the name change
in this case seems to be a simple oversight. That's just my opinion, and
of course the admins can do whatever they think is best.

(By the way, I tried the new version and it works well.)
On Sat, May 27, 2017 at 10:17:19PM +0700, Willy Sudiarto Raharjo wrote:
> >> I'm for a new version too if it fixes that bug, but wouldn't it be less
> >> confusing to leave the name the same and just have the new maintainer
> >> take over? Some people don't subscribe to this list and wouldn't see the
> >> announcement.
> > 
> > That's a good point. There will be probably be users on the
> > "password-store" build that will never even notice that it's migrated
> > over "pass". Seems better then to just replace the unmaintained script
> > with the new one.
> 
> There's always a ChangeLog in every public update
> also i have added "password store" and "password-store" to the keyword
> so they will be pointed to pass after next public update.
> 
> 
> -- 
> Willy Sudiarto Raharjo
> 




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

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

Re: [Slackbuilds-users] pass / password-store

[Daniel Prosser]

I'm for a new version too if it fixes that bug, but wouldn't it be less 
confusing to leave the name the same and just have the new maintainer take 
over? Some people don't subscribe to this list and wouldn't see the 
announcement.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] wine-2.0 and wine-2.0.1 no longer compile: missing gnutls_hash

[Daniel Prosser]

Thanks guys. Sure enough, I was missing libunistring-compat32. Must have been a 
new package that I missed somewhere along the line.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] wine-2.0 and wine-2.0.1 no longer compile: missing gnutls_hash

[Daniel Prosser]

I had the same issue here. Since I don't think I need gnutls support in wine, I 
just edited the SlackBuild to set --with-gnutls=no. (I didn't have time to dig 
why further than that.) After that, the build went fine. I haven't tested it 
yet, but that might be an option if you know you don't need gnutls support.

On May 13, 2017 10:32 AM, David Woodfall  wrote:

>On 05/08/2017 09:54 PM, Willy Sudiarto Raharjo wrote:
>>> I tried upgrading to wine-2.0.1 and got during configure:
>>> -
>>> checking gnutls/gnutls.h usability... yes
>>> checking gnutls/gnutls.h presence... yes
>>> checking for gnutls/gnutls.h... yes
>>> checking for -lgnutls... not found
>>> checking for gnutls_hash... no
>>> configure: error: libgnutls 32-bit development files not found, no
>>> schannel support.
>>> This is an error since --with-gnutls was requested.
>>> ---
>>>
>>> Oddly, I'm running wine-2.0.  Trying to rec-ompile wine-2.0  also now
>>> fails with the same error.  wine-2.0 compiled fine on 01-FEB-2017 (the
>>> package I am currently using).  All the updates to Slackware64 14.2 and
>>> multilib are installed as of 08-MAY-2017.
>>>
>>> I'll try later with a clean VM, but does anyone have any ideas?
>>
>> have you tried to reinstall gnutls just in case it was overwritten?
>>
>
>yes, first thing.  AHit's not gnutls that is missing but a gnutls
>dependency:
>
>libunistring-compat32-0.9.3-x86_64-1compat32
>
>where did that come from and why was it missing?  weird.  slackpkg or I
>missed it.
>
>well, let see what happens...
>
>-Ed

Hi. Did you sort this out?

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


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

Re: [Slackbuilds-users] gcc-legacy

[Daniel Prosser]

I posted this on LQ as well, but I just tried compiling Pale Moon with
clang/clang++ and the default flags. It works fine with no segfaults.
Personally, I'd prefer this route instead of requiring a legacy gcc.

Dan

On Fri, May 05, 2017 at 02:52:01AM +, Daniel Prosser wrote:
> I completed some tests today with SBo's PaleMoon (the from-source
> version). I found two sites where it segfaults consistently, no matter
> whether I use the ENABLE_DEBUG and OPTIMIZE=-Os or the default
> parameters. I also applied the workaround for the Oxygen gtk2 theme that
> is mentioned in the README. The sites are:
> 
> https://www.yahoo.com/ and
> http://hfboards.hockeysfuture.com/
> 
> In both cases, just opening up the page would result in a segfault
> within a few seconds. For reference, this is on Slackware64-14.2 with
> gcc-5.3.0.
> 
> Following that, I compiled gcc-4.9.4 and used it instead to build
> PaleMoon. Other than that change, the default parameters from the script
> were used. This fixed the problem, and now neither site segfaults. I
> also tried with the other PaleMoon ("palemoon") on SBo that repackages
> the official binary, and with Alien Bob's Pale Moon package. Neither of
> those have trouble with those two sites either.
> 
> More discussion here:
> 
> http://www.linuxquestions.org/questions/slackware-14/palemoon-from-source-slackbuild-4175605127/
> 
> Dan
> 
> On Thu, May 04, 2017 at 06:37:42AM +0200, Matteo Bernardini wrote:
> > 2017-05-04 3:56 GMT+02:00 Christoph Willing <chris.will...@iinet.net.au>:
> > > PS. I've seen only vague descriptions of the problems people are having
> > > when using the new PaleMoon not built with the earlier gcc version. It
> > > would be good to see something more definite  about these problems so
> > > others can test/verify them.
> > 
> > for this might be useful the ENABLE_DEBUG parameter in the SlackBuild
> > but, still for people experiencing crashes, have a look also at the
> > OPTIMIZE one
> > 
> > https://slackbuilds.org/repository/14.2/network/PaleMoon/
> > 
> > Matteo
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@slackbuilds.org
> > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> > 
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] gcc-legacy

[Daniel Prosser]

I completed some tests today with SBo's PaleMoon (the from-source
version). I found two sites where it segfaults consistently, no matter
whether I use the ENABLE_DEBUG and OPTIMIZE=-Os or the default
parameters. I also applied the workaround for the Oxygen gtk2 theme that
is mentioned in the README. The sites are:

https://www.yahoo.com/ and
http://hfboards.hockeysfuture.com/

In both cases, just opening up the page would result in a segfault
within a few seconds. For reference, this is on Slackware64-14.2 with
gcc-5.3.0.

Following that, I compiled gcc-4.9.4 and used it instead to build
PaleMoon. Other than that change, the default parameters from the script
were used. This fixed the problem, and now neither site segfaults. I
also tried with the other PaleMoon ("palemoon") on SBo that repackages
the official binary, and with Alien Bob's Pale Moon package. Neither of
those have trouble with those two sites either.

More discussion here:

http://www.linuxquestions.org/questions/slackware-14/palemoon-from-source-slackbuild-4175605127/

Dan

On Thu, May 04, 2017 at 06:37:42AM +0200, Matteo Bernardini wrote:
> 2017-05-04 3:56 GMT+02:00 Christoph Willing :
> > PS. I've seen only vague descriptions of the problems people are having
> > when using the new PaleMoon not built with the earlier gcc version. It
> > would be good to see something more definite  about these problems so
> > others can test/verify them.
> 
> for this might be useful the ENABLE_DEBUG parameter in the SlackBuild
> but, still for people experiencing crashes, have a look also at the
> OPTIMIZE one
> 
> https://slackbuilds.org/repository/14.2/network/PaleMoon/
> 
> Matteo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [ANN] New SBo Template Tool

[Daniel Prosser]

Jeremy,

I just gave it a quick try. It seems like a useful script when preparing
a new submission. My test used the cmake template. Here are a few issues
I noticed:

1. I specified a single requirement using the -r option, but it was
absent from the .info file generated. I tried with and without quotes
around the requirement.

The next two are some inconsistencies between the generated SlackBuild
script and the template from SlackBuilds.org:

2. Compress manpages command. The template on SBo has this:
for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; 
rm $i ; done

In the generated script:
for i in $( find /usr/man -type l ) ; do ln -s $( readlink  ).gz $i.gz ; rm $i 
; done

>From a quick glance at that line, it looks like your script is not
handling variables inside other variables. Possibly need to use an
escape before a $ somewhere.

3. The perllocal.pod removal command doesn't have the "|| true" at the
end like the SBo template.

Thanks for sharing this!

Dan

On Thu, Apr 13, 2017 at 11:01:29PM -0400, Jeremy Hansen wrote:
>I recently was working on creating a new SlackBuild and found it had
>several dependencies that were not on SBo, so I had to create those.
>Whenever I needed to do this, I would always grab the templates from
>SBo, however, it ends up requiring a lot of adjustments. There's just
>so much text to remove (comments in the SlackBuild, text in the .info,
>and adjusting the slack-desc to match the new appname and removing all
>the text in there).
>I eventually prepped some local templates, but there's some minor work
>that needed to be done (moving the files, adding the various info,
>adjusting slack-desc, etc), so I figured I should just create a script
>to handle all of this for me.
>It's pretty easy to use, you just call the script, specify the number
>that corresponds with the type of SlackBuild you want (autotools,
>python, cmake, etc), then the PRGNAM and VERSION. Optionally you can
>add a category at the end to keep things sorted that will be used as a
>subdirectory for your local repo. You can also use options to fill all
>the info in the .info (see sbgen.sh -h output for more details). The
>numbers for the various type of scripts (autotools, python, cmake, etc)
>correspond with the frequency of their usage on SBo, so it goes
>autotools, python, cmake, perl, haskell, ruby... 1-6. There is also a 7
>for those scripts that don't use any of those build systems (make just
>repackaging a binary).
>I will be adding an interactive version (like Slackware's adduser
>script) to allow easier copy/paste and to minimize long complex
>commands.
>A simple script for a cmake-based SlackBuild would be:
>sbgen.sh 3 myprogram 2.6.7
>But you can also get all of the .info filled using options:
>sbgen.sh -w [1]https://github.com/project/myprogram \
>  -d
>[2]https://github.com/project/myprogram/archive/2.6.7/myprogram-2.6.7.t
>ar.gz \
>  -m f4261584809b70f908a53fad87aa87e1 \
>  -r "program1 program2" \
>  3 program 2.6.7 libraries
>(You can use a capital D and capital M for the 64bit DOWNLOAD and
>MD5SUM variables.)
>Hopefully this can cut down on a lot of the initial prep work when
>creating a new SlackBuild.
>You can edit the top of the script to set your name, email, and
>copyright year, as well as the location to store the SlackBuilds once
>created. There's checks in place to make sure you don't overwrite
>existing SlackBuilds (unless you use the -f option to force it).
>I'd love to hear your thoughts and suggestions as well as any issues
>you may have if you're willing to test.
>[3]https://github.com/bassmadrigal/scripts/blob/master/sbgen.sh
>Thanks for your time
>Jeremy (aka bassmadrigal on LQ)
> 
> References
> 
>1. https://github.com/project/myprogram
>2. 
> https://github.com/project/myprogram/archive/2.6.7/myprogram-2.6.7.tar.gz
>3. https://github.com/bassmadrigal/scripts/blob/master/sbgen.sh

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

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

Re: [Slackbuilds-users] [ANN] New SBo Template Tool

[Daniel Prosser]

Sounds useful. I will give it a try when I get a chance and get back to
you with any feedback I might come up with. 

I haven't tried it myself, but this also sounds similar to
sbo-templates:

https://github.com/dslackw/sbo-templates

Which is also on SlackBuilds.org. Not sure if you've seen that.

Dan

On Thu, Apr 13, 2017 at 11:01:29PM -0400, Jeremy Hansen wrote:
>I recently was working on creating a new SlackBuild and found it had
>several dependencies that were not on SBo, so I had to create those.
>Whenever I needed to do this, I would always grab the templates from
>SBo, however, it ends up requiring a lot of adjustments. There's just
>so much text to remove (comments in the SlackBuild, text in the .info,
>and adjusting the slack-desc to match the new appname and removing all
>the text in there).
>I eventually prepped some local templates, but there's some minor work
>that needed to be done (moving the files, adding the various info,
>adjusting slack-desc, etc), so I figured I should just create a script
>to handle all of this for me.
>It's pretty easy to use, you just call the script, specify the number
>that corresponds with the type of SlackBuild you want (autotools,
>python, cmake, etc), then the PRGNAM and VERSION. Optionally you can
>add a category at the end to keep things sorted that will be used as a
>subdirectory for your local repo. You can also use options to fill all
>the info in the .info (see sbgen.sh -h output for more details). The
>numbers for the various type of scripts (autotools, python, cmake, etc)
>correspond with the frequency of their usage on SBo, so it goes
>autotools, python, cmake, perl, haskell, ruby... 1-6. There is also a 7
>for those scripts that don't use any of those build systems (make just
>repackaging a binary).
>I will be adding an interactive version (like Slackware's adduser
>script) to allow easier copy/paste and to minimize long complex
>commands.
>A simple script for a cmake-based SlackBuild would be:
>sbgen.sh 3 myprogram 2.6.7
>But you can also get all of the .info filled using options:
>sbgen.sh -w [1]https://github.com/project/myprogram \
>  -d
>[2]https://github.com/project/myprogram/archive/2.6.7/myprogram-2.6.7.t
>ar.gz \
>  -m f4261584809b70f908a53fad87aa87e1 \
>  -r "program1 program2" \
>  3 program 2.6.7 libraries
>(You can use a capital D and capital M for the 64bit DOWNLOAD and
>MD5SUM variables.)
>Hopefully this can cut down on a lot of the initial prep work when
>creating a new SlackBuild.
>You can edit the top of the script to set your name, email, and
>copyright year, as well as the location to store the SlackBuilds once
>created. There's checks in place to make sure you don't overwrite
>existing SlackBuilds (unless you use the -f option to force it).
>I'd love to hear your thoughts and suggestions as well as any issues
>you may have if you're willing to test.
>[3]https://github.com/bassmadrigal/scripts/blob/master/sbgen.sh
>Thanks for your time
>Jeremy (aka bassmadrigal on LQ)
> 
> References
> 
>1. https://github.com/project/myprogram
>2. 
> https://github.com/project/myprogram/archive/2.6.7/myprogram-2.6.7.tar.gz
>3. https://github.com/bassmadrigal/scripts/blob/master/sbgen.sh

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

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

Re: [Slackbuilds-users] poedit 2.0 in review

[Daniel Prosser]

Agreed. I'm not sure why the developer felt like he needed to be so rude
and condescending. He could have saved himself a lot of typing by just
politely explaining why 1.60 is needed and how to check in the git log.
Maybe it was just one of those days.

On Wed, Apr 05, 2017 at 06:34:13AM -0400, B Watson wrote:
> On 4/5/17, Willy Sudiarto Raharjo  wrote:
> >
> > well, the developer said that boost 1.60 is required for executors to
> > work, so my "hack" is not recommended by upstream, so that means poedit
> > will have to stick to 1.8.x until next Slackware release.
> >
> > here's the official answer by upstream:
> > https://github.com/vslavik/poedit/issues/375
> 
> I see one line of actual helpful information there (from the git log),
> and a whole lot of unnecessarily rude invective.
> 
> And yes, for the record, I have run into stuff where a dependency's
> minimum version was set to whatever the author happened to have installed,
> without him checking if it worked on earlier versions. So your question
> was a valid one...
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Where/how to upload sources?

[Daniel Prosser]

Fernando,

Thanks, I hadn't seen those. It looks like the 2.2.1 tarball is a couple
years older than the last commit to the 2.2 branch on git though, so
I'll use the git version instead.

Dan

On Fri, Mar 17, 2017 at 02:53:08PM -0600, Fernando Lopez wrote:
>you could also get them from here:
>[1]https://download.kde.org/stable/kde-gtk-config/
>[2]https://download.kde.org/stable/kde-gtk-config/2.2/kde-gtk-config-2.
>2-1.tar.bz2
>or
>[3]https://download.kde.org/stable/kde-gtk-config/2.2/kde-gtk-config-2.
>2.tar.bz2
> 
>On Thu, Mar 16, 2017 at 11:50 PM, Fernando Lopez
><[4]fernando.lope...@gmail.com> wrote:
> 
>oh, good to know.
> 
>On Thu, Mar 16, 2017 at 11:50 PM, Willy Sudiarto Raharjo
><[5]will...@slackbuilds.org> wrote:
> 
>> could you just git clone in the slackbuild?
>No
>We tried to list the source in the .info along with it's checksum to
>verify the source hasn't been changed
>using git clone will break whenever a new commit has been pushed
>--
>Willy Sudiarto Raharjo
> 
>  ___
>  SlackBuilds-users mailing list
>  [6]SlackBuilds-users@slackbuilds.org
>  [7]http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>  Archives - [8]https://lists.slackbuilds.org/
>  pipermail/slackbuilds-users/
>  FAQ - [9]https://slackbuilds.org/faq/
> 
>--
>
>Regards,
>Fernando Lopez Jr.
> 
>--
>
>Regards,
>Fernando Lopez Jr.
> 
> References
> 
>1. https://download.kde.org/stable/kde-gtk-config/
>2. 
> https://download.kde.org/stable/kde-gtk-config/2.2/kde-gtk-config-2.2-1.tar.bz2
>3. 
> https://download.kde.org/stable/kde-gtk-config/2.2/kde-gtk-config-2.2.tar.bz2
>4. mailto:fernando.lope...@gmail.com
>5. mailto:will...@slackbuilds.org
>6. mailto:SlackBuilds-users@slackbuilds.org
>7. http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>8. https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>9. https://slackbuilds.org/faq/

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

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

[Slackbuilds-users] Where/how to upload sources?

[Daniel Prosser]

SBo community,

I am taking over kde-gtk-config from Ryan P. McQuen. This project does
not have a place to download release tarballs as far as I can tell, only
a public git repository:

https://cgit.kde.org/kde-gtk-config.git

I have cloned the repository, checked out the latest commit for KDE
4 (version 2.2 of kde-gtk-config), removed the git files, and tarred it
up. Now I'm wondering where to host it. I see that the current version
on SBo is kept on Sourceforge:

http://sourceforge.net/projects/slackbuildsdirectlinks/files/kde-gtk-config/kde-gtk-config-2.2.1.tar.xz

(Note that the last commit for version 2.2 is newer than the 2.2.1
version SBo currently has, but the git repo no longer seems to have any
patch number tags for the 2.2 branch.) My question is, should the
updated source tarball be uploaded to the same Sourceforge page, and how
can I transfer it to an admin to do so?

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

Re: [Slackbuilds-users] Giving up all my builds. :^(

[Daniel Prosser]

Wow, 171 is indeed a lot. Thanks for all the time and effort you've put
into this. Looking at your list, the only one I use is kde-gtk-config,
so I'll volunteer for that one.

Dan

On Tue, Mar 07, 2017 at 02:25:42PM -0800, Ryan P.C. McQuen wrote:
>Slackers,
> 
>Several years back I was distro-hopping like a madman. I found that the
>community of Arch Linux was quite rude, and after trying nearly
>everything else, I started trying to crack Slackware. It turns out it
>really agreed with me (from a mindset perspective). I became far more
>involved in this community than I have in any other distro community.
> 
>Thank you for teaching me so much!
> 
>Nevertheless, I have been debating this for weeks, but I must do it. I
>am still using Slackware (and FreeSlack!), but some life changes have
>happened and I am no longer the maintainer I once was. I do not want
>the community to suffer.
> 
>I will not include the list of my builds here, but instead will point
>to this list that I will update as builds are removed:
> 
>[1]https://github.com/ryanpcmcquen/ryanpc-slackbuilds/blob/master/READM
>E.md
> 
>As of today, I am maintaining 171 builds.
> 
>I love this community and know that SBo is something very special, it
>has been an honor to be a small part of it, and I won’t be disappearing
>but I will probably remove myself from the mailing lists once enough
>builds are transferred. I will be available at this email (or
>ryanpcmcquen on IRC) if anyone wants to drop me a line.
> 
>Thank you and take care,
> 
>-Ryan
>[ryanpcmcquen.org]
>​
> 
> References
> 
>1. https://github.com/ryanpcmcquen/ryanpc-slackbuilds/blob/master/README.md

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

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

Re: [Slackbuilds-users] ncmpcpp requires mpd

[Daniel Prosser]

Interesting. Ok, well in that case, I think that information should be
mentioned in the README. The "Connection refused" error isn't really
descriptive enough for the uninitiated to understand what the problem
is. It had me scratching my head and googling for a solution the first
time I encountered it.

Also, then, for the sake of consistency with all the others, maybe
mpdscribble shouldn't list mpd as a requirement either? (Again, I 
haven't used it, so that's just my assumption. Maybe mpdscribble 
actually does need to connect to a local mpd instance.)


On Wed, Feb 08, 2017 at 05:31:49PM -0800, Doogster wrote:
> The reason is that ncmpcpp (and other mpd clients) can connect to an
> mpd instance on a different computer. They don't need mpd installed on
> the same box in order to work.
> 
> On Wed, Feb 8, 2017 at 5:23 PM, Daniel Prosser <dpross1...@msn.com> wrote:
> > Hi,
> >
> > ncmpcpp lists only libmpdclient as a requirement, but not mpd. However,
> > from what I can tell, mpd is required at runtime. If mpd is not running,
> > when I start ncmpcpp I get the following error:
> >
> > ncmpcpp: Connection refused
> >
> > I did a search in the SBo repository and I found that the following
> > MPD clients list libmpdclient as a requirement, but not mpd itself:
> >
> > ario
> > mpc
> > ncmpc
> > ncmpcpp
> > vimpc
> >
> > But there is one that lists both libmpdclient and mpd:
> >
> > mpdscribble
> >
> > Given that so many do not list mpd as a requirement, I'm inclined to
> > think I'm missing something, and mpd must not actually be required for
> > ncmpcpp. If so, I'd like to know what it is that I'm missing. If not,
> > then I think mpd should be added as a requirement for ncmpcpp, and
> > possibly the others listed above as well (though ncmpcpp is the only
> > one I've used, so I don't know for sure).
> >
> > Dan
> > ___
> > SlackBuilds-users mailing list
> > SlackBuilds-users@slackbuilds.org
> > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> > FAQ - https://slackbuilds.org/faq/
> >
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] ncmpcpp requires mpd

[Daniel Prosser]

Hi,

ncmpcpp lists only libmpdclient as a requirement, but not mpd. However,
from what I can tell, mpd is required at runtime. If mpd is not running,
when I start ncmpcpp I get the following error:

ncmpcpp: Connection refused

I did a search in the SBo repository and I found that the following
MPD clients list libmpdclient as a requirement, but not mpd itself:

ario
mpc
ncmpc
ncmpcpp
vimpc

But there is one that lists both libmpdclient and mpd:

mpdscribble

Given that so many do not list mpd as a requirement, I'm inclined to
think I'm missing something, and mpd must not actually be required for
ncmpcpp. If so, I'd like to know what it is that I'm missing. If not,
then I think mpd should be added as a requirement for ncmpcpp, and 
possibly the others listed above as well (though ncmpcpp is the only
one I've used, so I don't know for sure).

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

[Slackbuilds-users] Octave with qt5

[Daniel Prosser]

Hi,

Earlier there was some discussion about problems building VLC when Qt5
is installed. I had a similar problem with Octave. With Qt5 installed,
the editor didn't work (it depends on QScintilla, which is built against
Qt4 in Slackware), and the command window also used a really strange
font in my case. I had to add the configure flag --with-qt=4 in order 
for it to work properly. Maybe someone can confirm?

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

Re: [Slackbuilds-users] PyQt5 requirements

[Daniel Prosser]

Chris and Matteo,

Thanks for the replies. That makes sense. The question was more to clarify
my own understanding of what constitutes a requirement, which I guess
was mistaken or incomplete.

Dan

On Tue, Feb 07, 2017 at 09:23:29AM +0100, Matteo Bernardini wrote:
> 2017-02-07 9:18 GMT+01:00 Christoph Willing <chris.will...@iinet.net.au>:
> > On 07/02/17 13:40, Daniel Prosser wrote:
> >> Hi,
> >>
> >> I asked the maintainer of PyQt5 this question a couple weeks ago but
> >> didn't get a response, so I thought I would ask the group. PyQt5 lists
> >> qt5-webkit as a required dependency, but it builds and runs (at least
> >> for my use case) fine without it. Is there a reason why it is listed as
> >> a requirement? I was under the impression that requirements should be
> >> needed either to build or run the software.
> >
> > I think that statement should be something more like:
> > "requirements should be needed to build or run the software
> > so that it has some level of usefulness"
> >
> > SBo SlackBuilds and packages generally (as far as I know) don't aim to
> > be minimalist. They don't aim to  provide the barest possible pieces of
> > software with as few requirements as possible. The resulting software
> > needs to provide some amount utility, not just exist as an example of
> > how few requirements it needs.
> >
> > The level of usefulness is decided by the maintainer. In this case it
> > appears the maintainer believes qt5-webkit is needed to make the built
> > software useful - to them anyway.
> >
> >> In the case of qt5-webkit,
> >> it also takes a long time to compile, so for most people it would be
> >> preferred not to install it if not needed.
> >>
> > The fact that something is not useful (and time consuming, in this case)
> > to you doesn't necessarily mean that "most people" feel the same way (or
> > differently for that matter). If you don't need it, just leave it out.
> 
> Hi Daniel,
> 
> last time I tried if you didn't build PyQt5 against qt5-webkit
> calibre, that depends on PyQt5, didn't build at all.
> 
> Matteo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] PyQt5 requirements

[Daniel Prosser]

Hi,

I asked the maintainer of PyQt5 this question a couple weeks ago but
didn't get a response, so I thought I would ask the group. PyQt5 lists
qt5-webkit as a required dependency, but it builds and runs (at least
for my use case) fine without it. Is there a reason why it is listed as
a requirement? I was under the impression that requirements should be
needed either to build or run the software. In the case of qt5-webkit,
it also takes a long time to compile, so for most people it would be
preferred not to install it if not needed.

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

[Slackbuilds-users] Error in ncmpcpp.SlackBuild

[Daniel Prosser]

Hi,

Today I had trouble upgrading to the new version of ncmpcpp because of
what appears to be an error in the SlackBuild. ./autogen.sh and
./configure should be two separate commands, but they are joined
together into one by a "\" at the end of the line. Therefore, the
following errors result:

configure.ac:3: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are 
deprecated.  For more info, see:
configure.ac:3: 
http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.ac:11: installing './compile'
configure.ac:11: installing './config.guess'
configure.ac:11: installing './config.sub'
configure.ac:3: installing './install-sh'
configure.ac:3: installing './missing'

<<< snip >>>

src/Makefile.am: installing './depcomp'
  autoconf
make: *** No targets specified and no makefile found.  Stop.

A patch for the SlackBuild is attached.

Dan
--- ncmpcpp.SlackBuild  2017-01-15 23:34:48.270711105 -0500
+++ ncmpcpp.SlackBuild_new  2017-01-15 23:36:29.908717273 -0500
@@ -74,7 +74,7 @@
 
 sed -ie 's/if (!mpeg_file->save(TagLib::MPEG::File::ID3v2, true, 4, false))/if 
(!mpeg_file->save(TagLib::MPEG::File::ID3v2, true, 4))/g' src/tags.cpp
 
-./autogen.sh \
+./autogen.sh
 ./configure \
 --prefix=/usr \
   --libdir=/usr/lib${LIBDIRSUFFIX} \
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] xephem broken download link

[Daniel Prosser]

I'm not sure if this is temporary or not, but the download link for
xephem gives a 404 error. The source code is available at the xephem 
website, but it has a different compression type (.tgz), so the 
SlackBuild and info file would need to be updated if this link is used.

http://www.clearskyinstitute.com/xephem/xephem-3.7.7.tgz

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

Re: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir]

[Daniel Prosser]

I like David's suggestion of making sure we know exactly what problem is
going to be solved by this and how much work is going to be needed
before deciding to go ahead and do it (i.e., looking through all the
SlackBuilds and keeping track of all the different ways optional
dependencies are handled, and then making a decision). If this is too 
complicated to be included in the automated tools without programming in
handling for a ton of possible permutations and edge cases, which I 
think it might be, and there is not another significant benefit to it, 
then there's no point in doing in. If, on the other hand, it does make 
life better for the users and maintainers, then it might be worth it. 
But that needs to be determined first.

Dan

On Sat, Nov 05, 2016 at 01:45:33PM +0100, Andrzej Telszewski wrote:
> On 05/11/16 13:32, Willy Sudiarto Raharjo wrote:
> > > I mentioned the real benefit previously, that is easier and faster
> > > navigation through the website.
> > 
> > I personally don't see a real benefit if it's just easier and faster
> > navigation through website.
> > 
> > suppose you are suggesting to work on a CI (continuous integration) for
> > SBo, then i (and probably other admins) will be interested since it
> > really helped us to test and make sure all scripts are working fine.
> > 
> 
> I've been thinking about CI too.
> But hey, let's make the life better for both, the users and maintainers, at
> the same time.
> 
> > 
> > > We are doing this already, for better or worse.
> > 
> > Have you count active maintainers vs non-active maintainers out there?
> > take a simple example, i486->i586 migration. Out of 5800+ scripts out
> > there, 3800+ are still in i486 after few months since 14.2 branch is
> > released and i tried to stick with weekly public update.
> > 
> > 
> 
> This is hard to say, but yes, if time allows, I'm here to help ;-)
> I have small experience in writing PHP extension in C (on a plus side it is
> used in real world commercial application).
> 
> I could also help with some script conversions, if that would help.
> You can tell what you need and I can tell what I can give.
> 
> -- 
> Best regards,
> Andrzej Telszewski
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] ffmpeg and tetex

[Daniel Prosser]

Thanks for the reminder, Willy. I have 'su' aliased to 'su -' on my main
machine, but not on the VM where I was testing this. So maybe that error
message and/or README doesn't need to be changed. I'll leave it up to 
the maintainer to decide.

Dan

On Sat, Nov 05, 2016 at 06:52:07PM +0700, Willy Sudiarto Raharjo wrote:
> >> In the terminal you build in:
> >> source /etc/profile.de/tetex.sh
> >>
> >> It seems you installed tetex, but didn't login again or reboot. That would
> >> have fixed your issue also.
> >>
> > 
> > Aha! That's what I was missing. The first time I tried installing vlc, I
> > did not have any latex package installed. When I got that error, I
> > simply installed tetex and tried again. So I guess it's not really an
> > issue, but maybe it would be a good idea for the maintainer to put that
> > info you just told me in the README or the error message.
> 
> You should run the script using "su -" instead of "su"
> That should solve the problem with tetex PATH
> 
> 
> -- 
> Willy Sudiarto Raharjo
> 



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

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

Re: [Slackbuilds-users] ffmpeg and tetex

[Daniel Prosser]

On Sat, Nov 05, 2016 at 07:12:07AM +0100, Franzen wrote:
> 
> In the terminal you build in:
> source /etc/profile.de/tetex.sh
> 
> It seems you installed tetex, but didn't login again or reboot. That would
> have fixed your issue also.
> 

Aha! That's what I was missing. The first time I tried installing vlc, I
did not have any latex package installed. When I got that error, I
simply installed tetex and tried again. So I guess it's not really an
issue, but maybe it would be a good idea for the maintainer to put that
info you just told me in the README or the error message.

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

[Slackbuilds-users] ffmpeg and tetex

[Daniel Prosser]

(This is a copy of the message I accidentally sent as a reply to a
different thread. Please respond to this one.)

Hi,

I am installing ffmpeg on a clean 14.2 system (well, actually I am
installing vlc in order to test something, and ffmpeg is a dependency,
but that's not important). I have tetex installed instead of texlive,
and I get the following error:

Could not find texi2html! Please make sure to have tetex or texlive
installed and that texi2html is in PATH.

The message is clear enough: the problem is that texi2html is not in
the
PATH. I checked the install log for tetex and found that it is in
/usr/share/texmf/bin, so I made a symlink for it in /usr/bin. Is this
situation expected? IMO it is not a great solution, because ideally
any
given package on SBo *should* build properly on a clean system
provided
all the dependencies are present, without having to manually create
symlinks or modify the PATH. Someone new to Linux and/or Slackware,
for
example, would probably be stuck. At the very least, the README for
ffmpeg should make it clear how to get around the problem.

Or am I missing something?

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

Re: [Slackbuilds-users] ffmpeg and tetex

[Daniel Prosser]

I'm sorry, that was not supposed to be a reply to the OPTIONAL thread. I
will re-send it as a new message.

Dan

On Sat, Nov 05, 2016 at 02:23:13AM +, Daniel Prosser wrote:
> Hi,
> 
> I am installing ffmpeg on a clean 14.2 system (well, actually I am
> installing vlc in order to test something, and ffmpeg is a dependency,
> but that's not important). I have tetex installed instead of texlive,
> and I get the following error:
> 
> Could not find texi2html! Please make sure to have tetex or texlive
> installed and that texi2html is in PATH.
> 
> The message is clear enough: the problem is that texi2html is not in the
> PATH. I checked the install log for tetex and found that it is in
> /usr/share/texmf/bin, so I made a symlink for it in /usr/bin. Is this
> situation expected? IMO it is not a great solution, because ideally any
> given package on SBo *should* build properly on a clean system provided
> all the dependencies are present, without having to manually create
> symlinks or modify the PATH. Someone new to Linux and/or Slackware, for
> example, would probably be stuck. At the very least, the README for
> ffmpeg should make it clear how to get around the problem.
> 
> Or am I missing something?
> 
> Dan
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/