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.

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 2 of 2 — ← Prev page 1 [2]

#183112

> > 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.
> 

Hmmm I use Jessie for last years, with no any experience with Strech
yet. But I feel you have some problem(s) with sources.list or with apt
file(s) privileges somehow/somewhere.

In this link before, there is something more - did You try to install
debian-keyring (before was debian-archive-keyring)?

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

#183116

> > > 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 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.
> > 
>
> Hmmm I use Jessie for last years, with no any experience with Strech yet. But I feel you have some problem(s) with sources.list or with apt
> file(s) privileges somehow/somewhere.
>
> In this link before, there is something more - did You try to install debian-keyring (before was debian-archive-keyring)?

I had no problems under Jessie and have used it on multiple systems. This seems to be a new issue with Stretch.

There doesn't seem to be a debian-keyring package under stretch (only debian-archive-keyring).

I'm following some other leads and will report back how I go. I do very much appreciate your assistance.

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

#183094

How about this solution, it worked in similar case:

https://lists.debian.org/debian-user/2017/05/msg00467.html

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

#183097

>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 clutching at straws now. 

FYI - I just tested a brand new clean install, this time NOT using a local
mirror during installation and it's the same problems again. I have to
conclude that there's something wrong with the installation, at least for
the combination of options I am choosing. I may have to go back to Jessie
where I never had these kinds of problems. 

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

#183091

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 that is what is set on the Stretch I have
booted currently (as are all regular files in /etc/apt/), and I've never touched
it myself.

Do you get the same errors running 'apt update' instead of 'apt-get update'?
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

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

#183095

> 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 that is what is set on the Stretch I have booted currently (as are all regular files in /etc/apt/), and I've never touched it myself.
>
> Do you get the same errors running 'apt update' instead of 'apt-get update'?

Yes, it seems that I get the same errors that way too.

I tried a new clean install test and seem to end up with permissions under /etc/apt/ always as 0600, so I am not sure what is going on. Looks like an issue with a clean install, but I am wondering why it's not coming up more often (unless most people are upgrading from Jessie).

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

#183103

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
> > > trusted.gpg?)...
> >
> > I have to guess 644 is correct, as that is what is set on the
> > Stretch I have booted currently (as are all regular files in
> > /etc/apt/), and I've never touched it myself.
> >
> > Do you get the same errors running 'apt update' instead of 'apt-get
> > update'?
> 
> Yes, it seems that I get the same errors that way too.
> 
> I tried a new clean install test and seem to end up with permissions
> under /etc/apt/ always as 0600, so I am not sure what is going on.
> Looks like an issue with a clean install, but I am wondering why it's
> not coming up more often (unless most people are upgrading from
> Jessie).
> 
> 
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 allow sudo for your user after that?

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

#183104

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

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
> > > > to
> > > > be 0644. (Is this the correct default permission for the file
> > > > trusted.gpg?)...
> > > 
> > > I have to guess 644 is correct, as that is what is set on the
> > > Stretch I have booted currently (as are all regular files in
> > > /etc/apt/), and I've never touched it myself.
> > > 
> > > Do you get the same errors running 'apt update' instead of 'apt-
> > > get
> > > update'?
> > 
> > Yes, it seems that I get the same errors that way too.
> > 
> > I tried a new clean install test and seem to end up with
> > permissions
> > under /etc/apt/ always as 0600, so I am not sure what is going on.
> > Looks like an issue with a clean install, but I am wondering why
> > it's
> > not coming up more often (unless most people are upgrading from
> > Jessie).
> > 
> > 
> 
> 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 allow sudo for your user after that?
> 
> 

Hi all,

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 'Settings -> Repositories. A soon as you do this a
file '/etc/apt/trusted.gpg' is created and it is this that is throwing
everything off.

Output:

