Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #183082 > unrolled thread

Problems with apt in a clean stretch install.

Started by"Wayne Hartell" <w.hartell@ozemail.com.au>
First post2017-07-04 08:30 +0200
Last post2017-07-04 12:40 +0200
Articles 20 on this page of 35 — 11 participants

Back to article view | Back to linux.debian.user

Contents

  Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 08:30 +0200
    Re: Problems with apt in a clean stretch install. Dejan Jocic <jodejka@gmail.com> - 2017-07-04 09:10 +0200
      RE: Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 09:30 +0200
        Re: Problems with apt in a clean stretch install. Dejan Jocic <jodejka@gmail.com> - 2017-07-04 10:20 +0200
          RE: Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 11:40 +0200
            Re: Problems with apt in a clean stretch install. Norbert Kiszka <norbert@linux.pl> - 2017-07-04 11:50 +0200
              RE: Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 12:00 +0200
                Re: Problems with apt in a clean stretch install. Norbert Kiszka <norbert@linux.pl> - 2017-07-04 12:10 +0200
                  RE: Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 12:50 +0200
                    Re: Problems with apt in a clean stretch install. SDA <marathon.durandal@gmail.com> - 2017-07-04 13:00 +0200
                    Re: Problems with apt in a clean stretch install. SDA <marathon.durandal@gmail.com> - 2017-07-04 13:00 +0200
                      Re: Problems with apt in a clean stretch install. Phil Wyett <philwyett@kathenas.org> - 2017-07-04 13:20 +0200
                        Re: Problems with apt in a clean stretch install. Michael Lange <klappnase@freenet.de> - 2017-07-04 20:30 +0200
                      RE: Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 13:30 +0200
                        Re: Problems with apt in a clean stretch install. Phil Wyett <philwyett@kathenas.org> - 2017-07-04 13:40 +0200
                          RE: Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 16:30 +0200
                            Re: Problems with apt in a clean stretch install. Jason Wittlin-Cohen <jwittlincohen@gmail.com> - 2017-07-04 16:40 +0200
                            Re: Problems with apt in a clean stretch install. Michael Lange <klappnase@freenet.de> - 2017-07-04 20:40 +0200
                              Re: Problems with apt in a clean stretch install. Jimmy Johnson <field.engineer@gmail.com> - 2017-07-05 00:30 +0200
                        Re: Problems with apt in a clean stretch install. Phil Wyett <philwyett@kathenas.org> - 2017-07-04 13:50 +0200
                    Re: Problems with apt in a clean stretch install. Norbert Kiszka <norbert@linux.pl> - 2017-07-04 13:10 +0200
                      RE: Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 13:20 +0200
        Re: Problems with apt in a clean stretch install. Dejan Jocic <jodejka@gmail.com> - 2017-07-04 10:30 +0200
          RE: Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 11:40 +0200
    Re: Problems with apt in a clean stretch install. Felix Miata <mrmazda@earthlink.net> - 2017-07-04 10:20 +0200
      RE: Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 11:20 +0200
        Re: Problems with apt in a clean stretch install. Dejan Jocic <jodejka@gmail.com> - 2017-07-04 12:10 +0200
          Re: Problems with apt in a clean stretch install. Phil Wyett <philwyett@kathenas.org> - 2017-07-04 12:30 +0200
            Re: Problems with apt in a clean stretch install. Jimmy Johnson <field.engineer@gmail.com> - 2017-07-04 13:00 +0200
              RE: Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 13:20 +0200
                Re: Problems with apt in a clean stretch install. Jimmy Johnson <field.engineer@gmail.com> - 2017-07-04 14:20 +0200
            Re: Problems with apt in a clean stretch install. Frank <zuiderduin@gmx.com> - 2017-07-04 21:10 +0200
            Re: Problems with apt in a clean stretch install. Fungi4All <fungilife@protonmail.com> - 2017-07-05 01:20 +0200
          RE: Problems with apt in a clean stretch install. "Wayne Hartell" <w.hartell@ozemail.com.au> - 2017-07-04 13:20 +0200
        Re: Problems with apt in a clean stretch install. Michael Lange <klappnase@freenet.de> - 2017-07-04 12:40 +0200

Page 1 of 2  [1] 2  Next page →

#183082 — Problems with apt in a clean stretch install.

From"Wayne Hartell" <w.hartell@ozemail.com.au>
Date2017-07-04 08:30 +0200
SubjectProblems with apt in a clean stretch install.
Message-ID<tZpvr-4v6-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hi all,

 

I'm a Linux novice and have run into a problem with a clean Stretch install
and apt.

 

I started tinkering with Debian late in the game with Wheezy and have used
Jessie pretty much without problem. After setting up some new Stretch
systems (amd64) I am running into issues when using apt.

 

The first set of errors I get from apt when trying to run "update" are:

 

W: http://ftp.iinet.net.au/debian/debian/dists/stretch-updates/InRelease:
The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
not readable by user '_apt' executing apt-key.

W: http://ftp.iinet.net.au/debian/dists/stretch/Release.gpg: The key(s) in
the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by
user '_apt' executing apt-key.

W:
http://security.debian.org/debian-security/dists/stretch/updates/InRelease:
The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
not readable by user '_apt' executing apt-key.

 

I managed to solve<?> this error after checking that the permissions on
/etc/apt/trusted.gpg were 0600 and edited them to be 0644. (Is this the
correct default permission for the file trusted.gpg?)

 

After that, when I run apt-get update again, I get a list of errors about
errors occurring due to signature verification. 

e.g., "The repository is not updated and the previous index files will be
used. GPG error: http://ftp.iinet.net.au/debian/debian stretch-updates
InRelease: The following signatures couldn't be verified because the public
key is not available: NO_PUBKEY <key>

 

