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

Bug#359852: marked as done (linux-2.6: control autogeneration code will make binNMU's FTBFS)



Your message dated Fri, 24 Dec 2010 17:39:21 +0100
with message-id <20101224163921.GA4887@galadriel.inutil.org>
and subject line Closing
has caused the Debian Bug report #359852,
regarding linux-2.6: control autogeneration code will make binNMU's FTBFS
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 owner@bugs.debian.org
immediately.)


-- 
359852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=359852
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.16-3
Severity: important

I tried building linux-2.6 with a version of 2.6.16-3+pb1 here (to help apt
distinguish the results from the official packages), and got this from
pbuilder:

...
md5sum debian/bin/gencontrol.py debian/changelog [snip]...

This target is made to fail intentionally, to make sure
that it is NEVER run during the automated build. Please
ignore the following error, the debian/control file has
been generated SUCCESSFULLY.

exit 1
make[1]: *** [debian/control-real] Error 1
make[1]: Leaving directory `/tmp/buildd/linux-2.6-2.6.16'
make: *** [debian/control] Error 2

This means that if you or the release managers ever want to schedule a
binNMU of the kernel image packages on the buildds, the result will be a
FTBFS.
-- 
Daniel Schepler


--- End Message ---
--- Begin Message ---
These wishlist bugs have been tagged wontfix for quite some time. Since
we already too much noise in the linux-2.6 bug page, I'm closing them
now.

Cheers,
        Moritz


--- End Message ---

Reply to: