From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/giflib/
Date: Sat, 7 Oct 2023 03:47:31 +0000 (UTC) [thread overview]
Message-ID: <1696650446.30e69fdc79d6ecbb5c840f1c87087681b7a7314f.mattst88@gentoo> (raw)
commit: 30e69fdc79d6ecbb5c840f1c87087681b7a7314f
Author: Allen Webb <allenwebb <AT> google <DOT> com>
AuthorDate: Thu Oct 5 19:27:43 2023 +0000
Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Sat Oct 7 03:47:26 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=30e69fdc
media-libs/giflib: Add CPE string to metadata.xml
Add a CPE string for easier CVE tracking.
Closes: https://bugs.gentoo.org/915135
Closes: https://github.com/gentoo/gentoo/pull/33208
Signed-off-by: Allen Webb <allenwebb <AT> google.com>
Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>
media-libs/giflib/metadata.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/media-libs/giflib/metadata.xml b/media-libs/giflib/metadata.xml
index 5eb82c87abf9..a2b1e1d7463d 100644
--- a/media-libs/giflib/metadata.xml
+++ b/media-libs/giflib/metadata.xml
@@ -7,5 +7,6 @@
</maintainer>
<upstream>
<remote-id type="sourceforge">giflib</remote-id>
+ <remote-id type="cpe">cpe:/a:giflib_project:giflib</remote-id>
</upstream>
</pkgmetadata>
next reply other threads:[~2023-10-07 3:47 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 3:47 Matt Turner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-13 13:51 [gentoo-commits] repo/gentoo:master commit in: media-libs/giflib/ Andreas Sturmlechner
2024-10-12 23:53 Sam James
2024-09-24 15:22 Sam James
2024-09-23 7:34 Arthur Zamarin
2024-09-23 7:34 Arthur Zamarin
2024-09-23 7:13 Arthur Zamarin
2024-09-23 7:13 Arthur Zamarin
2024-09-23 6:02 Arthur Zamarin
2024-09-23 6:02 Arthur Zamarin
2024-09-23 5:46 Sam James
2022-05-14 3:42 WANG Xuerui
2021-01-25 22:05 Sam James
2021-01-14 12:29 Fabian Groffen
2020-10-19 19:15 Mike Gilbert
2020-06-12 7:33 Sergei Trofimovich
2020-05-16 21:28 David Seifert
2020-03-25 21:30 Thomas Deutschmann
2020-03-25 20:55 Thomas Deutschmann
2020-03-25 20:55 Thomas Deutschmann
2020-03-16 18:25 Sergei Trofimovich
2020-03-12 23:05 Mart Raudsepp
2020-03-10 8:35 Agostino Sarubbo
2020-03-09 12:42 Agostino Sarubbo
2020-03-09 12:41 Agostino Sarubbo
2020-03-09 12:39 Agostino Sarubbo
2020-03-09 11:17 Agostino Sarubbo
2020-03-09 10:49 Agostino Sarubbo
2020-03-09 10:23 Agostino Sarubbo
2020-03-08 23:22 Thomas Deutschmann
2020-03-08 21:22 Andreas Sturmlechner
2019-11-13 1:03 Aaron Bauman
2019-11-13 1:03 Aaron Bauman
2019-06-24 16:35 Lars Wendler
2019-03-11 10:28 Lars Wendler
2019-02-15 7:49 Guilherme Amadio
2019-02-14 12:26 Lars Wendler
2018-03-29 22:32 Mart Raudsepp
2018-01-21 1:49 Aaron Bauman
2018-01-21 1:03 Aaron Bauman
2017-04-14 18:49 Michał Górny
2017-04-14 16:28 Michał Górny
2017-01-09 14:19 Jeroen Roovers
2016-11-29 17:35 Markus Meier
2016-11-19 13:55 Agostino Sarubbo
2016-11-19 13:53 Agostino Sarubbo
2016-11-15 14:53 Tobias Klausmann
2016-06-19 10:16 Andrew Savchenko
2016-04-03 15:51 Lars Wendler
2016-04-03 15:51 Lars Wendler
2016-03-17 19:58 Lars Wendler
2016-03-17 19:58 Lars Wendler
2016-01-11 13:25 Lars Wendler
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=1696650446.30e69fdc79d6ecbb5c840f1c87087681b7a7314f.mattst88@gentoo \
--to=mattst88@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