September 2014 - erlang - Fedora Mailing-Lists

[Bug 1087396] New: wings-1.5.3 is available

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1087396 Bug ID: 1087396 Summary: wings-1.5.3 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, fdc(a)fcami.net, lemenkov(a)gmail.com Latest upstream release: 1.5.3 Current version/release in Fedora Rawhide: 1.5.2-1.fc21 URL: https://api.github.com/repos/dgud/wings/tags 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 -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 8 months

1
1
0 / 0

[Bug 1132601] New: ejabberd 2.1.13 has had support dropped; should adopt community version

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1132601 Bug ID: 1132601 Summary: ejabberd 2.1.13 has had support dropped; should adopt community version Product: Fedora Version: 20 Component: ejabberd Severity: low Assignee: lemenkov(a)gmail.com Reporter: ToBeReplaced(a)gmail.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: The current version of ejabberd is 2.1.13. That version is unsupported as of 2013-10-9 according to: http://www.ejabberd.im/ejabberd-13.10 There have been a number of major stable releases since then, including the most recent: http://www.ejabberd.im/ejabberd-14.07 A supported ejabberd should be adopted. -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 8 months

1
1
0 / 0

[Bug 1117450] New: needs network-online.target instead of network.target

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1117450 Bug ID: 1117450 Summary: needs network-online.target instead of network.target Product: Fedora Version: 20 Component: ejabberd Assignee: lemenkov(a)gmail.com Reporter: benfell(a)parts-unknown.org 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: silently fails to open assigned interface Version-Release number of selected component (if applicable): 2.1.13-7.fc20 How reproducible: 100% Steps to Reproduce: 1. reboot system with ejabberd enabled 2. 3. Actual results: systemctl sees ejabberd as having successfully started, but it is inaccessible to clients. Expected results: clients are able to connect to ejabberd Additional info: This appears to be of similar origin to bug #116538 (postfix). I am working around the problem with the following lines in ejabberd.service: Requires=network-online.target After=network-online.target This problem also afflicts nsd, but nsd fails in a way that systemctl recognizes and reports. To my knowledge, ejabberd, nsd, and postfix are the only services affected on my server. This is a server using static addresses. It does not use NetworkManager. -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 8 months

1
2
0 / 0

[Bug 1036359] New: ejabberd logs not reopened after rotation

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1036359 Bug ID: 1036359 Summary: ejabberd logs not reopened after rotation Product: Fedora Version: 20 Component: ejabberd Assignee: lemenkov(a)gmail.com Reporter: redhat(a)subs.maneos.org 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: Version-Release number of selected component (if applicable): ejabberd-2.1.13-7.fc20.x86_64 How reproducible: Steps to Reproduce: 1. Make sure ejabberd is running and logrotate is enabled. 2. Wait until logrotate runs. 3. Check contents of /var/log/ejabberd/ejabberd.log. Actual results: 0 size file that never gets updated. Expected results: File containing log entries for events as they occur. Additional info: /etc/logrotate.d/ejabberd is trying to run /usr/sbin/ejabberdctl, but ejabberdctl is installed in /usr/bin now. -- You are receiving this mail because: You are on the CC list for the bug.

9 years, 8 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

erlang September 2014