MadBlog
Wednesday 7 May 2008

git prompt

Following Martin's post on the subject, since I created my prompt, I've updated quite a lot.

It only showed the branch before, now it does so even when I'm on a detached head or something, and also shows when I'm in the middle of a rebase or a merge. You can see the zsh-fu for this. For example, when I'm in the middle of a rebase on my paid work repository, it looks like:

┌─(10:34)──<~/dev/mmsx master <rebase -i>>──
└[artemis]                                                 (~/dev/mmsx/Build/)

With nice colors I cannot really show without a screenshot that I'm too lazy to do :) This is a recent addition that I shamelessly took from the contrib bash prompt in git-core package. And to be frank it's really needed, because it's cheap tests (basically looking for magic file names) and that it can tell you if you forgot to end a rebase or a merge, which can happen if you have been disturbed in the middle of it by a colleague for example.

I liked the '*' idea from Martin to show if the tree is dirty. Sadly it's not an option. Martin, to do that, you can do:

 unclean=
 git diff-files --quiet && git diff-index --cached --quiet HEAD -- || unclean='*'

But this is a very expensive operation. On the glibc git repository, it takes seconds with cold cache (and it's not very surprising because it basically has to stat(3) a lot of stuff). And not having a shell for seconds is a bit extreme.

PS: I know my prompt only supports git, but:

  1. I barely care about other VCSes as I only use git and sometimes svn for packaging ;
  2. when I have to use svn it's for cheap stuff where I don't really need the prompt help.
Sunday 6 April 2008

[RC-Bug-A-Day] Day 19

Today is again about removing packages from testing as my hintfile says. We've discussed (in the RM team) policy a bit, and it seems that we agree that packages with Release Critical bugs open for more than 3 weeks without any kind of activity from the Maintainer warrant a removal from testing without prior notification. Tonight's work is then just doing the quite not fascinating work of going through this list and look for removal candidates.

Note that we will always give more time to Maintainers that need it to fix a bug, if he/she states so in the bug report. Needing time is perfectly okay. Not telling about it isn't.

[RC-Bug-A-Day] Day 18

Paid work burnt all my free time recenlty, that's why there wasn't a rc-bug-a-day for two days. I'm back with two removals, a couple of gcc-4.3 FTBFSes fixed. And 5 uploads for RG bugs from Sandro Tosi that were rotting in my mail client.

The bad news for tonight is that gcc-4.3 FTBFSes are now RC, since it's the default compiler on several architectures. That's almost 40 new RC we now have to deal with. The fun part will be that those RC will probably hinder some transitions to testing. Maintainers, please, fix your packages. There are still too many packages with RG bugs on them, open for many days, from maintainer that are otherwise quite active on IRC or the lists…

Thursday 3 April 2008

[RC-Bug-A-Day] Day 17

Today's RC bug was 470462, removal of a package that as a patch for a FTBFS and absolutely no maintainer answers (#417047).

I'm also quite excited because I have a mail with 9 nmudiff's for RG/RC bugs waiting to be processed from Sandro Tosi. I want MOAR !

Tuesday 1 April 2008

[RC-Bug-A-Day] Day 16

There was no RC-Bug-A-Day yesterday, so two RC bugs for today:

  • #463094 some missing ${subst:Stuff} in a debian/control;
  • #456864 some other missing Build-Dependency causing a FTBFS.

I also plan to sponsor the requests piling in my @debian.org mailbox tonight too.

Sunday 30 March 2008

[RC-Bug-A-Day] Day 15

For today, a debian/copyright bug in tct was fixed.

Saturday 29 March 2008

[RC-Bug-A-Day] Day 14

I sponsored (ugh!) a new ia32-libs today, which means we now are 4 RC down.

Note: I really hate this package.

Friday 28 March 2008

[RC-Bug-A-Day] Day 13

For today: 469552 was downgraded for probably be a user problem and ktranslator was removed due to 469552. I know that the latter wasn't RC for very long (a couple of days at least) but the maintainer should have detect the criticity of the problem himself (the package is mostly unusable because he can't find some of its plugins or sth like that) and is totally unresponsive.

I'm pleased to announce that we went under the 400 bugs in lenny (according to turmzimmer) and around 250 bugs that are present in both lenny and sid (which is the "real" amount of bugs to fix).

[RC-Bug-A-Day] Day 12

Today's paid work ate all my time, so my RC/RG bug squashing was only made of uploading other's work.

Thanks again to Kartik and Kumar.

Thursday 27 March 2008

[RC-Bug-A-Day] Day 11

Today saw the removal (from testing) of:

  • syslog-ng that has a really grave bug (loss of logs when the daemon is signaled with a SIGHUP) that is fixed-upstream for quite a while;
  • w3c-libwww that the maintainer would like to get rid of, that had two RC. Sadly, I had to remove wmweather+ (its sole r-dep in lenny) that the maintainer still hasn't fixed, but it should be temporary.

All in all, that's 5 RC bugs that aren't in lenny anymore.

Note: I've been pretty busy today, I've seen mails to ask NMU sponsoring for RC/RG bugs, I will have a look, don't worry.

Tuesday 25 March 2008

[RC-Bug-A-Day] Day 10

For today, 464893 was downgraded partly because gksu works fine for me for a long time, hence critical was completely overestimated, and partly because no matter how hard I try to reproduce the bug I can't. If you do, please follow up on the bug log.

Also, a new sponsored NMU for gnomesword (bug#461959), thanks to Kumar again :)

Monday 24 March 2008

[RC-Bug-A-Day] Day 9

Today's work:

  • I sponsored one more NMU from Kumar Appaiah for 454829.
  • I also closed 458659 that wasn't reproducible, hence probably fixed in 5.7012-4 or 5.7012-5.