Codeberg imports release metadata from GitHub, but release downloads contain text URLs only #2077

leaf-node commented 2025年08月12日 03:50:45 +02:00

Comment

On my releases page, if I click to download any of the .deb or .tar.gz releases imported from GitHub, the file is not downloaded, but a text file is downloaded containing a link to the release on GitHub. I'm cool with old releases being hosted on GitHub, but getting a ~1KB text file that has to be copied and pasted as a URL doesn't seem correct. New releases via Codeberg CI appear to work just fine.

I tried a new migration from the same GitHub repo to Codeberg, and the issue persisted.

I also tried migrating to https://v13.next.forgejo.org/, and it worked properly. I don't know if that is due to an improvement in the front end or back end, but upgrading Codeberg to Forejo v13 will hopefully solve the issue.

### Comment On my [releases page](https://codeberg.org/leaf-node/open_alert_viewer/releases), if I click to download any of the .deb or .tar.gz releases imported from GitHub, the file is not downloaded, but a text file is downloaded containing a link to the release on GitHub. I'm cool with old releases being hosted on GitHub, but getting a ~1KB text file that has to be copied and pasted as a URL doesn't seem correct. New releases via Codeberg CI appear to work just fine. I tried a new migration from the same GitHub repo to Codeberg, and the issue persisted. I also tried migrating to <https://v13.next.forgejo.org/>, and it worked properly. I don't know if that is due to an improvement in the front end or back end, but upgrading Codeberg to Forejo v13 will hopefully solve the issue.

Gusted commented 2025年08月12日 03:52:17 +02:00

Hi, this was already fixed but we hadn't yet time to deploy the fix on Codeberg.

Hi, this [was already fixed](https://codeberg.org/forgejo/forgejo/pulls/8771) but we hadn't yet time to deploy the fix on Codeberg.

Gusted commented 2025年08月12日 05:23:31 +02:00

Hi please try migrating again, the fix should be deployed now.

Hi please try migrating again, the fix should be deployed now.

leaf-node commented 2025年08月13日 22:33:47 +02:00

Thanks for the update!

Unfortunately the links on my releases page are still text:

https://codeberg.org/leaf-node/open_alert_viewer/releases

For instance: https://codeberg.org/leaf-node/open_alert_viewer/releases/download/v1.3.2/open-alert-viewer-x86_64_1.3.2-1ubuntu-noble.deb

Thanks for the update! Unfortunately the links on my releases page are still text: https://codeberg.org/leaf-node/open_alert_viewer/releases For instance: <https://codeberg.org/leaf-node/open_alert_viewer/releases/download/v1.3.2/open-alert-viewer-x86_64_1.3.2-1ubuntu-noble.deb>

Gusted commented 2025年08月13日 22:35:06 +02:00

It only works if you use the migration tool again.

It only works if you use the migration tool again.

leaf-node commented 2025年08月13日 22:49:47 +02:00

Is it possible to migrate only the releases from GitHub to my existing Codeberg repo without overwriting other data? I'm wondering about preserving issues updated and added on Codeberg.

Is it possible to migrate only the releases from GitHub to my existing Codeberg repo without overwriting other data? I'm wondering about preserving issues updated and added on Codeberg.

leaf-node commented 2025年08月13日 22:57:49 +02:00

I tried on a test repo, and I get a "The repository name is already used." error.

I tried on a test repo, and I get a "The repository name is already used." error.

Gusted commented 2025年08月14日 09:56:59 +02:00

@leaf-node wrote in #2077 (comment):

Is it possible to migrate only the releases from GitHub to my existing Codeberg repo without overwriting other data? I'm wondering about preserving issues updated and added on Codeberg.

No. But I could look into doing some database shenanigans to fix the release asset links, but it would require a new repository with "good" releases.

@leaf-node wrote in #2077 (comment):

I tried on a test repo, and I get a "The repository name is already used." error.

You will need to change the repository name in the migration form (it's automatically filled out once you paste the the repository URL).

@leaf-node wrote in https://codeberg.org/Codeberg/Community/issues/2077#issuecomment-6342721: > Is it possible to migrate only the releases from GitHub to my existing Codeberg repo without overwriting other data? I'm wondering about preserving issues updated and added on Codeberg. No. But I could look into doing some database shenanigans to fix the release asset links, but it would require a new repository with "good" releases. @leaf-node wrote in https://codeberg.org/Codeberg/Community/issues/2077#issuecomment-6347746: > I tried on a test repo, and I get a "The repository name is already used." error. You will need to change the repository name in the migration form (it's automatically filled out once you paste the the repository URL).

leaf-node commented 2025年08月14日 21:33:09 +02:00

@Gusted wrote in #2077 (comment):

Is it possible to migrate only the releases from GitHub to my existing Codeberg repo without overwriting other data? I'm wondering about preserving issues updated and added on Codeberg.

No. But I could look into doing some database shenanigans to fix the release asset links, but it would require a new repository with "good" releases.

Hey, thanks for helping with this issue 😄 I created a temporary repo with correct releases: https://codeberg.org/leaf-node/import-tmp/releases and the one I'm hoping you could move the releases to is https://codeberg.org/leaf-node/open_alert_viewer.

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2077#issuecomment-6372235: > > Is it possible to migrate only the releases from GitHub to my existing Codeberg repo without overwriting other data? I'm wondering about preserving issues updated and added on Codeberg. > > No. But I could look into doing some database shenanigans to fix the release asset links, but it would require a new repository with "good" releases. Hey, thanks for helping with this issue 😄 I created a temporary repo with correct releases: <https://codeberg.org/leaf-node/import-tmp/releases> and the one I'm hoping you could move the releases to is <https://codeberg.org/leaf-node/open_alert_viewer>.

Gusted commented 2025年08月15日 09:20:30 +02:00

Hi, they should point to the correct link now.

Hi, they should point to the correct link now.

leaf-node commented 2025年08月15日 14:46:56 +02:00

Awesome, thanks so much! 😀

Awesome, thanks so much! 😀