Skip to content

Update CLDR to version 42#14273

Merged
seanbudd merged 3 commits into
nvaccess:masterfrom
OzancanKaratas:updateCLDR
Oct 20, 2022
Merged

Update CLDR to version 42#14273
seanbudd merged 3 commits into
nvaccess:masterfrom
OzancanKaratas:updateCLDR

Conversation

@OzancanKaratas

@OzancanKaratas OzancanKaratas commented Oct 19, 2022

Copy link
Copy Markdown
Collaborator

Link to issue number:

Related nvda-cldr update: nvaccess/nvda-cldr#3

Summary of the issue:

Periodically CLDR update: CLDR team released version 42 of the CLDR package.

Description of user facing changes

New emojis and characters

Description of development approach

None

Testing strategy:

Use your favorite emoji provider like emojipedia.org

Known issues with pull request:

None

Change log entries:

Changes

Code Review Checklist:

  • Pull Request description:
    • description is up to date
    • change log entries
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • API is compatible with existing add-ons.
  • Documentation:
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English
  • Security precautions taken.

@OzancanKaratas OzancanKaratas requested a review from a team as a code owner October 19, 2022 14:42
Comment thread readme.md Outdated
@seanbudd seanbudd merged commit 30017fa into nvaccess:master Oct 20, 2022
@nvaccessAuto nvaccessAuto added this to the 2023.1 milestone Oct 20, 2022
@OzancanKaratas OzancanKaratas deleted the updateCLDR branch October 20, 2022 13:02
@LeonarddeR

Copy link
Copy Markdown
Collaborator

I'm getting the following error on multiple systems when updating submodules:

fatal: transport 'file' not allowed                                                                                     
fatal: Fetched in submodule path 'nvda-cldr', but it did not contain 8e98c77fc3cdb33cf6d530f27f82c972ef3d93c0. Direct fetching of that commit failed.                                                                                           

@zstanecic

zstanecic commented Oct 21, 2022 via email

Copy link
Copy Markdown
Contributor

@vielmetti

Copy link
Copy Markdown

This is almost certainly CVE-2022-39253 which prompted changes in git
due to security problems identified.

You may find this issue summary useful with an account of some workarounds
done by other projects to get around the "fatal: transport 'file' not allowed" problem.

https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html

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 this pull request may close these issues.

6 participants