blog/index.rss

   1 <?xml version="1.0" encoding="utf-8"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
   3         <channel>
   4                 <title>Petter Reinholdtsen</title>
   5                 <description></description>
   6                 <link>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" />
   8
   9         <item>
  10                 <title>Økt overvåkning applauderes igjen av Arbeiderpartiet, Høyre og Fremskrittspartiet</title>
  11                 <link>http://people.skolelinux.org/pere/blog/_kt_overv_kning_applauderes_igjen_av_Arbeiderpartiet__H_yre_og_Fremskrittspartiet.html</link>
  12                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/_kt_overv_kning_applauderes_igjen_av_Arbeiderpartiet__H_yre_og_Fremskrittspartiet.html</guid>
  13                 <pubDate>Mon, 4 Feb 2013 00:30:00 +0100</pubDate>
  14                 <description>&lt;p&gt;Jeg ser med gru at Arbeiderpartiet, Høyre og Fremskrittspartiet
  15 &lt;a href=&quot;http://www.aftenposten.no/nyheter/iriks/Positive-til-mer-smuglerovervaking-7110348.html&quot;&gt;applauderer
  16 tollvesenets forslag&lt;/a&gt; om å øke overvåkningen i Norge nok et hakk.
  17 Det er ikke så rart, da de som uttaler seg jo også har støttet
  18 innføringen av datalagringsdirektivet eller i hvert fall ikke veldig
  19 aktivt har motarbeidet det.  Innføringen av datalagringsdirektivet er
  20 en lovendring som innebærer brev og besøkskontroll for hele
  21 befolkningen.&lt;/p&gt;
  22
  23 &lt;p&gt;&lt;a href=&quot;http://www.stortinget.no/no/Saker-og-publikasjoner/Saker/Sak/?p=48717&quot;&gt;Datalagringsdirektivet&lt;/a&gt;
  24 har vært oppe til votering i stortinget tre ganger så langt.  Det ble
  25 &lt;a href=&quot;http://svartelisten.org/&quot;&gt;vedtatt første gang 2011-04-04&lt;/a&gt;
  26 og
  27 &lt;a href=&quot;https://github.com/holderdeord/hdo-folketingparser/blob/master/data/votering-2011-04-11.xml&quot;&gt;andre
  28 gang 2011-04-11&lt;/a&gt; (lovendringer voteres to ganger), og forslag om å
  29 stoppe loven ble
  30 &lt;a href=&quot;http://www.stortinget.no/no/Saker-og-publikasjoner/Saker/Sak/Voteringsoversikt/?p=53844&amp;dnid=1&quot;&gt;nedstemt
  31 2012-12-06&lt;/a&gt; (se også
  32 &lt;a href=&quot;http://beta.holderdeord.no/issues/innfore-datalagringsdirektivet&quot;&gt;oversikt fra Holder De
  33 Ord&lt;/a&gt;).&lt;/p&gt;
  34
  35 &lt;p&gt;Jan Bøhler i Arbeiderpartiet stemte for å innføre
  36 datalagringsdirektivet i lovverket i første votering, var ikke
  37 tilstede i andre votering og støttet loven i tredje votering.  André
  38 Oktay Dahl i Høyre var ikke til stede i første og andre votering men
  39 støttet loven i tredje votering.  Ulf Leirstein i Fremskrittspartiet
  40 stemte mot loven i første votering men var ikke til stede i andre og
  41 tredje votering.&lt;/p&gt;
  42
  43 &lt;p&gt;Hvis du lurer på hva som er problemet med datalagringsdirektivet,
  44 anbefaler jeg å lese &lt;a href=&quot;http://www.uhuru.biz/?cat=84&quot;&gt;artiklene
  45 fra Jon Wessel-Aas&lt;/a&gt; om temaet, samt informasjon fra foreningen
  46 &lt;a href=&quot;http://www.digitaltpersonvern.no/&quot;&gt;Digitalt
  47 Personvern&lt;/a&gt;.&lt;/p&gt;
  48
  49 &lt;p&gt;&lt;strong&gt;Oppdatering 2013-03-09&lt;/strong&gt;: Endret lenke til Holder De
  50 Ord, som har byttet mange lenker i forbindelse med import av
  51 voteringsdata for 2010-2011.&lt;/p&gt;
  52 </description>
  53         </item>
  54
  55         <item>
  56                 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
  57                 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
  58                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
  59                 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
  60                 <description>&lt;p&gt;My
  61 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html&quot;&gt;last
  62 bitcoin related blog post&lt;/a&gt; mentioned that the new
  63 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
  64 Debian was waiting in NEW.  It was accepted by the Debian ftp-masters
  65 2013-01-19, and have been available in unstable since then.  It was
  66 automatically copied to Ubuntu, and is available in their Raring
  67 version too.&lt;/p&gt;
  68
  69 &lt;p&gt;But there is a strange problem with the build that block this new
  70 version from being available on the i386 and kfreebsd-i386
  71 architectures.  For some strange reason, the autobuilders in Debian
  72 for these architectures fail to run the test suite on these
  73 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
  74 We are so far unable to reproduce it when building it manually, and
  75 no-one have been able to propose a fix.  If you got an idea what is
  76 failing, please let us know via the BTS.&lt;/p&gt;
  77
  78 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
  79 I often run low on disk space, is the fact that the client will exit
  80 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
  81 #696715&lt;/a&gt;).  So make sure you have enough disk space when you run
  82 it. :)&lt;/p&gt;
  83
  84 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
  85 activities, please send Bitcoin donations to my address
  86 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
  87 </description>
  88         </item>
  89
  90         <item>
  91                 <title>Welcome to the world, Isenkram!</title>
  92                 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
  93                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
  94                 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
  95                 <description>&lt;p&gt;Yesterday, I
  96 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
  97 for testers&lt;/a&gt; for my prototype for making Debian better at handling
  98 pluggable hardware devices, which I
  99 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
 100 out to create&lt;/a&gt; earlier this month.  Several valuable testers showed
 101 up, and caused me to really want to to open up the development to more
 102 people.  But before I did this, I want to come up with a sensible name
 103 for this project.  Today I finally decided on a new name, and I have
 104 renamed the project from hw-support-handler to this new name.  In the
 105 process, I moved the source to git and made it available as a
 106 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
 107 repository in Debian.  The new name?  It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
 108 To fetch and build the latest version of the source, use&lt;/p&gt;
 109
 110 &lt;pre&gt;
 111 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
 112 cd isenkram &amp;&amp; git-buildpackage -us -uc
 113 &lt;/pre&gt;
 114
 115 &lt;p&gt;I have not yet adjusted all files to use the new name yet.  If you
 116 want to hack on the source or improve the package, please go ahead.
 117 But please talk to me first on IRC or via email before you do major
 118 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
 119
 120 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
 121 stuff, typically meaning tools, nails, screws, etc.  Typical hardware
 122 stuff, in other words.  I&#39;ve been told it is the Norwegian variant of
 123 the German word eisenkram, for those that are familiar with that
 124 word.&lt;/p&gt;
 125
 126 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
 127 instructions, to avoid confusing people with an error from the signing
 128 process.&lt;/p&gt;
 129
 130 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
 131 clone argument to avoid the need for authentication.&lt;/p&gt;
 132 </description>
 133         </item>
 134
 135         <item>
 136                 <title>First prototype ready making hardware easier to use in Debian</title>
 137                 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
 138                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
 139                 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
 140                 <description>&lt;p&gt;Early this month I set out to try to
 141 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
 142 the Debian support for pluggable hardware devices&lt;/a&gt;.  Now my
 143 prototype is working, and it is ready for a larger audience.  To test
 144 it, fetch the
 145 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
 146 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
 147 package.  You might have to log out and in again activate the
 148 autostart script.&lt;/p&gt;
 149
 150 &lt;p&gt;The design is simple:&lt;/p&gt;
 151
 152 &lt;ul&gt;
 153
 154 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
 155 hw-support-handlerd to start when the user log in.&lt;/li&gt;
 156
 157 &lt;li&gt;This program listen for kernel events about new hardware (directly
 158 from the kernel like udev does), not using HAL dbus events as I
 159 initially did.&lt;/li&gt;
 160
 161 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
 162 the APT database, a database
 163 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
 164 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
 165
 166 &lt;li&gt;If a package is mapped to the hardware in question, the package
 167 isn&#39;t installed yet and this is the first time the hardware was
 168 plugged in, show a desktop notification suggesting to install the
 169 package or packages.&lt;/li&gt;
 170
 171 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
 172 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
 173
 174 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
 175 package while showing progress information in a window.&lt;/li&gt;
 176
 177 &lt;/ul&gt;
 178
 179 &lt;p&gt;I still need to come up with a better name for the system.  Here
 180 are some screen shots showing the prototype in action.  First the
 181 notification, then the password request, and finally the request to
 182 approve all the dependencies.  Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
 183
 184 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
 185 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
 186 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
 187 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
 188 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-5-installing-details.png&quot; width=&quot;70%&quot;&gt;&lt;/p&gt;
 189
 190 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
 191 is already useful.  The database of hardware to package mappings also
 192 need more work.  It is currently compatible with the Ubuntu way of
 193 storing such information in the package control file, but could be
 194 changed to use other formats instead or in addition to the current
 195 method.  I&#39;ve dropped the use of discover for this mapping, as the
 196 modalias approach is more flexible and easier to use on Linux as long
 197 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
 198
 199 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
 200 here is the command required to check out and build the source: Use
 201 &#39;&lt;tt&gt;svn checkout
 202 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
 203 hw-support-handler; debuild&lt;/tt&gt;&#39;.  If you lack debuild, install the
 204 devscripts package.&lt;/p&gt;
 205
 206 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
 207 renamed to Isenkram and the source moved from the Debian Edu
 208 subversion repository to a Debian collab-maint git repository.  See
 209 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
 210 instructions&lt;/a&gt; for details.&lt;/p&gt;
 211 </description>
 212         </item>
 213
 214         <item>
 215                 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
 216                 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
 217                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
 218                 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
 219                 <description>&lt;p&gt;This Christmas my trusty old laptop died.  It died quietly and
 220 suddenly in bed.  With a quiet whimper, it went completely quiet and
 221 black.  The power button was no longer able to turn it on.  It was a
 222 IBM Thinkpad X41, and the best laptop I ever had.  Better than both
 223 Thinkpads X30, X31, X40, X60, X61 and X61S.  Far better than the
 224 Compaq I had before that.  Now I need to find a replacement.  To keep
 225 going during Christmas, I moved the one year old SSD disk to my old
 226 X40 where it fitted (only one I had left that could use it), but it is
 227 not a durable solution.
 228
 229 &lt;p&gt;My laptop needs are fairly modest.  This is my wishlist from when I
 230 got a new one more than 10 years ago.  It still holds true.:)&lt;/p&gt;
 231
 232 &lt;ul&gt;
 233
 234 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
 235   than A4).&lt;/li&gt;
 236 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
 237 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
 238 &lt;li&gt;Long battery life time.  Preferable a week.&lt;/li&gt;
 239 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
 240 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
 241 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
 242 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
 243 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
 244 size).&lt;/li&gt;
 245 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
 246   X.org packages.&lt;/li&gt;
 247 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
 248   the time).
 249
 250 &lt;/ul&gt;
 251
 252 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
 253 list.  The reason is simply that the specifications on laptops the
 254 last 10-15 years have been sufficient for my needs, and I have to look
 255 at other features to choose my laptop.  But are there still made as
 256 robust laptops as my X41?  The Thinkpad X60/X61 proved to be less
 257 robust, and Thinkpads seem to be heading in the wrong direction since
 258 Lenovo took over.  But I&#39;ve been told that X220 and X1 Carbon might
 259 still be useful.&lt;/p&gt;
 260
 261 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
 262 external keyboard?  I&#39;ll have to check the
 263 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
 264 well-supported laptops, or perhaps just buy one preinstalled from one
 265 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
 266 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
 267 </description>
 268         </item>
 269
 270         <item>
 271                 <title>How to find a browser plugin supporting a given MIME type</title>
 272                 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
 273                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
 274                 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
 275                 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
 276 install to get support for a given MIME type.  Thanks to
 277 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
 278 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
 279 Unfortunately, not very many packages provide the needed meta
 280 information, Anyway, here is a small script to look up all browser
 281 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
 282
 283 &lt;pre&gt;
 284 #!/usr/bin/python
 285 import sys
 286 import apt
 287 def pkgs_handling_mimetype(mimetype):
 288     cache = apt.Cache()
 289     cache.open(None)
 290     thepkgs = []
 291     for pkg in cache:
 292         version = pkg.candidate
 293         if version is None:
 294             version = pkg.installed
 295         if version is None:
 296             continue
 297         record = version.record
 298         if not record.has_key(&#39;Npp-MimeType&#39;):
 299             continue
 300         mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
 301         for t in mime_types:
 302             t = t.rstrip().strip()
 303             if t == mimetype:
 304                 thepkgs.append(pkg.name)
 305     return thepkgs
 306 mimetype = &quot;audio/ogg&quot;
 307 if 1 &lt; len(sys.argv):
 308     mimetype = sys.argv[1]
 309 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
 310 for pkg in pkgs_handling_mimetype(mimetype):
 311     print &quot;  %s&quot; %pkg
 312 &lt;/pre&gt;
 313
 314 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
 315
 316 &lt;pre&gt;
 317 % ./apt-find-browserplug-for-mimetype
 318 Browser plugin packages supporting audio/ogg:
 319   gecko-mediaplayer
 320 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
 321 Browser plugin packages supporting application/x-shockwave-flash:
 322   browser-plugin-gnash
 323 %
 324 &lt;/pre&gt;
 325
 326 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
 327 itself to query for plugins and propose to install the needed
 328 packages.  It would be great if Debian supported such feature too.  Is
 329 anyone working on adding it?&lt;/p&gt;
 330
 331 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
 332 request for icweasel support for this feature is
 333 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
 334 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today).  Lack
 335 of manpower and wish for a different design is the reason thus feature
 336 is not yet in iceweasel from Debian.&lt;/p&gt;
 337 </description>
 338         </item>
 339
 340         <item>
 341                 <title>What is the most supported MIME type in Debian?</title>
 342                 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
 343                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
 344                 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
 345                 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
 346 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
 347 proposal to make it possible for a Desktop application to propose to
 348 the user some package to install to gain support for a given MIME
 349 type, font, library etc. that is currently missing.  With such
 350 mechanism in place, it would be possible for the desktop to
 351 automatically propose and install leocad if some LDraw file is
 352 downloaded by the browser.&lt;/p&gt;
 353
 354 &lt;p&gt;To get some idea about the current content of the archive, I decided
 355 to write a simple program to extract all .desktop files from the
 356 Debian archive and look up the claimed MIME support there.  The result
 357 can be found on the
 358 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
 359 site&lt;/a&gt;.  Using the collected information, it become possible to
 360 answer the question in the title.  Here are the 20 most supported MIME
 361 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
 362 The complete list is available from the link above.&lt;/p&gt;
 363
 364 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
 365
 366 &lt;pre&gt;
 367   count MIME type
 368   ----- -----------------------
 369      32 text/plain
 370      30 audio/mpeg
 371      29 image/png
 372      28 image/jpeg
 373      27 application/ogg
 374      26 audio/x-mp3
 375      25 image/tiff
 376      25 image/gif
 377      22 image/bmp
 378      22 audio/x-wav
 379      20 audio/x-flac
 380      19 audio/x-mpegurl
 381      18 video/x-ms-asf
 382      18 audio/x-musepack
 383      18 audio/x-mpeg
 384      18 application/x-ogg
 385      17 video/mpeg
 386      17 audio/x-scpls
 387      17 audio/ogg
 388      16 video/x-ms-wmv
 389 &lt;/pre&gt;
 390
 391 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
 392
 393 &lt;pre&gt;
 394   count MIME type
 395   ----- -----------------------
 396      33 text/plain
 397      32 image/png
 398      32 image/jpeg
 399      29 audio/mpeg
 400      27 image/gif
 401      26 image/tiff
 402      26 application/ogg
 403      25 audio/x-mp3
 404      22 image/bmp
 405      21 audio/x-wav
 406      19 audio/x-mpegurl
 407      19 audio/x-mpeg
 408      18 video/mpeg
 409      18 audio/x-scpls
 410      18 audio/x-flac
 411      18 application/x-ogg
 412      17 video/x-ms-asf
 413      17 text/html
 414      17 audio/x-musepack
 415      16 image/x-xbitmap
 416 &lt;/pre&gt;
 417
 418 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
 419
 420 &lt;pre&gt;
 421   count MIME type
 422   ----- -----------------------
 423      31 text/plain
 424      31 image/png
 425      31 image/jpeg
 426      29 audio/mpeg
 427      28 application/ogg
 428      27 image/gif
 429      26 image/tiff
 430      26 audio/x-mp3
 431      23 audio/x-wav
 432      22 image/bmp
 433      21 audio/x-flac
 434      20 audio/x-mpegurl
 435      19 audio/x-mpeg
 436      18 video/x-ms-asf
 437      18 video/mpeg
 438      18 audio/x-scpls
 439      18 application/x-ogg
 440      17 audio/x-musepack
 441      16 video/x-ms-wmv
 442      16 video/x-msvideo
 443 &lt;/pre&gt;
 444
 445 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
 446 information mentioned in DEP-11.  I have not yet had time to look at
 447 it, but hope the PackageKit people in Debian are on top of these
 448 issues.&lt;/p&gt;
 449
 450 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
 451 discovering a typo in my script.&lt;/p&gt;
 452 </description>
 453         </item>
 454
 455         <item>
 456                 <title>Using modalias info to find packages handling my hardware</title>
 457                 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
 458                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
 459                 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
 460                 <description>&lt;p&gt;Yesterday, I wrote about the
 461 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
 462 values provided by the Linux kernel&lt;/a&gt; following my hope for
 463 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
 464 dongle support in Debian&lt;/a&gt;.  Using this knowledge, I have tested how
 465 modalias values attached to package names can be used to map packages
 466 to hardware.  This allow the system to look up and suggest relevant
 467 packages when I plug in some new hardware into my machine, and replace
 468 discover and discover-data as the database used to map hardware to
 469 packages.&lt;/p&gt;
 470
 471 &lt;p&gt;I create a modaliases file with entries like the following,
 472 containing package name, kernel module name (if relevant, otherwise
 473 the package name) and globs matching the relevant hardware
 474 modalias.&lt;/p&gt;
 475
 476 &lt;p&gt;&lt;blockquote&gt;
 477 Package: package-name
 478 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
 479 &lt;/blockquote&gt;&lt;/p&gt;
 480
 481 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
 482 for a given modalias value using this file.&lt;/p&gt;
 483
 484 &lt;p&gt;An entry like this would suggest the video and picture application
 485 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
 486
 487 &lt;p&gt;&lt;blockquote&gt;
 488 Package: cheese
 489 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
 490 &lt;/blockquote&gt;&lt;/p&gt;
 491
 492 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
 493 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
 494
 495 &lt;p&gt;&lt;blockquote&gt;
 496 Package: pcmciautils
 497 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
 498 &lt;/blockquote&gt;&lt;/p&gt;
 499
 500 &lt;p&gt;An entry like this would suggest the package colorhug-client when
 501 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
 502
 503 &lt;p&gt;&lt;blockquote&gt;
 504 Package: colorhug-client
 505 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
 506 &lt;/blockquote&gt;&lt;/p&gt;
 507
 508 &lt;p&gt;I believe the format is compatible with the format of the Packages
 509 file in the Debian archive.  Ubuntu already uses their Packages file
 510 to store their mappings from packages to hardware.&lt;/p&gt;
 511
 512 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
 513 announce the hardware it support in a way my prototype understand.
 514 This allow those publishing packages in an APT source outside the
 515 Debian archive as well as those backporting packages to make sure the
 516 hardware mapping are included in the package meta information.  I&#39;ve
 517 tested such header in the pymissile package, and its modalias mapping
 518 is working as it should with my prototype.  It even made it to Ubuntu
 519 Raring.&lt;/p&gt;
 520
 521 &lt;p&gt;To test if it was possible to look up supported hardware using only
 522 the shell tools available in the Debian installer, I wrote a shell
 523 implementation of the lookup code.  The idea is to create files for
 524 each modalias and let the shell do the matching.  Please check out and
 525 try the
 526 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co&quot;&gt;hw-support-lookup&lt;/a&gt;
 527 shell script.  It run without any extra dependencies and fetch the
 528 hardware mappings from the Debian archive and the subversion
 529 repository where I currently work on my prototype.&lt;/p&gt;
 530
 531 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
 532 install yubikey-personalization:&lt;/p&gt;
 533
 534 &lt;p&gt;&lt;blockquote&gt;
 535 % ./hw-support-lookup
 536 &lt;br&gt;yubikey-personalization
 537 &lt;br&gt;%
 538 &lt;/blockquote&gt;&lt;/p&gt;
 539
 540 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
 541 propose to install the pcmciautils package:&lt;/p&gt;
 542
 543 &lt;p&gt;&lt;blockquote&gt;
 544 % ./hw-support-lookup
 545 &lt;br&gt;pcmciautils
 546 &lt;br&gt;%
 547 &lt;/blockquote&gt;&lt;/p&gt;
 548
 549 &lt;p&gt;If you know of any hardware-package mapping that should be added to
 550 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
 551 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
 552
 553 &lt;p&gt;It could be possible to generate several of the mappings between
 554 packages and hardware.  One source would be to look at packages with
 555 kernel modules, ie packages with *.ko files in /lib/modules/, and
 556 extract their modalias information.  Another would be to look at
 557 packages with udev rules, ie packages with files in
 558 /lib/udev/rules.d/, and extract their vendor/model information to
 559 generate a modalias matching rule.  I have not tested any of these to
 560 see if it work.&lt;/p&gt;
 561
 562 &lt;p&gt;If you want to help implementing a system to let us propose what
 563 packages to install when new hardware is plugged into a Debian
 564 machine, please send me an email or talk to me on
 565 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
 566 </description>
 567         </item>
 568
 569         <item>
 570                 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
 571                 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
 572                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
 573                 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
 574                 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
 575 information, to find the packages that support a given piece of
 576 hardware, I refreshed my memory regarding modalias values, and decided
 577 to document the details.  Here are my findings so far, also available
 578 in
 579 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
 580 Debian Edu subversion repository&lt;/a&gt;:
 581
 582 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
 583
 584 &lt;p&gt;This document try to explain what the different types of modalias
 585 values stands for.  It is in part based on information from
 586 &amp;lt;URL: &lt;a href=&quot;https://wiki.archlinux.org/index.php/Modalias&quot;&gt;https://wiki.archlinux.org/index.php/Modalias&lt;/a&gt; &amp;gt;,
 587 &amp;lt;URL: &lt;a href=&quot;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&quot;&gt;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&lt;/a&gt; &amp;gt;,
 588 &amp;lt;URL: &lt;a href=&quot;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&quot;&gt;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&lt;/a&gt; &amp;gt; and
 589 &amp;lt;URL: &lt;a href=&quot;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&quot;&gt;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&lt;/a&gt; &amp;gt;.
 590
 591 &lt;p&gt;The modalias entries for a given Linux machine can be found using
 592 this shell script:&lt;/p&gt;
 593
 594 &lt;pre&gt;
 595 find /sys -name modalias -print0 | xargs -0 cat | sort -u
 596 &lt;/pre&gt;
 597
 598 &lt;p&gt;The supported modalias globs for a given kernel module can be found
 599 using modinfo:&lt;/p&gt;
 600
 601 &lt;pre&gt;
 602 % /sbin/modinfo psmouse | grep alias:
 603 alias:          serio:ty05pr*id*ex*
 604 alias:          serio:ty01pr*id*ex*
 605 %
 606 &lt;/pre&gt;
 607
 608 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
 609
 610 &lt;p&gt;A typical PCI entry can look like this.  This is an Intel Host
 611 Bridge memory controller:&lt;/p&gt;
 612
 613 &lt;p&gt;&lt;blockquote&gt;
 614 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
 615 &lt;/blockquote&gt;&lt;/p&gt;
 616
 617 &lt;p&gt;This represent these values:&lt;/p&gt;
 618
 619 &lt;pre&gt;
 620  v   00008086  (vendor)
 621  d   00002770  (device)
 622  sv  00001028  (subvendor)
 623  sd  000001AD  (subdevice)
 624  bc  06        (bus class)
 625  sc  00        (bus subclass)
 626  i   00        (interface)
 627 &lt;/pre&gt;
 628
 629 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
 630 -n&#39; as 8086:2770.  The bus class/subclass is also shown by lspci as
 631 0600.  The 0600 class is a host bridge.  Other useful bus values are
 632 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
 633
 634 &lt;p&gt;Not sure how to figure out the interface value, nor what it
 635 means.&lt;/p&gt;
 636
 637 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
 638
 639 &lt;p&gt;Some typical USB entries can look like this.  This is an internal
 640 USB hub in a laptop:&lt;/p&gt;
 641
 642 &lt;p&gt;&lt;blockquote&gt;
 643 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
 644 &lt;/blockquote&gt;&lt;/p&gt;
 645
 646 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
 647
 648 &lt;pre&gt;
 649  v    1D6B  (device vendor)
 650  p    0001  (device product)
 651  d    0206  (bcddevice)
 652  dc     09  (device class)
 653  dsc    00  (device subclass)
 654  dp     00  (device protocol)
 655  ic     09  (interface class)
 656  isc    00  (interface subclass)
 657  ip     00  (interface protocol)
 658 &lt;/pre&gt;
 659
 660 &lt;p&gt;The 0900 device class/subclass means hub.  Some times the relevant
 661 class is in the interface class section.  For a simple USB web camera,
 662 these alias entries show up:&lt;/p&gt;
 663
 664 &lt;p&gt;&lt;blockquote&gt;
 665 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
 666 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
 667 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
 668 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
 669 &lt;/blockquote&gt;&lt;/p&gt;
 670
 671 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
 672 camera), 0101 is audio control device and 0102 is audio streaming (aka
 673 microphone).  Thus this is a camera with microphone included.&lt;/p&gt;
 674
 675 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
 676
 677 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff.  This is an IR
 678 receiver in a Thinkpad X40:&lt;/p&gt;
 679
 680 &lt;p&gt;&lt;blockquote&gt;
 681 acpi:IBM0071:PNP0511:
 682 &lt;/blockquote&gt;&lt;/p&gt;
 683
 684 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
 685
 686 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
 687
 688 &lt;p&gt;The DMI table contain lots of information about the computer case
 689 and model.  This is an entry for a IBM Thinkpad X40, fetched from
 690 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
 691
 692 &lt;p&gt;&lt;blockquote&gt;
 693 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
 694 &lt;/blockquote&gt;&lt;/p&gt;
 695
 696 &lt;p&gt;The values present are&lt;/p&gt;
 697
 698 &lt;pre&gt;
 699  bvn  IBM            (BIOS vendor)
 700  bvr  1UETB6WW(1.66) (BIOS version)
 701  bd   06/15/2005     (BIOS date)
 702  svn  IBM            (system vendor)
 703  pn   2371H4G        (product name)
 704  pvr  ThinkPadX40    (product version)
 705  rvn  IBM            (board vendor)
 706  rn   2371H4G        (board name)
 707  rvr  NotAvailable   (board version)
 708  cvn  IBM            (chassis vendor)
 709  ct   10             (chassis type)
 710  cvr  NotAvailable   (chassis version)
 711 &lt;/pre&gt;
 712
 713 &lt;p&gt;The chassis type 10 is Notebook.  Other interesting values can be
 714 found in the dmidecode source:&lt;/p&gt;
 715
 716 &lt;pre&gt;
 717   3 Desktop
 718   4 Low Profile Desktop
 719   5 Pizza Box
 720   6 Mini Tower
 721   7 Tower
 722   8 Portable
 723   9 Laptop
 724  10 Notebook
 725  11 Hand Held
 726  12 Docking Station
 727  13 All In One
 728  14 Sub Notebook
 729  15 Space-saving
 730  16 Lunch Box
 731  17 Main Server Chassis
 732  18 Expansion Chassis
 733  19 Sub Chassis
 734  20 Bus Expansion Chassis
 735  21 Peripheral Chassis
 736  22 RAID Chassis
 737  23 Rack Mount Chassis
 738  24 Sealed-case PC
 739  25 Multi-system
 740  26 CompactPCI
 741  27 AdvancedTCA
 742  28 Blade
 743  29 Blade Enclosing
 744 &lt;/pre&gt;
 745
 746 &lt;p&gt;The chassis type values are not always accurately set in the DMI
 747 table.  For example my home server is a tower, but the DMI modalias
 748 claim it is a desktop.&lt;/p&gt;
 749
 750 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
 751
 752 &lt;p&gt;This type is used for PS/2 mouse plugs.  One example is from my
 753 test machine:&lt;/p&gt;
 754
 755 &lt;p&gt;&lt;blockquote&gt;
 756 serio:ty01pr00id00ex00
 757 &lt;/blockquote&gt;&lt;/p&gt;
 758
 759 &lt;p&gt;The values present are&lt;/p&gt;
 760
 761 &lt;pre&gt;
 762   ty  01  (type)
 763   pr  00  (prototype)
 764   id  00  (id)
 765   ex  00  (extra)
 766 &lt;/pre&gt;
 767
 768 &lt;p&gt;This type is supported by the psmouse driver.  I am not sure what
 769 the valid values are.&lt;/p&gt;
 770
 771 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
 772
 773 &lt;p&gt;There are heaps of other modalias subtypes according to
 774 file2alias.c.  There is the rest of the list from that source: amba,
 775 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
 776 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
 777 vmbus, x86cpu and zorro.  I did not spend time documenting all of
 778 these, as they do not seem relevant for my intended use with mapping
 779 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
 780
 781 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
 782
 783 &lt;p&gt;To check which kernel modules provide support for a given modalias,
 784 one can use the following shell script:&lt;/p&gt;
 785
 786 &lt;pre&gt;
 787   for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
 788     echo &quot;$id&quot; ; \
 789     /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/  /&#39; ; \
 790   done
 791 &lt;/pre&gt;
 792
 793 &lt;p&gt;The output can look like this (only the first few entries as the
 794 list is very long on my test machine):&lt;/p&gt;
 795
 796 &lt;pre&gt;
 797   acpi:ACPI0003:
 798     insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
 799   acpi:device:
 800   FATAL: Module acpi:device: not found.
 801   acpi:IBM0068:
 802     insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
 803     insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
 804     insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
 805     insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
 806   acpi:IBM0071:PNP0511:
 807     insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
 808     insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
 809     insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
 810   [...]
 811 &lt;/pre&gt;
 812
 813 &lt;p&gt;If you want to help implementing a system to let us propose what
 814 packages to install when new hardware is plugged into a Debian
 815 machine, please send me an email or talk to me on
 816 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
 817
 818 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
 819 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
 820 in /sys/ with space in them.&lt;/p&gt;
 821 </description>
 822         </item>
 823
 824         <item>
 825                 <title>Moved the pymissile Debian packaging to collab-maint</title>
 826                 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
 827                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
 828                 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
 829                 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
 830 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
 831 Launcher and updated the Debian package
 832 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
 833 sure udev will fix the device permissions when it is plugged in.  I
 834 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
 835 hopefully make the package be proposed by jockey in Ubuntu when a user
 836 plug in his rocket launcher.  In the process I moved the source to a
 837 git repository under collab-maint, to make it easier for any DD to
 838 contribute.  &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
 839 is not very active, but the software still work for me even after five
 840 years of relative silence.  The new git repository is not listed in
 841 the uploaded package yet, because I want to test the other changes a
 842 bit more before I upload the new version.  If you want to check out
 843 the new version with a .desktop file included, visit the
 844 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
 845 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
 846 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
 847 </description>
 848         </item>
 849
 850         </channel>
 851 </rss>