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.
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.srchttps://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.
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.
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.
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.
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1234568
Bug ID: 1234568
Summary: Package should not ship a separate emacs sub-package
Product: Fedora
Version: rawhide
Component: erlang-lfe
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
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.