erlang July 2016

erlang@lists.fedoraproject.org

2 participants
183 discussions

[Bug 1354694] New: erlang-protobuffs-0.8.4 is available
by Red Hat Bugzilla 11 Dec '16

11 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1354694 Bug ID: 1354694 Summary: erlang-protobuffs-0.8.4 is available Product: Fedora Version: rawhide Component: erlang-protobuffs 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, lemenkov(a)gmail.com Latest upstream release: 0.8.4 Current version/release in rawhide: 0.8.3-1.fc25 URL: https://github.com/basho/erlang_protobuffs 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/738/ -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1347945] New: erlang-lfe-1.1 is available
by Red Hat Bugzilla 03 Dec '16

03 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1347945 Bug ID: 1347945 Summary: erlang-lfe-1.1 is available Product: Fedora Version: rawhide Component: erlang-lfe 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, lemenkov(a)gmail.com Latest upstream release: 1.1 Current version/release in rawhide: 1.0.2-2.fc25 URL: https://github.com/rvirding/lfe 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/728/ -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1357387] New: Erlang 19
by Red Hat Bugzilla 22 Nov '16

22 Nov '16

https://bugzilla.redhat.com/show_bug.cgi?id=1357387 Bug ID: 1357387 Summary: Erlang 19 Product: Fedora Version: rawhide Component: Changes Tracking Assignee: jkurik(a)redhat.com Reporter: jkurik(a)redhat.com CC: erlang(a)lists.fedoraproject.org, jeremy(a)jcline.org, lemenkov(a)gmail.com, rbarlow(a)redhat.com This is a tracking bug for Change: Erlang 19 For more details, see: https://fedoraproject.org//wiki/Changes/Erlang_19 Update Erlang/OTP to version 19, and improve Erlang support in Fedora. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1077547] New: Riak service won't start
by Red Hat Bugzilla 09 Nov '16

09 Nov '16

https://bugzilla.redhat.com/show_bug.cgi?id=1077547 Bug ID: 1077547 Summary: Riak service won't start Product: Fedora Version: 20 Component: riak Severity: high Assignee: lemenkov(a)gmail.com Reporter: j.mark.brooks(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1307993] New: riak: FTBFS in rawhide
by Red Hat Bugzilla 09 Nov '16

09 Nov '16

https://bugzilla.redhat.com/show_bug.cgi?id=1307993 Bug ID: 1307993 Summary: riak: FTBFS in rawhide Product: Fedora Version: rawhide Component: riak Assignee: lemenkov(a)gmail.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com Blocks: 1305208 Your package riak failed to build from source in current rawhide. http://koji.fedoraproject.org/koji/taskinfo?taskID=12865042 For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1305208 [Bug 1305208] Fedora 24 Mass rebuild FTBFS tracker bug -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1361742] New: rabbitmq-server-3.6.4 is available
by Red Hat Bugzilla 06 Sep '16

06 Sep '16

https://bugzilla.redhat.com/show_bug.cgi?id=1361742 Bug ID: 1361742 Summary: rabbitmq-server-3.6.4 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.4 Current version/release in rawhide: 3.6.3-6.fc25 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.

1 21

[Bug 1360657] New: rabbitmq-server fails to start
by Red Hat Bugzilla 31 Aug '16

31 Aug '16

https://bugzilla.redhat.com/show_bug.cgi?id=1360657 Bug ID: 1360657 Summary: rabbitmq-server fails to start Product: Fedora Version: 24 Component: rabbitmq-server Assignee: lemenkov(a)gmail.com Reporter: bochecha(a)daitauha.fr 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'm trying to start the service, to no avail. Here's the error messages I get in the journal: Jul 27 10:55:27 mathieus-laptop systemd[1]: Starting RabbitMQ broker... Jul 27 10:55:27 mathieus-laptop audit[9052]: AVC avc: denied { read } for pid=9052 comm="inet_gethost" name="unix" dev="proc" ino=4026532033 scontext=system_u:system_r:rabbitmq_t:s0 tcontext=system_u:object_r:proc_net_t:s0 tclass=file permissive=1 Jul 27 10:55:27 mathieus-laptop audit[8591]: AVC avc: denied { accept } for pid=8591 comm="epmd" lport=4369 scontext=system_u:system_r:init_t:s0 tcontext=system_u:system_r:unconfined_service_t:s0 tclass=tcp_socket permissive=1 Jul 27 10:55:27 mathieus-laptop audit[8591]: AVC avc: denied { getattr } for pid=8591 comm="epmd" laddr=127.0.0.1 lport=4369 faddr=127.0.0.1 fport=51345 scontext=system_u:system_r:init_t:s0 tcontext=system_u:system_r:unconfined_service_t:s0 tclass=tcp_socket permissive=1 Jul 27 10:55:31 mathieus-laptop rabbitmq-server[8939]: ERROR: epmd error for host mathieus-laptop: address (cannot connect to host/port) Jul 27 10:55:31 mathieus-laptop systemd[1]: rabbitmq-server.service: Main process exited, code=exited, status=1/FAILURE Jul 27 10:55:31 mathieus-laptop audit[9110]: AVC avc: denied { getattr } for pid=9110 comm="rabbitmqctl" path="/var/lib/rabbitmq/mnesia/rabbit(a)mathieus-laptop.pid" dev="sda3" ino=2101255 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:rabbitmq_var_lib_t:s0 tclass=file permissive=1 Jul 27 10:55:31 mathieus-laptop audit[9123]: AVC avc: denied { getattr } for pid=9123 comm="rabbitmqctl" path="/var/log/rabbitmq/rabbit(a)mathieus-laptop.log" dev="sda3" ino=2101899 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:rabbitmq_var_log_t:s0 tclass=file permissive=1 Jul 27 10:55:31 mathieus-laptop rabbitmqctl[9057]: Stopping and halting node 'rabbit@mathieus-laptop' ... Jul 27 10:55:34 mathieus-laptop rabbitmqctl[9057]: Error: unable to connect to node 'rabbit@mathieus-laptop': nodedown Jul 27 10:55:37 mathieus-laptop rabbitmqctl[9057]: DIAGNOSTICS Jul 27 10:55:37 mathieus-laptop rabbitmqctl[9057]: =========== Jul 27 10:55:37 mathieus-laptop rabbitmqctl[9057]: attempted to contact: ['rabbit@mathieus-laptop'] Jul 27 10:55:37 mathieus-laptop rabbitmqctl[9057]: rabbit@mathieus-laptop: Jul 27 10:55:37 mathieus-laptop rabbitmqctl[9057]: * unable to connect to epmd (port 4369) on mathieus-laptop: address (cannot connect to host/port) Jul 27 10:55:37 mathieus-laptop rabbitmqctl[9057]: current node details: Jul 27 10:55:37 mathieus-laptop rabbitmqctl[9057]: - node name: 'rabbitmq-cli-31@mathieus-laptop' Jul 27 10:55:37 mathieus-laptop rabbitmqctl[9057]: - home dir: /var/lib/rabbitmq Jul 27 10:55:37 mathieus-laptop rabbitmqctl[9057]: - cookie hash: A0+gWuGkAgb8P/MD2n0e4A== Jul 27 10:55:37 mathieus-laptop audit[1]: SERVICE_START 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' Jul 27 10:55:37 mathieus-laptop systemd[1]: Failed to start RabbitMQ broker. Jul 27 10:55:37 mathieus-laptop systemd[1]: rabbitmq-server.service: Unit entered failed state. Jul 27 10:55:37 mathieus-laptop systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'. There's some SELinux messages, but I've set it to permissive and still rabbitmq fails to start. Version-Release number of selected component (if applicable): rabbitmq-server-3.6.2-3.fc24.noarch How reproducible: Always Additional info: Note that it was working just fine last week when I installed rabbitmq. I could start the service without issue at that time. So it might be an update that broke it? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1337216] New: p1_pam fails to start - ejabberd barfs
by Red Hat Bugzilla 31 Aug '16

31 Aug '16

