LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-21-2019, 08:50 AM   #1
cdek
Member
 
Registered: Jul 2016
Posts: 39

Rep: Reputation: Disabled
How to keep a fresh slackware-current installation up to date?


I installed a fresh slackware-current on an Intel NUC using the iso from here:

http://bear.alienbase.nl/mirrors/sla...4-current-iso/

I've been using Slackware 14.2 on my main PC since its release in 2016, and I would have been perfectly happy with it on the NUC as well, but it didn't recognize the nvme ssd.

On slackware 14.2, I update the system with slackpkg by unselecting a mirror and running the following commands:

Code:
# slackpkg update gpg (first time only)
# slackpkg update
# slackpkg upgrade-all
I saw in another thread that for -current this should be

Code:
# slackpkg update gpg (first time only)
# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system
After unselecting a mirror for current and running "slackpkg update gpg", I get the following message from slackpkg:

Quote:
You have selected a mirror for Slackware -current in /etc/slackpkg/mirrors,
but Slackware version 14.2+ appears to be installed.

Slackware -current is the development (i.e. unstable) tree.

Is this really what you want?

To confirm your choice, press Y, else press N. Then, press Enter
I think "14.2+" means "current". I'm a bit hesitant here, but I think I can just say "Yes" here. Am I right?

Another thing that I'm trying to learn is managing slackbuilds on current. I have installed a ton of software from slackbuilds.org on my slackware 14.2, but now I'm directed to the git repository of ponce.

http://cgit.ponce.cc/slackbuilds/

I have two problems here:

I am used to sbotools to install from slackbuilds.org. It has worked for me almost flawlessly. Amazing! But now I have to use sbopkg which I'm less familiar with. I installed a bunch of software with:

Code:
# sbopkg -i <package>
However when I run "sbopkg" to enter dialog mode and want to list the installed packages, it says

Code:
 It appears that you have no SBo-git packages installed.
So, how come it doesn't see my installed packages?

And secondly, how do I upgrade the ponce slackbuilds? Is there an equivalent for sboupgrade or even better, can I use sbotools?

Many thanks!
 
Old 06-21-2019, 09:01 AM   #2
linus72
LQ Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: Slack14.2/Many
Posts: 5,573

Rep: Reputation: 470Reputation: 470Reputation: 470Reputation: 470Reputation: 470
subscribing to this post
 
Old 06-21-2019, 09:05 AM   #3
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 6,049

Rep: Reputation: Disabled
Quote:
Originally Posted by cdek View Post
I think "14.2+" means "current". I'm a bit hesitant here, but I think I can just say "Yes" here. Am I right?
yes.

Quote:
Another thing that I'm trying to learn is managing slackbuilds on current. I have installed a ton of software from slackbuilds.org on my slackware 14.2, but now I'm directed to the git repository of ponce.

http://cgit.ponce.cc/slackbuilds/

I have two problems here:

I am used to sbotools to install from slackbuilds.org. It has worked for me almost flawlessly. Amazing! But now I have to use sbopkg which I'm less familiar with. I installed a bunch of software with:

Code:
# sbopkg -i <package>
However when I run "sbopkg" to enter dialog mode and want to list the installed packages, it says

Code:
 It appears that you have no SBo-git packages installed.
So, how come it doesn't see my installed packages?
you probably have to configure the right repository in sbopkg: read the first post of this topic

https://www.linuxquestions.org/quest...ls-4175561999/

you can also do an "ls -1 /var/log/packages/*ponce".

