taingram reported a new issue against the project: `releng` that you are following:
``
Please assign this package to me, I have contributed patches to brightnessctl and would like to take over packaging it. Thanks!
https://src.fedoraproject.org/rpms/brightnessctl
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8508
fweimer reported a new issue against the project: `releng` that you are following:
``
I've just filed this fedpkg-minimal feature request:
* https://bugzilla.redhat.com/show_bug.cgi?id=1578348
It would be great if we could get this to work on Fedora Koji, with a suitable whitelist of supported repositories.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7498
ppisar reported a new issue against the project: `releng` that you are following:
``
Bugzilla finally contains component for modules. But "perl" is still missing there (in contrast to "perl-bootstrap").
Please create "perl" component in Fedora/Fedora Module product with default assignee "ppisar(a)redhat.com".
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7393
fale reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Hi, I would like to pick-up the brightnessctl package that I've orphaned a while ago.
* When do you need this? (YYYY/MM/DD)
When possible
* When is this no longer needed or useful? (YYYY/MM/DD)
I think it would still be useful
* If we cannot complete your request, what is the impact?
brightnessctl stays orphaned and unmaintained.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8364
atim reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
faience-icon-theme
* FAS username of the new maintainer?
atim
* Branches that you need it to be unretired for?
master
f30
f29
epel7
* Package re-review BZ URL?
Retired for less than six weeks so no re-review required.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8499
ankursinha reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
I'm no longer a maintainer for gitg, but new bugs on bugzilla still include my e-mail address. Would someone please know what I must do to stop new bugs for gitg including it too?
https://src.fedoraproject.org/rpms/gitg
Example new bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1727558
* When do you need this? (YYYY/MM/DD)
NA
* When is this no longer needed or useful? (YYYY/MM/DD)
Not urgent at all.
* If we cannot complete your request, what is the impact?
I keep getting these bug e-mails and remove myself manually.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8512
decathorpe reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
emma
felix-osgi-obr-resolver
hibernate-jpa-2.0-api
jboss-connector-1.7-api
jboss-el-2.2-api
jboss-jsf-2.1-api
jboss-jsp-2.3-api
jboss-jstl-1.2-api
jboss-marshalling
jboss-servlet-3.0-api
jboss-websocket-1.0-api
jline1
weld-parent
* FAS username of the new maintainer?
decathorpe
* Any extra information?
These recently orphaned packages are still needed in fedora, and hence will be maintained by the Stewardship SIG for now ...
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8510
eclipseo reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
golang-google-appengine
* FAS username of the new maintainer?
eclipseo
* Branches that you need it to be unretired for?
master
* Any extra information?
I've accidentally retired this package, could you please reinstate it?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8511
cverna reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
I have pushed an update of the Fedora base image container on Docker Hub we should be doing the same for registry.fp.o
The following version can be release f30 and f31.
* 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/8505