RM: telegraf from Noble; no longer maintained in Ubuntu
Bug #2062013 reported by
Sergio Durigan Junior
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| telegraf (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Hi,
Telegraf was added in Ubuntu back in 2020 as part of the LMA (Logging, Monitoring and Alert) effort, but priorities have changed since then and the package is no longer maintained in the distribution. Telegraf is also one of those "hard" packages to maintain because it requires bundling of everything it depends on, which makes things very difficult for the Security team, for example.
The package does not have any reverse dependencies.
Revision history for this message
| Christian Ehrhardt (paelzer) wrote | #1 |
| Changed in telegraf (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| Christian Ehrhardt (paelzer) wrote | #2 |
| Changed in telegraf (Ubuntu): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Agreed, and due to that it gets rather few updates (for example M/N are the same)
telegraf | 1.21.4+ds1-0ubuntu2 | jammy/universe | source
telegraf | 1.22.3+ds1-0ubuntu2 | mantic/universe | source
telegraf | 1.22.3+ds1-0ubuntu2 | noble/universe | source
But gladly has no reverse dependencies:
$ reverse-depends -r noble --build-depends src:telegraf
No reverse dependencies found
$ reverse-depends -r noble src:telegraf
No reverse dependencies found
For what most nodes need - the agent - there is a snap
$ snap find telegraf
Name Version Publisher Notes Summary
telegraf 1.30.0 sajoupa classic Telegraf agent
Or people would often use container images instead.
The package as-is without much more investment is really is more misleading than helpful.
Agreed to remove.
And it is currently no more building from source in noble which is a state cleaned up towards the release.
While there would be a fix for the build, the removal seems more appropriate in this case.