Generated.

[homepage.git] / blog / archive / 2024 / 07 / 07.rss

diff --git a/blog/archive/2024/07/07.rss b/blog/archive/2024/07/07.rss
index cac543e53500c8e306cab34f9d6f1620c2353fa1..460507a499bd9743117303ab058ef1b3bfadd6be 100644 (file)
--- a/blog/archive/2024/07/07.rss
+++ b/blog/archive/2024/07/07.rss
@@ -6,6 +6,66 @@
                 <link>https://people.skolelinux.org/pere/blog/</link>
 
        
+       <item>
+               <title>More than 200 orphaned Debian packages moved to git, 216 to go</title>
+               <link>https://people.skolelinux.org/pere/blog/More_than_200_orphaned_Debian_packages_moved_to_git__216_to_go.html</link>        
+               <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/More_than_200_orphaned_Debian_packages_moved_to_git__216_to_go.html</guid>
+                <pubDate>Thu, 11 Jul 2024 12:30:00 +0200</pubDate>
+               <description>&lt;p&gt;&lt;a href=&quot;https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html&quot;&gt;In
+April&lt;/a&gt;, I started migrating orphaned Debian packages without any
+version control system listed in debian/control to git.  This morning,
+my Debian QA page finally reached 200 QA packages migrated.  In
+reality there are a few more, as the packages uploaded by someone else
+after my initial upload have disappeared from my QA uploads list.  As
+I am running out of steam and will most likely focus on other parts of
+Debian moving forward, I hope someone else will find time to continue
+the migration to bring the number of orphaned packages without any
+version control system down to zero.  Here is the updated recipe if
+someone want to help out.&lt;/p&gt;
+
+&lt;p&gt;To locate packages to work on, the following one-liner can be used:&lt;/p&gt;
+
+&lt;blockquote&gt;&lt;pre&gt;
+PGPASSWORD=&quot;udd-mirror&quot; psql --port=5432 --host=udd-mirror.debian.net \
+  --username=udd-mirror udd -c &quot;select source from sources \
+   where release = &#39;sid&#39; and (vcs_url ilike &#39;%anonscm.debian.org%&#39; \
+   OR vcs_browser ilike &#39;%anonscm.debian.org%&#39; or vcs_url IS NULL \
+   OR vcs_browser IS NULL) AND maintainer ilike &#39;%packages@qa.debian.org%&#39; \
+   order by random() limit 10;&quot;
+&lt;/pre&gt;&lt;/blockquote&gt;
+
+&lt;p&gt;Pick a random package from the list and run the latest edition of
+the script
+&lt;tt&gt;&lt;a href=&quot;https://people.skolelinux.org/pere/blog/images/2024-07-11-debian-snap-to-salsa.sh&quot;&gt;debian-snap-to-salsa&lt;/a&gt;&lt;/tt&gt;
+with the package name as the argument to prepare a git repository with
+the existing packaging.  This will download old Debian packages from
+&lt;tt&gt;snapshot.debian.org&lt;/tt&gt;.  Note that very recent uploads will not
+be included, so check out the package on &lt;tt&gt;tracker.debian.org&lt;/tt&gt;.
+Next, run &lt;tt&gt;gbp buildpackage --git-ignore-new&lt;/tt&gt; to verify that
+the package build as it should, and then visit
+&lt;a href=&quot;https://salsa.debian.org/debian/&quot;&gt;https://salsa.debian.org/debian/&lt;/a&gt;
+and make sure there is not already a git repository for the package
+there.  I also did &lt;tt&gt;git log -p debian/control&lt;/tt&gt; and look for vcs
+entries to check if the package used to have a git repository on
+Alioth, and see if it can be a useful starting point moving forward.
+If all this check out, I created a new gitlab project below the Debian
+group on salsa, push the package source there and upload a new version.
+I tend to also ensure build hardening is enabled, if it prove to be
+easy, and check if I can easily fix any lintian issues or bug reports.
+If the process took more than 20 minutes, I dropped it and moved on to
+another package.&lt;/p&gt;
+
+&lt;p&gt;If I found patches in debian/patches/ that were not yet passed
+upstream, I would send an email to make sure upstream know about them.
+This has proved to be a valuable step, and caused several new releases
+for software that initially appeared abandoned. :)&lt;/p&gt;
+
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+</description>
+       </item>
+       
        <item>
                <title>Some notes from the 2024 LinuxCNC Norwegian developer gathering</title>
                <link>https://people.skolelinux.org/pere/blog/Some_notes_from_the_2024_LinuxCNC_Norwegian_developer_gathering.html</link>