Package Base Details: font-symbola

Git Clone URL: https://aur.archlinux.org/font-symbola.git (read-only, click to copy)
Submitter: grawlinson
Maintainer: grawlinson (caleb)
Last Packager: caleb
Votes: 71
Popularity: 6.04
First Submitted: 2020-03-21 23:45
Last Updated: 2020-03-27 16:02

Pinned Comments

caleb commented on 2020-03-25 05:53

In the latest release of this package I've introduced a workaround to force fresh downloads whenever we bump the package release number, not just the version. This should work around most people's caching issues resulting from upstream's replacing files without changing the filename or versions.

If you hit a checksum error now please flag this package as out of date.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

nTia89 commented on 2020-03-27 11:17

@caleb @grawlinson, I am a bit confused about ttf-symbola-infinality package: 1- as ttf-* package I expect it contains a ttf, but it doesn't. 2- the group 'infinality-bundle-fonts' doesn't exist anymore, it was substituted by 'fonts-meta-base' and 'fonts-meta-extended-lt' meta packages 3- already exists an identical package 'ttf-symbola-ib'

caleb commented on 2020-03-26 09:40

@aorth I cannot confirm, I get the same checksum on a fresh download right now.

caleb commented on 2020-03-25 23:11

Thanks @Brottweiler, that's my mistake. I just corrected it. I did not bump the pkgver since that would make people download it all over again for something that didn't actually get changed, it only shows a warning on install, it doesn't actually change the permissions. The fix will stop the warning for new installs and everybody else is okay anyway.

Brottweiler commented on 2020-03-25 23:01

warning: directory permissions differ on /etc/fonts/conf.d/

filesystem: 755 package: 644

brianbrodsky12 commented on 2020-03-25 08:49

I just updated to 13.00-6 with aurman and worked fine. If it did not I would have downloaded a snapshot and tried makepkg. Thank you.

caleb commented on 2020-03-25 05:53

In the latest release of this package I've introduced a workaround to force fresh downloads whenever we bump the package release number, not just the version. This should work around most people's caching issues resulting from upstream's replacing files without changing the filename or versions.

If you hit a checksum error now please flag this package as out of date.

GeoZac commented on 2020-03-25 01:12

Seems the package is failing because of validity checks

Validating source files with sha512sums... font-symbola-13.00.zip ... FAILED LICENSE.pdf ... Passed 

But built fine with makepkg

grawlinson commented on 2020-03-24 23:37

brianbrodsky12: AUR package managers are not supported, I recommend using makepkg or a clean chroot. From a cursory glance, I suggest cleaning your cache.

brianbrodsky12 commented on 2020-03-24 22:46

No still getting error, just tried again:

[brian@brian-arch-desktop ~]$ aurman -Syyu [sudo] password for brian: :: Synchronizing package databases... core 135.6 KiB 797 KiB/s 00:00 [######################] 100% extra 1643.3 KiB 1182 KiB/s 00:01 [######################] 100% community 4.8 MiB 1208 KiB/s 00:04 [######################] 100% :: Starting full system upgrade... there is nothing to do

~~ initializing aurman... ~~ calculating solutions...

:: The following 1 package(s) are getting updated: aur/ttf-symbola 13.00-4 -> 13.00-5

?? Do you want to continue? Y/n: ~~ looking for new pkgbuilds and fetching them... ==> Making package: font-symbola 13.00-5 (Tue 24 Mar 2020 06:45:08 PM EDT) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found font-symbola-13.00.zip -> Found LICENSE.pdf ==> Validating source files with sha512sums... font-symbola-13.00.zip ... FAILED LICENSE.pdf ... Passed ==> ERROR: One or more files did not pass the validity check! 2020-03-24 18:45:08,252 - wrappers - makepkg - ERROR - makepkg query ['makepkg', '-cf', '--noconfirm'] failed in directory /home/brian/.cache/aurman/font-symbola [brian@brian-arch-desktop ~]$

F1nny commented on 2020-03-24 22:37

@caleb and @gawlinson Ahh gotcha and thank you both for the quick action/reply here, greatly appreciate you both :)

@brianbrodsky12 gawlinson got it fixed up pretty quick, just try again and should be good (I just confirmed all clear/good!)