erlang June 2016

erlang@lists.fedoraproject.org

1 participants
54 discussions

[Bug 1234567] New: Package should not ship a separate emacs sub-package
by Red Hat Bugzilla 26 Nov '18

26 Nov '18

https://bugzilla.redhat.com/show_bug.cgi?id=1234567 Bug ID: 1234567 Summary: Package should not ship a separate emacs sub-package Product: Fedora Version: rawhide Component: erlang Assignee: lemenkov(a)gmail.com Reporter: jonathan.underwood(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, rhbugs(a)n-dimensional.de, s(a)shk.io Blocks: 1234479 The Emacs add-on packaging guidelines no longer stipulate that packages which also bundle support for Emacs should split out those Emacs files into separate sub-packages. This package should instead ship those files with the main package which should also Require emacs-filesystem. See https://fedoraproject.org/wiki/Packaging:Emacs for more detail. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1234479 [Bug 1234479] Violations of Emacs add-on packaging guidelines -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1231430] New: Missing jinterface maven metadata
by Red Hat Bugzilla 20 Nov '18

20 Nov '18

https://bugzilla.redhat.com/show_bug.cgi?id=1231430 Bug ID: 1231430 Summary: Missing jinterface maven metadata Product: Fedora Version: rawhide Component: erlang Assignee: lemenkov(a)gmail.com Reporter: puntogil(a)libero.it QA Contact: extras-qa(a)fedoraproject.org CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, rhbugs(a)n-dimensional.de, s(a)shk.io Description of problem: erlang-jinterface do not provides maven metadata, which used by some projects e.g. https://github.com/spring-projects/spring-amqp/ (spring-erlang sub module) The pom file is available but is not installed https://github.com/erlang/otp/blob/maint/lib/jinterface/java_src/pom.xml.src https://fedoraproject.org/wiki/Packaging:Java#Maven_pom.xml_files and the JAR file should be placed in %_javadir https://fedoraproject.org/wiki/Packaging:Java#JAR_file_installation The spec file "should be" modified in this way: %if %{?fedora} >= 21 BuildRequires: javapackages-local %else BuildRequires: maven-local %endif jinterface_lib_dir="$(ls -d1 $RPM_BUILD_ROOT%{_libdir}/erlang/lib/jinterface-*/ | sed "s,^$RPM_BUILD_ROOT,,")" test -d "$RPM_BUILD_ROOT$jinterface_lib_dir" rm -rf "${jinterface_lib_dir}priv/OtpErlang.jar" if the pom file is not processed sed 's/%VSN%/%{version}/' <otp/lib/jinterface/java_src/pom.xml.src >pom.xml generates maven metadata %mvn_artifact [path of the processed pom file]/pom.xml [path of the built java library]/[name of the java library].jar install JAR file in %_javadir and generate a its symlink %mvn_file org.erlang.otp:jinterface erlang/OtpErlang ${jinterface_lib_dir}priv/OtpErlang %mvn_install Version-Release number of selected component (if applicable): All How reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1295663] New: dialyzer --build_plt crashes
by Red Hat Bugzilla 20 Sep '18

20 Sep '18

https://bugzilla.redhat.com/show_bug.cgi?id=1295663 Bug ID: 1295663 Summary: dialyzer --build_plt crashes Product: Fedora Version: rawhide Component: erlang 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, jeckersb(a)redhat.com, lemenkov(a)gmail.com, rhbugs(a)n-dimensional.de, s(a)shk.io Created attachment 1111752 --> https://bugzilla.redhat.com/attachment.cgi?id=1111752&action=edit erl_crash.dump Description of problem: When I try to build a PLT, dialyzer crashes. Version-Release number of selected component (if applicable): $ rpm -q erlang-dialyzer erlang-dialyzer-17.4-5.fc24.x86_64 How reproducible: Every time Steps to Reproduce: 1. $ dialyzer --build_plt --apps erts kernel stdlib Actual results: $ dialyzer --build_plt --apps erts kernel stdlib Compiling some key modules to native code...{"init terminating in do_boot",{{badmatch,{error,{'EXIT',{badarg,[{hipe_bifs,patch_call,[1095479243,94032498909904,[]],[]},{hipe_unified_loader,patch_call_insn,3,[{file,"hipe_unified_loader.erl"},{line,507}]},{hipe_unified_loader,patch_bif_call_list,4,[{file,"hipe_unified_loader.erl"},{line,492}]},{hipe_unified_loader,patch_call,5,[{file,"hipe_unified_loader.erl"},{line,483}]},{hipe_unified_loader,patch,5,[{file,"hipe_unified_loader.erl"},{line,458}]},{hipe_unified_loader,load_common,4,[{file,"hipe_unified_loader.erl"},{line,235}]},{hipe_unified_loader,load_module,3,[{file,"hipe_unified_loader.erl"},{line,156}]},{code_server,handle_call,3,[{file,"code_server.erl"},{line,332}]}]}}}},[{hipe,finalize,5,[{file,"hipe.erl"},{line,751}]},{hipe,compile_finish,3,[{file,"hipe.erl"},{line,708}]},{hipe,'-run_compiler_1/3-fun-0-',4,[{file,"hipe.erl"},{line,669}]}]}} Crash dump was written to: erl_crash.dump init terminating in do_boot () Expected results: Successful build. Additional info: I've attached the erl_crash.dump file. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1324922] New: Log handler repeatedly crashes
by Red Hat Bugzilla 07 Sep '18

