I was made aware of this case today by lathiat - thanks.
I agree that it must be a pain to miss this and yes, IMHO it should be added back.
I have prepared a test build for jammy [1] in a PPA.
Which works just fine AFAICS, feel free to try that and have a look.
It really is - as assumed above and seen in [2] - a removal because the dependency liboping was FTBFS in bug 1960612 however this was fixed and got published in jammy pretty late, but collectd wasn't restored.
Collectd exists in all previous and future versions so makes sense to restore it to jammy I think.
So from a users of anything that depends on it (see all the pings on this bug) as well upgrade perspective of users that had it e.g. on Focal - it should be better to add it back.
I see no conflict of this in regard to the SRU policy, so let us get this started.
I was made aware of this case today by lathiat - thanks.
I agree that it must be a pain to miss this and yes, IMHO it should be added back.
I have prepared a test build for jammy [1] in a PPA.
Which works just fine AFAICS, feel free to try that and have a look.
It really is - as assumed above and seen in [2] - a removal because the dependency liboping was FTBFS in bug 1960612 however this was fixed and got published in jammy pretty late, but collectd wasn't restored.
Collectd exists in all previous and future versions so makes sense to restore it to jammy I think.
So from a users of anything that depends on it (see all the pings on this bug) as well upgrade perspective of users that had it e.g. on Focal - it should be better to add it back.
I see no conflict of this in regard to the SRU policy, so let us get this started.
[1]: https:/ /launchpad. net/~paelzer/ +archive/ ubuntu/ jammy-get- collectd- back/+packages /launchpad. net/ubuntu/ +source/ collectd/ +publishinghist ory
[2]: https:/