From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-bashcomp:master commit in: helpers/
Date: Sat, 14 Jan 2023 16:39:38 +0000 (UTC) [thread overview]
Message-ID: <1673714374.184a51233d05f7b45a3c3fc73782be600add6000.sam@gentoo> (raw)
commit: 184a51233d05f7b45a3c3fc73782be600add6000
Author: Jernej Jakob <jernej.jakob+gentoo <AT> gmail <DOT> com>
AuthorDate: Tue Jun 7 13:44:35 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jan 14 16:39:34 2023 +0000
URL: https://gitweb.gentoo.org/proj/gentoo-bashcomp.git/commit/?id=184a5123
Ignore backup prefixed or suffixed files in repos.conf subdirectory.
Portage ignores any files starting with '.' or ending with '~' in
the repos.conf directory.
See 'portage.util' function '_recursive_basename_filter'.
Closes: https://bugs.gentoo.org/730624
Signed-off-by: Sam James <sam <AT> gentoo.org>
helpers/gentoo-common.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/helpers/gentoo-common.sh b/helpers/gentoo-common.sh
index 6e8d51c..35b5946 100644
--- a/helpers/gentoo-common.sh
+++ b/helpers/gentoo-common.sh
@@ -65,7 +65,7 @@ _parsereposconf() {
for f in @GENTOO_PORTAGE_EPREFIX@/usr/share/portage/config/repos.conf \
@GENTOO_PORTAGE_EPREFIX@/etc/portage/repos.conf \
- @GENTOO_PORTAGE_EPREFIX@/etc/portage/repos.conf/*; do
+ @GENTOO_PORTAGE_EPREFIX@/etc/portage/repos.conf/[!.]*[!~]; do
[[ -f ${f} ]] || continue
insection=0
next reply other threads:[~2023-01-14 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 16:39 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 7:34 [gentoo-commits] proj/gentoo-bashcomp:master commit in: helpers/ Sam James
2023-01-14 16:39 Sam James
2021-11-16 16:08 Patrice Clement
2019-02-10 23:04 Patrice Clement
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=1673714374.184a51233d05f7b45a3c3fc73782be600add6000.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@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