[release] Pungi 4.2.8
by Ondrej Nosek
Hello everyone,
Pungi development team is pleased to announce the availability of Pungi
4.2.8. The updates for F32 and F33 are waiting in updates-testing repo.
Others (Rawhide, F34) are already in stable repo
Main changes:
A new version of Pungi is available and installable from RCM Tools
compose and repositories.
Here are the major changes:
* Added image-container phase. This phase runs after image-build and
osbuild and can embed an image into a container.
* Added ability to wait for signed packages. If packages are appearing
quickly in Koji, and signing them is triggered by automation, there may be
a delay between the package being signed and compose running. In such case,
it may be preferable to wait for the signed copy rather than fail the
compose.
* Include just one version of module. When adding extra modules via option
*pkgset_koji_module_builds*, all other versions of the same stream
potentially available in a Brew tag should be skipped.
* Remove reuse file when packages are not signed. In such case, we never
want to reuse the pkgset, as it risks leaking unsigned packages. The safest
option is to remove the file completely.
* Preserve default arg on groupid. When the wrapper processes comps file,
it wasn't emitting "default" argument for groupid element. The default is
false and most entries are actually using the default, so let's only emit
it if set to true.
* Stopped copying .git directory with module defaults. This will
potentially speedup full cloning of big repositories.
* Dropped usage of kobo.plugins
... and other minor fixes
Refer to the documentation [1] for details on what configuration
options are available.
[1] https://docs.pagure.org/pungi/index.html
If you encounter problems or need general help, stop by #fedora-releng
IRC channel or file issues in Pagure.
Happy composing!
Compose team
_______________________________________________
rel-eng mailing list -- rel-eng(a)lists.fedoraproject.org
To unsubscribe send an email to rel-eng-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/rel-eng@lists.fedoraproject...
2 years, 1 month
Guardrails for too-short RC-to-Go/No-Go
by Ben Cotton
Hi everyone,
In Friday's Go/No-Go meeting, we decided that having 5 hours between
the completion of an RC and the start of the Go/No-Go meeting is not
the ideal situation. So I got assigned the homework of starting the
conversation about how to prevent this in the future. After all, if we
don't stop ourselves from doing it, the temptation will be there.
Since this is going to multiple mailing lists, I ask that the
conversation happen in this Discussion thread to make sure we're all
talking in one place:
https://discussion.fedoraproject.org/t/guardrails-for-too-short-rc-to-go-...
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 1 month
F34 Final Go/No-Go moved to Friday
by Ben Cotton
Hi everyone,
Since we anticipate a Fedora Linux 34 release candidate request today,
I am moving the Go/No-Go meeting from Thursday to Friday. This will
allow the QA team more time to perform validation tests.
The Fedora Linux 34 Final Go/No-Go[1] meeting is scheduled for Friday
23 April at 1700 UTC in #fedora-meeting-1. At this time, we will
determine the status of F34 for the 27 April target date. For more
information about the Go/No-Go meeting, see the wiki[2].
[1] https://calendar.fedoraproject.org/meeting/9969/
[2] https://fedoraproject.org/wiki/Go_No_Go_Meeting
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
2 years, 1 month