Re: [Slackbuilds-users] SBOPKG: android-tools

[Larry Hajali]

>
> It builds fine here (Slackware64 14.2 with all patches applied).
>

Same.  Builds fine here on Slackware64 14.2.
___
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] calibre will not build

[Larry Hajali]

I'll take a look at it this weekend.  I haven't looked at this for a while
so I will need to troubleshoot.

Thanks,
--Larry

On Tue, Jun 2, 2020 at 9:20 AM Chris Abela  wrote:

> That brings out nothing:
>
> $ grep \/tmp /proc/mounts
>
> $ cat /proc/mounts
> proc /proc proc rw,relatime 0 0
> sysfs /sys sysfs rw,relatime 0 0
> tmpfs /run tmpfs rw,nosuid,nodev,noexec,relatime,size=32768k,mode=755 0 0
> devtmpfs /dev devtmpfs rw,relatime,size=8192k,nr_inodes=1009193,mode=755 0
> 0
> /dev/myvg/root / ext4 rw,relatime,stripe=32736,data=ordered 0 0
> devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0
> tmpfs /dev/shm tmpfs rw,relatime 0 0
> cgroup_root /sys/fs/cgroup tmpfs rw,relatime,mode=755 0 0
> cpuset /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset,clone_children 0 0
> cpu /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0
> cpuacct /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0
> blkio /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0
> memory /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
> devices /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0
> freezer /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0
> net_cls /sys/fs/cgroup/net_cls cgroup rw,relatime,net_cls 0 0
> perf_event /sys/fs/cgroup/perf_event cgroup
> rw,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event
> 0 0
> net_prio /sys/fs/cgroup/net_prio cgroup rw,relatime,net_prio 0 0
> pids /sys/fs/cgroup/pids cgroup
> rw,relatime,pids,release_agent=/run/cgmanager/agents/cgm-release-agent.pids
> 0 0
> fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
> /dev/mapper/myvg-boot /boot ext4 rw,relatime,data=ordered 0 0
> /dev/mapper/myvg-home /home ext4 rw,relatime,data=ordered 0 0
> /dev/mapper/myvg-www /var/www ext4 rw,relatime,stripe=32748,data=ordered 0
> 0
> cgmfs /run/cgmanager/fs tmpfs rw,relatime,size=100k,mode=755 0 0
>
>
>
> On Tue, Jun 2, 2020 at 5:50 PM Matteo Bernardini <
> matteo.bernard...@gmail.com> wrote:
>
>> IMHO you could verify it with a
>>
>> grep \/tmp /proc/mounts
>>
>> Il mar 2 giu 2020, 17:35 Chris Abela  ha scritto:
>>
>>> No Matteo,
>>>
>>> $ ls -ld /tmp
>>> drwxrwxrwt 12 root root 102400 Jun  2 17:29 /tmp/
>>>
>>> I notice that I missed some dependencies as my queue files were
>>> outdated. My building machine is very slow, so please stand-by until I
>>> update you.
>>>
>>> Chris
>>>
>>> On Tue, Jun 2, 2020 at 5:16 PM Matteo Bernardini <
>>> matteo.bernard...@gmail.com> wrote:
>>>
 Seeing that "permissione denied" makes me think that you are trying to
 build it with a /tmp filesystem mounted with a "noexec" option...
 Is that the case?
 If It is, try to export a different TMP for building just calibro.

 Il mar 2 giu 2020, 17:02 Chris Abela  ha scritto:

> I have installed updated packages of all the dependencies but clibre
> will still not build:
>
> ### Building extension podofo ###
>
> ### Building extension pictureflow ###
> Traceback (most recent call last):
>   File "setup.py", line 121, in 
> sys.exit(main())
>   File "setup.py", line 106, in main
> command.run_all(opts)
>   File "/tmp/SBo/calibre-3.34.0/setup/__init__.py", line 242, in
> run_all
> self.run_cmd(self, opts)
>   File "/tmp/SBo/calibre-3.34.0/setup/__init__.py", line 234, in
> run_cmd
> self.run_cmd(scmd, opts)
>   File "/tmp/SBo/calibre-3.34.0/setup/__init__.py", line 238, in
> run_cmd
> cmd.run(opts)
>   File "/tmp/SBo/calibre-3.34.0/setup/build.py", line 278, in run
> self.build(ext, dest)
>   File "/tmp/SBo/calibre-3.34.0/setup/build.py", line 301, in build
> return self.build_pyqt_extension(ext, dest)
>   File "/tmp/SBo/calibre-3.34.0/setup/build.py", line 488, in
> build_pyqt_extension
> with open(os.path.join(src_dir, sip['target'] + '.exp'), 'wb') as
> f:
> IOError: [Errno 13] Permission denied:
> u'/tmp/SBo/calibre-3.34.0/build/pyqt/pictureflow/pictureflow.exp'
> ___
> 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 - 

Re: [Slackbuilds-users] How to Build a Project Based On pyproject.toml for SBo

[Larry Hajali]

Easier solution is just download the tarball from pypi.python.org.  It has
the setup.py file.

https://pypi.python.org/packages/source/t/tinydb/tinydb-4.1.1.tar.gz

--Larry

On Sun, May 24, 2020 at 2:23 AM Jeremy Hansen 
wrote:

> On Sun, May 24, 2020, 3:05 AM Christoph Willing 
> wrote:
>
>> On 24/5/20 3:56 pm, Jeremy Hansen wrote:
>>
>> > To clarify, the developer removed the ability to build this using a
>> > setup.py, so where do I go from there within the SlackBuild?
>> >
>>
>> From:
>> pip install --help
>>
>> I see:
>> --root   Install everything relative to this alternate root
>> directory.
>>
>>
>> chris
>>
>
> Thanks! I just did man pip and didn't notice anything about a root
> directory. I didn't realize I could run hello against pip install. I'll
> give this a shot tomorrow.
>
> Jeremy
>
>> ___
> 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] I failed to build qt5

[Larry Hajali]

>
> I did a rebuild overnight to make sure everything is still working and
> kept a log. Unfortunately, no magical insights from it though.
>
> However, it looks like the c++14 thing was a red herring - I see plenty
> of references to it (including checking for its capability).
>
Yeah, I don't believe this is an issue.


> I noticed that ninja itself (version, whatever) is probably not
> implicated; the configuration finds the system ninja to be too old and
> doesn't use it:
>
> Checking for system ninja...
> Found ninja from path: /usr/bin/ninja
> + /usr/bin/ninja --version
> > 1.10.0
> Ninja version too old
> Building own ninja
>
The upstream qtwebengine repo has a patch that hasn't been back ported it
to a version > 5.12.8 in the 5.12.x branch, which adds logic to pick up
ninja version >= 1.10.x.
https://github.com/qt/qtwebengine/commit/8c1a4841174a90299ba2e2851b4d9e79da3b9b25
Patch attached to pick up newer ninja version.

I also found the area where OP's build failed. No failure here but it is
> interesting that the progress indicator was quite different. In my build
> it was [15020/16427] but for OP it was [641/2162]. I wonder if that
> means different things are being built - leading to question of what the
> configuration discovered on the build machine (therefore determining
> what needed to be built).
>
Same.  Mine failed on [116/2525].  Looking up farther in the build output I
saw the following lines.

FAILED: obj/third_party/blink/renderer/core/core/core_initializer.o
..
virtual memory exhausted: Cannot allocate memory


> My build was on a clean, up to date, VM - nothing else installed except
> the required ninja, python3, meson & libxkbcommon packages.
>
Same.

Original VM had 4GB of RAM and no swap.  I increased it to 8GB of RAM and
that succeeded in less than half the time it took to fail on 4GB of RAM.

--Larry


qt5.SlackBuild.diff
Description: Binary data
From 8c1a4841174a90299ba2e2851b4d9e79da3b9b25 Mon Sep 17 00:00:00 2001
From: Kirill Burtsev 
Date: Fri, 6 Mar 2020 17:38:45 +0100
Subject: [PATCH] Support build with system ninja >= 1.10.0

Fixes: QTBUG-82715
Change-Id: I9a269efa20d092f75a8a43cb20d1e0dc0f46b9f9
Reviewed-by: Michal Klocek 
---
 configure.pri | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure.pri b/configure.pri
index 3a144e3f8..3cfce71e0 100644
--- a/configure.pri
+++ b/configure.pri
@@ -163,7 +163,7 @@ defineTest(qtConfTest_detectNinja) {
 !isEmpty(ninja) {
 qtLog("Found ninja from path: $$ninja")
 qtRunLoggedCommand("$$ninja --version", version)|return(false)
-contains(version, "1.[7-9].*"): return(true)
+contains(version, "1\.([7-9]|1[0-9])\..*"): return(true)
 qtLog("Ninja version too old")
 }
 qtLog("Building own ninja")
___
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] ignition-transport fails to download

[Larry Hajali]

Hi All,

I tried building ignition-transport but got an md5sum error.  The actual
download seems to be an html file.

Found ignition-transport-0.7.0.tar.bz2 in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for ignition-transport-0.7.0.tar.bz2 ... FAILED!
Expected: e7a69c622bf3145bdb7061f13eacd985
Found:fa26e8de4a0b0fe9980d89300222dd86


# file /var/cache/sbopkg/ignition-transport-0.7.0.tar.bz2
/var/cache/sbopkg/ignition-transport-0.7.0.tar.bz2: HTML document, ASCII
text

In the fedora spec file they use the following url.

https://osrf-distributions.s3.us-east-1.amazonaws.com/ign-transport/releases/ignition-transport-0.7.0.tar.bz2

Thanks,
--Larry
___
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 Slackbuild.

[Larry Hajali]

On Tue, Feb 26, 2019 at 5:19 AM Tim Dickson via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:

> On 25/02/2019 22:55, kla...@mixedsignals.ml wrote:
> > On 2019-02-25 16:03, Tim Dickson via SlackBuilds-users wrote:
> >> Just sending this via sbo mailing list in case klaatu didn't get my
> >> email sent a couple of weeks ago..
> >>
> >> Hi Klaatu, any chance of an update to Musescore? The current one is
> >> 3.0.2
>
Current version upstream as of this writing is 3.0.4.


> >> changing the version number, and adding the line
> >> sed -i 's| qmake| qmake-qt5|' build/FindQt5.cmake
> >> just before the "make " lines in the buildscript is all that is
> >> required to make it work with v3.0.2.
>
That didn't have any affect for the build process.

>> Regards, Tim
> >>
> >>
> >
> > Thanks, Tim. I did get your email and did mean to respond.
> >
> > I can't get it to build even with your suggested patch, so I need to
> > dig into why that's not working for me. What version of Qt5 are you
> > building against?
> >
> qt 5.9.7 (SBo version) built with following DOCS=yes PROPRIETARY_CODECS=yes
> graphviz built with gts, qt5 built with optional freetds,  OpenAL,
> libwebp, opus, pcre2, snappy and wayland
> qt5-webkit 5.9.0 with optional libwebp
>
I built qt5 and qt5-webkit with no extra options or optional packages.

I was able to build MuseScore with version 3.0.4 but I did add a lot of
changes to the build script.  Most were superficial but some were setting
new options available in the Makefile.  I am adding an attachment of the
diff between the MuseScore 3.0.4 and 2.1.0.

On a side note.  I was not able to build it with QtWebEngine.  I get an
error that is described here.
https://musescore.org/en/node/281322
and something similar here.
https://musescore.org/en/node/276196

Thanks,
--Larry
diff -Naur MuseScore.orig/MuseScore.SlackBuild MuseScore/MuseScore.SlackBuild
--- MuseScore.orig/MuseScore.SlackBuild	2017-09-23 15:44:05.0 +
+++ MuseScore/MuseScore.SlackBuild	2019-03-03 21:12:02.168982833 +
@@ -3,7 +3,7 @@
 # Maintained by Klaatu at member.fsf dot org
 
 PRGNAM=MuseScore
-VERSION=${VERSION:-2.1.0}
+VERSION=${VERSION:-3.0.4}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}
 
@@ -20,21 +20,6 @@
 PKG=$TMP/package-$PRGNAM
 OUTPUT=${OUTPUT:-/tmp}
 
-set -e
-
-rm -rf $PKG
-mkdir -p $TMP $PKG $OUTPUT
-cd $TMP
-rm -rf $PRGNAM-$VERSION
-tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
-cd $PRGNAM-$VERSION
-chown -R root:root .
-find -L . \
- \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
-  -o -perm 511 \) -exec chmod 755 {} \; -o \
- \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
-  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
-
 if [ "$ARCH" = "i586" ]; then
   SLKCFLAGS="-O2 -march=i586 -mtune=i686"
   LIBDIRSUFFIX=""
@@ -44,26 +29,54 @@
 elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
   LIBDIRSUFFIX="64"
-  #must hardcode arch or it fails as 32bit
-  sed -i 's|m32|m64|' ./CMakeLists.txt
 else
   SLKCFLAGS="-O2"
   LIBDIRSUFFIX=""
 fi
 
-  make release PREFIX=/usr CFLAGS="$SLKCFLAGS" CXXFLAGS="$SLKCFLAGS" LDFLAGS="-pthread"
-  make install PREFIX=/usr DESTDIR=$PKG UPDATE_CACHE=FALSE
+set -e
 
-mkdir -p $PKG/usr/man/man1
-mv $PKG/usr/share/man/* $PKG/usr/man/
-rm -rf $PKG/usr/share/man
+rm -rf $PKG
+mkdir -p $TMP $PKG $OUTPUT
+cd $TMP
+rm -rf $PRGNAM-$VERSION
+tar xvf $CWD/$PRGNAM-$VERSION.tar.gz
+cd $PRGNAM-$VERSION
+chown -R root:root .
+find -L . \
+ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
+  -o -perm 511 \) -exec chmod 755 {} \; -o \
+ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
+  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
-find $PKG/usr/man -type f -exec gzip -9 {} \;
-for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done
+# Copy over sound files for installation.
+cp $CWD/MuseScore_General-License.md share/sound
+cp $CWD/MuseScore_General.sf3 share/sound
+
+# Turn off Qt crash reporter.  Option isn't available in Makefile,
+# so turn it off in CMakeLists.txt
+sed -i '/(BUILD_CRASH_REPORTER/s|ON)|OFF)|' CMakeLists.txt
+sed -i 's|share/man|man|' CMakeLists.txt
+
+make release \
+  PREFIX=/usr \
+  CFLAGS="$SLKCFLAGS" \
+  CXXFLAGS="$SLKCFLAGS" \
+  LDFLAGS="-pthread" \
+  DOWNLOAD_SOUNDFONT=OFF \
+  USE_SYSTEM_FREETYPE=ON \
+  BUILD_WEBENGINE=OFF \
+  VERBOSE=1
+make install \
+  -C build.release \
+  DESTDIR=$PKG \
+  UPDATE_CACHE=FALSE
 
 find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \
   | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true
 
+find $PKG/usr/man -type f -exec gzip -9 {} \;
+
 mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
 cp -a  LICENSE.* README.md $PKG/usr/doc/$PRGNAM-$VERSION
 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
diff -Naur MuseScore.orig/MuseScore.info MuseScore/MuseScore.info
--- MuseScore.orig/MuseScore.info	2017-09-23 15:44:05.0 +

Re: [Slackbuilds-users] qt5 is sorely in need of an update

[Larry Hajali]

Go ahead.  I have no problem giving up qt5, qt5-webkit and PyQt5.  I don't
have time right now to test big packages like qt5.

--Larry

On Tue, Jul 31, 2018 at 2:57 PM David Woodfall  wrote:

> On Wednesday 25 July 2018 08:57,
> or...@fredslev.dk  put forth the proposition:
> > 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.
>
> I have no problem with doing Qt5 and PyQt5 is Larry doesn't want to
> keep them updated.
>
> --
>
> .--.  oo
>()//
> ~'
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt5 is sorely in need of an update

[Larry Hajali]

>
> The only issue I had was finding a more up-to-date Qt5-webkit because
> there only seems to be some rc version for 5.9 at the location in
> the original .info, so I used my build of the fork by annulen. 5.7.1
> wouldn't build. Unless you know of a link to an upstream release of
> 5.9.x?
>
I used this one.

https://download.qt.io/community_releases/5.9/5.9.0-final/qtwebkit-opensource-src-5.9.0.tar.xz
___
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 is sorely in need of an update

[Larry Hajali]

>
> Have a look at:
>
> https://www.riverbankcomputing.com/pipermail/pyqt/2018-June/040421.html
>
> which talks about new releases of PyQt using a private copy of the sip
> module. I haven't thought deeply into the ramifications but perhaps that
> would ease the problem of old sip in 14.2.
>
Interesting.  That might be a solution.  I can take a look at that.

--Larry
___
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 is sorely in need of an update

[Larry Hajali]

On Tue, Jul 3, 2018 at 11:03 AM B Watson  wrote:

> On 7/3/18, or...@fredslev.dk  wrote:
> >
> > When programs I use will soon no longer support releases older than
> > 5.9 I can not complain to them that it will no longer build in
> > Slackware because by all means we should of updated literally years
> > ago...
>
> You (or whoever) could submit a qt59 or qt5-new or something like that,
> and the stuff that requires qt 5.9 or newer could list that as a dep.
>
> That, or if the old qt5 maintainer's OK with the change, rename the
> existing qt5 to qt5-legacy and someone can submit a new qt5 build and
> keep it up to date. Anything that won't build with the new qt5 has the
> dep changed to qt5-legacy (more work that the previous option).
>
> 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?
>
I'm here and I did respond if you look at this email chain.

Issue is that newer PyQt5 versions rely on a newer version of sip that
comes with Slackware 14.2.  Last I remember someone was going to look at
packaging a newer sip pacakge that can either replace or run alongside the
stock sip package in Slackware 14.2.  I don't have time to investigate this.

If the ultimate goal is to have a new version of qt5, than someone can
create a package called qt59 or whatever to satisfy a dependency.  If
someone does take over qt5 and upgrade then it would be up to them to make
sure the dependencies work after the update.  Upgrading a package like qt5
is a big ask as it is a big package itself to compile and there are
multiple dependencies to test.

--Larry
___
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 is sorely in need of an update

[Larry Hajali]

On Fri, Jun 1, 2018 at 9:32 PM, David Woodfall  wrote:

> On Saturday 2 June 2018 05:26,
> Dave Woodfall  put forth the proposition:
> > On Saturday 2 June 2018 11:16,
> > Willy Sudiarto Raharjo  put forth the
> proposition:
> > > > I asked about this a couple of weeks ago, but eg qutebrowser is
> > > > designed for features in the latest qtwebengine and I would like to
> > > > supply a qt5 version that is up-to-date, or at least qt 5.10.1
> > > > anyway.
> > > >
> > > > I've been running 5.10.1 since around the time it was released with
> > > > no issues at all.
> > >
> > > If i recalled correctly, it has something to do with sip package
> shipped
> > > with Slackware which doesn't meet the minimum requirement for newer
> > > PyQt5 which relies on Qt5-webkit and eventually Qt5 package.
> >
>
Yes, this is the reason qt5 hasn't been updated.  PyQt5 can only be updated
to
5.7 because the sip package is too old for new PYQt5 packages.


> > Ah right. Qutebrowser uses python3-sip/python3-PyQt5 so I haven't hit
> > that problem.
> >
> > How about a separate sip package for python2 that can co-exist with
> > the stock version? It may be possible.
> >
>
Possibly, however, I don't have the time to investigate this.  If someone
wants to
own that investigation and create a package, than I'm more than happy to
update
qt5/PyQt5 packages.

--Larry
___
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 + pulseaudio

[Larry Hajali]

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 absolutely 0 replies.
>
I only see one email from you in my inbox on April 22.  I haven't replied
as I started a new job and life has gotten in the way.

Can this be done? I've attached the patch to this e-mail.
>
I'll look at the patch this weekend.

--Larry
___
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] Kodi and ffmpeg

[Larry Hajali]

On Wed, Feb 7, 2018 at 10:41 PM, King Beowulf  wrote:

> On 02/04/2018 06:54 AM, Daniel Stein wrote:
> > Doesn't the Kodi build use it's own ffmpeg for the build?
> >
> > On Feb 3, 2018 10:34 PM, "King Beowulf"  > > wrote:
> >
> > The kodi Slackbuild states:
> >
> > # The version of ffmpeg on SBo is too old to compile kodi
> >
> > and provides ffmpeg-3.1.11 however SBo provides ffmpeg-3.2.4
> >
> > -Ed
> >
>
> Maybe I was too terse: the version of ffmpeg supported by the kodi
> script maintainer is older than the one provided by the script to
> compile kodi.  The comment in the build script is now misleading.  It is
> NOT that SBo ffmpeg is too old, rather that kodi devs REQUIRE a
> ffmpeg-3.1.x as they have patched it for kodi "krypton"
>
> Yes, the message is the README is old and I haven't updated/removed it.
The main thing is that I don't really support that option and I haven't
tried building Kodi with SBo ffmpeg in the build script even though it is
still there.  The maintainers of Kodi highly recommend their version of
ffmpeg.

I can test it if it works but not sure if I want to support that option.

Thanks,
--Larry


> Whether ffmpeg upstream is aware of these patches, I'm too tired to
> research...
>
> -Ed
>
>
>
>
> ___
> 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] libass ABI changes

[Larry Hajali]

I updated kodi to 17.6 and it built fine against libass 0.14.0.

--Larry

On Sat, Jan 6, 2018 at 3:12 PM, Edinaldo  wrote:

>
> Hi people,
>
> For your knowledge, QMPlay2 builds and works fine with libass 1.4.0.
>
> Cheers,
>
> Edinaldo.
>
> ___
> 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] Calibre and Gourmet revisited

[Larry Hajali]

Hi Len,

On Mon, Aug 14, 2017 at 9:11 AM, Lenard Spencer 
wrote:

> In working with calibre, I found that the new versions (3.5 and newer)
> have another dependency, httml5-parser (also written by Kavid Goyal), which
> doesn't have a SB script in the repo.  I have created a script for it, and
> now I can get calibre to buid and run on my system.  Shoiuld I go ahead and
> submit it to SBo?  I'm sure Larry (the maintainer of the calibre SBo) would
> be especially interested in it.  I have tested in both 14.2 and current and
> have had no problems on either (other than having to rebuild EVERYTHING on
> current because of other package upgrades).
>
> No need.  I've already updated the repo and it is in the approved queue.
Calibre is also updated as well to 3.6.0.

--Larry


> With Gourmet, I found that the patched script that is currently in Ponce's
> repo is necessary to fix a problem that makes it impossible to enter or
> edit recipes.  Earlier I had thought it was an issue with Python itself,
> but it really lies with the upgrade of the python image library (from PIL
> in 14.1 to pillow in 14.2).
>
> Hope this helps.
>
> Len
>
>
> ___
> 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] Installing Python packages

[Larry Hajali]

On Fri, Jul 14, 2017 at 9:14 AM, Rich Shepard 
wrote:

>   I installed the Python packages virtualenv, virtualenvwrapper,
> virtualenv-clone and their dependencies (e.g., tox, py, pluggy, stevedore)
> and they're all in /usr/lib/python2.7/site-packages/.
>
> I don't know about all of the packages above but I think virtualenv comes
with python3.


>   While I keep python2 installed for those applications built against it
> all
> my new projects use python3 and I want to install/move all the above to
> /usr/lib/python3.6/site-packages/ on this host.
>
>   Looking at the virtualenv.SlackBuild script I see that it calls python
> setup.py install.
>
>   Should I remove all these packages, modify each build script to specify
> python3, rebuild, and reinstall each one, or is there an easier way?
>
Rich
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] html5lib

[Larry Hajali]

Hi,

I've been busy the past couple of weeks with life/work.  I'll look at
html5lib this week.

--Larry

On Thu, Jul 6, 2017 at 3:53 PM, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > I tried emailing the html5lib maintainer a few months back about an
> update,
> > which is required for one of my builds, but didn't get a response. I'm
> > attaching a patch for version 0.9 (two more 9s than we currently
> have)
> > and have also submitted python-webencodings for inclusion.
> >
> > Any chance of getting this applied?
>
> Larry is an active maintainer, so hopefully he will see this email soon
> enough.
>
> FYI, i have python-webencodings approved on my branch
>
> --
> Willy Sudiarto Raharjo
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Qt 5.9 LTS released

[Larry Hajali]

> unfortunately I am not optimistic that soon for Qt, sbo will run a sane
>>> version politic,
>>> The current maintainer showed more or less that he/she does not care to
>>> much and/or does not understand why a LTS version strategy is the right
>>> thing for a distribution like Slackware.
>>>
>> All I'll say about this is that the above is a bogus statement!


> That will have to be decided by qt5 maintainer (Larry)
>> My suggestion (suppose we bump to 5.9) is to place them on -review
>> branch first and see if other scripts are working fine with it. If it
>> turns out to be OK, we can then merge it into master and 14.2.
>>
> I don't plan on upgrading Qt5 past the 5.7.X branch for Slackware 14.2.  I
like to keep PyQt5 around the same version as Qt5.  Unfortunately, PyQt5
5.7.1 requires sip 4.19 or above.  I can look at upgrading for -current but
I don't see it happening for 14.2.


> based on rough count, we have more than 60 other scripts depending on
>> qt5 for hard dep and probably more with optional dep. That will take
>> some time to test.
>>
> This is true.  It takes a while to go through all the builds that depend
on Qt5.

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

Re: [Slackbuilds-users] dolphin-emu nvidia-cg-toolkit dependency

[Larry Hajali]

done

On Mon, Apr 10, 2017 at 7:22 AM, Doogster  wrote:

> Heads up that the nvidia-cg-toolkit needs to be removed from
> dolphin-emu's "requires" list.
>
> I did notify the maintainer, and I expect he'll get to it soon.
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] update link in qt5.info

[Larry Hajali]

It works here.

$ wget
http://download.qt.io/official_releases/qt/5.7/5.7.1/single/qt-everywhere-opensource-src-5.7.1.tar.xz
--2017-03-13 21:24:01--
http://download.qt.io/official_releases/qt/5.7/5.7.1/single/qt-everywhere-opensource-src-5.7.1.tar.xz
Resolving download.qt.io (download.qt.io)... 77.86.229.90
Connecting to download.qt.io (download.qt.io)|77.86.229.90|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location:
http://qt.mirrors.tds.net/qt/archive/qt/5.7/5.7.1/single/qt-everywhere-opensource-src-5.7.1.tar.xz
[following]
--2017-03-13 21:24:02--
http://qt.mirrors.tds.net/qt/archive/qt/5.7/5.7.1/single/qt-everywhere-opensource-src-5.7.1.tar.xz
Resolving qt.mirrors.tds.net (qt.mirrors.tds.net)... 64.50.236.217
Connecting to qt.mirrors.tds.net (qt.mirrors.tds.net)|64.50.236.217|:80...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 337124364 (322M) [application/x-xz]
Saving to: ‘qt-everywhere-opensource-src-5.7.1.tar.xz’

qt-everywhere-opensource-src-5.7.1.t
100%[=>]
321.51M   903KB/sin 6m 40s

2017-03-13 21:30:42 (823 KB/s) -
‘qt-everywhere-opensource-src-5.7.1.tar.xz’ saved [337124364/337124364]

$ md5sum qt-everywhere-opensource-src-5.7.1.tar.xz
7524ffba849d867f673155ec91bc  qt-everywhere-opensource-src-5.7.1.tar.xz

On Mon, Mar 13, 2017 at 7:37 PM, Nate Bargmann  wrote:

> I set out to build qt5 and could not download the file using the link on
> the Web page.  Seems that the qt.io site only works with https now.  I
> verified the failure and success with wget.
>
> A git diff from Git is attached.
>
> - Nate
>
> --
>
> "The optimist proclaims that we live in the best of all
> possible worlds.  The pessimist fears this is true."
>
> Ham radio, Linux, bikes, and more: http://www.n0nb.us
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Stellarium-0.15.x, qt-5.7.x and libinput

[Larry Hajali]

On Tue, Jan 31, 2017 at 2:36 PM, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > Installing libinput fixes the stellarium error which then runs normally.
> >  I recommend the following:
> > 1. bump stellarium to 0.15.1
> > 2. mention that libinput is required as a run time dependency.
> > 3. on qt5 page, move libinput to "required" or "optional" as a run time
> > dependency for Qt5 plugin xcb (libqxcb.so)
> > 4. on qt5 page fix libinput (not available at slackbuilds.org) since it
> > is available.
>
> I agree with adding libinput as a mandatory dep for qt5.
>
why?
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] qt 5.7.1 update test [was: qt5 fails to build]

[Larry Hajali]

>
> Qt5 5.7.1 builds fine on my side.
>
> The following packages build fine and seem to work correctly:
> - qbs-1.7.1 (commit 5db00d0f1f514317f08222b93aebc32fced7608e)
> - qt-creator-4.2.1 (commit d5a61b975a8b647415ce54f5f7021310bbdab4d3)
> - wireshark-2.2.4 (commit 46266ba0fb01c448aaa5b7d32028a3ad61da9905)
>
> The following packages build fine, but running them was not tested:
> - converseen-0.9.6 (commit dda7d73e9437d6a1847be4e6cbb5d031d5a3f6a8)
> - PyQt5-5.7 (commit 6f637b3d4b40ef8e583e0085731d66e00359)
> - qt5-webkit-5.7.1 (commit 93967a67521e0f3fe12cb41ae03ac0886b6a829d)
> - calibre-2.77.0 (commit 71c16c20037fdc740f5f9806c22dc6be1f4a9f08)

I built calibre and it initially failed with this error.
https://bbs.archlinux.org/viewtopic.php?pid=1547092#p1547092
But after rebuilding PyQt5 and then calibre again it worked fine.

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

Re: [Slackbuilds-users] zim wiki crashes, python 2.7.13 update

[Larry Hajali]

The new version of python also affects building qt5.

Updating projects from gyp files...
Traceback (most recent call last):
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/tools/buildscripts/gyp_qtwebengine",
line 178, in 
sys.exit(gyp.main(args))
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/__init__.py",
line 538, in main
return gyp_main(args)
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/__init__.py",
line 514, in gyp_main
options.duplicate_basename_check)
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/__init__.py",
line 130, in Load
params['parallel'], params['root_targets'])
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/input.py",
line 2759, in Load
check, generator_input_info)
  File
"/tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtwebengine/src/3rdparty/chromium/tools/gyp/pylib/gyp/input.py",
line 596, in LoadTargetBuildFilesParallel
parallel_state.pool = multiprocessing.Pool(multiprocessing.cpu_count())
  File "/usr/lib64/python2.7/multiprocessing/__init__.py", line 232, in Pool
return Pool(processes, initializer, initargs, maxtasksperchild)
  File "/usr/lib64/python2.7/multiprocessing/pool.py", line 138, in __init__
self._setup_queues()
  File "/usr/lib64/python2.7/multiprocessing/pool.py", line 233, in
_setup_queues
from .queues import SimpleQueue
  File "/usr/lib64/python2.7/multiprocessing/queues.py", line 48, in

from .synchronize import Lock, BoundedSemaphore, Semaphore, Condition
  File "/usr/lib64/python2.7/multiprocessing/synchronize.py", line 59, in

" function, see issue 3770.")
ImportError: This platform lacks a functioning sem_open implementation,
therefore, the required synchronization primitives needed will not
function, see issue 3770.

--Larry

On Fri, Jan 6, 2017 at 9:28 AM, Brenton Earl 
wrote:

> On Fri, Jan 06, 2017 at 04:34:41PM +0700, Willy Sudiarto Raharjo wrote:
> > > Zim wiki seems to crash with the recent update to python 2.7.13.  There
> > > is a work around to launch Zim:
> > >
> > >> zim --standalone
> > >
> > > A bug report has been filed upstream here:
> > >
> > > https://bugs.launchpad.net/zim/+bug/1618410
> > >
> > > I attached the error message to this email.  Reproduced in a fresh
> > > virtual machine of Slackware x86 and x86_64 14.2.  Can anyone else
> > > reproduce this?  Any suggestions are welcome.
> >
> > Works on current machine with same Python 2.7.13
> > probably a bug caused by the way Python was compiled? (UCS-2 vs UCS-4)
> >
>
> In short, rebuild python 2.7.13 and this problem will be fixed.  Remove
> your $HOME/.config/zim and $HOME/.cache/zim.  Start zim as normal.
>
> The issue lies in the python multiprocessing module.  Zim is unable to
> start up because it cannot import the required module.
>
> The following will return the import error:
>
> > python -c "from _multiprocessing import SemLock"
>
> This problem can be seen if you run zim in debug mode during the first
> launch of the application.  See attached log.
>
> Thanks,
> Brenton Earl
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] wrong md5sum for lxml-3.7.1.tar.gz

[Larry Hajali]

This has been fixed in Willy's branch.  It will be available in the next
update.

https://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr=bfd7f4fd196469eb6b575e3c5bc961224685c699

--Larry

On Thu, Jan 5, 2017 at 4:01 PM, chytraeu  wrote:

>
> hello,
> while downloading lxml-3.7.1.tar.gz I'm repeatedly getting the wrong
> md5sum.
>
> 2017-01-05 17:56:40 (243 KB/s) - ‘lxml-lxml-3.7.1.tar.gz’ saved
> [925193/925193]
>
> Found lxml-lxml-3.7.1.tar.gz in /var/cache/sbopkg/distfiles.
> Checking MD5SUM:
>   MD5SUM check for lxml-lxml-3.7.1.tar.gz ... FAILED!
> Expected: 1fd1051aa08437f54d1e18c3b80342b
> Found:e1fd1051aa08437f54d1e18c3b80342b
>
>
> ---
> Regards,
> Donald Cooley
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] imapfilter maintainer

[Larry Hajali]

>
> ./libraries/html5lib
>
I can take this one.

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

Re: [Slackbuilds-users] qt5.Slackbuild segmenation error

[Larry Hajali]

I'm not familiar with that error.  It works for me with Slackware64 full
install.  Trying to google the error message didn't pull up much
information.

--Larry

On Thu, Oct 20, 2016 at 6:55 AM, Chris Abela  wrote:

> I have new and default x86_64 Slackware 14.2 installation. qt5 does not
> build. The last 50 lines of my build logs may be found here:
>
> http://pastebin.com/Y4EGGMYB
>
> I do not need qt5 but I thought that you would want to know.
>
> Chris
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Early notification for new libwebp

[Larry Hajali]

qt5 is another package if built against optional libwebp dependency.

--Larry

On Sun, Sep 18, 2016 at 6:00 PM, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> Hi all
>
> This email act as an early notification for those installing libwebp and
> or packages that depends on libwebp.
>
> An updated libwebp has been approved in my branch and soon it will be
> merged to master in the next public update.
>
> Upgrading to the new version will require you to rebuilt all packages
> that depends on libwep. Here are the list of the packages that have
> first level hard dep of libwebp:
> games/unvanquished
> graphics/openimageio
> graphics/vips
> libraries/webkit2gtk
> libraries/webkitgtk
> libraries/webkitgtk3
> multimedia/vlc
>
> there are so many packages that depends on some of the libraries
> mentioned above, so there could be more packages affected.
> If you have a working packages suddenly no longer work after upgrading
> libwebp, rebuilding all deps will be your first options before reporting
> a bug in the list.
>
> Thanks
>
> --
> Willy Sudiarto Raharjo
>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Missing requirement for kodi

[Larry Hajali]

It is listed in the requirements as dcadec.

--Larry

On Sun, Aug 28, 2016 at 9:12 PM, Daniel Prosser  wrote:

> Hi everyone / kodi maintainer,
>
> When trying to update kodi to version 16.1, I got an error about libdcadec
> not
> being found. Apparently dcadec should be listed as a requirement for this
> new
> version.
>
> Dan
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] tmw source is missing

[Larry Hajali]

Hi,

I tried building tmw and it failed to download.  The sources have been
deleted from sourceforge and moved to either github or gitorious.  I'm not
sure which, but the files download page on sourceforge does give a readme.

https://sourceforge.net/projects/themanaworld/files/

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

Re: [Slackbuilds-users] Orphaned slackbuilds.....

[Larry Hajali]

>
> * eyeD3
> * fdkaac
> * physfs
>
 I can take these.

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

Re: [Slackbuilds-users] Preferred way of configuring daemon that takes command line arguments only as its configuration step

[Larry Hajali]

>
>
> My question is, what is the preferred way of configuring such a daemon,
> that only takes command line arguments for its configuration?
>
> The two possibilities I'm thinking of are:
> 1. put the configuration variables directly into the /etc/rc.d/rc.daemon
> script
> 2. put the configuration variables into /etc/daemon.conf file and later on
> source the file from within /etc/rc.d/rc.daemon
>
> Which way to go?

When I'm writing a daemon file and there is no default location that the
program puts the configuration file then I put it into /etc/default and
source it there from the rc file.

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

Re: [Slackbuilds-users] Texstudio is failing to build

[Larry Hajali]

Hi Willy,

Patch looks fine.  Its only a version bump.

Thanks,
--Larry

On Thu, Jul 14, 2016 at 6:55 PM, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> >> Texstudio is failing to build with Qt5 5.6.1.
> >> However, a newer Texstudio version has built successfully with Qt5.
> >> Please check the attached patch.
> >
> > Hi Andre
> > i think it requires qt5-webkit if you want to build the GUI using Qt5
>
> Nope, it still failed to build with qt5-webkit, so i applied your patch
> and it seems to build fine (it's still building at the moment).
>
> Larry, what do you think? can i apply this patch?
>
> --
> Willy Sudiarto Raharjo
>
>
___
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] Request: recent version of Calibre

[Larry Hajali]

I already have an updated calibre slackbuild.  I'm just waiting to test it
a little more when I have time.

--Larry

On Tue, Jul 12, 2016 at 11:59 PM, Gwenhael Le Moine <
gwenhael.le.mo...@gmail.com> wrote:

> or repackage the official build with my SlackBuild :
> https://github.com/cycojesus/slackbuilds/tree/master/xap/calibre
>
> 2016-07-13 8:49 GMT+02:00 Jeremy Hansen :
> > If you're interested, Eric has 2.61 available.
> >
> > http://www.slackware.com/~alien/slackbuilds/calibre/build/
> >
> >
> > On Wed, Jul 13, 2016, 2:45 AM Nicolas Kovacs  wrote:
> >>
> >> Hi,
> >>
> >> The current stable version of Calibre (e-book management software) is
> >> 2.62, but SBo only offers a very old version, 1.48. Maybe the maintainer
> >> can offer an upgrade?
> >>
> >> Cheers,
> >>
> >> Niki
> >> --
> >> Microlinux - Solutions informatiques durables
> >> 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 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/
>
>
___
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] qt5 5.5.1 fails to build with multiple jobs

[Larry Hajali]

Matteo, go ahead and add the additional upstream patch.

Willy, I don't have a lot of time to test 5.6.0.  So, I won't don't see
5.6.0 getting into the repo anytime soon.

--Larry

On Wed, Mar 16, 2016 at 6:03 AM, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > Larry, thanks a lot for the patch! I just tested it and everything went
> fine.
> > if it's ok for you I will push it to our git grabbing the occasion to
> > include another small fix related to some other report we got (already
> > applied to the upstream git), regarding video cropping when using vlc
> > built over qt5 (verified also here): I just grabbed the patch from
> > Eric's vlc build directory.
> > I attach the diff waiting for your confirmation.
>
> and now Qt 5.6 is officially released
>
> any thought we should stick to 5.5 or try to update to 5.6 ?
>
>
> --
> Willy Sudiarto Raharjo
>
>
> ___
> 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] qt5 -master and wayland optional dep

[Larry Hajali]

>
> README for qt5 SlackBuild tells that *wayland* is optional dep, but not
> available at SBo.
>
> However, we have *wayland* at SBo in libraries category.
>
> Is it a different "wayland" that we have or should the README be corrected
> to say that "wayland" is actually available at SBo?

Well, Wayland wasn't available at the time when I first submitted the qt5
slackbuild.  The README included in the qt5 source code says Wayland is an
optional dependency.  I don't see where it is auto detected by the
configure script but I do see it being called.  So, I guess the README
could be updated to say Wayland is now just an optional dependency.

--Larry
___
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] qt5 5.5.1 fails to build with multiple jobs

[Larry Hajali]

So, I was able to recreate the issue Matteo posted on
http://pastebin.com/6QcYEQVE using all optional dependencies and adding
DOCS and EXAMPLES as yes.  Fortunately, I was able to create a patch that
compiles qt5.

The short answer of why it fails on Slackware -current is that the newer
mozilla-nss package now defines CKM_NSS_CHACHA20_POLY1305
and CK_NSS_AEAD_PARAMS.  They were originally defined in ssl3con.c if
CKM_NSS_CHACHA20_POLY1305 wasn't defined.  Also the nonce and nonce length
for CK_NSS_AEAD_PARAMS, which were pIv and ulIvLen, are now renamed pNonce
and ulNonceLen, respectively, in /usr/include/nss/pkcs11n.h.
I'm still building qt5 but it is past the point where the error happens.
I'm providing a patch to account for the updated headers in mozilla-nss
package.

Note that this patch won't work on Slackware 14.1.

--Larry

On Tue, Mar 15, 2016 at 11:36 AM, Willy Sudiarto Raharjo <
will...@slackbuilds.org> wrote:

> > That's the easy part.
> >
> > The difficult part is to find which other packages will fail if
> > qtwebengine is not built, and how to fix them.
> >
> > If we can't do that quickly and easily, then it might be easier to fix
> > qtwebengine.
>
> and FYI, here are the packages that directly requires qt5
>
> academic/stellarium
> academic/ugene
> audio/acousticbrainz-gui
> audio/qjackctl
> desktop/lumina
> desktop/qmapshack
> desktop/rss-guard
> development/fuel
> development/qt-creator3
> development/zeal
> games/dustrac
> games/peg-e
> games/solarus-quest-editor
> games/vcmi
> graphics/fritzing
> graphics/luminance-hdr
> graphics/photoqt
> graphics/phototonic
> graphics/qelectrotech
> graphics/scantailor
> libraries/poppler-qt5
> libraries/python3-PyQt5
> libraries/qmltermwidget
> multimedia/obs-studio
> multimedia/xvst
> network/cmst
> network/otter
> network/qTox
> network/wireshark
> office/sigil
> system/zuluCrypt
>
> it doesn't count packages that optionally depends on qt5
>
>
> --
> Willy Sudiarto Raharjo
>
>
> ___
> 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/
>
>
>
diff -Naur qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_decrypter_nss.cc qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_decrypter_nss.cc
--- qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_decrypter_nss.cc	2015-10-13 04:36:54.0 +
+++ qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_decrypter_nss.cc	2016-03-15 11:57:53.898988200 +
@@ -66,9 +66,9 @@
AeadParams* aead_params) const {
   aead_params->len = sizeof(aead_params->data.nss_aead_params);
   CK_NSS_AEAD_PARAMS* nss_aead_params = _params->data.nss_aead_params;
-  nss_aead_params->pIv =
+  nss_aead_params->pNonce =
   reinterpret_cast(const_cast(nonce.data()));
-  nss_aead_params->ulIvLen = nonce.size();
+  nss_aead_params->ulNonceLen = nonce.size();
   nss_aead_params->pAAD =
   reinterpret_cast(const_cast(associated_data.data()));
   nss_aead_params->ulAADLen = associated_data.size();
diff -Naur qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_encrypter_nss.cc qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_encrypter_nss.cc
--- qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_encrypter_nss.cc	2015-10-13 04:36:54.0 +
+++ qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_encrypter_nss.cc	2016-03-15 11:57:53.902988200 +
@@ -66,9 +66,9 @@
AeadParams* aead_params) const {
   aead_params->len = sizeof(aead_params->data.nss_aead_params);
   CK_NSS_AEAD_PARAMS* nss_aead_params = _params->data.nss_aead_params;
-  nss_aead_params->pIv =
+  nss_aead_params->pNonce =
   reinterpret_cast(const_cast(nonce.data()));
-  nss_aead_params->ulIvLen = nonce.size();
+  nss_aead_params->ulNonceLen = nonce.size();
   nss_aead_params->pAAD =
   reinterpret_cast(const_cast(associated_data.data()));
   nss_aead_params->ulAADLen = associated_data.size();
diff -Naur qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c
--- qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c	2015-10-13 

Re: [Slackbuilds-users] Next Round of Testing

[Larry Hajali]

>
> here are the remaining entries of the BUILD FAIL from last week
>
>   desktop/rsl
>
 rsl - https://github.com/larryhaja/SBo/pull/2

>
  graphics/fontmatrix
>
 fontmatrix - https://github.com/larryhaja/SBo/pull/1

>
>   libraries/gwenhywfar
>
gwenhywfar - https://github.com/larryhaja/SBo/pull/3

>
  multimedia/subtitleeditor
>
 subtitleeditor - works with updates in ponce's repo

I haven't had a lot of time to go over all of the failed builds in the list
but here is what I did to get them to build.
___
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] Next Round of Testing

[Larry Hajali]

>
> >   games/dolphin-emu
>
> I've pushed an update for this on my branch: maybe Larry should want
> to have a look at this but for the little testing I have done it seems
> to work.
>
> Looks good.
___
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] Support for Python 3 in python-pillow?

[Larry Hajali]

I've been on the fence about adding that auto-detection in my python
slackbuilds.  Some people think that this should be an option set at build
time to add python3 support by using a variable.

Eg.

if ["${PYTHON3SUPPORT:-no}" == "yes" ]; then

  python3 setup.py install --root=$PKG

fi


I'm not opposed to that, but I'm also not sure how to handle packages that
put files in /usr/bin directory (like python-pillow) for python2 and
python3 scripts.  If python3 files are built after python2 files, then
everything in /usr/bin/* will have a shebang with #!/usr/bin/python3.  I'm
not sure that is a desired outcome.

It may be best to create a second python3 package for python-pillow and
possibly other python slackbuilds that support python3 to avoid file
conflicts.

Thanks,
--Larry

On Sun, Dec 13, 2015 at 11:23 AM, Philip Lacroix  wrote:

> Greetings
>
> I wonder if something like the following test could be added to
> python-pillow.SlackBuild, in order to automatically add support for Python3
> if the latter is installed:
>
>  python setup.py install --root=$PKG
>>
>> + if $(python3 -c 'import sys' 2>/dev/null); then
>> +  python3 setup.py install --root=$PKG
>> + fi
>>
>
> I've been using this test in my script for glances, after borrowing it
> from Larry Hajali's script for psutil, and it seems to do its job nicely.
>
> The reason for my suggestion is that I'm preparing a new SlackBuild that
> will require both python3 and python-pillow. The software expects pillow to
> support Python 3, but it doesn't, unless the script is manually edited. I
> understand that Slackware-current, from which the python-pillow script was
> taken, doesn't include Python 3, however SBo does, so it would be nice to
> have it autodetected. :)
>
> Best regards
> Philip
> ___
> 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] Marco Boneti's Packages

[Larry Hajali]

> libraries/BeautifulSoup

I can take over BeautifulSoup.  This is a dependency for one of my packages.

--Larry


On Mon, Nov 2, 2015 at 8:02 AM, Didier Spaier  wrote:

> On 02/11/2015 16:34, Willy Sudiarto Raharjo wrote:
> > Hi
> >
> > I contacted Marco and he no longer maintain his packages, so feel free
> > to grab and send updates to the following packages
>
> I volunteer for these:
>
> > libraries/newt
> > system/byobu
>
> I didn't check but if other packages also depend on newt
> I could adopt them as well.
>
> I plan to include the patch that links newt to fribidi
> discarded by Fedora but included by Debian so that their
> text installer can properly display Middle East languages.
>
> Didier
> ___
> 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] Unable to build qt5 5.5.0

[Larry Hajali]

Does Qt5WebKit.pc exist in the $PKG directory?

--Larry

On Thu, Oct 1, 2015 at 10:39 AM, Christopher Culver <
crcul...@christopherculver.com> wrote:

> Andrzej Telszewski 
> writes:
> > Do you have any previous qt5 installation?
> > This might be a blind shot, but if you happen to have it, try first
> > uninstalling and then building.
>
> Unfortunately, even after uninstalling the previous installation of qt5,
> building qt5 5.5.0 fails with the error I mentioned at the beginning of
> this thread. This really sucks, as I can no longer open any Qt5
> applications.
>
> This bug has been reported before:
>
> http://comments.gmane.org/gmane.comp.lib.qt.user/14016
>
> but no solution was provided in that discussion.
>
> ___
> 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] Unable to build qt5 5.5.0

[Larry Hajali]

On Wed, Sep 30, 2015 at 6:18 AM, Christopher Culver <
crcul...@christopherculver.com> wrote:

> When I attempt to build qt5 5.5.0 from the SBo Slackbuild, the build
> fails at the make install stage with the error:
>
> can't read
> /media/BUILD/sbotmp//package-qt5/usr/lib64/pkgconfig/Qt5WebKit.pc: No
> such file or directory
>
> Now, I am invoking qt5 as root as follows:
>
> TMP=/media/BUILD/ ./qt5.SlackBuild
>
> because I don’t have so much space in /tmp/ and prefer to use another
> drive for Slackbuilds, but I don’t think that is the problem here
> – all other SBo Slackbuilds compile fine.
>
> What could be the cause of this error?

  I'm not sure.  Did you run out of space in /media/BUILD? Do you have a
full Slackware64 install?

--Larry
___
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] fftw

[Larry Hajali]

I just noticed that fftw is in the ready queue.  Slackware 14.1 already has
fftw, so I'm wondering why it was approved.

Thanks,
Larry
___
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] owncloud-client

[Larry Hajali]

I turns out if you just have the minimum dependencies installed (ie.
qtkeychain) then you'll get the error that $PKG/usr/man doesn't exist.  The
following message during cmake step is seen when Sphinx isn't installed.

-- Could NOT find Sphinx (missing:  SPHINX_EXECUTABLE)

Sphinx is used to create the documentation.  However if Sphinx is installed
and documentation isn't generated then $PKG/usr/man exists as an empty
directory.  I've created a diff of the owncloud-client.SlackBuild that will
accommodate if Sphinx is installed or not.  This patch also works on the
new owncloud-client version 2.0.1.

Thanks,
Larry

On Fri, Sep 4, 2015 at 1:09 PM, Panagiotis Nikolaou <
hostmas...@slackonly.com> wrote:

> Hi!
> owncloud-client failed to build here is the log from sbopkg:
>
> -- Installing:
>
> /tmp/SBo/package-owncloud-client/usr/share/nautilus-python/extensions/syncstate.py
> rmdir: failed to remove '/tmp/SBo/package-owncloud-client/usr/man': No
> such file or directory
>
> owncloud-client:
> Would you like to continue processing the rest of the
> queue or would you like to abort?  If this failed
> package is a dependency of another package in the queue
> then it may not make sense to continue.
>
> (Y)es to continue, (N)o to abort, (R)etry the build?: n
>
> seems there is no $PKG/usr/man so after comment out:
> rmdir $PKG/usr/man
> sbopkg is able to build owncloud-client successfully...
>
>
>
>
>
>
> ___
> 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/
>
>
--- owncloud-client.SlackBuild.orig 2015-09-04 22:06:27.900243680 +
+++ owncloud-client.SlackBuild  2015-09-04 21:57:17.002226072 +
@@ -24,7 +24,7 @@
 
 PRGNAM=owncloud-client
 VERSION=${VERSION:-1.8.4}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2}
 TAG=${TAG:-_SBo}
 
 SRCNAM=owncloudclient
@@ -83,6 +83,7 @@
 -DCMAKE_BUILD_TYPE="Release" \
 ..
   make VERBOSE=1
+  make doc
   make install DESTDIR=$PKG
 cd ..
 
@@ -95,7 +96,7 @@
   $PKG/usr/doc/$PRGNAM-$VERSION
 cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
 
-rmdir $PKG/usr/man
+[ -d "$PKG/usr/man" ] && find $PKG/usr/man -type f -exec gzip -9 '{}' \;
 
 mkdir -p $PKG/install
 cat $CWD/slack-desc > $PKG/install/slack-desc
___
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] Source download for voxelands

[Larry Hajali]

Hi,

The download link for voxelands has changed.

On SBo: http://www.voxelands.com/downloads/voxelands-1501.00-src.tar.bz2
New link:
http://www.voxelands.com/downloads/old/voxelands-1501.00-src.tar.bz2

Thanks,
Larry
___
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] Problem with mono (and probably mono2) on Slackware64

[Larry Hajali]

This was also an issue with libgdiplus in the config file in earlier
versions of mono.  The issue seems to now be with MonoPosixHelper library.
I'm providing a slightly updated patch to fix the /usr/lib issue.

Thanks,
--Larry

On Mon, Aug 10, 2015 at 4:14 AM, Thomas Szteliga t...@websafe.pl wrote:

 On 08/10/2015 06:07 AM, Christoph Willing wrote:
  That is not an appropriate patch; it is completely 64bit-centric, just
  as the config in the source code is completely 32bit-centric.

 Sorry for that, this patch wasn't meant to be a patch for
 the slackbuild package, just for visualisation of changes I've
 made that allowed me to run KeePass. Sorry for misleading.

 --
 Best regards,

 Thomas Szteliga
 https://github.com/websafe/


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



diff -Naur mono-3.10.0.orig/data/config.in mono-3.10.0/data/config.in
--- mono-3.10.0.orig/data/config.in	2014-10-04 09:27:43.0 +
+++ mono-3.10.0/data/config.in	2015-08-09 14:47:00.208372631 +
@@ -10,7 +10,7 @@
 	dllmap dll=i:odbc32.dll target=libiodbc.dylib os=osx/
 	dllmap dll=oci target=libclntsh@libsuffix@ os=!windows/
 	dllmap dll=db2cli target=libdb2_36@libsuffix@ os=!windows/
-	dllmap dll=MonoPosixHelper target=@prefix@/lib/libMonoPosixHelper@libsuffix@ os=!windows /
+	dllmap dll=MonoPosixHelper target=@libdir@/libMonoPosixHelper@libsuffix@ os=!windows /
 	dllmap dll=i:msvcrt target=@LIBC@ os=!windows/
 	dllmap dll=i:msvcrt.dll target=@LIBC@ os=!windows/
 	dllmap dll=sqlite target=@SQLITE@ os=!windows/
--- mono.SlackBuild.orig	2015-08-09 08:46:59.094525671 -0700
+++ mono.SlackBuild	2015-08-09 07:48:21.697376096 -0700
@@ -50,7 +50,9 @@
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
-# Fix libgdiplus library path
+# Fix library path in config file
+patch -p1  $CWD/config.patch
+
 CFLAGS=$SLKCFLAGS \
 CXXFLAGS=$SLKCFLAGS \
 ./configure \
___
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] categories/tags

[Larry Hajali]

 Short descriptions are not in the db, and I have no real mysql skills, so
 this will only be doable if another admin has the time.

 Before anyone jumps in to offer a one-liner or some such, this requires
 more than just adding the current short descriptions to the db. The
 submission form and back-end approval process tools that we use during
 updates would also need to be hammered on.

 I'll consider bringing someone in to help with it, since it's a feature
 I've wanted for some time.


I'm a mysql DBA if you need some db help.

--Larry
___
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] dolphin-emu and latest x264

[Larry Hajali]

  /usr/lib64/gcc/x86_64-slackware-linux/4.8.2/../../../../x86_64-slackware
  -linux/bin/ld:
  warning: libx264.so.138, needed by
  /usr/lib64/gcc/x86_64-slackware-linux/4.8.2/../../../../lib64/libavcodec
  .so,
  not found (try using -rpath or -rpath-link)
  /usr/lib64/gcc/x86_64-slackware-linux/4.8.2/../../../../lib64/libavcodec
  .so:
  undefined reference to `x264_encoder_close'
  ...
  /usr/lib64/gcc/x86_64-slackware-linux/4.8.2/../../../../lib64/libavcodec
  .so:
  undefined reference to `x264_encoder_delayed_frames'
  collect2: error: ld returned 1 exit status
  make[2]: *** [Binaries/dolphin-emu] Error 1
  make[2]: Leaving directory `/tmp/SBo/dolphin-4.0.2/build'
  make[1]: *** [Source/Core/DolphinWX/CMakeFiles/dolphin-emu.dir/all]
  Error 2
  make[1]: Leaving directory `/tmp/SBo/dolphin-4.0.2/build'
  make: *** [all] Error 2
 

I think the problem is that ffmpeg needs to be rebuilt against a newer
installation of x264.

--Larry


  No problem, just go into /usr/lib64 and make a libx264.so.138 symlink:
 
  root@hades:/usr/lib64 # ls -l libx264*
  lrwxrwxrwx 1 root root  14 Jul 22 23:02 libx264.so - libx264.so.146
  *
  lrwxrwxrwx 1 root root  10 Jul 22 23:02 libx264.so.138 - libx264.so
  *
  -rwxr-xr-x 1 root root 1008448 Jul  6 00:59 libx264.so.146*
 
  Tried again and this time got the following error:
 
  cd /tmp/SBo/dolphin-4.0.2/build/Source/Core/DolphinWX 
  /usr/bin/cmake -E cmake_link_script
  CMakeFiles/dolphin-emu.dir/link.txt --verbose=1
  ...
  /Common/libcommon.a -lpthread -lasound -lao -lopenal -lSoundTouch
  /usr/lib64/gcc/x86_64-slackware-linux/4.8.2/../../../../lib64/libavcodec
  .so:
  undefined reference to `x264_encoder_open_138'
  collect2: error: ld returned 1 exit status
  make[2]: *** [Binaries/dolphin-emu] Error 1
  make[2]: Leaving directory `/tmp/SBo/dolphin-4.0.2/build'
  make[1]: *** [Source/Core/DolphinWX/CMakeFiles/dolphin-emu.dir/all]
  Error 2
  make[1]: Leaving directory `/tmp/SBo/dolphin-4.0.2/build'
  make: *** [all] Error 2
 
  I ended up reverting to x264-20131101 which has the real
  libx264.so.138 file instead of a symlink. From the error above Dolphin
  seems to expect 138 for some reason.

 I think you need to rebuilt the deps for dolphin-emu

 here's the result of building x264 and dolphin-emu via sbopkg

 x264:
   MD5SUM check for x264-snapshot-20150223-2245-stable.tar.xz ... OK
   Building package x264-20150223-x86_64-1_SBo.tgz ... OK
   Installing package x264-20150223-x86_64-1_SBo.tgz ... OK

 nvidia-cg-toolkit:
   MD5SUM check for Cg-3.1_April2012_x86_64.tgz ... OK
   Building package nvidia-cg-toolkit-3.1_April2012-x86_64-1_SBo.tgz ... OK
   Installing package nvidia-cg-toolkit-3.1_April2012-x86_64-1_SBo.tgz ...
 OK

 dolphin-emu:
   MD5SUM check for 4.0.2.tar.gz ... OK
   Building package dolphin-emu-4.0.2-x86_64-3_SBo.tgz ... OK
   Installing package dolphin-emu-4.0.2-x86_64-3_SBo.tgz ... OK


 --
 Willy Sudiarto Raharjo


 ___
 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] supervisor issues

[Larry Hajali]

 root@ea5f05b08549:/# supervisord
 Traceback (most recent call last):
   File /usr/bin/supervisord, line 5, in module
 from pkg_resources import load_entry_point
   File /usr/lib64/python2.7/site-packages/pkg_resources/__init__.py,
 line 3084, in module
 @_call_aside
   File /usr/lib64/python2.7/site-packages/pkg_resources/__init__.py,
 line 3070, in _call_aside
 f(*args, **kwargs)
   File /usr/lib64/python2.7/site-packages/pkg_resources/__init__.py,
 line 3097, in _initialize_master_working_set
 working_set = WorkingSet._build_master()
   File /usr/lib64/python2.7/site-packages/pkg_resources/__init__.py,
 line 651, in _build_master
 ws.require(__requires__)
   File /usr/lib64/python2.7/site-packages/pkg_resources/__init__.py,
 line 952, in require
 needed = self.resolve(parse_requirements(requirements))
   File /usr/lib64/python2.7/site-packages/pkg_resources/__init__.py,
 line 839, in resolve
 raise DistributionNotFound(req, requirers)
 pkg_resources.DistributionNotFound: The* 'meld3=0.6.5'* distribution
 was not found and is required by supervisor
 root@ea5f05b08549:/#

 Looks like meld3 is a missing dependency for supervisor.  Arch Linux,
Gentoo and Fedora all have meld3 as a dependency.

https://projects.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/supervisor
https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-admin/supervisor/supervisor-3.1.3.ebuild?revision=1.4view=markup
http://pkgs.fedoraproject.org/cgit/supervisor.git/tree/supervisor.spec

--Larry
___
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] nginx permissions?

[Larry Hajali]

On Wed, Jul 8, 2015 at 1:31 PM, Miguel De Anda mig...@thedeanda.com wrote:

 I just had to rebuild my nginx machine and I ran into this issue
 again! I managed to fix it this time with a:

 chmod 755 /var/lib/nginx

What does setting the permissions of /var/lib/nginx to 755 accomplish?
Nginx will create the folders by default when it starts up.  I assume your
issue is that you had a previous instance of nginx running as a different
user than user nobody.

I could look at having a nginx user rather than it being optional.

--Larry



 I notice the buildscript set it to 700. I simply installed it via
 slackrepo using nothing but defaults so nginx runs as user nobody.

 Might be worth checking out to prevent future issues.

 On Thu, May 7, 2015 at 11:53 AM, Thomas Morper tho...@beingboiled.info
 wrote:
  On Tue, 5 May 2015, Miguel De Anda wrote:
 
  i've installed nginx from the slackbuild and i have it run as a proxy
 for
  tomcat with a config something like this...
 
  when it tries to load some files, it fails with the following error:
  /var/lib/nginx/proxy/3/00/03 failed (13: Permission denied)
 
  it seems to kind of work if i add a
  user mdeanda users;
  to the config and change the permission to /var/lib/nginx/*
 
  Nginx uses /var/lib/nginx for various temporary files, especially when
  proxying. The directory should belong to root:root. Upon start, nginx
 will
  then create the various subfolders and asign them to the $NGINXUSER
 unless
  they already exist.
 
  I ran into problems once when I either reconfigured or rebuilt nginx to
  use a different user id but forgot about /var/lib/nginx/* still belonging
  to the old user. I don't know how you ended up with the wrong
 permissions,
  but if you stop nginx, remove the contents of /var/lib/nginx and restart
  you should be fine. If the permission problems remain you should check
  your config and your nginx package for possible errors (e.g. built in
  wrong environment, manually specified user doesn't exist, etc.).
 
  Regarding the user id... the SlackBuild script follows best practices by
  using the defaults but still giving the user a choice. Having a dedicated
  nginx user is IMHO desirable with regards to permissions and security.
  It's not technically required, though.
 
  --
  ___
  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/


___
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] Updates - 20150517.1

[Larry Hajali]

SFML doesn't have an md5sum value, instead it has a url.

From sbopkg:
Found SFML-2.3-sources.zip in /var/cache/sbopkg.
Checking MD5SUM:
  MD5SUM check for SFML-2.3-sources.zip ... FAILED!
Expected: https://sourceforge.net/projects/slpkg
Found:abc06b4cdef6531143ac0221cd1b184a

Md5sum should be updated to 'abc06b4cdef6531143ac0221cd1b184a'.

Thanks,
--Larry

On Sun, May 17, 2015 at 4:14 PM, B Watson yalh...@gmail.com wrote:

 On 5/17/15, B Watson yalh...@gmail.com wrote:
  On 5/17/15, B Watson yalh...@gmail.com wrote:
  However, there *is* an md5sum failure for the other file,
  zathura-pdf-poppler-0.2.5.tar.gz (my fault, failed to update it in the
  .info file). Will fix.
 
  I spoke too soon. Somehow the md5sum in the .info file isn't what I put
  in there. Will investigate.

 OK, fixed in my branch. Also attached the fixed zathura.info to this
 email,
 thanks for bringing to my attention.

 ___
 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] texmaker missing dependency information

[Larry Hajali]

I don't understand.  The README says:

Note: Texmaker can be optionally compiled with
poppler-qt5 by passing the argument QT5GUI=yes.

QT5GUI=yes ./texmaker.SlackBuild

Is it not worded correctly?  Or make Qt5 a more explicit optional
dependency?

Thansk

On Fri, Apr 24, 2015 at 3:21 PM, KaMii laciela...@rocketmail.com wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Texmaker: for QT5GUI=yes to build poppler-qt5 is required but this is
 not listed as a dependency.

 - -KaMii
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1

 iJwEAQECAAYFAlU6we8ACgkQkO84ARmAdEDxKwP9EW2ZRXQwU0uA8zyXRM917m1y
 c4KlQ/YmwB+zbRlxWgHG20ed1PzQ6fiBJ7khr+yLynFo0aqHaskQxonUva7OalKy
 UA5lMDUApYCU3qKCqESua7nmIy+YVMegF7N989r5lNfN49cJ3DA2kZ/7Dsx8kA05
 ZzYPhUvoY0HiJW5T/Hg=
 =G5aM
 -END 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 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] Calibre

[Larry Hajali]

Hi,

I've been aware of calibre upgrading to Qt5 and I have my own system
updated to work with it on Slackware 14.1.  Right now Slackware 14.1 and
current cannot use the newer calibre due to the sip package being too old.
I was hoping Slackware current would update the sip package so that I could
update calibre for the next release.  Not sure if this will happen.

I still would like to be the maintainer of calibre and I'm aware of the
binary calibre download.  But I won't be maintaining a binary repackaging
of calibre.

With that said, if the SBo community wants calibre to be updated with the
binary repackaging then I'm willing to give up maintaining calibre.

Thanks,
--Larry

On Wed, Apr 1, 2015 at 8:08 AM, Gwenhael Le Moine 
gwenhael.le.mo...@gmail.com wrote:

 Hi,

 Since Calibre made the move to Qt5 the available Slackware packages
 (both from here and AlienBob) have been stuck to the 1.48 version.

 Today I've realized that there's a binary package provided by
 Calibre's developer that is quite simple to package and I've made a
 SlackBuild that does just that :

 https://github.com/cycojesus/slackbuilds/blob/master/xap/calibre/calibre.SlackBuild

 Due to the source used the resulting package is similar to AlienBob's
 in that it includes all dependencies.

 If there's any interest I'm willing to migrate my SlackBuild to SBo's
 standards, submit it and take over the maintainer-ship from the old
 calibre.SlackBuild (whose maintainer is CC'd here.)

 Cordially,
 Gwenhael Le Moine

 P.S. : for the sake of conviviality I attach my SlackBuild to this email.

___
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] My packages

[Larry Hajali]

A little late on this, but I'll take back libraries/irrlicht.

--Larry

On Thu, Feb 5, 2015 at 8:15 PM, Klaatu kla...@straightedgelinux.com wrote:

 I'll take povray.

 It's up to date with the latest stable release, so I will not be pushing
 any update, but it's something that is relevant to my work, so I'll
 gladly keep an eye out for it.

 - klaatu


 On 02/04/2015 02:02 PM, Niels Horn wrote:
  Greetings to all,
 
  As some of you may have noticed, I've not been able to update my
 SlackBuild
  scripts for some time now.
 
  It's not that I've lost interest.
  My whole professional life has been motivated by changes and challenges
 and
  when some time ago the company I work for offered me a new challenge, I
  accepted it. At the time I had no real clue about the consequences, but
 the
  idea of branching away from a technical career to an executive position
  seduced me (money-wise as well, naturally).
  I've learned many new things, like negotiating with legal departments,
  collaboration with branches from all aver the world, motivating leaders,
  setting goals and encouraging people to work hard to reach them, etc.
 
  But, it came with a price... More responsibility and more work hours.
  And that means less time for fun projects like maintaining SlackBuilds, a
  blog, homepage, etc.
  I miss that, but it is a choice I made and I'm enjoying some of the
 results.
  The only non-professional activity I kept is carpentry. I enjoy building
  furniture, fixing anything made from wood and hope to continue doing so
  ever after I retire.
 
  I still use Slackware and will continue doing so as long as it exists. No
  Windows or Mac for me.
 
  Over the last several months I've received some e-mails requesting
 updates
  of scripts.
  Some people I managed to convince to take over maintainership of a
 certain
  package, others not (yet).
  Basically, all my scripts are up for grabs. I've not even been able to
  keep track of which ones already have been taken over, so feel free to
 do a
 
  # find ./ -name *.info -exec grep -l Niels Horn {} \;
 
  in your local copy of the SlackBuilds repository.
  If you have any technical questions about a specific script, feel free to
  contact me. It might take a few days to get an answer, but eventually I
  will.
 
  For the rest, the very capable administrators of SlackBuilds.org will no
  doubt find a way to handle any questions.
 
  Have fun!
 
  --
  Niels Horn
 
 
 
  ___
  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/


___
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] Qt 5.4.0, QTWebEngine and Pulseaudio

[Larry Hajali]

Hmmm...interesting.  I took a look at the BLFS page for qt5.  Thanks for
the link.

I haven't tried compiling qtwebengine without pulseaudio, but the link you
sent says that it needs version of nss = 3.17.3.  Slackware 14.1 and
-current comes with mozilla-nss 3.16.5.  qtwebengine is new in qt5 5.4.0,
so I didn't put much effort in compiling it into the qt5.SlackBuild.

Good luck,
--Larry

On Wed, Feb 4, 2015 at 7:32 PM, KaMii laciela...@rocketmail.com wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 I have been working on getting QTWebEngine to compile without
 pulseaudio and found a very helpful sed line which allows this.  Yet I
 am having some later issues with the compile job.
 http://pastebin.com/gSLhPyek

 The sed lines I found here:
 http://www.linuxfromscratch.org/~krejzi/kblfs/x/qt5.html

 sed -e $ a !contains(QT_CONFIG, pulseaudio): GYP_CONFIG +=
 use_pulseaudio=0 \
 -i qtwebengine/src/core/config/desktop_linux.pri

 The script I wrote and am using is here:

 https://github.com/KaMiila/SlackBuilds/blob/master/qtwebengine/qtwebengine.SlackBuild

 Ideally I would love to get a qt5 script that combines QTWebEngine
 without pulseaudio.  I noticed the slackbuild for qt5 has the
 QTWebEngine disabled if you do not USEPULSE=yes prefix.  I just wanted
 to pass on this sed line and perhaps it is useful for those that want
 QTWebEngine without pulseaudio?  Furthermore, if you can get this to
 build without, what appears to be a compiler version issue, that I have
 yet to conquer, please let me know!

 - -KaMii
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1

 iJwEAQECAAYFAlTS5FcACgkQkO84ARmAdEBdqQQAqw7d23WHJwUxQsBTSZkfXJ3O
 nBh5cC8YuOEzfbnpgbX91NDO2opX428NCSsAT3B2M8mj66gubay2fbFnvB5MtmDB
 34eqWLhuM8sxxAeWM8Fo2hgTLD8CEd2ORlkhx5lJpGy9H4o9yhc9RE3KTAI2MIRv
 BAb+fgVqgjRSAaPzmws=
 =/icP
 -END 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 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] eyeD3 requires...

[Larry Hajali]

The gentoo folks seem to apply this to their eyed3.ebuild so that optional
dependency python-magic is not automatically downloaded and installed.

sed -i -e '/scripts/d' -e '/install_requires/d' pavement.py

Ref:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-python/eyeD3/eyeD3-0.7.5.ebuild?revision=1.2view=markup

--Larry



On Wed, Jan 21, 2015 at 5:13 PM, andrew andrew.david.str...@gmail.com
wrote:

 On Thu, Jan 22, 2015 at 06:36:28AM +0700, Willy Sudiarto Raharjo wrote:
   the script will DOWNLOAD python-magic if it's not installed
   during build this is something we tried to avoid since users
   might not be aware all downloadable source must be present in the
   DOWNLOAD or REQUIRES
  
   But I believe this is only if eyeD3 is installed using pip
   directly? The slackbuild I have submitted does not use pip and does
   not install or use python-magic.
 
  run the slackbuild and see the build output
  it will download them and install them (python-magic)

 My deep apologies Willy! Of course when I looked at the output
 properly I saw:

 
 eyeD3-0.7.5/src/eyed3/info.py
 Searching for python-magic
 Reading https://pypi.python.org/simple/python-magic/
 Best match: python-magic 0.4.6
 Downloading
 https://pypi.python.org/packages/2.7/p/python-magic/python_magic-0.4.6-py2.7.egg#md5=b016ddfa7d1e3d888eb64f3e8e44d933
 Processing python_magic-0.4.6-py2.7.egg
 Moving python_magic-0.4.6-py2.7.egg to /tmp/SBo/eyeD3-0.7.5/.eggs
 --

 Thank you for catching this error in my script and thank you for all
 of your work :).

 Andrew
 --
 You think that's air you're breathing now?
 ___
 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] COMPAT32 question

[Larry Hajali]

Has this been signed off by the SBo admins?  I see that apulse now has the
[ -e /lib/libc.so.6 ]  COMPAT32=${COMPAT32:-yes} check in the ready
queue.

--Larry

On Wed, Dec 17, 2014 at 4:53 PM, B Watson yalh...@gmail.com wrote:

 On 12/17/14, Ryan P.C. McQuen rya...@linux.com wrote:
  Furthermore, does someone know a better way to perform this check.
  Maybe I should be relying on checking glibc or gcc ...

 That's what I'd do. In the section that checks ARCH:

 ...
 elif [ $ARCH = x86_64 ]; then
   SLKCFLAGS=-O2 -fPIC
   LIBDIRSUFFIX=64
   [ -e /lib/libc.so.6 ]  COMPAT32=${COMPAT32:-yes}
 else
 ...

 Doing it that way will autodetect, but still allow the user to override
 with COMPAT32=no in the environment. It also avoids the use of find,
 which is kinda slow and heavy.

 As to whether it's a good idea... I don't see why not. The existing
 apulse.SlackBuild already has multilib-specific code, this just automates
 enabling it (instead of user having to manually COMPAT32=yes).
 ___
 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] COMPAT32 question

[Larry Hajali]

On Sat, Jan 3, 2015 at 5:10 PM, Ryan P.C. McQuen rya...@linux.com wrote:

 ryanpcmcquen.com
 On Jan 3, 2015 4:32 PM, Larry Hajali larryh...@gmail.com wrote:
 
  Has this been signed off by the SBo admins?  I see that apulse now has
 the [ -e /lib/libc.so.6 ]  COMPAT32=${COMPAT32:-yes} check in the
 ready queue.
 

 Actually it has been live on SBo since 12.20:


 http://slackbuilds.org/cgit/slackbuilds/commit/?id=58e9ea52ff1b6b018bd0d601e43fbeb4800ff5e2

 Ok, thanks.  I'll just remember to export COMPAT32=no in my sbopkg.conf
file on my multilib system.

--Larry



  --Larry
 
  On Wed, Dec 17, 2014 at 4:53 PM, B Watson yalh...@gmail.com wrote:
 
  On 12/17/14, Ryan P.C. McQuen rya...@linux.com wrote:
   Furthermore, does someone know a better way to perform this check.
   Maybe I should be relying on checking glibc or gcc ...
 
  That's what I'd do. In the section that checks ARCH:
 
  ...
  elif [ $ARCH = x86_64 ]; then
SLKCFLAGS=-O2 -fPIC
LIBDIRSUFFIX=64
[ -e /lib/libc.so.6 ]  COMPAT32=${COMPAT32:-yes}
  else
  ...
 
  Doing it that way will autodetect, but still allow the user to override
  with COMPAT32=no in the environment. It also avoids the use of find,
  which is kinda slow and heavy.
 
  As to whether it's a good idea... I don't see why not. The existing
  apulse.SlackBuild already has multilib-specific code, this just
 automates
  enabling it (instead of user having to manually COMPAT32=yes).
  ___
  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/
 
 

 ___
 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] matplotlib does not build on 1 of 3 systems

[Larry Hajali]

Looks like your PyQt package is not compatible with the installed sip
package.  I get similar errors on calibre 1.x versions because I upgraded
sip to a newer version for building PyQt5.  You might want to reinstall
PyQt and sip on the system that is giving you problems.

--Larry

On Sat, Dec 13, 2014 at 1:30 PM, Jim Diamond jim.diam...@acadiau.ca wrote:

 Hi,

 I'm trying to compile matplotlib on some Slackware64 14.1 systems, all
 with multilib.

 On 2 of the 3, it compiles fine using sboinstall and/or sboupgrade.

 On the third, my attempts are rewarded with the following:

 ...
 BUILDING MATPLOTLIB
 matplotlib: yes [1.4.2]
 python: yes [2.7.5 (default, May 29 2013, 02:28:51)  [GCC
 4.8.0]]
   platform: yes [linux2]

 REQUIRED DEPENDENCIES AND EXTENSIONS
  numpy: yes [version 1.9.1]
six: yes [using six version 1.8.0]
   dateutil: yes [using dateutil version 2.2]
   pytz: yes [using pytz version 2013.8]
tornado: yes [using tornado version 4.0.2]
  pyparsing: yes [using pyparsing version 2.0.1]
  pycxx: yes [Couldn't import.  Using local copy.]
 libagg: yes [pkg-config information for 'libagg' could not
 be found. Using local copy.]
   freetype: yes [version 2.5.0]
png: yes [version 1.4.12]
  qhull: yes [pkg-config information for 'qhull' could not
 be
 found. Using local copy.]

 OPTIONAL SUBPACKAGES
sample_data: yes [installing]
   toolkits: yes [installing]
  tests: no  [skipping due to configuration]
 toolkits_tests: no  [skipping due to configuration]

 OPTIONAL BACKEND EXTENSIONS
 macosx: no  [Mac OS-X only]
 qt5agg: no  [PyQt5 not found]
 Traceback (most recent call last):
   File setup.py, line 155, in module
 result = package.check()
   File /tmp/SBo/matplotlib-1.4.2/setupext.py, line 504, in check
 additional_info = self.check_requirements()
   File /tmp/SBo/matplotlib-1.4.2/setupext.py, line 1989, in
 check_requirements
 msg = p.map(self.callback, [self])[0]
   File /usr/lib64/python2.7/multiprocessing/pool.py, line 250, in map
 return self.map_async(func, iterable, chunksize).get()
   File /usr/lib64/python2.7/multiprocessing/pool.py, line 554, in get
 raise self._value
 RuntimeError: the sip module implements API v7.0 to v7.1 but the
 PyQt4.QtCore module requires API v9.1
 ...


 On the good systems, I see

 ...
 OPTIONAL BACKEND EXTENSIONS
 macosx: no  [Mac OS-X only]
 qt5agg: no  [PyQt5 not found]
 qt4agg: yes [installing, Qt: 4.8.4, PyQt: 4.8.4]
 pyside: no  [PySide not found]
gtk3agg: no  [Requires pygobject to be installed.]
  gtk3cairo: no  [Requires pygobject to be installed.]
 gtkagg: yes [installing, Gtk: 2.24.20 pygtk: 2.24.0]
  tkagg: yes [installing, version 81008]
  wxagg: yes [installing, version 2.8.12.1]
gtk: yes [installing, Gtk: 2.24.20 pygtk: 2.24.0]
agg: yes [installing]
  cairo: yes [installing, pycairo version 1.8.10]
  windowing: no  [Microsoft Windows only]

 OPTIONAL LATEX DEPENDENCIES
 dvipng: yes [version 1.14]
ghostscript: yes [version 9.07]
  latex: yes [version 3.14159265]
pdftops: yes [version 0.24.3]

 running install
 ...


 I've compared the packages installed (and their versions) on all three
 systems, and while there are a few differences, I didn't see any
 difference which looked like it should affect any of Python, PyQt or
 Qt.  (Admittedly, I may have missed some significant difference.)


 Does anyone have any insight as to what I might be looking for?
 Obviously I can copy over the package from one of the successful
 systems and install it (whether it would work correctly is another
 issue), but I'd rather have some idea about what the real problem is.

 Thanks.

 Jim
 ___
 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] problem compiling entangle 0.6.0 on S64 14.1

[Larry Hajali]

Thanks!

--Larry

On Mon, Nov 17, 2014 at 12:44 PM, Willy Sudiarto Raharjo 
will...@slackbuilds.org wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

  I also had issues building entangle on a Slackware64 14.1, but on
  a multi-lib system.  I know multi-lib is not supported but the
  problem turned out to be a hard coded libdir to /usr/lib in the
  libgexiv2 pkgconfig file. Newer versions of libgexiv2 seem to have
  fixed this, but I haven't tested newer versions.  Can we apply the
  patch in this email to libgexiv2.SlackBuild so that the proper
  libdir is in the gexiv2.pc file?

 Applied in my branch
 Thanks

 - --
 Willy Sudiarto Raharjo
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2

 iEYEARECAAYFAlRqXkgACgkQiHuDdNczM4GhZgCfcgNfVFKyADFhTbcITcui38g/
 aegAnROsUgq3zxT2inHU/M5zn2b+ua91
 =aw5B
 -END 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 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] problem compiling entangle 0.6.0 on S64 14.1

[Larry Hajali]

I also had issues building entangle on a Slackware64 14.1, but on a
multi-lib system.  I know multi-lib is not supported but the problem turned
out to be a hard coded libdir to /usr/lib in the libgexiv2 pkgconfig file.
Newer versions of libgexiv2 seem to have fixed this, but I haven't tested
newer versions.  Can we apply the patch in this email to
libgexiv2.SlackBuild so that the proper libdir is in the gexiv2.pc file?

Thanks,
--Larry

On Sun, Nov 16, 2014 at 9:02 AM, Jim Diamond jim.diam...@acadiau.ca wrote:

 On Sun, Nov 16, 2014 at 21:11 (+0700), Willy Sudiarto Raharjo wrote:

  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA1

  I'm trying to compile entangle.  I have all of the packages which
  the page says I need.

  When I try to build it, after it works for a while it says ... GEN
  Entangle-0.1.gir Couldn't find include 'GExiv2-0.4.gir' (search
  path: ['.', '.', 'gir-1.0', '/usr/share/gir-1.0',
  '/usr/share/gir-1.0', '/usr/share/gir-1.0'])

  I looked around a bit and I'm not sure which package should have
  that file. Anyone point me in the right direction?

  i just tested on VM and it worked here

 snip

  libgexiv2:
  MD5SUM check for gexiv2-0.7.0.tar.xz ... OK
  Building package libgexiv2-0.7.0-x86_64-2_SBo.tgz ... OK
  Installing package libgexiv2-0.7.0-x86_64-2_SBo.tgz ... OK

 snip

  i think you missed libgexiv2

 Nope, I had it installed.  But given your comment, I removed it and
 rebuilt it, and now things work.

 Investigating, I see that I had had libgexiv2-0.7.0-x86_64-1_SBo, not
 the latest and greatest libgexiv2-0.7.0-x86_64-2_SBo.
 I guess this is the sort of thing which slips through the crack;
 sbocheck didn't tell me I had an old version of libgexiv2-0.7.0.

 Thanks very much for your help.

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


--- libgexiv2.SlackBuild.orig	2014-11-16 17:25:00.716801035 +
+++ libgexiv2.SlackBuild	2014-11-16 17:13:45.132592495 +
@@ -25,7 +25,7 @@
 PRGNAM=libgexiv2
 SRCNAM=gexiv2
 VERSION=${VERSION:-0.7.0}
-BUILD=${BUILD:-2}
+BUILD=${BUILD:-3}
 TAG=${TAG:-_SBo}
 
 if [ -z $ARCH ]; then
@@ -70,6 +70,8 @@
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
+sed -i /^libdir/s|/lib$|/lib${LIBDIRSUFFIX}| gexiv2.m4
+
 CFLAGS=$SLKCFLAGS \
 CXXFLAGS=$SLKCFLAGS \
 ./configure \
___
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] compiling php

[Larry Hajali]

It looks like you're building on a x86_64 multilib machine.  The library
libldap.so is being found first in /usr/lib (as well as other libs), but
you're using the '-O2 -fPIC' SLKCFLAGS which are x86_64 specific.  Try
rebuilding php on a non-multilib x86_64 machine or else try passing
LDFLAGS=/usr/lib${LIBDIRSUFFIX} to the configure script.

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

--Larry

On Mon, Sep 8, 2014 at 3:27 PM, Miguel De Anda mig...@thedeanda.com wrote:

 i couldn't find a suitable mailing list on slackware official so i thought
 i'd ask here...

 i'm trying to build php to add debug support as it seems the supplied one
 has '--disable-debug' set. when i run the php slackbuild in the sources
 directory (from current) i get the following:

 /bin/sh ../libtool --tag=CC   --mode=link gcc -std=gnu99 -pthread -O2
 -fPIC  -L/usr/lib  -o pico main.o utf8stub.o ../c-client/utf8.o libpico.a
 osdep/libpicoosd.a ../pith/osdep/libpithosd.a ../pith/charconv/libpithcc.a
  -lcrypto -lssl -lldap  -lncurses -llber -lssl -lcrypto
 libtool: link: gcc -std=gnu99 -pthread -O2 -fPIC -o pico main.o utf8stub.o
 ../c-client/utf8.o  -L/usr/lib libpico.a osdep/libpicoosd.a
 ../pith/osdep/libpithosd.a ../pith/charconv/libpithcc.a /usr/lib/libldap.so
 /usr/lib/libsasl2.so -ldl -lncurses /usr/lib/liblber.so -lresolv -lssl
 -lcrypto -pthread
 /usr/lib/libldap.so: error adding symbols: File in wrong format
 collect2: error: ld returned 1 exit status
 make[3]: *** [pico] Error 1
 make[3]: Leaving directory `/mnt/sdb1/tmp/alpine-2.11/pico'
 make[2]: *** [all-recursive] Error 1
 make[2]: Leaving directory `/mnt/sdb1/tmp/alpine-2.11/pico'
 make[1]: *** [all-recursive] Error 1
 make[1]: Leaving directory `/mnt/sdb1/tmp/alpine-2.11'
 make: *** [all] Error 2

 has anybody dealt with this? do i need to build other slackware sources
 first maybe? i notice it references alpine at some point.

 thanks,
 miguel

 ___
 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] compiling php

[Larry Hajali]

Interesting that php is under the /n directory (
http://mirrors.slackware.com/slackware/slackware64-current/source/n/php/).
I though it would be in /d or even /l directory.

--Larry

On Mon, Sep 8, 2014 at 7:27 PM, Larry Hajali larryh...@gmail.com wrote:

 It looks like you're building on a x86_64 multilib machine.  The library
 libldap.so is being found first in /usr/lib (as well as other libs), but
 you're using the '-O2 -fPIC' SLKCFLAGS which are x86_64 specific.  Try
 rebuilding php on a non-multilib x86_64 machine or else try passing
 LDFLAGS=/usr/lib${LIBDIRSUFFIX} to the configure script.

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

 --Larry

 On Mon, Sep 8, 2014 at 3:27 PM, Miguel De Anda mig...@thedeanda.com
 wrote:

 i couldn't find a suitable mailing list on slackware official so i
 thought i'd ask here...

 i'm trying to build php to add debug support as it seems the supplied one
 has '--disable-debug' set. when i run the php slackbuild in the sources
 directory (from current) i get the following:

 /bin/sh ../libtool --tag=CC   --mode=link gcc -std=gnu99 -pthread -O2
 -fPIC  -L/usr/lib  -o pico main.o utf8stub.o ../c-client/utf8.o libpico.a
 osdep/libpicoosd.a ../pith/osdep/libpithosd.a ../pith/charconv/libpithcc.a
  -lcrypto -lssl -lldap  -lncurses -llber -lssl -lcrypto
 libtool: link: gcc -std=gnu99 -pthread -O2 -fPIC -o pico main.o
 utf8stub.o ../c-client/utf8.o  -L/usr/lib libpico.a osdep/libpicoosd.a
 ../pith/osdep/libpithosd.a ../pith/charconv/libpithcc.a /usr/lib/libldap.so
 /usr/lib/libsasl2.so -ldl -lncurses /usr/lib/liblber.so -lresolv -lssl
 -lcrypto -pthread
 /usr/lib/libldap.so: error adding symbols: File in wrong format
 collect2: error: ld returned 1 exit status
 make[3]: *** [pico] Error 1
 make[3]: Leaving directory `/mnt/sdb1/tmp/alpine-2.11/pico'
 make[2]: *** [all-recursive] Error 1
 make[2]: Leaving directory `/mnt/sdb1/tmp/alpine-2.11/pico'
 make[1]: *** [all-recursive] Error 1
 make[1]: Leaving directory `/mnt/sdb1/tmp/alpine-2.11'
 make: *** [all] Error 2

 has anybody dealt with this? do i need to build other slackware sources
 first maybe? i notice it references alpine at some point.

 thanks,
 miguel

 ___
 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] Fwd: transmission make failure

[Larry Hajali]

The problem is that the file configure.ac is updated but the the configure
script isn't recreated.  The timestamp on the configure.ac file is newer
than the configure script due to the sed statements and that causes the
files to be regenerated.  In order for transmission.SlackBuild to run
properly, then the line 'autoreconf -ivf' needs to be ran before the
configure script is called.  This allows the automake scripts to be
recreated with the installed versions that come with Slackware{,64} 14.1.

You could also call the script ./autogen.sh from with in the
trasnmission-2.28 directory and that will do something similar to the
'autoreconf -ivf' step mentioned above.  But that will cause the configure
script to be ran twice.

--Larry


On Tue, Sep 2, 2014 at 3:41 PM, Erik Hanson e...@slackbuilds.org wrote:

 On Tue, 2 Sep 2014 17:06:47 -0500
 JK Wood joshuakw...@gmail.com wrote:


  If it doesn't build on a stock 14.1 Slackware, why is it on SBo?

 Mistakes happen.

 For now I'd like to make absolutely certain that it can't be coaxed into
 building before downgrading it.


 --
 Erik Hanson

 ___
 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] Possible bug in gtkimageview.SlackBuild script

[Larry Hajali]

Thanks, I'll send an update pointing to the right directory.

--Larry


On Mon, Aug 11, 2014 at 4:35 AM, José Manuel García-Patos 
jm.inf...@gesaku.es wrote:


 Hello,

 In the gtkimageview.SlackBuild script, the symlink to the HTML
 documentation points to the wrong directory. Attached to this email there's
 a diff file with the changes I'm proposing for it.

 Hope it helps, and thanks for maintaining so many SlackBuilds. I find them
 really useful.

 --
 José Manuel García-Patos
 Madrid

 ___
 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] Unmaintained Packages

[Larry Hajali]

I can take them.

multimedia/avidemux
games/chromium-bsu
system/dosemu

--Larry


On Sat, May 31, 2014 at 7:28 PM, Willy Sudiarto Raharjo 
will...@slackbuilds.org wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Here are some more unmaintained packages which can be taken over by
 someone interested

 multimedia/avidemux
 games/chromium-bsu
 system/dosemu


 - --
 Willy Sudiarto Raharjo
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.22 (GNU/Linux)

 iEYEARECAAYFAlOKj98ACgkQiHuDdNczM4EkMQCglVaXPuBTYhs791h8Hp5ZwdQo
 A28AoJIuHp5xLyppw6JMC+VxkmIJVa0l
 =CYBH
 -END 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 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] nginx temp paths

[Larry Hajali]

Confirmed.  I will update the nginx slackbuild to correct for this.

Thanks,
--Larry


On Tue, May 13, 2014 at 3:40 PM, Thomas Morper tho...@beingboiled.infowrote:

 Hello there,

 I'm using my own build script for nginx, but I just noticed a behaviour
 that probably affects the SBo SlackBuild as well.

 If you don't explicitly define the various temp paths when calling
 configure, nginx will create them in /usr during startup.

 --
 ___
 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] nginx maintainer

[Larry Hajali]

Here is what I'm doing with the nginx.SlackBuild file.

1) Update nginx to current stable version 1.4.7
2) Adding GeoIP as an optional dependency that can be used via a command
line parameter USE_GEOIP=yes.
3) Move /usr/html to /var/www/html.  This shouldn't conflict with anything
in /var/www.
4) Add sub-directory conf.d to /etc/nginx.  This will allow to easily
separate different virtual servers from the main nginx.conf file.
5) Update root directory in /etc/nginx/nginx.conf to point to the new
default docroot /var/www/html. Add include /etc/nginx/conf.d/*.conf; to
the end of /etc/nginx/nginx.conf to allow for multiple virtual server files.
6) Overall cleanup with the slackbuild.

The only thing that should be noticeable to the end user is that the
default index.html file that ships with nginx is now available at
http://127.0.0.1 when they first start /etc/rc.d/rc.nginx.

Thanks,
--Larry


On Sun, Apr 13, 2014 at 12:28 AM, Doogster thedoogs...@gmail.com wrote:

 And I just realized that the current SlackBuild doesn't just remove
 the error pages. It also removes nginx's welcome page.

 On Sun, Apr 13, 2014 at 12:23 AM, Doogster thedoogs...@gmail.com wrote:
  Where to put the included error pages is a matter of taste. I choose
  /var/www/ngdocs; another blogger chose /var/html
  (
 http://zhu-qy.blogspot.ca/2012/11/slackware-14-nginx-fastcgi-php-php-fpm.html
 ).
 
  What's definitely not acceptable is just removing them, which the
  current SlackBuild does.
 
  On Sun, Apr 13, 2014 at 12:15 AM, Doogster thedoogs...@gmail.com
 wrote:
  The error pages are installed, by default, into /usr/html. The default
  nginx.conf expects to find them there. The current SlackBuild just
  removes this directory. I consider that a problem.
 
  IIRC,if you have an unmodified nginx.conf, then /usr/html is also your
  document root.
 
  On Sat, Apr 12, 2014 at 9:08 PM, Miguel De Anda mig...@thedeanda.com
 wrote:
  i haven't check the 40x and 50x pages but are you saying the default
 pages
  w/o changing the included nginx.conf file? i would agree that this is a
  somewhat trivial change that doesn't affect the binary or the original
  source. another option is to correct the shipped nginx.conf to not
 reference
  the nonexistent files.
 
  it would make sense that a clean build/install of the package should be
  fully functional. for example, chown'ing log files so the
 pre-configured
  runas user can actually write to them instead of leaving it as an
  undocumented step.
 
  -m
 
 
  On Sat, Apr 12, 2014 at 3:40 PM, Doogster thedoogs...@gmail.com
 wrote:
 
  Removing the 40x and 50x error pages is a problem with the SlackBuild,
  and it should be fixed.
 
  The rest of what my patch does is a matter of taste.
 
  On Sat, Apr 12, 2014 at 2:53 PM, Klaatu kla...@straightedgelinux.com
 
  wrote:
   I hear what you're saying, Doogster, but is that really an issue
 with
   the Slackbuild? It looks like that is the way Nginx distributes
 itself,
   and Slack{ware,Builds.org} policy, I believe, is to not change the
   upstream package unless not doing so will result in the thing
 literally
   not launching or being functional on Slackware.
  
   I realise that you may be making the argument that it is not
 functional
   without being changed, and I can see what you mean. However, I use
 Nginx
   on a few different servers, and on one I do change it to match the
   htdocs webroot, but on others I change it to something else
 entirely.
  
   Bottom line is, if the SBo maintainer patches the config file for
 me,
   I'm just going to have to unpatch it later to suit however I have
 it set
   up on any given box.
  
   This is one of the things that drives me nuts about Debian and Red
 Hat;
   they change the defaults from something I'm going to have to
 change, to
   something else I'm going to have to change...
  
  
   tl;dr
   Not flaming you or disrespecting your opinion, just wondering if
 it's
   really correct to patch the config from the point of install, or
 whether
   a simple note in the README to remind the user hey! you need to
   configure this!) and maybe even a link to your blogpost so that
 new sys
   admins might have some sensible example of what a good config would
 look
   like.
  
   -klaatu
  
  
  
   On 04/13/2014 05:28 AM, Doogster wrote:
   Hey Larry. There's a pretty serious problem with the current SBo
 nginx
   SlackBuild: it removes the 40x and 50x error pages that are
 supposed
   to be included. I hope that as the new maintainer, you can address
   that.
  
   My LEMP Howto (http://duganchen.ca/lemp-on-slackware/) has a patch
   that might give you some ideas.
  
   On Sat, Apr 12, 2014 at 10:07 AM, Willy Sudiarto Raharjo
   will...@slackbuilds.org wrote:
   I'm interested Maintainer is sometimes slow to respond...
 Might
   want to
   wait a few days though.
  
   It's been more than a week :)
   Anyway, Larry Hajali was the first to respond to become a new
   maintainer

Re: [Slackbuilds-users] call for digikam tester

[Larry Hajali]

Hi Willy,

I'm able to reproduce the error in a VM when I only have ffmpeg, opencv and
lensfun installed.  You are correct in you assumption that when lensfun is
installed that liblqr is also needed.

In the file digikam-3.5.0/core/cmake/modules/FindLqr-1.cmake, if the
variables LQR-1_LIBRARY and LQR-1_INCLUDE_DIR are defined then the GLIB2
package is searched for.  If GLIB2_FOUND is set, then both of the libraries
(ie. liblqr and lensfun) are linked to libdigikamcore.so library as defined
in the file dikigam-3.5.0/core/digikam/CMakeLists.txt using this block of
code.

# For Contents Aware Resizer and Lens auto-correction tools.
IF(GLIB2_FOUND)
TARGET_LINK_LIBRARIES(digikamcore ${GLIB2_LIBRARIES} ${liblqr_LIBS}
${liblensfun_LIBS})
ENDIF(GLIB2_FOUND)

So the way I see it, both liblqr and lensfun are required for proper
linking, otherwise, you get the undefined references for lensfun.

--Larry


On Sun, Feb 2, 2014 at 7:55 PM, Willy Sudiarto Raharjo 
will...@slackbuilds.org wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On Mon 03 Feb 2014 08:32:08 AM WIT, Willy Sudiarto Raharjo wrote:
  * *BEGIN ENCRYPTED or SIGNED PART* *
 
  There has been some reports that digikam failed to build when lensfun
  is installed and i can confirm that by reproducing it using a minimum
  dependencies installed (only ffmpeg and opencv)
 
  This morning, i tried to rebuild digikam on a clean VM using all
  optional dependencies installed :lensfun, eigen3, liblqr, libpgf,
  libdc1394, and plus LibRaw (i don't know whether this has an effect or
  not), but it does built perfectly here

 I'm able to narrow it down after some testing on VM
 it seems that libpgf is still optional (it built even when this is
 removed), but liblqr will be needed when you want to build digikam
 against lensfun

 i'm still testing with eigen3 removed and then with libdc1394 removed

 - --
 Willy Sudiarto Raharjo
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.22 (GNU/Linux)
 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

 iEYEARECAAYFAlLvEy0ACgkQiHuDdNczM4FNPgCeMH+8jemziTQj33iuPDJVbuhx
 uIIAoKKhOUxyXhtpu6BsBws19MzmvROV
 =EFsK
 -END 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 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] call for digikam tester

[Larry Hajali]

 Thanks for confirming about this Larry
 i think i will make lensfun and liblqr hard dep for digikam to
 anticipate future releases
 any objection for this idea?

 No objections here.
___
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] Pygame SlackBuild build error

[Larry Hajali]

Bojan,

Just to be clear, the patch you posted is for pygame 1.9.1.  The version
for SBo is for version 1.7.1, which doesn't have a dependency on v4l.

--Larry


On Thu, Jan 9, 2014 at 8:01 AM, Klaatu kla...@straightedgelinux.com wrote:

 On 01/10/2014 04:43 AM, Willy Sudiarto Raharjo wrote:
  On Thu 09 Jan 2014 09:15:04 PM WIT, Bojan Popovic wrote:
  Hi,
 
  It seems Pygame SlackBuild is broken. I tried contacting the
  maintainer but the email bounced back.
 
  Anyways, it seems to be about missing legacy v4l headers from the newer
  kernels. There is a patch in Arch Linux repo that seems to fix the
  issue.
 
 https://projects.archlinux.org/svntogit/packages.git/tree/trunk/pygame-v4l.patch?h=packages/python-pygame
 
  I'm using it for some time now and didn't notice any problems. Pygame
  based games I tried seemed to work.
 
  The warning i got is like this
  Hunting dependencies...
  SDL : found 1.2.15
  FONT: found
  IMAGE   : found
  MIXER   : found
  SMPEG   : found 0.4.5
  NUMERIC : not found
 
 
  Warning, some of the pygame dependencies were not found. Pygame can
  still
  compile and install, but games that depend on those missing dependencies
  will not run. Would you like to continue the configuration? [Y/n]:
 
  but if i answered yes, then the build continue and it built
  is this the one you got?
 
 
  ___
  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/
 
 
 

 I'm using this build for all kinds of Pygame stuff, and it works fine.

 I could be wrong, but I think I read somewhere that Numeric's functions
 are being covered by numpy anyway, so the fact that it is not found
 turns out to be negligible.
 See first answer on:
 http://bytes.com/topic/python/answers/592272-numpy-_numpy-numeric

 -- klaatu
 ___
 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] pysetuptools update

[Larry Hajali]

 python/cssutils
 python/mechanize
 python/netifaces
 python/python-dateutil
 python/python-distutils-extra
 python/python-magic
 python/python2-chardet
 python/rsa
 python/tagpy


Confirmed to be working.

--Larry
___
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] digikam: call for tester

[Larry Hajali]

 Thanks for testing dave
 It seems the culprit is lensfun
 It doesn't properly export the libs when using configure
 I have spoken with the maintainer and he doesn't use it anymore, so i will
 be taking this package and switch to cmake


I'm glad lensfun is being switched to cmake.  There is an extra option to
build the AUXFUN library (not sure what it does) with
'-DDBUILD_AUXFUN:BOOL=ON' and it also creates a proper pkgconfig file.
 I've attached my changes for reference.

--Larry
--- /var/lib/sbopkg/SBo/14.1/libraries/lensfun/lensfun.SlackBuild   
2013-11-25 09:19:36.0 -0800
+++ lensfun.SlackBuild  2013-12-07 11:46:08.982322088 -0800
@@ -67,23 +67,28 @@
  \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
 
-CFLAGS=$SLKCFLAGS \
-CXXFLAGS=$SLKCFLAGS \
-  ./configure \
-  --prefix=/usr \
-  --libdir=/usr/lib${LIBDIRSUFFIX} \
-  --docdir=/usr/doc/$PRGNAM-$VERSION \
-  || exit 1
-
-make install DESTDIR=$PKG || exit 1
+mkdir -p build-$PRGNAM
+cd build-$PRGNAM
+  cmake -G Unix Makefiles \
+-DCMAKE_INSTALL_PREFIX:PATH=/usr \
+-DCMAKE_C_FLAGS:STRING=$SLKCFLAGS \
+-DCMAKE_CXX_FLAGS:STRING=$SLKCFLAGS \
+-DLIB_SUFFIX=$LIBDIRSUFFIX \
+-DDOCDIR:PATH=doc/$PRGNAM-$VERSION \
+-DBUILD_AUXFUN:BOOL=ON \
+-DBUILD_FOR_SSE:BOOL=ON \
+-DBUILD_FOR_SSE2:BOOL=ON \
+-DBUILD_DOC:BOOL=ON \
+-DCMAKE_BUILD_TYPE=Release .. || exit 1
+
+  make VERBOSE=1 || exit 1
+  make install DESTDIR=$PKG || exit 1
+cd -
 
 find $PKG | xargs file | grep -e executable -e shared object \
   | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2 /dev/null
 
-( cd $PKG/usr/man
-  find . -type f -exec gzip -9 {} \;
-  for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
-)
+cat $CWD/$PRGNAM.SlackBuild  $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
 
 mkdir -p $PKG/install
 cat $CWD/slack-desc  $PKG/install/slack-desc
___
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] calibre update tested and reccomendation

[Larry Hajali]

1) Done in next submission.
2) Done in next submission.

--Larry


On Sat, Nov 30, 2013 at 12:15 PM, King Beowulf kingbeow...@gmail.comwrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 I've tested calbire-1.13.0 with the current SBo slackbuild script and
 everything appears A-OK.  Recommendations:

 1. This line does not seems to be needed as the version string appears
 to be correct:
 # Make sure version string is correct.
 sed -i /^numeric_version/s|(.*)|(${VERSION//\./, })|
 src/calibre/constants.py

 It doesn't hurt anything, but sends my minimalist sensibilities all
 a-flutter...

 2. For $PRGNAM-gui.desktop (ie calibre-gui.desktop) I suggest we
 capitalize the menu file name:

 Name=calibre

 to

 Name=Calibre

 Some DE menus will then sort the name name correctly.  For example,
 Xfce sorts capitals before lower case letters (If anyone knows how to
 change that I am all ears).

 - -Ed
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.22 (GNU/Linux)

 iEYEARECAAYFAlKaR08ACgkQXvwMaW61dLevFQCfZW+xPKJgeYBx58CZUcO9rZ8n
 eTwAmQE0d7re6sR9s7AoCNf7/NI3ayAy
 =wPOe
 -END 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 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] Package Maintainer

[Larry Hajali]

 audio/kradio - 4.0.6

I'll take this one.

--Larry
___
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] xmms-status-plugin

[Larry Hajali]

Hi,

The problem seems to be that there is a local version of libtool in the
source directory that is used to link the libraries isn't /lib64 or
/usr/lib64 aware.  I created a simple hack to use the system libtool so
that proper linking works.  You can use it if you'd like.  The static
library is also installed so you may want to manually remove that.

Cheers,
Larry


On Sun, Nov 24, 2013 at 3:29 AM, Petar Petrov
petar.pet...@student.oulu.fiwrote:

 Hi guys

 it seems there's a problem with another entry of mine:
 xmms-status-plugin... It builds and works fine on 32bit system, however on
 a 64bit it builds and installs the file

 usr/lib64/xmms/General/libstatusdocklet.a

 in stead of the proper libstatusdocklet.so

 I do not know how to fix that, searched for a patch, but it seems none of
 the distros I checked ship this anymore. The last release was in 2005
 anyways... So, either just remove it or mark x86_64 as UNSUPPORTED? It's a
 pity, but I guess I was the only one using it anyways.

 Sorry for the inconvenience, i just didn't notice it earlier.

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


diff --git a/desktop/xmms-status-plugin/xmms-status-plugin.SlackBuild 
b/desktop/xmms-status-plugin/xmms-status-plugin.SlackBuild
index ac2da6f..c6fdbca 100644
--- a/desktop/xmms-status-plugin/xmms-status-plugin.SlackBuild
+++ b/desktop/xmms-status-plugin/xmms-status-plugin.SlackBuild
@@ -69,6 +69,9 @@ find -L . \
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 
\) \
  -exec chmod 644 {} \;
 
+# Force the Makefile to use the installed version of libtool.
+sed -i 's|^LIBTOOL =.*|LIBTOOL = /usr/bin/libtool|' $(find . -iname 
Makefile.*)
+
 CFLAGS=$SLKCFLAGS \
 CXXFLAGS=$SLKCFLAGS \
 ./configure \
___
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] installing openoffice 3.3.0 - building error

[Larry Hajali]

On Sat, Aug 24, 2013 at 8:14 AM, Valdir Franco chuck...@gmail.com wrote:

 Hi.

 Trying install openoffice using slackbuild got a error, stopping script.

 SOURCEDIR: unbound variable

 Any hint on fixing it?


Yeah, download the openoffice.org tarball for your particular architecture
and put it in the same folder as the openoffice.org.SlackBuild.  The error
is stating that $SOURCEDIR is not defined because it can't find the tarball.

--Larry
___
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] Transmission: transmission-qt client does not load translations

[Larry Hajali]

1) Qt desktop file is in transmission-$VERSION/qt/transmission-qt.desktop.
 Easy enough to add a line in the slackbuild to install the Qt desktop file.

2) I haven't tried it but gentoo has a translation patch for
transmission-qt.

Version 2.77:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-p2p/transmission/files/transmission-2.77-translations-path-fix.patch?revision=1.1pathrev=MAIN

Version 2.80:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-p2p/transmission/files/transmission-2.80-translations-path-fix.patch?revision=1.1pathrev=MAIN

Larry


On Thu, Aug 15, 2013 at 3:46 AM, Niki Kovacs i...@microlinux.fr wrote:

 Hi,

 I've been using Transmission for the last five years or so, it's my
 favourite BitTorrent client. Until recently I've always used the
 transmission-gtk client, since it integrates nicely into Xfce.

 Currently I'm fiddling with my personal blend of KDE, so I thought I'd
 rather use the transmission-qt client. The program seems to work OK, but :

 1) There's no desktop entry for the Qt client. Which is not a big deal,
 since I can simply create one manually and/or fire it up from a graphical
 terminal.

 2) Translations aren't loaded, the Qt client only displays the interface
 in english. My workstation uses fr_FR.utf8 as locale, and sometimes
 de_DE.utf8.

 I googled about this (transmission-qt translation), and the problem seems
 to affect many users. Various bug reports suggest to simply update, but
 version 2.77 (from SBo) is still affected by it. And I've found no usable
 solution for this yet.

 Any suggestions?

 Niki

 PS: Niels, I'm forwarding this to you, since you're the maintainer.
 --
 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 SlackBuilds-users@slackbuilds.org
 http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**usershttp://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
 Archives - 
 http://lists.slackbuilds.org/**pipermail/slackbuilds-users/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] python setuptools | distribute

[Larry Hajali]

I pick distribute for my python packages because it was actively
maintained.  If upstream maintains setuptools then I have no issue with
this change.

--Larry


On Sat, Jul 13, 2013 at 12:54 AM, Robby Workman rwork...@slackbuilds.orgwrote:

 Everyone who has python packages that depend on distribute
 or setuptools, please have a look at the setuptools branch:
 http://slackbuilds.org/cgit/slackbuilds/log/?h=setuptools

 We've got pysetuptools-0.8 in the ready queue, so I installed
 it and built everything that called for distribute to confirm
 that they still worked.  The results are in that branch.
 If anyone has any objections to merging that branch to master,
 I'd like to hear them :-)

 -RW

 ___
 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] virtualenv SlackBuild

[Larry Hajali]

Yeah, that was me.  I pushed an updated version as I didn't see anyone else
updating it.  I no longer use virtualenv, so whoever wants it is welcome to
own it.

--Larry


On Sun, Jul 7, 2013 at 11:31 PM, Robby Workman rwork...@slackbuilds.orgwrote:

 On Sun, 28 Apr 2013 13:25:17 +0300
 Audrius Kažukauskas audr...@neutrino.lt wrote:

  Hi, slackers,
 
  About a couple of months ago I sent an email to Larry Hajali and
  Vincent Batts asking if one of them could update virtualenv build
  script.  I wrote to them both because Larry had orphaned this script
  (among the others) and Vincent claimed[*] it, but this happened on
  2011-10-24, and since then there were no updates to the script, while
  virtualenv itself had numerous releases.  In other words, I wasn't
  sure who was the current maintainer.
 
  Larry replied that he indeed is not the maintainer anymore.
  Unfortunately, I haven't heard from Vincent at all (I sent the email
  to his hashbangbash.com address), perhaps he was busy with life at
  that time and simply forgot to reply later, or maybe my email was
  eaten by a grue while on its way to Vincent, who knows what really
  happened.
 
  So I'm trying again, this time to this mailing list.  If Vincent isn't
  interested anymore, I'll gladly take over the script.  It's one of
  those tools that are essential to my workflow while writing Python
  code.
 
  [*]
 
 http://lists.slackbuilds.org/pipermail/slackbuilds-users/2011-October/008223.html


 Well, I don't know what happened in the meantime - maybe I made
 some mistake in pushing an updated version of the script, but I
 have this commit just recently:

 commit 3e440ec9bc06d9f5fe780f9e7dec1e4d1cc56584
 Author: Larry Hajali larryhaja[at]gmail[dot]com
 Date:   Sun Jun 2 23:42:07 2013 -0500

 python/virtualenv: Updated for version 1.9.1.

 Signed-off-by: Robby Workman rwork...@slackbuilds.org


 Larry, Vincent, et al  ???

 -RW

___
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] Updates - 20130605.1

[Larry Hajali]

Yes, much obliged to the SBo admins and the maintainers.  It makes for a
very robust system where multiple eyes are looking over the build scripts.

-Larry


On Fri, Jun 7, 2013 at 6:12 AM, Chess Griffin ch...@chessgriffin.comwrote:

 * King Beowulf kingbeow...@gmail.com [2013-06-06 18:19:27]:

  On 06/05/2013 01:33 AM, Robby Workman wrote:
   commit 8f8263186ccc60e69296f64c80b7434451e1a760 Author: Robby
   Workman rwork...@slackbuilds.org Date:   Wed Jun 5 03:20:11 2013
   -0500
  
   Public www update: Wed Jun  5 08:19:26 UTC 2013
  
   It's been seven years since we decided to give this idea a shot, so
   thanks for all of your support over that time. Here's hoping for at
   least seven more productive years...
  
   Signed-off-by: Robby Workman rwork...@slackbuilds.org
  
 
  Congratulations and thanks to all.  SBo has made my life just a bit
  easier these past years.

 Agreed.  Thank you to all the SBo admins, contributors, and maintainers.
 SBo is a fantastic project.

 --
 Chess Griffin
 ___
 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] lilv Slackbuild

[Larry Hajali]

Hi,

I haven't compiled this myself but it looks like the patch from archlinux
might work.

https://projects.archlinux.org/svntogit/packages.git/tree/trunk/lilvmm.patch?h=packages/lilv

It looks like it addresses the errors you are seeing.

--Larry


On Tue, Apr 16, 2013 at 12:40 PM, Jerry Barker je...@woodmanstudio.co.ukwrote:

 Hi, I've been installing the many dependencies required by Ardour V3 on a
 clean Slackware64 V14 system, all went well until I reached lilv.

 The Slackbuild uses lilv-0.14.2 however Ardour requires lilv-0.16.0, I
 changed the program version in the Slackbuild but the resulting Slackbuild
 fails in the build stage.

 I have attached the log of the Slackbuild. The following two lines crop up:
 could not find 
 'lv2/lv2plug.in/ns/lv2core/**lv2.hhttp://lv2plug.in/ns/lv2core/lv2.h
 '
 could not find 
 'lv2/lv2plug.in/ns/ext/urid/**urid.hhttp://lv2plug.in/ns/ext/urid/urid.h
 '

 The files lv2core/lv2.h and urid/urid.h are present in the lv2 folder i.e.
 not at the addresses shown. I tried adding some symbolic links to their
 actual location but the build still failed.

 Lilv does install by using the waf instructions, and I have Ardour up and
 running but there does seem to be a problem with the lilv Slackbuild.

 ___
 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] lilv Slackbuild

[Larry Hajali]

Yeah, I just tested out the patch.  It works on the newer version of lilv,
otherwise, I get the same error you get.  Patch attached.

Apply with:
patch -p2  $CWD/lilvmm.patch

--Larry


On Tue, Apr 16, 2013 at 12:47 PM, Larry Hajali larryh...@gmail.com wrote:

 Hi,

 I haven't compiled this myself but it looks like the patch from archlinux
 might work.


 https://projects.archlinux.org/svntogit/packages.git/tree/trunk/lilvmm.patch?h=packages/lilv

 It looks like it addresses the errors you are seeing.

 --Larry


 On Tue, Apr 16, 2013 at 12:40 PM, Jerry Barker 
 je...@woodmanstudio.co.ukwrote:

 Hi, I've been installing the many dependencies required by Ardour V3 on a
 clean Slackware64 V14 system, all went well until I reached lilv.

 The Slackbuild uses lilv-0.14.2 however Ardour requires lilv-0.16.0, I
 changed the program version in the Slackbuild but the resulting Slackbuild
 fails in the build stage.

 I have attached the log of the Slackbuild. The following two lines crop
 up:
 could not find 
 'lv2/lv2plug.in/ns/lv2core/**lv2.hhttp://lv2plug.in/ns/lv2core/lv2.h
 '
 could not find 
 'lv2/lv2plug.in/ns/ext/urid/**urid.hhttp://lv2plug.in/ns/ext/urid/urid.h
 '

 The files lv2core/lv2.h and urid/urid.h are present in the lv2 folder
 i.e. not at the addresses shown. I tried adding some symbolic links to
 their actual location but the build still failed.

 Lilv does install by using the waf instructions, and I have Ardour up and
 running but there does seem to be a problem with the lilv Slackbuild.

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






lilvmm.patch
Description: Binary data
___
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] qemu and qemu-kvm descriptions could really do with a bit of clarification

[Larry Hajali]

I haven't been keeping track of qemu/qemu-kvm status on the Slackware front
but I believe that qemu/qemu-kvm will be merged in future SBo updates
(reference:
http://lists.slackbuilds.org/pipermail/slackbuilds-users/2013-February/010190.html).
The kqemu is only needed for older versions of qemu for better performance
or older processors that don't have VT (I believe) built into them so that
either kvm-intel/kvm-amd modules are loaded.  So, if you're building the
latest version of qemu, you should not have to worry about kqemu unless
your processor doesn't support it.

To test if you have VT capabilities the run the following
# grep '(vmx|svm)' /proc/cpuinfo

If there isn't any output then your processor doesn't support KVM and you
will need kqemu for better performance.

--Larry


On Mon, Apr 15, 2013 at 4:29 AM, Sebastian Arcus s...@open-t.co.uk wrote:

 I've just spent an hour trying to get my head around to what is the
 difference between qemu and qemu-kvm and which one do I need. I couldn't
 even figure out if they somehow need each other. If it wasn't for the page
 below from the qemu website that states qemu-kvm is actually a fork of qemu
 (which seems to have been absorbed back into the qemu package upstream) I
 would still be trying to figure it all out:

 http://wiki.qemu.org/KVM

 I don't want to start a flame war (in case this is one of those debatable
 topics with supporters on both sides) - but I think the description at SBo
 for both packages could do with a little note that either package can do
 the job (although there probably are some differences between them). Also
 the SBo page for qemu states:

 When used as a virtualizer [...] A host driver called QEMU accellerator
 (also known as KQEMU) is needed.

 Is the above still a valid statement - or does it apply only to processors
 without virtualization extensions? From what I've read so far, it seems
 that the cpu's with virtualization extensions are served by the kvm-intel
 or kvm-amd modules nowadays?

 That is unless I got it all wrong and I still need to research some more
 to get clued up :-)
 __**_
 SlackBuilds-users mailing list
 SlackBuilds-users@slackbuilds.**org SlackBuilds-users@slackbuilds.org
 http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**usershttp://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
 Archives - 
 http://lists.slackbuilds.org/**pipermail/slackbuilds-users/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] qemu and qemu-kvm descriptions could really do with a bit of clarification

[Larry Hajali]

 Also - I can't seem to find a a definite answer anywhere - is it still
 possible to run the current qemu on a processor without the virtualization
 extensions at all? Will it just not use kvm - but still be able to run the
 same virtual machine (just slower)?

Yes, correct.  Qemu will just run slower because the kvm modules are not
loaded.
___
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] Using SBo with distcc

[Larry Hajali]

The following may not work for 100% of use cases but does work in simple
tests with make only on the line taking certain whitespace into account.
There are probably other regex's I'm missing but it probably accounts for
most occurrences.

sed -i 's|^[ \t]*make[ \t\r\n]*$| CC=distcc \$NUMJOBS|'
/var/lib/sbopkg/SBo/*/*/*/*.SlackBuild.sbopkg


On Sat, Apr 13, 2013 at 3:50 PM, openpand...@free.fr wrote:

 Hi !

 I plan to use distcc to compile a lot of SBo packages.
 As i know no other method (maybe there's an easier one ?), i use sed to
 alter the *.SlackBuild.sbopkg :

 This sed job will replace the make $NUMJOBS with make CC=distcc
 $NUMJOBS

 sed '/NUMJOBS/s/make/make CC=distcc/g'
 /var/lib/sbopkg/SBo/*/*/*/*.SlackBuild.sbopkg

 But i don't know how to replace the lines with make only.

 Any tips ?
 ___
 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] acpica's broken link to source code

[Larry Hajali]

An updated acpica is already been approved.  Just needs to be released.

http://slackbuilds.org/cgit/slackbuilds/commit/?h=rworkmanid=f020dfdb2619458a15c6c2e9091c990048de8067


On Sun, Apr 7, 2013 at 12:19 PM, Dimitris Tsagkatakis dtsa...@otenet.grwrote:

 Hi all,

 The link to acpica's source seems broken. Here's a working one:
 https://acpica.org/sites/**acpica/files/acpica-unix2-**20120420.tar.gzhttps://acpica.org/sites/acpica/files/acpica-unix2-20120420.tar.gz

 PS. There is a newer version available (actually 10 of them).
 __**_
 SlackBuilds-users mailing list
 SlackBuilds-users@slackbuilds.**org SlackBuilds-users@slackbuilds.org
 http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**usershttp://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
 Archives - 
 http://lists.slackbuilds.org/**pipermail/slackbuilds-users/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] pyquery broken after lxml update

[Larry Hajali]

Hi Robby,

I didn't patch the 0.6.1 source.  I am providing a diff of what works for
me on the 1.2.4 version of pyquery.  Update it as you like.

Thanks,
Larry

On Sun, Feb 24, 2013 at 12:06 AM, Robby Workman rwork...@slackbuilds.orgwrote:

 On Fri, 28 Dec 2012 15:54:24 -0800
 Larry Hajali larryh...@gmail.com wrote:

  Hi,
 
  Between lxml version 2.x and 3.x, lxml broke out the cssselect module
  into its own separate package.  The version on SBo is definitely
  outdated and incompatible (w/out patching) with the new lxml.
  Looking at the setup.py file on the github page (ie.
  https://github.com/gawel/pyquery), the new version looks to be
  compatible with the new lxml with cssselect and distribute as new
  dependencies.
 
  All that needs to be done is download the latest version of pyquery (
  http://pypi.python.org/packages/source/p/pyquery/pyquery-1.2.4.tar.gz),
  install the new dependencies and change the version number in the
  slackbuild to 1.2.4.  I'm providing a patch with the changes I made
  to get things working.  Now using 'import pyquery' at the python
  command prompt works.
 
  On a side note, there isn't a dependency listed for pysetuptools or
  distribute for version 0.6.1 of pyquery.  It is optional for lxml and
  not listed for BeautifulSoup.


 Since the maintainer hasn't moved on this since then, and since
 you seem to have already done all of this, would you mind
 submitting what you've got, or at least attach some patches I
 can apply to what's currently in the repo?  Perhaps I should just
 go to bed now, but I'm having a bit of trouble wrapping my head
 around exactly what I need to do to fix all of this... :/

 -RW



pyquery.diff
Description: Binary data
___
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] unrar should be discontinued

[Larry Hajali]

I don't use the rar package so I won't comment on that but I do like
Mateo's idea of combining unrar/libunrar packages.

--Larry

On Wed, Feb 20, 2013 at 3:10 PM, JB yocha...@lavabit.com wrote:

 On Wed, 20 Feb 2013 21:35:24 +0100
 Bojan Popovic bo...@mycity.rs wrote:

  Hi,
 
   The unrar SlackBuild should be discontinued.
  
 
  Sorry, I don't agree.

   snip

 
  I'm using a bunch of archivers/unarchivers on my machines and
  basically depend on any of them a lot.
 

   +1

   I recommend pulling the unrar SlackBuild and setting the rar
   SlackBuild to build unrar.
 

   snip

  Anyway, I'm aware of possible conflict between the two packages and
  would suggest trying to find a more sensible sollution instead of
  getting rid of any of the two.
 
  Bojan.
 

   +1


 --
 Man is a religious animal. He is the only religious animal. He is the only
 animal that has the True Religion -- several of them.  -Mark Twain

 ___
 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] 2 Issues

[Larry Hajali]

Sorry, to hijack this thread but there is one more issue.

libmicrohttpd version 0.9.13 is no longer available.  Minimum version
available is 0.9.16.  I have tested the newest one available for version
0.9.25 and it works with the current libmicrohttpd.SlackBuild with only a
version bump.

http://mirror.clarkson.edu/gnu/gnu/libmicrohttpd/libmicrohttpd-0.9.25.tar.gz

I contacted the maintainer located in the libmicrohttpd.info file over a
week ago but haven't heard anything back.

--Larry

On Thu, Feb 14, 2013 at 11:32 AM, Chess Griffin ch...@chessgriffin.comwrote:

 1.  MD5SUM for faenza-icon-theme is incorrect.  The .info file has:

 08a9d1567ee6e90dd5e2c271461c7390

 should be:

 e9bd6106d13017ce06d24b586259ae9c

 2.  Download for epdfview fails - the home page
 (http://trac.emma-soft.com/epdfview/) seems to be gone so maybe a
 download from freebsd distfiles would work in the interim:

 http://ftp.freebsd.org/pub/FreeBSD/distfiles/epdfview-0.1.8.tar.bz2

 --
 Chess Griffin
 ___
 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/

[Slackbuilds-users] uid and gid for vdr

[Larry Hajali]

Hello,

I'm looking at vdr on my own system (ie.
http://linuxtv.org/vdrwiki/index.php/Main_Page) and was looking at running
it as a daemon.  As I was looking at possible users for this package, I
took a look at reserved uid/gid at http://slackbuilds.org/uid_gid.txt.  It
looks like vdr is already defined by using the policyd uid/gid, which in
turn is also used for policyd2.  I found this in the SBo email archive.

http://lists.slackbuilds.org/pipermail/slackbuilds-users/2009-June/004234.html

My question is should this uid/gid be used for vdr or should it be separate
from the uid/gid for policyd2?

BTW...I'm just asking for clarification.  I don't plan on submitting my vdr
slackbuild.

Thanks,
--Larry
___
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] building calibre-0.9.13-x86_64 fails - missing py module

[Larry Hajali]

Hi Cary,

The problem that you are seeing is that python-dateutil has a new
dependency on another python module called six.  The python module six is
in SBo and is listed as a dependency of python-dateutil.  Just install six
and rebuild calibre.

--Larry

On Wed, Feb 6, 2013 at 5:17 PM, Cary c...@sdf.org wrote:

 Hello,

 It looks as though a module needs to be added to REQUIRES= in the
 calibre.info file.
 Using sbopkg, my attempt to upgrade from calibre-0.8.69 to version 0.9.13
 failed with the following error:

 *
 * Running gui
 *

 Traceback (most recent call last):
   File setup.py, line 99, in module
 sys.exit(main())
   File setup.py, line 85, in main
 command.run_all(opts)
   File /tmp/SBo/calibre/setup/__init__.py, line 163, in run_all
 self.run_cmd(self, opts)
   File /tmp/SBo/calibre/setup/__init__.py, line 156, in run_cmd
 self.run_cmd(scmd, opts)
   File /tmp/SBo/calibre/setup/__init__.py, line 159, in run_cmd
 cmd.run(opts)
   File /tmp/SBo/calibre/setup/gui.py, line 37, in run
 self.build_forms()
   File /tmp/SBo/calibre/setup/gui.py, line 60, in build_forms
 from calibre.gui2 import build_forms
   File /tmp/SBo/calibre/src/calibre/gui2/__init__.py, line 21, in
 module
 from calibre.utils.date import UNDEFINED_DATE
   File /tmp/SBo/calibre/src/calibre/utils/date.py, line 13, in module
 from dateutil.tz import tzlocal, tzutc
   File /usr/lib64/python2.7/site-packages/dateutil/tz.py, line 9, in
 module
 from six import string_types, PY3
 ImportError: No module named six


 -
 -end of error msg.
 -

 After building and installing module python/six the upgrade
 of calibre was successful.

 Cary
 ___
 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] Desmume on 64-bit - optimization flag

[Larry Hajali]

Could just add an if statement that will add it to the SLKCFLAGS if it is
detected on the computer.

if grep [^s]sse3 /proc/cpuinfo 2/dev/null; then
  SLKCFLAGS=$SLKCFLAGS -msse3
fi

Not sure if this leads to undesirable results.  I don't have an sse3
capable processor, so I can't test.

--Larry

On Tue, Jan 22, 2013 at 7:42 AM, King Beowulf kingbeow...@gmail.com wrote:

 Add it as a switch option? That way there is a reminder for those
 users who can benefit from ss3 as they might not think of it or
 release otherwise.


 On 1/22/13, Tobias Eichmann slack...@gmail.com wrote:
  On Tue, Jan 22, 2013 at 01:45:54AM -0200, Luis Henrique Mello wrote:
  Hi,
 
  I've noticed that adding '-msse3' to the $SLKCFLAGS on a x86_64 bit
  build improves performance.
 
  - Luis
  ___
  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/
 
 
  Not all x86_64 CPUs support SSE3 (the lowest common denominator is SSE2),
  so
  adding this option by default will render the script unusable for owners
 of
  such CPUs.
 
  - Tobi
 
  --
  Tobias Eichmann, slack...@gmail.com
  LinuxQuestions.org Forum Moderator
  http://www.linuxquestions.org/questions/user/tobisgd-506425/
 
  ___
  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/
 
 

 --
 Sent from my mobile device

 You! What PLANET is this!
 -- McCoy, The City on the Edge of Forever, stardate 3134.0
 ___
 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] Desmume on 64-bit - optimization flag

[Larry Hajali]

Yes, that probably is correct.  But there wasn't good information on sse3
vs. ssse3 when I did a google search.

On Tue, Jan 22, 2013 at 5:29 PM, Luis Henrique Mello
lmello@gmail.comwrote:

 The correct 'if' statement would be:

 if grep ssse3 /proc/cpuinfo 1 /dev/null; then
   SLKCFLAGS=$SLKCFLAGS -msse3
 fi


 On 01/22/2013 02:23 PM, Larry Hajali wrote:

 Could just add an if statement that will add it to the SLKCFLAGS if it
 is detected on the computer.

 if grep [^s]sse3 /proc/cpuinfo 2/dev/null; then
SLKCFLAGS=$SLKCFLAGS -msse3
 fi

 Not sure if this leads to undesirable results.  I don't have an sse3
 capable processor, so I can't test.

 --Larry

 On Tue, Jan 22, 2013 at 7:42 AM, King Beowulf kingbeow...@gmail.com
 mailto:kingbeow...@gmail.com** wrote:

 Add it as a switch option? That way there is a reminder for those
 users who can benefit from ss3 as they might not think of it or
 release otherwise.


 On 1/22/13, Tobias Eichmann slack...@gmail.com
 mailto:slack...@gmail.com wrote:
   On Tue, Jan 22, 2013 at 01:45:54AM -0200, Luis Henrique Mello
 wrote:
   Hi,
  
   I've noticed that adding '-msse3' to the $SLKCFLAGS on a x86_64
 bit
   build improves performance.
  
   - Luis
   __**_
   SlackBuilds-users mailing list
   
 SlackBuilds-users@slackbuilds.**orgSlackBuilds-users@slackbuilds.org
 
 mailto:SlackBuilds-users@**slackbuilds.orgSlackBuilds-users@slackbuilds.org
 

   http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**
 users http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
   Archives - http://lists.slackbuilds.org/**
 pipermail/slackbuilds-users/http://lists.slackbuilds.org/pipermail/slackbuilds-users/
   FAQ - http://slackbuilds.org/faq/
  
  
   Not all x86_64 CPUs support SSE3 (the lowest common denominator
 is SSE2),
   so
   adding this option by default will render the script unusable for
 owners of
   such CPUs.
  
   - Tobi
  
   --
   Tobias Eichmann, slack...@gmail.com mailto:slack...@gmail.com

   LinuxQuestions.org Forum Moderator
   
 http://www.linuxquestions.org/**questions/user/tobisgd-506425/http://www.linuxquestions.org/questions/user/tobisgd-506425/
  
   __**_
   SlackBuilds-users mailing list
   SlackBuilds-users@slackbuilds.**orgSlackBuilds-users@slackbuilds.org
 
 mailto:SlackBuilds-users@**slackbuilds.orgSlackBuilds-users@slackbuilds.org
 

   http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**
 users http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
   Archives - http://lists.slackbuilds.org/**
 pipermail/slackbuilds-users/http://lists.slackbuilds.org/pipermail/slackbuilds-users/
   FAQ - http://slackbuilds.org/faq/
  
  

 --
 Sent from my mobile device

 You! What PLANET is this!
  -- McCoy, The City on the Edge of Forever, stardate 3134.0
 __**_
 SlackBuilds-users mailing list
 SlackBuilds-users@slackbuilds.**orgSlackBuilds-users@slackbuilds.org
 
 mailto:SlackBuilds-users@**slackbuilds.orgSlackBuilds-users@slackbuilds.org
 

 
 http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**usershttp://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
 Archives - http://lists.slackbuilds.org/**
 pipermail/slackbuilds-users/http://lists.slackbuilds.org/pipermail/slackbuilds-users/
 FAQ - http://slackbuilds.org/faq/




 __**_
 SlackBuilds-users mailing list
 SlackBuilds-users@slackbuilds.**org SlackBuilds-users@slackbuilds.org
 http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**usershttp://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
 Archives - 
 http://lists.slackbuilds.org/**pipermail/slackbuilds-users/http://lists.slackbuilds.org/pipermail/slackbuilds-users/
 FAQ - http://slackbuilds.org/faq/


 __**_
 SlackBuilds-users mailing list
 SlackBuilds-users@slackbuilds.**org SlackBuilds-users@slackbuilds.org
 http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**usershttp://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
 Archives - 
 http://lists.slackbuilds.org/**pipermail/slackbuilds-users/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] hitting a problem with a SlackBuild

[Larry Hajali]

Hello Glenn,

You could make a patch to remove the interactive portion of the build
process.  But it would be easier to just echo y to the build script
during configure time.
Eg.
echo y | perl Makefile.PL

On Sat, Dec 29, 2012 at 5:13 PM, Glenn Becker burni...@sdf.org wrote:


 Hi all, and Happy Almost-2013,

 I've been packaging up some Perl modules recently and have run into an
 issue with one that I am not sure how to address.

 Inline is a Perl module that includes a sub-module, Inline::C. When the
 overall build gets to the spot where Inline::C is to be built, it goes
 interactive, a la the following:

 Config.pm indicates that your version of Perl was built with this C
 compiler:

 cc

 I have located this compiler on your system.

 Do you want to install Inline::C? [y]

 Is it acceptable, in this case, to create a diff for this makefile that
 simply skips over the interactive bit and auto-supplies the y? I am not
 sure how else to accomplish this.

 Thanks,

 Glenn
 +-**+
 Glenn Becker - burni...@sdf.org
 SDF Public Access UNIX System - http://sdf.org
 +-**+
 __**_
 SlackBuilds-users mailing list
 SlackBuilds-users@slackbuilds.**org SlackBuilds-users@slackbuilds.org
 http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**usershttp://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
 Archives - 
 http://lists.slackbuilds.org/**pipermail/slackbuilds-users/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] pyquery broken after lxml update

[Larry Hajali]

Hi,

Between lxml version 2.x and 3.x, lxml broke out the cssselect module into
its own separate package.  The version on SBo is definitely outdated and
incompatible (w/out patching) with the new lxml.  Looking at the setup.py
file on the github page (ie. https://github.com/gawel/pyquery), the new
version looks to be compatible with the new lxml with cssselect and
distribute as new dependencies.

All that needs to be done is download the latest version of pyquery (
http://pypi.python.org/packages/source/p/pyquery/pyquery-1.2.4.tar.gz),
install the new dependencies and change the version number in the
slackbuild to 1.2.4.  I'm providing a patch with the changes I made to get
things working.  Now using 'import pyquery' at the python command prompt
works.

On a side note, there isn't a dependency listed for pysetuptools or
distribute for version 0.6.1 of pyquery.  It is optional for lxml and not
listed for BeautifulSoup.

--Larry

On Fri, Dec 28, 2012 at 9:16 AM,   rwx...@tut.bywrote:

 I am sending it here since my attempt to contact the buildscript
 maintainer directly resulted in this:

 Delivery to the following recipient failed permanently:

  email address of the pyquery buildscript maintainer

 Technical details of permanent failure:
 DNS Error: DNS server returned general failure

 Recently buildscript for lxml at SBo got updated (from lxml 2.x to lxml
 3.x). After building the new lxml package and upgrading, I have noticed
 that pyquery (the version that's available on SBo as well and that didn't
 change) is now broken - importing it fails. Here is the traceback from
 ipython:

 --- snip ---
 In [1]: import pyquery
 ---
 ImportError   Traceback (most recent call last)
 ipython-input-1-6c6972830b98 in module()
  1 import pyquery

 /usr/lib64/python2.7/site-packages/pyquery/__init__.py in module()
   8 import webob
   9 except ImportError:
 --- 10 from pyquery import PyQuery
  11 else:
  12 from ajax import PyQuery

 /usr/lib64/python2.7/site-packages/pyquery/pyquery.py in module()
   4 #
   5 # Distributed under the BSD license, see LICENSE.txt
  6 from cssselectpatch import selector_to_xpath
   7 from lxml import etree
   8 import lxml.html

 /usr/lib64/python2.7/site-packages/pyquery/cssselectpatch.py in module()
   4 #
   5 # Distributed under the BSD license, see LICENSE.txt
  6 from lxml.cssselect import Pseudo, XPathExpr, XPathExprOr,
 Function, css_to_xpath, Element
   7 from lxml import cssselect
   8

 /usr/lib64/python2.7/site-packages/lxml/cssselect.py in module()
  16 external_cssselect = __import__('cssselect')
  17 except ImportError:
 --- 18 raise ImportError('cssselect seems not to be installed. '
  19   'See http://packages.python.org/cssselect/')
  20

 ImportError: cssselect seems not to be installed. See
 http://packages.python.org/cssselect/
 --- snip ---

 Just import lxml works.

 I am using Slackware64-14.0 (no multilib).

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





pyquery.diff
Description: Binary data
___
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] pyquery broken after lxml update

[Larry Hajali]

It looks like WebOb and requests are optional dependencies for pyquery.

http://pypi.python.org/pypi/requests
http://pypi.python.org/pypi/WebOb

--Larry

On Fri, Dec 28, 2012 at 3:54 PM, Larry Hajali larryh...@gmail.com wrote:

 Hi,

 Between lxml version 2.x and 3.x, lxml broke out the cssselect module into
 its own separate package.  The version on SBo is definitely outdated and
 incompatible (w/out patching) with the new lxml.  Looking at the setup.py
 file on the github page (ie. https://github.com/gawel/pyquery), the new
 version looks to be compatible with the new lxml with cssselect and
 distribute as new dependencies.

 All that needs to be done is download the latest version of pyquery (
 http://pypi.python.org/packages/source/p/pyquery/pyquery-1.2.4.tar.gz),
 install the new dependencies and change the version number in the
 slackbuild to 1.2.4.  I'm providing a patch with the changes I made to get
 things working.  Now using 'import pyquery' at the python command prompt
 works.

 On a side note, there isn't a dependency listed for pysetuptools or
 distribute for version 0.6.1 of pyquery.  It is optional for lxml and not
 listed for BeautifulSoup.

 --Larry

 On Fri, Dec 28, 2012 at 9:16 AM,   rwx...@tut.bywrote:

 I am sending it here since my attempt to contact the buildscript
 maintainer directly resulted in this:

 Delivery to the following recipient failed permanently:

  email address of the pyquery buildscript maintainer

 Technical details of permanent failure:
 DNS Error: DNS server returned general failure

 Recently buildscript for lxml at SBo got updated (from lxml 2.x to lxml
 3.x). After building the new lxml package and upgrading, I have noticed
 that pyquery (the version that's available on SBo as well and that didn't
 change) is now broken - importing it fails. Here is the traceback from
 ipython:

 --- snip ---
 In [1]: import pyquery

 ---
 ImportError   Traceback (most recent call
 last)
 ipython-input-1-6c6972830b98 in module()
  1 import pyquery

 /usr/lib64/python2.7/site-packages/pyquery/__init__.py in module()
   8 import webob
   9 except ImportError:
 --- 10 from pyquery import PyQuery
  11 else:
  12 from ajax import PyQuery

 /usr/lib64/python2.7/site-packages/pyquery/pyquery.py in module()
   4 #
   5 # Distributed under the BSD license, see LICENSE.txt
  6 from cssselectpatch import selector_to_xpath
   7 from lxml import etree
   8 import lxml.html

 /usr/lib64/python2.7/site-packages/pyquery/cssselectpatch.py in module()
   4 #
   5 # Distributed under the BSD license, see LICENSE.txt
  6 from lxml.cssselect import Pseudo, XPathExpr, XPathExprOr,
 Function, css_to_xpath, Element
   7 from lxml import cssselect
   8

 /usr/lib64/python2.7/site-packages/lxml/cssselect.py in module()
  16 external_cssselect = __import__('cssselect')
  17 except ImportError:
 --- 18 raise ImportError('cssselect seems not to be installed. '
  19   'See http://packages.python.org/cssselect/
 ')
  20

 ImportError: cssselect seems not to be installed. See
 http://packages.python.org/cssselect/
 --- snip ---

 Just import lxml works.

 I am using Slackware64-14.0 (no multilib).

 ___
 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] pyquery broken after lxml update

[Larry Hajali]

The following packages also have lxml as a dependency.  But looking through
the source code it looks like only pyquery is affected by the updated lxml
version.

compiz-boxmenu
calibre
mythtv
pyquery
inkscape
weboob
w3af
openerp-server

--Larry

On Fri, Dec 28, 2012 at 4:13 PM, Larry Hajali larryh...@gmail.com wrote:

 It looks like WebOb and requests are optional dependencies for pyquery.

 http://pypi.python.org/pypi/requests
 http://pypi.python.org/pypi/WebOb

 --Larry


 On Fri, Dec 28, 2012 at 3:54 PM, Larry Hajali larryh...@gmail.com wrote:

 Hi,

 Between lxml version 2.x and 3.x, lxml broke out the cssselect module
 into its own separate package.  The version on SBo is definitely outdated
 and incompatible (w/out patching) with the new lxml.  Looking at the
 setup.py file on the github page (ie. https://github.com/gawel/pyquery),
 the new version looks to be compatible with the new lxml with cssselect and
 distribute as new dependencies.

 All that needs to be done is download the latest version of pyquery (
 http://pypi.python.org/packages/source/p/pyquery/pyquery-1.2.4.tar.gz),
 install the new dependencies and change the version number in the
 slackbuild to 1.2.4.  I'm providing a patch with the changes I made to get
 things working.  Now using 'import pyquery' at the python command prompt
 works.

 On a side note, there isn't a dependency listed for pysetuptools or
 distribute for version 0.6.1 of pyquery.  It is optional for lxml and not
 listed for BeautifulSoup.

 --Larry

  On Fri, Dec 28, 2012 at 9:16 AM,   rwx...@tut.bywrote:

  I am sending it here since my attempt to contact the buildscript
 maintainer directly resulted in this:

 Delivery to the following recipient failed permanently:

  email address of the pyquery buildscript maintainer

 Technical details of permanent failure:
 DNS Error: DNS server returned general failure

 Recently buildscript for lxml at SBo got updated (from lxml 2.x to lxml
 3.x). After building the new lxml package and upgrading, I have noticed
 that pyquery (the version that's available on SBo as well and that didn't
 change) is now broken - importing it fails. Here is the traceback from
 ipython:

 --- snip ---
 In [1]: import pyquery

 ---
 ImportError   Traceback (most recent call
 last)
 ipython-input-1-6c6972830b98 in module()
  1 import pyquery

 /usr/lib64/python2.7/site-packages/pyquery/__init__.py in module()
   8 import webob
   9 except ImportError:
 --- 10 from pyquery import PyQuery
  11 else:
  12 from ajax import PyQuery

 /usr/lib64/python2.7/site-packages/pyquery/pyquery.py in module()
   4 #
   5 # Distributed under the BSD license, see LICENSE.txt
  6 from cssselectpatch import selector_to_xpath
   7 from lxml import etree
   8 import lxml.html

 /usr/lib64/python2.7/site-packages/pyquery/cssselectpatch.py in
 module()
   4 #
   5 # Distributed under the BSD license, see LICENSE.txt
  6 from lxml.cssselect import Pseudo, XPathExpr, XPathExprOr,
 Function, css_to_xpath, Element
   7 from lxml import cssselect
   8

 /usr/lib64/python2.7/site-packages/lxml/cssselect.py in module()
  16 external_cssselect = __import__('cssselect')
  17 except ImportError:
 --- 18 raise ImportError('cssselect seems not to be installed. '
  19   'See http://packages.python.org/cssselect/
 ')
  20

 ImportError: cssselect seems not to be installed. See
 http://packages.python.org/cssselect/
 --- snip ---

 Just import lxml works.

 I am using Slackware64-14.0 (no multilib).

 ___
 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] making a SlackBuild for golly

[Larry Hajali]

It should go without saying that you should run 'removepkg golly-2.4'
before installing the new package.  Otherwise, you'll have 2 programs with
the same contents.

--Larry

On Thu, Dec 27, 2012 at 5:27 AM, Willy Sudiarto Raharjo
will...@gmail.comwrote:

  http://pastebin.com/Dythzi6i
 
  ... my only thought is the eccentric version number might be causing
  problems ...?

 Yes
 you should have this line
 VERSION=${VERSION:-2.4}

 and move -src part to this line
 rm -rf $PRGNAM-$VERSION-src
 tar xvf $CWD/$PRGNAM-$VERSION-src.tar.gz
 cd $PRGNAM-$VERSION-src

 and it should be working as intended


 --
 Willy Sudiarto Raharjo
 Personal Blog : http://willysr.blogspot.com
 Linux Blog: http://slackblogs.blogspot.com
 ___
 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/

[Slackbuilds-users] lockdev submission

[Larry Hajali]

Hello,

I've tried removing the package lockdev from the pending list using the
md5sum listed in the SBo mail on new package submissions.  It currently
doesn't show up in pending/ready list on SBo.  But when I try to submit an
updated package it says it exists and is pending approval.

Can one of the admins remove the package so I can resubmit?

Thanks and Happy Holidays,
--Larry
___
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/