Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

freedesktop zeal.desktop file is broken in the release archive #1610

Open
craftyguy opened this issue Apr 2, 2024 · 1 comment
Open

freedesktop zeal.desktop file is broken in the release archive #1610

craftyguy opened this issue Apr 2, 2024 · 1 comment

Comments

@craftyguy
Copy link

The assets/freedesktop/org.zealdocs.zeal.desktop file has incorrect line endings in the release source archive hosted here on github. The file uses CR in the git repo, but it uses CRLF in the release source archive. Applications on e.g., Linux that follow the fd.o Desktop Entry Spec are unable to use it.

The release tag source archive (e.g. v0.7.0.zip and the git repo have correct line endings for zeal.desktop:

$ file assets/freedesktop/org.zealdocs.zeal.desktop: ASCII text

However the release source archive (e.g. zeal-0.7.0.tar.gz) has incorrect CRLF line endings:

$ file
assets/freedesktop/org.zealdocs.zeal.desktop: ASCII text, with CRLF line terminators

From what I can tell, the release source archives are created in a Windows environment, in the same job that created the Windows builds for your app:

run: cmake --build build --preset ${{ matrix.config.buildPreset }} --target package_source
and
build/${{ matrix.config.configurePreset }}/zeal-${{ env.ZEAL_VERSION }}.*

My guess is that the Windows env / build process is enough to change this file's line endings.

As a workaround, Linux distros and others can use the git tag source archives.

@trollixx
Copy link
Member

trollixx commented Apr 3, 2024

Very odd. That's a static file which is not generated, so Windows or not should not matter. I'll investigate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants