Debian Packages
Every now and again I look over server logs and see people downloading random .deb packages from my mirrors, or from my servers, via wget or Firefox (rather than with apt-get/aptitude). Personally I don't often download random binaries even from people I believe I can trust. Instead I'll download source and rebuild. But it bugs me that somebody might download a work-in-progress, decide it isn't complete or otherwise good enough, and miss out on an update of awesome-sauce a day or two later. I suspect there is no real solution to this "problem", and that including /etc/apt/sources.list.d/ entries inside a binary package to "force" an upgrade behind the scenes is a little too evil to tolerate. And yet .. something something dark-side .. something something seductive something?Blog Update
This is my last film-subject entry. In the future I will have more accurate subjects, albeit more dull ones. I still amuse myself with quotations, and before that the song lyrics, but I guess that now is a good time to call it a day with that.ObFilm: Cruel Intentions
Thanks to the versatility of the Linux kernel, Debian has always been known for supporting a large number of architectures. It has also often been criticized for that as it is said to slow down the development of Debian.
Among these architectures, the ARM one was considered dead a few years ago, and some people wanted to get rid of it. Today all major distributions now have an ARM port, one of those distributions being even based on Debian. It seems Debian was right.
Now that Android has been ported to MIPS, we may see more and more MIPS based devices. Will the same scenario happen again?
Folks at last year's Wikimania may remember the presentation I gave
there. It was essentially a literature review of Wikipedia and
Wikimedia scholarship from the previous year. The idea was to give a
bird's-eye-view as well a series of highlights -- all aimed at
Wikimedians.
Apparently somebody found it useful because I've been asked to do it
again! I'm going to be paired up in a longer session with Felipe
Ortega -- whose excellent dissertation I summarized as part of my
talk last year -- and Mayo Fuster Morell has also agreed to help
out. Felipe is program chair for WikiSym this year and will be
focusing on providing folks with a summary of the papers published at
that conference. It will be held immediately before Wikimania in Gdansk.
For my part, I'm going to be focusing more broadly and talking about
papers published, well, anywhere else.
And this is where you come in!
With search engines and all, I've got a pretty good idea of breadth of
the work that's out there. I also "just know" stuff from my own areas of
interest and study. That said, I don't have as strong of an idea of
what's good and what's relevant beyond what I can grok from citation
counts. And after one year (or less!), that's clearly not very much
information.
As a result, I'm looking for suggestions or recommendations from anybody
on interesting, useful, important, or otherwise noteworthy scholarly
papers on or about Wikipedia or other Wikimedia projects published in
the last year. Feel free to leave a comment, email mako@atdot.cc, or
edit this page.
Since I have started to use Org-mode, I though it was missing something to
have appointment locations on a map. Of course, it's easy to get a LOCATION
property from an entry, and then browse-url on Google Maps.
But it is too easy for me, so once again I said: challenge accepted! I will
bring Google Maps into Emacs!
After several hours of work, the google-maps-el project shows a map!
It fully implements the Google Static Maps API and the
Google Maps Geocoding API.
You can type M-x google-maps and type some place to see it marked on map. Of
course you can do much more, as seen in the screen shot above.
I've also completed all of this with a small org-location-google-maps which
simply show a Google Maps' map for the location of an event in Org mode by
pressing C-c M-l in an Org buffer or in the Org agenda.
Funny how life brings those A-HA moments in the least probable of circumstances. Take my career's development, for instance. I'm currently taking a training to become a government bureaucrat. During this training, each student goes through a thorough skill assessment to help the trainer select an appropriate training place in some government office. Asides from covering the obvious aspects of formal education and employment history, we also reviewed achievements and accumulated skills. My A-HA moment came as a result of our trainer asking me to completely rewrite my CV to match some known template. Additionally, she requested that I emphasize my technology background more. I countered by pointing out that the word "technology" tends to mean "engineer" to the average employer and yet I've have always been in Product Management or Business Development, which are more Sales-oriented roles than anything else, hence why I emphasize the Sales aspect and deflate the technology aspect in my CV. Still, while she conceded that difference in emphasis, she insisted that having worked in technology probably influenced my skills or my preferred workflow in one way or another. At the moment, I simply could not think of how it might have.
Boy, was I wrong! Where do I begin?
First of all, it dawned onto me that I simply cannot claim to know Microsoft Office anymore. Until recently, my Open Office skills were easily applicable to Microsoft Office, because Open Office borrowed a lot of concepts from its Microsoft counterpart. However, following the recent redesign of Microsoft Office, I found that I cannot navigate my way around Microsoft Word's menus anymore. While this new user interface paradigm indeed removes a lot of clutter, it also hides too many features in less than obvious places, which resulted in me concluding that I simply have to downgrade my Microsoft Office skills to medium. Given the progressive conversion of several Finnish agencies and ministries to Open Office, I'm not in such an uncomfortable position but, then again, other agencies and ministries fiercely cling on to their Microsoft licenses and have recently upgraded them. As such, should my practical training take place in one of those offices, I would essentially be unable to perform at my job. Redeeming factor: a friend who only knows Microsoft products faced similar frustrations last year when she got back from her summer vacations, after she realized that their network administrator had upgraded her workstation. It took her the whole autumn before she felt comfortable using Word again.
Another aspect of working in Free Software that influences my workflow: telecommuting and teleworking. As anyone working on Free Software projects knows, teams tend to be distributed around the globe, which means that there's always someone somewhere pushing a commit or answering bug reports, at any given time of the day. Simultaneously, work quickly becomes location-independent and flexible schedules are the norm; whatever and wherever works for a given developer, as long as the work gets done. Without anyone really noticing, this work methodology has permeated the whole technology ecosystem, even at fortune-500 companies. Employees come in and out of the office at whichever time suits them, while others choose to work from home and only show up whenever face-to-face meetings are called. Others even adopt a nomad lifestyle, constantly roaming the globe for adventures and connecting to the office network via VPN, from the comfort of their hotel room or from a friend's couch, on the other side of the globe.
In my case, having twice worked for Estonian companies while living in Finland, it meant taking the ferry twice a week to visit the office. This brought in more benefits than one might initially think: first of all, the quick walk between the metro station and the harbor in Helsinki meant that I arrived on the ferry with blood pumping adrenaline and fully alert. Being on the ferry gave me 2 hours of quiet time to grab my first coffee and plan my day. Getting out of the ferry in Tallinn meant another quick walk, this time between the harbor and the tramway. By the time I arrived at the office, I had exercised twice and planned all my workday. It's probably the most productive that I've ever been in my whole career. Additionally, I was frequently on the road, meeting customers and following on sales leads, which meant that I got to close many deals using my laptop in my hotel room. As our CEO used to joke, "I have no idea where in the world Martin- ric is today but, just as long as the purchase orders keep on pouring in, it's all the same to me."
As a result of this reflexion, I had to explain to our trainer why I am extremely well-suited to government jobs that require a lot of traveling and where Free Software is used on the desktop and, vice-versa, extremely unsuited to back-office jobs where whatever Microsoft products of the day are the norm. I've had to put particular emphasis on what Open Office is all about, because many homeworks were supposed to be submitted in Microsoft Word format. While Writer indeed offers the option to import and export Microsoft formats, it doesn't come with any WYSIWYG guarantee, which is why I took on the habit of sending her PDF documents. Sadly, this did not always work out so well, especially in cases where the intention was to forward selected parts of a document to third-parties.
Conclusion: working in the Free Software industry, even in non-engineering roles, indeed has a strong influence on someone's choice of methodology, tools and workflow. In some cases, it can even disqualify someone from making certain career choices.
Who would have thought?
I ve written a simple application which will automatically extract media from CDs and DVDs when they are inserted into the drive attached to my server. This makes it easy for me to compile all of my media in one place and access it anytime I like. The application uses the modern udisks API, formerly known as DeviceKit-disks, and I wrote it in part to learn get some experience working with udisks (which, it turns out, is rather nice indeed).
Naturally, I wanted to grant this application the privileges necessary to mount, unmount and eject removable media. The server is headless, and the application runs as a daemon, so this would require explicit configuration. udisks uses PolicyKit for authorization, so I expected this to be very simple to do. In fact, it is very simple, but finding out exactly how to do it wasn t quite so easy.
The Internet is full of web pages which recommend editing /etc/PolicyKit/PolicyKit.conf. As far as I can tell, nothing pays attention to this file anymore, and all of these instructions have been rendered meaningless. My system was also full of tools like polkit-auth, from the apparently-obsolete policykit package, which kept their configuration in some other ignored place, i.e. /var/lib/PolicyKit. It seems the configuration system has been through a revolution or two recently.
In Ubuntu 10.04, the right place to configure these things seems to be /var/lib/polkit-1/localauthority, and this is documented in pklocalauthority(8). Authorization can be tested using pkcheck(1), and the default policy can be examined using pkaction(1).
I solved my problem by creating a file in /var/lib/polkit-1/localauthority/50-local.d with a .pkla extension with the following contents:
[Access to removable media for the media group]
Identity=unix-group:media
Action=org.freedesktop.udisks.drive-eject;org.freedesktop.udisks.filesystem-mount
ResultAny=yes
This took effect immediately and did exactly what I needed. I lost quite some time trying to figure out why the other methods weren t working, so perhaps this post will save the next person a bit of time. It may also inspire some gratitude for the infrastructure which makes all of this work automatically for more typical usage scenarios, so that most people don t need to worry about any of this.
Along the way, I whipped up a patch to add a --eject option to the handy udisks(1) tool, which made it easier for me to test along the way.
I've grown tired of the firefox/iceweasel memory hog for a couple of reasons:
Neil Williams recently commented on the lack of smart-bookmarks in Firefox/Iceweasel/Chromium and since the post doesn t accept comments, counter-post FTW.
Inspired by various Planet Debian postings, I've spent some time
recently looking into a few RC bugs to help with the Squeeze release.
mpg123-el #581227 A
previous commenter on this bug suggested a proposed fix, which I tested
and uploaded. I think the bug's severity was inflated to begin with, so
I downgraded the bug as well.
doclifter #580246 This
one had to do with the python2.6 transition. I
pointed out a patch against Ubuntu's version of the package that fixes
this problem, and someone else made an NMU based on that. (Seemed like a
good idea to look in the PTS for Ubuntu patches since Ubuntu always
transitions to newer Python before Debian proper.)
gnuvd #580110 I
checked upstream and a new version that's supposed to fix this bug was
released today, so I updated the bug report to make note of this and
give the maintainer a chance to look at it.
libtommath #583820 This
FTBFS bug was caused by a previous NMU that fixed a different FTBFS and
also made some unrelated changes. I sent a message to the previous NMUer
noting this fact and made a new upload fixing the new FTBFS.
fceu #580820 Needs
new upstream packaged to fix. The maintainer seems pseudo-MIA but has
shown some signs of returning to activity; I sent an email inquiring as
to whether he intends to fix the critical issue in this package.
op-panel #582377 and #571427
These were not merged when I started out, so I merged them after
noticing they were the same. I spent some poking at the bug itself and
made a simple patch, only to find out that there was a pending patch in
pkg-voip's subversion repo. I hopped onto #debian-voip to prod the
person who'd prepared the patch in subversion about the importance of
updating the BTS when working on bugs. These bugs are currently blocking
on testing the patch.
Most all of these bugs I've subscribed to in case of follow-up. (Geez,
challenge-response subscription via email is kind of a pain.)
Jacob s second discovery was a cassette tape player. Awhile back, Terah rescued an old cassette tape player that was being thrown out, and bought a few 15-cent tapes for Jacob at a thrift store. The idea is that we can just let him play, and not care if he smashes it to bits. He enjoys it, but like the computer, didn t really get excited about it. Until yesterday, when we had this conversation:
Me: Jacob, would you like to record your own voice on a tape?
Jacob: (excited) Sure!
Me: OK, bring me your tape recorder.
Jacob: (exasperated) Dad, it s not a tape RECORDER. It s a tape PLAYER.
Me: Jacob, it is a tape player, but it s also a tape recorder too.
Jacob: (paused for about 5 seconds, then ) Ooooo! That is silly! (scampers off to find it)
He found it, and I helped him put some tape over the write-protect tab on a cassette he had. Then he recorded his voice. He eventually figured out the stop, rewind, play, and record buttons with my help. But he s still confused: while he s recording, why doesn t he hear anything? Our first recording had me asking him some questions, and then telling him to press the stop button when he was done. He listened to it dozens of times, and each time my recorded voice asked a question, he answered it a little before his recorded voice did. And each time my recorded voice told him to press the stop button, he would say, I don t want to while his recorded voice asked is this it? He pretty well understands what the radios are about, but doesn t really get the tape recorder yet. Nevertheless, it has just become a far more exciting device in his eyes.
Terah has been rolling her eyes at me today as I ve been trying to think up what other broken or old bits of technology we might have that Jacob would enjoy. My latest plan involves adapting his broken old batte
On probably a dozen occasions, I've had people in cars taunt me by
yelling some version of "Lance!", "Hey Lance!" or "Go Lance!" at me
while I am riding my bike. It seems to be particularly likely if I'm
wearing spandex.
Indeed, the "verb" to Lance has an Urban Dictionary entry and there
is a Facebook group for Yelling "Hey Lance!" when you see someone
riding their bike.
My friend Seth pointed out -- after we were (collectively?)
called "Lance" in California -- that it's pretty strange to insult
somebody by comparing them to a man who is nearly guaranteed to be on
any list of greatest living athletes, in any sport.
So previously I introduced the idea of my image-tagging system. There seemed to be at least a little interest. So here's a brief introduction and real update.
There is a command line tool, itag, which will index the UserComment field from a hierarchy of JPG files. (This field is compatible with digikam, by happy accident).
Additionally there are a pair of GUI tools, both very nasty in terms of code quality and extensibility:
Next.