I would have expected slapt-get to import keys or tell me those keys were cached from slint-testing but that didn't happen.

cut here.
Script started on Wed 11 Oct 2017 05:09:32 AM EDT
root@taf:/etc/slapt-get# slapt-get --add-keys
Retrieving GPG key 
[http://slackware.uk/slint/x86_64/slint-testing/:PREFERRED./]...Not Found
Retrieving GPG key [http://slackware.uk/salix/x86_64/slackware-14.2/]...Cached
GPG key already present.
Retrieving GPG key [http://slackware.uk/salix/x86_64/slackware-14.2/extra/]...  
0%  0%  0%  0%  0%  0%  0%  0%  0%  0%  
0%  0%  0%  0%  0% 79% 
79%100%100%100%100%Done
GPG key already present.
Retrieving GPG key [http://slackware.uk/salix/x86_64/14.2/]...Cached
GPG key already present.
Retrieving GPG key [http://slackware.uk/salix/x86_64/extra-14.2/]...Cached
GPG key already present.
root@taf:/etc/slapt-get# exit
exit

Script done on Wed 11 Oct 2017 05:10:31 AM EDT
On Wed, 11 Oct 2017, Linux for blind general discussion wrote:

Date: Wed, 11 Oct 2017 02:00:18
From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: [Testers wanted before the official release] Slint64-4.2.1
    release candidate is accessible.

Also, after having modified a SOURCE line you need to run again:
slapt-get --add-keys
slapt-get -u
Le 11/10/2017 ? 07:51, Didier Spaier a ?crit?:
Le 11/10/2017 ? 02:39, Linux for blind general discussion a ?crit?:
The slapt-getrc line:
SOURCE=http://slackware.uk/slint/x86_64/slint-testing/:PREFERRED
probably returns an error 404 repository not found using that source line.

Actually, in this line the URL is:
http://slackware.uk/slint/x86_64/slint-testing/

What follows, i.e.
PREFERRED is just a priority indicated to the slapt-get program


_______________________________________________
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list

--

_______________________________________________
Blinux-list mailing list
Blinux-list@redhat.com
https://www.redhat.com/mailman/listinfo/blinux-list

Reply via email to