Hello everyone,
a new version of Pungi is available. The 4.2.5 build is ready to be used. There are updates pending for updates-testing repo.
These are the major changes:
* A new compose type was added: development. It is meant for non- production versions of the compose. This requires python-productmd
= 1.28, which has also been released today.
* Detection when package set results from previous compose can be reused has been improved. * Ability to include modules in the compose by exact NSVC was added. This mimics existing functionality for RPMs and allows testing modules before they are tagged for the compose. * The pungi-patch-iso has been improved to allow customizing temporary directory.
And a couple of other smaller 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!
Lubomír
On Fri, 2020-09-25 at 14:56 +0200, Lubomír Sedlář wrote:
Hello everyone,
a new version of Pungi is available. The 4.2.5 build is ready to be used. There are updates pending for updates-testing repo.
These are the major changes:
- A new compose type was added: development. It is meant for non- production versions of the compose. This requires python-productmd
= 1.28, which has also been released today.
How does it differ from the 'test' type?
Adam Williamson píše v Po 05. 10. 2020 v 14:40 -0700:
On Fri, 2020-09-25 at 14:56 +0200, Lubomír Sedlář wrote:
Hello everyone,
a new version of Pungi is available. The 4.2.5 build is ready to be used. There are updates pending for updates-testing repo.
These are the major changes:
- A new compose type was added: development. It is meant for non- production versions of the compose. This requires python-
productmd >= 1.28, which has also been released today.
How does it differ from the 'test' type?
Test can be confusing sometimes: it could mean a test of the tools, configuration or content. Development compose is meant to work similarly to production composes, but it's not supposed to be shipped anywhere.
The type has no effect on the content, it only changes the compose ID to make it easier to distinguish parallel compose lines for the same product.
Hope this helps, Lubomír
rel-eng@lists.fedoraproject.org