Re: how to solve GPG keys missing for apt-get ??
On 4/13/20 1:27 PM, Dennis Clarke wrote:
>> I'm not sure why people have such a hard time installing one of the older
>> Yaboot images I created:
>>
>>> https://cdimage.debian.org/cdimage/ports/10.0/
>
> Well, I have worked on this all night long, a solid 8 hours with four
> dvd image burns, multiple installs and failures. Never was able to get
> a bootable running machine until I resorted to an old iso I had laying
> about. It was from 2017 and it worked but is 32-bit userland. So I
> don't want that.
>
> I may as well start over.
>
> ISO images I did try :
>
> nix$
> nix$ ls -1 *ppc*
> debian-10.0-ppc64-NETINST-1_2018-05-18.iso
> debian-10.0-ppc64-NETINST-1_2019-04-11.iso
> debian-10.0-ppc64-NETINST-1_2019-11-24.iso
> debian_ppc64_jessie_8.7.1_201701161157.iso
> nix$
>
> None work except the jessie_8.7.1 iso from 2017.
Well, you could have asked me. I created almost all the images found on
cdimage.debian.org/cdimage/ports.
And if you provided me logs, I could have told you what the problem
during installation was.
There are only three known ways the images can fail.
1) Packages are not installable in the step "Select and install
software", something you can always skip and perform after the
machine has been rebooted. People seem to assume that it's
mandatory to install extra software during the initial installation
which is not true. It's purely optional and you should just
install the basic system from CD.
2) Installation of the base system failing because of vim-tiny
being uninstallable. An image that has this problem is unusable
and I was sure I deleted all images that suffered this problem.
The background of this problem is explained here:
> https://lists.debian.org/debian-devel/2020/03/msg00221.html
3) GRUB not being installable on PowerMacs due to ofpathname not
returning the correct OpenFirmware pathnames on Apple PowerMacs
and hence grub-installer unable to figure out the correct OF
path.
The GRUB issue can be solved by installing GRUB manually as
explained by Frank Scheiner:
> https://lists.debian.org/debian-powerpc/2017/09/msg00034.html
> https://lists.debian.org/debian-powerpc/2017/10/msg00005.html
Also, you should always choose the basic installation and not try anything
fancy. I have not tested each and every possible setup in d-i so you
might run into something untested which might not work.
I don't have the manpower to perform all these tests and development
on my own. Currently it seems that no one is willing to help with
the Debian PowerPC port.
>> Just skip the part where the debian-installer wants to download and install extra
>> software. That won't work as the keyring shipped on the installation image
>> is too old for the release file on the server. The moment you will have
>> rebooted the machine, you can install the updated keyring and update your
>> installation
>
> Well I can try again in a day. I have been through two machines and
> multiple dvd images to try and get an install that at least boots in
> some way. So most people give up after five or six hours of failure but
> after 8 hours I did get this :
Yeah, trial-and-error is not very efficient. Posting your installation log
on this mailing list (found in /var/log/syslog during installation) would
have probably been more helpful.
> Perhaps the problem is that I am trying to use the expert install option
> and should just do the basic default install and accept whatever the
> parted disk layout results from the guided partitioner.
Yes, and the fact that you are not trying to debug your problem systematically,
trying random things doesn't help unless you have an infinite amount of time.
The installer provides error logging in /var/log/syslog, so you should have
a look at that log and post the error messages here.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: