Search Results: "ag"

27 September 2007

Simon Richter: #!

Dirk, actually it is suggested that there is a single space between the shebang and the path to the interpreter. It's not particularly important on Linux, but there are systems out there that use "#! /" as the magic value for scripts, thereby ensuring that the interpreter path is indeed absolute.

Dirk Eddelbuettel: Dear Samsung,

Your ML-3051N is a lovely little 'network printer. Hopefully, it will serve us well in the next few years as a replacement for the thirteen year old HP Laserjet ML we bought (for about five times the price: a native postscript printer was rather expensive in 1994) a long time ago. And you even mention that it can talk to Linux! But still, I have a few things to talk to you about:
  1. as you mention Linux, it's a tad odd that you enumerate various flavours (RH 8 to 9; FC 1 to 3; Mandrake 9 to 10.2; SuSE 8.2 to 9.2) but happen to exclude the two variants that run around here: Debian and its cousin Ubuntu. Besides, the versions of those other flavours are a tad old, no?
  2. as you ship Linux software on a cdrom, it is even odder that the install shell script fails (note: spaces between #! and /bin/sh may not be a good idea). Fails not once, but twice: you say /bin/sh, but you meant /bin/bash as you use features of the latter. Oh well, I guess we all made that mistake in our youth. Irregardless, the software never installed. Which is a pity as this would be about the first 'household appliance' I bought with native Linux support. So close, and yet so far.
  3. the control panel is a cumbersome way to set a static IP and to turn the odd protocol off.
  4. did I really have to install all this windoze stuff on my wife's laptop just to learn that the printer does in fact have a nice web interface? You could have mentioned that with Linux info, no? It is in fact a rather nice and complete web interface.
  5. as you supply networking support, do you really have to enable every possible protocol under the sun? I mean slp, snmp, multicast dns, dynamic dns, raw tcp, ipp, ethertalk, netware ...? I still see my cable modem go down 'seemingly randomly' rigth after I print even though I now disabled just about everything but raw tcp to port 9100 as well as ipp to 613. Still, dropping the cable connection just because the printer wakes up is odd, isn't it?
  6. Cups, foomatic and all the other printing goodies do not yet know the ML-3050 family, so we are making do with the ML-2151NPS settings for postscript. Works fine, so I won't bother copying the ppd file from the cdrom to the handful of computers around here.
Kind regards, Dirk Updated to fix a markup error. And the shebanh space is standard, I am told.

Ian Wienand: The stamp idiom with make

Sometimes you need direct make to progress through various phases which may not have a particular file target associated with them. For example the first step might be to extract a compressed tarball of data and run a script over it in preparation for compiling that data into something else. Equally you might need to patch some files or maybe download some data. The general idiom to accomplish this sort of thing is the stamp file. The general principle is to make a phony target that depends on a file called target-stamp. The target-stamp target can then do what it needs to do and simply create a dummy file via touch. This file indicates to make that the phase is complete, and targets that depend on this phase being complete can now depend on the stamp file. A small example follows
all: final
.PHONY: prepare clean
final: prepare
        # run build process
prepare: prepare-phase1-stamp prepare-phase2-stamp
prepare-phase1-stamp:
        # untar data or something
        touch $@
prepare-phase2-stamp: prepare-phase1-stamp
        # run a script or do something else
        touch $@
clean:
        rm -f *-stamp
One place you may notice extensive use of this is the -stamp files in the /debian directory of packages built with CDBS.

26 September 2007

Miriam Ruiz: Piklab in Debian

I’ve been so busy lately that I forgot to write about it: Piklab is now in Debian. I don’t know if any of you has done and development with PIC microcontrollers, but it’s not that there was a lot of free programs for doing so. Even now, it might be problematic depending on which hardware you have for programming them. In any case, Piklab is an integrated development environment for applications based on Microchip PIC and dsPIC microcontrollers similar to the MPLAB environment, which makes it easier to develop. It’s a real pity that we cannot consider the newer versions of SDCC as DFSG-free, due some non-commercial clauses, because it is a real nice companion compiler for Piklab.

Julien Blache: Fun with bootloaders, continued

After adding the ability to load 64bit kernels on machines equipped with a 32bit PROM, I’ve now added initrd support to arcload. I’ve tested that code on IP22, if you give it a go on another platform please let me know how it goes! Don’t bother with IP27, initrd is unsupported in the kernel on that one (some work required). Patches welcome if any are required. To add an initrd to your arcload config, use the initrd keyword in the same manner you use the image keyword. And to be on the safe side, add a test entry, so that you can still boot the machine if for some reason the initrd can’t be loaded :) I’ve produced a patch for arcboot too, so that will appear in arcboot at some point in the near future too.

