[releng] Issue #7031: Should f27 and f27-build have different architectures?
by Kellin
kellin reported a new issue against the project: `releng` that you are following:
``
$ koji taginfo f27
Tag: f27 [417]
Arches: armv7hl i686 x86_64 ppc64 ppc64le aarch64
^PGroups: appliance-build, build, livecd-build, livemedia-build, srpm-build
Required permission: 'admin'
Tag options:
mock.package_manager : 'dnf'
Inheritance:
$ koji taginfo f27-build
Tag: f27-build [425]
Arches: aarch64 armv7hl i686 ppc64 ppc64le s390x x86_64
Groups: appliance-build, build, livecd-build, livemedia-build, srpm-build
Required permission: 'admin'
Tag options:
This tag is a buildroot for one or more targets
Current repo: repo#785431: 2017-09-14 21:09:29.969602
Targets that build from this tag:
f27-candidate
f27-rebuild
f27-binutils-rebuild
f27
Inheritance:
0 .... f27-override [424]
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7031
5 years, 2 months
[releng] Issue #7612: moving fedora-release entirely to src.fp.o
by Zbigniew Jędrzejewski-Szmek
zbyszek reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
This is a continuation of the proposal made on fedora-devel late last year and repeated recently [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...].
The dicussion there didn't result in any decision, and @ausil recommended that it talk with releng directly.
I'd asking for the following:
- retirement of the seperate "upstream" for fedora-release, i.e. simply merge https://pagure.io/fedora-release/pull-request/119. This has to be done by one of the owners of that repo.
- the ability to build fedora-release. I probably can write to dist-git directly as proven packager, but I'm not sure if I can successfully build the package in koji. Either way, I'd prefer to be added as co-maintainer to make this official, and for any other changes that need to be made to be made.
- review of https://src.fedoraproject.org/fork/zbyszek/rpms/fedora-release/branch/dro.... I can't submit that as PR now, because PRs are disabled.
Stuff that I can do myself, once the above is done:
- enable PRs on src.fp.o/rpms/fedora-release
- resubmit the drop-upstream-split as PR, merge it once it's reviewed, and build
- resubmit other requests against fedora-release as PRs, e.g. https://pagure.io/fedora-release/pull-request/139 and others.
* When do you need this? A few days or a week would be great. Doing this will allow preset requests to be processed more quickly, making other things happen faster too.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7612
5 years, 4 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, 5 months