Re: [Slackbuilds-users] SBo-GitHub-Workflows.txt update suggestion

[Tim Dickson via SlackBuilds-users]

without setting up a key, the command

gitclone git@github:/slackbuils.git

fails with the error

Cloning into 'slackbuilds'...
g...@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

(at least for me, YMMV)
regards, Tim

On 26/07/2024 03:45, Willy Sudiarto Raharjo wrote:

hi all, regarding https://slackbuilds.org/SBo-Github-Workflows.txt
A suggestion/request to help the git neophytes.

it would be nice to add a point between 2 and 3 explaining how to 
create a certificate and upload it to you git account, otherwise 
point 3 onwards will fail. something like


if you haven't created a key for secure access, run
ssh-keygen -t ed25519 -C "your@email.address"
then
cat ~/.ssh/id_ed25519
copy the text of the catted file
in web-browser on github, click your profile icon (top left), click 
settings, under access (on the left) click SSH and GPG keys
click "New SSH key", add a title of your choice, and paste the copied 
key into the key text box, then click "Add SSH key"


This is more of personal options you can have, but AFAIK, it's not 
really necessary to do this in order to send PR to SBo




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




--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] SBo-GitHub-Workflows.txt update suggestion

[Tim Dickson via SlackBuilds-users]

hi all, regarding https://slackbuilds.org/SBo-Github-Workflows.txt
A suggestion/request to help the git neophytes.

it would be nice to add a point between 2 and 3 explaining how to create 
a certificate and upload it to you git account, otherwise point 3 
onwards will fail. something like


if you haven't created a key for secure access, run
ssh-keygen -t ed25519 -C "your@email.address"
then
cat ~/.ssh/id_ed25519
copy the text of the catted file
in web-browser on github, click your profile icon (top left), click 
settings, under access (on the left) click SSH and GPG keys
click "New SSH key", add a title of your choice, and paste the copied 
key into the key text box, then click "Add SSH key"


regards, Tim


--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] replacement of backtick in slackbuild scripts

[Tim Dickson via SlackBuilds-users]

thanks for the feedback.
My first intro was to unix on ICL drs300 (386) and drs6000 running unix 
system V in 1992/3 so I probably sit in the "legacy" era before I was 
introduced to linux. (initially redhat in lat 90's, and slackware in 
around 2003)

:-)
regards, Tim


--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] replacement of backtick in slackbuild scripts

[Tim Dickson via SlackBuilds-users]

hi all, I noticed a bunch of scripts had backtick cmdsub changed.
is there any technical reason?.
both $(cmds) and `cmds` obviously work

just interested, as i didn't notice any announcement about a preferred style
(and I tend to use backtick method myself :-)    )
regards, Tim

--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Slackbuilds: doinst.sh and douninst.sh

[Tim Dickson via SlackBuilds-users]

On 19/07/2024 09:24, Alessandro Baggi wrote:



Il 19/07/24 02:38, Willy Sudiarto Raharjo ha scritto:


if you notice on postgresql.SlackBuild, we have this commands:

mkdir -p $PKG/var/lib/pgsql/$PG_VERSION/data
chown -R postgres:postgres $PKG/var/lib/pgsql

without having postgres user and group, this would fail and the 
files/directories will not have correct permission for the application


Hi Willy,

in this way, yes if user will not be created the chown command will 
fail, but at this point why not put the chown,user/group creation 
commands in doinst.sh and remove the statement that requires postgres 
user/group?


I think it is more genuine. For example I build my packages inside a 
VM, then I install on my workstation. Here, on my workstation (and on 
other machines where I will install postgresql package) without the 
user/group creation postgresql "cannot be used" as configured so I'm 
forced to create them manually, plus configuring 
rc.local/rc.local_shutdown, while this should be done during package 
installation.


For example, I have an automated build script to compile all needed 
slackbuilds. If I add a new package that requires a specific 
user/group definition the automated script will be stopped by that 
requirement but if provided inside doinst.sh the automation will work. 
From my point of view if an operation needs to be done many times, the 
right solution is automate it (this is one big advantages of IT).


Another thing that could be inserted in the doinst.sh (for services 
that require to start on boot) is populating rc.local with the correct 
statement (if . /etc/rc.d/rc.service start...fi) with the caution 
to not rewrite the same "starts statements" if already defined (maybe 
used in upgrading the package)


In the current state the package installation is not complete because 
it misses some points:


1. User/group privileges configuration that are required by the 
software to run (as shipped in the slackbuild)
2. Configuring and prepare the system to start/stop the service (if 
enabled) during boot/reboot/shutdown process
3. A clean process during package uninstall that clean created 
user/group, start/stop system configuration in rc.local/rc.local_shutdown


My 2 cents,

Alessandro.




Although I agree it would be more convenient if users/groups and 
rc.local/rc.local_shutdown entries were done automatically (I have a 
printer driver which would benefit), these extra actions can be 
automated outside of the slackbuild script itself.
You mentioned you have a build script. You can add the user/group 
creation in that.

for example, in one of my scripts I have

#lets create required avahi user and group if needed
  if [ `cat /etc/group|grep avahi|wc -l`x = "0x" ]; then
    groupadd -g 214 avahi
  fi
  if [ `cat /etc/passwd|grep avahi|wc -l`x = "0x" ]; then
    useradd -u 214 -g 214 -c "Avahi User" -d /dev/null -s /bin/false avahi
  fi

You would also need an install script to do the same. (and the 
startup/shutdown stuff as well)
I use such a script for the avahi and epson-inkjet-printer-escpr2 
packages. one needs user and group, and they both need 
auto-startup/shutdown entries. denyhosts is another which should be 
started from rc.inet2 so it is running before sshd starts, but after the 
network is up.


As there are so many "special case" packages, it is usually left for the 
admin to externally script their preferred handling, and keep the doinst 
scripts as minimal as possible.


Unless there is consensus on a approach that is not invasive eg. is 
optional; such as a env variable which could be set if this stuff was 
wanted to be run on install,

eg:
SBOAUTOMATE=yes; export SBOAUTOMATE
then in the doinst.sh
if [ "x$SBOAUTOMATE" = "xyes" ]; then
   #do extra setup tasks automatically
   #
fi

it's not likely to get much traction.

regards, Tim

--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] kicad slackbuild

[Tim Dickson via SlackBuilds-users]

anyone having issues with md5sum i'm getting
Expected: dd187abbfb1109f8d417aa08fc75d19f
    Found:    414143a111e9217b3ae792328ff98bdc

?
regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] eclipse-platform slackbuild

[Tim Dickson via SlackBuilds-users]

the download link for the source?/binary for this package appears not be 
be available any more.

newer versions are available, but they require java 17 or higher.
regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

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

[Tim Dickson via SlackBuilds-users]

the problem is the optional dependencies. how does a tool know which 
options you like.
Only when such a tool which has your preferred optional deps recorded 
exists, can there

be a way to reverse dep without missing out bits.
regards, Tim

On 01/03/2024 09:38, Petar Petrov wrote:

there were several discussions about Slackware needing a tool such as
revdep, to check for issues like this. Search LQ, however, I did not
find a good solution that just works. I got advice to make my own
tool, as well as, statements how people use their own "home made"
tools for this.

-p

On Thu, 29 Feb 2024 at 18:12, Jim  wrote:

I recently upgraded the SBo dav1d, which upgraded the library from
libdav1d.so.6 to libdav1d.so.7.

Unfortunately, a couple of other SBo packages (libheif and vlc) had
references to (specifically) libdav1d.so.6, which caused them to whine a
bit.

It was easy enough to recompile libheif and vlc after I found the problem,
but this got me wondering...

Does anyone have an easy way of tracking down this sort of "breakage" which
might happen when upgrading an SBo package?

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


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



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

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

[Tim Dickson via SlackBuilds-users]

it is hard for optional dependencies. for hard deps, you can do an 
advanced reverse dependency(full) search on slackbuilds.org


Personally I keep build lists for the things I use, including optional 
deps, and build flags and other special build instructions.
It is more work, and when a package is updated one should recheck the 
deps incase they have changed, but it helps, so I rebuild
all packages that directly depend on the updated one. Occasionally you 
have to rebuild further up the dep tree, but it works

most of the time.
Regards, Tim

On 29/02/2024 16:12, Jim wrote:

I recently upgraded the SBo dav1d, which upgraded the library from
libdav1d.so.6 to libdav1d.so.7.

Unfortunately, a couple of other SBo packages (libheif and vlc) had
references to (specifically) libdav1d.so.6, which caused them to whine a
bit.

It was easy enough to recompile libheif and vlc after I found the problem,
but this got me wondering...

Does anyone have an easy way of tracking down this sort of "breakage" which
might happen when upgrading an SBo package?

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



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

Re: [Slackbuilds-users] webkit2gtk api question

[Tim Dickson via SlackBuilds-users]

yes, I noticed a discussion online about the issues relating to gnome 
and the search in the help system

getting broken with the shift to 4.1.
I've requested to the xiphos developer that he provides a way to enable 
using the 4.0 api even if he adds support

for 4.1 to support those of us stuck on 4.0.
regards, Tim

On 16/02/2024 17:31, Didier Spaier wrote:

Since zenity version 3.43.0 the requirement for WebkitGTK optional dependency
has been bumped to API 4.1 :(

As it is optional I will just built it without if I need to upgrade.

But for yelp (current version: 42.2) one can still choose the API, fortunately
for me (Mate is the flagship of Slint and I wouldn't ship Mate without its
contextual help system).

Cheers,
Didier

Le 2/16/24 à 16:46, Tim Dickson via SlackBuilds-users a écrit :

4.1 is optionally used by zenity as well.
I raised the question on linuxquestions a couple of years ago,
https://www.linuxquestions.org/questions/slackware-14/webkit2gtk4-1-gtk3-query-4175710629/
 and at the time we standardised on the 4.0 api, as the problem was if multiple 
components link to different versions of libsoup (2 and 3) then the binaries 
fail, because there can't be links to 2 different soup libs in the same binary 
without it crashing as soon as one of them is referenced. As distros such as 
ubuntu and debian are moving to 4.1api it means that applications are looking 
at moving as well, so I wondered what the situation was these days.

As far as I understand, the only difference between the 2 api's is one links to
soup2 and the other links to soup3, the api is the same, just not binary
compatible.  If the packages detect the newer webkit2gtk it may be possible to
just switch, and as long as all the deps are rebuilt, it may just work. I don't
know if there are links to slackware's stock libsoup(2) that are also being
used, which might be problematic.
the reason I asked this time is because the developer of xiphos is thinking of
updating to 4.1 api, which would effect yelp as well. I don't mind which is the
standard, but I wouldn't like to loose an application if it changes either. I
guess it depends on whether the build scripts see the 4.1 webkit2gtk and use it
if it is present. As you point out, it affects a number of builds.
regards, Tim

On 16/02/2024 12:16, Didier Spaier wrote:

Hi,
I can't answer this is question but a search of direct dependees on SBO tells
that 4.0 has 29 (in addition atril and geany-plugins can be built against it)
and 4.1 only one: epiphany.

I remember having discussed this with Bob and if 4.1 is removed maybe epiphany
could be installed as a flatpak (i do not require its removal though). I do not
know if a bundle of epiphany with 4.1 could be built.

Cheers,
Didier



Le 2/16/24 à 11:55, Tim Dickson via SlackBuilds-users a écrit :

hi all, I have a question about webkit2gtk api 4.0 vs 4.1
webkit2gtk is currently used by wxGTK3, yelp, xiphos, wxWidgets, gambas3 and
wxPython4 plus a lot of other packages which I don't use.

Does anyone know which dependant packages work with both versions of the api ?
Apparently a number of major distros are moving over to 4.1api so I'm trying to
find out what packages support either api versions
as you can't have both installed at the same time.
I've responded to the xiphos developer who first raised the question to me on
the devel mailing list, and asked the question on the gambas mailing list, but
if someone has collated the information that would be useful.
regards, Tim

___
SlackBuilds-users mailing list
SlackBuilds-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] webkit2gtk api question

[Tim Dickson via SlackBuilds-users]

4.1 is optionally used by zenity as well.
I raised the question on linuxquestions a couple of years ago, 
https://www.linuxquestions.org/questions/slackware-14/webkit2gtk4-1-gtk3-query-4175710629/ 
and at the time we standardised on the 4.0 api, as the problem was if 
multiple components link to different versions of libsoup (2 and 3) then 
the binaries fail, because there can't be links to 2 different soup libs 
in the same binary without it crashing as soon as one of them is 
referenced. As distros such as ubuntu and debian are moving to 4.1api it 
means that applications are looking at moving as well, so I wondered 
what the situation was these days.


As far as I understand, the only difference between the 2 api's is one 
links to soup2 and the other links to soup3, the api is the same, just 
not binary compatible.  If the packages detect the newer webkit2gtk it 
may be possible to just switch, and as long as all the deps are rebuilt, 
it may just work. I don't know if there are links to slackware's stock 
libsoup(2) that are also being used, which might be problematic.
the reason I asked this time is because the developer of xiphos is 
thinking of updating to 4.1 api, which would effect yelp as well. I 
don't mind which is the standard, but I wouldn't like to loose an 
application if it changes either. I guess it depends on whether the 
build scripts see the 4.1 webkit2gtk and use it if it is present. As you 
point out, it affects a number of builds.

regards, Tim

On 16/02/2024 12:16, Didier Spaier wrote:

Hi,
I can't answer this is question but a search of direct dependees on SBO tells
that 4.0 has 29 (in addition atril and geany-plugins can be built against it)
and 4.1 only one: epiphany.

I remember having discussed this with Bob and if 4.1 is removed maybe epiphany
could be installed as a flatpak (i do not require its removal though). I do not
know if a bundle of epiphany with 4.1 could be built.

Cheers,
Didier



Le 2/16/24 à 11:55, Tim Dickson via SlackBuilds-users a écrit :

hi all, I have a question about webkit2gtk api 4.0 vs 4.1
webkit2gtk is currently used by wxGTK3, yelp, xiphos, wxWidgets, gambas3 and
wxPython4 plus a lot of other packages which I don't use.

Does anyone know which dependant packages work with both versions of the api ?
Apparently a number of major distros are moving over to 4.1api so I'm trying to
find out what packages support either api versions
as you can't have both installed at the same time.
I've responded to the xiphos developer who first raised the question to me on
the devel mailing list, and asked the question on the gambas mailing list, but
if someone has collated the information that would be useful.
regards, Tim

___
SlackBuilds-users mailing list
SlackBuilds-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] webkit2gtk api question

[Tim Dickson via SlackBuilds-users]

hi all, I have a question about webkit2gtk api 4.0 vs 4.1
webkit2gtk is currently used by wxGTK3, yelp, xiphos, wxWidgets, gambas3 
and wxPython4 plus a lot of other packages which I don't use.


Does anyone know which dependant packages work with both versions of the 
api ?
Apparently a number of major distros are moving over to 4.1api so I'm 
trying to find out what packages support either api versions

as you can't have both installed at the same time.
I've responded to the xiphos developer who first raised the question to 
me on the devel mailing list, and asked the question on the gambas 
mailing list, but if someone has collated the information that would be 
useful.

regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] update homepage query

[Tim Dickson via SlackBuilds-users]

On 13/02/2024 18:58, Jeremy Hansen wrote:
On Tue, Feb 13, 2024, 6:30 AM Tim Dickson via SlackBuilds-users 
 wrote:


Hi all, there are three slackbuilds I look after which need a
homepage
update from http to https
should I submit 3 updates with .info updated and build no. bumped,
or is
there an easier way.

as the build is identical, maybe the build number doesn't need
bumping,
but is it possible
to do an updated with no change in version or build?

the old http home sites still work, they are just permanently
redirected
to the https versions.
regards, Tim


I wouldn't do a build number bump since the resulting program that's 
created remains unchanged. If you changed dependencies or the 
compilation process, that should constitute a build number bump.


Personally, I would do individual commits but submit them under a 
single PR... like I did here in the following PR:


https://github.com/SlackBuildsOrg/slackbuilds/pull/3261

Jeremy

thanks. I submitted individual updates. it turns out one needed a md5sum 
update as well, so that particular one got a build bump. I'm not used to 
git so just used the web submit form which works well.

Regards, Tim___
SlackBuilds-users mailing list
SlackBuilds-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] update homepage query

[Tim Dickson via SlackBuilds-users]

Hi all, there are three slackbuilds I look after which need a homepage 
update from http to https
should I submit 3 updates with .info updated and build no. bumped, or is 
there an easier way.


as the build is identical, maybe the build number doesn't need bumping, 
but is it possible

to do an updated with no change in version or build?

the old http home sites still work, they are just permanently redirected 
to the https versions.

regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] Linphone maintenance

[Tim Dickson via SlackBuilds-users]

you could do a cmake-202x opt package like was done for 14.2 with the 
newest version of cmake

have a look at it's README_SBo.txt for tips as well.
regards, Tim

On 08/02/2024 11:48, Sebastian Arcus wrote:





___
SlackBuilds-users mailing list
SlackBuilds-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 md5sum mismatch

[Tim Dickson via SlackBuilds-users]

