Don Armstrong wrote:
> http://bugs.debian.org/debbugs-source/debbugs and mainline.
Thanks. I assume this should be
http://bugs.debian.org/debbugs-source/debian
and that I should fetch with bzr.
Also thanks for the other explanations. I’ll look at this some
more tomorrow.
Regards,
Jonathan
On Wed, 14 Apr 2010, Jonathan Nieder wrote:
> Don Armstrong wrote:
> > If the bug is merged, unmerge it, and use one of the existing bugs.
>
> Maybe the message can make that more clear. For example, what did you
> think of this suggestion?
>
> -Bug is marked as being merged with others. Use an
Don Armstrong wrote:
> If the bug is merged, unmerge it, and use one of the existing bugs.
Maybe the message can make that more clear. For example, what did you
think of this suggestion?
-Bug is marked as being merged with others. Use an existing clone.
+Bug is marked as being merged with oth
forcemerge 577487 57729
thanks
On Tue, 13 Apr 2010, Jonathan Nieder wrote:
> Huh? Does that mean I have to unmerge before cloning? Once I
> understand this, I’ll be happy to file a separate bug for it.
If the bug is merged, unmerge it, and use one of the existing bugs.
> | > retitle -1 conflict
Jonathan Nieder wrote:
> | > clone 577650 -1
> | Bug#577650: libcupt-perl: Does not handle automatic upgrade of git packages
> | Bug is marked as being merged with others. Use an existing clone.
>
> Huh? Does that mean I have to unmerge before cloning? Once I understand
> this, I’ll be happy to
Package: bugs.debian.org
Severity: wishlist
I think these error messages can be improved:
| Processing commands for cont...@bugs.debian.org:
|
| > clone 577650 -1
| Bug#577650: libcupt-perl: Does not handle automatic upgrade of git packages
| Bug is marked as being merged with others. Use an exi
6 matches
Mail list logo
