Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Building my own Debian m68k NETINST ISO from Debian Installer kernel and initrd
28 views
Skip to first unread message
John Paul Adrian Glaubitz
Dec 13, 2021, 12:40:03 PM12/13/21
to
Hello!
On 12/9/21 23:24, Carlos Milán Figueredo wrote:
> If I am able to check that the changes successfully work, I will
> send a Merge Request in the debian-installer repo.
Thanks, but I prefer making all those changes myself as I want to
do that for all the other architectures where it's missing, too.
Also, I want to do some clean up while at it.
However, if you send me your test results, that's actually very helpful.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glau...@debian.org
`. `' Freie Universitaet Berlin - glau...@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
On 12/9/21 23:24, Carlos Milán Figueredo wrote:
> If I am able to check that the changes successfully work, I will
> send a Merge Request in the debian-installer repo.
Thanks, but I prefer making all those changes myself as I want to
do that for all the other architectures where it's missing, too.
Also, I want to do some clean up while at it.
However, if you send me your test results, that's actually very helpful.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glau...@debian.org
`. `' Freie Universitaet Berlin - glau...@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
John Paul Adrian Glaubitz
Jan 4, 2022, 2:50:02 AM1/4/22
to
Hi Carlos!
On 12/26/21 00:44, Carlos Milán Figueredo wrote:
> After running these steps I run into some problems. It looks like when running
> sort_deps it just doesn't find any packages. I am attaching a log of the output,
> with my configuration files as well.
You are missing the "debian-ports-archive-keyring" package, see:
> E: The repository 'file:/srv/debian-m68k-archive sid Release' is not signed.
> Also I have to do some modifications in your sample scripts:
>
> 1. In CONF.sh, I disabled the 'unreleased' repository, as it was just sid was
> retrieved by reprepro. I used [1] as base for the configuration, replacing sparc64
> for m68k.
You should include "unreleased" though.
> 2. In easy-build.sh, I changed the CODENAME and DI_CODENAME from 'bookwork' to 'sid'.
Huh, I'm pretty sure it was set to "sid" in my configuration.
> Am I missing something here?
Yes, the signing key.
FWIW, including firmware should now work as well since "contrib" and "non-free" were
recently added for arch:all packages in Debian Ports.
On 12/26/21 00:44, Carlos Milán Figueredo wrote:
> After running these steps I run into some problems. It looks like when running
> sort_deps it just doesn't find any packages. I am attaching a log of the output,
> with my configuration files as well.
You are missing the "debian-ports-archive-keyring" package, see:
> E: The repository 'file:/srv/debian-m68k-archive sid Release' is not signed.
> Also I have to do some modifications in your sample scripts:
>
> 1. In CONF.sh, I disabled the 'unreleased' repository, as it was just sid was
> retrieved by reprepro. I used [1] as base for the configuration, replacing sparc64
> for m68k.
You should include "unreleased" though.
> 2. In easy-build.sh, I changed the CODENAME and DI_CODENAME from 'bookwork' to 'sid'.
Huh, I'm pretty sure it was set to "sid" in my configuration.
> Am I missing something here?
Yes, the signing key.
FWIW, including firmware should now work as well since "contrib" and "non-free" were
recently added for arch:all packages in Debian Ports.
John Paul Adrian Glaubitz
Jan 8, 2022, 3:20:03 AM1/8/22
to
Hello Carlos!
On 1/8/22 01:31, Carlos Milán Figueredo wrote:
> Sadly, there is no mention to the keyring package in [1] nor the signing
> process. The documentation is missing several points. First, the sample
> config files to download at [2] do not include Unreleased repo, so I
> figured out that I had to add a new entry in the reprepro's distributions file:
The repository is already signed. You just need to get the repo from the remote
server onto your local hard disk, including the signed Release and Packages files.
There is no need to create your own Release file or sign it, so I'm not sure what
you are trying to achieve. You could also use rsync for clowning the mirror but
then you would have to exclude the other architectures.
On 1/8/22 01:31, Carlos Milán Figueredo wrote:
> Sadly, there is no mention to the keyring package in [1] nor the signing
> process. The documentation is missing several points. First, the sample
> config files to download at [2] do not include Unreleased repo, so I
> figured out that I had to add a new entry in the reprepro's distributions file:
The repository is already signed. You just need to get the repo from the remote
server onto your local hard disk, including the signed Release and Packages files.
There is no need to create your own Release file or sign it, so I'm not sure what
you are trying to achieve. You could also use rsync for clowning the mirror but
then you would have to exclude the other architectures.
John Paul Adrian Glaubitz
Feb 2, 2022, 3:20:03 PM2/2/22
to
On 2/2/22 21:11, John Paul Adrian Glaubitz wrote:
>From the git history, it looks like nativehd is an old image type that is only being used at all
> on m68k but not on the other architectures. I will perform a test installer build and check what's
> actually in the initrd.
OK, so "nativehd" is basically a hard-disk based network installer while "hd-media"
is a hard-disk based CD-ROM installer, see [1].
Now, since we also have a "netboot" installer, I wonder whether we still need the
"nativehd" installer.
Adrian
> [1] https://www.debian.org/releases/sarge/m68k/ch05s01.html.en
>From the git history, it looks like nativehd is an old image type that is only being used at all
> on m68k but not on the other architectures. I will perform a test installer build and check what's
> actually in the initrd.
OK, so "nativehd" is basically a hard-disk based network installer while "hd-media"
is a hard-disk based CD-ROM installer, see [1].
Now, since we also have a "netboot" installer, I wonder whether we still need the
"nativehd" installer.
Adrian
> [1] https://www.debian.org/releases/sarge/m68k/ch05s01.html.en
John Paul Adrian Glaubitz
Feb 2, 2022, 3:20:03 PM2/2/22
to
Hi Carlos!
I have finally found the time to look at hd-media images.
On 12/9/21 23:24, Carlos Milán Figueredo wrote:
> The changes I have made to the debian-installer configurations to the m68k builds right are fairly simple:
>
> In /build/pkg-lists/hd-media/m68k.cfg added following lines:
> pata-modules-${kernel:Version}
> fat-modules-${kernel:Version}
> ext4-modules-${kernel:Version}
> affs-modules-${kernel:Version}
> loop-modules-${kernel:Version}
>
> In /build/pkg-lists/nativehd/m68k.cfg added following line:
> nic-modules-${kernel:Version}
I just wanted to update this and now I'm wondering whether we actually still need the "nativehd"
media type or whether we can just merge it with the "hd-media" type which is what's being used
on the other architectures.
>From the git history, it looks like nativehd is an old image type that is only being used at all
on m68k but not on the other architectures. I will perform a test installer build and check what's
actually in the initrd.
Did you use the "hd-media" or the "nativehd" image for your tests?
Adrian
I have finally found the time to look at hd-media images.
On 12/9/21 23:24, Carlos Milán Figueredo wrote:
>
> In /build/pkg-lists/hd-media/m68k.cfg added following lines:
> pata-modules-${kernel:Version}
> fat-modules-${kernel:Version}
> ext4-modules-${kernel:Version}
> affs-modules-${kernel:Version}
> loop-modules-${kernel:Version}
>
> In /build/pkg-lists/nativehd/m68k.cfg added following line:
> nic-modules-${kernel:Version}
I just wanted to update this and now I'm wondering whether we actually still need the "nativehd"
media type or whether we can just merge it with the "hd-media" type which is what's being used
on the other architectures.
>From the git history, it looks like nativehd is an old image type that is only being used at all
on m68k but not on the other architectures. I will perform a test installer build and check what's
actually in the initrd.
Adrian
0 new messages