[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#514237: debian-cd: Support non-i386 mirrors, and support D-I modules in non-main



On Thursday 05 February 2009, Frans Pop wrote:
> On Thursday 05 February 2009, Jonathan Hall wrote:
> > --- debian-cd/tools/update_tasks	(revision 7407)
> > +++ debian-cd/tools/update_tasks	(revision 7487)

> Wouldn't it be much simpler to use tools/which_deb instead?
> That would also avoid having arch lists (which will need to be
> updated!) all over the place.

This is not going to work as we don't only need the tasksel package, but 
also the Packages file for a specific arch as that is our basis for the 
task expansion. So, although which_deb could be used to get tasksel, it 
would not solve the whole problem.

So the following really has to be implemented in update_tasks itself.

On Thursday 05 February 2009, Frans Pop wrote:
> So IMO:
> * ideally we should run update_tasks for every architecture separately,
>   using the Packages file for that arch; for source-only CDs we should
>   use i386 with fallback to amd64, and fail otherwise
> * but as long as we do not do that
>   - for binary or binary/source CDs: prefer i386, with fallback to:
>     1) amd64
>     2) arches listed in $ARCHES
>   - for source-only CDs: use i386, with fallback to amd64, and fail
>     otherwise

But, given the reasons I gave in [1], we could also do this a bit 
differently and as a bonus improve the task expansion:

* if ARCHES contains a single arch OR a single arch + "source", then
  use that arch
* if ARCHES contains multiple arches or is source-only, then use i386
  with a fallback to the arches listed in ARCHES

This means in most cases we'll do exactly the right thing. Except for 
multi-arch images, and for those we use the most "generic" default we 
have, which at least ensures consistency ("amd64 i386 powerpc" will give 
the same result as "powerpc amd64 i386").

[1] http://bugs.debian.org/514237#40



Reply to: