nphilipp reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The `9.6` stream branch of the `postgresql` module is inactive, probably because it's past its EOL date which was set to 2018-12-01 when it was created. The maintainer of the module @praiskup reported this to the [Modularity Tracker](https://pagure.io/modularity/issue/123).
Two possible remedies come to mind:
- Manually set the `bug_fixes` (and `security_fixes`?) EOL date for the `modules/postgresql:9.6` branch to 2021-12-01, corresponding with the upstream EOL date of 2021-11-11.
- Or, ignore the SL metadata when determining which branch is active ([background](https://pagure.io/modularity/issue/124#comment-549423), [#2](https://pagure.io/modularity/issue/112)). This probably involves changes in code/scripts.
* When do you need this? (YYYY/MM/DD)
I assume the sooner the better. @praiskup?
* When is this no longer needed or useful? (YYYY/MM/DD)
End of 2021 when 9.6 maintenance ceases upstream.
* If we cannot complete your request, what is the impact?
The `9.6` stream can't be updated.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8057
fivaldi opened a new pull-request against the project: `releng` that you are following:
``
Use Fedora 29 for Vagrant
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/8075
mohanboddu opened a new pull-request against the project: `releng` that you are following:
``
Mass rebuild modules
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/8082
vondruch reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
js=jquery2
* FAS username of the new maintainer?
vondruch
* Branches that you need it to be unretired for?
f30
* Package re-review BZ URL?
Non. I hope I made it in two weeks.
* Any extra information?
If somebody is going to dispute this unretirement, I will bundle js-jquery2 in rubygem-jquery-rails:
https://src.fedoraproject.org/rpms/rubygem-jquery-rails/blob/master/f/rubyg…
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8035
sharkcz reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The installer runtime image (install.img) created by lorax is 2GB in size, the content written there by lorax fits into the 2GB space, but there isn't enough free space for anaconda in runtime. As a result the installation on ppc64le crashes. See https://bugzilla.redhat.com/show_bug.cgi?id=1666298
One possible solution is to explicitly set a bigger rootfs size for ppc64le compose similarly to what is done for cloud images in the Fedora pungi config.
* When do you need this? (YYYY/MM/DD)
ASAP
* When is this no longer needed or useful? (YYYY/MM/DD)
N/A
* If we cannot complete your request, what is the impact?
non-installable ppc64le compose
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8059
mprahl reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Instead of creating a fork, I created the branches `pungi-dep` and `pungi-dep2` on the rpms/module-build-service dist-git repo in preparation for a PR. Could you please remove them?
* When do you need this? (YYYY/MM/DD)
Whenever there is time. This is not urgent at all.
* When is this no longer needed or useful? (YYYY/MM/DD)
N/A
* If we cannot complete your request, what is the impact?
No real impact. This is just a cosmetic fix.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8055
mizdebsk reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Presence of [rawhide-repo-holder](https://koji.fedoraproject.org/koji/buildtargetinfo?ta… build target in Koji makes kojira generate repos for [rawhide](https://koji.fedoraproject.org/koji/taginfo?tagID=197) tag, which according to @puiterwijk is not used any longer.
* When do you need this? (YYYY/MM/DD)
earliest convenience
* When is this no longer needed or useful? (YYYY/MM/DD)
* If we cannot complete your request, what is the impact?
Koji resources are wasted generating unneeded repos.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7664
sharkcz opened a new pull-request against the project: `pungi-fedora` that you are following:
``
set installer image size to 3GB on ppc64le
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/684
jmontleon reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
These requests for epel7 and f29 were closed invalid with, "The branch in PDC already exists"
https://pagure.io/releng/fedora-scm-requests/issue/9556https://pagure.io/releng/fedora-scm-requests/issue/9557
The branches don't exist in dist-git and can't be pushed:
https://src.fedoraproject.org/rpms/python-openshift/branches
* When do you need this? (YYYY/MM/DD)
Next several days
* When is this no longer needed or useful? (YYYY/MM/DD)
N/A
* If we cannot complete your request, what is the impact?
I think someday it will delay RDO, but I'm not aware of any pressing date. They asked for us to release the package in Fedora/EPEL.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8090