Re: [Slackbuilds-users] borgbackup msgpack-python problem
On Wed, 2018-12-05 at 17:42:27 -0800, David O'Shaughnessy wrote: > I'm having trouble with borgbackup on 14.2_64. Here's the error message > upon running borg init . <...> > > pkg_resources.DistributionNotFound: The 'msgpack- > > python!=0.5.0,!=0.5.1,!=0.5.2,!=0.5.3,!=0.5.4,!=0.5.5,<=0.5.6,>=0.4.6' > > distribution was not found and is required by borgbackup> > > I've tried uninstalling and reinstalling borgbackup and all > dependencies, but no luck yet. The msgpack-python installed is 0.5.6, so > that should be ok? I was hit by this as well a week or two ago, but was too tired and annoyed to investigate the root of this issue, so what I've done was a stupid, yet effective workaround -- I commented out msgpack-python line in /usr/lib64/python3.6/site-packages/borgbackup-1.1.7-py3.6.egg-info/requires.txt file and things were functional again. But now I got curious and looked around a bit. Here's what I dug up: the problem here is that borgbackup requires msgpack-python while upstream of the latter switched its name to msgpack (without -python suffix). borgbackup devs are aware of this change and will fix it eventually (if they haven't already), but what we can do right now is add the following to borgbackup.SlackBuild somewhere before the line that calls 'python3 setup.py install': sed -i 's/msgpack-python/msgpack/' setup.py -- Audrius Kažukauskas ___ 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] Fix for iotop issue with 4.4.144 kernel
Hi, Jason, On Sun, 2018-08-19 at 00:27:25 -0400, Jason Graham wrote: > Hi, > > iotop is broken with the latest Slackware kernel. I've included the > maintainer here, but also posting the note and a patch for the iotop > SlackBuild to the list for further review. > > A few comments regarding the issue and patch: > > Recent kernels, including Slackware's 4.4.144 kernel, have introduced at > least one blank line in /proc//status which breaks the > parse_proc_pid_status() function in iotop/data.py. The patch > fix-proc-status-read.patch updates this > function to skip empty lines. > > Additional reports of this issue can be found here: > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1584612 > [2] > https://unix.stackexchange.com/questions/446624/error-with-command-iotop-on-centos > [3] https://bugs.launchpad.net/pkg-website/+bug/1773383 > > The fix is based on the report in [2]. Thanks for the heads up. I was on holiday for the last couple of weeks and just now getting back to computer stuff (including SlackBuilds). I'll submit the fix as soon as I can. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Unable to build runc (for docker)
Hi, Duncan, On Sat, 2018-04-14 at 22:41:14 +1000, Duncan Roe wrote: > Does "go help buildmode" work for you? What does "go version" show? I get > > go version go1.4.2 gccgo (GCC) 5.3.0 linux/amd64 You're missing one bit that's described in google-go-lang's README (and what Willy was hinting at): The tools are added to the path by putting go.sh and go.csh files in /etc/profile.d and letting the system's /etc/profile or /etc/csh.login pick it up. Since you haven't logged out and logged in yet (or sourced /etc/profile.d/go.sh manually), your shell session is still trying to use gcc-go instead of google-go-lang. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] openDKIM questions
On Wed, 2017-11-22 at 06:31:59 -0800, Rich Shepard wrote: > I tried to directly contact Gerado Zamudio, the opendkim package > maintainer, but the message bounced: His name is Gerardo -- you missed the second "r", the same typo is in the email address you've used. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Updates - 20170916.1
On Sun, 2017-09-17 at 10:23:51 +1200, Andrew Clemons wrote: > On 2017-09-16 13:44:10 +0300, audr...@neutrino.lt wrote: > > Maybe something changed at GitHub itself after I downloaded them? > > ^ this > > https://github.com/libgit2/libgit2/issues/4343#issuecomment-328631745 Thanks for the link, that explains it. I guess there's nothing we can do about it, only update the checksums when we find they have changed. Also forgot to thank Willy for updating all the checksums for my scripts, I appreciate it. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Updates - 20170916.1
On Sat, 2017-09-16 at 17:00:52 +0700, Willy Sudiarto Raharjo wrote: > There's a chance that upstream re-upload the tar.gz source again with a > minor change? These archives are generated by GitHub from git commits or tags, so they're not really uploaded. Extracted content is identical according to diff, file timestamps look the same as well. Maybe something changed at GitHub itself after I downloaded them? -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Updates - 20170916.1
On Sat, 2017-09-16 at 08:18:33 +0700, Willy Sudiarto Raharjo wrote: > > system/containerd: Updated for version 0.2.9_6e23458. > > system/docker-machine: Updated for version 0.12.2. > > system/docker-proxy: Updated for version 20170120_7b2b1fe. > > system/docker: Updated for version 17.06.2. > > system/runc: Updated for version 1.0.0_rc3_810190c. > > It seems some of the docker updates have invalid MD5SUM values. > i have pushed the fixes on my branch Well, this is strange. I still have all the tarballs downloaded when I was updating docker-related build scripts (it was last Sunday). I checked all of them and their MD5 checksums match the ones in .info files. But when I downloaded runc tarball now, its checksum is different, although there are no apparent changes. Both times I used wget to download the tarballs. Has anyone got a clue what happened here? -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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
On Fri, 2017-07-14 at 11:17:31 -0700, Rich Shepard wrote: > On Fri, 14 Jul 2017, Larry Hajali wrote: > > I don't know about all of the packages above but I think virtualenv comes > > with python3. > > Not here. I just upgraded python3 from 3.6.0 to 3.6.1. There's no > virtualenv in /usr/lib/python3/site-packages/. virtualenv is included in Python 3 Standard Library as venv[*] module. The name of executable is pyvenv, but it was deprecated recently, although it's still there and usable: The pyvenv script has been deprecated as of Python 3.6 in favor of using python3 -m venv to help prevent any potential confusion as to which Python interpreter a virtual environment will be based on. Regarding other packages you have listed, you'll need to rebuild them using python3, I don't see any other way around it. [*] https://docs.python.org/3/library/venv.html -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Updates - 20170701.1 youtube-dl
On Sun, 2017-07-02 at 14:25:16 +0200, Andrzej Telszewski wrote: > But still, plain wget happily saves with the filename as in the last url > path component. > > This all adds up to the confusion. > > Would telling maintainers to use wget with --content-disposition help > solving the problem? I don't know, but following the instructions from David to create download URL for GitHub makes this a non-issue, see below. > > It seems that the way GitHub handles download URLs still confuses > > people, though I can't blame them, it really isn't obvious at first. > > I'd recommend to read this really good explanation by David Spencer: > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-February/018447.html > > That's really valuable reading. > But I don't think it talks about the problem we have here. It does in a way that it explains how to construct GitHub download URL so that its last component would be the same as the filename in Content-Disposition header. That way it doesn't matter if HTTP user agent (be it web browser or wget, curl, etc) uses the last component of URL or Content-Disposition to name the file, it will be the same in all cases. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Updates - 20170701.1 youtube-dl
On Sat, 2017-07-01 at 22:19:39 +0200, Andrzej Telszewski wrote: > On 01/07/17 03:11, Willy Sudiarto Raharjo wrote: > > network/youtube-dl: Updated for version 2017.06.25. > > I'm facing the same download error as I mentioned previously regarding > youtube-dl, i.e. the tarball is saved with underscore replaced with hyphen. The underscore is actually not replaced, whatever you're using to download the file honours Content-Disposition header which tells what filename to use when saving a file. In this case it's youtube-dl-2017.06.25.tar.gz You can inspect that yourself by invoking the following: curl -sIL https://github.com/rg3/youtube-dl/archive/2017.06.25/youtube_dl-2017.06.25.tar.gz | grep ^Content-Disposition For download URL to work the same way regardless of Content-Disposition, the last component of URL should use hyphen instead of underscore. In other words, your patch is correct fix. > As a side note, when the tarball is saved: > - Firefox replaces the underscore _ with hyphen - , > - wget keeps whatever it was invoked with, > - slackrepo behaves like Firefox. It seems that the way GitHub handles download URLs still confuses people, though I can't blame them, it really isn't obvious at first. I'd recommend to read this really good explanation by David Spencer: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-February/018447.html -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] letsencrypt users
On Thu, 2017-06-15 at 22:45:25 +0700, Willy Sudiarto Raharjo wrote: > Audrius > Thanks for spotting that. It build fine without it, so we never notice > it. I will add them to python-requests. I searched for scripts that require both python-requests and one of its four new dependencies. Found these: (have python-certifi) development/jupyter-nbdime multimedia/Mopidy system/salt (have python-urllib3) libraries/dropbox-python network/deis system/virt-manager My understanding is that admins prefer that maintainers only list first level dependencies, so both python-certifi and python-urllib3 can be dropped from all the listed packages REQUIRES, since these requirements are now satisfied by python-requests. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] letsencrypt users
On Thu, 2017-06-15 at 22:45:25 +0700, Willy Sudiarto Raharjo wrote: > Audrius > Thanks for spotting that. It build fine without it, so we never notice > it. I will add them to python-requests. One small note: your changes to python/idna mangled years on copyright line, probably the result of '2.1' regexp where dot here matches any character (should have been '2\.1' instead). -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] letsencrypt users
On Thu, 2017-06-15 at 20:55:37 +0700, Willy Sudiarto Raharjo wrote: > after further testing, it requires more than python-certifi > here's what i need to do in order for LE to work again > - python-certifi (new dep) > - python-chardet-3.0.4 (new dep and bump new version) > - idna-2.5 (bump new version) > - python-urllib3-1.21.1 (bump new version) > > maintainers, can we bump those three scripts that belongs to you? Willy, these four are actually direct dependencies of python-requests, as can be seen in its setup.py. You should add them to python-requests REQUIRES instead of letsencrypt. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Updates - 20170415.1
On Sat, 2017-04-15 at 07:58:10 +0700, Willy Sudiarto Raharjo wrote: > Lastly, Ryan has orphaned the remaining of his scripts. Anyone > interested to take over can directly submit an update via submission > form as usual. Looks like Ryan accidentally added a helper script which was used to orphan his remaining builds: https://slackbuilds.org/cgit/slackbuilds/commit/?id=b320b5e -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Updates - 20170408.1
On Sat, 2017-04-08 at 13:24:59 +0300, Audrius Kažukauskas wrote: > On Sat, 2017-04-08 at 07:35:53 +0700, Willy Sudiarto Raharjo wrote: > > libraries/lua-mpack: Updated for version 1.0.6. > > The actual MD5SUM I get (8870b151c71234435b5d21f1f825aa17) differs from > the one in .info file. I was too quick to post this, because it doesn't build as well, there are some source files missing. It seems that the correct download URL should be https://github.com/libmpack/libmpack-lua/releases/download/1.0.6/libmpack-lua-1.0.6.tar.gz and not the one provided in .info file. This file has the correct MD5SUM and the package builds correctly. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Updates - 20170408.1
On Sat, 2017-04-08 at 07:35:53 +0700, Willy Sudiarto Raharjo wrote: > libraries/lua-mpack: Updated for version 1.0.6. The actual MD5SUM I get (8870b151c71234435b5d21f1f825aa17) differs from the one in .info file. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Is the pyparsing SlackBuild still needed?
On Sat, 2017-03-25 at 03:55:25 +0100, Kees Theunissen wrote: > Hello, > > The slackware package python-setuptools-22.0.5-x86_64-1 contains > /usr/lib64/python2.7/site-packages/pkg_resources/_vendor/pyparsing.py > and > /usr/lib64/python2.7/site-packages/pkg_resources/_vendor/pyparsing.pyc > > So I'm wondering if there is still a need for a separate pyparsing SBo > SlackBuild? > > The pyparsing SlackBuild is currently required as a first level > dependency by: spice packaging pydot matplotlib sqlpp11 snuggs puddletag > flexget enki plaso targetcli-fb letsencrypt _vendor directory here contains embedded third party libraries which are meant for internal use by setuptools only, likely because it requires exact versions of those libraries. There's no guarantee that those embedded libraries will even be there for newer setuptools versions. It's really not a good idea to use them by anything else other than setuptools. Vendoring third party code is not unusual, another well known project that does this is python-requests. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Ready queue undefined offset
On Fri, 2017-03-24 at 10:13:19 +0100, Matteo Bernardini wrote:
> 2017-03-24 9:57 GMT+01:00 Andrzej Telszewski <atelszew...@gmail.com>:
> > Hi,
> >
> > At https://slackbuilds.org/ready/
> >
> > Notice: Undefined offset: 1 in /slackbuilds/.ready/index.php on line 17
> > Notice: Undefined offset: 2 in /slackbuilds/.ready/index.php on line 20
> > [..]
>
> I thinks that happens because the commit message is missing in the
> formatting the "${category}/${slackbuild_name}: " prefix.
Yeah, looks like those commits without category and SlackBuild name at
the top of the list are the culprit. Some of them change more than one
SlackBuild and should be split as well.
--
Audrius Kažukauskas
signature.asc
Description: PGP signature
___
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] Potentially conflicting commits for system/runc
Hi, I see in https://slackbuilds.org/ready/ that there are two commits for system/runc, one in my branch (user/audriusk/updates) and another one probably in user/urchlay/updates, though I'm not certain about that. The latter commit only removes trailing spaces in .info file and could potentially conflict with my commit which changes much more in this file. Could this commit with cosmetic changes be removed please? -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] docker update
On Mon, 2017-03-20 at 00:27:27 +0700, Willy Sudiarto Raharjo wrote: > > It's been a week and Asaf hasn't replied neither directly to me nor to > > this list. Meanwhile I updated the scripts for version 17.03.0 and have > > been using them without any problems at work. > > > > Question to the admins: should I wait longer or should I take over > > ownership and submit updated SlackBuilds for runc, containerd and > > docker? > > push it Went ahead and pushed the updates (and a couple of new submissions as well). Docker set of packages now consists of: runc containerd docker-proxy tini docker All components use exact git commits expected by docker 17.3.0. As for additional tool docker-compose, you can fetch it from https://github.com/docker/compose/releases by following provided instructions or (since it's a Python app) install it inside virtualenv (works with both Python 2 and 3) using: pip install docker-compose It seems that there will be a new version (17.3.1) released next Monday (currently at rc1), but I thought that it's better to push scripts for version I've been testing the last few days and know that it's functioning correctly. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] docker update
On Sun, 2017-03-12 at 19:46:54 +0200, Audrius Kažukauskas wrote: > Hi, Asaf, > > About a month ago Vincent Batts, the current maintainer of Docker > SlackBuild, wrote[0] in slackbuilds-users mailing list that he was > giving away ownership of this build script to you, but you haven't > followed to date. > > Are you still interested in taking over this script? I'm asking because > recently I had a need to work on a project using Docker at work and I've > been working on my own update for the latest version of Docker (17.03.0 > at the time of writing). If you're planning to submit the updated > SlackBuild soon, it would save me (and many others) quite some effort. > > But if you're no longer interested, I'm willing to take over ownership > of docker (if it's OK with Vincent), as well as runc and containerd (the > dependencies of latest Docker versions), which you are the maintainer > of. > > (Sending this to slackbuilds-users mailing list as well, because another > person[1] have had difficulty contacting Asaf recently). > > [0] > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-January/018052.html > [1] > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-March/018627.html It's been a week and Asaf hasn't replied neither directly to me nor to this list. Meanwhile I updated the scripts for version 17.03.0 and have been using them without any problems at work. Question to the admins: should I wait longer or should I take over ownership and submit updated SlackBuilds for runc, containerd and docker? -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] docker update
Hi, Asaf, About a month ago Vincent Batts, the current maintainer of Docker SlackBuild, wrote[0] in slackbuilds-users mailing list that he was giving away ownership of this build script to you, but you haven't followed to date. Are you still interested in taking over this script? I'm asking because recently I had a need to work on a project using Docker at work and I've been working on my own update for the latest version of Docker (17.03.0 at the time of writing). If you're planning to submit the updated SlackBuild soon, it would save me (and many others) quite some effort. But if you're no longer interested, I'm willing to take over ownership of docker (if it's OK with Vincent), as well as runc and containerd (the dependencies of latest Docker versions), which you are the maintainer of. (Sending this to slackbuilds-users mailing list as well, because another person[1] have had difficulty contacting Asaf recently). [0] https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-January/018052.html [1] https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-March/018627.html -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Request to remove obsolete build scripts
On Fri, 2016-08-26 at 05:22:23 +0300, Dimitris Zlatanidis wrote: > On 08/25/2016 10:59 PM, Audrius Kažukauskas wrote: > > Could admins please remove the following obsolete build scripts? > > > > network/node (replaced by development/nodejs) > > python/pep8 (replaced by python/pycodestyle) > > python/autopep8 still uses pep8 as dependency, until version 2.0 release. Now that Dimitris pushed the latest version of autopep8 which depends on pycodestyle instead of pep8 and there are no longer any build scripts depending on it, could pep8 finally be removed? Thanks. -- Audrius Kažukauskas signature.asc Description: PGP signature ___ 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] Updates - 20161231.1
On Mon, 2017-01-02 at 01:16:32 +0100, Andrzej Telszewski wrote: > Maybe slackrepo does not allow to download something needed by the Python > install script. I don't know slackrepo well enough, but this seems likely. > But it shouldn't be downloaded in the first place. > > I don't know enough about Python installation scripts to say the final word. borgbackup's setup.py contains the following line: setup_requires=['setuptools_scm>=1.7'], Thus setuptools_scm should really be a requirement for borgbackup. setuptools documentation has this description of setup_requires field: A string or list of strings specifying what other distributions need to be present in order for the setup script to run. setuptools will attempt to obtain these (even going so far as to download them using EasyInstall) before processing the rest of the setup script or commands. <...> This explains why the build succeeded for Willy and, if slackrepo does indeed disable network access, why it didn't for you. -- Audrius Kažukauskas http://neutrino.lt/ signature.asc Description: PGP signature ___ 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] Questions about pending python3 changes
Hi, I noticed that Willy added a patch for python3 to change a comment in one of header files from C++ style to C. I'm not objecting it, just want to understand if there's a particular reason for this change, e.g. suppressing compiler warning or some build issues. And may I suggest that you change the patch filename to something more specific like python3.fix-comment-style.patch. Regarding a fix for enum34, which disables python3 support, I was surprised that it was there in the first place, because starting from version 3.4 (hence the name enum34) enum module is part of Python's standard library. The purpose of enum34 is to bring this functionality to previous Python versions. Maybe the maintainer, Dimitris Zlatanidis, could comment on why enum34 SlackBuild had python3 support. -- Audrius Kažukauskas http://neutrino.lt/ signature.asc Description: PGP signature ___ 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] Python 3.6.0
Hi, As some of you may already know, Python 3.6.0 was released on 2016-12-23. I was asked by a few people to update the SlackBuild for this new version, so here it is: https://slackbuilds.org/cgit/slackbuilds/commit/?h=user/audriusk/python36=3cdaabce13f27bdeddea4ded2033ff02474ff0ea I deliberately pushed it to a separate user/audriusk/python36 branch, because more and more software in SBo depends on Python 3 and some of it may not build or work correctly with the latest version, especially when just a few days have passed from its release date. So instead of pushing version 3.6.0 immediately for weekly batch of updates, I'm keeping it in this separate branch and asking all the maintainers who have scripts depending on python3 to test it out and report any problems here. If something is not ready yet for version 3.6, we can keep this update for awhile instead of merging it to master. Otherwise it will be good to go for the next public update. Thanks and happy holidays to all of you! -- Audrius Kažukauskas http://neutrino.lt/ signature.asc Description: PGP signature ___ 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] Request to remove obsolete build scripts
Hi, Could admins please remove the following obsolete build scripts? network/node (replaced by development/nodejs) python/pep8 (replaced by python/pycodestyle) Thanks. -- Audrius Kažukauskas http://neutrino.lt/ signature.asc Description: PGP signature ___ 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] Blender
On Sat, 2016-01-02 at 12:57:53 +0200, Panagiotis Nikolaou wrote: > Hi to all and happy new year! > I have notice Blender needing "libpython3.4m.so.1.0", while python3 > (3.5.1) provides "libpython3.5m.so.1.0". > This makes Blender impossible to run without downgrading to an older > python3 version or make a symlink > from "libpython3.5m.so.1.0" to "libpython3.4m.so.1.0". You have Blender linked against Python 3.4, now you need to rebuild it to link against Python 3.5. This is nothing Blender specific, you need to do that for every package that links against Python 3.4. -- Audrius Kažukauskas http://neutrino.lt/ signature.asc 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] pysetuptools 8 implements PEP 440
On Mon, 2014-12-22 at 21:21:17 +0100, Markus Reichelt wrote: just a heads-up wrt pysetuptools 8+ #tahoe-lafs on freenode: dstufft setuptools 8 implements PEP 440 dstufft PEP 440 makes the meaning of , change from a bunch of arbitrary confusing crap that PJE invented in the past to AND related: https://gist.github.com/kylemanna/a22e7c37e5ff1f9286c2 tl;dr: if you can, keep pysetuptools 8 I pushed updates for pysetuptools, pip and virtualenv latest versions. I feel that we waited long enough for things to settle down, and most of the issues related to PEP 440 should be solved either by setuptools devs (if there were any bugs in their code) or by upstream of other projects depending on setuptools. Regarding allmydata-tahoe, developers fixed version specifiers in their Git repo, but there doesn't seem to be any versions released with those fixes, so I extracted them into a patch (attached). It works for me with setuptools 12.0.5, but I only installed allmydata-tahoe and tried to run tahoe --version, so please test it and see if everything works correctly. For other maintainers of packages depending on setuptools: if your package won't build with latest setuptools, see if there's newer version released. If there isn't, read PEP 440 version specifier section[*] and try fixing it yourself, it's not very complicated. Although in most cases I expect that everything will work as before. [*] https://www.python.org/dev/peps/pep-0440/#version-specifiers -- Audrius Kažukauskas http://neutrino.lt/ pgpxbvP5LP38P.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] 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] Cauterizing heartbleed (CVE-2014-0160)
On Wed, 2014-04-09 at 06:05:20 +, mancha wrote: ... An example of the latter is Node.js [1] which has already been fixed in their devel branch [2]. ... Our node build script passes --shared-openssl to configure, so node is dynamically linked against system openssl and therefore does not require a rebuild. -- Audrius Kažukauskas http://neutrino.lt/ pgpYdg8spuv4l.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] pysetuptools update
On Fri, 2013-12-27 at 21:38:44 +0700, Willy Sudiarto Raharjo wrote: We have a pysetuptool update from 0.9.x to 2.0.1 and unfortunately, 1.0.x brings incompatible changes as mentioned here https://pypi.python.org/pypi/setuptools#backward-incompatible-changes I have been using setuptools 1.x for quite some time now and haven't encountered any issues. Of course this is just an anecdotal evidence and not a thorough test, but it seems to me that majority of the packages depending on pysetuptools will most likely just work. python/pep8 python/pip system/multicorn These are good. -- Audrius Kažukauskas http://neutrino.lt/ pgpndiUDDWSlF.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] PostgreSQL - multiple installed versions
On Mon, 2013-09-30 at 15:29:28 +0200, Adis Nezirovic wrote: Yes, that's the pain of having libraries in non public directory. Either solution is fine, I would like to avoid editing the /etc/ld.so.conf What about adding --with-postgres-libraries to the psycopg2 configure line? In my last email I forgot to tell that in my case psycopg2 is installed into virtualenv via pip together with other dependencies of my projects (that's how I prefer it). It seems to me that the correct fix is to query pg_config for LDFLAGS value in setup.py file of psycopg2, as suggested by Thomas. I decided to ask about this in psycopg2 mailing list, will see what the developers think. Thanks to all for your input. -- Audrius Kažukauskas http://neutrino.lt/ pgpYe_JNYyLSR.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] virtualenv SlackBuild
On Mon, 2013-07-08 at 10:20:22 -0700, Larry Hajali wrote: 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. If nobody objects, I'd gladly take it over. -- Audrius Kažukauskas http://neutrino.lt/ pgptcXRCC01zc.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] Updates - 20130605.1
On Wed, 2013-06-05 at 03:33:36 -0500, Robby Workman wrote: 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... I'm not really good at saying these things, but thank you to all the people involved in SlackBuilds.org project (admins, contributors, maintainers, users), I learned from you a lot during all these years. Without you Slackware wouldn't be as fun to use as it is now. -- Audrius Kažukauskas http://neutrino.lt/ pgpJimS_6165a.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] virtualenv SlackBuild
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 -- Audrius Kažukauskas http://neutrino.lt/ pgpOowk7aA8mY.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Redis compilation error with ARCH x86_64
Hi, Giorgio, On Sat, 2013-01-19 at 01:56:10 +0100, Giorgio Peron wrote: I got this error during the Redis compilation on a 64 bit machine ... my workaround was unset and set the ARCH variable before and after the make command. There is a better solution? Not that I know of. It's the second time this issue arises, and the solution last time was the same (unset ARCH). See http://lists.slackbuilds.org/pipermail/slackbuilds-users/2012-September/009230.html -- Audrius Kažukauskas http://neutrino.lt/ pgp65Rwx5149U.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Redis compilation error with ARCH x86_64
On Sat, 2013-01-19 at 08:50:48 -0800, Larry Hajali wrote: Yeah, it looks like the Makefile picks up the ARCH variable when it is exported. Probably best solution is to unset ARCH (like it was already mentioned) right before the redis.SlackBuild defines ARCH. That way ARCH is defined but not used by the Makefile. I submitted an update which unsets ARCH in a subshell before calling make (thanks to Matteo for the patch). -- Audrius Kažukauskas http://neutrino.lt/ pgpxGy6EeGXF_.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] smem.SlackBuild
On Sat, 2013-01-05 at 17:56:31 +0100, Dušan Stefanović wrote: Thanks for interest, but I'm very busy at a moment, and it will last at least for month. I see that you are active contributor for SBo, so if you want, you can take the script. OK, I can take it, the releases seem to be rare, so it won't make much effort to maintain. Thanks! CC'ing this to SBo mailing list. On 1/5/13, Audrius Kažukauskas audr...@neutrino.lt wrote: Hi, Dušan, I recently discovered smem and am very happy with this nice little tool. Thanks for adding a build script to SlackBuilds.org. It would be great if you update it to the latest version (1.2), since the one in SBo is pretty old (0.1). I'm attaching the patch with changes that I had made for SlackBuild to work with the version 1.2. -- Audrius Kažukauskas http://neutrino.lt/ pgpVUoVvR5EaO.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] slack-desc syntax file for Vim
On Mon, 2012-12-10 at 17:54:33 -0500, B Watson wrote: Very nice! Glad that you like it! One thing: the file (as downloaded from gmail's web interface, with Firefox) had DOS-style CRLF endings. So if anyone's getting E492: Not an editor command: ^M, fix it with: perl -i -pe 's/\r//' ~/.vim/syntax/slackdesc.vim Hmm, that's strange, I'm certain that here it has Unix line endings. It must have have been either GMail or Firefox that changed it. -- Audrius Kažukauskas http://neutrino.lt/ pgppU8Xk8gjMG.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] Asunder needs an update
On Mon, 2012-12-10 at 16:13:42 +0200, Dimitris Tsagkatakis wrote: Asunder's SlackBuild hasn't been updated since '08. The SlackBuild runs fine just by changing $VERSION, and it would be nice if we had this working through sbopkg too :) If the maintainer is no longer interested, I could submit an update and maintain the script. You should send this to the maintainer directly. Not every maintainer reads this list, and in case this SlackBuild's abandoned, this is even more likely. If you won't hear from him in a reasonable time, submit updated script to SBo and write a note about this in submission form. -- Audrius Kažukauskas http://neutrino.lt/ pgpqTohli5unK.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] slack-desc syntax file for Vim
Hi,
I have been using this slack-desc Vim syntax file which I wrote a couple
of years ago. I recall intending to share it with this mailing list,
but somehow forgot to do so (probably was busy with something at the
time). So now I'm correcting my mistake and sending this file attached
in hope that other slackers will find it useful. To use slackdesc.vim,
put it in ~/.vim/syntax/ (if that directory doesn't exist, create it)
and place the following somewhere inside your ~/.vimrc:
Highlight SlackBuild description files.
au BufNewFile,BufRead slack-desc set ft=slackdesc
Feedback (especially in form of patches ;-) is welcome!
--
Audrius Kažukauskas
http://neutrino.lt/
Vim syntax file
Language: slack-desc
Maintainer: Audrius Kažukauskas audr...@neutrino.lt
Last Change: 2010-08-21
Version: 0.1
if exists('b:current_syntax')
finish
endif
if has('spell')
syn spell toplevel
endif
syn region sdComment start='^\s*#' end='$'
syn region sdRuler start='^\s*|' end='|'
syn region sdName start='^\w' end=':' nextgroup=sdDesc
syn match sdDesc '.\{0,71}' contained nextgroup=sdOverflow
contains=@Spell
syn match sdOverflow '.*' contained contains=@Spell
hi def link sdComment Comment
hi def link sdRuler Label
hi def link sdName String
hi def link sdOverflow Error
let b:current_syntax='slackdesc'
pgp8X84Lf5pa2.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] xcdroast slackbuild broken only for me ?
On Tue, 2012-11-27 at 14:28:49 +0100, Giuseppe De Nicolo' wrote: in slackware 14 cdrtools as been dropped and replace with cdrkit ( it wasn't the case in 13.37 ) Slackware 14.0 still has cdrtools: $ cat /etc/slackware-version Slackware 14.0 $ slackpkg info cdrtools PACKAGE NAME: cdrtools-3.01a08-x86_64-1.txz PACKAGE LOCATION: ./slackware64/ap ... -- Audrius Kažukauskas http://neutrino.lt/ pgp89DU9ORL4w.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] Script licensing
On Sun, 2012-11-18 at 07:12:37 +0200, Mikko Varri wrote: If the script is public domain, as a maintainer you can do whatever you want with it. You do not have to mention the previous maintainers. But... I did contact all the previous maintainers (those mentioned in the script and those who had touched the script according to git log) and asked whether they want to be mentioned according to the BSD/MIT style. Most of them couldn't care less, so I dropped their names. However, some of them appreciated the gesture and wanted to keep their names in the scripts, so those stayed. Thank you guys for the answers. I think I'll try Mikko's approach and contact past maintainers and contributors, as simply removing them doesn't feel right to me. -- Audrius Kažukauskas http://neutrino.lt/ pgpgapQfoDxn3.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Script licensing
Hello, According to notes in SBo SlackBuild templates, Public Domain scripts are no longer allowed: A license is required, and we strongly suggest you use the above BSD/MIT style license. We DO NOT accept Public Domain scripts. Public domain is not valid in some countries, and no license is worse than a bad license in those countries. This is easily applicable for new SlackBuilds, but what about the ones that were submitted to SBo in the past as Public Domain and need an update now? If they also need to be licensed, there are two cases not clear to me: - Scripts that were authored by one person as Public Domain and were taken maintenance of by somebody else, and now they have the following note: # Created by Foo # Maintained as of version 1.2.3 by Bar - Scripts that were authored by one person, but were modified by one or more SBo admins and/or somebody else: # Created by Foo # Modified by Bar # Modified by Baz It would be very helpful if admins would clarify how to act in such cases. Thank you. BTW, licensing requirements in http://slackbuilds.org/guidelines/ should also be updated to reflect these policy changes. -- Audrius Kažukauskas http://neutrino.lt/ pgp9nyGLNu0be.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] download/tar discrepancies in several SBos
On Thu, 2012-11-08 at 04:31:47 -0600, J wrote: while running an audit of DOWNLOAD bits in .info files compared to tar lines in .SlackBuilds, I found several cases where there are discrepancies between the file that is downloaded and the file that the SlackBuild tries to decompress. this kills the SlackBuild: /usr/sbo/development/jsctags/jsctags.info: DOWNLOAD=https://github.com/mozilla/doctorjs/tarball/69588ab /usr/sbo/development/jsctags/jsctags.SlackBuild: SRCNAM=mozilla-doctorjs SRCNAMSUF=69588ab $SRCNAM-$SRCNAMSUF.tar.gz If you are running your script against SBo tree for 14.0, you might want to purge it from stale SlackBuilds, as the one above was removed. -- Audrius Kažukauskas http://neutrino.lt/ pgphyjqGLGiMY.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] postgresql.SlackBuild
On Fri, 2012-10-05 at 18:02:04 +0200, Mario wrote: I know its not the usual way, but if someone needs a bit better postgresql script, here it is: Patch against 14.0 SB: http://mirror.slackverse.org/slackbuilds/fixed/postgresql.diff Whole package: http://mirror.slackverse.org/slackbuilds/fixed/postgresql.tar.gz If author does not mind, I could aswell take this one over, seeing how last update was last year(?), and postgres is such a nice database. 9.1.4 was released 2012-06-04[*], so the script was updated quite recently. Besides, there's no need to update it for every minor release, cause usually it's a simple version bump. And 9.2 happened while submissions to SBo were closed. [*] http://www.postgresql.org/docs/9.1/static/release-9-1-4.html And yes, Postgres is simply awesome. Even though I've been using it for a few years, only this year I really began to learn about (some of) its tremendous features. This script comes with the ability to update old version database, which previous SB did not do successfuly, mainly due to missing pg_upgrade_support module. I have already informed Adis about it a couple of weeks ago (when I encountered this myself while trying to upgrade to 9.2), and he replied that pg_upgrade_support will be included on the next script update. -- Audrius Kažukauskas http://neutrino.lt/ pgpbGTkHON6d1.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] postgresql.SlackBuild
On Fri, 2012-10-05 at 22:40:48 +0200, Mario wrote: Yeah, but I saw modified by the SBo project in there, thought it was abandoned, and that 2011 did not help either. Ah, yes, that could have been confusing. At least one of the scripts I maintain has this notice as well, though I'm not sure how common it is. I have already informed Adis about it a couple of weeks ago (when I encountered this myself while trying to upgrade to 9.2), and he replied that pg_upgrade_support will be included on the next script update. Whatever though, I ran into an issue when upgrading my postgres databases so I decided to share fixed up version with patches in case if someone needs it. And it's great that you shared it, I'm certain that people will find this helpful. All I wanted to say that the maintainer is aware about the missing pg_upgrade_support module. :-) -- Audrius Kažukauskas http://neutrino.lt/ pgpMoLYRLtcxh.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] redis can't be built on slackware64 13.37
On Sat, 2012-09-08 at 23:16:54 +0900, crocket wrote: Below is the error log. cd src make all make[1]: Entering directory `/tmp/SBo/redis-2.4.14/src' MAKE hiredis make[2]: Entering directory `/tmp/SBo/redis-2.4.14/deps/hiredis' cc -std=c99 -pedantic -c -O3 -fPIC -O2 -fPIC -Wall -W -Wstrict-prototypes -Wwrite-strings -g -ggdb x86_64 net.c cc: x86_64: No such file or directory make[2]: *** [net.o] Error 1 make[2]: Leaving directory `/tmp/SBo/redis-2.4.14/deps/hiredis' make[1]: *** [dependencies] Error 2 make[1]: Leaving directory `/tmp/SBo/redis-2.4.14/src' make: *** [all] Error 2 What do I need to do for building redis? I think the problem lies in the following line: redis-2.4.14/deps/hiredis/Makefile:18: REAL_CFLAGS=$(OPTIMIZATION) -fPIC $(CFLAGS) $(WARNINGS) $(DEBUG) $(ARCH) Not sure why $(ARCH) is there, but in your case it's set to 'x86_64' and that gets inserted in compiler line. Try unset ARCH before building redis. -- Audrius Kažukauskas http://neutrino.lt/ pgpmGKVohbQ3y.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] redis can't be built on slackware64 13.37
On Sat, 2012-09-08 at 23:59:25 +0900, crocket wrote: It turned out that redis fails to build within sbopkg. It builds fine on a bare shell. (Sent my last email before I saw this one.) Well, that means that sbopkg is setting ARCH var which interferes with at least one of redis Makefiles. -- Audrius Kažukauskas http://neutrino.lt/ pgpjEWGx3YXYU.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] REQUIRES info
On Wed, 2012-08-22 at 09:18:45 +1000, Christoph Willing wrote: I have a use case where such information is actually useful rather than superfluous. I run each build inside an LXC container which is created just for that build. Rather than being a fully loaded Slackware system, the container is a minimal system containing just enough of the official Slackware packages to actually run a package build script. At build time, based on the REQUIRES field, any missing packages (both Slackware and SBo) are first installed into the container. Of course the REQUIRES field is new so, so far, I've been modifying the .inf files myself to include that information. You could make a 'template' of a full Slackware installation in btrfs filesystem and then clone it each time you want a fresh LXC container. The clone won't take any additional space on disk except for the changes you make inside it. After using it you can simply remove it and create a new one for another build. I have a helper script that simplifies the aforementioned steps. You can find it at https://bitbucket.org/audriusk/lxc-slack. Haven't had the chance to test it with updated btrfs-progs in -current, but it should still work. -- Audrius Kažukauskas http://neutrino.lt/ pgpgKVprGsGo6.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] eric ide
On Sun, 2012-08-19 at 05:05:48 -0400, B Watson wrote: While you're at it, use something like this (code taken from my ecasound.SlackBuild): # Figure out the version number part of the python lib dir: PYVER=$( python -c 'import sys; print %d.%d % sys.version_info[0:2]' ) PYVER will be 2.6 or 2.7 or whatever. Then in your ./configure or cmake or whatever, use something like --with-python-modules=/usr/lib$LIBDIRSUFFIX/python$PYVER Then when Slack 14.1 comes out, with python 2.8, your script wouldn't need changing (at least, it wouldn't need that part changed). Disclaimer: IANAPP (I am not a Python programmer). If someone who is a Python programmer has a better (more elegant) snippet of code to do the same job, feel free to correct me. This is fine, that's what Slackware's subversion SlackBuild is doing as well. You can omit 0 to shorten it by one character (sys.version_info[:2]), otherwise both ways are correct. -- Audrius Kažukauskas http://neutrino.lt/ pgpFF4UYXl0C0.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] SlackBuilds for Humble Bundle games
On Fri, 2012-06-08 at 13:07:28 +0300, Dimitris Tsagkatakis wrote: So, I wanted to ask: a) Given the fact that these scripts rely on commercial and (usually) proprietary software and would appeal only to Humble Bundle customers, would these scripts be welcome by SBo? The potential problem I see here is (un)availability of source (or binary in this case) tarballs to everybody, and that includes SBo admins wanting to test your build scripts against those tarballs. If these games can be downloaded freely and only require some sort of activation to play, then the fact that they're commercial software shouldn't be an issue. I believe SBo already contains SlackBuilds for this sort of software, although I don't have any examples to point you at. b) If yes, do you think it would actually be a worthy addition to the database? Because, currently, there are scripts for 43 games and I suspect I'll have to modify them to be as consistent as possible with SBo's templates. Yep, they should be as close to SBo templates as possible, but feel free to do things differently if it makes sense. Regards, Dimitris PS. Sorry for any grammar mistakes :) I think your grammar is great, but I'm not a native English speaker. :-) -- Audrius Kažukauskas http://neutrino.lt/ pgpvxzUUwFY4S.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] Updated Xerces-c and Xalan-c Slackbuilds
On Sat, 2012-05-05 at 23:22:19 -0600, Slacker build user wrote: ... My question then is this: Should I submit the new versions under a different name such as Xerces-c_3 and Xalan-c-svn with explanation in the README? Or is there a better way to handle this? Or should I keep it to myself and just offer them to anyone interested? ;-) First, SBo won't accept build scripts that download source files, so your best bet would be to checkout the revision that works, make a tarball and put it somewhere online, so others could fetch it. But I think it's not a good idea to have multiple versions of the same software in SBo, unless there's a *really* good reason to do so (e.g. some applications require newer version of library, while others still use the old one, etc). I'm pretty sure that Heinz (maintainer of both SlackBuilds) will comment on your questions sooner or later, as he reads this mailing list and is one of SBo admins (if I'm not mistaken). Perhaps the email provided for both scripts is not in use anymore, and that's why he didn't reply to you. -- Audrius Kažukauskas http://neutrino.lt/ pgpOp2mwYIniZ.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] libffi conflicts with gcc-java
Hi, I have noticed that not too long ago libffi was added to SBo. It was included in the past and removed on Slackware 13.0 release with the following note in the changelog: libraries/libffi: Removed; conflicts with gcc-java-4.3.3. This is still true for the newest gcc-java package. There's one thing though, which gcc-java lacks (and libffi has). It's $libdir/pkgconfig/libffi.pc, which is needed by some software[0] at build time. Another difference is that libffi inside gcc-java seems to be older, judging from .so version number. My suggestion would be to add libffi to Slackware or at least include libffi.pc into gcc-java. [0] http://www.linuxquestions.org/questions/slackware-14/guile-upgrade-dependency-problems-884879/ -- Audrius Kažukauskas http://neutrino.lt/ pgp0zzMfe1iAV.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] My echinus and vifm slackbuilds are ready.
On Mon, 2012-02-06 at 11:35:53 -0600, Charles Kauffman wrote: 2. In the echinus.SlackBuild sed -i s;-Os;$SLKCFLAGS ;g config.mk sed -i s;.pixmap: ;.pixmap: \/usr\/share\/echinus\/_g echinusrc sed -i s/DOCPREFIX}\/echinus/DOCPREFIX}\/echinus-$VERSION/g Makefile The source only contains Makefile and config.mk, no configure script. So I replaced the compiler flag -Os with SLKCFLAGS, as well as had the script create a doc directory that had the version number appended to it. The second sed makes modifications to the rc file since problems can occur when the program loads. So, does that look good, or should I just leave some of that alone? Looks good to me. As long as the changes don't break anything, I'd say go for it. Just not sure if global (g) substitute is needed (it looks for multiple regex matches in a single line). Also there should be a semicolon at the end of second sed-line, no (and no need to escape slashes)? -- Audrius Kažukauskas http://neutrino.lt/ pgpNjmTxxXARX.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] distribute-0.6.19, md5 mismatch.
On Wed, 2011-12-07 at 02:20:07 -0600, Antonio Hernández Blas wrote: According with distribute.info md5 is 45a17940eefee849d4cb8cc06d28d96f but i get 21e7a442c4d8f0cb0223f2ed5e4569ad. Btw, its a know issue[1]. [1] https://bitbucket.org/tarek/distribute/issue/247/reuploading-same-version-brakes-md5-sum Submitted update to latest version (0.6.24), thanks! -- Audrius Kažukauskas pgpMyEYx8U3Ac.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] /lib/libssl.so.0.9.8: no version information available
Hi,
New version of PyPy just got released, and seeing that the binaries do
not depend on (incompatible with Slackware) libffi anymore, I decided to
repackage them instead of building from source (which takes lots of time
and RAM).
I tested pypy with some code of mine, it worked great except one thing:
whenever I invoke pypy executable, I get the following warnings in
stderr:
./pypy: /lib/libssl.so.0.9.8: no version information available
(required by ./pypy)
./pypy: /lib/libcrypto.so.0.9.8: no version information available
(required by ./pypy)
Running ldd -v ./pypy shows:
libssl.so.0.9.8 = /lib/libssl.so.0.9.8 (0xf76cd000)
libcrypto.so.0.9.8 = /lib/libcrypto.so.0.9.8 (0xf7587000)
and in version information section:
libssl.so.0.9.8 (OPENSSL_0.9.8) = not found
libcrypto.so.0.9.8 (OPENSSL_0.9.8) = not found
I recalled reading a discussion on some mailing list (can't find a link
to archives though) where it was explained that this is what happens
when you use something built against OpenSSL from Debian on a different
system. Wanting to be sure, I checked Debian source package for openssl
and indeed found a patch where they add
$shared_ldflag .= -Wl,--version-script=openssl.ld;
line to Configure script and create openssl.ld file containing
OPENSSL_0.9.8 {
global:
*;
};
So, I am quite confident that PyPy was built using Debian (or
derivative) system.
Now, the real questions: is it safe to use such binary on Slackware? If
yes, is it possible to suppress these warnings?
--
Audrius Kažukauskas
pgpmcbpi4krvU.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] ffmpeg
On Mon, 2011-11-14 at 11:09:10 -0700, darrell dupas wrote: http://slackbuilds.org/slackbuilds/13.37/multimedia/ffmpeg.tar.gz line 196, i had to comment it out, got an error that the files are not found #cp -a doc/*.html $PKG/usr/doc/$PRGNAM-$VERSION From ffmpeg SlackBuild README: Make sure to run this script in a real root shell (su -) and that you have either tetex or texlive installed. -- Audrius Kažukauskas pgpaFXqhWNyDg.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] ffmpeg
On Mon, 2011-11-14 at 19:14:50 +0100, Matteo Bernardini wrote: this happens frequently Yeah, it sure does. Maybe it's a good idea to include this in FAQ? (If it's not there already -- couldn't find anything related after a quick glance.) -- Audrius Kažukauskas pgp3OsbRO8zMX.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] ffmpeg
On Mon, 2011-11-14 at 20:21:48 +0200, Grigorios Bouzakis wrote: On Mon, Nov 14, 2011 at 08:18:41PM +0200, Audrius Kažukauskas wrote: Yeah, it sure does. Maybe it's a good idea to include this in FAQ? (If it's not there already -- couldn't find anything related after a quick glance.) You mean http://slackbuilds.org/faq/#root ? The fact that dependencies in Slackware dont get mentioned should be considered common knowledge. No, I mean this particular case about su - and PATH, which quite often confuses people and they think that something's wrong with the build script, when it's not. -- Audrius Kažukauskas pgpZXa2JhG1lM.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] Where does the contents of package's SBo page come from?
On Wed, 2011-11-09 at 09:08:18 -0500, Eric Schultz wrote: I'm looking at the digikam page (I use that a lot, thanks Frank) at http://slackbuilds.org/repository/13.37/graphics/digikam/ but the contents don't seem to come directly from any of the files - neither the README nor slack-desc match what is displayed on the page. So I was wondering if the admins come up with that, or do I need to provided it? Am I missing something? Page contents for packages come from README files. You don't need to provide it separately. The digikam page differs from README most likely because the database record wasn't updated after the last changes to README. -- Audrius Kažukauskas pgp1CYLU3lSle.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] Rejected SlackBuild
Hi, Serban and others, I want to point out one thing that's probably not obvious to you: when sending new email (not a reply to an existing one) to the mailing list, do not use reply feature of your mail client and just change the subject. Instead, start a new email. When you choose to reply, your mail client includes an additional header (In-Reply-To), which some mail software (e.g. Mutt, Mailman archives[*]) use to group emails into threads. By replying to a message from an existing thread with completely different subject, you effectively threadjack it. Please don't do that. [*] http://lists.slackbuilds.org/pipermail/slackbuilds-users/2011-November/thread.html PS Yes, I know that in Mutt you can break a thread by pressing # key, but Mailman archives still look messed up. -- Audrius Kažukauskas pgpa7YdAmowcP.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] nvidia-kernel fix
On Tue, 2011-08-30 at 08:55:47 -0700, King Beowulf wrote: SBo admins, attached it a diff to fix up the the recently submitted nividia-kernel.tar.gz Your submission is still not approved, I think it would be easier to remove it yourself using removal code you should have got and resubmit with applied fixes. -- Audrius Kažukauskas pgpe2g72BpND0.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] python stuff under /usr/share
On Thu, 2011-08-25 at 16:34:59 +0200, Marco Bonetti wrote:
I'm trying to build a package for pysvn and its dependency PyCXX.
The latter is quite hard to build right: setup.py is configured to
install include files under /usr/include/python2.6/CXX and source
files under /usr/share/python2.6/CXX. As I dind't find anything
related to /usr/share/python2.6 in Slackware but it looks ok from the
respective debian/rule I think it's a debianism used by the source
code mantainer. On the other hand, I have some locally installed
python packages which put stuff under /usr/share/packagename (like
pygtk and pygobject).
If source files are usual .py files, ideally they should go to
/usr/lib{,64}/python2.6/site-packages, but I suspect this is not the
case with PyCXX.
What should I do now?
1) installing files under /usr/share/python2.6/CXX so both the demos
and pysvn build with no changes at all
2) installing files under /usr/share/CXX and use pysvn setup.py switch
to point to the right folder
To me option number 2 looks best but it will probably mean more work
for everyone who needs to build anything against PyCXX as there is no
pkgconfig or anything similar which will tell you where needed files
are.
I also think option 2 is nicer, but if it creates more troubles for
PyCXX users, it's probably better to stick with defaults, as ugly as
they are.
--
Audrius Kažukauskas
pgpWSmkGUyHoa.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] opera buildscript needs a new maintainer
On Wed, 2011-07-06 at 01:37:04 -0500, Robby Workman wrote: Since I was the previous maintainer, I felt obligated to fix the sub-par packaging as of late (not Markus' fault), so I just put a build using the tar.xz sources into pending. I'm not partial to opera, and in fact, I only use it on my android device, so either of you is welcome to take it after this gets pushed out to the public. You two can fight over it, flip a coin, have a duel, see who can drink the most, or see who can send the most beer to me, or some other more sensible (and more boring) idea. I'll choose the most boring option and let vvoody take it (of course, if he's still interested). What's important to me is that Opera build script has a maintainer. Would be sad if it was dropped from SBo as unmaintained. -- Audrius Kažukauskas pgpQbOaccPLqk.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] How to get source hostet?
On Sun, 2011-06-26 at 19:22:34 -0400, Ben Mendis wrote: Also, Github gives you 0.30 GB of disk space with a free account which you could use for hosting. And bitbucket.org gives you unlimited disk space for hosting repositories and files. -- Audrius Kažukauskas pgpfZQZD7IGDk.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] Updates - 20110620.1
On Mon, 2011-06-20 at 04:43:56 +, Robby Workman wrote: libraries/virtualenv: Updated for version 1.6.1. There's something wrong with this. On the website it's in python category, but files are missing. In git repo it's in libraries. -- Audrius Kažukauskas pgpmPoIOMUzOF.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] Updates - 20110620.1
On Mon, 2011-06-20 at 15:04:39 -0500, Robby Workman wrote: Is it supposed to be in python/ ? I've sent an email to Larry a couple of weeks ago suggesting to move this to python/, and he agreed, so I guess that it should... I'm going to fix it by putting it back in libraries/ (wrt the db), but if it should be in python, then I'll do that in the next update. -- Audrius Kažukauskas pgp1X2BBKnhy5.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] Introduction questions about link creation for the 'oxygen-gtk' theme
Welcome back to Slackware! On Sat, 2011-06-18 at 09:36:02 +0200, Nicolas Kovacs wrote: 3) Now here comes the point where I reach my limit of competence. I'm trying to package my default user profile. I'm writing a SlackBuild script for this, and right now, I wonder how to define that symlink. I know how to go about it with a simple file. Say I have a 'gtkrc' file in the same directory as the SlackBuild script, the solution would be something like this: mkdir -p $PKG/etc/skel cat $CWD/gtkrc $PKG/etc/skel/.gtkrc-2.0 chmod 0644 $PKG/etc/skel/.gtkrc-2.0 But how could I have something similar with the symlink? Wouldn't something like this work? mkdir -p $PKG/etc/skel ln -sf /usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc $PKG/etc/skel/.gtkrc-2.0 And don't forget to add -l y to makepkg, so that it will add all symlinks to doinst.sh script. -- Audrius Kažukauskas pgpAVnsh788D4.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] Can't get kbluetooth slackbuild
On Fri, 2011-06-17 at 10:32:02 -0300, Gustavo Conrad wrote: Hi all, I want to install kbluetooth on my 13.37 Slackware but it seems that the slackbuild file is not present on the server. kbluetooth was removed from the repo recently, although there seems to be a stale DB entry on the website: http://slackbuilds.org/gitweb/?p=slackbuilds.git;a=commit;h=cb373c32 As kbluetooth is abandoned by upstream, consider using blueman (included in Slackware) or bluedevil (Eric has SlackBuilds for it in http://taper.alienbase.nl/mirrors/alien-kde/, I'm just not sure if that will work with KDE 4.5.5 from Slackware). -- Audrius Kažukauskas pgpk65ChimJD5.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] Graphviz Build Error
On Fri, 2011-06-17 at 06:38:11 -0700, Rich Shepard wrote: On Thu, 16 Jun 2011, B Watson wrote: Well, no, I was saying to make sure /usr/lib/pkgconfig is *not* listed in your PKG_CONFIG_PATH (and make sure /usr/lib64/pkgconfig *is* in there). Darn! I changed PKG_CONFIG_PATH in both ~/.bash_profile and /root/.bash_profile, sourced the latter, and still get the same fatal build error that /usr/lib/libstdc++.la has moved. With the path change to /usr/lib64/ I expected this error to be fixed. What else have I missed? Rich, Have you tried what Greg suggested? He was successful at compiling graphviz on a multilib system. Unfortunately, I can't help with this issue as I'm using pure 64-bit system myself. -- Audrius Kažukauskas pgpyQ6F8LImJh.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] Opera Widgets
On Wed, 2011-06-15 at 22:46:23 +0200, markus reichelt wrote: Reason I'm asking: I do not use Opera Widgets myself, at all. The more input the better. Thanks :) I do not use Opera widgets either, so I guess this doesn't count as useful input. :-) What I do use are UserJS scripts. I find them very valuable. -- Audrius Kažukauskas pgp93A1FklVym.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] GoogleEarth Won't Start
On Thu, 2011-06-16 at 12:55:41 -0700, Rich Shepard wrote: Using the new SlackBuild script and a fresh copy of GoogleEarth...bin for 13.37/x86_64 I'm running into a puzzling problem when trying to invoke the application. What I see on the virtual terminal is: /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: no such file or directory /usr/bin/googleearth: line 18: /opt/GoogleEarth/googleearth-bin: success Well! googleearth-bin _is_ in /opt/GoogleEarth. And I added the LD_LIBRARY_PATH shown in /usr/bin/googleearth, but all to no avail. What might I have done wrong here? Are you trying to run it on Slackware64? From GoogleEarth SlackBuild README: 3) GoogleEarth is a 32bit application only. You need to have the 32bit compatibility packages installed to have this work on a 64bit system. Otherwise you'll just see no such file or directory errors. -- Audrius Kažukauskas pgpenjFQRk3HK.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Announcing lxc-slack
Hi, I've announced my lxc-slack script for creating Slackware LXC containers on LQ, but thought it may be interesting to people on this mailing list, so here's the link: http://www.linuxquestions.org/questions/slackware-14/announcing-lxc-slack-885017/ -- Audrius Kažukauskas pgp7Ol3LHBR3T.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] Flying next friday
On Sat, 2011-05-14 at 22:05:45 +0500, Ozan Türkyılmaz wrote: However I am after a stupid http proxy that keeps my connections in a limited way (Any tips are welcome). If you're able to ssh to a box without any restrictions somewhere, this article might be useful to you: http://alien.slackbook.org/blog/securely-browsing-the-net-using-socks/ -- Audrius Kažukauskas pgp6bQRXZSxXz.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Change category for my SlackBuilds
Hi, Could admins please change the category from development to python for the following of my SlackBuilds: development/distribute development/pep8 development/pip All of them are used for Python code, so they fit better in python category. There's also libraries/virtualenv which is used to create virtual isolated Python environments and does belong to python category, too, I believe, but since it's not mine, it's up to Larry Hajali to decide on this one. Thanks, -- Audrius Kažukauskas pgpGuIORfOeDu.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] Jmol 12.0.39 SB script
On Sun, 2011-04-03 at 12:33:45 +0200, Ivan Pavicevic wrote:
This script makes tgz package from Jmol's java binary. The script makes jmol
branch in /opt and then makes symbolic link to /usr/bin. Also, I made
jmol.desktop, and added jmol.png as icon, so after installation Jmol appears
in Applications/Education section (I'm using Xfce).
It works, but if you find anything wrong in the script, please let me know.
I had a quick peek into your script and it doesn't look like it was
based on any of SBo templates[0]. I suggest to follow them as closely
as possible. To handle different program and source file names, you
could use SRC_NAME (or something similar) for the latter one. The
former should be PRGNAM as written in templates.
[0] http://slackbuilds.org/templates/
Documentation in Slackware should be placed in /usr/doc, not
/usr/share/doc. Icon file should be placed in /usr/share/pixmaps, that
way you won't have to provide a full path for it in .desktop file.
And there are some issues with .desktop file:
$ desktop-file-validate jmol.desktop
jmol.desktop: warning: key Encoding in group Desktop Entry is deprecated
jmol.desktop: error: value Application;Education for string list key
Categories in group Desktop Entry does not have a semicolon (';')
as trailing character
I haven't tried to run it, but overall it looks okay, just needs to be
written more closely to SBo guidelines.
--
Audrius Kažukauskas
pgp1y72gcPk5z.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] Orphaned SlackBuilds
On Sun, 2011-04-03 at 01:07:10 -0500, Robby Workman wrote: On Fri, 1 Apr 2011 10:27:48 +0300 iskar enev iskar.e...@gmail.com wrote: system/pgadmin3 network/nicotine+ development/scite These three are now in my maybe-remove branch in git. If they're not claimed RSN, that will change... Um, maybe you meant something else instead of nicotine+, because I've claimed it recently. Or is there a build problem with it? Since it's pure Python code, there shouldn't be any... -- Audrius Kažukauskas pgpmjKk0TsE0r.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] Orphaned SlackBuilds
On Fri, 2011-04-01 at 10:27:48 +0300, iskar enev wrote: network/nicotine+ I can take this (since I use it from time to time), unless someone else wants it. -- Audrius Kažukauskas pgpX6gGMo6fE8.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] mercurial repositry
On Tue, 2011-02-08 at 09:30:22 +, Tim Dickson wrote: hi all, I am creating a slackbuild for a project where the source is only available as a mecurial repo. on googlecode.com It is easy enough to get (the source), but is not accessible directly by http or ftp, and is just the source itself, not a gzipped tar of the source. any suggestions? thanks, Tim PS. source can be got with something like.. hg clone https://$APNAME.googlecode.com/hg/ $APPNAME It doesn't seem that googlecode.com allows one to download arbitrary changeset from the repo as an archive (yet). There's a registered issue[0] about this on their support issue tracker, but I don't see anywhere that it had been solved. [0] http://code.google.com/p/support/issues/detail?id=4134 Perhaps this project has a mirror on bitbucket.org? This feature is supported there: http://bitbucket.org/$USERNAME/$APPNAME/get/$CHANGESET.tar.bz2 If there's no official mirror, you could provide it yourself by cloning the repo and pushing it into bitbucket.org. Or you could try asking the upstream to do this for you. -- Audrius Kažukauskas pgpgmIWaIzl5j.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] mrtg-2.15.2 breaks with latest slackware-current
On Thu, 2011-01-06 at 21:45:33 +0700, Willy Sudiarto Raharjo wrote: A recompile didn't help. As there's currently no newer version for mrtg on slackbuilds, I downloaded mrtg-2.17.0.tar.gz source code from oetiker's page and compiled it. It works well. I posted this quick note on LinuxQuestions and they suggested to inform the package maintainer and cc the slackbuilds-users list. MRTG packages in SBo are guarranted to work on 13.1, not in -Current :) If you are using -Current, then it's up to you to make it work under your machine if it's not yet released on SBo That's true, but as -current eventually will become -stable (and it feels like this *may* happen pretty soon), I think it's still a useful bit of information to know, at least to the maintainer. -- Audrius Kažukauskas pgpW28kA3tB7u.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] Updates - 20100816.1
On Sun, 2010-08-15 at 21:11:08 -0500, Erik Hanson wrote: ... development/Sphinx: Added (Documentation generator) ... There's also another entry at SBo called sphinx: $ find slackbuilds/ -type d -iname sphinx slackbuilds/development/Sphinx slackbuilds/network/sphinx The problem is that network/sphinx is shadowed by development/Sphinx on SBo website -- search can't find it nor is it accessible by direct URL http://slackbuilds.org/repository/13.1/network/sphinx/. I guess adding some prefix to development/Sphinx name (either pysphinx or python-sphinx) should be sufficient to fix this. -- Audrius Kažukauskas pgpoekexgIyWX.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] Supplementary manpages
On Thu, 2010-07-15 at 16:34:34 +0100, Pierre Cazenave wrote: I've written a SlackBuild for OCROpus which builds fine given a couple of Debian patches. When I was getting those patches, I noticed Debian have created a manpage for OCROpus as there isn't one included by default. Would including this in the SlackBuild submission as a separate file be OK? Would it be treated like a patch (i.e. incorporated in the submitted build) or should I link to it as another download? Or, should I just omit it altogether and leave the package as upstream released it: manpageless? Running find . -type f -name '*.[1-9]' on my local git clone of SBo shows quite a few SlackBuilds which have man pages as the separate files added. So, yes, it's a good idea to provide a man page. One example might be unrar; I suggest checking it and doing the same for OCROpus. -- Audrius Kažukauskas pgpyvHg6SvmQy.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] Updates - 20100706.1
On Tue, 2010-07-06 at 02:49:03 -0500, Erik Hanson wrote: Tue Jul 6 07:38:43 UTC 2010 ... office/kmymoney: Fixed slack-desc and build tweaks. office/kmymoney2: Removed now obsolete. ... kmymoney2 is still visible on the website, and something's wrong with kmymoney README file. It looks to be binary, and file(1) thinks that it's a gzip compressed data. -- Audrius Kažukauskas pgpGXiUriI7b6.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Stale rubygems entry on SBo website
Hi, A quick note about rubygems still being visible on SBo website, while it's no longer in git repository. Also kqemu description on the site differs from its README. -- Audrius Kažukauskas pgpRlSoQOzQzA.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] qemu-legacy puts man pages in /usr/share/man
Hi, I've noticed that qemu-legacy script puts man pages in /usr/share/man and doesn't compress them. I'm writing to SBo list, because I think that admins can quickly fix this by copying the part from qemu script that handles man pages. -- Audrius Kažukauskas pgpVQoDDes1JV.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] Reworked Python3 SlackBuild
On Thu, 2010-06-03 at 09:12:30 +0300, Ozan Türkyılmaz wrote: you should able to run virtual machines. virtualisation instructions speed up the virtual system. i run a virtual machine on my old laptop which is older than amd64. I had an impression that to run, say, VirtualBox with 64 bit guest on my 32 bit host I need to have x86_64 CPU with hardware virtualization support (in my case Intel VT-x), and mine doesn't have it (lower end model). Sure, I can run qemu instead (full emulation), but wouldn't that be too slow (especially for compiling software)? but it's good to do tests by several people. i'll test it and let you know Thanks. -- Audrius Kažukauskas pgpb9j36zeaZD.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Reworked Python3 SlackBuild
Hello, A few months ago someone complained that Python3 wasn't working for them on x86_64. It was building fine, but couldn't find stdlib due to incorrect paths. Finally I decided to look into this issue (better later than never) and made patches similar to the ones used for Python 2.x from Slackware for x86_64. I don't have any 64 bit systems to test this on (still using 32 bit Slackware; also my laptop's CPU, though 64 bit capable, lacks virtualisation instructions, hence I'm unable to run 64 bit guests), so I'd be really glad if someone could test this on x86_64 (building and trying to run 'python3' in command line should be sufficient). I'm attaching a tarball containing SlackBuild with patches. -- Audrius Kažukauskas python3.tar.gz Description: application/tar-gz pgpRx45WdNK7j.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Kismet update
Hi, I'm going to submit updated Kismet SlackBuild (thanks goes to Antonio Hernández Blas for updating it), but before that I want to ask something. Kismet developers strongly encourage to use 'make suidinstall' for new version which makes it work only for the members of 'kismet' group. I've tested that during installation this group is created automatically, but I wanted to ask if it would be a better idea to add it to http://slackbuilds.org/uid_gid.txt file and require it before starting the build process as I've seen in other scripts that use UIDs and GIDs from SBo list? If so, should I take the next unused GID from the list and add the code to check for the group or should I leave it for SBo admins to do? -- Audrius Kažukauskas pgpCyfMx1iiSp.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] Problem with python3
On Fri, 2010-02-26 at 12:58:24 +1100, Kevin Pulo wrote:
Hi,
This builds and installs fine, but I get the following when I try to
run the python3.1 interpreter:
$ python3.1
Could not find platform independent libraries prefix
Could not find platform dependent libraries exec_prefix
Consider setting $PYTHONHOME to prefix[:exec_prefix]
Fatal Python error: Py_Initialize: can't initialize sys standard streams
ImportError: No module named encodings.utf_8
Aborted
$
Even when I try setting $PYTHONHOME to /usr, or /usr:/usr/bin, I still
get the same error, minus the first 3 lines.
Looks like Python can't find its standard libraries. And $PYTHONHOME
var should point to them if set, not to Python executable. According to
the man page, standard libraries are searched in
${prefix}/lib/pythonversion and ${exec_prefix}/lib/pythonversion by
default (and both ${prefix} and ${exec_prefix} would be '/usr' in this
case if I'm not mistaken). I wonder if the problem you're experiencing
is related to x86_64, where Python libraries are placed in
/usr/lib64/pythonversion.
This is on Slackware64 13.0, with alienBob's -current multilib
compilers.
Any ideas?
Unfortunately, I don't have any 64bit system to test this, so I'm really
not sure how to remedy this properly. One way would be to use
$PYTHONHOME, but there should be something better.
BTW, does Python 2.x from Slackware work well? (I guess it does.) I'll
look into its SlackBuild later today to see what it does for x86_64.
I'm also wondering if copying the subdirectories of Tools/, most of
which are standalone scripts, into the site-packages/ directory, is
correct, since site-packages is supposed to be for python modules that
are imported into the interpreter. Probably these files belong in
/usr/doc/python3-3.1.1, instead of just being symlinked there.
I was basing my SlackBuild on the official one, so I believe I've copied
this bit from there.
--
Audrius Kažukauskas
pgpBY4fOtDlcf.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] fbreader.SlackBuild uses /usr/lib in x86_64
On Thu, 2010-01-14 at 20:14:18 +0200, George Vlahavas wrote:
Hi,
the current fbreader.SlackBuild on slackbuilds.org puts libraries in
/usr/lib, even when compiled under x86_64. The fix (provided by rworkman) is
apparently to change the make and make install lines to:
make LIBDIR=/usr/lib${LIBDIRSUFFIX}
make install LIBDIR=/usr/lib${LIBDIRSUFFIX} DESTDIR=$PKG
Best regards,
George
PS: I'm CCing the SBo mail list, but I'm not registered.
Sorry for late reply and thanks for report. I'm not using fbreader
anymore, so feel free to take over its maintenance (together with its
dependency liblinebreak).
--
Audrius Kažukauskas
pgpNw7lYMYX90.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] Build Errors: graphviz-2.24.0
On Fri, 2009-12-04 at 13:49:32 -0800, Rich Shepard wrote: Audrius, That avoided the first error, but now the build chokes on gv_perl.cpp: g++ -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../lib/gvc -I../../lib/common -I../../lib/graph -I../../lib/cdt -I../../lib/pathplan -DDEMAND_LOADING=1 -I/usr/lib/perl5/5.10.0/i486-linux-thread-multi/CORE -O2 -march=i486 -mtune=i686 -MT libgv_perl_la-gv_perl.lo -MD -MP -MF .deps/libgv_perl_la-gv_perl.Tpo -c gv_perl.cpp -fPIC -DPIC -o .libs/libgv_perl_la-gv_perl.o gv_perl.cpp:1232: error: expected unqualified-id before string constant gv_perl.cpp:1233: error: expected initializer before '*' token gv_perl.cpp:1238: error: 'SwigPerlWrapperPtr' does not name a type gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' gv_perl.cpp:7331: error: too many initializers for 'swig_command_info' ... gv_perl.cpp: In function 'void boot_gv(PerlInterpreter*, CV*)': gv_perl.cpp:7574: error: 'struct swig_command_info' has no member named 'wrapper' make[4]: *** [libgv_perl_la-gv_perl.lo] Error 1 make[4]: Leaving directory /tmp/SBo/graphviz-2.24.0/tclpkg/gv' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory /tmp/SBo/graphviz-2.24.0/tclpkg/gv' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory /tmp/SBo/graphviz-2.24.0/tclpkg' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory /tmp/SBo/graphviz-2.24.0' make: *** [all] Error 2 Perhaps it is SWIG related. I have -1.3.31 installed here, from a SBo script. Should that be upgraded first? Looks like SWIG is really the culprit here. You could try to upgrade it (Slackware-13.0 has 1.3.38, so maybe that's a good version to choose), or if you don't need any bindings at all, adding --enable-swig=no should disable them completely. -- Audrius Kažukauskas pgpEDuBIPqAle.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Bzr missing in repo
Hi, development/bzr is listed in ChangeLog as included, but missing in the repository. -- Audrius Kažukauskas pgp87dwPCv5VW.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] Unchecked entries for 13.0
On Mon, 2009-08-10 at 14:55:39 -0500, Robby Workman wrote:
As I promised several people privately, here's a list of things that we
have not had time to check/update for 13.0 yet:
http://slackbuilds.org/NOT_CHECKED
If you maintain one of these and would like to see it in the initial
repo for 13.0, or if you use one of them and would like to step up
and handle any needed changes, now is your chance. I can't promise
that we'll be able to merge in all of the changes we get, even if
they are fixed, but we'll do our best.
As things are merged into the 13.0 repo (which is still private,
and will be until 13.0 is released), we'll update the listing above,
so be sure to refresh that before replying.
Fixes should come in as replies to this mail, with a complete tarball
attached (just as if you were submitting it on the website - no source
code of the app should be included).
development/python3:
I'm going to update this for freshly released version 3.1.1 and solve
some issues (like /usr/bin/2to3 overwriting the one from Python
2.6.2), so it should be removed for now.
office/fbreader:
I can't test this on x86_64, but it seems to work fine on i486, the
only change needed is to set UI to qt4 in the SlackBuild. I'm also
abandoning this with libraries/liblinebreak, if anybody's interested,
feel free to take them over.
system/spambayes:
Changed ARCH from noarch to ${ARCH:-i486}, otherwise works fine as is
on -current.
--
Audrius Kažukauskas
spambayes.tar.gz
Description: application/tar-gz
pgpPANPwrONRS.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] Problems with building qemu and clamav
On Fri, 2009-05-29 at 14:42:05 +0200, Odd Martin Baanrud wrote: I have problems with building the qemu and clamav packages. Here is the error I get while building qemu: Error: esd check failed Make sure to have the esd libs and headers installed. For that you need esound. And here are those from clamav: configure: error: Cannot find libmilter make: *** No targets specified and no makefile found. Stop. And for this one you need sendmail. How should I solve these problems? Are their some packages I need to build/install? If you use slackpkg, here's a handy way to quickly look for package which has missing library: $ slackpkg search missing_lib -- Audrius Kažukauskas pgpMt4oWMKGsV.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] nicotine-plus and psyco
Hi, Just a couple of small observations: 1) full path to icon needs to be provided for nicotine-plus in its .desktop file, otherwise KDE4 won't find it; 2) it would be more appropriate for psyco to use i486 as ARCH -- after all it's a C extension, not an ordinary Python code; -- Audrius Kažukauskas pgp18CH5hnli5.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] Freeze on New Submissions to Prepare for 12.2
On Mon, 2008-11-24 at 18:54:15 +, Robby Workman wrote: Please begin testing the things you maintain on a -current system if at all possible; as with last time, anything that won't build for us or for which the source is unavailable as listed in the .info file will be removed from the repo when it goes live for 12.2. Status of SlackBuilds maintained by me in -current: audio/mp3check -- ok desktop/kkbswitch -- I'm not using KDE3 anymore, but last time I tried kkbswitch with KDE 3.5.10 from -current, it was working fine; also couldn't download the source using dl.sourceforge.net, but hadn't any problems with downloads.sourceforge.net graphics/graphviz -- ok (swig dependency not maintained by me also works fine) libraries/liblinebreak -- ok (dependency of fbreader) network/kismet -- ok office/fbreader -- ok system/spambayes -- ok (same problem downloading source as with kkbswitch) -- Audrius Kažukauskas pgp7Ni2Gr5DIf.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] Herrie 2.2 SlackBuild has old tarball still
On Tue, 2008-10-21 at 01:10:52 -0400, [EMAIL PROTECTED] wrote: Phil, I am not sure what the problem is but the best I can tell there is nothing wrong with the tarball, it is the 2.2 version. I check both my local repo and the tarball downloaded from the website. I can confirm this. Downloaded the tarball right after I got the email with the changelog mentioning herrie. The version was 2.2. -- Audrius Kažukauskas pgp3cU1fAhCzZ.pgp Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] VirtualBox
Hello, I am using KDE 4.1.1 from -current and VirtualBox 2.0.2 which I've built using a SlackBuild from SBo, and there's no menu entry for it in KMenu (or whatever it's called right now), neither I can run it by typing `VirtualBox' in command line. The only way to run it is to type a full path to /usr/lib/virtualbox/VirtualBox (BTW, it's a bit strange place for the executable file). If I remember correctly, there was no such problem with KDE3 and VirtualBox 1.6.x. I understand that SBo scripts are meant to use in -stable, but still this seems wrong. Is it just me or is it a problem of VirtualBox itself? Oh, and I've built VBox with VBOXUSERS=no QT4=yes QT3=no flags. -- Audrius Kažukauskas pgpFFpWuaAg3U.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/
