The modified fix for EJAB-1229 appears to be committed to the 2.1.x
branch, so we can expect it do be available in 2.1.4:
http://github.com/processone/ejabberd/commit/f58d03c12e1160f40a7c38b61b0b6a47a1bc6a1b
--
ejabberd fails at ssl
https://bugs.launchpad.net/bugs/252698
You received this bug not
The patches mentioned in comments #3 and #4 do only implement a way to
enable LDAPS's server certificate checking; the second problem mentioned
in the original bug report was fixed in one of the following commits:
https://git.process-
one.net/ejabberd/mainline/commit/6ae8b9c4d6b66296829483487a9d41e
I'm not sure what do you mean, Neustradamus.
The bug can be told to be "correct" in the sense it is not invalid, but the
patches being discussed here will only hit the next stable release (2.1.4)
which is not ready yet.
If I will push these patches to the next version of the 2.1.3 Debian package,
Could you please justify why these directories should be overriddable by
an administrator and describe at least one non-contrived use case for
this?
--
ejabberd home shouldn't be hardcoded in start()/stop() init script function
https://bugs.launchpad.net/bugs/578318
You received this bug notifica
SegFault, please note that backing up stuff this way is not proper: to
my knowledge, Linux does not offer any technology like VSS in Windows
(whch allows to "hint" a running application to make its currently
opened files into some consistent state) and hence copying or otherwise
snapshotting files
Efren, we have just uploaded 2.1.5-2 to unstable and it contains the fix for
this bug released by upstream.
As I persobally have no easy way to verify the fix actually works, please do
test this version when it is pulled by Ubuntu and report back.
--
Unable to retrieve vCard if PHOTO element is
Looks like you've hit [1] because Saucy has Erlang 16B packaged [2]
while Debian Testing (from which this version of ejabberd had supposedly
been pulled) has the previous Erlang version packaged, R15B [3] and so
the bug is not triggered there.
That's just triaging, I don't know how's best to fix i
Fix committed [1].
While testing the fix I discovered that LDAPS (LDAP over SSL) fails to
work. This has been found to be caused by R16 compat issues as well,
and unfortunately, this will be harder to fix as the problem is about
module name clashes between ejabberd and Erlang. Will file a separa
*** This bug is a duplicate of bug 1041201 ***
https://bugs.launchpad.net/bugs/1041201
Duplicate of #1041201, possibly a bogus form submit.
** Changed in: tkabber (Ubuntu)
Status: New => Invalid
** Changed in: tkabber (Ubuntu)
Assignee: (unassigned) => Konstantin Kho
ispell.
On the other hand, we should possibly add ispell to the list of
suggested packages, this is a good idea indeed. Will do that for the
Debian package.
** Changed in: tkabber (Ubuntu)
Status: New => Invalid
** Changed in: tkabber (Ubuntu)
Assignee: (unassigned) => Kons
I've retitled the bug and re-opened it so that we refer to it in Debian
and make it auto-closed when the fixed package is pulled in Ubuntu.
Thanks for reporting.
** Summary changed:
- tkabber wants ispell
+ tkabber package should suggest ispell
** Tags removed: amd64 running-unity
** Changed i
Should be fixed in 0.11.2-3 which has been uploaded to Debian unstable
today [1] and its transition to testing unblocked [2] so it should hit
testing in ten days if all goes well.
1. http://packages.qa.debian.org/t/tkabber/news/20120714T170325Z.html
2. http://bugs.debian.org/cgi-bin/bugreport.cgi?
The correct version is 0.11.1-3, sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922862
Title:
no icon visual in unity and unity 2d
To manage notifications about this bug go to:
https://bugs.l
(I maintain ejabberd in Debian.)
Could you please be more specific? I'd like to get more details on this
two points:
1) What do you mean precisely by saying "I modified the config directory
to a relative path."? Where and what exactly did you modify?
2) If you state it was your fault, what needs
I have prepared a backport for Lucid about two months ago [1] and
getting a working package is just a matter of running git-buildpackage
on the checkout of that branch. I have prepared that fix to help MiGri
get this fix into his distro, but I can't do anything beyond that as I'm
not affiliated wit
I think the bug status was changed automatically as the "Bug Watch
Updater" does not appear to be a human ;-)
In any case this bug should be closed. The reason may be this: ejabberd
does not have a dedicated maintainer in Ubuntu, and in Debian, where I
maintain ejabberd package at present, I also
I disagree: Badlop connected to a muc service and sent it an error
stanza, in reply, the muc service sent his client another stanza; this
violates RFC but what else? This does not result in any loop just by
itself because well-behaving clients won't send their own error stanza
back. So to DoS the s
Reported in Debian as http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=585832
I think there's no need to take special actions for 2.1.3: we will
upload 2.1.4 quite soon which has this issue fixed.
** Bug watch added: Debian Bug tracker #585832
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Hmm, if I read https://support.process-one.net/browse/EJAB-930 correctly, this
issue affects ejabberd versions since 2.0.1; this even means Debian Lenny
(current stable). I've no idea about Ubuntu versions affected as I have no idea
about what's considered "supported" at the moment.
Consequently
Well, I failed to reply the "Will the 2.1.4 be available for Ubuntu 10.04,
too?" question, MiGri, sorry.
The answer is: I have no idea how to make 2.1.4 available for specific Ubuntu
release as I do not use Ubuntu.
Also, in Debian, we would not upload 2.1.4 to already-released version, but
this
After consulting with one of upstream developers, it became clear this bug
cannot be exploited from the outside and so it's not really that serious as it
might sound because it does not introduce a vulnerability.
To exploit this bug, a hostile party should convince the server administrator
to mi
I see 2.1.5-1 is in Maverick so this bug should possibly be closed now.
--
Don't send error stanza as reply to error stanza (EJAB-930)
https://bugs.launchpad.net/bugs/596676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The maintainer of Expect in Debian asked me to post this comment on his
behalf (he doesn't have a launchpad account):
Could you please report this bug in the Debian bug tracker or at least
provide a minimal script triggering this error?
Reporting bugs against Debian packages does not require havi
Upstream is aware of this bug; it's being tracked as [1].
I see your comments in that bug report so it's a bit unknown to me what was the
reason to file the same bug report here.
1. https://support.process-one.net/browse/EJAB-1258
--
Unable to retrieve vCard if PHOTO element is present
https://
24 matches
Mail list logo