Search Results: "ag"

13 February 2010

Joey Hess: web minimalism

After Wired attempted to redesign Craigslist, (with predictably bad results) a opinion piece (paywalled) in the WSJ suggests that Craigslist's look is what users really want. I'd take that a step further... The original design of HTML 1.1 and its presentation in early web browsers gave users what they really wanted. Black and white text, that goes all the way across the screen, is readable on any screen, and scrolls all the way down to the end of the document. Links. Maybe some images. No foofaraw of sidebars and mastheads; no bother with zooming to make the content part of the page readable, no need to search the cluttered page to find the print button so you can read the whole article without clicking "Next" 10 times. We didn't know it at the time, but that was a subtle part of the early appeal of the web circa 1994. The minimalism sucked you in, it made the web feel like one coherent, unified thing, unlike the constellation of corporate edifices occupying much of it today. In Craigslist, early Google, somewhat in Wikipedia, I see echos of that minimalism, filtered through all the ways that have emerged to enhance, and pollute the original vision of the web. So, how long until a resurgence in web design minimalism? PS, It's really no accident, nor is it entirely due to laziness that my own site looks like it does.

Ingo Juergensmann: BackupPC - messing around with backups

I'm using BackupPC to make backups from one computer to another. Usually no big deal, but between the two machines there's a VPN connection across two dialup connections and 450 km air line. So, there is a maximal usuable bandwidth of about 1 Mbps between both locations. The problem was now: host A (the machine which is backupped) was initially backupped by host B (the machine running BackupPC) when host B was still located right beside host A. In the meantiime host B has been moved to its remote location and there I excluded one or the other directory in the following backup. Now I wanted to include them again, thinking that BackupPC is clever enough to realize that those directories are already in the backup #0.

Sadly, BackupPC seems to just compare the latest full backup without considering the partial backup, that was filled during the last 14 days over the 1 Mbps link. So BackupPC began to pull all the 200 GB of data again, although it already got roughly 180 GB in the partial backup. The cause for the partial backup was a longer connection timeout between the two dialup hosts.

Because I don't wanted to pull all 180 GB again and again and again, I looked for another solution for the problem. And it is quite simple. Given are a full backup #0 and another backup #7. #0 is the initial, complete backup before the relocation. Backup #7 is the backup after the relocation where I omitted some directories that contains 200 GB of data. Backup #8 is the partial backup. What I now did was this:



BackupPC will now base its freshly started full backup on the directory contents of backup directory 9. When the backup finished, you can delete that backup directory #9 again. This works quite well for me and the transfer with rsync. Maybe there are other methods dealing with that problem. Feel free to leave some comments.

Dirk Eddelbuettel: Rcpp 0.7.6

