Debian Bug report logs - #657900
libpcap: symlink to libpcap.so.1 appears missing

version graph

Package: libpcap0.8; Maintainer for libpcap0.8 is Romain Francoise <rfrancoise@debian.org>; Source for libpcap0.8 is src:libpcap.

Reported by: Chris Morgan <chmorgan@gmail.com>

Date: Sun, 29 Jan 2012 18:12:02 UTC

Severity: important

Found in version libpcap/1.1.1-8

Done: Romain Francoise <rfrancoise@debian.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, chmorgan@gmail.com, Romain Francoise <rfrancoise@debian.org>:
Bug#657900; Package libpcap0.8. (Sun, 29 Jan 2012 18:12:05 GMT) Full text and rfc822 format available.

Acknowledgement sent to Chris Morgan <chmorgan@gmail.com>:
New Bug report received and forwarded. Copy sent to chmorgan@gmail.com, Romain Francoise <rfrancoise@debian.org>. (Sun, 29 Jan 2012 18:12:05 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Chris Morgan <chmorgan@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: libpcap: symlink to libpcap.so.1 appears missing
Date: Sun, 29 Jan 2012 13:09:40 -0500
Package: libpcap0.8
Version: 1.1.1-8
Severity: important
File: libpcap


I'm the developer of SharpPcap, a c# library that interacts with libpcap. Noticed that it wasn't working
on my system because the mapping from windows dll to linux dll was broken. Previously I was able to map
from wpcap to libpcap.so.0 but there was no libpcap.so.0 file. After some research and discussion with a few
people online I discovered that fedora ships libpcap.so.1.2.1 and a symlink at libpcap.so.1, opensuse libpcap.so.0.9.7
and a symlink at libpcap.so.0. Ubuntu/debian ship libpcap.so.1.1.1 with a symlink at libpcap.so.0.8.

Looking at http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-runtime it appears that
this package *should* have a libpcap.so.1 symlink. And it would make my life a lot simpler :-)


-- System Information:
Debian Release: wheezy/sid
  APT prefers oneiric-updates
  APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric'), (100, 'oneiric-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-14-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpcap0.8 depends on:
ii  libc6                     2.13-20ubuntu5 Embedded GNU C Library: Shared lib
ii  multiarch-support         2.13-20ubuntu5 Transitional package to ensure mul

libpcap0.8 recommends no packages.

libpcap0.8 suggests no packages.

-- no debconf information




Reply sent to Romain Francoise <rfrancoise@debian.org>:
You have taken responsibility. (Sun, 29 Jan 2012 20:39:06 GMT) Full text and rfc822 format available.

Notification sent to Chris Morgan <chmorgan@gmail.com>:
Bug acknowledged by developer. (Sun, 29 Jan 2012 20:39:06 GMT) Full text and rfc822 format available.

Message #10 received at 657900-done@bugs.debian.org (full text, mbox):

From: Romain Francoise <rfrancoise@debian.org>
To: Chris Morgan <chmorgan@gmail.com>
Cc: 657900-done@bugs.debian.org
Subject: Re: Bug#657900: libpcap: symlink to libpcap.so.1 appears missing
Date: Sun, 29 Jan 2012 21:35:52 +0100
Hi,

Yes, the way libpcap is shipped in binary form varies from one
distribution to the next. For a long time upstream only supported static
linking, so each distribution improvised its own build recipes and, more
importantly, versioning for the shared version. That's why some
distributions use '0', others '1', and Debian '0.8'. Unfortunately
changing it now would be a major pain for almost no benefit as there is no
guarantee that the libraries would be compatible between distributions
even if they had the same soname.

So, anyway: there is no symlink missing from the package, and if you want
to provide binaries outside the confines of Debian's build system your
best bet is to provide one binary per supported distribution.

Cheers,
-- 
Romain Francoise <rfrancoise@debian.org>
http://people.debian.org/~rfrancoise/




Message #11 received at 657900-done@bugs.debian.org (full text, mbox):

From: Chris Morgan <chmorgan@gmail.com>
To: Romain Francoise <rfrancoise@debian.org>
Cc: "657900-done@bugs.debian.org" <657900-done@bugs.debian.org>
Subject: Re: Bug#657900: libpcap: symlink to libpcap.so.1 appears missing
Date: Sun, 29 Jan 2012 16:23:03 -0500
Hello.

From the debian runtime library document, shouldn't there be a symlink
to the latest version of the library? And isn't that something in the
1.x series? Is the version not 1.x? I can't help but thing there is
some way to keep existing apps working without change while also
making things more consistent with other distributions. The libpcap
developers seem pretty receptive to things so I could talk to them
depending on what might help.

Chris



On Jan 29, 2012, at 3:35 PM, Romain Francoise <rfrancoise@debian.org> wrote:

> Hi,
>
> Yes, the way libpcap is shipped in binary form varies from one
> distribution to the next. For a long time upstream only supported static
> linking, so each distribution improvised its own build recipes and, more
> importantly, versioning for the shared version. That's why some
> distributions use '0', others '1', and Debian '0.8'. Unfortunately
> changing it now would be a major pain for almost no benefit as there is no
> guarantee that the libraries would be compatible between distributions
> even if they had the same soname.
>
> So, anyway: there is no symlink missing from the package, and if you want
> to provide binaries outside the confines of Debian's build system your
> best bet is to provide one binary per supported distribution.
>
> Cheers,
> --
> Romain Francoise <rfrancoise@debian.org>
> http://people.debian.org/~rfrancoise/




Information forwarded to debian-bugs-dist@lists.debian.org:
Bug#657900; Package libpcap0.8. (Sun, 29 Jan 2012 22:42:07 GMT) Full text and rfc822 format available.

Acknowledgement sent to Romain Francoise <rfrancoise@debian.org>:
Extra info received and forwarded to list. (Sun, 29 Jan 2012 22:42:07 GMT) Full text and rfc822 format available.

Message #16 received at 657900@bugs.debian.org (full text, mbox):

From: Romain Francoise <rfrancoise@debian.org>
To: Chris Morgan <chmorgan@gmail.com>
Cc: 657900@bugs.debian.org
Subject: Re: Bug#657900: libpcap: symlink to libpcap.so.1 appears missing
Date: Sun, 29 Jan 2012 23:40:01 +0100
Chris Morgan <chmorgan@gmail.com> writes:

> From the debian runtime library document, shouldn't there be a symlink
> to the latest version of the library?

Yes, there is one:

 /usr/lib/x86_64-linux-gnu/libpcap.so.0.8 -> libpcap.so.1.2.1

> And isn't that something in the 1.x series? Is the version not 1.x?

The version, yes. The soname, no.

> The libpcap developers seem pretty receptive to things so I could talk
> to them depending on what might help.

There's nothing they can do about this, the upstream build defines a
different soname. If someone were to package libpcap from scratch today
they would probably use it, but each distribution has to live with its
historical soname.

-- 
Romain Francoise <rfrancoise@debian.org>
http://people.debian.org/~rfrancoise/




Information forwarded to debian-bugs-dist@lists.debian.org, Romain Francoise <rfrancoise@debian.org>:
Bug#657900; Package libpcap0.8. (Mon, 30 Jan 2012 00:09:07 GMT) Full text and rfc822 format available.

Acknowledgement sent to Chris Morgan <chmorgan@gmail.com>:
Extra info received and forwarded to list. Copy sent to Romain Francoise <rfrancoise@debian.org>. (Mon, 30 Jan 2012 00:09:07 GMT) Full text and rfc822 format available.

Message #21 received at 657900@bugs.debian.org (full text, mbox):

From: Chris Morgan <chmorgan@gmail.com>
To: Romain Francoise <rfrancoise@debian.org>
Cc: "657900@bugs.debian.org" <657900@bugs.debian.org>
Subject: Re: Bug#657900: libpcap: symlink to libpcap.so.1 appears missing
Date: Sun, 29 Jan 2012 19:06:57 -0500
Hi.

I guess I'm a little confused. Why would it not make sense to make a
so.1 symlink to the .so.1.1.1 library? I don't see why one would want
them to differ. The 0.8 symlink could remain right?

Chris


On Jan 29, 2012, at 5:40 PM, Romain Francoise <rfrancoise@debian.org> wrote:

> Chris Morgan <chmorgan@gmail.com> writes:
>
>> From the debian runtime library document, shouldn't there be a symlink
>> to the latest version of the library?
>
> Yes, there is one:
>
> /usr/lib/x86_64-linux-gnu/libpcap.so.0.8 -> libpcap.so.1.2.1
>
>> And isn't that something in the 1.x series? Is the version not 1.x?
>
> The version, yes. The soname, no.
>
>> The libpcap developers seem pretty receptive to things so I could talk
>> to them depending on what might help.
>
> There's nothing they can do about this, the upstream build defines a
> different soname. If someone were to package libpcap from scratch today
> they would probably use it, but each distribution has to live with its
> historical soname.
>
> --
> Romain Francoise <rfrancoise@debian.org>
> http://people.debian.org/~rfrancoise/




Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Mon, 27 Feb 2012 07:33:15 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sun Apr 20 23:30:40 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.