2024-06-23T11:05:42  <acidsys> calendar.i.o.o => Repository would be updated from 515377e to 88915f0, but there are uncommitted changes.
2024-06-23T11:05:59  <acidsys> LCP ^^
2024-06-23T11:06:36  <matrix-o-o> <LCP> what did I do again
2024-06-23T11:07:22  <acidsys> naughty local changes >:O https://paste.opensuse.org/pastes/8c85fdb9b876
2024-06-23T11:07:52  <matrix-o-o> <LCP> oh I see
2024-06-23T11:08:02  <matrix-o-o> <LCP> yeah, I will commit those to the repo first
2024-06-23T11:08:14  <acidsys> plsthx
2024-06-23T11:40:13  <acidsys> stonehat needs a bit to come back
2024-06-23T11:45:44  <matrix-o-o> <LCP> I should figure out why the calendar actioncable is broken
2024-06-23T11:46:27  <matrix-o-o> <LCP> I wonder how difficult it would be to set it up so that highstate sends a deployment info to the github repository
2024-06-23T11:47:00  <matrix-o-o> <LCP> something like https://github.com/openSUSE/open-build-service/deployments
2024-06-23T11:48:22  <acidsys> https://docs.saltproject.io/en/latest/ref/returners/all/index.html#all-salt-returners if one writes something that takes data from any one of these returners and writes whatever github wants then it can be done
2024-06-23T11:48:59  <matrix-o-o> <LCP> https://docs.github.com/en/rest/deployments/deployments?apiVersion=2022-11-28
2024-06-23T11:49:16  <matrix-o-o> <LCP> we could even mark failed highstates this way presumably
2024-06-23T11:50:36  <matrix-o-o> <LCP> idk if that's something that is possible though, haven't delved into it deeply enough
2024-06-23T11:53:11  <matrix-o-o> <LCP> meanwhile I fixed the repo and run highstate on calendar
2024-06-23T11:54:25  <acidsys> kewl
2024-06-23T12:07:37  <acidsys> stonehat is done now
2024-06-23T13:47:47  *** teepee_ is now known as teepee
2024-06-23T20:17:26  *** teepee_ is now known as teepee
2024-06-23T20:48:11  <cboltz> did someone grant vacation to our gitlab runners?
2024-06-23T20:48:26  <cboltz> I just merged some pending MRs, and all tests fail
2024-06-23T20:48:59  <cboltz> ERROR: Failed to remove network for build
2024-06-23T20:49:00  <cboltz> ERROR: Preparation failed: Cannot connect to the Docker daemon at unix:///run/podman/podman.sock. Is the docker daemon running? (docker.go:958:0s)
2024-06-23T21:00:04  <acidsys> Bodman[25212]: Error: database graph driver "" does not match our graph driver "overlay": database configuration mismatch
2024-06-23T21:04:05  <acidsys> it seems whereas in the past, the existance of /etc/containers/storage.conf caused all problems, now the lack of this file (and the relevant driver option https://github.com/containers/podman/issues/21683#issuecomment-1954016101) does.
2024-06-23T21:04:22  <acidsys> funnily enough, the file is now no longer provided by the package
2024-06-23T21:06:50  <cboltz> that's indeed funny...
2024-06-23T21:07:27  <cboltz> see also the last comment in that issue where someone changed the config inside the database
2024-06-23T21:07:33  <acidsys> I copied the one from /usr/share/containers/storage.conf, which has [storage] driver="overlay" but it does not seem to help
2024-06-23T21:12:53  <acidsys> ok, the "solution" is `rm -r /var/lib/containers/*`
2024-06-23T21:13:29  <acidsys> (maybejust deleting the database would be sufficient, but might as well ..)
2024-06-23T21:14:50  <cboltz> now I'm curious - does your "solution" also work if there's no storage.conf, or is that file needed?
2024-06-23T21:15:02  <acidsys> works without storage.conf
2024-06-23T21:15:30  <acidsys> also noted that in my issue comment
2024-06-23T21:18:02  <cboltz> ok, so at least no longer packaging storage.conf is ok
2024-06-23T21:18:18  <acidsys> yep
2024-06-23T21:19:22  * acidsys thinks maybe just maybe the ci/cd workers deploying your stable infra shouldn't be using a rolling distro
2024-06-23T21:19:32  <cboltz> I restarted one of the failed pipelines, and the first tests are green :-)  (others are still running)
2024-06-23T21:19:43  <acidsys> kewl