| 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) |
| Last Packager: | bboozzoo |
| Votes: | 231 |
| Popularity: | 3.42 |
| First Submitted: | 2018-01-07 17:37 (UTC) |
| Last Updated: | 2026-04-20 08:01 (UTC) |
I'm getting a big, fat warning
==> WARNUNG: Verwende bestehenden $srcdir/ Baum
==> Beginne build()...
fatal: Kein Git-Repository (oder irgendein Elternverzeichnis bis zum Einhängepunkt /)
Stoppe bei Dateisystemgrenze (GIT_DISCOVERY_ACROSS_FILESYSTEM nicht gesetzt).
fatal: Kein Git-Repository (oder irgendein Elternverzeichnis bis zum Einhängepunkt /)
Stoppe bei Dateisystemgrenze (GIT_DISCOVERY_ACROSS_FILESYSTEM nicht gesetzt).
*** Setting version to '2.46.1-1' from user.
I'm getting a build problem after removing .cache/yay/snapd:
configure: WARNING: "cannot find the valgrind tool, will not run unit tests through valgrind"
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
make: *** No rule to make target '"4"'. Stop.
==> ERROR: A failure occurred in build().
Aborting...
error making: snapd
@dslink builds fine with 2.45.3.1-2 I pushed a week ago.
Wont build, even tried to build directly from offical git. This is the aur error snap-confine-private.a make[1]: Leaving directory '/tmp/trizen-***/snapd/src/snapd-2.45.3.1/cmd' ==> Starting check()... ==> ERROR: A failure occurred in check(). Aborting... :: Unable to build snapd - makepkg exited with code: 4
@bittin can you try again? There was some delay in publishing tarballs in the releases page. This also overlapped with some unexpected github downtime.
The download from Github does not work
@bboozzoo Thanx, 'export LC_ALL=C' and 'pikaur -S snapd' now did the trick, snapd was installed from AUR and is now working fine!
@ZombB please attach the journal output, preferrably try building it again with LC_ALL=C. Make sure that all packages from base-devel are installed and that build dependencies are installed.
Pinned Comments
bboozzoo commented on 2018-10-25 11:56 (UTC) (edited on 2025-07-10 11:42 (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.servicesnapd:systemctl restart snapd.servicesystemctl enable --now snapd.apparmor.service2.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.service2.70
Snapd 2.70 drops setuid permissions on /usr/lib/snapd/snap-confine in favor of explicit file capabilities. After an upgrade to 2.70, the users are prompted to restart the
apparmor.serviceotherwise attempts to run snaps will error withcannot set capabilitiesmessage.