Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
slackpkg clean-system problem
238 views
Skip to first unread message
Joseph Rosevear
Aug 12, 2022, 12:52:46 AM8/12/22
to
Hi Folks!
I have a relatively new Slackware64 15.0, and I'm trying to run "slackpkg
clean-system" on it. In the usual way, because I haven't before used
slackpkg on this installation, it asked me to select a mirror. I did
that, ultimately trying several (one at a time) including these:
https://mirrors.slackware.com/slackware/slackware64-15.0/
http://mirrors.us.kernel.org/slackware/slackware64-15.0/
It failed it seems in the same way each time. Here is the last bit of
output which gives the error message:
vvv
/tmp/slackpkg.d7inKy/CHECKSUMS.md5.asc 100%
[=========================================================================
============================>] 163 --.-KB/s in 0s
2022-08-11 19:58:13 (12.7 MB/s) - ‘/tmp/slackpkg.d7inKy/
CHECKSUMS.md5.asc’ saved [163/163]
ERROR: Verification of the gpg signature on CHECKSUMS.md5
failed! This could mean that the file is out of
date
or has been tampered with. If you use
mirrors.slackware.com
as your mirror, this could also mean that the
mirror to
which you got redirected is not yet updated with
the most
recent changes in the Slackware tree.
^^^
Can anyone help?
-Joe
I have a relatively new Slackware64 15.0, and I'm trying to run "slackpkg
clean-system" on it. In the usual way, because I haven't before used
slackpkg on this installation, it asked me to select a mirror. I did
that, ultimately trying several (one at a time) including these:
https://mirrors.slackware.com/slackware/slackware64-15.0/
http://mirrors.us.kernel.org/slackware/slackware64-15.0/
It failed it seems in the same way each time. Here is the last bit of
output which gives the error message:
vvv
/tmp/slackpkg.d7inKy/CHECKSUMS.md5.asc 100%
[=========================================================================
============================>] 163 --.-KB/s in 0s
2022-08-11 19:58:13 (12.7 MB/s) - ‘/tmp/slackpkg.d7inKy/
CHECKSUMS.md5.asc’ saved [163/163]
ERROR: Verification of the gpg signature on CHECKSUMS.md5
failed! This could mean that the file is out of
date
or has been tampered with. If you use
mirrors.slackware.com
as your mirror, this could also mean that the
mirror to
which you got redirected is not yet updated with
the most
recent changes in the Slackware tree.
^^^
Can anyone help?
-Joe
Henrik Carlqvist
Aug 12, 2022, 1:37:37 AM8/12/22
to
On Fri, 12 Aug 2022 04:52:42 +0000, Joseph Rosevear wrote:
> Hi Folks!
> It failed it seems in the same way each time. Here is the last bit of
> output which gives the error message:
>
> vvv /tmp/slackpkg.d7inKy/CHECKSUMS.md5.asc 100%
Those .asc files contain a signature created using the file (in this case
CHECKSUMS.md5) and a gnupg private key. You can use gnupg together with
the public key from Slackware to verify that the file CHECKSUMS.md5
really comes from Slackware and has not been tampered with.
> ERROR: Verification of the gpg signature on
> CHECKSUMS.md5 failed!
I suppose that slackpkg simply calls gpg to validate the gnupg
signatures. However, before you are able to validate signatures you will
have to install the public key in your gpg keyring.
What output do you get if you stand in the directory where you have
CHECKSUMS.md5 and CHECKSUMS.md5.asc and type:
gpg --verify CHECKSUMS.md5.asc
echo $?
regards Henrik
> Hi Folks!
> I'm trying to run "slackpkg clean-system"
I haven't used slackpkg myself.
> It failed it seems in the same way each time. Here is the last bit of
> output which gives the error message:
>
> vvv /tmp/slackpkg.d7inKy/CHECKSUMS.md5.asc 100%
CHECKSUMS.md5) and a gnupg private key. You can use gnupg together with
the public key from Slackware to verify that the file CHECKSUMS.md5
really comes from Slackware and has not been tampered with.
> ERROR: Verification of the gpg signature on
> CHECKSUMS.md5 failed!
signatures. However, before you are able to validate signatures you will
have to install the public key in your gpg keyring.
What output do you get if you stand in the directory where you have
CHECKSUMS.md5 and CHECKSUMS.md5.asc and type:
gpg --verify CHECKSUMS.md5.asc
echo $?
regards Henrik
Rinaldi
Aug 12, 2022, 1:29:56 PM8/12/22
to
slackpkg [OPTIONS] update [gpg] ?
--
Critic, n.:
A person who boasts himself hard to please because nobody tries
to please him. -- Ambrose Bierce, "The Devil's Dictionary"
Critic, n.:
A person who boasts himself hard to please because nobody tries
to please him. -- Ambrose Bierce, "The Devil's Dictionary"
Jimmy Johnson
Aug 12, 2022, 1:43:09 PM8/12/22
to
On 08/11/2022 09:52 PM, Joseph Rosevear wrote:
> Hi Folks!
>
> I have a relatively new Slackware64 15.0, and I'm trying to run "slackpkg
> clean-system" on it.
>
> Can anyone help?
> Hi Folks!
>
> I have a relatively new Slackware64 15.0, and I'm trying to run "slackpkg
> clean-system" on it.
>
Hi,
You need to read this:
https://docs.slackware.com/slackware:beginners_guide
You can skip down to slackpkg instructions if you want, but I suggest
you read as much as you can and then if you still have questions come on
back, you're always welcome. :)
--
Jimmy Johnson
Alien Linux - AMD A8-7600 - EXT4 at sda9
Registered Linux User #380263
Joseph Rosevear
Aug 13, 2022, 7:34:36 PM8/13/22
to
On Fri, 12 Aug 2022 05:37:34 -0000 (UTC), Henrik Carlqvist wrote:
> On Fri, 12 Aug 2022 04:52:42 +0000, Joseph Rosevear wrote:
>
>> Hi Folks!
>> I'm trying to run "slackpkg clean-system"
>
> I haven't used slackpkg myself.
>
>> It failed it seems in the same way each time. Here is the last bit of
>> output which gives the error message:
>>
>> vvv /tmp/slackpkg.d7inKy/CHECKSUMS.md5.asc 100%
>
> Those .asc files contain a signature created using the file (in this
> case CHECKSUMS.md5) and a gnupg private key. You can use gnupg together
> with the public key from Slackware to verify that the file CHECKSUMS.md5
> really comes from Slackware and has not been tampered with.
>
>> ERROR: Verification of the gpg signature on
>> CHECKSUMS.md5 failed!
>
> I suppose that slackpkg simply calls gpg to validate the gnupg
> signatures. However, before you are able to validate signatures you will
> have to install the public key in your gpg keyring.
Inspired by your patient words of explanation, I figured it out. It
> On Fri, 12 Aug 2022 04:52:42 +0000, Joseph Rosevear wrote:
>
>> Hi Folks!
>> I'm trying to run "slackpkg clean-system"
>
> I haven't used slackpkg myself.
>
>> It failed it seems in the same way each time. Here is the last bit of
>> output which gives the error message:
>>
>> vvv /tmp/slackpkg.d7inKy/CHECKSUMS.md5.asc 100%
>
> Those .asc files contain a signature created using the file (in this
> case CHECKSUMS.md5) and a gnupg private key. You can use gnupg together
> with the public key from Slackware to verify that the file CHECKSUMS.md5
> really comes from Slackware and has not been tampered with.
>
>> ERROR: Verification of the gpg signature on
>> CHECKSUMS.md5 failed!
>
> I suppose that slackpkg simply calls gpg to validate the gnupg
> signatures. However, before you are able to validate signatures you will
> have to install the public key in your gpg keyring.
works now.
I should add, however, that I started by writing a different reply
altogether. I had written a bunch of questions asking how gpg worked.
In the process of writing my questions I turned to the man pages for gpg,
did some online searching, and tried a few tests.
Here are steps of my, not insignificant, journey:
-I played with the .gnupg dir. I moved root/.gnupg to a different
name to see what would happen. It didn't break anything. I think that
it simply took away whatever had previously been setup.
-First as root, and then as user joe, I did "gpg --gen-key" to make a
key pair. I took the defaults, provided an email address, and a
passphrase. Incidentally, I made a mistake when entering my full name
the first time (for root)--how can I fix it?
-As user joe I did "gpg --list-keys" before and after doing the
above. Three entries appeared for pub, uid and sub. Hmmm. I don't know
what "pub", "uid" and "sub" mean.
-As user joe I did "gpg --sign-key 40102233". This prompted me for
the passphrase I had entered above. It worked.
-Note that as joe, I wasn't able easily to run slackpkg, so I didn't
try. I did, however, try what you suggested "gpg --verify
CHECKSUM.md5.asc" after first making the .asc and .md5 files from what I
got from the mirror. It worked! Incidentally I had also attempted this
as both joe and root before, per your suggestion, without success.
-I still needed to get "slackpkg clean-system" working, so... I did
"gpg --list-keys" as root and got pub, uid and sub lines.
-I don't know if I previously had a pub line for Slackware Linux
Project, but if so, then it went away when I moved .gnupg to a new name.
So I went online and found the public key that I needed. I saved it to a
file. Then, as root, I did "gpg --import <file>". Afterwards it
appeared as a second set of pub, uid and sub lines in the output from
"gpg --list-keys".
-As root I did "gpg --sign-key 40102233", exactly as I did before as
user joe, except I used the root passphrase.
-Now confident, I didn't bother to test with "gpg --verify ...". I
went to a console and ran as root "slackpkg clean-system". It worked!
> regards Henrik
Thank you, Henrik.
-Joe
Joseph Rosevear
Aug 15, 2022, 12:38:25 AM8/15/22
to
On Fri, 12 Aug 2022 10:43:02 -0700, Jimmy Johnson wrote:
> On 08/11/2022 09:52 PM, Joseph Rosevear wrote:
>> Hi Folks!
>>
>> I have a relatively new Slackware64 15.0, and I'm trying to run
>> "slackpkg clean-system" on it.
>>
>> Can anyone help?
>
> Hi,
>
> You need to read this:
> https://docs.slackware.com/slackware:beginners_guide
>
> You can skip down to slackpkg instructions if you want, but I suggest
> you read as much as you can and then if you still have questions come on
> back, you're always welcome. :)
Hi Jimmy,
> On 08/11/2022 09:52 PM, Joseph Rosevear wrote:
>> Hi Folks!
>>
>> I have a relatively new Slackware64 15.0, and I'm trying to run
>> "slackpkg clean-system" on it.
>>
>> Can anyone help?
>
> Hi,
>
> You need to read this:
> https://docs.slackware.com/slackware:beginners_guide
>
> You can skip down to slackpkg instructions if you want, but I suggest
> you read as much as you can and then if you still have questions come on
> back, you're always welcome. :)
I have not often run slackpkg on a new installation. I can't remember
what I did before--perhaps the problem I had this time didn't crop up, or
maybe I stumbled onto the information that I needed and forgot to make a
note of it.
Anyway, your tip is valuable--thank you!
-Joe
0 new messages