LinuxQuestions.org
Help answer threads with 0 replies.
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 01-06-2018, 05:38 PM   #16
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,303

Rep: Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808

How's this, Darth?

Code:
commit 8c6d8b9947d58bd92bd7dd662807b0eb528c7563
Author: Robby Workman <rworkman@slackware.com>
Date:   Sat Jan 6 17:33:02 2018 -0600

    post-functions.sh: check for /etc/lilo.conf too for lilo offer
    
    Existence of /etc/lilo.conf coupled with executable /sbin/lilo
    probably indicates lilo usage on the system, so that seems like
    a reasonable compromise for everyone fussing about slackpkg's
    offer to run /sbin/lilo for them after kernel upgrades even
    though they use grub or whatever else.
 
1 members found this post helpful.
Old 01-06-2018, 05:57 PM   #17
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,436

Rep: Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979
Brilliant, thank you!

I would do nitpicking that grepping in the /etc/lilo.conf can result in signs of an initrd usage, then manually intervention of the user is a must.

Better no LILO auto-updates when the initrds are used, right?

I say that, because I observed that the usual rookie is bitten by updating LILO in a new kernel install, while s/he does NOT update the (required) initrd too. Resulting in a failed boot, usually.

Because s/he trust the slackpkg doing that job.

Last edited by Darth Vader; 01-08-2018 at 09:38 AM.
 
Old 01-07-2018, 12:31 AM   #18
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,303

Rep: Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808
Code:
commit caf6a1ab9635b01908dffdfd4e55d52d186be447 (HEAD -> master, origin/master, github/master)
Author: Robby Workman <rworkman@slackware.com>
Date:   Sat Jan 6 23:57:19 2018 -0600

    post-functions.sh: Don't offer to run lilo if initrd is in lilo.conf
 
2 members found this post helpful.
Old 03-28-2018, 11:04 AM   #19
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu
Posts: 267

Original Poster
Rep: Reputation: 36
looknew() not yet $ROOT aware

Using rlworkman's slackpkg 2.82.3beta5 (https://github.com/rworkman/slackpkg dated Jan 7, 2018) I noticed that /usr/libexec/slackpkg/functions.d/post-functions.sh:looknew() is not yet $ROOT aware: it reports a .new on the "host" instead of on the "client".
Possibly the "find" should be amended.

Last edited by burdi01; 03-28-2018 at 11:12 AM.
 
Old 03-29-2018, 03:48 AM   #20
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu
Posts: 267

Original Poster
Rep: Reputation: 36
looknew() not yet $ROOT aware

Indeed amending looknew()'s find resolved the problem:
Code:
--- /usr/libexec/slackpkg/functions.d/post-functions.sh.orig	2018-01-07 07:12:05.000000000 +0100
+++ /usr/libexec/slackpkg/functions.d/post-functions.sh	2018-03-29 10:54:45.265569903 +0200
@@ -134,7 +134,7 @@
 	fi
 
 	echo -e "\nSearching for NEW configuration files"
