Search Results: "ag"

2 February 2008

Adeodato Sim : Markdown links with newlines in the anchor text

Links in Markdown can be done in a couple ways. First, similarly to HTML links, where you place the link next to the anchor text, like this:
  I am a [Debian](http://www.debian.org) Developer.
Or, if you feel this clutters your paragraphs too much, you can choose an alternate syntax, which I prefer (particulary handy for very long links):
  I am a [Debian][] Developer. Bla bla bla...
    [debian]: http://www.debian.org
There is however a gotcha with this alternate syntax, namely, anchor text with spaces in them. This works fine:
  I study Computer Science in [this University][].
    [this University]: http://www.ua.es
But this does not:
  Some years ago, I started studying Computer Science in [this
  University][]. Bla bla bla...
    [this University]: http://www.ua.es
This actually happens quite a lot when formatting the paragraphs in the editor, which made this otherwise-pleasant syntax almost a no-go for me. (Well, to be honest you could use it like this, but still:
  Some years ago, I started studying Computer Science in [this
  University][uni]. Bla bla bla...
    [uni]: http://www.ua.es
)
There is a beta version of Markdown in experimental that almost fixes the problem. This version introduces a new but similar syntax for links: you can omit the second pair of empty brackets. And when using that newer syntax, there is code in the program to change newlines into a space when looking for the link definition. It is not applied to the code path of the old syntax, though, which is a pity. This is all explained in bug #459885, with a patch as well (that applies both to 1.0.1 and 1.0.2). You can find packages with that patch applied here.

Adeodato Sim : Running scripts on resume, after moving to pm-utils

I had a couple of annoyances with suspend in my laptop, namely that the screen would not lock prior to suspending (this seems to be #407224), and that sound would not work after resume (this seems to be an ALSA driver bug; muting and unmuting Master and PCM solves the issue). For this latter problem, I just wanted to drop a script somewhere to do the mute/unmute dance on resume automatically, but I was a bit lost as to where to put it. (Or, rather, I thought I’d be a bit lost even if I investigated.) Anyway, I recently moved to pm-utils from powersaved, since that’s what my kpowersave recommends first, and not only now my screen gets locked properly, but there is somewhat clear documentation as to where to put such scripts: /etc/pm/sleep.d. So I now have there a script like:
  case "$1" in
      thaw resume)
          amixer -q sset Master mute
          amixer -q sset Master unmute
          amixer -q sset PCM mute
          amixer -q sset PCM unmute
      ;;
      *)
      ;;
  esac
I only miss one thing: in my old suspend to disk scheme, the computer would change to a console where progress about the operation would be reported. Now it’s just a blank console. Guess it’s time to investigate again. (But overall I’m happy about the move.)

Christian Perrier: Preparing lenny D-I beta 1: l10n status

Otavio is currently busy preparing the first release of D-I for lenny. He is still polishng the release schedule but, as part of the process, I sent a call for translation updates today. The starting point is: 59 activated languages (including English) but 'only' 18 of them are 100%. For others:
1 100% bg
   100% cs
   100% de
   100% es
   100% eu
   100% fr
   100% gl
   100% gu
   100% it
   100% ja
   100% ko
   100% nl
   100% pt
   100% ru
   100% sk
   100% sv
   100% vi
   100% zh_CN   18
 2 099% hu      1
 3 098% be
   098% ca
   098% dz
   098% eo
   098% he
   098% ml
   098% nb
   098% nn
   098% pl
   098% pt_BR
   098% ro
   098% sq
   098% ta
   098% th
   098% zh_TW   15
 4 097% bn
   097% lt
   097% ne
   097% pa      4
 5 094% ar      1
 6 093% bs
   093% da
   093% el
   093% et
   093% fi
   093% hi
   093% hr
   093% id
   093% ka
   093% km
   093% lv
   093% mk
   093% sl
   093% tl
   093% tr
   093% uk
   093% wo      17
 7 090% am      1
 8 085% ku      1
Languages at 93% had no single updates since Etch. For these, I have some worries and I fear we could 'lose' some if their translator disappeared. Amharic and Kurdish never reached 100% yet but they have translated the most important strings, so we'll probably keep them. So, in short, the message to translators is: *move*. You have about 2 weeks.

1 February 2008

Andrew Pollock: [life] Hi ho, hi ho, it's back to work I... went

I went back to work today after something like a total of 6 weeks off. (2 weeks vacation, 4 weeks unpaid leave). The month of January went pretty quickly really. The week in hospital with Sarah was a blur. The week and a half afterwards was also pretty much a blur. Then we had the week where things went a bit backwards, and then we had this week, a few days of which were spent up north at an inn in Little River, Mendocino County. Heck, let's just call the entire month a blur and be done with it. Sarah's doing pretty well now. Surgery on the 3rd, discharged on the 9th, back in the Emergency Room on the 21st with tachycardia. Concerns about the incision weeping on the 21st, and again on the 28th. General increase in pain on the 28th, along with a few sleepless nights preceding. But now, with a doubling of her beta blockers, some antibiotics, pain killers, anti-inflammatories and sleeping tablets, she's feeling a bit more human again, if not like a human pill bottle. The surgical folks want to see her again on Monday to follow up how the incision is going since they prescribed the antibiotics. The weeping has calmed down significantly, but hasn't gone away completely. A couple more months to go before we can call her "recovered".

Filip Van Raemdonck: Read between the lines

Recently I've been debugging a SQL Server 2005 replication setup, where the "Distribution clean up" job for the distributor database was failing. The error message in the agent history was:
Executed as user: <sqlagent_serviceuser>. Could not remove directory <UNC_path_to_snapshot_directory>.
Check the security context of xp_cmdshell and close other processes that may be accessing the directory.
[SQLSTATE 42000] (Error 20015).  The step failed.
The “<sqlagent_serviceuser>” was the Windows user that the SQL Server Agent service was running under, while the “<UNC_path_to_snapshot_directory>” was the network path to the directory where snapshots where created.

Looking around on some discussion forums, I found the same message reported several times but without any real solution; at least no solution that would work when I tried to apply it to this particular setup. Most answers to the problem focused on the xp_cmdshell procedure mentioned in the error, and how it would require certain configuration at the server end.

However, one answer on the MSDN forums did give a useful clue — it pointed to the SQL Books Online article about Securing the Snapshot Folder (which I should've read right away, rally). In a note, this page reads:
If a publication is dropped, replication attempts to remove the snapshot folder under the security context of the SQL Server service account. [...]

It's the SQL Server service account reference which is essential: even though the SQL Agent service account may be the one mentioned in the error message, the actual account that is used to try and delete the snapshot directories is the SQL Server service account instead. Giving that service account the necessary access rights fixed the problem; as in the Task Scheduler case, accurate error reporting on Microsoft's side might go a long way towards people disliking their software less.

Simon Richter: Guards, guards!

Another design decision for "dammit" is how to handle dependency loops between header files -- these may be intentional, but most often are not, and I'd like to find these because they often lead to confusing error messages.

Evan Prodromou: 12 Pluvi se CCXVI

I'm really pleased to announce here that one of the projects Maj and I have been working on for a long time has finally come to fruition. Today Wikitravel Press launched its first two Open Content printed guidebooks -- Wikitravel Chicago and Wikitravel Singapore. When we started Wikitravel back in 2003 (!), our sincere hope was that at some point in the future, people would be able to carry Wikitravel guidebooks with them on a trip. I think that mobile technology is excellent, and it's amazing how much you can read on a cell phone or PDA these days. But there's still something so convenient about a printed guidebook: it never runs out of batteries; you don't need an uplink to read it; you don't have to worry about it getting stolen because you flashed it out in the wrong caf or restaurant. To be honest, I thought that one of the "traditional" guidebook publishers would step in and use Wikitravel content in their guides. But that didn't happen, and along with our partner Jani Patokallio, Maj and I decided to start a publishing company ourselves. Thus Wikitravel Press, and our first two books. We have a number of other books in the pipeline, and our hope is to have a few dozen available by the end of the year, and a few hundred by the end of the following year. I'm working on the Wikitravel guide to Montreal, and Maj and I are collaborating on Buenos Aires. We're taking a 6-week trip to Argentina in February/March, so this should be a great time for research. I heartily encourage any writers or editors who are interested in working on travel books to contact Wikitravel Press about your ideas of bringing Wikitravel content to print. I think this is a great opportunity for people who want to encourage Open Content, or who want to get into the travel writing field, or who just love the idea of wikis-to-books. tags:

31 January 2008

Joey Hess: generating pristine tarballs from git repositories

With pristine-tar version 0.5, I've added a new feature: The ability to easily inject enough information into a git repository so that a pristine tarball can later be regenerated from that repository. If a package's upstream branch contains the upstream source corresponding to the tarball to be imported, it's very simple to use.
joey@kodama:~/src/fbreader> pristine-tar commit ~/lib/debian/unstable/fbreader_0.8.12.orig.tar.gz 
pristine-tar: committed fbreader_0.8.12.orig.tar.gz.delta to branch pristine-tar
Otherwise, you also have to specify a tag (or any tree-ish really) where the upstream source can be found.
joey@kodama:~/src/fbreader> pristine-tar commit ~/fbreader_0.8.9.orig.tar.gz upstream/0.8.9
pristine-tar: committed fbreader_0.8.9.orig.tar.gz.delta to branch pristine-tar
Here's what it puts in the pristine-tar branch that it creates. In this example, the delta files are 40-some kilobytes, which is much nicer than if I'd had to check the 2 megabyte tarballs into git directly.
joey@kodama:~/src/fbreader> git checkout pristine-tar 
Switched to branch "pristine-tar"
joey@kodama:~/src/fbreader> ls -l
total 104
-rw-r--r-- 1 joey joey 46583 Jan 31 21:26 fbreader_0.8.12.orig.tar.gz.delta
-rw-r--r-- 1 joey joey    40 Jan 31 21:26 fbreader_0.8.12.orig.tar.gz.id
-rw-r--r-- 1 joey joey 45267 Jan 31 21:26 fbreader_0.8.9.orig.tar.gz.delta
-rw-r--r-- 1 joey joey    40 Jan 31 21:26 fbreader_0.8.9.orig.tar.gz.id
Don't forget to push the pristine-tar branch to your server for safekeeping.
joey@kodama:~/src/fbreader> git push origin pristine-tar
Once a tarball's delta is checked in, you can easily and quickly regenerate the original tarball.
joey@kodama:~/src/fbreader> pristine-tar checkout ../fbreader_0.8.12.orig.tar.gz
pristine-tar: successfully generated ../fbreader_0.8.12.orig.tar.gz
Yes, it's really the same file. :-)
joey@kodama:~/src/fbreader> md5sum ~/lib/debian/unstable/fbreader_0.8.12.orig.tar.gz ../fbreader_0.8.12.orig.tar.gz 
8045abe1acc75dbdd220400df541f23f  /home/joey/lib/debian/unstable/fbreader_0.8.12.orig.tar.gz
8045abe1acc75dbdd220400df541f23f  ../fbreader_0.8.12.orig.tar.gz
The above example is from the perspective of a maintainer of a Debian package. But this can also be used by the authors who generate the pristine tarballs in the first place. Check them into git using pristine-tar. Then you can regenerate any tarball you've ever released using just your project's git repository.
joey@kodama:~/src/pristine-tar> pristine-tar commit ../pristine-tar_0.5.tar.gz tags/0.5
pristine-tar: committed pristine-tar_0.5.tar.gz.delta to branch pristine-tar
One word of warning: For pristine-tar to check out the tarball, git needs to be able to check out the tree that you referred to when you committed it in the first place. If that was a tag that you've told git to delete, you're SOL. If it was a branch and the branch has changed in the meantime, that's fine, so long as git can find the original id that is stored in the .tar.gz.id file.
I hope that tools like git-import-orig and git-debimport can get support for automatically calling pristine-tar commit when importing tarballs into git, and that tools like git-buildpackage and gitpkg can use it to check out the tarballs.

Frank Lichtenheld: Some packages. debian.org,ubuntu.com updates

Lior Kaplan: The kernel evolution speed


Apc quotes Jonathan Corbet on his “The Kernel Report” talk in LCA 2008:
“We are adding about 2000 lines of code to the kernel every single day of the year, without exception,” Corbet said. “Nobody can really keep up with this [on their own] any more. It’s an amazing process, and it seems to be working.”
Although I didn’t (and probably can’t) contribute a single line to the kernel, reading this made me a prouder Linux user… you too ?

Filip Van Raemdonck: King of the hill

John, don't get too excited.
I hate to disappoint you, but I got #1 for “mysql takeover” on the very day I wrote about it. I also seem to be #1 for “CEST software”, simply because these are appearing next to each other whenever I post something about software, during CEST months. And I was on top for “converting from metres per seconds to metres per days”, too, but my silly post about it from two days ago already took over. For all I know, there are a few more like these, though none are obvious from search referrals yet.

I guess being on a few planets might be very good to your Google karma. (or should I say, pagerank?)

Kartik Mistry: ASUS Eee Laptop

* Laptop running Linux is yet dream for me! ASUS launched Eee laptop and PC and it is perfect for people like me :P And it can be hacked to do anything. Its fun!

Aigars Mahinovs: Quoted

A person that I deeply respect and who is very know in Latvian IT society recently said that he often uses a quote of mine in his presentations. I completely forgot that I ever said that, but it sounds very much like what I would say, so I wanted to write it down so that I do not forget about it again:
90% of the people do not understand copyright, the other 10% simply ignore it.
Heh, I must have been optimistic. There is no way that so many people actually understand copyright. :) Note: most Debian Developers and FLOSS developers in general are an exception to this rule, but sadly comprise such a small percentage of the population that it means very little from a public policy perspective.

Aigars Mahinovs: Slow starting USB storage in Linux

I have this USB hard drive enclosure that can also share the files on the local network (LAN DRIVE HD9-U2LA, vendor id - 05e3:0702). Due to that it has an operating system and some other software inside. Unfortunately this software is rather slow to start and that cause the following kernel error when trying to mount this enclosure:

[90459.236000] usb 5-5: new high speed USB device using ehci_hcd and address 9
[90459.368000] usb 5-5: configuration #1 chosen from 1 choice
[90459.368000] scsi4 : SCSI emulation for USB Mass Storage devices
[90459.368000] usb-storage: device found at 9
[90459.368000] usb-storage: waiting for device to settle before scanning
[90464.368000] usb-storage: device scan complete
[90470.148000] usb 5-5: USB disconnect, address 9
[90470.148000] scsi 4:0:0:0: scsi: Device offlined - not ready after error recovery
The device is fine, it is just slow to start. To work around this bug you can change /sys/module/usb_storage/parameters/delay_use from a default 5 second delay to something larger. 60 seconds worked fine in my case.
echo 60 sudo tee /sys/module/usb_storage/parameters/delay_use
Anyone know what a proper solution could be?

Peter Eisentraut: CDBS usage statistics

Here is a fun little statistic for CDBS lovers and haters: Percent of packages (source, binary) using CDBS over time:


Sources-sid-main-2005-04 9.76 10.02
Sources-sid-main-2005-05 10.20 10.62
Sources-sid-main-2005-06 10.36 10.76
Sources-sid-main-2005-07 10.76 11.16
Sources-sid-main-2005-08 11.05 11.36
Sources-sid-main-2005-09 11.48 12.32
Sources-sid-main-2005-10 12.08 13.12
Sources-sid-main-2005-11 12.66 13.68
Sources-sid-main-2005-12 13.13 14.13
Sources-sid-main-2006-01 13.29 14.37
Sources-sid-main-2006-02 13.59 15.00
Sources-sid-main-2006-03 13.97 15.34
Sources-sid-main-2006-04 14.38 15.73
Sources-sid-main-2006-05 14.53 16.17
Sources-sid-main-2006-06 14.71 16.30
Sources-sid-main-2006-07 15.17 16.54
Sources-sid-main-2006-08 15.84 17.04
Sources-sid-main-2006-09 16.23 17.07
Sources-sid-main-2006-10 16.60 17.24
Sources-sid-main-2006-11 16.97 17.56
Sources-sid-main-2006-12 17.46 17.90
Sources-sid-main-2007-01 17.66 17.97
Sources-sid-main-2007-02 17.87 18.12
Sources-sid-main-2007-03 18.06 18.38
Sources-sid-main-2007-04 18.27 18.68
Sources-sid-main-2007-05 18.86 19.39
Sources-sid-main-2007-06 19.64 20.66
Sources-sid-main-2007-07 19.79 20.93
Sources-sid-main-2007-08 20.13 21.15
Sources-sid-main-2007-09 20.32 21.33
Sources-sid-main-2007-10 20.81 21.95
Sources-sid-main-2007-11 21.16 22.02
Sources-sid-main-2007-12 21.48 22.17
Sources-sid-main-2008-01 22.12 22.67


World domination in about 2020. :)

Colin Watson: Vim omni completion for Launchpad bugs

I hacked together a little timesaver for developers this morning: omni completion for Launchpad bugs in Vim's debchangelog mode. To use it, install vim 7.1-138+1ubuntu3 once it hits the mirrors, open up a debian/changelog file, type "LP: #", and hit Ctrl-X Ctrl-O. It'll think for a while and then give you a list of all the bugs open in Launchpad against the package in question, from which you can select to insert the bug number into your changelog. Here's a screenshot to make it clearer: Thanks to Stefano Zacchiroli for doing the same for Debian bugs back in July.

Russell Coker: Suse and LCA

I previously wrote about how I gave a talk about SE Linux at a conference spot when a talk about AppArmor was scheduled. It turned out that the Suse people had notified the LCA people some time in advance about the fact that John would not be attending the conference. The LCA people had removed the entries from their databases and when the conference schedule was printed it had no reference to such a talk. The problem occurred when another tutorial (which had occupied the slot that was previously assigned to John) was moved to a different part of the schedule. For some reason the CMS that they use did not leave the slot in question empty but instead restored earlier contents (which was the Suse tutorial). No-one at LCA noticed this error and from that time on the web page generated by the CMS was used as the authoritative source of information about the issue by delegates and most of the LCA team.

Lior Kaplan: tar.bz2 sources in debian


Reading Raphael’s Misc development news (#2), I thought I can now upload packages with orig.tar.bz2 sources. Dak quickly replied an error, and the ftp-masters verified that this feature isn’t available (yet). So, for people like me, who didn’t read the text carefully or comprehended it wrongly, the new feature refers to the comprssion of the .deb file itself and not the the one of the upstream tarball. I just wonder when will it be possible to upload .orig.tar.bz2 files to the archive, as it will save me repackaging some of my upstream tarballs…

30 January 2008

Martin F. Krafft: Linux for visually-impaired (developers)

On Sunday, the day before LCA 2008 officially started, Kelly and Rusty asked us first-timers to blog about events, specifically about what we liked and disliked. So far, this conference has been really enjoyable and busy, and I have not found the time to write about its content. The talk I just heard leaves me without an excuse, so there: I have recently had a very interesting and enlightening discussion with a blind Debian developer. When I saw on the conference schedule that Jason White would talk about using Linux with speech and Braille output interfaces, I passed up my opportunity to hear Andrew Tridgell talk about clustered Samba and attended his lecture instead. Jason covered a great number of aspects: from the history of the Braille system, and current, Free implementations thereof, via speech output, to strategies of integrating these techniques into existing programmes which are generally not designed with visually-impaired users in mind. He has a collection of references on his webpage, to which I shall refer for the technical content. His presentation left me very excited and impressed. Excited to see him giving a presentation with such enthusiasm and energy, and impressed because his talk (without notes or slides) was by far better than the job of the average presenter with access to notes and slides to display. Jason conveyed a lot of information in a very well-structured, capitivating report. I think he left most of the audience speechless (figuratively speaking; there were good questions). I feel uneasy with thanking Jason explicitly, or even writing this blog post. If you bear with me for a minute, then let me bridge to women involvement in open-source software. My position on this topic is quite clear: I make no distinctions where they are not obvious, and simultaneously I think it s awesome that more and more women are joining the predominantly male crowd (and their influence undeniably makes the community a more comfortable place). Every now and then, I would like to comment on that, such as I think it s awesome that you are working on this, being a woman (an oversimplified example). What I am trying to say is given how few women are involved with OSS, I appreciate all the more what you are doing. This is non-judgemental, I don t say this because I am trying to highlight someone s gender or sex. It s a communication issue, and I am learning, but I d also rather not limit what I say by making absolutely sure never to offend anyone. But when I utter such a comment, it might still greatly annoy someone or yield vicious returns. This is not always the case in fact, less than it used to be but I ve encountered it here and there, which made me more careful. So when I write about Jason s presentation and how great it was, I want to highlight how it s a greater achievement for him than it would be for me, because he is blind and I am not. I don t mean to single him out or put him on the spot. I am simply impressed, very impressed. And being who I am, I d like to say so. Thanks, Jason. Update: David Schmitt makes an interesting point:
The important question is now, why are we blind people doing great presentations more impressing than people with working eyes doing a great presentation? My personal answer isn t so great: because I didn t expect it. No wonder people get offended if you tell em to their face that I m impressed with his achievements, because I wouldn t have expected it.
I don t agree, or at least I fail to see it. I was impressed, I did not expect it (which isn t to say that I came in to Jason s talk expecting it to be any less than a good talk, I had no expectation! Please think for a second if this isn t immediately clear!) is that offensive? I didn t know Jason, had no way to know whether his presentations are great or less so, but then he pretty much blew me away. The presentation was better than what I am used to (from anyone), and the achievement is all the more greater because it seems to me that he has had to put much more effort into it, purely for accessibility reasons. I guess I should know better, but I still, after all these years, have a problem seeing through the end of it, understanding it. Kant to the rescue, my intentions are good (I claim), but this goes both ways regardless: in any communication, one ought to try hard never to offend. At the same time, one ought to try hard not to be offended until one can be reasonably sure that offence was intended. When I brought this up in Adaora Oniya s miniconf talk on communication challenges, Bdale Garbee recalled the policy in use when he was involved in protocol design work groups: send politely, receive with an open mind. I don t remember his exact words, but I think I got the gist. Update: I just talked to Jason and got his feedback on the issue. It boils down to a quote I ll transcribe: I want my work to be judged by its merit and not by who I am. It only leaves me wondering about the situation at hand: I was impressed by his very well-structured and presented talk and by the fact that he did such a good job given his visual impairment. In any case, I ll close the issue. Jason told me he d happily engage in further discussion and I stated that he is not offended. There is another lesson I learnt: the next time I blog about someone else in such a way, I should really get his/her clearance before publishing! Just to be sure

John Goerzen: #1 on Google

I started this blog 5 years ago. In that time, I've written about Linux on the desktop, photography, international peace, version control systems, ice storms, Haskell, health care, rural life, Kansas, and infants.

Today I realized something: I am the #1 hit on Google when you search for smelly ducting. This will take you to a story I wrote back in 2005 about an odd odor in our house. I believe it is my most popular story ever, with almost 100 comments -- and comments continue to trickle in, a few a week.

What's the right word to use for that? When the great worldwide democratizing force that is the Internet collectively decides that your most important blog post is about smelly ducting?

I'm glad folks know what matters. Wouldn't want to worry too much about what's going on in Iraq, Washington, or Kansas if your ducts smell, that's for sure.

Obviously every single Presidential candidate has missed out on a key issue in voters' minds. If only someone would come out with a freshly-scented ducting platform, this country could finally move forward!

Next.

Previous.