<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>debian on linux &amp; the mountains</title>
    <link>https://bzed.de/tags/debian/</link>
    <description>Recent content in debian on linux &amp; the mountains</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <copyright>Copyright 2009-2017 Bernd Zeimetz</copyright>
    <lastBuildDate>Tue, 05 Jan 2021 15:33:00 +0000</lastBuildDate><atom:link href="https://bzed.de/tags/debian/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building reverse build dependencies in salsa CI</title>
      <link>https://bzed.de/post/2021/01/building_reverse_build_dependencies_in_salsa_ci/</link>
      <pubDate>Tue, 05 Jan 2021 15:33:00 +0000</pubDate>
      
      <guid>https://bzed.de/post/2021/01/building_reverse_build_dependencies_in_salsa_ci/</guid>
      <description>For the next library soname bump of gpsd I needed to rebuild all reverse dependencies. As this is a task I have to do very often, I came up with some code to generate (and keep uptodate) an include for the gitlab CI. Right now it is rather uncommented, undocumented, but works well. If you like it, MRs are very welcome.
https://salsa.debian.org/bzed/reverse-dependency-ci/
The generated files are here:
https://bzed.pages.debian.net/reverse-dependency-ci/
Usage:
include: - https://salsa.</description>
    </item>
    
    <item>
      <title>Public service annoucement for a modern Debian</title>
      <link>https://bzed.de/post/2019/12/public_service_annoucement_for_a_modern_debian./</link>
      <pubDate>Sun, 08 Dec 2019 01:48:00 +0000</pubDate>
      
      <guid>https://bzed.de/post/2019/12/public_service_annoucement_for_a_modern_debian./</guid>
      <description>Don&amp;rsquo;t forget to vote!
echo &#34; - - -=-=-=-=-=- Don&#39;t Delete Anything Between These Lines =-=-=-=-=-=-=-=- 7b77e0f2-4ff9-4adb-85e4-af249191f27a [ 1 ] Choice 1: F: Focus on systemd [ 2 ] Choice 2: B: Systemd but we support exploring alternatives [ 5 ] Choice 3: A: Support for multiple init systems is Important [ 6 ] Choice 4: D: Support non-systemd systems, without blocking progress [ 4 ] Choice 5: H: Support portability, without blocking progress [ 7 ] Choice 6: E: Support for multiple init systems is Required [ 8 ] Choice 7: G: Support portability and multiple implementations [ 3 ] Choice 8: Further Discussion - - -=-=-=-=-=- Don&#39;t Delete Anything Between These Lines =-=-=-=-=-=-=-=- &#34;</description>
    </item>
    
    <item>
      <title>Collecting statistics from TP-Link HS110 SmartPlugs using collectd</title>
      <link>https://bzed.de/post/2017/12/tp-link_hs110_plugin_for_collectd/</link>
      <pubDate>Wed, 13 Dec 2017 18:15:00 +0000</pubDate>
      
      <guid>https://bzed.de/post/2017/12/tp-link_hs110_plugin_for_collectd/</guid>
      <description>&lt;p&gt;Running a 3d printer alone at home is not necessarily the best idea - so I was
looking for a way to force it off from remote. As &lt;a href=&#34;http://octoprint.org/&#34;&gt;OctoPrint&lt;/a&gt;
user I stumbled upon a
&lt;a href=&#34;https://plugins.octoprint.org/plugins/tplinksmartplug/&#34;&gt;plugin to control TP-Link Smartplugs&lt;/a&gt;,
so I decided to give them a try.
What I found especially nice on the HS110 model was that it is possible to
monitor power usage, current and voltage. Of course I wanted to have a long term graph of it.
The result is a small &lt;a href=&#34;http://collectd.org/&#34;&gt;collectd&lt;/a&gt; plugin, written in Python. It is
available on github: &lt;a href=&#34;https://github.com/bzed/collectd-tplink_hs110&#34;&gt;https://github.com/bzed/collectd-tplink_hs110&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Connecting your 3D printer to OctoPrint automatically</title>
      <link>https://bzed.de/post/2017/11/octoprint_autoconnect_printer/</link>
      <pubDate>Wed, 01 Nov 2017 14:35:00 +0000</pubDate>
      
      <guid>https://bzed.de/post/2017/11/octoprint_autoconnect_printer/</guid>
      <description>Recently I joined the group of 3d printer owners and OctoPrint users. After some days I got annoyed by the fact that so far nobody seems to have thought about automatically connecting a printer to OctoPrint after turning the printer on. If you start OctoPrint after your printer, everything works fine. But here OctoPrint runs 24/7 but I turn off the printer when it is done with printing.
