From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] recipeutils adds get_recipe_upstream_version and distrodata fixes
Date: Thu, 04 Jun 2015 11:54:32 -0500 [thread overview]
Message-ID: <557082C8.2090907@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LbAsutsVamsW4mYt8rKHL069DKFKhWMYhwMK-o9tcabwQ@mail.gmail.com>
Hi Ross,
The problem is i forget to add v2 to the patch [1] that is a new version
of the patch [2], sorry
about that.
Kind regards,
alimon
[1]
http://lists.openembedded.org/pipermail/openembedded-core/2015-June/105576.html
[2]
http://lists.openembedded.org/pipermail/openembedded-core/2015-June/105534.html
On 04/06/15 11:09, Burton, Ross wrote:
> On 2 June 2015 at 20:49, Aníbal Limón <anibal.limon@linux.intel.com> wrote:
>
>> Aníbal Limón (4):
>> recipeutils: Add get_recipe_upstream_version and
>> get_recipe_pv_without_srcpv functions
>> distrodata: Remove unnecessary include of package_regex.inc
>> distrodata: checkpkg make usage of
>> oe.recipeutils.get_recipe_upstream_version
>> distrodata: Use Python CSV instead of did by hand
>>
> This series is causing this error if I run core-image-sato -c checkpkgall:
>
> ERROR: Error executing a python function in
> /home/ross/Yocto/poky/meta/recipes-graphics/xorg-lib/libxcalibrate_git.bb:
>
> The stack trace of python calls that resulted in this exception/failure was:
> File: 'do_checkpkg', lineno: 126, function: <module>
> 0122: f.close()
> 0123: bb.utils.unlockfile(lf)
> 0124:
> 0125:
> *** 0126:do_checkpkg(d)
> 0127:
> File: 'do_checkpkg', lineno: 87, function: do_checkpkg
> 0083: """Set upstream version status"""
> 0084: if not pupver:
> 0085: pupver = "N/A"
> 0086: else:
> *** 0087: pv, _, _ =
> oe.recipeutils.get_recipe_pv_without_srcpv(pversion, uri_type)
> 0088: upv, _, _ =
> oe.recipeutils.get_recipe_pv_without_srcpv(pupver, uri_type)
> 0089:
> 0090: cmp = vercmp_string(pv, upv)
> 0091: if cmp == -1:
> File: '/home/ross/Yocto/poky/meta/lib/oe/recipeutils.py', lineno: 641,
> function: get_recipe_pv_without_srcpv
> 0637: pfx = ''
> 0638: sfx = ''
> 0639:
> 0640: if uri_type == 'git':
> *** 0641: rd_tmp = rd.createCopy()
> 0642:
> 0643: rd_tmp.setVar('SRCPV', '')
> 0644: pv = rd_tmp.getVar('PV', True)
> 0645:
> Exception: AttributeError: 'str' object has no attribute 'createCopy'
>
> Ross
>
next prev parent reply other threads:[~2015-06-04 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 19:49 [PATCH 0/4] recipeutils adds get_recipe_upstream_version and distrodata fixes Aníbal Limón
2015-06-02 19:49 ` [PATCH 1/4] recipeutils: Add get_recipe_upstream_version and get_recipe_pv_without_srcpv functions Aníbal Limón
2015-06-02 19:49 ` [PATCH 2/4] distrodata: Remove unnecessary include of package_regex.inc Aníbal Limón
2015-06-02 19:49 ` [PATCH 3/4] distrodata: checkpkg make usage of oe.recipeutils.get_recipe_upstream_version Aníbal Limón
2015-06-02 19:49 ` [PATCH 4/4] distrodata: Use Python CSV instead of did by hand Aníbal Limón
2015-06-04 16:09 ` [PATCH 0/4] recipeutils adds get_recipe_upstream_version and distrodata fixes Burton, Ross
2015-06-04 16:54 ` Aníbal Limón [this message]
2015-06-04 16:54 ` Burton, Ross
2015-06-04 16:58 ` Aníbal Limón
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=557082C8.2090907@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox