Search Results: "ag"

20 October 2007

Andreas Schuldei: Dear Lazyweb: Au-Pair wanted!

So we will move back from Sweden to Germany after 7.5 years. Besides swedish nature and working culture we will surely also miss swedish broadband. On the other hand we survived swedish health care without serious repercussions and look forward to the german alternative.
So after having found a really nice house in L beck's historic center we now look for an swedish Au-Pair. One of the main goals with that would be to help our children to keep their swedish language skills. If anyone reading this knows someone interested in working as an Au-Pair during 2008 please have them contact me.

This years first Extremadura work meeting with people from Debian Edu, FAI, Debian-Science and Debian-Med takes place at time of writing. The group is 20 people (with some locals included). There is a rich supply of good spanish food so I skipped dinner yesterday in order to let my digestive system recuperate and get work done at the same time. I feel tempted to do that again today. Having stared and poked at FAIs new partition framework makes me consider partman as an alternative.

Enrico Zini: liferea-summarise

Automatic feed summaries What do you get if you merge this and this? You get a scary little filter that extract the top 5 keywords from a post content and adds them to the titles. Useful titles for all posts: how about that?
#!/usr/bin/python
# Copyright (C) 2007 Enrico Zini <enrico@debian.org>
# This software is licensed under the therms of the GNU General Public
# License, version 2 or later.
import libxml2, re, math
tokenize = re.compile(r"\W+")
doc = libxml2.parseFile("-")
root = doc.getRootElement()
# Create an xpath context and register the namespaces
xpc = doc.xpathNewContext()
for d in root.nsDefs():
    if d.name == None:
        xpc.xpathRegisterNs("rss", d.content)
    else:
        xpc.xpathRegisterNs(d.name, d.content)
# Collect text stats to generate summaries
doc_tokens =  
for x in xpc.xpathEval("/rdf:RDF/rss:item"):
    res = x.nsProp("about", "http://www.w3.org/1999/02/22-rdf-syntax-ns#")
    tokens =  
    for c in x.children:
        if c.type != 'element' or (c.name != 'encoded' and c.name != 'title'):
            continue
        for t in c.children:
            if t.type != 'text': continue
            for tok in tokenize.split(t.content):
                if tok in tokens:
                    tokens[tok] += 1
                else:
                    tokens[tok] = 1
    doc_tokens[res] = tokens
# Aggregate token counts
aggregated =  
for d in doc_tokens.itervalues():
    for tok, count in d.iteritems():
        tok = tok.lower()
        if tok in aggregated:
            aggregated[tok] += count
        else:
            aggregated[tok] = count
def tfidf(doc, tok):
    "Compute TFIDF score of a token in a document"
    tok = tok.lower()
    return doc_tokens[doc].get(tok, 0) * math.log(float(len(doc_tokens)) / aggregated.get(tok, 0))
def top5(doc):
    # Output the top 5 tokens by TFIDF
    return sorted(doc_tokens[doc].keys(), key=lambda tok: tfidf(doc, tok), reverse=True)[:5]
# Rewrite the titles
for x in xpc.xpathEval("/rdf:RDF/rss:item"):
    res = x.nsProp("about", "http://www.w3.org/1999/02/22-rdf-syntax-ns#")
    for c in x.children:
        if c.type != 'element' or c.name != 'title':
            continue
        for t in c.children:
            if t.type != 'text': continue
            name, content = t.content.split(":", 1)
            summary = ", ".join(top5(res))
            t.replaceNode(doc.newDocText(name+" ["+summary+"]:"+content))
# Serialize the result
print doc.saveFormatFile("-", True)

Enrico Zini: apt-xapian-index

Introducing apt-xapian-index apt-xapian-index has just been approved into experimental, and in the next days I'm going to blog more about it. The package contains a tool called update-apt-xapian-index that indexes Debian package metadata into a Xapian index located at /var/lib/apt-xapian-index/index. The index is read-only, except for update-apt-xapian-index; however, it is world-readable: every user can query it, all the time, at the same time, even during index updates. The index can contain more than package descriptions. update-apt-xapian-index indexes data using plugins located in /usr/share/apt-xapian-index/plugins, and any package can add their own. For example, debtags will provide a plugin to index tags. Since Xapian can index numeric values as well, if anyone makes a popcon package that downloads popcon information, they can provide a plugin to index popcon values. If anyone makes an iterating package that downloads ratings, they can provide a plugin to index ratings. Another plugin could be a specialised Debian stemmer that generates token such as foo out of libfoo-dev. I think you get the idea: it's very extensible. You can have a look at the initial set of plugins in subversion. The index is also self-documenting, so that one can keep track of all the intresting things that can be found in it. update-apt-xapian-index does not only maintain the index, but also the file /var/lib/apt-xapian-index/README that aggregates documentation provided by the plugins. To query the index, you just use Xapian. Debian contains Xapian bindings for various languages: In the next days I am going to post various example queries and interesting tricks that the index allows you to do. It's going to be fun.

19 October 2007

Ian Haken: Long Time, No Update

So I've clearly neglected giving frequent updates, so I'll try to summarize everything that's been going on and maybe try to post more frequently in the future (I feel like I've said that many times before).

The summer ended very well, I think. My GSoC project vlosuts concluded with a fully working version, and so hopefully some guys over at Quality Assurance can be goaded into giving it a try. Once Lars and I find some time (it seems like both our lives have been quite hectic) we'll be submitting it to the unstable branch. I intend to continue supporting and developing it; in fact last night I just checked in the first update for VirtualBox support, as recommended by Jon in my comments. It does seem to work faster than QEMU and Innotek did a quality job (in my opinion at least) of packaging it. The biggest kink is that it does not support raw disk images, and so vlosuts gets slowed down by having to convert to VMDK and back, for which I am using qemu-img (and does anyone know why VBoxManage unregisterimage doesn't seem to be working for VMDKs?). If it's possible to do a loopback mount of VMDK (without VMware's utility) it would probably make more sense to use VMDK instead of a raw image to begin with, but I'm not familiar with any way to do this. At any rate, first version of VirtualBox is there for anyone who'd like to give it a shot.

Anyone not concerned with the personal going-ons of my life should stop reading right about now. Since my semester started up again at the end of August, I've pretty much hit the ground running. I'm taking 20 units (I think the average is around 15), one of which is a mathematics graduate course. I'm also doing a research project in computer science, working a part time job (which I try to do for about 10 hours a week), and getting my graduate school applications taken care of. For anyone who is curious, the GRE is a terrible thing. Graduate school and fellowship applications have been a particular headache, but fortunately I'm just about finished up with the essays. For the curious I'll be applying to mathematics departments with an emphasis in logic and foundations at the following universities (list subject to change frequently): MIT, Berkeley, Stanford, Carnegie Mellon, Urbana-Champaign, UMich.

Christian Perrier: RWC: France punished by Argentina

France sank against Argentina tonight. Last time France played in Parc des Princes, they were crushed by South-Africa, 10 years ago. The same happened tonight with an impressive victory by Argentina against France. France dominated the first 20 minutes but Argentina's defense was heroic and strong. Certainly the best defense play of this entire world cup, in this match, with a great organization around mauls, an impressive scrum and explosive tackles. After being dominated 26 minutes long and anyway scoring a try an, Argentina had to resist 10 minutes before half time when France unsuccessfully attempted to score a try (which would probably have changed the match). I think I will have to review these 10 minutes again as this was a demonstration of defensive play. It is indeed not a surprise that Ibanez lost his nerves and got expelled at the very end of 1st half time. Sad end of career...very similar to Zidane's one, indeed. In second half time, seeing France being crushed so hard was sometimes saddening but Argentina played so wonderfully that we could just be admirative of that play. Again, their solidarity and defensive play made the difference and, 5 tries later, they finally logically beat France. The Argentinian team is really a great satisfaction of the world cup. Playing only with 18 players, they only half-missed one match: their semi-final against South-Africa. I think they now really deserve to play in the Tri-Nations tournament along with New Zealand, Australia and South-Africa: if that doesn't happen, I will really think that other southern hemisphere nations are just cowards..:-) What about France? Well, this is a really sad ending for that world cup. Finishing with two very bad matches is really worrying for the future of that team. There are many promising players in that team (such as Dusautoir, Szarzewski...) and they can probably rebuild something and we still be enthusiast about that sport in this country.

Russell Coker: Finishing a Presentation too soon

In my previous post about Advice for Speakers [1] I referred to the common problem of going through presentation materiel too quickly due to being nervous. In extreme cases (which tend to happen when giving a presentation for an unusually large audience) the materiel for an hour long presentation may be covered in 10 minutes or less. This is a problem that most speakers have at least once in their career. I recently heard an interesting (and in retrospect obvious) way of dealing with this problem. That is to label each note card with the estimated time through the presentation when it should be presented. If you are reading from the 10 minute card at 2 minutes into the presentation then you need to slow down. Of course this doesn’t work as well if you follow the “strict powerpoint” method of presenting where the only notes are the slides. It would be good if a presentation program supported having windows on two displays so you could have one full-screen window on an external video device for the audience to see and one window that’s not full-screen on the built-in display in the laptop for the speaker. The built-in display could have speaker notes, a time clock, and other useful things. I have just filed Debian bug report 447207 [2] requesting that this feature be added to Open Office. It was closed before this post was even published due to Unstable apparently having some degree of support for this and the rest being already on the planned feature list (see the bug report for details). I found the complaint about a feature request being against Etch interesting as Debian doesn’t have bugs tracked against different releases, so it’s not as if a bug reported against Etch will get any different treatment than a bug reported against Unstable.

Thomas Girard: Gtk User Interface for GNU Smalltalk

Thanks to Alexander, the next upload of GNU Smalltalk will include the Gtk Blox Browser. To run it, I used:
st> PackageLoader fileInPackage: 'BloxGTK'!
st> PackageLoader fileInPackage: 'Browser'!
st> BLOX.BLOXBrowser.BrowserMain new initialize!
Here is a screenshot: GNU Smalltalk Gtk Browser The package still needs some polishing.

Norbert Tretkowski: MySQL Customer Conference

Yesterday I visited the MySQL Customer Conference in Munich. First of all, GDL sucks. But the locomotive driver strike was the only negative issue on that day, the conference itself was quite good, especially Jan Kneschke's talk about MySQL performance tuning (which was mostly about combining MySQL Cluster and MySQL Proxy) and the panel discussion about storage engines with Ralf Gebhardt, Jan Kneschke and Kai Voigt as vocal and Kaj Arn as moderator. All in all a great (but quite long and exhausting) day.

Steve Kemp: As I move on through the year

Bits from the Security Team I am happy to look over patches, built packages, and generally encourage people to be involved. Our team isn't huge but historically we've only added people who've done a fair bit of work first. That is both good and bad. I could write more, and probably should, but I'll stop there for now because I'm frustrated by the HPPA build machine. Again. ObRelated: Moritz is trying to get the archive rebuilt with security features from our compilers (eg. -fstack-protector) included. This would be a fantastic achievement. People interested in tested kernel patches, donating buildd machines, etc, etc should give him a ping.

Enrico Zini: filtering-planet

Filtering planet entries Here is how to setup liferea not to show me some entries in Planet Debian:
  1. Create a script that reads the rss from stdin, removes the entries you don't want and then writes the rss to stdout;
  2. From the feed properties in liferea, choose the source tab, enable the conversion filter and point that at your script.
Now you just need a simple script that filters the RSS. Here is mine:
#!/usr/bin/python
# Copyright (C) 2007 Enrico Zini <enrico@debian.org>
# This software is licensed under the therms of the GNU General Public
# License, version 2 or later.
import libxml2, re
# What links we should filter out
unwanted = re.compile(r"^(http://feed1.example.com http://feed2.example.com)")
doc = libxml2.parseFile("-")
root = doc.getRootElement()
# Create an xpath context and register the namespaces
xpc = doc.xpathNewContext()
for d in root.nsDefs():
    if d.name == None:
        xpc.xpathRegisterNs("rss", d.content)
    else:
        xpc.xpathRegisterNs(d.name, d.content)