MJ Ray: New to the Forum? Say hello! / Re: Hello, how do we keep this running?

"We got a few more members now. The forum platform is now Simple Machines instead of Invision, I should have listened to Slef!"
Well, I have been doing this a long time... unfortunately, that means I also sound bitter and should be ignored sometimes ;-)

We're still not exactly in danger of filling up the new WSMForum yet.  How should we promote this?  Door-to-door cards?  Flame-bait the letters pages of the newspapers?

Also, how do we ensure the forum survives in the long term?  Could we try a web-co-op-2.0 idea to reward the community?
http://tom.acrewoods.net/blog/2007/apr/enclosure-co-operative-2-0

Steve Kemp: ust to be the man who walked 1000 miles

A new release of xen-shell was made last night, which fixes a couple of minor niggles: Unless there are great demands for additional features I'm now going to regard this project as complete/finished. Certainly it works well enough for myself and my users. Satisfaction is ...

Wouter Verhelst: Live!

My brother and me, we've been maintaining the website for the Jozef Pauly Ensemble since a few years. I'd written some stuff in PHP so that a few things could be automated, but it wasn't much more than a glorified SSI setup, with a random picture at the home page, a calendar page that would automatically strike out past events, and some semi-homebrewn language negotiation support based on my accept-to-gettext.inc file that I wrote a few years ago (and which apparently has become quite popular in the mean time—even with the bug in that it requires you to set a charset, which is totally unnecessary). I had tried to set it up so that people could easily modify the site: everything was stored in subversion, and I made people use TortoiseSVN to make a checkout, explaining them how to safely use it, and providing a bunch of page templates, but that was still too difficult. Over the past year, I've been off and on working on replacing the whole setup with something based on Drupal, and today we've gone live. It's nothing too spectacular—just the default theme with some non-default colors and a few extra non-default modules—but at least I won't be the bottleneck for doing updates anymore; and stuff which used to run separately (forum, guest book, a few other things) are now nicely integrated into the main site. Isn't that nice.

Adrian von Bidder: Introducing bookmarks.debian.net

I'm constantly amazed how much useful information about Debian is published daily (on web sites, blogs and mailing lists.) I'm also amazed about how much time I spend searching web pages I've seen in the past but haven't bookmarked. So bookmarks.debian.net is an attempt to improve this situation, and having all the links organised in a way so that I actually find what I'm searching for. There are only 14 links right now, and of course lots of standard “places to start” links missing (like pages from debian.org), but I'll add stuff as I use the pages and as submissions come in. I'll think about suggestions on how to organise the categories, but all in all, it's my bookmark collection, not yours, so the final decision is mine. Oh, and: please be patient if I'm not adding your submission immediately. (Btw, the number one piece of information I never remember is the name of that script to sort a list of packages by maintainer. I know it's on lists.d.o somewhere... :-)

Jeff Bailey: Leif's first cold

Have I mentioned before that Leif is such an amazing baby? He's got his first cold, but despite this managed to sit up this morning, crack a smile, and then panicked because he couldn't breathe. But he's still trying to be cute and lovable.

In related news, I think a nose syringe is something that J&J makes for parents to let them pass the time while their child is screaming. It certainly doesn't seem to do anything else.

Michal Čihař: First success with Photo uploader

Today I did really big stress testing of Photo uploader - I needed to upload 400 photos (total size somewhere near 600 MiB). And it worked without problems! I could not imagine that I would have to upload so much files using web forms or some damn slow Windows application. Also since last announcement uploader development went on. It now supports 4 services (all in Czechia for now), I added some documentation and man page. Also version 0.1 has been released yesterday (but it does not yet contain mentioned updates), with plan to release 0.2 somewhere next week. And as I got quite a lot of requests for GUI - I do not plan to write one myself (or at least not soon). So if you want one, please write it. As all hard work is done by phoupl module, it can be easily embedded into some simple image viewer written in Python.

Russell Coker: Is the Server Dead?

