Upgrade to bullseye/bookworm blocked due to T332015. @MoritzMuehlenhoff, can I help you to get poolcounter-prometheus-exporter imported to bullseye and/or bookworm (preferably both)?

@Dzahn iirc you were able to do some reprepro magic recently? If not I can give it a go but it's been a LONG time

Well, if it was a simple case of just copying it from one distro to another, like for something that is just static files, I could do that with reprepro. But this doesn't seem to be such a case.

This looks like Go code that builds to a binary and needs a Go environment.

There is history about the naming at T239688 and an abandoned patch at https://gerrit.wikimedia.org/r/c/operations/debs/poolcounter-prometheus-exporter/+/553736

There was only one release in 2019 https://gerrit.wikimedia.org/r/q/project:operations/debs/poolcounter-prometheus-exporter

Maybe the initial releaser is still most familiar, but it's been a long time for all it looks: https://gerrit.wikimedia.org/r/c/operations/debs/poolcounter-prometheus-exporter/+/552572/1/debian/changelog

Oh, I see that the prod poolcounter hosts are also still running Buster. Is someone tasked with fixing that?

That would be T332015 and a question for the serviceops team.

@Andrew Good news, see T332015#10035989

Oh, great. @Southparkfan does that unblock you here?

Found this from T332015 and a simple question on my side is, does anyone know why this VM needs to exist? Aside from "this is how it is in production", which given T215217 (5+ years without a workable resolution), isn't a very good answer.