Comment 14 for bug 1668126

So there are two options here, currently:

You can create a snap and distribute it as a snap package and not have to pay any attention to the Ubuntu dev cycle and freeze dates, you can release whenever you want to, whatever versions you want to regardless of where we are in the development cycle.

OR

You can pressure the Debian maintainer to update and I can try to request a freeze exception to get this version from Debian.

Here is the problem we're facing.

ledmon already exists in Ubuntu, but it's pulled from Debian.

Currently, ledmon in Debian is version 0.79.

Please refer to the upstream Debian bug here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878271

In October, we filed the bug asking to update ledmon in Debian to 0.80 once it was available.

The debian maintainer said he could do it, and we offered to help testing (thought for VROC, we'd need Intel to do the testing).

The Debian maintainer then went silent and nothing further happened. In feburary, we advised the debian maintainer that 1: ledmon 0.90 was now out and he should update to that version instead of 0.80. We also informed him that debian is watching the wrong (Older) source location for updates to ledmon. We provided the new GitHub upstream location.

The Debian maintainer has not responded to this. The package watch is still looking at the old Source Forge location.

I will ask around internally as well, but ultimately there is likely not much that can be done for Bionic outside of my suggestions above.