I often get reports such as “the server was dead so I rebooted it“. This really doesn’t help me fix the problem, so if the person who uses the server wants reliability (and doesn’t want to be rebooting it and losing data all the time) then more information needs to be provided. Here is a quick list of tests to perform before a reboot if you would like your server not to crash in future:

  1. Does pressing the CAPS-LOCK key on the keyboard make the CAPS LED light up? If so then the OS isn’t entirely dead.

  2. What is on the screen of the server (you may have to press a key to get the screen to un-blank)? If it’s a strange set of numbers then please photograph them if possible, I might understand what they mean. If you don’t have a camera with high enough resolution to capture them then please make a note of some of the messages. Don’t write down numbers - they are not useful enough to be worth the effort. Write down words, including special words such as OOM and pairs of words seperated by a “_” character.

    If the “server” is a Xen virtual machine then save the contents of the console (as described in my previous post [1]).

  3. Can you ping the machine (usually by ping servername)? If so then networking is basically operational.

  4. Are the hard drive access lights indicating heavy use? If so then it might be thrashing due to excessive memory use (maybe a DOS attack).

  5. Can you login at the console? If so please capture the output of free, ps auxf, and netstat -tn.

  6. If the machine offers TCP services (almost all servers do) then use the telnet command to connect to the service port and make a note of what happens. For example to test a mail server type “telnet server 25” and if all goes well you expect to see “220 some message from the mail server“, note how long it takes for such a message to be displayed. Some protocols don’t send a message on a connect, for example with HTTP (the protocol used by web servers) you have to enter a few characters and press ENTER to get a response (usually some sort of HTTP error message).

Finally please don’t tell me that the server is too important and that the users couldn’t wait for you to perform any tests before rebooting it. If the server is important then it is important that it doesn’t crash repeatedly. A crash may even be caused by something that could cause data loss (EG hardware that is failing) or something that could incur extra expense if not fixed quickly (EG failing hardware that will be out of warranty soon). You have to tell users that the choice is to wait for an extra few minutes or risk having another crash tomorrow with further data loss. If the server is important enough for it to be worth my time to try and fix it then it’s important enough to have these tests performed before the reboot.

Scott James Remnant: Why I choose Bazaar (a history of revision control)