(note that sbopkg doesn't resolve dependencies, you have to use the sqg shipped with it to generate build queues).

Quote:
And secondly, how do I upgrade the ponce slackbuilds? Is there an equivalent for sboupgrade or even better, can I use sbotools?
please read the third post the topic I linked you above.

note that using current you often will have to rebuild also the dependencies of the stuff you want to upgrade, for example when icu4c or poppler or whatever else gets a *.so version bump, it's not that straightforward as using a stable installation: current is not a rolling release a-la-archlinux, it's the developing version of the distribution, it's mostly rock-solid but you should know that you can possibly face occasional breaks (and package rebuilds).
that is to say that, IMHO, if you need an always rock solid os just use stable.

Last edited by ponce; 06-21-2019 at 09:08 AM.
 
3 members found this post helpful.
Old 06-21-2019, 09:12 AM   #4
linus72
LQ Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: Slack14.2/Many
Posts: 5,573

Rep: Reputation: 470Reputation: 470Reputation: 470Reputation: 470Reputation: 470
May I add, and correct me if wrong...

In slackware current many sboui pkgs appear as "upgrades" when actually they would be equal or downgrades compared to pkgs added in current that are not in 14.2
For instance in my slackerc build here 06-17-19, if I update sboui it shows as upgrades a bunch of sbo builds that are not installed by slackbuilds but by slackware
https://sourceforge.net/projects/sla...acker-current/

I assume (lol) that these should not be "upgraded" by sboui/slackbuilds as they would be in fact downgrades?
Ponce, your wisdom would be appreciated and AlienBob...
 
Old 06-21-2019, 09:14 AM   #5
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 6,049

Rep: Reputation: Disabled
Quote:
Originally Posted by linus72 View Post
May I add, and correct me if wrong...

In slackware current many sboui pkgs appear as "upgrades" when actually they would be equal or downgrades compared to pkgs added in current that are not in 14.2
For instance in my slackerc build here 06-17-19, if I update sboui it shows as upgrades a bunch of sbo builds that are not installed by slackbuilds but by slackware
https://sourceforge.net/projects/sla...acker-current/

I assume (lol) that these should not be "upgraded" by sboui/slackbuilds as they would be in fact downgrades?
Ponce, your wisdom would be appreciated and AlienBob...
I don't understand to what are you referring to... could you do some actual examples with name of the packages and versions?
 
Old 06-21-2019, 10:06 AM   #6
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Ubuntu, Debian, Slackware
Posts: 2,151
Blog Entries: 6

Rep: Reputation: 2433Reputation: 2433Reputation: 2433Reputation: 2433Reputation: 2433Reputation: 2433Reputation: 2433Reputation: 2433Reputation: 2433Reputation: 2433Reputation: 2433
Quote:
Originally Posted by cdek View Post
Another thing that I'm trying to learn is managing slackbuilds on current. I have installed a ton of software from slackbuilds.org on my slackware 14.2, but now I'm directed to the git repository of ponce.
Well this is interesting, I wonder how that redirect happened. I have been using 14.2 Slackbuilds, as far as I know, with sbopkg. Everything seems to work fine on -current.

EDIT: maybe it was because you upgraded to -current whereas I did a fresh install of one of Eric's ISOs. Not sure.

EDIT2: a lot of the versions in 14.2 Slackbuilds seem to be the same as in ponce's repo for the packages I use.

Last edited by Lysander666; 06-21-2019 at 10:15 AM.
 
Old 06-22-2019, 05:20 PM   #7
linus72
LQ Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: Slack14.2/Many
Posts: 5,573

Rep: Reputation: 470Reputation: 470Reputation: 470Reputation: 470Reputation: 470
this is what I mean Ponce, thanks for any input
it lists like 20-30 pkgs that need upgrading that seem to already be installed from Slackware?
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2019-06-22_18-14-24.png
Views:	160
Size:	67.6 KB
ID:	30778  

Last edited by linus72; 06-22-2019 at 05:21 PM.
 
Old 06-23-2019, 09:33 AM   #8
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 6,049

Rep: Reputation: Disabled
the terminal window shell you opened in the front is covering the version that your third-party software manager is proposing to update to, so I cannot tell you what's happening ("Installed: 2.4.3 (Build 2) -> Ai[?????]").
can you please do another screenshot without that terminal window?

Last edited by ponce; 06-23-2019 at 11:57 AM.
 
Old 06-24-2019, 04:57 AM   #9
cdek
Member
 
Registered: Jul 2016
Posts: 39

Original Poster
Rep: Reputation: Disabled
I think what linus72 means is that Slackware packages from current also appear in the SBo-git repo as upgradeable:

eg (without sboui in the way)

Code:
➜  ~ ls -l /var/adm/packages/argon2-20171227-x86_64-1 
-rw-r--r-- 1 root root 1139 Jun 18 22:34 /var/adm/packages/argon2-20171227-x86_64-1
➜  ~ ls /var/lib/sbopkg/SBo-git/libraries/argon2/argon2.SlackBuild 
/var/lib/sbopkg/SBo-git/libraries/argon2/argon2.SlackBuild
argon2 is not part of Slackware 14.2, but there is a slackbuild for it (https://slackbuilds.org/repository/1...?search=argon2

However, argon2 now is part of Slackware current https://mirrors.slackware.com/slackw...7-x86_64-1.txt, but it's still in the unofficial Slackbuilds repo for current https://github.com/Ponce/slackbuilds...braries/argon2

It seems therefore that in current, Slackbuilds get mixed up with native Slackware packages...
 
Old 06-24-2019, 05:09 AM   #10
cdek
Member
 
Registered: Jul 2016
Posts: 39

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ponce View Post
yes.


you probably have to configure the right repository in sbopkg: read the first post of this topic

https://www.linuxquestions.org/quest...ls-4175561999/

you can also do an "ls -1 /var/log/packages/*ponce".
I followed the instructions from here https://github.com/Ponce/slackbuilds...ry-with-sbopkg

I still don't understand why "sbopkg -p" doesn't list anything. Of course I can list them with "ls -1 /var/log/packages/*ponce" without problems:

Code:
➜  ~ ls -1 /var/log/packages/*ponce
/var/log/packages/FontAwesome-4.7.0-noarch-1ponce
/var/log/packages/OpenAL-1.18.0-x86_64-1ponce
/var/log/packages/awesome-4.3-x86_64-1ponce
/var/log/packages/awesome-extra-2019021001-noarch-1ponce
/var/log/packages/calc-2.12.7.2-x86_64-1ponce
/var/log/packages/check-0.12.0-x86_64-1ponce
/var/log/packages/djvusmooth-0.2.19-x86_64-1ponce
/var/log/packages/ffmpeg4-4.1-x86_64-1ponce
/var/log/packages/geoclue2-2.4.7-x86_64-1ponce
/var/log/packages/ghc-8.4.3-x86_64-2ponce
/var/log/packages/girara-0.3.0-x86_64-1ponce
/var/log/packages/irrlicht-1.8.4-x86_64-1ponce
/var/log/packages/lgi-0.9.2-x86_64-1ponce
/var/log/packages/libass-0.14.0-x86_64-1ponce
/var/log/packages/libconfig-1.7.2-x86_64-1ponce
/var/log/packages/libmpdclient-2.9-x86_64-1ponce
/var/log/packages/libtermkey-0.22-x86_64-1ponce
/var/log/packages/libuv-1.29.1-x86_64-1ponce
/var/log/packages/libvterm-20181126-x86_64-1ponce
/var/log/packages/libxdg-basedir-1.2.0-x86_64-1ponce
/var/log/packages/libxkbcommon-0.8.4-x86_64-1ponce
/var/log/packages/lua-5.1.5-x86_64-1ponce
/var/log/packages/lua-lpeg-1.0.2-x86_64-1ponce
/var/log/packages/lua-mpack-1.0.7-x86_64-1ponce
/var/log/packages/luajit-2.0.5-x86_64-2ponce
/var/log/packages/mpd-0.20.18-x86_64-1ponce
/var/log/packages/msgpack-c-3.2.0-x86_64-1ponce
/var/log/packages/ncmpcpp-0.7.7-x86_64-1ponce
/var/log/packages/neovim-0.3.7-x86_64-1ponce
/var/log/packages/python-djvulibre-0.8-x86_64-1ponce
/var/log/packages/ranger-1.9.2-x86_64-3ponce
/var/log/packages/redshift-1.12-x86_64-2ponce
/var/log/packages/rofi-1.5.1-x86_64-1ponce
/var/log/packages/rubygem-asciidoctor-1.5.6.1-x86_64-1ponce
/var/log/packages/sbotools-2.7-noarch-1ponce
/var/log/packages/sboui-2.0.1-x86_64-1ponce
/var/log/packages/slock-1.4-x86_64-1ponce
/var/log/packages/unibilium-2.0.0-x86_64-1ponce
/var/log/packages/unrar-5.6.1-x86_64-1ponce
/var/log/packages/wxPython-2.8.12.1-x86_64-2ponce
/var/log/packages/xcb-util-xrm-1.3-x86_64-1ponce
/var/log/packages/zathura-0.3.8-x86_64-1ponce
/var/log/packages/zathura-djvu-0.2.7-x86_64-1ponce
/var/log/packages/zsh-completions-0.30.0-x86_64-1ponce
/var/log/packages/zsh-syntax-highlighting-20181101-x86_64-1ponce
My sbopkg.conf looks like this:

Code:
➜  ~ cat /etc/sbopkg/sbopkg.conf
# $Id$
#
# Please read the sbopkg.conf(5) man page for information about this
# configuration file, including an explanation of how to set these
# variables.

# The following variables are used by sbopkg and by the SlackBuild
# scripts themselves.  They must be exported for this reason.
export TMP=${TMP:-/tmp/SBo}
export OUTPUT=${OUTPUT:-/tmp}

# The following are variables used by sbopkg.  Any of these variables
# could be exported, if desired.

# Path variables
LOGFILE=${LOGFILE:-/var/log/sbopkg/sbopkg-build-log}
QUEUEDIR=${QUEUEDIR:-/var/lib/sbopkg/queues}
REPO_ROOT=${REPO_ROOT:-/var/lib/sbopkg}
SRCDIR=${SRCDIR:-/var/cache/sbopkg}
# sbopkg's temporary directory (where its internal temporary files are
# kept and where packages are made prior to being moved to OUTPUT)
# defaults to /tmp/sbopkg.XXXXXX where 'XXXXXX' is a random string. If
# /tmp is not a suitable containing directory, pass in an alternate
# TMPDIR or modify the following variable. This is actually a mktemp(1)
# variable.
export TMPDIR=${TMPDIR:-/tmp}

# Other variables:
CLEANUP=${CLEANUP:-NO}
DEBUG_UPDATES=${DEBUG_UPDATES:-0}
KEEPLOG=${KEEPLOG:-YES}
MKDIR_PROMPT=${MKDIR_PROMPT:-YES}
NICE=${NICE:-10}
REPO_BRANCH=${REPO_BRANCH:-current}
REPO_NAME=${REPO_NAME:-SBo-git}

# The following variable determines if multiple instances of sbopkg can
# be run simultaneously. It is *strongly* recommended that this value be
# set to NO. Do not set it to YES without first reading the
# sbopkg.conf(5) man page.
ALLOW_MULTI=${ALLOW_MULTI:-NO}

# The following variables are required and can be tweaked if desired,
# although this is not recommended.  Note:  rsync already uses
# --archive, --delete, --no-owner, and --exclude in the main sbopkg
# script so there is no need to add those flags here.
DIFF=${DIFF:-diff}
DIFFOPTS=${DIFFOPTS:--u}
RSYNCFLAGS="${RSYNCFLAGS:---verbose --timeout=30}"
WGETFLAGS="${WGETFLAGS:--c --progress=bar:force --timeout=30 --tries=5}"

# SRC_REPO defaults to "http://slackware.uk/sbosrcarch". To use
# a different repository, uncomment and edit this variable. The value
# must be the URL of the directory containing the by-name and by-md5
# sub directories, and should NOT have a trailing slash.
# SRC_REPO="http://slackware.uk/sbosrcarch"
I there anything else that I can check or needs configuring?

Last edited by cdek; 06-24-2019 at 05:11 AM. Reason: added link for instructions to configure sbopkg
 
Old 06-24-2019, 05:11 AM   #11
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 6,049

Rep: Reputation: Disabled
I usually remove packages added to Slackware current from the unofficial repository for current: you can see the removals here (they have a commit message "foo/bar: Removed (added to Slackware).").
this way you shouldn't have proposed updates to the packages addition in current because the scripts with the same name shouldn't simply be there.
as I stated multiple times, but seem useful to state it again here, I don't remove them from the REQUIRES lines in the *.info files of the scripts that need the removed SlackBuilds as dependencies (or it will be a nightmare when rebasing a lot more than the actual =~500 branches every week), sorry if this confuses your favourite third party tool.

argon2 should be an exeception to what written above, it just slipped... report other oversights (BTW, thanks for this!) in the pinned thread dedicated to this repository.

Quote:
Originally Posted by cdek View Post
I still don't understand why "sbopkg -p" doesn't list anything.
[...]
I there anything else that I can check or needs configuring?
maybe the sbopkg maintainer could answer this if he spots this topic: if he doesn't you can file an issue on github.

EDIT: regarding this it might be possible that the behaviour you notice is already fixed in sbopkg's git repository, so it will work just fine when the next version will be out.

Last edited by ponce; 06-24-2019 at 06:38 AM.
 
Old 06-24-2019, 07:36 AM   #12
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,874

Rep: Reputation: 1437Reputation: 1437Reputation: 1437Reputation: 1437Reputation: 1437Reputation: 1437Reputation: 1437Reputation: 1437Reputation: 1437Reputation: 1437
Quote:
Originally Posted by linus72 View Post
this is what I mean Ponce, thanks for any input
it lists like 20-30 pkgs that need upgrading that seem to already be installed from Slackware?
First, make sure your SBo package manager is using ponce's repo for -current. If you find packages like this, double check that they are actually coming from Slackware and not some other 3rd-party repository, then report them to ponce for removal. As a temporary solution, you can blacklist them in sboui until they are removed.
 
Old 06-24-2019, 02:30 PM   #13
hpfeil
Member
 
Registered: Nov 2010
Location: Tucson, Arizona US
Distribution: Slackware Current
Posts: 254
Blog Entries: 1

Rep: Reputation: Disabled
how I stay current

> How to keep a fresh slackware-current installation up to date?

I've been using a couple of scripts to stay current. They need to be combined before release on github. Since you asked, here are chk.new and get.new. Remember, work in progress, still some manual cleanup tasks, lots of comments to add:
chk.new
Code:
#!/bin/bash

# delete the old ChangeLog
if [ -e ChangeLog.txt ]; then rm ChangeLog.txt; fi
#get new ChangeLog
wget https://mirrors.kernel.org/slackware/slackware64-current/ChangeLog.txt

# keep only the top section
sed -i '/+--------------------------+/,$d' ChangeLog.txt

# omit comments that begin with spaces
sed -i '/^ /d' ChangeLog.txt

# see if any new changes
date +%s -d "$(head -n 1 ChangeLog.txt)"
date +%s -f last.upd

# compare the two dates, proceed to get the new packages if not equal
if [[ $(date +%s -d "$(head -n 1 ChangeLog.txt)") -ne $(date +%s -f last.upd) ]]; then ./get.new; fi
get.new
Code:
#!/bin/bash

echo $(head -n 1 ChangeLog.txt) > last.upd
sed -i '/UTC/d' ChangeLog.txt

awk -F: '{print $1}' ChangeLog.txt > fu
sed -i 's/^/https\:\/\/mirrors.kernel.org\/slackware\/slackware64-current\/slackware64\//g' fu
wget -i fu 
upgradepkg *.t?z
## Clean up
rm fu
I know someone with more experience writing bash scripts can do better, but it works.
 
Old 06-24-2019, 07:32 PM   #14
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 -current
Posts: 2,300

Rep: Reputation: 90
I use sbotools with -current with no problems, although some packages you are using might be the reason for having to use ponce (I don't really know). Pretty much everything I use is available via sbotools and so far has built without issue.
 
Old 06-25-2019, 03:19 AM   #15
cdek
Member
 
Registered: Jul 2016
Posts: 39

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by masonm View Post
I use sbotools with -current with no problems, although some packages you are using might be the reason for having to use ponce (I don't really know). Pretty much everything I use is available via sbotools and so far has built without issue.
If sbotools is configured to use current, then it also uses ponce, right? Or am I missing something?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Unable to subtract current date and future date in YYYY-MM-DD format archie7 Linux - Newbie 11 05-11-2018 03:29 AM
[SOLVED] [Slackware 64-current] Fresh installation with KDE5 stucks when open the "Leave" tab Francexi Slackware 1 09-14-2015 09:09 AM
Best way to keep Slackware 14.1 current upto date with the latest packages Quicken2k Slackware 10 11-10-2014 09:22 AM
[SOLVED] BASH: Keep original mod date of a file and 'date' it back to same file? SilversleevesX Programming 4 07-16-2010 11:12 AM
current date - yesterday's date newbie_adm Linux - Newbie 4 09-04-2006 03:56 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

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

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration