-
-
Notifications
You must be signed in to change notification settings - Fork 560
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
incorrectly parsed DESKTOP_COMMENT
leads to YAML syntax error front matter
#3438
Comments
Just to confirm, I ran # cat squashfs-root/Cryptomator.desktop
[Desktop Entry]
Name=Cryptomator
Comment=Cloud Storage Encryption Utility
Exec=cryptomator %F
Icon=org.cryptomator.Cryptomator
Terminal=false
Type=Application
Categories=Utility;Security;FileTools;
StartupNotify=true
StartupWMClass=org.cryptomator.launcher.Cryptomator$MainApp
MimeType=application/vnd.cryptomator.encrypted;application/vnd.cryptomator.vault; |
Thanks for analyzing this @overheadhunter. Possibly we need to preprocess the desktop files with sed to remove lines starting with # or ; A PR would be appreciated. |
In preparation for a PR, I attempted to find the problem with the parser. It works just fine, though. The problem can be seen here in the build log:
Note there are two So the new question is: Why are there two files. Apparently the lowercase one is 7 years old. We have two options: Either make the script clean clean the directory before parsing metadata or simply delete the legacy file and leave the script as is. |
I guess they changed the upper/lowercase in an update of the AppImage.
That's what we should do. |
After #3437 got merged, I noticed that the app has been unlisted. Looking at this build log it seems like the
Comment
from the*.desktop
file is incorrectly parsed:This results in a syntax error in the generated
/app/*.md
file:appimage.github.io/apps/Cryptomator.md
Lines 5 to 6 in 3c813eb
Note that the original desktop file has always been
Comment=Cloud Storage Encryption Utility
, no line breaks or duplications involved (as can be shown with this git blame).The same desktop file was parsed correctly in the past (last time with #2828).
The text was updated successfully, but these errors were encountered: