Skip to content

Set TM_DATA_DIR in release.yml#351

Merged
veluca93 merged 1 commit into
masterfrom
veluca93-patch-1
Sep 6, 2025
Merged

Set TM_DATA_DIR in release.yml#351
veluca93 merged 1 commit into
masterfrom
veluca93-patch-1

Conversation

@veluca93

@veluca93 veluca93 commented Sep 6, 2025

Copy link
Copy Markdown
Collaborator

No description provided.

@edomora97 edomora97 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Top!

Can you also attach the generated .deb files to the release on Github? We used to, and that's would be useful for automations and for keeping track of the debs of past versions.

@veluca93

veluca93 commented Sep 6, 2025

Copy link
Copy Markdown
Collaborator Author

Top!

Can you also attach the generated .deb files to the release on Github? We used to, and that's would be useful for automations and for keeping track of the debs of past versions.

Sure. While I was at it, i also got rid of double zipping on the artifacts uploaded to each workflow run.

@veluca93 veluca93 merged commit 817cc8f into master Sep 6, 2025
7 of 14 checks passed
with:
name: tmr-debs-${{ env.ARTIFACT_SUFFIX }}
path: tmr-debs-${{ env.ARTIFACT_SUFFIX }}.tar.gz
path: "target/debian/*.deb"

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do those files have unique names? I see above that they are for some reason compressed into a tar.gz, but why so?

I'd rename the deb into something with ARTIFACT_SUFFIX, avoid compressing them, and upload the renamed .deb file. What do you think, @veluca93?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no reason for them to be compressed in a tar.gz, upload-artifact already creates a zip file (this is some gh action code I copied from libjxl). I also believe it's hard to upload non-zipped artefacts to CI outcomes, but I am not super sure.

However, I see that the name collisions is causing issues for releases... I will check how to rename the debian files.

@Virv12 Virv12 deleted the veluca93-patch-1 branch September 27, 2025 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants