** Description changed:

+ [SRU] 2.76
+ (https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2154498)
+ 
+ [ Impact ]
+ The snapd package installs systemd unit files and udev helpers to legacy 
paths (/lib/systemd/, /lib/udev/) instead of the DEP17-compliant /usr/lib/ 
paths. On Ubuntu Resolute and later releases that enforce usr-merge, this 
triggers lintian errors (aliased-location) and violates the distribution 
packaging policy.
+ 
+ This is a packaging-only change with no functional impact on snapd
+ behaviour.
+ 
+ [ Test Plan ]
+ This is a packaging compliance fix (PR 
https://github.com/canonical/snapd/pull/16755). No automated unit/spread tests 
apply as this is purely about installed file paths.
+ 
+ Verification:
+ 1. Install snapd 2.76 on Noble, Questing, or Resolute.
+ 2. Confirm systemd units are installed under /usr/lib/systemd/system/:
+    $ dpkg -L snapd | grep systemd
+    Verify paths are /usr/lib/systemd/system/... (not /lib/systemd/system/...)
+ 3. Confirm udev helper is under /usr/lib/udev/:
+    $ dpkg -L snapd | grep udev
+    Verify paths are /usr/lib/udev/... (not /lib/udev/...)
+ 4. Confirm snapd still starts and operates normally:
+    $ systemctl status snapd
+    $ snap list
+ 
+ Backwards compatibility: On Jammy and Focal, the package continues to
+ install to /lib/... as those releases use older systemd that reports
+ /lib/systemd/system as the unit directory.
+ 
+ [ Where problems could occur ]
+ If the pkg-config query for systemdsystemunitdir returns an unexpected path 
on a given release, units could be installed to the wrong location. This was 
verified across Bionic through Resolute during PR review.
+ 
+ [ Applicability ]
+ Classic Ubuntu only (Noble 24.04+). Does not affect Ubuntu Core.
+ 
+ ---original---
+ 
  snapd has been identified as having a possible issue related to usr-
  merge. DEP-17 describes the issue and problems at length[0]. The check
  done was not perfect, and may lead to false positives. The following was
  the run to identify possible packages, further refined with slight
  pruning of obvious false positives
  
  apt-file search --package-only --regexp
  '^/(sbin|bin|lib|lib32|lib64|libx32)/*'
  
  Lintian, when run on a suitably new system (such as within a resolute
  build environment), will provide some errors related to usr-merge. an
  example of a Lintian error from busybox
  
  E: busybox-static: aliased-location [bin/]
  E: busybox-static: aliased-location [bin/static-sh]
  
  Please evalute snapd for any issues dictated in dep17
  
  [0] https://dep-team.pages.debian.net/deps/dep17/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2139213

Title:
  [usrmerge] evaluate snapd for DEP17 compliance

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/2139213/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to