From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: Re: [gentoo-dev-announce] repositories.xml now served via api.gentoo.org
Date: Mon, 29 Jul 2013 16:09:58 -0700 [thread overview]
Message-ID: <1375139398.15964.31.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <51F694B8.2050702@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]
On Mon, 2013-07-29 at 18:13 +0200, Alex Legler wrote:
> The overlays configuration file repositories.xml is the first file that
> is now being served via api.gentoo.org.
>
> New public URL: https://api.gentoo.org/overlays/repositories.xml
> Git repository: git+ssh://git@git.gentoo.org/proj/api.git
>
> The old URL will redirect to the new one.
>
The new url is in layman's git and is available in layman-9999 now. It
is also an easy edit in /etc/layman/layman.cfg to change the url to the
new one. Due to a python ssl limitation, <python-3.2 is not capable of
verifying the https connection. There is a backport of the changes
available which I will create an ebuild for so that layman can verify
the connection.
I will get a new release out soon which will include the new portage
repos.conf style configuration changes. Also coming very soon will be a
gpg signed repositories.xml file which layman-9999 is already capable of
verifying. I will be changing it to use the new gentoo-keys project
which wraps the pyGPG lib I'm using in layman currently. Currently
layman requires you to manually install the gentoo gpg release keys to
verify against. The gentoo-keys project will automate that and provide
access to the correct keyrings for verification.
For stable layman to not use the redirect, edit /etc/layman/layman.cfg.
Change:
overlays:
http://www.gentoo.org/proj/en/overlays/repositories.xml
to:
overlays:
https://api.gentoo.org/overlays/repositories.xml
There will likely be 1 leftover cache file and it's correcponding
timestamp file in /var/lib/layman since it uses a hash of the url as
part of the filename. The new url will produce a new, different hash
and subsequently a new pair of files. I will work on detecting that in
layman-updater and remove it automatically on upgrade. In the meantime
they can be removed manually.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
prev parent reply other threads:[~2013-07-29 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 16:13 [gentoo-dev-announce] repositories.xml now served via api.gentoo.org Alex Legler
2013-07-29 23:09 ` Brian Dolbec [this message]
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=1375139398.15964.31.camel@big_daddy.dol-sen.ca \
--to=dolsen@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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