LinuxQuestions.org
Help answer threads with 0 replies.
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 07-14-2012, 05:28 AM   #16
xslc
Member
 
Registered: Jan 2012
Location: korea
Distribution: slackware64
Posts: 32

Rep: Reputation: Disabled

wow ... time to sync :-)
 
Old 07-14-2012, 05:44 AM   #17
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,661

Original Poster
Rep: Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784
Quote:
Originally Posted by markush View Post
Hi,

my systems (slackware64-current) are running now after the massive upgrade. It seems that one has to do
Code:
slackpg install-new
at first. Also be sure that you configure for DOWNLOAD_ALL=on in /etc/slackpkg/slackpkg.conf

Problem is that gnutls, p11 and nettle have to be upgraded/installed in order to get the upgraded version of wget running. On my server where DOWNLOAD_ALL=on is configured the "slackpkg upgrade-all" went well, but since wget was broken I could not run "slackpkg install-new".

I had to rebuild google-chrome.

USB was no longer working until I rebooted the system.

Markus
slackpkg install-new is always recommended to be executed before upgrade-all as new packages may be introduced
even if the order is correct, we still need to download wget manually first because it will install like the following:
- nettle (install-new)
- p11 (install-new)
- gnutls (upgrade-all) <- wget is now broken due to changes in gnutls
- wget (upgradepkg manually)

about USB, i didn't test before reboot, so i didn't aware of it
 
2 members found this post helpful.
Old 07-14-2012, 05:44 AM   #18
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,967

Rep: Reputation: 1545Reputation: 1545Reputation: 1545Reputation: 1545Reputation: 1545Reputation: 1545Reputation: 1545Reputation: 1545Reputation: 1545Reputation: 1545Reputation: 1545
Updates! Always like days like this.
 
Old 07-14-2012, 05:53 AM   #19
solarfields
Senior Member
 
Registered: Feb 2006
Location: slackalaxy.com
Distribution: Slackware, CRUX
Posts: 1,449

Rep: Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997
Quote:
Updates! Always like days like this.
yes
that's a good reason to buy beer
 
Old 07-14-2012, 06:24 AM   #20
BroX
Member
 
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current, SlackwareARM-15.0
Posts: 833

Rep: Reputation: 90
oh my, the dilemma... get some work done this weekend, or upgrade with the risk to break stuff and spend the rest of the day fixing things while having a beer

Now syncing...

Thanks Slack team!
 
Old 07-14-2012, 06:46 AM   #21
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,298
Blog Entries: 61

Rep: Reputation: Disabled
I installed -current in VBox on wednesday, thought it was about time I had another go at it. And then this happens.
Might need something considerably stronger than beer...
 
Old 07-14-2012, 08:15 AM   #22
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,844

Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
Thanks to willysr and markush - I had a very uneventful upgrade. I do have 3 dead links to delete, but I'm gonna be sure before I delete them. For the moment, everything seems just fine! That said, I am only about 4 minutes running..... hehehe!
 
Old 07-14-2012, 08:27 AM   #23
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,844

Rep: Reputation: 452Reputation: 452Reputation: 452Reputation: 452Reputation: 452
I get the feeling I am about to screw up.

Code:
ldconfig: /usr/lib64/libnssutil3.so is not a symbolic link

ldconfig: /usr/lib64/libnspr4.so is not a symbolic link

ldconfig: /usr/lib64/libplc4.so is not a symbolic link
These are not dead links, and they are also present in /usr/lib64/seamonkey-2.10.1
Something didn't go right, but it does not seem to be a problem yet. Got more lookin' to do.
 
Old 07-14-2012, 08:43 AM   #24
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Here another question regarding p11-kit for slackware-current 32bit.

