public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-db/sqlmap/
Date: Sun, 10 Apr 2022 17:01:03 +0000 (UTC)	[thread overview]
Message-ID: <1649609787.0b18d1898641c43db468dc9fea39a1c7e2edf3d6.sam@gentoo> (raw)

commit:     0b18d1898641c43db468dc9fea39a1c7e2edf3d6
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Apr 10 16:56:27 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Apr 10 16:56:27 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0b18d189

dev-db/sqlmap: add pypi upstream metadata

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-db/sqlmap/metadata.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/dev-db/sqlmap/metadata.xml b/dev-db/sqlmap/metadata.xml
index 9be066d6c8f4..d5f5a618a4d0 100644
--- a/dev-db/sqlmap/metadata.xml
+++ b/dev-db/sqlmap/metadata.xml
@@ -16,5 +16,6 @@
 	</longdescription>
 	<upstream>
 		<remote-id type="github">sqlmapproject/sqlmap</remote-id>
+		<remote-id type="pypi">sqlmap</remote-id>
 	</upstream>
 </pkgmetadata>


             reply	other threads:[~2022-04-10 17:01 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10 17:01 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-05 10:06 [gentoo-commits] repo/gentoo:master commit in: dev-db/sqlmap/ Sam James
2024-10-05 10:06 Sam James
2024-10-05 10:06 Sam James
2024-10-05  7:52 Arthur Zamarin
2024-10-05  7:39 Michał Górny
2024-09-09 18:02 Sam James
2024-09-09 18:02 Sam James
2024-08-29  3:23 Sam James
2024-08-29  3:23 Sam James
2024-08-23 11:32 Jakov Smolić
2024-08-23 11:32 Jakov Smolić
2024-08-04  7:03 Joonas Niilola
2024-08-04  7:03 Joonas Niilola
2024-08-04  7:03 Joonas Niilola
2024-07-13  7:58 Joonas Niilola
2024-07-01 16:47 Sam James
2024-07-01 16:47 Sam James
2024-06-01  3:07 Sam James
2024-06-01  3:07 Sam James
2024-04-23 14:24 Sam James
2024-04-23 13:57 Sam James
2024-03-16  9:26 Joonas Niilola
2024-02-15  6:50 Joonas Niilola
2024-02-14 23:12 Jakov Smolić
2024-01-14  4:59 Sam James
2024-01-14  4:59 Sam James
2023-10-21 11:58 Sam James
2023-10-21 11:58 Sam James
2023-09-19 19:10 Arthur Zamarin
2023-09-19 19:10 Arthur Zamarin
2023-09-14  2:51 Sam James
2023-09-14  2:51 Sam James
2023-08-11  6:11 Joonas Niilola
2023-08-11  6:11 Joonas Niilola
2023-07-13  4:51 Joonas Niilola
2023-07-13  4:51 Joonas Niilola
2023-06-11  8:22 Joonas Niilola
2023-06-06  1:51 Sam James
2023-06-06  1:51 Sam James
2023-05-15  6:47 Sam James
2023-05-15  6:47 Sam James
2023-05-06  3:52 Sam James
2023-05-06  3:52 Sam James
2023-04-19  6:07 Sam James
2023-04-19  6:07 Sam James
2023-04-09 18:31 Sam James
2023-03-19  3:22 Sam James
2023-03-19  3:22 Sam James
2023-03-16  7:33 Joonas Niilola
2023-03-16  7:33 Joonas Niilola
2023-03-07  7:49 Joonas Niilola
2023-02-16 22:57 Sam James
2023-02-16 22:52 Sam James
2023-02-08  4:11 Sam James
2023-01-04  5:32 Sam James
2023-01-04  5:32 Sam James
2022-12-27  7:29 Sam James
2022-12-27  7:29 Sam James
2022-12-15  4:44 Sam James
2022-11-22 13:26 Joonas Niilola
2022-11-22 13:26 Joonas Niilola
2022-11-11  5:34 Sam James
2022-11-11  4:25 Sam James
2022-11-07 23:18 Sam James
2022-11-07 23:18 Sam James
2022-10-10 13:18 Joonas Niilola
2022-10-05  7:00 Joonas Niilola
2022-08-31  1:24 Sam James
2022-08-26 23:27 Sam James
2022-08-26 10:08 Sam James
2022-08-23  5:34 Sam James
2022-08-23  5:34 Sam James
2022-08-23  5:34 Sam James
2022-08-04  0:13 Sam James
2022-08-04  0:13 Sam James
2022-07-27  5:56 Sam James
2022-07-27  5:55 Sam James
2022-07-26  4:26 Sam James
2022-07-15  0:45 Sam James
2022-07-02 23:40 Sam James
2022-06-15 18:24 Sam James
2022-05-16  5:26 Sam James
2022-05-16  5:26 Sam James
2022-04-05  3:33 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=1649609787.0b18d1898641c43db468dc9fea39a1c7e2edf3d6.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