Hi Andreas,

On Mon, 2025-09-15 at 19:51 +0200, Andreas Tille wrote:
> Hi Adrian,
> 
> Am Mon, Sep 15, 2025 at 05:59:24PM +0200 schrieb John Paul Adrian Glaubitz:
> > > > [1] 
> > > > https://salsa.debian.org/debian/aboot/-/commit/f3fe7516dcd1e8921e99bed41d8006ba9bdcc53e
> > > 
> > > It's unfortunately a little more complex than just fixing the doc build
> > > to unbreak aboot. I'm currently searching for the list of extensive 
> > > changes
> > > necessary.
> > 
> > I found it, see [1]. As you can see, there are 19 patches necessary to fully
> > unbreak aboot, so the simple change you made is not going to be sufficient.
> 
> Ohh, I admit I should have read the full bug log.

Indeed ;-).

> > I appreciate the willingness to help fixing packages, but I would rather 
> > have
> > people contact me first before pushing something to the repositories I 
> > maintain.
> 
> Sorry, will choose MR next time.  Let me know if you want me to revert
> the changes using `git push --force`.

No worries, I'll take care of that.

You already noticed the first problem which is that even when the package 
builds,
it's not installable. The problem is that the original build process was 
designed
with alpha being a release architecture in mind and the package being always
a binary-plus-source upload meaning that the aboot-base package would be built
on alpha before upload.

And your diagnosis is not fully correct as aboot-base doesn't just contains
documentation but also the alpha-only bootloader artifacts which are used
for creating a bootable installation medium.

On top of that, we have the problem that the Linux kernel has gotten rid of
a.out support or wants to get rid of it which means we need to retrieve
the headers for a.out from somewhere else.

I also want to restructure the aboot package the same way as the palo package
so that the alpha artifacts can be cross-compiled on x86_64. I tried that
but eventually ran into problems, see [1].

> I was simply wondering why aboot is mentioned twice in UDD[1] and wanted
> to do something about this.

I understand. I don't blame you, but I think it would always be better to
contact the maintainer first before attempting package fixes. I'm usually
responding within short notice.

> [1] https://lists.debian.org/debian-qa/2025/09/msg00029.html

Adrian


> [1] https://github.com/mattst88/aboot/issues/5

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Reply via email to