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.
The first two are upgrades. The last is a dependency for most of the new KDE packages. Main Slackware FTP server seems to be pretty bogged down, too. I had several others that wouldn't download, but I kept trying and am now left with just these three. All the packages that were giving me headaches were something to do with KDE. I also rsync to -current from the .at mirror. I noticed that not all of the packages are updated yet. Probably just have to wait for the mirrors to catch up.
That's funny. Mine must be a "special" SWareT. I just upgraded KDE today. I'm posting this from Konqueror on my newly updated KDE 3.3.1.
Quote:
it will be a while until a GOOD package manager
pkgtool seems pretty good. You can always manually download updates and install them with that.
Quote:
update at your own risk, or just don't
Or, don't upgrade at your own risk. Not upgrading leaves you open to security issues. That's why there are updates to Slackware 10 in addition to the updated Slackware-current.
Quote:
swaret sux ..It crashed my sound and aslo some programs failed to work after upgrading with swaret ...guess you gotta upgrade from source ....
SWareT didn't crash your sound. Your upgrading ALSA most likely crashed your sound. You configured SWareT. You can easily tell it not to upgrade ALSA. As for programs failing to work, there are several possibilities. First, it may be a known issue. If you read the changelogs, you'll note that some programs can be broken by updating. There have been some issues mentioned in the changelog about KDE symlinks, Mozilla, Epiphany, and Galeon. Another possibilty is that you didn't update your config files. SWareT doesn't blow away your old config files. You need to see what relevant changes have been made to config files and incorporate those into your old config file. Another possibility is your choice of repositories. If you use third party repositories, you may have issues with their packages. The official packages from the official mirrors work. Other packages may or may not. For the most part, checkinstall is a very easy tool to use and has pretty much eliminated my dependence on third-party packages. Packages that I install from source are the only packages that I ever have to upgrade from source.
Quote:
Swaret work fine if you know how to use it...
I have to agree. There are some things I'd like to see changed to make it work BETTER, but it does work like it is supposed to.
That's funny. Mine must be a "special" SWareT. I just upgraded KDE today. I'm posting this from Konqueror on my newly updated KDE 3.3.1.
Quote:
it will be a while until a GOOD package manager
pkgtool seems pretty good. You can always manually download updates and install them with that.
Quote:
update at your own risk, or just don't
Or, don't upgrade at your own risk. Not upgrading leaves you open to security issues. That's why there are updates to Slackware 10 in addition to the updated Slackware-current.
Quote:
swaret sux ..It crashed my sound and aslo some programs failed to work after upgrading with swaret ...guess you gotta upgrade from source ....
SWareT didn't crash your sound. Your upgrading ALSA most likely crashed your sound. You configured SWareT. You can easily tell it not to upgrade ALSA. As for programs failing to work, there are several possibilities. First, it may be a known issue. If you read the changelogs, you'll note that some programs can be broken by updating. There have been some issues mentioned in the changelog about KDE symlinks, Mozilla, Epiphany, and Galeon. Another possibilty is that you didn't update your config files. SWareT doesn't blow away your old config files. You need to see what relevant changes have been made to config files and incorporate those into your old config file. Another possibility is your choice of repositories. If you use third party repositories, you may have issues with their packages. The official packages from the official mirrors work. Other packages may or may not. For the most part, checkinstall is a very easy tool to use and has pretty much eliminated my dependence on third-party packages. Packages that I install from source are the only packages that I ever have to upgrade from source.
Quote:
Swaret work fine if you know how to use it...
I have to agree. There are some things I'd like to see changed to make it work BETTER, but it does work like it is supposed to.
I just upgraded from my rsync'd current directory and I'm missing libidn.so.11
My KDE is hosed (upgrading from 3.2.3) - and I had things so nice....
Oh well. At least I'm not alone
By the way, shit happens - whether you use swaret, dropline, slapt-get, or traditional routes.
Things work 90% of the time, but sometimes things just fsck up.
It doesn't mean anything is inherently bad. Just grin and bear it. At least it's the weekend.
libidn is in the /l directory. It was not installed via upgradepkg but was present in my /l.
Installing it via pkgtool made life good again.
If you are having probs due to this, just download the package from slackware.org (or your favorite mirror)
and install it.
HTH
EDIT: Checking the changelog answers all questions. This package was an addition, not an upgrade - something I missed when I first read the log and something swaret will always miss if you substitute it for basic prepwork. Regardless of which system you use, you MUST read the changelog or get burned - I got burned tonight and I don't use anything. The same thing happens with deletions of packages. If you want to use these tools to make you life easier, you still need to use your brain a bit and not let these same tools do your thinking for you.
I seem to have stumbled upon another slackware update program, i haven't tried this one, but it might be worth checking out... http://128.173.184.249/slackupdate/
Originally posted by Franklin libidn is in the /l directory. It was not installed via upgradepkg but was present in my /l.
Installing it via pkgtool made life good again.
If you are having probs due to this, just download the package from slackware.org (or your favorite mirror)
and install it.
Thanks,
For anyone else who gets the same problem, either let swaret download and install the library itself, or manually download from http://slackware.com/pb/download.php...n-0.5.8-i486-1
and installpkg libidn......tgz
Originally posted by Franklin I just upgraded from my rsync'd current directory and I'm missing libidn.so.11
My KDE is hosed (upgrading from 3.2.3) - and I had things so nice....
Oh well. At least I'm not alone
By the way, shit happens - whether you use swaret, dropline, slapt-get, or traditional routes.
Things work 90% of the time, but sometimes things just fsck up.
It doesn't mean anything is inherently bad. Just grin and bear it. At least it's the weekend.
I had that problem too. It wasn't a serious problem, but it was annoying.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.