[00:26] <mgz> this laptop better behave itself now I've spent all evening fiddling with it.
[00:27] <mgz> well, except for debian bug #619019 which means I'll just not be running x I guess
[00:37] <bob2> heh, I have an awesome hardware cursor bug that turns my cursor into a 64pixel long vertical black line
[00:51] <mgz> that's cute.
[00:51] <mgz> I'm now risking my evening's work with squeeze-proposed-updates to see if it's really fixed.
[00:57] <mgz> and I have a cursor, woho. will stop now before I break something else.
[08:45] <maxb> Does anyone know how to alter which key bzr-builddeb signs with by default *If* there are multiple secret keys with the same uid on the local keyring?
[08:45] <AuroraBorealis> is that a plugin?
[08:51] <lifeless> maxb: DEB_somethingorother
[08:51] <maxb> gah
[08:52] <maxb> Answer: Don't forget that you hardcoded your keyid in ~/.devscripts several years ago
[08:52] <maxb> :-)
[09:46] <maxb> Hmm, no jelmer
[09:47]  * maxb wanted to propose uncommitting a rogue merge from the debian packaging branch
[16:58]  * maxb bemoans obscure bzr-builddeb on karmic test failure
[18:19] <maxb> If I have a lower layer exception, which gets caught by a command implementation and a BzrCommandError thrown instead, what's the correct way to make the lower layer exception not completely lost so that debugging can find the underlying cause?
[18:47] <maxb> Right, I believe the proposed PPA is back in reasonably good shape
[21:26] <meoblast001> hi
[21:26] <meoblast001> is a .bzrignore file maintained across all checkouts?
[21:26] <meoblast001> or is it custom to each individual checkout?
[21:30] <lifeless> both
[21:30] <lifeless> there is one in your config directory
[21:31] <lifeless> and one in each working tree
[21:31] <lifeless> the rules are merged
[21:39] <meoblast001> ah