<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>jodal.dev - debian</title>
    <subtitle>Personal blog of Stein Magnus Jodal</subtitle>
    <link rel="self" type="application/atom+xml" href="https://jodal.dev/tags/debian/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://jodal.dev"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2016-04-30T00:00:00+00:00</updated>
    <id>https://jodal.dev/tags/debian/atom.xml</id>
    <entry xml:lang="en">
        <title>March and April contributions</title>
        <published>2016-04-30T00:00:00+00:00</published>
        <updated>2016-04-30T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2016/04/30/march-and-april-contributions/"/>
        <id>https://jodal.dev/2016/04/30/march-and-april-contributions/</id>
        
        <summary type="html">&lt;p&gt;The following is a short summary of my open source work in March and April,
almost like in previous months, except that I haven’t spent as much time as
previously on Open Source the last two months.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>February contributions</title>
        <published>2016-03-01T00:00:00+00:00</published>
        <updated>2016-03-01T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2016/03/01/february-contributions/"/>
        <id>https://jodal.dev/2016/03/01/february-contributions/</id>
        
        <summary type="html">&lt;p&gt;The following is a short summary of my open source work in February, just like
&lt;a href=&quot;https://jodal.dev/2015/11/30/november-contributions/&quot;&gt;in&lt;/a&gt;
&lt;a href=&quot;https://jodal.dev/2016/01/01/december-contributions/&quot;&gt;previous&lt;/a&gt;
&lt;a href=&quot;https://jodal.dev/2016/02/01/january-contributions/&quot;&gt;months&lt;/a&gt;.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>A guide to poor API management</title>
        <published>2016-02-18T00:00:00+00:00</published>
        <updated>2016-02-18T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2016/02/18/guide-to-poor-api-management/"/>
        <id>https://jodal.dev/2016/02/18/guide-to-poor-api-management/</id>
        
        <summary type="html">&lt;p&gt;This is the story of libspotify, as experienced by a Spotify customer and
libspotify developer for six years.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>January contributions</title>
        <published>2016-02-01T00:00:00+00:00</published>
        <updated>2016-02-01T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2016/02/01/january-contributions/"/>
        <id>https://jodal.dev/2016/02/01/january-contributions/</id>
        
        <summary type="html">&lt;p&gt;The following is a short summary of my open source work in January, just like I
did back in &lt;a href=&quot;https://jodal.dev/2015/11/30/november-contributions/&quot;&gt;November&lt;/a&gt; and
&lt;a href=&quot;https://jodal.dev/2016/01/01/december-contributions/&quot;&gt;December&lt;/a&gt;.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>December contributions</title>
        <published>2016-01-01T00:00:00+00:00</published>
        <updated>2016-01-01T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2016/01/01/december-contributions/"/>
        <id>https://jodal.dev/2016/01/01/december-contributions/</id>
        
        <summary type="html">&lt;p&gt;The following is a short summary of my open source work in December, following
up on &lt;a href=&quot;https://jodal.dev/2015/11/30/november-contributions/&quot;&gt;my first report in November&lt;/a&gt;.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>November contributions</title>
        <published>2015-11-30T00:00:00+00:00</published>
        <updated>2015-11-30T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2015/11/30/november-contributions/"/>
        <id>https://jodal.dev/2015/11/30/november-contributions/</id>
        
        <summary type="html">&lt;p&gt;The following is a short summary of my open source work in November. My hope is
that keeping better track of what I’m doing will help me reflect on how I spend
my time, and help me to focus my efforts better.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Building ARM Debian packages with pbuilder</title>
        <published>2015-03-08T00:00:00+00:00</published>
        <updated>2015-03-08T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2015/03/08/building-arm-debs-with-pbuilder/"/>
        <id>https://jodal.dev/2015/03/08/building-arm-debs-with-pbuilder/</id>
        
        <summary type="html">&lt;p&gt;&lt;em&gt;The goal of this post is to help myself reproduce this pbuilder setup in the
