LinuxQuestions.org - [SOLVED] Krusader slackbuild 14.2

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Krusader slackbuild 14.2 - no source available (https://www.linuxquestions.org/questions/slackware-14/krusader-slackbuild-14-2-no-source-available-4175605867/)

Gerard Lally

05-13-2017 03:13 PM

Krusader slackbuild 14.2 - no source available

Been like this for a while now. Is it not possible for the maintainer to use the source available at the official krusader website instead of using some unaudited git version at his own mirror which is as often as not unavailable?

Didier Spaier

05-13-2017 03:29 PM

Having seen this I assume that Andrzej made the choice of shipping a git version as it includes commits not applied to 2.4.0-beta3 and on the another hand 2.6.0 require Qt5. Just a guess. Maybe what you could suggest if that is the case that the source file be stored elsewhere, maybe @ sbosrcarch?

Anyway I suggest that you send an email to Andrzej about the issue and post on the SBo mailing list if you don't receive an asswer within a week or two, as suggested here.

Gerard Lally

05-13-2017 03:56 PM

Thanks Didier. It's now the third or fourth day I've tried to install this through sbopkg. I shouldn't have let the red mist descend. Having said that, it doesn't reflect very well on Linux generally or Slackbuilds specifically when this kind of thing happens with a stable release. Installing from source is easy with krusader but I was trying to keep everything as close to official as possible.

bassmadrigal

05-13-2017 11:18 PM

I ran into this issue a while back and I had Andrzej send me the source. I have it on my server if you'd like to use it.

**Link removed** (please PM me if you need a copy before the update gets pushed to SBo)

The MD5 should match the krusader.info entry (f83558662166a1537aedaaa6b1e22c4d)

EDIT: If you decide to get it, let me know when you do so I can remove the link. I don't want it to eventually 404 when I pull the source from the server.

orbea

05-14-2017 09:13 AM

Someone should probably replace the link at SBo with one hosted on a server that usually doesn't go down...

Alien Bob

05-14-2017 09:43 AM

Quote:

Originally Posted by orbea (Post 5710536)

Someone should probably replace the link at SBo with one hosted on a server that usually doesn't go down...

... or provide script that creates the tarball for you. Note that there have been some relevant commits to the krusader repository since that 20150309 commit. The most recent commit "389b153" has the date "20160328".
I wrote a quick script which checks out that latest commit and creates a tarball for you. It won't matter if there will be future commits - the script will check out that exact commit for you always.
So if you want the "git_20150309_13fa966" version to match the SBo entry instead, you need to just change one line of the script: "HASH=389b153" into "HASH=13fa966"

Code:

#!/bin/sh



BRANCH=kde4

HASH=389b153

GITURI=git://anongit.kde.org/krusader.git



# Checkout the repository:

if [ -d krusader-git*${HASH} ] ; then

  cd krusader-git*${HASH}

    git checkout ${BRANCH}

    git pull origin ${BRANCH}

  cd -

else

  git clone ${GITURI} krusader-${HASH}/

fi



# Checkout the exact commit:

cd krusader-*${HASH}/

git checkout ${BRANCH}

git checkout ${HASH}



# Retrieve the date of the commit:

COMMITDATE=$(git show -s --format=%cd --date=format:%Y%m%d ${HASH})



cd -



# Rename the source directory if this is the first time we cloned it:

if [ -d krusader-${HASH} -a ! -d krusader-git_${COMMITDATE}_${HASH} ]; then

  mv krusader-${HASH} krusader-git_${COMMITDATE}_${HASH}

fi



# Create the tarball:

tar --exclude .git -Jcf krusader-git_${COMMITDATE}_${HASH}.tar.xz krusader-git_${COMMITDATE}_${HASH}

orbea

05-14-2017 10:49 AM

I have to say I rather like this, I'm going to have to start using it. :)

Code:

COMMITDATE=$(git show -s --format=%cd --date=format:%Y%m%d ${HASH})

Before in my own git slackbuilds I was using this which calls several more binaries...

Code:

DATE="$(date -d "$(git log | awk '/Date:/ {print $4 " " $3 " " $6}' | head -1)" +%Y.%m.%d)"

bassmadrigal

05-14-2017 11:45 AM

Quote:

Originally Posted by Alien Bob (Post 5710547)

The only issue I see is that SBo doesn't allow scripts to download sources. But you could set the download link to be the archive of that commit, so that it will always download the source from github.

Code:

https://github.com/KDE/krusader/archive/389b153/krusader-389b153dab661dfc93423ce64d36bfee7843d33c.tar.gz

I reworked the script and .info to use that, and the diff is below.

Code:

diff --git a/system/krusader/krusader.SlackBuild b/system/krusader/krusader.SlackBuild

index e6a3913..4b597bb 100644

--- a/system/krusader/krusader.SlackBuild

+++ b/system/krusader/krusader.SlackBuild

@@ -26,7 +26,8 @@

 #  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.



 PRGNAM=krusader

-VERSION=${VERSION:-git_20150309_13fa966}

+VERSION=${VERSION:-389b153}

+SRCVER=${SRCVER:-389b153dab661dfc93423ce64d36bfee7843d33c}

 BUILD=${BUILD:-1}

 TAG=${TAG:-_SBo}



@@ -62,9 +63,9 @@ set -e

 rm -rf $PKG

 mkdir -p $TMP $PKG $OUTPUT

 cd $TMP

-rm -rf $PRGNAM-$VERSION

-tar xvf $CWD/$PRGNAM-$VERSION.tar.xz

-cd $PRGNAM-$VERSION

+rm -rf $PRGNAM-$SRCVER

+tar xvf $CWD/$PRGNAM-$SRCVER.tar.gz

+cd $PRGNAM-$SRCVER

 chown -R root:root .

 find -L . \

  \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \

diff --git a/system/krusader/krusader.info b/system/krusader/krusader.info

index 7c6aa9c..8422545 100644

--- a/system/krusader/krusader.info

+++ b/system/krusader/krusader.info

@@ -1,8 +1,8 @@

 PRGNAM="krusader"

-VERSION="git_20150309_13fa966"

+VERSION="389b153"

 HOMEPAGE="https://krusader.org/"

-DOWNLOAD="http://mirror.telszewski.net/source/krusader/krusader-git_20150309_13fa966.tar.xz"

-MD5SUM="f83558662166a1537aedaaa6b1e22c4d"

+DOWNLOAD="https://github.com/KDE/krusader/archive/389b153/krusader-389b153dab661dfc93423ce64d36bfee7843d33c.tar.gz"

+MD5SUM="f0a98626e73e560a5338a2871bddf935"

 DOWNLOAD_x86_64=""

 MD5SUM_x86_64=""

 REQUIRES=""

atelszewski

05-14-2017 01:01 PM

Hi,

Long story short, I'm out of time till the end of May.

My server had a disk failure, it'll be fixed next month.
That's the reason the source is not available.

The reason I chose to host the source myself is to shorten the version string (i.e. not using the full git hash).

The reason I chose that particular commit is that it has some more or less useful changes after the 2.4.0-beta and it is the last commit that still compiles on KDE4.

P.S.
Jeremy Hansen emailed me with some hints on how I can solve the situation and not host the source on my server.
I can't believe I haven't figured it out before ;-)
Thanks Jeremy :-)

