Search Results: "ag"

29 June 2007

Lucas Nussbaum: How old are our packages?

Debian’s binary packages are only built when they are uploaded (or when a binNMU is requested, but that doesn’t happen frequently). They are never rebuilt later. This means that some binary packages in etch weren’t build in an up-to-date etch environment, but possibly in a much older environment. Is this a problem? It depends. Old packages don’t benefit from the improvements introduced in Debian after they were built. Like new compiler optimizations, or other changes in the toolchain that could induce changes in binary packages. For example, some files used to be at some place, but are now put at another place. Also, some parts of maintainers scripts are automatically generated, and would be different if the package was rebuilt today. But is it really a problem? Are our packages _that_ old? Also, when a big change is made in the way we generate our binary packages (like Raphael Hertzog’s new dpkg-shlibdeps), when can we expect that the change will be effective in all packages? I went through all binary packages in unstable (as on 24/06/2007) (both main, contrib and non-free packages) on i386. Using dpkg-deb –contents, I extracted the most recent date of each package (which can reasonably be taken as the date of the package’s creation). And here are the results. Most packages are actually quite recent. 9008 packages (43%) were built after the release of etch. And 19857 packages (94%) were built after the release of sarge. But that still leaves us with 1265 packages that were built before sarge was released, and even one package (exim-doc-html) that was built before the release of woody! (the removal of this package has been requested, so we will soon be woody-clean :-) Now, what could we do with this data? We could review the older packages, to determine if: Here is the full sorted list of packages.

David Nusinow: Post Debconf Spewage

I've been back from Edinburgh for a few days, but this is the first real chance I've had to sit down and write a little bit about it. I'll preface this blog post by saying that my first Debconf was probably the best single week of my entire life. Yeah, it was that awesome.

I won't talk about all the stuff that happened, because that would just take too long. The most important thing was that I got to see a number of old friends again and spend more time with them in one run than ever before. That alone was really enormous for me. On top of that was the pleasure of finally meeting so many people in person. I met a few XSF members finally, including Julien Cristau, my partner in crime. There's no way I could possibly list everyone that I'm so thankful to have finally met. There was one very memorable evening in the night venue where it was largely the same crowd who's usually in #debian-devel when I'm on, and we all just couldn't stop cracking jokes and laughing (not to mention ITP'ing absurd programs). There was another night when Old World Cambridge collided with New World Cambridge, and much Pimm's was had by (almost) all. There was staying up until 5 in the morning and stumbling back to the hostel in the dawn to try and get some sleep before running back to the conference. The most delightful thing about all this was that so many people I already knew and loved were there, and everyone who I hadn't met in person before turned out to be even better in real life. It was like a week of the purest joy.

I also got the privilege of giving my talk and BoF to fairly full audiences, particularly the former. The BoF was on maintaining packages with git. I didn't expect more than 10 people to show, but more than 5 times that did express interest, so many that they moved it to the main lecture hall instead of the small discussion room that it was going to be in originally. I hadn't really planned out how to handle an audience like that, and while I managed to get other people in the audience talking (thanks in particular to Madduck, MadCoder, and keithp for adding so much to the discussion) I felt like I had to fumble through a lot of it. That's the nature of a BoF I guess. I also gave a talk on my plans for the XSF for the Lenny release. I'll talk about that stuff in future blog posts (some of which are overdue) but I will say that it was surprisingly well attended given that it was scheduled for 9:45 am after one of the usual nights of drinking and hacking until dawn.

I have to echo others and give a big thank you to the organizers. You guys did a great job, and persevered in the face of adversity (read: cowgate) and really made a great conference out of it. I learned a lot, laughed even more, and drank even more than that and I can't wait to do it again.

Evan Prodromou: 9 Messidor CCXV

Last-minute note to Montreal BarCampers, hackers, entrepreneurs, designers, coworkingers, designers and other troublemakers: Tara Hunt is coming into town and I invited her to have lunch with local folks in the scene. We'll meet at 1PM, at La ka, since half of us will be there anyways. I've reserved space for twelve, but that can expand pretty easily. For those who don't spend 60% of their time there, La ka is at 4040 blvd St. Laurent near the corner of Duluth. URL: http://www.laikamontreal.com/ Please feel free to come and to invite others you think would like to meet Tara and vice versa. And feel free to Contact me if you've got questions or comments. I'd especially like to hear if a lot of people are coming, since I might need to expand the reservation. tags:

