AUR (en) - snapd

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: snapd 2.66.1-1

Package Actions

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 .. 17 18 19 20 21 22 23 24 25 Next › Last »

7314776 commented on 2018-05-07 21:29 (UTC)

triple confirm @Janzu report - same syntax error while building, yaourt twice and pacman-helper once. @bboozzoo – thanks for noting this.

bboozzoo commented on 2018-05-07 18:58 (UTC)

@Janzu thanks for reporting this. A fix is in the works right here: https://github.com/snapcore/snapd/pull/5138 and we should be able to merge it soon. Once in master, it will be cherry-picked to the upcoming 2.32.7 release and I'll also pick it up for 2.32.6-2.

Janzu commented on 2018-05-07 18:34 (UTC) (edited on 2018-05-07 18:40 (UTC) by Janzu)

Latest version fails build with error during make

Relevant part of log: https://pastebin.com/mSGSYTgx

lockheed commented on 2018-04-12 06:54 (UTC)

@bboozzoo thanks for clarification. Could you update arch wiki to reflect this change?

bboozzoo commented on 2018-04-12 06:48 (UTC) (edited on 2018-04-12 06:48 (UTC) by bboozzoo)

@lockheed snap.refresh.timer has been removed in favor of an internal mechanism of snapd. It can be controlled by setting refresh.timer, eg. snap set core refresh.timer=0:00-24:00/4. See https://forum.snapcraft.io/t/system-options/87 for more details on how to set refresh.timer. snap refresh --time shows last/next refresh times.

FWIW the syntax is more expressive and as we learned people try to do pretty crazy things with refresh times. Also, snap.refresh.timer was also acting as a workaround for bad (or nonexistent) support for monotonic timers in Go, what could cause the refresh to not happen at all (hence the separate, systemd-driven, timer which would kick the refresh anyway).

lockheed commented on 2018-04-11 20:24 (UTC)

Why is there no snapd.refresh.timer in this package?

systemctl start snapd.refresh.timer

Failed to start snapd.refresh.timer: Unit snapd.refresh.timer not found.

aimileus commented on 2018-03-23 16:37 (UTC)

@cmsigler, you are right that these files should be removed. Upstream includes a script to clean up the snapd files, but this does not include the udev rules. Since these rules are generated on the fly (one per snap), it is also not possible to include them in the package. For now I just decided to remove them manually in snapd.install.

cmsigler commented on 2018-03-21 15:47 (UTC)

Hi,

I hope these aren't stupid questions.

A few days ago I installed snapd from AUR and tried it. The snaps I installed didn't work and that's fine, no complaint as it was purely an experiment. I removed snapd. This left behind one file I found today -- `/etc/udev/rules.d/70-snap.core.rules'. This is some kind of USB modem manager file(?). Please see:

https://github.com/snapcore/snapd/blob/master/interfaces/builtin/modem_manager.go

1.) The package itself seems to generate this file? Does that mean it's not intended to go in /usr/lib/udev/rules.d/ ? Or should it? 2.) Is it possible to have the package manager clean up this file upon removal?

Just something I noticed. The answer to both may be "no." :) HTH and thank you.

Clemmitt Sigler

bboozzoo commented on 2018-03-12 06:31 (UTC)

@archlinux38 Can you post that to https://forum.snapcraft.io so that we don't spam the comments here?

The only think I can suggest now, having a cloned tree and while in the package directory:

go env and paste the output somewhere
export GOPATH=$PWD
try to build one of the components, eg. go build -x -v -o test-snapd github.com/snapcore/snapd/cmd/snapd once it fails, upload the log somewhere

archlinux38 commented on 2018-03-11 20:15 (UTC)

@aimileus I wish I could answer that but I can't. I don't think I have changed anything like that. Can you guide me how to look for those changes?