On Fri, Jun 19, 2009 at 09:37:12AM +0200, Jonas Smedegaard wrote:
Did you reset your environment between each step? I.e. remove your
unpacked netatalk sources and unpack again from scratch using
dpkg-source -x netatalk*.dsc? If not, please try that (as the source
becomes infected when
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Thu, Jun 18, 2009 at 11:46:58PM -0500, Itai Seggev wrote:
At all times I had libltdl7=2.2.6a-4 and libltdl3=1.5.26-4 installed.
I started out with the following packages.
libtool i=2.2.6a-4
libltdl-dev i=2.2.6a-4
libltl3-dev p
This
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Wed, Jun 17, 2009 at 11:26:30PM -0500, Itai Seggev wrote:
This issue wasn't quite solved for me, but I'm no longer sure this is a
bug in netatalk. After further investigation, I discovered that the
bug manifested because of the following
At all times I had libltdl7=2.2.6a-4 and libltdl3=1.5.26-4 installed. I
started out with the following packages.
libtool i=2.2.6a-4
libltdl-dev i=2.2.6a-4
libltl3-dev p
This produced the error messages in my bug report, and it still does. (With
2.0.4-1). As someone suggested, I
This issue wasn't quite solved for me, but I'm no longer sure this is a bug in
netatalk. After further investigation, I discovered that the bug manifested
because of the following two situations
a) libltdl-dev provides libltdl3-dev and hence satisfies the build-dep
b) even if you install
5 matches
Mail list logo
