© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Turns out it's not as simple as the above comments suggest.
> https:/
> https:/
udev changes are not relevant to the failures in https:/
> https:/
Our dh doesn't seem to understand "${env:" in *.install, so using the same approach as Debian doesn't seem to work. It always treats "${env:..." as a literal path. And yes I did remember to export the variable from debian/rules.
Just hard coding the service file paths to /usr would probably work for Launchpad builds, but is not something I'm willing to do right now since the path change hasn't graduated from proposed yet and I can't test it locally. I'm only willing to upload changes I have tested locally so it can wait till systemd has migrated... In the meantime, can anyone tell me why "${env:..." isn't understood? Is it the compatibility level?