exactly. "you had permissions, you misused them. you're baaaaaad ! who's bad ? YOU'RE BAD !"

For anyone that has been waiting for Fedora 45 builds, I just pushed

openvox-agent-9.3.0.11.g88bb9eb35-1.fc45.x86_64.rpm

and

openvox-agent-9.3.0.11.g88bb9eb35-1.fc45.aarch64.rpm

to our testing repositories. This repo can be configured by installing the following package: s3.osuosl.org/openvox-artifacts/repo_test/yum/openvox9-release-fedora-45.noarch.rpm The testing repo is volatile, so the package might blink out of existence if we need to test something else. But, if anyone is able to test that build and provide feedback, it will be much appreciated and could help us address issues before the first full Fedora 45 build ships!

I wonder if that's really a temporary problem

all other pass, only the two ubuntu 22 fail.

Gooood evening

alaunay: Ubuntu/Debian containers had/have dns issues today

@Vadym Chepkov nice, you are a maintainer now

bastelfreak: ok. I guess I'll retry tomorrow then

darn. well. I am working on puppet-yum fix. we now have freaking different centos 10 and the other epel 10 sigh

:(

It is getting out of hands

$ rpm -ql mock-core-configs|grep -c /etc
515

If you want I can split these in two parts, but they seems go together github.com/voxpupuli/puppet-yum/pull/405

Those Redhat/epel changes are so annoying

indeed

ugh. something failed. 👀

damn, they put packages in different repos facepalm

Had to modify tests, 10 versionlock is different and I dropped 7 checks, it's not in metadata

green now

--2026-11-05 234031-- https://apt.voxpupuli.org//openvox9-release-ubuntu22.04.deb

Resolving apt.voxpupuli.org (apt.voxpupuli.org)... failed: Temporary failure in name resolution.

I find this quite surprising in duration, while deb12 goes like a breeze, ubuntu 22.04 still does not resolve that

could there be some kind of trouble with beaker ?

https?

nm, slack just made the link http by default

http or https anyway, it just cannot resolve the name

Yeah, I don't know what's up with that

Maybe it doesn't like the double slash for some reason?

Which, yes, shouldn't have to do with name resolution, but I've seen weirder bugs in puppet tooling

I'll call it a night and check again in the morning, maybe it will magically work