Like any sensible software developer, I have a close relationship with revision control systems. In my previous job, I was an SCM Engineer (see Software configuration management) which meant I had an even closer relationship than most, since we were running the CVS servers and actively using them to track changes and deployments. We all know, deep down, that revision control systems shouldn’t exist. This kind of thing should be inherent in the design of the operating system, through standard file and filesystem formats. The OLPC interface is making some headway towards that, but for the rest of us, it means using a revision control tool throughout the development process. Unfortunately, even though the tool is expected to be the most-used command on your system, very few of them are particularly easy to use. Thus there’s a large learning curve, and people become religious about their choice since they have invested significant time in using it. Just to spice the mix up, not only will people religiously defend their choice of revision control system, but they’ll do so while actively hating it. In the beginning there was CVS and we all thought that it was pretty good. It was based on the simpler RCS and shared a file-format with it, but introduced control of directory trees and remote operation. Actually, in reality, CVS wasn’t that good. Its command set could be a little strange and inconsistent (e.g. it’s not possible to diff between two dates on a branch); the support for branching assumed that all branches would be merged into the mainline, and only once; and nobody ever really knew how to create a new project in a repository (tip. cvs import is wrong). But we all used it anyway, and we muddled through. It did have some good features; it was simple, fast and pretty reliable–when it did break, you could usually fix the repository yourself. And most importantly of all, we understood how to drive it. And so it was for many years, until Subversion (SVN) came along. Subversion intended to be “a better CVS”, perhaps this goal should have made us suspicious at the time since CVS was already being a pretty good CVS by itself; unfortunately we hated CVS so much we flocked to the new system in hope. In hindsight, Subversion didn’t really improve on CVS much at all. In fact, arguably, the only real improvement was the addition of atomic commits (in CVS, each commit is per-file, so it’s manual labour to work out which change was made to two files at the same time). (Its support for branching, tagging, copying, renaming, etc. were no better than CVS’s when done in the repository by hand.) The cost of this single new feature was a much more complicated interface (with two separate commands), a backend that tended to break down weekly and a lethargic slowness to its operation. Most people I know now justify their use of Subversion instead of CVS by “Subversion is maintained, CVS isn’t” which is a somewhat self-fulfilling justification. While the mass conversion to Subversion, and ensuing disappointment and frustration, was going on; something new appeared on the horizon: Arch. Arch was different, it broke one of the core assumptions of revision control, that of the repository as a cathedral. In CVS, and Subversion like it, if somebody wants to modify your code (even if on a branch) you need to give them access to your own repository. In some cases (especially with CVS), vast access control and permission structures would be in place to ensure proper behaviour. With Arch, you don’t; all you need to give to anyone is read access. Anybody can make their own branch by copying yours and committing to their own copy. This model also necessitated fixing a long standing problem that CVS had; Arch has repeatable (smart) merging. If you merge from a branch, you can merge again later, and again, and again. Arch made this possible through each commit (changeset) having a globally unique identifier; made from the branch’s own globally unique identifier and the changeset number in the branch. Unfortunately while this was a massive step in a new direction, Arch had an absolutely terrible user interface. Its command list was terrifying with over 100 commands, many of which had multiple word names (tla set-tree-version). It exposed too many of its own innards, and expected you to learn them. It also forced baroque file naming semantics on its users and strange policy (though shalt not commit without first running “make clean”). Efforts were made to improve Arch’s user interface through projects such as baz, but they were always to be doomed from the start. We’ve since seen an explosion of new revision control systems; Monotone, Darcs, Git and Bazaar. What’s especially interesting is the commonality between these systems. They are all “distributed” like Arch, though they also all discard the strange “unique branch identifier” convention and instead simply assign a unique identifier to each file or commit. This means that they all support personal branches, and by necessity all support repeatable (smart) merging. So how do they differ, what are their killer features and killer problems? Monotone is all about repository integrity, ensuring that every commit is both authorised and intact. It pays for this with a severe lack of speed. Darcs is based around a “theory of patches”, a branch is not made up of its history but by the collection of patches in it. Unfortunately this often breaks down, and darcs frequently gets stuck calculating even trial and commonplace branch models. Git is very strange to me; its killer feature appears to be the speed at which it can handle very large trees, but the interface is as insane as Arch’s was. It is heavily optimised for the “I only apply patches” development model, at the expense of ordinary development models (it shares an issue with Arch where calculating annotations on an individual file is an expensive operation). What about Bazaar? Its killer feature is that it is designed to work the way you do. The command set is relatively small, and each of them works in the most obvious manner. It also supports plugins so that you can always implement your own workflow. Of all the revision control systems, it’s the only one (that I’m aware of) that supports both distributed and centralised workflows (and lets you go distributed when you need to, e.g. when you’re on a plane). Here’s a few examples of how Bazaar’s command set works the way you do. To start managing some code in bzr:
$ cd myproject
$ bzr init
To add the files, copy in your usual .bzrignore file and just add everything:
$ cp ~/bzrignore .bzrignore
$ bzr add
added foo.c
added bar.c
Check the output for mistakenly added files, adjust .bzrignore and remove the file with bzr rm. A common operation is realising that the commit you’re about to make should really go on a new branch for now:
$ cd ..
$ cp -a myproject myproject-foo
$ cd myproject-foo
$ bzr commit
A copy of a Bazaar branch is a different branch, you can commit to it separately. There’s a bzr branch command for it too (which deals with issues such as bound branches, checkouts, etc.) but it’s nice to demonstrate that Bazaar does what you’d expect even when you don’t use its own commands. Pulling changes from another branch (where you haven’t made any modifications yet) is easy:
$ bzr pull ../myproject
As is merging (when your branches have diverged):
$ bzr merge ../myproject
One particularly nice feature is that after a merge, you see the merge as a single commit and it can be treated as such; but it also has the set of merged commits indented under it–you can examine these as individual commits as well! What’s the downside of Bazaar? Well, it’s not the fastest system (but by no means the slowest), for small to medium sized projects this is never an issue but may be for extremely large projects–fortunately the developers are improving its performance all the time! But that doesn’t matter; it is, honestly, the first revision control system that I don’t hate.

MJ Ray: Places to Visit / Re: WSM Season?

I was trying to figure out when "the season" ends in Weston, but it's not obvious any more.

