Re: [Slackbuilds-users] gnome-python2-gconf.SlackBuild breaks
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > First I thought it's a missing dependency: > > gnome-python2-gconf > http://slackbuilds.org/repository/14.1/libraries/gnome-python2-gconf/ > > probably requires > > pyorbit http://slackbuilds.org/repository/14.1/python/pyorbit/ > > otherwise build fails with: > >> Note: PyORBit 2.0.1 or later is required by bonobo and gnomeui >> bindings. Download it from: >> http://ftp.gnome.org/pub/GNOME/sources/pyorbit/2.0/ > > > but then I've noticed, gnome-python2-gconf.SlackBuild fails on > this: > >> find $PKG | xargs file | egrep "ELF.*shared object" | cut -f 1 -d >> : \ | xargs strip --strip-unneeded 2> /dev/null > > > After commenting these two lines the package is created without > problems. this works without any changes from what we have in our repo, but i notice this lines during build process The following modules will be built: gconf The following modules will NOT be built: gnome gnome.ui gnomecanvas gnomevfs gnomevfs.bonobo gnome-vfs python module support bonobo bonobo.activation bonobo.ui Note: PyORBit 2.0.1 or later is required by bonobo and gnomeui bindings. so PyORBit is basically an optional dependency and not mandatory here's the build result gnome-python2-gconf: MD5SUM check for gnome-python-2.28.1.tar.bz2 ... OK Building package gnome-python2-gconf-2.28.1-x86_64-1_SBo.tgz ... OK Installing package gnome-python2-gconf-2.28.1-x86_64-1_SBo.tgz ... OK - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlSwwjAACgkQiHuDdNczM4EA/wCaA8ZTTPb64/+0Ei0SGKIhih/M dHkAn2Znq3fPTck9rTBT0H9nT+MQrSOk =6G7n -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/
Re: [Slackbuilds-users] Missing requirement: spice-gtk requires usbredir
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > http://slackbuilds.org/repository/14.1/network/spice-gtk/ >> requires usbredir >> http://slackbuilds.org/repository/14.1/system/usbredir/ >> otherwise: configure: error: usbredir support explicitly >> requested, but some required packages are not available when >> building spice-gtk. > > > Now I see there is: > > # enable support for usbredir and libcacard, if available if > pkg-config --exists libusbredirhost; then usbredir="en"; else > usbredir="dis"; fi if pkg-config --exists libcacard; then > cacard="en"; else cacard="dis"; fi if [ "$GTK" = "2" ]; then > gtkver="2"; else gtkver="3"; fi > > in spice-gtk.SlackBuild (I was building with slpkg). The slackbuild > enabled in my case usbredir automatically, but the build failed, so > I assumed usbredir is missing in REQUIRED... it built fine here using sbopkg on a clean VM vala: MD5SUM check for vala-0.26.0.tar.xz ... OK Building package vala-0.26.0-x86_64-1_SBo.tgz ... OK Installing package vala-0.26.0-x86_64-1_SBo.tgz ... OK spice-protocol: MD5SUM check for spice-protocol-0.12.7.tar.bz2 ... OK Building package spice-protocol-0.12.7-noarch-1_SBo.tgz ... OK Installing package spice-protocol-0.12.7-noarch-1_SBo.tgz ... OK pyparsing: MD5SUM check for pyparsing-2.0.1.tar.gz ... OK Building package pyparsing-2.0.1-x86_64-1_SBo.tgz ... OK Installing package pyparsing-2.0.1-x86_64-1_SBo.tgz ... OK celt051: MD5SUM check for celt-0.5.1.3.tar.gz ... OK Building package celt051-0.5.1.3-x86_64-1_SBo.tgz ... OK Installing package celt051-0.5.1.3-x86_64-1_SBo.tgz ... OK spice: MD5SUM check for spice-0.12.5.tar.bz2 ... OK Building package spice-0.12.5-x86_64-1_SBo.tgz ... OK Installing package spice-0.12.5-x86_64-1_SBo.tgz ... OK spice-gtk: MD5SUM check for spice-gtk-0.25.tar.bz2 ... OK Building package spice-gtk-0.25-x86_64-1_SBo.tgz ... OK Installing package spice-gtk-0.25-x86_64-1_SBo.tgz ... OK - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlSwwZMACgkQiHuDdNczM4GySgCgqCYmNOUeOEhUdJEMDjc54rmv evwAoJn4tjzosa/tOOUvXH1PondPm/8r =CCVp -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/
Re: [Slackbuilds-users] Missing requirement: spice-gtk requires usbredir
On 01/10/2015 05:21 AM, Thomas Szteliga wrote:> spice-gtk http://slackbuilds.org/repository/14.1/network/spice-gtk/ > requires usbredir http://slackbuilds.org/repository/14.1/system/usbredir/ > otherwise: > configure: error: usbredir support explicitly requested, but some > required packages are not available > when building spice-gtk. Now I see there is: # enable support for usbredir and libcacard, if available if pkg-config --exists libusbredirhost; then usbredir="en"; else usbredir="dis"; fi if pkg-config --exists libcacard; then cacard="en"; else cacard="dis"; fi if [ "$GTK" = "2" ]; then gtkver="2"; else gtkver="3"; fi in spice-gtk.SlackBuild (I was building with slpkg). The slackbuild enabled in my case usbredir automatically, but the build failed, so I assumed usbredir is missing in REQUIRED... -- Thomas Szteliga ___ 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] gnome-python2-gconf.SlackBuild breaks
First I thought it's a missing dependency: gnome-python2-gconf http://slackbuilds.org/repository/14.1/libraries/gnome-python2-gconf/ probably requires pyorbit http://slackbuilds.org/repository/14.1/python/pyorbit/ otherwise build fails with: > Note: PyORBit 2.0.1 or later is required by bonobo > and gnomeui bindings. > Download it from: http://ftp.gnome.org/pub/GNOME/sources/pyorbit/2.0/ but then I've noticed, gnome-python2-gconf.SlackBuild fails on this: > find $PKG | xargs file | egrep "ELF.*shared object" | cut -f 1 -d : \ > | xargs strip --strip-unneeded 2> /dev/null After commenting these two lines the package is created without problems. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0
On 01/10/2015 12:48 AM, King Beowulf wrote: > -current already has the new(er) libusb so there is no need to build a > static version. The build system should pickup the system libusb. > Don't forget to read the README! Don't forget usbredir. Please check my http://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-January/013448.html spice-gtk (dependency of virt-manager) already requires usbredir so maybe usbredir should become a default for qemu? -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic 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] Missing requirement: spice-gtk requires usbredir
spice-gtk http://slackbuilds.org/repository/14.1/network/spice-gtk/ requires usbredir http://slackbuilds.org/repository/14.1/system/usbredir/ otherwise: configure: error: usbredir support explicitly requested, but some required packages are not available when building spice-gtk. -- Thomas Szteliga smime.p7s Description: S/MIME Cryptographic Signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Possible typo in python3.SlackBuild
On 01/10/2015 04:45 AM, Audrius Kažukauskas wrote:
On Fri, 2015-01-09 at 13:34:03 -0400, Jim Diamond wrote:
On Fri, Jan 9, 2015 at 17:09 (+1000), Christoph Willing wrote:
On 01/09/2015 04:35 PM, Niki Kovacs wrote:
Hi,
I just noticed a strange line in python3.SlackBuild:
PYVER=${VERSION::3}
I only know this kind of notation:
PYVER=${VERSION:-3}
Is this an error or some special syntax I don't know?
From the Parameter Expansion section of the bash manpage:
${parameter:offset:length}
Substring Expansion. Expands to up to length characters of the
value of parameter starting at the character specified by off-set.
Its not stated there but I presume a blank offset defaults it to 0,
therefore for a VERSION of 3.4.2, PYVER would be set to 3.4
That is fragile code. If VERSION got as high as 3.10.x, Bad Things
would happen.
Agreed, although very unlikely, according to one of Python
developers[*]:
My current expectation is that Python 4.0 will merely be "the release
that comes after Python 3.9". <...>
At the current rate of language feature releases (roughly every 18
months), that means we would likely see Python 4.0 some time in 2023,
rather than seeing Python 3.10.
But I'm still going to future-proof the code by changing the offending
line to
PYVER=$(cut -d. -f1,2 <<< "$VERSION")
unless someone has a better suggestion.
That would work but, just for fun, also:
PYVER=${VERSION%.*}
chris
___
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] Updates - 20150110.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sat Jan 10 00:49:56 UTC 2015 academic/units: Updated for version 2.11. audio/acousticbrainz-client: Added (Acoustic Music Scanner). audio/acousticbrainz-gui: Added (Acoustic Music Scanner). audio/acousticbrainz-music-extractor: Added (Music Extractor). audio/apulse: Allow library path option. audio/jack_capture: Updated for version 0.9.71 + new maintainer. business/ledger: Update HOMEPAGE. business/ledger: Updated for version 3.1 + new maintainer. desktop/catfish: Updated for version 1.2.2. desktop/insync-thunar: Added (Insync thunar integration). desktop/ssr: Updated for version 0.3.2. development/google-webdesigner: Fix permission on .desktop file. development/mono: Updated for version 3.10.0. development/p4v: Updated for version 2014.1.978848. games/minetest: Updated for version 0.4.11. games/minetest_game: Updated for version 0.4.11. games/openmw: Updated for version 0.34.0. games/unknown-horizons: Updated for version 2014.1. gis/Shapely: Updated for version 1.5.2. graphics/blender: Updated for version 2.73. graphics/graphviz: Fix for multilib. graphics/jpegoptim: Remove needless configure option. graphics/nomacs: Updated for version 2.2.0. graphics/photoqt: Update DOWNLOAD url. graphics/phototonic: Updated for version 1.5. graphics/qcad: Added (Open Source CAD). graphics/xdot: Updated for version 0.6 + new maintainer. ham/7plus: Update DOWNLOAD url. ham/svxlink-sounds-en_US-heather-16k: Updated for version 14.08. ham/svxlink: Updated for version 14.08. libraries/MyGUI: Fix VERSION. libraries/libwebp: Added optional python 3 support. libraries/live555: Updated for version 2015.01.04. libraries/ogre: Fix commit ID and MD5SUM. misc/par2cmdline-tbb: Updated for version 0.4_20141125. misc/protobuf: Update DEP. multimedia/cuetools: Updated for version 1.4.0. multimedia/get_iplayer: Updated for version 2.91. multimedia/picard-plugins: Added (MusicBrainz Picard Plugins). multimedia/picard: Updated for version 1.3.2. multimedia/xbmc: Fix DOWNLOAD url. network/copy: Updated for version 1.48.0451. network/courier-authlib: Updated for version 0.66.1. network/courier-imap: Updated for version 4.16.0. network/courier-unicode: Added (Courier Unicode library). network/dnscrypt-proxy: Updated for version 1.4.3. network/dnscrypt-wrapper: Updated for version 0.1.15. network/dropbox: Updated for version 3.0.5. network/etherpoke: Added (scriptable network session monitor). network/insync: Added (Google Drive Client). network/node: Updated for version 0.10.35. network/openntpd: Added (Network Time Protocol client/server). network/pastebincl: Added (submit pastes on Pastebin). network/skylable-sx: Updated for version 1.0. office/xmind: Updated for version 3.5.1 + new maintainer. perl/perl-AnyEvent-HTTP: Added (non-blocking HTTP/HTTPS client). perl/perl-common-sense: Fix DOWNLOAD url. python/python-gflags: Added (Python argument parsing library). python/python3: Report correct extension suffix. python/thunarx-python: Added (Thunar Python Bindings). system/brasero: Updated for version 3.12.0. system/firejail: Added (security sandbox). system/mlterm: Updated for version 3.4.2. system/postgresql: Updated for version 9.4.0. system/profile-sync-daemon: Updated for version 5.60.1. system/redis: Updated for version 2.10.3. system/simpleburn: Added (CD / DVD burning and extraction tool). system/slpkg: Updated for version 2.2.0. system/trmaid: Updated for version 0.3.3. system/unison: Updated for version 2.40.128. system/vagrant: Updated for version 1.7.2. system/virt-manager: Update HOMEPAGE. +--+ - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlSweVUACgkQiHuDdNczM4GnrQCgj3sWIYHiA+z0LnzCz6cPWsIU uk4AnRm3rqL/WEpLpGHLv5bxd6YqsUNB =bErm -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/
Re: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0
thank you! On Jan 9, 2015 3:48 PM, "King Beowulf" wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 01/08/2015 11:26 PM, Ryan P.C. McQuen wrote: > > thanks for the build! > > > > what should i do on current? > > > > http://ryanpcmcquen.com>> > > > > Just run (as root), > > ./qemu.Slackbuild > > - -current already has the new(er) libusb so there is no need to build a > static version. The build system should pickup the system libusb. > Don't forget to read the README! Don't forget usbredir. > > Then read: > http://qemu.weilnetz.de/qemu-doc.html#pcsys_005fusb > > Note that whenever you plug in a USB device, dev nodes are still > root:root for example: > > $ lsusb > ... > Bus 001 Device 013: ID 08ec:0008 M-Systems Flash Disk Pioneers > TravelDrive 2C > ... > > ls -l /dev/bus/usb/001 > total 0 > crw-rw-r-- 1 root root 189, 0 Jan 4 18:33 001 > crw-rw-r-- 1 root root 189, 5 Jan 4 18:33 006 > crw-rw-r-- 1 root lp 189, 6 Jan 4 18:33 007 > crw-rw-r-- 1 root root 189, 12 Jan 7 19:03 013 > > # chown :users /dev/bus/usb/001/013 > > NOW, you can > > $ qemu ... -usb -usbdevice host:08ec:0008 > > or use from within the qemu monitor (cli or gui depending on your > preference): > > (qemu) usb_add host:08ec:0008 > > > > > > - -Ed > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iEYEARECAAYFAlSwaOcACgkQXvwMaW61dLe2MQCfcBAf5dOdBhBASBahEm857Bih > wcIAoJdARLyObNQn67YMXlpAkf8D9zng > =UqRM > -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] ANNOUNCEMENT: qemu-2.2.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/08/2015 11:26 PM, Ryan P.C. McQuen wrote: > thanks for the build! > > what should i do on current? > > http://ryanpcmcquen.com>> > Just run (as root), ./qemu.Slackbuild - -current already has the new(er) libusb so there is no need to build a static version. The build system should pickup the system libusb. Don't forget to read the README! Don't forget usbredir. Then read: http://qemu.weilnetz.de/qemu-doc.html#pcsys_005fusb Note that whenever you plug in a USB device, dev nodes are still root:root for example: $ lsusb ... Bus 001 Device 013: ID 08ec:0008 M-Systems Flash Disk Pioneers TravelDrive 2C ... ls -l /dev/bus/usb/001 total 0 crw-rw-r-- 1 root root 189, 0 Jan 4 18:33 001 crw-rw-r-- 1 root root 189, 5 Jan 4 18:33 006 crw-rw-r-- 1 root lp 189, 6 Jan 4 18:33 007 crw-rw-r-- 1 root root 189, 12 Jan 7 19:03 013 # chown :users /dev/bus/usb/001/013 NOW, you can $ qemu ... -usb -usbdevice host:08ec:0008 or use from within the qemu monitor (cli or gui depending on your preference): (qemu) usb_add host:08ec:0008 - -Ed -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlSwaOcACgkQXvwMaW61dLe2MQCfcBAf5dOdBhBASBahEm857Bih wcIAoJdARLyObNQn67YMXlpAkf8D9zng =UqRM -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/
Re: [Slackbuilds-users] Possible typo in python3.SlackBuild
On Fri, 2015-01-09 at 13:34:03 -0400, Jim Diamond wrote:
> On Fri, Jan 9, 2015 at 17:09 (+1000), Christoph Willing wrote:
>
> > On 01/09/2015 04:35 PM, Niki Kovacs wrote:
> >>Hi,
>
> >>I just noticed a strange line in python3.SlackBuild:
>
> >>PYVER=${VERSION::3}
>
> >>I only know this kind of notation:
>
> >>PYVER=${VERSION:-3}
>
> >>Is this an error or some special syntax I don't know?
>
> > From the Parameter Expansion section of the bash manpage:
>
> > ${parameter:offset:length}
> > Substring Expansion. Expands to up to length characters of the
> > value of parameter starting at the character specified by off-set.
>
> > Its not stated there but I presume a blank offset defaults it to 0,
> > therefore for a VERSION of 3.4.2, PYVER would be set to 3.4
>
> That is fragile code. If VERSION got as high as 3.10.x, Bad Things
> would happen.
Agreed, although very unlikely, according to one of Python
developers[*]:
My current expectation is that Python 4.0 will merely be "the release
that comes after Python 3.9". <...>
At the current rate of language feature releases (roughly every 18
months), that means we would likely see Python 4.0 some time in 2023,
rather than seeing Python 3.10.
But I'm still going to future-proof the code by changing the offending
line to
PYVER=$(cut -d. -f1,2 <<< "$VERSION")
unless someone has a better suggestion.
[*] http://opensource.com/life/14/9/why-python-4-wont-be-python-3
--
Audrius Kažukauskas
http://neutrino.lt/
pgpXx2vncDZ9d.pgp
Description: PGP signature
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Catfish not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/09/2015 04:43 AM, Willy Sudiarto Raharjo wrote: >> My base Slackware system contains everything except KDE. > >> And here's a list of extra stuff that's installed on my system: > >> http://www.microlinux.fr/slackware/desktop-14.1-64bit/ChangeLog.txt > >> Any idea what's going on here? > > Most of us tested the packages in a clean environment with full > installation a "pollutted" environment can make debugging harder > since more packages means more combination to test > > Niki Just tested on my "polluted" box: Slackware64 14.1 multilib (full install, updated last week). Most add-ins from SBo (some customized or newer versions), some "rolled my own" (eq WINE), some from AlienBOB (with or without my bastardizations). Just too numerous, as well as pointless to list. I also have both wxPython-2.8.12.1-x86_64-1_SBo wxGTK3-3.0.1-x86_64-1_SBo installed (with wxPython-2.8 installed after wxGTK3 se README). So I would say, there either is a hidden dependency on KDE, or your installation is screwed up somewhere. I have many of your same gnome/* installed, but that is where I'd start. As per the discussion here in the past, IRC, and linuxquestions, ALWAYS test on a clean default install. Good Luck! Ed -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlSwIWQACgkQXvwMaW61dLfllgCdHN4NvHQ8mwwWkCdUa1YjcAhp ExUAnj0zibzMkfJa+ji3kAm4q0py+KZt =1lmf -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/
Re: [Slackbuilds-users] Possible typo in python3.SlackBuild
On Fri, Jan 9, 2015 at 17:09 (+1000), Christoph Willing wrote:
> On 01/09/2015 04:35 PM, Niki Kovacs wrote:
>>Hi,
>>I just noticed a strange line in python3.SlackBuild:
>>PYVER=${VERSION::3}
>>I only know this kind of notation:
>>PYVER=${VERSION:-3}
>>Is this an error or some special syntax I don't know?
> From the Parameter Expansion section of the bash manpage:
> ${parameter:offset:length}
> Substring Expansion. Expands to up to length characters of the
> value of parameter starting at the character specified by off-set.
> Its not stated there but I presume a blank offset defaults it to 0,
> therefore for a VERSION of 3.4.2, PYVER would be set to 3.4
That is fragile code. If VERSION got as high as 3.10.x, Bad Things
would happen.
Cheers.
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/
Re: [Slackbuilds-users] Postfix-2.11.3 test warning message
On Fri, 9 Jan 2015, Mario Preksavec wrote: You are very welcome, although it would probably make more sense to clean up paths in configuration files and avoid post-install file hackery... :-) Mario, That does make sense, but there were no path changes unless as a result of the postfix upgrade from 2.11.2 to 2.11.3. And, in that case, either postfix or the SBo build script should have accommodated it. When the next upgrade is installed we'll see if the issue re-appears. If it does, then further digging to find what's different in my system would be warranted. Rich ___ 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] Catfish not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > My base Slackware system contains everything except KDE. > > And here's a list of extra stuff that's installed on my system: > > http://www.microlinux.fr/slackware/desktop-14.1-64bit/ChangeLog.txt > > Any idea what's going on here? Most of us tested the packages in a clean environment with full installation a "pollutted" environment can make debugging harder since more packages means more combination to test - -- Willy Sudiarto Raharjo -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlSvzPEACgkQiHuDdNczM4F1RgCfeIMELUnJ049Qgfj14U2Mt74Y RfcAn2TSj+bW0AI/MPK1F23uO7Wj9Fg1 =Q2m9 -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/
Re: [Slackbuilds-users] Catfish not working
Le 09/01/2015 08:41, King Beowulf a écrit : Compiling catfish-1.2.1 from SBo manually, no sbopkg etc. Clean Slackware64 14.1 qemu VM (updated) pexpect-3.2 pyxdg-0.25 pygobject3-3.10.1 Compiles fine. No issues or errors. Appears to run OK in XFCE inside the Slackware64 guest. I would think, based on my testing tonight, that catfish removal from SBo is premature. Hmmm. I'm puzzled. My base Slackware system contains everything except KDE. And here's a list of extra stuff that's installed on my system: http://www.microlinux.fr/slackware/desktop-14.1-64bit/ChangeLog.txt Any idea what's going on here? BTW, in the meantime, I've reverted to the GTK2-based 0.32 version of Catfish, which works fine. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Lxpanel build issue
On Thu, 8 Jan 2015 22:09:09 +0700 Willy Sudiarto Raharjo wrote: > > > It worked when I installed libfm-extra - excellent! > > That is not noted as a dependency., it should be mentioned. > > Thank you for your help. > > REQUIRES only list first level of dependency, so you need to check > whether a dependency requires another package or not I simply use > sbopkg + sqg to generate all the queues files which list all the dep > and build it using a correct order > > Willy Sudiarto Raharjo Ah, I only checked Lxpanel because I did the Sbopkg thing - and menu-cache built without errors. Thank you! All the best, Morten ___ 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] Catfish not working
Le 06/01/2015 11:17, David Spencer a écrit : It looks like this: http://bugs.python.org/issue17998 which affects python-2.7.5. You could try SBo's python3? That would probably be neater than building your own python-2.7.6+ to replace Slackware's. I followed your suggestion and installed pycairo3, gnome-common and python3. I upgrade Catfish, and now I have: ImportError: No module named gi.repository I suggest removing Catfish from SBo, since this is clearly not working. Cheers, Niki Hi. I'm the maintainer. Nobody else has come forward with any problems with it. I can compile it just fine on a stock 14.1 system, with only the deps that are currently on sbo for 14.1. Dave ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