--
Best regards,
Andrzej Telszewski

Gerard Lally

05-14-2017 01:21 PM

Quote:

Originally Posted by bassmadrigal (Post 5710371)

I ran into this issue a while back and I had Andrzej send me the source. I have it on my server if you'd like to use it.

Thanks for your kind offer. The problem really is that this situation reflects badly on Slackbuilds for a stable release. No offence, but the problem is not resolved by yet another private individual temporarily stepping in with his own private server. I had a similar situation with the Xen slackbuild last year. It takes quite a leap of faith to trust a Level 1 hypervisor hosted on a private server when the source is already available at the official Xen download site. Trust should not be taken for granted, especially given that Slackbuilds - built and installed as root - do not honour the principle of least privilege.

Gerard Lally

05-14-2017 01:23 PM

Quote:

Originally Posted by Alien Bob (Post 5710547)

I wrote a quick script which checks out that latest commit and creates a tarball for you. It won't matter if there will be future commits - the script will check out that exact commit for you always.

Thank you Eric.

atelszewski

05-14-2017 02:07 PM

Hi,

I've just sent SlackBuild update, so that the source is downloaded from github.

--
Best regards,
Andrzej Telszewski

55020

05-14-2017 03:01 PM

Quote:

Originally Posted by Gerard Lally (Post 5710623)

The problem really is that this situation reflects badly on Slackbuilds for a stable release. No offence, but the problem is not resolved by yet another private individual temporarily stepping in with his own private server.

This is complaint 1 of 3 :)

It may not be much consolation, because it's another instance of the "private individual + private server" design pattern, but pretty much every SlackBuild's source tarball is mirrored at sbosrcarch, http://slackware.uk/sbosrcarch/ which is a heroic co-production between Urchlay and Tadgy. Taking this to the next level, some of the more popular build tools are sbosrcarch-aware and will automatically substitute a download from sbosrcarch if the canonical download is found to be unavailable.

