Re: Bug#379090: Still no news on 64bit i386 kernels
Andreas Barth <firstname.lastname@example.org> writes:
> * Goswin von Brederlow (email@example.com) [061031 15:01]:
>> Frederik Schueler <firstname.lastname@example.org> writes:
>> I asked this before and haven't yet recieved an answere:
>> What does w-b do when the amd64 build uploads amd64+i386 64bit kernel
>> debs but not 32bit. Afaik the package should be detected as incomplete
>> and set to "needs-build" for i386. i386 then builds the 32bit kernels
>> only and uploads them.
> As soon as there are binary packages for i386, wanna-build marks i386 as
> installed. How should it detect otherwise if e.g. a kernel was dropped?
Because the Binary field in Sources does list the packages and P-a-s
does not specificaly exclude them. (or for your second part, because
the kernel drops from Binary:).
I haven't tested this but that is what the lines listing binaries (not
%source entries) in P-a-s are for or not? To tell w-b that an arch
does not build those debs and it should not miss them.
Did you test it with some dummy packages and source?
>> > The "real" solution for this still is multiarch. I haven't heard much
>> > of it since a couple of months, is anyone still actively working on it?
>> Which means, at a minimum, changes to debian-cd and D-I to include the
>> amd64 packages on i386 and the linux64 boot option and a wrapper
>> package for apt/aptitude/dpkg to make the amd64 debs appear and
> Which won't happen anyways for etch.
Why? A new source can still make it to etch, right? The D-I change is
adding one entry in the isolinux.cfg and debian-cd can still be
modified or not?
Worst case we just have the wrapper and you can only install 64bit
kernel from the network (after installing the wrapper).