[Bug 1309523] New: Bump up Erlang version
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1309523
Bug ID: 1309523
Summary: Bump up Erlang version
Product: Fedora EPEL
Version: epel7
Component: erlang
Assignee: rjones(a)redhat.com
Reporter: gdubreui(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jeckersb(a)redhat.com,
rjones(a)redhat.com, s(a)shk.io
Erlang RPM for EPEL7 is version 16
Meawhile Erlang 18 is available.
Fedora 23 is using version 17 while Fedora 24 (rawhide has version 18).
Other projects like Elixir depends on more recent version of Erlang.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 9 months
[Bug 1397225] New: rabbitmq-server-3.6.6 is available
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1397225
Bug ID: 1397225
Summary: rabbitmq-server-3.6.6 is available
Product: Fedora
Version: rawhide
Component: rabbitmq-server
Keywords: FutureFeature, Triaged
Assignee: lemenkov(a)gmail.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
hubert.plociniczak(a)gmail.com, jeckersb(a)redhat.com,
lemenkov(a)gmail.com, rjones(a)redhat.com, s(a)shk.io
Latest upstream release: 3.6.6
Current version/release in rawhide: 3.6.5-1.fc26
URL: http://www.rabbitmq.com/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/5585/
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years
[Bug 1340275] New:
rabbitmq-server does not start on a fresh Fedora 24 installation
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1340275
Bug ID: 1340275
Summary: rabbitmq-server does not start on a fresh Fedora 24
installation
Product: Fedora
Version: 24
Component: rabbitmq-server
Severity: high
Assignee: lemenkov(a)gmail.com
Reporter: rbarlow(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org,
hubert.plociniczak(a)gmail.com, jeckersb(a)redhat.com,
lemenkov(a)gmail.com, rjones(a)redhat.com, s(a)shk.io
Description of problem:
I installed rabbitmq-server and tried to start it, but it failed to start.
Version-Release number of selected component (if applicable):
rabbitmq-server-3.6.2-1.fc24.noarch
How reproducible:
Every time.
Steps to Reproduce:
1. $ sudo dnf install rabbitmq-server
2. $ sudo systemctl start rabbitmq-server
Actual results:
$ sudo systemctl start rabbitmq-server
Job for rabbitmq-server.service failed because the control process exited with
error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe"
for details.
Expected results:
It should start successfully.
Additional info:
There seem to be some AVC denials:
$ sudo audit2allow -al
#============= init_t ==============
allow init_t rabbitmq_var_lib_t:file getattr;
allow init_t rabbitmq_var_log_t:file getattr;
allow init_t unconfined_service_t:tcp_socket create;
$ sudo grep rabbit /var/log/audit/audit.log
type=AVC msg=audit(1464301890.501:728): avc: denied { getattr } for pid=5944
comm="rabbitmqctl" path="/var/log/rabbitmq/rabbit(a)rbarlow-install-f24-sasl.log"
dev="vda1" ino=142758 scontext=system_u:system_r:init_t:s0
tcontext=system_u:object_r:rabbitmq_var_log_t:s0 tclass=file permissive=0
type=AVC msg=audit(1464301890.501:729): avc: denied { getattr } for pid=5944
comm="rabbitmqctl" path="/var/log/rabbitmq/rabbit(a)rbarlow-install-f24-sasl.log"
dev="vda1" ino=142758 scontext=system_u:system_r:init_t:s0
tcontext=system_u:object_r:rabbitmq_var_log_t:s0 tclass=file permissive=0
type=SERVICE_START msg=audit(1464301891.682:730): pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rabbitmq-server
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=failed'
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years
[Bug 1186674] New: Failed to create directory /var/lock/ejabberdctl: No such file or directory
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1186674
Bug ID: 1186674
Summary: Failed to create directory /var/lock/ejabberdctl: No
such file or directory
Product: Fedora
Version: 21
Component: ejabberd
Assignee: lemenkov(a)gmail.com
Reporter: arcfi(a)aetera.net
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jkaluza(a)redhat.com,
lemenkov(a)gmail.com, martin(a)laptop.org
Description of problem:
> # journalctl -lu systemd-tmpfiles-setup.service -b
> systemd-tmpfiles[1493]: Failed to create directory /var/lock/ejabberdctl: No such file or directory
> systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
> systemd[1]: Failed to start Create Volatile Files and Directories.
> systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
> systemd[1]: systemd-tmpfiles-setup.service failed.
Incorrect path in "/usr/lib/tmpfiles.d/ejabberd.conf".
Use "/run/lock/ejabberdctl" instead of "/var/lock/ejabberdctl".
Version-Release number of selected component (if applicable):
ejabberd-14.07-6.fc21.x86_64
systemd-216-17.fc21.x86_64
How reproducible:
Always.
Actual results:
# cat /usr/lib/tmpfiles.d/ejabberd.conf
d /var/lock/ejabberdctl 0750 ejabberd ejabberd
Expected results:
# cat /usr/lib/tmpfiles.d/ejabberd.conf
d /run/lock/ejabberdctl 0750 ejabberd ejabberd
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 1 month
[Bug 1400080] New: erlang-19.1.6 is available
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1400080
Bug ID: 1400080
Summary: erlang-19.1.6 is available
Product: Fedora
Version: rawhide
Component: erlang
Keywords: FutureFeature, Triaged
Assignee: lemenkov(a)gmail.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jeckersb(a)redhat.com,
lemenkov(a)gmail.com, rhbugs(a)n-dimensional.de, s(a)shk.io
Latest upstream release: 19.1.6
Current version/release in rawhide: 19.1.2-1.fc26
URL: http://www.erlang.org/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/707/
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 2 months
[Bug 1094143] New: Desktop centric polkit ejabberdctl policy file, prevents server use
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1094143
Bug ID: 1094143
Summary: Desktop centric polkit ejabberdctl policy file,
prevents server use
Product: Fedora
Version: 20
Component: ejabberd
Assignee: lemenkov(a)gmail.com
Reporter: stefw(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jkaluza(a)redhat.com,
lemenkov(a)gmail.com, martin(a)laptop.org
Blocks: 1094121
Description of problem:
The shipped polkit policy is completely desktop-centric and expects that the
admin user is logged in a local session (ie: a seat in logind parlance, with a
monitor and keyboard).
This prevents DBus API use when logged in via ssh (and using pkttyagent as your
polkit agent) or via Cockpit.
The <allow_any> tag in polkit policy applies to non-local sessions. It should
be set to something other than 'no' unless the action directly affects hardware
of the login seat.
Version-Release number of selected component (if applicable):
2.1.13-7.fc20
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1094121
[Bug 1094121] Tracker: Fix desktop centric polkit policy
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 2 months