[pungi-fedora] Issue #740: composeinfo file in Fedora Rawhid
by Mike Boswell
mboswell reported a new issue against the project: `pungi-fedora` that you are following:
``
We started having Beaker import issues around July 17th. There seems to be a mismatch in the .composeinfo file and the compose. I was able to successfully import secondary Rawhide w/ the following edit:
[variant-Everything]
-arches = ppc64le,s390x
+arches = ppc64le,i386,s390x
id = Everything
name = Everything
type = variant
Below was the error prior to manual edit of composeinfo.
[root@fedmsg fedmsg]# beaker-import --dry-run --lab-controller=http://lab-02.rhts.eng.bos.redhat.com:8000 http://download.eng.bos.redhat.com/fedmsg/dumpdata/secondary/Fedora-Rawhi... ftp://download.
eng.bos.redhat.com/fedmsg/dumpdata/secondary/Fedora-Rawhide-20190725.n.0 nfs://aoe-cluster.lab.bos.redhat.com:/ibm/exports/fedmsg/dumpdata/secondary/Fedora-Rawhide-20190725.n.0
2019-07-26 15:29:27,072 root INFO Dry Run only, no data will be sent to beaker
2019-07-26 15:29:27,205 root INFO Attempting to import: http://download.eng.bos.redhat.com/fedmsg/dumpdata/secondary/Fedora-Rawhi...
2019-07-26 15:29:27,226 root INFO Attempting to import: http://download.eng.bos.redhat.com/fedmsg/dumpdata/secondary/Fedora-Rawhi...
2019-07-26 15:29:27,273 root INFO Fedora-Rawhide-20190725.n.0 Everything ppc64le added to beaker.
2019-07-26 15:29:27,293 root INFO Attempting to import: http://download.eng.bos.redhat.com/fedmsg/dumpdata/secondary/Fedora-Rawhi...
2019-07-26 15:29:27,367 root CRITICAL No section: 'images-i386'
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/740
5 days, 16 hours
[releng] Issue #8569: Side tag for llvm rebase in Rawhide
by Tom Stellard
tstellar reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
We need a side tag (f31-llvm) for the upcoming llvm rebase in Fedora
* When do you need this? (YYYY/MM/DD)
07/29/2019
* When is this no longer needed or useful? (YYYY/MM/DD)
08/29/2019
* If we cannot complete your request, what is the impact?
Temporary breakage in rawhide when the LLVM rebase occurs.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8569
2 months, 3 weeks
[releng] Issue #8664: Module mass-rebuild for F32 Rawhide needed
by Stephen Gallagher
sgallagh reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
At the Branch point, we need to perform a mass-rebuild of modular content so that they can be rebuilt against the new base module (in this case `platform:f32`). This does not seem to have happened during the F31 Branch from Rawhide, as https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-2019082... shows only those modules whose maintainers have done a manual rebuild since the Branch.
* When do you need this? (YYYY/MM/DD)
Immediately (2019-08-21)
* When is this no longer needed or useful? (YYYY/MM/DD)
When F32 goes EOL
* If we cannot complete your request, what is the impact?
Upgrade path on Rawhide will be broken for anyone with modules enabled. (That means pretty much everyone at this point).
CC @kevin
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8664
2 months, 3 weeks
[releng] Issue #8702: F31 stable push requests
by Adam Williamson
adamwill reported a new issue against the project: `releng` that you are following:
``
This ticket will be used for requesting pushes of tested blocker / freeze exception fixes during F31 release freezes. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process . Similar to candidate compose request tickets, this ticket can be closed by releng after each push and re-opened by QA each time a new push is needed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8702
2 months, 3 weeks
[releng] Issue #8684: Create F32FTBFS and F32FailsToInstall Bugzilla trackers
by Miro Hrončok
churchyard reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
According to the Fails to build and Fails to install policy, we need new Buzgilla trackers for Fedora 32.
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai...
* When do you need this?
After Fedora 31 was branched (already happened).
* When is this no longer needed or useful?
When Fedora 32 goes EOL.
* If we cannot complete your request, what is the impact?
We cannot properly track F32 install and build failures.
----
I know I can create the bugizllas myself, but last time i did, it created confusion during teh mass rebuild. So I'd prefer if releng creates them. It also looks better if the trackers are created by the releng account.
Thanks
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8684
2 months, 4 weeks
[releng] Issue #8468: fedora-scm-requests new repository procedure
repeatedly keeps the repo owned by the releng person
by Miro Hrončok
churchyard reported a new issue against the project: `releng` that you are following:
``
1. I've create a new repository request, where something was wrong
2. @limb processed the request, closed as invalid
3. I fixed the thing and reopened the issue
4. @limb processed the request, closed as invalid again (already exists)
5. as a result, the repo was created, but owned by @limb
This is probably broken in some script that @limb runs, it probably creates the repo, checks some constraints and assigns the repo to me. When the constraints fail, the repo exists, but is not assigned to me. I cannot provide more details, because I have no idea what happens "on the other side".
This already happened twice to me:
https://pagure.io/releng/fedora-scm-requests/issue/10716
https://pagure.io/releng/fedora-scm-requests/issue/13178
In both cases, the branch was set to epel7 and initial_commit to false, if that makes any difference.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8468
2 months, 4 weeks