On Wed 05 Jul 2017 at 11:10:44 (+0200), Michael Lange wrote:
> Hi,
>
> I'm glad you could finally fix the issue.
>
> On Wed, 5 Jul 2017 12:15:33 +0930
> "Wayne Hartell" wrote:
>
> > I know I just wrote a long e-mail on this, but I think I just figured
> > out in my own mind exactly what is goin
Hi,
I'm glad you could finally fix the issue.
On Wed, 5 Jul 2017 12:15:33 +0930
"Wayne Hartell" wrote:
> I know I just wrote a long e-mail on this, but I think I just figured
> out in my own mind exactly what is going on and wanted to document it.
>
>
>
> As others have said the /etc/apt/tr
On 05-07-17, Wayne Hartell wrote:
>
> Fungi4All wrote:
> > And this for the OP:
> > 1 But if there is such a basic problem with installation what is
> > so different that the rest of the new stretch installers did not
> > face?
> >
>
> That's a good question. I'm not 100% sure what the problem w
I know I just wrote a long e-mail on this, but I think I just figured out in
my own mind exactly what is going on and wanted to document it.
As others have said the /etc/apt/trusted.gpg file is the issue.
It seems that what is happening is this:
1. For some reason the first use of
Firstly, thanks to all of those who have participated in this thread.
I have some follow up comments and responses. This is a long reply, so the
executive summary is that I managed to solve the issues on all my Stretch
systems. There is a main issue and some kindred issues that manifest under
diff
> From: philwy...@kathenas.org
> This issue seems to be created by "synaptic".
> If you you "apt" in the terminal, you will be fine.
As mindblowing as this topic seems to be I can not help but
comment your response. It seems you must have not read
90% of the thread missing out on all the output an
On 07/04/2017 11:28 AM, Michael Lange wrote:
Hi,
On Tue, 4 Jul 2017 23:58:17 +0930
"Wayne Hartell" 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
Op 04-07-17 om 12:23 schreef Phil Wyett:
This issue seems to be created by 'synaptic'.
If you you 'apt' in the terminal, you will be fine.
If you use 'software-properties-gtk' to adjust repositories, you will
be fine.
The issue is created if you run 'synaptic' and then adjust
repositories via
Hi,
On Tue, 4 Jul 2017 23:58:17 +0930
"Wayne Hartell" 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 Sour
On Tue, 04 Jul 2017 12:19:24 +0100
Phil Wyett 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.
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.gp
> 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 n
On 07/04/2017 04:15 AM, Wayne Hartell wrote:
The OP did not say, but I believe the problem is coming from a 9.1-live-dvd
install, I had to same problem using it. The problem does not occur using the
net-install. I have not tested any other installers but the rc3-live did not seem
to have the p
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 t
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 t
> 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 creat
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
> > > Read this:
> > >
> > > https://unix.stackexchange.com/questions/75807/no-public-key-availab
> > > le-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
> > co
> The OP did not say, but I believe the problem is coming from a 9.1-live-dvd
> install, I had to same problem using it. The problem does not occur using the
> net-install. I have not tested any other installers but the rc3-live did not
> seem to have the problem, cause I > used it and installed
> Out of the head, but you did check install media with MD5 or SHA sums?
> Also, many people did do clean install of Jessie. Though, it is annoying
bug for sure. But it is probably not so widespread. Perhaps you could give
it a shot on a clean install with root enabled from start, you can always
al
> > 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 alre
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.
On 07/04/2017 03:23 AM, Phil Wyett wrote:
On Tue, 2017-07-04 at 12:02 +0200, Dejan Jocic wrote:
On 04-07-17, Wayne Hartell wrote:
Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930):
...I managed to solve this error after checking that the
permissions on /etc/apt/trusted.gpg were 0600 and e
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 und
> > 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 'ht
Hi,
On Tue, 4 Jul 2017 18:47:14 +0930
"Wayne Hartell" wrote:
> > Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930):
> >
> > > ...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
On Tue, 2017-07-04 at 12:02 +0200, Dejan Jocic wrote:
> On 04-07-17, Wayne Hartell wrote:
> > > Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930):
> > >
> > > > ...I managed to solve this error after checking that the
> > > > permissions on /etc/apt/trusted.gpg were 0600 and edited them
> > >
> 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.d
On 04-07-17, Wayne Hartell wrote:
> > Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930):
> >
> > > ...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
> 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-keyrin
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).
> > >
> >
> 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
> > follow
>How about this solution, it worked in similar case:
>
> https://lists.debian.org/debian-user/2017/05/msg00467.html
I saw that discussion earlier, but if you follow the thread through you'll
note that the claim of "solution" was a false alarm.
I will give it a try none the less, since I am clutc
> Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930):
>
> > ...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?)...
>
> I have to guess 644 i
How about this solution, it worked in similar case:
https://lists.debian.org/debian-user/2017/05/msg00467.html
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'
Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930):
> ...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?)...
I have to guess 644 is correct, as
> 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
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 Stret
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 a
40 matches
Mail list logo
