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

bug(tengwar): two keyboards with the same name #3333

Closed
mcdurdin opened this issue Feb 10, 2025 · 4 comments · Fixed by #3339
Closed

bug(tengwar): two keyboards with the same name #3333

mcdurdin opened this issue Feb 10, 2025 · 4 comments · Fixed by #3339
Labels

Comments

@mcdurdin
Copy link
Member

$ find . -name 'tengwar'
./experimental/shared/fonts/tengwar
./experimental/t/tengwar
./legacy/t/tengwar

This has caused the upload to fail due to the duplication.

The keyboard under experimental/t/tengar needs to be renamed unless it is a keystroke-compatible replacement for legacy/t/tengwar (which is longstanding).

Secondary - we should be able to detect these overlaps at build time (looks like detection is only in place for experimental/release, and does not check legacy folder).

@mcdurdin mcdurdin added the bug label Feb 10, 2025
@DavidLRowe
Copy link
Contributor

@Caliph3ubaidUrRe7man Unfortunately, the "tengwar" keyboard we approved recently will need to be renamed (unless, as noted above, it is keystroke for keystroke the same as the legacy one, in which case I believe we could deprecate the legacy one in favour of the new one).

@Caliph3ubaidUrRe7man
Copy link
Contributor

what would you like to rename it?

@mcdurdin
Copy link
Member Author

Secondary - we should be able to detect these overlaps at build time (looks like detection is only in place for experimental/release, and does not check legacy folder).

I have moved this to #3338.

@mcdurdin
Copy link
Member Author

This was supposed to be fixed in:

But upload is still failing but with a different error now:

07:04:30   Uploading /c/BuildAgent/work/837a1c4afc30068e/keyboards/legacy/t/tengwar/
07:04:30   parse error: Expected separator between values at line 18, column 19
07:04:30   parse error: Expected separator between values at line 18, column 19
07:04:30   parse error: Expected separator between values at line 18, column 19
07:04:30   parse error: Expected separator between values at line 18, column 19
07:04:30   Failed to locate /c/BuildAgent/work/837a1c4afc30068e/keyboards/legacy/t/tengwar/build/
07:04:30   Aborting with error 1

Investigating.

mcdurdin added a commit that referenced this issue Feb 12, 2025
The patch in #3336 missed a comma, which broke the release build. (The
files in legacy/ are more fragile and do not have many build checks, as
they generally do not get modified.)

Fixes: #3333
Emerging-From: #3336
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants