[16:22:47] jayme: it looks to me like you added the helm packages to our apt repo -- I'm seeing an interesting thing: [16:22:54] https://www.irccloud.com/pastebin/y5ecbRHZ/ [16:23:02] and yet, on a trixie host: [16:23:12] https://www.irccloud.com/pastebin/Q0jOxaC5/ [16:23:53] any idea what's happening there? Seems most likely that the repo just isn't configured right on the trixie host but it sure looks right to me. [19:02:44] andrewbogott: o/ helm is a virtual package, you can check via `apt-cache policy helm`, the right package should be helm3 [19:03:22] when you say 'you can check via' do you mean that apt-cache policy will tell me it's virtual? [19:03:39] (btw, helm3 wasn't available on Trixie either but I have now fixed that) [19:04:30] Um... to restate my question: is apt-cache policy actually different from apt policy? They produce the same response where 'helm' is concerned. [19:37:52] they should be the same andrewbogott, just different cli interfaces to the same data [19:54:40] then why... [20:00:49] andrewbogott: you're being tricked by that package being in a non-default component https://phabricator.wikimedia.org/P83516 [20:02:21] taavi: oh, I've long since solved the actual problem. The 'but why...' was wondering why Luca suggested that I run a command immediately under my pasting the results of that same command. Doesn't matter :) [20:10:07] andrewbogott: I thought for some reason that apt policy didn't report the fact that the package was virtual, this is why I suggested it [20:11:23] I see! You're right that it doesn't but neither command does. [20:11:59] apt-cache show helm would [20:12:19] andrewbogott: yep, I didn't mention it --^ [20:12:47] anyway, I am not sure if you solved your issue, hopefully yes and if I added more confusion sorry! [20:14:01] Yeah, I just copied the helm3 package from bookworm to trixie in reprepo. The virtual package thing does explain why 'helm' was in reprepro but didn't do anything on trixie though!