LinuxQuestions.org
Visit the LQ Articles and Editorials section
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
 
LinkBack Search this Thread
Old 12-12-2008, 01:06 PM   #1
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Rep: Reputation: 70
Slackware 12.1/12.2 pine/alpine users pay attention!


I noticed when I upgraded my 12.1 install to 12.2 that pine has /etc/pine.conf while alpine has the now typical /etc/pine.conf.new.

The unwary admin might accidentally have their pine.conf file deleted if they remove obolete packages after upgrading as per the UPGRADE.TXT.

Of course everyone is backing up their system before upgrading, right?
 
Old 12-12-2008, 03:04 PM   #2
niels.horn
Senior Member
 
Registered: Mar 2007
Location: Rio de Janeiro - Brazil
Distribution: Slackware64-current
Posts: 1,004

Rep: Reputation: 87
How did you do the upgrade?

The .new files are normally the result of upgrades and need to be checked before substituting the original .conf files.
The slackpkg tool (now part of the base install of Slackware 12.2) automatically checks for .new files after upgrading and gives you the option to check the differences, overwrite the original file (renaming it to .orig), delete the .new file or keep both to check later.
 
Old 12-12-2008, 06:37 PM   #3
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.0
Posts: 2,231

Rep: Reputation: 573Reputation: 573Reputation: 573Reputation: 573Reputation: 573Reputation: 573
Quote:
Originally Posted by niels.horn View Post
How did you do the upgrade?

The .new files are normally the result of upgrades and need to be checked before substituting the original .conf files.
The slackpkg tool (now part of the base install of Slackware 12.2) automatically checks for .new files after upgrading and gives you the option to check the differences, overwrite the original file (renaming it to .orig), delete the .new file or keep both to check later.
True as that may be, I see shadowsnipes' point here. From CHANGES_AND_HINTS.TXT:
Code:
*** PACKAGE REMOVALS SINCE 12.1 ***

d/bin86: Removed. Replaced by d/dev86.
n/pine: Removed. Replaced by n/alpine.
extra/parted: Moved to l/ series.
extra/slackpkg: Moved to ap/ series.
The pine package has not been upgraded -- instead it has been replaced by alpine. Therefore, you are supposed to install alpine and then remove pine (it is NOT an upgrade). Since the .conf file will differ between pine and alpine, the .conf.new file will not overwrite the existing .conf file and will remain as .conf.new. Removing the pine package will remove the .conf file with it. The old pine package does not use the .conf.new format and just has the .conf file in the actual package. removepkg removes all files from the package that don't conflict with any other packages. Since the .conf.new file does NOT conflict, the old .conf file WILL be removed. Even worse, I think that if you merge the .config files before removing pine, it may remove the new merged .config file with it...scary stuff. Of course, backups are always good.

Thanks for this tip shadowsnipes.
 
Old 12-12-2008, 07:09 PM   #4
niels.horn
Senior Member
 
Registered: Mar 2007
Location: Rio de Janeiro - Brazil
Distribution: Slackware64-current
Posts: 1,004

Rep: Reputation: 87
OK, it is not an upgrade, but alpine is the evolution of pine and uses pine.conf as its configuration file.

I followed the -current branch and don't remember having problems with the change from pine to alpine (which I do use) while upgrading with slackpkg in August.
Slackpkg probably found the .new file (it uses 'find') and I probably used the 'diff' option of slackpkg to check the differences.

Nothing 'scary' happened here
 
Old 12-12-2008, 07:10 PM   #5
niels.horn
Senior Member
 
Registered: Mar 2007
Location: Rio de Janeiro - Brazil
Distribution: Slackware64-current
Posts: 1,004

Rep: Reputation: 87
OK, it is not an upgrade, but alpine is the evolution of pine and uses pine.conf as its configuration file.

I followed the -current branch and don't remember having problems with the change from pine to alpine (which I do use) while upgrading with slackpkg in August.
Slackpkg probably found the .new file (it uses 'find') and I probably used the 'diff' option of slackpkg to check the differences.

Nothing 'scary' happened here
 
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Alpine (a.k.a pine, pico) wants a lot of dependencies Seregwethrin Linux - Newbie 4 02-21-2008 04:11 PM
Attention SATA users kaz2100 Linux - Kernel 2 05-11-2007 08:15 PM
Pay It Forward. Attention: EVERYONE!!!!! Amykins LinuxQuestions.org Member Intro 2 12-31-2006 05:36 AM
Attention PCLinuxOS Users. jmiahman Linux - News 3 12-29-2006 05:52 AM


All times are GMT -5. The time now is 12:04 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