]> pere.pagekite.me Git - homepage.git/blob - blog/archive/2024/04/04.rss
Generated.
[homepage.git] / blog / archive / 2024 / 04 / 04.rss
1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
3 <channel>
4 <title>Petter Reinholdtsen - Entries from April 2024</title>
5 <description>Entries from April 2024</description>
6 <link>https://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>RAID status from LSI Megaraid controllers in Debian</title>
11 <link>https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_in_Debian.html</link>
12 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_in_Debian.html</guid>
13 <pubDate>Wed, 17 Apr 2024 17:00:00 +0200</pubDate>
14 <description>&lt;p&gt;I am happy to report that
15 &lt;a href=&quot;https://github.com/namiltd/megactl&quot;&gt;the megactl package&lt;/a&gt;,
16 useful to fetch RAID status when using the LSI Megaraid controller,
17 now is available in Debian. It passed NEW a few days ago, and is now
18 &lt;a href=&quot;https://tracker.debian.org/pkg/megactl&quot;&gt;available in
19 unstable&lt;/a&gt;, and probably showing up in testing in a weeks time. The
20 new version should provide Appstream hardware mapping and should
21 integrate nicely with isenkram.&lt;/p&gt;
22
23 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
24 activities, please send Bitcoin donations to my address
25 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
26
27 </description>
28 </item>
29
30 <item>
31 <title>Time to move orphaned Debian packages to git</title>
32 <link>https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html</link>
33 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html</guid>
34 <pubDate>Sun, 14 Apr 2024 09:30:00 +0200</pubDate>
35 <description>&lt;p&gt;There are several packages in Debian without a associated git
36 repository with the packaging history. This is unfortunate and it
37 would be nice if more of these would do so. Quote a lot of these are
38 without a maintainer, ie listed as maintained by the
39 &#39;&lt;a href=&quot;https://qa.debian.org/developer.php?email=packages%40qa.debian.org&quot;&gt;Debian
40 QA Group&lt;/a&gt;&#39; place holder. In fact, 438 packages have this property
41 according to UDD (&lt;tt&gt;SELECT source FROM sources WHERE release = &#39;sid&#39;
42 AND (vcs_url ilike &#39;%anonscm.debian.org%&#39; OR vcs_browser ilike
43 &#39;%anonscm.debian.org%&#39; or vcs_url IS NULL OR vcs_browser IS NULL) AND
44 maintainer ilike &#39;%packages@qa.debian.org%&#39;;&lt;/tt&gt;). Such packages can
45 be updated without much coordination by any Debian developer, as they
46 are considered orphaned.&lt;/p&gt;
47
48 &lt;p&gt;To try to improve the situation and reduce the number of packages
49 without associated git repository, I started a few days ago to search
50 out candiates and provide them with a git repository under the
51 &#39;debian&#39; collaborative Salsa project. I started with the packages
52 pointing to obsolete Alioth git repositories, and am now working my
53 way across the ones completely without git references. In addition to
54 updating the Vcs-* debian/control fields, I try to update
55 Standards-Version, debhelper compat level, simplify d/rules, switch to
56 Rules-Requires-Root: no and fix lintian issues reported. I only
57 implement those that are trivial to fix, to avoid spending too much
58 time on each orphaned package. So far my experience is that it take
59 aproximately 20 minutes to convert a package without any git
60 references, and a lot more for packages with existing git repositories
61 incompatible with git-buildpackages.&lt;/p&gt;
62
63 &lt;p&gt;So far I have converted 10 packages, and I will keep going until I
64 run out of steam. As should be clear from the numbers, there is
65 enough packages remaining for more people to do the same without
66 stepping on each others toes. I find it useful to start by searching
67 for a git repo already on salsa, as I find that some times a git repo
68 has already been created, but no new version is uploaded to Debian
69 yet. In those cases I start with the existing git repository. I
70 convert to the git-buildpackage+pristine-tar workflow, and ensure a
71 debian/gbp.conf file with &quot;pristine-tar=True&quot; is added early, to avoid
72 uploading a orig.tar.gz with the wrong checksum by mistake. Did that
73 three times in the begin before I remembered my mistake.&lt;/p&gt;
74
75 &lt;p&gt;So, if you are a Debian Developer and got some spare time, perhaps
76 considering migrating some orphaned packages to git?&lt;/p&gt;
77
78 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
79 activities, please send Bitcoin donations to my address
80 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
81 </description>
82 </item>
83
84 </channel>
85 </rss>