On 2024-10-03 22:59:42, Daniel Swarbrick wrote: > I think you know as well as I do that the likelihood of this being > feasible is pretty remote.
I know, but i think it's worth, if not trying, at least keeping track of how and why it's not possible. :) > The fact that sufficient versions of npm, nodejs and React are already > available in Debian does not help much if the web app uses a ton of > bleeding edge modules which are not even on anybody's radar to package > for Debian. Combine that with the fact that the Prometheus web UI is > getting yet another major overhaul for v3.0.0. It seems to be a > fast-moving target. Yeah, I'm kind of hoping they stop doing that already with the v3. But i will note that people *are* trying to keep up with a lot of modules like this for other projects, and I think it's actually possible to give it a try already. I would also argue *for* vendoring the stuff that's not practical to package. We have a few special precedents in Debian for important packages that have bent the rules a little bit to ship vendored copies of source code (firefox and kubernetes, for example), and I think we could get away with shipping a couple javascript libraries like this. > The classic web UI was actually removed upstream in v2.34.0, and I have > forward-ported / reinstated the necessary Go code to keep supporting it. > This is a dead end however, since Prometheus has newer functionality > like exemplars and native (sparse) histograms, which are not supported > by the legacy web UI. I would prefer to see the Debian package finally > drop the classic UI also, since the Debian package is starting to > resemble more of a /fork/ of Prometheus. Yep, this is mainly why I've opened that issue, actually. > You may have noticed that I recently added an install-ui.sh helper > script to the prometheus package, to fetch the React web UI tarball from > upstream, similar to the script that is bundled with > prometheus-alertmanager. So you /can/ use the React web UI now, if you want. Yes, I've seen that! I have even tried it out, but it didn't work out so well for me, something which could perhaps be filed as a separate bug. > If you're willing to pitch in and help package the React UI, by all > means, please do. I will be honest and admit this is a request more than an offer, but I *might* get time to deal with this in the coming *year* (aka "2025", definitely not until January), so I wanted to see if there was at least *some* openness in dealing with it. Also, we're not alone with this: there's a bunch of people working on JavaScript stuff in Debian, and we could get some help there. So the question is: do we, as a golang team (and you, as an uploader for this package), want to do this? Or do we want to fundamentally object to even trying to fix this issue? Because this is essentially why i filed this issue: I don't expect anyone to just drop everything and do this. I want to see if people are okay with us trying to do this. Thanks for considering my request, in any case! :) A.
