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>New oggz release 1.1.2 after 15 years</title>
                <link>http://www.hungry.com/~pere/blog/New_oggz_release_1_1_2_after_15_years.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/New_oggz_release_1_1_2_after_15_years.html</guid>
                <pubDate>Sun, 9 Feb 2025 01:10:00 +0100</pubDate>
                <description>&lt;p&gt;A little over a week ago, I noticed
&lt;a href=&quot;https://tracker.debian.org/pkg/liboggz&quot;&gt;the liboggz
package&lt;/a&gt; on my Debian dashboard had not had a new upstream release
for a while.  A closer look showed that its last release, version
1.1.1, happened in 2010.  A few patches had accumulated in the Debian
package, and I even noticed that I had passed on these patches to
upstream five years ago.  A handful crash bugs had been reported
against the Debian package, and looking at the upstream repository I
even found a few crash bugs reported there too.  To add insult to
injury, I discovered that upstream had accumulated several fixes the
years between 2010 and now, and many of them had not made their way
into the Debian package.  I decided enough was enough, and that a new
upstream release was needed fixing these nasty crash bugs.  Luckily I
am also a member of the Xiph team, aka upstream, and could actually go
to work immediately to fix it.&lt;/p&gt;

&lt;p&gt;I started by adding automatic build testing on
&lt;a href=&quot;https://gitlab.xiph.org/xiph/liboggz&quot;&gt;the Xiph gitlab oggz
instance&lt;/a&gt;, to get a better idea of the state of affairs with the
code base.  This exposed a few build problems, which I had to fix.  In
parallel to this, I sent an email announcing my wish for a new release
to every person who had committed to the upstream code base since
2010, and asked for help doing a new release both on email and on the
#xiph IRC channel.  Sadly only a fraction of their email providers
accepted my email.  But Ralph Giles in the Xiph team came to the
rescue and provided invaluable help to guide be through the release
Xiph process.  While this was going on, I spent a few days tracking
down the crash bugs with good help from
&lt;a href=&quot;https://www.valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, and came up with
patch proposals to get rid of at least these specific crash bugs.  The
open issues also had to be checked.  Several of them proved to be
fixed already, but a few I had to creat patches for.  I also checked
out the Debian, Arch, Fedora, Suse and Gentoo packages to see if there
were patches applied in these Linux distributions that should be
passed upstream.  The end result was ready yesterday.  A new liboggz
release, version 1.1.2, was tagged, wrapped up and published on the
project page.  And today, the new release was uploaded into
Debian.&lt;/p&gt;

&lt;p&gt;You are probably by now curious on what actually changed in the
library.  I guess the most interesting new feature was support for
Opus and VP8.  Almost all other changes were stability or
documentation fixes.  The rest were related to the gitlab continuous
integration testing.  All in all, this was really a minor update,
hence the version bump only from 1.1.1 to to 1.1.2, but it was long
overdue and I am very happy that it is out the door.&lt;/p&gt;

&lt;p&gt;One change proposed upstream was not included this time, as it
extended the API and changed some of the existing library methods, and
thus require a major SONAME bump and possibly code changes in every
program using the library.  As I am not that familiar with the code
base, I am unsure if I am the right person to evaluate the change.
Perhaps later.&lt;/p&gt;

&lt;p&gt;Since the release was tagged, a few minor fixes has been committed
upstream already: automatic testing the cross building to Windows, and
documentation updates linking to the correct project page.  If a
important issue is discovered with this release, I guess a new release
might happen soon including the minor fixes.  If not, perhaps they can
wait fifteen years. :)&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>Frokostseminar om Noark 5 i Oslo fredag 2025-03-14</title>
                <link>http://www.hungry.com/~pere/blog/Frokostseminar_om_Noark_5_i_Oslo_fredag_2025_03_14.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Frokostseminar_om_Noark_5_i_Oslo_fredag_2025_03_14.html</guid>
                <pubDate>Fri, 31 Jan 2025 11:00:00 +0100</pubDate>
                <description>&lt;p&gt;Nikita-prosjektet, der jeg er involvert, inviterer i samarbeid med
forskningsgruppen METAINFO og foreningen NUUG, til et frokostseminar
om Noark 5 og Noark 5 Tjenestegrensesnitt fredag 2025-03-14.  Fokus
denne gangen er på bevaring og kassasjon.  Seminaret finner sted ved
OsloMet, Pilestredet 46.  Vi håper å få til videostrømming via
Internett av presentasjoner og paneldiskusjon.  Oppdatert program og
lenker til påmeldingsskjema finner en via
&lt;a href=&quot;https://noark.codeberg.page/noark5-seminars/2025-03-14-noark-workshop.html&quot;&gt;arrangementets infoside&lt;/a&gt;.  Arrangementet er gratis.

&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>121 packages in Debian mapped to hardware for automatic recommendation</title>
                <link>http://www.hungry.com/~pere/blog/121_packages_in_Debian_mapped_to_hardware_for_automatic_recommendation.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/121_packages_in_Debian_mapped_to_hardware_for_automatic_recommendation.html</guid>
                <pubDate>Sun, 19 Jan 2025 12:40:00 +0100</pubDate>
                <description>&lt;p&gt;For some years now, I have been working on a automatic hardware
based package recommendation system for Debian and other Linux
distributions.  The isenkram system I started on back in 2013 now
consist of two subsystems, one locating firmware files using the
information provided by apt-file, and one matching hardware to
packages using information provided by AppStream.  The former is very
similar to the mechanism implemented in debian-installer to pick the
right firmware packages to install. This post is about the latter
system.  Thanks to steady progress and good help from both other
Debian and upstream developers, I am happy to report that
&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;the Isenkram
system&lt;/a&gt; now are able to recommend 121 packages using information
provided via
&lt;a href=&quot;https://www.freedesktop.org/wiki/Distributions/AppStream/&quot;&gt;AppStream&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The mapping is done using modalias information provided by the
kernel, the same information used by udev when creating device files,
and the kernel when deciding which kernel modules to load.  To get all
the modalias identifiers relevant for your machine, you can run the
following command on the command line:&lt;/p&gt;

&lt;pre&gt;
find /sys/devices -name modalias -print0 | xargs -0 sort -u
&lt;/pre&gt;

&lt;p&gt;The modalias identifiers can look something like this:&lt;/p&gt;

&lt;pre&gt;
acpi:PNP0000
cpu:type:x86,ven0000fam0006mod003F:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0075,0076,0078,0079,007C,0080,0081,0082,0083,0084,0085,0086,0087,0088,0089,008B,008C,008D,008E,008F,0091,0092,0093,0094,0095,0096,0097,0098,0099,009A,009B,009C,009D,009E,00C0,00C5,00E1,00E3,00EB,00ED,00F0,00F1,00F3,00F5,00F6,00F9,00FA,00FB,00FD,00FF,0100,0101,0102,0103,0111,0120,0121,0123,0125,0127,0128,0129,012A,012C,012D,0140,0160,0161,0165,016C,017B,01C0,01C1,01C2,01C4,01C5,01C6,01F9,024A,025A,025B,025C,025F,0282
dmi:bvnDellInc.:bvr2.18.1:bd08/14/2023:br2.18:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn0H21J3:rvrA09:cvnDellInc.:ct23:cvr:skuSKU=NotProvided
pci:v00008086d00008D3Bsv00001028sd00000600bc07sc80i00
platform:serial8250
scsi:t-0x05
usb:v413CpA001d0000dc09dsc00dp00ic09isc00ip00in00
&lt;/pre&gt;

&lt;p&gt;The entries above are a selection of the complete set available on
a Dell PowerEdge R730 machine I have access to, to give an idea about
the various styles of hardware identifiers presented in the modalias
format.  When looking up relevant packages in a Debian Testing
installation on the same R730, I get this list of packages
proposed:&lt;/p&gt;

&lt;pre&gt;
% sudo isenkram-lookup
firmware-bnx2x
firmware-nvidia-graphics
firmware-qlogic
megactl
wsl
%
&lt;/pre&gt;

&lt;p&gt;The list consist of firmware packages requested by kernel modules,
as well packages with program to get the status from the RAID
controller and to maintain the LAN console.  When the edac-utils
package providing tools to check the ECC RAM status will enter testing
in a few days, it will also show up as a proposal from isenkram.  In
addition, once the mfiutil package we uploaded in October get past the
NEW processing, it will also propose a tool to configure the RAID
controller.&lt;/p&gt;

&lt;p&gt;Another example is the trusty old Lenovo Thinkpad X230, which have
hardware handled by several packages in the archive.  This is running
on Debian Stable:&lt;/p&gt;

&lt;pre&gt;
% isenkram-lookup 
beignet-opencl-icd
bluez
cheese
ethtool
firmware-iwlwifi
firmware-misc-nonfree
fprintd
fprintd-demo
gkrellm-thinkbat
hdapsd
libpam-fprintd
pidgin-blinklight
thinkfan
tlp
tp-smapi-dkms
tpb
%
&lt;/pre&gt;

&lt;p&gt;Here there proposal consist of software to handle the camera,
bluetooth, network card, wifi card, GPU, fan, fingerprint reader and
acceleration sensor on the machine.&lt;/p&gt;

&lt;p&gt;Here is the complete set of packages currently providing hardware
mapping via AppStream in Debian Unstable: air-quality-sensor,
alsa-firmware-loaders, antpm, array-info, avarice, avrdude,
bmusb-v4l2proxy, brltty, calibre, colorhug-client, concordance-common,
consolekit, dahdi-firmware-nonfree, dahdi-linux, edac-utils,
eegdev-plugins-free, ekeyd, elogind, firmware-amd-graphics,
firmware-ath9k-htc, firmware-atheros, firmware-b43-installer,
firmware-b43legacy-installer, firmware-bnx2, firmware-bnx2x,
firmware-brcm80211, firmware-carl9170, firmware-cavium,
firmware-intel-graphics, firmware-intel-misc, firmware-ipw2x00,
firmware-ivtv, firmware-iwlwifi, firmware-libertas,
firmware-linux-free, firmware-mediatek, firmware-misc-nonfree,
firmware-myricom, firmware-netronome, firmware-netxen,
firmware-nvidia-graphics, firmware-qcom-soc, firmware-qlogic,
firmware-realtek, firmware-ti-connectivity, fpga-icestorm, g810-led,
galileo, garmin-forerunner-tools, gkrellm-thinkbat, goldencheetah,
gpsman, gpstrans, gqrx-sdr, i8kutils, imsprog, ledger-wallets-udev,
libairspy0, libam7xxx0.1, libbladerf2, libgphoto2-6t64,
libhamlib-utils, libm2k0.9.0, libmirisdr4, libnxt, libopenxr1-monado,
libosmosdr0, librem5-flash-image, librtlsdr0, libticables2-8,
libx52pro0, libykpers-1-1, libyubikey-udev, limesuite,
linuxcnc-uspace, lomoco, madwimax, media-player-info, megactl, mixxx,
mkgmap, msi-keyboard, mu-editor, mustang-plug, nbc, nitrokey-app, nqc,
ola, openfpgaloader, openocd, openrazer-driver-dkms, pcmciautils,
pcscd, pidgin-blinklight, ponyprog, printer-driver-splix,
python-yubico-tools, python3-btchip, qlcplus, rosegarden, scdaemon,
sispmctl, solaar, spectools, sunxi-tools, t2n, thinkfan, tlp,
tp-smapi-dkms, trezor, tucnak, ubertooth, usbrelay, uuu, viking,
w1retap, wsl, xawtv, xinput-calibrator, xserver-xorg-input-wacom and
xtrx-dkms.&lt;/p&gt;

&lt;p&gt;In addition to these, there are several
&lt;a href=&quot;https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pere%40hungry.com&amp;tag=appstream-modalias&quot;&gt;with
patches pending in the Debian bug tracking system&lt;/a&gt;, and even more
where no-one wrote patches yet.  Good candiates for the latter are
packages
&lt;a href=&quot;https://udd.debian.org/lintian-tag.cgi?tag=appstream-metadata-missing-modalias-provide&quot;&gt;with
udev rules but no AppStream hardware information&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The isenkram system consist of two packages, isenkram-cli with the
command line tools, and isenkram with a GUI background process.  The
latter will listen for dbus events from udev emitted when new hardware
become available (like when inserting a USB dongle or discovering a
new bluetooth device), look up the modalias entry for this piece of
hardware in AppStream (and a hard coded list of mappings from isenkram
- currently working hard to move this list to AppStream), and pop up a
dialog proposing to install any not already installed packages
supporting this hardware.  It work very well today when inserting the
LEGO Mindstorms RCX, NXT and EV3 controllers. :) If you want to make
sure more hardware related packages get recommended, please help out
fixing the remaining packages in Debian to provide AppStream metadata
with hardware mappings.&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>What is the most supported MIME type in Debian in 2025?</title>
                <link>http://www.hungry.com/~pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2025_.html</link>
                <guid isPermaLink="true">http://www.hungry.com/~pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2025_.html</guid>
                <pubDate>Sat, 18 Jan 2025 10:30:00 +0100</pubDate>
                <description>&lt;p&gt;&lt;a href=&quot;http://www.hungry.com/~pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html&quot;&gt;Seven&lt;/a&gt;
and
&lt;a href=&quot;http://www.hungry.com/~pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;twelve&lt;/a&gt;
years ago, I measured what the most supported MIME type in Debian
was&lt;/a&gt;, first by analysing the desktop files in all packages in the
archive, then by analysing the DEP-11 AppStream data set.  I guess it
is time to repeat the measurement, only for unstable as last time:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;

&lt;pre&gt;
  count MIME type
  ----- -----------------------
     63 image/png
     63 image/jpeg
     57 image/tiff
     54 image/gif
     51 image/bmp
     50 audio/mpeg
     48 text/plain
     42 audio/x-mp3
     40 application/ogg
     39 audio/x-wav
     39 audio/x-flac
     36 audio/x-vorbis+ogg
     35 audio/x-mpeg
     34 audio/x-mpegurl
     34 audio/ogg
     33 application/x-ogg
     32 audio/mp4
     31 audio/x-scpls
     31 application/pdf
     29 audio/x-ms-wma
&lt;/pre&gt;

&lt;p&gt;The list was created like this using a sid chroot:&lt;/p&gt;

&lt;pre&gt;
cat /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz | \
  zcat | awk &#39;/^  - \S+\/\S+$/ {print $2 }&#39; | sort | \
  uniq -c | sort -nr | head -20
&lt;/pre&gt;

&lt;p&gt;It is nice to see that the same number of packages now support PNG
and JPEG.  Last time JPEG had more support than PNG.  Most of the MIME
types are known to me, but the &#39;audio/x-scpls&#39; one I have no idea what
represent, except it being an audio format.  To find the packages
claiming support for this format, the appstreamcli command from the
appstream package can be used:

&lt;pre&gt;
% appstreamcli what-provides mediatype audio/x-scpls | grep Package: | sort -u
Package: alsaplayer-common
Package: amarok
Package: audacious
Package: brasero
Package: celluloid
Package: clapper
Package: clementine
Package: cynthiune.app
Package: elisa
Package: gtranscribe
Package: kaffeine
Package: kmplayer
Package: kylin-burner
Package: lollypop
Package: mediaconch-gui
Package: mediainfo-gui
Package: mplayer-gui
Package: mpv
Package: mystiq
Package: parlatype
Package: parole
Package: pragha
Package: qmmp
Package: rhythmbox
Package: sayonara
Package: shotcut
Package: smplayer
Package: soundconverter
Package: strawberry
Package: syncplay
Package: vlc
%
&lt;/pre&gt;

&lt;p&gt;Look like several video and auto tools understand the format.
Similarly one can check out the number of packages supporting the STL
format commonly used for 3D printing:&lt;/p&gt;

&lt;pre&gt;
% appstreamcli what-provides mediatype model/stl | grep Package: | sort -u
Package: cura
Package: freecad
Package: open3d-viewer
%
&lt;/pre&gt;

&lt;p&gt;How strange the
&lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
&lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;prusa-slicer&lt;/a&gt;
packages do not support STL.  Perhaps just missing package metadata?
Luckily the amount of package metadata in Debian is getting better,
and hopefully this way of locating relevant packages for any file
format will be the preferred one soon.

&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>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 2025.  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=&quot;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>
        
        </channel>
</rss>