From: TOMAS FABRIZIO ORSI <torsi@fi.uba.ar>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Eselect repository feature request
Date: Wed, 21 Jun 2023 12:34:39 -0300 [thread overview]
Message-ID: <CAHTSwYjrUew2eM3qm5q9LCm2zVrmw2qkfUjx9uM+zBViFv6TBA@mail.gmail.com> (raw)
In-Reply-To: <CAJ0EP43ZiJbcvB2VB33kLNdMxcB=c0o0Yrd1LmKg4KbPCQ3qJQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
>
> $ sudo emerge --sync
> Unavailable repository 'foo' referenced by masters entry in
> '/var/db/repos/gentoo/metadata/layout.conf'
Oh! I was not aware of this feature. I apologize.
So, in theory, could '%s' be used to automatically enable the missing
repository
(if available in repositories.xml)?
Thank you for you insight,
Best regards,
- Tomas Fabrizio Orsi
El mié, 21 jun 2023 a las 12:07, Mike Gilbert (<floppym@gentoo.org>)
escribió:
> On Wed, Jun 21, 2023 at 10:43 AM TOMAS FABRIZIO ORSI <torsi@fi.uba.ar>
> wrote:
> >>
> >> Sure, I think it could work.
> >
> > Great to hear.
> > In that case I could try to give it a try and make a pull request to the
> emerge --sync with a basic idea.
> > Any tips?
>
> So emerge already emits a warning message when a repo is missing:
>
>
> https://gitweb.gentoo.org/proj/portage.git/tree/lib/portage/repository/config.py?h=portage-3.0.48.1#n1070
>
> That looks something like this:
>
> $ sudo emerge --sync
> Unavailable repository 'foo' referenced by masters entry in
> '/var/db/repos/gentoo/metadata/layout.conf'
>
>
[-- Attachment #2: Type: text/html, Size: 1994 bytes --]
next prev parent reply other threads:[~2023-06-21 15:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 20:39 [gentoo-dev] Eselect repository feature request TOMAS FABRIZIO ORSI
2023-06-20 13:44 ` Florian Schmaus
2023-06-20 14:41 ` TOMAS FABRIZIO ORSI
2023-06-20 17:08 ` Florian Schmaus
2023-06-20 17:26 ` Mike Gilbert
2023-06-20 18:07 ` Andrew Ammerlaan
2023-06-21 2:17 ` TOMAS FABRIZIO ORSI
2023-06-21 7:15 ` Andrew Ammerlaan
2023-06-21 13:40 ` TOMAS FABRIZIO ORSI
2023-06-21 13:58 ` Andrew Ammerlaan
2023-06-21 14:12 ` TOMAS FABRIZIO ORSI
2023-06-21 14:30 ` Andrew Ammerlaan
2023-06-21 14:43 ` TOMAS FABRIZIO ORSI
2023-06-21 15:07 ` Mike Gilbert
2023-06-21 15:34 ` TOMAS FABRIZIO ORSI [this message]
2023-06-21 15:41 ` Florian Schmaus
2023-06-21 15:56 ` Mike Gilbert
2023-06-21 16:47 ` TOMAS FABRIZIO ORSI
2023-06-21 17:45 ` Mike Gilbert
2023-06-21 17:59 ` TOMAS FABRIZIO ORSI
2023-06-24 17:02 ` Florian Schmaus
[not found] ` <8ef315e8-a9fe-c33a-7ab4-ef7653c10cb9@gentoo.org>
[not found] ` <CAHTSwYiXiO2OMU4A5TiunrEy+Zs+UMFwoV3wmSdEW5RNrS5xJA@mail.gmail.com>
[not found] ` <CAHTSwYgO7F2gOOSWHDOBFry4YBb1a1KSy9g8h4iUh+rK0GFRuQ@mail.gmail.com>
[not found] ` <2d264617-f48e-d129-adc2-10aac6cef2a2@gentoo.org>
2023-07-12 18:03 ` TOMAS FABRIZIO ORSI
2023-06-21 17:59 ` Anna
2023-06-21 16:49 ` Florian Schmaus
2023-06-21 17:28 ` Mike Gilbert
2023-06-21 18:42 ` Sam James
2023-06-21 19:03 ` TOMAS FABRIZIO ORSI
2023-06-21 19:16 ` Sam James
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=CAHTSwYjrUew2eM3qm5q9LCm2zVrmw2qkfUjx9uM+zBViFv6TBA@mail.gmail.com \
--to=torsi@fi.uba.ar \
--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