From 18cb561696fc87a873b98ece5733eaccad3fc1eb Mon Sep 17 00:00:00 2001
From: "Liguros - Gitlab CI/CD [develop]" <gitlab@liguros.net>
Date: Tue, 20 Jul 2021 21:26:04 +0000
Subject: Adding metadata

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

(limited to 'dev-python/sphobjinv')

diff --git a/dev-python/sphobjinv/metadata.xml b/dev-python/sphobjinv/metadata.xml
index dc83e0f5d0f7..c239e693844b 100644
--- a/dev-python/sphobjinv/metadata.xml
+++ b/dev-python/sphobjinv/metadata.xml
@@ -1,12 +1,11 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
-
+<!DOCTYPE pkgmetadata SYSTEM "https://liguros.gitlab.io/dtd/metadata.dtd">
 <pkgmetadata>
-  <maintainer type="person">
-    <email>andrewammerlaan@gentoo.org</email>
-    <name>Andrew Ammerlaan</name>
-  </maintainer>
-  <longdescription lang="en">
+ <maintainer type="person">
+  <email>andrewammerlaan@gentoo.org</email>
+  <name>Andrew Ammerlaan</name>
+ </maintainer>
+ <longdescription lang="en">
 Using Sphinx?
 
 Having trouble writing cross-references?
@@ -15,9 +14,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>
-  <upstream>
-    <remote-id type="github">bskinn/sphobjinv</remote-id>
-    <remote-id type="pypi">sphobjinv</remote-id>
-  </upstream>
-  <stabilize-allarches/>
-</pkgmetadata>
+ <upstream>
+  <remote-id type="pypi">sphobjinv</remote-id>
+ </upstream>
+ <origin>gentoo-staging</origin>
+ <stabilize-allarches/>
+</pkgmetadata>
\ No newline at end of file
-- 
cgit v1.3