Age | Commit message (Collapse) | Author |
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
snap-failure and snapd.failure.service are not expected to be used in classical
distributions. Make sure to disable/drop them.
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Update to new upstream release.
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
- update to the latest release
- drop Antergos patch, already merged upstream
- linux-hardened has AppArmor enabled now, do not snapd.apparmor.service in case
someone wants to use it
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Backport a patch improving distro detection on other Arch like systems that also
use this package, eg. Antegros.
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
- update to 2.33.1 release
- backport a patch that improves distro detection on arch derivatives
- drop unused /var/lib/snapd/apparmor directory
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Users have reported issues with govendor trying to get the dependencies. Avoid
this by using the source tarball with bundled vendor dependencies.
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Drop unnecessary patch for gcc 8.x
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Include upstream patch fixing the build of snap-confine with gcc version 8.x
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Instead of disabling cgo, leave it enabled and pass -static to ld. This will
build snap-exec and snap-update-ns as proper static binaries.
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Building statically linked PIE binaries appears to be broken in both Go upstream
and Arch packages. The toolchain ignores CGO_ENABLED=0, does not fail when
building and produces dynamically linked binaries. The output looks like this:
$ CGO_ENABLED=0 go build -o snap-exec github.com/snapcore/snapd/cmd/snap-exec
# github.com/snapcore/snapd/cmd/snap-exec
loadinternal: cannot find runtime/cgo
Since snap-exec *must* be built statically, switch to building with regular Go
toolchain and without PIE.
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
|
|
New upstream release
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
New upstream release
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Similar to the udev files in the previous commit, snapd generates some
dbus files on the fly, and snap-mgmt does not clean it up (yet, should
come soon). Just remove these files manually for now.
|
|
Snapd installs some udev rules (one for each snap) in /etc/udev/rules.d.
because these files are generated on the fly, they are not owned by any
package and therefore are not automatically cleaned up after removal. I think
snap-mgmt should be configured to remove them, but for now, remove them
manually in snapd.install.
|
|
|
|
Previously the source tarball was downloaded to snapd-$pkgver. This is
not a really big problem, since tar is still able to extract the file.
However it might create some unnecessary confusion about the file type,
and there is no reason not to add it. Therefore, since this commit
makepkg downloads the source code to snapd-$pkgver.tar.gz.
|
|
|
|
Previously, to allow user installation of classic snaps, snapd
shipped with a symlink from /snap to /var/lib/snapd/snap. However,
this is a FHS violation. If a user wants to install a classic snap,
the snap command suggests to create the symlink manually.
|
|
snap-seccomp patches
New upstream release 2.31.1.
Add python-docutils to makedepends, so that man pages for snap-confine and
snap-discard-ns are generated.
Drop snap-seccomp patches. The upstream has dropped setting LDFLAGS for cgo
directly in cgo comment sections.
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Previously, snapd would error out in some situations
(it worked on a dirty build, but it didn't on a chroot.
"/startdir/PKGBUILD: line 147:
/build/snapd/pkg/snapd/usr/share/man/man1/snap.1:
No such file or directory".
This is fixed by creating the
usr/share/man/man1 directory
|
|
Drop all cgo/pkgconfig flags in snap-seccomp that are now rejected by go1.9.4+.
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Some updates:
- add missing dependency on libseccomp
- add bash-completion as optional dependency
- drop python-docutils from makedepends (we don't use them, not sure why they
were left behind)
- update mkversion to include $pkgrel, this affects what is reported in `snap
version`:
snap 2.31-2
snapd 2.31-2
series 16
arch
kernel 4.15.1-2-ARCH
- dump extra cleanups in pre_remove(), those are already done by snap-mgmt
- pass all configuration settings when running `make -C data`
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
* Removed non x86_64 architectures according to the Arch packaging guidelines
* Changed from GitHub clones to github tarballs.
* Cleaned up PKGBUILD
|
|
|
|
SNAP_MOUNT_DIR
Couple of updates:
- pre-create /var/lib/snapd/lib/{gl32,vulkan}
Both are needed when setting importing the files into the mount namespace in
snap-confine. Although the code will create both dirs automatically, it's
better to have them created explicitly
- cleanup redundant rules
Both /var/lib/snapd/{hostfs,lib/gl} are created later on with the rest of
/var/lib/snapd directories
- pass SNAP_MOUNT_DIR to make install
This will break when we update to 2.31 due to a new snap.mount systemd unit.
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
environment file
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Both tools may be executed in a different mount space (chroot) where the
libraries could not be resolved.
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|