touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Finally there are two dependency cycles which we need to fix:

Found ordering cycle on basic.target/start
Found dependency on sysinit.target/start
Found dependency on apparmor.service/start
Found dependency on remote-fs.target/start
Found dependency on remote-fs-pre.target/start
Found dependency on nfs-client.target/start
Found dependency on rpc-statd-notify.service/start
Found dependency on nfs-server.service/start
Found dependency on rpc-svcgssd.service/start
Found dependency on basic.target/start
Breaking ordering cycle by deleting job apparmor.service/start
Job apparmor.service/start deleted to break ordering cycle starting with basic.target/start

Found ordering cycle on basic.target/start
Found dependency on sysinit.target/start
Found dependency on console-setup.service/start
Found dependency on remote-fs.target/start
Found dependency on remote-fs-pre.target/start
Found dependency on nfs-client.target/start
Found dependency on rpc-statd-notify.service/start
Found dependency on nfs-server.service/start
Found dependency on rpc-svcgssd.service/start
Found dependency on basic.target/start
Breaking ordering cycle by deleting job console-setup.service/start
Job console-setup.service/start deleted to break ordering cycle starting with basic.target/start

This is because these two don't have native systemd units, and their
init.d script depends on $remote_fs. But remote-fs.target requires quite
a lot (networking, dbus, perhaps NetworkManager, etc.), and we do want
to protect those with apparmor. Also, apparmor only uses files in /, so
$local_fs is sufficient even for the hypothetical "/usr on NFS" case.

That's less true for console-setup: This does use files from /usr;
however, as we've never officially supported /usr on NFS, and nobody
ever tested that under upstart, I'm very much inclined to just fix its
init.d dependency to $local_fs, too.

** Also affects: apparmor (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: apparmor (Ubuntu)
       Status: New => In Progress

** Changed in: apparmor (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

** Also affects: console-setup (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: console-setup (Ubuntu)
       Status: New => In Progress

** Changed in: console-setup (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: apparmor (Ubuntu)
       Status: In Progress => Fix Committed

** Changed in: console-setup (Ubuntu)
       Status: In Progress => Fix Committed

** Summary changed:

- nfs-utils needs systemd unit or init.d script
+ Make NFS client/server work under systemd

** Changed in: console-setup (Ubuntu)
       Status: Fix Committed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1312976

Title:
  Make NFS client/server work under systemd

Status in apparmor package in Ubuntu:
  Fix Committed
Status in console-setup package in Ubuntu:
  In Progress
Status in nfs-utils package in Ubuntu:
  In Progress
Status in rpcbind package in Ubuntu:
  Fix Committed
Status in rpcbind package in Debian:
  Unknown

Bug description:
  nfs-utils can not be used with systemd due to missing systemd unit or
  init.d script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1312976/+subscriptions