zlopez reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
I'm trying to reproduce issue https://pagure.io/fedora-infrastructure/issue/8150 in staging, but I'm now getting that package is retired, so the bugzilla issue creation is just skipped.
Could you unretire golang-github-MakeNowJust-heredoc on staging? It will help me to check if my fix is really working.
* When do you need this? (YYYY/MM/DD)
ASAP
* When is this no longer needed or useful? (YYYY/MM/DD)
When bugzilla is no longer a thing
* If we cannot complete your request, what is the impact?
I can't test if the issue with the-new-hotness is fixed and it could happen again in the future
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8763
adamwill reported a new issue against the project: `releng` that you are following:
``
Can we please have a candidate compose for Fedora 31 Beta?
There is one side package request for the compose:
== Blockers ==
* [kde-settings-31.0-1.fc31](https://bodhi.fedoraproject.org/updates/FEDORA-20… for [#1749086](https://bugzilla.redhat.com/show_bug.cgi?id=1749086)
Thanks!
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8781
mschorm reported a new issue against the project: `releng` that you are following:
``
Hello,
I'm contacting you as per Fedora changes Policy.
I prepared a proposal of a change about MariaDB 10.4 becoming the default MariaDB series in Fedora, instead of 10.3 which we have now.
https://fedoraproject.org/w/index.php?title=Changes/MariaDB_10.4
I don't expect any work for relengs there, however I'd be happy if you point out anything I missed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8783
pkfed reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
I was the original maintainer of fastbit and would like to unretire it. It seems that the problems I had building it were transient toolchain-related problems that have since been cleared. I have tested builds on F30, F31 and F32 and they are all clearing now:
F30: https://koji.fedoraproject.org/koji/taskinfo?taskID=37488573
F31: https://koji.fedoraproject.org/koji/taskinfo?taskID=37488336
F32: https://koji.fedoraproject.org/koji/taskinfo?taskID=37488566
Currently blocked are F31 and F32:
fastbit f31 releng [BLOCKED]
fastbit f32 releng [BLOCKED]
* When do you need this? (YYYY/MM/DD)
* When is this no longer needed or useful? (YYYY/MM/DD)
* If we cannot complete your request, what is the impact?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8760
adamwill reported a new issue against the project: `pungi-fedora` that you are following:
``
See https://bugzilla.redhat.com/show_bug.cgi?id=1734179 . That's a Fedora 31 blocker because an uninstallable package gets pulled into the Server DVD...but the package probably doesn't really need to be on the DVD at all. It's being included because in `fedora.conf` we list `dracut*` in `additional_packages`, which pulls in not just all the subpackages of the dracut .src.rpm itself but various other packages whose name starts with `dracut`, some of which we probably don't really want to pull in at all.
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/issue/759
jankratochvil reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
I was asked in https://bugzilla.redhat.com/show_bug.cgi?id=1749556 to create an EPEL8 branch for package inotify-tools.
.../fedora/inotify-tools/master$ fedpkg --user jankratochvil request-branch epel8
Could not execute request_branch: The following error occurred while creating a new issue in Pagure: Invalid or expired token. Please visit https://pagure.io/settings#nav-api-tab to get or renew your API token.
For invalid or expired token refer to "fedpkg request-repo -h" to set a token in your user configuration.
$ cat ~/.config/rpkg/fedpkg.conf
[fedpkg.pagure]
token = 3JU...ESQ
I have created multiple tokens, with all or just one of the rights and it is still the same.
* When do you need this? (YYYY/MM/DD)
sometimes soon
* When is this no longer needed or useful? (YYYY/MM/DD)
N/A
* If we cannot complete your request, what is the impact?
There will be no inotify-tools for EPEL8.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8762
ngompa reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
`ipsilon`
* FAS username of the new maintainer?
`ngompa`
* Branches that you need it to be unretired for?
`f31`, `master`
* Package re-review BZ URL?
N/A
* Any extra information?
It was just retired in [RH#1741099](https://bugzilla.redhat.com/show_bug.cgi?id=1741099) as ipsilon now is py3 compatible and works in f31+ in git master
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8713
spot reported a new issue against the project: `releng` that you are following:
``
gstreamer also needs to be unretired and assigned to me. The fix is identical to gstreamer-plugins-base (disable gtk-doc generation). Hasn't been dead 8 weeks.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8764
kalev reported a new issue against the project: `releng` that you are following:
``
I'd like to get koji admin access, similar to https://pagure.io/releng/issue/8142 where ignatenkobrain was added to koji admins.
I do a large number of package builds on a routine basis and sometimes run into issues where having admin permission would considerably speed things up. Examples: kojira is often flaky and need to wait hours for a newRepo task; having access to "koji regen-repo" would speed things up a lot. Sometimes I (or someone else) messes something up and needs a quick emergency untag from rawhide before a nightly compose starts; having untag permission would make my life a bit easier.
I might also help out a bit with side tag creation, similar to ignatenkobrain, but no promises that I'd do that in a timely manner. Just in case I happen to have spare cycles.
Thanks for considering my application!
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8728