Erlang package names
by Randy Barlow
Hello again!
I've been working on getting ejabberd updated in Fedora, and I've been
trying to package its dependencies separately. After submitting a review
request for erlang-p1_pgsql[0], I noticed that there is already a pgsql
package from process one called erlang-pgsql. Oops!
However, I've also noticed that the other package installs to the
library folder pgsql, while rebar from ejabberd is looking for p1_pgsql
so I think it won't "just work" though I'm not totally sure how
dependencies in Erlang work. It seems to me that it was looking in the
Erlang lib folder for folders that match specific names.
I have two questions:
0) Do you think I should just patch the ejabberd rebar.config file to
depend on the name pgsql instead of p1_pgsql? Is that all that would be
required to get ejabberd to use that package instead of mine?
1) I've been naming several of my packages erlang-p1_* instead of
erlang-*. Do you think I should not do that, even though that seems to
be the naming scheme that ejabberd is expecting?
Sorry for so many questions over the past few days. Being new at Erlang,
I've got a lot to learn.
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1294730
--
Randy Barlow
xmpp: bowlofeggs(a)electronsweatshop.com
irc: bowlofeggs on Freenode
8 years, 4 months
How to get an Erlang package to link to erl_driver
by Randy Barlow
Hello! I am trying to package https://github.com/processone/zlib and the
resulting library has some errors:
[rbarlow@boole erlang-p1_zlib]$ ldd -r
~/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so
linux-vdso.so.1 (0x00007ffec3a62000)
libz.so.1 => /lib64/libz.so.1 (0x00007fe1683c3000)
libc.so.6 => /lib64/libc.so.6 (0x00007fe167ffc000)
/lib64/ld-linux-x86-64.so.2 (0x00005639b527a000)
undefined symbol: set_port_control_flags
(/home/rbarlow/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so)
undefined symbol: driver_free
(/home/rbarlow/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so)
undefined symbol: driver_alloc_binary
(/home/rbarlow/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so)
undefined symbol: driver_alloc
(/home/rbarlow/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so)
undefined symbol: driver_realloc_binary
(/home/rbarlow/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so)
I've determined that these symbols are included in the erts package, and
I think in libei.a. I am unsure if this is a packaging error that I need
to respond to, or if this is how Erlang ports work. Can someone advise
me on what I am supposed to do here?
--
Randy Barlow
xmpp: bowlofeggs(a)electronsweatshop.com
irc: bowlofeggs on Freenode
8 years, 4 months
How to get an Erlang package to link to erl_driver
by Randy Barlow
Hello! I am trying to package https://github.com/processone/zlib and the
resulting library has some errors:
[rbarlow@boole erlang-p1_zlib]$ ldd -r
~/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so
linux-vdso.so.1 (0x00007ffec3a62000)
libz.so.1 => /lib64/libz.so.1 (0x00007fe1683c3000)
libc.so.6 => /lib64/libc.so.6 (0x00007fe167ffc000)
/lib64/ld-linux-x86-64.so.2 (0x00005639b527a000)
undefined symbol: set_port_control_flags
(/home/rbarlow/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so)
undefined symbol: driver_free
(/home/rbarlow/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so)
undefined symbol: driver_alloc_binary
(/home/rbarlow/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so)
undefined symbol: driver_alloc
(/home/rbarlow/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so)
undefined symbol: driver_realloc_binary
(/home/rbarlow/rpmbuild/BUILD/zlib-e3d4222b7aae616d7ef2e7e2fa0bbf451516c602/priv/lib/ezlib_drv.so)
I've determined that these symbols are included in the erts package, and
I think in libei.a. I am unsure if this is a packaging error that I need
to respond to, or if this is how Erlang ports work. Can someone advise
me on what I am supposed to do here?
--
Randy Barlow
irc: bowlofeggs
8 years, 4 months
[Bug 1184159] New: ejabberd: XMPP resource consumption denial of service when using application-layer compression (XEP-0138) [fedora-all]
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1184159
Bug ID: 1184159
Summary: ejabberd: XMPP resource consumption denial of service
when using application-layer compression (XEP-0138)
[fedora-all]
Product: Fedora
Version: 21
Component: ejabberd
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: lemenkov(a)gmail.com
Reporter: vdanen(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: 1084850
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1084850
[Bug 1084850] XMPP resource consumption denial of service when using
application-layer compression (XEP-0138)
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 5 months