[flang-dev] [cfe-dev] Bugzilla migration is stopped again
Nemanja Ivanovic via flang-dev
flang-dev at lists.llvm.org
Fri Dec 3 16:53:59 PST 2021
This may be a dumb question, but could this just be an issue of forward
references (i.e. issue A references B, but B has not been transferred yet
so doesn't exist)?
If so, could the transfer be split into a two step process:
1. Open all issues with summaries only
2. Populate description, comments, labels, etc.
Please note that I have no idea how any of this GitHub or Bugzilla stuff
works, so this suggestion may be completely absurd.
On Fri, Dec 3, 2021 at 7:19 PM Anton Korobeynikov via cfe-dev <
cfe-dev at lists.llvm.org> wrote:
> Dear All,
> I hate to say this, but the migration was stopped again. Now it seems
> that GitHub does not rewrite issue references properly during the
> transfer (sick!). Let me show what the problem is exactly:
> Consider two issues: A and B, where A will reference B and B will
> reference A. In our case this is used to model various relations like
> "duplicates / is duplicated by", "blocks / is blocked by", "depends on
> / required by". So, in bz archive A will reference B as #B and B
> will reference #A.
> Now, let's migrate A. The references will be rewritten. #B =>
> bz-archive#B and #A => llvm-project#A. However, after migration of B
> only one reference is rewritten llvm-project#A => #A, the bz-archive#B
> link in the issue A will not be rewritten and therefore a dangling
> reference will appear.
> For us this means that we will lose all links to duplicate issues, and
> (more important!) to linked issues in the meta bugs.
> I informed GitHub about the bug and I am waiting for their answer.
> With best regards, Anton Korobeynikov,
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the flang-dev