Hello everyone,
a new version of Pungi is available! The 4.1.17 build is ready to be
used. There are updates for F26 and F25 in Bodhi waiting to be pushed
to updates-testing.
This release brings an update to documentation. There is now
description of the configuration format, overview of what happens
during the compose and explanation of how packages are gathered and how
the process can be customized.
Bugs fixed and features added:
* Creating delta RPMs is fixed. If this makes a compose too slow,
just change createrepo_deltas option to False (the default).
* When package dependencies are not resolved, Pungi will still read
input packages from comps file.
* Environments in comps files can now be filtered by architecture.
* All command line parsers are ported to argparse.
* Improved logging of where packages in the compose are coming from.
Improvements for Ostree
* Multiple notification scripts can now be used, which turns it into
a hook callback system.
* A script is provided that will pause the compose until new ostree
commits are signed. To enable this, add
--notification-script=pungi-wait-for-signed-ostree-handler to the
pungi-koji command invocation.
* When creating the installer, Pungi ensures lorax runs on
non-existing directory to avoid errors.
Modularity improvements
* Multiple Koji tags can be used as source of packages.
* Use release number of a module.
And a few 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
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2017-07-17 from 09:30:00 to 10:30:00 US/Central
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/5873/
Hi all,
I would like to propose the following change to allowed_scms for our
koji config.
This change is intended to disallow building stuff from Pagure forks
once that gets in front of distgit.
The current patch is only for staging.
Basically, it adds the following to allowed_scms:
!src.fedoraproject.org:/forks/* !pkgs.stg.fedoraproject.org:/forks/*
!pkgs.fedoraproject.org:/forks/*
This is per the new Koji 1.13 allowed_scms exclude format[1].
Any opinions?
[1]: https://docs.pagure.org/koji/release_notes_1.13/#extended-allowed-scms-form…
Thanks,
Patrick
commit 5fb4a6a028b031a01ee0ab25f434ae2bf4ed7c1d (HEAD -> master)
Author: Patrick Uiterwijk <puiterwijk(a)redhat.com>
Date: Thu Jul 13 00:07:57 2017 +0200
Exclude forks from kojid allowed_scms
Signed-off-by: Patrick Uiterwijk <puiterwijk(a)redhat.com>
diff --git a/roles/koji_builder/templates/kojid.conf
b/roles/koji_builder/templates/kojid.conf
index 3229fd47a..4818f6755 100644
--- a/roles/koji_builder/templates/kojid.conf
+++ b/roles/koji_builder/templates/kojid.conf
@@ -60,7 +60,7 @@ pkgurl=http://kojipkgs.stg.fedoraproject.org/packages
{% if env == 'staging' %}
; A space-separated list of hostname:repository pairs that kojid is
authorized to checkout from (no quotes)
-allowed_scms=pkgs.stg.fedoraproject.org:/docker/*:false
pkgs.stg.fedoraproject.org:/rpms/*:false:fedpkg,sources
pkgs.stg.fedoraproject.org:/*:false:fedpkg,sources
pkgs.fedoraproject.org:/rpms/*:false:fedpkg,sources
pkgs.fedoraproject.org:/*:false:fedpkg,sources
pagure.io:/fedora-kickstarts.git:false
src.fedoraproject.org:/*:false:fedpkg,sources
+allowed_scms=pkgs.stg.fedoraproject.org:/docker/*:false
pkgs.stg.fedoraproject.org:/rpms/*:false:fedpkg,sources
pkgs.stg.fedoraproject.org:/*:false:fedpkg,sources
pkgs.fedoraproject.org:/rpms/*:false:fedpkg,sources
pkgs.fedoraproject.org:/*:false:fedpkg,sources
pagure.io:/fedora-kickstarts.git:false
src.fedoraproject.org:/*:false:fedpkg,sources
!src.fedoraproject.org:/forks/* !pkgs.stg.fedoraproject.org:/forks/*
!pkgs.fedoraproject.org:/forks/*
{% else %}
; A space-separated list of hostname:repository pairs that kojid is
authorized to checkout from (no quotes)
allowed_scms=pkgs.fedoraproject.org:/*:false:fedpkg,sources
pagure.io:/fedora-kickstarts.git:false
src.fedoraproject.org:/*:false:fedpkg,sources
pagure.io:/fork/*/fedora-kickstarts.git:false
ralph opened a new pull-request against the project: `releng` that you are following:
``
PDC: scripts to create product-releases.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/6903
Hi,
Pungi / Mash roadmap meeting -- 2017-07-13
Attendees: stickster, threebean, jcline, dustymabe, kushal, mboddu, bowlofeggs, mcurlej, sayanchowdhury, lsedlar, puiterwijk
kushal: found that it would be hard to do just ostree generation from bodhi using pungi
dusty: I don't think this is true. All we have to do is provide repo URLs for the repos that
were just mashed. I have a pungi config that can accept repo URLs and create ostrees
already - we can use a url like this for the repo: https://kojipkgs.fedoraproject.org/mash//updates/f26-updates-testing-170712…
mcurlej: In middle of work on pungi -- hope to have something to demo next week
* pungi config is only coded for RHEL at the moment, but working on that
* threebean: mcurlej work on pungi masher doesn't replace the bodhi masher -- bodhi masher would still respond to push requests, but pungi masher would do modules and... ?
* [threebean] - that's about it. The motivation behind separating them was so that we wouldn't risk any major changes to the mainline bodhi masher while working on the module support.
Questions
* kushal: Can we use pungi currently with a config file to do a normal mash?
* [threebean] Yes, we think so -- if we need to shell out to pungi-koji for mainline compose, so be it. Would be good to make that a jinja2 template to make it more flexible
* Note: Bodhi does understand jinja2 templates
* Can Pungi make drpms?
* [pfrields] And if it can, can this process avoid the long delay associated with drpms when we create trees? (i.e. parallelize or a spinoff process?) -- IIRC this is one of the most costly parts of the process
* Not currently; it is an option in createrepo_c and bodhi currently does it with mash (which has createrepo_c?)
* https://pagure.io/pungi/issue/344
* Can Pungi make updateinfo.xml?
* AFAIK no. Bodhi right now inserts updateinfo.xml after masher is done creating the repo. (This feature is kept same in the WIP PR from kushal).
* if we are running a pungi compose for updates-testing what tag do we need to pull from?
* f25-updates-testing
*
* if we are running a pungi compose for updates what tag do we need to pull from?
* f$version-updates(-testing)
* This tag is defined in bodhi's DB in the release table (for each release).
Blockers for this effort:
* We believe there is an issue where pungi does not create deltarpms (some issue with createrepo_c)
* https://pagure.io/pungi/issue/344
Action Items:
* Lubos: We need https://pagure.io/pungi/issue/344 fixed, or some other way to get drpms into a pungi-composed bodhi repo
* Randy: will verify that updateinfo.xml can be generated separately
* Kushal: schedule a sync time next week (invitees TBD, probably don't need everyone)
* Dusty, Randy, Kushal: Get Bodhi staging able to mash with pungi. (build a pyramid together, no pun intended)
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.inhttps://dgplug.org
jforbes reported a new issue against the project: `releng` that you are following:
``
The change is to stop building the i686 kernels, and produce kernel-headers packages only. This will no impact the build of any other package as i686, but will mean no more bootable images.
Change page for review: https://fedoraproject.org/wiki/Changes/Stop_Building_i686_Kernels
Owner: @jforbes
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6894
dustymabe opened a new pull-request against the project: `pungi-fedora` that you are following:
``
atomic: use new json file name
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/295
dustymabe opened a new pull-request against the project: `pungi-fedora` that you are following:
``
f26: atomic: move to new versioning scheme for ostree
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/245