The new 0.7.6 release of Rcpp, our set of R / C++ interface classes, is now at CRAN and Debian. This comes just a few days after 0.7.5 as we had made a mistake in Makefile.win which is now fixed. A few other things sneaked in while were at it, see the snippet from the NEWS file below or look at Romain's blog where he highlights named-based indexing in vectors and the addition of iterator as well as begin() and end() members that now allow the use of STL algorithms on our R objects which is nifty. The changes are summarised below in the NEWS file snippet, more details are in the ChangeLog as well.
0.7.6   2010-02-12
    o   SEXP_Vector (and ExpressionVector and GenericVector, a.k.a List) now
	have methods push_front, push_back and insert that are templated
    o   SEXP_Vector now has int- and range-valued erase() members
    o   Environment class has a default constructor (for RInside)
    o   SEXP_Vector_Base factored out of SEXP_Vector (Effect. C++ #44)
    o   SEXP_Vector_Base::iterator added as well as begin() and end()
        so that STL algorithms can be applied to Rcpp objects
    o   CharacterVector gains a random access iterator, begin() and end() to
	support STL algorithmsl; iterator dereferences to a StringProxy
    o   Restore Windows build; successfully tested on 32 and 64 bit;
    o   Small fixes to inst/skeleton files for bootstrapping a package
    o   RObject::asFoo deprecated in favour of Rcpp::as<foo>
As always, even fuller details are in the ChangeLog on the Rcpp page which also leads to the downloads, the browseable doxygen docs and zip files of doxygen output for the standard formats. Questions, comments etc should go to the rcpp-devel mailing list off the R-Forge page

Mike Hommey: When will Iceweasel 3.6 come ?

That is a question I hear more and more, and I felt it had to be answered publicly. Short answer: when it s ready. The current target for Squeeze is 3.5, for various reasons, but the main is that it shares the same Gecko version as Iceape (SeaMonkey) and Icedove (Thunderbird), which means that while the security team (or myself) will have to update these three for security updates, they will share patches. So 3.6 is less a priority than having 3.5 in shape for the release. Last week, I wrote on a mailing list post that I was expecting 3.6 to come this week. Well, that was before I discovered the sad reality about the state of the current version. But 3.6 is still on the radar. I already went through all the patches we apply on 1.9.1, and rebasing should now be straightforward. Most of the 3.5 failures have now also been addressed: sparc and powerpc were fixed first, and I am now (re-re-re -re)building on arm for, I hope, the last time. Unfortunately, mips is still missing, and without a porterbox, I can t do much. I tried, some time ago, in qemu, but there is no way I m going to wait 50 hours for a build again ; it was already painful on a real arm box (where it takes 90 minutes just to link libxul.so). Anyways, 2 patches stolen from upstream and 5 patches sent (or almost sent for the one currently under validation) later, we should be down to one release architecture failing instead of four. Which is already good. On the other hand, a new 3.5 upstream release, with security fixes, is planned for next tuesday, which means some time will have to be spent for stable updates, too. So, in the next few days, expect that I ll be working on stable security updates, then unstable updates, including the three architectures fix, and then work on 3.6 will continue. Which means we can hope for a 3.6 release in experimental by the end of next week, or the following one, in the worst case. Update: *sigh* 4 patches on arm is not enough :(. At least this time I think I m done with xptcinvoke and xptcstubs. Update:In the end, 2 patches and disabling the JIT compiler did the trick on arm. The 2 other patches were actually addressing bugs that only existed because the JIT is doing something wrong with the stack alignment.

Martin F. Krafft: ACTA: less knowledge means less resistance

Right now, your government is probably engaged in the discussion of the Anti-Counterfeiting Trade Agreement (ACTA). You are likely not aware of that because your government has been actively keeping these negotiations and details surrounding them secret. Your government does not want you to know about a treaty that has far-reaching negative effects on your freedom, as well as your basic human rights. If you did know, you might speak up and make it difficult for the drivers of ACTA to smoothly push their interests past you. The red light should light up in your head right now! The goals of the trade agreement that is being negotiated are multifarious, but essentially seem to centre around challenges related to intellectual property, and copyright in the digital age, even though it is sometimes claimed that the agreement serves primarily to contain trade of fake Prada bags and Rolex watches. In reality, ACTA is about content producers like movie studios, who try everything to prevent you from copying their work without paying for it even if you cannot actually purchase the work, because of e.g. technical measures designed to prevent certain people from legally obtaining content, or simply because the media companies are greedy and consider it PR-savvy to delay the release of a given work in certain countries until after people have had a chance to pay a lot of money to the cinemas. In theory, a creative work goes out of copyright 50 or 75 years after its author died, depending on whether the creativity can be attributed to a person or a corporation, respectively. Therefore, 50 or 75 years after creation, it gets increasingly hard to monetise a work that has not been reinvented in that period of time. Sounds plausible to you and me, but this sort of stuff frightens companies like Disney, who seem powerful enough to simply have the law changed. That is not how things should work. The media producers are failing to control the Internet, and hence they want to turn it into something more like cable TV, which they do know how to control. ACTA aims to make copyright infringement a criminal offence. ACTA wants to make it possible for a government to cut you off the Internet because someone thinks you did something bad they don t actually have to prove it though, accusation is enough. Similar efforts have already failed all over the world, e.g. in France and New Zealand. That s a sign, not a reason to try again. ACTA wants to set in stone that you have absolutely no rights when you cross borders. This is largely already the case border officials can pretty much do with you whatever they want now it s supposed to be made official, and legally binding. ACTA will create a culture of surveillance and suspicion. ACTA is designed to break the Internet, among other things. But worst of all: I am just speculating because we are not supposed to know the details. The best current source of information on ACTA seems to be Canadian law professor Dr. Michael Geist, who has been collecting content and linking to articles consistently since the ACTA negotiations commenced 2 3 years ago. The Electronic Frontier Foundation also has comprehensive resources available. It s even more important today than before to put an end to this secrecy. Don t let your government enter secret agreements that affect you and your life, refusing to talk to you about it beforehand, and probably refusing all responsibility afterwards. Talk to your politicians and ask questions that cannot be answered with stock replies. If you have specific contact addresses for politicians, please let me know so I can add them. Colin Jackson helped me with this article at Kiwi Foo Camp. He also takes an issue with the secrecy around ACTA.

12 February 2010

Josselin Mouette: The Debian/GNOME bug weekend

Do you like Debian? Do you like GNOME? Are you free on February 27-28? If so, please reserve your week-end, because you are going to help us do a massive cleanup in the insane amount of bugs submitted against GNOME packages. You don t need any special skills. Just join on #debian-gnome and we ll provide all the guidance you need. Ultimately, the goal is to have, at the end of that week-end, all bugs against GNOME packages in one of those states: After this, maybe the BTS can become useful again for the GNOME team.

Sandro Tosi: Italy has (again) a PHP.net mirror

After a long time of no Italy mirror, now PHP.net has enabled it.php.net, kindly sponsored by Register.it.

Why am I happy? Because I did it! :)

Sandro Tosi: This RRD was created on another architecture

That is the message you'll receive when trying to open a RRD database created on a 32bit machine from a 64bit one (it's also true the reverse). It's due to the fact that RRD is an architecture-dependent file format: endianess and integer bits length matter.

That's quite boring, given it's quite common to let each machine generate its own RRDs and graph them from a central place, and the more machines you have, the more chances of the above problem.

So, for another example, if you migrate one machine from 32 to 64 bits, you'll have to:
as described here. And when you have +4GB of RRDs it's not so painless.

So, can we haz an architecture independed RRD file format? Pretty please?

It was planned for 1.4, and now that 1.4 is release it's planned for 1.5. Let's hope it comes soon, it would be really nice! :)

Joost Yervante Damad: Nokia N82 Bluetooth + GPRS/3G

A few months ago I did an interesting discovery about using my cellphone to go on the internet via bluetooth. I had this strange situation before where it just stopped working, and after revisiting all configs it worked again. What really happens is that my cellphone somehow crashes, after which I power cycle it by removing the batteries. The phone then boots again, but here is the twist: the service channels in the phone are re-allocated and apparently in a random order! This implies that the RFCOMM channel configured in the /etc/bluetooth/rfcomm.conf file is possible wrong now! Solution: just browse the services again with sdptool browse, adapt the file and it should work again!

Wouter Verhelst: FOSDEM 2010...

... is over (for almost a week now), and it was a blast again. If you went to one of the distro devrooms, I would appreciate it if you were to reply to this mail. We need feedback to improve stuff for next year. Thanks. In related news, I've uploaded the slides of my (unexpectedly horrendously successful) talk here

Biella Coleman: Explosive Mural

A mural that geeks just might like. (via one of my students )

Biella Coleman: Explosive Mural

A mural that geeks just might like. (via one of my students )

11 February 2010

Robert Collins: Using UEC instead of EC2


So, we wanted to move a Hudson CI server at Canonical from using chroots to VM s (for better isolation and security), and there is this great product Ubuntu Enterprise Cloud (UEC basically Eucalyptus). To do this I needed to make some changes to the Hudson EC2 plugin and thats where the fun starts. While I focus on getting Hudson up and running with UEC in this post, folk generally interested in the differences between UEC and EC2, or getting a single-machine UEC instance up for testing should also find this useful. Firstly, getting a test UEC instance installed was a little tricky I only had one machine to deploy it on, and this is an unusual configuration. Nicely though, it all worked, once a few initial bugs and misconfiguration items got fixed up. I wrote up the crux of the outcome on the Ubuntu community help wiki. See 1 Physical system . The particular trap to watch out for seems to be that this configuration is not well tested, so the installation scripts have a hard time getting it right. I haven t tried to make it play nice with Network Manager in the loop, but I m pretty sure that that can be done via interface aliasing or something similar. Secondly I needed to find out what was different between EC2 and UEC (Note that I was running on Karmic (Ubuntu 9.10) so things could be different in Lucid). I couldn t find a simple description of this, so this list may be incomplete:
  1. UEC runs an old version of the EC2 API. This is because it hasn t implemented everything in the new API versions yet.
  2. UEC defaults to port 8773, not port 80 (for both the EC2 and S3 API s)
  3. The EC2 and S3 API s are rooted differently: at AWS they are at /, for UEC they are at /services/Eucalyptus and /services/Walrus
  4. UEC doesn t supply a SSL API port as far as I can tell.
  5. DescribeImages has something wonky with it.
So the next step then is to modify the Hudson EC2 plugin to support these differences. Fortunately it is in Java, and the Java community has already updated the various libraries (jets3t and typica) to support UEC I just needed to write a UI for the differences and pass the info down the various code paths. Kohsuke has let me land this now even though it has an average UI (in rev 27366), and I m going to make the UI better now by consolidating all the little aspects into a couple of URL s. Folk comfortable with building their own .hpi can get this now by svn updating and rebuilding the ec2 plugin. We ve also filed another bug asking for a single API call to establish the endpoints, so that its even easier for users to set this up. Finally, and this isn t a UEC difference, I needed to modify the Hudson EC2 plugin to work with the ubuntu user rather than root, as Ubuntu AMI s ship with root disabled (as all Ubuntu installs do). I chose to have Hudson reenable root, rather than making everything work without root, because the current code paths assume they can scp things as root, so this was less disruptive. With all that done, its now possible to configure up a Hudson instance testing via UEC nodes. Here s how:
  1. Install UEC and make sure you can run up instances using euca-run-instances, ssh into them and that networking works for you. Make sure you have installed at least one image (EMI aka AMI) to run tests on. I used the vanilla in-store UEC Karmic images.
  2. Install Hudson and the EC2 plugin (you ll need to build your own until a new release (1.6) is made).
  3. Go to /configure and near the bottom click on Add a new cloud and choose Amazon EC2.
  4. Look in ~/.euca/eucarc, or in the zip file that the UEC admin web page lets you download, to get at your credentials. Fill in the Access Key and Secret Access key fields accordingly. You can put in the private key (UEC holds onto the public half) that you want to use, or (once the connection is fully setup) use the Generate Key button to have a dedicated Hudson key created. I like to use one that I can ssh into to look at a live node YMMV. (Or you could add a user and as many keys as you want in the init script more on that in a second).
  5. Click on Advanced, this will give you a bunch of details like EC2 Endpoint hostname . Fill these out.
  6. Sensible values for a default UEC install are: 8773 for both ports, /services/Eucalyptus and /services/Walrus for the base URLs, and SSL turned off. (Note that the online help tells you this as well).
  7. Set an instance cap, unless you truely have unlimited machines. E.g. 5, to run 5 VMs at a time.
  8. Click on Test Connection it should pretty much instantly say Success .
  9. Thats the Cloud itself configured, now we configure VM s that Hudson is willing to start. Click on Add right above the List of AMIs to be launched as slaves text.
  10. Fill out the AMI with your EMI e.g. emi-E027107D is the Ubuntu 9.10 image I used.
  11. for remote FS root, just put /hudson or something, unless you have a preseeded area (e.g. with a shared bzr repo or something) inside your image.
  12. For description describe the intent of the image e.g. DB test environment
  13. For the labels put one or more tags that you will use to tell test jobs they should run on this instance. They can be the same as labels on physical machines it will act as an overflow buffer. If no physical machines exist, a VM will be spawned when needed. For testing I put euca
  14. For the init script, its a little more complex. You need to configure up java so that hudson itself can run:
    cat >> /etc/apt/sources.list << EOF
    deb http://archive.ubuntu.com/ubuntu/ karmic multiverse
    deb http://archive.ubuntu.com/ubuntu/ karmic-updates multiverse
    deb http://archive.ubuntu.com/ubuntu/ karmic-security multiverse
    EOF
    export http_proxy=http://192.168.1.1:8080/
    export DEBIAN_FRONTEND=noninteractive
    apt-get update
    echo "buildd shared/accepted-sun-dlj-v1-1 boolean true"   debconf-set-selections
    apt-get install -y -f sun-java6-jre
    
    Note that I have included my local HTTP proxy there just remove that line if you don t have one.
  15. Click on Advanced, to get at the less-common options.
  16. For remote user, put ubuntu , and for root command prefix put sudo .
  17. For number of executors, you are essentially choosing the number of CPU s that the instance will request. E.g. putting 20 will ask for an extra-large high-cpu model machine when it deploys. This will then show up as 20 workers on the same machine.
  18. Click save :)
  19. Now, when you add a job a new option in the job configuration will appear tie this job to a node . Select one of the label(s) you put in for the AMI, and running the job will cause that instance to start up if its not already available.
Note that Hudson will try to use java from s3 if you don t install it, but that won t work right for a few reasons I ll be filing an issue in the Hudson tracker about it, as thats a bit of unusual structure in the existing code that I m happier leaving well enough alone :) .

Romain Beauxis: OCaml cross compiler for win32 in Debian !

Thanks to the great work from Richard Jones on building a OCaml cross-compiler for windows, we now have a similar package in Debian ! The package is called mingw32-ocaml and has just been accepted yesterday. We have already used it to build a win32 version of liquidsoap. I hope that this cross-compiler will be useful to OCaml developers, in particular in porting their application to the world of windows and fences, in order to spread the word about how great OCaml is :-)

Joachim Breitner: Diploma Thesis Finished

