Re: [Slackbuilds-users] metis download problem

On 3/7/23, William PC wrote: > Hi, > > metis download: > http://glaros.dtc.umn.edu/gkhome/fetch/sw/metis/metis-5.1.0.tar.gz > isn't working. Development appears to have moved to Github (https://github.com/KarypisLab/METIS) but I don't see a commit with the same contents. I'll work on updating

Re: [Slackbuilds-users] memtest86+ (5.01) has deadlink

On 9/9/22, Richard Narron wrote: > On Tue, 16 Aug 2022, Ched Ex wrote: > >> Hello, >> memtest86+ v. 5.01 at the Slackware 15.0 branch has a dead link to the >> source. >> Was: https://www.memtest.org/download/5.01/memtest86+-5.01.tar.gz >> Now:

Re: [Slackbuilds-users] python-certifi and python3-certifi

On 1/2/21, Willy Sudiarto Raharjo wrote: > On 1/3/21 1:44 AM, Benjamin Trigona-Harany wrote: >> python-certifi now has Python 3 as a mandatory dependency, which makes >> python3-cetifi unnecessary. I'll be removing python3-certifi, so >> maintainers >> should update their REQUIRES accordingly and

Re: [Slackbuilds-users] Dependency cleanup after package removal

On 6/23/20, Erich Ritz via SlackBuilds-users wrote: > Original Message > On Jun 23, 2020, 5:27 AM, Fellype < fell...@gmail.com> wrote: > > Hi all! > > Just a comment/suggestion related to reverse deps: > > Then, it would be useful to have a field called "OPTIONAL" or >

Re: [Slackbuilds-users] Unstated requirement (apparently) to build octave

On 3/21/20, Jim Diamond wrote: > Well, that may be so. However, after 1525 seconds of compiling on a > somewhat low-end Xeon, here is the end of the show: > ... > help/which.m ... PASS > 8/8 > image/cmpermute.m

Re: [Slackbuilds-users] Qt5 Update to 5.12

On Fri, Jan 31, 2020, 08:12 Willy Sudiarto Raharjo wrote: > > misc/goldencheetah has a dependency on qt5-webkit that I missed. I > > think the qt5 upgrade exposes some include dependency that's missing > > in qt5-webkit ( includes headers and can't find > > ); I can't figure out what changed to

Re: [Slackbuilds-users] Qt5 Update to 5.12

On 1/30/20, Dave Woodfall wrote: > Remaining builds that fail with Qt 5.12.6: > > development/qbsAndrzej Telszewski > audio/muse Felix Pfeifer > development/cutter Fernando Lopez Jr. > misc/goldencheetah Kyle Guinn &

Re: [Slackbuilds-users] Qt5 Update to 5.12

On 1/25/20, Dave Woodfall wrote: > On 2020-01-25 14:15, > Kyle Guinn put forth the proposition: >> I got stuck here in the qt5 build. Any ideas? >> >> g++ -Wl,-O1 -L/usr/lib64 -Wl,--enable-new-dtags -Wl,--gc-sections -o >> ../../../bin/moc .obj/moc.o .obj/preproces

Re: [Slackbuilds-users] Qt5 Update to 5.12

On 1/25/20, Dave Woodfall wrote: > To the maintainers of build scripts that depend on Qt5. > > I've been testing Qt5 LTS version 5.12, and everything seems to build > apart from the following applications: > > academic/fet > audio/SuperCollider > audio/muse > development/cutter > development/qbs

Re: [Slackbuilds-users] openmpi request

On 7/25/19, Emmanuel wrote: > On Thu, Jul 25, 2019 at 5:04 AM Robby Workman > wrote: > >> On Thu, 25 Jul 2019 09:58:03 +0200 >> Karel Venken wrote: >> >> > Hi, >> > >> > For installing our cluster we need to add to the openmpi.Slackbuilds >> > with --with-pmi=pmi2 configure option. So it

Re: [Slackbuilds-users] Feature request: add $NUMJOBS to SBo build scripts

