Generated.

[homepage.git] / blog / index.rss

<?xml version="1.0" encoding="utf-8"?>
<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
        <channel>
                <title>Petter Reinholdtsen</title>
                <description></description>
                <link>http://www.hungry.com/~pere/blog/</link>
                <atom:link href="http://www.hungry.com/~pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
        <item>
                <title>The 2025 LinuxCNC Norwegian developer gathering</title>
                <link>http://www.hungry.com/~pere/blog/The_2025_LinuxCNC_Norwegian_developer_gathering.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/The_2025_LinuxCNC_Norwegian_developer_gathering.html</guid>
                <pubDate>Sat, 11 Jan 2025 14:30:00 +0100</pubDate>
                <description>&lt;p&gt;&lt;a href=&quot;https://linuxcnc.org/&quot;&gt;The LinuxCNC project&lt;/a&gt; is
trotting along.  And I believe this great software system for
numerical control of machines such as milling machines, lathes, plasma
cutters, routers, cutting machines, robots and hexapods, would do even
better with more in-person developer gatherings, so we plan to
organise such gathering this summer too.&lt;/p&gt;

&lt;p&gt;This year we would like to invite to a small LinuxCNC and free
software fabrication workshop/gathering in Norway this summer for the
weekend starting July 4th 2024.  New this year is the slightly larger
scope, and we invite people also outside the LinuxCNC community to
join.  As earlier, we suggest to organize it as an
&lt;a href=&quot;https://en.wikipedia.org/wiki/Unconference&quot;&gt;unconference&lt;/a&gt;,
where the participants create the program upon arrival.&lt;/p&gt;

&lt;p&gt;The location is a metal workshop 15 minutes drive away from to the
Gardermoen airport (OSL), where there is a lot of space and a hotel only
5 minutes away by car. We plan to fire up the barbeque in the evenings.&lt;/p&gt;

&lt;p&gt;Please let us know if you would like to join.  We track the list of
participants on &lt;a href=https://pad.efn.no/p/linuxcnc-2025-norway&quot;&gt;a
simple pad&lt;/a&gt;, please add yourself there if you are interested in joining.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://www.nuugfoundation.no/&quot;&gt;The NUUG Foundation&lt;/a&gt; has on
our request offered to handle any money involved with this gathering,
in other words holding any sponsor funds and paying any bills.
NUUG Foundation is a spinnoff from the NUUG member organisation here
in Norway with long ties to the free software and open standards
communities.&lt;/p&gt;

&lt;p&gt;As usual we hope to find sponsors to pay for food, lodging and travel.&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>New lsdvd release 0.18 after ten years</title>
                <link>http://www.hungry.com/~pere/blog/New_lsdvd_release_0_18_after_ten_years.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/New_lsdvd_release_0_18_after_ten_years.html</guid>
                <pubDate>Sat, 21 Dec 2024 10:50:00 +0100</pubDate>
                <description>&lt;p&gt;The rumors of the death of
&lt;a href=&quot;https://sourceforge.net/projects/lsdvd/&quot;&gt;the lsdvd project&lt;/a&gt;
is slightly exaggerated.  And the last few months, we have been
working on fixing and improving it, culminating in a new release last
night.  This is the list of changes in the new 0.18 release, as
&lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/59108028/&quot;&gt;announced
on the project mailing list&lt;/a&gt;:&lt;/p&gt;

&lt;ul&gt;

  &lt;li&gt;Simplified autoconf setup, dropped --enable-debug option.&lt;/li&gt;
  &lt;li&gt;Improved video resolution reporting (&lt;a href=&quot;https://sourceforge.net/p/lsdvd/patches/8/&quot;&gt;Fixes #8&lt;/a&gt;).&lt;/li&gt;
  &lt;li&gt;Applied patches fetched from BSDs (&lt;a href=&quot;https://sourceforge.net/p/lsdvd/patches/7/&quot;&gt;Fixes #7&lt;/a&gt;).&lt;/li&gt;
  &lt;li&gt;Corrected Perl output (&lt;a href=&quot;https://sourceforge.net/p/lsdvd/patches/1/&quot;&gt;Fixes #1&lt;/a&gt;).&lt;/li&gt;
  &lt;li&gt;Adjusted Pan and Scan entries to produce valid XML.&lt;/li&gt;
  &lt;li&gt;Changed --help output from stderr to stdout.&lt;/li&gt;
  &lt;li&gt;Corrected aspect ratio and audio format formatting.&lt;/li&gt;
  &lt;li&gt;Avoid segfault when hitting a NULL pointer in the IFO structure.&lt;/li&gt;
  &lt;li&gt;Change build rules to supress compiler flags, to make it easier to
   spot warnings.&lt;/li&gt;
  &lt;li&gt;Set default DVD device based on OS (Linux, *BSD, Darwin)&lt;/li&gt;
  &lt;li&gt;Added libdvdread DVDDiscID to output.&lt;/li&gt;
  &lt;li&gt;Corrected typo in longest track value in XML format.&lt;/li&gt;
  &lt;li&gt;Switched XML output to use libxml to avoid string encoding issues.&lt;/li&gt;
  &lt;li&gt;Added simple build time test suite.&lt;/li&gt;
  &lt;li&gt;Cleaned up language code handling and adding missing mapping for
   language codes &#39;nb&#39; and &#39;nn&#39;.&lt;/li&gt;
  &lt;li&gt;Added JSON output support using -Oj.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The most exciting news to me is easy access to the DVDDiscID, which
make it a lot easier to identify DVD duplicates across a large
collection of DVDs.  During testing it has proved to be very effective
ad identifying when DVDs in a DVD box (say all Star Wars movies) is
identical to DVDs sold individually (like the same Star Wars movies
packaged individually).&lt;/p&gt;

&lt;p&gt;Because none of the current developers got access to do tarball
releases on Sourceforge any more, the release is only available as
&lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/0.18/tree/&quot;&gt;a git
tag&lt;/a&gt; in the repository.  Lets hope it do not take ten years for the
next release.  The project are discussing to move away from
Sourceforge, but it has not yet concluded.&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>More than 200 orphaned Debian packages moved to git, 216 to go</title>
                <link>http://www.hungry.com/~pere/blog/More_than_200_orphaned_Debian_packages_moved_to_git__216_to_go.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~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;http://www.hungry.com/~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;http://www.hungry.com/~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>http://www.hungry.com/~pere/blog/Some_notes_from_the_2024_LinuxCNC_Norwegian_developer_gathering.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Some_notes_from_the_2024_LinuxCNC_Norwegian_developer_gathering.html</guid>
                <pubDate>Wed, 10 Jul 2024 14:45:00 +0200</pubDate>
                <description>&lt;p&gt;The Norwegian &lt;a href=&quot;https://linuxcnc.org/&quot;&gt;The LinuxCNC&lt;/a&gt;
developer gathering 2024 is over.  It was a great and productive
weekend, and I am sad that it is over.&lt;/p&gt;

&lt;p&gt;Regular readers probably still remember what LinuxCNC is, but her
is a quick summary for those that forgot?  LinuxCNC is a free software
system for numerical control of machines such as milling machines,
lathes, plasma cutters, routers, cutting machines, robots and
hexapods.  It eats G-code and produce motor movement and other changes
to the physical world, while reading sensor input.&lt;/p&gt;

&lt;p&gt;I am not quite sure about the total head count, as not all people
were present at the gathering the entire weekend, but I believe it was
close to 10 people showing their faces at the gathering.  The &quot;hard
core&quot; of the group, who stayed the entire weekend, were two from
Norway, two from Germany and one from England.  I am happy with the
outcome from the gathering.  We managed to wrap up a new stable
LinuxCNC release 2.9.3 and even tested it on real hardware within
minutes of the release.  The release notes for 2.9.3 are still being
written, but should show up on on the project site in the next few
days.  We managed to go through around twenty pull requests and merge
then into either the stable release (2.9) or the development branch
(master).  There are still around thirty pull requests left to
process, so we are not out of work yet.  We even managed to
fix/improve a slightly worn lathe, and experiment with running a
mechanical clock using G-code.&lt;/p&gt;

&lt;p&gt;The evening barbeque worked well both on Saturday and Sunday.  It
is quite fun to light up a charcoal grill using compressed air.  Sadly
the weather was not the best, so we stayed indoors most of the
time.&lt;/p&gt;

&lt;p&gt;This gathering was made possible partly with sponsoring from both
&lt;a href=&quot;https://www.redpill-linpro.com/&quot;&gt;Redpill Linpro&lt;/a&gt;,
&lt;a href=&quot;https://debian.org/&quot;&gt;Debian&lt;/a&gt; and
&lt;a href=&quot;https://nuugfoundation.no/&quot;&gt;NUUG Foundation&lt;/a&gt;, and we are
most grateful for the support.  I would also like to thank the local
school for lending us some furniture, and of course the rest of the
members of the organizers team, Asle and Bosse, for their countless
contributions.  The gathering was such success that we want to do it
again next year.&lt;/p&gt;

&lt;p&gt;We plan to organize the next Norwegian LinuxCNC developer gathering
at the end of June next year, the weekend Friday 27th to Sunday 29th
of June 2025.  I recommend you reserve the dates on your calendar
today.  Other related communities are also welcome to join in, for
example those working on systems like FreeCAD and opencamlib, as I am
sure we have much in common and sharing experiences would be very
useful to all involved.  We are of course looking for sponsors for
this gathering already.  The total budget for this gathering was
around NOK 25.000 (around EUR 2.300), so our needs are quite modest.
Perhaps a machine or tools company would like to help out the free
software manufacturing community by sponsoring food, lodging and
transport for such gathering?&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>«Møter vi liv eller død?», pamfletten som inspirerte</title>
                <link>http://www.hungry.com/~pere/blog/_M_ter_vi_liv_eller_d_d____pamfletten_som_inspirerte.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/_M_ter_vi_liv_eller_d_d____pamfletten_som_inspirerte.html</guid>
                <pubDate>Tue, 4 Jun 2024 11:30:00 +0200</pubDate>
                <description>&lt;img align=&quot;center&quot; src=&quot;http://www.hungry.com/~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;

&lt;p&gt;Da jeg i høst hørte jeg et innslag på
&lt;a href=&quot;https://radiorakel.no/&quot;&gt;radiOrakel&lt;/a&gt; om en inspirerende dame
som levde for over hundre år siden, fikk jeg en vill ide.  Elsa Laula
var en svensk samisk dame som ikke bare fikk utdannelsen finansiert av
den danske dronningen, men som gjorde så god jobb med å inspirere og
organisere den samiske befolkningen at det visstnok ble forslått i
Sverige å straffeforfølge henne for oppvigleri før hun flyttet fra
Sverige til Norge.  Radiopraterne fortalte videre at da Elsa Laula ga
ut en pamflett for å inspirere samene til samling var dette den
første bok gitt ut av en samisk dame noensinne.  Jeg fikk høre at
denne korte teksten kun fantes på originalspråket svensk under
tittelen «Inför lif eller död» og aldri var oversatt til norsk.  Da
tenkte jeg, der jeg satt i bilen, at en norsk utgave kan vel jeg
fikse.  Jeg har jo fått oversatt endel bøker, og en liten pamflett på
noen få sider burde jo være grei skuring.&lt;/p&gt;

&lt;p&gt;Den imponerende Elsa Laula, som senere la til etternavnet Renberg, har
blant annet fått dokumentaren
«&lt;a href=&quot;https://www.nrk.no/video/elsa-laula-renberg-kvinnen-som-samlet-sapmi_SAPP67002117&quot;&gt;Elsa
Laula Renberg, kvinnen som samlet Sápmi&lt;/a&gt;» (2017) av Per Kristian
Olsen på NRK, NRK-artikkelen
«&lt;a href=&quot;https://www.nrk.no/kultur/xl/et-liv-i-kamp-for-samefolkets-rettigheter-1.13351401&quot;&gt;Samenes
Jeanne d’Arc&lt;/a&gt;» av Karen Brodshaug Sveen (2017), oppgaven
«&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
Laulas Innför lif och död – sanningsord i de lappska
förhållandena&lt;/a&gt;» av Edel Olsen, biografien
«&lt;a href=&quot;https://www.siribrochjohansen.no/biografien-om-elsa-laula-renberg/&quot;&gt;Elsa
Laula Renberg - Historien om samefolkets store Minerva&lt;/a&gt;» (2015) av
Siri Broch Johansen og radiOrakel-podkasten
&lt;a href=&quot;https://radiorakel.no/podcast/revolusjonen-har-et-kvinnelig-ansikt-elsa-laula/&quot;&gt;Revolusjonen
har et kvinnelig ansikt – Elsa Laula&lt;/a&gt;, for å nevne de jeg har
finnet uten å lete spesielt hardt.  En virkelig spennende dame, som i
tillegg til å inspirere til opprettelsen av samiske organisasjoner,
har inspirert til opprettelsen av Sametinget, og født seks barn der
fire vokste opp.&lt;/p&gt;

&lt;p&gt;I dag er jeg veldig glad for å kunne annonsere at
&lt;a href=&quot;http://www.hungry.com/~pere/publisher/#infoerlifellerdoed2024&quot;&gt;bokmålsoversettelsen
er klar og tilgjengelig&lt;/a&gt; for både bestilling på papir og
epub-utgave fra lulu.com, samt som nettside.  Den kringkastede
bokinformasjonen ser slik ut:&lt;/p&gt;

&lt;blockquote&gt;

&lt;p&gt;Den 27 år gamle sørsamiske kvinnen Elsa Laula ga i august 1904 ut
en pamflett i Stockholm. Opplaget var på 6000, finansiert av
Stockholmsredaktøren Gustav Hedenström, som også bidro i stiftelsen av
Lapparnes Centralforbund. Dette kampskriftet var den første boken gitt
ut av en samisk kvinne, og hadde som mål å inspirere til opprettelsen
av samiske foreninger over hele landet, samt skape blest om
sentralforbundet. Pamfletten er et politisk manifest som fortsatt
inspirerer i dag.&lt;/p&gt;

&lt;p&gt;Denne pamfletten er nå for første gang tilgjengelig på bokmål,
sammen med en nyutgivelse av originalteksten på svensk.&lt;/p&gt;

&lt;/blockquote&gt;

&lt;p&gt;Oversettelsen hadde ikke vært mulig uten gode hjelpere.  En virkelig
stor innsats både i korrekturarbeidet og utforskning av arkaiske
svenske ord, står Axel Rosén bak.  I tillegg har jeg fått innspill fra
Edel May Karlsen og flere andre både på språkføring og historisk
bakgrunn for å forstå teksten.&lt;/p&gt;

&lt;p&gt;En kuriositet som jeg oppdaget i arbeidet med oversettelsen er at
det ikke stemmer at denne boken ikke var oversatt til noen andre
språk.  Anna Wuolab oversatte den til nordsamisk i 2017 i en utgave
gitt ut av samisk skribent- och författarförening (Bágu čálliid
searvi) under tittelen «Eallit vai jápmit? : duohtavuođasánit sámi
diliid birra = Inför lif eller död? : sanningsord i de lappska
förhållandena».  Papirutgaven er så vidt jeg kan forstå utsolgt fra
forlaget og jeg har ikke klart å finne informasjonsside om boken på
Internett.  Mulig den er mulig å få tak i som ebok, hvis en skal tro
&lt;a href=&quot;https://search.worldcat.org/title/1405213087&quot;&gt;oppføring i
worldcat&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Oversetterrammeverket jeg har satt opp for å gjennomføre dette
oversettelsesprosjektet håndterer flere språk.  Jeg er igang med
engelsk utgave, og er åpen for å også gi ut andre oversettelser hvis
noen er interessert i å gjøre jobben.  Det hadde vært ekstra moro å gi
den ut på sørsamisk, det samiske språket i regionen der Elsa Laula kom
fra.  Der er jeg som vanlig avhengig av frivillige som er også
interessert i å gjøre dette på dugnad.&lt;/p&gt;

&lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
til min adresse
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;. Merk,
betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>The 2024 LinuxCNC Norwegian developer gathering</title>
                <link>http://www.hungry.com/~pere/blog/The_2024_LinuxCNC_Norwegian_developer_gathering.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/The_2024_LinuxCNC_Norwegian_developer_gathering.html</guid>
                <pubDate>Fri, 31 May 2024 07:45:00 +0200</pubDate>
                <description>&lt;p&gt;&lt;a href=&quot;https://linuxcnc.org/&quot;&gt;The LinuxCNC project&lt;/a&gt; is still
going strong.  And I believe this great software system for numerical control of
machines such as milling machines, lathes, plasma cutters, routers,
cutting machines, robots and hexapods, would do even better with more
in-person developer gatherings, so we plan to organise such gathering
this summer too.&lt;/p&gt;

&lt;p&gt;The Norwegian LinuxCNC developer gathering take place the weekend
Friday July 5th to 7th this year, and is open for everyone interested
in contributing to LinuxCNC and free software manufacturing.  Up to
date information about the gathering can be found in
&lt;a href=&quot;https://sourceforge.net/p/emc/mailman/emc-developers/thread/123eaae0-f3b9-4170-a251-b7d608f1e974%40bofh.no/&quot;&gt;the
developer mailing list thread&lt;/a&gt; where the gathering was announced.
Thanks to the good people at

&lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; as well as leftover money
from last years gathering from
&lt;a href=&quot;https://www.redpill-linpro.com/&quot;&gt;Redpill-Linpro&lt;/a&gt; and
&lt;a href=&quot;https://www.nuugfoundation.no/no/&quot;&gt;NUUG Foundation&lt;/a&gt;, we
have enough sponsor funds to pay for food, and probably also shelter
for the people traveling from afar to join us.  If you would like to
join the gathering, get in touch and add your details on
&lt;a href=&quot;https://pad.efn.no/p/linuxcnc-2024-norway&quot;&gt;the pad&lt;/a&gt;.&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>45 orphaned Debian packages moved to git, 391 to go</title>
                <link>http://www.hungry.com/~pere/blog/45_orphaned_Debian_packages_moved_to_git__391_to_go.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/45_orphaned_Debian_packages_moved_to_git__391_to_go.html</guid>
                <pubDate>Thu, 25 Apr 2024 22:00:00 +0200</pubDate>
                <description>&lt;p&gt;Nine days ago, I started migrating orphaned Debian packages with no
version control system listed in debian/control of the source to git.
At the time there were 438 such packages.  Now there are 391,
according to the UDD.  In reality it is slightly less, as there is a
delay between uploads and UDD updates.  In the nine days since, I have
thus been able to work my way through ten percent of the packages.  I
am starting to run out of steam, and hope someone else will also help
brushing some dust of these packages.  Here is a recipe how to do it.

I start by picking a random package by querying the UDD for a list of
10 random packages from the set of remaining packages:

&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;Next, I visit http://salsa.debian.org/debian and search for the
package name, to ensure no git repository already exist.  If it does,
I clone it and try to get it to an uploadable state, and add the Vcs-*
entries in d/control to make the repository more widely known.  These
packages are a minority, so I will not cover that use case here.&lt;/p&gt;

&lt;p&gt;For packages without an existing git repository, I run the
following script &lt;tt&gt;debian-snap-to-salsa&lt;/tt&gt; to prepare a git
repository with the existing packaging.&lt;/p&gt;

&lt;blockquote&gt;&lt;pre&gt;
#!/bin/sh
#
# See also https://bugs.debian.org/804722#31

set -e

# Move to this Standards-Version.
SV_LATEST=4.7.0

PKG=&quot;$1&quot;

if [ -z &quot;$PKG&quot; ]; then
    echo &quot;usage: $0 &lt;pkgname&gt;&quot;
    exit 1
fi

if [ -e &quot;${PKG}-salsa&quot; ]; then
    echo &quot;error: ${PKG}-salsa already exist, aborting.&quot;
    exit 1
fi

if [ -z &quot;ALLOWFAILURE&quot; ] ; then
    ALLOWFAILURE=false
fi

# Fetch every snapshotted source package.  Manually loop until all
# transfers succeed, as &#39;gbp import-dscs --debsnap&#39; do not fail on
# download failures.
until debsnap --force -v $PKG || $ALLOWFAILURE ; do sleep 1; done
mkdir ${PKG}-salsa; cd ${PKG}-salsa
git init

# Specify branches to override any debian/gbp.conf file present in the
# source package.
gbp import-dscs  --debian-branch=master --upstream-branch=upstream \
    --pristine-tar ../source-$PKG/*.dsc

# Add Vcs pointing to Salsa Debian project (must be manually created
# and pushed to).
if ! grep -q ^Vcs- debian/control ; then
    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
    git commit -m &quot;Updated vcs in d/control to Salsa.&quot; debian/control
fi

# Tell gbp to enforce the use of pristine-tar.
inifile +inifile debian/gbp.conf +create +section DEFAULT +key pristine-tar +value True
git add debian/gbp.conf
git commit -m &quot;Added d/gbp.conf to enforce the use of pristine-tar.&quot; debian/gbp.conf

# Update to latest Standards-Version.
SV=&quot;$(grep ^Standards-Version: debian/control|awk &#39;{print $2}&#39;)&quot;
if [ $SV_LATEST != $SV ]; then
    sed -i &quot;s/\(Standards-Version: \)\(.*\)/\1$SV_LATEST/&quot; debian/control
    git commit -m &quot;Updated Standards-Version from $SV to $SV_LATEST.&quot; debian/control
fi

if grep -q pkg-config debian/control; then
    sed -i s/pkg-config/pkgconf/ debian/control
    git commit -m &quot;Replaced obsolete pkg-config build dependency with pkgconf.&quot; debian/control
fi

if grep -q libncurses5-dev debian/control; then
    sed -i s/libncurses5-dev/libncurses-dev/ debian/control
    git commit -m &quot;Replaced obsolete libncurses5-dev build dependency with libncurses-dev.&quot; debian/control
fi
&lt;/pre&gt;&lt;/blockquote&gt;

Some times the debsnap script fail to download some of the versions.
In those cases I investigate, and if I decide the failing versions
will not be missed, I call it using ALLOWFAILURE=true to ignore the
problem and create the git repository anyway.&lt;/p&gt;

&lt;p&gt;With the git repository in place, I do a test build (gbp
buildpackage) to ensure the build is actually working.  If it does not
I pick a different package, or if the build failure is trivial to fix,
I fix it before continuing.  At this stage I revisit
http://salsa.debian.org/debian and create the project under this group
for the package.  I then follow the instructions to publish the local
git repository.  Here is from a recent example:&lt;/p&gt;

&lt;blockquote&gt;&lt;pre&gt;
git remote add origin git@salsa.debian.org:debian/perl-byacc.git
git push --set-upstream origin master upstream pristine-tar
git push --tags
&lt;/pre&gt;&lt;/blockquote&gt;

&lt;p&gt;With a working build, I have a look at the build rules if I want to
remove some more dust.  I normally try to move to debhelper compat
level 13, which involves removing debian/compat and modifying
debian/control to build depend on debhelper-compat (=13).  I also test
with &#39;Rules-Requires-Root: no&#39; in debian/control and verify in
debian/rules that hardening is enabled, and include all of these if
the package still build.  If it fail to build with level 13, I try
with 12, 11, 10 and so on until I find a level where it build, as I do
not want to spend a lot of time fixing build issues.&lt;/p&gt;

&lt;p&gt;Some times, when I feel inspired, I make sure debian/copyright is
converted to the machine readable format, often by starting with
&#39;debhelper -cc&#39; and then cleaning up the autogenerated content until
it matches realities.  If I feel like it, I might also clean up
non-dh-based debian/rules files to use the short style dh build
rules.&lt;/p&gt;

&lt;p&gt;Once I have removed all the dust I care to process for the package,
I run &#39;gbp dch&#39; to generate a debian/changelog entry based on the
commits done so far, run &#39;dch -r&#39; to switch from &#39;UNRELEASED&#39; to
&#39;unstable&#39; and get an editor to make sure the &#39;QA upload&#39; marker is in
place and that all long commit descriptions are wrapped into sensible
lengths, run &#39;debcommit --release -a&#39; to commit and tag the new
debian/changelog entry, run &#39;debuild -S&#39; to build a source only
package, and &#39;dput ../perl-byacc_2.0-10_source.changes&#39; to do the
upload.  During the entire process, and many times per step, I run
&#39;debuild&#39; to verify the changes done still work.  I also some times
verify the set of built files using &#39;find debian&#39; to see if I can spot
any problems (like no file in usr/bin any more or empty package).  I
also try to fix all lintian issues reported at the end of each
&#39;debuild&#39; run.&lt;/p&gt;

&lt;p&gt;If I find Debian specific patches, I try to ensure their metadata
is fairly up to date and some times I even try to reach out to
upstream, to make the upstream project aware of the patches.  Most of
my emails bounce, so the success rate is low.  For projects with no
Homepage entry in debian/control I try to track down one, and for
packages with no debian/watch file I try to create one.  But at least
for some of the packages I have been unable to find a functioning
upstream, and must skip both of these.&lt;/p&gt;

&lt;p&gt;If I could handle ten percent in nine days, twenty people could
complete the rest in less then five days.  I use approximately twenty
minutes per package, when I have twenty minutes spare time to spend.
Perhaps you got twenty minutes to spare too?&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;

&lt;p&gt;&lt;strong&gt;Update 2024-05-04:&lt;/strong&gt; There is
&lt;a href=&quot;http://www.hungry.com/~pere/blog/images/2024-05-04-debian-snap-to-salsa.sh&quot;&gt;an
updated edition of my migration script&lt;/a&gt;, last updated
2024-05-04.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>RAID status from LSI Megaraid controllers in Debian</title>
                <link>http://www.hungry.com/~pere/blog/RAID_status_from_LSI_Megaraid_controllers_in_Debian.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/RAID_status_from_LSI_Megaraid_controllers_in_Debian.html</guid>
                <pubDate>Wed, 17 Apr 2024 17:00:00 +0200</pubDate>
                <description>&lt;p&gt;I am happy to report that
&lt;a href=&quot;https://github.com/namiltd/megactl&quot;&gt;the megactl package&lt;/a&gt;,
useful to fetch RAID status when using the LSI Megaraid controller,
now is available in Debian.  It passed NEW a few days ago, and is now
&lt;a href=&quot;https://tracker.debian.org/pkg/megactl&quot;&gt;available in
unstable&lt;/a&gt;, and probably showing up in testing in a weeks time.  The
new version should provide Appstream hardware mapping and should
integrate nicely with isenkram.&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>Time to move orphaned Debian packages to git</title>
                <link>http://www.hungry.com/~pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Time_to_move_orphaned_Debian_packages_to_git.html</guid>
                <pubDate>Sun, 14 Apr 2024 09:30:00 +0200</pubDate>
                <description>&lt;p&gt;There are several packages in Debian without a associated git
repository with the packaging history.  This is unfortunate and it
would be nice if more of these would do so.  Quote a lot of these are
without a maintainer, ie listed as maintained by the
&#39;&lt;a href=&quot;https://qa.debian.org/developer.php?email=packages%40qa.debian.org&quot;&gt;Debian
QA Group&lt;/a&gt;&#39; place holder.  In fact, 438 packages have this property
according to UDD (&lt;tt&gt;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;;&lt;/tt&gt;).  Such packages can
be updated without much coordination by any Debian developer, as they
are considered orphaned.&lt;/p&gt;

&lt;p&gt;To try to improve the situation and reduce the number of packages
without associated git repository, I started a few days ago to search
out candiates and provide them with a git repository under the
&#39;debian&#39; collaborative Salsa project.  I started with the packages
pointing to obsolete Alioth git repositories, and am now working my
way across the ones completely without git references.  In addition to
updating the Vcs-* debian/control fields, I try to update
Standards-Version, debhelper compat level, simplify d/rules, switch to
Rules-Requires-Root: no and fix lintian issues reported.  I only
implement those that are trivial to fix, to avoid spending too much
time on each orphaned package.  So far my experience is that it take
aproximately 20 minutes to convert a package without any git
references, and a lot more for packages with existing git repositories
incompatible with git-buildpackages.&lt;/p&gt;

&lt;p&gt;So far I have converted 10 packages, and I will keep going until I
run out of steam.  As should be clear from the numbers, there is
enough packages remaining for more people to do the same without
stepping on each others toes.  I find it useful to start by searching
for a git repo already on salsa, as I find that some times a git repo
has already been created, but no new version is uploaded to Debian
yet.  In those cases I start with the existing git repository.  I
convert to the git-buildpackage+pristine-tar workflow, and ensure a
debian/gbp.conf file with &quot;pristine-tar=True&quot; is added early, to avoid
uploading a orig.tar.gz with the wrong checksum by mistake.  Did that
three times in the begin before I remembered my mistake.&lt;/p&gt;

&lt;p&gt;So, if you are a Debian Developer and got some spare time, perhaps
considering migrating some orphaned packages to git?&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>Plain text accounting file from your bitcoin transactions</title>
                <link>http://www.hungry.com/~pere/blog/Plain_text_accounting_file_from_your_bitcoin_transactions.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Plain_text_accounting_file_from_your_bitcoin_transactions.html</guid>
                <pubDate>Thu, 7 Mar 2024 18:00:00 +0100</pubDate>
                <description>&lt;p&gt;A while back I wrote a small script to extract the Bitcoin
transactions in a wallet in the
&lt;ahref=&quot;https://plaintextaccounting.org/&quot;&gt;ledger plain text accounting
format&lt;/a&gt;.  The last few days I spent some time to get it working
better with more special cases.  In case it can be useful for others,
here is a copy:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
#!/usr/bin/python3
#  -*- coding: utf-8 -*-
#  Copyright (c) 2023-2024 Petter Reinholdtsen

from decimal import Decimal
import json
import subprocess
import time

import numpy

def format_float(num):
    return numpy.format_float_positional(num, trim=&#39;-&#39;)

accounts = {
    u&#39;amount&#39; : &#39;Assets:BTC:main&#39;,
}

addresses = {
    &#39;&lt;some address&gt;&#39; : &#39;Assets:bankkonto&#39;,
    &#39;&lt;some address&gt;&#39; : &#39;Assets:bankkonto&#39;,
}

def exec_json(cmd):
    proc = subprocess.Popen(cmd,stdout=subprocess.PIPE)
    j = json.loads(proc.communicate()[0], parse_float=Decimal)
    return j

def list_txs():
    # get all transactions for all accounts / addresses
    c = 0
    txs = []
    txidfee = {}
    limit=100000
    cmd = [&#39;bitcoin-cli&#39;, &#39;listtransactions&#39;, &#39;*&#39;, str(limit)]
    if True:
        txs.extend(exec_json(cmd))
    else:
        # Useful for debugging
        with open(&#39;transactions.json&#39;) as f:
            txs.extend(json.load(f, parse_float=Decimal))
    #print txs
    for tx in sorted(txs, key=lambda a: a[&#39;time&#39;]):
#        print tx[&#39;category&#39;]
        if &#39;abandoned&#39; in tx and tx[&#39;abandoned&#39;]:
            continue
        if &#39;confirmations&#39; in tx and 0 &gt;= tx[&#39;confirmations&#39;]:
            continue
        when = time.strftime(&#39;%Y-%m-%d %H:%M&#39;, time.localtime(tx[&#39;time&#39;]))
        if &#39;message&#39; in tx:
            desc = tx[&#39;message&#39;]
        elif &#39;comment&#39; in tx:
            desc = tx[&#39;comment&#39;]
        elif &#39;label&#39; in tx:
            desc = tx[&#39;label&#39;]
        else:
            desc = &#39;n/a&#39;
        print(&quot;%s %s&quot; % (when, desc))
        if &#39;address&#39; in tx:
            print(&quot;  ; to bitcoin address %s&quot; % tx[&#39;address&#39;])
        else:
            print(&quot;  ; missing address in transaction, txid=%s&quot; % tx[&#39;txid&#39;])
        print(f&quot;  ; amount={tx[&#39;amount&#39;]}&quot;)
        if &#39;fee&#39;in tx:
            print(f&quot;  ; fee={tx[&#39;fee&#39;]}&quot;)
        for f in accounts.keys():
            if f in tx and Decimal(0) != tx[f]:
                amount = tx[f]
                print(&quot;  %-20s   %s BTC&quot; % (accounts[f], format_float(amount)))
        if &#39;fee&#39; in tx and Decimal(0) != tx[&#39;fee&#39;]:
            # Make sure to list fee used in several transactions only once.
            if &#39;fee&#39; in tx and tx[&#39;txid&#39;] in txidfee \
               and tx[&#39;fee&#39;] == txidfee[tx[&#39;txid&#39;]]:
                True
            else:
                fee = tx[&#39;fee&#39;]
                print(&quot;  %-20s   %s BTC&quot; % (accounts[&#39;amount&#39;], format_float(fee)))
                print(&quot;  %-20s   %s BTC&quot; % (&#39;Expences:BTC-fee&#39;, format_float(-fee)))
                txidfee[tx[&#39;txid&#39;]] = tx[&#39;fee&#39;]

        if &#39;address&#39; in tx and tx[&#39;address&#39;] in addresses:
            print(&quot;  %s&quot; % addresses[tx[&#39;address&#39;]])
        else:
            if &#39;generate&#39; == tx[&#39;category&#39;]:
                print(&quot;  Income:BTC-mining&quot;)
            else:
                if amount &lt; Decimal(0):
                    print(f&quot;  Assets:unknown:sent:update-script-addr-{tx[&#39;address&#39;]}&quot;)
                else:
                    print(f&quot;  Assets:unknown:received:update-script-addr-{tx[&#39;address&#39;]}&quot;)

        print()
        c = c + 1
    print(&quot;# Found %d transactions&quot; % c)
    if limit == c:
        print(f&quot;# Warning: Limit {limit} reached, consider increasing limit.&quot;)

def main():
    list_txs()

main()
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;It is more of a proof of concept, and I do not expect it to handle
all edge cases, but it worked for me, and perhaps you can find it
useful too.&lt;/p&gt;

&lt;p&gt;To get a more interesting result, it is useful to map accounts sent
to or received from to accounting accounts, using the
&lt;tt&gt;addresses&lt;/tt&gt; hash.  As these will be very context dependent, I
leave out my list to allow each user to fill out their own list of
accounts.  Out of the box, &#39;ledger reg BTC:main&#39; should be able to
show the amount of BTCs present in the wallet at any given time in the
past.  For other and more valuable analysis, a account plan need to be
set up in the &lt;tt&gt;addresses&lt;/tt&gt; hash.  Here is an example
transaction:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2024-03-07 17:00 Donated to good cause
    Assets:BTC:main                           -0.1 BTC
    Assets:BTC:main                       -0.00001 BTC
    Expences:BTC-fee                       0.00001 BTC
    Expences:donations                         0.1 BTC
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;It need a running Bitcoin Core daemon running, as it connect to it
using &lt;tt&gt;bitcoin-cli listtransactions * 100000&lt;/tt&gt; to extract the
transactions listed in the Wallet.&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>
        
        </channel>
</rss>