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

Re: Inconsistent handling of sourceless packages in main

Jeroen van Wolffelaar <jeroen@wolffelaar.nl> writes:

> On Mon, Jun 13, 2005 at 12:34:21PM +0200, Goswin von Brederlow wrote:
>> Jeroen van Wolffelaar <jeroen@wolffelaar.nl> writes:
>> > The above is a bit sparce on details of what exactly is the issue here.
>> > debian-installer builds use udeb's, and work is underway to not only
>> > keep those udeb's used last, but the udeb's for all d-i builds on the
>> > mirror network. If a udeb or deb is on the mirrors, the corresponding
>> > source is too, that's already ensured.
>> How will you do that? Will that include the files copied from the
>> build system into the D-I images? Can the same mechanism be used for
>> ia32-libs and similar?
> Nothing decided yet, thinking about the raw-installer upload hook to do
> something terribly d-i specific to keep all the needed udeb's for the
> installed d-i images around in some special 'fake' suite.

How about an entry in the changes file:

Deb-Sources: libc6 (= 1.2-3), devmapper-udeb (= 4.5-6), ....

The D-I build can fill in the right packages and versions and the same
could be used by ia32-libs.

I like the idea of a fake suite so D-I or ia32-libs doesn't stop
packages migrating to testing. But before a release someone has to
check that all packages in the fake suite are also in testing. Not
like with sarge.


Reply to: