[releng] Issue #7933: f30-tinyxml2 side tag
by Igor Gnatenko
ignatenkobrain reported a new issue against the project: `releng` that you are following:
``
### For which release?
f30
### Name of the side tag? (Generally fxx-pkg)
f30-tinyxml2
### Number of builds that are expected in the side tag?
7
### How long do you need the side tag?
Few days.
### Any extra information?
None.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7933
5 years, 6 months
[releng] Issue #7934: 20181126: Release Fedora 29 Atomic Host
by Michael Nguyen
mnguyen reported a new issue against the project: `releng` that you are following:
``
You should be able to do it with this command:
`python push-two-week-atomic.py -k fedora-29 -r 29 --pungi-compose-id Fedora-29-updates-20181126.0`
`Note:`
We won't need to use options --compose-basedir and --first-release from this release onward.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7934
5 years, 6 months
[releng] Issue #7568: Tag fedora-kickstarts (and fedora-comps?) repo for
candidate composes
by Adam Williamson
adamwill reported a new issue against the project: `releng` that you are following:
``
So, I recently floated a proposal to remove the release criterion that requires a spin-kickstarts package that corresponds to the kickstarts used to create the release be included in the release. This has met with a generally positive response, but before I go ahead with it, I think we should ensure the proposed replacement is done already.
That idea is, every time a candidate compose is done, a tag should be created in the fedora-kickstarts repo with the compose's ID (and/or label). That way it's easy to get the correct kickstarts that match the compose: just check out the tag.
We could also do this for *nightly* composes, I guess, it just depends whether creating tons of tags causes any problems for git - I don't know if it does or not.
We could also tag the fedora-comps repo, possibly; it's less important in that case as the actual generated comps automatically become a part of the compose itself, but could still be useful.
Ideally this should be a part of the scripts that produce the compose, it should not be a manual step that the person doing the compose has to remember to do, as of course that introduces the possibility that they won't.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7568
5 years, 6 months
[releng] Issue #7927: f30-protobuf side tag
by Igor Gnatenko
ignatenkobrain reported a new issue against the project: `releng` that you are following:
``
## For which release?
F30.
## Name of the side tag? (Generally fxx-pkg)
`f30-protobuf`
## Number of builds that are expected in the side tag?
~20
## How long do you need the side tag?
Week or two.
## Any extra information?
No.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7927
5 years, 6 months
[release] pungi 4.1.31
by Lubomír Sedlář
Hello everyone,
a new version of Pungi is available! The 4.1.31 build is ready to be
used. There are updates waiting in Bodhi to go to updates-testing.
The main change for Fedora in this release is that phase ordering is
tweaked to run ostree sooner in the process. This should make composes
a little faster. This was actually tested before, but did not work
due to bugs in the entire stack. Those should now be fixed.
The files created in Koji runroot environment are now changed to be
owned by the user running process. This should simplify cleanup of
old composes in Bodhi.
Handling configuration files is refactored.
* Pungi can now read a JSON config file.
* There is a script pungi-config-dump that can dump configuration
from a compose or merged multiple files.
* Copies of config in the logs/ directory are no longer renamed.
* Dump of config in JSON format now has a predictable name without
a timestamp.
Refer to the documentation [0] for details on what configuration
options are available.
[0] 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
5 years, 6 months
[releng] Issue #7928: Untag request: glibc-2.28.9000-18.fc30 from rawhide
by Florian Weimer
fweimer reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
glibc malloc seems to be broken and rebuilding glibc fails on i686. glibc-2.28.9000-17.fc30 appears to be fine.
* When do you need this? (YYYY/MM/DD)
As soon as it is convenient.
* When is this no longer needed or useful? (YYYY/MM/DD)
Unclear.
* If we cannot complete your request, what is the impact?
Rawhide development is severely impacted.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7928
5 years, 6 months