Every package gives me "FAILED!".
I've tried changing the version, updatedb, swaret --update etc and nothing has solved this.

Happens on any package and any version.

Have you tried slackpkg? I've found this to be a very good utility.

http://www.slackpkg.org/documentation.html

Thanks, this looks better. But it doesn't seem to see anything. I enabled a mirror and did an update.

After you added a mirror did you first run:

# slackpkg update

Yes, like I said I did an update. Got it working though, apparently any current mirror had this issue so I enabled a 12.0 mirror.

Now I'm having this issue:

I wouldn't give up on swaret yet. I've been using the latest version (1.6.3.2) with no issues at all.
Has it ever worked for you? If not, you may need to check your swaret.conf. I don't have access to mine right now, but I can send it to you later, if it would help.

There is nothing mysterious about this message. There is no prior file "/etc/rc.d/rc.font" so it is impossible to show the difference with the "/etc/rc.d/rc.font.new" file.

Eric

I don't know what makes you think you can just jump from using a 10.1 mirror to a 12.0 mirror, but it doesn't work like that. If you really did that, then I suspect that swaret is the least of your problems (and that's saying a lot, because swaret is probably the last piece of software you'll ever find installed on one my systems).

To be honest, I have seen opinions like this many times over the years, posted here and elsewhere. But it is actually not clear to me, what these harsh statements are caused by.

Of course, a fool with a tool is still a fool (not adressed to the OP).

I find useful functionality in tools like swaret and slapt-get, mainly dependency checking, which is something that none of the (good!) official tools does for me. But I won't ever allow them to resolve dependencies unattended.
Neither swaret nor slapt-get has ever caused any damage in my system, probably because I used them with care. Still, they provide useful features, not available in the stock tools.

So I wonder what this hostility is caused by.

BTW, I use slapt-get not very often, but I like to use sbopkg, slackyd and src2pkg. These are all very helpful for me, and they way they guide the user minimises the risk of unintential replacements of libraries due to dependencies being resolved automatically, or so.
However, as I said, swaret and slapt-get provide a couple of useful features, that I haven't found elsewhere. I only use these features to get some hints of gaps or inconsistencies, and they proved very useful for this.

But to make this clear too: I rely on slapt-get or swaret to maintain my system. I use slackpkg and the pkgtools for this.

gargamel

Please don't put words in my mouth - I made no statements at all about slapt-get in that post. In fact, if used properly and with an understanding of its limitations, I think slapt-get can be a great tool for many users.

I cannot say the same about swaret - the way it tries to find dependencies is fundamentally flawed. That might have changed in the most recent version, and if so, perhaps I need to have a look at it again, but otherwise, my opinion stands as stated earlier.

That's certainly not what I was going to say. If my post can be mis-interpreted in this way, I apologise for this.

gargamel

Fair enough. It was *early* in the morning when I replied, so perhaps I just needed more caffeine. :-)

No problem. Keep up the excellent work!

gargamel