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

Bug#490652: debian-cd: should support including source for mixed builds



Package: debian-cd
Version: 3.0.4

Building a DVD image including source for Etch+1/2 - using packages from
stable, but D-I/udebs from testing - the following errors occur:
Use of uninitialized value in pattern match (m//) at /home/deb-cd/fjp/debian-cd/tools/make_disc_trees.pl line 674, <INLIST> line 632.
Use of uninitialized value in string eq at /home/deb-cd/fjp/debian-cd/tools/make_disc_trees.pl line 685, <INLIST> line 632.
Use of uninitialized value in concatenation (.) or string at /home/deb-cd/fjp/debian-cd/tools/make_disc_trees.pl line 715, <INLIST> line 632.
Use of uninitialized value in print at /home/deb-cd/fjp/debian-cd/tools/make_disc_trees.pl line 733, <INLIST> line 632.
Use of uninitialized value in subroutine entry at /home/deb-cd/fjp/debian-cd/tools/make_disc_trees.pl line 737, <INLIST> line 632.
Failed to write /org/cdbuilder.debian.org/src/deb-cd/fjp/tmp//etch/CD1/dists/etch/local/source/Sources.gz:
make: *** [image-trees] Error 255

It looks like the $pkg passed into add_packages is borked and
log.add_packages shows that:
   Looking at source:main:: arch source, package , rollback 0

Reason is incorrect data in the packages list due to a bug in the
Packages/Sources file handling somewhere. In the packages list:
   i386:main:libpcap0.8
   amd64:main:libpcap0.8
-->source:main:
   i386:main:acpi-modules-2.6.24-1-486-di
   source:main:apt-setup
   amd64:main:apt-cdrom-setup

Base cause is that the same Sources.gz is used for both debs and udebs,
and acpi-modules-2.6.24-1-486-di just does not exist in the stable
Sources.gz file in this scenario. For other udebs an incorrect source
version could be included.

Some solutions were discussed, but in the end it was decided to work
around the issue by not adding source for udebs at all (see SVN
revision 1630).
A real solution possibly requires that the debian-installer section of
the archive gets its own Sources.gz file, although it may be possible
to do without by checking which suite is used for what and basing the
Sources.gz file to consult on that.

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: