[SOLVED] Checkout the Current Changelog

AlleyTrotter · 04-18-2018, 10:09 PM

Like WOW man!

Thu Apr 19 01:04:06 UTC 2018

Guess it's time to mark this one SOLVED
never got this responses/reads before

Daedra · 04-18-2018, 10:10 PM

That is one epic changelog lol!

frushiyama · 04-18-2018, 10:14 PM

I am using 14.2 right now, never felt so tempted to switch to -current

dugan · 04-18-2018, 10:30 PM

Oh. My. God.

Paulo2 · 04-18-2018, 10:32 PM

Yes, I was just creating a new thread, but I will post here if you excuse me

I read the ChangeLog.txt, but I didn't understand the steps to run 'slackpkg update|install-new|upgrade-all' routine this time

Should I uninstall all third party packages,
then run 'rm /{,usr/}lib{,64}/*.la',
and then upgrade with slackpkg?
I have packages from ponce's SBo-current, AlienBob, and others,
making a list of all packages and reinstalling after the mass upgrade isn't a problem.

Or

I run 'slackpkg update|install-new|upgrade-all' and then
run 'rm /{,usr/}lib{,64}/*.la' without uninstalling third party packages.

Another question, in this upgrade, we have to upgrade first glibc-solibs (as written in UPGRADE.TXT)?

cwizardone · 04-18-2018, 10:35 PM

I think I'll sit this one out (until the dust settles).

mralk3 · 04-18-2018, 10:39 PM

Quote:

Originally Posted by cwizardone

I think I'll sit this one out (until the dusk settles).

Same here!

Paulo2 · 04-18-2018, 10:45 PM

My notebook isn't a production machine, it can be a guinea pig

hitest · 04-18-2018, 10:57 PM

One -current box upgraded so far. All is well.

On to the next one.

ponce · 04-18-2018, 11:02 PM

Quote:

Originally Posted by Paulo2

Yes, I was just creating a new thread, but I will post here if you excuse me

I read the ChangeLog.txt, but I didn't understand the steps to run 'slackpkg update|install-new|upgrade-all' routine this time

Should I uninstall all third party packages,
then run 'rm /{,usr/}lib{,64}/*.la',
and then upgrade with slackpkg?
I have packages from ponce's SBo-current, AlienBob, and others,
making a list of all packages and reinstalling after the mass upgrade isn't a problem.

Or

I run 'slackpkg update|install-new|upgrade-all' and then
run 'rm /{,usr/}lib{,64}/*.la' without uninstalling third party packages.

when you will install these updates a lot of your third party packages won't work anymore.
IMHO, the best course of action would be to do, *BEFORE* installing the updates, a clean install of slackware current on a virtual machine and rebuild *ALL* of the third party packages that you use there.
then you can follow the first road that you describe above (you can alternatively move the *.la files out of the way instead of deleting them, so you have a reference of what was there), upgrading/reinstalling all of the third party packages at the end using the just-built ones.

Quote:

Another question, in this upgrade, we have to upgrade first glibc-solibs (as written in UPGRADE.TXT)?

if you were following current's updates tightly (you had the latest before these installed) it shouldn't be necessary in this case, but that's not a bad idea in general, if you use slackpkg it should take care of installing it first.

orbea · 04-18-2018, 11:12 PM

I just want to point out that brace expansions are a bash feature.

Code:

#!/bin/sh
rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la

Code:

$ checkbashisms test.sh 
possible bashism in test.sh line 2 (brace expansion):
rm -f $PKG/{,usr/}lib${LIBDIRSUFFIX}/*.la

nobodino · 04-18-2018, 11:27 PM

I would be very interested to know how they managed to do this mass rebuild. I'm really impressed!
To paraphraze Martin Luther King, 'I made a dream, of mass rebuild...'
and they did it finally!!

1337_powerslacker · 04-19-2018, 12:50 AM

I am upgrading my NVMe setup, and I was thinking about re-installing anyway, so this gives me another excuse to do it.
Like others here, I am holding off on the update, but just until my parts get here, and then install from scratch. That way, it's a clean install, and I don't have to worry that some package upgrade is going to bork my system.

volkerdi · 04-19-2018, 01:40 AM

Quote:

Originally Posted by Paulo2

I run 'slackpkg update|install-new|upgrade-all' and then
run 'rm /{,usr/}lib{,64}/*.la' without uninstalling third party packages.

Yes. Third party package should continue to run, since we still support the dual C++ ABI.

Quote:

Another question, in this upgrade, we have to upgrade first glibc-solibs (as written in UPGRADE.TXT)?

Shouldn't matter either way. I didn't try it, but I think slackpkg will do just fine.

Really, the most disruptive parts of this batch (besides the .la files) are the soname bumps in poppler and boost.

If you rebuild things later, they'll probably still build .la files, but at least they'll be correct.

RadicalDreamer · 04-19-2018, 01:40 AM

I'm gonna try it. I'm curious.