Earlier today, I went to a local copy shop and had my diploma thesis printed. This afternoon, I will hand it in. The title is Loop subgroups of Fr and the images of their stabilizer subgroups in GLr( ) and discusses a group-theoretical result. I assume that very few readers care about the content of the thesis, but maybe some are interested in a few assorted LaTeX hints. I m also publishing the full TeX source code, maybe someone can make use of it. Less chatty varioref I m using the varioref package, in conjunction with the cleveref package. This provides a command \vref fig:S3S4l which will expand to, for example, to Figure 1 on page 11 . But if the referenced figure is actually on the current page, the next page, the previous page or the facing page (in two-side layouts), it will say so: Figure 1 on this page. This is very nice, but I assume that the reader of my thesis is able to find Figure 1 when it is visible, i.e. on the current or facing page. One can remove the referencing texts with the commands \def\reftextfaceafter , \def\reftextfacebefore and \def\reftextcurrent . But because varioref puts a space between Figure 1 and this text, we will get a superfluous space even before punctuation. The remedy is the command \unskip, which removes this space again. So I use in my preamble:
\def\reftextfaceafter  \unskip %
\def\reftextfacebefore \unskip %
\def\reftextcurrent    \unskip %
Palatino and extra leading I chose the Palatino font for my thesis, using the mathpazo package. Various sources (such as the KOMA-Script manual) suggest to use 5% extra leading:
\linespread 1.05 
Counting figures independently from chapters I don t have too many figures and tables in my thesis, and I want them to be numbered simple 1, 2, ... By default, LaTeX would say 1.1, 1.2, 2.1, ... This can be fixed using the remreset package and these commands:
\makeatletter
\@removefromreset figure chapter 
\renewcommand \thefigure \arabic figure 
\@removefromreset table chapter 
\renewcommand \thetable \arabic table 
\makeatother
No widows and club lines LaTeX already avoids these, but I wanted to get rid of them completely. This can be done with:
% Disable single lines at the start of a paragraph (Schusterjungen)
\clubpenalty = 10000
% Disable single lines at the end of a paragraph (Hurenkinder)
\widowpenalty = 10000 \displaywidowpenalty = 1000
Struck table lines I had to typeset tables with some lines struck, and I could not find a ready command for that. I used the following definition, based on the code for \hline. Note that it probably does not adjust well to other font sizes and needs to be adjusted manually:
\makeatletter
\def\stline %
  \noalign \vskip-.7em\vskip-\arrayrulewidth\hrule \@height \arrayrulewidth\vskip.7em 
\makeatother
Title page in one-sided layout According to the KOMA manual, the title page as set by LaTeX is not meant to be the cover of a publication, and therefore has to be set with the margins of a right page i.e. a larger right margin and a smaller left margin. But when printing cheaply, one often just put a transparent sheet on top of the print, so the title page is the cover. You can convince KOMA that you are right by using
\KOMAoptions twoside=false 
\begin titlepage 
...
\end titlepage 
\KOMAoptions twoside=true 
Not flushing the page for chapter heads LaTeX would put the list of algorithms on a new right page. I found this a waste of paper for my few algorithms, and preferred to put the list right after the table of contents. You can override the LaTeX behavior using:
\tableofcontents
 
\let\cleardoublepage\relax  % book
\let\clearpage\relax  % report
\let\chapter\section
\listofalgorithms
 
This code also reduces the size of the heading to that of a section. The same trick also works with \chapter. Math in headings vs. PDF bookmarks LaTeX with the hyperref package creates nice PDF bookmarks from your chapter and section titles. Unfortunately, PDF bookmark names can only be plain strings, while the titles in the document might contain some math symbols. You can make both happy with \texorpdfstring:
\section Stabilizer subgroups in \texorpdfstring $\GL_r(\Z/2\Z)$ GL\_r(Z/2Z) 
Setting lines for the signature The diploma thesis contains a small note which I have to sign, saying that I created it on my own etc. Below that, I put two labeled lines for date and signature, using the tabbing environment:
\begin tabbing 
\rule 4cm .4pt \hspace 1cm  \= \rule 7cm .4pt  \\
Ort, Datum \> Unterschrift
\end tabbing 

Alexander Reichle-Schmehl: [Updated] RC-Bug statistics for Squeeze, calendar week 6:

