Prev: stop cups starting at boot
Next: Slackware 11.0 production server upgrade to 12.1
From: notbob on 17 Jun 2008 15:56
I get a pop-up with:


-------

/tmp/foo.md5 could not be saved because the source file could not be read.

Try again later or contact server administrator.

-------

I thought this was just a couple packages, but it seems to be all packages
and I'm pretty sure I ran into this the last time I looked at Erics packages
several weeks ago. What's up?


nb

From: Eric Hameleers on 17 Jun 2008 16:49
notbob wrote:
> I get a pop-up with:
>
>
> -------
>
> /tmp/foo.md5 could not be saved because the source file could not be read.
>
> Try again later or contact server administrator.
>
> -------
>
> I thought this was just a couple packages, but it seems to be all packages
> and I'm pretty sure I ran into this the last time I looked at Erics packages
> several weeks ago. What's up?
>
>
> nb
>
Please explain more clearly what you mean. The above makes no sense as
it provides no reference (what program used to download; what URL to
download from; what date/time,...)
I can see nothing wrong.


Eric
From: notbob on 17 Jun 2008 18:26
On 2008-06-17, Eric Hameleers <alien(a)penguin1.dyndns.org> wrote:

> Please explain more clearly what you mean. The above makes no sense as
> it provides no reference (what program used to download; what URL to
> download from; what date/time,...)
> I can see nothing wrong.

OK. Googling for slackware packages, I get:

http://www.slackware.com/~alien/

.....which takes me to:

http://www.slackware.com/~alien/slackbuilds/

.....and from there I go to digikam > pkg > 12.1 where I click on the:

digikam-0.9.3-i486-1alien.tgz.md5

.....file which gives me the following error message pop-up:

-------

/tmp/ftzulqw0.md5 could not be saved because the source file could not be read.
Try again later or contact server administrator.
[ OK }

-------

Note: the "ftzulqw0" portion of the file changes everytime I click on the
file link.

The rest of the files are ok, just the md5 files, which are indicated by a ?
icon. All md5 files I try are the same. Other files like .asc, .meta, and
..dep are fine, including the actual binaries which I downloaded and
installed, no problem. I don't know how to explain it any clearer than
that.

Could it be my browser is messing something up? I'm using 12.1 and mozilla
on kde.

nb

From: notbob on 17 Jun 2008 18:36
On 2008-06-17, Eric Hameleers <alien(a)penguin1.dyndns.org> wrote:

> I can see nothing wrong.

Also, I came to a dead-end with digikam when it said I need libjasper.so.1.
I have already loaded your libkipi and sqlite3 pkgs, but find no jasper.
Did you compile from source? I found the source at:

http://www.ece.uvic.ca/~mdadams/jasper

.....and a tip to configure with '--enable-dynamic' on the Polish slackware
forum. Is that how you did it? Any other tips I need to get digikam flying?

Thanks,
nb
From: Helmut Hullen on 18 Jun 2008 01:39
Hallo, notbob,

Du meintest am 17.06.08:

> ....and from there I go to digikam > pkg > 12.1 where I click on the:

> digikam-0.9.3-i486-1alien.tgz.md5

> ....file which gives me the following error message pop-up:

Which program do you start when you click on a file with the extension
*.md5?
Sounds like Windows ...

I'd try the CLI way:
download *.tgz
download *.md5
running md5sum

Viele Gruesse
Helmut

"Ubuntu" - an African word, meaning "Slackware is too hard for me".

 |  Next  |  Last
Pages: 1 2 3
Prev: stop cups starting at boot
Next: Slackware 11.0 production server upgrade to 12.1