All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Barker" <paul@betafive.co.uk>
To: "Paul Eggleton" <paul.eggleton@linux.intel.com>,
	"Nicolas Dechesne" <nicolas.dechesne@linaro.org>
Cc: "Yocto discussion list" <yocto@yoctoproject.org>,
	yocto@lists.yoctoproject.org
Subject: Re: [yocto] Missing layer in the layer index
Date: Thu, 05 Dec 2019 08:48:48 +0000	[thread overview]
Message-ID: <717103ea-e4b3-4e9e-88eb-e31f80eb1cb3@www.fastmail.com> (raw)
In-Reply-To: <1725959.xBGxL0dlV4@shodan>

On Thu, 5 Dec 2019, at 01:37, Paul Eggleton wrote:
> On Wednesday, 4 December 2019 11:10:49 PM NZDT Nicolas Dechesne wrote:
> > > I'd like to make sure meta-sancloud (https://github.com/SanCloudLtd/meta-> > sancloud) is listed in the layer index. I can't see it listed for either
> > > of the branches we support (thud & rocko). However, when I try to add the
> > > layer I get the error message "Layer with this Layer name already exists."
> > >
> > > Perhaps this was already added with an old URL. Is there any way to get
> > > this fixed up?
> > 
> > yes, this is the reason. It exists with the following URL:
> > https://bitbucket.sancloud.co.uk/scm/yb/meta-sancloud.git
> > 
> > The maintainer for that layer is not listed.. was it you?
> 
> Oddly there are no maintainer records and no layer branch records either, 
> hence why the layer doesn't show up properly. I'm unsure how it would have got 
> into that state or how long it's been there, but since it's pretty much 
> useless I have gone ahead and deleted it - Paul, could you please file your 
> submission again?

Thanks for that, it may have got broken in the layer index when we moved the repo from our private Bitbucket instance over to GitHub. I've resubmitted now.

-- 
Paul Barker

  reply	other threads:[~2019-12-05  8:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04  9:59 Missing layer in the layer index Paul Barker
2019-12-04 10:10 ` [yocto] " Nicolas Dechesne
2019-12-05  1:37   ` Paul Eggleton
2019-12-05  8:48     ` Paul Barker [this message]
2019-12-05 10:07       ` Paul Eggleton
2019-12-05 11:18         ` Paul Barker
2019-12-05 16:38           ` Denys Dmytriyenko

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=717103ea-e4b3-4e9e-88eb-e31f80eb1cb3@www.fastmail.com \
    --to=paul@betafive.co.uk \
    --cc=nicolas.dechesne@linaro.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=yocto@lists.yoctoproject.org \
    --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.