[SOLVED] Slack-current change logs--changeless in Feb?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've always looked forward to applying new changes from -current, knowing that my system
was going to be even better and safer. This is the first time I've ever felt a sense of trepidation.
Maybe like jumping out of an aeroplane ? Anyone seen some sort of executive summary explaining
exactly what we can expect to happen - especially around the X-server stuff where most desktops
will be affected ?
Click here to see the post LQ members have rated as the most helpful post in this thread.
If you are having second thoughts.. (and it looks like they are valid at this time =)), Then I'd give it a couple of days for the major kinks to be worked out.
/sbin/dhclient-script: line 117: ifconfig: command not found
/sbin/dhclient-script: line 155: ifconfig: command not found
/sbin/dhclient-script: line 162: route: command not found
i assume editing /sbin/dhclient-script and using the full path to those binaries would fix it, but this shouldnt need to be done
Maybe I'm just having a short-bus moment here, but can someone tell me why it is that, having just updated slackpkg (slackpkg update) using a -current mirror, the only new things I am told are available are slacktrack-2.07 and bash-completion-1.1 ??
I'm running 13.0 x86_64
I checked the ChangeLog I just received -- it is indeed filled with new goodies -- but.. WTH am I missing here? Is it my /etc/slackware-version file or what!?! Why doesn't it tell me there are hundreds of new things to upgrade to?
GrapefruitGirl... perhaps this happens becauase your slackpkg is pointing to a Slackware 13.0 mirror while all these new goodies are available for slackware-current?
/sbin/dhclient-script: line 117: ifconfig: command not found
/sbin/dhclient-script: line 155: ifconfig: command not found
/sbin/dhclient-script: line 162: route: command not found
i assume editing /sbin/dhclient-script and using the full path to those binaries would fix it, but this shouldnt need to be done
I saw the same errors yesterday on an Acer Aspire One D250 laptop. I assumed my issues were wireless driver related (ath9k module with AR9285 card) until I switched from wicd/dhclient to inetd/dhcpcd and wireless worked.
@ Eric -- nope I don't think that's the problem; as mentioned, I changed my mirror file to point at a --current mirror, and I am getting a changelog (and the other files) from that very mirror, and it's the NEW changelog, dated early March (1st or 2nd of March).. So it all looks good so far. But when I do `slackpkg upgrade-all` or `slackpkg install-new`, there's nothing to do! I admit I'm a little spaced sometimes but this has me stumped still..
Sasha
Have you deleted the space as well as the hashmark from your chosen mirror?
Code:
# USA,
# ftp://ftp-linux.cc.gatech.edu/pub/slackware/slackware-13.0/
# USA, 1Gbit
http://slackware.mirrors.tds.net/pub/slackware/slackware-13.0/
# ftp://slackware.mirrors.tds.net/pub/slackware/slackware-13.0/
@ Brian - yes, just re-checked. No leading space. The funny thing is, the ChangeLog is the correct one, so the mirror itself doesn't seem to be the problem:
Code:
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.
..blah blah..
Still stumped..
I just tried `slackpkg upgrade-all` and still get only an offer of bash-completion and slacktrack.
I've just been having a quick look back through the ChangeLogs (current & stable), and didn't see those two items mentioned anywhere. Very strange, huh?
Strange indeed! For the moment I guess I'll switch focus to my other ongoing situation RE: composite & multiple monitors, which is being chatted about in the "What are you doing now" thread.
Distribution: Slackware 14 (Server),OpenSuse 13.2 (Laptop & Desktop),, OpenSuse 13.2 on the wifes lappy
Posts: 781
Rep:
Just a quick question here. In the slackpkg blacklist it quite clearly states that aaa_elflibs can't be updated and as such the blackist applies to them. Does the inclusion of them in this update now mean it is safe to remove the entry from the blacklist?
Just a quick question here. In the slackpkg blacklist it quite clearly states that aaa_elflibs can't be updated and as such the blackist applies to them. Does the inclusion of them in this update now mean it is safe to remove the entry from the blacklist?
It is safe to comment that out if you are running -current. However, you don't want to update that package if you are running -stable.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.