My solution of the problem is based on udev and systemd and should work on most recent Linux installations.</description>
    </item>
    
    <item>
      <title>bzed-letsencrypt puppet module</title>
      <link>https://bzed.de/post/2016/02/bzed-letsencrypt_puppet_module/</link>
      <pubDate>Fri, 05 Feb 2016 19:55:01 +0000</pubDate>
      
      <guid>https://bzed.de/post/2016/02/bzed-letsencrypt_puppet_module/</guid>
      <description>With the announcement of the Let&amp;rsquo;s Encrypt dns-01 challenge support we finally had a way to retrieve certificates for those hosts where http challenges won&amp;rsquo;t work. Also it allows to centralize the signing procedure to avoid the installation and maintenance of letsencrypt clients on all hosts.
For an implementation I had the following requirements in my mind:
 Handling of key/csr generation and certificate signing by puppet. Private keys don&amp;rsquo;t leave the host they were generated on.</description>
    </item>
    
    <item>
      <title>open-vm-tools updated</title>
      <link>https://bzed.de/post/2016/01/open-vm-tools_updated/</link>
      <pubDate>Mon, 04 Jan 2016 10:06:01 +0000</pubDate>
      
      <guid>https://bzed.de/post/2016/01/open-vm-tools_updated/</guid>
      <description>In January 2014 the open-vm-tools package was orphaned and I took the chance to take over the maintenance. Unfortunately the package is still not 100% in the shape I&amp;rsquo;d like to see it, but I&amp;rsquo;m getting closer. I have to say Thank You for a lot of good bug reports, especially for those use cases which are hard to test/reproduce for me (running Debian in a Windows-based VMware Workstation Player for example&amp;hellip;.</description>
    </item>
    
    <item>
      <title>bzed.de online again</title>
      <link>https://bzed.de/post/2015/11/bzed.de_online_again/</link>
      <pubDate>Tue, 24 Nov 2015 19:41:06 +0000</pubDate>
      
      <guid>https://bzed.de/post/2015/11/bzed.de_online_again/</guid>
      <description>Finally, bzed.de is back online and I&amp;rsquo;m planning to start blogging again! Part of the reason why I became inactive was the usage of ikiwiki, which is great, but at end unnecessarily complicated. So I&amp;rsquo;ve migrated by page to gohugo.io - a static website generator, written in go. Hugo has an active community and it is easy to create themes for it or to enhance it. Also it is using plain Markdown syntax instead of special ikiwiki syntax mixed into it - should make it easy to migrate away again if necessary.</description>
    </item>
    
    <item>
      <title>Report from the Bug Squashing Party in Salzburg</title>
      <link>https://bzed.de/post/2012/06/report_from_the_bug_squashing_party_in_salzburg/</link>
      <pubDate>Fri, 29 Jun 2012 23:00:00 +0000</pubDate>
      
      <guid>https://bzed.de/post/2012/06/report_from_the_bug_squashing_party_in_salzburg/</guid>
      <description>Participation and Results From June 15-17th we held a Debian BugSquashingParty in Salzburg, hosted and sponsored by conova communications GmbH. It was a fun and busy weekend, with 15-17 people from 5 countries being around, mainly working on RC bugs in Testing/Unstable. Gerfried Fuchs (rhonda) also worked on triaging the impact of RC bugs on the version in Squeeze, while Peter Palfrader (weasel) took care of Tor related things and Debian sysadmin work, including starting on the new bugs and udd hosts.</description>
    </item>
    
    <item>
      <title>Bug squashing party in Salzburg</title>
      <link>https://bzed.de/post/2012/06/bug_squashing_party_in_salzburg/</link>
      <pubDate>Tue, 12 Jun 2012 19:00:00 +0000</pubDate>
      
      <guid>https://bzed.de/post/2012/06/bug_squashing_party_in_salzburg/</guid>
      <description>Just as a little reminder, the Bug Squashing Party in Salzburg will start in three days. We still have sponsored accomodation for five four people left, so don&amp;rsquo;t hesitate to come! Squashing as many RC bugs for Wheezy as possible is on the TODO list for the weekend! Also we&amp;rsquo;ll work on making Debian a proper Spacewalk client. This might be a bit too late for Wheezy, but there will be backports :)</description>
    </item>
    
    <item>
      <title>Working on spacewalk support for and in Debian</title>
      <link>https://bzed.de/post/2012/04/working_on_spacewalk_support_for_and_in_debian/</link>
      <pubDate>Tue, 10 Apr 2012 21:38:00 +0000</pubDate>
      
      <guid>https://bzed.de/post/2012/04/working_on_spacewalk_support_for_and_in_debian/</guid>
      <description>With the latest release of Spacewalk PostgreSQL seems to be supported properly
  finally. Also there are efforts to support Debian as a client system. So I&amp;rsquo;m thinking about using the upcoming BugSquashingParty in Salzburg to
 analyze the current support of Debian as a client in Spacewalk and maybe work on a better integration finalize the packaging and upload the client packages which were prepared by Miroslav Suchý (I hope he will be able to join us!</description>
    </item>
    
    <item>
      <title>Nagios-plugins-contrib released</title>
      <link>https://bzed.de/post/2012/02/nagios-plugins-contrib_released/</link>
      <pubDate>Wed, 22 Feb 2012 22:47:19 +0000</pubDate>
      
      <guid>https://bzed.de/post/2012/02/nagios-plugins-contrib_released/</guid>
      <description>Nagios or Icinga users probably know the problem that neither the default plugin packages (nagios-plugins-basic and -standard) nor the few other plugin packages ship all the plugins you need to monitor your hardware and software properly. And unless you have puppet, cfengine or some other automation software, you probably just start searching plugins on Nagios Exchange, MonitoringExchange or some other machines you are monitoring already.
Your problem shall be solved! nagios-plugins-contrib passed NEW today.</description>
    </item>
    
    <item>
      <title>Re-indenting files with vim</title>
      <link>https://bzed.de/post/2011/07/re-indenting_files_with_vim/</link>
      <pubDate>Tue, 12 Jul 2011 17:28:45 +0200</pubDate>
      
      <guid>https://bzed.de/post/2011/07/re-indenting_files_with_vim/</guid>
      <description>Sometimes projects with a long history of committers tend to collect various styles of indentation. Unfortunately not for all programming languages exist specialized tools like indent for C/C++, so we need to find a different way to mass-indent files properly. Using vim is one of them.
First you need to create a file (let&amp;rsquo;s call it /tmp/indent.vim) including all the vim commands you want to run on your code. The following piece is a good start:</description>
    </item>
    
    <item>
      <title>Plusone button plugin for ikiwiki</title>
      <link>https://bzed.de/post/2011/07/plusone_button_plugin_for_ikiwiki/</link>
      <pubDate>Sat, 02 Jul 2011 16:29:32 +0200</pubDate>
      
      <guid>https://bzed.de/post/2011/07/plusone_button_plugin_for_ikiwiki/</guid>
      <description>Just published an ikiwiki plugin to add google&amp;rsquo;s +1 buttons. See ikiwiki.info/plugins/contrib/plusone/ for details.
And if you enable html5 in your ikiwiki settings, it won&amp;rsquo;t show up on planet debian as ugly g:plusone tag.</description>
    </item>
    
    <item>
      <title>Merkaartor development version in experimental</title>
      <link>https://bzed.de/post/2010/10/merkaartor_development_version_in_experimental/</link>
      <pubDate>Mon, 25 Oct 2010 15:28:22 +0000</pubDate>
      
      <guid>https://bzed.de/post/2010/10/merkaartor_development_version_in_experimental/</guid>
      <description>For people who do not follow the Merkaartor mailing list: Regulary updated development snapshots are available in experimental again. Please report bugs, either in the Debian BTS or in the upstream bugtracker. Latest addition to Merkaartor is a plugin to support the French Cadastre peoject. </description>
    </item>
    
    <item>
      <title>Monitoring scientific atlanta cable modems with munin</title>
      <link>https://bzed.de/post/2010/09/monitoring_scientific_atlanta_cable_modems_with_munin/</link>
      <pubDate>Wed, 22 Sep 2010 22:57:23 +0200</pubDate>
      
      <guid>https://bzed.de/post/2010/09/monitoring_scientific_atlanta_cable_modems_with_munin/</guid>
      <description>Usually I like to monitor as much as possible. but unfortunately my cable provider does not allow to access the cable modem via SNMP, so I had to find a different way to retrieve at least some basic information. After a bit of googling I figured out how to access the web interface of the Scientific Atlanta modems. The model here is a EPC2203 - seems to work for various models, though.</description>
    </item>
    
    <item>
      <title>Refactoring the guruplug server plus - part two</title>
      <link>https://bzed.de/post/2010/09/refactoring_the_guruplug_server_plus_-_part_two/</link>
      <pubDate>Wed, 22 Sep 2010 11:58:10 +0000</pubDate>
      
      <guid>https://bzed.de/post/2010/09/refactoring_the_guruplug_server_plus_-_part_two/</guid>
      <description>Although the modifications described in my last blog post about refactoring the GuruPlug resulted in a well working GuruPlug, I&amp;rsquo;ve decided to give it some more air to breath at the top of the case. The large round piece of plastic in the middle asked to be removed - and now a shiny 60mm fan grill protects the board from the bad world outside of the case.
So far its working fine and not too hot.</description>
    </item>
    
    <item>
      <title>Refactoring the guruplug server plus</title>
      <link>https://bzed.de/post/2010/09/refactoring_the_guruplug_server_plus/</link>
      <pubDate>Fri, 10 Sep 2010 22:24:12 +0000</pubDate>
      
      <guid>https://bzed.de/post/2010/09/refactoring_the_guruplug_server_plus/</guid>
      <description>As mentioned in my last blog post the GuruPlug Server Plus needs some major refactoring before it can be used. Not doing so will make you end up with a fried brick. There are various stories in the forums about cooling it properly, so you might want to have a look first instead of following mine blindly. And of course - whatever you do - it is your fault when you end up with a brick, not mine!</description>
    </item>
    
    <item>
      <title>The guruplug server plus - major design and qa fail</title>
      <link>https://bzed.de/post/2010/08/the_guruplug_server_plus_-_major_design_and_qa_fail/</link>
      <pubDate>Sun, 29 Aug 2010 10:25:24 +0000</pubDate>
      
      <guid>https://bzed.de/post/2010/08/the_guruplug_server_plus_-_major_design_and_qa_fail/</guid>
      <description>As a lot of people are coming to my blog to read the installing instructions for Debian on the GuruPlug Server Plus, I shall not hide my opinion about it: It is a major design and QA fail. Don&amp;rsquo;t waste your money on it.
The power supply Although I&amp;rsquo;ve ordered the Guruplug pretty early with the promise, that I&amp;rsquo;d have it in April, it arrived at the end of May due to QA issues with the power supply.</description>
    </item>
    
    <item>
      <title>Gimp-plugin-registry 3.5-1</title>
      <link>https://bzed.de/post/2010/07/gimp-plugin-registry_3.5-1/</link>
      <pubDate>Sun, 04 Jul 2010 22:41:34 +0200</pubDate>
      
      <guid>https://bzed.de/post/2010/07/gimp-plugin-registry_3.5-1/</guid>
      <description>During the last three months and since my last blog-post about gimp-plugin-registry a lot happened: Mainly a large number of new plugins was added, but also various enhancements and bugfixes went into the package, together with updates for various already included plugins.
For those who don&amp;rsquo;t know gimp-plugin-registry yet, it is a collection of scripts and plugins for The GIMP. The name is based on the webpage GIMP Plugin Registry, where most (new) plugins and scripts are listed.</description>
    </item>
    
    <item>
      <title>Creating a google sitemap for ikiwiki</title>
      <link>https://bzed.de/post/2010/06/creating_a_google_sitemap_for_ikiwiki/</link>
      <pubDate>Wed, 23 Jun 2010 20:23:49 +0200</pubDate>
      
      <guid>https://bzed.de/post/2010/06/creating_a_google_sitemap_for_ikiwiki/</guid>
      <description>ikiwiki is not yet able to create a Google sitemap internally, so I&amp;rsquo;m using google-sitemapgen. To run it automatically when the website is being updated, I&amp;rsquo;ve changed the git hook to run it after the ikiwiki hook.
 In the ikiwiki setup file let git_wrapper point to a file which is not the post-update hook, so you&amp;rsquo;re able to run it from your own skript. I&amp;rsquo;m using /path/to/myikiwiki.git/hooks/post-update.ikiwiki. Write a skript which runs as post-update hook and executes the created hook from ikiwiki and google-sitemapgen with a proper configuration.</description>
    </item>
    
    <item>
      <title>Signs of bad package maintenance</title>
      <link>https://bzed.de/post/2010/06/signs_of_bad_package_maintenance/</link>
      <pubDate>Sun, 13 Jun 2010 02:13:52 +0200</pubDate>
      
      <guid>https://bzed.de/post/2010/06/signs_of_bad_package_maintenance/</guid>
      <description>&amp;lt;rant&amp;gt;Recently I&amp;rsquo;ve adopted a package, mainly as Merkaartor uses it now. It made me sad to see in which bad condition the package was. Here are just a few things I had to do to bring it into shape:
 The former maintainer removed the documentation and added a +dfsg to the version as there were a few hints left that it is under GFDL or under no license at all.</description>
    </item>
    
    <item>
      <title>Styling changes in ikiwiki 3.20100610</title>
      <link>https://bzed.de/post/2010/06/styling_changes_in_ikiwiki_3.20100610/</link>
      <pubDate>Sat, 12 Jun 2010 01:53:00 +0200</pubDate>
      
      <guid>https://bzed.de/post/2010/06/styling_changes_in_ikiwiki_3.20100610/</guid>
      <description>Some minutes before the release of 3.20100610 we convinced Joey in #ikiwiki to commit the following changes:
 The part of the page which is usually parallel to the sidebar lives within a new div with the id &amp;ldquo;pagebody&amp;rdquo; now. This is the proper fix for the issue and workaround described here. pre elements will show a scrollbar automatically now, thanks to overflow: auto; in the CSS.  We hope that nobody wants to hit us with a bat now :-)</description>
    </item>
    
    <item>
      <title>Merkaartor 0.16.0 available in unstable</title>
      <link>https://bzed.de/post/2010/06/merkaartor_0.16.0_available_in_unstable/</link>
      <pubDate>Sat, 12 Jun 2010 01:10:13 +0200</pubDate>
      
      <guid>https://bzed.de/post/2010/06/merkaartor_0.16.0_available_in_unstable/</guid>
      <description>Merkaartor 0.16.0 was uploaded to Debian/unstable several days ago and should be available on all architectures now.
As usual please help testing the new version - upstream and me will try to fix all bugs as fast as possible. Below follows the long list of new features, for the full list of changes see the CHANGELOG.
 Ramer-Douglas-Peucker simplification of ways (in Roads menu) support for JOSM remote protocol on port 8111 support for &amp;ldquo;standard&amp;rdquo; (as in http://wiki.</description>
    </item>
    
    <item>
      <title>Installing Debian on the guruplug server plus</title>
      <link>https://bzed.de/post/2010/05/installing_debian_on_the_guruplug_server_plus/</link>
      <pubDate>Sat, 29 May 2010 15:36:42 +0000</pubDate>
      
      <guid>https://bzed.de/post/2010/05/installing_debian_on_the_guruplug_server_plus/</guid>
      <description>&amp;ndash; Before buying or using a GuruPlug make sure you first read &amp;ldquo;the guruplug server plus - major design and qa fail&amp;rdquo; and &amp;ldquo;refactoring the guruplug server plus&amp;rdquo; &amp;ndash; 
Yesterday finally my GuruPlug Server Plus arrived. Took longer than expected, but as it seems Globalscale had some issues with the power supplies and they were replaced before shipping the GuruPlugs.
The GuruPlug Basically the GuruPlugs are an enhanced version of the well known SheevaPlugs, the biggest difference is probably the need for an external JTAG/UART&amp;lt;&amp;gt;RS232 board to access the serial console.</description>
    </item>
    
    <item>
      <title>Merkaartor - countdown to 0.16</title>
      <link>https://bzed.de/post/2010/05/merkaartor_-_countdown_to_0.16/</link>
      <pubDate>Thu, 20 May 2010 22:44:09 +0200</pubDate>
      
      <guid>https://bzed.de/post/2010/05/merkaartor_-_countdown_to_0.16/</guid>
      <description>As announced on the Merkaartor mailing lists, version 0.16 is planned to be released on 6th June. Therefore I&amp;rsquo;ve uploaded a git snapshot to experimental today. Please give it a try and report all problems, either to the Debian BTS or directly in the upstream bug tracker.
Version 0.16 will contain a lot of new features and various bugfixes and enhancements. For me the most important additions are support for Walking Papers and support for OpenStreetBugs.</description>
    </item>
    
    <item>
      <title>Deb.li - the Debian ShortURL Service - status update</title>
      <link>https://bzed.de/post/2010/05/deb.li_-_the_debian_shorturl_service_-_status_update/</link>
      <pubDate>Wed, 19 May 2010 01:11:30 +0200</pubDate>
      
      <guid>https://bzed.de/post/2010/05/deb.li_-_the_debian_shorturl_service_-_status_update/</guid>
      <description>Although my progress in adding new features is not too fast (hint: patches and help is welcome), I&amp;rsquo;m quite happy with the progress of deb.li. As mentioned on my last post on debian-devel@l.d.o, I&amp;rsquo;ve spent some time to migrate it to the new, but very well written microframework Flask, which is based on Werkzeug, the probably most advanced WSGI utility module. The migration also allowed me to clean up several pieces of messy code which were necessary to work around some issues in python-bottle.</description>
    </item>
    
    <item>
      <title>New css for bzed.de</title>
      <link>https://bzed.de/post/2010/05/new_css_for_bzed.de/</link>
      <pubDate>Wed, 19 May 2010 01:11:30 +0200</pubDate>
      
      <guid>https://bzed.de/post/2010/05/new_css_for_bzed.de/</guid>
      <description>After more than a year of using ikiwiki to run bzed.de I thought it would be a good time replace the darkish-brown style by something bright. Also I wanted to get righ of the massive changes I had to do on the template files to make the old layout work.
Unfortunately I hit one of the - in my opinion - major problems in the ikiwiki templates again: You can&amp;rsquo;t rely on all &amp;lt;div&amp;gt;s being available on all pages, which is quite annoying when you need them to style the page with CSS.</description>
    </item>
    
    <item>
      <title>Gimp-plugin-registry package updated</title>
      <link>https://bzed.de/post/2010/04/gimp-plugin-registry_package_updated/</link>
      <pubDate>Thu, 15 Apr 2010 21:05:47 +0200</pubDate>
      
      <guid>https://bzed.de/post/2010/04/gimp-plugin-registry_package_updated/</guid>
      <description>Yesterday I finally found the time to update gimp-plugin-registry, the (hopefully!) largest and best collection of plugins for The GIMP. As usual here comes a short summary of the changes:
 The wonderful scripts from El Samuko are included now: Antique Photo Border Script Che Guevara Script Cyanotype Script Difference Layer Script Escape Line Script Film Grain Script First Photo Border Script Lomo Script with Old Style Colors Movie 300 Script National Geographic Script Obama &amp;ldquo;HOPE&amp;rdquo; Script Rainy Landscape Script Photochrom Script Sprocket Hole Script Sunny Landscape Script Technicolor 2 Color Script Technicolor 3 Color Script Vintage Look Script Included the X11 Mouce Curser (XMC) plugin as requested by KiBi.</description>
    </item>
    
    <item>
      <title>Deb.li - the Debian ShortURL Service - beta test</title>
      <link>https://bzed.de/post/2010/04/deb.li_-_the_debian_shorturl_service_-_beta_test/</link>
      <pubDate>Sun, 04 Apr 2010 01:46:45 +0200</pubDate>
      
      <guid>https://bzed.de/post/2010/04/deb.li_-_the_debian_shorturl_service_-_beta_test/</guid>
      <description>After several other Debian developers convinced me that a ShortURL service, which is under control of a Debian Developer would be useful for them, I&amp;rsquo;ve spent some time to write the necessary code for it. And if it will be used regulary, I&amp;rsquo;ll ask DSA if they want to host it on a proper machine.
So I&amp;rsquo;m happy to announce the public beta test of deb.li (also available under go.debian.net)! Please note that neither the content of the pages nor the CSS is finished&amp;hellip; :)</description>
    </item>
    
    <item>
      <title>Assimilated</title>
      <link>https://bzed.de/post/2010/03/assimilated/</link>
      <pubDate>Sat, 13 Mar 2010 17:09:08 +0100</pubDate>
      
      <guid>https://bzed.de/post/2010/03/assimilated/</guid>
      <description>[[!img /_images/fedora_assimilated.jpg alt=&amp;ldquo;At the Chemnitzer Linux Tage the fedora project was assimilated by the Debian project as fedora realized that rpm is crap ;)&amp;rdquo; ]]</description>
    </item>
    
    <item>
      <title>Merkaartor svn snapshot uploaded to experimental</title>
      <link>https://bzed.de/post/2010/02/merkaartor_svn_snapshot_uploaded_to_experimental/</link>
      <pubDate>Thu, 18 Feb 2010 16:01:28 +0100</pubDate>
      
      <guid>https://bzed.de/post/2010/02/merkaartor_svn_snapshot_uploaded_to_experimental/</guid>
      <description>As the release of version 0.15 of Merkaartor (a map editor for OpenStreetMap.org) is planned for the end of February, I&amp;rsquo;ve uploaded a svn snapshot based on revision 19956 to Debian experimental. Please test it and report bugs to the BTS as soon as possible, so I can triage and forward them to upstream.</description>
    </item>
    
    <item>
      <title>Caching issues in django</title>
      <link>https://bzed.de/post/2010/02/caching_issues_in_django/</link>
      <pubDate>Wed, 10 Feb 2010 15:41:13 +0100</pubDate>
      
      <guid>https://bzed.de/post/2010/02/caching_issues_in_django/</guid>
      <description>Yesterday I stumbled upon an interesting and broken behaviour of Django: Running two instances with the same memcached as cache backend might result in displaying the wrong template from the cache in case we have template files with the same name but a different content.
