What to do when a packaging branch is out of date

[Scott Kitterman]

On Tuesday, March 20, 2012 10:56:27 AM Andreas Hasenack wrote:
> So apparently a package update can be prepared using udd, released
> into the archive, and the packaging branch still be out of date:
> 
> """
> $ bzr branch
> ubuntu:landscape-client landscape-client-12.04-0ubuntu1
> Most recent Ubuntu version: 12.04-0ubuntu1
> 
> 
> Packaging branch version: 11.07.1.1-0ubuntu2
> Packaging branch status: OUT-OF-DATE
> Branched 40 revisions.
> $
> """
> 
> It's like it was released before being committed.
> 
> What should I do if I want to prepare another fix? Wait? Ping someone
> to commit and then branch again? Do it with debdiffs and not worry
> about branches anymore?
> 
> I emailed ubuntu-devel-discuss and someone told me that somebody has
> to manually commit to the udd branch, and that this is normal.

It's normal for there to be some delay.  It will (normally) be automatically 
updated from what was uploaded.  The only way there isn't some delay is if 
someone manually commits the branch.

I'm not sure how much delay is considered normal these days.

Scott K