Snappy

snappy:release/2.60

Git
lp:snappy
release/2.60

Last commit made on 2024-01-15

Get this branch:: git clone -b release/2.60 https://git.launchpad.net/snappy

Branch merges

Branch information

Name:: release/2.60

Repository:: lp:snappy

Recent commits

70b7817... by Miguel Pires on 2023-10-18

tests: clear snap cache before interfaces-content test

The test was pulling in the core snap which failed to be validated.
This happened because the snap was already in the cache and had
been modified in the prepare stage. Since it was modified, there's
no assertion matching the digest. Clearing the cache fixes the
problem. This was triggered because we recently stopped building
core on i386 so all channels now have the same revision.

Signed-off-by: Miguel Pires <email address hidden>

e386a71... by Philip Meulengracht on 2023-10-05

tests/main: remove unsupported core16 tests

b1e223a... by Samuele Pedroni on 2023-10-26

o/snapstate: make tests work consistently also in containers

5ae1c96... by Valentin David on 2023-08-28

cmd/snapd-generator: read mountinfo for pid 1

Systemd now runs generators in a sandbox. That means
`/proc/self/mountinfo` does not represent correctly the mounts of the
system.

3ab0acd... by Michael Vogt on 2023-09-15

release: 2.60.4 (#13200)

197c9a2... by Alfonso Sanchez-Beato on 2023-09-13

snap/naming: add ancillary function to check label names

6cd2aa7... by Alfonso Sanchez-Beato on 2023-09-13

interfaces/qualcomm-ipc-router: split in slot and plug

Split permissions between a slot and a plug that can both be provided
by a snap, but still allow to connect to a system provided slot.

a4f8923... by Valentin David on 2023-06-07

i/b/qualcomm_ipc_router.go: switch to plug/slot and add socket permission

ebaee9d... by Oliver Calder on 2023-09-08

interfaces/builtin: fix custom-device udev KERNEL values (#13178)

* interfaces/builtin: fix custom-device udev KERNEL values

Previously, the handling of udev tagging rules was modified to allow
device paths in subdirectories of `/dev/`. As part of this work,
checks were put in place to ensure that all KERNEL values, including
default rules, must be basenames of a device path.

That work can be found in two previous commits:

- b1df21de4719da0644ce7528d9bc9cd46dbf99c1
- 12ca6af3a000b30552abb33377724379faf4aab8

The former allows either full paths (stripped of leading `/dev/`) or
basenames, while the latter switches this requirement so that all values
must be basenames. The commit message of the latter indicates that
KERNEL values which are not basenames violate the udev spec -- this is
incorrect.

For some devices, the udev KERNEL value must be the full path of the
device, stripped of leading `/dev/`, while for other devices, the udev
KERNEL value must be the basename of the device path. If an explicit
udev tagging rule is not given, it is unclear which of these is the
case.

This commit changes udev tagging handling to emit two rules for each
device path in a subdirectory of `/dev/` which is not given as the
kernel value of an explicit udev rule in the "udev-tagging" section:
one using the full device path following `/dev/`, and one using the
basename of the device path.

If there are device paths of the form /dev/bar and /dev/foo/bar, then
default rules will be generated for both KERNEL=="bar" and
KERNEL=="foo/bar". If there are explicit rules for either, the default
rule for the other (if it has no explicit rule) will still be emitted.