Hi,
when you make the next release, please make sure that it is coordinated with this:
https://bugzilla.redhat.com/show_bug.cgi?id=1129645
I am afraid that the risk is high that our change to 9090 might break Cockpit completely in Fedora 21 unless we coordinate carefully with the SELinux policy.
If coordination is too difficult, let's just revert our change and go back to port 1001.
In any case, there is nothing dramatically bad about going in to the test day with Cockpit 0.20, so we can also decide to not make a release for Fedora 21 Alpha at all.
Can you take care of this, Patrick?
On 08/26/2014 04:10 AM, Marius Vollmer wrote:
Hi,
when you make the next release, please make sure that it is coordinated with this:
https://bugzilla.redhat.com/show_bug.cgi?id=1129645
I am afraid that the risk is high that our change to 9090 might break Cockpit completely in Fedora 21 unless we coordinate carefully with the SELinux policy.
If coordination is too difficult, let's just revert our change and go back to port 1001.
In any case, there is nothing dramatically bad about going in to the test day with Cockpit 0.20, so we can also decide to not make a release for Fedora 21 Alpha at all.
Can you take care of this, Patrick? _______________________________________________ cockpit-devel mailing list cockpit-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cockpit-devel
As of selinux-policy-3.13.1-73 cockpit should be allowed to bind to port 9090.
cockpit-devel@lists.fedorahosted.org