Search Results: "ag"

15 March 2008

Daniel Burrows: aptitude 0.4.10 released

I've just released version 0.4.10 of aptitude, a terminal and command-line package management tool for Debian. This release has many user-visible changes (see the changelog below). It also fixes an annoying and much-reported segfault. The Debian packages of this version are built against the new version of cwidget, which is sitting in NEW, but if you're impatient you can compile it by hand by dropping the versioned dependency. The dependency is there to ensure that we don't get dependency skew across architectures (aptitude depending on libcwidget0 on some archs and libcwidget1 on others) and doesn't represent an actual build requirement of aptitude.
[12/15/2007] Version 0.4.10 Oscillating Reindeer
  • New features:
    • In command-line mode, if the resolver fails to produce a solution for whatever reason, then instead of aborting the program entirely aptitude will now display a prompt at which you can fix the dependency problems by hand. Enter r at this prompt to try to automatically fix dependencies again.
    • safe-upgrade will now install new packages to fulfill dependences (but it will never remove packages, downgrade packages, or install a version that's not the default). The option --no-new-installs will disable this behavior.
    • Updates and commands that install, remove, or upgrade packages will now display a brief summary of what changed. For instance:
      There are now 64 updates [+10], 3 new [+1].
      
      Unfortunately, this change requires reading the cache after an update is complete. Passing -q will disable this behavior, but also make the update progress bar less attractive. More work on resolving this tension between features and performance remains to be done.
    • Add an option --allow-untrusted to override trust warnings. (Closes: bug #452201, bug #452541)
    • Recommended packages are now hidden if quiet mode is enabled. (Closes: bug #452202)
    • The options Aptitude::ProblemResolver::Trace-File and Aptitude::ProblemResolver::Trace-Directory allow you to generate a minimal cut of the cache that allows a problem resolver run to be reproduced. The eventual aim is both to simplify bug reporting and to generate a corpus of automatic test cases for the resolver (although more work needs to be done to accomplish the latter).
    • When run in command-line mode, instead of displaying many separate and sometimes duplicative groups of packages (e.g.: installed, auto-installed, auto-installed in a light cream sauce, etc), aptitude displays packages in a few exclusive categories and uses tags (like the existing purge tag) to provide more state information. For instance:
      $ aptitude -s install wesnoth
      The following NEW packages will be installed:
        wesnoth wesnoth-data a  wesnoth-music a 
      $ aptitude -s remove freeciv-data
          (... dependency resolution ...)
      The following packages will be REMOVED:
        freeciv-client-gtk a  freeciv-data freeciv-server a  ggzcore-bin u 
        libggz-gtk1 u  libggz2 u  libggzcore9 u  libggzdmod6 u  libggzmod4 u 
      
      Here a indicates that a package was automatically installed or removed, and u indicates that a package is being removed because it is unused. Hopefully this will be less confusing than the old format.
  • Bug fixes:
    • Crashes and serious errors:
      • Track down and fix a SEGV triggered on the first action after a cache reload (sometimes). There are multiple bugs where this might have been the root cause, but it's confirmed that it was the cause of at least bug #454695, bug #454700, bug #455349, and bug #453362. Bug bug #455865 is almost certainly the same issue, and bug bug #352278 may be another manifestation of it.
      • If StepLimit is set to 0, refuse to solve dependencies instead of going into an infinite loop. (Closes: bug #451311)
    • Minor bugs:
      • Return a failing exit code after jumping from the command-line to visual mode if the last install run failed. (Closes: bug #282408)
      • Return a failing exit code from aptitude update if any download fails. (Closes: bug #233129)
    • Cosmetic and UI bugs:
      • In addition to Enter, Space will now activate checkboxes and radio buttons. (Closes: bug #451765)
      • Abort the program if we get EOF at the resolver prompt instead of claiming the resolver failed.
      • Command-line searches will now only print each result once. (Closes: bug #450798)
    • Documentation bugs:
      • The options menu documentation now minimally describes the new configuration interface.
      • The documentation of the configuration file options has been placed back in alphabetic order after apparently suffering bitrot over the years.
      • Corrected the documented default of Parse-Description-Bullets to match reality.
      • The manpages for aptitude-create-state-bundle and aptitude-run-state-bundle are now generated using DocBook, which should produce higher-quality and more consistent typesetting, as well as making the manpages more maintainable and allowing translators to easily produce localized versions of the manpages.
  • Internal changes:
    • Removed some unit tests that really tested cwidget.
  • Translation updates:
    • French (Christian Perrier)

Daniel Burrows: I hate it when I'm right this way

A few months ago, I registered my first domain name ever. When you want to register a domain, the first step is generally to enter the domain you are interested in into a box; the registrar will then check to see if the domain is not registered yet, and allow you to register it if it's available. When I saw this, I thought to myself: huh, I bet that if I were a registrar and I were evil, I would take domain names that people ask about but don't register and register them myself. So I used the normal DNS lookup process to check hostnames until I came up with one I liked, on the theory that they can't possibly be registering every single lookup failure. I really hoped that I was just being excessively paranoid, so it makes me sad to learn that apparently my cynicism in this particular case was entirely well-founded. Someday I want to believe bad things about humanity and have them turn out to be false. :-(

Daniel Burrows: The power of self-delusion

Groklaw has a link up to an interesting interview regarding behavioral economics. I haven't listened to the podcast, but the posted text is quite interesting. This line, in particular, struck a chord with me:
Feeling that your work is useful, even if you know it's an illusion, has motivational power with respect to that work.
This resonates with some thoughts I've been turning over in my head lately. Back when I was in college, I thought my work in Debian was useful and I was really excited to work on it. I'd sit around thinking up new ways to improve the system and spend all my spare time hacking code to implement my ideas. Then I graduated, and went into the real world, and got a job, and suddenly I discovered that working on Debian was not so much useful as it was worthless self-indulgence with no value to anyone but a small and marginal group of individuals. This sent me into a funk for a good year or so, during which time I released a few bugfix uploads for aptitude but didn't do much else free-software-related. I spent my time on the bus reading science fiction novels and computer science textbooks. However, at some point last year I realized a couple things:
  1. In the grand scheme of things, the work I do for pay is no more important than the work I do for free. It might be more important to the people who pay for it, but to most of the world I simply don't matter no matter what hat I'm wearing, and I need to learn to live with it.
  2. At the end of your life, you're dead and no-one asks you whether you made yourself miserable enough by doing useful stuff, so you might as well do things you enjoy instead.
  3. The only practical effect of my delusions regarding Debian was that I spent my spare time hacking code and enjoying it, instead of playing video games and feeling like a loser.
  4. If there's any chance that I might ever have a kid, I certainly want to write free software now, while I don't have one. Based on observing my coworkers who have kids, it's pretty much impossible to be both a free software hacker and a parent: after the paid job and the kid, there isn't much time left over for writing code.
So, I decided to try deliberately believing a false thing: namely that my Debian work is valuable and worthwhile. And hey, it worked! I still know that what I'm doing is worthless, but I can convince myself otherwise for stretches of time, and I have enough fun while I'm working on the project that I consider it worth a small amount of unreality. It sure beats the heck out of computer games (which I still spend a distressingly large amount of time on). The doublethink aspect of it creeps me out, but I can't argue with the results. The one problem is that this state of deluded motivation seems to be a bit fragile and is vulnerable to being popped by rude shocks. In December, I found myself mentally composing a letter in which I resigned from Debian to go spend my free time on stuff that was more gratifying, or at least where the expectations and (more importantly) level of abuse were commensurate with the pay and hours. As usual, I had enough sense to not follow through, and everything seemed less dire in the morning, but it was still weeks before I could bring myself to begin to think about spending my free time working on Debian. Presumably the only way to avoid this is to find something to do in my spare time that I enjoy and that is actually meaningful to the world. But since I don't know of any activity that meets these criteria, I'll keep my self-delusion for the time being, thank you very much. At least I know I'm doing it -- I suspect that most people don't.

Daniel Burrows: Abstracting over record fields in Haskell

It seems like I often run into situations in Haskell where it would be nice to be able to refer indirectly to a member of a record. For instance, say that I have a command-line program that can accept many options. I might choose to store its configuration in a large record:
data Settings = Settings   fld1 :: Type1, fld2 :: Type2, ...  
The intuitive way of describing command-line options for a Haskell programmer would be something like:
let options = [ BoolOption   (Just "--foo") (Just "-f") fld1,
                StringOption (Just "--bar") Nothing     fld2,
                ... ]
However, this doesn't work. Since the type of fld1 is Settings -> Type1, there's no way to use it to modify the value of fld1 in a Settings record (or rather, to produce a new Settings record with a different value of fld1). In other words, we need something like this:
let options = [ BoolOption (Just "--foo") (Just "-f") fld1 (\s val -> s   fld1 = val  ),
                ... ]
As the number of setings increases, it becomes annoying and error-prone to type out a setter function for each field of the record. Moreover, it feels very out of place, in a language where we can generalize over almost everything else, that we can't generalize over record fields. Other languages have solved this problem. Of course, in languages that aren't statically typed you just refer to fields using strings:
field_name = "name"
val = getattr(o, field_name)
setattr(o, field_name, val)
But you can do this in a statically typed language too. C++ has the concept of a pointer to member, which essentially stores the offset of a field within a structure:
struct X
 
  int a;
  int b;
 ;
// ...
int X::* p = &X::a;
X x;
x.*p = 5;
What we want, then, is a pointer to member for Haskell. Probably the easiest way to do this is something like:
data Member t rec = Member   get :: rec -> t;
                             set :: t -> rec -> rec  
Now you can just write:
data Settings = Settings   realFld1 :: Type1, ...  
fld1 = Member realFld1 (\x r -> r   realFld1 = x )
-- ...
let y = get s fld1 in
(y, set s (y - 1))
This still needs a lot of boilerplate code for every record, though, and of course there's no guarantee that accesses will be inlined (I would assume that compilers treat record accessors specially in current compilers). Ideally the field declarations would be written out by the compiler, but this would conflict with fields being functions in Haskell98; Haskell is a mature enough language that I assume it's not acceptable to break existing code. Is there a nice way of fixing these problems and getting reasonable indirection to record members?

Daniel Burrows: Why so few X maintainers?

Andrew McMillian asks why X.org has so few active developers:
[Bernardo Innocenti] did a quick and dirty analysis of Xorg LoC vs Linux LoC, to give a "X codebase is roughly 1/2 Linux codebase" (which surprised me, actually, I'd always thought it was larger) and then a similarly rough analysis that suggests that Xorg has roughly 1/20th of the developer base. To some extent Bernardo's metrics are arguable, but the basic facts are that Linux gets the lions share of the developers. Is this what we should expect? Is this a healthy way for the free and open source software community to support the development of what I personally would like to see as the future desktop base?
There are a lot of factors involved in determining which projects get more attention. I'd imagine that things like the amount of domain knowledge required to contribute a simple patch, the structure of the code, the amount of press that a project and its maintainers get, and the presence (or not) of a charismatic and photogenic leader. You could probably even base your entire academic career on studying this question. But I also think we shouldn't underestimate the impact of paid jobs. Admittedly, I have never asked whether I could get paid before jumping off a cliff and starting a new project. But on the other hand, I now effectively work two jobs and only get paid for one. Most people are not as stupid as me, and will rationally choose to spend their time on tasks that they actually get compensated for. Even people who don't care about being paid will find it difficult to continue contributing over time due to practical issues of their personal life, families, etc, and they won't be able to contribute as much as if they were working full-time. It's well-known in the programming community that if you can hack the Linux kernel, you can pretty much write your own job description [1]. On the other hand, I've never heard that companies are looking to hire skilled X programmers. A quick pair of searches on that font of knowledge, Google, seem to back this up. Compare the results for x programming jobs -"active x" -"OS X" and linux kernel programming jobs[2]. Nothing on the first page has anything to do with being paid to work on X.org, whereas the second search gives me an entire page full of people offering to pay me money if only I knew how to hack the kernel. KernelTrap, a central site for information on the kernel, even has a job board just for jobs related to kernel programming. That's not to say that the X coders don't get paid; I'm sure many of them are compensated for their work on X, and given the level of expertise involved they're probably paid well. Companies that manufacture graphics cards have an interest in employing people to hack on X; Linux distributions and embedded hardware manufacturers also benefit from a better X and strike me as likely places of employment for X hackers. But there doesn't seem to be anything for X.org like the cornucopia of available and well-advertised jobs related to the Linux kernel. Programmers who want to be paid someday will, on average, end up gravitating to the project where the prospects are obvious, not hidden. [1] Note that for the purposes of this discussion, it doesn't matter whether this common wisdom is true. The perception of jobs available in Linux-land will tend to cause people to head towards Linux regardless of whether the jobs exist or not. [2] I also tried x server programming jobs -"OS X", x.org server programming jobs, x server jobs -"OS X", and x.org server jobs without notable success.

Daniel Burrows: Why should Europeans get all the cool words?

My sister is studying at a German university. Having talked to her about her experiences there means I can understand blog posts like this one instead of just being confused. For non-Europeans: apparently in some parts of continental Europe video projectors are called beamers. Given how much more succinct and easy on the vocal apparatus beamer is than video projector, not to mention that it's plain cool, I think we should adopt the name here in the States. All in favor: refer to the next video projector you see as a beamer. If enough of us do it they'll call it a movement! UPDATE: the original post confused overhead and video projectors. I always have used the terms interchangably, and apparently incorrectly. I'm not sure why: maybe it's partly because when I was a kid the only projectors I encountered were overheads. Anyway, several readers wrote me to say that beamer is quite specifically a term for a video-projector and not at all a term for the overhead type. My bad. Comment by Meike Reichle on 2007-12-13: Hey Daniel! actually we do call an overhead projector[0] simply an "Overhead" (in the former GDR is used to be called a "Polylux"). A "Beamer" is a video projector[1]. Best wishes from Germany, Meike [0] http://en.wikipedia.org/wiki/Image:OHP-sch.JPG [1] http://www.audio-ideas.com/reviews/video/graphics/LG-JT41.jpg Comment by Magnus Therning on 2007-12-13: No, /video projectors/ are called beamers in some places. Search for "beamer" on wikipedia and you'll find "Video projector, a pseudo-anglicism in a number of languages including German and Dutch." An overhead projector is quite a different thing: http://en.wikipedia.org/wiki/Overhead_projector /Magnus (wearing his besserwisser hat)

David Nusinow: Random Bits

I've been extremely busy with labwork lately, trying to get a second paper ready for submission in the coming months. It's taken an obvious toll on my free software work, but that's life I guess. The upside is that the other night I realized why a year and half's worth of experiments kept turning up with negative results that seemed to contradict our other results. It turns out that this experiment was conceptually flawed, and even though I wasted a year and a half on this I did learn something even from those negative results that should go in to the final paper. I'm actually relieved, because even though I don't have all the data yet I can really see how the paper will end up, so I can start writing soon. Oftentimes knowing why something is wrong so you can fix it is even more important than being right.

I set up an ikiwiki to help organize my lab data a few weeks ago, and it's been a huge win. Joey really did a fantastic job on the program and I can't imagine using a wiki that doesn't share a very similar design for any of my personal stuff. I showed my boss some of my data using it and now he wants me to set up a wiki for the lab. He actually wants me to show off my wiki to give my lab members a feel for the idea. Since ikiwiki doesn't seem to be appropriate for my lab members, I'm going to have to look in to the giant list of wikis to figure out the exact right one for my lab's requirements. This is something I never expected to be doing in grad school.

Because there's no way my brain can go without doing a little bit of programming, I finally sat down and wrote myself a small shell script that lets me grep through pdf's, which is something I couldn't find googling around. If you have a lot of pdf's like I do and don't something like beagle or tracker churning away in the background constantly just so you can search them, this is very helpful. It's obviously very crude, but it gets the job done nicely. It relies on the pdftotext program; hopefully it'll be of use to someone.

I've been digging in to my copy of UNIX Power Tools lately, trying to pick up new UNIX and vi arcana, which is something I haven't made a real serious effort to do in a long time. It's been surprisingly fun to try and replace old habits with things that I know are better but don't use. A good example is that I usually will fire off a new subshell in vim when I should really just suspend vim and use my original shell to save time. Re-examining the basics of how I use the system has been a lot of fun, and has made me a lot more comfortable with the simple day to day tasks.

Davide Viti: Font tips #3: digits width

A while back Frans filed an interesting bug explaining the reason why digits width should always be the same.

Finding out if the previous condition is true, is just a matter of creating a sample text file

FONT="DejaVu Sans Oblique"
OUTFNAME=$(echo $ FONT sed -e "s _ g")
numdigits=100
for i in $(seq 0 9) ; do
for j in $(seq 1 $ numdigits ) ; do
echo -n $i >> numeri.txt
done
printf "\n" >> numeri.txt
done

and creating a waterfall image:

pango-view --font="$ FONT " --waterfall --dpi=72 -q -o $ OUTFNAME .png numeri.txt

The resulting image shows how Dejavu Oblique is victim of a regression at size 9 and 10 (credits to fjp who spotted it once more!)
bugreport filed.

Patrick Winnertz: How to get most spam?

I've created a small contest together with several other guys. We'll try to get as much as possible spams on a emailadress. The people with the most spam and viruses on his emailaccount will win. I think a good starting point is to publish here, we'll see. Some other things which could end in having success are: If you have other ideas how to get as much as possible spam to this address please write a Comment to this post to the Discussion page. Thanks in advance The emailadress which should recieves as much as possible spam is: winnie@qsc218.credativ.com.

Steve Kemp: I promise that I will not kill anyone

Planet Debian now has Javascript to facilitate the persistent hiding of particular feeds. The code is still in flux, but appears to work. Comments welcome, especially from people better at Javascript than myself! The way it works was chosen to minimise the changes requred: At load-time the function hideHosts() is called. If a comma-separated cookie called "excludes" is present this is split and iterated over. For each domain-name in the list the current document is searched for elements having a class prefixed with that hostname - if any match and they have an ID defined (regardless of what that might be) they are hidden. And thats it. The changes to the template were minimal; each index entry already has a "link" attribute, so I just had to add this:
 <div class="<!-- tmpl_var name='link' escape='html' -->"
         id="<!-- tmpl_var name='link' escape='html' -->" >
 ....
 </div>
Because the ID and LINK attributes are URLs there is a little mangling, and inefficiency. But I didn't want to change the core of the PlanetPlanet to define a "hostname" attribute for each feed member... In an ideal world I'd add "class='feed, $link'" and then iterate over that at load-time to attach handlers, and an ID appropriately. But that is a little scary.. If it works in IE great. I've tested Firefox & Ephinay ObQuote: Terminator II Update: Moved javascript into external file, and removed the image toggling, it seemed to fail and I'm not sure why. I will investigate.

Isaac Clerencia: Please, Dems, don t mess up this one: vote for Obama

I am a huge political junkie and I have been closely following Europe and US politics for more than 5 years. After this time and several disappointments, I have to admit that Obama is the first truly inspirational politician I have seen (listen to the Yes We Can song based on his New Hampshire speech). Some of his detractors dismiss his speeches as lousy, empty or vague, but you just have to listen to a couple of them to see that he is genuinely smart (such as the one about faith and atheism or the interview at Google). He doesn’t only take the right stance on most issues that I care about (Iraq, foreign policy, ethics, net neutrality, …), but he does it in a sincere way. Obama just gets it. I have got this impression from watching several of his speeches and interviews, but Marc Andreessen had the chance to spend an hour and a half with him a year ago and got the very same feeling. The main argument against Barack Obama nowadays is his alleged lack of experience. “Watch how I run my campaign”, Barack said to Marc when inquired about that. It’s obvious that running a primary campaign isn’t the same as being POTUS, but being the president’s wife isn’t exactly the same either. So if we compare the Obama and Hillary campaigns we can easily see Hillary’s experience as an “old school” politician. She overstates, lies, accepts loads of money from lobbies (because “they represent people too”, haha), resorts to fear-mongering (”Obama is not a muslim, …, as far as I know”, 3 a.m. ad), sides with McCain if needed to get some extra votes, surrounds herself with nitwits, … . To summarize, she uses every dirty trick she has learned in these years in Washington, and that’s exactly what I am so sick of right now. On the other hand, Obama’s campaign hasn’t just been one of the best organized and executed campaigns I have ever seen, but also the cleanest one. He has managed to overcome double-digit Hillary leads in most states without having to resort to any of these experienced politician’s dirty tricks. If I have to trust one of both to run a country, the decision is obvious. If I didn’t manage to convince you, I hope Lawrence Lessig and xkcd’s Randall Munroe do. Obama is leading and almost there, he just needs the final push. Please, do the right thing.

Martin Zobel-Helas: What they didn t announce

What they didn't announce... (To be fair: It is not theirs, Tolimar will be the godfather. But they do it with a perfection.) No Tags

Martin Zobel-Helas: What they didn t announce

What they didn't announce... (To be fair: It is not theirs, Tolimar will be the godfather. But they do it with a perfection.)

William Pitcock: A look at SCO Unixware 7.1.3

So, you know, SCO has been suing various people in the Linux community for the last few years, claiming that some code in Linux was stolen from them. So, I’m willing to bet that a lot of people were wondering: what exactly is SCO UnixWare? Well. Have I got a treat for you. Thanks to this wonderful thing called the Internet, you too, can experience SCO UnixWare in it’s full glory. Right, so! I wouldn’t want to stop you from experiencing perhaps, the most enterprisy OS ever. Lets get it on. Installing the OS — the most enterprisy installer ever. The SCO installer is the most ass-backwards convoluted thing someone could have ever invented. It’s downright bloody insane. But, a picture is worth a thousand words, or something like that. This is the boot splash screen. You’ll see it a lot. The release 7.1.3 text goes back and forth a lot, kinda like the Windows XP startup screen except with less artistic talent. After a little while, you boot into a language selection screen. SCO UnixWare Installer Language Selection Screen You choose English, and it presents you with: Welcome to the SCO installer !!!1111one+1 You press F10 to continue. Pressing F10 is kinda like rolling a 2d6, except it’s more enterprisy. You’ll be pressing F10 a lot. It asks you to enter a license key. But, SCO doesn’t really care about licensing it seems. You press F8 to tell it that “you don’t have a license”, and it gives you the option to use an “evaluation license which expires in 60 days”. Licensing You choose yes, you anti-capitalist pirate. Don’t worry, at this point, the SCO installer has probably phoned home and told them to add you to their SCOsource litigation. It starts unpacking drivers, and asks you if you would like to use the driver configuration utility. Driver installation You exit out of the driver configuration utility. It asks you for the system hostname, and installation method. Nodename? Select install method Time to partition your hard drive. Finally. This is what it’s all about. fdisk step 1 fdisk step 2 fdisk step 3 Wow, that was easy wasn’t it. You press enter three times, kinda like the free software OS we know and love. It asks you what packages you would like to install. Package selection You choose the default. Mostly because I couldn’t be assed. Now you go back to setting up the network??? You think back, and recall vaguely that you set up the network already. Apparently you didn’t, as it now wants you to manually configure your ethernet adaptor, despite the fact that it autoconfigured itself moments ago. Network configuration, part 2 Network configuration, part 3 You enter in some information to make it happy. It asks you to set the clock. Time configuration You enter in some data and press F10. It asks you to set up a user, set the root password and set the system security level. User configuration Security level? It asks you to accept the license agreement, in a very enterprisy way. Infact, it’s so enterprisy you don’t have to read the actual license. License Agreement You choose “display licenses”; because you’re curious. You see the following copyleft licenses: SCO uses GPLv2 software SCO uses Artistic-Licensed software. It asks to be sure you really want to install this enterprisy OS. Are you sure?! You hit F10, acknowledging your willingness to sell your soul to satan SCO. Installation begins, you wait about 20 minutes, and the thing is finally installed. File Installation, part 1 File Installation, part 2 You look up and see it installing netscape. You sigh, as you know what that means. It installs documentation. You nearly fall asleep. File Installation, part 5 Wasn’t that percentage meter more a little while ago? You go back to whatever you were doing. Finally, it “sets up UnixWare”, and tells you that it has finished. You hit Enter. But, you forgot to eject your CD. Ok, you reboot finally. It boots back into unixware, and you get presented with the bootsplash: It boots up for the first time. It asks if you would like to install anything off of CD2 or CD3. You choose no, and it spams you about some update support contract thing. It decides to rebuild your kernel for some random reason. By rebuild, I mean, “relink using binary blobs”. But, I digress. The system reboots, because it rebuilt the kernel. The system boots, you’re presented with even more advertising. This concludes our look at SCO UnixWare. I hope you’ve found it fun. There’s more fun images in this directory, including a mollyguarded shutdown and much more.

Kartik Mistry: Cruftiness > 0


* System’s cruftiness is > 0. kartik:/home/kartik# apt-get remove deborphan
……
The following packages were automatically installed and are no longer required:
libgtkhtml3.8-15 gcalctool gnome-nettool openoffice.org-impress openoffice.org-draw gucharmap network-manager gnome-games type-handling esound gnome-cards-data w3c-dtd-xhtml libnm-util0 kdebase-data kdebase-bin-kde3 gnome-themes xulrunner-gnome-support unrar-free network-manager-gnome gnome-utils dhcdbd gnome-volume-manager libkpathsea4 gs-common gdb eog gdm python-4suite-doc gnome-backgrounds python-xdg bug-buddy kdebase-bin vino gnome-keyring-manager evince gnome-games-data iputils-arping gtkhtml3.8 zip pmount gconf-editor resolvconf totem unace file-roller
Use ‘apt-get autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
……

14 March 2008

Axel Beckert: Axel's Cruftiness Theorem

Theorem: If aptitude is used, set to automatically remove unneeded packages and every not willingly installed package is marked auto, the system’s cruftiness is always 0.

MJ Ray: Your Pics / Save Our Post Office March

I'm back from the protest march from Kewstoke Post Office to Milton Post Office with some pictures (click through to full post to see them).

The first photo shows about 50 of us setting off from Kewstoke Post Office at 1230. Monks Hill was pretty busy with traffic, scattering the walkers at various times, like shown in the second picture.  Most people walked up the 25% gradient road instead of the (even steeper) footpath because the footpath steps are very wet and slippery just now, as shown in the third photo - top left shows the steps up the wall, which looked lethal. I walked up the main steps to see what state they were in: green and slippy with moss (top right), some of them washed away (bottom left) and others had animal poo on them (bottom right).

About 1310, 24 walkers arrived at Milton Post Office, shown in the last picture (District Councillor Ian Porter (Con) in the centre there).  So, that's 40 minutes for 50% of people, which means a round trip for a simple transaction will take about an hour and a half and only the able will do it in that.  It wasn't even particularly bad weather today, so that just isn't a reasonable journey for most people and even less so for those who rely on the Kewstoke village Post Office for financial services and parcels.  Closing it will clearly make it take much more time or make people poorer from using buses or cars to get to the alternatives, or paying parcel companies to collect.  Shame on Royal Mail!

I got a lift home in an LPG vehicle with three others. I have to go to Milton again now, as the shop I needed was closed for lunch.  (I visit it about once a quarter, so not as often as the Post Office, no.  Travelling to Milton for something once a quarter is tolerable.)

Cord Beermann: being busy / Request for Help

Because of some modifications at my Real Life Orkplace, I decided to reduce other duties to get a better chance to deal with my new duties. So i requested help for my four packages in the Distribution

RFH: jove
My first package. A small, but powerful Emacs-relative, with all those uneeded things stripped which makes emacs fat. Maybe these days especially useful for small memory devices, as it gives you emacs-likeness for the price of nvi or ae. I have no idea how well it works in a real utf-8-environment.
RFH: milter-greylist
A greylist-milter which makes running a mailserver somehow possible for me. it keeps away about 2/3 of spam, which leaves me with only 400spams/day. I already have two contacts who want to help with that.
RFH: nn
No news is good news, but nn is better. This is a USENET reader, for those people who grow up with Webforums and Blogs: This could be still the most effective way to celebrate flamefests, gather information or communicate with people sharing same interests. And nn has in my opinion the best UI for it, and makes it easy and fast to find interesting articles and skip others. Well, Upstream Development has ceased to exist around 1994. I think if no one takes over, this package will become finally useless when IPv6 gets widely used (right after the release of 'Duke Nukem Forever') and it also doesn't deal well with non iso-8859-1-charsets. So best for this package would be to rewrite it from scratch (my dream: message/mime-handling/threading from mutt, scoring from slrn, and UI from nn) because the User Interface is much better than those of all still alive Newsreaders i tried.
RFA: synergy
This is my most popular package, which makes it possible to share one mouse and keyboard over many computers and displays. (It is available for UNIX/Linux, Windows and MacOS) This is a very very useful software, and i use it permanently. Sadly the Upstream Development mostly ceased to exist, and so i put this to RFA (instead of RFH) because many Debian-Users use it according to popcon. This software should be taken over by someone who is able to help Upstream. There is a RC-Bug, which caused the package be pulled from testing.

Interesting is that while filing those RFH/RFA all the same day, i only got responses for the packages which scores lowest in popcon, (24 for milter-greylist, 1196 for synergy).

Michal &#268;iha&#345;: Nvidia is bad, Intel is good?

Intel is always seen as good guy, who is writing open source drivers, releasing at least some specifications for hardware. Unfortunately it is not always the case. If you want to use their new embedded solution - Menlow CPU and Poulsbo chipset, they provide you lot of crap. Basically what you get is a zip file containing several Microsoft Word documents, badly formatted text files (end of lines at each 80 chars), PDFs and some zip and tar archives. If you look to one of these archives, you will get binary graphical installer, which will install license, uninstallator and yet another set of tarballs. These tarballs finally contain binary and source packages you need to make graphics work on this platform. Maybe somebody did this to practise various ways of compressing and distributing things, but it is really amazing how many times you need to decompress several archives to actually get to the things you want. Unfortunately at the end you will find out that libgl1-mesa-dri-psb binary (DRI driver for graphics) has no sources and Intel is not willing to give them to you. Bad luck if you have slightly different distribution than one of these which are supported (FC6, Midinux-build9, ubuntu-gutsy, ubuntu-hardy) and the provided binary simply crashes.

Lior Kaplan: The benefits of focused group maintainership


Instead of everyone maintaining his own packages, we try to have several people cooperating to maintain the packages. This reduces the dependency on a single person to take care of packages and makes it possible to keep the packages in a good shape while people are busy or absent. Having such groups focused on a specific set of packages is even better, because they develop a standard for that packages type. While the Debian’s KDE and GNOME teams have a large variety of packages (application, libraries, etc…), other groups maintain packages which are similar in their technology. The Debian Perl group and Debian fonts group are good examples (and I’m sure there are much more examples). We can see that such group can easily (the facto) enforce the policy rather than having to “just talk” with other people to comply with the policy. This of course makes Debian a better distribution in which more parts are working well. The Debian Perl group has recently took text-bidi into their maintainership, and I
was amassed to see the amount of changes they did on their first upload. That made me very happy about “giving” them the package and showed me how much more do I have to learn about Perl related packages. I don’t expect people to let go of their packages, but please consider working more closely with such groups. I’m sure you and your package users will benefit.

Next.

Previous.