<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>Advogato blog for pabs3</title>
    <link>http://www.advogato.org/person/pabs3/</link>
    <description>Advogato blog for pabs3</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Wed, 19 Jun 2013 16:44:37 GMT</pubDate>
    <item>
      <pubDate>Sat, 23 Feb 2013 08:09:17 GMT</pubDate>
      <title>Inadequate software</title>
      <link>http://www.advogato.org/person/pabs3/diary.html?start=64</link>
      <guid>http://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/</guid>
      <description>&lt;p&gt;Just 168 of the 4961 packages (3%) I have installed are inadequate.
Unfortunately those packages collectively have 3440 inadequacies.
How much of the software on your system has these inadequacies?&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;broken symlinks&lt;/li&gt;
&lt;li&gt;missing copyright files&lt;/li&gt;
&lt;li&gt;obsolete conffiles&lt;/li&gt;
&lt;li&gt;Python modules not byte-compiled&lt;/li&gt;
&lt;li&gt;/bin and /sbin binaries requiring /usr/lib libraries&lt;/li&gt;
&lt;li&gt;undefined symbols.&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;You can find out today by installing Jakub Wilk's software,
which is appropriately named &lt;a href="http://jwilk.net/software/adequate" &gt;adequate&lt;/a&gt;.
It is now available in Debian experimental.
I recommend enabling the apt hook which notifies you when
software you are installing is inadequate.
Other ways of being notified when you are installing inadequate
software include &lt;a href="http://packages.debian.org/sid/apt-listbugs" &gt;apt-listbugs&lt;/a&gt; and &lt;a href="http://packages.debian.org/sid/debsecan" &gt;debsecan&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you are interested in software quality, &lt;a href="http://wiki.debian.org/qa.debian.org" &gt;Debian's QA activities&lt;/a&gt;
wiki page provides a good overview of the quality assurance activities
that are being worked on within the context of Debian.
If you want to provide better quality software for Debian, please
keep an eye on the &lt;a href="http://packages.qa.debian.org/" &gt;PTS&lt;/a&gt; pages for software you maintain.
You can also run various &lt;a href="http://wiki.debian.org/HowToPackageForDebian#Check_points_for_any_package" &gt;automated checks&lt;/a&gt; on your software
before you make new releases or upload them to the Debian archive.&lt;/p&gt;

&lt;p&gt;More people are needed to improve and expand upon Debian's existing
quality assurance activities and infrastructure.
Come join us today!&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Sat, 23 Feb 2013 08:09:17 GMT</pubDate>
      <title>23 Feb 2013</title>
      <link>http://www.advogato.org/person/pabs3/diary.html?start=63</link>
      <guid>http://bonedaddy.net/pabs3/log/template/</guid>
      <description>&lt;p&gt;[]: http://&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Mon, 3 Dec 2012 06:08:37 GMT</pubDate>
      <title>Debian on mobile devices</title>
      <link>http://www.advogato.org/person/pabs3/diary.html?start=62</link>
      <guid>http://bonedaddy.net/pabs3/log/2012/12/03/debian-mobile/</guid>
      <description>&lt;p&gt;
  &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/../../2012/12/03/debian-mobile/debian-sgs-large.jpg" &gt;
    &lt;img src="http://bonedaddy.net/pabs3/log/tags/advogato/../../2012/12/03/debian-mobile/240x320-debian-sgs-large.jpg" width="240" height="320" alt="Debian on Samsung Galaxy S" class="img" align="right"/&gt;&lt;/a&gt;
&lt;/p&gt;

&lt;p&gt;It is possible to put &lt;a href="http://wiki.debian.org/Mobile" &gt;Debian on smartphones&lt;/a&gt; like the Samsung Galaxy S:&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;Find a &lt;a href="http://replicant.us/" &gt;friendly Android distro&lt;/a&gt; that &lt;a href="http://replicant.us/supported-phones/" &gt;supports your device&lt;/a&gt;,
&lt;a href="http://redmine.replicant.us/projects/replicant/wiki#Installing-Replicant" &gt;install&lt;/a&gt; it with &lt;a href="http://packages.debian.org/sid/android-tools-fastboot" &gt;fastboot&lt;/a&gt; or &lt;a href="http://packages.debian.org/sid/heimdall-flash" &gt;heimdall&lt;/a&gt; and play around.&lt;/li&gt;
&lt;li&gt;Be sad that the proprietary &lt;a href="http://redmine.replicant.us/projects/replicant/wiki/S5PC110Bootloader" &gt;bootloader&lt;/a&gt; doesn't support dual boot.&lt;/li&gt;
&lt;li&gt;Reformat the "sdcard" as ext3 and install &lt;a href="http://wiki.debian.org/ChrootOnAndroid" &gt;Debian in a chroot&lt;/a&gt; on it.&lt;/li&gt;
&lt;li&gt;"Tether" your device via USB using the Android settings menu &amp;amp; add a default
route with &lt;a href="http://packages.debian.org/sid/android-tools-adb" &gt;adb&lt;/a&gt;: &lt;code&gt;adb shell ip add route default via 192.168.XXX.XXX&lt;/code&gt;.
Then use &lt;a href="http://redmine.replicant.us/projects/replicant/wiki/ReplicantUSBNetworking" &gt;one&lt;/a&gt; or &lt;a href="http://wiki.openmoko.org/wiki/Plug-and-Play_USB_Networking" &gt;other&lt;/a&gt; USB network script on your PC.&lt;/li&gt;
&lt;li&gt;Install OpenSSH, copy &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/../../../log/2012/12/03/debian-mobile/rc-local-commands.txt" &gt;some commands&lt;/a&gt; from the &lt;a href="http://gitorious.org/replicant/device_samsung_aries-common/blobs/raw/replicant-4.0/init.aries.usb.rc" &gt;usb.rc&lt;/a&gt; to /etc/rc.local
so that you will have a way to access your Debian system over USB.&lt;/li&gt;
&lt;li&gt;Hack up the &lt;a href="http://gitorious.org/replicant/kernel_samsung_aries/blobs/raw/replicant-4.0/usr/galaxysmtd_initramfs_files/init" &gt;initramfs&lt;/a&gt; to mount the sdcard partition and then
run the Debian init in the chroot instead of the Replicant init.&lt;/li&gt;
&lt;li&gt;Install some sort of graphical environment such as Enlightenment and nodm.&lt;/li&gt;
&lt;li&gt;Realise that the &lt;a href="http://gitorious.org/replicant/kernel_samsung_aries/blobs/raw/replicant-4.0/drivers/input/touchscreen/mxt224.c" &gt;touchscreen driver&lt;/a&gt; is buggy, which means
that udev and thus Xorg do not recognise it as an input device.
Find out that the same device seems to also be supported by a
&lt;a href="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob_plain;f=drivers/input/touchscreen/atmel_mxt_ts.c" &gt;different driver&lt;/a&gt; that is in Linux mainline. Boggle.&lt;/li&gt;
&lt;li&gt;Work around the buggy touchscreen driver by using x2x (&lt;a href="http://bugs.debian.org/435702" &gt;orphaned&lt;/a&gt;)
to send your laptop input devices over SSH to Xorg running on the phone.&lt;/li&gt;
&lt;li&gt;Click through the Enlightenment startup wizard, work around desktop-base
not supporting E17 and install a touchscreen-friendly app like intone.&lt;/li&gt;
&lt;li&gt;Marvel at the speed and flashyness of Enlightenment even though it does
not use OpenGL because there are no open drivers for PowerVR devices.&lt;/li&gt;
&lt;li&gt;Take a photo and blog about it to create some bzzt.&lt;/li&gt;
&lt;li&gt;Get depressed about the rediculousness of all that and
proceed to drinking over 9000 litres of beer.&lt;/li&gt;
&lt;li&gt;Think about just using Replicant plus f-droid.&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;Linux mainline doesn't run on any of the &lt;a href="http://wiki.debian.org/Mobile#People" &gt;mobile devices I have&lt;/a&gt;.
It probably doesn't run on any of the mobile devices you have either.
There has been some effort by the OpenMoko community to &lt;a href="http://wiki.openmoko.org/wiki/Kernel/Upstreaming" &gt;merge&lt;/a&gt;
the gta02 kernel patches but it is not yet complete.
I doubt Samsung will spend money on merging support for old devices
obsoleted by more recent devices.
There is Linaro but they are focused on things the hardware vendors
pay them for and probably would not have the resources anyway.
Therefore I would guess the timeframe for supporting the OpenMoko FreeRunner
and the Samsung Galaxy S in Linux mainline is between many years and never.
For better or worse, the Debian Linux kernel maintainers &lt;a href="http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines" &gt;prefer&lt;/a&gt;
not to include non-mainline stuff and Debian as a whole generally
prefers to include one copy of each package instead of &lt;a href="http://gitorious.org/search?q=replicant+kernel" &gt;9&lt;/a&gt;.
The procedures I documented above are not a great way to support
mobile devices at all and could break at any moment anyway.
So everyone, please &lt;a href="http://kernelnewbies.org/" &gt;become a kernel developer&lt;/a&gt; and help
&lt;a href="http://kernelnewbies.org/UpstreamMerge" &gt;merge&lt;/a&gt; all of the many many versions of Android Linux
into Linux mainline so that you can have your
&lt;a href="http://distrowatch.com/popularity" &gt;favourite distribution&lt;/a&gt; on your devices.&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Mon, 29 Oct 2012 05:08:58 GMT</pubDate>
      <title>Some thoughts on using Debian</title>
      <link>http://www.advogato.org/person/pabs3/diary.html?start=61</link>
      <guid>http://bonedaddy.net/pabs3/log/2012/10/29/thoughts-on-debian-testing/</guid>
      <description>&lt;p&gt;I'm currently running Debian's rolling release (aka "testing") on my main
machine and have added some stuff to make that nicer.&lt;/p&gt;

