mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Config and script to generate modular build repos using overrides
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/777
mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Fedora Minimal Compose for OpenQA testing
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/598
kellin opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Add post-compose rsync script
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/438
walters opened a new pull-request against the project: `pungi-fedora` that you are following:
``
WIP: Add fedora-atomic-ws config
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/502
tstellar reported a new issue against the project: `pungi-fedora` that you are following:
``
The i686 packages for compiler-rt are no longer available in the x86_64 repositories starting with Fedora 27. Could you mark this package as multilb.
See https://bugzilla.redhat.com/show_bug.cgi?id=1513286
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/501
dustymabe opened a new pull-request against the project: `pungi-fedora` that you are following:
``
cloud: remove s390x from image builds
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/731
kellin reported a new issue against the project: `pungi-fedora` that you are following:
``
The way we rsync composes today is a one-liner bash script that is not very durable and requires that a release engineer babysit it through the entire four hour rsync process.
I am going to make this more durable, however, it will also slightly change our process behind the scenes.
Today if a process works or is DOOMED after a full run it is assigned an RC release number. (EG: 1.1, 1.2, 1.3, etc). If the compose fails quickly from something such as a failure to have signed packages then it will not be assigned a release candidate.
Per @mohanboddu there is not a durable way to identify the all of the different ways the special case DOOMed composes occur so they will be assigned an RC number after the automation is deployed.
The only visible change will be extra gaps in the RC composes in /pub/alt/stage that represent these extra numbers being inserted to the sequence.
@mohanboddu is fine with this change; does anyone else have objections?
@ausil , @kevin , @puiterwijk please let me know. The initial script PR will be coming within the next two business days.
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/426
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2019-12-25 from 16:00:00 to 17:00:00 UTC
At fedora-meeting-2(a)irc.freenode.net
The meeting will be about:
Fedora Release Engineering weekly meeting
Source: https://apps.fedoraproject.org/calendar/meeting/9274/
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2019-12-18 from 16:00:00 to 17:00:00 UTC
At fedora-meeting-2(a)irc.freenode.net
The meeting will be about:
Fedora Release Engineering weekly meeting
Source: https://apps.fedoraproject.org/calendar/meeting/9274/