(Solved) can't upgrade Seamonkey-solibs

[loukingjr]

Obviously to me anyway there are people here who know a lot more about Salix and Slackware than myself. Is there someone who can post the commands I need to fix the issue?

danke

[jonas]

Dear all,

I also have the same slapt-get -upgrade error with seamonkey-solibs, on all my machines, DELL, Thinkpad, Asus etc.
I'm also running Salix OS 14, XFCE, 64 bit.

Error message from gslapt:
"Faild to download seamonkey: HTTP response code said error"

I would very much appricate a "possible to understand answer/advice"...

Br Jonas B

[mimosa]

Here is where Slackware's own changelog says the new packages are:

http://www.slackware.com/security/viewe ... ity.494943

I tried downloading with wget (for both architectures), also no luck.

I don't understand why this seems to keep happening (I believe this thread goes back a couple of years) but my guess is it will be fixed upstream in a few days. Meanwhile, a slapt-get --upgrade will fail because of this one package, but you can install the others manually: the failure includes a list of the packages to be installed, just do slapt-get -i [that list without seamonkey*]

If anyone else knows of another mirror where the packages can be found, please let us know!

[mimosa]

There appears to be some mix-up with the package version number. Packages available here (choose your architecture):

32-bit:
ftp://ftp.slackware.com/pub/slackware/s ... ck14.0.txz

64-bit:
ftp://ftp.slackware.com/pub/slackware/s ... ck14.0.txz

I downloaded with wget and installed with spkg:

Code: Select all

spkg -u seamonkey-solibs-2.16.2-i486-1_slack14.0.txz

Package upgrades still won't work properly (till this gets sorted out) because slapt-get / Gslapt tries to download the nonexistent tarball and fails as before.

You might prefer to just leave it till somebody fixes it, unless you're very concerned about security.

[ElderDryas]

1) Has anyone conclusively determined this is an Upstream Problem; and if so
2) Has anyone informed Upstream of the problem;
or
3) Has anyone conclusively determined this is a Salix Problem; and if so
4) Has anyone determined who and how the problem needs to be fixed?

This is not just a single update problem, any initial update after a new install will fail. Not the first impression one wants to make. I know mimosa has posted a work around, but still....

I ask about determining that is is an upstream problem because I see nothing in the slack forum on LQ about it, and one would expect to see someone asking about it there.

EDIT:

(11:17:12 AM) JRD: Sackers don't upgrade their system using slapt-get usually, that could be related.

That probably answers my last statement (nothing in LQ).

[mimosa]

Here is a link to the Slackware announcement of this package, with version number inconsistent with the Slack repo:

http://www.slackware.com/lists/archive/ ... ity.494943

However, nobody on LQ or the Wider Web seems to have noticed it except Salix users.

Nonetheless, looks like an upstream problem.

[mimosa]

The problem has now been solved and everything should be back to normal. Just do an update to download the corrected package information.

For anyone who installed the upgrade with spkg, it may be best (though I'm not sure if it's necessary) to uninstall it with spkg then reinstall in the normal way:

Code: Select all

spkg -d seamonkey-solibs ... txz
slapt-get -i seamonkey-solibs

That way everything is sure to run smoothly when the *next* upgrade comes along.

[loukingjr]

works for me now.

[gapan]

It was a case of mirrors not syncing properly. It eventually fixed itself as it seems

[jonas]

Yes, it works fine, as it should, now.
The issue is solved/closed from my perspective.
Thank you! // Br Jonas B