https://bugzilla.redhat.com/show_bug.cgi?id=1337216 Bug ID: 1337216 Summary: p1_pam fails to start - ejabberd barfs Product: Fedora Version: rawhide Component: ejabberd Severity: high Assignee: lemenkov(a)gmail.com Reporter: alan.milligan(a)last-bastion.net QA Contact: extras-qa(a)fedoraproject.org CC: erlang(a)lists.fedoraproject.org, jeremy(a)jcline.org, lemenkov(a)gmail.com, martin(a)laptop.org, rbarlow(a)redhat.com Description of problem: p1_pam fails to start because ejabberd is looking in the incorrect place for epam.beam (in ejabberd file path instead of p1_pam) - sorry haven't looked at code to provide patch Version-Release number of selected component (if applicable): Rawhide 16.04 How reproducible: Always Steps to Reproduce: 1. Ensure PAM turned on in ejabberd.yml 2. start ejabberd 3. it fails: check /var/log/ejabberd/server.log Actual results: /var/log/ejabberd/server.log 2016-05-18 23:40:47.128 [info] <0.38.0>@cyrsasl_digest:start:60 FQDN used to check DIGEST-MD5 SASL authentication: jenkins-dev.last-bastion.net 2016-05-18 23:40:47.154 [error] <0.392.0> Can't open file "/usr/lib64/erlang/lib/ejabberd/priv/bin/epam": enoent 2016-05-18 23:40:47.154 [error] <0.392.0> CRASH REPORT Process epam with 0 neighbours exited with reason: bad return value: error in gen_server:init_it/6 line 356 2016-05-18 23:40:47.154 [error] <0.391.0> Supervisor epam_sup had child epam started with epam:start_link() at undefined exit with reason bad return value: error in context start_error 2016-05-18 23:40:47.154 [error] <0.389.0> CRASH REPORT Process <0.389.0> with 0 neighbours exited with reason: {{shutdown,{failed_to_start_child,epam,{bad_return_value,error}}},{epam_app,start,[normal,[]]}} in application_master:init/4 line 134 2016-05-18 23:40:47.154 [critical] <0.38.0>@ejabberd:exit_or_halt:133 failed to start application 'p1_pam': {error, {{shutdown, {failed_to_start_child,epam, {bad_return_value,error}}}, {epam_app,start,[normal,[]]}}} 2016-05-18 23:40:47.155 [info] <0.7.0> Application p1_pam exited with reason: {{shutdown,{failed_to_start_child,epam,{bad_return_value,error}}},{epam_app,start,[normal,[]]}} Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1036780] New: rabbitmq-server wrapper script drops arguments
by Red Hat Bugzilla 29 Aug '16

29 Aug '16

https://bugzilla.redhat.com/show_bug.cgi?id=1036780 Bug ID: 1036780 Summary: rabbitmq-server wrapper script drops arguments Product: Fedora Version: rawhide Component: rabbitmq-server Assignee: hubert.plociniczak(a)gmail.com Reporter: rhbugs(a)rbu.sh QA Contact: extras-qa(a)fedoraproject.org CC: erlang(a)lists.fedoraproject.org, hubert.plociniczak(a)gmail.com, lemenkov(a)gmail.com Description of problem: the wrapper script /usr/sbin/rabbitmqctl drops all arguments to the command in certain cases, for example when the calling user is not root. I am running a rabbitmq node as a local user (for development) as a regular user, outside of /var. This works fine, however the Fedora-specific wrapper to "rabbitctl" will obscure access to the rabbitctl script. It took me quite a while to debug what was happening, until I found out the command is really a wrapper whose sole purpose is munging arguments -- and it does it wrong. Version-Release number of selected component (if applicable): I am on 3.1.5-1.fc19 but I see the same bug in rawhide. How reproducible: Always. Steps to Reproduce: 1. Be non-root / non-rabbitmq user 2. Run rabbitmqctl status Actual results: Error: could not recognise command Usage: rabbitmqctl [-n <node>] [-q] <command> [<command options>] ... Expected results: Status of node rabbit@localhost ... [{pid,1234},... Additional info: The warning "Only root or rabbitmq should run" should really be "Only root or rabbitmq must run", as currently it makes it impossible for anyone else. However, this is not true, as any user *can* run rabbitmq. Furthermore, users in the rabbitmq group should be able to run management commands, given the correct parameters. Lastly, the "rabbitmq-plugins" case looks fishy too, as it allows anyone to run the rabbitmq-plugins command, and makes the first line obsolete. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1353394] New: rabbitmq-server-3.6.3 is available
by Red Hat Bugzilla 15 Aug '16

15 Aug '16

https://bugzilla.redhat.com/show_bug.cgi?id=1353394 Bug ID: 1353394 Summary: rabbitmq-server-3.6.3 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.3 Current version/release in rawhide: 3.6.2-4.fc25 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.

1 20

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

erlang July 2016