The seafront/Sand Bay bus service reduced at the start of September (end of the Peak Summer open-top service) and again on the 22nd (end of the Summer service), which makes things a bit less convenient, but that's about the only major change I can spot.  Some of the council services reduce in winter, but that won't really affect tourists.  I asked a neighbour who works at a holiday park and he said they're still busy and won't really be quiet all winter, except about four days closed around Christmas.

I'm not a big fan of autumn, but it's better here than many places, with several good firework events to cheer things up and then the town carnival, which I think is linked to Bridgwater's somehow, so looking at their gallery will give an idea of what's coming.
http://www.bridgwatercarnival.org.uk/carnival_gallery/2006-gallery.php

Only downside of the carnival IMO is the travel chaos as large parts of the bus network shut down instead of routing around the road closures, so almost everyone hits the cars - but they can't reach some of the car parks because of the road closures...

Alastair McKinstry: GIT Changelog comments

My job involves working on other peoples scientific codes, and recently I've been experimenting with using GIT as a VCS. Its very handy for making a quick repository while you change one or two files, nice and lightweight. What distinguishes science codes from other software projects, both open-source and proprietary, is the comparative lack of formal releases. Often the developers are the users, making changes for their own use. They make a model, write a paper, done. They'll take their old code and edit it to add features, but don't plan on "releasing" it in any formal way. So, often you get a tarball from a fellow researcher with the name 'astro.tar.gz', and beyond the paper describing the science, you'll be lucky to find a changelog. Online repositories, test suites, etc. are a rarity. So I've been wondering how to improve on this, in terms of refactoring, etc. and how GIT and other Distributed VCS's can best be used in science. Some ideas: Has anyone else seen similar techniques or tags in use, particularly for science ? Tags , ,

Raphaël Hertzog: DSA needs a leader

Seriously. Now that we have been using the request tracker for quite some time, it’s even more obvious that the DSA team is not up to its task. Use login “guest” and password “readonly” if you want to check the RT tickets linked in this article. The facts Note that myself and Matt do not have the needed rights to fix most of the tickets, so we provided help on a best-effort basis. Otherwise we would have done more. The communication problem It’s a multi-level problem. Each of the members has some problems with one or more other members. Joey’s behavior has been part of the recurring problems mentioned: he doesn’t use the RT, doesn’t read the DSA email alias and doesn’t follow the DSA IRC channel but he still does stuff very regularly without reporting anything and obviously problems happen. Ryan and James tried to impose him a rule to document what he does, without success apparently. On the other side, as far as I know, Ryan and James also don’t impose themselves to document everything in a central changelog. Joey has refused to provide me an explanation for his behavior. He just reminded me that he holds grudges against James and Ryan because as ftpmasters they didn’t cooperate well with him while he was stable release manager. In general, outside of all personal griefs that they might have, the DSA members do not communicate very much (at least not on their own official channels). Some examples have already been given concerning the request tracker, but it’s not much more effective on IRC. Most of the traffic on the channel is made up by local admins fixing the problems themselves without any intervention by any DSA. I also use the channel to regularly ping some DSA about simple issues and/or stuff that they usually handle. It used to work somewhat but lately fil has been busy (with the kernel summit and other conferences) and I simply got no answer at all… for example I pinged elmo, neuro and fil several times in the last weeks in the hope that they handle the tickets of the security team (#150, #157, #164) without results. There’s room for improvement. The leadership problem The team has no designated leader and every time that there’s a decision to take, they are blocked. Joey wouldn’t communicate and give his opinion, Ryan is extremely requiring and perfectionist, there’s not much room for compromise… A long time ago in a galaxy far, far away, Joey and elmo were friends. It’s even Joey who gave root rights to elmo. Nowadays, it’s rather James that is sort-of leading the team but he’s fed up of the situation and hasn’t managed to get out of this mess. He refuses to take drastic measures by himself because he’s not clearly the leader and doesn’t solicit a decision of the Debian leader (or the project) because he believes that the DSA team is not under the scope of the constitution! This can’t last any further. We’ll have to do something about it. Stay tuned.

Eddy Petrișor: svn-buildpackage pending changes

Just a few snippets:

Author: eddyp-guest
Date: Wed Sep 26 02:14:15 2007
New Revision: 4959

URL: http://svn.debian.org/wsvn/collab-maint/?sc=1&rev=4959
Log:
create a special branch for the svn "mkdir -p" like functionality until all scripts are converted to use this function and more tests are done

Added:
deb-maint/svn-buildpackage/branches/svnmkdir-p/
- copied from r4958, deb-maint/svn-buildpackage/trunk/

0 eddy@bounty ~/usr/src/svn-buildpackage/svnmkdir-p $ dpkg-parsechangelog
Source: svn-buildpackage
Version: 0.6.22
Distribution: UNRELEASED
Urgency: low
Maintainer: Eddy Petri or
Date: Wed, 26 Sep 2007 05:24:59 +0300
Closes: 408690 411666 414581 419996 423487 428225 428689 433404 433536 434932 435746 436133
Changes:
svn-buildpackage (0.6.22) UNRELEASED; urgency=low
.
[ Eddy Petri or ]
* IMPORTANT: changed default behaviour of saving the configuration in
.svn/deb-layout by default to avoid stale data to override the
configuration options that were updated in the repository.
(Closes: #414581)
As a consequence, a new option --svn-savecfg was added to allow a
mechanism for easily overriding options locally
.
[ Gon ri Le Bouder ]
* SDCommon::sd_exit: read the parameter correctly is SDCommon::nosave=1
(Closes: #428225)
.
[ Eddy Petri or ]
* s-u: when importing options from ~/.svn-buildpackage.conf, filter in
only the valid options (Closes: #428689)
* s-u: replace retcode with retval for consistency with svn-bp
* s-i: manpage still claimed layout 2 was not implmented (Closes: #433404)
* s-i: now really supports injects for layout 2 (with the disadvantage of
not creating the tag directory)
* s-i: no longer fails on initial checkout (Closes: 411666)
* when using origUrl, make sure the origDir exists before downloading
in it
* s-i: man page: document the missing -o option (Closes: 419996, 435746)
* s-u: complete the man page synopsis section (Closes: 436133)
* s-b: do not require the build deps to be present when exporting
(Closes: 423487); thanks Stefano Zacchiroli for the patch
* SDcommon.pm: enhance the guessing algo of the layout to make svn-upgrade
guess correctly on layout 2 repos; thanks Gregor Herrmann for the patch
(Closes: 434932)
* Makefile: the version of the package is placed quoted in "SDCommon.pm" so
that versions like "0.6.22~bpo40+1" don't cause s-b to barf
* SDCommon.pm: implemented a function that emulates a 'mkdir -p'
functionality for svn; this will allow a fix for #434932
* s-i: based on the mkdir-p functionality create missing directories on
inject (Closes: 433536, 408690)


Jaldhar Vyas: The Proof Of The Pudding Is Under The J Key

Pudding

25 September 2007

Christian Perrier: RWC: AUS-FID, NZL-SCO

Sunday was a quiet day for the top teams. Neither Australia nor New Zealand were in danger against Fidji (55-12) or Scotland (44-0). I'm still impressed by the australian team. They didn't show much weaknesses against Fidji, despite the strong physical contest bringed by the Fidjian forward players. The australian rear lanes were impressive, particularly Matt Giteau, scoring 27 points and designed as MVP for Australia-Fidji. The All Blacks crushed a B team from Scotland. The scottish staff decided that winning against New Zealand is nearly impossible and therefore they choosed to have their key players resting, which is a wise choice, but not a gift for the Murrayfield supporters. As a consequence, New Zealand quitely won the match and therefore qualifies for 1/4th finals (and they'll win their pool unless Romania plays with 30 players against them....). No match for yesterday and two matches today. Unfortunately, Canada-Japan (12-12) in Bordeaux was broadcasted too early for me and I haven't seen it. For Japan, this is the end of 13 consecutively lost matches in RWC for Japan, so kind of victory. I've seen parts of Romania-Portugal. I wished Portugal wins that one as they're clearly the most courageous team in the RWC and certainly, among the non top teams, the most promising one. The Portuguese lost 10-14 even though they lead 10-7 for a while. Quite a deception for me but surely these players will never forget the support of the French crowd (most of these being the strong portuguese community we have in our country). Tomorrow will feature Georgia-Namibia and Samoa-USA. I'll try to watch the latter, which is played in St-Etienne, my welcoming home town (ask the Scots supporter and team!).

Simon Richter: suddenly, holidays

Well, still in the planning stages... The general idea is to get a largish house in Denmark for one or two weeks, share the cost among ten people, and live a life of debauchery for one or two weeks, probably in the first or second week of January.

Next.

Previous.