tor (0.2.0.33-1ubuntu1) jaunty; urgency=low
* debian/rules: invoke dh_shlibdeps -- -xglibc-private to avoid
unmet dependency with glibc-private if linked with glibc = 2.8.
-- Luca Falavigna dktrkr...@ubuntu.com Mon, 02 Feb 2009 08:14:21
+
** Changed in: tor (Ubuntu)
Status:
Original upstream bug report on memory allocation:
http://bugs.noreply.org/flyspray/index.php?do=detailsid=468area=comments.
--
tor 0.2.0.32-1 Depends: glibc-private but it is not installable
https://bugs.launchpad.net/bugs/303949
You received this bug notification because you are a member of
All we need is a change in debian/rules, calling dh_shlibdeps with
-xglibc-private. A patch is attached.
Does this need to be send back to Debian?
** Attachment added: call dh_shlibdeps with -- -xglibc-private
http://launchpadlibrarian.net/21853057/dh-shlibdeps-glibc-private.patch
**
This can also be fixed by building without --enable-openbsd-malloc.
--
tor 0.2.0.32-1 Depends: glibc-private but it is not installable
https://bugs.launchpad.net/bugs/303949
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Confirmed. Updated patch attached.
** Attachment added: disable openbsd mallocs on ./debian/rules
http://launchpadlibrarian.net/21867438/disable-openbsd-malloc.patch
--
tor 0.2.0.32-1 Depends: glibc-private but it is not installable
https://bugs.launchpad.net/bugs/303949
You received this
DEB_BUILD_OPTIONS is supposed to be set from outside the package, not
from debian/rules. Just delete the four lines that add --enable-
openbsd-malloc to CONF_OPTIONS instead.
Here is what the Tor wiki has to say about --enable-opensbd-malloc:
Still present on tor 0.2.0.33-1. Maybe Debian patched locally?
--
tor 0.2.0.32-1 Depends: glibc-private but it is not installable
https://bugs.launchpad.net/bugs/303949
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Debian experimental has the 0.2.1.x unstable branch, so we shouldn't
sync that. I have filed a sync request for 0.2.0.33-1 at bug 321122.
It may be worth noting that the Debian 0.2.0.32-1 package doesn't
contain the glibc-private dependency.
** Changed in: tor (Ubuntu)
Importance: Medium =
can we sync it from debian experimental? will solve this issue
--
tor 0.2.0.32-1 Depends: glibc-private but it is not installable
https://bugs.launchpad.net/bugs/303949
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I also confirm this bug on Jaunty.
--
tor 0.2.0.32-1 Depends: glibc-private but it is not installable
https://bugs.launchpad.net/bugs/303949
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
from glibc-2.9/debian/debhelper.in/libc-alt.lintian (bottom):
# glibc-private is an invalid dependency generated if someone uses a
# private glibc API, thus it's on purpose
LIBC-FLAVOR: symbols-declares-dependency-on-other-package glibc-private
So... marking confirmed. Jaunty tor is
This bug affects me in jaunty as well, on an Intel Core Duo.
I'm trying to install Tor fresh, not upgrade it and I receive the
same broken package report. Behavior seen in synaptic and commandline
apt-get, though I assume that the difference is negligible.
--
tor 0.2.0.32-1 Depends:
12 matches
Mail list logo
