Hi,

I noticed that the gitlab integration on code.dlang.org is broken. I think it is like this for several months. Should I mirror my projects on github to publish packages on code.dlang.org or there are plans to fix this issue?

Bogdan

```
 Branch ~master: Unexpected reply for 'https://gitlab.com/api/v4/projects/szabobogdan3%2Fdescribe-d/repository/files/%2Fdub.json/raw?ref=1db90dc9a624f4b43e0eb15cb2ad163cd2c61bb3&private_token=***': Bad Request
Version 0.5.0: Unexpected reply for 'https://gitlab.com/api/v4/projects/szabobogdan3%2Fdescribe-d/repository/files/%2Fdub.json/raw?ref=1db90dc9a624f4b43e0eb15cb2ad163cd2c61bb3&private_token=***': Bad Request
Version 0.4.0: Unexpected reply for 'https://gitlab.com/api/v4/projects/szabobogdan3%2Fdescribe-d/repository/files/%2Fdub.json/raw?ref=43ce5f5662c9f1c862d6c9c486602c97b79e87a1&private_token=***': Bad Request
Version 0.3.0: Unexpected reply for 'https://gitlab.com/api/v4/projects/szabobogdan3%2Fdescribe-d/repository/files/%2Fdub.json/raw?ref=eb7d7ca0d2637d0da67b470870c57a87370629b6&private_token=***': Bad Request
Version 0.2.0: Unexpected reply for 'https://gitlab.com/api/v4/projects/szabobogdan3%2Fdescribe-d/repository/files/%2Fdub.json/raw?ref=f21a746b9376fda747588ed5d94778b77df7a12d&private_token=***': Bad Request
Version 0.1.0: Unexpected reply for 'https://gitlab.com/api/v4/projects/szabobogdan3%2Fdescribe-d/repository/files/%2Fdub.json/raw?ref=511826391d093e06084f0e86a8d75ca1da2d7368&private_token=***': Bad Request
```

On Saturday, 10 October 2020 at 12:34:15 UTC, bogdan wrote:
> Hi,
>
> I noticed that the gitlab integration on code.dlang.org is broken. I think it is like this for several months. Should I mirror my projects on github to publish packages on code.dlang.org or there are plans to fix this issue?
>
> Bogdan

It's been broken for at least half a year.  Here's the upstream root cause:
https://gitlab.com/gitlab-org/gitlab/-/issues/212216

It seems to be a side effect of Gitlab consolidating and tightening up path validation (i.e., blocking absolute paths), so I don't expect the old behaviour to come back.

Here's the dub-registry bug report:
https://github.com/dlang/dub-registry/issues/471

Stuff like this makes me less enthusiastic about writing/testing a fix and managing a PR, though:
https://github.com/dlang/dub-registry/issues/472

What's the status of dub-registry maintenance?  Is the D Foundation backing it?