[flang-dev] [cfe-dev] Bugzilla migration is stopped again
Christian Kühnel via flang-dev
flang-dev at lists.llvm.org
Wed Dec 8 00:30:35 PST 2021
Anton, thank you so much for driving the migration and all the effort you
We discussed the current situation and the options in the Infrastructure
Working Group meeting yesterday . Our proposal is to give GitHub another
48 hours (i.e. Thursday EOB) to resolve the issue regarding missing links
in circular dependencies.
If it can't be resolved by that time, we propose to move forward with the
migration anyway. The data is there, we're only missing the links. From our
perspective this is something we can live with.
Christian on behalf of the Infrastructure Working Group
On Sat, Dec 4, 2021 at 1:19 AM 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