[06:35:05] FYI, I [06:35:14] FYI, I'm rebooting bast6003 shortly [06:50:28] I'm also rebooting bast2003 shortly [14:28:13] hi moritzm, I wanted to ask, could it be that there is a component repository with backport https://apt.wikimedia.org/wikimedia/dists/bookworm-wikimedia/component/jdk21/, but no debianisation repo for it? i'm looking for a right place to put jdk25 for bookworm.. [14:32:00] hi, what do you mean with debianisation repo? [14:32:21] and we can't simply build Java 25 for Bookworm, each JRE release needs to be bootstrapped with the preceding release [14:32:34] there is openjdk-25 in trixie if needed by any setup [14:38:23] moritzm: thanks! we tried going with Java 25 on trixie, but we run into the problem with flink dependencies not being compatible with python 3.13: grpcio-tools==1.62.1 is not compatible with it and the next working version is 1.67 [14:39:46] we now exploring our options: keep flink on bookworm/python3.11/java21, bring java 25 on bookworm, bring python 3.11 on trixie, fix the dependencies for flink to work with newer grpcio-tools [14:42:50] I would suggest to focus on fixing the deps for grpcio-tools, introducing a forward port of OpenJDK is a massive undertaking [14:44:13] thanks for the input, I didn't know it will be a big problem, we will go with fixing the software to work with trixie [14:45:09] ok! [15:15:48] dpogorzelski: https://gerrit.wikimedia.org/r/c/operations/docker-images/production-images/+/1260656 all these changelog entries have wrongly formatted footers (maintainer name and email, see https://manpages.debian.org/testing/dpkg-dev/deb-changelog.5.en.html) which leads to multiple warnings from docker-pkg. Would you mind fixing please? [15:20:03] .oO (should docker-images gain a git hook / some CI to check for changelog errors? We keep having this issue) [15:20:28] be my guest :) [16:17:12] I don't actually know where to start with adding gerrit CI checks for new repos :-/ [16:22:07] Emperor: I keep meaning to have a chat with dduvall about easy ways to try doing kokkuri-in-gerrit [16:56:31] cdanis: that would be cool. it's something i've been thinking about as well as we push the Zuul v14 boulder up the hill. there's a GitLab specific layer in the Kokkuri repo but it mostly just binds GitLab CI variables to kokkuri ones and "under the hood" kokkuri is a CLI with few GitLab specifics (though I'm sure there's some coupling that would need to be adapted) [16:59:39] Emperor: zuul(v2)/jenkins based ci for gerrit repos is managed centrally. the project would need an entry at https://gerrit.wikimedia.org/r/plugins/gitiles/integration/config/+/refs/heads/master/zuul/layout.yaml#3694 for jobs to be scheduled. it looks like other `docker-images` repos have just a standard `tox` job which might make sense for that repo as well [18:15:56] hmm, trying to remember.. was there anything specific I should think of before switching an IP in netbox from "reserved" to "active" or is there really not much to it and "active" is the same as was adding them to the zones before we used netbox and that's that [18:20:08] mutante: I _think_ it needs to be active and then the cookbook needs to be run for the changes to be effective? I am not very sure but that's how I have done it at least [18:20:16] especially because if you add a new IP, the default is Active? [18:20:48] sukhe: I already added a bunch of VIP IPs but only as "reserved" [18:20:58] now thinking to just activate them [18:21:12] for gitlab that is [18:21:41] some things are merged, some are not, just want to unblock things [18:22:21] ACK, well, let me try with one and run cookbook [18:39:16] Emperor late to the party, but we have a gitlab CI pipeline for our opensearch plugins at https://w.wiki/PQ59, I'd be interested in helping to get changelog formatting into CI as well