I'm getting 126e593e5990a1a3bb7768bfb2317da8 for the kicad-7.0.9 source, not
what is in the info file.

The kicad seems to build ok.
anyone else got the same problem?
regards, Tim

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

Re: [Slackbuilds-users] issue with openimageio after pybind11 update

[Tim Dickson via SlackBuilds-users]

thanks for the heads up chris, I wondered if that might be the case.
Maybe a note in the opencolorio readme to temporarily uninstall 
openimageio if present before building the package would be useful?

regards, Tim

On 20/01/2024 01:31, Christoph Willing wrote:

On 20/1/24 08:56, Tim Dickson via SlackBuilds-users wrote:

since the pybind11 update opencolorio is no longer building for me.
[]

I don't know why it's trying to link to libOpenImageIO files when it 
is not marked as a dependency (I do have openimageio-2.2.21.0-4 
installed)

anyone else seeing this or got a fix?
thanks,Tim


openimageio and opencolorio will each try to link against the other if 
present. It's an unfortunate "natural" recursive dependency which I 
try to minimise in the .info files by setting opencolorio as a 
dependency of openimageio but _not_ setting openimageio as a 
dependency of opencolorio. This attempted minimisation fails in the 
case where openimageio is already installed when building opencolorio, 
which is exactly your situation.


If a clean VM for building is not available, I would recommend that 
you temporarily remove openimageio, then build opencolorio, then 
reinstall (or even better: rebuild & install) openimageio.


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] issue with openimageio after pybind11 update

[Tim Dickson via SlackBuilds-users]

since the pybind11 update opencolorio is no longer building for me.
at 86% it gives
[ 86%] Linking CXX executable ociolutimage
/usr/bin/ld: warning: libdcmimage.so.17, needed by 
/usr/lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libdcmimgle.so.17, needed by 
/usr/lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libdcmdata.so.17, needed by 
/usr/lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: liboflog.so.17, needed by 
/usr/lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libofstd.so.17, needed by 
/usr/lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`OFString::OFString()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmStack::top() const'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`OFLog::configure(OFLogger::LogLevel)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmFileFormat::getDataset()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`OFFilename::OFFilename(char const*, bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetFloat32(DcmTagKey const&, float&, unsigned long, bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DiRegister::DiRegister()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmTag::getTagName()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmFileFormat::loadFile(OFFilename const&, E_TransferSyntax, 
E_GrpLenEncoding, unsigned int, E_FileReadMode)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DicomImage::DicomImage(char const*, unsigned long, unsigned long, 
unsigned long)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetOFString(DcmTagKey const&, OFString&, unsigned long, 
bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DiRegister::~DiRegister()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmFileFormat::DcmFileFormat()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetSint32(DcmTagKey const&, int&, unsigned long, bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetUint32(DcmTagKey const&, unsigned int&, unsigned 
long, bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`OFString::~OFString()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmStack::DcmStack()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmStack::~DcmStack()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetFloat64(DcmTagKey const&, double&, unsigned long, bool)'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`OFFilename::~OFFilename()'
/usr/bin/ld: /usr/lib64/libOpenImageIO.so: undefined reference to 
`DcmItem::findAndGetUint16(DcmTagKey const&, unsigned short&, unsigned 
long, bool)'

collect2: error: ld returned 1 exit status
make[2]: *** 
[src/apps/ociolutimage/CMakeFiles/ociolutimage.dir/build.make:100: 
src/apps/ociolutimage/ociolutimage] Error 1
make[1]: *** [CMakeFiles/Makefile2:1690: 
src/apps/ociolutimage/CMakeFiles/ociolutimage.dir/all] Error 2

make: *** [Makefile:146: all] Error 2

I don't know why it's trying to link to libOpenImageIO files when it is 
not marked as a dependency (I do have openimageio-2.2.21.0-4 installed)

anyone else seeing this or got a fix?
thanks,Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] KDE kuickshow image viewer (testing, needs extra-cmake-modules)

[Tim Dickson via SlackBuilds-users]

On 11/12/2023 10:43, David Chmelik wrote:

On Mon, 11 Dec 2023 05:24:48 -0500 (EST), B. Watson wrote:

On Mon, 11 Dec 2023, David Chmelik wrote:

I have updated the old KDE image viewer (simple/minimalist)
kuickshow.SlackBuild for testing.

You probably can update kuickshow without having to have a cmake-extras
package, if your script manually sets some -D
variables on the cmake command line.

Also. Have you addressed these issues, found by sbopkglint?

Still learning sbo-maintainer-tools.  Will address these before I formally
upload.  All below failed tests are about stuff in the source code file
itself.  Should I fix these in script and/or graphics editor, or contact/
bug-report KDE?
What i do is report upstream, and in the meantime edit the files in the 
build script via sed (or patch), chmod etc. and use convert for resizing 
the iconsAs you know exactly what the issues are, you can submit fixes 
upstream as well. that really helps them get approved. regards, Tim___
SlackBuilds-users mailing list
SlackBuilds-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] Tuxpaint: homepage URL

[Tim Dickson via SlackBuilds-users]

thanks for the report and fix. I'll report the issue upstream, as it 
used to be ok.

regards, Tim

On 03/11/2023 14:43, Willy Sudiarto Raharjo wrote:

The homepage of Tuxpaint is not :

https://www.tuxpaint.org

but

https://tuxpaint.org


Fixed on my branch


___
SlackBuilds-users mailing list
SlackBuilds-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] MPD needs an update

[Tim Dickson via SlackBuilds-users]

this might help.
https://github.com/MusicPlayerDaemon/MPD/commit/f869593ac8913e52c711e974257bd6dc0d5dbf26

On 27/10/2023 19:01, Андрей Рабусов wrote:

Hi all,

I think the mpd's slackbuild (and the corresponding info file) needs to be
updated to match the latest mpd version, 0.23.14, due to the libfmt 
update to version 10. I didn't get a reply from the maintainer, so 
hopefully somebody else could quickly fix it.


The build error with the current mpd version, 0.23.9, is as follows:

[419/639] Compiling C++ object 
src/decoder/plugins/libdecoder_plugins.a.p/FfmpegDecoderPlugin.cxx.o
FAILED: 
src/decoder/plugins/libdecoder_plugins.a.p/FfmpegDecoderPlugin.cxx.o
ccache c++ -Isrc/decoder/plugins/libdecoder_plugins.a.p 
-Isrc/decoder/plugins -I../src/decoder/plugins -Isrc -I../src -I. -I.. 
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include 
-I/usr/include/opus -I/usr/include/dbus-1.0 
-I/usr/lib64/dbus-1.0/include -I/usr/include/SDL2 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch 
-Wnon-virtual-dtor -Wextra -Wpedantic -std=c++17 -O3 -ffast-math 
-ftree-vectorize -Wcast-qual -Wdouble-promotion -Wmissing-declarations 
-Wshadow -Wunused -Wvla -Wwrite-strings -Wno-stringop-overflow 
-fno-threadsafe-statics -fmerge-all-constants -Wcomma-subscript 
-Wextra-semi -Wmismatched-tags -Woverloaded-virtual -Wsign-promo 
-Wvolatile -Wvirtual-inheritance -Wno-non-virtual-dtor 
-Wsuggest-override -fvisibility=hidden -ffunction-sections 
-fdata-sections -D_GNU_SOURCE -O2 -fPIC -fPIC -DHAVE_UNIX -pthread 
-D_REENTRANT -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -MD -MQ 
src/decoder/plugins/libdecoder_plugins.a.p/FfmpegDecoderPlugin.cxx.o 
-MF 
src/decoder/plugins/libdecoder_plugins.a.p/FfmpegDecoderPlugin.cxx.o.d 
-o 
src/decoder/plugins/libdecoder_plugins.a.p/FfmpegDecoderPlugin.cxx.o 
-c ../src/decoder/plugins/FfmpegDecoderPlugin.cxx

In file included from ../src/Log.hxx:25,
                 from ../src/decoder/plugins/FfmpegDecoderPlugin.cxx:47:
/usr/include/fmt/core.h: In instantiation of ‘constexpr 
fmt::v10::detail::value fmt::v10::detail::make_arg(T&) [with 
bool PACKED = true; Context = 
fmt::v10::basic_format_context; T = 
AVSampleFormat; typename std::enable_if::type  
= 0]’:
/usr/include/fmt/core.h:1808:51:   required from ‘constexpr 
fmt::v10::format_arg_store::format_arg_store(T& ...) 
[with T = {const char*, AVSampleFormat}; Context = 
fmt::v10::basic_format_context; Args = 
{const char*, AVSampleFormat}]’
/usr/include/fmt/core.h:1826:18:   required from ‘constexpr 
fmt::v10::format_arg_storestd::remove_reference::type>::type ...> 
fmt::v10::make_format_args(T& ...) [with Context = 
fmt::v10::basic_format_context; T = {const 
char*, AVSampleFormat}]’
../src/Log.hxx:50:31:   required from ‘void LogFmt(LogLevel, const 
Domain&, const S&, Args&& ...) [with S = char [51]; Args = {const 
char*&, AVSampleFormat&}]’
../src/Log.hxx:99:8:   required from ‘void FmtError(const Domain&, 
const S&, Args&& ...) [with S = char [51]; Args = {const char*&, 
AVSampleFormat&}]’

../src/decoder/plugins/FfmpegDecoderPlugin.cxx:358:11:  required from here
/usr/include/fmt/core.h:1576:63: error: 
‘fmt::v10::detail::type_is_unformattable_for 
_’ has incomplete type

 1576 |     type_is_unformattable_for _;
      |                      ^
/usr/include/fmt/core.h:1580:7: error: static assertion failed: Cannot 
format an argument. To make type T formattable provide a formatter 
specialization: https://fmt.dev/latest/api.html#udt

 1580 |       formattable,
      |       ^~~
/usr/include/fmt/core.h:1580:7: note: formattable evaluates to false

Regards
Andrei

___
SlackBuilds-users mailing list
SlackBuilds-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] new webkit2gtk{4.1}

[Tim Dickson via SlackBuilds-users]

...

https://bugs.webkit.org/show_bug.cgi?id=228268
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2498

I guess this is the issue with the NVidia driver/webkit itself rather 
than yelp, so we need upstream to work on this.



does that mean holding fire on the update, or shall we continue to test?
regards, Tim

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

Re: [Slackbuilds-users] new webkit2gtk{4.1}

[Tim Dickson via SlackBuilds-users]

also gambas3, wxWidgets and wxGTK3 depend (optionally) on webkit2gtk
(wxWidgets requires webkit2gtk for audacity to build/run, and webkit2gtk 
will be required for gambas in next update, rather than optional)


and zenity depends (optionally) on webkit2gtk4.1

Regards, Tim

(sorry if this got sent twice)

___
SlackBuilds-users mailing list
SlackBuilds-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 - 20230812.1

[Tim Dickson via SlackBuilds-users]

zoom md5sum is ok, you just have to re-download as the "source" always 
has the same name.

regards, Tim

On 12/08/2023 05:34, Fernando Lopez wrote:

zoom-linux invalid MD5 sum.

On Fri, Aug 11, 2023 at 9:06 PM Willy Sudiarto Raharjo 
 wrote:


Sat Aug 12 01:39:29 UTC 2023
academic/ephem: Added (an astronomy program).
academic/xephem: Updated for version 4.1.0.
audio/ncspot: Fix URLs.
audio/qpwgraph: Updated for version 0.5.2.
desktop/UltimateDailyWallpaper: Updated for version 3.3.5.
desktop/bukubrow: Use static.crates.io .
desktop/leftwm: Fix URLs.
desktop/nwg-dock: Updated for version 0.3.6.
desktop/nwg-shell-config: Updated for version 0.5.14.
desktop/variety: Change the dependency to python2-httplib2.
desktop/waybar: Fix github tarball handling.
desktop/weston: Updated for version 10.0.5.
desktop/zenity: Updated for version 3.44.2.
development/SQLiteStudio: Updated for version 3.4.4.
development/argouml: Updated for version 0.35.1.
development/colordiff: Updated for version 1.0.21, new maintainer.
development/dbeaver-ce: Updated for version 23.1.4.
development/hugo: Updated for version 0.117.0.
development/kdiff3: Updated for version 1.9.6 and new maintainer.
development/mdbook: Fix URLs.
development/pre-commit: Added (git pre-commit hooks.).
development/pycharm: Updated for version 2023.2.232.8660.197.
development/racer: Use static.crates.io .
development/rizin: Updated for version 0.6.0
development/rustup: Use static.crates.io .
development/squirrel-sql: Updated for version 4.2.0.
development/universal-ctags: Updated for version p6.0.20230806.0
development/xnedit: Updated for version 1.5.0.
games/KoboDeluxe: New maintainer, various fixes.
games/abuse: New maintainer, fix segfault.
games/gzdoom: Fix build on -current.
games/hedgewars: New maintainer, various fixes.
gis/saga-gis: Updated for version 9.1.1.
gis/whitebox-tools: Fix URLs.
graphics/tesseract: Updated for version 5.3.2.
graphics/ueberzugpp: Updated for version 2.9.0.
graphics/vuescan: Updated for version 9.8.14.
libraries/libxmlb: Updated for version 0.3.12.
libraries/pthsem: Use working download URL.
libraries/wxsvg: Updated for version 1.5.24.
libraries/yajl: Added patches from fedora, changed maintainer.
misc/bitwarden-desktop: Updated for version 2023.7.1.
misc/fcitx-mozc: Use working download URL.
misc/fcitx5-mozc: Use working download URL.
misc/grc: Updated for version 1.13, new maintainer, support csh.
misc/kasumi: Use working download URL.
multimedia/dvdstyler: Updated for version 3.3b3.
multimedia/openshot: Change the dependency to python3-httplib2.
multimedia/smplayer: Update to version 23.6.0
multimedia/spot: Fix URLs.
network/armcord: Updated for version 3.2.1.
network/asuka: Fix URLs.
network/castor: Fix URLs.
network/connman: Updated for version 1.42.
network/element-desktop: Updated for version 1.11.38.
network/emailrelay: Updated for version 2.5.
network/kismet: Updated for version 2023.07.R1.
network/librewolf: Updated for version 116.0.
network/microsoft-edge: update 115.0.1901.203
network/newsboat: Use static.crates.io .
network/nextcloud-desktop: Updated for version 3.9.2.
network/rspamd: Updated for version 3.6
network/signal-desktop: Updated for version 6.28.0.
network/slack: Updated for version 4.33.84.
network/zoom-linux: Fix perms.
network/zoom-linux: Updated for version 5.15.7.6521
office/calcurse: Change the optional dependency to python3-httplib2.
office/jstock: Updated for version 1.0.7.60.
office/navi: Fix URLs.
office/pandoc-bin: Updated for version 3.1.6.1.
office/vmd: New maintainer.
office/zim: Updated for version 0.75.2.
perl/MoarVM: Updated for version 2023.06
perl/nqp: Updated for version 2023.06
perl/perl-Test-Harness: Updated for version 3.46.
perl/rakudo: Updated for version 2023.06
perl/zef: Updated for version 0.18.2
python/cryptography: Fix URLs.
python/google-api-python-client: Change the dep to python2-httplib2.
python/httplib2: Removed (splitted in python2/3 scripts).
python/pybind11: Update README
python/python3-bcrypt: Fix URLs.
python/python3-cfgv: Added (configuration validation).
python/python3-identify: Added (file identification).
system/Iosevka-aile: Updated for vertsion 26.0.2.
system/Iosevka-etoile: Updated for vertsion 26.0.2.
system/alacritty: Use static.crates.io .
system/android-file-transfer: Fix conflict with pybind11.
system/bat: Fix URLs.
system/bottom: Fix URLs.
system/bzip3: Updated for version 1.3.2.
system/conky: Updated for version 1.19.3.
system/cronie: Updated for version 

[Slackbuilds-users] Botan slackbuild

[Tim Dickson via SlackBuilds-users]

Maybe the maintainer of keepassxc or corectrl might be interested in 
taking Botan as it is a dep for them.

If neither are interested, i'll look after it, as I use keepassxc.
thanks,
Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] so-called terminal image viewers

[Tim Dickson via SlackBuilds-users]

fbida works just fine.
pass it the list of images and then use pageup/pagedown to navigate, and 
q or esc to quit. (h for help)

eg.
fbi smiley.png party.jpg game.bmp
or for viewing all files in the current dir
fbi *

regards, Tim

On 22/06/2023 12:05, dchme...@gmail.com wrote:

On 6/22/23 3:47 AM, Ralph Spitzner wrote:

dchme...@gmail.com wrote on 6/22/23 12:02 PM:
Recent years there have been a few so-called 'terminal image 
viewers' SlackBuilds uploaded but in these descriptions people are 
lying through 


slackware has fbv


No; Slackware has seejpeg (which hasn't worked in years on newer 
hardware).  SlackBuilds.org (SBo, which isn't (official) Slackware) 
has fbida & fbv, neither which can go to previous or next images 
anymore, apparently, which I reported years ago to the maintainers and 
one or more of the programmers but never heard back.  That's why I'm 
looking for new stuff, and they're all called terminal image viewers 
but aren't: only X terminal viewers!  There are a couple other 
framebuffer ones, but they don't seem to take input after you display 
an image.

___
SlackBuilds-users mailing list
SlackBuilds-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] OpenCASCADE build issue

[Tim Dickson via SlackBuilds-users]

On 20/06/2023 22:54, B. Watson wrote:



On Tue, 20 Jun 2023, Tim Dickson via SlackBuilds-users wrote:


Hi all, I'm getting build failure with the error

[100%] Linking CXX executable ../../lin64/gcc/bin/DRAWEXE
/usr/bin/ld: /usr/lib64/libldb.so.2: undefined reference to 
`rep_memset_s@SAMBA_4.15.13'


What happens if you run this?

ldd /usr/lib64/libldb.so.2

I bet you get a 'libreplace-samba4.so => not found' error.

If so, try reinstalling samba.

you hit it on the nail. for some reason I needed to reinstall it.
thanks for the pointer.
Tim

___
SlackBuilds-users mailing list
SlackBuilds-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] OpenCASCADE build issue

[Tim Dickson via SlackBuilds-users]

Hi all, I'm getting build failure with the error

[100%] Linking CXX executable ../../lin64/gcc/bin/DRAWEXE
/usr/bin/ld: /usr/lib64/libldb.so.2: undefined reference to 
`rep_memset_s@SAMBA_4.15.13'

collect2: error: ld returned 1 exit status
make[2]: *** [src/DRAWEXE/CMakeFiles/DRAWEXE.dir/build.make:118: 
lin64/gcc/bin/DRAWEXE-7.7.0] Error 1
make[1]: *** [CMakeFiles/Makefile2:3747: 
src/DRAWEXE/CMakeFiles/DRAWEXE.dir/all] Error 2

make: *** [Makefile:136: all] Error 2

I am using the following build flags/options
FREEIMAGE=yes TTB=yes GL2PS=yes

( VTK was built with IMAGING=yes MPI=yes )

any ideas?
regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] [python3-setuptools] A Question about a SlackBuild.

[Tim Dickson via SlackBuilds-users]

have you tried just sed'ing the version in the toml line to the version 
that ships with slackware 15.0  ?
quite often that works, and the only reason the requirement changed was 
that the system it was developed on had a newer setuptools, not that it 
actually used any new features.

regards, Tim

On 09/06/2023 10:23, fourtysixandtwo wrote:

Hi Yth,

I have a slackbuild for setuptools, using the same version (65.1.1) 
and patch from current source that I've been thinking of uploading.  
I've tested it with a newer version as well, so I'm not set on using 
the one from current.


I've attached the slackbuild if you want to give it a try. It could 
use another set of eyes and testing.  Let me know your thoughts.


Here's a snippet from the README on how to use it.

Installs to /opt/python3.9/site-packages.

Add the following before the python3 build commands in your
Slackbuild to use this version over the stock one in 15.0:

export PYTHONPATH=/opt/python3.9/site-packages/

Cheers

P.S. It's currently 26C in my house and I can't sleep so you're 
getting this reply now instead of later


On Fri, Jun 9, 2023 at 1:44 AM Arnaud via SlackBuilds-users 
 wrote:


Hi everybody !

        I'm facing a slight problem.
I've updated python3-dulwich, apparently more than a month ago.
It is used by Kallithea and hg-git which I also maintain, I'm not
using hg-git
often, but I have a working and updated Kallithea service around.
Well it seems I didn't test this update as throughly as I thought.
Or at all, for that matter.

The build is broken and produces those files :

/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/PKG-INFO
/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/SOURCES.txt

/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/dependency_links.txt

/usr/lib64/python3.9/site-packages/UNKNOWN-0.0.0-py3.9.egg-info/top_level.txt

That, obviously, doesn't work as expected.

The problem resides in the python-setuptools package of Slackware
15.0 which is
at version 57.5.0.
In dulwich/pyproject.toml lies the answer :
[build-system]
requires = ["setuptools>=61.2"]


Here I've got three solutions :

 * revert dulwich to earlier version, 0.21.3, and wait for
Slackware 15.1.

 * create a python3-setuptools package which'll overwrite
Slackware's stock
python-setuptools with a newer version. Could even name it
python-setuptools for
obvious, and transparent, replacement. It'll probably be updated
naturally when
Slackware releases 15.1 is out.
 -> I have it working with latest setuptools 67.8.0, and dulwich
builds fine.

 * somehow prepare a local setuptools to use for building dulwich,
adding the
source to dulwich's info file, and building both while installing
only dulwich.


Does anyone have any advice on that ?
I mean, apart from the obvious « test your friggin' SlackBuilds before
submitting them », I've got it in a loop between my ears, and in
French...

 - Yth.
___
SlackBuilds-users mailing list
SlackBuilds-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] kicade build issue

[Tim Dickson via SlackBuilds-users]

I am getting the following error building kicad on vanilla slackware 
15.0 64bit (no multilib)


[ 92%] Building CXX object 
plugins/3d/oce/CMakeFiles/s3d_plugin_oce.dir/loadmodel.cpp.o
cd /tmp/SBo/kicad-5.1.9/build/plugins/3d/oce && /usr/bin/c++ 
-DGLM_FORCE_CTOR_INIT -DHAVE_STDINT_H -DKICAD_SCRIPTING 
-DKICAD_SCRIPTING_ACTION_MENU -DKICAD_SCRIPTING_MODULES 
-DKICAD_SCRIPTING_WXPYTHON -DKICAD_SPICE -DKICAD_USE_OCC 
-DUSE_WX_OVERLAY -DWXUSINGDLL -DWX_COMPATIBILITY -D_FILE_OFFSET_BITS=64 
-D__WXGTK__ -Ds3d_plugin_oce_EXPORTS -I/tmp/SBo/kicad-5.1.9/include 
-I/tmp/SBo/kicad-5.1.9/3d-viewer -isystem /usr/include/opencascade 
-isystem /usr/lib64/wx/include/gtk3-unicode-3.0 -isystem 
/usr/include/wx-3.0 -Wall -O2 -fPIC -std=c++11 -Wsuggest-override 
-Werror=vla -pthread -Wshadow -O3 -DNDEBUG -fPIC -fvisibility=hidden 
-fvisibility-inlines-hidden -std=gnu++11 -MD -MT 
plugins/3d/oce/CMakeFiles/s3d_plugin_oce.dir/loadmodel.cpp.o -MF 
CMakeFiles/s3d_plugin_oce.dir/loadmodel.cpp.o.d -o 
CMakeFiles/s3d_plugin_oce.dir/loadmodel.cpp.o -c 
/tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp
/tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp: In function âbool 
processFace(const TopoDS_Face&, DATA&, SGNODE*, std::vector*, 
Quantity_Color*)â:
/tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp:868:64: error: âclass 
Poly_Triangulationâ has no member named âNodesâ; did you mean âNodeâ?
  868 | const TColgp_Array1OfPnt&    arrPolyNodes = 
triangulation->Nodes();

| ^
| Node
/tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp:869:73: warning: 
âconst Poly_Array1OfTriangle& Poly_Triangulation::Triangles() constâ is 
deprecated: Deprecated method, Triangle() should be used instead 
[-Wdeprecated-declarations]
  869 | const Poly_Array1OfTriangle& arrTriangles = 
triangulation->Triangles();

  | ^~
In file included from 
/usr/include/opencascade/Poly_ListOfTriangulation.hxx:19,

 from /usr/include/opencascade/BRep_Tool.hxx:30,
 from /tmp/SBo/kicad-5.1.9/plugins/3d/oce/loadmodel.cpp:57:
/usr/include/opencascade/Poly_Triangulation.hxx:330:32: note: declared here
  330 |   const Poly_Array1OfTriangle& Triangles() const { return 
myTriangles; }

  |    ^
make[2]: *** 
[plugins/3d/oce/CMakeFiles/s3d_plugin_oce.dir/build.make:90: 
plugins/3d/oce/CMakeFiles/s3d_plugin_oce.dir/loadmodel.cpp.o] Error 1

make[2]: Leaving directory '/tmp/SBo/kicad-5.1.9/build'
make[1]: *** [CMakeFiles/Makefile2:2328: 
plugins/3d/oce/CMakeFiles/s3d_plugin_oce.dir/all] Error 2

make[1]: Leaving directory '/tmp/SBo/kicad-5.1.9/build'
make: *** [Makefile:166: all] Error 2

All deps are up to date: using build tree as below.

kicad 5.1.9-1 k zzz ( electronic pcb circuit design/layout etc) - 
temporarily remove wxWidgets and reinstall wxGTK3 then wxPython3 before 
building. (reinstall wxWidgets after installing)

-requires
 wxPython3 3.0.2.0-4 k zz
 -requires
  wxGTK3 3.0.5-4 k z
  -requires
   webkit2gtk 2.40.0-2 k 
   -requires
    bubblewrap 0.4.0-1 -no deps k z
    geoclue2 2.6.0-1 k zzz
    AVAHI=yes
    -optional
 avahi 0.8-7 k zz
 -requires
      libdaemon 0.14-1 -no deps k z
    wpebackend-fdo 1.8.3-1 k zz
    -requires
 libwpe 1.14.1-1 -no deps k z
    xdg-dbus-proxy 0.1.2-1 -no deps k z
    unifdef 2.12-1 -no deps k z
 ngspice-40-1 k zz
 -requires
  openmpi 4.1.4-1 -no deps  (optional deps not used (slurm)) k z
 OpenCASCADE 7.7.0-2 k zzz
 FFMPEG=yes
 FREEIMAGE=yes
 TBB=yes
 GL2PS=yes
 -requires
  VTK 9.2.6-1 k zz (uninstall previous version before creating package)
  IMAGING=yes
  MPI=yes
  -requires
   openmpi k z
  FreeImage 3.18.0-1 -no deps k z
  tbb 2020u2-1 -no deps k z
  gl2ps 1.3.7-1 -no deps k z
 glm 0.9.9.5-1 -no deps k z

any ideas?
regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] VTK

[Tim Dickson via SlackBuilds-users]

On 15/04/2023 02:46, Christoph Willing wrote:

On 15/4/23 04:26, Tim Dickson via SlackBuilds-users wrote:

hi all, I'm getting the following error building VTK

[ 99%] Linking CXX shared module 
../../../lib64/qml/VTK.9.2/libqmlvtkplugin.so

Generating qmltypes file using qmlplugindump
QQmlComponent: Component is not ready
make[2]: *** 
[GUISupport/QtQuick/qml/CMakeFiles/qmlvtkplugin.dir/build.make:151: 
lib64/qml/VTK.9.2/libqmlvtkplugin.so] Error 3

make[2]: *** Deleting file 'lib64/qml/VTK.9.2/libqmlvtkplugin.so'
make[1]: *** [CMakeFiles/Makefile2:18427: 
GUISupport/QtQuick/qml/CMakeFiles/qmlvtkplugin.dir/all] Error 2

make: *** [Makefile:136: all] Error 2

I have IMAGING=yes and MPI=yes flags set. (and openmpi installed)

Any ideas?
regards, Tim


Interestingly, this exact problem has been raised recently on LQ in 
the "SBo scripts not building on current" thread. Therefore first 
question regards whether you're seeing this problem in 
Slackware-stable or -current?


Unfortunately I have tried all combinations (I think) of build flags 
in clean -stable & -current VMs and have not been able to replicate 
the problem. I just built it again now without incident in -stable 
using IMAGING=yes and MPI=yes flags. Therefore the next question is 
whether you're building in a VM or normal environment. If the latter, 
how clean is it?



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/


I'm running on stable (15.0 64bit)

Thanks for looking at this Chris. I have managed to get VTK to build now.
My solution was to uninstall the existing (older) version of VTK before 
creating the newer package. If someone wants to confirm this as a 
repeatable solution then it may be worth adding a comment to that effect 
to the readme.

regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] VTK

[Tim Dickson via SlackBuilds-users]

hi all, I'm getting the following error building VTK

[ 99%] Linking CXX shared module 
../../../lib64/qml/VTK.9.2/libqmlvtkplugin.so

Generating qmltypes file using qmlplugindump
QQmlComponent: Component is not ready
make[2]: *** 
[GUISupport/QtQuick/qml/CMakeFiles/qmlvtkplugin.dir/build.make:151: 
lib64/qml/VTK.9.2/libqmlvtkplugin.so] Error 3

make[2]: *** Deleting file 'lib64/qml/VTK.9.2/libqmlvtkplugin.so'
make[1]: *** [CMakeFiles/Makefile2:18427: 
GUISupport/QtQuick/qml/CMakeFiles/qmlvtkplugin.dir/all] Error 2

make: *** [Makefile:136: all] Error 2

I have IMAGING=yes and MPI=yes flags set. (and openmpi installed)

Any ideas?
regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] OpenSubdiv linking issue

[Tim Dickson via SlackBuilds-users]

thanks for the pointer. unfortunately applying that patch doesn't fix 
the problem.
I assume Chris got it working when he updated it, as both it and blender 
are his.


On 14/04/2023 16:31, marav wrote:

Le 14/04/2023 à 17:14, Tim Dickson via SlackBuilds-users a écrit :
hi all, I'm attempting to build OpenSubdiv with optional deps tbb and 
glfw3 and am getting a linking error


[ 33%] Linking CXX executable ../../bin/glViewer
/usr/bin/ld: 
../common/CMakeFiles/examples_common_gl_obj.dir/clDeviceContext.cpp.o: 
in function `CLDeviceContext::Initialize()':
clDeviceContext.cpp:(.text+0x1b3): undefined reference to 
`glXGetCurrentContext'
/usr/bin/ld: clDeviceContext.cpp:(.text+0x1bd): undefined reference 
to `glXGetCurrentDisplay'

collect2: error: ld returned 1 exit status
make[2]: *** 
[examples/glViewer/CMakeFiles/glViewer.dir/build.make:149: 
bin/glViewer] Error 1
make[1]: *** [CMakeFiles/Makefile2:4055: 
examples/glViewer/CMakeFiles/glViewer.dir/all] Error 2

make: *** [Makefile:146: all] Error 2

any ideas?
thanks, Tim
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


Hi,

Maybe this one

https://github.com/PixarAnimationStudios/OpenSubdiv/commit/9079a517.patch


___
SlackBuilds-users mailing list
SlackBuilds-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] OpenSubdiv linking issue

[Tim Dickson via SlackBuilds-users]

hi all, I'm attempting to build OpenSubdiv with optional deps tbb and 
glfw3 and am getting a linking error


[ 33%] Linking CXX executable ../../bin/glViewer
/usr/bin/ld: 
../common/CMakeFiles/examples_common_gl_obj.dir/clDeviceContext.cpp.o: 
in function `CLDeviceContext::Initialize()':
clDeviceContext.cpp:(.text+0x1b3): undefined reference to 
`glXGetCurrentContext'
/usr/bin/ld: clDeviceContext.cpp:(.text+0x1bd): undefined reference to 
`glXGetCurrentDisplay'

collect2: error: ld returned 1 exit status
make[2]: *** [examples/glViewer/CMakeFiles/glViewer.dir/build.make:149: 
bin/glViewer] Error 1
make[1]: *** [CMakeFiles/Makefile2:4055: 
examples/glViewer/CMakeFiles/glViewer.dir/all] Error 2

make: *** [Makefile:146: all] Error 2

any ideas?
thanks, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] audacity fails to build after wxWidgets upgrade

[Tim Dickson via SlackBuilds-users]

it built for me.
I did rebuild libs whos' direct deps had been updated. ie for each 
updated package, I saw what package used it as a first level dep, and 
rebuilt it as well.


On the first time only, running it, I got a "incompatible plugin(s) 
found" message, listing

http://breakfastquay.com/rdf/lv2-rubberband#r3mono
http://breakfastquay.com/rdf/lv2-rubberband#r3stereo
http://lv2plug.in/plugins/eg-sampler
but apart from that it seems to work ok.
regards, Tim

On 13/02/2023 19:21, B. Watson wrote:



On Mon, 13 Feb 2023, Erich Ritz via SlackBuilds-users wrote:

# diff wxWidgets-3.2.1/usr/lib64/wx/config/gtk3-unicode-3.2 
wxWidgets-3.2.2/usr/lib64/wx/config/gtk3-unicode-3.2

407c407
< wxconfdir="${exec_prefix}/lib64/wx/config"
---

wxconfdir="${exec_prefix}/lib/wx/config"

943c943
< libdir="${exec_prefix}/lib64"
---

libdir="${exec_prefix}/lib"

950,951c950,951
< [ -z "$output_option_version"   ] || echo "3.2.1"
< [ -z "$output_option_version_full"  ] || echo "3.2.1.0"
---

[ -z "$output_option_version"   ] || echo "3.2.2"
[ -z "$output_option_version_full"  ] || echo "3.2.2.0"


The new /usr/lib64/wx/config/gtk3-unicode-3.2 file appears to be 
wrong in my build.  Does the SlackBuild need additional sed magic, or 
did I mess up something during my build?


I get the same result here. gtk3-unicode-3.2 has lib, not lib64.
___
SlackBuilds-users mailing list
SlackBuilds-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] vlc build issue

[Tim Dickson via SlackBuilds-users]

On 10/02/2023 20:41, B. Watson wrote:
 > > On Fri, 10 Feb 2023, Tim Dickson via SlackBuilds-users wrote: > >> 
I'm having vlc fail to build since the last update (3.0.17.3-3 to >> 
3.0.17.3-4) all deps are installed, including dav1d it may relate >> to 
a recent update of libplacebo which isn't listed as a dep for >> vlc. 
(installed as a dep of mpv) last few lines of build log >> are... > > 
Try editing the SlackBuild, add --disable-libplacebo to the > 
./configure args. > > Not sure who's going to take over vlc... are you 
interested, since > you use it? that seems to do the trick, thanks.
re taking over vlc. I have a suspicion that i wouldn't be better than 
Benjamin who had it before. it is rather large and I don't have any of 
the dedicated 3d hardware (the nvidia and amd toolkits are huge) to test.
I do use it , so if no-one steps up, I can give it a go, but I would 
give other people a chance to take it first, and I wouldn't be testing 
the afore-mentioned hardware acceleration options.

regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] vlc build issue

[Tim Dickson via SlackBuilds-users]

I'm having vlc fail to build since the last update (3.0.17.3-3 to 
3.0.17.3-4)

all deps are installed, including dav1d
it may relate to a recent update of libplacebo which isn't listed as a 
dep for vlc. (installed as a dep of mpv)

last few lines of build log are...

In file included from /usr/include/libplacebo/shaders/colorspace.h:26,
 from video_output/opengl/vout_helper.h:35,
 from video_output/opengl/vout_helper.c:44:
/usr/include/libplacebo/shaders.h:74:34: note: expected âpl_logâ {aka 
âconst struct pl_log_t *â} but argument is of type âstruct pl_context *â
   74 | pl_shader pl_shader_alloc(pl_log log, const struct 
pl_shader_params *params);

  |   ~~~^~~
video_output/opengl/vout_helper.c:632:23: warning: assignment to âstruct 
pl_shader *â from incompatible pointer type âpl_shaderâ {aka âstruct 
pl_shader_t *â} [-Wincompatible-pointer-types]
  632 | tc->pl_sh = pl_shader_alloc(tc->pl_ctx, &(struct 
pl_shader_params) {

  |   ^
cc1: some warnings being treated as errors
make[4]: *** [Makefile:22431: 
video_output/opengl/libgl_plugin_la-vout_helper.lo] Error 1

make[4]: Leaving directory '/tmp/SBo/vlc-3.0.17.3/modules'
make[3]: *** [Makefile:28239: all-recursive] Error 1
make[3]: Leaving directory '/tmp/SBo/vlc-3.0.17.3/modules'
make[2]: *** [Makefile:12874: all] Error 2
make[2]: Leaving directory '/tmp/SBo/vlc-3.0.17.3/modules'
make[1]: *** [Makefile:1561: all-recursive] Error 1
make[1]: Leaving directory '/tmp/SBo/vlc-3.0.17.3'
make: *** [Makefile:1448: all] Error 2

has anyone had the same problem.?
I'm reporting it here as the existing maintainer reported he was 
stepping down.

regards. Tim

On 07/02/2023 21:57, B. Watson wrote:



On Tue, 7 Feb 2023, Matteo Bernardini wrote:

ok, you convinced me: if noone else wants them badly I'll take 
portaudio, libshout and libdca!


Sounds great to me.

live555 and zvbi can go to whoever ends up taking over vlc. Hopefully
someone who actually uses vlc will step up...
___
SlackBuilds-users mailing list
SlackBuilds-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 build error

[Tim Dickson via SlackBuilds-users]

I've found a work-around.
1. uninstall wxWidgets if installed
2. reinstall wxGTK3
3. reinstall wxPython3
4. run the kicad slackbuild
it looks like there is a compiling issue when the stand-alone wxWidgets 
package is a different version than the ones included/used by wxGTK3 and 
wxPython3

5. reinstall wxWidgets if it was installed

I'm not sure what the longer term solution is though. :-)
regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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 build error

[Tim Dickson via SlackBuilds-users]

Hi all, I'm getting the following error when trying to build kicad

/usr/lib64/python2.7/site-packages/wx-3.0-gtk3/wx/_core.py:16629: 
UserWarning: wxPython/wxWidgets release number mismatch

  warnings.warn("wxPython/wxWidgets release number mismatch")
-- Found wxPython 3.0.2.0/gtk3 (wxWidgets 3.0.2.0)
-- Found wxWidgets: 
-L/usr/lib64;-pthread;-lwx_gtk3u_gl-3.2;-lwx_gtk3u_aui-3.2;-lwx_gtk3u_html-3.2;-lwx_gtk3u_core-3.2;-lwx_baseu_net-3.2;-lwx_baseu-3.2;-lwx_baseu_xml-3.2;-lwx_gtk3u_stc-3.2 
(found suitable version "3.2.1", minimum required is "3.0.2.0")

CMake Error at CMakeLists.txt:795 (message):
  Cannot find wxPython.h


-- Configuring incomplete, errors occurred!
See also "/tmp/SBo/kicad-5.1.9/build/CMakeFiles/CMakeOutput.log".

a quick find / -iname wxPython.h comes up with
/usr/include/wx-3.0/wx/wxPython/wxPython.h
/usr/include/wx-2.8/wx/wxPython/wxPython.h

any ideas on how to fix.?

I have the latest wxwidgets installed (used by audacity), and also 
wxPython (used by youtube-dl-gui) and wxPython3 (used by kicad)


regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] issues with some deps.

[Tim Dickson via SlackBuilds-users]

On 12/12/2022 07:04, fourtysixandtwo wrote:

Hi Tim,

Having a closer look and double checking the deps, you were correct 
about python3-hatchling.  However, I can't agree on the other changes 
you suggest.  I've noted the following discrepancies:


-python3-hatch_fancy_pypi_readme and python3-hatch_vcsare build time 
deps only and neither depend on each other.
-several of the versions you list are outdated (primarily 
python3-jsonschema 3.17.3-1)

-python3-pyrsistent does not have a dep for BeautifulSoup4

Here's the output from pipdeptree (does not show build deps) on my 
build vm:


jsonschema==4.17.3
 - attrs [required: >=17.4.0, installed: 21.4.0]
 - pyrsistent [required: >=0.14.0,!=0.17.2,!=0.17.1,!=0.17.0, 
installed: 0.19.2]


hatch-fancy-pypi-readme==22.8.0
 - hatchling [required: Any, installed: 1.11.1]
   - editables [required: >=0.3, installed: 0.3]
   - packaging [required: >=21.3, installed: 21.3]
     - pyparsing [required: >=2.0.2,!=3.0.5, installed: 2.4.7]
   - pathspec [required: >=0.10.1, installed: 0.10.3]
   - pluggy [required: >=1.0.0, installed: 1.0.0]
   - tomli [required: >=1.2.2, installed: 1.2.2]
 - tomli [required: Any, installed: 1.2.2]

hatch-vcs==0.3.0
 - hatchling [required: >=1.1.0, installed: 1.11.1]
   - editables [required: >=0.3, installed: 0.3]
   - packaging [required: >=21.3, installed: 21.3]
     - pyparsing [required: >=2.0.2,!=3.0.5, installed: 2.4.7]
   - pathspec [required: >=0.10.1, installed: 0.10.3]
   - pluggy [required: >=1.0.0, installed: 1.0.0]
   - tomli [required: >=1.2.2, installed: 1.2.2]
 - setuptools-scm [required: >=6.3.2, installed: 6.3.2]
   - packaging [required: >=20.0, installed: 21.3]
     - pyparsing [required: >=2.0.2,!=3.0.5, installed: 2.4.7]
   - setuptools [required: Any, installed: 57.5.0]
   - tomli [required: >=1.0.0, installed: 1.2.2]

Hope that clears things up and I'll get python3-hatchling updated.

Cheers

On Sun, Dec 11, 2022 at 7:32 AM Tim Dickson via SlackBuilds-users 
 wrote:


python3-jsonschema lists a couple of new deps
python3-hatch-fancy_pypi_readme and python3_hatch_vcs but as
python3_hatch_vcs is a dep of python3-hatch-fancy_pypi_readme it
shouldn't be listed (no deps of deps)
in the same vein, python3-hatchling lists python3-build and
python3-installer among it's deps list, both of which are already
deps
of python3-edittables and python3-pathspec, which are also deps of
python3-hatchling.

the dep tree is
python3-jsonschema 3.17.3-1
  -requires
   python3-importlib_metadata
   python3-attrs 21.4.0-1
   python3-pyrsistent 0.19.2-1
   python3-hatch_fancy_pypi_readme
   -requires
    python3-hatch_vcs 0.2.0-1
    -requires
 python3-hatchling 1.11.1-1
 -requires
  python3-editables 0.3-1
  -requires
   python3-build
   python3-installer
   wheel
  python3-pathspec 0.10.2-1
  -requires
   python3-build
   python3-installer
   wheel
  python3-pluggy 1.0.0-1
   BeautifulSoup4
   -requires
    python3-soupsieve 2.3.1-2

to summerise,

so python3-jsonschema deps should be

python3-importlib_metadata
python3-attrs
python3-pyrsistent
  python3-hatch_fancy_pypi_readme
  BeautifulSoup4

and python3-hatchling_vcs deps should be

python3-hatchling

and  python3-hatchling deps should be

python3-editables
python3-pathspec
python3-pluggy


regards, Tim

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


hi fourtysixandtwo , and thank for looking at it.
Sorry, I made a couple of mistakes. (the python3-hatch_fancy_pypi_readme 
one, and the BeautifulSoup dep I just had indented wrong - it is a dep 
of anki, which is what uses all the other stuff :-)  )

regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] issues with some deps.

[Tim Dickson via SlackBuilds-users]

python3-jsonschema lists a couple of new deps 
python3-hatch-fancy_pypi_readme and python3_hatch_vcs but as 
python3_hatch_vcs is a dep of python3-hatch-fancy_pypi_readme it 
shouldn't be listed (no deps of deps)
in the same vein, python3-hatchling lists python3-build and 
python3-installer among it's deps list, both of which are already deps 
of python3-edittables and python3-pathspec, which are also deps of 
python3-hatchling.


the dep tree is
python3-jsonschema 3.17.3-1
 -requires
  python3-importlib_metadata
  python3-attrs 21.4.0-1
  python3-pyrsistent 0.19.2-1
  python3-hatch_fancy_pypi_readme
  -requires
   python3-hatch_vcs 0.2.0-1
   -requires
    python3-hatchling 1.11.1-1
    -requires
 python3-editables 0.3-1
 -requires
  python3-build
  python3-installer
  wheel
 python3-pathspec 0.10.2-1
 -requires
  python3-build
  python3-installer
  wheel
 python3-pluggy 1.0.0-1
  BeautifulSoup4
  -requires
   python3-soupsieve 2.3.1-2

to summerise,

so python3-jsonschema deps should be

python3-importlib_metadata
python3-attrs
python3-pyrsistent
 python3-hatch_fancy_pypi_readme
 BeautifulSoup4

and python3-hatchling_vcs deps should be

python3-hatchling

and  python3-hatchling deps should be

python3-editables
python3-pathspec
python3-pluggy


regards, Tim

___
SlackBuilds-users mailing list
SlackBuilds-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] gusersoundfont slackbuild

[Tim Dickson via SlackBuilds-users]

All the script does is unzip the file, rename to remove spaces in the 
sf2 file name, and move them to the correct location.

if the mdsum checks out (it did on a test I just did), then it works.

As a general rule, slackbuild scripts do not check that your source is 
correct (ie. not corrupt or incomplete or the right name)
if you are using sbopkg or another tool, it will tell you if your 
download is not as expected (mismatched md5sums), and warn you suitably.


regards, Tim

On 18/10/2022 20:00, Jude DaShiell wrote:

zip file on dropbox account failed to download or install, the script
didn't give enough detail to know the cause of the failure.



Jude  "There are four boxes to be used in
defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)

.

On Tue, 18 Oct 2022, Jude DaShiell wrote:


Needs an md5sum checksum update.



Jude  "There are four boxes to be used in
defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)

.
___
SlackBuilds-users mailing list
SlackBuilds-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] Sourceforge Slackbuildsdirectlinks access changed ?

[Tim Dickson via SlackBuilds-users]

i have the same problem with epson-printer stuff. :-(

On 04/10/2022 19:51, Arnaud via SlackBuilds-users wrote:

Hi!

It seems I can't upload files to the slackbuildsirectlinks account on
Sourceforge.
Did something change here ?
I may have missed some information...
I was connecting through sftp and uploading into :
  /home/frs/project/slackbuildsdirectlinks/dosbox/
But now that directory doesn't exist anymore, even /home/frs/project/ seems
unavailable...



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

[Tim Dickson via SlackBuilds-users]

hi, I'm having permissions issues trying to upload a new source archive 
to slackbuildsdirectlinks (using filezilla)

(epson-inkjet-pirnter-escpr2)
I didn't have any problems last time. has anything changed?
thanks.

--
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] gsm slackbuild

[Tim Dickson via SlackBuilds-users]

The source url for gsm is dead and the homepage in the slack-desk is 
dead as well.

The current "live" location only has the newer 1.0.19 version.
I thought I would post it here so the maintainer (david somero ) might 
see it.

I have an updated build for the 1.0.19 version if it is wanted)
regards, Tim

--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] KiCad not loading symbols

[Tim Dickson via SlackBuilds-users]

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/




--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] Modifying config.mk's CFLAGS variable

[Tim Dickson via SlackBuilds-users]

for longer term solution submit a patch upstream. you might want to 
check the optimization flag because some applications don't run 
well/have runtime issues with some flags. In those cases you don't want 
to override them. (I have at least one package with that issue.)

Regards Tim

On 23/04/2022 05:53, Brandon Pribula wrote:

Hi,

I have a situation with an application I'm packaging. The CFLAGS 
variable, et al in config.mk  can't be prepended.


CFLAGS = -std=c99 ...

instead of

CFLAGS += -std=c99 ...

so as is I can't prepend $SLKFLAGS to $CFLAGS. It also contains an 
optimization flag: -Os which conflicts with Slackware's.


The solution I came up with is to change '=' to '+='

sed -i '/CFLAGS/s/=/+=/' config.mk 

and remove the optimization flag -Os

sed -i '/CFLAGS/s/-Os//' config.mk 

This works fine but I would like to know if there is a more preferable 
solution with a slackbuild.


Thanks

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




--
This email has been checked for viruses by AVG.
https://www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qemu build issue

[Tim Dickson via SlackBuilds-users]

point noted, and thanks. qemu was my first slackbuild to be built for 
15.0 to get my dev vm's up to date so I can get on with the rest, 
including the ones i look after.

regards, Tim

On 21/03/2022 13:05, Dave Woodfall wrote:

On 21/03/22 13:54,
Matteo Bernardini  put forth the proposition:

well, to be fair that shouldn't actually be a problem in a Slackware stable
setup because libraries' versions should be the same...
that should only happens when you are using current or upgrading between
Slackware versions (but in that case many other things could happen).
Matteo

I've just put a small note at the bottom of the README, that if there
are any problems with missing or wrong versioned libraries to try
uninstalling older versions first.

Dave


Il giorno lun 21 mar 2022 alle ore 13:48 Tim Dickson via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> ha scritto:

thanks Matteo, that did the trick. It looks like part of the build process
uses already created binaries to process files, and when older binaries are
already in the path they are used instead, giving the error.

It may be worth adding a comment to remove existing version of qemu before
installing a newer one into the README.

regards, Tim

On 20/03/2022 18:31, Matteo Bernardini wrote:

have you tried removing the already installed qemu package first?

Il giorno dom 20 mar 2022 alle ore 19:29 Tim Dickson via SlackBuilds-users
 ha scritto:


I am getting the following error when attempting to create qemu package.

/usr/bin/qemu-keymap: error while loading shared libraries:
libjemalloc.so.1: cannot open shared object file: No such file or
directory

/usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there
is a libjemalloc installed (part of slackware 15.0).
It seems that the build script is looking for the wrong version of the
lib. Ideally it would try libjemalloc.so and thus pick up whichever
version was installed.
Is there a quick fix. (if it involves a sim-link would that have to be
done on target computers as well?)
regards, Tim




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




--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] qemu build issue

[Tim Dickson via SlackBuilds-users]

thanks Matteo, that did the trick. It looks like part of the build 
process uses already created binaries to process files, and when older 
binaries are already in the path they are used instead, giving the error.


It may be worth adding a comment to remove existing version of qemu 
before installing a newer one into the README.


regards, Tim

On 20/03/2022 18:31, Matteo Bernardini wrote:

have you tried removing the already installed qemu package first?

Il giorno dom 20 mar 2022 alle ore 19:29 Tim Dickson via 
SlackBuilds-users  ha scritto:


I am getting the following error when attempting to create qemu
package.

/usr/bin/qemu-keymap: error while loading shared libraries:
libjemalloc.so.1: cannot open shared object file: No such file or
directory

/usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so
there
is a libjemalloc installed (part of slackware 15.0).
It seems that the build script is looking for the wrong version of
the
lib. Ideally it would try libjemalloc.so and thus pick up whichever
version was installed.
Is there a quick fix. (if it involves a sim-link would that have
to be
done on target computers as well?)
regards, Tim


-- 
This email has been checked for viruses by AVG.

https://www.avg.com

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


___
SlackBuilds-users mailing list
SlackBuilds-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] qemu build issue

[Tim Dickson via SlackBuilds-users]

I am getting the following error when attempting to create qemu package.

/usr/bin/qemu-keymap: error while loading shared libraries: 
libjemalloc.so.1: cannot open shared object file: No such file or directory


/usr/lib64/libjemalloc.so links to usr/lib64/libjemalloc.so.2 so there 
is a libjemalloc installed (part of slackware 15.0).
It seems that the build script is looking for the wrong version of the 
lib. Ideally it would try libjemalloc.so and thus pick up whichever 
version was installed.
Is there a quick fix. (if it involves a sim-link would that have to be 
done on target computers as well?)

regards, Tim


--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] epson-printer-utility slackbuild for 15.0

[Tim Dickson via SlackBuilds-users]

thanks B Watson. I'll see if I can test it out with a real printer. 
What's the best way to get qt4 and it's deps, or can I just wait till 
submissions are open and then use sbopkg ?
If the package went out as is I could test it when sbopkg works with 
15.0 :-)


Regards, Tim

On 09/03/2022 17:09, B Watson wrote:

On 3/8/22, Tim Dickson via SlackBuilds-users
 wrote:

Hi Willy, this can be scrapped for now, rather than holding up
re-opening submissions.
It might work vaguely with qt4 installed, but in reality it is waiting
for epson to update their code to something that works.

I managed to get the thing to compile on 15.0, and was able to at
least start the daemon and the GUI, which told me it couldnt't find
the printer (since I don't have an epson printer, that was correct).

https://git.slackbuilds.org/slackbuilds/commit/?id=2a42a0916ad7d3b7f2cef7eacadefc0d96f0c2fb
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/




--
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] epson-printer-utility slackbuild for 15.0

[Tim Dickson via SlackBuilds-users]

Hi Willy, this can be scrapped for now, rather than holding up 
re-opening submissions.
It might work vaguely with qt4 installed, but in reality it is waiting 
for epson to update their code to something that works.


Regards, Tim

--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] Epson M105 printer with PPD on CUPS (it was Re: Howto for slackware tgz)

[Tim Dickson via SlackBuilds-users]

the two printer packages at sbo are epson-inkjet-printer-escpr and 
epson-inkjet-printer-escpr2

and cater for printers that use the different protocol versions.
the m100 series was last supported in 2012, so it must be a really old 
model.

It is not listed in either of the current driver packages available.

you'll need to create a package based on 
epson-inkjet-printer-201215w-1.0.0-1lsb3.2.src.rpm from epson.

you can use rpm2tgz to convert the source package to something more useful.

If you look at either of the two epson printer packages available, it 
will give some pointers to getting epson source code to compile. If you 
are successful, you should end up with the ppd files and the back-end as 
well. Be prepared for an uphill task.

regards, Tim


On 01/02/2022 02:01, Beco via SlackBuilds-users wrote:

Dear Donald Laster, Jeremy, Chris and Kris,


Sorry for the late reply, I was unable to test all the options you
gave, due to some health problems. I'm back trying to install the
printer.

To recap:

I have a epson M105 via wifi that I use with other multiple devices,
android, linux, etc. (all working.) Now I'm trying to add Slackware to
the pool.


--

On Sat, 15 Jan 2022 , Donald R Laster Jr  wrote:

Bèco,

   Regardless of how you have the printer attached, network or direct,
you should be able to use CUPS to setup the printer if CUPS supports the 
printer.
The first thing to do is to insure that you have CUPS running.  Make sure
that /etc/rc.d/rc.cups is executable and you have started the CUPS daemon.

[...cut...]

   Sincerely,
   Donald R Laster Jr

--

On Wed, 12 Jan 2022 at 23:38, Christoph Willing  wrote:

On 13/1/22 11:39, Beco via SlackBuilds-users wrote:

Hi Jeremy, hi Chris,

Thanks for the tips, guys.

I'll take a look at every link.

Currently I'm having trouble with my printer, Epson M105, and I'm
trying to adapt source code from drivers I've found in "src.rpm" to
slackware package format.


Have a look at:
 https://slackbuilds.org/repository/14.2/system/epson-printer-utility/

whose README.models claims to support the M105 Series (and is based on
a src.rpm too).


chris

--



The Slackware experience for this specific printer is not the best.
I'm trying to configure a new server using Slackware and it is a first
attempt after a lifetime away from this distro that I love. (It was my
first distro in 1998/1999). So, lets give it a try.

I tried to install the "14.2 > System > epson-printer-utility (1.1.1)
" (I'm on Slackware Current), and it didn't compile. After some
tweeks, I got it to compile with errors but didn't work.

Anyway: I was not that much upset, since this is not the path I would
prefer to take. I don't need the utility, the monitor, ink levels,
nozzles checks, etc. I can skip all that.

In all my other linuxes, it is enough a PPD file that I have, and
CUPS. And that is it. so, i tried the other path I am more familiar,
just to install the printer with PPD.

CUPS detected it with a lpd://localhost:port and also I can connect
with socket://localhost:port. So, these 2 options can "see" the
printer and send "test pages", but all end up as garbage.

The PPD file I have that I used in many systems, passing from one to
another and it always worked, don't work anymore. I noticed that it
gives this error:


Idle - "File 
"/opt/epson-inkjet-printer-201215w/cups/lib/filter/epson_inkjet_printer_filter"
not available: No such file or directory"


I have tried to compile this filter from many sources, RPM, Debian,
Slackbuilds, but I can't find a way to make this filter work.

For now, my hope is that the maintainer of the Slackbuilds packages
that may offer this would make it updated for slackware-current.



Donald, I completely agree with you. Regardless how the printer is
connected, if CUPS is working, and I have the PPD, the printer should
work fine. I guess this PPD I have is not well suited to the PATH of
slackware filters. Maybe a small adjustment, or to find if the printer
can work with another filter that comes with CUPS , that could work.


Thanks for now, I'll keep trying and keep you guys posted.

Cordially,
Bèco









--
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] rEFInd not building

[Tim Dickson via SlackBuilds-users]

rEFInd fails to build on 14.2 with all updates. (for me)
it gets stuck trying to create install.o
in file included from /usr/include/efi/efi.h:35:0,
    from gloabl.h:49,
    from install.c:13:
install.c: In function 'RenameFile':
install.c:176:43: error: 'gEfiFileInfoGuid' undeclared (first use in 
this function)

    ,
 ^

there's more error stuff. if it helps.
Has anyone else tried it recently and had success?.
(refind (the repackaged binary) is ok. )

regards, Tim

--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] separating source archives and SlackBuilds

[Tim Dickson via SlackBuilds-users]

Unfortunately it doesn't quite work. A number of the source files have 
the same name, even though they are different. Especially for 
multi-versions available, such as various versions of jdk.
On the other hand, if you use sbopkg for creating packages, it already 
has a default location for source, /var/cache/sbopkg/  and that is 
checked first before the source url's, to save re-downloading the same 
files. You might want to try it, as it sounds like the behaviour you are 
looking for. It still suffers from the issue mentioned, but as it checks 
md5sums, it offers to download the correct source, which is useful.

regards, Tim

On 22/05/2021 21:19, Thomas Morper wrote:

Hello there!

There's a certain feature in FreeBSD ports that I think I'd like to have
in SlackBuilds, too, and I want to know what you think about it:

FreeBSD ports keep all source archives in the /usr/ports/distfiles folder
while SlackBuilds expect the source archive in the same folder as the
SlackBuld itself.

With a simple "DISTFILES=${DISTFILES:-$CWD}" and "tar xvf $DISTFILES/..."
rather than "tar xvf $CWD/..." in the template we could have both ways.

The reason for keeping it the way it is: simplicity.

The reason for having a separate distfiles folder: you can keep as many
source archive versions around as you want without affecting the way you
work with the SlackBuilds directory tree, e.g. always using a pristine and
possibly read-only copy, or going all-in on git without ever accidentally
adding and comitting the LibreOffice tar ball.

Would this be desirable and feasible?

Cheers!




--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] files to users /home

[Tim Dickson via SlackBuilds-users]

if the file is program data which is only read, newver written, then 
linking to a common location e. /usr/share/appname/datafile is the most 
efficient, especially for large datafiles (think warzone2100 for example).
 I haven't seen any good way of handling this in a slackbuild, because 
you may have many existing users, and what about users added later?. 
editing the default user template to add link creation and going through 
existing users to add links is not ideal. if you remove the package, the 
links will remain.


It is better if possible to get upstream to fix their code so that 
common user data is stored in a common place. local user data should be 
created as required by the software.

regards,
Tim

On 21/04/2021 03:06, slackbui...@ninefamily.com wrote:
If an application needs to use a file in the user's /home what is the 
correct way to do so in a Slackbuild?  Do I put it in a central place 
and link to it or just instruct the user to manually put the file or a 
script for it?


Thanks

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




--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] openimageio with pybind11 issues

[Tim Dickson via SlackBuilds-users]

On 24/03/2021 11:42, Christoph Willing wrote:

On 24/3/21 6:55 pm, Tim Dickson via SlackBuilds-users wrote:


On 24/03/2021 07:48, Christoph Willing wrote:

On 23/3/21 5:44 pm, Tim Dickson via SlackBuilds-users wrote:

has anyone had success building openimageio with the new pybind11  ? it
is failing for me. it seems to be looking for pybind11 files in
/usr/include/python2.7/pybind11  when the pybind11 package has the files
in /usr/include/pybind11


I've held pybind11 at version at 2.5.0 - the latest that enables
building of openimageio - however not for want of finding include files.
With latest pybind11-2.6.2 configuration output says:
  -- pybind11 2.6.2, include dir: /usr/include

i.e. include files are found OK.

The error I see is after 92% has compiled:
  /var/tmp/SBo/oiio-Release-2.0.13/src/python/py_oiio.h:303:47: error:
no matching function for call to 'cast(OpenImageIO_v2_0::span::element_type&)'

I'm assuming this is due to new definitions in pybind11 which newer
versions of openimageio will deal with. However newer versions of
openimageio don't build in 14.2 so we're stuck with openimageio-2.0.13
and (therefore) pybind11-2.5.0.

chris


hmm. i'm using pybind11 2.5.0 all on slackware 14.2 (64bit) the errors i
get with openimageio are

-- robin-map include dir: /usr/include
CMake Error at src/cmake/externalpackages.cmake:568 (file):
   file STRINGS file "/usr/include/python2.7/pybind11/common.h" cannot be
   read.
Call Stack (most recent call first):
   CMakeLists.txt:206 (find_or_download_pybind11)

CMake Error at src/cmake/externalpackages.cmake:570 (file):
   file STRINGS file "/usr/include/python2.7/pybind11/common.h" cannot be
   read.
Call Stack (most recent call first):
   CMakeLists.txt:206 (find_or_download_pybind11)

CMake Error at src/cmake/externalpackages.cmake:572 (file):
   file STRINGS file "/usr/include/python2.7/pybind11/common.h" cannot be
   read.
Call Stack (most recent call first):
   CMakeLists.txt:206 (find_or_download_pybind11)

-- pybind11 366.366.366, include dir: /usr/include/python2.7
CMake Error at
/usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148
(message):
   Could NOT find PythonInterp: Found unsuitable version "2.7.17", but
   required is at least "3.7.2" (found /usr/bin/python2.7)
Call Stack (most recent call first):
/usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:386
(_FPHSA_FAILURE_MESSAGE)
   /usr/share/cmake-3.5/Modules/FindPythonInterp.cmake:163
(FIND_PACKAGE_HANDLE_STANDARD_ARGS)
   src/python/CMakeLists.txt:4 (find_package)

-- Configuring incomplete, errors occurred!
See also "/tmp/SBo/oiio-Release-2.0.13/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/SBo/oiio-Release-2.0.13/build/CMakeFiles/CMakeError.log".

looking at the CMakeEerror.log the complaint is that pthread_create does
not exist.

I don't think that's a problem - I see the same pthread problem  in
CMakeError.log of a successful build.

How old is your pybind11 build? In February I updated the SLackBuilkd
for pybind11, the main change being to use CMake instead of Python as
the build instrument; also to use python3 exclusively instead of
python2. I suggest you rebuild/install this latest pybind11, then try
openimageio again.

chris
___

I did have the latest pybind11 installed (I reinstalled it again, just 
in case). But your info about the change got me thinking, and i've got 
it going now. (after running rm -r /tmp/SBo/*  ). It looks like previous 
build artefacts in openimageio messed up the build attempt. thanks for 
the pointer.


From looking at the openimageio.Slackbuild, it tries to remove the 
wrong temporary directory before extracting the files, thus leaving 
stale stuff from previous package creation. Because the PRGNAM is 
"openimageio" but the extracted source is in "oiio-Release" the script 
never cleans up (removes) any previous contents of oiio-Release

A fix for this in the slackbuild is to replace
rm -rf PRGNAM-$VERSION

with

rm -rf $SRCNAM-$VERSION

Regards, Tim (and thanks for the slackbuild :-)   )

--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] openimageio with pybind11 issues

[Tim Dickson via SlackBuilds-users]

On 24/03/2021 07:48, Christoph Willing wrote:

On 23/3/21 5:44 pm, Tim Dickson via SlackBuilds-users wrote:

has anyone had success building openimageio with the new pybind11  ? it
is failing for me. it seems to be looking for pybind11 files in
/usr/include/python2.7/pybind11  when the pybind11 package has the files
in /usr/include/pybind11


I've held pybind11 at version at 2.5.0 - the latest that enables
building of openimageio - however not for want of finding include files.
With latest pybind11-2.6.2 configuration output says:
 -- pybind11 2.6.2, include dir: /usr/include

i.e. include files are found OK.

The error I see is after 92% has compiled:
 /var/tmp/SBo/oiio-Release-2.0.13/src/python/py_oiio.h:303:47: error:
no matching function for call to 'cast(OpenImageIO_v2_0::span::element_type&)'

I'm assuming this is due to new definitions in pybind11 which newer
versions of openimageio will deal with. However newer versions of
openimageio don't build in 14.2 so we're stuck with openimageio-2.0.13
and (therefore) pybind11-2.5.0.

chris

hmm. i'm using pybind11 2.5.0 all on slackware 14.2 (64bit) the errors i 
get with openimageio are


-- robin-map include dir: /usr/include
CMake Error at src/cmake/externalpackages.cmake:568 (file):
  file STRINGS file "/usr/include/python2.7/pybind11/common.h" cannot be
  read.
Call Stack (most recent call first):
  CMakeLists.txt:206 (find_or_download_pybind11)

CMake Error at src/cmake/externalpackages.cmake:570 (file):
  file STRINGS file "/usr/include/python2.7/pybind11/common.h" cannot be
  read.
Call Stack (most recent call first):
  CMakeLists.txt:206 (find_or_download_pybind11)

CMake Error at src/cmake/externalpackages.cmake:572 (file):
  file STRINGS file "/usr/include/python2.7/pybind11/common.h" cannot be
  read.
Call Stack (most recent call first):
  CMakeLists.txt:206 (find_or_download_pybind11)

-- pybind11 366.366.366, include dir: /usr/include/python2.7
CMake Error at 
/usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148 
(message):

  Could NOT find PythonInterp: Found unsuitable version "2.7.17", but
  required is at least "3.7.2" (found /usr/bin/python2.7)
Call Stack (most recent call first):
/usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:386 
(_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.5/Modules/FindPythonInterp.cmake:163 
(FIND_PACKAGE_HANDLE_STANDARD_ARGS)

  src/python/CMakeLists.txt:4 (find_package)

-- Configuring incomplete, errors occurred!
See also "/tmp/SBo/oiio-Release-2.0.13/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/SBo/oiio-Release-2.0.13/build/CMakeFiles/CMakeError.log".

looking at the CMakeEerror.log the complaint is that pthread_create does 
not exist.

gcc is 5.5, the latest for 14.2 and in /usr/include/pthread is
extern int pthread_create (pthread_t *__restrict __newthread,
   const pthread_attr_t *__restrict __attr,
   void *(*__start_routine) (void *),
   void *__restrict __arg) __THROWNL __nonnull 
((1, 3));


so there is at least a function declaration.

the only thing in my setup/config I can think of that might be different 
is i'm using ffmpeg4 rather than ffmpeg3

regards, Tim

--
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] openimageio with pybind11 issues

[Tim Dickson via SlackBuilds-users]

has anyone had success building openimageio with the new pybind11  ? it 
is failing for me. it seems to be looking for pybind11 files in
/usr/include/python2.7/pybind11  when the pybind11 package has the files 
in /usr/include/pybind11


regards, Tim

--
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] fop source issue

[Tim Dickson via SlackBuilds-users]

The source for fop seems to be down. or at least fontbox is 404'ing it 
looks like it has been replaced with fontbox-2.0.23.jar
this also applies to pdfbox-2.0.23 also used by fop. changing the 
fop.info file as below, gets everything working.


DOWNLOAD="https://archive.apache.org/dist/xmlgraphics/fop/source/fop-2.6-src.tar.gz 
\

http://mirror.reverse.net/pub/apache/pdfbox/2.0.23/fontbox-2.0.23.jar \
http://mirror.reverse.net/pub/apache/pdfbox/2.0.23/pdfbox-2.0.23.jar \
https://downloads.sourceforge.net/offo/2.2/offo-hyphenation.zip;
MD5SUM="1d6bc84d2ab7f971bbc628080e3c307f \
    f9aa90c666c88ff29e3cd34c15d538ca \
    6b71c42c567d419f068f46f410dcc3a5 \
    bf9c09bf05108ef9661b8f08d91c2336"

regards, Tim

--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] geoclue2: wants optional dependencies [FIXED]

[Tim Dickson via SlackBuilds-users]

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

those on the SBo repo.

no, what it does is rsync your script repo with the public sbo (script) 
repo, so all your sbo local slackbuild scripts will be up to date.
you can then run "updates" to identify scripts which have a different 
version or build number from what is installed. It won't tell you if 
dependencies have changed, you have to check the info and readme's for 
that. There isn't really a short cut, as tools like sqg will give you a 
build queue, but that is only for required deps, not optional ones, 
which wouldn't have helped in your case (geoclue2).
I have been caught out before by not checking the info and readme and 
just building the updated package, and getting problems, but at least 
working from the recent script repo.
Of course, sometimes you have to rebuild stuff even when the version 
hasn't changed, because a dep. has changed significantly.


If you maintain any slackbuilds yourself, I would do their updates out 
of tree, so that you don't wipe out changes you are working on if there 
is a sbo update before you submitted your updated script. Just remember 
to re-copy from the tree before working on the next update, in case an 
sbo admin has patched your script in between times.

regards, Tim


--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] geoclue2: wants optional dependencies [FIXED]

[Tim Dickson via SlackBuilds-users]

see inline comment.

On 18/02/2021 13:40, Rich Shepard wrote:

On Thu, 18 Feb 2021, B Watson wrote:


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


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

here.


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


And now I've learned this.


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


Every week after updates are posted I run sbopkg and update what's
installed. Now I'm installing removed packages which is not automated by
sbopkg.
if you had run "sync" from within sbopkg as you just said, your 
geoclue2.SlackBuild would have been the most up-to-date one, and you 
would have avoided the problem you had, which makes it puzzling. Either 
you used a different repo than the one created by sbopkg (default 
location /var/lib/sbopkg/SBo/14.2/ ), or you didn't run sync from 
sbopkg, or there is a bug somewhere.


Admittedly, deps can change, so if you didn't check them and the readme 
for changes, that is the first port of call. Also, sometimes you have to 
rebuild libs and programs that depend on the updated package, even if 
the version is the same.


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

Not knowing there was a potential problem by having an outdated build 
script

here for the same source version as on the SBo I couldn't avoid it.
see above comment. if you use sync from sbopkg, your sbopkg repo will 
always be as up to date as when you last ran sync.
you may not spot a script that changed noticeably without a build number 
change (fortunately a rare occurrence), but at least you would be 
looking at the current script. As the change was done 2.5yrs ago, I 
would suggest you either haven't been syncing the whole repo from within 
sbopkg, or you are working on an entirely different copy of the repo.


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




--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] [Slackbuilds-user] Teamviewer3 EULA bypass

[Tim Dickson via SlackBuilds-users]

another method that might work is  a simple pipe.

echo -e "y\n"|teamviewerscript

assuming teamviewerscript is the program that asks for eula acceptance. 
(and expects a "y" )


On 21/10/2020 23:34, King Beowulf wrote:

Hello

Teamviewer3 will run the EULA acceptance no matter what - there doesn't
seem to me a command line option to automatically accept.  as a result,
any automated SBo build tools get "stuck."  As my bash-fu is
rudimentary, anyone know a good bashism to allow for automatic acceptance?

Thanks.


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





--
This email has been checked for viruses by AVG.
https://www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] MuseScore slackbuild

[Tim Dickson via SlackBuilds-users]

this is for kla...@member.fsf.org, (I tried emailing directly but was 
getting a 550 unrouteable address when sending from gmail; but as you 
commented recently on the mailing list, you're still there :-)  so 
hopefully this gets to you.)


Any chance of an update for musescore?
current version is 3.5.2
updated MuseScore.info file below.

PRGNAM="MuseScore"
VERSION="3.5.2"
HOMEPAGE="http://www.musescore.org/;
DOWNLOAD="https://github.com/musescore/MuseScore/archive/v3.5.2/MuseScore-3.5.2.tar.gz 
\
http://ftp.osuosl.org/pub/musescore/soundfont/MuseScore_General/MuseScore_General.sf3 
\

http://ftp.osuosl.org/pub/musescore/soundfont/MuseScore_General/MuseScore_General_License.md;
MD5SUM="8e73610dcb4a89616d44decf8687783f \
    7b354559c7ef4e859a2bfad8738d477d \
    bc7b4fbe58b37788876b6c36f19577d0"
DOWNLOAD_x86_64=""
MD5SUM_x86_64=""
REQUIRES="qt5-webkit jack lame portaudio portmidi"
MAINTAINER="Klaatu"
EMAIL="kla...@member.fsf.org"

it will also require a version bump in the SlackBuild, and due to a 
slight change in the build system,

MUSESCORE_BUILD_CONFIG=release \
needs to be added into the options passed to make release, otherwise the 
program is erroneously marked as dev, unstable when it is run.


Regards, Tim

--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] fontforge

[Tim Dickson via SlackBuilds-users]

it compiled just fine on my 64bit slackware 14.2
Tim

On 21/10/2020 16:54, Jim Diamond via SlackBuilds-users wrote:

When I try to compile the most recent update to fontforge on S64-14.2,
I get


libtool: install: (cd /tmp/SBo/package-fontforge/usr/lib64 && { ln -s -f 
libgunicode.so.5.0.0 libgunicode.so.5 || { rm -f libgunicode.so.5 && ln -s 
libgunicode.so.5.0.0 libgunicode.so.5; }; })
libtool: install: (cd /tmp/SBo/package-fontforge/usr/lib64 && { ln -s -f 
libgunicode.so.5.0.0 libgunicode.so || { rm -f libgunicode.so && ln -s 
libgunicode.so.5.0.0 libgunicode.so; }; })
libtool: install: /usr/bin/ginstall -c .libs/libgunicode.lai 
/tmp/SBo/package-fontforge/usr/lib64/libgunicode.la
libtool: warning: remember to run 'libtool --finish /usr/lib64'
make[3]: Leaving directory '/tmp/SBo/fontforge-20190801/Unicode'
make[2]: Leaving directory '/tmp/SBo/fontforge-20190801/Unicode'
Making install in gutils
make[2]: Entering directory '/tmp/SBo/fontforge-20190801/gutils'
make[3]: Entering directory '/tmp/SBo/fontforge-20190801/gutils'
make[3]: Nothing to be done for 'install-data-am'.
  /usr/bin/mkdir -p '/tmp/SBo/package-fontforge/usr/lib64'
  /bin/sh ../libtool   --mode=install /usr/bin/ginstall -c   libgutils.la 
'/tmp/SBo/package-fontforge/usr/lib64'
libtool: warning: relinking 'libgutils.la'
libtool: install: (cd /tmp/SBo/fontforge-20190801/gutils; /bin/sh 
"/tmp/SBo/fontforge-20190801/libtool"  --silent --tag CC --mode=relink gcc -O2 
-fPIC -Wl,--no-undefined -Werror=implicit-function-declaration -Werror=int-conversion 
-I/tmp/SBo/freetype-2.10.0/src/truetype -I/tmp/SBo/freetype-2.10.0/include 
-I/tmp/SBo/freetype-2.10.0/include/freetype -pthread -I/usr/include/glib-2.0 
-I/usr/lib64/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include 
-I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 
-I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include 
-I/usr/include/libdrm -I/usr/include/libpng16 -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib

-2

  .0/include -I/usr/include/libxml2 -I/usr/include/python2.7 -pthread 
-version-info 3:1:0 -no-undefined -o libgutils.la -rpath /usr/lib64 
libgutils_la-dlist.lo libgutils_la-fsys.lo libgutils_la-g_giomime.lo 
libgutils_la-gcol.lo libgutils_la-gimage.lo libgutils_la-gimageread.lo 
libgutils_la-gimagereadbmp.lo libgutils_la-gimagereadgif.lo 
libgutils_la-gimagereadjpeg.lo libgutils_la-gimagereadpng.lo 
libgutils_la-gimagereadras.lo libgutils_la-gimagereadrgb.lo 
libgutils_la-gimagereadtiff.lo libgutils_la-gimagereadxbm.lo 
libgutils_la-gimagereadxpm.lo libgutils_la-gimagewritebmp.lo 
libgutils_la-gimagewritegimage.lo libgutils_la-gimagewritejpeg.lo 
libgutils_la-gimagewritepng.lo libgutils_la-gimagewritexbm.lo 
libgutils_la-gimagewritexpm.lo libgutils_la-gio.lo libgutils_la-giofile.lo 
libgutils_la-giotrans.lo libgutils_la-gutils.lo libgutils_la-gwwintl.lo 
libgutils_la-prefs.lo libgutils_la-unicodelibinfo.lo -lgif -ljpeg -lpng -ltiff 
-lpangocairo-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lcairo

 -l

  pangoxft-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig 
-lfreetype -lXft -lSM -lICE -lreadline -ltermcap -lfreetype -lz -lgio-2.0 
-lgobject-2.0 -lglib-2.0 -lxml2 ../Unicode/libgunicode.la -lX11 -lm 
-inst-prefix-dir /tmp/SBo/package-fontforge)
.libs/libgutils_la-fsys.o: In function `getFontForgeUserDir':
fsys.c:(.text+0x1775): undefined reference to `smprintf'
fsys.c:(.text+0x17c5): undefined reference to `smprintf'
collect2: error: ld returned 1 exit status
libtool:   error: error: relink 'libgutils.la' with the above command before 
installing it
make[3]: *** [install-libLTLIBRARIES] Error 1
Makefile:559: recipe for target 'install-libLTLIBRARIES' failed
make[3]: Leaving directory '/tmp/SBo/fontforge-20190801/gutils'
make[2]: *** [install-am] Error 2
Makefile:952: recipe for target 'install-am' failed
make[2]: Leaving directory '/tmp/SBo/fontforge-20190801/gutils'
make[1]: *** [install-recursive] Error 1
Makefile:788: recipe for target 'install-recursive' failed
make[1]: Leaving directory '/tmp/SBo/fontforge-20190801'
make: *** [install] Error 2
Makefile:1085: recipe for target 'install' failed
Failures:
   fontforge: fontforge.SlackBuild return non-zero


Can anyone provide any insight on this?  Or even a report that it
successfully compiled for you on S64 14.2?

Thanks.

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





--
This 

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

[Tim Dickson via SlackBuilds-users]

i use pico myself. Apparently there are security reasons why modeline is 
usually disabled, especially for root user.

Tim

On 05/09/2020 08:40, Christoph Willing wrote:

On 5/9/20 10:13 am, flinchx via SlackBuilds-users wrote:

Vim has a thing called modeline.

Perhaps such settings could be added straighgt into SlackBuild template files, 
this will exclude the need for each contributor to manage them explicitly in 
vimrc?


Not everyone uses vim to edit their SlackBuilds so I'd be against adding
such support.

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/




--
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] wsdd2

[Tim Dickson via SlackBuilds-users]

hi all, I'm creating a slackbuild for wsdd2. this provides device and 
samba share browsing when netbios is not used.
As this includes ip6, it is pretty essential in a lan unless you disable 
ip6 on all the windows clients, as it allows autodiscovery. (you do need 
to make sure you allow ip6 addresses in smb.conf as well)


There isn't an rc.wsdd2 file with the source, so I was thinking of 
creating one. What I am not sure is the preferred way of adding it to 
rc.M and rc.K or similar in the doinst.sh
It would be nice if the package was activated when it was installed. It 
could always be de-activated by removing the executable bit from it's rc 
file.
i could grep for it, and if not there, then add it, but that doesn't 
handle removing it if someone removes the package.


I was surprised it hadn't been added to samba already, but looking at 
the samba mailing list, it has been sitting around but not added for 4 
years. assuming it does eventually get added, then there will be no need 
for a separate package, but until that time, it is pretty essential with 
windows 10 these days.


are there recommended ways of adding rc files so that they are run on 
startup. ?

thanks, Tim
regards, Tim

--
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] gloox slackbuild

[Tim Dickson via SlackBuilds-users]

I noticed this gloox has been orphaned, and it is a dependency for 0ad 
so if no-one else wants it,
I'll look after it, and will update it with a current (1.0.23) version 
when submissions are open again.



--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] VLC 3.0.11 segfault

[Tim Dickson via SlackBuilds-users]

rebuild ffmpeg and transode and maybe vid.stab
(I had the same issue with vlc).
You will need to make sure that if you do upgradepkg use the 
--reinstall  option for the sub-libs
because otherwise they won't be replaced with the same versions linked 
with the newer x265

regards, Tim


On 23/06/2020 17:43, Frédéric Falsetti wrote:

Hi,
vlc want  libx265.so.188, but x265-3.4-i586-1_SBo have libx265.so.192

$ LANG=en vlc -vv
VLC media player 3.0.11 Vetinari (revision 3.0.11-0-gdc0c5ced72)
[086ad140] main libvlc debug: VLC media player - 3.0.11 Vetinari
[086ad140] main libvlc debug: Copyright © 1996-2020 the VideoLAN team
[086ad140] main libvlc debug: revision 3.0.11-0-gdc0c5ced72
[086ad140] main libvlc debug: configured with ./configure  '--prefix=/usr' 
'--libdir=/usr/lib' '--sysconfdir=/etc' '--mandir=/usr/man' 
'--docdir=/usr/doc/vlc-3.0.11' '--localstatedir=/var' 
'--build=i586-slackware-linux' '--enable-qt=5' '--disable-wayland' 
'--enable-opencv' '--enable-merge-ffmpeg' '--enable-libva=no' 
'--with-kde-solid=no' 'build_alias=i586-slackware-linux' 'CFLAGS=-O2 
-march=i486 -mtune=i686' 'LDFLAGS=-lrt' 'CXXFLAGS=-O2 -march=i486 -mtune=i686' 
'PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig'
[086ad140] main libvlc debug: searching plug-in modules
[086ad140] main libvlc debug: loading plugins cache file 
/usr/lib/vlc/plugins/plugins.dat
[086ad140] main libvlc debug: recursively browsing `/usr/lib/vlc/plugins'
[086ad140] main libvlc warning: cannot load module 
`/usr/lib/vlc/plugins/stream_out/libstream_out_chromaprint_plugin.so' 
(libx265.so.188: cannot open shared object file: No such file or directory)
[086ad140] main libvlc warning: cannot load module 
`/usr/lib/vlc/plugins/vdpau/libvdpau_avcodec_plugin.so' (libx265.so.188: cannot 
open shared object file: No such file or directory)
[086ad140] main libvlc warning: cannot load module 
`/usr/lib/vlc/plugins/video_filter/libopencv_wrapper_plugin.so' 
(libx265.so.188: cannot open shared object file: No such file or directory)
[086ad140] main libvlc warning: cannot load module 
`/usr/lib/vlc/plugins/codec/libavcodec_plugin.so' (libx265.so.188: cannot open 
shared object file: No such file or directory)
[086ad140] main libvlc debug: plug-ins loaded: 489 modules
[086ad140] main libvlc debug: opening config file…
Erreur de segmentation
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/




--
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] cmake too old issues

[Tim Dickson via SlackBuilds-users]

Just a note to say I was successful in adding a private version of cmake 
to the script
for details in case anyone else has the same problem, I posted the steps 
in the

answer to my own query on linuxquestions.org

https://www.linuxquestions.org/questions/slackware-14/problem-with-newer-cmake-options-run-on-slackware-cmake-3-5-2-a-4175674772/

Regards, Tim

On 25/05/2020 18:21, B Watson wrote:

On 5/25/20, Tim Dickson via SlackBuilds-users
 wrote:

Can anyone point me towards a way to include a newer local version of
cmake, just for the slackbuild, or if they have other suggestions,
as I have not managed to get the build to work.

One thing you could do: include the source to your newer cmake as
a DOWNLOAD in the .info file. First thing your script does is
unpack and compile cmake, and install it to $TMP/$PRGNAM/cmake or
similar. Then export PATH=$TMP/$PRGNAM/cmake/bin (or wherever the
cmake binary ends up).

Pat's cmake slackbuild at
http://slackware.uk/slackware/slackware64-current/source/d/cmake/
might give you some hints on how to build it. You'll want
--prefix=$TMP/$PRGNAM/cmake and you might need --enable-static and
--disable-shared if they're supported. You *won't* need --qt-gui, should
probably say --no-qt-gui.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/




---
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] cmake too old issues

[Tim Dickson via SlackBuilds-users]

Thanks for the suggestion B.Watson, I'll give it a go. I'm cautious that 
I don't pollute a "clean" system, but hopefully
that should work. If it does, I could always document it, so other 
people with the same issue could use the

same method in their scripts.

I agree that the other method suggested would be problematic, especially 
as it would be hard to add to

REQUIRES

I have patched other build packages that were forcing an cmake update, 
but this one was proving too problematic.
I would like to wait for slackware 15 as well, but I don't want to wait 
indefinitely. Hopefully Pat can sort out his
distribution model, and gets happy enough with current to do a release 
soon. "when it's ready" :-)
Although I appreciate the stability of slackware release version, I 
wouldn't want it to be so old that It won't run
current common software, or hardware, but (almost as an oxymoron) I 
wouldn't want to move to "current", because

the base changes too much, and my  internet data allowance is restricted.
Hence I try to "do my bit" to keep software I use current on my 
favourite distro.


Regards, Tim


---
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] cmake too old issues

[Tim Dickson via SlackBuilds-users]

One of the slackbuilds I look after has switched from waf to cmake. 
Unfortunately they have targetted cmake v 3.11 and have used
features which are not available, or are broken in cmake 3.5.2 (the 
version that comes with slackware 14.2)
Can anyone point me towards a way to include a newer local version of 
cmake, just for the slackbuild, or if they have other suggestions,

as I have not managed to get the build to work.
upstream have made heavy use of IMPORTED_TARGET in pkg_check_modules 
statements, and in a custom cmake Find module
I can bypass the custom Find module and revert to pkgconfig, but I don't 
know how to do the equivalent of

pkg_check_modules(Gnome REQUIRED IMPORTED_TARGET
  "atk"
  "cairo"
  "gdk-3.0"
  "gdk-pixbuf-2.0"
  "gio-2.0"
  "gobject-2.0"
  "libsoup-2.4"
  "pango"
  "minizip"
  "zlib"
  "libxml-2.0>=2.7.8"
  )

for example, without the "IMPORTED_TARGET" bit.
unfortunately, just removing IMPORTED_TARGET text from the dependencies 
file does not work.
the slackbuild in question is xiphos for which I'm trying to get 4.2.1 
to build. ( https://github.com/crosswire/xiphos  )


Thanks, Tim

---
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] perl-Module-Build slackbuild

[Tim Dickson via SlackBuilds-users]

regarding the  perl-Module-Build slackbuild

This package has an extra (unlisted) optional dependency,
perl-Archive-Zip

I emailed the maintainer (Edinaldo) regarding adding it to the
readme, and he suggested posting to the list, as he is too busy
to look at it at the moment.

if it could be added to the README that would be great.
many thanks.
Tim

---
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] Puzzling error building qt5-webkit

[Tim Dickson via SlackBuilds-users]

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

On 2020-04-25 17:36,
Slackbuilds Users  put forth the proposition:

i spotted an optional dep of qt5-webkit which is dwz
this appears to de-duplicate debug symbols etc in elf files. however, as we
tend to remove all
extra debug stuff with strip, It doesn't appear to change the package size
much.
is anyone interested in a dwz as a package?. I did create one to see if it
made much difference
to the qt5-webkit package, and though the size was within 9bytes!, it did
appear to create the package
a bit quicker, so may be worth using.
comments?
regards, Tim

According to the man page[1], it isn't for qt5-webkit, but for any
ELF binary.

[1] https://www.mankier.com/1/dwz

that's right. I haven't seen what else may have code to use it if it is 
there (I'm not sure how to do that anyway without downloading all the 
sbo package sources and greping for it in makefiles). I submitted the 
dwz package yesterday. Generally because the practice is often to strip 
the  binaries, we wouldn't see much benefit, unless there are lots of 
intermediate stages which are sped up with smaller ELF binaries during 
the build process.
I only spotted the existence of dwz  when going through the (qt5-webkit) 
build log, I saw the mention of it, and checked it out, and saw it is 
available for lots of other distros, so why not for slackware? if it 
improves executable size or build speeds I'm in favour, but I don't know 
what else uses it. it appears to be used by debian, ubuntu, redhat, 
fedora etc. so the odds are we may see it appearing more  in some 
packages. I'm not sure which category it should go in, development or 
system, but it can be moved if I picked the wrong one.

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





---
This email has been checked for viruses by AVG.
https://www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5-webkit issues

[Tim Dickson via SlackBuilds-users]

On 26/04/2020 03:12, Dave Woodfall wrote:

On 2020-04-26 00:13,
Slackbuilds Users  put forth the proposition:

i've noticed a change in qt5-webkit; any applications that use it will fail
if run as root,
unless you set QTWEBENGINE_DISABLE_SANDBOX=1 before running the executable
that uses it. It may be worth a comment, or something as binaries that used
to run as root
will not any more without this environment variable set. it effects
musescore 3.4.2, and possibly
gambas and others that use it (approx 23 packages).
regards, Tim

I'll make a note of it in README, but it's not a good idea to run GUI
applications as root, especially anything web-browserish, and most
people would have no need.  Sandboxing it is for safety.

thanks.
yes I'm aware of the risks of running browsers as root, the "software 
police" doesn't like anyone running as root. but for package builders 
you often should be building packages as root, with full root path env 
ie. su - (at least a number of packages will fail otherwise)
and a quick test (while still as root) that the package built and runs 
ok would fail in those cases. This is how I spotted the problem anyway. :-)
musescore just crashes (fails to come up) unless you call it with -w  to 
disable the web related component, or set that environment variable I 
mentioned.
talking of which, incase klaatu is checking this mail group, if he is 
interested, musescore 3.4.2 has been out for a few months now, and just 
requires the usual version bump and updated download links and md5 sums 
in the slackbuild to get it to work.

On 25/04/2020 18:13, Dave Woodfall wrote:

On 2020-04-25 17:36,
Slackbuilds Users  put forth the proposition:

i spotted an optional dep of qt5-webkit which is dwz
this appears to de-duplicate debug symbols etc in elf files. however, as we
tend to remove all
extra debug stuff with strip, It doesn't appear to change the package size
much.
is anyone interested in a dwz as a package?. I did create one to see if it
made much difference
to the qt5-webkit package, and though the size was within 9bytes!, it did
appear to create the package
a bit quicker, so may be worth using.
comments?
regards, Tim

If you want to submit it, I'll add it to the readme as optional.

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




---
This email has been checked for viruses by AVG.
https://www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



___
SlackBuilds-users mailing list
SlackBuilds-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] qt5-webkit issues

[Tim Dickson via SlackBuilds-users]

i've noticed a change in qt5-webkit; any applications that use it will 
fail if run as root,

unless you set QTWEBENGINE_DISABLE_SANDBOX=1 before running the executable
that uses it. It may be worth a comment, or something as binaries that 
used to run as root
will not any more without this environment variable set. it effects 
musescore 3.4.2, and possibly

gambas and others that use it (approx 23 packages).
regards, Tim


On 25/04/2020 18:13, Dave Woodfall wrote:

On 2020-04-25 17:36,
Slackbuilds Users  put forth the proposition:

i spotted an optional dep of qt5-webkit which is dwz
this appears to de-duplicate debug symbols etc in elf files. however, as we
tend to remove all
extra debug stuff with strip, It doesn't appear to change the package size
much.
is anyone interested in a dwz as a package?. I did create one to see if it
made much difference
to the qt5-webkit package, and though the size was within 9bytes!, it did
appear to create the package
a bit quicker, so may be worth using.
comments?
regards, Tim


If you want to submit it, I'll add it to the readme as optional.

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





---
This email has been checked for viruses by AVG.
https://www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Puzzling error building qt5-webkit

[Tim Dickson via SlackBuilds-users]

i spotted an optional dep of qt5-webkit which is dwz
this appears to de-duplicate debug symbols etc in elf files. however, as 
we tend to remove all
extra debug stuff with strip, It doesn't appear to change the package 
size much.
is anyone interested in a dwz as a package?. I did create one to see if 
it made much difference
to the qt5-webkit package, and though the size was within 9bytes!, it 
did appear to create the package

a bit quicker, so may be worth using.
comments?
regards, Tim

On 25/04/2020 15:58, Matteo Bernardini wrote:

Il giorno sab 25 apr 2020 alle ore 16:52 Luveh Keraph
<1.41...@gmail.com> ha scritto:

   Could NOT find Hyphen (missing: HYPHEN_INCLUDE_DIR HYPHEN_LIBRARIES)

it seems you are missing at least one of the dependencies.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/




---
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] /usr/include/python3.7 or 3.7m ?

[Tim Dickson via SlackBuilds-users]

i've a reasonable collection of python .sbo packages installed, and 
sip.h is the only file in /usr/include/python3.7

which is from stock slackware 14.2 sip-4.18 package
Regards, Tim


On 24/04/2020 09:51, MyRequiem wrote:
Re: Christoph Willing 24.04.2020 
<74588ed6-9214-79c1-3b2b-9fb252a57...@linux.com>

At the moment, SBo builds of python3 on both my daily machine and a
clean VM result in the include files being placed into
/usr/include/python3.7m (rather than a plain /usr/include/python3.7).

Apparently the different paths signified use (or non-use) of an internal
memory allocator which is on by default but controllable using the
--with(out)-pymalloc configure option when building python3. I've tested
this and the --without-pymalloc does result in /usr/include/pyton3.7
(not python3.7m).

BTW this behaviour has changed in 3.8 where everything goes into
/usr/include/pyton3.8 (see -current, also see
https://bugs.python.org/issue36707).


Before proceeding here with a complaint about other packages wrongly
hard coding python-related .h files into /usr/include/python3.7, rather
than python3.7m, could people first confirm that their python3
installation is using /usr/include/python3.7m, as mine does, please?


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


Yes,
Python3.7: /usr/include/python3.7m
Python3.8: /usr/include/python3.8
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/





---
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] ATT: anyone using python3-PyQt5

[Tim Dickson via SlackBuilds-users]

I also spotted that qt5-webkit is marked as a dependency of python3-PyQt5
if it has been split into python3-PyQt5 and python3-PyQtWebEngine does 
that change the qt5-webkit dependency of python3-PyQt5 to just qt5 , or 
is the

webengine different from webkit?
Regards, Tim

On 23/04/2020 06:18, Dave Woodfall wrote:

Hi all,

This is a heads-up for anyone using python3-PyQt5.  The version we
have now has had support for QtWebEngine python bindings split into
a separate package - python3-PyQtWebEngine.

Here is a list of SlackBuilds that currently depend on python3-PyQt5
and that may /possibly/ need python3-PyQtWebEngine.

Since python3-PyQt5 is a dependency of python3-PyQtWebEngine, it's a
matter of swapping one for the other in REQUIRES.

academic/Mnemosyne
academic/veusz
audio/carla
desktop/anki
desktop/kolorcontrol
development/jupyter-qtconsole
games/pybik
libraries/QScintilla-qt5
multimedia/openshot
network/Electrum
network/onionshare
network/persepolis
office/ReText
python/pyqode.qt
system/fs-uae-arcade
system/fs-uae-launcher
system/laptop-mode-tools

So far, `anki' is the only one that I know that needs it and I've
adjusted it in my branch.



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





---
This email has been checked for viruses by AVG.
https://www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5-webkit

[Tim Dickson via SlackBuilds-users]

the md5 sum seems to be different for qt5-webkit. I'm getting 
22e442063e7d0362439934442e269ed2

but am expecting  cd77f90cbf312f88d23699a65cd76ee4
have downloaded a couple of times just in case, but still different.

(I got qt5 built ok (8gb ram is enough).)


On 19/04/2020 22:09, Dave Woodfall wrote:

On 2020-04-19 22:06,
Dave Woodfall  put forth the proposition:

On 2020-04-19 17:00,
B Watson  put forth the proposition:

On 4/19/20, Dave Woodfall  wrote:


As soon as that's done I'll push the update to my git updates branch.

Actually, I kinda already pushed a fix for the download URL... it
was indeed the "v" in the filename.

It created a problem is the slackbuild.  I had put in some vars for
the source directory etc. that failed with the new tarball because
the output directory was named differently.

is = in.

--
Dave

The antibloat squad!
For those interested in no bloat, minimal desktop Linux
gopher://tty1.uk/1/?minimal-linux
http://tty1.uk/minimal-linux
#minimallinux @ chat.freenode.net

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





---
This email has been checked for viruses by AVG.
https://www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Qt5 ... newer versions available

[Tim Dickson via SlackBuilds-users]

will there be a new version of qt5-webkit in line with the new qt5 ?
thanks,
Tim




---
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] qt5 build fail

[Tim Dickson via SlackBuilds-users]

build completed successfully on my vm with 8gb RAM allocated, (and 12G+ 
free disk space)

so swap+ram should be>7GB to complete. - may be more with docs.
thanks all.
Tim

---
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] hope this isn't a stupid question

[Tim Dickson via SlackBuilds-users]

i use qemu 4.0 to do just that (4.1 requires stuff from current, and I 
didn't want to pollute my host slack stable)

something like
qemu-img create -f qcow2 /data/images/slack14.2_64bit_base.qcow2 100G
will create a virtual disk drive 100G which you can snapshot, if you 
want to reverse changes,

configuring the bridge in /etc/rc.d/rc.inet1.conf
create /etc/qemu/bridge.conf  containing a single line
allow br0

and using
nohup qemu-system-x86_64 -cpu qemu64 -smp 4 -m 8G -drive 
file=/data/images/slack14.2_64bit_base.qcow2,format=qcow2 -cdrom 
/mnt/smb1/slackware/iso/slackware64-14.2-install-dvd.iso -boot c -net 
nic,macaddr=02:00:00:11:11:18,model=i82551 -net bridge,br=br0 
-enable-kvm -k en-gb -display vnc=:1 -monitor 
telnet:localhost:7100,server,nowait,nodelay &


runs a vm with 8GB ram (assuming you have enough real ram to give it 
that), a virtual dvd drive with the slack installer iso - for 
installing, and setting the output to vnc and telnet. this way you can 
telnet to see the console tty, or/and vnc (port 5901 to see it and any 
xwindows stuff you run, and off course if you set it up, you can telnet 
or ssh to the vm directly as well.


obviously change the paths to suit your preferred setup.

Regards, Tim

On 08/04/2020 14:43, Glenn Becker wrote:

Hi -

I am thinking of buying a smallish laptop to dedicate to Slackware. 
I've usually done double-, triple- and occasionally more- boot 
machines, but my distro-hopping is (I think!) coming to an end.


And I was wondering ... if I ran slack-current as my main system, but 
ran slack-stable in a VM, could I use the latter to work on my 
SlackBuilds? I'm by no means well-versed in what is possible or 
impossible with VMs.


Thanks,

Glenn Becker


"Doctor, I have come to ask you to tell me everything you know about 
the night."

- Djuna Barnes, /Nightwood/


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





---
This email has been checked for viruses by AVG.
https://www.avg.com
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] qt5 build issue

[Tim Dickson via SlackBuilds-users]

extra log info from /var/log/sbopkg/sbopkg-build-log|tail -n50

[258/2543] /usr/bin/g++ -MMD -MF 
obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_10.o.d 
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 
-DUSE_OZONE=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD 
-DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD 
-DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBLINK_CORE_IMPLEMENTATION=1 
-DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DBLINK_IMPLEMENTATION=1 
-DINSIDE_BLINK -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 
-DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE 
-DUCHAR_TYPE=uint16_t -DGOOGLE_PROTOBUF_NO_RTTI 
-DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD 
-DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS -DSK_HAS_PNG_LIBRARY 
-DSK_HAS_WEBP_LIBRARY -DSK_HAS_JPEG_LIBRARY -DSK_SUPPORT_GPU=1 
-DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" 
-DWTF_USE_WEBAUDIO_FFMPEG=1 -DSUPPORT_WEBGL2_COMPUTE_CONTEXT=1 
-DWTF_USE_DEFAULT_RENDER_THEME=1 -DUSE_SYSTEM_LIBJPEG 
-DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=0 -DGTEST_RELATIVE_PATH 
-DWEBRTC_CHROMIUM_BUILD -DWEBRTC_POSIX -DWEBRTC_LINUX 
-DABSL_ALLOCATOR_NOTHROW=1 -DNO_MAIN_THREAD_WRAPPING -DLIBXSLT_STATIC 
-DUSE_SYSTEM_ZLIB=1 -I. -Igen -I../../3rdparty/chromium -Igen -Igen 
-Igen -Igen -I../../3rdparty/chromium/third_party/khronos 
-I../../3rdparty/chromium/gpu 
-I../../3rdparty/chromium/third_party/libyuv/include -Igen -Igen -Igen 
-I../../3rdparty/chromium/third_party/ced/src 
-I../../3rdparty/chromium/third_party/icu/source/common 
-I../../3rdparty/chromium/third_party/icu/source/i18n 
-I../../3rdparty/chromium/third_party/protobuf/src 
-I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out 
-I../../3rdparty/chromium/third_party/boringssl/src/include 
-I../../3rdparty/chromium/skia/config -I../../3rdparty/chromium/skia/ext 
-I../../3rdparty/chromium/third_party/skia/include/c 
-I../../3rdparty/chromium/third_party/skia/include/config 
-I../../3rdparty/chromium/third_party/skia/include/core 
-I../../3rdparty/chromium/third_party/skia/include/effects 
-I../../3rdparty/chromium/third_party/skia/include/encode 
-I../../3rdparty/chromium/third_party/skia/include/gpu 
-I../../3rdparty/chromium/third_party/skia/include/images 
-I../../3rdparty/chromium/third_party/skia/include/lazy 
-I../../3rdparty/chromium/third_party/skia/include/pathops 
-I../../3rdparty/chromium/third_party/skia/include/pdf 
-I../../3rdparty/chromium/third_party/skia/include/pipe 
-I../../3rdparty/chromium/third_party/skia/include/ports 
-I../../3rdparty/chromium/third_party/skia/include/utils 
-I../../3rdparty/chromium/third_party/skia/src/gpu 
-I../../3rdparty/chromium/third_party/skia/src/sksl 
-I../../3rdparty/chromium/third_party/angle/include 
-I../../3rdparty/chromium/third_party/angle/src/common/third_party/base 
-Igen/angle -I../../3rdparty/chromium/v8/include -Igen/v8/include 
-I../../3rdparty/chromium/third_party/webrtc_overrides 
-I../../3rdparty/chromium/third_party/webrtc 
-I../../3rdparty/chromium/third_party/iccjpeg 
-I../../3rdparty/chromium/third_party/ots/include 
-I../../3rdparty/chromium/v8/include -Igen/v8/include 
-I../../3rdparty/chromium/third_party/libxml/src/include 
-I../../3rdparty/chromium/third_party/libxml/linux/include 
-I../../3rdparty/chromium/third_party/libxslt/src -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -m64 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 
-Wno-unused-local-typedefs -Wno-maybe-uninitialized 
-Wno-deprecated-declarations -fno-delete-null-pointer-checks 
-Wno-comments -Wno-dangling-else -Wno-packed-not-aligned 
-Wno-missing-field-initializers -Wno-unused-parameter 
-fno-omit-frame-pointer -fvisibility=hidden -O2 -fno-ident 
-fdata-sections -ffunction-sections -g0 
-isystem../../../../../../../usr/include/nss 
-isystem../../../../../../../usr/include/nspr -isystem 
../../3rdparty/chromium/third_party/abseil-cpp 
-isystem../../../../../../../usr/include/libpng16 -DLIBXML_STATIC= 
-std=gnu++14 -Wno-narrowing -Wno-attributes -Wno-class-memaccess 
-Wno-subobject-linkage -fno-exceptions -fno-rtti 
-fvisibility-inlines-hidden -c 
gen/third_party/blink/renderer/core/frame/frame_jumbo_10.cc -o 
obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_10.o

FAILED: obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_10.o
/usr/bin/g++ -MMD -MF 
obj/third_party/blink/renderer/core/frame/frame/frame_jumbo_10.o.d 
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 
-DUSE_OZONE=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD 
-DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD 
-DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 

[Slackbuilds-users] qt5 build fail

[Tim Dickson via SlackBuilds-users]

trying to build the updated qt5  5.12.7 (using sbopkg) is failing for me.
with the error message.

ninja: build stopped: subcommand failed.
Makefile.gn_run:1237: recipe for target 'run_ninja' failed
make[4]: *** [run_ninja] Error 1
make[4]: Leaving directory 
'/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine/src/core'

Makefile:82: recipe for target 'sub-gn_run-pro-make_first' failed
make[3]: *** [sub-gn_run-pro-make_first] Error 2
make[3]: leaving directory 
'/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine/src'

Makefile:80: recipe for target 'sub-core-make_first' failed
make[2]: *** [sub-core-make_first] Error 2
make[2]: Leaving directory 
'/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine/src'

Makefile:48: recipe for target 'sub-src-make_first' failed
make[1]: *** [sub-arc-make_first] Error 2
make[1]: Leaving directory '/tmp/SBo/qt-everywhere-src-5.12.7/qtwebengine'
Makefile:1031: recipe for target 'module-qtwebengine-make_first' failed
make: *** [module-qtwebengine-make_first] Error 2

I do have Jinja installed
/var/log/packages/ninja-1.10.0-x86_64-1_SBo
I am building with proprietry codecs and webengine options
Anyone any ideas
regards, Tim


---
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] frei0r slackbuild issue