I see no way that SlackBuilds.org could do a better job than sbosrcarch. We could, however, and probably should, update the FAQ etc to mention sbosrcarch. Meanwhile, please accept this post as an interim update.

Quote:

Originally Posted by Gerard Lally (Post 5710623)

It takes quite a leap of faith to trust a Level 1 hypervisor hosted on a private server when the source is already available at the official Xen download site. Trust should not be taken for granted.

This is complaint 2 of 3 :)

It may not be much consolation, but in this scenario, you are Emperor Nero, and me and Willy are your food tasters. If a maintainer wants to poison you, then me or Willy will get poisoned first when we review the submission. We don't want to get poisoned, so mirrors and repacks and self hosted tarballs are a last resort -- we always prefer to download from the canonical provenance.

There are also some cases where the SlackBuild is for software written by the actual maintainer. This is the ultimate instance of the self-hosted tarball. There is no way of banning self-hosted tarballs without banning software creators from supporting Slackware by providing SBo SlackBuilds.

Quote:

Originally Posted by Gerard Lally (Post 5710623)

especially given that Slackbuilds - built and installed as root - do not honour the principle of least privilege

This is complaint 3 of 3 ;)

First, not being root will help to protect you from erroneous software, but it won't protect you from malicious software. The files I truly care about on my boxes are not those in /usr/lib64 or /etc, but those in /home/d.

Second, there is at least one build tool that supports non-root building and packaging. All the SlackBuilds I review are built this way and test-installed to see what happens.

Thanks for raising these valid concerns, it's not often that we have the chance to explain the background ideas (and limitations) of our trust model.

Gerard Lally

05-14-2017 03:23 PM

Quote:

Originally Posted by 55020 (Post 5710636)

It may not be much consolation, but in this scenario, you are Emperor Nero

That'll do Me. Thanks!

Didier Spaier

05-14-2017 03:24 PM

Quote:

Originally Posted by 55020 (Post 5710636)

Second, there is at least one build tool that supports non-root building and packaging.

fakeroot is my friend. Not because I don't trust other people's work, rather as a protection against my own stupidity (I have messed up perms in big sub-trees more than once building my own packages).

Gerard Lally

05-14-2017 03:24 PM

Quote:

Originally Posted by 55020 (Post 5710636)

Second, there is at least one build tool that supports non-root building and packaging.

Namely?

bassmadrigal

05-14-2017 03:49 PM

Quote:

Originally Posted by Gerard Lally (Post 5710623)

No offence, but the problem is not resolved by yet another private individual temporarily stepping in with his own private server.

I know trust can be difficult. That is at least why I mentioned that the md5sum matches the one in the .info, so it is at least matching what Andrzej had originally used to build the SlackBuild. But no worries, I'm certainly not offended (but I will be removing the link now... I just would prefer links to my site not 404, since I occasionally clean out my temp/ directory on that site (hence the name of the folder)).

Quote:

Originally Posted by Gerard Lally (Post 5710645)

Namely?

He wasn't wanting to toot his own horn, but he created slackrepo, and it has the ability to create packages using fakeroot. But it is much more than something like sbopkg. It will actually create a full repo with all your software, and it will update all the dependency tree when one of them changes (if x264 is updated, it will rebuild all the software that relies on x264, and the software that relies on those, etc, etc).

Gerard Lally

05-14-2017 04:35 PM

Quote:

Originally Posted by bassmadrigal (Post 5710650)

That's interesting. Much more akin to NetBSD pkgsrc, which allows you to build and install an entire system (minus base, which is <200MB) as an ordinary user.

Can we expect this tool to see more development or has it been abandoned?

montagdude

05-14-2017 04:42 PM

At the risk of sounding ignorant, can't sbopkg build package as a regular user if you redirect TMP and OUTPUT (and maybe change some of its other paths in the config file)?

bassmadrigal

05-14-2017 04:47 PM

Quote:

Originally Posted by Gerard Lally (Post 5710659)

Can we expect this tool to see more development or has it been abandoned?

I had been dormant for a few years (mainly because it worked and David was spending time elsewhere), but he has recently started tinkering with it more. Check out his github.

https://github.com/idlemoor/slackrepo

atelszewski

05-14-2017 04:48 PM

Hi,

Quote:

Originally Posted by Gerard Lally (Post 5710623)

No offence, but the problem is not resolved by yet another private individual temporarily stepping in with his own private server.

Well, if it solved your problem, then the problem is resolved ;->

