Spec URL: https://raphgro.fedorapeople.org/review/py/webvirtmgr/webvirtmgr.spec SRPM URL: https://raphgro.fedorapeople.org/review/py/webvirtmgr/webvirtmgr-4.8.9-2.20160508git.fc24.src.rpm Description: webvirtmgr panel for manage virtual machine Fedora Account System Username: raphgro Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=15849466
Notes: - There's an issue with current django to make webvirtmgr not work. https://github.com/retspen/webvirtmgr/issues/624 https://github.com/retspen/webvirtmgr/issues/592 - The package should be ported to Python3. i assume upstream did not port so far.
EPEL7 has (still) Django 1.6, so we can provide a package there, at least.
Hello! I'm wiling to review, however whats the point of bringing it in, if the application do not work in Fedora? Maybe django1.6-compact package is the way to go in fedora (and keep python2)? I do not have precedense for epel7 only pkg, although I do not have issues with epel7 pkg only...
Hey, I'm currently the django maintainer in Fedora (and EPEL). I'd be trying to get rid of (unmaintained by upstream) Django-1.6 in EPEL7 ASAP. Django releases roughly every 9 months, latest LTS version is Django-1.8. That means, you should wait for a new release of webvirtmgr, if possible.
I can try to work with upstream on a patch to update webvirtmgr to work with a newer Django.
Thanx. Please let me know when you feel the review can be continued. I will finish it.
(In reply to Matthias Runge from comment #4) > Hey, I'm currently the django maintainer in Fedora (and EPEL). I'd be trying > to get rid of (unmaintained by upstream) Django-1.6 in EPEL7 ASAP. Django > releases roughly every 9 months, latest LTS version is Django-1.8. > > That means, you should wait for a new release of webvirtmgr, if possible. "Django 1.6 actually is maintained"! https://bugzilla.redhat.com/show_bug.cgi?id=1432365#c8
Current Django LTS version is Django 1.11 Django 1.6 is maintained by reviewboard upstream. If you want webvirtmgr in EPEL (and maybe in Fedora), please make sure it works with the compatibility package.
As python-django16 is now available at least in epel7, I'm going to continue ASAP with the fixes for this review.
Upstream does not intend to support SELinux. Is that a reason to discontinue with the package review? https://github.com/retspen/webvirtmgr/issues/195 https://github.com/retspen/webvirtmgr/issues/645#issuecomment-339066079
(In reply to Raphael Groner from comment #10) > Upstream does not intend to support SELinux. Is that a reason to discontinue > with the package review? > > https://github.com/retspen/webvirtmgr/issues/195 > https://github.com/retspen/webvirtmgr/issues/645#issuecomment-339066079 No, it means that if it needs an SELinux policy to work, you should write and contribute one. You can ask for help from the Fedora SELinux team.
Essentially, CVE-2015-5144 and CVE-2015-5145 prevent me from continuing with this review request. Sorry for not looking into the release model and security aspects of django even more earlier, thanks for your time to hint me to all the issues. Though, please feel free to use this as a base for another try when upstream hopefully switch to officially support a more current version of django. https://github.com/retspen/webvirtmgr/issues/592
FTR Future development seems to happen with WebVirtCloud. https://github.com/retspen/webvirtcloud https://readthedocs.org/projects/webvirtcloud/