LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Heads Up! Upgrading from 14.0 -> current with Networkmanager broken (http://www.linuxquestions.org/questions/slackware-14/heads-up-upgrading-from-14-0-current-with-networkmanager-broken-4175463048/)

fl0 05-22-2013 02:32 PM

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

rkelsen 05-22-2013 08:46 PM

Quote:

Originally Posted by fl0 (Post 4956739)
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.

ReaperX7 05-22-2013 09:08 PM

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.

zakame 05-23-2013 02:22 AM

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.)

fl0 05-23-2013 05:55 PM

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

fl0 05-24-2013 03:05 PM

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


All times are GMT -5. The time now is 12:41 AM.