[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.
Thanks to all who posted. My idle curiosity has been generously
fed full of info :-) I'm glad to see that all is well--developers
developing, and Slackware well on track. I'll look forward to when
that trigger is pulled.
I looked in 64bit current and there wasn't anything new there and thought what the hell is he on about. Then I checked 32bit! Yikes!
I normally pay close attention to the updates. With that lot I'm just going to have to go on blind trust and use a 'for blah in *.t?z' loop against the entire lot. Far too many changes to actually follow what's going on with.
Thankfully, it'll take a day or so for my local mirror to sync so I'll have time to get over the shock before I have to apply them. I don't even want to have to think about all those *.new's I'm gonna have to deal with!
I think the forum's are gonna be quiet tomorrow while everyone deals with these.
Yes, mRgOBLIN, thanks for the clue. I just looked. The changelog does
indeed appear to have had at least a month's worth of changes by the
Slackware team added at Mar 1 22:43:53 UTC 2010. Current users may find
it interesting :-)
After reviewing the changelog entry for today (March 1, 2010), I'm thinking maybe it would have been easier for Pat to tell us what hasn't changed. In 6 years of using Slack, I don't think I've ever seen a single changelog entry of this magnitude.
After reviewing the changelog entry for today (March 1, 2010), I'm thinking maybe it would have been easier for Pat to tell us what hasn't changed. In 6 years of using Slack, I don't think I've ever seen a single changelog entry of this magnitude.
Quote:
l/libjpeg-v8-x86_64-1.txz: Upgraded.
This changes the soname to .so.8.
This is the first time in almost 8 years libjpeg got a new upstream release, let alone one with a soname bump.
Thats why sooner of later if Pat wanted to upgrade to it there would be a huge amount of rebuilds required.
It just happened to be now.
I get the error: libgmp.so.10 is not found. So I terminated the slackpkg update-all process.
Now I can't run slackpkg, installpkg, upgradepkg because of the same error. I'm so excited to try the -current so I just symlinked the file to libgmp.so which is also a synlink to the real lib. Now I restarted the upgrade process. Hopefully it will work. (breaking the virtual machine first, before breaking my laptop )
You may find that thread handy (or informative at least) if you haven't yet read it.
Myself, I'm just curious how long it usually takes for the latest stuff (like as of the latest changelog) on the slackware ftp server to propagate to the various mirrors.... Any general idea anyone? I've tried 3 or 4 mirrors and so far nothing new.
You may find that thread handy (or informative at least) if you haven't yet read it.
Myself, I'm just curious how long it usually takes for the latest stuff (like as of the latest changelog) on the slackware ftp server to propagate to the various mirrors.... Any general idea anyone? I've tried 3 or 4 mirrors and so far nothing new.
My symlink work, but I prefer that thread you posted, it is more elegant.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.