GPLv3 iPhone So, I'm as excited as everyone else to hear that the new Apple iPhone will be available today with a new GPLv3 Free Software license. A bold partnership between Apple and the FSF! tags:

New Oceans OK, so, that's a big lie. But wouldn't it be cool if it were the truth, and you could get a cool and good-looking Open Source phone? That way, you wouldn't only get Web 2.0 applications, without an API for the local machine. You could write local apps for the phone itself, and you could even re-write the phone OS if you want. Looks like pretty soon we'll have these Open phones. According to the http://lists.openmoko.org/pipermail/announce/2007-June/000013.html announcement on the openmoko-announce list, FIC will start taking orders on the first generation Neo 1973 on July 9. So, given that we've got an Open Source alternative to the iPhone coming down the pike in just a week or so, why is anyone working on iPhoneDevCamp? tags:

Joey Hess: google notebook

There's a photo of me going around the interwebs with a strange caption that misses what was going on. The real story is, after my notebook's power supply died, I tried out this other weird notebook that Google had obtained, apparently from some alternate universe, and was giving away at the conference. It was very nice and small, and had impressive touch-screen data-entry technology (though I kept losing the stylus), and amazing battery power. Seems the data I put it in might stick around for a good hundred years, without any recharging. I was happy to not have to hook a clunky British power adapter up to it. It was also impressively easy to enter arbitrary unicode character such as BOPOMOFO LETTER EH, RUNIC TVIMADUR SYMBOL, and THING I SCRIBBLED DURING BORING PRESENTATION WITH CEDILLA BELOW. Downsides: No wifi or other network (didn't check GSM), very limited storage space (only a few dozen Kibobytes I think), an atrocious text editor that made moving text around way too hard, and had a really bad font, difficulty deleting things (the obvious way to delete something often accidentially removed nearby files as well -- and didn't actually regain any storage space), and very limited encryption (best I could get out it was rot-13). On the network front, there is apparently some "Postal Mail" app that can be used to send mail, but it can take like, weeks, and charges per message. And yeah, no solitare at all, though there was this hangman app. All in all, I was happy to get my Fujitsu back, though I might hold onto this Google notebook thing for emergencies. Won't be porting d-i to it anytime soon though.

28 June 2007

Michael Prokop: synergy - share mouse and keyboard

Quoting the project homepage:
Synergy lets you easily share a single mouse and keyboard between multiple computers with different operating systems, each with its own display, without special hardware. It’s intended for users with multiple computers on their desk since each system uses its own monitor(s).
It really rocks, especially as it works for Linux/Unix as well as for Windows and Mac OS. The setup is simple: just run ‘aptitude install synergy‘ on your Debian system(s) or grab the sources/binaries for the other platforms. Assuming you want one screen named meilenschwein on the left, and another client named funkenzutzler on the right:
mika@funkenzutzler ~ % cat .synergy.conf
# synergy configuration file
section: screens
   funkenzutzler:
   meilenschwein:
end
section: links
   funkenzutzler:
      left = meilenschwein
   meilenschwein:
      right = funkenzutzler
end
Now start synergy on the “server” running “synergys -f –config ~/.synergy.conf” and start it on the client using “synergy -f $SERVER”. That’s it. Make sure to check out the security page.

Jacobo Tarrío Barreiro: A little bit of everything

July 5th, 2007 will be the 10th anniversary of the Debian Social Contract. Also, on July 5th, 2007, I will be flying to Dublin to start a new job at Google Ireland the following Monday. Today (well, technically yesterday now) was my last day at Allenta. It’s been several good years, with nice and funny coworkers (and friends), learning and doing lots of very varied stuff. However, after several years I felt a need to do something a bit different. It appears that working at Google is all the rage now, so I decided to jump on the bandwagon ;) Oh, yeah, I’m excited about living in Dublin, and about working at Google. I already have so many plans, I’ll be happy if I manage to undertake 1/10 of them ;-) If you live in or near Dublin and want to meet, feel free to call or email me. My Spanish phone number is in the Debian developer database or in all of my domains’ WHOIS records. My email addresses are all easy to find. As I don’t know what kind of Internet access I’ll have outside of work (assuming I will not be out exploring the city when not working), it’ll probably be a bit hard for me to keep up with mail and with the Galician debconf template translation stuff. Today I’m in the 12th position in the ranking, with only 12 strings left to catch the Brazilian Portuguese team. I know that the Catalan team wants revenge from when I overtook them. It’s your opportunity, nois! :-)

Steve McIntyre: Slowly recovering...

Debconf's over for another year - people have gone their separate ways, taking their newly-shared sense of purpose (and germs!) back home with them. Speaking for the organising team, I think we can justifiably be proud of ourselves - we seem to have pulled off a Debconf! Not everything worked perfectly or quite as we expected/wanted, but in the end I don't think we had any major issues. Fundamentally, it seems that all the attendees enjoyed themselves immensely and lots of productive work and socialising happened. That's the important bit! Thanks to all of you that turned up and helped us to make the conference a success this year, especially the volunteers who dived in to fetch, carry, man the front desk, run the cameras, organise the day trip, etc. And also (of course) to the sponsors who paid for the event - we love you all! The orga team still have some small bits to finish up before we declare things completely finished, though. We've still got some bits and pieces left in Edinburgh yet, waiting to be returned to their respective owners. And we're going to make a start on the post-conference report shortly. That's a place where conference attendees can help us again - we're looking for short write-ups of your experiences at the conference and a good selection of photos to give an impression of how things went. If you're able/willing to help, please mail the debconf-team list. Thank you and goodnight.

Jan Wagner: performancing.com and privacy

Today I was crawling through my mail logs for various reasons.
I was really surprised, that I saw a mail to a dedicated mailaddress which I’m using for communication with performancing.com. I was short checking, if this mailaddress is anywhere published at performancing.com, but couldn’t find anything. A one liner over the last week of mail logs:

# zgrep performancing /var/log/mail.info* grep clam wc -l
26 For a address only used for communicating with one organisation (used as contact mail address) this seems a bit too much traffic and this are only the mails, which was accepted by the MTA. So the questions comes to my mind …. what happens with the addresses at performancing.com? Maybe I missed something? , ,

Joey Hess: heat

Imagine that you went somewhere cool in the middle of the summer and screwed up your body's ability to cope with heat. And then had to come home and suffer. I thought this had happened to me, and was pondering putting in air conditioning (and dreading next week's trip to the beach). It was frightning. But it turns out that I just had a fever.

David Welton: DedaWiki - alpha

I came down with a serious case of Not Invented Here, and created a wiki of my own. Before you look, consider that: That said, I'd love to have a collaborator or two: DedaWiki It will eventually replace the wiki engine utilized over at http://www.leenooks.com, which is showing its age, and not as fun to work with as Rails at this point in time.

Alastair McKinstry: Fun Filenames

Ok, some interesting output from a build script of a nameless code I'm working on:
...
scanning lib[10].a ...
scanning lib[11].a ...
scanning lib[12].a ...
scanning lib[13].a ...
scanning lib[14].a ...
scanning lib[15].a ...
pgf90 -Wl,--start-group ./master.o -L. -l[1] -l[2] -l[3] -l[4] -l[5] -l[6] -l[7] -l[8] -l[9] -l[10] -l[11] -l[12] -l[13] -l[14] -l[15] -Wl,--end-group -llapack -lblas
./lib[2].a(cprep1.o)(.text+0x181d): In function  cprep1':
...
Next time, think of someone trying to find these interesting files. People using regexps, ok ? What do these 'libraries' contain, anyway ? Tags , ,

Biella Coleman: Minimizing Lingusitic Drift for the Sake of Political Clarity and Integrity

I am finally catching up with the remarkably thick goulash of email and blogs entries that comes from traveling for well over a month and today I read one in particular When is Open Source not Open Source? that captivated my interest for it compellingly addresses the dangers that follow from diluting, or one might say hijacking, the term open source. When people learn that I study “free software” one of the most common questions I get asked is: why did I chose free software over open source? The answer is quite simple: given that the bread and butter of my research covers ethics, freedom, and liberalism, free software is the obvious path to follow, yet I also feel like a lot of my work is still relevant to the open source camp because of the affinities between the two. I have long maintained that the ideological gulf between open source and free software is not so great nor impassable, but more modest. As most know, both share a certain strong commitment to access and in a strict technical sense they refer to the same set of licenses. Philosophically there is agreement that openness and, especially, non-discrimination are essential for the quality of software and often by close extension, the vibrancy of community responsible for the software. Of course, when pontificating the ramifications and implications of openness, they do part company and enter into different territories. Free software tends to flag rights and freedoms, while open source meanders into a discussion of markets, business, and competition and in this regard they do craft different visions of the social world and human behavior, etc. But the case that Karl Fogel writes about, where OSI is strongly opposing the use of the term open source for licenses that don’t adhere to the definition demonstrates where the two positions join. As Michael Tiemann from the OSI succinctly put it:
The FSF may have got the orthodoxy wrong, and the OSI may have got the interpretation wrong, but we both agree that prohibition of commercial use without special permission is antithetical to both positions.
There is a unmistakable kernel of agreement and it is great to see the OSI taking such a strong stance in this regard. Now, David Richard’s response, who seeks, I think, to essentially dilute the term open source, is as (or perhaps even more) fascinating for in a nut shell, and using a lot of florid religious imagery, it accuses the OSI of being too rigid! In his own words:
I believe the OSI has a wonderful opportunity to continue being relevant and helping to lead the movement forward. If, however, y’all choose to define your denomination of this religion in a way that we don’t fit in, that’s fine. No hard feelings. It’s your choice. You’ll ultimately be excluding a large congregation and we for one will continue trying to build a church made up of others like ourselves.
In response, I would say that the goal of F/OSS is not to be inclusive of anyone who wants to release bits of source code, but to create the conditions under which software, as it has been defined by the community, can be created. Join the church if you would like to make free/open source software as defined and you can go elsewhere (i.e., create a different term) if you are creating something different, even if it is only slightly different. Integrity matters. And again inclusiveness, if it comes at the expense of the main goal, is not a boon but a danger to F/OSS. The OSI will remain relevant by halting the dilution of the term OSI, not by expanding the definition so that it is left with no substance. And in contradistinction to what David Richard maintains, however, there is a great degree of flexibility within this domain but it does not lie in the strict definition of F/OSS but in the realm of interpretation. You are also free, as Mako and I have argued elsewhere to interpret the significance of F/OSS in multiple ways. And I think this is where the political strength of free software lies. There is interplay between a well-defined goal (in this case for creating free software) and a more flexible realm of interpreting the significance of these technical practice. And we wold lose and I might add, a lot if we became flexible about the strict definition of F/OSS and inflexible about its political significance. I get irked with folks like David Richards who would like to bend open source rules to meet their (often commercial) interests and I find it pretty na ve when folks say the political significance of F/OSS is just x (or worse should be x) for in reality its political significance lies in the fact that it has spawned multiple types of political and economic projects. And there is something almost playfully ironic, (or at least it makes me smile) in this fact. Though there is strict definition contained withing F/OSS, this strictness has, at least to some extent, encouraged by an extreme and very healthy form of political proliferation and promiscuity. More than anyone else I know, Mako has most passionately and thoughtfully argued for the importance of what I would call political clarity and integrity. That is, the importance of having a well articulated definition for social movements, for they act, as he says a rallying point to realize a social movement. Urging the Creative Commons to learn from F/OSS and dare to simultaneously narrow and more clearly define their goals, he states it quite nicely in the following terms:
Free software advocates have been able to use the free software definition as the rallying point for a powerful social movement. Free software, like the concept of freedom in any freedom movement, is something that one can demand, something that one can protest for, and something that one can work toward. Working toward these goals, free and open source software movements have created the GNU/Linux operating system and billions of lines of freely available computer code.
In essence, a definition that people can abide by, respect, and perhaps eventually cherish is the condition of possibility to make working political code. And given how hard it is to make social change happen (at least in comparison to build computer code), we should learn from what F/OSS has to offer. And at the same time there is another lesson embedded in F/OSS. The Free Software Definition is well defined; but it must be emphasized, narrowly so. It does not try to do everything and have everyone pledge allegiance to an inordinately complex set of commitments. Clarity, narrowness, and well-defined goals –> these three attributes have powered it far and wide and I hope it remains so. Now, since the term open source is not trademarked, we are left with the problem of how to challenge the current hijacking of the term. For the solution, I will leave you with Karl Fogel, who I think proposes a good solution:
Note that the OSI s objection is not to the Zimbra license per se. The objection is just to Zimbra s calling that license open source . They can use any license they want, but they shouldn t call it open source unless it actually is. Freedom is freedom, and no amount of spin will change that. So what should we do about this? The term open source isn t trademarked. Years ago, the OSI tried to register it, but it was apparently too generic. …But there is public opinion. What Danese and Michael are proposing doing is organizing a lot of open source developers (and I mean open source according to the traditional definition, the one the OSI and I and most other open source developers I know adhere to) to stand up and, basically, say All of us agree on what the definition of open source is, and we reject as non-open source any license that does not comply with the letter and spirit of the Open Source Definition.

Eddy Petrișor: My small contribution to pbuilder...

... is a patch that allows a decent default mirror selection via some heuristic and a debconf question.
This is bug number 333294.

The patch is part of the git repo at http://users.alioth.debian.org/~eddyp-guest/git/pbuilder/.git. Since it uses debconf it has po-debconf support and a Romanian translation. The language should be in line with the one used in other templates, but I don't mind if anyone from Project Smith suggests some changes.

MJ Ray: Comments about another W3C WG and WGs in general

Alex Hudson commented:

"Similar comments about another W3C WG: http://ln.hixie.ch/?start=1181118077&order=-1&count=1 W3C should be about authoring material for the web. It seems at the moment, they're more concerned with the stuff that happens after authoring - e.g., how stuff relates in "the semantic web". IMHO we still don't have any powerful tools for authoring either, so the idea that authoring tools will automate many of the "bolt on accessibility" tasks is pretty naive."
After implementing pingback, I have some respect for hixie. It's disappointing but not surprising to read those comments. Not sure what is meant by powerful authoring tools there. My tools are powerful, but I know they're not easy for new users. As I'm getting old and cynical, I'm not sure whether power tools can ever be correct and truly easy - just look at the pigswill spewing out of some Web 2.0 sites. niq sent me a link to the WCAG Samurai Errata and commented:
"The problem with WCAG 2, as with WCAG 1, is precisely that it's a Work of Committee, and seeks to represent too many irreconcilable viewpoints and egos. In some cases, even the ideas behind it are inconsistent. Many (myself included) regard accessibility as being about ensuring a reader with a physical disability can make use of a site (think Steven Hawking). That's also what HTML is designed to support. Others are concerned with the mentally impaired, also a worthy cause, but one that becomes counterproductive when its advocates fail to distinguish between a site that's inherently inaccessible because it presents a complex and challenging subject, and one that's unnecessarily difficult due to poor presentation. Add the two together, blend in some stupidity, and you get "accessible" sites full of classic "friendly" little illustrations like a "helpful" government booklet, and a horribly intrusive "alt" to explain each pointless "ethnic mummy and child" picture."
I think a Work of Committee could be useful, as long as you have the right committee. Thinking about that, I found the group membership list and I'm not sure that's the right committee. For example, I think the ex-Adobe Google-worker must surely have an irreconcilable conflict of interest (inappropriate use of Adobe's Flash and PDF formats and Google's Web Apps have done more than many to harm accessibility in the past IMO), yet is a leading light of WCAG 2.0 - maybe that's why it's gone so dark? Update: Thijs Kinkhorst comments:
"As I read in the draft, suggestions are still possible until the 29th, not the 27th of June."
I'm sure that's different to the email which started me writing this, but please go comment and see if we can make WCAG-2.0 useful.

MJ Ray: Online Banking with GNU/Linux, Firefox-based browsers or Free Software: 2007-06-28

Problems reported on ingdirect.es:
"I get a message in Firefox to the effect that the web page is NOT a secure site, even though the address bar shows the URL as https...??? THIS is the URL on the pop up. THIS is the URL of the bank's opening page. Access de clientes is the link to log in."
I didn't see the cause at a glance... anyone? Does this work with GNU/Linux or not? Also spotted a D+Cglug subscriber reporting problems on UK HSBCnet - anyone willing to confirm or reject that? Comment form at the bottom of the list.

MJ Ray: BBC Two's Money Programme Tonight

I wrote this yesterday:
"Dear BBC Money Programme, I'm really surprised that BBC Two's Money Programme "How Green is Your High Street?" correctly mentions that the recent greenwashing of public listed companies is motivated by shareholder returns rather than ethics, yet doesn't mention that cooperative businesses are motivated by ethics. [pic of agm lunch] Nor does it mention that the UK's largest cooperative retailer, the Cooperative Group, has been at the forefront of moving its stores to renewable energy and developing friendlier food packaging across its whole range, from biodegradable onion nets to thin-but-tough whisky bottles. I think it's also the first high street retailer to commit to only selling A-rated electrical appliances in its stores. It does this because it is motivated by ethics as well as dividends. As a result, the Co-operative Group food stores are outperforming competitors in the IGD reports and winning awards such as the Queens Award for Enterprise in Sustainable Development. Why do you ignore this success of green and ethical principles in your report?"
and this morning Sam notes he's seen the Daily Mirror report that the co-operative food came top in the original research so will there be a nice present on the end of the TV show?

Antti-Juhani Kaijanaho: The Dying Philosophers Problem

Reading a masters thesis draft that mentions the dining philosophers problem – a parable about the difficulties of process synchronization very well known in computer science – it occurred to me that it must not be a very good idea to eat just spaghetti (or just rice). I asked a nutritionist about it, and here is her answer. Even if they manage to avoid deadlock or livelock, dying of malnutrition is not going to be their first problem, go read the full story! [Typos and thinkos corrected after initial publication]

Stefano Zacchiroli: secret identity

Secret Identity From now on, I'll be (also) known as zack@member.fsf.org, (not so) secret agent #5507. Go Mako, go: I'm really happy to see you there. /me hoping in a better future.

Fabio M. Di Nitto: Linux running on SUN's LDOM!

Guys.. meet Super Davem We did it again. After another *really* long session of super-tag-team play with Davem coding as hell and me testing like crazy we finally managed to do a full install of Linux (based on Debian/Ubuntu installer) on SUN's LDOM as guest host (similar to domU concept of Xen). There is still a lot of work to do and major problems to solve before we will able to call this "stable" for the generic user. David's blog has detailed instructions on how to install and a complete list of the issues. If you plan to try it, make sure to read David's blog! A net-boot gutsy installer image is available here and net-boot kernel here. The code published by David will hit the gutsy kernel as soon as we are satisfied with the overall situation. Most of the userland bits required to install are already in the archive and others will land soon after Tribe-2 release. STAY TUNED!

Cameron Dale: Making DebTorrent Work With APT

It's been a while since I've given a status update for my Google Summer of Code project to create a BitTorrent proxy for downloading packages using APT, so here it is. I've been working hard on integrating support for APT into the DebTorrent program. I've almost got it working perfectly, now it's just a matter of testing to make sure all is well. The functionality works like this: There are two things I really like about this. One of the best is the backup HTTP downloader. It insures that if you're an early adopter and there are no peers, or if the package you're requesting is rare and can't be found in any connected peers, the download will still occur in a reasonable amount of time (taking no more, or less, mirror bandwidth than if you had just been using APT directly). The other thing I like is that you get the BitTorrent-style peer-to-peer downloading, with simple HTTP proxying thrown in for free. You can run DebTorrent on a single computer on your network, and have the others connect to it to initiate downloads and request packages. I haven't done any serious time testing, but I estimate it currently only takes twice as long to use as a regular APT update and download from a mirror. Most of that slowdown is because it currently only processes a single request at a time from APT, which is not very efficient for BitTorrent systems where downloading from multiple peers is how the highest download speeds are achieved. I have been talking to the APT maintainer, Michael Vogt, about a better way to do this, probably by adding a new APT transport method for DebTorrent (i.e. debtorrent:// instead of http://). This will not only speed up the downloads, but also hopefully provide better feedback to the APT user, as currently it will seem nothing is happening until the download comes in all at once at the end. My work has unfortunately been slowed by other commitments, and bugs. I have two papers to submit to a conference by Monday, but after that I should be back full time on DebTorrent. I also spent a long time tracking down and fixing a bug in the underlying BitTornado code (which lead to much rejoicing at 3am), only to find it was fixed in upstream's CVS. (Doh!)

Next.

Previous.