Re: [Slackbuilds-users] Download link broken for simple-scan
Niki Kovacs a écrit : Hi, Just tried to build simple-scan on 13.37. The download link is broken. Launchpad must have moved it. OK, I found the reason. They simply moved from http to https, so the download link has to be corrected. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Download link broken for simple-scan
Hi, Just tried to build simple-scan on 13.37. The download link is broken. Launchpad must have moved it. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Changing some odd permissions in a tarball.
On 9/8/12, Dave Margell wrote:
> # change directory permissions (700 to 755) of bin, doc, udiskie
> # as well as the parent directory to allow a user to browse the source
>
> Where I've added an extra "dot" to the "find" command and also added "
> -o -perm 700 "
Is this in a subdirectory of the tarball's dir? For most builds, .. would
refer to /tmp/SBo, which you probably didn't mean...
Sometimes if upstream's tarball has weird permissions, it's best to
ditch the template code and just do something like...
chown -R root:root .
find . -type f -exec chmod 644 {} \; -o -type d -exec chmod 755 {} \;
In general, the template code is there to help you... if it doesn't help,
you're not required to keep it exactly as-is. But if you change it,
especially in a non-obvious way (your find command looks very similar to
the template, someone in a hurry might not notice the changes or might
think it's a typo and "correct" it), it's polite to leave a comment for
the admins so they will know you did it that way for a reason.
I don't speak for the SBo team, I'm just a user. The above is my opinion
based on spending a few years submitting a bunch of builds.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] System-wide addons for Seamonkey and Firefox? (SlackBuilds-users Digest, Vol 76, Issue 3)
On 8.9.2012 01:32, Eric Hameleers wrote: > > I uploaded a language pack SlackBuild for firefox. You can use it to > build a package for any supported language: > http://slackware.com/~alien/slackbuilds/mozilla-firefox-l10n/build/ > > I run "LANG=nl VERSION=15.0 ./mozilla-firefox-l10n.SlackBuild" to build > a firefox language pack. The build directory contains a README.1st which > explains how to enable the new language after installing the language pack. > > Should not be hard to change this into a seamonkey script. > > Eric > > Hi, thanks a lot for that! I was wondering how to add another language to Firefox. I actually thought that mozilla doesn't release language .xpi files anymore. I just want to note that LANG variable doesn't work because provided slackbuild use PKGLANG variable. Otherwise it works fine. Could you please correct that in README? Regards Martin ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] redis can't be built on slackware64 13.37
It looks like the ARCH variable is exported by sbopkg when it is building
the redis package and is being picked up by a Makefile('s). Without
hacking the redis code, one could put 'unset ARCH' in
/etc/sbopkg/sbopkg.conf' and let the slackbuild do its work and figure out
ARCH by itself.
--Larry
On Sat, Sep 8, 2012 at 8:13 AM, Audrius Kažukauskas wrote:
> On Sat, 2012-09-08 at 23:59:25 +0900, crocket wrote:
> > It turned out that redis fails to build within sbopkg.
> >
> > It builds fine on a bare shell.
>
> (Sent my last email before I saw this one.)
>
> Well, that means that sbopkg is setting ARCH var which interferes with
> at least one of redis Makefiles.
>
> --
> Audrius Kažukauskas
> http://neutrino.lt/
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] redis can't be built on slackware64 13.37
On Sat, 2012-09-08 at 23:59:25 +0900, crocket wrote: > It turned out that redis fails to build within sbopkg. > > It builds fine on a bare shell. (Sent my last email before I saw this one.) Well, that means that sbopkg is setting ARCH var which interferes with at least one of redis Makefiles. -- Audrius Kažukauskas http://neutrino.lt/ pgpjEWGx3YXYU.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] redis can't be built on slackware64 13.37
On Sat, 2012-09-08 at 23:16:54 +0900, crocket wrote: > Below is the error log. > > cd src && make all > make[1]: Entering directory `/tmp/SBo/redis-2.4.14/src' > MAKE hiredis > make[2]: Entering directory `/tmp/SBo/redis-2.4.14/deps/hiredis' > cc -std=c99 -pedantic -c -O3 -fPIC -O2 -fPIC -Wall -W > -Wstrict-prototypes -Wwrite-strings -g -ggdb x86_64 net.c > cc: x86_64: No such file or directory > make[2]: *** [net.o] Error 1 > make[2]: Leaving directory `/tmp/SBo/redis-2.4.14/deps/hiredis' > make[1]: *** [dependencies] Error 2 > make[1]: Leaving directory `/tmp/SBo/redis-2.4.14/src' > make: *** [all] Error 2 > > What do I need to do for building redis? I think the problem lies in the following line: redis-2.4.14/deps/hiredis/Makefile:18: REAL_CFLAGS=$(OPTIMIZATION) -fPIC $(CFLAGS) $(WARNINGS) $(DEBUG) $(ARCH) Not sure why $(ARCH) is there, but in your case it's set to 'x86_64' and that gets inserted in compiler line. Try unset ARCH before building redis. -- Audrius Kažukauskas http://neutrino.lt/ pgpmGKVohbQ3y.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Changing some odd permissions in a tarball.
Hi list,
I want to change a bit of our template code to this:
# change directory permissions (700 to 755) of bin, doc, udiskie
# as well as the parent directory to allow a user to browse the source tree.
find .. \
\( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 -o
-perm 700 \) \
-exec chmod 755 {} \; -o \
\( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o
-perm 400 \) \
-exec chmod 644 {} \;
Where I've added an extra "dot" to the "find" command and also added "
-o -perm 700 "
to the list of permissions to change.
Source in question is:
https://bitbucket.org/byronclark/udiskie/downloads/udiskie-0.4.1.tar.gz
Acceptable to the admins or not?
Thanks!
Dave.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] redis can't be built on slackware64 13.37
It turned out that redis fails to build within sbopkg. It builds fine on a bare shell. On Sat, Sep 8, 2012 at 11:16 PM, crocket wrote: > Below is the error log. > > cd src && make all > make[1]: Entering directory `/tmp/SBo/redis-2.4.14/src' > MAKE hiredis > make[2]: Entering directory `/tmp/SBo/redis-2.4.14/deps/hiredis' > cc -std=c99 -pedantic -c -O3 -fPIC -O2 -fPIC -Wall -W > -Wstrict-prototypes -Wwrite-strings -g -ggdb x86_64 net.c > cc: x86_64: No such file or directory > make[2]: *** [net.o] Error 1 > make[2]: Leaving directory `/tmp/SBo/redis-2.4.14/deps/hiredis' > make[1]: *** [dependencies] Error 2 > make[1]: Leaving directory `/tmp/SBo/redis-2.4.14/src' > make: *** [all] Error 2 > > What do I need to do for building redis? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] redis can't be built on slackware64 13.37
Below is the error log. cd src && make all make[1]: Entering directory `/tmp/SBo/redis-2.4.14/src' MAKE hiredis make[2]: Entering directory `/tmp/SBo/redis-2.4.14/deps/hiredis' cc -std=c99 -pedantic -c -O3 -fPIC -O2 -fPIC -Wall -W -Wstrict-prototypes -Wwrite-strings -g -ggdb x86_64 net.c cc: x86_64: No such file or directory make[2]: *** [net.o] Error 1 make[2]: Leaving directory `/tmp/SBo/redis-2.4.14/deps/hiredis' make[1]: *** [dependencies] Error 2 make[1]: Leaving directory `/tmp/SBo/redis-2.4.14/src' make: *** [all] Error 2 What do I need to do for building redis? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Evince and DVI backend
Robby Workman a écrit : You need the shared libkpathsea library from TeXLive 2012. Thanks for the info! Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
