LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
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 03-07-2013, 10:24 AM   #1
stringchopper
LQ Newbie
 
Registered: Feb 2013
Posts: 22

Rep: Reputation: Disabled
Question confused by slackpkg upgrade-all and install-new


Hi everyone,

I've read a bit, but I'm still confused.

I just want regular updates (security, bug fixes, etc) to my system software and extra apps that come with Slackware 14.

Should I do this?:
Code:
slackpkg update
slackpkg upgrade patches
upgrade-all freaks me out, because (to me) it sounds like it will upgrade me to a new slackware version (15 when it's out, or current)

and install-new popped up a box with pre-chosen items that aren't even on my system - a bunch of KDE "crap" that I chose not to install when installing slackware. So, is there a reason for me to use install-new?

On my laptop, where I just now installed Slackware 14, I did
Code:
slackpkg update gpg
slackpkg update
slackpkg upgrade-all
even though I don't fully understand what's going on with upgrade-all.

I cancelled out of the "slackpkg install-new" when I saw the window with all the kde stuff, and a ton of other pre-selected items. Most of the how-to's that I've googled tell people to include it though.
 
Old 03-07-2013, 10:58 AM   #2
chess
Member
 
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 728

Rep: Reputation: 168Reputation: 168
From the slackpkg man page:
Code:
       upgrade-all
            This action upgrades every package installed on the system to  the
            version  in the official Slackware tree; this is the "good" way to
            upgrade the entire system.
            Remember to use the "install-new" action before you use  "upgrade-
            all."

       install-new
            This  action installs any new packages that are added to the offi-
            cial Slackware package set.  Run this if you  are  upgrading  your
            system to another Slackware version or if you are using -current.
            If  you  want  to  install all uninstalled Slackware packages onto
            your system, use the following command instead of the  install-new
            action:
      
                 # slackpkg install slackware.
So upgrade-all will upgrade any packages on your system to newer versions for your Slackware release, e.g. security patches and bug fixes. EDIT - see below discussion.

You might also find this helpful: http://docs.slackware.com/slackware:slackpkg

Last edited by chess; 03-07-2013 at 05:00 PM. Reason: add info re: blacklist
 
Old 03-07-2013, 11:09 AM   #3
Mike_M
Member
 
Registered: Mar 2011
Location: California
Distribution: Slackware
Posts: 116

Rep: Reputation: 50
In the file /etc/slackpkg/mirrors you specify a single mirror, and the URL points to the location of a single version on that mirror. Accordingly, upgrade-all will not upgrade your packages to those from a different version of Slackware.
 
Old 03-07-2013, 12:20 PM   #4
clem-bot
LQ Newbie
 
Registered: Mar 2013
Distribution: Slackware64 14.0
Posts: 3

Rep: Reputation: Disabled
Quote:
... install-new popped up a box with pre-chosen items that aren't even on my system - a bunch of KDE "crap" that I chose not to install when installing slackware.
Just because you chose not to install something, doesn't mean that it is crap.
 
Old 03-07-2013, 12:21 PM   #5
clem-bot
LQ Newbie
 
Registered: Mar 2013
Distribution: Slackware64 14.0
Posts: 3

Rep: Reputation: Disabled
Quote:
... install-new popped up a box with pre-chosen items that aren't even on my system - a bunch of KDE "crap" that I chose not to install when installing slackware.
Just because you chose not to install something, doesn't mean that it is crap.
 
Old 03-07-2013, 02:40 PM   #6
stringchopper
LQ Newbie
 
Registered: Feb 2013
Posts: 22

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by clem-bot View Post
Just because you chose not to install something, doesn't mean that it is crap.
well... no disrespect meant toward you or anyone else. That's just my personal opinion. I guess I was just surprised and shocked to see that I could've inadvertently installed those packages, after making the happy decision to have a "KDE-clean" install.

EDIT (off-topic):
I switched back to KDE on my main desktop and I have to say, I really do like it there.

Last edited by stringchopper; 03-09-2013 at 06:54 AM.
 
Old 03-07-2013, 03:25 PM   #7
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,190

Rep: Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024
@stringchopper: Slackware 14.0 was released on 2012-09-28 and since then no package whose name begins with "kde" was included in it.

So, either
(1) you are running Slackware-current, not Slackware 14.0
(2) You uncommented a wrong mirror in /etc/slackpkg/mirrors, i.e. one whose URL does not end in slackware-14.0/

Else it is impossible that you see anything kde related running "slackpkg install-new" as it would show as "added" in the Changelog more recently than the release date.

EDIT I was wrong: see following post from Alien Bob

Last edited by Didier Spaier; 03-07-2013 at 04:02 PM.
 
Old 03-07-2013, 03:54 PM   #8
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,238

Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
@stringchopper: Slackware 14.0 was released on 2012-09-28 and since then no package whose name begins with "kde" was included in it.

So, either
(1) you are running Slackware-current, not Slackware 14.0
(2) You uncommented a wrong mirror in /etc/slackpkg/mirrors, i.e. one whose URL does not end in slackware-14.0/

Else it is impossible that you see anything kde related running "slackpkg install-new" as it would show as "added" in the Changelog more recently than the release date.
Well... you have the concept wrong here.

Code:
$ grep Added. slackware-14.0/ChangeLog.txt | grep ^kde | wc -l
109
This means, if you enable a Slackware 14.0 repository in slackpkg and then run "slackpkg install-new" you will see all those 109 packages listed for installation. That is how slackpkg works. It scans the ChangeLog.txt of that release for all packages which have the string "Added" which means they were added during development of the release, and are therefore new in comparison with the previous release.

A "slackpkg install-new" does not mean "install all packages which are part of Slackware and which I have not yet installed" ! It means "install all packages which have been added between the previous and this Slackware release".

That is why you always accompany the command "slackpkg install-new" and "slackpkg upgrade-all",

Eric
 
Old 03-07-2013, 03:59 PM   #9
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,190

Rep: Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024
I stand corrected, thanks Eric.
 
Old 03-07-2013, 04:24 PM   #10
chess
Member
 
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 728

Rep: Reputation: 168Reputation: 168
Quote:
Originally Posted by Alien Bob View Post
A "slackpkg install-new" does not mean "install all packages which are part of Slackware and which I have not yet installed" ! It means "install all packages which have been added between the previous and this Slackware release".
But Eric isn't this only true when using slackpkg to upgrade from one release to another release? If one is using slackpkg to maintain an installed release (not upgrading to a new release) then doesn't install-new list packages that were not installed originally? I do not install kde so when I use slackpkg install-new on my 14.0 system it shows the kde packages, which I then blacklist so they don't keep showing up.

Edit: I mention this because the OP is just using slackpkg to maintain a system, not upgrade to another release.

Last edited by chess; 03-07-2013 at 04:31 PM.
 
Old 03-07-2013, 04:42 PM   #11
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,238

Rep: Reputation: Disabled
Quote:
Originally Posted by chess View Post
But Eric isn't this only true when using slackpkg to upgrade from one release to another release? If one is using slackpkg to maintain an installed release (not upgrading to a new release) then doesn't install-new list packages that were not installed originally? I do not install kde so when I use slackpkg install-new on my 14.0 system it shows the kde packages, which I then blacklist so they don't keep showing up.
Nope.
 
Old 03-07-2013, 04:51 PM   #12
chess
Member
 
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 728

Rep: Reputation: 168Reputation: 168
Huh. On my 14.0 system without kde or calligra packages installed, if I don't have kde* and calligra* listed in the blacklist file, slackpkg install-new will list them. If I do have kde* and calligra* listed in the blacklist file then they don't show up. *shrug*
 
Old 03-07-2013, 04:54 PM   #13
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,238

Rep: Reputation: Disabled
Quote:
Originally Posted by chess View Post
Huh. On my 14.0 system without kde or calligra packages installed, if I don't have kde* and calligra* listed in the blacklist file, slackpkg install-new will list them. If I do have kde* and calligra* listed in the blacklist file then they don't show up. *shrug*
That is just because those packages were new in Slackware 14.0. If you would upgrade to slackware-current and still not have anything of KDE installed, none of those packages will show up in "slackpkg install-new" anymore, because they were not added in to the release (-current) which you configured slacpkg for.

Eric
 
1 members found this post helpful.
Old 03-07-2013, 04:55 PM   #14
chess
Member
 
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 728

Rep: Reputation: 168Reputation: 168
Quote:
Originally Posted by Alien Bob View Post
That is just because those packages were new in Slackware 14.0. If you would upgrade to slackware-current and still not have anything of KDE installed, none of those packages will show up in "slackpkg install-new" anymore, because they were not added in to the release (-current) which you configured slacpkg for.

Eric
Got it, makes sense. Thanks!
 
  


Reply

Tags
slackpkg


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] slackpkg upgrade-all and install-new default behaviour altering? vharishankar Slackware 2 08-08-2012 02:21 AM
[SOLVED] Confused: My /etc/slackpkg/mirrors has 13.37, 13.1 & current - what is 13.37? Robert.Thompson Slackware 6 04-05-2011 10:21 AM
[SOLVED] After upgrade all using slackpkg upgrade, configuration is failed to read ethereal1m Linux - Newbie 3 04-28-2010 01:03 AM
slackpkg upgrade-all does not show an upgrade sycamorex Slackware 6 11-03-2009 05:29 AM
keep old or install new configuration files during slackpkg upgrade-all ? james2b Slackware 6 03-02-2009 10:51 AM


All times are GMT -5. The time now is 02:28 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration