Package Details: ttf-harmonyos-sans 2025.09.23-1

Git Clone URL: https://aur.archlinux.org/ttf-harmonyos-sans.git (read-only, click to copy)
Package Base: ttf-harmonyos-sans
Description: HarmonyOS Sans Fonts.华为鸿蒙字体
Upstream URL: https://developer.huawei.com/consumer/cn/design/resource/
Keywords: harmonyos 鸿蒙
Licenses: LicenseRef-custom
Conflicts: harmonyos-sans
Submitter: zxp19821005
Maintainer: zxp19821005
Last Packager: zxp19821005
Votes: 16
Popularity: 0.198418
First Submitted: 2023-04-19 07:18 (UTC)
Last Updated: 2025-11-10 05:02 (UTC)

Dependencies (0)

Required by (1)

Sources (1)

Latest Comments

1 2 Next › Last »

zxp19821005 commented on 2025-08-01 05:34 (UTC)

@oldherl Thanks for your feedback, fixed it.

oldherl commented on 2025-07-23 02:44 (UTC)

Please install the LICENSE.txt file to the usual license location

JustinSB commented on 2025-05-03 08:50 (UTC)

I had identical checksum problems to @OddBook, but I followed the comment from @zxp19821005 and deleted ~/.cache/yay/ttf-harmonyos-sans/ which fixed it instantly. ttf-harmonyos-sans installed straight away after that, & everything worked

zxp19821005 commented on 2025-04-30 02:48 (UTC)

@OddBook I've downloaded the source file for several times, it's checksums was always ba7ddf71fc4dee33a7170869564ad76d421a2ed5c58e5aac9a573c39945ef654 . I think you should do rm -rf ~/.cache/yay/ttf-harmonyos-sans/ to delete the old files before.

OddBook commented on 2025-04-30 02:31 (UTC) (edited on 2025-04-30 02:31 (UTC) by OddBook) 

andrew@desktop ~> yay -S ttf-harmonyos-sans --noconfirm
AUR Explicit (1): ttf-harmonyos-sans-2024.06.19-3
:: PKGBUILD up to date, skipping download: ttf-harmonyos-sans
  1 ttf-harmonyos-sans                       (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
  1 ttf-harmonyos-sans                       (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
==> Making package: ttf-harmonyos-sans 2024.06.19-3 (Tue 29 Apr 2025 09:22:01 PM CDT)
==> Retrieving sources...
  -> Found ttf-harmonyos-sans-2024.06.19.zip
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha256sums...
    ttf-harmonyos-sans-2024.06.19.zip ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error downloading sources: /home/andrew/.cache/yay/ttf-harmonyos-sans 
         context: exit status 1 


:: (1/1) Parsing SRCINFO: ttf-harmonyos-sans
==> Making package: ttf-harmonyos-sans 2024.06.19-3 (Tue 29 Apr 2025 09:22:02 PM CDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found ttf-harmonyos-sans-2024.06.19.zip
==> Validating source files with sha256sums...
    ttf-harmonyos-sans-2024.06.19.zip ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error making: ttf-harmonyos-sans-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
ttf-harmonyos-sans - exit status 1

zxp19821005 commented on 2025-04-27 09:12 (UTC)

@TRex Thanks for your feedback, fixed it.

TRex commented on 2025-04-27 08:10 (UTC) (edited on 2025-04-27 08:12 (UTC) by TRex)

new version, new shasum: ba7ddf71fc4dee33a7170869564ad76d421a2ed5c58e5aac9a573c39945ef654

and the license file is missing...

ulugbeg commented on 2024-07-12 15:47 (UTC)

Great, thank you!

As an FYI, I did get a warning during my upgrade:

.cache/paru/clone/ttf-harmonyos-sans/PKGBUILD: line 16: warning: setlocale: LC_CTYPE: cannot change locale (zh_CN.UTF-8): No such file or directory

I'm guessing I don't have that locale installed, but it was just a warning, all seemed fine :)

zxp19821005 commented on 2024-07-12 05:09 (UTC)

@ulugbeg Thank you for your feedback, but this was indeed a problem that occurred in the upstream packaging. After decompression, there were indeed spaces behind the folder. Yesterday, I also found that packaging failed many times.

ulugbeg commented on 2024-07-11 14:41 (UTC)

Please forgive my ignorance, but in the latest version (dated 2024-07-10) of this package, there are extra spaces in the install statement. Is that a mistake, or intentional?

I've skimmed through the documentation of install , but I can't tell for sure if this causes an error or fixes one.

Haven't installed the update just to be sure.

1 2 Next › Last »