What to do when a packaging branch is out of date

[Andreas Hasenack]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

- -- 
Andreas Hasenack
andreas at canonical.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9ojIsACgkQeEJZs/PdwpDzAgCgpvRePROgSwZjqwS5uWiuYCzN
WScAoPLT/aVcibCEUHEVwHE8p8o1WSGg
=VzJk
-----END PGP SIGNATURE-----