From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] package.bbclass: when running 'file', be explicit about the path to the magic
Date: Mon, 01 Mar 2010 10:47:20 +0100 [thread overview]
Message-ID: <hmg2f8$usj$1@dough.gmane.org> (raw)
In-Reply-To: <20100301094515.GI30145@xora-desktop.xora.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01-03-10 10:45, Graeme Gregory wrote:
> On Mon, Mar 01, 2010 at 10:35:36AM +0100, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I think I know what's happening.
>>
>> On my (debian) buildhost I have file 4.26. (Re)building file-native 5.04
>> gives me:
>>
>> ./staging/x86_64-linux/usr/share/misc/magic.mgc
>>
>> Graeme has file 5.03 on his buildhost and has
>>
>> ./staging/x86_64-linux/usr/share/file/magic
>>
>> So it seems that the buildhost contamination also affects file-native :(
>>
> Its not contamination, its just simply that file 5.XX moved its magic
> file to /usr/share/misc/
>
> Im still building 4.21 for some reason so dont see this.
Bitbake 1.8.x? I'm using bitbake master from git, that has a different
sorting algo AIUI.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLi40oMkyGM64RGpERAjEIAJ4+rW+07FQBjx9std0w7ZE1tYcdtQCgtgI6
X6RRtXw6ttRVlMSfzyUAUBk=
=QSlm
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-01 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 18:47 [PATCH] package.bbclass: when running 'file', be explicit about the path to the magic Chris Larson
2010-03-01 9:17 ` Koen Kooi
2010-03-01 9:35 ` Koen Kooi
2010-03-01 9:45 ` Graeme Gregory
2010-03-01 9:47 ` Koen Kooi [this message]
2010-03-01 13:42 ` Chris Larson
2010-03-01 13:51 ` Philip Balister
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='hmg2f8$usj$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox