From: Kevin White <ml-kevin@kevbo.org>
To: netfilter@lists.netfilter.org
Subject: Can't get pom-ng to batch apply one patch
Date: Tue, 20 Jul 2004 15:05:58 -0400 [thread overview]
Message-ID: <40FD6D16.1000004@kevbo.org> (raw)
I'm trying to automatically build a kernel. As such, I need to
automatically apply pom patches, and I can't get it to work.
I'm using patch-o-matic-ng-20040621. For kicks, I'm trying to apply the
"first" patch in the base suite, 04_linux-2.4.26-helper_reassign.patch.
That patch does apply if I run:
./runme base
and say "Y" to it. But I can't get this to work:
./runme --batch updates/04_linux-2.4.26-helper_reassign.patch
First, on an unmodified runme, this code causes my patch to be skipped:
for my $rep (@repositories) {
PATCHLET: for my $plname (@patchlets) {
my $patchlet = $session->{patchlets}->{$plname};
next PATCHLET unless defined $patchlet
The $session hash doesn't have a patch called
"updates/04_linux-2.4.26-helper_reassign.patch", but I have to refer to
the patch by that name to get past all of the prior checks for .info
files and such.
So, I hacked this in there:
$plname =~ s/.*\///;
print "looking at $plname\n";
before the my $patchlet line, and it causes it to match, but then, the
patch won't actually apply:
cannot apply (1 rejects out of 1 hunks)
cannot apply (41 rejects out of 43 hunks)
ERROR (41 rejects out of 43 hunks)
apply_dependency: unable to apply dependent 02_linux-2.4.24.patch
-----------------------------------------------------------------
Which wouldn't happen if I just ran runme and picked this patch.
So, help! How to people batch apply specific patches?
Kevin
reply other threads:[~2004-07-20 19:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40FD6D16.1000004@kevbo.org \
--to=ml-kevin@kevbo.org \
--cc=netfilter@lists.netfilter.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.