Back in the Lenny release cycle, I published some statistics of the release critical bugs. As we are (try to) get nearer to a freeze of Squeeze I think it's time to start that again. But first, a small explanation follows, what these numbers actually mean. If you look at our official bug tracking system currently lists 750 release critical bugs affecting the next stable release. While this number is kind of true, it is not accurate to use it to measure the state of the release. The unofficial rc bug thingy at bts.turmzimmer.net is quite more powerful to actual get some interesting numbers, as you can ignore specific kinds of bug and filter them properly. Note, that at the very end of the detailed list of the bugs you get the total number. With that interface you can for example filter them by different distributions. For example it currently lists 650 rc bugs in total for any distribution, but if you filter for squeeze bugs, you get only 518. That's a different number as the official bug tracker shows; I'm not entirely sure why, but a part of that difference is that both the official and the unofficial web pages are only synced periodically. Should someone be able to give a good explanation about the differences, please step forward ;) But let's play more: You can filter for bugs valid in squeeze-only, but not in sid. These bugs are already fixed in sid, but the packages haven't yet migrated to squeeze. Currently that are 94 bugs. We can furthermore ignore bugs only in sid; when squeeze is unaffected, we just don't migrate the broken package from sid to squeeze. The number that is most interesting for contributors is the number of bugs affecting both, sid and squeeze, as these are the ones which really need to be fixed as no fix is known, yet. So filtering for bugs for both we are down to 424 at the moment. But of these 424 remaining release critical bugs, we can still ignore some (for now). For example bugs concerning packages in non-free or contrib (9 currently) won't stop us from release, will they? There are also many bugs marked as pending (32), meaning that the maintainer is aware of the bug has a fix prepared and is just waiting with the upload a moment. Some of this bugs have already a patch (64), but no one reviewed it and uploaded it by now. You'll also see that you can ignore merged bug reports (47). That are bug reports reporting the very same bug several times. Finally there are bug fixes already uploaded to the so called delayed queue (6). This are bug fixes which where uploaded by someone else than the real maintainer, but to give the maintainer a chance to act on himself or to comment, the upload is delayed by some days before it will actually hit the archive. Currently 6 bugs are fixed by uploads to delayed. 17 bugs are claimed meaning that someone already said he will take care of this bug (but they are not finished, yet). You could also ignore the bugs invalidated by today's britney bug category, representing bugs which will vanish after the next migration of packages from sid to freeze, but as we are only looking at rc bugs in both sid and squeeze, this number will always 0 ;) That leaves bugs somehow other marked as fixed which are bugs (39) where I honestly have no Idea what they are... If someone can explain them, please do so ;) Here is a small tabular showing the above numbers:
Total:650
Affecting Squeeze:518
Squeeze-only:94
Unfixed bugs remaining in Squeeze:424
Of these 424 bugs...
... are pending32
... are patched:64
... are duplicates:47
... are in Non-free or contrib:9
... are claimed by someone:17
... are fixed in the delayed queue:6
... are somehow marked as fixed:39
Or in other words:
Release critical bugs left in squeeze, when ignoring all these:
260 That's a pretty number, isn't it? There are only 260 bugs left which need our immediate attention :) But that is a rather optimistic view of the situation. We e.g. assume that all bugs having a patch are really fixed by the patch. We also ignored, that some bugs in squeeze are already fixed in sid, but the package can't migrate because the package in sid contains a new bug. (Which happens to release wizard Marc Brockschmidt quite often.) So if we take off the purple classes and take a more pessimistic view (release mangers must be pessimists to ensure high quality packages ;) we count the bugs in squeeze and ignore only those bugs, which are: With this release managers views, 424 bugs remain to be fixed somehow before we can release. As far as I know, we can freeze once that number is reliable under 300. So we better get working ;) When asked, what is the thing mostly needed to help the release, I was told: mips porter!
As you might have read we have some problems with the mips and mipsel architectures. It seems we have all the hardware we need, but it doesn't work very reliable. I have been told, that over 300 packages are only waiting to be build on mips* architectures. So if you can help us in that regard, please contact our mips porter mailing list. Update: Andreas Barth just told me, that he already send a couple of mails to the mips list describing the problem and asking questions. Answers to these questions would be most welcome and accpeted gladly.

Michal &#268;iha&#345;: Preparing for Google Summer of Code 2010

It might be quite premature, but in phpMyadmin we've started our preparations for this year Google Summer of Code. This is basically just one of followups to the team meeting at FOSDEM, where we decide to apply again this year, but to try as hard as we can to be standalone project and not hidden inside of MySQL. We're grateful for participation in their project, however we feel it would be easier to manage if we're standalone project. So if you are a student who might be interested in participating, you can already browse our ideas list (this time PHP coding skills are not strictly necessary as I've given there a documentation improvements also) or come with your ideas and follow our student checklist, to see what you can do to get accepted (in case we're accepted to GSoC).

Asheesh Laroia: Google and University email

Should universities switch away from hosting their own email and join the Google bandwagon? Adi Kamdar wrote to the Students for Free Culture discussion mailing list linking us to a Yale Daily News article discussing an "almost-definite" switch for Yale to Google Apps for Education. Adi asked for thoughts, so here are mine.

Privacy One interesting thing about the Gmail option is that, when deployed for all students, students have no choice but to let Google read their official email. Some students might take part in activism that they want to shield from Google, a corporation with its own interests, or the attackers that attempt to break into Google's systems (see the recent attacks from crafty pro-Chinese-government hacktivists). Before a switch to Gmail, each student could choose if Google was the kind of company they wanted to share their email with. After a switch to Google Apps, the choice is made for them. But this highlights a different issue: Before a switch to Google, students have no choice but to let university administrators read their official email. That's not necessarily optimal, either. Others have pointed out in this thread that this option comes with legal advantages with regard to privacy law. At least that's some consolation. It's still true that students can encrypt their email and make it difficult for any eavesdropper to figure out the bodies of their emails. But that's no use for hiding the identities of the people with whom they communicate -- no email crypto I know hides email addresses.

Software freedom and open standards This is juxtaposed against another difficult situation: Matt Senate wrote about the sucky Squirrelmail system that Berkeley uses (used?) for webmail. The fact that SquirrelMail is Free Software is small consolation for Matt. From his perspective, because it's a hosted web application, he has no more freedom than he would have with Gmail. At least Berkeley's IMAP server followed standards! That's more than we can say for the Gmail IMAP server, which is famous for basically supporting just enough IMAP for Microsoft Outlook to work. But standards compliance is small consolation. If the university email server "properly" supports IMAP, but isn't fast or doesn't provide the new extensions that make threading or search speedy, it's not much relief to know that you can use any client you want to slowly read your email.

Internet history Truth be told, University-hosted Internet services are based on what you might call the original Internet perspective. The Internet began as a network of networks. A University was a network island unto itself, running its own email, news, and Ethernet services. When inter-network connection was available, you can email people at other institutions. When it wasn't, well -- the Internet is a useful tool, but it's down right now. "Don't worry," the admins might tell you, "you can still read your email with PINE." It used to be that inter-network connectivity was icing on top of the "real" network a person used. Today, inter-network connectivity is the whole point of a network connection. How embarrassing for each individual network! To test if our connections are working, we skip right over the local content and point our web browsers at a search engine. Users today aren't satisfied to read their email from imap.institution.edu and read USENET news-- they thirst for real-time access resources available beyond the university. Students weren't interested in the J-Stream service I helped set up at Johns Hopkins; instead they mostly posted and watched videos at YouTube. They don't really care if the the student-oriented wiki is based on campus or instead halfway across the globe (say, in Japan). The original Internet was based on autonomous networks and opt-in routing. But eventually, all the networks opted in. Users drive everything, and when they don't get what they want, they vote with their feet. Companies like Facebook and Google stand ready and armed to provide shockingly-efficient services to millions of users who choose them. You could say that with today's network, the autonomy shifted from the network to the users. The nice thing about University-run services is that students can organize and ask for changes, as Fred pointed out. And for people like me, there's something nice about knowing the person who runs your email system. But if your busy university staff doesn't have time to investigate an email server with fast full-text indexing, you might wish for change. Having the university tear down its internal services is a progression toward seeing its network as simply transit. Imagine the loss of pride. It used to be that the university personally ran a system for helping users get what they wanted. As it becomes simply transit, the staff are just greasing the cogs of a larger, invisible machine that's easy for users take for granted. Some netizens like me hold email as sacred, a beautiful institution based on standards and a decision to interoperate. When your university switches to Gmail, I'll be sadder, but maybe what you'll get is professors who can spend more time with students and less time configuring desktop software.

Trade offs Every university has a choice: Pay hundreds of thousands to millions of dollars a year for dedicated staff to run an in-house email system, or let Google do it. Think for a moment of what good could come from those dollars when put to use in other ways for students. Your school could start a switch to all-organic food. It could start paying more of its employees a living wage. Imagine the travel funding for student activities that can come from hundreds of thousands a year well-spent. It could run a massive used textbook clearinghouse to help students avoid pouring their dollars into the textbook industry. And now cry with me. What I've asked you do is to consider sacrificing institutional autonomy for cold, hard cash. That's to say nothing of the ecological benefits or the productivity increases possible from having Google's paid experts run this part of the computing system.

Conclusion Is an official Google email system much different than the reality most students I know live, which is configuring their student email address to forward to gmail.com? For those of us who would be sadder with one more push toward centralizing email with Google -- for those who see it as the behemoth whose size threatens the decentralization that used to be the core of the Internet -- I ask you to think positive. "See the profit from your loss." I have no conclusions for you, just niggling questions.

10 February 2010

Bernd Zeimetz: BSP2010 a great success - 200 bugs eliminated

Some of the participants of the BSP here in M nchengladbach asked me to put the blog post from blog.credativ.com on planet Debian. I think thats a great idea as the BSP was not only successfull, but also a lot of fun and it was very nice to meet a lot of Debian Developers and package maintainers. We were glad that so many people followed the invitation! So here we go - please leave your comments at the original blog post.

Debian Logo
The 2010 Debian Bug Squashing Party turned out to be a great success: around 200 bugs were fixed, ready for the forthcoming version of Debian. The weekend of 22-24 January saw this year s Bug Squashing Party hosted yet again by credativ. The aim of the weekend was to find and fix bugs in the next Debian release. The results were as follows:
Work on Debian Results
Installed Patches 5
Fixed Bugs 44
Non-critical Bugs 28
Completely removed Packages 87
Packages removed from Testing 29
Altogether that gives a grand total of 200 bugs. In addition, information was gathered on a further 100 bugs, which will help when they come to be fixed. A lot of time was also spent on quality assurance, an under appreciated but very important job. More gossip: it is rumoured that backports.org is not far off becoming an official Debian project and in the meantime it will be launching a brand new website running on ikiwiki. Our guests from far and wide were more than happy with the BSP party: Steve McIntyre: (Debian project leader)
Thanks to the folks at credativ for hosting and participating in the BSP - we got a huge amount of work done towards the next release and had a great time doing it!
Stefano Zacchiroli:
My 1st M nchengladbach BSP, won t be the last! Lots of cool people and hacking, and I ve enjoyed my 1st traditional Formorer s chilli too :).
credativ would like to thank all those who came and got involved - now you can lean back, relax and enjoy the photos of the event.

Biella Coleman: Suffering from MEAD?

If I told you that you suffer from MEAD you might think (if you are an anthropologist like me) that you suffer from an obsession with a plump anthropologist of said name who popularized the discipline bringing home tales of Samoan teenagers who did not seem to suffer from the angst and anxiety of their American counterpart. Or you might think MASSIVE EMAIL ANXIETY DISORDER, which is a DSM diagnosis I invented last week and thus have minimized the work that the American Psychiatric Association will have to put into updating their DSM (you re welcome). So I have penned down its major characteristics and effects so that you too can identify with some other inner pathology that might mark your daily life and being (you re welcome)

The Diagnostic and Statistical Manual of the American Psychiatric Association currently defines Massive Email Anxiety Disorder (MEAD) disorder in the following way. Please note that while this definition of MEAD is the most definitive and clearly produced to date, there are several potential problems with this definition that will hopefully be addressed by the task forces, editors, and research coordinators of the association as time progresses. The Current DSM-IV Definition (Abridged): A. A persistent fear of one or more emails situations in which an author of an email worries about the status of a sent email. The individual fears that the tone or content of a message was misinterpreted or that an email never arrived to its correct destination. Alternatively, they worry excessively about why they have not received a response. B. Exposure to the feared situation almost invariably provokes anxiety, which may take the form of a situationally bound or situationally pre-disposed Panic Attack. C. The person recognizes that this fear is unreasonable or excessive. D. The feared situations are avoided or else are endured with intense anxiety and distress. Alternatively the person suffering from MEAD shuffles over to their partner or office-mate to talk (obsessively) about the nature and possible effect of the email, sometimes for hours, sometimes even for days. E. The avoidance, anxious anticipation, or distress in writing email, which interferes significantly with the person s normal routine, occupational (academic) functioning, or social activities or relationships, or there is marked distress about having the phobia. F. In individuals under age 18 years, the duration is at least 6 months. G. The fear or avoidance is not due to direct physiological effects of a substance (e.g., drugs, medications) or a general medical condition not better accounted for by another mental disorder. Problems with the DSM Definition of Massive Email Anxiety Disorder While this definition is clearly the most definitive and precise official definition produced so far, Massive Email Anxiety Disorder has only been officially recognized since 2020, and the problem did not become adequately explained until the 2015 version of the DSM. Thus, the definition of MEAD disorder is becoming clearer and more precise with each edition.
Written in honor of current revisions for the DSM, expected to be published in 2013

Next.

Previous.