-	FILES=$(find /etc /var/yp /usr/share/vim -name "*.new" ${ONLY_NEW_DOTNEW} \
+	FILES=$(find $ROOT/etc /var/yp /usr/share/vim -name "*.new" ${ONLY_NEW_DOTNEW} \
 		-not -name "rc.inet1.conf.new" \
 		-not -name "group.new" \
 		-not -name "passwd.new" \
Note that the above patch resolves *my* usecase only -- I am not sure what the /var/yp and /usr/share/vim entries are meant for here, so I did not touch them.
I assume lookkernel() should also be amended, but as I do not use slackpkg for my kernels I am not in a position to test this.

BTW: Will these amendments be included in the "official" Slackware and, if so, when?
Regards, Dick

Last edited by burdi01; 03-29-2018 at 05:38 AM.
 
Old 03-29-2018, 02:51 PM   #21
drumz
Member
 
Registered: Apr 2005
Location: Scottsdale, AZ, USA
Distribution: Slackware
Posts: 206

Rep: Reputation: 52
Quote:
Originally Posted by burdi01 View Post
I am not sure what the /var/yp and /usr/share/vim entries are meant for here, so I did not touch them.
/usr/share/vim is there becuase vim installs /usr/share/vim/vimrc.new, and /var/yp is there because yptools installs Makefile.new, nicknames.new, and securenets.new to /var/yp:

Code:
# grep var/yp /var/log/packages/*
/var/log/packages/yptools-2.14-x86_64-7:var/yp/
/var/log/packages/yptools-2.14-x86_64-7:var/yp/Makefile.new
/var/log/packages/yptools-2.14-x86_64-7:var/yp/nicknames.new
/var/log/packages/yptools-2.14-x86_64-7:var/yp/securenets.new

# grep vimrc /var/log/packages/*
/var/log/packages/python-2.7.14-x86_64-1_slack14.2:usr/doc/python-2.7.14/Misc/Vim/vimrc
/var/log/packages/vim-8.0.1519-x86_64-1:usr/share/vim/vim80/gvimrc_example.vim
/var/log/packages/vim-8.0.1519-x86_64-1:usr/share/vim/vim80/vimrc_example.vim
/var/log/packages/vim-8.0.1519-x86_64-1:usr/share/vim/vimrc.new
But it doesn't handle all the "new" files. I believe these are all of them not in /etc:

Code:
# grep config /var/log/scripts/* | grep new | grep -v etc
/var/log/scripts/MPlayer-1.2_20160125-x86_64-3:# Prepare the new configuration file
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/criblog.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/saillog.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/cfscores.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/atc_score.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/phantasia/gold.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/phantasia/mess.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/phantasia/motd.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/phantasia/void.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/phantasia/monsters.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/phantasia/lastdead.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/phantasia/characs.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/phantasia/scoreboard.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/battlestar.log.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/robots_roll.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/snakerawscores.new
/var/log/scripts/bsd-games-2.13-x86_64-12:config var/lib/bsdgames/snake.log.new
/var/log/scripts/dhcp-4.4.1-x86_64-1_slack14.2:config var/state/dhcp/dhcpd.leases.new
/var/log/scripts/dhcp-4.4.1-x86_64-1_slack14.2:config var/state/dhcp/dhcpd6.leases.new
/var/log/scripts/dhcp-4.4.1-x86_64-1_slack14.2:config var/state/dhcp/dhclient.leases.new
/var/log/scripts/dhcp-4.4.1-x86_64-1_slack14.2:config var/state/dhcp/dhclient6.leases.new
/var/log/scripts/eclipse-java-4.7.3-x86_64-1_SBo:config opt/eclipse-java/configuration/config.ini.new
/var/log/scripts/eclipse-java-4.7.3-x86_64-1_SBo:config opt/eclipse-java/eclipse.ini.new
/var/log/scripts/ghostscript-9.19-x86_64-2:config usr/share/ghostscript/9.19/Resource/Init/cidfmap.new
/var/log/scripts/glib2-2.46.2-x86_64-3_slack14.2:# Prepare the new configuration files
/var/log/scripts/httpd-2.4.29-x86_64-1_slack14.2:config var/www/htdocs/index.html.new
/var/log/scripts/imagemagick-6.9.4_9-x86_64-1:# Process all .new config files:
/var/log/scripts/libcgroup-0.41-x86_64-2_slack14.2:# If there are already installed config files, get rid of the .new ones.
/var/log/scripts/man-1.6g-x86_64-3:# Install new config file if none exists:
/var/log/scripts/nfs-utils-1.3.3-x86_64-2:config var/lib/nfs/etab.new
/var/log/scripts/nfs-utils-1.3.3-x86_64-2:config var/lib/nfs/rmtab.new
/var/log/scripts/nfs-utils-1.3.3-x86_64-2:config var/lib/nfs/state.new
/var/log/scripts/nfs-utils-1.3.3-x86_64-2:config var/lib/nfs/xtab.new
/var/log/scripts/perl-5.22.2-x86_64-1:config usr/lib64/perl5/perllocal.pod.new
/var/log/scripts/scim-1.4.17-x86_64-1_slack14.2:# Prepare the new configuration files
/var/log/scripts/shadow-4.2.1-x86_64-1:config var/log/faillog.new
/var/log/scripts/slrn-1.0.2-x86_64-1:config var/spool/slrnpull/slrnpull.conf.new
/var/log/scripts/sysklogd-1.5.1-x86_64-2:config var/log/cron.new
/var/log/scripts/sysklogd-1.5.1-x86_64-2:config var/log/debug.new
/var/log/scripts/sysklogd-1.5.1-x86_64-2:config var/log/maillog.new
/var/log/scripts/sysklogd-1.5.1-x86_64-2:config var/log/messages.new
/var/log/scripts/sysklogd-1.5.1-x86_64-2:config var/log/secure.new
/var/log/scripts/sysklogd-1.5.1-x86_64-2:config var/log/spooler.new
/var/log/scripts/sysklogd-1.5.1-x86_64-2:config var/log/syslog.new
/var/log/scripts/uucp-1.07-x86_64-1:config var/log/uucp/DEBUG.new
/var/log/scripts/uucp-1.07-x86_64-1:config var/log/uucp/Debug.new
/var/log/scripts/uucp-1.07-x86_64-1:config var/log/uucp/LOGFILE.new
/var/log/scripts/uucp-1.07-x86_64-1:config var/log/uucp/Log.new
/var/log/scripts/uucp-1.07-x86_64-1:config var/log/uucp/SYSLOG.new
/var/log/scripts/uucp-1.07-x86_64-1:config var/log/uucp/Stats.new
/var/log/scripts/vim-8.0.1519-x86_64-1:config usr/share/vim/vimrc.new
/var/log/scripts/yptools-2.14-x86_64-7:config var/yp/nicknames.new
/var/log/scripts/yptools-2.14-x86_64-7:config var/yp/Makefile.new
/var/log/scripts/yptools-2.14-x86_64-7:config var/yp/securenets.new
 
Old 04-03-2018, 07:12 PM   #22
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,303

Rep: Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808
The rest of those shouldn't be "handled" in this context - they are "handled" otherwise :-)
 
1 members found this post helpful.
Old 04-03-2018, 07:24 PM   #23
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,303

Rep: Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808
Re including this in Slackware upstream, that is the goal, but I'm trying to be very conservative (for what I hope are obvious reasons).
Proposing large changes to slackpkg is going to scare me away, if only because proposing moderate changes to slackpkg will scare volkerdi away ;-)
 
1 members found this post helpful.
Old 04-03-2018, 08:30 PM   #24
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,303

Rep: Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808
Please go test 2.83.0beta1 and report back.
https://slackpkg.org/
 
Old 04-03-2018, 10:08 PM   #25
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, Debian, CentOS, FreeBSD
Posts: 1,090

Rep: Reputation: 454Reputation: 454Reputation: 454Reputation: 454Reputation: 454
I am running slackpkg-2.83.0beta1-noarch-1_rlw and slackpkg+-1.7.0-noarch-5mt on latest -current. I am using a mirror on my LAN that was working with 2.82.2. I backed up my /etc/slackpkg and did a removepkg slackpkg and upgradepkg --install-new slackpkg-2.83.0beta1-noarch-1_rlw.txz. I left /var/lib/slackpkg as is when upgrading.

The following looks good:
Code:
slackpkg update gpg
slackpkg update
slackpkg install-new
BUT, I am getting the following error with upgrade-all:

Code:
# slackpkg upgrade-all

Checking local integrity... DONE
Looking for packages to upgrade. Please wait... awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
awk: /usr/libexec/slackpkg/pkglist.awk:6: (FILENAME=- FNR=1) fatal: attempt to access field -2
DONE

No packages match the pattern for upgrade. Try:

	/usr/sbin/slackpkg install|reinstall
 
Old 04-03-2018, 10:17 PM   #26
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,303

Rep: Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808
I'm not seeing it here, but I guess that's related to this commit:
Code:
commit 47a185d6c6a7458ee994e3740adb2ecbd0103db6
Author: Robby Workman <rworkman@slackware.com>
Date:   Sat Dec 30 01:06:40 2017 -0600

    pkglist.awk: Handle the (hopefully rare) case of $ROOT usage

diff --git a/files/pkglist.awk b/files/pkglist.awk
index 5a0c18e..9b4b1bc 100644
--- a/files/pkglist.awk
+++ b/files/pkglist.awk
@@ -3,7 +3,7 @@
                fs=FS
                FS="/" ; OFS="/"
                $0=INPUT
-               if ( $2 != "var" ) {
+               if ( $(NF-3) != "var" ) {
                        DIR=$2
                        FULLPACK=$NF
                } else {
 
Old 04-03-2018, 10:19 PM   #27
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, Debian, CentOS, FreeBSD
Posts: 1,090

Rep: Reputation: 454Reputation: 454Reputation: 454Reputation: 454Reputation: 454
I removed slackpkg+ and I am not getting that error now.

EDIT:

I ran an upgrade on the Wed Apr 4 00:16:40 UTC 2018 updates in -current and everything looks good so far. It is an issue between slackpkg and slackpkg+.

Last edited by mralk3; 04-03-2018 at 10:33 PM.
 
1 members found this post helpful.
Old 04-03-2018, 10:27 PM   #28
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,303

Rep: Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808
OHHH. I misread your first report and thought you had replaced slackpkg+ with slackpkg - otherwise, I would have closed the bug report as invalid ;-)
 
Old 04-03-2018, 10:36 PM   #29
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, Debian, CentOS, FreeBSD
Posts: 1,090

Rep: Reputation: 454Reputation: 454Reputation: 454Reputation: 454Reputation: 454
Quote:
Originally Posted by rworkman View Post
OHHH. I misread your first report and thought you had replaced slackpkg+ with slackpkg - otherwise, I would have closed the bug report as invalid ;-)
Yeah I will run without slackpkg+ for a few days while running the slackpkg 2.83.0beta1 and see if I have any other issues. It looks rock solid so far. I will have to try and break it in one of my really outdated -current virtual machines.
 
1 members found this post helpful.
Old 04-03-2018, 10:51 PM   #30
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,303

Rep: Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808
Quote:
Originally Posted by mralk3 View Post
Yeah I will run without slackpkg+ for a few days while running the slackpkg 2.83.0beta1 and see if I have any other issues. It looks rock solid so far. I will have to try and break it in one of my really outdated -current virtual machines.
Yes, please do.
 
  


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
[SOLVED] Slackware ARM 14.1 slackpkg file at the root of the package Linux.tar.gz Slackware - ARM 3 10-04-2016 06:21 AM
BUG slackpkg upgrade does not work with $ROOT zerouno Slackware 3 01-15-2016 05:29 PM
[SOLVED] Slackpkg, Slackpkg Plus, Slackware 14.1 x86_64 install.log delay or slow to write bamunds Slackware 7 04-22-2014 11:12 AM
[SOLVED] slackpkg creates /.gnupg (in the root of the file system) Woodsman Slackware 3 04-07-2011 06:18 PM
Making Apache Aware of a WebSite sefarlow Linux - Newbie 1 04-18-2009 07:20 AM

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

All times are GMT -5. The time now is 10:23 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration