From fdaddd608a0563770ee6be3c05d78c3e1b41b34a Mon Sep 17 00:00:00 2001
From: Petter Reinholdtsen
#!/bin/sh diff --git a/blog/archive/2025/02/02.rss b/blog/archive/2025/02/02.rss index a30461ceed..6d47c2fdc4 100644 --- a/blog/archive/2025/02/02.rss +++ b/blog/archive/2025/02/02.rss @@ -32,9 +32,8 @@ across the <tt>ltnu</tt> script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the <a href="https://udd.debian.org/">UDD</a> SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command:</p> +summary. Based on the <a href="https://udd.debian.org/">UDD</a> SQL +query used by ltnu, I ended up with the following command:</p> <pre> #!/bin/sh diff --git a/blog/archive/2025/02/index.html b/blog/archive/2025/02/index.html index 7bf38e69f1..009ad7d85d 100644 --- a/blog/archive/2025/02/index.html +++ b/blog/archive/2025/02/index.html @@ -50,9 +50,8 @@ across the ltnu script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the UDD SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command: +summary. Based on the UDD SQL +query used by ltnu, I ended up with the following command:#!/bin/sh diff --git a/blog/index.html b/blog/index.html index 6f7948b0f5..f78267bc20 100644 --- a/blog/index.html +++ b/blog/index.html @@ -43,9 +43,8 @@ across the ltnu script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the UDD SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command: +summary. Based on the UDD SQL +query used by ltnu, I ended up with the following command:#!/bin/sh diff --git a/blog/index.rss b/blog/index.rss index 8117604b40..d43ea71e6d 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -32,9 +32,8 @@ across the <tt>ltnu</tt> script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the <a href="https://udd.debian.org/">UDD</a> SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command:</p> +summary. Based on the <a href="https://udd.debian.org/">UDD</a> SQL +query used by ltnu, I ended up with the following command:</p> <pre> #!/bin/sh diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss index 30eaa89643..9c39a53fd5 100644 --- a/blog/tags/debian/debian.rss +++ b/blog/tags/debian/debian.rss @@ -32,9 +32,8 @@ across the <tt>ltnu</tt> script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the <a href="https://udd.debian.org/">UDD</a> SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command:</p> +summary. Based on the <a href="https://udd.debian.org/">UDD</a> SQL +query used by ltnu, I ended up with the following command:</p> <pre> #!/bin/sh diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html index 7cc520399b..3a4cd26f4d 100644 --- a/blog/tags/debian/index.html +++ b/blog/tags/debian/index.html @@ -49,9 +49,8 @@ across the ltnu script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the UDD SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command: +summary. Based on the UDD SQL +query used by ltnu, I ended up with the following command:#!/bin/sh diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss index 870a9bd84f..9b68c6cb45 100644 --- a/blog/tags/english/english.rss +++ b/blog/tags/english/english.rss @@ -32,9 +32,8 @@ across the <tt>ltnu</tt> script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the <a href="https://udd.debian.org/">UDD</a> SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command:</p> +summary. Based on the <a href="https://udd.debian.org/">UDD</a> SQL +query used by ltnu, I ended up with the following command:</p> <pre> #!/bin/sh diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html index 4ce68cb1df..e83a185ae7 100644 --- a/blog/tags/english/index.html +++ b/blog/tags/english/index.html @@ -49,9 +49,8 @@ across the ltnu script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the UDD SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command: +summary. Based on the UDD SQL +query used by ltnu, I ended up with the following command:#!/bin/sh diff --git a/blog/tags/multimedia/index.html b/blog/tags/multimedia/index.html index 976626abe8..970765beee 100644 --- a/blog/tags/multimedia/index.html +++ b/blog/tags/multimedia/index.html @@ -49,9 +49,8 @@ across the ltnu script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the UDD SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command: +summary. Based on the UDD SQL +query used by ltnu, I ended up with the following command:#!/bin/sh diff --git a/blog/tags/multimedia/multimedia.rss b/blog/tags/multimedia/multimedia.rss index c28597748e..c53d02d117 100644 --- a/blog/tags/multimedia/multimedia.rss +++ b/blog/tags/multimedia/multimedia.rss @@ -32,9 +32,8 @@ across the <tt>ltnu</tt> script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the <a href="https://udd.debian.org/">UDD</a> SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command:</p> +summary. Based on the <a href="https://udd.debian.org/">UDD</a> SQL +query used by ltnu, I ended up with the following command:</p> <pre> #!/bin/sh diff --git a/blog/tags/standard/index.html b/blog/tags/standard/index.html index b37ed18175..a195d826ea 100644 --- a/blog/tags/standard/index.html +++ b/blog/tags/standard/index.html @@ -49,9 +49,8 @@ across the ltnu script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the UDD SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command: +summary. Based on the UDD SQL +query used by ltnu, I ended up with the following command:#!/bin/sh diff --git a/blog/tags/standard/standard.rss b/blog/tags/standard/standard.rss index 33ea20fd3c..c9af98ac3c 100644 --- a/blog/tags/standard/standard.rss +++ b/blog/tags/standard/standard.rss @@ -32,9 +32,8 @@ across the <tt>ltnu</tt> script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the <a href="https://udd.debian.org/">UDD</a> SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command:</p> +summary. Based on the <a href="https://udd.debian.org/">UDD</a> SQL +query used by ltnu, I ended up with the following command:</p> <pre> #!/bin/sh diff --git a/blog/tags/video/index.html b/blog/tags/video/index.html index f2e69507b5..7460441654 100644 --- a/blog/tags/video/index.html +++ b/blog/tags/video/index.html @@ -49,9 +49,8 @@ across the ltnu script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the UDD SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command: +summary. Based on the UDD SQL +query used by ltnu, I ended up with the following command:#!/bin/sh diff --git a/blog/tags/video/video.rss b/blog/tags/video/video.rss index 5dbc32cdd6..4a045ce499 100644 --- a/blog/tags/video/video.rss +++ b/blog/tags/video/video.rss @@ -32,9 +32,8 @@ across the <tt>ltnu</tt> script from the package. It can sort by last update, packages maintained by a single user/group, and is useful to figure out which packages a single maintainer should have a look at. But I wanted a archive wide -summary. I lifted the <a href="https://udd.debian.org/">UDD</a> SQL -query used by ltnu from the script and adjusted it slightly to end up -with the following command:</p> +summary. Based on the <a href="https://udd.debian.org/">UDD</a> SQL +query used by ltnu, I ended up with the following command:</p> <pre> #!/bin/sh -- 2.47.2