On Mon, Jan 20, 2025 at 7:26 AM Alexander Neundorf <neund...@kde.org> wrote:
> Hi Ben, > Hey Alex, > > On Sonntag, 19. Januar 2025 19:12:06 Mitteleuropäische Normalzeit Ben > Cooksley wrote: > > > On Mon, Jan 20, 2025 at 6:51 AM Julius Künzel <julius.kuen...@kde.org> > > > > > > wrote: > > > > 19.01.2025 18:44:40 Alexander Neundorf <neund...@kde.org>: > > > > > > > > Hi, > > > > > > > > I'm wondering whether the CI images are tagged along with the KF6 > > > > releases. > > > > > > > > I haven't seen tags here, but maybe I looked in the wrong place: > > > > > > > > https://invent.kde.org/sysadmin/ci-images > > > > > > > > I'm looking for that so that I could use e.g. the suse images tagged > with > > > > 6.8 to do development with KDE frameworks 6.6. > > > > > > > > Are they tagged and I didn't see it ? > > > > > > > > Would it make sense ? > > > > > > If we wanted to provide an "SDK" as it were that had everything needed to > > > build KDE software then you'd probably want that to be a separate, > > > dedicated image. > > > It certainly could be done though. > > basically that's what I'm aiming at. > > I'd like to keep duplicated work to a minimum, so if there is already a > dockerfile which works it would be nice to be able to reuse that in some > way. > You could probably build on top of the existing CI images - essentially starting from them and adding Frameworks on top. You might want to find something that is less of a moving target than SUSE Tumbleweed though as that is a rolling distribution. I got a full KF6 docker image using kde-builder working last November, I'm > trying to refresh that now. Unfortunately when trying to have that image > created automatically on quay.io it ran into a timeout. > > Having said that, building the suse image currently fails for me: > > podman build --tag kf6-qt69-image -f Dockerfile > ... > > ( 71/110) Installing: dbus-1-common-1.14.10-4.2.noarch [.. > /usr/sbin/useradd -r -c User for D-Bus -d /run/dbus -U messagebus -s > /usr/sbin/nologin > useradd: cannot open /etc/shadow > error: %prein(dbus-1-common-1.14.10-4.2.noarch) scriptlet failed, exit > status 1 > error: dbus-1-common-1.14.10-4.2.noarch: install failed > error] > Installation of dbus-1-common-1.14.10-4.2.noarch failed: > Error: Subprocess failed. Error: RPM failed: Command exited with status 1. > Abort, retry, ignore? [a/r/i] (a): a > Warning: %posttrans and %transfiletrigger scripts are not executed when > aborting! > See https://invent.kde.org/sysadmin/ci-images/-/blob/master/.gitlab-ci.yml?ref_type=heads#L1 for how we build the images in our environment. That error isn't something I've seen before i'm afraid - looks like a temporary issue in Tumbleweed perhaps so maybe one of the SUSE folks here can chime in? > > > > Thanks > > Alex > Cheers, Ben