future. If you find it useful too, then that’s great.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Building ARM packages on older ARM devices like the Raspberry Pi 1 is slow, so
I want to use a single amd64 machine to build Debian packages for all my target
platforms:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;amd64,&lt;/li&gt;
&lt;li&gt;i386,&lt;/li&gt;
&lt;li&gt;armel/ARMv4+ (e.g. Debian on Raspberry Pi 1),&lt;/li&gt;
&lt;li&gt;armhf/ARMv6+ (Raspbian), and&lt;/li&gt;
&lt;li&gt;armhf/ARMv7+ (e.g. Debian/Ubuntu on Raspberry Pi 2, Odroid C1, etc.).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Preferably, I want to build the packages for the current Debian stable, which
at the time of writing is wheezy, so that they’ll work for as many users as
possible.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Debian packaging of Mopidy</title>
        <published>2014-10-28T00:00:00+00:00</published>
        <updated>2014-10-28T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2014/10/28/debian-packaging/"/>
        <id>https://jodal.dev/2014/10/28/debian-packaging/</id>
        
        <summary type="html">&lt;p&gt;My first upload to Debian as a Debian Maintainer, Mopidy 0.19.4-3, landed in
Debian testing today, well in time for the upcoming freeze.&lt;/p&gt;
&lt;p&gt;The new version adjusts the LSB facilities the sysvinit script depends on, to
make sure that DNS lookups, DBus (used by Mopidy-MPRIS), and Avahi (used for
Zeroconf service publishing) are available before Mopidy starts.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Mopidy packaged in Debian and Ubuntu</title>
        <published>2013-12-28T00:00:00+00:00</published>
        <updated>2013-12-28T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2013/12/28/mopidy-packaged-in-debian-and-ubuntu/"/>
        <id>https://jodal.dev/2013/12/28/mopidy-packaged-in-debian-and-ubuntu/</id>
        
        <summary type="html">&lt;p&gt;Looking back to my last post from September, my goal was to have
the music server &lt;a rel=&quot;external&quot; href=&quot;https://mopidy.com/&quot;&gt;Mopidy&lt;/a&gt; packaged in Debian by the end
of the year and in Ubuntu in time for the 14.04 LTS release in April. As of
yesterday, Mopidy 0.17.0 is a part of &lt;a rel=&quot;external&quot; href=&quot;http://packages.debian.org/source/sid/mopidy&quot;&gt;Debian
unstable&lt;/a&gt; and &lt;a rel=&quot;external&quot; href=&quot;https://launchpad.net/ubuntu/+source/mopidy&quot;&gt;Ubuntu
trusty&lt;/a&gt;, just a few days after
Mopidy’s fourth anniversary on December 23.&lt;/p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>Pykka packaged in Debian and Ubuntu</title>
        <published>2013-09-03T00:00:00+00:00</published>
        <updated>2013-09-03T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://jodal.dev/2013/09/03/pykka-packaged-in-debian-and-ubuntu/"/>
        <id>https://jodal.dev/2013/09/03/pykka-packaged-in-debian-and-ubuntu/</id>
        
        <summary type="html">&lt;p&gt;The Python actor library &lt;a rel=&quot;external&quot; href=&quot;http://pykka.readthedocs.io/&quot;&gt;Pykka&lt;/a&gt; is now packaged as
&lt;code&gt;python-pykka&lt;/code&gt; and &lt;code&gt;python3-pykka&lt;/code&gt; in
&lt;a rel=&quot;external&quot; href=&quot;http://packages.debian.org/source/sid/python-pykka&quot;&gt;Debian unstable&lt;/a&gt; and
&lt;a rel=&quot;external&quot; href=&quot;https://launchpad.net/ubuntu/+source/python-pykka&quot;&gt;Ubuntu saucy&lt;/a&gt;, soon to be
Ubuntu 13.10. In a few more days, the packages will be probably be available in
Debian testing as well.&lt;/p&gt;</summary>
        
    </entry>
</feed>
