-
Notifications
You must be signed in to change notification settings - Fork 120
validation fails on developer IDs with uppercase #617
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
Comments
Since using the app id as developer id will be a common use case - it would be pragmatic to allow upper case letters in the developer id. See also https://matrix.to/#/!jcUJARuitCjSJLKnYP:gnome.org/$8oPWRH_nrNHPCDwQR4EaYYBU25ficM85cybtJ1n1_Y0 |
Note that |
I agree, sorry for the delayed response! (I am very preoccupied at the moment) I faintly remember that we initially wanted to allow only lowercase, then dropped that, and it looks like I did not adjust the check (it was supposed to test only the domain part of the rDNS for case, not the whole string...). |
Hello, is there any update to this? We are using the app id in some apps like e.g. Bustle <developer id="org.freedesktop.Bustle">
<name>The Bustle developers</name>
</developer> Since the GNOME runtime now has a new enough appstream the app fails at CI. |
When using "The APP developers" one should use the app id. Unfortunately, it cannot contain uppercase letters, othwerwise we fail during validation: ``` W: org.gnome.Podcasts.Devel:411: developer-id-invalid org.gnome.Podcasts The developer-ID is invalid. It should be an rDNS string identifying the developer, or a Fediverse handle. It must also only contain lowercase ASCII letters, numbers and punctuation. ``` See ximion/appstream#617
We cannot use the app id as appstreamcli does not support uppercase letters. See ximion/appstream#617
The following:
produces a warning:
The docs at https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-developer do not mention any requirement on lowercase vs uppercase.
Either the docs are missing info or the linter is not doing the right thing.
The text was updated successfully, but these errors were encountered: