Your message dated Wed, 22 Nov 2006 12:34:22 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#399314: debian-installer: when two kernel versions are
present in the archive, d-i does strange things when building.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: debian-installer, ftp.debian.org
Severity: normal
In todays checkout, we get :
...
Get:1 http://ftp2.fr.debian.org unstable/main/debian-installer
ext3-modules-2.6.18-2-powerpc-di 1.23 [106kB]
Get:2 http://ftp2.fr.debian.org unstable/main/debian-installer
kernel-image-2.6.17-2-powerpc-di 1.22 [1871kB]
While the 2.6.18-2 kernels should have been fetched. This is probably due to
2.6.17-2 still being in the archive, and not versioned dependencies doing
strange stuff in these conditions. I have some serious doubts about a d-i
image resulting from such a build working, but haven't investigated further.
This bug report is thus serving a double purpose, first, to ftp.debian.org, to
remove the 1.22 2.6.17 d-i powerpc .udebs from the unstable archive, and
second so, maybe someone with a clue about the kernel .udeb dependencies
coming in and being able to comment on this issue, and maybe propose a fix.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-powerpc
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
On Sunday 19 November 2006 09:16, Sven Luther wrote:
> While the 2.6.18-2 kernels should have been fetched. This is probably
> due to 2.6.17-2 still being in the archive, and not versioned
> dependencies doing strange stuff in these conditions. I have some
> serious doubts about a d-i image resulting from such a build working,
> but haven't investigated further.
This has never been a problem in the past and I doubt that the mere
existence of the old packages is the problem here.
Anyway, deleting the packages from the archive is completely the wrong
solution for this. Therefore closing the BR.
pgpq6Wb5cvjCF.pgp
Description: PGP signature
--- End Message ---
