All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCHv2] [layerindex-web] recipe blacklisted information
Date: Tue, 1 Dec 2015 10:40:58 +0100	[thread overview]
Message-ID: <20151201094058.GA2251@jama> (raw)
In-Reply-To: <2603447.ByLEse0mF5@peggleto-mobl.ger.corp.intel.com>

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

On Tue, Dec 01, 2015 at 11:22:01AM +1300, Paul Eggleton wrote:
> Hi Alex,
> 
> On Mon, 30 Nov 2015 16:03:05 Alex Franco wrote:
> > Display blacklisted information for recipes on Layerindex, in the
> > recipe details, as well as the recipe search page, and layer page
> > tables. This information is pulled from the PNBLACKLIST variable.
> > Includes a hover text containing the reason for blacklist labels.
> > 
> > Changes to Django and Layerindex files:
> > - models.py, update.py
> > - migration file
> > - templates and static content (stylesheet)
> > 
> > [YOCTO #7855]
> > 
> > Signed-off-by: Alex Franco <alejandro.franco@linux.intel.com>
> > ---
> >  .../0010_auto__add_field_recipe_blacklisted.py     | 197
> > +++++++++++++++++++++ layerindex/models.py                               | 
> >  1 +
> >  layerindex/static/css/additional.css               |  19 +-
> >  layerindex/update.py                               |   1 +
> >  templates/layerindex/detail.html                   |   3 +-
> >  templates/layerindex/recipedetail.html             |  13 +-
> >  templates/layerindex/recipes.html                  |   3 +-
> >  7 files changed, 232 insertions(+), 5 deletions(-)
> >  create mode 100644
> > layerindex/migrations/0010_auto__add_field_recipe_blacklisted.py
> > 
> This looks great, thanks.
> 
> Another thing that just occurred to me though - apologies for not raising it 
> earlier - for the benefit of newer users it may be useful to explain 
> implications of the blacklisting. What I'd suggest is we put a line after the 
> reason on the recipe detail page saying "This means that the recipe will not 
> be buildable until the PNBLACKLIST value is cleared and the issue that caused 
> it to be added has been fixed or worked around." (Just on the recipe detail 
> page - not in the popup.)
> 
> Does that sound OK?

Maybe some more information how to clear PNBLACKLIST (people often don't
know that they can just set it to empty value in their bbappend or even
distro/local config).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  parent reply	other threads:[~2015-12-01  9:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 22:03 [PATCHv2] [layerindex-web] recipe blacklisted information Alex Franco
2015-11-30 22:22 ` Paul Eggleton
2015-11-30 22:42   ` strange QA issue - how to ignore automatic so dependency Dvorkin Dmitry
2015-11-30 23:06     ` Khem Raj
2015-11-30 23:15       ` Dvorkin Dmitry
2015-11-30 23:22         ` Khem Raj
2015-11-30 23:32           ` Dvorkin Dmitry
2015-12-01  9:40   ` Martin Jansa [this message]
2015-12-01 10:42     ` [PATCHv2] [layerindex-web] recipe blacklisted information Barros Pena, Belen
2015-12-01 11:14       ` Martin Jansa
     [not found]         ` <565DDB89.1030005@intel.com>
2015-12-01 18:26           ` Alex Franco
2015-12-01 19:11             ` Paul Eggleton
2015-12-02  0:47               ` Alex Franco
2015-12-02 11:38                 ` Barros Pena, Belen
2015-12-02 11:35               ` Barros Pena, Belen
2015-12-02 20:02                 ` Paul Eggleton

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=20151201094058.GA2251@jama \
    --to=martin.jansa@gmail.com \
    --cc=paul.eggleton@intel.com \
    --cc=yocto@yoctoproject.org \
    /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.