The download link for sourceforge listed on the SBo page works for me.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail
Hi,
I have been maintaining development/slibtool on SBo for a while which is
a drop-in replacement for GNU libtool and working with its upstream to
fix any build issues I can find with my limited setup.
Slibtool ships with several different symlinks which generate different
behaviors and with thi
>What video hardware are you using? I had brought this up before on LQ
>and it almost ignited a flame war. The reason you are seeing the
>libvdpau_nvidia.so message is that it is hard-coded into libvdpau, and
>your video card is probably not supported by the kernel. I had bought
>an Nvidia G
> Chris, Ozab, orbea, reread my original post, particularly 'I don't even
> have any
> Nvidia hardware,' and I never had on this PC. None what you said has
> anything to do with it.
I did read it and I read it again, this is the first that you mentioned
that you do not have nvidia hardware, but
> It looks more like a nvidia driver problem. Check wheater the dravier
installed correctly.
Yes, the nvidia driver is incorrectly installed. The issue is
specifically that libvdpau_nvidia.so does not exist. I would suggest
removing nvidia, cleaning up any broken symlinks left behind (See the
READ
> “You’re going to have to when 15 is released”? You don’t know that.
> I’ll deal with 15 compatibility when a release candidate is out, not
> before.
I just want to point out that I tried to compile DevIL on current and
found no build issues. I next built it again without issues on a clean
14.2
On Mon, 13 Aug 2018 11:27:22 +1000
Christoph Willing wrote:
> On 12/08/18 00:20, or...@fredslev.dk wrote:
> > Hi,
> >
> > Its been bugging me for a long time that the LibreOffice from source
> > SlackBuild has both incorrect and many missing optional
> > depend
I looked at the 6.1.0.3 source and found two small corrections.
1. LibreOffice can also use lxml and will apparently build it
internally if missing, I am not sure if it needs to be a python3 lxml
or not.
2. With 6.1.0.3 libnumbertext is a new optional dependency which is
missing from SBo, I have
> Ah, patch not actually needed then, thanks.
While restarting the system may of fixed the issue, it was a
non-obvious solution and I think eliminating potential points of
failure is good.
Also while sandbox may be pedantic here, I personally expect that /dev/
won't be touched when running a Slac
Hi,
Its been bugging me for a long time that the LibreOffice from source
SlackBuild has both incorrect and many missing optional dependencies.
The only required dependency is:
perl-Archive-Zip
The following dependencies are erroneously marked as required and
libreoffice will either work fine
Hi,
As reported in the "SBo scripts not building on current" thread at
linuxquestions showed that the tests in the makefile can segfault.
https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/page91.html#post5890532
Neither ponce o
Hi,
I've noticed that the libretro port for snes9x is working upstream and
its possible to use that instead of the snes9x-libretro fork from the
libretro github repo.
Would you be willing to add the libretro build in your script so that
snes9x-libretro can be removed and SBo can then benefit from
Given that you are doing great with Qt5 and that Larry has not even
bothered to reply to your python2-sip comment my suggestion is that you
should maintain Qt5 from this point on. You clearly seem the most
willing and capable.
___
SlackBuilds-users mailin
Hi,
I built capnproto with sandbox from SBo and found it resulted with a
open_wr violation for /etc/ld.so.cache~.
ldconfig < /dev/null > /dev/null 2>&1 || true
* ACCESS DENIED: open_wr: /etc/ld.so.cache~
* --- ACCESS VIOLATION SUMMARY
---
> >I suppose I replied to the wrong thread, but I mentioned I'd be willing
> >to take over system/yash in the "[Slackbuilds-users] Slackbuild patch
> >for luakit 2.1" thread. Though if you really want it I have no issues
> >with you maintaining it instead as long its kept up to date. :)
>
> I reall
Hi,
I noticed that cryptography depends on six, but also depends on
packaging which then depends on six. I think six can be removed from
the REQUIRES in cryptography to avoid listing it twice in the
dependency chain.
___
SlackBuilds-users mailing list
Sl
When I suggested to use upstream's releases instead of the
auto generated ones at github which were causing issues I neglected to
notice that upstream removed old releases... Sorry about that...
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbu
Well I hit a roadblock with Qt-5.11 on 14.2.
With '-system-harfbuzz' it bails on configure because harfbuzz is too
old, with '-qt-harfbuzz' it fails to build late in the ninja stage and
with '-no-harfbuzz' it around the same place with errors indicating it
misses harfbuzz. The obvious solution wou
> Sorry, I forgot to upload the qt5 5.9.2 SlackBuild and .info. Done.
I went to test before you noticed this and found your Qt-5.10.1 script
instead. After many cryptic build failures I was informed that gentoo
never unmasked 5.10 and now considers 5.11 to be stable. So I tried
your script to buil
> Is the problem just that the maintainer's gone missing, or is he
> answering emails and giving out a reason why he won't update the
> build?
My issue is that this is a years old known packaging bug and no one has
bothered to do anything about it despite complaining on numerous
occasions here and
> Maybe you meant this by EOL also, the source mentioned in qt5.info
> has vanished. Sorry if this is already known by everybody, i didn't
> follow the qt discussion yet.
I didn't even notice that yet!
I meant that Qt5 upstream released 5.7.1 in December 14 2016 and will
not update it again.
htt
I just want to point out that when I first started using repology I had
many false positive when looking at my own packages. However most of
these have been solved quickly by e-mailing the repology maintainer
whose e-mail is listed on their site at the bottom of the front page.
Yes, it occurred to me after I hit send that I should of been clearer.
I meant the qt-5.9.* package for current AlienBob maintains. I'll build
it on 14.2 and test that if needed...
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https
Is there any news on updating Qt5? The version 5.7.1 is EOL and has
known security issues that will not be fixed. Slackware is also the
only distro terrible enough to use 5.7.1 according to repology.
https://repology.org/metapackage/qt5/versions
To be blunt, software that will fail with a support
> I really want it if you don't mind.
Go for it!
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
F
I suppose I replied to the wrong thread, but I mentioned I'd be willing
to take over system/yash in the "[Slackbuilds-users] Slackbuild patch
for luakit 2.1" thread. Though if you really want it I have no issues
with you maintaining it instead as long its kept up to date. :)
___
I am willing to maintain system/yash if it requires a new maintainer?
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/
I think the problem is because the SlackBuild is using the github
generated source tarball instead of the real tarball from upstream.
I think the correct solution is to use the source from upstream and
remove the hacks for the github source.
https://yt-dl.org/downloads/2018.06.25/youtube-dl-2018.
Sorry for the slow reply. I lost interest in pushing this when it
became clear that merging a simple patch required more energy than I
had to expend... Take it or leave it, I'm not interested in fighting
over this.
Previous e-mails were written a while ago and with a previous e-mail
address.
_
Below is the original message sent regarding mdocml/mandoc, if you
could please reply it would be very much appreciated. Also note I
put your address in the cc for the related messages to the SBo users
mailing list so you should of received those too?
Hi,
I'm not sure if you
Its been 2 more weeks without a reply, does anyone know what's up?
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/sla
That assumption is irrelevant and if a maintainer is not willing to
respond to bug reports then it should be possible to implement fixes
without the maintainer.
The bottom line is that this patch would make the qt5.SlackBuild more
fail proof and the only reason to not accept it is to spite people
Hi,
I e-mailed a very small patch to the qt5.SlackBuild maintainer more
than once to allow dynamically detecting if pulseaudio is installed with
pkg-config and disabling it if its not. However its been a few weeks
since my last attempt and much longer for the previous ones. I have
received absolut
I am the maintainer of the guix SlackBuild and its optional dependency,
guile-json. However I have suffered deal breaking runtime issues which
may or not be pebkac and an unresponsive upstream. I lack the knowledge
and interest in guile to pursue this further.
So if anyone would be willing to take
Hi,
I am interested in seeing the mdocml updated to the current upstream
version of 1.14.3. Additionally it had since been renamed to mandoc
upstream and should also be renamed for SBo.
I have contacted the maintainer, but I have not received a reply even
though I have waited more than a week. Do
Hi,
I am maintaining the python3-xlib build script which when I first
submitted it was distinct from python-xlib which was already in the
repo. However at some point this changed and python3 support was added
to the main python-xlib upstream. Consequently my requirement for it in
pyewmh and caffei
36 matches
Mail list logo
