LinuxQuestions.org
Visit Jeremy's Blog.
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 08-13-2012, 12:26 PM   #1
foobarz
Member
 
Registered: Aug 2010
Distribution: slackware64-current
Posts: 48

Rep: Reputation: 10
slackpkg upgrade-all is not working in slackware64-current


I have a local mirror of slackware64-current. After syncing it to the lastest changes and running slackpkg update, I have tried to use slackpkg upgrade-all. I get the "upgrade" dialog with a package entry at the top that is "[*] ." like a package called ".". Following that "." package, I get either no other packages, or a random list of packages to upgrade. If I cancel and run slackpkg upgrade-all again, then I get different lists of packages almost everytime, but package "." is always there at the top.

I have manually upgraded pkgtools and slackpkg to the versions in -current to make sure they are the most recent, but this problem is what I get.

slackpkg installed is slackpkg-2.82.0-noarch-6
pkgtools installed is pkgtools-14.0-noarch-1
gawk-3.1.8-x86_64-1

I even tried to upgrade to gawk-4.0.1, but it made no difference, so I upgraded back to slackware's 3.1.8.

Can anyone help?
 
Old 08-13-2012, 02:55 PM   #2
foobarz
Member
 
Registered: Aug 2010
Distribution: slackware64-current
Posts: 48

Original Poster
Rep: Reputation: 10
This problem was caused by grep-2.13; downgrading to grep-2.12 solved this problem on ZFSonLinux as rootfs.

grep-2.13 has a bug in certain situations involving sparse files. It can affect ZFSonLinux, NFS, BtrFS and filesystems that make usage of sparse files in certain ways.

When the bug happens, slackpkg fails to list packages properly, compiling kernel modules will fail, and other malfunctions can happen in scripts that call grep.

I've e-mailed Pat about this, so have to wait to see what happens. According to some mail list threads on grep development, they want to release a new grep version very soon to fix this bug; it looks like the grep development version has the bug fix already.

Last edited by foobarz; 08-15-2012 at 02:25 AM. Reason: solved: problem was grep-2.13, downgrade or upgrade
 
  


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
[SOLVED] Can't get slackpkg to upgrade to slackware64 NightSky Slackware - Installation 4 06-09-2010 05:38 PM
Slackware64 -current (20-04-2010) problem with slackpkg mlpa Slackware 5 04-22-2010 02:55 AM
[SOLVED] slackpkg insists on NOT upgrading me to slackware64-current. What am I missing? GrapefruiTgirl Slackware 5 03-04-2010 02:01 PM
Slackware64-Current / slackpkg slackass Slackware 31 06-06-2009 11:51 PM
Using slackpkg to Upgrade to Slackware-Current x94qvi Slackware 8 10-20-2007 08:53 PM


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