gentoo auto-resync : 20:10:2022 - 07:59:49

5 files changed, 21 insertions, 21 deletions

diff --git a/net-dns/Manifest.gz b/net-dns/Manifest.gz
index b3de17fc0014..311878f08242 100644
--- a/net-dns/Manifest.gz
+++ b/net-dns/Manifest.gz
diff --git a/net-dns/dnrd/Manifest b/net-dns/dnrd/Manifest
index b08fde86bc33..2adad7a8f898 100644
--- a/net-dns/dnrd/Manifest
+++ b/net-dns/dnrd/Manifest
@@ -3,4 +3,4 @@ AUX dnrd-2.20.3-docdir.patch 719 BLAKE2B 45cf21aaf65ef35c7de3ffd12398d6962fed28a
 AUX dnrd.conf 250 BLAKE2B a9334bdd7ed06152068e22d72c7fbb5c4de97fa888e0b0cde6a6517c8d29e47e9727c0bfdb732156b77e7f825413d31c808565c5a65103d90828ba04bbc3ee92 SHA512 461bbebba321b5216a15ea9550342ca9f7374af6446c2f515a3f5ce35bf45480c8f684b60ce8c206ec017e7ca060d4588c0d2da026d2e99162f3f9a6e58f03d2
 DIST dnrd-2.20.3.tar.gz 161887 BLAKE2B e04941fe59a8835386d398aa4a76bb0b2562705f98994b1d9d6c57557499de49a084dd2c3bab4c25499c81267fb336bac7a2b27dd8efd77164bf8d5409b2c94c SHA512 a526ec9c2f82ac36fa7beaf864ab39c56e5956530b10115ad2ca2f79ecb820fe865d9da9edd1dea5f4cb97508afbec88f0606b03f87baba25561c097e7c0ea9b
 EBUILD dnrd-2.20.3-r3.ebuild 563 BLAKE2B b02764ec765255bec16954f0f61b18ff7bd933f2bdd84211241c334163de3b9e0c51c5c406ff27114fda62ce61a13de66fff3bcff8b1edf9ee41ca518a80de7c SHA512 de155101a45e517a2c1785131b95acc0ab32eb4cd3facdc0f2cccd3fc6c620dbaf104cfaed49c19071bfb12b4c1554b9db5e62d3b6bdaa8f96a6fc64c8bf5772
-MISC metadata.xml 456 BLAKE2B ff90780141bef08c4007837c39fb6e5a2e8828cd201d8aca78cc981b0e52bebda153db8a172719c016ab6ebd169aee83eb7740e7846b5585e2415a2053d124e9 SHA512 fa83cc1f6af48a41f31347f4637265fa6773f8096d9c2c4d3f8d9a337c4fb3f1c5d6f49b7350e302acfae30f3e77f7afec7623890731dc125b1329b513b2a8d6
+MISC metadata.xml 458 BLAKE2B e3f4ae88ec4d653706ac8dc2d57be4011e3ab5aa5d76959660ae32bdaae67163eea2231fce50663d9a67605d641b19fc00f0f6b325a2d294e65128f6791c756d SHA512 b2121422fdf9232fc068c095e211fd1a5d7e95d24210e0fb4191169099cfc6fa943e71a600bc2a43d9e985f37f68238b27cfd7d37fc6f683f6bc91501acd118d
diff --git a/net-dns/dnrd/metadata.xml b/net-dns/dnrd/metadata.xml
index 8a6342466ffe..4f0638f48b0a 100644
--- a/net-dns/dnrd/metadata.xml
+++ b/net-dns/dnrd/metadata.xml
@@ -3,8 +3,8 @@
 <pkgmetadata>
 	<!-- maintainer-needed -->
 	<longdescription>
-Domain Name Relay Daemon is a caching, forwarding DNS proxy server. Most useful on vpn or dialup firewalls but it is also a nice DNS cache for minor networks and workstations.
-</longdescription>
+	Domain Name Relay Daemon is a caching, forwarding DNS proxy server. Most useful on vpn or dialup firewalls but it is also a nice DNS cache for minor networks and workstations.
+	</longdescription>
 	<upstream>
 		<remote-id type="sourceforge">dnrd</remote-id>
 	</upstream>
