Allow linking a package upload to a bzr revision

Bug #395200 reported by James Westby
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Hi,

It would be great if a package upload could be linked to a bzr revision, here's
why.

I commit a candidate fix for a bug in my branch, and push it up under my name. It is
then linked to the bug report (with revision information please) so that users can
grab a branch that fixes it, and see the change.

As installing from a branch is often a pain, I also push to one of my PPAs. If that ould
be linked to the revision, then it would be possible for the bug page to say something
like:

   revision 2145 of lp:~james-w/.... attempts to fix this bug.
   This fix is also available in the following PPAs:
       ~james-w/....

(Revision ancestry checks would be great, and pointing to Ubuntu archives as well)

Populating the link isn't something that would be easy to do right now, but we can work
on that. Having somewhere in LP to do it would be good though, as we can do it for
official package branches already.

With the changes to bug-branch linking that are being discussed this could get even
cooler, but I think including packages in this is something that we can be working on.

We currently do package->bug linking with "LP: #<number>" in the changelog, but
that only works for official packages currrently. Making that become a package<->bug
link for PPAs may in fact become a better way to solve that, but having the package<->
revision links would be useful elsewhere.

Thanks,

James

Tags: lp-code
Revision history for this message
Diogo Matsubara (matsubara) wrote :

Hi James,

this looks very similar to bug 246166. Is it a dupe or am I mistaken?
In any case, see also bug 374931 and bug 179873 which would also cover the "This fix is also available in the following PPAs" in your suggestion.

affects: launchpad → launchpad-code
Changed in launchpad-code:
status: New → Incomplete
Revision history for this message
James Westby (james-w) wrote :

Hi,

This is different to bug 246166. My description drifted a little off topic,
but the aim of this bug is different.

I think it would be useful to say "This upload in this PPA corresponds to
this revision id". Then there are some interesting things you can do in
the UI with this information.

Thanks,

James

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

What about having e.g. bzr builddeb producing a .changes file with :

XC-Revision-Id: <email address hidden>

in it?

That should make it possible to match up revision and upload.

Revision history for this message
James Westby (james-w) wrote : Re: [Bug 395200] Re: Allow linking a package upload to a bzr revision

On Fri, 20 Aug 2010 16:24:32 -0000, Jelmer Vernooij <email address hidden> wrote:
> What about having e.g. bzr builddeb producing a .changes file with :
>
> XC-Revision-Id: <email address hidden>
>
> in it?
>
> That should make it possible to match up revision and upload.

That would be fairly straightforward.

Also see

  http://lists.debian.org/debian-dpkg/2010/02/msg00061.html

for an idea that would encode this an more in the .dsc. It was blocked on
a rather trivial detail though unfortunately.

Thanks,

James

Revision history for this message
Robert Collins (lifeless) wrote :

What was the blocking detail?

Revision history for this message
James Westby (james-w) wrote :

It was in the referenced thread:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566230

Thanks,

James

Changed in launchpad:
status: Incomplete → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.