[Tim Dickson via SlackBuilds-users]

On 21/01/2020 11:50, Matteo Bernardini wrote:

Il giorno mar 21 gen 2020 alle ore 12:37 Tim Dickson via
SlackBuilds-users  ha scritto:

frei0r did work with opencv 4.1
it looks like a patch or two have been worked on which may fix the issue
with opencv 4.2
https://github.com/dyne/frei0r/pull/97
and
https://github.com/dyne/frei0r/pull/94
hopefully frei0r >V1.7 will work ok.
Tim

I've tried those and they actually don't help...
even if some patch will do at some point most probably 10 days later a
new opencv release will break support again: it doesn't makes much
sense IMHO to leave it enabled, most of the other distros build frei0r
with opencv disabled so I suppose we will do the same from now on.

Matteo
I guess so, it's a pity opencv api is not more stable. thanks for the 
work on frei0r anyway.


---
This email has been checked for viruses by AVG.
https://www.avg.com

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

Re: [Slackbuilds-users] frei0r slackbuild issue

[Tim Dickson via SlackBuilds-users]

frei0r did work with opencv 4.1
it looks like a patch or two have been worked on which may fix the issue 
with opencv 4.2

https://github.com/dyne/frei0r/pull/97
and
https://github.com/dyne/frei0r/pull/94
hopefully frei0r >V1.7 will work ok.
Tim

On 20/01/2020 14:05, Christoph Willing wrote:

On 20/1/20 11:07 pm, Tim Dickson via SlackBuilds-users wrote:

frei0r is failing to build when opencv is installed. (using sbopkg).
see error below. Any ideas on how to fix it?


/tmp/SBo/frei0r-plugins-1.7.0/src/filter/facebl0r/facebl0r.cpp: In
member function 'virtual void FaceBl0r::update(double, uint32_t*,
const uint32_t*)':
/tmp/SBo/frei0r-plugins-1.7.0/src/filter/facebl0r/facebl0r.cpp:217:43:
error: could not convert
'((FaceBl0r*)this)->FaceBl0r::tracked_obj->TrackedObj::prev_rect' from
'cv::Rect {aka cv::Rect_}' to 'CvRect'
     cvSetImageROI (image, tracked_obj->prev_rect);
    ^
/tmp/SBo/frei0r-plugins-1.7.0/src/filter/facebl0r/facebl0r.cpp:226:73:
error: could not convert 'cv::Scalar_(0.0, 0.0, 2.55e+2, 0.0)'
from 'cv::Scalar {aka cv::Scalar_}' to 'CvScalar'
    cvEllipseBox(image, face_box, CV_RGB(255,0,0), 2,
CV_AA, 0);
^
/tmp/SBo/frei0r-plugins-1.7.0/src/filter/facebl0r/facebl0r.cpp: In
member function 'CvBox2D FaceBl0r::camshift_track_face(IplImage*,
TrackedObj*)':
/tmp/SBo/frei0r-plugins-1.7.0/src/filter/facebl0r/facebl0r.cpp:350:10:
error: could not convert 'rot_rect' from 'cv::RotatedRect' to 'CvBox2D'
    return rot_rect;
   ^
src/filter/facebl0r/CMakeFiles/facebl0r.dir/build.make:62: recipe for
target 'src/filter/facebl0r/CMakeFiles/facebl0r.dir/facebl0r.cpp.o'
failed
make[2]: ***
[src/filter/facebl0r/CMakeFiles/facebl0r.dir/facebl0r.cpp.o] Error 1
CMakeFiles/Makefile2:632: recipe for target
'src/filter/facebl0r/CMakeFiles/facebl0r.dir/all' failed
make[1]: *** [src/filter/facebl0r/CMakeFiles/facebl0r.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

I think the alternatives are:
1. file a bug report with frei0r, about compatibility with the latest
opencv-4.2.0 (I'm pretty sure it was OK with the previous opencv-4.1.0).
2. build frei0r using opencv-legacy rather than opencv
3. don't build frei0r against opencv or opencv-legacy at all (since
it's an optional dep for frei0r).

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/




---
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] frei0r slackbuild issue

[Tim Dickson via SlackBuilds-users]

frei0r is failing to build when opencv is installed. (using sbopkg).
see error below. Any ideas on how to fix it?

/tmp/SBo/frei0r-plugins-1.7.0/src/filter/facebl0r/facebl0r.cpp: In 
member function 'virtual void FaceBl0r::update(double, uint32_t*, 
const uint32_t*)':
/tmp/SBo/frei0r-plugins-1.7.0/src/filter/facebl0r/facebl0r.cpp:217:43: 
error: could not convert 
'((FaceBl0r*)this)->FaceBl0r::tracked_obj->TrackedObj::prev_rect' from 
'cv::Rect {aka cv::Rect_}' to 'CvRect'

    cvSetImageROI (image, tracked_obj->prev_rect);
   ^
/tmp/SBo/frei0r-plugins-1.7.0/src/filter/facebl0r/facebl0r.cpp:226:73: 
error: could not convert 'cv::Scalar_(0.0, 0.0, 2.55e+2, 0.0)' 
from 'cv::Scalar {aka cv::Scalar_}' to 'CvScalar'
   cvEllipseBox(image, face_box, CV_RGB(255,0,0), 2, 
CV_AA, 0);

^
/tmp/SBo/frei0r-plugins-1.7.0/src/filter/facebl0r/facebl0r.cpp: In 
member function 'CvBox2D FaceBl0r::camshift_track_face(IplImage*, 
TrackedObj*)':
/tmp/SBo/frei0r-plugins-1.7.0/src/filter/facebl0r/facebl0r.cpp:350:10: 
error: could not convert 'rot_rect' from 'cv::RotatedRect' to 'CvBox2D'

   return rot_rect;
  ^
src/filter/facebl0r/CMakeFiles/facebl0r.dir/build.make:62: recipe for 
target 'src/filter/facebl0r/CMakeFiles/facebl0r.dir/facebl0r.cpp.o' failed
make[2]: *** 
[src/filter/facebl0r/CMakeFiles/facebl0r.dir/facebl0r.cpp.o] Error 1
CMakeFiles/Makefile2:632: recipe for target 
'src/filter/facebl0r/CMakeFiles/facebl0r.dir/all' failed

make[1]: *** [src/filter/facebl0r/CMakeFiles/facebl0r.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2



---
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] gambas3 slackbuild

[Tim Dickson via SlackBuilds-users]

For those using gambas3; since I updated gambas3 yesterday the dev team 
(Benoit) has pushed a couple of extra fixes. (without changing the 
version number!)

This will make the checksum for the slackbuild fail.
the new md5sum is 734b5f0bcd750e5727027b62a5545a56
I'll fix it before next Friday.
regards, Tim

---
This email has been checked for viruses by AVG.
https://www.avg.com

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

[Slackbuilds-users] what is the view on slackbuilds for none-free stuff

[Tim Dickson via SlackBuilds-users]

I have a slackbuild for a game of which the sourc ecode is gpl and is on 
github, but the game data has to be purchased. As such the game homepage 
has a link to itch.io to buy the game which provides a personalised link 
fora gz of the source including the extra game data, as well as a 
pre-compiled binary.  I can include an md5sum for this source file, but 
obviously can't provide a direct download link.
all you have to do is buy it (£1 minimum) and put the source tar.gz 
which includes the game data in the same folder as the build script as 
usual.
Is that eligible for slackbuilds.org ? obviously to respect the author's 
data, resulting package would have to be for personal use.

regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] MuseScore slackbuild

[Tim Dickson via SlackBuilds-users]

There are a couple of typos in MuseScore slackbuild.
in the MuseScore.info file MuseScore_General-License.md
should be
MuseScore_General_License.md

the cp line in MuseScore.SlackBuild also needs fixing.

cp $CWD/MuseScore_General-License.md share/sound
should be
cp $CWD/MuseScore_General_License.md share/sound

(FWIW version updating to 3.3 works fine with the usual updates to the 
.info and .SlackBuild ,including the fix mentioned above)

Regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] MuseScore needs patches to build

[Tim Dickson via SlackBuilds-users]

I found 2 of the md5sums need updating, and if you want to go to v 3.2.3 
you can update them all.


c82487e32b680a8d6702f4f7ca898d95  MuseScore_General.sf3
a0cf65b59c54b3ab6727c02336461315  MuseScore_General_License.md
f7b6a53fea406c0a0e90c12ee347c056  MuseScore-3.2.tar.gz  or 
9c8d8015b5a3f8e202f5c9652f90c48d  MuseScore-3.2.3.tar.gz
( version 3.2.3 is just a version bump in the slackbuild , the  - to _ 
modification for the license file that erich mentioned, and the info 
update accordingly. )


Regards, Tim

On 05/09/2019 15:17, Erich Ritz via SlackBuilds-users wrote:
I had to apply the attached two patches to build MuseScore on 
Slackware64-14.2.


MuseScore_General-License.md needs to be renamed to 
MuseScore_General_License.md in both the SlackBuild and info file, and 
the md5sum of that file needed to be updated in the info file to 
c82487e32b680a8d6702f4f7ca898d95.


Erich

___
SlackBuilds-users mailing list
SlackBuilds-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] audacity slackbuild bug/fix

[Tim Dickson via SlackBuilds-users]

There's a typo in the audacity slackbuild
the line

rm -rf $PRGNAM-src-$VERSION

should read

rm -rf $PRGNAM-$SRCNAM-$VERSION

Without this change, if you try to rebuild the same version of audacity 
on a machine (using sbo for example) the build fails.

regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] Musescore slackbuild

[Tim Dickson via SlackBuilds-users]

There's a new version of musescore. (3.2.3) a version bump and relevant 
.info updates +change from

MuseScore_General-licence.md  to
MuseScore_General_licence.md in the build and info file is all that's 
needed to update it.

regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] musescore slackbuild

[Tim Dickson via SlackBuilds-users]

just emailing the list in case my email didn't get through to klaatu 
last week.

I've updated the musescore slackbuild to 3.2.2 if you are interested.?
current version on slackbuilds is 3.0.4 from february this year.
regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] frei0r slackbuild issue with opencv4

[Tim Dickson via SlackBuilds-users]

frei0r slackbuild is failing to build with opencv (4) giving the 
following...


CMake Error: The following variables are used in this project, but they 
are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the 
CMake files:

OpenCV_INCLUDE_DIR

I have tried adding
OpenCV_INCLUDE_DIR=/usr/include/opencv4/opencv2; export OpenCV_INCLUDE_DIR
to the build script before the cmake line build it still says it can't 
find it even those those directories are ok.

any ideas?
regards, Tim
___
SlackBuilds-users mailing list
SlackBuilds-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] docutils slackbuild

[Tim Dickson via SlackBuilds-users]

many thanks, that fixed it.
Hopefully that one-liner patch  will make it into this weekends update. :-)
regards, Tim

On 25/06/2019 17:12, MyRequiem wrote:

Script support is enabled by default. Patch in the attached file.

___
SlackBuilds-users mailing list
SlackBuilds-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] docutils slackbuild

[Tim Dickson via SlackBuilds-users]

since docutils and python3-docutils have been combined I am getting an 
error running a python3 program needing docutils

the error is
File "/usr/lib64/python3.7/site-packages/docutils/__init__.py", line 
112, in 

  class ApplicationError(StandardError):
NameError: name 'StandardError' is not defined

Apparently StandardError was dropped in python3. is there a 
workaround/fix for this to get it to work?.

Thanks.
Tim
___
SlackBuilds-users mailing list
SlackBuilds-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 - 20190601

[Tim Dickson via SlackBuilds-users]

you're welcome to combine python3-docutils with docutils and 
python3-pyserial with pyserial if robby and cristiano don't mind

(the thonny dep will need updating.)
regards, Tim

On 02/06/2019 17:38, Willy Sudiarto Raharjo wrote:

BTW, other python3-based module scripts, would be better inegrated into
their python2-based scripts? for easier management. e.g. there is still
python3-itsdangerous.

Also, there are quite a lot python-module scripts based in Libraries
category, rather than Python category. What's the reason for such? Would
it be nice if sort them in one category to make life easy ? :P

If the maintainer (Dimitri) has no objections, that would be a good idea
I cc him on this email

please note that python3-itsdangerous still being listed as a dependency
for python3-Flask, so if it's being removed, python3-Flask need to be
updated (again).

Thanks


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



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

[Tim Dickson via SlackBuilds-users]

this is a request for an update to the denyhosts slackbuild version, 
which is very old. I noticed that the project moved to github, with 
releases on sourceforge under the name denyhost instead of denyhosts 
(which only has up to 2.6).

It is currently at 3.1
This email is sent to the list, as I haven't had a response from the 
maintainer (Doug) directly so I don't know if he is still around.
( I did create a patch for 2.6 to add slackware defaults and 
rc.denyhosts, but having spotted the newer versions which move one of 
the config files to /etc/ I could update the patch for version 3.1 if 
anyone is interested.)

regards, Tim

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