The above error is an abbreviated hand typed reproduction; not the actual
output. I can provide the full list of errors if it helps.

 

In another thread I read something about ensuring that the
"debian-archive-keyring" is installed, and it is, version 2017.5.

 

I just checked on second clean stretch install and it's the same situation;
same exact problems.

 

I am wondering what I might be doing wrong?

 

Regards,

Wayne.

[toc] | [next] | [standalone]

#183085

FromDejan Jocic <jodejka@gmail.com>
Date2017-07-04 09:10 +0200
Message-ID<tZq8a-51q-23@gated-at.bofh.it>
In reply to#183082
On 04-07-17, Wayne Hartell wrote:
> Hi all,
> 
>  
> 
> I'm a Linux novice and have run into a problem with a clean Stretch install
> and apt.
> 
>  
> 
> I started tinkering with Debian late in the game with Wheezy and have used
> Jessie pretty much without problem. After setting up some new Stretch
> systems (amd64) I am running into issues when using apt.
> 
>  
> 
> The first set of errors I get from apt when trying to run "update" are:
> 
>  
> 
> W: http://ftp.iinet.net.au/debian/debian/dists/stretch-updates/InRelease:
> The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
> not readable by user '_apt' executing apt-key.
> 
> W: http://ftp.iinet.net.au/debian/dists/stretch/Release.gpg: The key(s) in
> the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by
> user '_apt' executing apt-key.
> 
> W:
> http://security.debian.org/debian-security/dists/stretch/updates/InRelease:
> The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
> not readable by user '_apt' executing apt-key.
> 
>  
> 
> I managed to solve<?> this error after checking that the permissions on
> /etc/apt/trusted.gpg were 0600 and edited them to be 0644. (Is this the
> correct default permission for the file trusted.gpg?)
> 
>  
> 
> After that, when I run apt-get update again, I get a list of errors about
> errors occurring due to signature verification. 
> 
> e.g., "The repository is not updated and the previous index files will be
> used. GPG error: http://ftp.iinet.net.au/debian/debian stretch-updates
> InRelease: The following signatures couldn't be verified because the public
> key is not available: NO_PUBKEY <key>
> 
>  
> 
> The above error is an abbreviated hand typed reproduction; not the actual
> output. I can provide the full list of errors if it helps.
> 
>  
> 
> In another thread I read something about ensuring that the
> "debian-archive-keyring" is installed, and it is, version 2017.5.
> 
>  
> 
> I just checked on second clean stretch install and it's the same situation;
> same exact problems.
> 
>  
> 
> I am wondering what I might be doing wrong?
> 
>  
> 
> Regards,
> 
> Wayne.
> 
>  
> 
>  
> 

Did you try to change mirror you use in your sources.list?

[toc] | [prev] | [next] | [standalone]

#183087

From"Wayne Hartell" <w.hartell@ozemail.com.au>
Date2017-07-04 09:30 +0200
Message-ID<tZqrw-5a4-17@gated-at.bofh.it>
In reply to#183085
> On 04-07-17, Wayne Hartell wrote:
>> Hi all,
>> 
>>  
>> 
>> I'm a Linux novice and have run into a problem with a clean Stretch 
>> install and apt.
>> 
>>  
>> 
>> I started tinkering with Debian late in the game with Wheezy and have 
>> used Jessie pretty much without problem. After setting up some new 
>> Stretch systems (amd64) I am running into issues when using apt.
>> 
>>  
>> 
>> The first set of errors I get from apt when trying to run "update" are:
>> 
>>  
>> 
>> W: http://ftp.iinet.net.au/debian/debian/dists/stretch-updates/InRelease:
>> The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file 
>> is not readable by user '_apt' executing apt-key.
>> 
>> W: http://ftp.iinet.net.au/debian/dists/stretch/Release.gpg: The 
>> key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is 
>> not readable by user '_apt' executing apt-key.
>> 
>> W:
>>
http://security.debian.org/debian-security/dists/stretch/updates/InRelease:
>> The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file 
>> is not readable by user '_apt' executing apt-key.
>> 
>>  
>> 
>> I managed to solve<?> this error after checking that the permissions 
>> on /etc/apt/trusted.gpg were 0600 and edited them to be 0644. (Is this 
>> the correct default permission for the file trusted.gpg?)
>> 
>>  
>> 
>> After that, when I run apt-get update again, I get a list of errors 
>> about errors occurring due to signature verification.
>> 
>> e.g., "The repository is not updated and the previous index files will 
>> be used. GPG error: http://ftp.iinet.net.au/debian/debian 
>> stretch-updates
>> InRelease: The following signatures couldn't be verified because the 
>> public key is not available: NO_PUBKEY <key>
>> 
>>  
>> 
>> The above error is an abbreviated hand typed reproduction; not the 
>> actual output. I can provide the full list of errors if it helps.
>> 
>>  
>> 
>> In another thread I read something about ensuring that the 
>> "debian-archive-keyring" is installed, and it is, version 2017.5.
>> 
>>  
>> 
>> I just checked on second clean stretch install and it's the same 
>> situation; same exact problems.
>> 
>>  
>> 
>> I am wondering what I might be doing wrong?
>> 
>>  
>> 
>> Regards,
>> 
>> Wayne.
>
>Did you try to change mirror you use in your sources.list?
>

I did and it doesn't help (I get the same error with multiple different
sources).

GPG error: http://deb.debian.org/debian stretch-updates InRelease: The
following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010The
repository 'http://deb.debian.org/debian stretch-updates InRelease' is not
signed.Updating from such a repository can't be done securely, and is
therefore disabled by default.See apt-secure(8) manpage for repository
creation and user configuration details.

Notably, the keys (e.g., 8B48AD6246925553 and 7638D0442B90D010) ARE present
when I run 'apt-key list'.

When I search this forum for these keys (e.g., "8B48AD6246925553") I find
two threads with similar kinds of errors, but no solution on either. I'm
wondering whether I have fallen into some kind of crack perhaps.

I'm not sure why this is happening with all my fresh installs. I am
wondering whether the fact I used a local mirror (ftp.iinet.net.au) during
the install process has anything to do with it. I guess there is one way to
find out.

Another thing I'll mention that may or may not be relevant is that during
the installation I did not (and have not in the past) set up root, instead
preferring to use sudo.

I should also note that I read in another thread that Jimmy Johnson says:
"Also, if you used the live dvd it's screwing up apt gpg-keys and you will
not see updates until the keys are fixed.  ", but I didn't install from the
live DVD, I installed from the regular non live DVD, so I don't think this
is relevant.

In the meantime I guess I can experiment with different install
settings/approaches, but I'd rather, of course, find a way to fix an already
installed system.

Cheers.

[toc] | [prev] | [next] | [standalone]

#183092

FromDejan Jocic <jodejka@gmail.com>
Date2017-07-04 10:20 +0200
Message-ID<tZrdU-5Lm-21@gated-at.bofh.it>
In reply to#183087
On 04-07-17, Wayne Hartell wrote:
> >
> >Did you try to change mirror you use in your sources.list?
> >
> 
> I did and it doesn't help (I get the same error with multiple different
> sources).
> 
> GPG error: http://deb.debian.org/debian stretch-updates InRelease: The
> following signatures couldn't be verified because the public key is not
> available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010The
> repository 'http://deb.debian.org/debian stretch-updates InRelease' is not
> signed.Updating from such a repository can't be done securely, and is
> therefore disabled by default.See apt-secure(8) manpage for repository
> creation and user configuration details.
> 
> Notably, the keys (e.g., 8B48AD6246925553 and 7638D0442B90D010) ARE present
> when I run 'apt-key list'.
> 
> When I search this forum for these keys (e.g., "8B48AD6246925553") I find
> two threads with similar kinds of errors, but no solution on either. I'm
> wondering whether I have fallen into some kind of crack perhaps.
> 

Not sure that it will be helpful, but just a thought. How about
reinstalling debian-archive-keyring package?

[toc] | [prev] | [next] | [standalone]

#183098

From"Wayne Hartell" <w.hartell@ozemail.com.au>
Date2017-07-04 11:40 +0200
Message-ID<tZstk-6qV-33@gated-at.bofh.it>
In reply to#183092
> On 04-07-17, Wayne Hartell wrote:
> > >
> > >Did you try to change mirror you use in your sources.list?
> > >
> > 
> > I did and it doesn't help (I get the same error with multiple 
> > different sources).
> > 
> > GPG error: http://deb.debian.org/debian stretch-updates InRelease: The 
> > following signatures couldn't be verified because the public key is 
> > not
> > available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010The 
> > repository 'http://deb.debian.org/debian stretch-updates InRelease' is 
> > not signed.Updating from such a repository can't be done securely, and 
> > is therefore disabled by default.See apt-secure(8) manpage for 
> > repository creation and user configuration details.
> > 
> > Notably, the keys (e.g., 8B48AD6246925553 and 7638D0442B90D010) ARE 
> > present when I run 'apt-key list'.
> > 
> > When I search this forum for these keys (e.g., "8B48AD6246925553") I 
> > find two threads with similar kinds of errors, but no solution on 
> > either. I'm wondering whether I have fallen into some kind of crack
perhaps.
> > 
>
> Not sure that it will be helpful, but just a thought. How about
reinstalling debian-archive-keyring package?

That doesn't seem possible, I get:
"Reinstallation of debian-archive-keyring is not possible, it cannot be
downloaded."

I tried adding my installation DVD back into the sources, but apt rejects it
with the following:
"The repository 'cdrom://Debian GNU/Linux 9.0.0 _Stretch_ = Official amd64
DVD Binary-1 20170617-13:08] stretch Release' does not have a Release file."

[toc] | [prev] | [next] | [standalone]

#183099

FromNorbert Kiszka <norbert@linux.pl>
Date2017-07-04 11:50 +0200
Message-ID<tZsD0-6u0-21@gated-at.bofh.it>
In reply to#183098
Dnia 2017-07-04, wto o godzinie 19:02 +0930, Wayne Hartell pisze:
> > On 04-07-17, Wayne Hartell wrote:
> > > >
> > > >Did you try to change mirror you use in your sources.list?
> > > >
> > > 
> > > I did and it doesn't help (I get the same error with multiple 
> > > different sources).
> > > 
> > > GPG error: http://deb.debian.org/debian stretch-updates InRelease: The 
> > > following signatures couldn't be verified because the public key is 
> > > not
> > > available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010The 
> > > repository 'http://deb.debian.org/debian stretch-updates InRelease' is 
> > > not signed.Updating from such a repository can't be done securely, and 
> > > is therefore disabled by default.See apt-secure(8) manpage for 
> > > repository creation and user configuration details.
> > > 
> > > Notably, the keys (e.g., 8B48AD6246925553 and 7638D0442B90D010) ARE 
> > > present when I run 'apt-key list'.
> > > 
> > > When I search this forum for these keys (e.g., "8B48AD6246925553") I 
> > > find two threads with similar kinds of errors, but no solution on 
> > > either. I'm wondering whether I have fallen into some kind of crack
> perhaps.
> > > 
> >
> > Not sure that it will be helpful, but just a thought. How about
> reinstalling debian-archive-keyring package?
> 
> That doesn't seem possible, I get:
> "Reinstallation of debian-archive-keyring is not possible, it cannot be
> downloaded."
> 
> I tried adding my installation DVD back into the sources, but apt rejects it
> with the following:
> "The repository 'cdrom://Debian GNU/Linux 9.0.0 _Stretch_ = Official amd64
> DVD Binary-1 20170617-13:08] stretch Release' does not have a Release file."
> 


1. Comment out DVD repository from /etc/apt/sources.list (add # before
deb cdrom:...).
2. Try to # apt-get update
3. Check if it work. If not, manualy download latest
debian-archive-keyring for stretch (from repository) and install it like
this: #dpkg -i /path/to/debian-archive-keyring.deb and try again to make
update.

[toc] | [prev] | [next] | [standalone]

#183100

From"Wayne Hartell" <w.hartell@ozemail.com.au>
Date2017-07-04 12:00 +0200
Message-ID<tZsMG-6xj-15@gated-at.bofh.it>
In reply to#183099
> 1. Comment out DVD repository from /etc/apt/sources.list (add # before deb cdrom:...).
> 2. Try to # apt-get update
> 3. Check if it work. If not, manualy download latest debian-archive-keyring for stretch (from repository) and install it like
> this: #dpkg -i /path/to/debian-archive-keyring.deb and try again to make update.

I did this. Here is the full output in case I am missing something pertinent in my previous descriptions of the errors.

debianuser@masterdebian964:~/Documents$ sudo dpkg -i debian-archive-keyring_2017.5_all.deb
(Reading database ... 126483 files and directories currently installed.)
Preparing to unpack debian-archive-keyring_2017.5_all.deb ...
Unpacking debian-archive-keyring (2017.5) over (2017.5) ...
Setting up debian-archive-keyring (2017.5) ...
debianuser@masterdebian964:~/Documents$ sudo apt-get update
Ign:1 http://deb.debian.org/debian stretch InRelease
Ign:2 http://deb.debian.org/debian stretch/updates InRelease
Get:3 http://deb.debian.org/debian stretch-updates InRelease [88.5 kB]
Hit:4 http://deb.debian.org/debian stretch Release 
Ign:3 http://deb.debian.org/debian stretch-updates InRelease
Ign:5 http://deb.debian.org/debian stretch/updates Release
Get:6 http://deb.debian.org/debian stretch Release.gpg [3,108 B]
Ign:6 http://deb.debian.org/debian stretch Release.gpg
Ign:7 http://deb.debian.org/debian stretch/updates/main Sources
Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages
Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages
Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU
Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en
Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata
Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata
Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons
Ign:7 http://deb.debian.org/debian stretch/updates/main Sources
Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages
Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages
Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU
Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en
Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata
Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata
Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons
Ign:7 http://deb.debian.org/debian stretch/updates/main Sources
Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages
Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages
Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU
Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en
Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata
Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata
Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons
Ign:7 http://deb.debian.org/debian stretch/updates/main Sources
Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages
Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages
Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU
Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en
Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata
Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata
Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons
Ign:7 http://deb.debian.org/debian stretch/updates/main Sources
Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages
Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages
Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU
Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en
Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata
Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata
Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons
Err:7 http://deb.debian.org/debian stretch/updates/main Sources
  404  Not Found [IP: 52.85.41.44 80]
Ign:8 http://deb.debian.org/debian stretch/updates/main amd64 Packages
Ign:9 http://deb.debian.org/debian stretch/updates/main all Packages
Ign:10 http://deb.debian.org/debian stretch/updates/main Translation-en_AU
Ign:11 http://deb.debian.org/debian stretch/updates/main Translation-en
Ign:12 http://deb.debian.org/debian stretch/updates/main amd64 DEP-11 Metadata
Ign:13 http://deb.debian.org/debian stretch/updates/main all DEP-11 Metadata
Ign:14 http://deb.debian.org/debian stretch/updates/main DEP-11 64x64 Icons
Fetched 91.6 kB in 33s (2,733 B/s)
Reading package lists... Done
W: GPG error: http://deb.debian.org/debian stretch-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010
W: The repository 'http://deb.debian.org/debian stretch-updates InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'http://deb.debian.org/debian stretch/updates Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://deb.debian.org/debian stretch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
W: The repository 'http://deb.debian.org/debian stretch Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://deb.debian.org/debian/dists/stretch/updates/main/source/Sources  404  Not Found [IP: 52.85.41.44 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

[toc] | [prev] | [next] | [standalone]

#183102

FromNorbert Kiszka <norbert@linux.pl>
Date2017-07-04 12:10 +0200
Message-ID<tZsWm-6Q1-3@gated-at.bofh.it>
In reply to#183100
> W: GPG error: http://deb.debian.org/debian stretch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
> W: The repository 'http://deb.debian.org/debian stretch Release' is not signed.
> N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
> N: See apt-secure(8) manpage for repository creation and user configuration details.
> E: Failed to fetch http://deb.debian.org/debian/dists/stretch/updates/main/source/Sources  404  Not Found [IP: 52.85.41.44 80]
> E: Some index files failed to download. They have been ignored, or old ones used instead.
> 
> 

Read this:

https://unix.stackexchange.com/questions/75807/no-public-key-available-on-apt-get-update

[toc] | [prev] | [next] | [standalone]

#183107

From"Wayne Hartell" <w.hartell@ozemail.com.au>
Date2017-07-04 12:50 +0200
Message-ID<tZtz4-76W-25@gated-at.bofh.it>
In reply to#183102
> > W: GPG error: http://deb.debian.org/debian stretch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1 NO_PUBKEY EF0F382A1A7B6500
> > W: The repository 'http://deb.debian.org/debian stretch Release' is not signed.
> > N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
> > N: See apt-secure(8) manpage for repository creation and user configuration details.
> > E: Failed to fetch http://deb.debian.org/debian/dists/stretch/updates/main/source/Sources  404  Not Found [IP: 52.85.41.44 80]
> > E: Some index files failed to download. They have been ignored, or old ones used instead.
> > 
> > 
>
> Read this:
>
> https://unix.stackexchange.com/questions/75807/no-public-key-available-on-apt-get-update
>

Thanks. Yeah I have tried importing keys (even though they already exist as confirmed with 'apt-key list' and it makes no difference. All the keys complained about are already present.

I don't have enough experience nor understanding of Linux to know whether it's a bug or dumb user and though I suspect the latter, I feel like there's a chance it could be the former.

[toc] | [prev] | [next] | [standalone]

#183108

FromSDA <marathon.durandal@gmail.com>
Date2017-07-04 13:00 +0200
Message-ID<tZtIJ-7a9-5@gated-at.bofh.it>
In reply to#183107
On Tue, Jul 04, 2017 at 08:17:53PM +0930, Wayne Hartell wrote:
> Thanks. Yeah I have tried importing keys (even though they already exist 
> as confirmed with 'apt-key list' and it makes no difference. All the keys 
> complained about are already present.
> 
> I don't have enough experience nor understanding of Linux to know whether it's a bug or dumb user and though I suspect the latter, I feel like there's a chance it could be the former.

Did you try Phil Hartnell's suggestion? It sounds promising - In fact I had 
this exact issue on a relatives computer, and I'm going to try his 
suggestion later on. The sequence of events he describes sounds relevant to 
the situation I experienced, so worth a shot methinks. Please advise us how 
it goes.

[toc] | [prev] | [next] | [standalone]

#183109

FromSDA <marathon.durandal@gmail.com>
Date2017-07-04 13:00 +0200
Message-ID<tZtIK-7a9-15@gated-at.bofh.it>
In reply to#183107
On Tue, Jul 04, 2017 at 08:17:53PM +0930, Wayne Hartell wrote:

Er ... sorry that last email should read ".... Phil Wyett's suggestion" in 
this thread.

[toc] | [prev] | [next] | [standalone]

#183115

FromPhil Wyett <philwyett@kathenas.org>
Date2017-07-04 13:20 +0200
Message-ID<tZu25-7w6-5@gated-at.bofh.it>
In reply to#183109

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2017-07-04 at 06:56 -0400, SDA wrote:
> On Tue, Jul 04, 2017 at 08:17:53PM +0930, Wayne Hartell wrote:
> 
> Er ... sorry that last email should read ".... Phil Wyett's
> suggestion" in 
> this thread. 
> 

Hi,

Additional info. Why via synaptic the 'trusted.gpg' file is being
created needs investigation.

The file is a 32 byte file (way to small to be a valid key) is not
even viewable by normal key view methods i.e.

gpg -k /etc/apt/trusted.gpg

or

gpg -K /etc/apt/trusted.gpg

/me has the feeling the file is just garbage.

Regards

Phil

-- 
Playing the game for the games sake.

Web: https://kathenas.org

Twitter: kathenasorg

Instagram: kathenasorg

[toc] | [prev] | [next] | [standalone]

#183138

FromMichael Lange <klappnase@freenet.de>
Date2017-07-04 20:30 +0200
Message-ID<tZAKd-3xa-1@gated-at.bofh.it>
In reply to#183115
On Tue, 04 Jul 2017 12:19:24 +0100
Phil Wyett <philwyett@kathenas.org> wrote:


> Additional info. Why via synaptic the 'trusted.gpg' file is being
> created needs investigation.
> 
> The file is a 32 byte file (way to small to be a valid key) is not
> even viewable by normal key view methods i.e.
> 

Here it is 7.1 kB.

(...)
> /me has the feeling the file is just garbage.

I don't think so, quoting https://wiki.debian.org/SecureApt :

"apt-key is a program that is used to manage a keyring of gpg keys for
secure apt. The keyring is kept in the file /etc/apt/trusted.gpg (not to
be confused with the related but not very
interesting /etc/apt/trustdb.gpg). apt-key can be used to show the keys
in the keyring, and to add or remove a key. In more recent Debian
GNU/Linux versions (Wheezy, for example), the keyrings are stored in
specific files all located in the /etc/apt/trusted.gpg.d directory. For
example, that directory could contain the following files:
debian-archive-squeeze-automatic.gpg or
debian-archive-wheezy-automatic.gpg. Incidentally, both files are
provided by the debian-archive-keyring package. "

So apparently, if you have any keys added to the apt keyring that don't
appear in /etc/apt/trusted.gpg.d/ they went into trusted.gpg . The keys
included in any of these files can be queried with
# apt-key list 
Here the file includes five keys.

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

There's a way out of any cage.
		-- Captain Christopher Pike, "The Menagerie" ("The Cage"),
		   stardate unknown.

[toc] | [prev] | [next] | [standalone]

#183117

From"Wayne Hartell" <w.hartell@ozemail.com.au>
Date2017-07-04 13:30 +0200
Message-ID<tZubL-7zh-5@gated-at.bofh.it>
In reply to#183109
> Er ... sorry that last email should read ".... Phil Wyett's suggestion" in
this thread. 

Yes, trying Phil's suggestion and will report back once I have had the time
to explore it properly (several systems now exhibiting this problem). As a
teaser, it seems that even software-properties-gtk creates the trusted.gpg
file, but even with that file deleted (as per Phil) and sticking to the
terminal and apt-get, I get the same key related errors. In fact if I use
software-properties-gtk it seems to jam up on "Refeshing software cache"...
has been going on one machine now over 30 minutes.

[toc] | [prev] | [next] | [standalone]

#183118

FromPhil Wyett <philwyett@kathenas.org>
Date2017-07-04 13:40 +0200
Message-ID<tZuls-7Dd-19@gated-at.bofh.it>
In reply to#183117

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2017-07-04 at 20:50 +0930, Wayne Hartell wrote:
> > Er ... sorry that last email should read ".... Phil Wyett's
> > suggestion" in
> 
> this thread. 
> 
> Yes, trying Phil's suggestion and will report back once I have had
> the time
> to explore it properly (several systems now exhibiting this
> problem). As a
> teaser, it seems that even software-properties-gtk creates the
> trusted.gpg
> file, but even with that file deleted (as per Phil) and sticking to
> the
> terminal and apt-get, I get the same key related errors. In fact if
> I use
> software-properties-gtk it seems to jam up on "Refeshing software
> cache"...
> has been going on one machine now over 30 minutes.
> 


Hi,

I do not use the main server. I switched 'software-properties-gtk' to
use it and I also get a hang at the what seems the end of the 'reload'
process. In the terminal I see:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-
packages/softwareproperties/gtk/DialogCacheOutdated.py", line 86, in
on_pktask_finish
    results = self._pktask.generic_finish(result)
GLib.Error: pk-client-error-quark: E: The repository 'http://deb.debia
n.org/debian stretch/updates Release' does not have a Release file.
W: Updating from such a repository can't be done securely, and is
therefore disabled by default.
W: See apt-secure(8) manpage for repository creation and user
configuration details.
 (319)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-
packages/softwareproperties/gtk/DialogCacheOutdated.py", line 89, in
on_pktask_finish
    Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line
326, in new_init
    return super_init_func(self, **new_kwargs)
  File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 537,
in __init__
    self._init(*args, **new_kwargs)
  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line
326, in new_init
    return super_init_func(self, **new_kwargs)
  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line
326, in new_init
    return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow

Using a mirror such as bytemark.co.uk, results in no issues here.



Regards

Phil

-- 
Playing the game for the games sake.

Web: https://kathenas.org

Twitter: kathenasorg

Instagram: kathenasorg

[toc] | [prev] | [next] | [standalone]

#183123

From"Wayne Hartell" <w.hartell@ozemail.com.au>
Date2017-07-04 16:30 +0200
Message-ID<tZwZZ-UF-25@gated-at.bofh.it>
In reply to#183118
> On Tue, 2017-07-04 at 20:50 +0930, Wayne Hartell wrote:
> > > Er ... sorry that last email should read ".... Phil Wyett's 
> > > suggestion" in
> > 
> > this thread.
> > 
> > Yes, trying Phil's suggestion and will report back once I have had the 
> > time to explore it properly (several systems now exhibiting this 
> > problem). As a teaser, it seems that even software-properties-gtk 
> > creates the trusted.gpg file, but even with that file deleted (as per 
> > Phil) and sticking to the terminal and apt-get, I get the same key 
> > related errors. In fact if I use software-properties-gtk it seems to 
> > jam up on "Refeshing software cache"...
> > has been going on one machine now over 30 minutes.
> > 
>
>
> Hi,
>
> I do not use the main server. I switched 'software-properties-gtk' to use it and I also get a hang at the what seems the end of the 'reload'
> process. In the terminal I see:
>
> Traceback (most recent call last):
>  File "/usr/lib/python3/dist-
> packages/softwareproperties/gtk/DialogCacheOutdated.py", line 86, in on_pktask_finish
>    results = self._pktask.generic_finish(result)
> GLib.Error: pk-client-error-quark: E: The repository 'http://deb.debia n.org/debian stretch/updates Release' does not have a Release file.
> W: Updating from such a repository can't be done securely, and is therefore disabled by default.
> W: See apt-secure(8) manpage for repository creation and user configuration details.
> (319)
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>  File "/usr/lib/python3/dist-
> packages/softwareproperties/gtk/DialogCacheOutdated.py", line 89, in on_pktask_finish
>    Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
>  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 326, in new_init
>    return super_init_func(self, **new_kwargs)
>  File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 537, in __init__
>    self._init(*args, **new_kwargs)
>  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 326, in new_init
>    return super_init_func(self, **new_kwargs)
>  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 326, in new_init
>    return super_init_func(self, **new_kwargs)
> TypeError: could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow
>
> Using a mirror such as bytemark.co.uk, results in no issues here.
>
>
>
> Regards
>
> Phil

I double checked here whether trusted.gpg is created or not when I use 'software-properties-gtk' and it definitely is. When that file is present, however, I get the errors related to being unable to read it, plus all the other errors remain, even when using the same server as you are using.

FYI - I see the same exceptions as you in the terminal when running 'software-properties-gtk'.

On a laptop that I have set up for my wife (time to get her into Debian!) I was able to solve the issue just now by doing the following:

1. sudo -rm -f /etc/apt/trusted.gpg
	[Thanks for this step!]
2. sudo apt-get update
	[generated errors]
	Err:15 http://ftp.iinet.net.au/debian/debian stretch/updates/non-free Sources
		404 Not Found
		[Perhaps this expected with non-free sources]
	A bunch of stuff (only seen on this laptop) about 'Symlinking final file /var/lib/apt/lists <...> failed - pkgAcqIndex::StageDownloadDone (17: File exists)
	The repository 'http://ftp.iinet.net.au/debian/debian stretch/updates Release' does not have a Release file.
	Failed to fetch http://ftp.iinet.net.au/debian/dists/stretch/updates/non-free/source/Sources 404 Not Found
	But this time NO public key errors, which is weird because they were definitely happening earlier on this machine.
3. /var/lib/apt/lists$ sudo rm -r -f *
	[This was mentioned by Dejan Jocic earlier, but the thread didn't lead to a solution. I tried it this time due to the Symlinking errors I was seeing on this particular laptop.]
4. sudo apt-get update
	[generated errors]
	Err:16 http://ftp.iinet.net.au/debian/debian stretch/updates/non-free Sources
		404 Not Found
	The repository 'http://ftp.iinet.net.au/debian/debian stretch/updates Release' does not have a Release file.
	Failed to fetch http://ftp.iinet.net.au/debian/dists/stretch/updates/non-free/source/Sources 404 Not Found
5.  sudo apt-get upgrade
	0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
6. So then I tried changed sources.list to that found here:
https://wiki.debian.org/SourcesList

Running sudo apt-get upgrade now produces no errors at all.

Running sudo apt-get update now shows that there is one package that will be upgraded (libcrypt20).

Unfortunately, following these steps (1, 3 and 6) on my other machine does not work. I still get public key errors.

I guess it's quite possible that with my messing around trying to import public keys that I have killed something on that machine. On my wife's laptop I didn't do anything other than the above steps.

Being a novice I am unable to figure out what all this means in terms of a full explanation/diagnosis other than perhaps there being an issue with some mirrors?, but for the time being I am happy that my wife's machine is working. I will try these steps on another Stretch laptop that I have shortly.

The first machine that seems to be toast is a VM and not a big deal. I will try installing from the RC3 DVD (as per Jimmy) or upgrading from 8.8 instead.

Regards,
Wayne.

[toc] | [prev] | [next] | [standalone]

#183125

FromJason Wittlin-Cohen <jwittlincohen@gmail.com>
Date2017-07-04 16:40 +0200
Message-ID<tZx9E-12c-17@gated-at.bofh.it>
In reply to#183123

[Multipart message — attachments visible in raw view] — view raw

Hi Wayne,

I ran into the same issue with trusted.gpg.  I opened the file in nano and
it was completely empty.  My guess is that apt is looking to this file for
the public keys of the various servers, and it complains when it can't find
them.  In fact, the keys are stored in the /etc/apt/trusted.gpg.d/.  The
relevant files are debian-archive-stretch-automatic.gpg
and debian-archive-stretch-security-automatic.gpg.  When you have an empty
trusted.gpg file in /etc/apt, it appears to ignore the
/etc/apt/trusted.gpg.d directory.   Deleting the empty trusted.gpg file
resolved the issue for me.   Importing the public keys manually isn't
helping because apt is looking to the wrong location for the public keys.

Jason

On Tue, Jul 4, 2017 at 10:28 AM, Wayne Hartell <w.hartell@ozemail.com.au>
wrote:

> > On Tue, 2017-07-04 at 20:50 +0930, Wayne Hartell wrote:
> > > > Er ... sorry that last email should read ".... Phil Wyett's
> > > > suggestion" in
> > >
> > > this thread.
> > >
> > > Yes, trying Phil's suggestion and will report back once I have had the
> > > time to explore it properly (several systems now exhibiting this
> > > problem). As a teaser, it seems that even software-properties-gtk
> > > creates the trusted.gpg file, but even with that file deleted (as per
> > > Phil) and sticking to the terminal and apt-get, I get the same key
> > > related errors. In fact if I use software-properties-gtk it seems to
> > > jam up on "Refeshing software cache"...
> > > has been going on one machine now over 30 minutes.
> > >
> >
> >
> > Hi,
> >
> > I do not use the main server. I switched 'software-properties-gtk' to
> use it and I also get a hang at the what seems the end of the 'reload'
> > process. In the terminal I see:
> >
> > Traceback (most recent call last):
> >  File "/usr/lib/python3/dist-
> > packages/softwareproperties/gtk/DialogCacheOutdated.py", line 86, in
> on_pktask_finish
> >    results = self._pktask.generic_finish(result)
> > GLib.Error: pk-client-error-quark: E: The repository 'http://deb.debia
> n.org/debian stretch/updates Release' does not have a Release file.
> > W: Updating from such a repository can't be done securely, and is
> therefore disabled by default.
> > W: See apt-secure(8) manpage for repository creation and user
> configuration details.
> > (319)
> >
> > During handling of the above exception, another exception occurred:
> >
> > Traceback (most recent call last):
> >  File "/usr/lib/python3/dist-
> > packages/softwareproperties/gtk/DialogCacheOutdated.py", line 89, in
> on_pktask_finish
> >    Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
> >  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line
> 326, in new_init
> >    return super_init_func(self, **new_kwargs)
> >  File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 537,
> in __init__
> >    self._init(*args, **new_kwargs)
> >  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line
> 326, in new_init
> >    return super_init_func(self, **new_kwargs)
> >  File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line
> 326, in new_init
> >    return super_init_func(self, **new_kwargs)
> > TypeError: could not convert value for property `transient_for' from
> DialogCacheOutdated to GtkWindow
> >
> > Using a mirror such as bytemark.co.uk, results in no issues here.
> >
> >
> >
> > Regards
> >
> > Phil
>
> I double checked here whether trusted.gpg is created or not when I use
> 'software-properties-gtk' and it definitely is. When that file is present,
> however, I get the errors related to being unable to read it, plus all the
> other errors remain, even when using the same server as you are using.
>
> FYI - I see the same exceptions as you in the terminal when running
> 'software-properties-gtk'.
>
> On a laptop that I have set up for my wife (time to get her into Debian!)
> I was able to solve the issue just now by doing the following:
>
> 1. sudo -rm -f /etc/apt/trusted.gpg
>         [Thanks for this step!]
> 2. sudo apt-get update
>         [generated errors]
>         Err:15 http://ftp.iinet.net.au/debian/debian
> stretch/updates/non-free Sources
>                 404 Not Found
>                 [Perhaps this expected with non-free sources]
>         A bunch of stuff (only seen on this laptop) about 'Symlinking
> final file /var/lib/apt/lists <...> failed - pkgAcqIndex::StageDownloadDone
> (17: File exists)
>         The repository 'http://ftp.iinet.net.au/debian/debian
> stretch/updates Release' does not have a Release file.
>         Failed to fetch http://ftp.iinet.net.au/
> debian/dists/stretch/updates/non-free/source/Sources 404 Not Found
>         But this time NO public key errors, which is weird because they
> were definitely happening earlier on this machine.
> 3. /var/lib/apt/lists$ sudo rm -r -f *
>         [This was mentioned by Dejan Jocic earlier, but the thread didn't
> lead to a solution. I tried it this time due to the Symlinking errors I was
> seeing on this particular laptop.]
> 4. sudo apt-get update
>         [generated errors]
>         Err:16 http://ftp.iinet.net.au/debian/debian
> stretch/updates/non-free Sources
>                 404 Not Found
>         The repository 'http://ftp.iinet.net.au/debian/debian
> stretch/updates Release' does not have a Release file.
>         Failed to fetch http://ftp.iinet.net.au/
> debian/dists/stretch/updates/non-free/source/Sources 404 Not Found
> 5.  sudo apt-get upgrade
>         0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 6. So then I tried changed sources.list to that found here:
> https://wiki.debian.org/SourcesList
>
> Running sudo apt-get upgrade now produces no errors at all.
>
> Running sudo apt-get update now shows that there is one package that will
> be upgraded (libcrypt20).
>
> Unfortunately, following these steps (1, 3 and 6) on my other machine does
> not work. I still get public key errors.
>
> I guess it's quite possible that with my messing around trying to import
> public keys that I have killed something on that machine. On my wife's
> laptop I didn't do anything other than the above steps.
>
> Being a novice I am unable to figure out what all this means in terms of a
> full explanation/diagnosis other than perhaps there being an issue with
> some mirrors?, but for the time being I am happy that my wife's machine is
> working. I will try these steps on another Stretch laptop that I have
> shortly.
>
> The first machine that seems to be toast is a VM and not a big deal. I
> will try installing from the RC3 DVD (as per Jimmy) or upgrading from 8.8
> instead.
>
> Regards,
> Wayne.
>
>
>

[toc] | [prev] | [next] | [standalone]

#183140

FromMichael Lange <klappnase@freenet.de>
Date2017-07-04 20:40 +0200
Message-ID<tZATT-3Aa-5@gated-at.bofh.it>
In reply to#183123
Hi,

On Tue, 4 Jul 2017 23:58:17 +0930
"Wayne Hartell" <w.hartell@ozemail.com.au> wrote:

I did not read this last post or the whole thread very carefully, but
now something hit my eyes:


> 4. sudo apt-get update
> 	[generated errors]
> 	Err:16 http://ftp.iinet.net.au/debian/debian
> stretch/updates/non-free Sources 404 Not Found
       ^^^^
Shouldn't this be stretch-updates?
Not sure how this is related to the problem you described in the first
place, though.

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Worlds are conquered, galaxies destroyed -- but a woman is always a woman.
		-- Kirk, "The Conscience of the King", stardate 2818.9

[toc] | [prev] | [next] | [standalone]

#183150

FromJimmy Johnson <field.engineer@gmail.com>
Date2017-07-05 00:30 +0200
Message-ID<tZEut-61x-7@gated-at.bofh.it>
In reply to#183140
On 07/04/2017 11:28 AM, Michael Lange wrote:
> Hi,
> 
> On Tue, 4 Jul 2017 23:58:17 +0930
> "Wayne Hartell" <w.hartell@ozemail.com.au> wrote:
> 
> I did not read this last post or the whole thread very carefully, but
> now something hit my eyes:
> 
> 
>> 4. sudo apt-get update
>> 	[generated errors]
>> 	Err:16 http://ftp.iinet.net.au/debian/debian
>> stretch/updates/non-free Sources 404 Not Found
>         ^^^^
> Shouldn't this be stretch-updates?
> Not sure how this is related to the problem you described in the first
> place, though.
> 
> Regards
> 
> Michael

I thought it was only the live-dvd, apparently other dvd installers are 
bad too. "I recommend using the RC3 installer".
-- 
Jimmy Johnson

Ubuntu 14.04 LTS - KDE 4.13.2 - Intel G3220 - EXT4 at sda5
Registered Linux User #380263

[toc] | [prev] | [next] | [standalone]

#183120

FromPhil Wyett <philwyett@kathenas.org>
Date2017-07-04 13:50 +0200
Message-ID<tZuv8-7I0-11@gated-at.bofh.it>
In reply to#183117

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2017-07-04 at 20:50 +0930, Wayne Hartell wrote:
> > Er ... sorry that last email should read ".... Phil Wyett's
> > suggestion" in
> 
> this thread. 
> 
> Yes, trying Phil's suggestion and will report back once I have had
> the time
> to explore it properly (several systems now exhibiting this
> problem). As a
> teaser, it seems that even software-properties-gtk creates the
> trusted.gpg
> file, but even with that file deleted (as per Phil) and sticking to
> the
> terminal and apt-get, I get the same key related errors. In fact if
> I use
> software-properties-gtk it seems to jam up on "Refeshing software
> cache"...
> has been going on one machine now over 30 minutes.
> 

Hi,

When running 'software-properties-gtk' you may see:

gpg: keyblock resource '/etc/apt/trusted.gpg': Permission denied

in the terminal, but I see no creation of the file here.

Regards

Phil

-- 
Playing the game for the games sake.

Web: https://kathenas.org

Twitter: kathenasorg

Instagram: kathenasorg

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web