> Whats needed here is something that applies the appropriate
> workaround for the debhelper version which is used to build the
> package. I hope that at least in Debian sid there is no workaround
> necessary anymore.

I made a comparison of the current state.
Debhelper is 11ish on both most recent releases.
Debian (sid): 11.1.2
Ubuntu (Bionic): 11ubuntu1

open-vm-tools is an equal version: 2:10.1.15-1 (build1 for Ubuntu, but
never mind).

Now I ran four cases
1. current Debian sid
2. Ubuntu Bionic as in the Archive atm
3. Ubuntu Bionic rebulding open-vm-tools as-is (just to be sure)
4. Ubuntu Bionic dropping the workarounds

#1,2,3 fail (again :-/) with the issue as we had it in the past:
Failed to preset unit: Unit file run-vmblock\\x2dfuse.mount does not exist.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on
run-vmblock\\x2dfuse.mount: No such file or directory
Failed to get unit file state for run-vmblock\\x2dfuse.mount: No such
file or directory
run-vmblock\\x2dfuse.mount is a disabled or a static unit, not starting it.

#4 works great
Created symlink
/etc/systemd/system/multi-user.target.wants/run-vmblock\x2dfuse.mount
→ /lib/systemd/system/run-vmblock\x2dfuse.mount.

So it seems with the newer debhelper we actually need to fix the issue
again, by removing all workarounds we added before.
I'll propose that for you on GH as I now rebuilt it for my test.
See [1]
You can consider uploading that as-is to 10.1.15-2 as a fix or to wrap
it up in 10.2 as you get to it.

> Could you figure out what works in the the current ubuntu and
> maybe for all ubuntu backports, in case you are doing them?

No thoughts about backports (yet) so lets keep complexity down at least for now.
Eventually it would be the effort of the backport to select which
workaround applies to "the local" debhelper version.

> The current workarounds are here:

Yeah I remember adding some of these with you.

> I'll try to find some time soonish, but I'll happily take pull requests.

I'm currently traveling and after that blocked for about two weeks at
least, so surely no full PR soon for 10.2.
Lets see who finds free cycles earlier.

[1]: https://github.com/bzed/pkg-open-vm-tools/pull/12

Reply via email to