philwyett@ks-skywalker:~$ synaptic-pkexec 
ERROR:root:Cannot import UbuntuDrivers: No module named
'UbuntuDrivers'
gpg: keybox '/etc/apt/trusted.gpg' created
ERROR:root:Cannot import UbuntuDrivers: No module named
'UbuntuDrivers'
gpg: keybox '/etc/apt/trusted.gpg' created

It is the last line that is the issue. If you run 'software-
properties-gtk' and adjust repositories, the file is not created.

Quick remedy:

sudo rm -f /etc/apt/trusted.gpg

Now run 'synaptic' or 'apt' as usual. If you run 'synaptic', do not
use the menu option 'Settings -> Repositories.

This could probably do with a bug raising.

Regards

Phil

-- 
Playing the game for the games sake.

Web: https://kathenas.org

Twitter: kathenasorg

Instagram: kathenasorg

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

#183110

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 edited them
>>>>> to
>>>>> be 0644. (Is this the correct default permission for the file
>>>>> trusted.gpg?)...
>>>>
>>>> I have to guess 644 is correct, as that is what is set on the
>>>> Stretch I have booted currently (as are all regular files in
>>>> /etc/apt/), and I've never touched it myself.
>>>>
>>>> Do you get the same errors running 'apt update' instead of 'apt-
>>>> get
>>>> update'?
>>>
>>> Yes, it seems that I get the same errors that way too.
>>>
>>> I tried a new clean install test and seem to end up with
>>> permissions
>>> under /etc/apt/ always as 0600, so I am not sure what is going on.
>>> Looks like an issue with a clean install, but I am wondering why
>>> it's
>>> not coming up more often (unless most people are upgrading from
>>> Jessie).
>>>
>>>
>>
>> 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 allow sudo for your user after that?
>>
>>
>
> Hi all,
>
> 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 'Settings -> Repositories. A soon as you do this a
> file '/etc/apt/trusted.gpg' is created and it is this that is throwing
> everything off.
>
> Output:
>
> philwyett@ks-skywalker:~$ synaptic-pkexec
> ERROR:root:Cannot import UbuntuDrivers: No module named
> 'UbuntuDrivers'
> gpg: keybox '/etc/apt/trusted.gpg' created
> ERROR:root:Cannot import UbuntuDrivers: No module named
> 'UbuntuDrivers'
> gpg: keybox '/etc/apt/trusted.gpg' created
>
> It is the last line that is the issue. If you run 'software-
> properties-gtk' and adjust repositories, the file is not created.
>
> Quick remedy:
>
> sudo rm -f /etc/apt/trusted.gpg
>
> Now run 'synaptic' or 'apt' as usual. If you run 'synaptic', do not
> use the menu option 'Settings -> Repositories.
>
> This could probably do with a bug raising.
>
> Regards
>
> Phil

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 software with no problem.

Cheers,
-- 
Jimmy Johnson

Debian Stretch - KDE Plasma 5.8.6 at sda13
Registered Linux User #380263

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

#183114

> 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 software with no problem.
> 
> Cheers,
> --
> Jimmy Johnson
> Debian Stretch - KDE Plasma 5.8.6 at sda13 Registered Linux User #380263

Hi Jimmy,

I saw one of your previous posts regarding the live cd/dvd. 

I used the following to install, but not sure if this is the live dvd you refer to (I thought there was a difference between a regular install dvd and a live dvd?).

f0a87f42ba0090314a4d3e45afe43d7fe7c115305bed266fe51a650c58cf3cab  debian-9.0.0-amd64-DVD-1.iso

My keys (using apt-key list) seem to be present, but then I am not experienced enough to know 100% for sure what I am looking at. Certainly the keys complained about are listed.

Regards,
Wayne.

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

#183121

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 problem, cause I > used it and installed software with no problem.
>>
>> Cheers,
>> --
>> Jimmy Johnson
>> Debian Stretch - KDE Plasma 5.8.6 at sda13 Registered Linux User #380263
>
> Hi Jimmy,
>
> I saw one of your previous posts regarding the live cd/dvd.
>
> I used the following to install, but not sure if this is the live dvd you refer to (I thought there was a difference between a regular install dvd and a live dvd?).
>
> f0a87f42ba0090314a4d3e45afe43d7fe7c115305bed266fe51a650c58cf3cab  debian-9.0.0-amd64-DVD-1.iso
>
> My keys (using apt-key list) seem to be present, but then I am not experienced enough to know 100% for sure what I am looking at. Certainly the keys complained about are listed.
>
> Regards,
> Wayne.

Hi Wayne,

I have not tested that install dvd. But I did have problems with the 
live-dvd, I've used rc3 and it was great, maybe try it or use the zip 
file I attached to my other post for a quick fix, just extract and copy 
to /etc.

Cheers,
-- 
Jimmy Johnson

Debian Stretch - KDE Plasma 5.8.6 at sda13
Registered Linux User #380263

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

#183143

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 'Settings -> Repositories. A soon as you do this a
> file '/etc/apt/trusted.gpg' is created and it is this that is throwing
> everything off.

Synaptic uses software-properties-gtk which is the cause of this mess. 
Run it stand alone after deleting trusted.gpg and watch it reappear again.
> ERROR:root:Cannot import UbuntuDrivers: No module named
> 'UbuntuDrivers'
> gpg: keybox '/etc/apt/trusted.gpg' created
> ERROR:root:Cannot import UbuntuDrivers: No module named
> 'UbuntuDrivers'
> gpg: keybox '/etc/apt/trusted.gpg' created

These messages are from software-properties-gtk.

> It is the last line that is the issue. If you run 'software-
> properties-gtk' and adjust repositories, the file is not created.

Not my experience.

Regards,
Frank

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

#183155

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

> From: philwyett@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 and statements
that both apt and apt-get have produced the error. The first
who mentions synaptic is you.
But, what really blows my mind is that it took all this time of
stable "testing" to get to this stage of end-of-testing and how
the rc before stable didn't have this problem.
I would manually download the keyrings and all debian gpg
stuff, delete/uninstall whatever I had and reinstall/force new
ones.
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?
2 What filesystem did you use while partitioning?
3 Is there any kind of raid?
4 Is autoupdate/unattended-update enabled? And is there a log of it?

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

#183113

> 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
allow sudo for your user after that?

Yes I did verify using SHA-256.

f0a87f42ba0090314a4d3e45afe43d7fe7c115305bed266fe51a650c58cf3cab
debian-9.0.0-amd64-DVD-1.iso

My clean installs of Jessie never had any problems; just clean stretch
installs.

If I can't find any other solution I will try a clean install with root
enabled, though if the DVD is the culprit (as per Jimmy Johnson) I may be
best off installing 8.8 and doing a net upgrade.

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

#183105

Hi,

On Tue, 4 Jul 2017 18:47:14 +0930
"Wayne Hartell" <w.hartell@ozemail.com.au> 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
> > > trusted.gpg?)...
> >
> > I have to guess 644 is correct, as that is what is set on the Stretch
> > I have booted currently (as are all regular files in /etc/apt/), and
> > I've never touched it myself.
> >
> > Do you get the same errors running 'apt update' instead of 'apt-get
> > update'?
> 
> Yes, it seems that I get the same errors that way too.
> 
> I tried a new clean install test and seem to end up with permissions
> under /etc/apt/ always as 0600, so I am not sure what is going on.
> Looks like an issue with a clean install, but I am wondering why it's
> not coming up more often (unless most people are upgrading from Jessie).

here (Jessie) /etc/apt/trusted.gpg is 0600. I never touched this file, so
I guess this is standard. The other files in /etc/apt appear to be 0644.
Since root can read/write the file anyway, I don't believe that the
permissions could cause the OP's problem, though.

Regards

Michael

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

Madness has no purpose.  Or reason.  But it may have a goal.
		-- Spock, "The Alternative Factor", stardate 3088.7

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

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

csiph-web