Hi,
Thanks for fixing! Yes, GO111MODULES was set to on. I've disabled it (or rather, put it to the default behaviour of auto).
Thank you for being responsive :-)
-=david=-
Git Clone URL: | https://aur.archlinux.org/snapd.git (read-only, click to copy) |
---|---|
Package Base: | snapd |
Description: | Service and tools for management of snap packages. |
Upstream URL: | https://github.com/snapcore/snapd |
Licenses: | GPL3 |
Conflicts: | snap-confine |
Submitter: | Barthalion |
Maintainer: | bboozzoo (zyga, mardy) |
Last Packager: | bboozzoo |
Votes: | 217 |
Popularity: | 4.47 |
First Submitted: | 2018-01-07 17:37 (UTC) |
Last Updated: | 2024-11-13 08:24 (UTC) |
« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 25 Next › Last »
Hi,
Thanks for fixing! Yes, GO111MODULES was set to on. I've disabled it (or rather, put it to the default behaviour of auto).
Thank you for being responsive :-)
-=david=-
@dharrigan that's a bit surprising, snapd does not use go.mod. Is it possible that you have GO111MODULE=on in your environment?
Edit: yeah, I was able to reproduce this problem by setting GO111MODULE=on in my environment. I've pushed an update.
Hi,
Getting build errors when attempting to install snapd (or snapd-git). Here's the output:
==> Validating source files with sha256sums...
snapd-2.42.tar.xz ... Passed
==> Cleaning up...
==> Making package: snapd 2.42-1 (Sat 05 Oct 2019 08:51:16 BST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found snapd-2.42.tar.xz
==> Validating source files with sha256sums...
snapd-2.42.tar.xz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting snapd-2.42.tar.xz with bsdtar
==> Starting prepare()...
==> Sources are ready.
==> Making package: snapd 2.42-1 (Sat 05 Oct 2019 08:51:17 BST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
*** Setting version to '2.42-1' from user.
go: finding github.com/snapcore/snapd latest
can't load package: package github.com/snapcore/snapd/cmd/snap: no matching versions for query "latest"
==> ERROR: A failure occurred in build().
Aborting...
Error making: snapd
@bboozzoo remmina was the application that had no fonts, but also snap store was missing fonts also.
@homelessuser which snap had the fonts rendered incorrectly in your case?
@homelessuser thanks for letting me know. Indeed, I can see the problem here too: https://i.imgur.com/5sLAJTs.png
Fonts missing and replaced with empty boxes in 2.14.r1137. It looks exactly like this https://forum.snapcraft.io/t/snapped-app-not-loading-fonts-on-fedora/12484 Host fonts not being read correctly?
@Gonzalo2683 I think there's something broken in your system.
$ pkg-config --path libseccomp
/usr/lib/pkgconfig/libseccomp.pc
Maybe try reinstalling libseccomp
or using a clean chroot to build the package like described here: https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot
Hello @bboozzoo the results was:
gonza@Arch-Linux/ pacman -Q libseccomp libseccomp 2.4.1-2 gonza@Arch-Linux/ pkg-config --cflags --libs libseccomp Package libseccomp was not found in the pkg-config search path. Perhaps you should add the directory containing `libseccomp.pc' to the PKG_CONFIG_PATH environment variable No package 'libseccomp' found gonza@Arch-Linux/ I can not find the location of the file
'libseccomp.pc'
How would the correct way to create the environment variable called PKG_CONFIG_PATH
?
@Gonzalo2683 not sure I understand what's happening in your system then.
The libseccomp package is listed in makedepends
, so it should get automatically installed when you run makepkg -s
.
Can you verify that libseccomp
is indeed installed? Try running pacman -Q libseccomp
. If that works try pkg-config --cflags --libs libseccomp
.
Pinned Comments
bboozzoo commented on 2018-10-25 11:56 (UTC) (edited on 2024-04-09 07:39 (UTC) by bboozzoo)
Package update notes
2.36
2.36 is the first release with AppArmor enabled by default on Arch.
If you do not have AppArmor enabled at boot there should be no functional changes visible.
If you wish to use snaps with Apparmor, first make sure that Apparmor is enabled during boot, see https://wiki.archlinux.org/index.php/AppArmor for details. After upgrading the package, you need to do the following steps:
systemctl restart apparmor.service
snapd
:systemctl restart snapd.service
systemctl enable --now snapd.apparmor.service
2.62
Since 2.62 snapd generated additional files describing the sandbox. The snapd service needs to be restarted after the update for snaps to continue working (unless the system is rebooted after the update, in which case no additional steps are needed). To restart, run
systemctl restart snapd.service