LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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 05-22-2013, 02:32 PM   #1
fl0
Member
 
Registered: May 2010
Location: Germany
Distribution: Slackware
Posts: 103

Rep: Reputation: 34
Heads Up! Upgrading from 14.0 -> current with Networkmanager broken


Hi @all,

when upgrading from 14.0 -> current, networkmanager gets updated and refuses to start because of missing / to old libs which gets an update later, so the update process is broken.

You can prevent this by activating download befor installation in /etc/slackpkg/slackpkg.conf

Code:
DOWNLOAD_ALL=on
or you fix the connection manually and finish the update

PS: is their a way to control the installation order in slackpkg ?

regards fl0

Last edited by fl0; 05-22-2013 at 03:15 PM.
 
Old 05-22-2013, 08:46 PM   #2
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 1,748

Rep: Reputation: 159Reputation: 159
Quote:
Originally Posted by fl0 View Post
so the update process is broken.
There seem to be a lot more people running -current these days, and as a result there are more posts like this about the "upgrade process."

In times gone by, the developers would put a file called "CURRENT.WARNING" in the -current tree. They don't do it any more. Maybe they get better feedback this way... Anyhow, there was a copy online which I found and am pasting this from:

Quote:
Originally Posted by CURRENT.WARNING
Slackware-current is a snapshot of the active Slackware development tree.It is intended to give developers (and other Linux gurus) a chance to test out the latest packages for Slackware. The feedback we get will allow us to make the next stable release better than ever.
I don't think any of this has changed. -current is still a development tree. If you use it, then you should probably expect things to be broken from time to time.
 
1 members found this post helpful.
Old 05-22-2013, 09:08 PM   #3
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,447
Blog Entries: 14

Rep: Reputation: 592Reputation: 592Reputation: 592Reputation: 592Reputation: 592Reputation: 592
You should probably use AlienBOB's isobuilder script to create an ISO of the -current tree rather than use the upgrade process. I've used both, but honestly, the ISO works a lot better.
 
1 members found this post helpful.
Old 05-23-2013, 02:22 AM   #4
zakame
Member
 
Registered: Apr 2012
Distribution: Debian, Ubuntu, Slackware
Posts: 116

Rep: Reputation: 42
Hmm, isn't the update process all about doing what is told in UPGRADE.TXT? :P slackpkg is a convenience, but it doesn't replace the instructions in that file. In fact, in a default setup of slackpkg/blacklist, some stuff like aaa_elflibs won't get upgraded at all (unlike in UPGRADE.TXT's step 3, where it gets upgraded along with everyone else.)
 
Old 05-23-2013, 05:55 PM   #5
fl0
Member
 
Registered: May 2010
Location: Germany
Distribution: Slackware
Posts: 103

Original Poster
Rep: Reputation: 34
Hi,

i think my post was misinterpreted, i am aware that -current is development and can be broken at any time, i have also no problem with fixing the problem myself,
the intention is that "other" can prevent the problem.

regards fl0
 
1 members found this post helpful.
Old 05-24-2013, 03:05 PM   #6
fl0
Member
 
Registered: May 2010
Location: Germany
Distribution: Slackware
Posts: 103

Original Poster
Rep: Reputation: 34
Quote:
Fri May 24 04:18:18 UTC 2013
ap/slackpkg-2.82.0-noarch-9.tgz: Rebuilt.
Set DOWNLOAD_ALL=on in slackpkg.conf by default to avoid script failures
caused by programs (wget is an example) that may require library updates.
Without this option, a program might be needed again before the supporting
libraries have been upgraded.
problem solved, thx @ Pat
 
  


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
[SOLVED] NetworkManager broken in current yenn Slackware 16 07-03-2013 03:22 AM
[SOLVED] Networkmanager-vpnc-0.9.4 fails to compile under -current fl0 Slackware 7 04-05-2013 03:38 PM
[SOLVED] -current NetworkManager in non-KDE sessions zakame Slackware 8 07-24-2012 08:24 PM
[SOLVED] Abiword broken after upgrading 13.0 to 13.1 Josh000 Slackware 5 02-27-2011 12:30 PM
LXer: I easily repair broken NetworkManager in Debian Lenny LXer Syndicated Linux News 0 07-31-2009 04:41 PM


All times are GMT -5. The time now is 02:49 PM.

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