Package Details: snapd 2.66.1-1

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)

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:

  • Reload the profiles: systemctl restart apparmor.service
  • Restart snapd: systemctl restart snapd.service
  • Load profiles for snaps: 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

Latest Comments

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 Next › Last »

ibrokemypie commented on 2018-06-15 04:49 (UTC)

@bboozzoo My makepkg.conf is here: https://hastebin.com/bozoduwete.coffeescript

joopdo commented on 2018-06-13 05:46 (UTC)

@bboozzoo that's it! Thanks a lot for the quick response and fix for my problem. Cheers

bboozzoo commented on 2018-06-12 14:06 (UTC)

@joopdo pushed a change to use the source tarball with vendor dependencies bundled in. Can you check if it works for you now?

joopdo commented on 2018-06-12 08:23 (UTC) (edited on 2018-06-12 08:27 (UTC) by joopdo)

@bboozzoo I assumed it's generic due to the unrecognized import path.

If specific, I look myself. I'm based in China (forgot to mention this fact) but got same response with and without VPN. I noticed that my first mention included some output from my proxy, sorry for any confusion.

bboozzoo commented on 2018-06-12 07:50 (UTC)

@joopdo do the hosts you build the package on have network access or are behind some proxy that may mangle the headers?

I can probably look into using the source tarball that includes the vendored dependencies. The downside is that sometimes it took a while to have it published on github releases page.

joopdo commented on 2018-06-12 06:38 (UTC) (edited on 2018-06-12 08:26 (UTC) by joopdo)

Current AUR seems to fail for me on multiple machines.

Govendor reports: Obtaining dependencies Error: Remotes failed for: Failed for "golang.org/x/crypto/cast5" (failed to ping remote repo): unrecognized import path "golang.org/x/crypto/cast5"

bboozzoo commented on 2018-06-12 06:07 (UTC)

@ibrokemypie can you share your makepkg.conf and how you build the package? I tried building it with clang (and lld) inside and outside of a clean chroot, but failed to reproduce the build issue you're seeing. Can you double check that binutils is properly installed?

ibrokemypie commented on 2018-06-12 00:20 (UTC)

==> Starting build()... *** Setting version to '2.33-1' from shell. Obtaining dependencies

runtime/cgo

/usr/bin/ld: cannot find now: No such file or directory clang-6.0: error: linker command failed with exit code 1 (use -v to see invocation) ==> ERROR: A failure occurred in build(). Aborting... Error making: snapd

7314776 commented on 2018-05-08 15:12 (UTC)

@bboozzoo, this one builds fine, thank you!

bboozzoo commented on 2018-05-08 07:36 (UTC)

Included a patch from upstream, the package should build fine with gcc 8.x now.

« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 Next › Last »