Your message dated Fri, 03 May 2013 14:02:28 +0100
with message-id <[email protected]>
and subject line Re: Bug#706646: linux: FTBFS after regenerating debian/control 
(kernel-wedge find-dups errors)
has caused the Debian Bug report #706646,
regarding linux: FTBFS after regenerating debian/control (kernel-wedge 
find-dups errors)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
706646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706646
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: linux
Version: 3.8.5-1~experimental.1
Severity: normal

To reproduce:
vi debian/changelog  # and insert a dummy version entry
debian/rules debian/control
fakeroot debian/rules clean
dpkg-buildpackage -uc -us

At the end, I get these errors:
dh_testdir
dh_prep
kernel-wedge install-files 3.8-trunk
        install -D -m 644
debian/linux-image-3.8-trunk-amd64/boot/vmlinuz-3.8-trunk-amd64
debian/kernel-image-3.8-trunk-amd64-di/boot/vmlinuz
        install -d
debian/kernel-image-3.8-trunk-amd64-di/lib/modules/3.8-trunk-amd64
        install -m 644
debian/linux-image-3.8-trunk-amd64/lib/modules/3.8-trunk-amd64/modules.builtin
debian/linux-image-3.8-trunk-amd64/lib/modules/3.8-trunk-amd64/modules.order
debian/kernel-image-3.8-trunk-amd64-di/lib/modules/3.8-trunk-amd64/
        install -D -m 644
debian/linux-image-3.8-trunk-amd64/boot/System.map-3.8-trunk-amd64
debian/kernel-image-3.8-trunk-amd64-di/boot/System.map
        kernel-wedge copy-modules 3.8-trunk amd64 3.8-trunk-amd64
        kernel-wedge find-dups 3.8-trunk-amd64
debian/nic-modules-3.8-trunk-amd64-di
lib/modules/3.8-trunk-amd64/kernel/drivers/pps/pps_core.ko
debian/nic-extra-modules-3.8-trunk-amd64-di
lib/modules/3.8-trunk-amd64/kernel/drivers/pps/pps_core.ko
debian/nic-modules-3.8-trunk-amd64-di
lib/modules/3.8-trunk-amd64/kernel/drivers/ptp/ptp.ko
debian/nic-extra-modules-3.8-trunk-amd64-di
lib/modules/3.8-trunk-amd64/kernel/drivers/ptp/ptp.ko
debian/nic-usb-modules-3.8-trunk-amd64-di
lib/modules/3.8-trunk-amd64/kernel/lib/crc16.ko
debian/ext4-modules-3.8-trunk-amd64-di
lib/modules/3.8-trunk-amd64/kernel/lib/crc16.ko
debian/xfs-modules-3.8-trunk-amd64-di
lib/modules/3.8-trunk-amd64/kernel/lib/libcrc32c.ko
debian/crc-modules-3.8-trunk-amd64-di
lib/modules/3.8-trunk-amd64/kernel/lib/libcrc32c.ko
some modules are in more than one package
command exited with status 1
make[2]: *** [install-udeb_amd64] Error 2
make[2]: Leaving directory `/home/daniel/src/debian/linux/linux-3.8.5'
make[1]: *** [binary-arch_amd64] Error 2
make[1]: Leaving directory `/home/daniel/src/debian/linux/linux-3.8.5'
make: *** [binary-arch] Error 2

(My actual use case was that I wanted to build kernel packages with
CONFIG_X86_X32=y.  But as indicated above, I've verified that this is
reproducible without that setting added.  Luckily, this happens after all
the actual image packages are already built, but it's annoying not to be
able to get a changes file, nor to be able to use pbuilder or sbuild to do
the build.)
-- 
Daniel Schepler

--- End Message ---
--- Begin Message ---
On Thu, 2013-05-02 at 14:33 -0700, Daniel Schepler wrote:
> Source: linux
> Version: 3.8.5-1~experimental.1
> Severity: normal
> 
> To reproduce:
> vi debian/changelog # and insert a dummy version entry
> debian/rules debian/control
> fakeroot debian/rules clean
[...]

You didn't read the error message here.

Ben.

-- 
Ben Hutchings
Lowery's Law:
             If it jams, force it. If it breaks, it needed replacing anyway.

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


--- End Message ---

Reply via email to