[oe] meta-python/rocko

Derek Straka derek at asterius.io
Mon Mar 19 14:04:22 UTC 2018


I sent out a backport request [1] for commit 084db496 [2], which actually
added the first python3 version of the recipe.  You can cherry-pick in the
interim.

[1] - http://lists.openembedded.org/pipermail/openembedded-
devel/2018-March/117349.html
[2] -
http://lists.openembedded.org/pipermail/openembedded-devel/2017-October/115233.html


On Mon, Mar 19, 2018 at 9:56 AM, Derek Straka <derek at asterius.io> wrote:

> Yeah.  The python3 version wasn't there in rocko.  I'll send out a patch.
> Thanks for catching this.
>
> On Mon, Mar 19, 2018 at 9:55 AM, Derek Straka <derek at asterius.io> wrote:
>
>> Ah, you wanted the python3 version.  I just noticed that.  Stand by
>>
>> On Mon, Mar 19, 2018 at 9:54 AM, Derek Straka <derek at asterius.io> wrote:
>>
>>>
>>>
>>> On Mon, Mar 19, 2018 at 9:45 AM, Mirza Krak <mirza.krak at gmail.com>
>>> wrote:
>>>
>>>> Hi.
>>>>
>>>> I came across some break-age in meta-python/rocko. More specifically
>>>> that there is no python3-asn1crypto recipe though several packages
>>>> depend on it.  I can trigger this by building python3-requests.
>>>>
>>>
>>> I see the commit adding python-asn1cryto in the rocko branch.  Are you
>>> using an outdated rocko branch?  What commit is HEAD in your rocko branch?
>>>
>>>
>>>> I was reading the archives of the mailing list that indicated that
>>>> there some some instability regarding meta-python recently but nothing
>>>> covering this.
>>>>
>>>> I noticed the following commit [1], which mentions that it should be
>>>> merged together with another commit to actually add the
>>>> python3-asn1crypto. Which seems did not actually happen when the merge
>>>> was done.
>>>>
>>>> python3-asn1crypto was actually added in this commit [1] on master and
>>>> I can not seen that it has been back-ported. Note the somewhat commit
>>>> cryptic commit message in [2] where it does not actually say that it
>>>> added a python3-asn1crypto package.
>>>>
>>>
>>> To see the full history of a file, you'll need to tell git to follow,
>>> and you can see it was added in commit 8ceeb8b[1] not 80b6e6; however, both
>>> are in rocko.
>>>
>>> `git log --follow ./meta-python/recipes-devtools/python/python3-
>>> asn1crypto_0.24.0.bb`
>>>
>>> [1] - http://cgit.openembedded.org/meta-openembedded/commit/meta
>>> -python?h=rocko&id=8ceeb8b512a265b03b2175943a01d9318ebb8634
>>>
>>>
>>> -Derek
>>>
>>>>
>>>>
>>>> [1]. http://cgit.openembedded.org/meta-openembedded/commit/meta-p
>>>> ython?h=rocko&id=187f959fbd220678595c2aa1fe1e17b00a0b2d92
>>>>
>>>> [2]. http://cgit.openembedded.org/meta-openembedded/commit/meta-p
>>>> ython/recipes-devtools/python/python3-asn1crypto_0.24.0.bb?i
>>>> d=80b6e6f151588765000cf17d2b86d0ded762def1
>>>>
>>>> --
>>>> Med Vänliga Hälsningar / Best Regards
>>>>
>>>> Mirza Krak
>>>> --
>>>> _______________________________________________
>>>> Openembedded-devel mailing list
>>>> Openembedded-devel at lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>>>
>>>
>>>
>>
>



More information about the Openembedded-devel mailing list