| 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: | 222 |
| Popularity: | 4.60 |
| First Submitted: | 2018-01-07 17:37 (UTC) |
| Last Updated: | 2025-01-24 11:51 (UTC) |
There have never been any such checks, and if there were it would prevent many legitimate update situations. Or lead to a world where the pkgrel gets updated every time whitespace or quoting gets fixed in a PKGBUILD...
I'd suggest instead, using something like community/aurpublish which provides githooks to keep .SRCINFO up to date.
@qKUqm3wtY4 should be fixed now. Sorry for that. AUR used to have checks that rejected git push when pkg* were changed but .SRCINFO was not updated. This does not seem to work anymore.
This package is broken:
:: snapd package(s) failed to install. :: ensure package version does not mismatch between .SRCINFO and PKGBUILD :: ensure package name has a VCS suffix if this is a devel package
@bboozzoo it turned out to be unreproducible post-upgrade issue. Works fine now.
@mati865 thanks for the report. It's a bug in snapd service files, classical distributions should not need to use snap-failure, yikes! I'll try to fix it upstream.
While at it, can you check the log to see why snapd may have failed? The failure helper is run only of the main service fails, so snapd must have exited unexpectedly. I'd be really interested in knowing what happened there.
With the latest version I'm getting:
snapd.failure.service: Failed at step EXEC spawning /usr/lib/snapd/snap-failure: No such file or directory.
Probably snap-failure should be included in the package.
Autoconf and automake are included in the base-devel group, which is supposed to be installed when building AUR packages.
Hello @bboozzoo, there are missing dependencies in makedepends array - autoconf and automake. Thanks for completion.
Hello,
until snapd builds with flto would you mind adding fno-lto to the flags since you already use them?
Thanks!
thank you bboozzoo: I tried fixing it and messed with a bunch of settings not sure my machine would be the best to try to debug from... ended up removing snapd for now. believe that it had something to do with a symlink but couldn't figure out what needed to be changed. Again, thanks!
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.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.service