Generated.

[homepage.git] / blog / archive / 2013 / 11 / 11.rss

<?xml version="1.0" encoding="ISO-8859-1"?>
<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
        <channel>
                <title>Petter Reinholdtsen - Entries from November 2013</title>
                <description>Entries from November 2013</description>
                <link>http://people.skolelinux.org/pere/blog/</link>

        
        <item>
                <title>RSS-kilde for fritekstsøk i offentlige anbud hos Doffin</title>
                <link>http://people.skolelinux.org/pere/blog/RSS_kilde_for_friteksts_k_i_offentlige_anbud_hos_Doffin.html</link>        
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/RSS_kilde_for_friteksts_k_i_offentlige_anbud_hos_Doffin.html</guid>
                <pubDate>Fri, 22 Nov 2013 13:40:00 +0100</pubDate>
                <description>&lt;p&gt;I fjor sommer lagde jeg en
&lt;a href=&quot;http://people.skolelinux.org/pere/blog/SQL_database_med_anbud_publisert_p__Doffin.html&quot;&gt;offentlig
tilgjengelig SQL-database over offentlig anbud&lt;/a&gt; basert på skraping
av HTML-data fra Doffin.  Den har stått og gått siden da, og har nå
ca. 28000 oppføringer.  Jeg oppdaget da jeg tittet innom at noen
oppføringer var ikke blitt med, antagelig på grunn av at de fikk
tildelt sekvensnummer i Doffin en godt stund før de ble publisert,
slik at min nettsideskraper som fortsatte skrapingen der den slapp
sist ikke fikk dem med seg.  Jeg har fikset litt slik at skraperen nå
ser litt tilbake i tid for å se om den har gått glipp av noen
oppføringer, og har skrapet på nytt fra midten av september 2013 og
fremover.  Det bør dermed bli en mer komplett database for kommende
måneder.  Hvis jeg får tid skal jeg forsøke å skrape &quot;glemte&quot; data fra
før midten av september 2013, men tør ikke garantere at det blir
prioritert med det første. &lt;/p&gt;

&lt;p&gt;Men målet med denne bloggposten er å vise hvordan denne
Doffin-databasen kan brukes og integreres med en RSS-leser, slik at en
kan la datamaskinen holde et øye med Doffin-annonseringer etter
nøkkelord.  En kan lage sitt eget søk ved å besøke
&lt;ahref=&quot;https://classic.scraperwiki.com/docs/api?name=norwegian-doffin#sqlite&quot;&gt;API-et
hos Scraperwiki&lt;/a&gt;, velge format rss2 og så legge inn noe ala dette i
&quot;query in SQL&quot;:&lt;/p&gt;

&lt;p&gt;&lt;pre&gt;
select title, scrapedurl as link, abstract as description,
       publishdate as pubDate from &#39;swdata&#39;
   where abstract like &#39;%linux%&#39; or title like &#39;%linux%&#39;
   order by seq desc limit 20
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;Dette vil søke opp alle anbud med ordet linux i oppsummering eller
tittel.  En kan lage mer avanserte søk hvis en ønsker det.  URL-en som
dukker opp nederst på siden kan en så gi til sin RSS-leser (jeg bruker
akregator selv), og så automatisk få beskjed hvis det dukker opp anbud
med det aktuelle nøkkelordet i teksten.  Merk at kapasiteten og
ytelsen hos Scraperwiki er begrenset, så ikke be RSS-leseren hente ned
oftere enn en gang hver dag.&lt;/p&gt;

&lt;p&gt;Du lurer kanskje på hva slags informasjon en kan få ut fra denne
databasen.  Her er to RSS-kilder, med søkeordet
&quot;&lt;a href=&quot;https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&amp;name=norwegian-doffin&amp;query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20&#39;swdata&#39;%0A%20%20%20where%20abstract%20like%20&#39;%25linux%25&#39;%20or%20title%20like%20&#39;%25linux%25&#39;%0A%20%20%20order%20by%20seq%20desc%20limit%2020&quot;&gt;linux&lt;/a&gt;&quot;,
søkeordet
&quot;&lt;a href=&quot;https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&amp;name=norwegian-doffin&amp;query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20&#39;swdata&#39;%0A%20%20%20where%20abstract%20like%20&#39;%25fri%20programvare%25&#39;%20or%20title%20like%20&#39;%25fri%20programvare%25&#39;%0A%20%20%20order%20by%20seq%20desc%20limit%2020&quot;&gt;fri
programvare&lt;/a&gt;&quot;
og søkeordet
&quot;&lt;a href=&quot;https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&amp;name=norwegian-doffin&amp;query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20&#39;swdata&#39;%0A%20%20%20where%20abstract%20like%20&#39;%25odf%25&#39;%20or%20title%20like%20&#39;%25odf%25&#39;%0A%20%20%20order%20by%20seq%20desc%20limit%2020&quot;&gt;odf&lt;/a&gt;&quot;.
Det er bare å søke på det en er interessert i.  Kopier gjerne
datasettet og sett opp din egen tjeneste hvis du vil gjøre mer
avanserte søk.  SQLite-filen med Doffin-oppføringer kan lastes med fra
Scraperwiki for de som vil grave dypere.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>All drones should be radio marked with what they do and who they belong to</title>
                <link>http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html</link>        
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html</guid>
                <pubDate>Thu, 21 Nov 2013 15:40:00 +0100</pubDate>
                <description>Drones, flying robots, are getting more and more popular.  The most
know ones are the killer drones used by some government to murder
people they do not like without giving them the chance of a fair
trial, but the technology have many good uses too, from mapping and
forest maintenance to photography and search and rescue.  I am sure it
is just a question of time before &quot;bad drones&quot; are in the hands of
private enterprises and not only state criminals but petty criminals
too.  The drone technology is very useful and very dangerous.  To have
some control over the use of drones, I agree with Daniel Suarez in his
TED talk
&quot;&lt;a href=&quot;https://archive.org/details/DanielSuarez_2013G&quot;&gt;The kill
decision shouldn&#39;t belong to a robot&lt;/a&gt;&quot;, where he suggested this
little gem to keep the good while limiting the bad use of drones:&lt;/p&gt;
 
&lt;blockquote&gt;

&lt;p&gt;Each robot and drone should have a cryptographically signed
I.D. burned in at the factory that can be used to track its movement
through public spaces. We have license plates on cars, tail numbers on
aircraft. This is no different. And every citizen should be able to
download an app that shows the population of drones and autonomous
vehicles moving through public spaces around them, both right now and
historically. And civic leaders should deploy sensors and civic drones
to detect rogue drones, and instead of sending killer drones of their
own up to shoot them down, they should notify humans to their
presence. And in certain very high-security areas, perhaps civic
drones would snare them and drag them off to a bomb disposal facility.&lt;/p&gt;

&lt;p&gt;But notice, this is more an immune system than a weapons system. It
would allow us to avail ourselves of the use of autonomous vehicles
and drones while still preserving our open, civil society.&lt;/p&gt;

&lt;/blockquote&gt;

&lt;p&gt;The key is that &lt;em&gt;every citizen&lt;/em&gt; should be able to read the
radio beacons sent from the drones in the area, to be able to check
both the government and others use of drones.  For such control to be
effective, everyone must be able to do it.  What should such beacon
contain?  At least formal owner, purpose, contact information and GPS
location.  Probably also the origin and target position of the current
flight.  And perhaps some registration number to be able to look up
the drone in a central database tracking their movement.  Robots
should not have privacy.  It is people who need privacy.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Lets make a wireless community network in Oslo!</title>
                <link>http://people.skolelinux.org/pere/blog/Lets_make_a_wireless_community_network_in_Oslo_.html</link>        
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_wireless_community_network_in_Oslo_.html</guid>
                <pubDate>Wed, 13 Nov 2013 21:00:00 +0100</pubDate>
                <description>&lt;p&gt;Today NUUG and Hackeriet announced
&lt;a href=&quot;http://www.nuug.no/news/Bli_med___bygge_dugnadsnett_for_alle_i_Oslo.shtml&quot;&gt;our
plans to join forces and create a wireless community network in
Oslo&lt;/a&gt;.  The workshop to help people get started will take place
Thursday 2013-11-28, but we already are collecting the geolocation of
people joining forces to make this happen.  We have
&lt;a href=&quot;https://github.com/petterreinholdtsen/meshfx-node/blob/master/oslo-nodes.geojson&quot;&gt;9
locations plotted on the map&lt;/a&gt;, but we will need more before we have
a connected mesh spread across Oslo.  If this sound interesting to
you, please join us at the workshop.  If you are too impatient to wait
15 days, please join us on the IRC channel
&lt;a href=&quot;irc://irc.freenode.net/%23nuug&quot;&gt;#nuug on irc.freenode.net&lt;/a&gt;
right away. :)&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Running TP-Link MR3040 as a batman-adv mesh node using openwrt</title>
                <link>http://people.skolelinux.org/pere/blog/Running_TP_Link_MR3040_as_a_batman_adv_mesh_node_using_openwrt.html</link>        
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Running_TP_Link_MR3040_as_a_batman_adv_mesh_node_using_openwrt.html</guid>
                <pubDate>Sun, 10 Nov 2013 23:00:00 +0100</pubDate>
                <description>&lt;p&gt;Continuing my research into mesh networking, I was recommended to
use TP-Link 3040 and 3600 access points as mesh nodes, and the pair I
bought arrived on Friday.  Here are my notes on how to set up the
MR3040 as a mesh node using
&lt;a href=&quot;http://www.openwrt.org/&quot;&gt;OpenWrt&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I started by following the instructions on the OpenWRT wiki for
&lt;a href=&quot;http://wiki.openwrt.org/toh/tp-link/tl-mr3040&quot;&gt;TL-MR3040&lt;/a&gt;,
and downloaded
&lt;a href=&quot;http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin&quot;&gt;the
recommended firmware image&lt;/a&gt;
(openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin) and
uploaded it into the original web interface.  The flashing went fine,
and the machine was available via telnet on the ethernet port.  After
logging in and setting the root password, ssh was available and I
could start to set it up as a batman-adv mesh node.&lt;/p&gt;

&lt;p&gt;I started off by reading the instructions from
&lt;a href=&quot;http://wirelessafrica.meraka.org.za/wiki/index.php?title=Antoine&#39;s_Research&quot;&gt;Wireless
Africa&lt;/a&gt;, which had quite a lot of useful information, but
eventually I followed the recipe from the Open Mesh wiki for
&lt;a href=&quot;http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config&quot;&gt;using
batman-adv on OpenWrt&lt;/a&gt;.  A small snag was the fact that the
&lt;tt&gt;opkg install kmod-batman-adv&lt;/tt&gt; command did not work as it
should.  The batman-adv kernel module would fail to load because its
dependency crc16 was not already loaded.  I
&lt;a href=&quot;https://dev.openwrt.org/ticket/14452&quot;&gt;reported the bug&lt;/a&gt; to
the openwrt project and hope it will be fixed soon.  But the problem
only seem to affect initial testing of batman-adv, as configuration
seem to work when booting from scratch.&lt;/p&gt;

&lt;p&gt;The setup is done using files in /etc/config/.  I did not bridge
the Ethernet and mesh interfaces this time, to be able to hook up the
box on my local network and log into it for configuration updates.
The following files were changed and look like this after modifying
them:&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;/etc/config/network&lt;/tt&gt;&lt;/p&gt;

&lt;pre&gt;

config interface &#39;loopback&#39;
        option ifname &#39;lo&#39;
        option proto &#39;static&#39;
        option ipaddr &#39;127.0.0.1&#39;
        option netmask &#39;255.0.0.0&#39;

config globals &#39;globals&#39;
        option ula_prefix &#39;fdbf:4c12:3fed::/48&#39;

config interface &#39;lan&#39;
        option ifname &#39;eth0&#39;
        option type &#39;bridge&#39;
        option proto &#39;dhcp&#39;
        option ipaddr &#39;192.168.1.1&#39;
        option netmask &#39;255.255.255.0&#39;
        option hostname &#39;tl-mr3040&#39;
        option ip6assign &#39;60&#39;

config interface &#39;mesh&#39;
        option ifname &#39;adhoc0&#39;
        option mtu &#39;1528&#39;
        option proto &#39;batadv&#39;
        option mesh &#39;bat0&#39;
&lt;/pre&gt;

&lt;p&gt;&lt;tt&gt;/etc/config/wireless&lt;/tt&gt;&lt;/p&gt;
&lt;pre&gt;

config wifi-device &#39;radio0&#39;
        option type &#39;mac80211&#39;
        option channel &#39;11&#39;
        option hwmode &#39;11ng&#39;
        option path &#39;platform/ar933x_wmac&#39;
        option htmode &#39;HT20&#39;
        list ht_capab &#39;SHORT-GI-20&#39;
        list ht_capab &#39;SHORT-GI-40&#39;
        list ht_capab &#39;RX-STBC1&#39;
        list ht_capab &#39;DSSS_CCK-40&#39;
        option disabled &#39;0&#39;

config wifi-iface &#39;wmesh&#39;
        option device &#39;radio0&#39;
        option ifname &#39;adhoc0&#39;
        option network &#39;mesh&#39;
        option encryption &#39;none&#39;
        option mode &#39;adhoc&#39;
        option bssid &#39;02:BA:00:00:00:01&#39;
        option ssid &#39;meshfx@hackeriet&#39;
&lt;/pre&gt;
&lt;p&gt;&lt;tt&gt;/etc/config/batman-adv&lt;/tt&gt;&lt;/p&gt;
&lt;pre&gt;

config &#39;mesh&#39; &#39;bat0&#39;
        option interfaces &#39;adhoc0&#39;
        option &#39;aggregated_ogms&#39;
        option &#39;ap_isolation&#39;
        option &#39;bonding&#39;
        option &#39;fragmentation&#39;
        option &#39;gw_bandwidth&#39;
        option &#39;gw_mode&#39;
        option &#39;gw_sel_class&#39;
        option &#39;log_level&#39;
        option &#39;orig_interval&#39;
        option &#39;vis_mode&#39;
        option &#39;bridge_loop_avoidance&#39;
        option &#39;distributed_arp_table&#39;
        option &#39;network_coding&#39;
        option &#39;hop_penalty&#39;

# yet another batX instance
# config &#39;mesh&#39; &#39;bat5&#39;
#       option &#39;interfaces&#39; &#39;second_mesh&#39;
&lt;/pre&gt;

&lt;p&gt;The mesh node is now operational.  I have yet to test its range,
but I hope it is good.  I have not yet tested the TP-Link 3600 box
still wrapped up in plastic.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Debian init.d boot script example for rsyslog</title>
                <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>        
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
                <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
                <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
&lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
init.d scripts at all.  Here is an example init.d script, ie a rewrite
of /etc/init.d/rsyslog:&lt;/p&gt;

&lt;p&gt;&lt;pre&gt;
#!/lib/init/init-d-script
### BEGIN INIT INFO
# Provides:          rsyslog
# Required-Start:    $remote_fs $time
# Required-Stop:     umountnfs $time
# X-Stop-After:      sendsigs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: enhanced syslogd
# Description:       Rsyslog is an enhanced multi-threaded syslogd.
#                    It is quite compatible to stock sysklogd and can be 
#                    used as a drop-in replacement.
### END INIT INFO
DESC=&quot;enhanced syslogd&quot;
DAEMON=/usr/sbin/rsyslogd
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
script was 137 lines, and the above is just 15 lines, most of it meta
info/comments.&lt;/p&gt;

&lt;p&gt;How to do this, you ask?  Well, one create a new script
/lib/init/init-d-script looking something like this:

&lt;p&gt;&lt;pre&gt;
#!/bin/sh

# Define LSB log_* functions.
# Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
# and status_of_proc is working.
. /lib/lsb/init-functions

#
# Function that starts the daemon/service

#
do_start()
{
        # Return
        #   0 if daemon has been started
        #   1 if daemon was already running
        #   2 if daemon could not be started
        start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
                || return 1
        start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
                $DAEMON_ARGS \
                || return 2
        # Add code here, if necessary, that waits for the process to be ready
        # to handle requests from services started subsequently which depend
        # on this one.  As a last resort, sleep for some time.
}

#
# Function that stops the daemon/service
#
do_stop()
{
        # Return
        #   0 if daemon has been stopped
        #   1 if daemon was already stopped
        #   2 if daemon could not be stopped
        #   other if a failure occurred
        start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
        RETVAL=&quot;$?&quot;
        [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
        # Wait for children to finish too if this is a daemon that forks
        # and if the daemon is only ever run from this initscript.
        # If the above conditions are not satisfied then add some other code
        # that waits for the process to drop all resources that could be
        # needed by services started subsequently.  A last resort is to
        # sleep for some time.
        start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
        [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
        # Many daemons don&#39;t delete their pidfiles when they exit.
        rm -f $PIDFILE
        return &quot;$RETVAL&quot;
}

#
# Function that sends a SIGHUP to the daemon/service
#
do_reload() {
        #
        # If the daemon can reload its configuration without
        # restarting (for example, when it is sent a SIGHUP),
        # then implement that here.
        #
        start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
        return 0
}

SCRIPTNAME=$1
scriptbasename=&quot;$(basename $1)&quot;
echo &quot;SN: $scriptbasename&quot;
if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
    script=&quot;$1&quot;
    shift
    . $script
else
    exit 0
fi

NAME=$(basename $DAEMON)
PIDFILE=/var/run/$NAME.pid

# Exit if the package is not installed
#[ -x &quot;$DAEMON&quot; ] || exit 0

# Read configuration variable file if it is present
[ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

case &quot;$1&quot; in
  start)
        [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
        do_start
        case &quot;$?&quot; in
                0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
                2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
        esac
        ;;
  stop)
        [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
        do_stop
        case &quot;$?&quot; in
                0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
                2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
        esac
        ;;
  status)
        status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
        ;;
  #reload|force-reload)
        #
        # If do_reload() is not implemented then leave this commented out
        # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
        #
        #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
        #do_reload
        #log_end_msg $?
        #;;
  restart|force-reload)
        #
        # If the &quot;reload&quot; option is implemented then remove the
        # &#39;force-reload&#39; alias
        #
        log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
        do_stop
        case &quot;$?&quot; in
          0|1)
                do_start
                case &quot;$?&quot; in
                        0) log_end_msg 0 ;;
                        1) log_end_msg 1 ;; # Old process is still running
                        *) log_end_msg 1 ;; # Failed to start
                esac
                ;;
          *)
                # Failed to stop
                log_end_msg 1
                ;;
        esac
        ;;
  *)
        echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
        exit 3
        ;;
esac

:
&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
lot.  I did not really polish the approach, so it might not always
work out of the box, but you get the idea.  I did not try very hard to
optimize it nor make it more robust either.&lt;/p&gt;

&lt;p&gt;A better argument for switching init system in Debian than reducing
the size of init scripts (which is a good thing to do anyway), is to
get boot system that is able to handle the kernel events sensibly and
robustly, and do not depend on the boot to run sequentially.  The boot
and the kernel have not behaved sequentially in years.&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
                <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>        
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
                <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
                <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
remote display access is the preferred solution with oVirt and RedHat
Enterprise Virtualization, and I was sad to discover the other day
that the browser plugin needed to use these systems seamlessly was
missing in Debian.  The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
for a package&lt;/a&gt; was from 2012-04-10 with no progress since
2013-04-01, so I decided to wrap up a package based on the great work
from Cajus Pollmeier and put it in a collab-maint maintained git
repository to get a package I could use.  I would very much like
others to help me maintain the package (or just take over, I do not
mind), but as no-one had volunteered so far, I just uploaded it to
NEW.  I hope it will be available in Debian in a few days.&lt;/p&gt;

&lt;p&gt;The source is now available from
&lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary&quot;&gt;http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary&lt;/a&gt;.&lt;/p&gt;
</description>
        </item>
        
        </channel>
</rss>