From 7d009d2bc561a2df178eac5df75421e4bb4c6b62 Mon Sep 17 00:00:00 2001
From: root <root@alpha.trunkmasters.com>
Date: Sun, 31 May 2026 21:30:14 -0500
Subject: Adding metadata

---
 dev-python/sphobjinv/metadata.xml | 23 +++++++++++++----------
 1 file changed, 13 insertions(+), 10 deletions(-)

(limited to 'dev-python/sphobjinv')

diff --git a/dev-python/sphobjinv/metadata.xml b/dev-python/sphobjinv/metadata.xml
index ec6ff1fda51d..dd8bed6989d1 100644
--- a/dev-python/sphobjinv/metadata.xml
+++ b/dev-python/sphobjinv/metadata.xml
@@ -1,11 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE pkgmetadata SYSTEM "https://liguros.gitlab.io/dtd/metadata.dtd">
+<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
+
 <pkgmetadata>
- <maintainer type="project">
-  <email>python@gentoo.org</email>
-  <name>Python</name>
- </maintainer>
- <longdescription lang="en">
+  <maintainer type="project">
+    <email>python@gentoo.org</email>
+    <name>Python</name>
+  </maintainer>
+  <longdescription lang="en">
 Using Sphinx?
 
 Having trouble writing cross-references?
@@ -14,7 +15,9 @@ sphobjinv (short for ‘sphinx objects.inv’) can help!
 
 The syntax required for a functional Sphinx cross-reference is highly non-obvious in many cases. Sometimes Sphinx can guess correctly what you mean, but it’s pretty hit-or-miss. The best approach is to provide Sphinx with a completely specified cross-reference, and that’s where sphobjinv comes in.
   </longdescription>
- 
- <origin>liguros-repo</origin>
- <stabilize-allarches/>
-</pkgmetadata>
\ No newline at end of file
+  <upstream>
+    <remote-id type="github">bskinn/sphobjinv</remote-id>
+    <remote-id type="pypi">sphobjinv</remote-id>
+  </upstream>
+  <stabilize-allarches/>
+</pkgmetadata>
-- 
cgit v1.3.1