From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Disapproval of revision b8e46b797b32111526a2116d020fdd9e1c079965
Date: Thu, 08 May 2008 08:58:48 +0200 [thread overview]
Message-ID: <fvu8b8$kl2$1@ger.gmane.org> (raw)
Hello,
This morning I get:
File "/OE/bitbake/lib/bb/build.py", line 136, in exec_func_python
utils.better_exec(comp, g, tmp, bbfile)
File "/OE/bitbake/lib/bb/utils.py", line 144, in better_exec
exec code in context
File "patch_do_patch", line 100, in <module>
File "patch_do_patch", line 98, in patch_do_patch
File "<bb>", line 339, in Resolve
__builtin__.CmdError: Command Error: exit status: 1 Output:
Applying patch amd64.patch
patching file longlong.h
Hunk #1 FAILED at 715.
1 out of 1 hunk FAILED -- rejects in file longlong.h
Patch amd64.patch does not apply (enforce with -f)
So I look at the commits:
Commit by Laibsch on org.oe.dev :: rb8e46b79... / (14 files in 7 dirs):
gmp: consolidate common patches unchanged across versions into files/
koen@lieve:/OE/org.openembedded.dev/packages/gmp$ find . | grep amd64
./files/amd64.patch
Ok, so there really is only one patch. Let's do an experiment:
koen@lieve:/OE/org.openembedded.dev/packages/gmp$ mtn up -r f3aafac3
mtn: expanded selector 'f3aafac3' -> 'i:f3aafac3'
mtn: expanding selection 'f3aafac3'
mtn: expanded to 'f3aafac33dd3d98133bfd91efdee783ccd8da959'
mtn: selected update target f3aafac33dd3d98133bfd91efdee783ccd8da959
mtn: [left] 71c3bbc5e67f712d2f13eedc29e54d1d2e9c64c8
mtn: [right] f3aafac33dd3d98133bfd91efdee783ccd8da959
mtn: renaming packages/gmp/files/amd64.patch to
packages/gmp/gmp-4.1.2/amd64.patch
mtn: adding packages/gmp/gmp-4.1.4/amd64.patch
mtn: renaming packages/gmp/files/sh4-asmfix.patch to
packages/gmp/gmp-4.1.4/sh4-asmfix.patch
mtn: adding packages/gmp/gmp-4.2.1/amd64.patch
mtn: adding packages/gmp/gmp-4.2.1/sh4-asmfix.patch
mtn: renaming packages/gmp/files/x86-fat.diff to
packages/gmp/gmp-4.2.1/x86-fat.diff
mtn: adding packages/gmp/gmp-4.2.2/amd64.patch
mtn: adding packages/gmp/gmp-4.2.2/sh4-asmfix.patch
mtn: adding packages/gmp/gmp-4.2.2/x86-fat.diff
mtn: dropping packages/gmp/files
mtn: updated to base revision f3aafac33dd3d98133bfd91efdee783ccd8da959
koen@lieve:/OE/org.openembedded.dev/packages/gmp$ find . | grep amd64
./gmp-4.1.2/amd64.patch
./gmp-4.1.4/amd64.patch
./gmp-4.2.1/amd64.patch
./gmp-4.2.2/amd64.patch
OK, so I have the patches back, now see if they are all the same, as
claimed by the commit:
koen@lieve:/OE/org.openembedded.dev/packages/gmp$ find . | grep amd64 |
xargs md5sum
9c015f16636e1fd0d2f374672b7004a5 ./gmp-4.1.2/amd64.patch
a9876747e7ae95ee64f505022b92bb10 ./gmp-4.1.4/amd64.patch
a9876747e7ae95ee64f505022b92bb10 ./gmp-4.2.1/amd64.patch
a9876747e7ae95ee64f505022b92bb10 ./gmp-4.2.2/amd64.patch
Nope they aren't. Revision disapproved to unbreak my build.
This is the second time this week[1] that a 'cleanup' breaks the build.
Please pay more attention (e.g. 'for bb in *.bb ; do bitbake -b $bb -c
patch ; done') when doing things like this.
[1]
http://lists.linuxtogo.org/pipermail/openembedded-commits/2008-May/014437.html
next reply other threads:[~2008-05-08 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 6:58 Koen Kooi [this message]
2008-05-08 11:21 ` Disapproval of revision b8e46b797b32111526a2116d020fdd9e1c079965 Rolf Leggewie
2008-05-08 12:34 ` pHilipp Zabel
2008-05-08 13:25 ` Koen Kooi
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='fvu8b8$kl2$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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.