blog/index.rss

   1 <?xml version="1.0" encoding="utf-8"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
   3         <channel>
   4                 <title>Petter Reinholdtsen</title>
   5                 <description></description>
   6                 <link>https://people.skolelinux.org/pere/blog/</link>
   7                 <atom:link href="https://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
   8
   9         <item>
  10                 <title>Some notes from the 2024 LinuxCNC Norwegian developer gathering</title>
  11                 <link>https://people.skolelinux.org/pere/blog/Some_notes_from_the_2024_LinuxCNC_Norwegian_developer_gathering.html</link>
  12                 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_notes_from_the_2024_LinuxCNC_Norwegian_developer_gathering.html</guid>
  13                 <pubDate>Wed, 10 Jul 2024 14:45:00 +0200</pubDate>
  14                 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;https://linuxcnc.org/&quot;&gt;The LinuxCNC&lt;/a&gt;
  15 developer gathering 2024 is over.  It was a great and productive
  16 weekend, and I am sad that it is over.&lt;/p&gt;
  17
  18 &lt;p&gt;Regular readers probably still remember what LinuxCNC is, but her
  19 is a quick summary for those that forgot?  LinuxCNC is a free software
  20 system for numerical control of machines such as milling machines,
  21 lathes, plasma cutters, routers, cutting machines, robots and
  22 hexapods.  It eats G-code and produce motor movement and other changes
  23 to the physical world, while reading sensor input.&lt;/p&gt;
  24
  25 &lt;p&gt;I am not quite sure about the total head count, as not all people
  26 were present at the gathering the entire weekend, but I believe it was
  27 close to 10 people showing their faces at the gathering.  The &quot;hard
  28 core&quot; of the group, who stayed the entire weekend, were two from
  29 Norway, two from Germany and one from England.  I am happy with the
  30 outcome from the gathering.  We managed to wrap up a new stable
  31 LinuxCNC release 2.9.3 and even tested it on real hardware within
  32 minutes of the release.  The release notes for 2.9.3 are still being
  33 written, but should show up on on the project site in the next few
  34 days.  We managed to go through around twenty pull requests and merge
  35 then into either the stable release (2.9) or the development branch
  36 (master).  There are still around thirty pull requests left to
  37 process, so we are not out of work yet.  We even managed to
  38 fix/improve a slightly worn lathe, and experiment with running a
  39 mechanical clock using G-code.&lt;/p&gt;
  40
  41 &lt;p&gt;The evening barbeque worked well both on Saturday and Sunday.  It
  42 is quite fun to light up a charcoal grill using compressed air.  Sadly
  43 the weather was not the best, so we stayed indoors most of the
  44 time.&lt;/p&gt;
  45
  46 &lt;p&gt;This gathering was made possible partly with sponsoring from both
  47 &lt;a href=&quot;https://www.redpill-linpro.com/&quot;&gt;Redpill Linpro&lt;/a&gt;,
  48 &lt;a href=&quot;https://debian.org/&quot;&gt;Debian&lt;/a&gt; and
  49 &lt;a href=&quot;https://nuugfoundation.no/&quot;&gt;NUUG Foundation&lt;/a&gt;, and we are
  50 most grateful for the support.  I would also like to thank the local
  51 school for lending us some furniture, and of course the rest of the
  52 members of the organizers team, Asle and Bosse, for their countless
  53 contributions.  The gathering was such success that we want to do it
  54 again next year.&lt;/p&gt;
  55
  56 &lt;p&gt;We plan to organize the next Norwegian LinuxCNC developer gathering
  57 at the end of June next year, the weekend Friday 27th to Sunday 29th
  58 of June 2025.  I recommend you reserve the dates on your calendar
  59 today.  Other related communities are also welcome to join in, for
  60 example those working on systems like FreeCAD and opencamlib, as I am
  61 sure we have much in common and sharing experiences would be very
  62 useful to all involved.  We are of course looking for sponsors for
  63 this gathering already.  The total budget for this gathering was
  64 around NOK 25.000 (around EUR 2.300), so our needs are quite modest.
  65 Perhaps a machine or tools company would like to help out the free
  66 software manufacturing community by sponsoring food, lodging and
  67 transport for such gathering?&lt;/p&gt;
  68 </description>
  69         </item>
  70
  71         <item>
  72                 <title>«Møter vi liv eller død?», pamfletten som inspirerte</title>
  73                 <link>https://people.skolelinux.org/pere/blog/_M_ter_vi_liv_eller_d_d____pamfletten_som_inspirerte.html</link>
  74                 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/_M_ter_vi_liv_eller_d_d____pamfletten_som_inspirerte.html</guid>
  75                 <pubDate>Tue, 4 Jun 2024 11:30:00 +0200</pubDate>
  76                 <description>&lt;img align=&quot;center&quot; src=&quot;https://people.skolelinux.org/pere/blog/images/2024-06-04-bok-elsa-laula.svg&quot; width=&quot;20%&quot; align=&quot;center&quot; border=&quot;1&quot;&gt;&lt;/a&gt;
  77
  78 &lt;p&gt;Da jeg i høst hørte jeg et innslag på
  79 &lt;a href=&quot;https://radiorakel.no/&quot;&gt;radiOrakel&lt;/a&gt; om en inspirerende dame
  80 som levde for over hundre år siden, fikk jeg en vill ide.  Elsa Laula
  81 var en svensk samisk dame som ikke bare fikk utdannelsen finansiert av
  82 den danske dronningen, men som gjorde så god jobb med å inspirere og
  83 organisere den samiske befolkningen at det visstnok ble forslått i
  84 Sverige å straffeforfølge henne for oppvigleri før hun flyttet fra
  85 Sverige til Norge.  Radiopraterne fortalte videre at da Elsa Laula ga
  86 ut en pamflett for å inspirere samene til samling var dette den
  87 første bok gitt ut av en samisk dame noensinne.  Jeg fikk høre at
  88 denne korte teksten kun fantes på originalspråket svensk under
  89 tittelen «Inför lif eller död» og aldri var oversatt til norsk.  Da
  90 tenkte jeg, der jeg satt i bilen, at en norsk utgave kan vel jeg
  91 fikse.  Jeg har jo fått oversatt endel bøker, og en liten pamflett på
  92 noen få sider burde jo være grei skuring.&lt;/p&gt;
  93
  94 &lt;p&gt;Den imponerende Elsa Laula, som senere la til etternavnet Renberg, har
  95 blant annet fått dokumentaren
  96 «&lt;a href=&quot;https://www.nrk.no/video/elsa-laula-renberg-kvinnen-som-samlet-sapmi_SAPP67002117&quot;&gt;Elsa
  97 Laula Renberg, kvinnen som samlet Sápmi&lt;/a&gt;» (2017) av Per Kristian
  98 Olsen på NRK, NRK-artikkelen
  99 «&lt;a href=&quot;https://www.nrk.no/kultur/xl/et-liv-i-kamp-for-samefolkets-rettigheter-1.13351401&quot;&gt;Samenes
 100 Jeanne d’Arc&lt;/a&gt;» av Karen Brodshaug Sveen (2017), oppgaven
 101 «&lt;a href=&quot;https://nordligefolk.no/wp-content/uploads/2020/03/Elsa-Laulas-Info%CC%88r-Lif-och-Do%CC%88d.pdf&quot;&gt;Elsa
 102 Laulas Innför lif och död – sanningsord i de lappska
 103 förhållandena&lt;/a&gt;» av Edel Olsen, biografien
 104 «&lt;a href=&quot;https://www.siribrochjohansen.no/biografien-om-elsa-laula-renberg/&quot;&gt;Elsa
 105 Laula Renberg - Historien om samefolkets store Minerva&lt;/a&gt;» (2015) av
 106 Siri Broch Johansen og radiOrakel-podkasten
 107 &lt;a href=&quot;https://radiorakel.no/podcast/revolusjonen-har-et-kvinnelig-ansikt-elsa-laula/&quot;&gt;Revolusjonen
 108 har et kvinnelig ansikt – Elsa Laula&lt;/a&gt;, for å nevne de jeg har
 109 finnet uten å lete spesielt hardt.  En virkelig spennende dame, som i
 110 tillegg til å inspirere til opprettelsen av samiske organisasjoner,
 111 har inspirert til opprettelsen av Sametinget, og født seks barn der
 112 fire vokste opp.&lt;/p&gt;
 113
 114 &lt;p&gt;I dag er jeg veldig glad for å kunne annonsere at
 115 &lt;a href=&quot;http://www.hungry.com/~pere/publisher/#infoerlifellerdoed2024&quot;&gt;bokmålsoversettelsen
 116 er klar og tilgjengelig&lt;/a&gt; for både bestilling på papir og
 117 epub-utgave fra lulu.com, samt som nettside.  Den kringkastede
 118 bokinformasjonen ser slik ut:&lt;/p&gt;
 119
 120 &lt;blockquote&gt;
 121
 122 &lt;p&gt;Den 27 år gamle sørsamiske kvinnen Elsa Laula ga i august 1904 ut
 123 en pamflett i Stockholm. Opplaget var på 6000, finansiert av
 124 Stockholmsredaktøren Gustav Hedenström, som også bidro i stiftelsen av
 125 Lapparnes Centralforbund. Dette kampskriftet var den første boken gitt
 126 ut av en samisk kvinne, og hadde som mål å inspirere til opprettelsen
 127 av samiske foreninger over hele landet, samt skape blest om
 128 sentralforbundet. Pamfletten er et politisk manifest som fortsatt
 129 inspirerer i dag.&lt;/p&gt;
 130
 131 &lt;p&gt;Denne pamfletten er nå for første gang tilgjengelig på bokmål,
 132 sammen med en nyutgivelse av originalteksten på svensk.&lt;/p&gt;
 133
 134 &lt;/blockquote&gt;
 135
 136 &lt;p&gt;Oversettelsen hadde ikke vært mulig uten gode hjelpere.  En virkelig
 137 stor innsats både i korrekturarbeidet og utforskning av arkaiske
 138 svenske ord, står Axel Rosén bak.  I tillegg har jeg fått innspill fra
 139 Edel May Karlsen og flere andre både på språkføring og historisk
 140 bakgrunn for å forstå teksten.&lt;/p&gt;
 141
 142 &lt;p&gt;En kuriositet som jeg oppdaget i arbeidet med oversettelsen er at
 143 det ikke stemmer at denne boken ikke var oversatt til noen andre
 144 språk.  Anna Wuolab oversatte den til nordsamisk i 2017 i en utgave
 145 gitt ut av samisk skribent- och författarförening (Bágu čálliid
 146 searvi) under tittelen «Eallit vai jápmit? : duohtavuođasánit sámi
 147 diliid birra = Inför lif eller död? : sanningsord i de lappska
 148 förhållandena».  Papirutgaven er så vidt jeg kan forstå utsolgt fra
 149 forlaget og jeg har ikke klart å finne informasjonsside om boken på
 150 Internett.  Mulig den er mulig å få tak i som ebok, hvis en skal tro
 151 &lt;a href=&quot;https://search.worldcat.org/title/1405213087&quot;&gt;oppføring i
 152 worldcat&lt;/a&gt;.&lt;/p&gt;
 153
 154 &lt;p&gt;Oversetterrammeverket jeg har satt opp for å gjennomføre dette
 155 oversettelsesprosjektet håndterer flere språk.  Jeg er igang med
 156 engelsk utgave, og er åpen for å også gi ut andre oversettelser hvis
 157 noen er interessert i å gjøre jobben.  Det hadde vært ekstra moro å gi
 158 den ut på sørsamisk, det samiske språket i regionen der Elsa Laula kom
 159 fra.  Der er jeg som vanlig avhengig av frivillige som er også
 160 interessert i å gjøre dette på dugnad.&lt;/p&gt;
 161
 162 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
 163 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
 164 til min adresse
 165 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;. Merk,
 166 betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
 167 </description>
 168         </item>
 169
 170         <item>
 171                 <title>The 2024 LinuxCNC Norwegian developer gathering</title>
 172                 <link>https://people.skolelinux.org/pere/blog/The_2024_LinuxCNC_Norwegian_developer_gathering.html</link>
 173                 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_2024_LinuxCNC_Norwegian_developer_gathering.html</guid>
 174                 <pubDate>Fri, 31 May 2024 07:45:00 +0200</pubDate>
 175                 <description>&lt;p&gt;&lt;a href=&quot;https://linuxcnc.org/&quot;&gt;The LinuxCNC project&lt;/a&gt; is still
 176 going strong.  And I believe this great software system for numerical control of
 177 machines such as milling machines, lathes, plasma cutters, routers,
 178 cutting machines, robots and hexapods, would do even better with more
 179 in-person developer gatherings, so we plan to organise such gathering
 180 this summer too.&lt;/p&gt;
 181
 182 &lt;p&gt;The Norwegian LinuxCNC developer gathering take place the weekend
 183 Friday July 5th to 7th this year, and is open for everyone interested
 184 in contributing to LinuxCNC and free software manufacturing.  Up to
 185 date information about the gathering can be found in
 186 &lt;a href=&quot;https://sourceforge.net/p/emc/mailman/emc-developers/thread/123eaae0-f3b9-4170-a251-b7d608f1e974%40bofh.no/&quot;&gt;the
 187 developer mailing list thread&lt;/a&gt; where the gathering was announced.
 188 Thanks to the good people at
 189
 190 &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; as well as leftover money
 191 from last years gathering from
 192 &lt;a href=&quot;https://www.redpill-linpro.com/&quot;&gt;Redpill-Linpro&lt;/a&gt; and
 193 &lt;a href=&quot;https://www.nuugfoundation.no/no/&quot;&gt;NUUG Foundation&lt;/a&gt;, we
 194 have enough sponsor funds to pay for food, and probably also shelter
 195 for the people traveling from afar to join us.  If you would like to
 196 join the gathering, get in touch and add your details on
 197 &lt;a href=&quot;https://pad.efn.no/p/linuxcnc-2024-norway&quot;&gt;the pad&lt;/a&gt;.&lt;/p&gt;
 198
 199 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 200 activities, please send Bitcoin donations to my address
 201 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 202 </description>
 203         </item>
 204
 205         <item>
 206                 <title>45 orphaned Debian packages moved to git, 391 to go</title>
 207                 <link>https://people.skolelinux.org/pere/blog/45_orphaned_Debian_packages_moved_to_git__391_to_go.html</link>
 208                 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/45_orphaned_Debian_packages_moved_to_git__391_to_go.html</guid>
 209                 <pubDate>Thu, 25 Apr 2024 22:00:00 +0200</pubDate>
 210                 <description>&lt;p&gt;Nine days ago, I started migrating orphaned Debian packages with no
 211 version control system listed in debian/control of the source to git.
 212 At the time there were 438 such packages.  Now there are 391,
 213 according to the UDD.  In reality it is slightly less, as there is a
 214 delay between uploads and UDD updates.  In the nine days since, I have
 215 thus been able to work my way through ten percent of the packages.  I
 216 am starting to run out of steam, and hope someone else will also help
 217 brushing some dust of these packages.  Here is a recipe how to do it.
 218
 219 I start by picking a random package by querying the UDD for a list of
 220 10 random packages from the set of remaining packages:
 221
 222 &lt;blockquote&gt;&lt;pre&gt;
 223 PGPASSWORD=&quot;udd-mirror&quot; psql --port=5432 --host=udd-mirror.debian.net \
 224   --username=udd-mirror udd -c &quot;select source from sources \
 225    where release = &#39;sid&#39; and (vcs_url ilike &#39;%anonscm.debian.org%&#39; \
 226    OR vcs_browser ilike &#39;%anonscm.debian.org%&#39; or vcs_url IS NULL \
 227    OR vcs_browser IS NULL) AND maintainer ilike &#39;%packages@qa.debian.org%&#39; \
 228    order by random() limit 10;&quot;
 229 &lt;/pre&gt;&lt;/blockquote&gt;
 230
 231 &lt;p&gt;Next, I visit http://salsa.debian.org/debian and search for the
 232 package name, to ensure no git repository already exist.  If it does,
 233 I clone it and try to get it to an uploadable state, and add the Vcs-*
 234 entries in d/control to make the repository more widely known.  These
 235 packages are a minority, so I will not cover that use case here.&lt;/p&gt;
 236
 237 &lt;p&gt;For packages without an existing git repository, I run the
 238 following script &lt;tt&gt;debian-snap-to-salsa&lt;/tt&gt; to prepare a git
 239 repository with the existing packaging.&lt;/p&gt;
 240
 241 &lt;blockquote&gt;&lt;pre&gt;
 242 #!/bin/sh
 243 #
 244 # See also https://bugs.debian.org/804722#31
 245
 246 set -e
 247
 248 # Move to this Standards-Version.
 249 SV_LATEST=4.7.0
 250
 251 PKG=&quot;$1&quot;
 252
 253 if [ -z &quot;$PKG&quot; ]; then
 254     echo &quot;usage: $0 &lt;pkgname&gt;&quot;
 255     exit 1
 256 fi
 257
 258 if [ -e &quot;${PKG}-salsa&quot; ]; then
 259     echo &quot;error: ${PKG}-salsa already exist, aborting.&quot;
 260     exit 1
 261 fi
 262
 263 if [ -z &quot;ALLOWFAILURE&quot; ] ; then
 264     ALLOWFAILURE=false
 265 fi
 266
 267 # Fetch every snapshotted source package.  Manually loop until all
 268 # transfers succeed, as &#39;gbp import-dscs --debsnap&#39; do not fail on
 269 # download failures.
 270 until debsnap --force -v $PKG || $ALLOWFAILURE ; do sleep 1; done
 271 mkdir ${PKG}-salsa; cd ${PKG}-salsa
 272 git init
 273
 274 # Specify branches to override any debian/gbp.conf file present in the
 275 # source package.
 276 gbp import-dscs  --debian-branch=master --upstream-branch=upstream \
 277     --pristine-tar ../source-$PKG/*.dsc
 278
 279 # Add Vcs pointing to Salsa Debian project (must be manually created
 280 # and pushed to).
 281 if ! grep -q ^Vcs- debian/control ; then
 282     awk &quot;BEGIN { s=1 } /^\$/ { if (s==1) { print \&quot;Vcs-Browser: https://salsa.debian.org/debian/$PKG\&quot;; print \&quot;Vcs-Git: https://salsa.debian.org/debian/$PKG.git\&quot; }; s=0 } { print }&quot; &lt; debian/control &gt; debian/control.new &amp;&amp; mv debian/control.new debian/control
 283     git commit -m &quot;Updated vcs in d/control to Salsa.&quot; debian/control
 284 fi
 285
 286 # Tell gbp to enforce the use of pristine-tar.
 287 inifile +inifile debian/gbp.conf +create +section DEFAULT +key pristine-tar +value True
 288 git add debian/gbp.conf
 289 git commit -m &quot;Added d/gbp.conf to enforce the use of pristine-tar.&quot; debian/gbp.conf
 290
 291 # Update to latest Standards-Version.
 292 SV=&quot;$(grep ^Standards-Version: debian/control|awk &#39;{print $2}&#39;)&quot;
 293 if [ $SV_LATEST != $SV ]; then
 294     sed -i &quot;s/\(Standards-Version: \)\(.*\)/\1$SV_LATEST/&quot; debian/control
 295     git commit -m &quot;Updated Standards-Version from $SV to $SV_LATEST.&quot; debian/control
 296 fi
 297
 298 if grep -q pkg-config debian/control; then
 299     sed -i s/pkg-config/pkgconf/ debian/control
 300     git commit -m &quot;Replaced obsolete pkg-config build dependency with pkgconf.&quot; debian/control
 301 fi
 302
 303 if grep -q libncurses5-dev debian/control; then
 304     sed -i s/libncurses5-dev/libncurses-dev/ debian/control
 305     git commit -m &quot;Replaced obsolete libncurses5-dev build dependency with libncurses-dev.&quot; debian/control
 306 fi
 307 &lt;/pre&gt;&lt;/blockquote&gt;
 308
 309 Some times the debsnap script fail to download some of the versions.
 310 In those cases I investigate, and if I decide the failing versions
 311 will not be missed, I call it using ALLOWFAILURE=true to ignore the
 312 problem and create the git repository anyway.&lt;/p&gt;
 313
 314 &lt;p&gt;With the git repository in place, I do a test build (gbp
 315 buildpackage) to ensure the build is actually working.  If it does not
 316 I pick a different package, or if the build failure is trivial to fix,
 317 I fix it before continuing.  At this stage I revisit
 318 http://salsa.debian.org/debian and create the project under this group
 319 for the package.  I then follow the instructions to publish the local
 320 git repository.  Here is from a recent example:&lt;/p&gt;
 321
 322 &lt;blockquote&gt;&lt;pre&gt;
 323 git remote add origin git@salsa.debian.org:debian/perl-byacc.git
 324 git push --set-upstream origin master upstream pristine-tar
 325 git push --tags
 326 &lt;/pre&gt;&lt;/blockquote&gt;
 327
 328 &lt;p&gt;With a working build, I have a look at the build rules if I want to
 329 remove some more dust.  I normally try to move to debhelper compat
 330 level 13, which involves removing debian/compat and modifying
 331 debian/control to build depend on debhelper-compat (=13).  I also test
 332 with &#39;Rules-Requires-Root: no&#39; in debian/control and verify in
 333 debian/rules that hardening is enabled, and include all of these if
 334 the package still build.  If it fail to build with level 13, I try
 335 with 12, 11, 10 and so on until I find a level where it build, as I do
 336 not want to spend a lot of time fixing build issues.&lt;/p&gt;
 337
 338 &lt;p&gt;Some times, when I feel inspired, I make sure debian/copyright is
 339 converted to the machine readable format, often by starting with
 340 &#39;debhelper -cc&#39; and then cleaning up the autogenerated content until
 341 it matches realities.  If I feel like it, I might also clean up
 342 non-dh-based debian/rules files to use the short style dh build
 343 rules.&lt;/p&gt;
 344
 345 &lt;p&gt;Once I have removed all the dust I care to process for the package,
 346 I run &#39;gbp dch&#39; to generate a debian/changelog entry based on the
 347 commits done so far, run &#39;dch -r&#39; to switch from &#39;UNRELEASED&#39; to
 348 &#39;unstable&#39; and get an editor to make sure the &#39;QA upload&#39; marker is in
 349 place and that all long commit descriptions are wrapped into sensible
 350 lengths, run &#39;debcommit --release -a&#39; to commit and tag the new
 351 debian/changelog entry, run &#39;debuild -S&#39; to build a source only
 352 package, and &#39;dput ../perl-byacc_2.0-10_source.changes&#39; to do the
 353 upload.  During the entire process, and many times per step, I run
 354 &#39;debuild&#39; to verify the changes done still work.  I also some times
 355 verify the set of built files using &#39;find debian&#39; to see if I can spot
 356 any problems (like no file in usr/bin any more or empty package).  I
 357 also try to fix all lintian issues reported at the end of each
 358 &#39;debuild&#39; run.&lt;/p&gt;
 359
 360 &lt;p&gt;If I find Debian specific patches, I try to ensure their metadata
 361 is fairly up to date and some times I even try to reach out to
 362 upstream, to make the upstream project aware of the patches.  Most of
 363 my emails bounce, so the success rate is low.  For projects with no
 364 Homepage entry in debian/control I try to track down one, and for
 365 packages with no debian/watch file I try to create one.  But at least
 366 for some of the packages I have been unable to find a functioning
 367 upstream, and must skip both of these.&lt;/p&gt;
 368
 369 &lt;p&gt;If I could handle ten percent in nine days, twenty people could
 370 complete the rest in less then five days.  I use approximately twenty
 371 minutes per package, when I have twenty minutes spare time to spend.
 372 Perhaps you got twenty minutes to spare too?&lt;/p&gt;
 373
 374 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 375 activities, please send Bitcoin donations to my address
 376 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 377
 378 &lt;p&gt;&lt;strong&gt;Update 2024-05-04:&lt;/strong&gt; There is
 379 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/images/2024-05-04-debian-snap-to-salsa.sh&quot;&gt;an
 380 updated edition of my migration script&lt;/a&gt;, last updated
 381 2024-05-04.&lt;/p&gt;
 382 </description>
 383         </item>
 384
 385         <item>
 386                 <title>RAID status from LSI Megaraid controllers in Debian</title>
 387                 <link>https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_in_Debian.html</link>
 388                 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_in_Debian.html</guid>
 389                 <pubDate>Wed, 17 Apr 2024 17:00:00 +0200</pubDate>
 390                 <description>&lt;p&gt;I am happy to report that
 391 &lt;a href=&quot;https://github.com/namiltd/megactl&quot;&gt;the megactl package&lt;/a&gt;,
 392 useful to fetch RAID status when using the LSI Megaraid controller,
 393 now is available in Debian.  It passed NEW a few days ago, and is now
 394 &lt;a href=&quot;https://tracker.debian.org/pkg/megactl&quot;&gt;available in
 395 unstable&lt;/a&gt;, and probably showing up in testing in a weeks time.  The
 396 new version should provide Appstream hardware mapping and should
 397 integrate nicely with isenkram.&lt;/p&gt;
 398
 399 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 400 activities, please send Bitcoin donations to my address
 401 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 402
 403 </description>
 404         </item>
 405
 406         <item>
 407                 <title>Time to move orphaned Debian packages to git</title>
 408                 <link>https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html</link>
 409                 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html</guid>
 410                 <pubDate>Sun, 14 Apr 2024 09:30:00 +0200</pubDate>
 411                 <description>&lt;p&gt;There are several packages in Debian without a associated git
 412 repository with the packaging history.  This is unfortunate and it
 413 would be nice if more of these would do so.  Quote a lot of these are
 414 without a maintainer, ie listed as maintained by the
 415 &#39;&lt;a href=&quot;https://qa.debian.org/developer.php?email=packages%40qa.debian.org&quot;&gt;Debian
 416 QA Group&lt;/a&gt;&#39; place holder.  In fact, 438 packages have this property
 417 according to UDD (&lt;tt&gt;SELECT source FROM sources WHERE release = &#39;sid&#39;
 418 AND (vcs_url ilike &#39;%anonscm.debian.org%&#39; OR vcs_browser ilike
 419 &#39;%anonscm.debian.org%&#39; or vcs_url IS NULL OR vcs_browser IS NULL) AND
 420 maintainer ilike &#39;%packages@qa.debian.org%&#39;;&lt;/tt&gt;).  Such packages can
 421 be updated without much coordination by any Debian developer, as they
 422 are considered orphaned.&lt;/p&gt;
 423
 424 &lt;p&gt;To try to improve the situation and reduce the number of packages
 425 without associated git repository, I started a few days ago to search
 426 out candiates and provide them with a git repository under the
 427 &#39;debian&#39; collaborative Salsa project.  I started with the packages
 428 pointing to obsolete Alioth git repositories, and am now working my
 429 way across the ones completely without git references.  In addition to
 430 updating the Vcs-* debian/control fields, I try to update
 431 Standards-Version, debhelper compat level, simplify d/rules, switch to
 432 Rules-Requires-Root: no and fix lintian issues reported.  I only
 433 implement those that are trivial to fix, to avoid spending too much
 434 time on each orphaned package.  So far my experience is that it take
 435 aproximately 20 minutes to convert a package without any git
 436 references, and a lot more for packages with existing git repositories
 437 incompatible with git-buildpackages.&lt;/p&gt;
 438
 439 &lt;p&gt;So far I have converted 10 packages, and I will keep going until I
 440 run out of steam.  As should be clear from the numbers, there is
 441 enough packages remaining for more people to do the same without
 442 stepping on each others toes.  I find it useful to start by searching
 443 for a git repo already on salsa, as I find that some times a git repo
 444 has already been created, but no new version is uploaded to Debian
 445 yet.  In those cases I start with the existing git repository.  I
 446 convert to the git-buildpackage+pristine-tar workflow, and ensure a
 447 debian/gbp.conf file with &quot;pristine-tar=True&quot; is added early, to avoid
 448 uploading a orig.tar.gz with the wrong checksum by mistake.  Did that
 449 three times in the begin before I remembered my mistake.&lt;/p&gt;
 450
 451 &lt;p&gt;So, if you are a Debian Developer and got some spare time, perhaps
 452 considering migrating some orphaned packages to git?&lt;/p&gt;
 453
 454 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 455 activities, please send Bitcoin donations to my address
 456 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 457 </description>
 458         </item>
 459
 460         <item>
 461                 <title>Plain text accounting file from your bitcoin transactions</title>
 462                 <link>https://people.skolelinux.org/pere/blog/Plain_text_accounting_file_from_your_bitcoin_transactions.html</link>
 463                 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Plain_text_accounting_file_from_your_bitcoin_transactions.html</guid>
 464                 <pubDate>Thu, 7 Mar 2024 18:00:00 +0100</pubDate>
 465                 <description>&lt;p&gt;A while back I wrote a small script to extract the Bitcoin
 466 transactions in a wallet in the
 467 &lt;ahref=&quot;https://plaintextaccounting.org/&quot;&gt;ledger plain text accounting
 468 format&lt;/a&gt;.  The last few days I spent some time to get it working
 469 better with more special cases.  In case it can be useful for others,
 470 here is a copy:&lt;/p&gt;
 471
 472 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 473 #!/usr/bin/python3
 474 #  -*- coding: utf-8 -*-
 475 #  Copyright (c) 2023-2024 Petter Reinholdtsen
 476
 477 from decimal import Decimal
 478 import json
 479 import subprocess
 480 import time
 481
 482 import numpy
 483
 484 def format_float(num):
 485     return numpy.format_float_positional(num, trim=&#39;-&#39;)
 486
 487 accounts = {
 488     u&#39;amount&#39; : &#39;Assets:BTC:main&#39;,
 489 }
 490
 491 addresses = {
 492     &#39;&lt;some address&gt;&#39; : &#39;Assets:bankkonto&#39;,
 493     &#39;&lt;some address&gt;&#39; : &#39;Assets:bankkonto&#39;,
 494 }
 495
 496 def exec_json(cmd):
 497     proc = subprocess.Popen(cmd,stdout=subprocess.PIPE)
 498     j = json.loads(proc.communicate()[0], parse_float=Decimal)
 499     return j
 500
 501 def list_txs():
 502     # get all transactions for all accounts / addresses
 503     c = 0
 504     txs = []
 505     txidfee = {}
 506     limit=100000
 507     cmd = [&#39;bitcoin-cli&#39;, &#39;listtransactions&#39;, &#39;*&#39;, str(limit)]
 508     if True:
 509         txs.extend(exec_json(cmd))
 510     else:
 511         # Useful for debugging
 512         with open(&#39;transactions.json&#39;) as f:
 513             txs.extend(json.load(f, parse_float=Decimal))
 514     #print txs
 515     for tx in sorted(txs, key=lambda a: a[&#39;time&#39;]):
 516 #        print tx[&#39;category&#39;]
 517         if &#39;abandoned&#39; in tx and tx[&#39;abandoned&#39;]:
 518             continue
 519         if &#39;confirmations&#39; in tx and 0 &gt;= tx[&#39;confirmations&#39;]:
 520             continue
 521         when = time.strftime(&#39;%Y-%m-%d %H:%M&#39;, time.localtime(tx[&#39;time&#39;]))
 522         if &#39;message&#39; in tx:
 523             desc = tx[&#39;message&#39;]
 524         elif &#39;comment&#39; in tx:
 525             desc = tx[&#39;comment&#39;]
 526         elif &#39;label&#39; in tx:
 527             desc = tx[&#39;label&#39;]
 528         else:
 529             desc = &#39;n/a&#39;
 530         print(&quot;%s %s&quot; % (when, desc))
 531         if &#39;address&#39; in tx:
 532             print(&quot;  ; to bitcoin address %s&quot; % tx[&#39;address&#39;])
 533         else:
 534             print(&quot;  ; missing address in transaction, txid=%s&quot; % tx[&#39;txid&#39;])
 535         print(f&quot;  ; amount={tx[&#39;amount&#39;]}&quot;)
 536         if &#39;fee&#39;in tx:
 537             print(f&quot;  ; fee={tx[&#39;fee&#39;]}&quot;)
 538         for f in accounts.keys():
 539             if f in tx and Decimal(0) != tx[f]:
 540                 amount = tx[f]
 541                 print(&quot;  %-20s   %s BTC&quot; % (accounts[f], format_float(amount)))
 542         if &#39;fee&#39; in tx and Decimal(0) != tx[&#39;fee&#39;]:
 543             # Make sure to list fee used in several transactions only once.
 544             if &#39;fee&#39; in tx and tx[&#39;txid&#39;] in txidfee \
 545                and tx[&#39;fee&#39;] == txidfee[tx[&#39;txid&#39;]]:
 546                 True
 547             else:
 548                 fee = tx[&#39;fee&#39;]
 549                 print(&quot;  %-20s   %s BTC&quot; % (accounts[&#39;amount&#39;], format_float(fee)))
 550                 print(&quot;  %-20s   %s BTC&quot; % (&#39;Expences:BTC-fee&#39;, format_float(-fee)))
 551                 txidfee[tx[&#39;txid&#39;]] = tx[&#39;fee&#39;]
 552
 553         if &#39;address&#39; in tx and tx[&#39;address&#39;] in addresses:
 554             print(&quot;  %s&quot; % addresses[tx[&#39;address&#39;]])
 555         else:
 556             if &#39;generate&#39; == tx[&#39;category&#39;]:
 557                 print(&quot;  Income:BTC-mining&quot;)
 558             else:
 559                 if amount &lt; Decimal(0):
 560                     print(f&quot;  Assets:unknown:sent:update-script-addr-{tx[&#39;address&#39;]}&quot;)
 561                 else:
 562                     print(f&quot;  Assets:unknown:received:update-script-addr-{tx[&#39;address&#39;]}&quot;)
 563
 564         print()
 565         c = c + 1
 566     print(&quot;# Found %d transactions&quot; % c)
 567     if limit == c:
 568         print(f&quot;# Warning: Limit {limit} reached, consider increasing limit.&quot;)
 569
 570 def main():
 571     list_txs()
 572
 573 main()
 574 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 575
 576 &lt;p&gt;It is more of a proof of concept, and I do not expect it to handle
 577 all edge cases, but it worked for me, and perhaps you can find it
 578 useful too.&lt;/p&gt;
 579
 580 &lt;p&gt;To get a more interesting result, it is useful to map accounts sent
 581 to or received from to accounting accounts, using the
 582 &lt;tt&gt;addresses&lt;/tt&gt; hash.  As these will be very context dependent, I
 583 leave out my list to allow each user to fill out their own list of
 584 accounts.  Out of the box, &#39;ledger reg BTC:main&#39; should be able to
 585 show the amount of BTCs present in the wallet at any given time in the
 586 past.  For other and more valuable analysis, a account plan need to be
 587 set up in the &lt;tt&gt;addresses&lt;/tt&gt; hash.  Here is an example
 588 transaction:&lt;/p&gt;
 589
 590 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 591 2024-03-07 17:00 Donated to good cause
 592     Assets:BTC:main                           -0.1 BTC
 593     Assets:BTC:main                       -0.00001 BTC
 594     Expences:BTC-fee                       0.00001 BTC
 595     Expences:donations                         0.1 BTC
 596 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 597
 598 &lt;p&gt;It need a running Bitcoin Core daemon running, as it connect to it
 599 using &lt;tt&gt;bitcoin-cli listtransactions * 100000&lt;/tt&gt; to extract the
 600 transactions listed in the Wallet.&lt;/p&gt;
 601
 602 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 603 activities, please send Bitcoin donations to my address
 604 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 605 </description>
 606         </item>
 607
 608         <item>
 609                 <title>RAID status from LSI Megaraid controllers using free software</title>
 610                 <link>https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_using_free_software.html</link>
 611                 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/RAID_status_from_LSI_Megaraid_controllers_using_free_software.html</guid>
 612                 <pubDate>Sun, 3 Mar 2024 22:40:00 +0100</pubDate>
 613                 <description>&lt;p&gt;The last few days I have revisited RAID setup using the LSI
 614 Megaraid controller.  These are a family of controllers called PERC by
 615 Dell, and is present in several old PowerEdge servers, and I recently
 616 got my hands on one of these.  I had forgotten how to handle this RAID
 617 controller in Debian, so I had to take a peek in the
 618 &lt;a href=&quot;https://wiki.debian.org/LinuxRaidForAdmins&quot;&gt;Debian wiki page
 619 &quot;Linux and Hardware RAID: an administrator&#39;s summary&quot;&lt;/a&gt; to remember
 620 what kind of software is available to configure and monitor the disks
 621 and controller.  I prefer Free Software alternatives to proprietary
 622 tools, as the later tend to fall into disarray once the manufacturer
 623 loose interest, and often do not work with newer Linux Distributions.
 624 Sadly there is no free software tool to configure the RAID setup, only
 625 to monitor it. RAID can provide improved reliability and resilience in
 626 a storage solution, but only if it is being regularly checked and any
 627 broken disks are being replaced in time.  I thus want to ensure some
 628 automatic monitoring is available.&lt;/p&gt;
 629
 630 &lt;p&gt;In the discovery process, I came across a old free software tool to
 631 monitor PERC2, PERC3, PERC4 and PERC5 controllers, which to my
 632 surprise is not present in debian.  To help change that I created a
 633 &lt;a href=&quot;https://bugs.debian.org/1065322&quot;&gt;request for packaging of the
 634 megactl package&lt;/a&gt;, and tried to track down a usable version.
 635 &lt;a href=&quot;https://sourceforge.net/p/megactl/&quot;&gt;The original project
 636 site&lt;/a&gt; is on Sourceforge, but as far as I can tell that project has
 637 been dead for more than 15 years.  I managed to find a
 638 &lt;a href=&quot;https://github.com/hmage/megactl&quot;&gt;more recent fork on
 639 github&lt;/a&gt; from user hmage, but it is unclear to me if this is still
 640 being maintained.  It has not seen much improvements since 2016.  A
 641 &lt;a href=&quot;https://github.com/namiltd/megactl&quot;&gt;more up to date
 642 edition&lt;/a&gt; is a git fork from the original github fork by user
 643 namiltd, and this newer fork seem a lot more promising.  The owner of
 644 this github repository has replied to change proposals within hours,
 645 and had already added some improvements and support for more hardware.
 646 Sadly he is reluctant to commit to maintaining the tool and stated in
 647 &lt;a href=&quot;https://github.com/namiltd/megactl/pull/1&quot;&gt;my first pull
 648 request&lt;/A&gt; that he think a new release should be made based on the
 649 git repository owned by hmage.  I perfectly understand this
 650 reluctance, as I feel the same about maintaining yet another package
 651 in Debian when I barely have time to take care of the ones I already
 652 maintain, but do not really have high hopes that hmage will have time
 653 to spend on it and hope namiltd will change his mind.&lt;/p&gt;
 654
 655 &lt;p&gt;In any case, I created
 656 &lt;a href=&quot;https://salsa.debian.org/debian/megactl&quot;&gt;a draft package&lt;/a&gt;
 657 based on the namiltd edition and put it under the debian group on
 658 salsa.debian.org.  If you own a Dell PowerEdge server with one of the
 659 PERC controllers, or any other RAID controller using the megaraid or
 660 megaraid_sas Linux kernel modules, you might want to check it out.  If
 661 enough people are interested, perhaps the package will make it into
 662 the Debian archive.&lt;/p&gt;
 663
 664 &lt;p&gt;There are two tools provided, megactl for the megaraid Linux kernel
 665 module, and megasasctl for the megaraid_sas Linux kernel module. The
 666 simple output from the command on one of my machines look like this
 667 (yes, I know some of the disks have problems. :).&lt;/p&gt;
 668
 669 &lt;pre&gt;
 670 # megasasctl
 671 a0       PERC H730 Mini           encl:1 ldrv:2  batt:good
 672 a0d0       558GiB RAID 1   1x2  optimal
 673 a0d1      3067GiB RAID 0   1x11 optimal
 674 a0e32s0     558GiB  a0d0  online   errs: media:0  other:19
 675 a0e32s1     279GiB  a0d1  online
 676 a0e32s2     279GiB  a0d1  online
 677 a0e32s3     279GiB  a0d1  online
 678 a0e32s4     279GiB  a0d1  online
 679 a0e32s5     279GiB  a0d1  online
 680 a0e32s6     279GiB  a0d1  online
 681 a0e32s8     558GiB  a0d0  online   errs: media:0  other:17
 682 a0e32s9     279GiB  a0d1  online
 683 a0e32s10    279GiB  a0d1  online
 684 a0e32s11    279GiB  a0d1  online
 685 a0e32s12    279GiB  a0d1  online
 686 a0e32s13    279GiB  a0d1  online
 687
 688 #
 689 &lt;/pre&gt;
 690
 691 &lt;p&gt;In addition to displaying a simple status report, it can also test
 692 individual drives and print the various event logs.  Perhaps you too
 693 find it useful?&lt;/p&gt;
 694
 695 &lt;p&gt;In the packaging process I provided some patches upstream to
 696 improve installation and ensure
 697 &lt;ahref=&quot;https://github.com/namiltd/megactl/pull/2&quot;&gt;a Appstream
 698 metainfo file is provided&lt;/a&gt; to list all supported HW, to allow
 699 &lt;a href=&quot;https://tracker.debian.org/isenkram&quot;&gt;isenkram&lt;/a&gt; to propose
 700 the package on all servers with a relevant PCI card.&lt;/p&gt;
 701
 702 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 703 activities, please send Bitcoin donations to my address
 704 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 705
 706 </description>
 707         </item>
 708
 709         <item>
 710                 <title>Frokostseminar om Noark 5 i Oslo tirsdag 2024-03-12</title>
 711                 <link>https://people.skolelinux.org/pere/blog/Frokostseminar_om_Noark_5_i_Oslo_tirsdag_2024_03_12.html</link>
 712                 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Frokostseminar_om_Noark_5_i_Oslo_tirsdag_2024_03_12.html</guid>
 713                 <pubDate>Tue, 27 Feb 2024 15:15:00 +0100</pubDate>
 714                 <description>&lt;p&gt;Nikita-prosjektet, der jeg er involvert, inviterer i samarbeid med
 715 Oslo Byarkiv, forskningsgruppen METAINFO og foreningen NUUG, til et
 716 frokostseminar om Noark 5 og Noark 5 Tjenestegrensesnitt tirsdag
 717 2024-03-12.  Seminaret finner sted ved Oslo byarkiv.  Vi håper å få
 718 til videostrømming via Internett av presentasjoner og paneldiskusjon.
 719 Oppdatert program og lenker til påmeldingsskjema er
 720 &lt;a href=&quot;https://noark.codeberg.page/noark5-seminars/2023-03-12-noark-workshop.html&quot;&gt;tilgjengelig
 721 fra Nikita-prosjektet&lt;/a&gt;.  Arrangementet er gratis.
 722
 723 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
 724 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
 725 til min adresse
 726 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;. Merk,
 727 betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
 728 </description>
 729         </item>
 730
 731         <item>
 732                 <title>Welcome out of prison, Mickey, hope you find some freedom!</title>
 733                 <link>https://people.skolelinux.org/pere/blog/Welcome_out_of_prison__Mickey__hope_you_find_some_freedom_.html</link>
 734                 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Welcome_out_of_prison__Mickey__hope_you_find_some_freedom_.html</guid>
 735                 <pubDate>Mon, 1 Jan 2024 21:00:00 +0100</pubDate>
 736                 <description>&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;https://people.skolelinux.org/pere/blog/images/2024-01-01-mikke-verk-i-det-fri.jpeg&quot;/&gt;&lt;/p&gt;
 737
 738 &lt;p&gt;Today, the animation figure Mickey Mouse finally was released from
 739 the corporate copyright prison, as the 1928 movie
 740 &lt;a href=&quot;https://en.wikipedia.org/wiki/Steamboat_Willie&quot;&gt;Steamboat
 741 Willie&lt;/a&gt; entered the public domain in USA.  This movie was the first
 742 public appearance of Mickey Mouse.  Sadly the figure is still on
 743 probation, thanks to trademark laws and a the Disney corporations
 744 powerful pack of lawyers, as described in the 2017 article
 745 in &lt;a href=&quot;https://priceonomics.com/how-mickey-mouse-evades-the-public-domain/&quot;&gt;&quot;How
 746 Mickey Mouse Evades the Public Domain&quot;&lt;/a&gt; from Priceonomics.  On the
 747 positive side, the primary driver for repeated extentions of the
 748 duration of copyright has been Disney thanks to Mickey Mouse and the
 749 2028 movie, and as it now in the public domain I hope it will cause
 750 less urge to extend the already unreasonable long copyright
 751 duration.&lt;/p&gt;
 752
 753 &lt;p&gt;The first book I published, the 2004 book &lt;a
 754 href=&quot;https://free-culture.cc/&quot;&gt;&quot;Free Culture&quot; by Lawrence Lessig&lt;/a&gt;,
 755 published 2015 in
 756 &lt;a href=&quot;https://people.skolelinux.org/pere/publisher/#frikultur&quot;&gt;English,
 757 French and Norwegian Bokmål&lt;/a&gt;, touch on the story of Disney pushed
 758 for extending the copyright duration in USA.  It is a great book
 759 explaining problems with the current copyright regime and why we need
 760 Creative Commons movement, and I strongly recommend everyone to read
 761 it.&lt;/p&gt;
 762
 763 &lt;p&gt;This movie (with
 764 &lt;a href=&quot;https://www.imdb.com/title/tt0019422/&quot;&gt;IMDB ID tt0019422&lt;/a&gt;)
 765 is now available from the Internet Archive.  Two copies have been
 766 uploaded so far, one uploaded
 767 &lt;a href=&quot;https://archive.org/details/SteamboatWillie&quot;&gt;2015-11-04&lt;/a&gt;
 768 (&lt;a href=&quot;https://archive.org/download/SteamboatWillie/SteamboatWillie_archive.torrent&quot;&gt;torrent&lt;/a&gt;)
 769 and the other
 770 &lt;a href=&quot;https://archive.org/details/steamboat-willie-mickey&quot;&gt;2023-01-01&lt;/a&gt;
 771 (&lt;a href=&quot;https://archive.org/download/steamboat-willie-mickey/steamboat-willie-mickey_archive.torrent&quot;&gt;torrent&lt;/a&gt;) - see
 772 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/VLC_bittorrent_plugin_still_going_strong__new_upload_2_14_4.html&quot;&gt;VLC
 773 bittorrent plugin&lt;/a&gt; for streaming the video using the torrent link.
 774 I am very happy to see
 775 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/Legal_to_share_more_than_16_000_movies_listed_on_IMDB_.html&quot;&gt;the
 776 number of public domain movies&lt;/a&gt; increasing.  I look forward to
 777 when those are the majority.  Perhaps it will reduce the urge of the
 778 copyright industry to control its customers.&lt;/p&gt;
 779
 780 &lt;p&gt;A more
 781 &lt;a href=&quot;https://publicdomainreview.org/features/entering-the-public-domain/2024/&quot;&gt;comprehensive
 782 list of works entering the public domain in 2024&lt;/a&gt; is available from
 783 the Public Domain Review.&lt;/p&gt;
 784
 785 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 786 activities, please send Bitcoin donations to my address
 787 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 788 </description>
 789         </item>
 790
 791         </channel>
 792 </rss>