liblxc-common: AppArmor-Profile for /usr/bin/lxc-copy contains rule for lxc-start

[Nicolas Schier]

Hi,

liblxc-common 1:5.0.3-2ubuntu7 provides an AppArmor-Profile for /usr/bin/lxc-copy, but the profile file
contains the rule for /usr/bin/lxc-start instead of /usr/bin/lxc-copy. The mistake was introduced in [1], current Debian versions (1:5.0.2-1 and 1:6.0.1-1) are not affected, but Ubuntu 24.04 (noble) is. This
wrong profile file prevents running lxc-copy on my companies Ubuntu 24.04 machines.

Can you please replace the 'lxc-start' by 'lxc-copy' in /etc/apparmor/usr.bin.lxc-copy or update to Debian's 1:6.0.1-1 or above?

Thanks and kind regards,
Nicolas

[1]: https://salsa.debian.org/lxc-team/lxc/-/merge_requests/19/diffs?commit_id=a2ad01ca2081c4dd925037253b01fff0499af17e#d7b13f871dc297c7aa81e98c974db1a24f1b016d_0_21

---
Description: Ubuntu 24.04.1 LTS
Release: 24.04
liblxc-common:
  Installed: 1:5.0.3-2ubuntu7
  Candidate: 1:5.0.3-2ubuntu7
  Version table:
 *** 1:5.0.3-2ubuntu7 990
        990 http://de.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: liblxc-common 1:5.0.3-2ubuntu7
Uname: Linux 6.10.6 x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: sway
Date: Wed Sep 11 12:37:23 2024
InstallationDate: Installed on 2024-08-26 (16 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220)
SourcePackage: lxc
UpgradeStatus: Upgraded to noble on 2024-09-04 (7 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "[PATCH] apparmor: lxc-copy: Replace mistyped filename lxc-start by lxc-copy" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

[Nicolas Schier (nschier)]

FTR: A colleague mentioned that "switching" to Debian 1:6.0.0-1 w/o fixing the patch wouldn't help as the Debian sources still carry the bad patch, which is applied only when building for Ubuntu.