&lt;p&gt;First thing I have is configuration and package management.
Since I have relatively few machines, I am using a metapackage per machine that
installs some configuration files with changes that I want.
The metapackages depend on packages that I need installed so that I can mark
all other packages as being automatically installed.
The metapackages are also useful for documenting why I have things installed.
It depends on things like task-laptop from tasksel, hardware support packages,
the GUI I use, games I play often and so on.
My laptop does not have a CD/DVD drive so I have some metapackages to fool
apt into ignoring dependencies on CD/DVD related packages I don't need.
I'm building the metapackages using equivs-build and a small Makefile.
I use the File: header supported by equivs-build for installing config files.
I have popcon installed and enabled but I don't want it to leak the names of the
metapackages so I have added a prefix to my metapackages and &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/#popp" &gt;modified&lt;/a&gt;
the popcon cron job to remove anything containing that prefix.
I also don't want apt to ever remove the metapackages so I mark them as
&lt;code&gt;Important: yes&lt;/code&gt; and configure apt to &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/#norm" &gt;never autoremove&lt;/a&gt; them.&lt;/p&gt;

&lt;p&gt;
  &lt;a/&gt;
&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;--- /etc/cron.daily/popularity-contest~
+++ /etc/cron.daily/popularity-contest
@@ -71,8 +71,8 @@
 # try to post the report through http POST
 if [ "$SUBMITURLS" ] &amp;amp;&amp;amp; [ "yes" = "$USEHTTP" ]; then
     for URL in $SUBMITURLS ; do
-   if grep -v myprefix- $POPCON | setsid /usr/share/popularity-contest/popcon-upload \
-       -u $URL 2&amp;gt;/dev/null ; then
+   if setsid /usr/share/popularity-contest/popcon-upload \
+       -u $URL -f $POPCON 2&amp;gt;/dev/null ; then
        SUBMITTED=yes
    else
        logger -t popularity-contest "unable to submit report to $URL."
@@ -94,7 +94,7 @@
        echo "MIME-Version: 1.0"
        echo "Content-Type: text/plain"
        echo
-       grep -v myprefix- $POPCON
+       cat $POPCON
    ) | do_sendmail
    SUBMITTED=yes
     else
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;&lt;a/&gt;
/etc/apt/apt.conf.d/99metapackages:&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;APT::NeverAutoRemove { "^myprefix-.*";} ;
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;I am using Raphael Geissert's &lt;a href="http://http.debian.net/" &gt;mirror redirector&lt;/a&gt; in order to automatically
use up-to-date and hopefully non-broken mirrors.
Unfortunately this often causes apt to complain about hash sum mismatches
and then proceed to &lt;a href="http://bugs.debian.org/624122" &gt;forget&lt;/a&gt; about all packages.
I work around this by always running apt-get update in a loop until it succeeds.&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;while ! apt-get update ; do sleep 1m; done
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;A lot of the time I need to install packages from outside of testing.
So &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/#sources" &gt;my sources.list&lt;/a&gt; contains lines for testing, unstable and experimental.
I have &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/#pins" &gt;some apt pinning&lt;/a&gt; so that by default I only have packages from
testing but if I manually upgrade some packages to unstable or experimental,
then I will get upgrades within that suite until those packages migrate down to
unstable or testing.
The apt pinning needs priorities between 1000 and 500 for this to work nicely.
I also &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/#pinp" &gt;pin some things&lt;/a&gt; like lintian, debian-policy and devref
to unstable/experimental since having old versions of those is not useful.&lt;/p&gt;

&lt;p&gt;&lt;a/&gt;
/etc/apt/sources.list:&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;# testing
deb http://security.debian.org/ testing/updates main contrib non-free
deb-src http://security.debian.org/ testing/updates main contrib non-free
deb http://http.debian.net/debian/ testing main contrib non-free
deb-src http://http.debian.net/debian/ testing main contrib non-free
# unstable
deb http://http.debian.net/debian/ unstable main contrib non-free
deb-src http://http.debian.net/debian/ unstable main contrib non-free
# experimental
deb http://http.debian.net/debian/ experimental main contrib non-free
deb-src http://http.debian.net/debian/ experimental main contrib non-free
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;&lt;a/&gt;
/etc/apt/preferences.d/system:&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;Package: *
Pin: release a=testing
Pin-Priority: 800

Package: *
Pin: release a=unstable
Pin-Priority: 700

Package: *
Pin: release a=experimental
Pin-Priority: 600
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;&lt;a/&gt;
/etc/apt/preferences.d/packages:&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;Package: lintian
Pin: release a=unstable
Pin-Priority: 900

Package: lintian
Pin: release a=experimental
Pin-Priority: 910

Package: debian-policy
Pin: release a=unstable
Pin-Priority: 999

Package: developers-reference
Pin: release a=unstable
Pin-Priority: 999
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;I have a few configuration files and a cron job to make all programs dump
core files when they crash so that I can file bugs, even for random crashes
that are not easy to reproduce.
I enabled some kernel settings with &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/#coresysctl" &gt;sysctl&lt;/a&gt;,
lifted some &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/#corelimits" &gt;security limits&lt;/a&gt; to enable core dumps,
and added &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/#corecron" &gt;a cron job&lt;/a&gt; to delete old core dumps and
notify me of new core dumps.
In my shell configuration I also turn on &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/#malloc" &gt;two glibc options&lt;/a&gt; to cause
programs to crash when they have improper memory management.
I also have a second machine I use for bug discovery where I have lots of stuff
installed and everything apt pinned in the opposite way; experimental &amp;gt; unstable &amp;gt; testing.
When I have time I use this machine to do testing of packages I use, classes of 
packages that I care about (such as games) and sometimes packages I do not use.&lt;/p&gt;

&lt;p&gt;&lt;a/&gt;
/etc/sysctl.d/corefiles.conf:&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;fs.suid_dumpable = 1
kernel.core_uses_pid = 1
kernel.core_pattern = /var/cache/corefiles/core-%p-%u-%g-%s-%t-%h-%e
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;&lt;a/&gt;
/etc/security/limits.d/corefiles.conf:&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;*              soft    core            unlimited
*              hard    core            unlimited
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;&lt;a/&gt;
/etc/cron.daily/corefiles:&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;#!/bin/sh
mkdir -p /var/cache/corefiles
chmod 2777 /var/cache/corefiles
if [ $(find /var/cache/corefiles -mtime +100 -a ! -type d | wc -l) -gt 0 ]; then
    echo deleting:
    find /var/cache/corefiles -mtime +100 -a ! -type d
    find /var/cache/corefiles -mtime +100 -a ! -type d -print0 | xargs -0 rm -f
fi
if [ $(find /var/cache/corefiles ! -type d | wc -l) -gt 0 ] ; then
    echo still present:
    find /var/cache/corefiles ! -type d
fi
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;&lt;a/&gt;
~/.bash.d/malloc:&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;export MALLOC_CHECK_=2
export MALLOC_PERTURB_=$(($RANDOM % 255 + 1))
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;I unfortunately &lt;a href="http://wiki.debian.org/PaulWise#contribnonfree" &gt;need some packages from contrib/non-free&lt;/a&gt;, so
I have a cron job to let me know when I accidentally install new packages from
contrib/non-free.&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;@daily diffcmdoutput ~/.cache/non-free-contrib aptitude search ~i~snon-free\|~i~scontrib
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;I backup my dpkg package selections and debconf databases.&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;@daily diffcmdoutput ~/backup/packages dpkg --get-selections
@daily diffcmdoutput ~/backup/config debconf-get-selections 2&amp;gt; /dev/null
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;I notify myself of changes to the list of new packages so that I can review them,
install any useful/interesting ones and tell aptitude to forget them all.&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;@daily diffcmdoutput ~/.cache/new aptitude search ~N
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;I notify myself of changes to the list of packages I have installed that are not
up-to-date packages from testing.
This helps me catch packages removed from testing/unstable/etc that I use.&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;@daily diffcmdoutput ~/.cache/apt-show-versions sh -c "apt-show-versions | grep -v '/testing uptodate'"
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;I notify myself of packages that I maintain that are having issues migrating to testing.
I considered doing the same for teams I am involved in but they aren't particularly
functional teams so there would be a lot of noise.&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;@daily grep-excuses 'Paul Wise'
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;I notify myself of RC bugs that apply to testing and are installed.
The list is so long that it just makes me depressed instead of
motivated to help fix RC bugs so I only notify myself of changes.
Even then I rarely do anything other than delete the notifications.
If you are looking for ways to help Debian, fixing RC bugs is a great choice.&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;@daily diffcmdoutput ~/.cache/rcbugs rc-alert -d T --exclude-tags IP+MR
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;I notify myself of packages that are orphaned or need a new maintainer.
There are usually so many packages in this list that it is not useful,
so I only notify myself of changes to the list.
I rarely adopt packages because I feel overloaded already.
If you are looking for ways to help Debian, adopting packages is a good choice.&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;@daily wnpp-alert --diff
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;One of my packages is for interacting with servers on the Internet,
so I need to run tests periodically to ensure the package works.
I do that with a simple Makefile but maybe I need to move to
autopkgtest, need to find out if it saves data between runs first.&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;@monthly cd ~/devel/debian/tests ; make
&lt;/code&gt;
&lt;/pre&gt;

&lt;p&gt;I install debsecan so that I get notified of security updates in unstable
and new security issues that are not fixed yet.
The way debsecan works is that it notifies about changes in security issues
and updates and also includes a full list of all known unfixed  issues.
I generally install security updates from unstable when I see them.
The list of unchanged issues is so long that it makes me wonder
how many times I've been cracked already.
The oldest issue goes back to 2002 but most of them are 2010 or later.
The various parts of WebKit are by far the worst security offenders.
I don't bother with the white-listing functionality due to the 
quantity of security issues and because it isn't possible to
add a comment about each white-list item.
If you want to get involved with the security team, &lt;a href="http://security-tracker.debian.org/tracker/data/report" &gt;reporting&lt;/a&gt; issues
with the data in the security tracker is a good idea.&lt;/p&gt;

&lt;p&gt;I subscribe to the &lt;a href="https://ftp-master.debian.org/rss/" &gt;ftpmaster RSS feeds&lt;/a&gt; for new and removed packages
to keep up to date with changes in the archive.&lt;/p&gt;

&lt;p&gt;A lot of the above applies to running systems based on Debian stable too.
If you have any other thoughts about running Debian systems, please blog about them.
The &lt;code&gt;diffcmdoutput&lt;/code&gt; command used above is a simple shell script:&lt;/p&gt;

&lt;pre&gt;
  &lt;code&gt;#!/bin/sh
cache="$1"
shift
temp="$(mktemp "$cache"XXXXXXXXXXXXXX)"
"$@" &amp;gt; "$temp"
diff --unified "$cache" "$temp"
mv --force "$temp" "$cache"
&lt;/code&gt;
&lt;/pre&gt;</description>
    </item>
    <item>
      <pubDate>Thu, 30 Aug 2012 08:09:16 GMT</pubDate>
      <title>Ponds as time travel devices</title>
      <link>http://www.advogato.org/person/pabs3/diary.html?start=60</link>
      <guid>http://bonedaddy.net/pabs3/log/2012/08/30/space-invader-pond/</guid>
      <description>&lt;p&gt;I firmly believe that this pond is a time travel device:&lt;/p&gt;

&lt;p&gt;
  &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/../../2012/08/30/space-invader-pond/space-invader-pond.jpg" &gt;
    &lt;img src="http://bonedaddy.net/pabs3/log/tags/advogato/../../2012/08/30/space-invader-pond/640x480-space-invader-pond.jpg" width="640" height="480" alt="Space invader pond" class="img"/&gt;&lt;/a&gt;
&lt;/p&gt;

&lt;p&gt;The proof is in &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/../../../log/2012/08/30/space-invader-pond/space-invader-pond.wav" &gt;this recording&lt;/a&gt; I made&lt;sup&gt;&lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/#foot1" &gt;1&lt;/a&gt;&lt;/sup&gt;.
At minimum, clearly there is some sort of quantum entanglement with
&lt;a href="http://en.wikipedia.org/wiki/Space_Invaders" &gt;computer games from the 70s&lt;/a&gt; going on.&lt;/p&gt;

&lt;p&gt;&lt;a/&gt;
&lt;small&gt;1. Folks may want to use this recording in free software.
To the extent possible under law, I have &lt;a href="http://creativecommons.org/publicdomain/zero/1.0/" &gt;waived&lt;/a&gt; all copyright
and related or neighboring rights to this work. The frogs have too.
An &lt;a href="http://bonedaddy.net/pabs3/log/tags/advogato/../../../about/#contact" &gt;email&lt;/a&gt; or a link to this page would be appreciated though.&lt;/small&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Thu, 26 Apr 2012 05:09:02 GMT</pubDate>
      <title>What happens when a Debian derivative shuts down?</title>
      <link>http://www.advogato.org/person/pabs3/diary.html?start=59</link>
      <guid>http://bonedaddy.net/pabs3/log/2012/04/26/when-a-distro-dies/</guid>
      <description>&lt;p&gt;Over the past months we have seen the end of two Debian derivatives.
In January the news came that Junta de Extremadura (Spain) were abandoning
the development of &lt;a href="http://wiki.debian.org/Derivatives/Census/LinEx" &gt;LinEx&lt;/a&gt; and &lt;a href="http://lists.debian.org/20120206155102.GA25296@upsilon.cc" &gt;switching&lt;/a&gt; to Debian itself.
Early in March the Debian derivatives census scripts noted that the
&lt;a href="http://wiki.debian.org/Derivatives/Census/Vanillux" &gt;Vanillux&lt;/a&gt; apt repository was down.
Fabrice Quenneville then &lt;a href="http://lists.debian.org/debian-derivatives/2012/03/msg00002.html" &gt;confirmed&lt;/a&gt; that he had to put a hold on
the Vanillux project due to the cost of bandwidth and servers.
In addition the future of &lt;a href="http://wiki.debian.org/Derivatives/Census/StormOS" &gt;StormOS&lt;/a&gt; is in doubt after
&lt;a href="http://illumian.org/" &gt;Illumian&lt;/a&gt; was created.
StormOS is a port of Debian to the OpenSolaris kernel and Illumian is similar
but uses only apt/dpkg and repackages everything else.&lt;/p&gt;

