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

Problems in parsing the manifest when there is no en-US locale #68

Closed
vedantmgoyal9 opened this issue Oct 4, 2021 · 8 comments · Fixed by #70
Closed

Problems in parsing the manifest when there is no en-US locale #68

vedantmgoyal9 opened this issue Oct 4, 2021 · 8 comments · Fixed by #70

Comments

@vedantmgoyal9
Copy link

vedantmgoyal9 commented Oct 4, 2021

From logs of workflow run vedantmgoyal9/vedantmgoyal9#98 on my repo:
image

Actual behaviour:
https://github.com/microsoft/winget-pkgs/pull/29305/files

I think the problem occurs because the is only one locale: ko-KR.

Question:
Is it compulsory that en-US should be there with a package?

@vedantmgoyal9 vedantmgoyal9 changed the title Problems in parsing the manifest Problems in parsing the manifest when there is no en-US locale Oct 4, 2021
@vedantmgoyal9
Copy link
Author

@jedieaston
Copy link
Collaborator

That's not the problem, the problem is that Riiid.pollapo.locale.ko-KR.yaml has the type defaultLocale when it should have the type locale. You can't have two defaults.

@vedantmgoyal9
Copy link
Author

I could not understand what are you trying to say. The repo has only one defaultLocale i.e. ko-KR

@jedieaston
Copy link
Collaborator

But your PR has two files in it that both claim they are ManifestType: defaultLocale.

@jedieaston
Copy link
Collaborator

It seems like YamlCreate.ps1 makes assumptions that the defaultLocale will always be en-US (see 1615 among other places). I wonder if one of those is the problem here.

@Trenly
Copy link
Owner

Trenly commented Oct 4, 2021

It seems like YamlCreate.ps1 makes assumptions that the defaultLocale will always be en-US (see 1615 among other places). I wonder if one of those is the problem here.

I believe that is the issue; I did look at the version 1.0 script, and it seems the issue may exist there as well, but I haven't tried it.

I'm not sure the best way to fix this. Maybe looking at the last set of manifests, finding the file that has the default locale, and setting it to that?

@jedieaston
Copy link
Collaborator

jedieaston commented Oct 4, 2021

Maybe looking at the last set of manifests, finding the file that has the default locale, and setting it to that?

That's what I usually do. In fact, winget didn't even list en-US as the default until June.

This presents a little bit of a problem if the user of YamlCreate.ps1 doesn't know the language listed as default, but I guess they just wouldn't touch any of the fields in defaultLocale?

@Trenly
Copy link
Owner

Trenly commented Oct 4, 2021

This presents a little bit of a problem if the user of YamlCreate.ps1 doesn't know the language listed as default, but I guess they just wouldn't touch any of the fields in defaultLocale?

I think that's a reasonable thing to assume

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

Successfully merging a pull request may close this issue.

3 participants