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">
4 <title>Petter Reinholdtsen
</title>
5 <description></description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
7 <atom:link href=
"http://people.skolelinux.org/pere/blog/index.rss" rel=
"self" type=
"application/rss+xml" />
10 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
11 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
13 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
14 <description><p
>Making packages for Debian requires quite a lot of attention to
15 details. And one of the details is the content of the
16 debian/copyright file, which should list all relevant licenses used by
17 the code in the package in question, preferably in
18 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
19 readable DEP5 format
</a
>.
</p
>
21 <p
>For large packages with lots of contributors it is hard to write
22 and update this file manually, and if you get some detail wrong, the
23 package is normally rejected by the ftpmasters. So getting it right
24 the first time around get the package into Debian faster, and save
25 both you and the ftpmasters some work.. Today, while trying to figure
26 out what was wrong with
27 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
28 zfsonlinux copyright file
</a
>, I decided to spend some time on
29 figuring out the options for doing this job automatically, or at least
30 semi-automatically.
</p
>
32 <p
>Lucikly, there are at least two tools available for generating the
33 file based on the code in the source package,
34 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
35 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
36 not sure which one of them came first, but both seem to be able to
37 create a sensible draft file. As far as I can tell, none of them can
38 be trusted to get the result just right, so the content need to be
39 polished a bit before the file is OK to upload. I found the debmake
41 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
42 blog posts from
2014</a
>.
44 <p
>To generate using debmake, use the -cc option:
47 debmake -cc
> debian/copyright
48 </pre
></p
>
50 <p
>Note there are some problems with python and non-ASCII names, so
51 this might not be the best option.
</p
>
53 <p
>The cme option is based on a config parsing library, and I found
55 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
56 blog post from
2015</a
>. To generate using cme, use the
'update
57 dpkg-copyright
' option:
60 cme update dpkg-copyright -quiet
61 </pre
></p
>
63 <p
>This will create or update debian/copyright. The cme tool seem to
64 handle UTF-
8 names better than debmake.
</p
>
66 <p
>When the copyright file is created, I would also like some help to
67 check if the file is correct. For this I found two good options,
68 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
69 to focus on license types and file matching, and is able to detect
70 ineffective blocks in the copyright file. The latter reports missing
71 copyright holders and years, but was confused by inconsistent license
72 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
73 fix all issues reported by them before uploading. But I do not know
74 if the tools and the ftpmasters agree on what is important to fix in a
75 copyright file, so the package might still be rejected.
</p
>
77 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
78 will read through the source and try to find all copyright statements.
79 It is not comparing the result to the content of debian/copyright, but
80 can be useful when verifying the content of the copyright file.
</p
>
82 <p
>Are you aware of better tools in Debian to create and update
83 debian/copyright file. Please let me know, or blog about it on
84 planet.debian.org.
</p
>
86 <p
>As usual, if you use Bitcoin and want to show your support of my
87 activities, please send Bitcoin donations to my address
88 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
90 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
91 on how to use licensecheck and cdbs to create a draft copyright file
94 licensecheck --copyright -r `find * -type f` | \
95 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
96 </pre
></p
>
98 <p
>He mentioned that he normally check the generated file into the
99 version control system to make it easier to discover license and
100 copyright changes in the upstream source. I will try to do the same
101 with my packages in the future.
</p
>
106 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
107 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
108 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
109 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
110 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
111 is taking shape in Debian, and one provided feature is a very
112 convenient way to tell you which package to install to make a given
113 firmware file available when the kernel is looking for it. This can
114 be done using apt-file too, but that is for someone else to blog
117 <p
>Here is a small recipe to find the package with a given firmware
118 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
119 picked from the set of firmware announced using appstream in Debian
120 unstable. In general you would be looking for the firmware requested
121 by the kernel during kernel module loading. To find the package
122 providing the example file, do like this:
</p
>
124 <blockquote
><pre
>
125 % apt install appstream
129 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
130 awk
'/Package:/ {print $
2}
'
133 </pre
></blockquote
>
135 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
136 appstream wiki
</a
> page to learn how to embed the package metadata in
137 a way appstream can use.
</p
>
139 <p
>This same approach can be used to find any package supporting a
140 given MIME type. This is very useful when you get a file you do not
141 know how to handle. First find the mime type using
<tt
>file
142 --mime-type
</tt
>, and next look up the package providing support for
143 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
144 and you can find all packages handling this type like this:
</p
>
146 <blockquote
><pre
>
147 % apt install appstream
151 % appstreamcli what-provides mimetype image/svg+xml | \
152 awk
'/Package:/ {print $
2}
'
174 </pre
></blockquote
>
176 <p
>I believe the MIME types are fetched from the desktop file for
177 packages providing appstream metadata.
</p
>
182 <title>Creepy, visualise geotagged social media information - nice free software
</title>
183 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
184 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
185 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
186 <description><p
>Most people seem not to realise that every time they walk around
187 with the computerised radio beacon known as a mobile phone their
188 position is tracked by the phone company and often stored for a long
189 time (like every time a SMS is received or sent). And if their
190 computerised radio beacon is capable of running programs (often called
191 mobile apps) downloaded from the Internet, these programs are often
192 also capable of tracking their location (if the app requested access
193 during installation). And when these programs send out information to
194 central collection points, the location is often included, unless
195 extra care is taken to not send the location. The provided
196 information is used by several entities, for good and bad (what is
197 good and bad, depend on your point of view). What is certain, is that
198 the private sphere and the right to free movement is challenged and
199 perhaps even eradicated for those announcing their location this way,
200 when they share their whereabouts with private and public
203 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
205 <p
>The phone company logs provide a register of locations to check out
206 when one want to figure out what the tracked person was doing. It is
207 unavailable for most of us, but provided to selected government
208 officials, company staff, those illegally buying information from
209 unfaithful servants and crackers stealing the information. But the
210 public information can be collected and analysed, and a free software
211 tool to do so is called
212 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
213 discovered it when I read
214 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
215 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
216 November
2014, and decided to check if it was available in Debian.
217 The python program was in Debian, but
218 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
219 Debian
</a
> was completely broken and practically unmaintained. I
220 uploaded a new version which did not work quite right, but did not
221 have time to fix it then. This Christmas I decided to finally try to
222 get Creepy operational in Debian. Now a fixed version is available in
223 Debian unstable and testing, and almost all Debian specific patches
225 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
227 <p
>The Creepy program visualises geolocation information fetched from
228 Twitter, Instagram, Flickr and Google+, and allow one to get a
229 complete picture of every social media message posted recently in a
230 given area, or track the movement of a given individual across all
231 these services. Earlier it was possible to use the search API of at
232 least some of these services without identifying oneself, but these
233 days it is impossible. This mean that to use Creepy, you need to
234 configure it to log in as yourself on these services, and provide
235 information to them about your search interests. This should be taken
236 into account when using Creepy, as it will also share information
237 about yourself with the services.
</p
>
239 <p
>The picture above show the twitter messages sent from (or at least
240 geotagged with a position from) the city centre of Oslo, the capital
241 of Norway. One useful way to use Creepy is to first look at
242 information tagged with an area of interest, and next look at all the
243 information provided by one or more individuals who was in the area.
244 I tested it by checking out which celebrity provide their location in
245 twitter messages by checkout out who sent twitter messages near a
246 Norwegian TV station, and next could track their position over time,
247 making it possible to locate their home and work place, among other
248 things. A similar technique have been
249 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
250 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
251 tool to discover lying governments, and a useful tool to help people
252 understand the value of the private information they provide to the
255 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
256 it depend on several python modules currently missing in Jessie (at
257 least python-instagram, python-flickrapi and
258 python-requests-toolbelt).
</p
>
260 <p
>(I have uploaded
261 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
262 screenshots.debian.net
</a
> and licensed it under the same terms as the
263 Creepy program in Debian.)
</p
>
268 <title>Always download Debian packages using Tor - the simple recipe
</title>
269 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
270 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
271 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
272 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
273 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
274 that those listening on the Internet lines would have good reason to
275 believe a computer have a given security hole
</a
> if it download a
276 security fix from a Debian mirror. This is a good reason to always
277 use encrypted connections to the Debian mirror, to make sure those
278 listening do not know which IP address to attack. In August, Richard
279 Hartmann observed that encryption was not enough, when it was possible
280 to interfere download size to security patches or the fact that
281 download took place shortly after a security fix was released, and
282 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
283 to always use Tor to download packages from the Debian mirror
</a
>. He
284 was not the first to propose this, as the
285 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
286 package by Tim Retout already existed to make it easy to convince apt
287 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
288 aware of that package when I read the blog post from Richard.
</p
>
290 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
291 sysadmins, and he set up a Tor hidden service on one of the central
292 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
293 it possible to download packages directly between two tor nodes,
294 making sure the network traffic always were encrypted.
</p
>
296 <p
>Here is a short recipe for enabling this on your machine, by
297 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
298 urls with tor+http and tor+https, and using the hidden service instead
299 of the official Debian mirror site. I recommend installing
300 <tt
>etckeeper
</tt
> before you start to have a history of the changes
301 done in /etc/.
</p
>
303 <blockquote
><pre
>
304 apt install apt-transport-tor
305 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
306 sed -i
's% http% tor+http%
' /etc/apt/sources.list
307 </pre
></blockquote
>
309 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
310 the sed commands for these too. The sed command is assuming your are
311 using the ftp.debian.org Debian mirror. Adjust the command (or just
312 edit the file manually) to match your mirror.
</p
>
314 <p
>This work in Debian Jessie and later. Note that tools like
315 <tt
>apt-file
</tt
> only recently started using the apt transport
316 system, and do not work with these tor+http URLs. For
317 <tt
>apt-file
</tt
> you need the version currently in experimental,
318 which need a recent apt version currently only in unstable. So if you
319 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
321 <p
>Another advantage from this change is that your machine will start
322 using Tor regularly and at fairly random intervals (every time you
323 update the package lists or upgrade or install a new package), thus
324 masking other Tor traffic done from the same machine. Using Tor will
325 become normal for the machine in question.
</p
>
327 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
328 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
329 enabled. It would be great if it was the default on any Debian
335 <title>Nedlasting fra NRK, som Matroska med undertekster
</title>
336 <link>http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html
</link>
337 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html
</guid>
338 <pubDate>Sat,
2 Jan
2016 13:
50:
00 +
0100</pubDate>
339 <description><p
>Det kommer stadig nye løsninger for å ta lagre unna innslag fra NRK
340 for å se på det senere. For en stund tilbake kom jeg over et script
341 nrkopptak laget av Ingvar Hagelund. Han fjernet riktignok sitt script
342 etter forespørsel fra Erik Bolstad i NRK, men noen tok heldigvis og
343 gjorde det
<a href=
"https://github.com/liangqi/nrkopptak
">tilgjengelig
344 via github
</a
>.
</p
>
346 <p
>Scriptet kan lagre som MPEG4 eller Matroska, og bake inn
347 undertekster i fila på et vis som blant annet VLC forstår. For å
348 bruke scriptet, kopier ned git-arkivet og kjør
</p
>
351 nrkopptak/bin/nrk-opptak k
<ahref=
"https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-
1/episode-
1">https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-
1/episode-
1</a
>
352 </pre
></p
>
354 <p
>URL-eksemplet er dagens toppsak på tv.nrk.no. Argument
'k
' ber
355 scriptet laste ned og lagre som Matroska. Det finnes en rekke andre
356 muligheter for valg av kvalitet og format.
</p
>
358 <p
>Jeg foretrekker dette scriptet fremfor youtube-dl, som
359 <a href=
"http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html
">
360 nevnt i
2014 støtter NRK
</a
> og en rekke andre videokilder, på grunn
361 av at nrkopptak samler undertekster og video i en enkelt fil, hvilket
362 gjør håndtering enklere på disk.
</p
>
367 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
368 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
369 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
370 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
371 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
372 call the car license plate numbers in those days. I would write the
373 numbers down in my little book and compare notes with the other kids
374 to see how many region codes we had seen and if we had seen some
375 exotic or special region codes and numbers. It was a fun game to pass
376 time, as we kids have plenty of it.
</p
>
378 <p
>A few days I came across
379 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
380 project
</a
>, a free software project to automatically discover and
381 report license plates in images and video streams, and provide the
382 "car numbers
" in a machine readable format. I
've been looking for
383 such system for a while now, because I believe it is a bad idea that the
384 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
385 number plate recognition
</a
> tool only is available in the hands of
386 the powerful, and want it to be available also for the powerless to
387 even the score when it comes to surveillance and sousveillance. I
388 discovered the developer
389 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
390 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
391 help him get it into shape to get the package uploaded into the Debian
394 <p
>Today we finally managed to get the package into shape and uploaded
395 it into Debian, where it currently
396 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
397 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
399 <p
>I guess you are wondering why on earth such tool would be useful
400 for the common folks, ie those not running a large government
401 surveillance system? Well, I plan to put it in a computer on my bike
402 and in my car, tracking the cars nearby and allowing me to be notified
403 when number plates on my watch list are discovered. Another use case
404 was suggested by a friend of mine, who wanted to set it up at his home
405 to open the car port automatically when it discovered the plate on his
406 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
407 capable of placing his license plate number of a piece of cardboard to
408 open his car port, men replied that it was always unlocked anyway. I
409 guess for such use case it make sense. I am sure there are other use
410 cases too, for those with imagination and a vision.
</p
>
412 <p
>If you want to build your own version of the Debian package, check
413 out the upstream git source and symlink ./distros/debian to ./debian/
414 before running
"debuild
" to build the source. Or wait a bit until the
415 package show up in unstable.
</p
>
420 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
421 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
422 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
423 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
424 <description><p
>Around three years ago, I created
425 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
426 system
</a
> to get a more practical solution in Debian for handing
427 hardware related packages. A GUI system in the isenkram package will
428 present a pop-up dialog when some hardware dongle supported by
429 relevant packages in Debian is inserted into the machine. The same
430 lookup mechanism to detect packages is available as command line
431 tools in the isenkram-cli package. In addition to mapping hardware,
432 it will also map kernel firmware files to packages and make it easy to
433 install needed firmware packages automatically. The key for this
434 system to work is a good way to map hardware to packages, in other
435 words, allow packages to announce what hardware they will work
438 <p
>I started by providing data files in the isenkram source, and
439 adding code to download the latest version of these data files at run
440 time, to ensure every user had the most up to date mapping available.
441 I also added support for storing the mapping in the Packages file in
442 the apt repositories, but did not push this approach because while I
443 was trying to figure out how to best store hardware/package mappings,
444 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
445 appstream system
</a
> was announced. I got in touch and suggested to
446 add the hardware mapping into that data set to be able to use
447 appstream as a data source, and this was accepted at least for the
448 Debian version of appstream.
</p
>
450 <p
>A few days ago using appstream in Debian for this became possible,
451 and today I uploaded a new version
0.20 of isenkram adding support for
452 appstream as a data source for mapping hardware to packages. The only
453 package so far using appstream to announce its hardware support is my
454 pymissile package. I got help from Matthias Klumpp with figuring out
455 how do add the required
456 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
457 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
458 this content:
</p
>
460 <blockquote
><pre
>
461 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
462 &lt;component
&gt;
463 &lt;id
&gt;pymissile
&lt;/id
&gt;
464 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
465 &lt;name
&gt;pymissile
&lt;/name
&gt;
466 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
467 &lt;description
&gt;
469 Pymissile provides a curses interface to control an original
470 Marks and Spencer / Striker USB Missile Launcher, as well as a
471 motion control script to allow a webcamera to control the
474 &lt;/description
&gt;
475 &lt;provides
&gt;
476 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
477 &lt;/provides
&gt;
478 &lt;/component
&gt;
479 </pre
></blockquote
>
481 <p
>The key for isenkram is the component/provides/modalias value,
482 which is a glob style match rule for hardware specific strings
483 (modalias strings) provided by the Linux kernel. In this case, it
484 will map to all USB devices with vendor code
1130 and product code
487 <p
>Note, it is important that the license of all the metadata files
488 are compatible to have permissions to aggregate them into archive wide
489 appstream files. Matthias suggested to use MIT or BSD licenses for
490 these files. A challenge is figuring out a good id for the data, as
491 it is supposed to be globally unique and shared across distributions
492 (in other words, best to coordinate with upstream what to use). But
493 it can be changed later or, so we went with the package name as
494 upstream for this project is dormant.
</p
>
496 <p
>To get the metadata file installed in the correct location for the
497 mirror update scripts to pick it up and include its content the
498 appstream data source, the file must be installed in the binary
499 package under /usr/share/appdata/. I did this by adding the following
500 line to debian/pymissile.install:
</p
>
502 <blockquote
><pre
>
503 debian/pymissile.metainfo.xml usr/share/appdata
504 </pre
></blockquote
>
506 <p
>With that in place, the command line tool isenkram-lookup will list
507 all packages useful on the current computer automatically, and the GUI
508 pop-up handler will propose to install the package not already
509 installed if a hardware dongle is inserted into the machine in
512 <p
>Details of the modalias field in appstream is available from the
513 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
515 <p
>To locate the modalias values of all hardware present in a machine,
516 try running this command on the command line:
</p
>
518 <blockquote
><pre
>
519 cat $(find /sys/devices/|grep modalias)
520 </pre
></blockquote
>
522 <p
>To learn more about the isenkram system, please check out
523 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
524 blog posts tagged isenkram
</a
>.
</p
>
529 <title>Bokhandeldistribusjon av boken Fri kultur av Lawrence Lessig
</title>
530 <link>http://people.skolelinux.org/pere/blog/Bokhandeldistribusjon_av_boken_Fri_kultur_av_Lawrence_Lessig.html
</link>
531 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bokhandeldistribusjon_av_boken_Fri_kultur_av_Lawrence_Lessig.html
</guid>
532 <pubDate>Mon,
14 Dec
2015 12:
10:
00 +
0100</pubDate>
533 <description><p
><strong
>Besøk
534 <a href=
"https://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">lulu.com
</a
>
536 <a href=
"https://www.amazon.com/Fri-kultur-Norwegian-Lawrence-Lessig/dp/
8269018236/
">Amazon
</a
>
537 for å kjøpe boken på papir, eller last ned ebook som
538 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.pdf
">PDF
</a
>,
539 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.epub
">ePub
</a
>
541 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.mobi
">MOBI
</a
>
543 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig/
">github
</a
>.
</strong
></p
>
545 <p
>Jeg ble gledelig overrasket i dag da jeg oppdaget at boken jeg har
547 <a href=
"https://www.amazon.com/Fri-kultur-Norwegian-Lawrence-Lessig/dp/
8269018236/
">hadde
548 dukket opp i Amazon
</a
>. Jeg hadde trodd det skulle ta lenger tid, da
549 jeg fikk beskjed om at det skulle ta seks til åtte uker.
550 Amazonoppføringen er et resultat av at jeg for noen uker siden
551 diskuterte prissetting og håndtering av profitt med forfatteren. Det
552 måtte avklares da bruksvilkårene til boken har krav om
553 ikke-kommersiell bruk. Vi ble enige om at overskuddet fra salg av
554 boken skal sendes til
555 <a href=
"https://creativecommons.org/
">Creative Commons-stiftelsen
</a
>.
556 Med det på plass kunne jeg be
557 <a href=
"https://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">lulu.com
</a
>
558 om å gi boken «utvidet» distribusjon. Årsaken til at
559 bokhandeldistribusjon var litt utfordrende er at bokhandlere krever
560 mulighet for profitt på bøkene de selger (selvfølgelig), og dermed
561 måtte de få lov til å selge til høyere pris enn lulu.com. I tillegg
562 er det krav om samme pris på lulu.com og i bokhandlene, dermed blir
563 prisen økt også hos lulu.com. Hva skulle jeg gjøre med den profitten
564 uten å bryte med klausulen om ikkekommersiell? Løsningen var å gi
565 bort profitten til CC-stiftelsen. Prisen på boken ble nesten
566 tredoblet, til $
19.99 (ca.
160,-) pluss frakt, men synligheten øker
567 betraktelig når den kan finnes i katalogene til store nettbokhandlere.
568 Det betyr at hvis du allerede har kjøpt boken har du fått den veldig
569 billig, og kjøper du den nå, får du den fortsatt billig samt donerer i
570 tillegg noen tiere til fremme av Creative Commons.
</p
>
572 <p
>Mens jeg var i gang med å titte etter informasjon om boken
573 oppdaget jeg at den også var dukket opp på
574 <a href=
"https://books.google.no/books?id=uKUGCwAAQBAJ
">Google
575 Books
</a
>, der en kan lese den på web. PDF-utgaven har ennå ikke
576 dukket opp hos
<a href=
"https://www.nb.no/
">Nasjonalbiblioteket
</a
>,
577 men det regner jeg med kommer på plass i løpet av noen uker. Boken er
578 heller ikke dukket opp hos
579 <a href=
"https://www.barnesandnoble.com/
">Barnes
& Noble
</a
> ennå, men
580 jeg antar det bare er et tidsspørsmål før dette er på plass.
</p
>
582 <p
>Boken er dessverre ikke tilgjengelig fra norske bokhandlere, og
583 kommer neppe til å bli det med det første. Årsaken er at for å få det
584 til måtte jeg personlig håndtere bestilling av bøker, hvilket jeg ikke
585 er interessert i å bruke tid på. Jeg kunne betalt ca
2000,- til
586 <a href=
"http://www.bokbasen.no/
">den norske bokbasen
</a
>, en felles
587 database over bøker tilgjengelig for norske bokhandlere, for å få en
588 oppføring der, men da måtte jeg tatt imot bestillinger på epost og
589 sendt ut bøker selv. Det ville krevd at jeg var klar til å
590 sende ut bøker på kort varsel, dvs. holdt meg med ekstra bøker,
591 konvolutter og frimerker. Bokbasen har visst ikke opplegg for å be
592 bokhandlene bestille direkte via web, så jeg droppet oppføring der.
593 Jeg har spurt Haugen bok og Tronsmo direkte på epost om de er
594 interessert i å ta inn boken i sin bestillingskatalog, men ikke fått
595 svar, så jeg antar de ikke er interessert. Derimot har jeg fått en
596 hyggelig henvendelse fra Biblioteksentralen som fortalte at de har
597 lagt den inn i sin database slik at deres bibliotekskunder enkelt kan
598 bestille den via dem.
</p
>
600 <p
>Boken er i følge
601 <a href=
"http://bibsys-almaprimo.hosted.exlibrisgroup.com/primo_library/libweb/action/display.do?tabs=detailsTab
&ct=display
&fn=search
&doc=BIBSYS_ILS71518423420002201
&indx=
1&recIds=BIBSYS_ILS71518423420002201
&recIdxs=
0&elementId=
0&renderMode=poppedOut
&displayMode=full
&frbrVersion=
&dscnt=
0&tab=library_catalogue
&dstmp=
1448543801124&vl(freeText0)=fri%
20kultur
&vid=UBO
&mode=Basic
">Bibsys/Oria
</a
>
603 <a href=
"https://www.deich.folkebibl.no/cgi-bin/websok?tnr=
1819617">Deichmanske
</a
>
604 tilgjengelig fra flere biblioteker allerede, og alle eksemplarer er
605 visst allerede utlånt med ventetid. Det synes jeg er veldig gledelig
606 å se. Jeg håper mange kommer til å lese boken. Jeg tror den er
607 spesielt egnet for foreldre og bekjente av oss nerder for å forklare
608 hva slags problemer vi ser med dagens opphavsrettsregime.
</p
>
613 <title>The GNU General Public License is not magic pixie dust
</title>
614 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
615 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
616 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
617 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
618 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
619 GPL is not magic pixie dust
</a
>" explain the importance of making sure
620 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
621 I quote the blog post from Paul in full here with his permission:
<p
>
625 <p
><a href=
"https://sfconservancy.org/supporter/
"><img src=
"https://sfconservancy.org/img/supporter-badge.png
" width=
"194" height=
"90" alt=
"Become a Software Freedom Conservancy Supporter!
" align=
"right
" border=
"0" /
></a
></p
>
628 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
630 The first step is to choose a
631 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
634 The next step is, when someone fails to follow that copyleft license,
635 <b
>it must be enforced
</b
><br/
>
637 and its a simple fact of our modern society that such type of
640 is incredibly expensive to do and incredibly difficult to do.
643 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
644 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
645 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
646 0x57</a
></small
></p
>
648 <p
>As the Debian Website
649 <a href=
"https://bugs.debian.org/
794116">used
</a
>
650 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
651 imply, public domain and permissively licensed software can lead to
652 the production of more proprietary software as people discover useful
653 software, extend it and or incorporate it into their hardware or
654 software products. Copyleft licenses such as the GNU GPL were created
655 to close off this avenue to the production of proprietary software but
656 such licenses are not enough. With the ongoing adoption of Free
657 Software by individuals and groups, inevitably the community
's
658 expectations of license compliance are violated, usually out of
659 ignorance of the way Free Software works, but not always. As Karen
660 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
661 Freedom
">FaiF
</a
>
662 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
663 copyleft is nothing if no-one is willing and able to stand up in court
664 to protect it. The reality of today
's world is that legal
665 representation is expensive, difficult and time consuming. With
666 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
667 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
668 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
669 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
670 of the Linux project, Debian and other groups against GPL violations.
671 In March the SFC supported a
672 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
673 by Christoph Hellwig
</a
> against VMware for refusing to
674 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
675 with the GPL
</a
> in relation to their use of parts of the Linux
676 kernel. Since then two of their sponsors pulled corporate funding and
678 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
679 or cancelled their talks
</a
>. As a result they have decided to rely
680 less on corporate funding and more on the broad community of
681 individuals who support Free Software and copyleft. So the SFC has
682 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
683 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
684 a community of folks who stand up for copyleft and the GPL by
685 supporting their work on promoting and supporting copyleft and Free
688 <p
>If you support Free Software,
689 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
690 what the SFC do, agree with their
691 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
692 principles
</a
>, are happy about their
693 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
694 work on a project that is an SFC
695 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
696 just want to stand up for copyleft, please join
697 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
698 Allan Webber
</a
>,
699 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
701 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
702 Bacon
</a
>, myself and
703 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
705 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
706 next week your donation will be
707 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
708 by an anonymous donor. Please also consider asking your employer to
709 match your donation or become a sponsor of SFC. Don
't forget to
710 spread the word about your support for SFC via email, your blog and or
711 social media accounts.
</p
>
715 <p
>I agree with Paul on this topic and just signed up as a Supporter
716 of Software Freedom Conservancy myself. Perhaps you should be a
717 supporter too?
</p
>
722 <title>PGP key transition statement for key EE4E02F9
</title>
723 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
724 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
725 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
726 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
727 set it up properly. I wanted to generate it offline and have it
728 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
729 smart card
</a
> for daily use, and learning how to do it and finding
730 time to sit down with an offline machine almost took forever. But
731 finally I
've been able to complete the process, and have now moved
732 from my old GPG key to a new GPG key. See
733 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
734 full transition statement, signed with both my old and new key
</a
> for
735 the details. This is my new key:
</p
>
738 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
739 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
740 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
741 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
742 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
743 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
744 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
747 <p
>The key can be downloaded from the OpenPGP key servers, signed by
748 my old key.
</p
>
750 <p
>If you signed my old key
751 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
752 I
'd very much appreciate a signature on my new key, details and
753 instructions in the transition statement. I m happy to reciprocate if
754 you have a similarly signed transition statement to present.
</p
>