On Tue, Jul 23, 2019, 14:11 David O'Shaughnessy wrote: > On Tue, 23 Jul 2019, at 12:04 PM, Fellype wrote: > > Dear SBo Admins, > > Is it possible to add the $NUMJOBS variable to SBo build scripts by > default? At least for the next Slackware release? > > > I think that this can be more reliably

Re: [Slackbuilds-users] Memtest86+-5.01 patch for hang with SMP test #7 at 22% done

On 3/26/19, Richard Narron wrote: > On Mon, 25 Mar 2019, Matteo Bernardini wrote: > >> Il giorno lun 25 mar 2019 alle ore 18:34 Richard Narron >> ha scritto: >> > >> > Two of my machines hang in the exact same spot when using the Slackware >> > memtest with SMP (F2) at 22% done in test #7. >> >

Re: [Slackbuilds-users] TiMidity++ as daemon, failure to connect to pulseaudio

On 7/23/18, Rubén Llorente wrote: > Hello. > > The instructions provided in TiMidity++'s Slackbuild page for running > it as a daemon/alsa sequencer don't work. > https://slackbuilds.org/repository/14.2/audio/TiMidity++/ > > rc.timidity will have the daemon started, but it will fail to generate >

Re: [Slackbuilds-users] what should be the values for this two variables?

On 9/24/17, Fernando Lopez wrote: > https://github.com/zeromq/libzmq/blob/master/src/libzmq.pc.in > > what should be the values for this two variables? > > prefix=@prefix@ > exec_prefix=@exec_prefix@ > > prefix=/usr > exec_prefix=??? The configure script usually

Re: [Slackbuilds-users] Updates - 20170722.1

On 7/22/17, B Watson wrote: > On 7/22/17, Kent Fritz wrote: >> Regarding this claim on >> https://repology.org/repository/slackbuilds/problems >> : >> >> Homepage link "https://www.thc.org/thc-hydra/; is dead (cannot connect) >> for more than a month. >>

Re: [Slackbuilds-users] gpsbabel, long list of errors

On 6/15/17, Willy Sudiarto Raharjo wrote: >>> Looks like it's trying to build against Qt5. I've only tested against >>> Qt4. >>> >>> Also there is a newer version, 1.5.4, but I've held back at 1.5.3 >>> since 1.5.4 requires Qt5. Can you try a simple version bump and see

Re: [Slackbuilds-users] gpsbabel, long list of errors

On 6/12/17, Frédéric Falsetti wrote: > Hi, anybody can build gpsbabel ? > > error Qt requires a C++11 compiler and yours does not seem to be that. > a long list of errors and > > In file included from /usr/include/qt5/QtCore/qshareddata.h:46:0, > from

Re: [Slackbuilds-users] Tracking version releases

On 5/12/17, Christoph Willing wrote: > On 12/05/17 19:05, Willy Sudiarto Raharjo wrote: >>> No I hadn't seen that. It looks pretty good - despite a few odd little >>> things e.g. live555 versioning string incorrectly makes it think a >>> version from 2014 is the

Re: [Slackbuilds-users] Pablo Santamaria's builds

On 2/9/17, Christoph Willing wrote: > On 10/02/17 04:53, B Watson wrote: >> So these remain unclaimed still: >> >> academic/qrupdate > and >> academic/suitesparse > > are both optional dependencies of octave - hint :) OK. I can take academic/qrupdate.

Re: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir]

On 11/4/16, David Spencer wrote: > Hi - let me say to start that this is only a personal opinion, and > I've been too busy recently to pay careful attention to this > discussion. But IIRC we've talked about this before. In my opinion, > real life is much too

Re: [Slackbuilds-users] xulrunner deprecation

On 5/13/16, Willy Sudiarto Raharjo wrote: >> it can be it's possible to build gnash without xulrunner, but I think >> the maintainer should decide that it's the case of pursuing this way, >> in case in the end we agree to drop xulrunner. > > yes, we can use

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

On 3/14/16, Didier Spaier wrote: > Let me add: only make a change if there is a proven advantage, like > _ old way failing (provide example), where the new one does not I occasionally come across source tarballs where every file unintentionally has the sticky bit set. (I don't

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

On 3/14/16, Luís Fernando Carvalho Cavalheiro wrote: > Hey guys. As ironic it looks like, the fastest approach is find + xargs. I > won't rewrite my own SlackBuilds, but new ones will use find + xargs. Have you tried "-exec chmod 644 {} +" or "-execdir chmod 644 {} +"

Re: [Slackbuilds-users] Call for Bug Fixes, Patches, etc

On 2/23/16, Andrzej Telszewski wrote: > On 05/02/16 13:48, Martijn Dekker wrote: >> 2. The following horrible, broken and obsolete eyesore: >> >> find -L . \ >> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ >>-o -perm 511 \) -exec chmod 755 {} \;

Re: [Slackbuilds-users] Lilypond ignores the switch for not building dependencies.

On 1/5/16, Black Rider <softwarewo...@use.startmail.com> wrote: > El Sun, 03 Jan 2016 18:06:30 -0600, Kyle Guinn escribió: > >> On 1/3/16, Black Rider <softwarewo...@use.startmail.com> wrote: >>> El Sat, 02 Jan 2016 22:04:13 -0600, Kyle Guinn escribió: >>&g

Re: [Slackbuilds-users] Lilypond ignores the switch for not building dependencies.

On 1/3/16, Black Rider <softwarewo...@use.startmail.com> wrote: > El Sat, 02 Jan 2016 22:04:13 -0600, Kyle Guinn escribió: > >> On 1/2/16, Black Rider >> <softwarewo...@use.startmail.com> wrote: >>> Hello. >>> >>> I have notic

Re: [Slackbuilds-users] Patches in `$PKG/usr/doc/$PRGNAM-$VERSION/`?

On 8/10/15, Thomas Szteliga t...@websafe.pl wrote: SlackBuild templates (and scripts) contain this line: cat $CWD/$PRGNAM.SlackBuild \ $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild but what if a SlackBuild script requires patches applied during its execution. Shouldn't

Re: [Slackbuilds-users] failure building GNU Octave 3.8.2 with SuiteSparse 4.4.1, temporary workaround included

On 1/1/15, Marco Maggi marco.maggi-i...@poste.it wrote: Ciao, the latest GNU Octave release 3.8.2 fails to build when interfacing with the latest SuiteSparse release 4.4.1, because SuiteSparse changed interface in multiple places: these two packages have gotten out of sync. This

Re: [Slackbuilds-users] Error while installing package fontforge (20141014)

On 12/9/14, Christoph Willing chris.will...@iinet.net.au wrote: Maybe multilib can be implicated in the fontforge build failures but I think there's some other factor involved too. I tried building it about a week ago or so, got what I believe is the same error. It's on a 64-bit machine, but

[Slackbuilds-users] Call for testing: BLAS/LAPACK

Hi all, I have updated the blas and lapack Slackbuilds to version 3.5.0 in my user/elyk/lapack branch. I know these are dependencies of several other packages and I would appreciate any feedback if you maintain any packages that don't actually work with it. I've built octave and it seems to be

[Slackbuilds-users] Clarification of REQUIRES and dependencies

Willy and I have a disagreement about this line of http://slackbuilds.org/guidelines/ The content of REQUIRES should only be first level dependencies (i.e. no deps of deps). The disagreement occurs when package 1 depends on packages 2 and 3, and package 2 depends on 3. Should 3 be listed in 1's

Re: [Slackbuilds-users] Abandoned build scripts

On 7/7/14, Grissiom chaos.pro...@gmail.com wrote: Moreover, I'd like to abandon some of my Slackbuilds: network/mldonkey libraries/libsunpinyin misc/ibus-pinyin misc/ibus-qt misc/ibus-sunpinyin misc/ibus development/generatorrunner development/sdcc Feel free to take them if you are

Re: [Slackbuilds-users] pelican depends on Jinja2 = 2.7

On 1/25/14, Willy Sudiarto Raharjo will...@slackbuilds.org wrote: only hard-dep and direct dependencies should be listed in REQUIRES since you mentioned markupsafe in the REQUIRES, user must install it first (thus eventually have pysetuptools before installing markupsafe), so it should be

Re: [Slackbuilds-users] pelican depends on Jinja2 = 2.7

On 1/25/14, Willy Sudiarto Raharjo will...@slackbuilds.org wrote: The way I see it, if package A says it needs B and C, then I put them both in REQUIRES. Whether or not B requires C should have no effect on that. Maybe some newer version of B won't require C, and then the dependencies for A

Re: [Slackbuilds-users] On dependency definition (Was: pelican depends on Jinja2 = 2.7)

On 1/25/14, Mikko Värri v...@linuxbox.fi wrote: What Willy and Matteo are describing is, in my books, an optimization of dependency tree: removal of dependencies if they form a diamond graph. Is this optimization useful? I don't see any benefit, it just loses information. My vote would be to

[Slackbuilds-users] Sanitizing permissions

I have been using this chmod command in my scripts to sanitize permissions: chmod -R u+w,go-w,a+rX-st . In plain english, that will give read access to everyone, write access only to the owner, exec access to everyone if anyone has it, and remove all the special permissions (SUID/SGID/SVTX).

Re: [Slackbuilds-users] Desmume on 64-bit - optimization flag

On 1/23/13, xgiz...@slackbuilds.org xgiz...@slackbuilds.org wrote: I think all that would be needed is to add a line after the $SLKCFLAGS block. if [ -n $RICER_FLAGS ]; then SLKCFLAGS=$RICER_FLAGS; fi Then run your build RICER_FLAGS=-enable-more-fruitloops ./some.SlackBuild --dsomero :)

Re: [Slackbuilds-users] Desmume on 64-bit - optimization flag

On 1/22/13, Kyle Guinn ely...@gmail.com wrote: On 1/22/13, Larry Hajali larryh...@gmail.com wrote: Could just add an if statement that will add it to the SLKCFLAGS if it is detected on the computer. if grep [^s]sse3 /proc/cpuinfo 2/dev/null; then SLKCFLAGS=$SLKCFLAGS -msse3 fi Not sure

Re: [Slackbuilds-users] [PATCH]

On 9/26/12, Robby Workman rwork...@slackbuilds.org wrote: On Wed, 26 Sep 2012 00:01:06 -0500 Kyle Guinn ely...@gmail.com wrote: Here's a patch to make gnash compile. I haven't had a chance yet to build in all the optional dependencies, so there may be more updates soon-ish. Applied

Re: [Slackbuilds-users] [PATCH]

Here's a patch to make gnash compile. I haven't had a chance yet to build in all the optional dependencies, so there may be more updates soon-ish. -Kyle From d1d5d8b1c9a63f5e1e24b5902b40cabb528fbc98 Mon Sep 17 00:00:00 2001 From: Kyle Guinn ely...@gmail.com Date: Tue, 25 Sep 2012 23:51:26 -0500

Re: [Slackbuilds-users] [PATCH]

Somebody beat me to updating octave to 3.6.3, but there were some extra changes in that commit that aren't working for me. It still needs the sed-fu to find SuiteSparse headers. I've also attached some corrections to REQUIRES. -Kyle 0001-libraries-SPQR-Require-tbb.patch Description: Binary

Re: [Slackbuilds-users] [PATCH]

On 9/21/12, Robby Workman rwork...@slackbuilds.org wrote: On Fri, 21 Sep 2012 23:35:32 -0500 Kyle Guinn ely...@gmail.com wrote: Somebody beat me to updating octave to 3.6.3, but there were some extra changes in that commit that aren't working for me. It still needs the sed-fu to find

Re: [Slackbuilds-users] Proposal of SBU marker in README's

On 2/26/09, JK Wood joshuakw...@gmail.com wrote: On Thu, Feb 26, 2009 at 11:11 PM, Robby Workman rwork...@slackbuilds.org wrote: Besides, something like this would take all the fun out of comparing build times -- there would be this boring 1SBU or 10SBU or 400SBU instead of faster than a