# Remove unwanted items from the channel list
for x in xpc.xpathEval("/rdf:RDF/rss:channel/rss:items/rdf:Seq/rdf:li"):
    res = x.nsProp("resource", "http://www.w3.org/1999/02/22-rdf-syntax-ns#")
    if unwanted.match(res):
        x.unlinkNode()
        x.freeNode()
# Remove unwanted items from the item list
for x in xpc.xpathEval("/rdf:RDF/rss:item"):
    res = x.nsProp("about", "http://www.w3.org/1999/02/22-rdf-syntax-ns#")
    if unwanted.match(res):
        x.unlinkNode()
        x.freeNode()
# Serialize the result
print doc.saveFormatFile("-", True)
Now, getting to this simple script took some spitting blood. Basically, in Debian we seem to have lots of simple libraries for: I tried, in order:

Jose Luis Rivas Contreras: Yes, Ubuntu is still based on Debian

Answering to Christian Perrier about if Ubuntu is not based anymore on debian and that's why debian didn't get named in all their site avoiding any kind of relation with debian as their base even in the announcement of 7.10: I can see my packages there and I'm not a volunteer of Ubuntu (at least not directly) so they're definetely still based on Debian and just copying a lot of packages from debian to their repos.

Stefano Zacchiroli: debian on ubuntu com just a bug

No "debian" on ubuntu.com: undoubtfully a bug! The mention that the word "Debian" does not appear in the recent announce about Gutsy on the ubuntu.com website by Lucas reminded me something. Indeed, though I'm yet another DD that so far has never played the ubuntu bashing game, I remember having in the past tried to find the word "debian" on the ubuntu website. At the time of writing, using the site search on ubuntu.com, results in just a few hits, all of them are marginal: OpenOffice.org maintenance, the fact that Canonical employees are part of Debian, and an announcement as old as Ubuntu 5.04. What I want to see there is just a tiny teeny sentence that explain where a huge deal of Ubuntu packages come from and a mention of all the wonderful collaborative maintenance projects in which DDs and Canonical employees (or even MOTUs) work together to build great packages. So I wondered that it was probably a fault of mine: I wasn't looking in the right place of the website. Let's try with http://www.ubuntu.com/debian, since the ubuntu website is CMS/Wiki based it seems like a good attempt, doesn't it? But no luck: "Sorry, the page you are looking for was not found". But then, down in the page, I saw the root of the problem: "please consider reporting this problem as a bug". It is obvious now: it's simply a bug in the website! Let's point the maintainers to it ... As a careful bug reporter I first searched to check whether the bug was already reported, according to this search it hasn't (though now that you're clicking on it you're probably seeing something, when I did I got "No results for search debian"). So let's report the bug, the result is bug #154274 on launchpad. Let's see what will happen to it. Update: the reply on launchpad was really fast. I've followed up with what I think should be mentioned on the ubuntu website regarding Debian. Feel free to help out with your comments in the launchpad entry.

Russell Coker: Banking with an Infected Computer

Bruce Schneier summarised a series of articles about banking security [1]. He mentioned the fact that banks don’t seem to care about small losses and would rather just deal with the problem (presumably by increasing their fees to account for losses). There are some other interesting bits in the article, for example banks are planning a strategy of securing transactions with an infected computer [2]! Now there are some possible solutions to this, for example if the bank issued a hardware device that allowed the customer to enter the account number, amount to transfer, destination account, and PIN number and then produced a cryptographically secure hash (based in part on a rolling code) that the user could type in. The only way that you are going to do anything securely with an infected host is if everything is offloaded into an external device. In which case why not just do the Internet banking on the external device? It’s not difficult to make a hardware device that is small enough to carry everywhere, has a display, an input device, net access, and which is reasonably difficult to crack externally. Consider for example a typical mobile phone which has more RAM, CPU power, and storage than a low-end machine that was used for web browsing in 1996. Mobile phones have a good history of not being hacked remotely and are difficult for the owner to “unlock”. A locked-down mobile phone would be a good platform for Internet banking, it has wireless net access in most places (and with a Java application on the phone it could do banking by encrypted SMS). Being locked down to prevent the user from reconfiguring the software (or installing new software) will solve most of the security problems that plague Windows. If when signing up for a new phone contract I was offered the possibility of getting a phone with secure banking software installed for a small extra fee then I would be very interested. Of course we would want some external auditing of the software development to make sure that it’s not like some of the stupid ideas that banks have implemented. Here is a classic example of banking stupidity [3]. They display a selected word and picture for the user when they login to try and prevent phishing (of course a proxy or a key-logger on the local machine will defeat that). They also ask for an extra password (of the simple challenge phrase variety) if you use a different IP address, of course as the typical broadband user doesn’t know when their IP address changes they wouldn’t know if their data was being proxied and dial-up users will enter it every time. A google search for “internet banking” picture password turns up a bunch of banks that implement such ideas.

Romain Francoise: Shared links for 2007-10-19

Christian Perrier: A clean pet package

W00t, my pet package is so clean! Ah, looking closer, there's a Ubuntu thing in a corner. I'll integrate that patch when Debian will be mentioned in their release announcements.

Mike Hommey: Gobuntu and Firefox

You may remember, a while ago, Mark Shuttleworth announced that there would be a 100% free version of Ubuntu Gutsy Gibbon :
Ubuntu 7.10 will feature a new flavour - as yet unnamed - which takes an ultra-orthodox view of licensing: no firmware, drivers, imagery, sounds, applications, or other content which do not include full source materials and come with full rights of modification, remixing and redistribution.
Later, we learned it would be named Gobuntu. Well, they didn’t quite follow their promise. Yes, Gobuntu includes Firefox, making it a pretty useless failed attempt. By the way, I’m still amazed so many people believe it was all about the trademarks. For them, I’ll quote something I wrote a year ago:
Trademark and copyright are different things. Mozilla has unnecessarily given a non-free license to clarify the trademark situation, but that is not required. To make it clear: Debian thinks the logos are not free because they are not free. Period.
I’m glad at least Mark Pilgrim got it right. Update: And as seen on Planet Mozilla, Robert Sayre obviously still hasn’t understood the issue.

Jose Luis Rivas Contreras: So cheap!!

I found in my dad's office a Macworld of october 90' and saw this 2 page ad:
This is when you think how that people could live? If you need 2G right now for nice working that would make $138.000!! Thanks tech evolution!

Raphael Geissert: DeBaBaReTools: The de-what?

It's been a while since I wanted to post about a project I started.
But today when I read Russell Coker's post about his SE Linux repository I decided it was time to blog about DeBaBaReTools.


So, what is/are DeBaBaReTools?
is: a project which tries to unify different packages-building systems (pbuilder, buildd, etc) and different repository tools (debarchiver, reprepro, etc) in a single system by providing an incoming/ system.

are: Debian Bash-Based Repository Tools.

Or in other words:
DeBaBaReTools handles new packages by:


DeBaBaReTools is NOT a rewrite of a repository tool (like reprepro, debpool or debarchiver), neither yet an other building tool (like buildd or pbuilder). It is rather a glue between those two kind of tools.

So, how does DeBaBaReTools work?
As already said, they are a set of scripts which do all the work.
These are some of the scripts (more might be written later, they are under development):



Note that at the moment these are the only supported backends: gpgv, du, md5sums (all built in checkSums), pbuilder and reprepro.

Sounds interesting, doesn't it? :)

So, here's the magic:

The backends system
DeBaBaReTools doesn't try to re-invent the wheel, but it makes use of all the available tools so it works as less as possible.

This is where the backends take action. They are even more shell (even tough DeBaBaReTools clearly specifies they are Bash scripts they should work on any other POSIX-compatible shell) scripts which are loaded on demand and according to the user settings.

This opens a wide range of possible combinations of backends; making DeBaBaReTools work with almost anything.

The probe.sh script searches different directories for the specified backend (and will soon support user-hinted backends).

I think an example says more than a thousand words:
When needsBuild finds a package that needs to be built in a given architecture, the toBuild shell function is called. In order to provide the already said flexibility, needsBuild will at startup time call probeFile "buildQueue" which will then check several directories for the required backend (buildQueue in this case). Once it finds the given backend (backends/buildQueue/) it will check for any user hint (which will specify the real backend to be used) and then for a default one (default.sh which is a symlink to a real backend, plaintext.sh by default).

So, if somebody at some point wants to use a sqlite database to store all that information, that person would have to write a file called backends/buildQueue/sqlite.sh (or make it available in any of the include paths which can be extended via the EXTRA_PROBE_DIRS env variable) and either set a user hint or make default.sh point to it.
The sqlite.sh script can then call any external tools (or even more scripts) to insert the information in the database, read it and more.

I know this is a lot of blahblahblah but no single line of code is shown.
I've already requested an alioth project but it was denied because the package isn't already in the Debian archive.
If you are a DD and you think this sounds like a good project please contact the Alioth admins and convince them to create a project account for DeBaBaReTools.
Once created, many other people will be able to work on it and make it work with virtually any tool.

Any kind of feedback is very welcomed but I hope they are constructive ideas.

Why did I start this crazy project?
Because AFAIR only dak is able to do such job but I think dak is just too complex for a simple system to manage an a repository with an incoming system. And AFAIK there's no script which is able to do this job besides dak.

I hope this post makes sense because I don't want to review it again (I'm tired) :)

:bye: all

18 October 2007

Russell Coker: My SE Linux Etch Repository

deb http://www.coker.com.au etch selinux The above sources.list line has all the i386 packages needed for running SE Linux with strict policy on Etch as well as a couple of packages that are not strictly needed but which are really convenient (to solve the executable stack issue). gpg --keyserver hkp://subkeys.pgp.net --recv-key F5C75256
gpg -a --export F5C75256 apt-key add - To use it without warnings you need to download and install my GPG key, the above two commands do this. You will of course have to verify my key in some way to make sure that it has not been replaced in a MITM attack. The only thing missing is a change to /etc/init.d/udev to have a new script called /sbin/start_udev used to replace the make_extra_nodes function (so that the make_extra_nodes functionality can run in a different context). Of course a hostile init script could always exploit this to take over the more privileged domain, but I believe that running the init scripts in a confined domain does produce some minor benefits against minor bugs (as opposed to having the init scripts entirely owned). I back-ported all the SE Linux libraries from unstable because the version in Etch doesn’t support removing roles from a user definition by the “semanage user -m” command (you can grant a user extra roles but not remove any roles). Trying to determine where in the libraries this bug occurred was too difficult. Does anyone know of a good document on how to create repositories with apt-ftparchive? My current attempts are gross hacks but I’ve gone live anyway as the package data is good and the apt configuration basically works.

Lucas Nussbaum: Re: Giving credit where due?

Christian Perrier is wondering why the official announcement about the Gutsy release does not even contain the word “Debian”. It’s not new: Debian is virtually nonexistent in Ubuntu’s communication. It seems that the last Ubuntu release to acknowledge its Debian origins was Dapper (June 2006), maybe because that was the “Long Term Support” release. The fact that there’s no “Ubuntu is based on Debian” paragraph on www.ubuntu.com was raised during Debconf, and it was supposed to get fixed, but it seems that it didn’t happen for some reason (there was such a paragraph before the website redesign). In other news, I’ve been trying to install Ubuntu Gutsy inside qemu, but it fails miserably while booting the installer. I removed the “quiet” and “splash” options from the kernel cmdline, and discovered that after trying to “mount the root filesystem”, I get dropped into busybox with no error message to google for. Feisty fails as well, but Dapper boots fine. So much for the Ubuntu is an ancient African word, meaning “I can’t install Debian” joke!

Next.

Previous.