And thought I had already this revision as updated very recently (few minutes before I saw this bug and report it).
So I thought it still had a parsing problem (even with this commit done so) but no!
I checked and... I have the r237(!):
=> "Preparing to replace birdie 0.2+r231-0+pkg7~precise1 (using .../birdie_0.2+r237-0+pkg7~precise1_amd64.deb) ..."
And the commit that seems to resolve that is the r238! :^)
So, visibly, the (auto-)build is not done yet for this revision. Just need to wait then. :-)
Ahah, I saw recently this commit by browsing the new stuff done: bazaar. launchpad. net/~birdie- team/birdie/ trunk/revision/ 238?start_ revid=239
http://
And thought I had already this revision as updated very recently (few minutes before I saw this bug and report it).
So I thought it still had a parsing problem (even with this commit done so) but no!
I checked and... I have the r237(!): 0+pkg7~ precise1 (using .../birdie_ 0.2+r237- 0+pkg7~ precise1_ amd64.deb) ..."
=> "Preparing to replace birdie 0.2+r231-
And the commit that seems to resolve that is the r238! :^)
So, visibly, the (auto-)build is not done yet for this revision. Just need to wait then. :-)