LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
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 03-04-2010, 11:42 AM   #1
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Question slackpkg insists on NOT upgrading me to slackware64-current. What am I missing?


Many of you probably know, I've been using Slackware, and slackpkg, for about 3+ years now. I don't recall having this particular problem before, and I remain stumped as to why it is so. I've been poking at this problem for several days now, and am still missing what is probably a small stupid thing causing me this grief, and nobody else seems to have had this problem: I can't seem to upgrade to -current

History:

I went from Slackware-11.0 to Slackware64-current back before 13.0-64 was officially released. I initially did this by using Robby's rsync-mirror script to create myself a -current DVD and installed fresh from that DVD.

After that, I used slackpkg to keep my -current installation up to date.

Once 13.0/64 became officially released, I changed my slackpkg mirrors file to point at a 13.0 stable mirror, and all has, AFAICT, been fine since then.

Present Day:

So now, as we know there are lots of fun new changes and stuff in Slackware64-current as of early March 2010.
I would like to switch back to -current

I've got my /etc/slackpkg/mirrors file pointed at:
Code:
ftp://slackware.oregonstate.edu/pub/slackware/slackware64-current/
Here's my slackpkg.conf file:
Code:
root@reactor: cat /etc/slackpkg/slackpkg.conf | sed '/^#\|^$/d'
ARCH=x86_64
PKGMAIN=slackware
TEMP=/var/cache/packages
WORKDIR=/var/lib/slackpkg
WGETFLAGS="--passive-ftp"
DELALL=off
CHECKMD5=on
CHECKGPG=on
PRIORITY=( patches %PKGMAIN extra testing pasture )
POSTINST=on
ONLY_NEW_DOTNEW=off
ONOFF=on
DOWNLOAD_ALL=on
DIALOG=on
BATCH=off
DEFAULT_ANSWER=y
USE_INCLUDES=on
SPINNING=on
So, with the above settings, "slackpkg update" appears to work fine.
Here's the top bit of the ChangeLog.txt file that I get when I update slackpkg:
Code:
root@reactor: cat /var/lib/slackpkg/ChangeLog.txt
       
Tue Mar  2 19:07:31 UTC 2010
a/aaa_elflibs-13.013-x86_64-3.txz:  Rebuilt.
a/coreutils-8.4-x86_64-2.txz:  Rebuilt.
  Use --without-gmp, at least for now.  We don't want utilities in /bin
  requiring a library in /usr/lib{,64} that may not be available.
l/gtk+2-2.18.7-x86_64-2.txz:  Rebuilt.
l/libpng-1.4.1-x86_64-2.txz:  Rebuilt.
  Now with less rat.
xap/xchat-2.8.6-x86_64-5.txz:  Rebuilt.
+--------------------------+
Mon Mar  1 22:43:53 UTC 2010
Hey folks, we have a whole bunch of updates!  Huge thanks to Robby Workman,
Eric Hameleers, and Piter Punk for all the help.  :-)
a/aaa_elflibs-13.013-x86_64-2.txz:  Rebuilt.
a/acpid-2.0.2-x86_64-1.txz:  Upgraded.
a/bash-4.1.002-x86_64-1.txz:  Upgraded.
a/coreutils-8.4-x86_64-1.txz:  Upgraded.
a/cups-1.4.2-x86_64-1.txz:  Upgraded.
...
8<----snip----8<
Looks correct, yes? Nice new stuff in there, dated March 2010..

FWIW, here's me /etc/slackware-version file:
Code:
root@reactor: cat /etc/slackware-version
Slackware 13.0.0.0.0
root@reactor:
Now, if I run "slackpkg upgrade-all" right now, I am offered bash-completion-1.1-noarch-1.txz and slacktrack-2.07-x86_64-1.txz -- that's it!
If I run "slackpkg install-new" I'm told there's nothing new to install:
Code:
No packages match the pattern for install. Try:

        slackpkg upgrade|reinstall
So.. What gives here? It's GOTTA be something ridiculous, silly, stupid, whatever. I don't care you can even laugh at how dense I've been when the problem comes to light, that's cool but someone pLeAsE tell me what I'm missing!?

Big Thanks!
Sasha
 
Old 03-04-2010, 12:49 PM   #2
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
In slackpkg.conf comment PKGMAIN=slackware. Slackpkg can figure this out automatically for you.
In Slackware64 the package main is slackware64, not slackware

Double check blacklist as well.
 
1 members found this post helpful.
Old 03-04-2010, 12:52 PM   #3
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Original Poster
Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550


Freaking EGADS!!

Thank you disturbed1!!

Commenting out PKGMAIN did the trick!

Sasha
 
Old 03-04-2010, 12:58 PM   #4
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223

Can I laugh now?
 
Old 03-04-2010, 12:58 PM   #5
vdemuth
Member
 
Registered: Oct 2003
Location: West Midlands, UK
Distribution: Slackware 14 (Server),Suse 13.1 (Desktop),, Mepis on the wifes lappy
Posts: 768

Rep: Reputation: 92
To late

Last edited by vdemuth; 03-04-2010 at 01:01 PM.
 
Old 03-04-2010, 01:01 PM   #6
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Original Poster
Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
@ disturbed -- YES, laugh to your hearts content

@ vdemuth -- thank you for the suggestion! I had tried better than half a dozen mirrors already, with the same effect (which given the problem we now know, is obvious why it had the same result) but given that the ChangeLog was current, I feel it was pretty safe to assume that the rest of the mirror would be current too (or close to it).

disturbed1 hit it directly -- I had the wrong PKGMAIN setting

Thanks you guys!
Sasha
 
  


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
Kernel panic after upgrading slackware64-current to 2.6.32.x kernel Lenard Spencer Slackware 4 01-22-2010 10:54 AM
Updating from Slackware64-current to Slackware64 13. glore2002 Slackware 4 08-28-2009 06:50 PM
Slackware64-current missing kernel headers? UpAndUp Slackware 2 08-26-2009 07:08 PM
Slackware64-Current / slackpkg slackass Slackware 31 06-06-2009 10:51 PM
Slackpkg: missing something in /usr/libexec/slackpkg/functions.d/dialog-functions.sh michelino Slackware 4 03-20-2007 12:22 PM


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