This behaviour is also visible in all django applications which use the cache backend without taking care of settings.CACHE_MIDDLEWARE_KEY_PREFIX. As mentioned in the bug report a design decision is necessary here, as the setting was only supposed to be used in middlewares.</description>
    </item>
    
    <item>
      <title>The ganneff way of becoming a Debian package maintainer</title>
      <link>https://bzed.de/post/2009/11/the_ganneff_way_of_becoming_a_debian_package_maintainer/</link>
      <pubDate>Sat, 28 Nov 2009 22:46:43 +0100</pubDate>
      
      <guid>https://bzed.de/post/2009/11/the_ganneff_way_of_becoming_a_debian_package_maintainer/</guid>
      <description>Once there was a project called Debian and a Ganneff&amp;hellip;. (unfortunately in German only&amp;hellip;.)
 22:20 Das ist doch voll die Arbeit Maintainer zu werden :-). Ich geb gewünschte Pakete immer nur weiter an einen der da sowieso schon den Kernel betreut :-) 22:21 es is nur viel arbeit wenn du keinen schimmer hast 22:22 ja ich hab nur das seepferdchen *g* 22:22 Knusper: ja sicher ist es das 22:22 kopf - tisch 22:22 Knusper, wenn du die verwaisten pakete findest siehst du auf der gleichen seite auch die links wie man maintainer wird 22:22 die hab ich gefunden 22:22 zumindest hab ich das das letzte mal dort gesehen 22:24 wnpp?</description>
    </item>
    
    <item>
      <title>Douf00 - fat free presentations</title>
      <link>https://bzed.de/post/2009/09/douf00_-_fat_free_presentations/</link>
      <pubDate>Thu, 17 Sep 2009 01:39:21 +0200</pubDate>
      
      <guid>https://bzed.de/post/2009/09/douf00_-_fat_free_presentations/</guid>
      <description>Now there is yet another package with a weird name in Debian - douf00 - a lightweight, slim and straight forward presentation tool. Written by some guys from a hacking and security team, which is mainly based in Vienna - guess that explains the l33t name (if you&amp;rsquo;re scared now, yes, I&amp;rsquo;ve reviewed the code&amp;hellip;). At the FrOSCon one of the authors asked me if I&amp;rsquo;d be willing to package it for Debian.</description>
    </item>
    
    <item>
      <title>Retrieving debconf translations from the bts</title>
      <link>https://bzed.de/post/2009/07/retrieving_debconf_translations_from_the_bts/</link>
      <pubDate>Wed, 22 Jul 2009 17:17:16 +0200</pubDate>
      
      <guid>https://bzed.de/post/2009/07/retrieving_debconf_translations_from_the_bts/</guid>
      <description>Downloading debconf translations from the bts and committing them to my packaging repository was always a task which pretty much annoyed me. Today I spent some time on writing a script which does this job for me. There is still much to improve - it is more like a prove of concept - but it works for me. With some love and probably a rewrite in Perl or Python it is a good candidate for devscripts probably.</description>
    </item>
    
    <item>
      <title>Pidgin-blinklight replacement for other messengers</title>
      <link>https://bzed.de/post/2009/07/pidgin-blinklight_replacement_for_other_messengers/</link>
      <pubDate>Wed, 22 Jul 2009 11:39:22 +0200</pubDate>
      
      <guid>https://bzed.de/post/2009/07/pidgin-blinklight_replacement_for_other_messengers/</guid>
      <description>One of my favourite plugins for pidgin is pidgin-blinklight, which blinks my ThinkPad&amp;rsquo;s ThinkLight upon the arrival of new messages. Pretty useful as it is not as annoying (especially for others around you) as playing weird sounds. Unfortunately such a plugin is not available for other messengers like psi - but you&amp;rsquo;re able to specify your own sound player. So I came up with the following script, which is my default sound player in psi now.</description>
    </item>
    
    <item>
      <title>Gpsd 2.39-3 in Debian experimental</title>
      <link>https://bzed.de/post/2009/07/gpsd_2.39-3_in_debian_experimental/</link>
      <pubDate>Sat, 04 Jul 2009 22:56:07 +0200</pubDate>
      
      <guid>https://bzed.de/post/2009/07/gpsd_2.39-3_in_debian_experimental/</guid>
      <description>Since a few days a new revision of gpsd is available in Debian/experimental. If you&amp;rsquo;re a gpsd user, please give it a try as it contains various changes to the debconf templates and the config script. Although I don&amp;rsquo;t expect any problems, it is better to test it well. Also there&amp;rsquo;re several updates of the template translations missing and I want to give the translators some more time before uploading the package to unstable.</description>
    </item>
    
    <item>
      <title>Looking for a grip replacement</title>
      <link>https://bzed.de/post/2009/06/looking_for_a_grip_replacement/</link>
      <pubDate>Sun, 28 Jun 2009 23:50:10 +0200</pubDate>
      
      <guid>https://bzed.de/post/2009/06/looking_for_a_grip_replacement/</guid>
      <description>Today was the first day I needed a tool to rip an audio CD after the removal of grip from testing/unstable. Unfortunately I did not find an appropriate replacement yet. At the moment I&amp;rsquo;m using asunder, which is nice, but missing a lot of the features grip had.
