From: "Randy MacLeod" <randy.macleod@windriver.com>
To: akhilathota499@gmail.com, yocto@lists.yoctoproject.org,
bluelightning@bluelightning.org
Subject: Re: [yocto] Bug 10699 - Ensure consistency in repository URLs #yocto #python
Date: Fri, 9 Oct 2020 11:25:29 -0400 [thread overview]
Message-ID: <0fd65868-c4da-5783-3768-0156e2a0b12e@windriver.com> (raw)
In-Reply-To: <P0Lg.1602187991583242378.u0pz@lists.yoctoproject.org>
On 2020-10-08 4:13 p.m., akhilathota499@gmail.com wrote:
> Hi,
> I would like to work on #10699 -- Ensure consistency in repository URLs
> bug. Kindly help me to move forward by providing more information on
> this issue(like where I can find more URL's mentioned in the request)
Hi Akhila,
This bug is about the data in the recipes in oe-core and all layers.
There is a layer tracking system called 'the layer index':
https://layers.openembedded.org
where you can search by various keys such as recipe name, layer name, etc.
If you go to the bottom of that page, you can find:
https://layers.openembedded.org/layerindex/about
and that page has a link to the source code:
http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/
git clone git://git.yoctoproject.org/layerindex-web
I don't work on this code so if you have questions, hopefully Paul
(bluelightning) or someone else will help out. My take is that:
"we'll probably need to have a table (possibly in the database)
that we can populate with mappings for known URLs."
so you'll need to find where the SRC_URI such as line 8 here:
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-devtools/patch/patch.inc?h=master#n8
is stored in the layerindex code and add each SRC_URI to a table or
some other data structure.
Then, when a new layer is added the layerindex would use this table
to ensure that there are no duplicates that differ only by
the transport, i.e. "https://" vs "git://", as mentioned in the bug:
"The mapping would be done when the entry is submitted."
Also, there are no fixed rules here in Yocto land but you are free to
ask about things either on the list to a wide audience or in the
Bugzilla comments (once you have an account!).
> and kindly assign it to me.
If you create an account in the bugzilla:
https://bugzilla.yoctoproject.org/createaccount.cgi
you should be able to assign the defect to yourself.
Let us know if that doesn't work.
Thanks for looking into this bug.
../Randy
>
>
>
>
--
# Randy MacLeod
# Wind River Linux
next prev parent reply other threads:[~2020-10-09 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 20:13 Bug 10699 - Ensure consistency in repository URLs #yocto #python akhilathota499
2020-10-09 15:25 ` Randy MacLeod [this message]
2020-10-09 18:08 ` [yocto] " 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=0fd65868-c4da-5783-3768-0156e2a0b12e@windriver.com \
--to=randy.macleod@windriver.com \
--cc=akhilathota499@gmail.com \
--cc=bluelightning@bluelightning.org \
--cc=yocto@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox