Summary: | bzr.eclass might need to use bzr pull’s --overwrite-tags flag | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | James Cloos <cloos> |
Component: | Eclasses | Assignee: | Ulrich Müller <ulm> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | poletti.marco |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.launchpad.net/bzr/+bug/681792 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 487216, 646764 | ||
Bug Blocks: |
Description
James Cloos
2012-12-08 01:49:57 UTC
Yes, the tag for mh-e-8.4. Upstream shouldn't do such things, in the first place. (And I thought bzr push would refuse it, unless used with --force.) I'd suggest though that we don't use --overwrite but wait for the more specific --overwrite-tags that will hopefully appear in bzr-2.6: <https://bugs.launchpad.net/bzr/+bug/681792> As a workaround, you can simply delete the conflicting tag in the local repo: bzr tag --delete mh-e-8.4 > I'd suggest though that we don't use --overwrite but wait for the more specific > --overwrite-tags that will hopefully appear in bzr-2.6
Ah. I didn’t know about that one; sounds like a plan.
Emacs team is out of here. only to live ebuilds in the tree still need this eclass I have taken maintainership of the eclass. Great, thanks a lot! :) The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0b249d7175ae71e188e02ea60a90e9a932e2fda3 commit 0b249d7175ae71e188e02ea60a90e9a932e2fda3 Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2018-02-06 13:53:17 +0000 Commit: Ulrich Müller <ulm@gentoo.org> CommitDate: 2018-02-10 21:50:59 +0000 bzr.eclass: Add --overwrite-tags option to pull command. Closes: https://bugs.gentoo.org/446422 eclass/bzr.eclass | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) |