From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: saul.wold@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 5/5] rootfs.py: tweak _multilib_sanity_test for ipk incremental image generation
Date: Tue, 18 Feb 2014 17:36:20 +0200 [thread overview]
Message-ID: <20140218153617.GC22316@lpalcu-linux> (raw)
In-Reply-To: <8581ec40c107111a8001742d8b636a76910f5f5f.1392716065.git.hongxu.jia@windriver.com>
On Tue, Feb 18, 2014 at 05:42:28PM +0800, Hongxu Jia wrote:
> The _multilib_sanity_test installs multilib packages in a temporary
> root fs, and compare with the current image to figure out duplicated
> file that comes from different packages.
>
> While incremental image generation enabled and the previous image
> existed, there was a Multilib check error:
> ...
> ERROR: Multilib check error: duplicate files tmp/work/qemux86_64-poky-
> linux/core-image-minimal/1.0-r0/multilib/lib32/lib/libc.so.6 tmp/work/
> qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs/lib/libc.so.6
> is not the same
> ...
>
> The reason is the file in current image has been prelinked in previous
> image generation and the file in a temporary root fs is not prelinked,
> even though the files come from the same package, the Multilib check
> considers they are different.
>
> [YOCTO #1894]
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
> meta/lib/oe/rootfs.py | 56 +++++++++++++++++++++++++++++++++++++++++++++++----
> 1 file changed, 52 insertions(+), 4 deletions(-)
>
> diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py
> index 3d7adf9..5054d1e 100644
> --- a/meta/lib/oe/rootfs.py
> +++ b/meta/lib/oe/rootfs.py
> @@ -3,6 +3,8 @@ from oe.utils import execute_pre_post_process
> from oe.utils import contains as base_contains
> from oe.package_manager import *
> from oe.manifest import *
> +import oe.path
> +import filecmp
> import shutil
> import os
> import subprocess
> @@ -458,13 +460,61 @@ class OpkgRootfs(Rootfs):
>
> bb.utils.remove(self.d.getVar('MULTILIB_TEMP_ROOTFS', True), True)
>
> + def _prelink_file(self, root_dir, filename):
> + bb.note('prelink %s in %s' % (filename, root_dir))
> + prelink_cfg = oe.path.join(root_dir,
> + self.d.expand('${sysconfdir}/prelink.conf'))
> + if not os.path.exists(prelink_cfg):
> + shutil.copy(self.d.expand('${STAGING_DIR_NATIVE}${sysconfdir_native}/prelink.conf'),
> + prelink_cfg)
> +
> + cmd_prelink = self.d.expand('${STAGING_DIR_NATIVE}${sbindir_native}/prelink')
> + self._exec_shell_cmd([cmd_prelink,
> + '--root',
> + root_dir,
> + '-amR',
> + '-N',
> + '-c',
> + self.d.expand('${sysconfdir}/prelink.conf')])
> +
> + '''
> + Compare two files with the same key twice to see if they came
> + from the same package. If they are not same, they are duplicated
> + and come from different packages.
I'm kind of confused by this comment. Doesn't same = duplicate? There
might be a small confusion of terms here because the function's behavior
is not as the name implies.
> + 1st: Comapre them directly;
> + 2nd: While incremental image creation is enabled, one of the
> + files could be probaly prelinked in the previous image
> + creation and the file has been changed, so we need to
> + prelink the other one and compare them.
> + '''
> + def _file_duplicate(self, key, f1, f2):
Shouldn't be better to rename this function to something else in order
to avoid confusion? Let's say: _files_are_equal() ?
> +
> + if not os.path.exists(f1) or not os.path.exists(f2):
> + return False
> +
> + # f1 is the same with f2, both of them were not prelinked
> + if filecmp.cmp(f1, f2):
> + return False
filecmp.cmp() returns True if files are equal. Hence the confusion:
_file_duplicate() returns False here, if files are equal... I think the logic
is a little bit the other way around! :)
> +
> + if self.image_rootfs not in f1:
> + self._prelink_file(f1.replace(key, ''), f1)
> +
> + if self.image_rootfs not in f2:
> + self._prelink_file(f2.replace(key, ''), f2)
> +
> + # f1 is the same with f2, both of them were prelinked
> + if filecmp.cmp(f1, f2):
> + return False
> +
> + # Duplicated
> + return True
here the return value matches the comment and the function name! :)
> +
> """
> This function was reused from the old implementation.
> See commit: "image.bbclass: Added variables for multilib support." by
> Lianhao Lu.
> """
> def _multilib_sanity_test(self, dirs):
> - import filecmp
>
> allow_replace = self.d.getVar("MULTILIBRE_ALLOW_REP", True)
> if allow_replace is None:
> @@ -486,9 +536,7 @@ class OpkgRootfs(Rootfs):
> if allow_rep.match(key):
> valid = True
> else:
> - if os.path.exists(files[key]) and \
> - os.path.exists(item) and \
> - not filecmp.cmp(files[key], item):
> + if self._file_duplicate(key, files[key], item):
> valid = False
> bb.fatal("%s duplicate files %s %s is not the same\n" %
> (error_prompt, item, files[key]))
> --
> 1.8.1.2
>
next prev parent reply other threads:[~2014-02-18 15:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 9:42 [PATCH 0/5] package_manager.py/ootfs.py: support ipk incremental image generation Hongxu Jia
2014-02-18 9:42 ` [PATCH 1/5] package_manager.py: " Hongxu Jia
2014-02-18 14:38 ` Laurentiu Palcu
2014-02-19 9:39 ` Hongxu Jia
2014-02-18 9:42 ` [PATCH 2/5] package_manager.py: tweak handle_bad_recommendations for " Hongxu Jia
2014-02-18 9:42 ` [PATCH 3/5] rootfs.py: support " Hongxu Jia
2014-02-18 9:42 ` [PATCH 4/5] rootfs.py: fix BAD_RECOMMENDATIONS for " Hongxu Jia
2014-02-18 15:03 ` Laurentiu Palcu
2014-02-19 9:44 ` Hongxu Jia
2014-02-18 9:42 ` [PATCH 5/5] rootfs.py: tweak _multilib_sanity_test " Hongxu Jia
2014-02-18 15:36 ` Laurentiu Palcu [this message]
2014-02-19 9:51 ` Hongxu Jia
-- strict thread matches above, loose matches on Subject: below --
2014-02-21 6:38 [PATCH V3 0/5] manifest.py/package_manager.py/rootfs.py: support " Hongxu Jia
2014-02-21 6:38 ` [PATCH 5/5] rootfs.py: tweak _multilib_sanity_test for " Hongxu Jia
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=20140218153617.GC22316@lpalcu-linux \
--to=laurentiu.palcu@intel.com \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.com \
/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.