&lt;p&gt;The LinEx page in the &lt;a href="http://wiki.debian.org/Derivatives/Census" &gt;Debian derivatives census&lt;/a&gt; did not reveal much
information about the project that would have been useful to Debian, in
particular it does not list any apt repositories.
As a result it is quite hard to say what has potentially been lost.
&lt;a href="http://lists.debian.org/20120101125915.GA28172@pryan.ekaia.org" &gt;Two&lt;/a&gt; &lt;a href="http://lists.debian.org/debian-project/2012/01/msg00007.html" &gt;mails&lt;/a&gt; from people close to or involved in the project
indicate that much of the LinEx distribution was already merged into Debian.
It is probably safe to say that everything of value has been merged into Debian,
including at least one of the developers involved in LinEx.&lt;/p&gt;

&lt;p&gt;Vanillux was a small distribution with few developers according to the Google
caches of their website.
If we look at the &lt;a href="http://dex.alioth.debian.org/census/Vanillux/patches/" &gt;patches&lt;/a&gt; created by the derivatives census scripts,
we can see that the 5 source packages that were possibly derived from Debian
source packages were simply imported from Christian Marillat's repository of
non-free, patented, legally restricted and multimedia-related packages.
The patches indicate that 3 source packages were forked from Debian and that
2 source packages were done from scratch.
The forked packages seem to be mainly about enabling support for proprietary and
patented codecs in several programs.
This is a surprisingly small number of altered/differing packages, so what else
could Vanillux folks have been working on?
It appears that there were &lt;a href="http://dex.alioth.debian.org/census/Vanillux/sources.new" &gt;12 new source packages&lt;/a&gt; that were not derived
from Debian source packages.
These appear to be mainly multimedia-related packages, one font imported from
an Ubuntu PPA, some syslinux themes and a metapackage.
The multimedia packages are all from Christian Marillat's repository.
The Debian multimedia team is working hard on bringing multimedia related
software to Debian and welcomes &lt;a href="http://wiki.debian.org/DebianMultimedia/Join" &gt;help&lt;/a&gt; with that.
The font (Cantarell) is now in Debian under a different source package name.
The metapackage appears to be very similar to from the ubuntu-meta source
package from Ubuntu that uses germinate.
So at first glance, the contribution of Vanillux to the world of Linux
distributions appears to be in the area of artwork and package selection.
The artwork produced is basically Vanillux branding and is thus not usable by
Debian, although we would &lt;a href="http://www.debian.org/News/2012/20120213" &gt;like&lt;/a&gt; more artists involved in Debian.
The meta-package is not easily useful to Debian since we use a different
mechanism for our task packages and our task packages have already been updated
for the GNOME 3 transition.
Still, the amount of difference between to source packages is relatively small.
So, what else?
Perusing the &lt;a href="http://dex.alioth.debian.org/census/Vanillux/diff_source_packages" &gt;diff&lt;/a&gt; between the list of source packages exposed by the
Packages and Sources files, I noted that a number of binary packages in the
Packages files reference source packages not listed in the Sources files.
When I saw picasa in that list, it occurred to me that Vanillux might have
directly imported some binary packages without their corresponding source
packages.
Perusing their &lt;a href="http://dex.alioth.debian.org/census/Vanillux/apt/lists/" &gt;apt metadata&lt;/a&gt; confirms that they have imported some
binary packages of non-free software directly from vendors. These include
Google Desktop, Opera, Picasa and VirtualBox 3.2.
The rest of the packages in the diff appear to be caused by some sort of
issue with the import process from Debian and other apt repos.
Most of the above could be achieved by adding some &lt;a href="http://wiki.debian.org/UnofficialRepositories" &gt;external commerical
repositories&lt;/a&gt; to a normal Debian system or by merging some of those
repositories (such as the &lt;a href="http://lists.debian.org/op.ux624yia799kd0@linux.site" &gt;Opera&lt;/a&gt; one) into Debian.&lt;/p&gt;

&lt;p&gt;The interesting thing about the Debian derivatives census is that it allows us
to perform analyses like these and figure out what patches and packages we might
like to integrate into Debian. In this way we can salvage some of the value of
our derivatives if they abandon ship.&lt;/p&gt;

&lt;p&gt;If you have any ideas or code for improving the census or are running a Debian
derivative, please join us at the &lt;a href="http://wiki.debian.org/DerivativesFrontDesk" &gt;Debian derivatives frontdesk&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Fri, 16 Mar 2012 06:09:00 GMT</pubDate>
      <title>Report from the recent Debian bug squashing party in Perth</title>
      <link>http://www.advogato.org/person/pabs3/diary.html?start=58</link>
      <guid>http://bonedaddy.net/pabs3/log/2012/03/16/perth-bsp-report/</guid>
      <description>&lt;p&gt;We &lt;a href="http://wiki.debian.org/BSP/2012/03/au/Perth" &gt;recently&lt;/a&gt; held a Debian bug squashing party (BSP) in Perth,
Western Australia.
Over the weekend we had about 10 or so people show up to participate, learn
about fixing bugs in Debian and try to fix some.
The BSP co-incided with a weekend heat wave with temperatures reaching 38&#xB0;C and
the venue lacked air conditioning.
Most of the attendees were new to Debian development but were Debian users.
Our focus was on release critical bugs highlighted by &lt;code&gt;rc-alert&lt;/code&gt; and the
&lt;a href="http://udd.debian.org/bugs.cgi" &gt;UDD bugs list&lt;/a&gt;, but we also discussed IPv6 bugs in CUPS and some bugs
that were affecting UCC infrastructure.
The UCC president also worked on fixing their door-locking system, replacing
the broken system based on an ancient modem with an Arduino board.
We managed to fix, work on or investigate 12 or more bugs.
I was hoping we would get through more, but the weather and the average
experience level conspired against us.
After we were done on Sunday a few of us went down to the local pub to have a
meal, a beer and some geeky conversation.
All in all we had a good time and got some bugs fixed.&lt;/p&gt;

&lt;p&gt;The UCC president seemed to be keen on doing another BSP, hopefully we can do
another one before the freeze happens.
There were a few people who missed the BSP so it would be good to give them a
chance to work on some bugs.&lt;/p&gt;

&lt;p&gt;Thanks go to the &lt;a href="http://www.ucc.asn.au/" &gt;UCC&lt;/a&gt; folks for the venue and to &lt;a href="http://www.plug.org.au/" &gt;PLUG&lt;/a&gt; folks
for helping with organisation and promotion of the event.&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Tue, 28 Feb 2012 04:08:03 GMT</pubDate>
      <title>Debian/Ubuntu games screenshot party results</title>
      <link>http://www.advogato.org/person/pabs3/diary.html?start=57</link>
      <guid>http://bonedaddy.net/pabs3/log/2012/02/28/debian-ubuntu-games-party-results/</guid>
      <description>&lt;p&gt;The &lt;a href="http://wiki.debian.org/Games/Team" &gt;Debian/Ubuntu games team&lt;/a&gt; recently organised a half-day
&lt;a href="http://wiki.debian.org/Games/Parties/Screenshots" &gt;screenshots&lt;/a&gt; &lt;a href="http://wiki.debian.org/Games/Parties" &gt;party&lt;/a&gt; for creating screenshots for all the
games that are available in Debian/Ubuntu.&lt;/p&gt;

&lt;p&gt;Unfortunately, only 5 people participated in the screenshots party, I had hoped
that we would get more folks turn up. Only one of those was not already involved
in the games team and that one person found out via our spam on the
#debian-mentors IRC channel. This means that most of our &lt;a href="http://wiki.debian.org/Games/Parties/Screenshots#party-2012-02-26" &gt;promotion&lt;/a&gt;
of the event was ineffective. Hopefully for future games &lt;a href="http://wiki.debian.org/Games/Parties" &gt;parties&lt;/a&gt; we can
improve this, please &lt;a href="http://wiki.debian.org/Games/Team" &gt;let us know&lt;/a&gt; if you have any ideas about that.&lt;/p&gt;

&lt;p&gt;We also had 7 other people on the channel during the party lurking, discussing
and or working on other things, in particular Ben Armstrong was working on a
games live CD.&lt;/p&gt;

&lt;p&gt;Over the 7 hours of the party, we uploaded 100 screenshots for 40 different
packages. Of the packages, 2 are available only in Debian (auralquiz, cutechess),
one is available only in Ubuntu (plasma-widget-tictactoe) and the rest are
available in both. I think we got quite a bit done for such a small group.&lt;/p&gt;

&lt;p&gt;Some of us could not resist filing &lt;a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-devel-games@lists.debian.org;tag=party-screenshots-2012-02-26" &gt;some bugs&lt;/a&gt; on packages that had
issues preventing or delaying us from taking screenshots. I also suggested to
one maintainer that his package (acm4) be removed from Debian, since it is
obsoleted by acm and unusable.&lt;/p&gt;

&lt;p&gt;If you want to play some games, check out &lt;a href="http://packages.debian.org/sid/goplay" &gt;goplay&lt;/a&gt;, which is a tool for
browsing available games using &lt;a href="http://debtags.debian.net/" &gt;debtags&lt;/a&gt; that displays screenshots from
the &lt;a href="http://packages.debian.org/sid/games-thumbnails" &gt;games-thumbnails&lt;/a&gt; package, which has just been updated with the
screenshots created during the party. goplay needs some more development, if you
would like to help out with that, you would be most welcome.&lt;/p&gt;

&lt;p&gt;If you are interested to see our screenshots, they are all on the
screenshots.debian.net website and the packages are
&lt;a href="http://screenshots.debian.net/package/auralquiz" &gt;auralquiz&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/cardstories" &gt;cardstories&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/londonlaw" &gt;londonlaw&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/cube2font" &gt;cube2font&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/ardentryst" &gt;ardentryst&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/cutechess" &gt;cutechess&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/pianobooster" &gt;pianobooster&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/emacs-chess" &gt;emacs-chess&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/xye" &gt;xye&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/flare" &gt;flare&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/tmw" &gt;tmw&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/garden-of-coloured-lights" &gt;garden-of-coloured-lights&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/flight-of-the-amazon-queen" &gt;flight-of-the-amazon-queen&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/geekcode" &gt;geekcode&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/glpeces" &gt;glpeces&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/fofix" &gt;fofix&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/unknown-horizons" &gt;unknown-horizons&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/klickety" &gt;klickety&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/polygen" &gt;polygen&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/tictactoe" &gt;tictactoe&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/xscreensaver-screensaver-dizzy" &gt;xscreensaver-screensaver-dizzy&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/goban-original-games" &gt;goban-original-games&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/xjokes" &gt;xjokes&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/mudlet" &gt;mudlet&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/xabacus" &gt;xabacus&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/xtux-client" &gt;xtux-client&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/connectagram" &gt;connectagram&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/crystalspace" &gt;crystalspace&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/pescetti" &gt;pescetti&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/purity-ng" &gt;purity-ng&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/qstat" &gt;qstat&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/slashem" &gt;slashem&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/sudoku" &gt;sudoku&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/minetest" &gt;minetest&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/xscavenger" &gt;xscavenger&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/plasma-widget-tictactoe" &gt;plasma-widget-tictactoe&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/xbomb" &gt;xbomb&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/xfrisk" &gt;xfrisk&lt;/a&gt;,
&lt;a href="http://screenshots.debian.net/package/xpilot-ng" &gt;xpilot-ng&lt;/a&gt;
and &lt;a href="http://screenshots.debian.net/package/xsok" &gt;xsok&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Fri, 3 Feb 2012 04:37:24 GMT</pubDate>
      <title>Debian/Ubuntu games screenshot party!</title>
      <link>http://www.advogato.org/person/pabs3/diary.html?start=56</link>
      <guid>http://bonedaddy.net/pabs3/log/2012/02/03/debian-ubuntu-games-screenshot-party/</guid>
      <description>&lt;p&gt;Have you ever wondered how to start getting involved in Debian/Ubuntu?
Do you enjoy discovering new games and playing them?
You might want to come to the &lt;a href="http://deb.li/gamesparty" &gt;games screenshot party&lt;/a&gt;!
We hope that the party will be a fun, easy, low-commitment way to get involved.&lt;/p&gt;

&lt;p&gt;The &lt;a href="http://wiki.debian.org/Games/Team" &gt;Debian/Ubuntu games team&lt;/a&gt; is organising a half-day &lt;a href="http://wiki.debian.org/Games/Parties/Screenshots" &gt;screenshots&lt;/a&gt;
&lt;a href="http://wiki.debian.org/Games/Parties" &gt;party&lt;/a&gt; on the weekend of 25th-26th February for creating screenshots for
all the games that are available in Debian/Ubuntu.&lt;/p&gt;

&lt;p&gt;If you are interested in attending, please add your availability to the poll
linked from the &lt;a href="http://deb.li/gamesparty" &gt;announcement&lt;/a&gt; so that we can get some idea of
attendance and when is a good time for the people who are interested.&lt;/p&gt;

&lt;p&gt;Look forward to lots of game playing, screenshots and a merry time,
hope to see you all there!&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Thu, 2 Feb 2012 09:35:51 GMT</pubDate>
      <title>Debian bug squashing party in Perth</title>
      <link>http://www.advogato.org/person/pabs3/diary.html?start=55</link>
      <guid>http://bonedaddy.net/pabs3/log/2012/02/02/debian-bsp-in-perth/</guid>
      <description>&lt;p&gt;There is a Debian &lt;a href="http://wiki.debian.org/BSP" &gt;bug squashing party&lt;/a&gt; (BSP) in Perth, Western Australia
being &lt;a href="http://wiki.debian.org/BSP/2012/03/au/Perth" &gt;organised&lt;/a&gt; for the weekend of 9-11th of March.
It will be held at the University of Western Australia in loft of the
&lt;a href="http://www.ucc.asn.au/" &gt;University Computer Club&lt;/a&gt; (UCC) in the student guild building.
Sadly it is a bit far to travel for the majority of Debian contributors
(and they probably wouldn't enjoy being &lt;a href="http://answers.yahoo.com/question/index?qid=20080706031932AAoj4jk" &gt;upside&lt;/a&gt; &lt;a href="http://wiki.answers.com/Q/Why_don%27t_people_in_Australia_feel_like_there_upside_down" &gt;down&lt;/a&gt;) but
hopefully we can attract some locals and get them addicted to fixing bugs
and contributing to Debian and the FLOSS community in general.&lt;/p&gt;

&lt;p&gt;Come one, come all, lets squish some bugs and get Debian into better shape for
the &lt;a href="http://lists.debian.org/debian-devel-announce/2012/01/msg00009.html" &gt;coming freeze&lt;/a&gt; in June for the release of Debian 7 (wheezy).&lt;/p&gt;

&lt;p&gt;Thanks go to the &lt;a href="http://www.ucc.asn.au/" &gt;UCC&lt;/a&gt; folks for the venue and to &lt;a href="http://www.plug.org.au/" &gt;PLUG&lt;/a&gt; folks
for helping with organisation and promotion of the event.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
