This is a request for building "python-flask-whooshee" against EPEL7, as this is needed for the COPR project.
I'm willing to assist in the testing and maintaining of this package
In that case please apply as a package administrator, I will give you rights and you can build the package by yourself as I am not interested in having it in EPEL7.
You must be a packager to apply to the ACL: approveacls on python-flask-whooshee
User "mrmeee" is not in the packager group
When I try to apply for administrator right..
How do I become part of the packager group??
Here is the wiki:
Do I need to do something else here???
So, when does this package gets build and added to EPEL7?
(In reply to Martin Juhl from comment #5)
> So, when does this package gets build and added to EPEL7?
You first need to assure compatibility of the package with EPEL7 the same way you did that with COPR subpackages. Please make a COPR repo, try building the package for EPEL7 with no added repositories, then fix the problems and submit a patch here that should solve them. Note that the latest release of python-flask-whooshee, that you can work on, is 0.4.1-2 (https://bodhi.fedoraproject.org/updates/FEDORA-2017-b3afc21666). Contact me if you have any questions.
Are we sure that python3-flask-sqlalchemy, python3-blinker and python3-flask are required??? These packages are not in RHEL nor in CentOS/EPEL...
The rpms are building fine without them.. haven't testet much yet... but do we know why they are included??
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.
I have created this dependency repo:
gcab - build dep for libappstream-glib
libappstream-glib - install dep for copr-backend (libappstream-glib-builder)
python-requests - build/install dep for copr-backend
python-urllib3 - build dep for python-requests in version 1.10.4, only 1.10.2 in CentOS
Python packages needed for copr-frontend:
I think that the four packages on top needs to be added to the copr repo?
The others we can probably get into EPEL with some work??? Do anyone know the exact procedure for getting them in???
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.