bzr branches for ubuntu packages are not reliably updated (ex. aria2)

At least medium, maybe higher?

Its kind of a symptom of it being historically just-james; I think
there are a bunch of low hanging education things we can do to know
more about it that will help. And I agree on the priority - I'd put it
at High actually.

Well, that depends on how you are treating the bug.

  "aria2 is not up to date" - that's something we can fix and has a
  priority that depends on how important updating that package is,
  clearly important as Matt filed a bug because he couldn't make use of
  the branches.

  "packages aren't always up to date" - that's like filing a bug saying
  "this software has bugs", we can fix it, but it doesn't help in
  pointing to the things that need fixing.

If your point is that we need to put more effort in to fixing the
failures that we have, and fixing them quicker as they pop up then I
would agree. I'll point again to the current list of failures:

  http://package-import.ubuntu.com/status/

and the page that starts to explain how to reproduce locally for
debugging:

  https://wiki.ubuntu.com/DistributedDev...

My main motivation for reporting the bug was to draw attention to the
package branch system not working properly. aria2 was the package
where I noticed the issue but I'm not bothered specifically about that
package.

The issue means bzr branch lp... is less reliable than apt-get source
as a means of getting the latest source, which is a shame.

--
Matt Wheeler
<email address hidden>

On Wed, Jun 2, 2010 at 6:28 AM, James Westby <email address hidden> wrote:
> Well, that depends on how you are treating the bug.
>
>  "packages aren't always up to date" - that's like filing a bug saying
>  "this software has bugs", we can fix it, but it doesn't help in
>  pointing to the things that need fixing.

I don't think that analogy is all that useful to thinking about the
problem. I'd rather think about it like uptime in a web service: we
can tell when its down, and we should react by bringing it up, and
resourcing the ops staff appropriately to be able to respond; and
resourcing the dev team appropriately to be able to fix
root-cause-is-a-bug issues.

The aria2 import has been fixed. The broader issue of "imports sometimes fail" is addressed in part in various more specific bugs, but to fix it entirely would entail fixing all possible bugs in Bazaar that could affect the importer, and making the importer capable of dealing with any possible manual commits inserted in a package branch. As such, I don't see it as something that can ever be quantified as done, so it probably isn't worth keeping a bug open to track an untrackable goal.