On 3/5/22 18:09, Willy Sudiarto Raharjo wrote:
It's not on the list of failing builds, so does anybody know what this
error means or how to fix?
[974/1281] Generating 404.html with a custom command (wrapped by meson
to capture output)
FAILED: docs/404.html
/usr/bin/meson --internal exe --captur
Robby Workman wrote:
> Reply with which script you want, how you want to be listed in
> the .info file, and what email address you want listed there.
I can take network/snmpsim
Charles Polisher / cpol...@surewest.net
___
SlackBuilds-users m
Well, took me a few seconds to find out it wasn't equalx that was the
problem, but it may crop up some time so not a completely wasted question.
And yeah, I know a rebuild would be necessary for something large, say
Texlive (Which is where the problem lies. Hoo boy! That's going to have
to wait t
Ok, first off this is a rhetorical question. I'm away from my home computer
and will have to research it from there. However, however, if anyone has
any words of wisdom about this, by no means does this question need to be
answerless. (My brain works in horrible ways, and this happens to work for
With regret, voluntary work as a Debian and (cough) Ubuntu sysadmin
leaves me no time to update the xapian-omega and yad SlackBuilds :(
I am un-subscribing from this list so please address any mail to me
directly.
Best
Charles
___
SlackBuilds-users
Howdy! Howdy! Howdy!
I have been using pari and keeping it maintained on my system for quite a
while now, and a few weeks ago went ahead and started using a slackbuild
rather than a simple script to install into my user directory. Well, I
went a head and touched up the slackbuild information and
n upload through the submittal form.
https://dl.dropboxusercontent.com/u/8119425/stuff/vifm.tar.gz
Have a happy!
Charles
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-u
Oddly enough, I had attempted that (USE_LIBVPX=0), which got passed the
first #define USE_LIBVPX, but would fail on the second in game.c. However,
by deleting everything between "#ifdef USE_LIBVPX" to "#endef", then it
compiled just fine.
And even stranger yet, when I copied the backup game.c ove
ot;Debian Based" packages.
The spideroak SlackBuild maintainer has not replied to emails about it
using a superseded .deb download so I have not told them about this news.
Best, Charles
___
SlackBuilds-users mailing list
SlackBui
I use http://slackbuilds.org/slackbuilds/13.37/SLACKBUILDS.TXT to look for
changes in installed slackbuilds. Today, when I did so I noticed that
sshfs-fuse had been updated. When I went to the address listed in
"SLACKBUILD LOCATION: ./network/sshfs-fuse" (i.e.
http://slackbuilds.org/repository/13.3
The network/spideroak package fails because the MD5 sum is incorrect
because the "source" (actually an ubuntu lucid .deb) has been updated.
This was confirmed by spideroak support.
I mailed the maintainer on 14 June but have had no reply.
AFAIK, the version is now 4.6.9945 and the MD5 sum for th
already made most if not all of those changes that
are in the diff.
Unfortunately, I couldn't find anything to explain what the purpose was, so
if you or MR will, could I get a little help in understanding what was
meant by "base your updates on this"?
Thanks.
Charles
On Sat, Jun
t.
Thanks.
Charles
quoting http://slackbuilds.org/ready/
>
> 23-Jun-2012 09:35 vifm
>
> if you plan to submit a newer version, please base your updates on
> this:
>
> http://slackbuilds.org/cgit/slackbuilds/commit/?h=gizzmo&id=2aaa36a6649a5e59ac220cc5f8cb85707b5
Howdy!
There's been a few bugs found in the latest version, and fixes have been
implemented in the current release, but regardless I've decided to wait a
little bit longer to see if any other fixes/changes will happen. So if you
will, please remove it for the time being.
Thank
On 06/05/12 10:53, slackbuilds-users-requ...@slackbuilds.org wrote:
> Date: Fri, 27 Apr 2012 21:00:11 +0200
> From: Matteo Bernardini
> To: "SlackBuilds.org Users List"
> Subject: Re: [Slackbuilds-users] evince SlackBuild problem
> Message-ID:
>
> Content-Type: text/plain; charset=ISO-8859
The evince SlackBuild, run via sbopkg, failed on a newly-installed
Slackware64 13.37 system. It was a default installation of 13.37 except
KDE was de-selected, A variety of layered software had been installed
before running the evince SlackBuild.
I mailed the evince SlackBuild maintainer on 13
On Tue, Feb 7, 2012 at 5:24 AM, Audrius Kažukauskas wrote:
> On Mon, 2012-02-06 at 11:35:53 -0600, Charles Kauffman wrote:
> > 2.
> > In the echinus.SlackBuild
> > sed -i "s;-Os;$SLKCFLAGS ;g" config.mk
> > sed -i "s;.pixmap: ;.pixmap: \/usr\/share\/echi
flag -Os with SLKCFLAGS, as well as had the script
create a doc directory that had the version number appended to it.
The second sed makes modifications to the rc file since problems can occur
when the program loads.
So, does that look good, or should I just leave so
ropbox.com/u/8119425/slackbuilds/vifm/vifm.tar.gz
If Diogo doesn't want to do so I would be more than happy to maintain it.
--
Charles
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listi
19 matches
Mail list logo
