Dear all,
You are kindly invited to the meeting:
Fedora CI SIG on 2021-02-24 from 09:30:00 to 10:00:00 America/Chicago
At fedora-ci(a)irc.freenode.net
The meeting will be about:
Fedora CI SIG meeting
More information available at: https://fedoraproject.org/wiki/SIGs/CI
Introduce projects, discuss issues and plans for the future.
Please add topics to discuss into our etherpad: https://etherpad.gnome.org/p/fedora-ci
This meeting is recurring for every other Wednesday.
Source: https://apps.fedoraproject.org/calendar/meeting/9901/
Hello folks,
Our cloud provider plans to do maintainance operation on 2021-02-11 from
14:00 to 18:00 UTC.
Service interruption is expected, including:
- Zuul CI not running jobs for pagure.io or src.fedoraproject.org.
- Change in provided zuul-jobs roles.
We expect that the interruption of services will be less than 4 hours.
Regards,
Nicolas , on behalf of the Software Factory Operation Team
Attendees: jimbair, msrb, tflink, bgoncalv
Meeting log:
https://meetbot.fedoraproject.org/fedora-ci/2021-02-10/fedora_ci_sig.2021-0…
Items discussed:
1. Branching occurred, so rawhide is now f35
- Miro uploaded an f34 image to testing farm, so f34 should work now as
well
- Worth noting but not impacting, but as announced last week, master
branches are now main branches
Pretty light meeting today; reminder that we have it at the same time every
two weeks, so if you have a question or problem with fedora CI, come ping
us in freenode in #fedora-ci or drop into our next meeting.
Thanks!
-Jim
Dear all,
You are kindly invited to the meeting:
Fedora CI SIG on 2021-02-10 from 09:30:00 to 10:00:00 America/Chicago
At fedora-ci(a)irc.freenode.net
The meeting will be about:
Fedora CI SIG meeting
More information available at: https://fedoraproject.org/wiki/SIGs/CI
Introduce projects, discuss issues and plans for the future.
Please add topics to discuss into our etherpad: https://etherpad.gnome.org/p/fedora-ci
This meeting is recurring for every other Wednesday.
Source: https://apps.fedoraproject.org/calendar/meeting/9901/
Hello folks,
Our cloud provider plans to do maintainance operation on 2021-02-08 from
14:00 to 18:00 UTC.
Service interruption is expected, including:
- Zuul CI not running jobs for pagure.io or src.fedoraproject.org.
- Change in provided zuul-jobs roles.
We expect that the interruption of services will be less than 4 hours.
Regards,
Nicolas , on behalf of the Software Factory Operation Team
[resend, since the first one seems to have gotten stuck permanently in the moderation queue]
Hi,
I would like to make the CI pass for systemd builds. I added an rpminspect.yaml file [1]
to disable a bunch rpminspect checks, and rpminspect passes now. But I'm stuck on
rpm-install-test, which dutifully informs me that
> package systemd-247.2-3.fc34.x86_64 conflicts with
> systemd-standalone-tmpfiles < 247.2-3.fc34^ provided by systemd-standalone-tmpfiles-247.2-3.fc34.x86_64
Duh, no surprise, I added the Conflicts myself ;)
I do NOT want to disable the test completely. I am very much interested in CI catching the
case where packages cannot be installed or upgraded. I'd like just to either tell it that
it should ignore systemd-standalone-tmpfiles and systemd-standalone-sysusers, or ideally,
it would be able to guess on its own that if there are Conflicts between subpackages from
the same built, that is intentional and should be ignored.
I looked at the docs [2, 3], but I don't see anything relevant.
[1] https://src.fedoraproject.org/rpms/systemd/c/7e740c5252c3291d67def67d33e55b…
[2] https://docs.fedoraproject.org/en-US/ci/generic_tests/#_installability
[3] https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org/th…
Zbyszek