blog/archive/2024/07/07.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 July 2024</title>
   5                 <description>Entries from July 2024</description>
   6                 <link>https://www.hungry.com/~pere/blog/</link>
   7
   8
   9         <item>
  10                 <title>More than 200 orphaned Debian packages moved to git, 216 to go</title>
  11                 <link>https://www.hungry.com/~pere/blog/More_than_200_orphaned_Debian_packages_moved_to_git__216_to_go.html</link>
  12                 <guid isPermaLink="true">https://www.hungry.com/~pere/blog/More_than_200_orphaned_Debian_packages_moved_to_git__216_to_go.html</guid>
  13                 <pubDate>Thu, 11 Jul 2024 12:30:00 +0200</pubDate>
  14                 <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
  15 April&lt;/a&gt;, I started migrating orphaned Debian packages without any
  16 version control system listed in debian/control to git.  This morning,
  17 my Debian QA page finally reached 200 QA packages migrated.  In
  18 reality there are a few more, as the packages uploaded by someone else
  19 after my initial upload have disappeared from my QA uploads list.  As
  20 I am running out of steam and will most likely focus on other parts of
  21 Debian moving forward, I hope someone else will find time to continue
  22 the migration to bring the number of orphaned packages without any
  23 version control system down to zero.  Here is the updated recipe if
  24 someone want to help out.&lt;/p&gt;
  25
  26 &lt;p&gt;To locate packages to work on, the following one-liner can be used:&lt;/p&gt;
  27
  28 &lt;blockquote&gt;&lt;pre&gt;
  29 PGPASSWORD=&quot;udd-mirror&quot; psql --port=5432 --host=udd-mirror.debian.net \
  30   --username=udd-mirror udd -c &quot;select source from sources \
  31    where release = &#39;sid&#39; and (vcs_url ilike &#39;%anonscm.debian.org%&#39; \
  32    OR vcs_browser ilike &#39;%anonscm.debian.org%&#39; or vcs_url IS NULL \
  33    OR vcs_browser IS NULL) AND maintainer ilike &#39;%packages@qa.debian.org%&#39; \
  34    order by random() limit 10;&quot;
  35 &lt;/pre&gt;&lt;/blockquote&gt;
  36
  37 &lt;p&gt;Pick a random package from the list and run the latest edition of
  38 the script
  39 &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;
  40 with the package name as the argument to prepare a git repository with
  41 the existing packaging.  This will download old Debian packages from
  42 &lt;tt&gt;snapshot.debian.org&lt;/tt&gt;.  Note that very recent uploads will not
  43 be included, so check out the package on &lt;tt&gt;tracker.debian.org&lt;/tt&gt;.
  44 Next, run &lt;tt&gt;gbp buildpackage --git-ignore-new&lt;/tt&gt; to verify that
  45 the package build as it should, and then visit
  46 &lt;a href=&quot;https://salsa.debian.org/debian/&quot;&gt;https://salsa.debian.org/debian/&lt;/a&gt;
  47 and make sure there is not already a git repository for the package
  48 there.  I also did &lt;tt&gt;git log -p debian/control&lt;/tt&gt; and look for vcs
  49 entries to check if the package used to have a git repository on
  50 Alioth, and see if it can be a useful starting point moving forward.
  51 If all this check out, I created a new gitlab project below the Debian
  52 group on salsa, push the package source there and upload a new version.
  53 I tend to also ensure build hardening is enabled, if it prove to be
  54 easy, and check if I can easily fix any lintian issues or bug reports.
  55 If the process took more than 20 minutes, I dropped it and moved on to
  56 another package.&lt;/p&gt;
  57
  58 &lt;p&gt;If I found patches in debian/patches/ that were not yet passed
  59 upstream, I would send an email to make sure upstream know about them.
  60 This has proved to be a valuable step, and caused several new releases
  61 for software that initially appeared abandoned. :)&lt;/p&gt;
  62
  63 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
  64 activities, please send Bitcoin donations to my address
  65 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
  66 </description>
  67         </item>
  68
  69         <item>
  70                 <title>Some notes from the 2024 LinuxCNC Norwegian developer gathering</title>
  71                 <link>https://www.hungry.com/~pere/blog/Some_notes_from_the_2024_LinuxCNC_Norwegian_developer_gathering.html</link>
  72                 <guid isPermaLink="true">https://www.hungry.com/~pere/blog/Some_notes_from_the_2024_LinuxCNC_Norwegian_developer_gathering.html</guid>
  73                 <pubDate>Wed, 10 Jul 2024 14:45:00 +0200</pubDate>
  74                 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;https://linuxcnc.org/&quot;&gt;The LinuxCNC&lt;/a&gt;
  75 developer gathering 2024 is over.  It was a great and productive
  76 weekend, and I am sad that it is over.&lt;/p&gt;
  77
  78 &lt;p&gt;Regular readers probably still remember what LinuxCNC is, but her
  79 is a quick summary for those that forgot?  LinuxCNC is a free software
  80 system for numerical control of machines such as milling machines,
  81 lathes, plasma cutters, routers, cutting machines, robots and
  82 hexapods.  It eats G-code and produce motor movement and other changes
  83 to the physical world, while reading sensor input.&lt;/p&gt;
  84
  85 &lt;p&gt;I am not quite sure about the total head count, as not all people
  86 were present at the gathering the entire weekend, but I believe it was
  87 close to 10 people showing their faces at the gathering.  The &quot;hard
  88 core&quot; of the group, who stayed the entire weekend, were two from
  89 Norway, two from Germany and one from England.  I am happy with the
  90 outcome from the gathering.  We managed to wrap up a new stable
  91 LinuxCNC release 2.9.3 and even tested it on real hardware within
  92 minutes of the release.  The release notes for 2.9.3 are still being
  93 written, but should show up on on the project site in the next few
  94 days.  We managed to go through around twenty pull requests and merge
  95 then into either the stable release (2.9) or the development branch
  96 (master).  There are still around thirty pull requests left to
  97 process, so we are not out of work yet.  We even managed to
  98 fix/improve a slightly worn lathe, and experiment with running a
  99 mechanical clock using G-code.&lt;/p&gt;
 100
 101 &lt;p&gt;The evening barbeque worked well both on Saturday and Sunday.  It
 102 is quite fun to light up a charcoal grill using compressed air.  Sadly
 103 the weather was not the best, so we stayed indoors most of the
 104 time.&lt;/p&gt;
 105
 106 &lt;p&gt;This gathering was made possible partly with sponsoring from both
 107 &lt;a href=&quot;https://www.redpill-linpro.com/&quot;&gt;Redpill Linpro&lt;/a&gt;,
 108 &lt;a href=&quot;https://debian.org/&quot;&gt;Debian&lt;/a&gt; and
 109 &lt;a href=&quot;https://nuugfoundation.no/&quot;&gt;NUUG Foundation&lt;/a&gt;, and we are
 110 most grateful for the support.  I would also like to thank the local
 111 school for lending us some furniture, and of course the rest of the
 112 members of the organizers team, Asle and Bosse, for their countless
 113 contributions.  The gathering was such success that we want to do it
 114 again next year.&lt;/p&gt;
 115
 116 &lt;p&gt;We plan to organize the next Norwegian LinuxCNC developer gathering
 117 at the end of June next year, the weekend Friday 27th to Sunday 29th
 118 of June 2025.  I recommend you reserve the dates on your calendar
 119 today.  Other related communities are also welcome to join in, for
 120 example those working on systems like FreeCAD and opencamlib, as I am
 121 sure we have much in common and sharing experiences would be very
 122 useful to all involved.  We are of course looking for sponsors for
 123 this gathering already.  The total budget for this gathering was
 124 around NOK 25.000 (around EUR 2.300), so our needs are quite modest.
 125 Perhaps a machine or tools company would like to help out the free
 126 software manufacturing community by sponsoring food, lodging and
 127 transport for such gathering?&lt;/p&gt;
 128 </description>
 129         </item>
 130
 131         </channel>
 132 </rss>