Package Details: snapd 2.48-1

Git Clone URL: (read-only, click to copy)
Package Base: snapd
Description: Service and tools for management of snap packages.
Upstream URL:
Licenses: GPL3
Conflicts: snap-confine
Submitter: Barthalion
Maintainer: bboozzoo (zyga)
Last Packager: bboozzoo
Votes: 136
Popularity: 4.50
First Submitted: 2018-01-07 17:37
Last Updated: 2020-11-23 10:01

Pinned Comments

bboozzoo commented on 2018-10-25 11:56

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 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

Latest Comments

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

camilojm commented on 2020-05-21 23:44

Error makinkg snapd i have also LANG=zh_CN.UTF-8 not sure if that is the problem, but i have LANG=en_US.UTF-8 and LANG=es_COL.UTF-8 ass support

bboozzoo commented on 2020-05-19 09:41

@sxyzy1016 thanks, this is useful. I've pushed an update.

sxyzy1016 commented on 2020-05-19 09:30

set LANG=zh_CN.UTF-8 and run into Error making: snapd in check(); set LANG=en_US.UTF-8 and it works fine.

bboozzoo commented on 2020-05-19 08:04

@sl13kp can you upload the log somewhere? it builds fine in the CI system and clean chroot here.

sl13kp commented on 2020-05-19 07:43

Error making: snapd

bboozzoo commented on 2020-04-26 18:56

@WomboCombo pushed a fix, 2.44.3-2 sets GO111MODULES=off during the build.

WomboCombo commented on 2020-04-25 10:13

Oh, pretty sure that should fix it too. Could have thought about that. Setting it in the PKGBUILD should ensure that it works for people that, for whatever reason, have a newer golang version installed. And it does no harm for people with an older version.

bboozzoo commented on 2020-04-24 06:28

@WomboCombo I suspect I should set GO111MODULE=off in the PKGBUILD. Surprisingly, this does not come up in either chroot or my regular shell. Just checked that we already set that in the test environments on Arch. Unfortunately snapd does not use modules yet because of quite old Go versions used on other distros.

WomboCombo commented on 2020-04-23 20:27

Currerntly running into this error when installing snapd. Any ideas how to fix it?

==> Making package: snapd 2.44.3-1 (Thu 23 Apr 2020 10:16:45 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found snapd-2.44.3.tar.xz
==> Validating source files with sha256sums...
    snapd-2.44.3.tar.xz ... Passed
==> Extracting sources...
  -> Extracting snapd-2.44.3.tar.xz with bsdtar
==> Starting prepare()...
==> Removing existing $pkgdir/ directory...
==> Starting build()...
*** Setting version to '2.44.3-1' from user.
can't load package: cannot find module providing package            working directory is not part of a module
==> ERROR: A failure occurred in build().

EDIT: Okay got it working by manually initializing the modules in the snapd directory with:

go mod init

and then

go mod tidy

it's probably also not wrong to just run

go mod vendor

on your own if you run into this problem. I suspect the problem occured because I already hat a golang environment installed on my machine.

frankbe commented on 2020-03-05 15:21

@bboozzoo: Good point. Interestingly, I had the package group installed, but was missing a few group members. I guess it's because my arch installation is old and the base-devel group changed over time. Anyway, thanks for clearification.