From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: metadata/install-qa-check.d/
Date: Mon, 28 Jun 2021 00:12:35 +0000 (UTC) [thread overview]
Message-ID: <1624839125.43a4f3458b8520646239e3189dbf6695240af00f.gyakovlev@gentoo> (raw)
commit: 43a4f3458b8520646239e3189dbf6695240af00f
Author: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 28 00:12:05 2021 +0000
Commit: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Mon Jun 28 00:12:05 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=43a4f345
metadata/install-qa-check.d: add libcrypt tracker bug
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>
metadata/install-qa-check.d/60libcrypt-deps | 1 +
1 file changed, 1 insertion(+)
diff --git a/metadata/install-qa-check.d/60libcrypt-deps b/metadata/install-qa-check.d/60libcrypt-deps
index 53e2e0b9d6f..3ea1b5372ce 100644
--- a/metadata/install-qa-check.d/60libcrypt-deps
+++ b/metadata/install-qa-check.d/60libcrypt-deps
@@ -35,6 +35,7 @@ libcrypt_check() {
eqawarn
eqawarn "Please add virtual/libcrypt:= dependency"
eqawarn "Gentoo bug: https://bugs.gentoo.org/699422"
+ eqawarn "Tracker bug: https://bugs.gentoo.org/798963"
eqawarn "See: https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation"
fi
next reply other threads:[~2021-06-28 0:12 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 0:12 Georgy Yakovlev [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-21 15:12 [gentoo-commits] repo/gentoo:master commit in: metadata/install-qa-check.d/ Michał Górny
2024-09-05 8:43 Michał Górny
2024-03-29 18:47 Sam James
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2024-01-08 14:48 Michał Górny
2023-08-17 22:08 Ulrich Müller
2023-05-17 3:40 Michał Górny
2022-09-19 3:52 Sam James
2022-08-21 2:31 Sam James
2022-08-04 23:49 Sam James
2022-08-03 18:56 Sam James
2022-08-03 4:27 Sam James
2022-08-03 1:53 Sam James
2022-08-02 4:08 Michał Górny
2022-07-16 11:26 Michał Górny
2022-06-08 0:25 Mike Gilbert
2022-05-06 12:48 Ionen Wolkens
2022-05-05 23:38 Sam James
2022-05-02 6:01 Agostino Sarubbo
2022-04-30 19:13 Sam James
2022-04-28 3:06 Sam James
2022-04-27 0:13 Sam James
2022-04-26 23:45 Sam James
2022-04-26 15:32 Sam James
2022-04-19 18:31 Sam James
2022-04-19 18:31 Sam James
2022-04-17 14:21 Sam James
2022-04-17 14:18 Sam James
2022-03-04 1:26 Sam James
2022-03-04 1:26 Sam James
2022-02-01 18:19 Mike Gilbert
2022-02-01 1:37 Mike Gilbert
2022-01-16 9:40 Michał Górny
2021-08-19 1:35 Sam James
2021-08-16 2:12 Sam James
2021-08-16 2:12 Sam James
2021-08-16 2:12 Sam James
2021-08-16 2:12 Sam James
2021-08-02 8:17 Michał Górny
2021-07-03 8:16 Michał Górny
2021-07-01 8:57 Georgy Yakovlev
2021-06-28 18:47 Georgy Yakovlev
2021-06-28 8:56 Georgy Yakovlev
2021-06-27 2:08 Sam James
2021-06-26 23:25 Georgy Yakovlev
2021-06-26 23:09 Georgy Yakovlev
2021-05-29 15:15 Michał Górny
2021-05-25 5:13 Michał Górny
2021-04-29 11:42 Michał Górny
2021-04-29 11:42 Michał Górny
2021-04-29 11:42 Michał Górny
2021-04-29 11:42 Michał Górny
2021-04-09 23:17 Sam James
2020-10-17 19:01 Michał Górny
2020-10-16 7:42 Michał Górny
2020-09-22 11:12 Michał Górny
2020-09-22 7:33 Michał Górny
2020-09-22 7:00 Michał Górny
2020-09-22 7:00 Michał Górny
2020-09-21 17:48 Michał Górny
2020-09-21 15:30 Michał Górny
2020-02-13 18:59 Georgy Yakovlev
2020-01-20 20:45 Michael Orlitzky
2019-12-30 16:10 Michał Górny
2019-11-12 7:53 Sergei Trofimovich
2019-11-11 23:05 Zac Medico
2019-11-11 22:25 Sergei Trofimovich
2019-11-01 13:16 Michał Górny
2018-10-06 8:35 Michał Górny
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=1624839125.43a4f3458b8520646239e3189dbf6695240af00f.gyakovlev@gentoo \
--to=gyakovlev@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