Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Error font-v versioning #3582

Closed
RosaWagner opened this issue Feb 2, 2022 · 2 comments
Closed

Error font-v versioning #3582

RosaWagner opened this issue Feb 2, 2022 · 2 comments
Assignees
Milestone

Comments

@RosaWagner
Copy link
Contributor

💔 ERROR: Check for font-v versioning.
com.google.fonts/check/fontv
--- Rationale ---
The git sha1 tagging and dev/release features of Source Foundry font-v tool
are awesome and we would love to consider upstreaming the approach into fontmake
someday. For now we only emit a WARN if a given font does not yet follow the
experimental versioning style, but at some point we may start enforcing it.
💔 ERROR Failed with ImportError: Failed to initialize: Cmd('git') failed due to: exit code(1)
cmdline: git version
stderr: 'xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun'

@felipesanches felipesanches added this to the 0.8.7 milestone Feb 2, 2022
@felipesanches
Copy link
Collaborator

This seems to be a legitimate ERROR message. It indicates that something is wrong with the setup of the user's system.

I see that this message was included in the fontbakery report posted by Emma at google/fonts#4227 (comment) So, I think @emmamarichal could take a look at this page to see if the solution describe there works for her: https://stackoverflow.com/questions/52522565/git-is-not-working-after-macos-update-xcrun-error-invalid-active-developer-pa

There it is said that the "problem is that Xcode Command-line Tools needs to be updated."

@felipesanches
Copy link
Collaborator

I also see at the bottom of that same post (google/fonts#4227 (comment)) that INFO messages are being excluded from the report.

So, the only reason this check was seem was because it resulted in an ERROR. Otherwise it would have been muted. This in then pretty much pointless.

I would like to suggest to run fontbakery with --loglevel INFO instead of --loglevel WARN, so that INFO messages are also included in the report.

@fonttools fonttools locked and limited conversation to collaborators Feb 4, 2022
@felipesanches felipesanches converted this issue into discussion #3594 Feb 4, 2022
@felipesanches felipesanches self-assigned this Feb 4, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

2 participants