Migration from github to codeberg: items needing attention #65

gojimmypi commented 2026年03月08日 18:44:29 +01:00

Outstanding issues, blackmagic-debug organization-wide

See these 404 links in:

1. hacking/target-cortex-a.md:

These bits may need to change for devices other than Zynq-7000:

Cache line length: https://github.com/blackmagic-debug/blackmagic/blob/main/src/target/cortexa.c#L77
Reset implementation: https://github.com/blackmagic-debug/blackmagic/blob/main/src/target/cortexa.c#L555

2. This one (I suspect they was a target file rename, but I didn't chase it as the updated file & line was not immediately obvious.) in hacking/target-drivers.md:

• The generic logic for Cortex-A parts which is found in
  target/cortexa.c.

3. What to do with GitHub sponsor links?
   A: see Discord, leaving it for now.

4. Move Wki file contents (e.g. pdf links). See blackmagic-debug/blackmagic#2202
   A: Wiki Is retired. Files should be moved to assets.

5. API Links such as this one:
   https://api.github.com/repos/blackmagic-debug/blackmagic/releases

6. githubusercontent links, such as this one:
   https://raw.githubusercontent.com/blackmagic-debug/bmputil/refs/heads/main/src/metadata/metadata.schema.json

Wonkiness (Codeberg bug? A: no, see comment below)

Note the double src added to this after multiple trial-and-error attempts to simplify (see discord discussion):

https://codeberg.org/blackmagic-debug/blackmagic/src/src/platforms/hydrabus/README.md

The default URL when browsing to the same file is instead:

https://codeberg.org/blackmagic-debug/blackmagic/src/branch/main/src/platforms/hydrabus/README.md

Note that this, although the sytax has worked elsewhere, did NOT work for this link using just one src:

https://codeberg.org/blackmagic-debug/blackmagic/src/platforms/hydrabus/README.md

Progress Check

I have all the BM repos in my local codeberg directory and at that root, contains this check_migration.sh file:

#!/bin/bash
grep -Rni "github" . \
 --exclude-dir=".git" \
 --exclude-dir=".vs" \
 --exclude="Cargo.lock" \
| grep -Ev "github.com/sponsors/esden|github.com/sponsors/dragonmux" \
| grep -E "blackmagic-debug|raw\.githubusercontent"

Find all instances of "github", except for some directories and files; then from that result set show only the ones that contain the text "blackmagic-debug" or "raw.githubusercontent" .

This one may also be helpful to check codeberg links that still related to github:

grep -Rni "codeberg" . \
 --exclude-dir=".git" \
 --exclude-dir=".vs" \
 --exclude="Cargo.lock" \
| grep -E "github"

## Outstanding issues, `blackmagic-debug` organization-wide See these 404 links in: 1) [hacking/target-cortex-a.md](https://codeberg.org/blackmagic-debug/pages/src/commit/0c182ad7f8c7a066c2477a59496ffb74f4440516/hacking/target-cortex-a.md): > These bits may need to change for devices other than Zynq-7000: > Cache line length: https://github.com/blackmagic-debug/blackmagic/blob/main/src/target/cortexa.c#L77 > Reset implementation: https://github.com/blackmagic-debug/blackmagic/blob/main/src/target/cortexa.c#L555 2) This one (I suspect they was a target file rename, but I didn't chase it as the updated file & line was not immediately obvious.) in [hacking/target-drivers.md](https://codeberg.org/blackmagic-debug/pages/src/commit/0c182ad7f8c7a066c2477a59496ffb74f4440516/hacking/target-drivers.md): > * The generic logic for Cortex-A parts which is found in > [`target/cortexa.c`](https://github.com/blackmagic-debug/blackmagic/blob/main/src/target/cortexa.c). 3) What to do with GitHub sponsor links? A: see Discord, leaving it for now. 4) Move Wki file contents (e.g. pdf links). See https://codeberg.org/blackmagic-debug/blackmagic/issues/2202 A: Wiki Is retired. Files should be moved to assets. 5) API Links such as [this one](https://codeberg.org/blackmagic-debug/summon-blackmagic/src/commit/5bad1dad2a5f59e07f2f03e77ee365db0226960e/summon/github.py#L39): ```https://api.github.com/repos/blackmagic-debug/blackmagic/releases``` 6) githubusercontent links, such as [this one](https://codeberg.org/blackmagic-debug/summon-blackmagic/src/commit/5bad1dad2a5f59e07f2f03e77ee365db0226960e/summon/__init__.py#L49): ```https://raw.githubusercontent.com/blackmagic-debug/bmputil/refs/heads/main/src/metadata/metadata.schema.json``` ## Wonkiness (Codeberg bug? A: no, see comment below) Note the double `src` added to this after multiple trial-and-error attempts to simplify (see discord discussion): https://codeberg.org/blackmagic-debug/blackmagic/src/src/platforms/hydrabus/README.md The default URL when browsing to the same file is instead: https://codeberg.org/blackmagic-debug/blackmagic/src/branch/main/src/platforms/hydrabus/README.md Note that this, although the sytax has worked elsewhere, did NOT work for this link using just one `src`: https://codeberg.org/blackmagic-debug/blackmagic/src/platforms/hydrabus/README.md ## Progress Check I have all the BM repos in my local `codeberg` directory and at that root, contains this `check_migration.sh` file: ``` #!/bin/bash grep -Rni "github" . \ --exclude-dir=".git" \ --exclude-dir=".vs" \ --exclude="Cargo.lock" \ | grep -Ev "github.com/sponsors/esden|github.com/sponsors/dragonmux" \ | grep -E "blackmagic-debug|raw\.githubusercontent" ``` Find all instances of "github", except for some directories and files; then from that result set show only the ones that contain the text "blackmagic-debug" or "raw.githubusercontent" . This one may also be helpful to check codeberg links that still related to github: ``` grep -Rni "codeberg" . \ --exclude-dir=".git" \ --exclude-dir=".vs" \ --exclude="Cargo.lock" \ | grep -E "github" ```

dragonmux commented 2026年03月08日 18:50:08 +01:00

That would be https://codeberg.org/blackmagic-debug/blackmagic/src/branch/main/src/target/cortexar.c for cortexa.c - the line numbers will need revising, but this is the rename (actually merge-together of cortexa.c and cortexr.c) that happened.

That would be https://codeberg.org/blackmagic-debug/blackmagic/src/branch/main/src/target/cortexar.c for cortexa.c - the line numbers will need revising, but this is the rename (actually merge-together of cortexa.c and cortexr.c) that happened.

dragonmux commented 2026年03月09日 18:13:58 +01:00

For 6. you can replace that with usage of the raw link from Codeberg - https://codeberg.org/blackmagic-debug/bmputil/raw/branch/main/src/metadata/metadata.schema.json - as that's the purpose of that link in the first place.

For 6. you can replace that with usage of the raw link from Codeberg - https://codeberg.org/blackmagic-debug/bmputil/raw/branch/main/src/metadata/metadata.schema.json - as that's the purpose of that link in the first place.

dragonmux commented 2026年03月09日 18:17:22 +01:00

Looks like for 5 we want to be poking the Forgejo API help: https://codeberg.org/api/swagger#/repository/repoListReleases for example mapping to the https://api.github.com/repos/blackmagic-debug/blackmagic/releases request endpoint from GitHub. Working through parsing the responses properly though and extracting the information needed will be its own headache - one we'll embark on with summon over the next couple of days as this is kind of a pain to test works properly without a lot of setup on your local machine.

Looks like for 5 we want to be poking the Forgejo API help: https://codeberg.org/api/swagger#/repository/repoListReleases for example mapping to the `https://api.github.com/repos/blackmagic-debug/blackmagic/releases` request endpoint from GitHub. Working through parsing the responses properly though and extracting the information needed will be its own headache - one we'll embark on with summon over the next couple of days as this is kind of a pain to test works properly without a lot of setup on your local machine.

dragonmux commented 2026年03月09日 18:20:00 +01:00

For completeness sake, the badges that replace ones like the GitHub current release one, and the stargazers one, are documented at https://forgejo.org/docs/next/user/readme-badges/ - the SVGs it lists generate the actual badges and redirect to the generated badge.

For completeness sake, the badges that replace ones like the GitHub current release one, and the stargazers one, are documented at https://forgejo.org/docs/next/user/readme-badges/ - the SVGs it lists generate the actual badges and redirect to the generated badge.

dragonmux commented 2026年03月09日 22:58:47 +01:00

Just realised what's going on with the /src/src/ thing - and it's not a bug.. it's working exactly as intended: the first src is the command path in Forgejo telling it we're interested in stuff from the source tree; the second src is the directory in the repository itself.

Just realised what's going on with the `/src/src/` thing - and it's not a bug.. it's working exactly as intended: the first `src` is the command path in Forgejo telling it we're interested in stuff from the source tree; the second `src` is the directory in the repository itself.

whitequark commented 2026年04月14日 07:53:22 +02:00

Codeberg has now deployed git-pages for custom domains like black-magic.org, so you can move that over to git-pages as well.

Codeberg has now deployed git-pages for custom domains like black-magic.org, so you can move that over to git-pages as well.