[11:39] <jamespage> p/
[11:39] <jamespage> o/
[11:39] <jamespage> even
[11:40] <jamespage> I'm looking at an SRU sponsorship which is using systemd drop-ins to tweak the behaviour of a service so that it starts after another service - feels like drop-ins are designed for sysadmins rather than packages - is there any prior art/option on this topic?
[11:40] <jamespage> rbasak: have you seen anything like this before?
[11:41] <cjwatson> You can have drop-ins in /usr/lib/systemd/system/ as opposed to /etc/systemd/system/, and I think the former is designed for packages
[11:41] <cjwatson> There can certainly be complex interactions, but it doesn't seem fundamentally wrong
[11:42] <cjwatson> (or /lib/systemd/system/ for older releases)
[11:42] <bluca> drop-ins in /usr are definitely for packages
[11:43] <cjwatson> I see a moderate amount of prior art looking in /usr/lib/systemd/system/*.d/*.conf here
[11:43] <jamespage> great that answers my question - dev is looking for a minimal fix which does not involve changing the way we generate systemd units using openstack-pkg-tools for the SRU's
[11:43] <jamespage> dev is fixed to generate the right stuff
[11:43] <jamespage> but TBH I'd quite like to move away from that approach - its a bit of a hangover from having to suppprt three init systems.
[12:17] <sudip> can anyone with superpowers please click on this link - https://autopkgtest.ubuntu.com/request.cgi?release=mantic&package=sagemath&arch=amd64&trigger=sagemath%2F9.5-6ubuntu0.2&ppa=sudipmuk%2Fsagemath-1
[12:19] <seb128> sudip, clicked
[12:19] <sudip> thanks seb128
[12:19] <seb128> np!
[14:11] <slyon> jbicha: FYI I forward-ported the 64-bit time-t NMU from gpaste 44.1-2.1 to 45-2 (from experimental): https://launchpad.net/ubuntu/+source/gpaste/45-2ubuntu4
[16:30] <dbungert> @pilot in
[21:13] <dbungert> @pilot out