From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] opkg-build: Ignore tar error due to hardlinks issue when creating ipk files
Date: Mon, 06 Jul 2015 16:10:04 -0500 [thread overview]
Message-ID: <559AEEAC.8080005@linux.intel.com> (raw)
In-Reply-To: <20150706201018.GD2436@jama>
On 06/07/15 15:10, Martin Jansa wrote:
> On Mon, Jul 06, 2015 at 10:17:19AM +0000, Alejandro Hernandez wrote:
>
> +
> +This a similar behavior to the one on dpkg:
> +http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40731942515ec8d80c727ad561174986d4f05818
> +
> +Upsteam-Status: Inappropriate
> Typo and why is it inappropriate? Looks like bugfix to me, even for
> issue which usually happens in OE way of using opkg-build.
It seemed inappropriate to me, since this behavior is not expected
(number of hardlinks changing), we can't say for sure that this error
will be caused by this reason on when using opkg on another environment
>
> -SRC_URI = "git://git.yoctoproject.org/opkg-utils"
> +SRC_URI = "git://git.yoctoproject.org/opkg-utils "
> +
> +SRC_URI_append_class-native = "file://tar_ignore_error.patch"
> Add leading space in append not in original SRC_URI variable.
>
> Why is it applied only for native anyway?
Same argument as before, modifying the number of hardlinks while the tar
is created happens when building using bitbake, which should not happen
on target, if files changed when creating an ipk for any other reason it
shouldn't be ignored; space was a typo
next prev parent reply other threads:[~2015-07-06 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1436177709.git.alejandro.hernandez@linux.intel.com>
2015-07-06 10:17 ` [PATCH 1/1] opkg-build: Ignore tar error due to hardlinks issue when creating ipk files Alejandro Hernandez
2015-07-06 20:10 ` Martin Jansa
2015-07-06 21:10 ` Alejandro Hernandez [this message]
2015-07-06 21:16 ` Gary Thomas
2015-07-06 21:20 ` Otavio Salvador
2015-07-06 21:31 ` Richard Purdie
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=559AEEAC.8080005@linux.intel.com \
--to=alejandro.hernandez@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@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