From: Piotr Hosowicz <piotr@hosowicz.com>
To: piotr@hosowicz.com
Cc: linux-next@vger.kernel.org
Subject: Re: Has somethimg changed in next's Debian package generation?
Date: Fri, 09 Jul 2010 17:38:51 +0200 [thread overview]
Message-ID: <4C37428B.8000901@example.com> (raw)
In-Reply-To: <4C3732EA.7070105@example.com>
On 09.07.2010 16:32, Piotr Hosowicz wrote:
> On 05.07.2010 17:09, Piotr Hosowicz wrote:
>> Hello,
>>
>> I build the kernel with make-kpkg under debian like:
>>
>> make-kpkg kernel_image
>>
>> I have had done it this way also with linux next. Lacking fresh sources
>> after a short break from next I tried to build today's next as always
>> but the build failed when it was to finally build the package saying
>> that there is a inconsisteny in control file. I tried to tinker a bit
>> with ./debian/control but to no effect.
>>
>> Has something changed? It used to work just like that, there were no
>> problems at all.
>
> Anybody has any advice?
>
> Thanks in advance.
I tried again, precise cmd line was:
LANG=C CONCURRENCY_LEVEL=10 make-kpkg kernel_image
I ended with:
dpkg-gencontrol: error: package linux-image-2.6.35-rc4-next-20100709 not
in control info
make[2]: *** [debian/stamp/binary/linux-image-2.6.35-rc4-next-20100709]
Error 255
make[2]: Leaving directory `/usr/src/linux-2.6.35-rc4-next-20100709'
make[1]: ***
[debian/stamp/binary/pre-linux-image-2.6.35-rc4-next-20100709] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.35-rc4-next-20100709'
make: *** [kernel_image] Error 2
Can someone help me on this?
Regards,
Piotr Hosowicz
--
Janusz Korwin-Mikke:
"Idiota z dyplomem to taki sam idiota,
jak przedtem - tylko z pretensjami."
NP: Mark Knopfler - Cleaning My Gun
NB: 2.6.35-rc4-git4
next prev parent reply other threads:[~2010-07-09 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 15:09 Has somethimg changed in next's Debian package generation? Piotr Hosowicz
2010-07-09 14:32 ` Piotr Hosowicz
2010-07-09 15:38 ` Piotr Hosowicz [this message]
2010-07-10 12:54 ` Piotr Hosowicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C37428B.8000901@example.com \
--to=piotr@hosowicz.com \
--cc=linux-next@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.