diff --git a/net-dns/fpdns/Manifest b/net-dns/fpdns/Manifest
index 2d56765fec67..cb863af33cd2 100644
--- a/net-dns/fpdns/Manifest
+++ b/net-dns/fpdns/Manifest
@@ -1,4 +1,4 @@
 AUX fpdns-0.10.0_pre20130404.ro-header.patch 1115 BLAKE2B d8042816acce161ba4e19533700151489f3a169fb96a11d4eb44b107818fe0eab87cb916b4e8d5d2a45e22c82693517d069c6e12095b415b352d40384a9040db SHA512 e345037a210103f5202c0dd052952bd2d3889ad53393fc4881ec48810f3e6d39b1b7d2220d259ffda0b85e339bcc4ef9f1ae28023cf84b81a00685c66e116923
 DIST fpdns-0.10.0_pre20130404.tar.gz 931723 BLAKE2B cab459afee74ef5d8163a25b98c123b799270e6d3293f155a340ebdbfbc86266fbffa999d31928c9b1a732898b0adf4a49e97469f9ae992a0e38f9478431e84c SHA512 1a4d9c1cb666efa3f48dcca2b5cd04793e92727359652095572b17479f5343479c57d2937f1fff8070c071a2698eda5c4dff981caf86436f184f0b076b0fa0b3
 EBUILD fpdns-0.10.0_pre20130404-r1.ebuild 585 BLAKE2B e65b3bcb59605233edf82566bd02b28e858f2398bcc1d6984eb6713b567d9bf450ac976497c07c6d6129c6806e900477c862471eb5799c2a675c85822079d4da SHA512 99ded2a507030ff035b56945576f965473ab9e4ed6fde789dd79808978a96626ee087018c0b600d969d509820ff63eaf8e64bb9c3d96b6d3ff648d74313c1854
-MISC metadata.xml 1421 BLAKE2B aa284dbfc1b37ec2da8254b22242b872198de6a84940075cafc023d25e31a552c150f47b3eeac9d1d57ed6307ba71774733c3dcac5a8d6342a221c77de660086 SHA512 2f174a68b6bdbd47c32645b0faa408b51a2bfaa4869c3e32498aeb9311d7b9d4de7dd598b63858b1b4fef283172728f23beb9ae1812b5937420e96fbe7718388
+MISC metadata.xml 1438 BLAKE2B 048c17c0264b5e2b5709f4da82bc22d3f7a197ba202c9c95f27bfcb0d52e91b87fb1bbae7791d94eefc6f688856e0d6bf311ae712922606f5cb76300b7c05283 SHA512 1f8ca836146892d3ca4cede7547de9c682d1d77f95f77380db4f78f6d7e7472f5d80544b98dc3235f34b2c69b0071ab5e6af03986aae331616fb4bcf10c0e033
diff --git a/net-dns/fpdns/metadata.xml b/net-dns/fpdns/metadata.xml
index 7b8047263afb..d6cd618589b3 100644
--- a/net-dns/fpdns/metadata.xml
+++ b/net-dns/fpdns/metadata.xml
@@ -3,26 +3,26 @@
 <pkgmetadata>
 	<!-- maintainer-needed -->
 	<longdescription>
-A nameserver basically responds to a query. Interoperability is an obvious
-requirement here. The standard protocol behaviour of different DNS
-implementations is expected to be the same.
+	A nameserver basically responds to a query. Interoperability is an obvious
+	requirement here. The standard protocol behaviour of different DNS
+	implementations is expected to be the same.
 
-Requirements for protocol behaviour of DNS implementations is widely documented
-in the case of 'common' dns messages. The DNS protocol is over 20 years old and
-since its inception, there have been over 40 independent DNS implementations,
-while some implementations have over 20 versions.
+	Requirements for protocol behaviour of DNS implementations is widely documented
+	in the case of 'common' dns messages. The DNS protocol is over 20 years old and
+	since its inception, there have been over 40 independent DNS implementations,
+	while some implementations have over 20 versions.
 
-The methodology used to identify individual nameserver implementations is based
-on "borderline" protocol behaviour. The DNS protocol offers a multitude of
-message bits, response types, opcodes, classes, query types and label types in a
-fashion that makes some mutually exclusive while some are not used in a query
-messages at all. Not every implementation offers the full set of features the
-DNS protocol set currently has. Some implementations offer features outside the
-protocol set, and there are implementations that do not conform to standards.
+	The methodology used to identify individual nameserver implementations is based
+	on "borderline" protocol behaviour. The DNS protocol offers a multitude of
+	message bits, response types, opcodes, classes, query types and label types in a
+	fashion that makes some mutually exclusive while some are not used in a query
+	messages at all. Not every implementation offers the full set of features the
+	DNS protocol set currently has. Some implementations offer features outside the
+	protocol set, and there are implementations that do not conform to standards.
 
-Also, new features added to - or bugs removed allow for differentiations between
-versions of an implementation.
-</longdescription>
+	Also, new features added to - or bugs removed allow for differentiations between
+	versions of an implementation.
+	</longdescription>
 	<upstream>
 		<remote-id type="github">kirei/fpdns</remote-id>
 	</upstream>