From: Piotr Hosowicz <piotr@hosowicz.com>
To: linux-next@vger.kernel.org
Subject: Has somethimg changed in next's Debian package generation?
Date: Mon, 05 Jul 2010 17:09:52 +0200 [thread overview]
Message-ID: <4C31F5C0.2020106@example.com> (raw)
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.
Regards,
Piotr Hosowicz
--
Różnica między PiS, a PO jest taka, że PO nie zro-
biła liberalizacji, a PiS nie zrobił lustracji.
NP: Chickenfoot - Oh Yeah
NB: 2.6.35-rc4
next reply other threads:[~2010-07-05 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 15:09 Piotr Hosowicz [this message]
2010-07-09 14:32 ` Has somethimg changed in next's Debian package generation? Piotr Hosowicz
2010-07-09 15:38 ` Piotr Hosowicz
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=4C31F5C0.2020106@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).