I don't see you being harsh here, but anyways, keep in mind that SlackBuild maintainers sometimes try hard to make users lifes easy.
The source tarballs not always are available in the form we wished they were.
So we try to somehow distribute them, so that they are available.
Well, sometimes we fail ;-)

And version strings are sometimes art on its own.

--
Best regards,
Andrzej Telszewski

Gerard Lally

05-14-2017 04:53 PM

Quote:

Originally Posted by atelszewski (Post 5710666)

Hi,

Well, if it solved your problem, then the problem is resolved ;->

I don't see you being harsh here, but anyways, keep in mind that SlackBuild maintainers sometimes try hard to make users lifes easy.
The source tarballs not always are available in the form we wished they were.
So we try to somehow distribute them, so that they are available.
Well, sometimes we fail ;-)

And version strings are sometimes art on its own.

No problem Andrzej. Dzieki.

atelszewski

05-14-2017 04:56 PM

Hi,

Quote:

Originally Posted by Gerard Lally (Post 5710668)

No problem Andrzej. Dzieki.

;-)

--
Best regards,
Andrzej Telszewski

Gerard Lally

05-15-2017 07:58 PM

Source unavailable again.

bassmadrigal

05-15-2017 08:09 PM

Were you talking about my source or Andrzej's? Either way, try using this .SlackBuild and .info. It should build the newest KDE4 version of krusader, and it gets the source directly from github. I think this might be what Andrzej will submit once SBo submissions are reopened (they closed it for a bit due to a server migration).

krusader.SlackBuild

Code:

#!/bin/sh



# Slackware build script for krusader



# Copyright 2006,2007,2008,2009,2010  Robby Workman, Northport, Alabama, USA

# Copyright 2010 Grigorios Bouzakis <grbzks@xsmail.com>

# Copyright 2012 Bill Kirkpatrick <bkirkp@gmail.com>

# Copyright 2016 Andrzej Telszewski, Banie

# All rights reserved.

#

# Redistribution and use of this script, with or without modification, is

# permitted provided that the following conditions are met:

#

# 1. Redistributions of this script must retain the above copyright

#    notice, this list of conditions and the following disclaimer.

#

#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED

#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO

#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;

#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF

#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.



PRGNAM=krusader

VERSION=${VERSION:-389b153}

SRCVER=${SRCVER:-389b153dab661dfc93423ce64d36bfee7843d33c}

BUILD=${BUILD:-1}

TAG=${TAG:-_SBo}



if [ -z "$ARCH" ]; then

  case "$( uname -m )" in

    i?86) ARCH=i586 ;;

    arm*) ARCH=arm ;;

      *) ARCH=$( uname -m ) ;;

  esac

fi



CWD=$(pwd)

TMP=${TMP:-/tmp/SBo}

PKG=$TMP/package-$PRGNAM

OUTPUT=${OUTPUT:-/tmp}



if [ "$ARCH" = "i586" ]; then

  SLKCFLAGS="-O2 -march=i586 -mtune=i686"

  LIBDIRSUFFIX=""

elif [ "$ARCH" = "i686" ]; then

  SLKCFLAGS="-O2 -march=i686 -mtune=i686"

  LIBDIRSUFFIX=""

elif [ "$ARCH" = "x86_64" ]; then

  SLKCFLAGS="-O2 -fPIC"

  LIBDIRSUFFIX="64"

else

  SLKCFLAGS="-O2"

  LIBDIRSUFFIX=""

fi



set -e



rm -rf $PKG

mkdir -p $TMP $PKG $OUTPUT

cd $TMP

rm -rf $PRGNAM-$SRCVER

tar xvf $CWD/$PRGNAM-$SRCVER.tar.gz

cd $PRGNAM-$SRCVER

chown -R root:root .

find -L . \

 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \

  -o -perm 511 \) -exec chmod 755 {} \; -o \

 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \

  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;



mkdir -p build

cd build

  cmake \

    -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \

    -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \

    -DCMAKE_INSTALL_PREFIX=/usr \

    -DLIB_SUFFIX=${LIBDIRSUFFIX} \

    -DSYSCONF_INSTALL_DIR=/etc/kde \

    -DMAN_INSTALL_DIR=/usr/man \

    -DCMAKE_BUILD_TYPE=Release \

    ..

  make

  make install DESTDIR=$PKG

cd ..



find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \

  | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true



find $PKG/usr/man -type f -exec gzip -9 {} \;

for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done



mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION

cp -a AUTHORS COPYING CREDITS ChangeLog FAQ INSTALL README TODO \

  $PKG/usr/doc/$PRGNAM-$VERSION

cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild



mkdir -p $PKG/install

cat $CWD/slack-desc > $PKG/install/slack-desc

cat $CWD/doinst.sh > $PKG/install/doinst.sh



cd $PKG

/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}

krusader.info

Code:

PRGNAM="krusader"

VERSION="389b153"

HOMEPAGE="https://krusader.org/"

DOWNLOAD="https://github.com/KDE/krusader/archive/389b153/krusader-389b153dab661dfc93423ce64d36bfee7843d33c.tar.gz"

MD5SUM="f0a98626e73e560a5338a2871bddf935"

DOWNLOAD_x86_64=""

MD5SUM_x86_64=""

REQUIRES=""

MAINTAINER="Andrzej Telszewski"

EMAIL="atelszewski@gmail.com"

Gerard Lally

05-15-2017 08:26 PM

Quote:

Originally Posted by bassmadrigal (Post 5711197)

Were you talking about my source or Andrzej's?

Just the source linked at slackbuilds.org.

Quote:

Either way, try using this .SlackBuild and .info. It should build the newest KDE4 version of krusader, and it gets the source directly from github. I think this might be what Andrzej will submit once SBo submissions are reopened (they closed it for a bit due to a server migration).

OK. I didn't realise that. Thanks for the slackbuild; I'll just compile from the krusader.org source for the time being anyway. It's straightforward. I was just making the point in my OP that these problems reflect badly on Slackware, through no fault of PV of course. They can be frustrating when they accumulate; today I had another problem trying to download slackrepo!

55020

05-16-2017 05:01 AM

oh, yes, I'd sort of forgotten about that, sorry :(

You can download and build the latest git master with this:

Code:

wget https://github.com/idlemoor/slackrepo/archive/master/slackrepo-master.tar.gz

tar xf slackrepo-master.tar.gz slackrepo-master/SlackBuild/ --strip-components=2

chmod 755 ./slackrepo.SlackBuild

OUTPUT=$(pwd) VERSION=master ./slackrepo.SlackBuild

upgradepkg --install-new --reinstall ./slackrepo-master-noarch-1_SBo.tgz

It's not got many bugs at the moment (I broke --dry-run and --keep-tmp last week), but I still need to add some new contributions and update the documentation before I tag a new version.

My saintly pal bassmadrigal has a copy of the last tagged version from two years ago:
http://bassmadrigal.tk/temp/slackrep...arch-1_dbs.txz

Oh, the irony of that word 'temp' in his URL :rolleyes:

bassmadrigal

05-16-2017 06:38 AM

Quote:

Originally Posted by 55020 (Post 5711317)

My saintly pal bassmadrigal has a copy of the last tagged version from two years ago:
http://bassmadrigal.tk/temp/slackrep...arch-1_dbs.txz

Oh, the irony of that word 'temp' in his URL :rolleyes:

Well, if it's any consolation, I haven't had it archived there for 2 years... maybe just a month or so ;)

And temp makes it sound better if the file no longer becomes available whenever I decide to clear out that folder :D

atelszewski

05-22-2017 07:51 AM

Hi,

There you go.

--
Best regards,
Andrzej Telszewski

montagdude

05-22-2017 08:05 AM

Quote:

Originally Posted by montagdude (Post 5710663)

At the risk of sounding ignorant, can't sbopkg build package as a regular user if you redirect TMP and OUTPUT (and maybe change some of its other paths in the config file)?

FWIW (probably not much) I tried this, but it doesn't work because the SlackBuild scripts chown the build directory as root:root.

Didier Spaier

05-22-2017 08:15 AM

Quote:

Originally Posted by montagdude (Post 5713736)

FWIW (probably not much) I tried this, but it doesn't work because the SlackBuild scripts chown the build directory as root:root.

fakeroot is your friend.

I always use it, for SBo scripts I set TMP and OUTPUT to $CWD i.e. $(pwd), make sure makepkg is called with its full path, set PKGTYPE to txz.

Then just do "fakeroot sh <package>.SlackBuild" and find all outputs in $(pwd).

montagdude

05-22-2017 08:25 AM

Quote:

Originally Posted by Didier Spaier (Post 5713742)

Thanks for the info. I'm not really interested in doing it myself, but I just wanted to answer my previous query about whether sbopkg and the like can build packages as a regular user. It sounds like the answer is no.

atelszewski

05-22-2017 09:13 AM

Hi,

slackrepo is able to build as regular user.
Probably there are others that can do that too (sbopkg is not one of them).

All that being said, my preferred setup is to use slackrepo running as root within virtual machine.

--
Best regards,
Andrzej Telszewski

All times are GMT -5. The time now is 03:53 PM.