It is in the changelogs but on both mirrors I use (for my slackware-32bit laptop) I cannot seem to find the package ftp://ftp.gwdg.de/pub/linux/slackwar...t/slackware/n/ and ftp://sunsite.informatik.rwth-aachen...t/slackware/n/. Maybe I am confused here, but I built p11-kit with the slackbuilscript from source and installed it, but when I ran "slackpkg clean-system" it wanted to remove p11-kit. p11-kit is necessary for wget to run.

For my slackware64 computers the package was no problem.

Markus

Last edited by markush; 07-14-2012 at 08:44 AM.
 
Old 07-14-2012, 08:50 AM   #25
BroX
Member
 
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current, SlackwareARM-15.0
Posts: 833

Rep: Reputation: 90
clementine segfaults


Code:
$ clementine --verbose
Segmentation fault
Recompiling didn't produce any errors, and all libraries are found. Tried moving the config and rc files in ~/ away, but alas.

Amarok plays fine though.

Does anyone know how to get more debug info? The segfault message is all I get.

edit: maybe I should add that this is after today's update

Last edited by BroX; 07-14-2012 at 08:58 AM.
 
Old 07-14-2012, 09:00 AM   #26
helo
LQ Newbie
 
Registered: May 2007
Distribution: slackware
Posts: 18

Rep: Reputation: 2
Had a problem with the text consoles on this upgrade.

agetty would not start on boot.

Turns out agetty does not like the new --noclear option in the /etc/inittab. Going back to my inittab.old fixed the problem.

--noclear is an option in mingetty, I wonder if upstream has gone and changed things without checking.
 
Old 07-14-2012, 09:18 AM   #27
Bertman123
Member
 
Registered: Jun 2010
Distribution: Slackware Current 64 bit KDE 5
Posts: 380

Rep: Reputation: 77
If I were to do upgrade-all before install-new how would I then fix my system? Seems like I broke something...
 
Old 07-14-2012, 09:28 AM   #28
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Quote:
Originally Posted by Bertman123 View Post
If I were to do upgrade-all before install-new how would I then fix my system? Seems like I broke something...
You've probably broken wget. wget needs the following packages to be installed/upgraded before wget is upgraded: p11-kit, nettle and gnutls!

You can download this packages from the mirror and install with installpkg or upgradepkg respectively.

Markus

Last edited by markush; 07-14-2012 at 09:28 AM. Reason: made it bold
 
Old 07-14-2012, 09:33 AM   #29
Bertman123
Member
 
Registered: Jun 2010
Distribution: Slackware Current 64 bit KDE 5
Posts: 380

Rep: Reputation: 77
Quote:
Originally Posted by markush View Post
You've probably broken wget. wget needs the following packages to be installed/upgraded before wget is upgraded: p11-kit, nettle and gnutls!

You can download this packages from the mirror and install with installpkg or upgradepkg respectively.

Markus
Which section of the mirror would I find the package in? I've been trying to find it and haven't located it yet. Thanks for your help. It is appreciated.
 
Old 07-14-2012, 09:47 AM   #30
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,979

Rep: Reputation: Disabled
Well, if you're running current-32bit, the p11-kit packages is missing, you'll find it in sources/n/ the others are located in the n series.
If you need p11-kit, you need the sourcpackage and the slackbuildscript, both in the same directory, then make the slackbuildscript executable and run it, you'll find the package in /tmp (this is only necessary for 32bit).

Markus
 
2 members found this post helpful.
  


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



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Microsoft forms open source subsidiary on Friday the 13th LXer Syndicated Linux News 0 04-13-2012 06:50 PM
LXer: Linux Gets Gooey on Friday the 13th LXer Syndicated Linux News 0 02-13-2009 10:10 PM
LXer: One of those magic times: On Friday the 13th! LXer Syndicated Linux News 1 02-07-2009 09:43 AM
LQ Security Report - February 13th 2005 Capt_Caveman Linux - Security 4 02-13-2005 09:51 PM
LQ security report - Feb 13th 2004 unSpawn Linux - Security 5 02-13-2004 11:36 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

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

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration