Since quilt 0.46-7 (see #527255) you can automatically apply/unapply a quilt patch serie with debhelper s dh command. It s very practical in tiny rules files:
%: dh --with quilt $@There s also
dh_quilt_patch and dh_quilt_unpatch for those who don t use tiny rules files.
Enjoy !
Partagez cet article / Share This
This is going to be a fantastic and exciting Perl summer.
During the last week, I received notification that the talk I've proposed for both YAPC::NA and YAPC::EU was accepted.
I will be talking about Perl in the Time of Social Networks, which is mainly two broad things: how Perl can actively power a modern social networking site (I'll be releasing a free -as in speech- social network website, similar to Lovd or RailSpace, built with pure Catalyst); and about high-load applications dealing with social networks' APIs and users (a Moose-based universal social network distributor), with Twitter, Facebook, MySpace, Blogger, LastFM, and others. My current contractor has been sponsoring the development and research for this since almost two years now, and we believe it's ready to go public: there's a lot of work backing us up.
I'll be presenting the talk in Pittsburgh, PA, on June 23rd at YAPC 10. If you are around the area, come and attend the talk!
On YAPC::EU::2009, I will be presenting in Lisbon, Portugal, on August 4th, which is conveniently placed just after DebConf 9, which will happen in C ceres, Spain the week before (I will also be there).
Because of the recently announced attack against the SHA-1 digest algorithm, I finally decided to move away from my old 1024-bit DSA OpenPGP key, landing to a shiny new 4096-bit RSA one.
The old key will continue to be valid for some time, but I prefer all future correspondence to come to the new one. I would also like this new key to be re-integrated into the web of trust. I'm attaching a file with$ gpg --decrypt key-transition_20090509.txt gpg --decryptIf you need to transition your key too, and you're one of my signees, then let's please coordinate, so that we have the new keys cross-signed, without spurious signatures fromgoing-to-be-revoked keys 
Thank you for your help.
| Attachment | Size |
|---|---|
| key-transition_20090509.txt | 4.03 KB |
-----BEGIN PGP SIGNED MESSAGE-----How much money should be spent on this person's illness? which is a very, very bad question. We try to sidestep it by only taking about statistics etc., but no matter how you look at it, you either do 20'000 per week medications for 80 year old patients who will die soon anyway and get a system society can't pay, or you don't and you get a system where the rich are better off than the poor.The problem is, the majority of health costs are in the last few years of a persons life: when the body is breaking down. If viewed from the problem of health-care funding vs. eg. education, you have an ethical dilemma: is it worth it ? Here there are no easy answers. Nick Bostrom wrote a very interesting and persuasive essay a while back, The fable of the Dragon Tyrant. In short, we are getting somewhere with regenerative medicine While cures are hard to come by at this stage, there is a growing realization in medicine that senesence, what we used to call "old age", is curable. But we have a lot of psychological defensive mechanisms to help us cope with the carnage of old age that make us deny the problem: if we look afresh at "old age" knowing it to be curable, any delay in doing so is abhorrent. From a public, societal perspective, we spend a fortune every year on health. But we do so in a very disjointed way: we pay colossal amounts for health care, but also for basic health science: in the US, for example, the budget for the National Institutes of Health is about 30 billion dollars. Nearly twice that of NASA. Similar figures are spent in Europe, but there is this strange gap in the middle: the drug companies and medical industry. We start the development of new drugs with public money, and we buy the drugs with public money, but the choice of what drugs and treatments are developed are left to private industry, that is, a profit motive. This results in many cases in expensive treatments to treat symptoms rather than necessarily cure the problem. Faced with the huge costs of geriatric medicine and senesence, the response should be co-ordinated: funding a cure will be expensive, but save a fortune (Think, instead of a pensioner slowly dying and 'being a drain on resources', of 'experienced citizen in the prime of their productive, tax-paying years'). Instead of funding the basic science alone, we should be funding the complete drug and treatment development publically, only farming out the actual manufacture to private industry. It is silly to spend a fortune to keep merely keep someone alive at the age of eighty or so, when we know for a larger investment (bigger than a private company can do), we can cure them properly. The solution to the dilemma, then, is to stop thinking of the elderly being a drain, but actually applying our public efforts in a co-ordinated manner to solving the carnage of old age.
Following to the recent announce of a serious possible attack against the SHA-1 digest algorithm, I have just generated new GPG keys.
My personal key 9F71D449 will hence be progressively replaced by my new key: 290D20C5092F 4CB5 5F19 E006 1CFD B489 D32B 8D66 290D 20C5
D17A A78F 7992 A07D 9D85 517C C3E1 8B20 E435 C74B
wget -O - http://packages.kirya.net/Kirya.netDebianpackagesVerificationKey.asc apt-key add -
require 'rubygems'
gem 'soap4r'
require 'base64'
require 'soap/rpc/driver'
require 'soap/wsdlDriver'
wsdl_url = ARGV.shift
proxy = SOAP::WSDLDriverFactory.new(wsdl_url).create_rpc_driver
# run ruby with -d to see SOAP wiredumps.
proxy.wiredump_dev = STDERR if $DEBUG
require 'soap/header/simplehandler'
require 'soap/element'
require 'xsd/datatypes'
class WsseAuthHeader < SOAP::Header::Handler
NAMESPACE= 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd'
USERNAME = 'Not really the username'
PASSWORD = 'Put your own password here'
def initialize()
super(XSD::QName.new(NAMESPACE, 'Security'))
end
def on_outbound
security = SOAP::SOAPElement.new('wsse:Security')
security.extraattr['xmlns:wsse'] =
'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd'
unt = SOAP::SOAPElement.new('wsse:UsernameToken')
unt.extraattr['xmlns:wsu'] =
'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'
un = SOAP::SOAPElement.new('wsse:Username', USERNAME)
unt.add(un)
pw = SOAP::SOAPElement.new('wsse:Password', PASSWORD)
pw.extraattr['Type'] =
'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText'
unt.add(pw)
# Create a nonce...
nonce = SOAP::SOAPElement.new('wsse:Nonce', Base64.encode64((rand() * 1000000000).to_i.to_s))
nonce.extraattr['EncodingType'] =
'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary'
unt.add(nonce)
# The time format returned by XSDDateTime isn't quite right, so we
# fiddle with it a bit.
unt.add(SOAP::SOAPElement.new('wsu:Created',
XSD::XSDDateTime.new(Time.now.utc - 30).to_s.gsub(/..*/, "") + "Z"))
security.add(unt)
return SOAP::SOAPHeaderItem.new(security, true)
end
end
proxy.headerhandler << WsseAuthHeader.new()
... call proxy methods to interact with web service ...
\begin figure [htbp] \centering \begin tikzpicture [<->, auto, block/.style = rectangle, draw=blue, thick, fill=blue!20, text width=3.5cm, text centered, rounded corners, minimum height=2cm, font=\sffamily , line/.style = draw, thick ] \matrix [column sep=5mm, row sep=2cm] % row 1 & \node [block] (top) Rectangle A ; \\ % row 2 \node [block] (left) Rectangle B ; & & \node [block] (right) Rectangle C ; & \\ ; \begin scope [every path/.style=line] \path (left) -- node [midway,font=\sffamily\footnotesize] Arrow desc 1 (top); \path (left) -- node [midway,font=\sffamily\footnotesize] Arrow desc 2 (right); \path (top) -- node [midway,font=\sffamily\footnotesize] Arrow desc 3 (right); \end scope \end tikzpicture \caption My fancy image \label fancyimage \end figure
At this point, I d like to take a moment to speak to you about the Adobe PSD format. PSD is not a good format. PSD is not even a bad format. Calling it such would be an insult to other bad formats, such as PCX or JPEG. No, PSD is an abysmal format. Having worked on this code for several weeks now, my hate for PSD has grown to a raging fire that burns with the fierce passion of a million suns. If there are two different ways of doing something, PSD will do both, in different places. It will then make up three more ways no sane human would think of, and do those too. PSD makes inconsistency an art form. Why, for instance, did it suddenly decide that *these* particular chunks should be aligned to four bytes, and that this alignement should *not* be included in the size? Other chunks in other places are either unaligned, or aligned with the alignment included in the size. Here, though, it is not included. Were it within my power, I would gather every single copy of those specs, and launch them on a spaceship directly into the sun.Even if this account represents unadulterated irritation, he leaves us, the reader, with nothing of the irritation, only pleasure. This aftermath of frustration is delivered through the vehicle of humor, which within the hacker context, is the cultural container that best captures the spirit of hacker pleasure or so I will be arguing. Like many humorous rants from the world of hacking (and please send me any others you know of), this text dances with liveliness; it exudes its own rhythm; it glistens to use Ronald Barthes apt phrasing from his short book The Pleasure of Text, which I just finished as part of my theoretical escape into the pleasure-dome. Although there are parts of his book which are to be frank, *really* *not* *pleasurable*, partly due to obscure references to High French Theory, which elide even an academic pair of eyes, the book generally pleases. And one of the most pleasing chunks is his definition of a stereotype:
The stereotype is the word repeated without any magic, any enthusiasm, as though it were natural, as though by some miracle this recurring words were adequate on each occasion for different reasons, as though to imitate could no longer be sensed as an imitation: an unconstrained word that claims consistency and is unaware of its own insistenceIn contrast to the stereotype, a string of words that enchants does so by slipping off the page to hit you squarely in the heart or the gut. Unfortunately, while academic writing steers clear of stereotypes, often trying to present the detailed singularity of a phenomena (even when conditioned by social forces), it does not exactly glisten, though there are a handful of exceptions. I think we need more texts that glisten, even if only during sections or parts of our books and articles (much like the rant helped enliven the more staid technical document). In recent years, in large part due to the influence of free software, there has been an explosion, a move toward going open access. All of this is laudable and I fully embrace it (and have gotten into some small battles over it). But without an aesthetic politics that values pleasure in reading and writing we are doomed to obscurity anyway. A move toward making our knowledge public also required a move toward thinking about the literary aesthetics of pleasure.
At this point, I d like to take a moment to speak to you about the Adobe PSD format. PSD is not a good format. PSD is not even a bad format. Calling it such would be an insult to other bad formats, such as PCX or JPEG. No, PSD is an abysmal format. Having worked on this code for several weeks now, my hate for PSD has grown to a raging fire that burns with the fierce passion of a million suns. If there are two different ways of doing something, PSD will do both, in different places. It will then make up three more ways no sane human would think of, and do those too. PSD makes inconsistency an art form. Why, for instance, did it suddenly decide that *these* particular chunks should be aligned to four bytes, and that this alignement should *not* be included in the size? Other chunks in other places are either unaligned, or aligned with the alignment included in the size. Here, though, it is not included. Were it within my power, I would gather every single copy of those specs, and launch them on a spaceship directly into the sun.Even if this account represents unadulterated irritation, he leaves us, the reader, with nothing of the irritation, only pleasure. This aftermath of frustration is delivered through the vehicle of humor, which within the hacker context, is the cultural container that best captures the spirit of hacker pleasure or so I will be arguing. Like many humorous rants from the world of hacking (and please send me any others you know of), this text dances with liveliness; it exudes its own rhythm; it glistens to use Ronald Barthes apt phrasing from his short book The Pleasure of Text, which I just finished as part of my theoretical escape into the pleasure-dome. Although there are parts of his book which are to be frank, *really* *not* *pleasurable*, partly due to obscure references to High French Theory, which elide even an academic pair of eyes, the book generally pleases. And one of the most pleasing chunks is his definition of a stereotype:
The stereotype is the word repeated without any magic, any enthusiasm, as though it were natural, as though by some miracle this recurring words were adequate on each occasion for different reasons, as though to imitate could no longer be sensed as an imitation: an unconstrained word that claims consistency and is unaware of its own insistenceIn contrast to the stereotype, a string of words that enchants does so by slipping off the page to hit you squarely in the heart or the gut. Unfortunately, while academic writing steers clear of stereotypes, often trying to present the detailed singularity of a phenomena (even when conditioned by social forces), it does not exactly glisten, though there are a handful of exceptions. I think we need more texts that glisten, even if only during sections or parts of our books and articles (much like the rant helped enliven the more staid technical document). In recent years, in large part due to the influence of free software, there has been an explosion, a move toward going open access. All of this is laudable and I fully embrace it (and have gotten into some small battles over it). But without an aesthetic politics that values pleasure in reading and writing we are doomed to obscurity anyway. A move toward making our knowledge public also required a move toward thinking about the literary aesthetics of pleasure.
Debra and Ian at Tanagra.
The Source.
The Source at Yahoo.
Jaldhar and the Source at Tanagra.
Torvalds under two moons, his sky is grey. Git, his arms wide.
Jaldhar of Tanagra, Git of Torvalds, at Lungha.
Jaldhar and Git in court. The court of silence.
Jaldhar, his eyes closed.
#debian-devel, its arms wide, its thighs fat.
Jaldhar, his eyes open!
The Source in Git, its sails unfurled.
Update: From Barak A. Pearlmutter who doesn't have a blog.
JOIN US, AS GNULIB HAS.
THERE IS NOTHING TO FEAR.
SUSPEND YOUR DOUBTS.
SUBMIT TO THE GIT.OR.CZ SUPERIORITY.
YOUR REPOSITORY WILL BE CONVERTED.
COMPLEXITY IS BLISS.
ALL CODE WILL BE REPLICATED.
ALL BRANCHES SERVE THE CONSENSUALITY.
YOUR INDIVIDUALITY WILL BE A
TREASURED ASSET OF THE GITHUB.
* New upstream release
+ A large part of the code has been rewritten.
+ A new-style SPAM rule has been implemented.
+ A new, global Whitelist rule has been implemented, for
the SPAM rules to take advantage of.
+ New, "Custom Sieve Code" rule has been implemented; this allows users
to enter directly Sieve code snippets as a rule. (experimental)
+ Miscellaneous code movement and restructuring.
+ UI: The "Add New Rule" buttons are now links, and are displayed
both at the top and at the bottom of the rule table.
+ UI: Major rework in the UI of both the Rules Table and the Add New
Rule / Edit Rule pages.
+ UI: If a vacation rule is active, then display a notice in the
rules table page and upon logging in to Squirrelmail, that reminds
the user.
+ UI: Vacation options have been aligned properly; text has been
changed accordingly.
+ Sieve: Vacation Subject is now supported.
+ New functionality: "Insert New Rule Here"
+ New functionality: "Move Rule to Position" (requires Javascript)
+ Avelsieve now highly recommends the use of javascript_libs plugin
for some visual effects / UI improvements.
+ UI: Added new icons and used different ones, to improve usability.
Icons are provided by Mark James' famfamfam.com.
+ UI: Added new icon "theme" based also on famfamfam.com. This theme
is the default from now on.
+ UI: Removed unnecessary text / clutter from rules table page.
+ UI: The notify action options have been aligned in a table.
+ Added an LDAP Sieve storage backend, compatible with Sun Messaging
Server's Sieve features.
+ The DO_Sieve_* backends should have a separate retrieve() method
for retrieving the raw Sieve script. Currently, only the Managesieve
backend has it.
So, recently our email overlords graciously provided means for
us minions to help them in their toils and help clean up the
spammish clutter in the mailing lists by helping report the spam.
And the provided us with a dead simple means of reporting such spam
to them. Now, us folks who knoweth that there is but one editor,
the true editor, and its, err, proponent is RMS, use Gnus to follow
the emacs mailing lists, either directly, or through gmane. There are plenty of examples out
there showing how to automate reporting spam to gmane, so I
won t bore y all with the details. Here I only show how one serves
our list overlords, and smite the spam at the same time.
Some background, from the Gnus info page. I ll try to keep it
brief. There is far more functionality present if you read the
documentation, but you can see that for yourself.
The Spam package provides Gnus with a centralized mechanism for detecting and filtering spam. It filters new mail, and processes messages according to whether they are spam or ham. There are two contact points between the Spam package and the rest of Gnus: checking new mail for spam, and leaving a group. Checking new mail for spam is done in one of two ways: while splitting incoming mail, or when you enter a group. Identifying spam messages is only half of the Spam package s job. The second half comes into play whenever you exit a group buffer. At this point, the Spam package does several things: it can add the contents of the ham or spam message to the dictionary of the filtering software, and it can report mail to various places using different protocols.All this is very plugin and modular. The advantage is, that you can use various plugin front ends to identify spam and ham, or mark messages as you go through a group, and when you exit the group, spam is reported, ham and spam messages are copied to special destinations for future training of your filter. Since you inspect the marks put into the group buffer as you read the messages, there is a human involved in the processing, but as much as possible can be automated away. Do read the info page on the Spam package in Gnus, it is edifying. Anyway, here is a snippet from my
etc/emacs/news/gnusrc.el file, which can help automate
the tedium of reporting spam. This is perhaps more like how Gnus
does things than having to press a special key for every spam, and
which does nothing to help train your filter.
1 (add-to-list 2 'gnus-parameters 3 '("^nnml:\\(debian-.*\\)$" 4 (to-address . "\\1@lists.debian.org") 5 (to-list . "\\1@lists.debian.org") 6 (admin-address . "\\1-request@lists.debian.org") 7 (spam-autodetect . t) 8 (spam-autodetect-methods spam-use-gmane-xref spam-use-hashcash spam-use-BBDB) 9 (spam-process '(spam spam-use-resend)) 10 (spam-report-resend-to . "report-listspam@lists.debian.org") 11 (subscribed . t) 12 (total-expire . t) 13 ))
.gnusrc:
(defun jj-forward-spam-lists-debian ()
(interactive)
(gnus-summary-resend-message "report-listspam@lists.debian.org" 1)
)
(add-hook 'gnus-summary-mode-hook
(lambda ()
(local-set-key (kbd "<f7>") (quote jj-forward-spam-lists-debian))))
and whenever you are in a summary buffer you can press f7 to bounce the mail at your cursor to the report-listspam address. Thats all you need.
Providing city services only to users of specific proprietary software is bad public policy. I just discovered that New York City's 2009 Summer Youth Employment Program requires Internet Explorer in order to apply online. Even downloading the pdf version of the application to print out from the site is impossible under non-IE browsers because the actual pdf link is wrapped in some IE-only javascript. And even if you could download the PDF directly, any additional "online information to help you select a SYEP provider" is inaccessible for the same reason. I just called 311 and filed an official complaint against the NYC Dept. of Youth and Community Development (DYCD), who sponsor the program. I also called the number on the application page (1-800-246-4646), and spoke with "Karen" from the DYCD, who explained that the site was a New York City web site, and that it had been created by DoITT (the Department of Information Technology and Telecommunications) at the request of the DYCD, but that the DYCD didn't program it directly. She seemed to misunderstand the tech behind the situation, saying "we can't bring it to a higher level (like Firefox) because then it wouldn't work for everyone". I was happy that she understood that Firefox was a concern here, but the point is not to build the site "higher" to Firefox, but to use standard technology that all browsers can access for a public site. Karen also seemed to think the situation was acceptable because the city youth "can always use IE on local public library computers" to access the site. Note that the applications involve submitting very detailed information (SSN, health insurance, family income, criminal record, selective service registration #, etc), which are things that i would personally be unwilling to submit over a shared public computer if i had any other choice. Furthermore, this crappy implementation decision encourages the NYPL to continue to spend limited resources on proprietary software to an out-of-state monopolist to run their computer labs, which is money that could be better spent locally (or even spent on books or something similarly quaint and library-like). I'm frustrated. This is 2009. The application process for public services here should not require any proprietary technology, but it uses it gratuitously. This excludes legitimate citizens, and encourages Microsoft in its ongoing pursuit of monopoly status. Both of these are bad things. I submitted feedback on the DYCD customer survey web site, and submitted two 150-word-limited(!) complaints to Commissioner Mulgrav of the DYCD and Commissioner Cosgrave of DoITT. I'm sure they'd be interested in hearing from other people about this. Is this kind of proprietary lock-in what we should expect from a Mayor who cuts budgets city-wide except for IT? Where is all that money going? What is the city getting out of it?Tags: policy
Recently, I have made fairly major changes to kernel-package,
and there were some reports that I had managed to mess up cross
compilation. And, not having a cross-compilation tool chain handy,
I had to depend on the kindness of strangers to address that issue.
And, given that I am much less personable than Ms Vivien Leigh,
this is not something I particularly look forward to repeating.
At the onset, building a cross compiling tool chain seems a
daunting task. This is not an activity one does frequently, and so
one may be pardoned for being non-plussed by this. However, I have
done this before, the most recent effort being creating one to
compile rockbox binaries, so I
had some idea where to start. Of course, since it is usually years
between attempts to create cross-compiling tool chains, I generally
forget how it is all done, and have to go hunting for details.
Thank god for google.
Well, I am not the only one in the same pickle, apparently, for
there are gobs of articles and HOWTOs out there, including some
pretty comprehensive (and intimidating) general tool sets to
designed to create cross compilers in the most generic fashion
possible. Using them was not really an option, since I would forget
how to drive them in a few months, and have a miniature version of
the current problem again. Also, you know, I don t feel comfortable
using scripts that are too complex for me to understand I mean,
without understanding, how can there be trust?
Also, this time around, I could not decide whether to cross
compile for arm-elf, as I did the last time, or for
the newfangled armel target. A need for quickly
changing the target for the cross compiler build mechanism would be
nice. Manually building the tool chain makes a wrong decision here
expensive, and I hate that. I am also getting
fed up with having to root around on the internet every time I
wanted to build a cross compiler. I came across a script by Uwe
Hermann, which started me down the path of creating a script,
with a help option, to store the instructions, without trying to be
too general and thus getting overly complex. However, Uwe s
script hard coded too many things like version numbers and upstream
source locations, and I know I would rapidly find updating the
script irritating. Using Debian source packages would fix both of
these issues.
I also wanted to use Debian sources as far as I could, to ensure
that my cross compiler was as compatible as I could make it, though
I did want to use newlib (I don t know
why, except that I can, and the docs sound cool). And of course the
script should have a help option and do proper command line
parsing, so that editing the script would be unnecessary.
Anyway, all this effort culminated in the following script:
build cross
toolchain, surprisingly compact. So I am now all set to try and
cross compile a kernel the next time a kernel-package bug
comes around. I thought that I would share this with the lazy web,
while I was at it.
Enjoy.
The next thing, of course, is to get my script to create a
qemu base image every
week so I can move from user mode Linux to the much more nifty
kvm, which is what all
the cool kids use. And then I can even create an arm virtual
machine to test my kernels with, something that user mode linux
can t easily do.
Older (up to the *60 series) Thinkpads have a slightly odd mixer setup. There's a mixer stage that sits between the software controllable mixer and the speakers. This is controlled by the firmware in response to the volume keys being hit and can't be prevented by the OS. This is unfortunate, since users are quite enthusiastic about seeing an on-screen display when they hit various keys and if we do the obvious thing and map the volume keys to KEY_VOLUMEUP and KEY_VOLUMEDOWN then they get the OSD but also get their software-controlled mixer changed at the same time as their firmware-controlled mixer. This causes boundless confusion.
Next.