Dear lazyweb, is there a proper replacement for grip out there, or is anybody willing to take over the upstream maintenance for grip?</description>
    </item>
    
    <item>
      <title>Vmbuilder for Debian</title>
      <link>https://bzed.de/post/2009/06/vmbuilder_for_debian/</link>
      <pubDate>Sun, 07 Jun 2009 20:25:09 +0200</pubDate>
      
      <guid>https://bzed.de/post/2009/06/vmbuilder_for_debian/</guid>
      <description>As we needed it for one of our customers, I&amp;rsquo;ve started to add support for Debian to the Ubuntu VMBuilder. My changes are not merged into trunk yet, but you can get them by running bzr branch lp:~bzed/vmbuilder/debian. At the moment there is only support for Etch, I&amp;rsquo;ll add Lenny and Squeeze as soon as I find the time for it, probably next week - patches are welcome.</description>
    </item>
    
    <item>
      <title>Howto set android developer device permissions with udev</title>
      <link>https://bzed.de/post/2009/05/howto_set_android_developer_device_permissions_with_udev/</link>
      <pubDate>Sun, 24 May 2009 22:33:47 +0200</pubDate>
      
      <guid>https://bzed.de/post/2009/05/howto_set_android_developer_device_permissions_with_udev/</guid>
      <description>As there&amp;rsquo;re several, more or less well working howtos about creating udev rules to allow access to the USB debug devices of Android phones out there in the wild, I decided to write my own one. The udev rules file I provide here works at least for the HTC Dream models (aka T-Mobile G1 and Google Devphone) and the ZTE Blade (aka Orange San Francisco), probably for other phones, too.</description>
    </item>
    
    <item>
      <title>Package build time: cdbs vs dh</title>
      <link>https://bzed.de/post/2009/04/package_build_time_cdbs_vs_dh/</link>
      <pubDate>Mon, 20 Apr 2009 13:43:04 +0200</pubDate>
      
      <guid>https://bzed.de/post/2009/04/package_build_time_cdbs_vs_dh/</guid>
      <description>Most people (at least those who hear me shouting on irc) probably know that I&amp;rsquo;m not a fan of cdbs. While working on geoclue, which builds a lot of binary packages I realized, that cdbs wastes an insane amount of time by calling dh_* for every single package. One of the reasons geoclue uses cdbs is that the maintainer likes the short debian/rules file. We&amp;rsquo;ll, compare yourself:
cdbs:
 #!/usr/bin/make -f # -*- makefile -*- # Uncomment this to turn on verbose mode.</description>
    </item>
    
    <item>
      <title>Gimp-plugin-registry updated</title>
      <link>https://bzed.de/post/2009/04/gimp-plugin-registry_updated/</link>
      <pubDate>Sun, 19 Apr 2009 00:57:40 +0200</pubDate>
      
      <guid>https://bzed.de/post/2009/04/gimp-plugin-registry_updated/</guid>
      <description>Somehow I managed to forget to blog about this for some time - version 2.1-1 of gimp-plugin-registry is available in testing since several days. For detailed changes please have a look in the changelog, for the impatient - here is the summary:
 New plugins: btn4ws, sprocket-hole, cmyk-tiff-2-pdf, dustcleaner (back again, was removed for stable as it was not mature enough) New upstream versions of the following plugins: lqr, DBP, diana-holga2, focusblur, GREYCstoration, LayerEffects (now using Python), normalmap, save-for-web, seperate+, wavelet-denoise Removed plugins: exposure-blend  As usual let me know if there&amp;rsquo;s a nice plugin you&amp;rsquo;d like to see in the package.</description>
    </item>
    
    <item>
      <title>Gimp-plugin-registry update planned</title>
      <link>https://bzed.de/post/2009/03/gimp-plugin-registry_update_planned/</link>
      <pubDate>Fri, 13 Mar 2009 13:30:24 +0100</pubDate>
      
      <guid>https://bzed.de/post/2009/03/gimp-plugin-registry_update_planned/</guid>
      <description>Within the next days I plan to update the gimp-plugin-registry package, including the latest versions of all plugins. So if you&amp;rsquo;d like to see a new fance plugin in the package, or you have any other wish, please add a comment here, or even better, file a wishlist bug report against the package. Patches are welcome, git repository informations are listed below.
 gitweb git://git.recluse.de/debian/pkg-gimp-plugin-registry.git http://git.recluse.de/repos/debian/pkg-gimp-plugin-registry.git  Extra points if you find new/forked versions of plugins which are/were listed on registry.</description>
    </item>
    
    <item>
      <title>Why you should use gpsd over gypsy</title>
      <link>https://bzed.de/post/2009/02/why_you_should_use_gpsd_over_gypsy/</link>
      <pubDate>Tue, 24 Feb 2009 01:48:05 +0100</pubDate>
      
      <guid>https://bzed.de/post/2009/02/why_you_should_use_gpsd_over_gypsy/</guid>
      <description>While working on the Debian packages of navit I stumbled upon gypsy, as the libgypsy is used by navit to listen to notifications about location changes via D-Bus.
As maintainer of the gpsd package I started to wonder what the opinion of the gpsd developers about gypsy is - especially after reading that &amp;ldquo;Gypsy was designed to fix the numerous design flaws found in GPSD&amp;rdquo;. Well, here is their answer, which I support fully.</description>
    </item>
    
    <item>
      <title>Awesome calendar widget</title>
      <link>https://bzed.de/post/2009/02/awesome_calendar_widget/</link>
      <pubDate>Mon, 23 Feb 2009 01:18:25 +0100</pubDate>
      
      <guid>https://bzed.de/post/2009/02/awesome_calendar_widget/</guid>
      <description>One of the things I was missing in my favourite windowmanager awesome was a calendar widget. So I spent some minutes and coded it. Moving the mouse over the time widget will show a naughty popup with the current month, use your mouse buttons (and the shift key) to scroll trough the months. The only annoying thing was to figure out how to change the text of an existing notification: notification.</description>
    </item>
    
    <item>
      <title>Migrating to ikiwiki</title>
      <link>https://bzed.de/post/2009/02/migrating_to_ikiwiki/</link>
      <pubDate>Sun, 15 Feb 2009 03:31:57 +0100</pubDate>
      
      <guid>https://bzed.de/post/2009/02/migrating_to_ikiwiki/</guid>
      <description>Hi Planet Debian!
After being away from the planet for more than a year now, I&amp;rsquo;m finally back :) My plan to migrate to ikiwiki got postponed a lot of times as I had more important things to do. The migration of the content of my old wiki is still not complete, but I hope to finish that soon. Why I&amp;rsquo;ve migrated away from Dokuwiki? Mainly because I really prefer to have a git backend and being able to add content with vim.</description>
    </item>
    
  </channel>
</rss>
