how to un-blacklist a blacklisted recipe?

how to un-blacklist a blacklisted recipe?

[Robert P. J. Day]

  asking what is almost certainly a silly question, but as i'm poring
over the wind river LTS 19 (aka "zeus") developer's guide, i know that
WR adds a feature for un-blacklisting blacklisted recipes via the
PNWHITELIST variable, but the guide says something quite different in
that it suggests that one can clear a blacklist from a recipe by
setting the blacklist message to the empty string, as in:

  PNBLACKLIST[recipe] = ""

https://docs.windriver.com/bundle/Wind_River_Linux_Platform_Developers_Guide_LTS_19_tki1589820771450/page/inj1480988608162.html

  um, wut?

  oddly, there is no mention of WR's PNWHITELIST feature on that page,
so i assumed that 1) someone forgot to update the guide to mention it,
and 2) setting the message to the empty string might be the standard
YP way to do it, but i'm pretty sure that won't work.

  is there a way to un-blacklist a blacklisted recipe using standard
YP? the reference manual entry for PNBLACKLIST doesn't suggest so:

https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PNBLACKLIST

  thoughts?

rday

Re: [yocto] how to un-blacklist a blacklisted recipe?

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]

I don't use WR, but setting it to empty works fine for me.

Why do you think it shouldn't work? See
https://git.openembedded.org/openembedded-core/tree/meta/classes/blacklist.bbclass#n18

On Mon, May 25, 2020 at 6:38 PM Robert P. J. Day <rpjday@crashcourse.ca>
wrote:

>
>   asking what is almost certainly a silly question, but as i'm poring
> over the wind river LTS 19 (aka "zeus") developer's guide, i know that
> WR adds a feature for un-blacklisting blacklisted recipes via the
> PNWHITELIST variable, but the guide says something quite different in
> that it suggests that one can clear a blacklist from a recipe by
> setting the blacklist message to the empty string, as in:
>
>   PNBLACKLIST[recipe] = ""
>
>
> https://docs.windriver.com/bundle/Wind_River_Linux_Platform_Developers_Guide_LTS_19_tki1589820771450/page/inj1480988608162.html
>
>   um, wut?
>
>   oddly, there is no mention of WR's PNWHITELIST feature on that page,
> so i assumed that 1) someone forgot to update the guide to mention it,
> and 2) setting the message to the empty string might be the standard
> YP way to do it, but i'm pretty sure that won't work.
>
>   is there a way to un-blacklist a blacklisted recipe using standard
> YP? the reference manual entry for PNBLACKLIST doesn't suggest so:
>
>
> https://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PNBLACKLIST
>
>   thoughts?
>
> rday
>
>
>
> 
>

[-- Attachment #2: Type: text/html, Size: 2291 bytes --]

Re: [yocto] how to un-blacklist a blacklisted recipe?

[Robert P. J. Day]

On Mon, 25 May 2020, Martin Jansa wrote:

> I don't use WR, but setting it to empty works fine for me.
> Why do you think it shouldn't work? See
> https://git.openembedded.org/openembedded-core/tree/meta/classes/blacklist.bbclass#n18

  i tested it ... at least i *thought* i tested it on a blacklisted
recipe. i'll try it again, i guess i just misspelled something.

rday

Re: [yocto] how to un-blacklist a blacklisted recipe?

[Robert P. J. Day]

On Mon, 25 May 2020, Martin Jansa wrote:

> I don't use WR, but setting it to empty works fine for me.

  *where* did you set it to empty? in your local.conf?

> Why do you think it shouldn't work? See
> https://git.openembedded.org/openembedded-core/tree/meta/classes/blacklist.bbclass#n18

Re: [yocto] how to un-blacklist a blacklisted recipe?

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 665 bytes --]

Yes, in local.conf or distro config, both work fine.

Maybe your PNBLACKLIST you're trying to unblacklist is using normal
assignment instead of weak one? See
http://git.openembedded.org/meta-openembedded/commit/?id=96a92761c0a1bb2317fa4ea422c32e4473405103

On Mon, May 25, 2020 at 7:22 PM Robert P. J. Day <rpjday@crashcourse.ca>
wrote:

> On Mon, 25 May 2020, Martin Jansa wrote:
>
> > I don't use WR, but setting it to empty works fine for me.
>
>   *where* did you set it to empty? in your local.conf?
>
> > Why do you think it shouldn't work? See
> >
> https://git.openembedded.org/openembedded-core/tree/meta/classes/blacklist.bbclass#n18
>

[-- Attachment #2: Type: text/html, Size: 1256 bytes --]

Re: [yocto] how to un-blacklist a blacklisted recipe?

[Robert P. J. Day]

On Mon, 25 May 2020, Martin Jansa wrote:

> Yes, in local.conf or distro config, both work fine. Maybe your
> PNBLACKLIST you're trying to unblacklist is using normal assignment
> instead of weak one? See

  i just now determined that that is exactly what is happening --
tried it with nanopb recipe from meta-oe, which contains:

  PNBLACKLIST[nanopb] = "Needs forward porting to use python3"

switched that to weak assignment, all good. does that imply that,
other than in perhaps exceptional circumstances, *all* blacklisting
should use weak assignment?

rday

Re: [yocto] how to un-blacklist a blacklisted recipe?

[Robert P. J. Day]

On Mon, 25 May 2020, Robert P. J. Day wrote:

> On Mon, 25 May 2020, Martin Jansa wrote:
>
> > Yes, in local.conf or distro config, both work fine. Maybe your
> > PNBLACKLIST you're trying to unblacklist is using normal assignment
> > instead of weak one? See
>
>   i just now determined that that is exactly what is happening --
> tried it with nanopb recipe from meta-oe, which contains:
>
>   PNBLACKLIST[nanopb] = "Needs forward porting to use python3"
>
> switched that to weak assignment, all good. does that imply that,
> other than in perhaps exceptional circumstances, *all* blacklisting
> should use weak assignment?

  never mind, just took a look at the commit which does exactly this.
is it worth submitting a patch to tweak the few hard assignments?

rday

Re: [yocto] how to un-blacklist a blacklisted recipe?

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 944 bytes --]

Yes, it's worth. Thanks

On Mon, May 25, 2020 at 7:40 PM Robert P. J. Day <rpjday@crashcourse.ca>
wrote:

> On Mon, 25 May 2020, Robert P. J. Day wrote:
>
> > On Mon, 25 May 2020, Martin Jansa wrote:
> >
> > > Yes, in local.conf or distro config, both work fine. Maybe your
> > > PNBLACKLIST you're trying to unblacklist is using normal assignment
> > > instead of weak one? See
> >
> >   i just now determined that that is exactly what is happening --
> > tried it with nanopb recipe from meta-oe, which contains:
> >
> >   PNBLACKLIST[nanopb] = "Needs forward porting to use python3"
> >
> > switched that to weak assignment, all good. does that imply that,
> > other than in perhaps exceptional circumstances, *all* blacklisting
> > should use weak assignment?
>
>   never mind, just took a look at the commit which does exactly this.
> is it worth submitting a patch to tweak the few hard assignments?
>
> rday
>

[-- Attachment #2: Type: text/html, Size: 1340 bytes --]

Re: [yocto] how to un-blacklist a blacklisted recipe?

[Robert P. J. Day]

On Mon, 25 May 2020, Martin Jansa wrote:

> Yes, it's worth. Thanks

  done, and submitted. it was just my horrific luck that i was testing
that feature, and randomly grabbed two recipes that used standard
assignment. le *sigh* ...

rday