meta-python/rocko

meta-python/rocko

[Mirza Krak]

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 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.


[1]. http://cgit.openembedded.org/meta-openembedded/commit/meta-python?h=rocko&id=187f959fbd220678595c2aa1fe1e17b00a0b2d92

[2]. http://cgit.openembedded.org/meta-openembedded/commit/meta-python/recipes-devtools/python/python3-asn1crypto_0.24.0.bb?id=80b6e6f151588765000cf17d2b86d0ded762def1

-- 
Med Vänliga Hälsningar / Best Regards

Mirza Krak

Re: meta-python/rocko

[Derek Straka]

On Mon, Mar 19, 2018 at 9:45 AM, Mirza Krak <mirza.krak@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?
> id=80b6e6f151588765000cf17d2b86d0ded762def1
>
> --
> Med Vänliga Hälsningar / Best Regards
>
> Mirza Krak
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>

Re: meta-python/rocko

[Derek Straka]

Ah, you wanted the python3 version.  I just noticed that.  Stand by

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

>
>
> On Mon, Mar 19, 2018 at 9:45 AM, Mirza Krak <mirza.krak@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@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
>
>

Re: meta-python/rocko

[Derek Straka]

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@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@asterius.io> wrote:
>
>>
>>
>> On Mon, Mar 19, 2018 at 9:45 AM, Mirza Krak <mirza.krak@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@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>>
>>
>>
>

Re: meta-python/rocko

[Mirza Krak]

On 19 March 2018 at 14:56, Derek Straka <derek@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@asterius.io> wrote:
>>
>> Ah, you wanted the python3 version.  I just noticed that.  Stand by

Thanks for a swift response and fix.

-- 
Med Vänliga Hälsningar / Best Regards

Mirza Krak

Re: meta-python/rocko

[Derek Straka]

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@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@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@asterius.io> wrote:
>>
>>>
>>>
>>> On Mon, Mar 19, 2018 at 9:45 AM, Mirza Krak <mirza.krak@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@lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>>>
>>>
>>>
>>
>

Re: meta-python/rocko

[Tim Orling]

Thank you for jumping on this, Derek!
And thank you for catching the issue, Mirza. Extra eyes and hands are very
helpful to keep up our quality.

—Tim

Re: meta-python/rocko

[Philip Balister]

On 03/01/2018 09:49 AM, akuster808 wrote:
> Check rocko-next.
> 

Yes, this looks good to me!

Philip

> 
> 
> On 03/01/2018 06:39 AM, Martin Jansa wrote:
>> Read this thread:
>> http://lists.openembedded.org/pipermail/openembedded-devel/2018-February/116622.html
>>
>> On Thu, Mar 1, 2018 at 3:22 PM, Philip Balister <philip@balister.org> wrote:
>>
>>> I'm trying to build some gnuradio related stuff and am running into
>>> issues in meta-python with DEPENDS and missing recipes. Does anyone
>>> understand what is going on and have a plan to fix it, or do I need to
>>> dig further and figure out what needs doing?
>>>
>>> Philip
>>> --
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>>
> 
> 

Re: meta-python/rocko

[akuster808]

Check rocko-next.



On 03/01/2018 06:39 AM, Martin Jansa wrote:
> Read this thread:
> http://lists.openembedded.org/pipermail/openembedded-devel/2018-February/116622.html
>
> On Thu, Mar 1, 2018 at 3:22 PM, Philip Balister <philip@balister.org> wrote:
>
>> I'm trying to build some gnuradio related stuff and am running into
>> issues in meta-python with DEPENDS and missing recipes. Does anyone
>> understand what is going on and have a plan to fix it, or do I need to
>> dig further and figure out what needs doing?
>>
>> Philip
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>

Re: meta-python/rocko

[Martin Jansa]

Read this thread:
http://lists.openembedded.org/pipermail/openembedded-devel/2018-February/116622.html

On Thu, Mar 1, 2018 at 3:22 PM, Philip Balister <philip@balister.org> wrote:

> I'm trying to build some gnuradio related stuff and am running into
> issues in meta-python with DEPENDS and missing recipes. Does anyone
> understand what is going on and have a plan to fix it, or do I need to
> dig further and figure out what needs doing?
>
> Philip
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>

meta-python/rocko

[Philip Balister]

I'm trying to build some gnuradio related stuff and am running into
issues in meta-python with DEPENDS and missing recipes. Does anyone
understand what is going on and have a plan to fix it, or do I need to
dig further and figure out what needs doing?

Philip