07 Sep '18

https://bugzilla.redhat.com/show_bug.cgi?id=1324922 Bug ID: 1324922 Summary: Log handler repeatedly crashes Product: Fedora EPEL Version: epel7 Component: erlang Keywords: Regression, ZStream Severity: urgent Priority: urgent Assignee: jeckersb(a)redhat.com Reporter: jeckersb(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: apevec(a)redhat.com, binarin(a)binarin.ru, erlang(a)lists.fedoraproject.org, fdinitto(a)redhat.com, jeckersb(a)redhat.com, jschluet(a)redhat.com, lhh(a)redhat.com, oblaut(a)redhat.com, rjones(a)redhat.com, s(a)shk.io, ushkalim(a)redhat.com Depends On: 1322609 Blocks: 1324185 +++ This bug was initially created as a clone of Bug #1322609 +++ Starting with erlang-erts-R16B-03.10min.6.el7ost.x86_64, the log handler repeatedly crashes and fills up the rabbitmq startup_log with entries like: Event crashed log handler: {info_msg,<0.1719.0>, {<0.1832.0>,"Mirrored ~s: Adding mirror on node ~p: ~p~n", ["queue 'l3_agent_fanout_0f6bc20f4c54484f9de482cd6d83a15a' in vhost '/'", 'rabbit@overcloud-controller-1',<6192.10668.1>]}} function_clause Meanwhile the rabbitmq log is empty. Looks like a regression introduced in the "Enable error_logger depth fine tuning" patch. --- Additional comment from Alexey Lebedeff on 2016-04-07 09:17:10 EDT --- R16B-03.16.el7 is also affected. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1322609 [Bug 1322609] Log handler repeatedly crashes https://bugzilla.redhat.com/show_bug.cgi?id=1324185 [Bug 1324185] Log handler repeatedly crashes -- You are receiving this mail because: You are on the CC list for the bug.

2 21

[Bug 1163812] New: Cannot control ejabberd with ejabberdctl
by Red Hat Bugzilla 04 Jul '18

04 Jul '18

https://bugzilla.redhat.com/show_bug.cgi?id=1163812 Bug ID: 1163812 Summary: Cannot control ejabberd with ejabberdctl Product: Fedora Version: 21 Component: ejabberd Assignee: lemenkov(a)gmail.com Reporter: juan.orti(a)miceliux.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 Description of problem: After a clean install of ejabberd in Fedora 21, I cannot use the ejabberdctl utility to register users, etc. I run: # ejabberdctl register admin localhost password Failed RPC connection to the node ejabberd@localhost: nodedown Commands to start an ejabberd node: start Start an ejabberd node in server mode debug Attach an interactive Erlang shell to a running ejabberd node live Start an ejabberd node in live (interactive) mode Optional parameters when starting an ejabberd node: --config-dir dir Config ejabberd: /etc/ejabberd --config file Config ejabberd: /etc/ejabberd/ejabberd.yml --ctl-config file Config ejabberdctl: /etc/ejabberd/ejabberdctl.cfg --logs dir Directory for logs: /var/log/ejabberd --spool dir Database spool dir: /var/lib/ejabberd --node nodename ejabberd node name: ejabberd@localhost And I see this in the log /var/log/ejabberd/ejabberd.log: 2014-11-13 14:57:30.188 [info] <0.7.0> Application lager started on node ejabberd@localhost 2014-11-13 14:57:30.257 [info] <0.7.0> Application sasl started on node ejabberd@localhost 2014-11-13 14:57:30.286 [info] <0.7.0> Application crypto started on node ejabberd@localhost 2014-11-13 14:57:30.354 [info] <0.7.0> Application asn1 started on node ejabberd@localhost 2014-11-13 14:57:30.354 [info] <0.7.0> Application public_key started on node ejabberd@localhost 2014-11-13 14:57:30.421 [info] <0.7.0> Application ssl started on node ejabberd@localhost 2014-11-13 14:57:30.450 [info] <0.7.0> Application p1_yaml started on node ejabberd@localhost 2014-11-13 14:57:30.482 [info] <0.7.0> Application p1_tls started on node ejabberd@localhost 2014-11-13 14:57:30.492 [info] <0.7.0> Application p1_xml started on node ejabberd@localhost 2014-11-13 14:57:30.498 [info] <0.7.0> Application p1_stringprep started on node ejabberd@localhost 2014-11-13 14:57:30.508 [info] <0.7.0> Application p1_zlib started on node ejabberd@localhost 2014-11-13 14:57:30.515 [info] <0.7.0> Application p1_cache_tab started on node ejabberd@localhost 2014-11-13 14:57:31.015 [info] <0.7.0> Application mnesia started on node ejabberd@localhost 2014-11-13 14:57:33.259 [info] <0.37.0>@cyrsasl_digest:start:57 FQDN used to check DIGEST-MD5 SASL authentication: charm.miceliux.com 2014-11-13 14:57:33.423 [info] <0.7.0> Application p1_iconv started on node ejabberd@localhost 2014-11-13 14:57:42.556 [info] <0.564.0>@ejabberd_listener:listen_tcp:194 Reusing listening port for 5222 2014-11-13 14:57:42.556 [info] <0.565.0>@ejabberd_listener:listen_tcp:194 Reusing listening port for 5269 2014-11-13 14:57:42.557 [info] <0.566.0>@ejabberd_listener:listen_tcp:194 Reusing listening port for 5280 2014-11-13 14:57:42.557 [info] <0.37.0>@ejabberd_app:start:69 ejabberd community is started in the node ejabberd@localhost 2014-11-13 14:57:42.557 [info] <0.7.0> Application ejabberd started on node ejabberd@localhost 2014-11-13 14:59:18.926 [error] <0.567.0> ** Connection attempt from disallowed node 'ejabberdctl-1@charm' ** Version-Release number of selected component (if applicable): ejabberd-14.07-3.fc21.x86_64 How reproducible: Always Steps to Reproduce: 1. yum install ejabberd 2. systemctl start ejabberd 3. ejabberdctl register admin localhost password Actual results: Cannot register a user. Expected results: Register a user. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 1341252] New: ejabberd does not log to journald
by Red Hat Bugzilla 12 Dec '17

12 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1341252 Bug ID: 1341252 Summary: ejabberd does not log to journald Product: Fedora Version: rawhide Component: ejabberd Assignee: lemenkov(a)gmail.com Reporter: jeremy(a)jcline.org 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 Created attachment 1163265 --> https://bugzilla.redhat.com/attachment.cgi?id=1163265&action=edit Patch to ejabberd.service Description of problem: It'd be great if ejabberd logged to journald rather than /var/log/ejabberd/. This can be achieved with a few small changes to the systemd unit file. I've attached my proposed systemd unit file. Version-Release number of selected component (if applicable): All currently released versions. Steps to Reproduce: 1. systemctl start ejabberd.service 2. journalctl -u ejabberd 3. :( Actual results: Logs are placed in /var/log/ejabberd Expected results: Logging is handled by journald -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1348753] New: wings-2.0.5 is available
by Red Hat Bugzilla 09 Sep '17

09 Sep '17

https://bugzilla.redhat.com/show_bug.cgi?id=1348753 Bug ID: 1348753 Summary: wings-2.0.5 is available Product: Fedora Version: rawhide Component: wings 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: 2.0.5 Current version/release in rawhide: 2.0.4-1.fc25 URL: https://github.com/dgud/wings 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/5135/ -- You are receiving this mail because: You are on the CC list for the bug.

2 38

[Bug 1291330] New: [epel7s390x] List of packages not found in RHEL7 channels or EPEL7 FTP sites
by Red Hat Bugzilla 08 Aug '17

08 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1291330 Bug ID: 1291330 Summary: [epel7s390x] List of packages not found in RHEL7 channels or EPEL7 FTP sites Product: Fedora EPEL Version: epel7 Component: erlang-mochiweb Severity: medium Assignee: extras-orphan(a)fedoraproject.org Reporter: bugproxy(a)us.ibm.com QA Contact: extras-qa(a)fedoraproject.org CC: erlang(a)lists.fedoraproject.org, extras-orphan(a)fedoraproject.org, jkachuck(a)redhat.com, s(a)shk.io -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1331908] New: erlang-riak_client-2.3.2-timeseries is available
by Red Hat Bugzilla 31 Jul '17

31 Jul '17

https://bugzilla.redhat.com/show_bug.cgi?id=1331908 Bug ID: 1331908 Summary: erlang-riak_client-2.3.2-timeseries is available Product: Fedora Version: rawhide Component: erlang-riak_client 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: 2.3.2-timeseries Current version/release in rawhide: 2.1.1-1.fc25 URL: https://github.com/basho/riak-erlang-client 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/742/ -- You are receiving this mail because: You are on the CC list for the bug.

2 36

[Bug 1331892] New: erlang-riak_pb-2.1.3.0 is available
by Red Hat Bugzilla 11 Jul '17

11 Jul '17

https://bugzilla.redhat.com/show_bug.cgi?id=1331892 Bug ID: 1331892 Summary: erlang-riak_pb-2.1.3.0 is available Product: Fedora Version: rawhide Component: erlang-riak_pb 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: 2.1.3.0 Current version/release in rawhide: 2.1.2.0-6.fc25 URL: https://github.com/basho/riak_pb 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/747/ -- You are receiving this mail because: You are on the CC list for the bug.

2 41

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

erlang June 2016