Now that I know how things are more-or-less supposed to work in this
situation (see thread started: https://lists.ubuntu.com/archives/ubuntu-
devel-discuss/2010-March/010844.html) I'll contact the debian maintainer
and see what he says.
--
libpcap0.8-dev package should not contain libpcap
From the maintainer:
'0.8' refers to the library soname, not the version. The ABI has
remained unchanged since libpcap 0.8 (where this soname was
introduced), so the soname (and in consequence, the packages names)
haven't changed.
The reason why the soname is 0.8 rather than e.g. 0 or 1 is
On Wed, Mar 10, 2010 at 11:36 AM, eapache eapa...@gmail.com wrote:
'0.8' refers to the library soname, not the version. The ABI has
remained unchanged since libpcap 0.8 (where this soname was
introduced), so the soname (and in consequence, the packages names)
haven't changed.
The reason why
I'll ping devel-discuss and see what turns up.
--
libpcap0.8-dev package should not contain libpcap headers equal to version 0.9.x
https://bugs.launchpad.net/bugs/311634
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'm not sure that upstream is where to go, since it seems more like a
packaging problem on our end than anything.
I'll note additionally that the libpcap0.8 package (the library itself)
seems to contain libs equal to 1.0.
Something fishy is going on.
** Changed in: libpcap (Ubuntu)
On initial glance it doesn't appear that the package has been renamed and
the headers still appear to remain the same. Can you verify upstream?
--
Kristian Erik Hermansen
(Note: Please excuse any grammar or spelling mistakes as this message may
have been verbally dictated via the speech
This bug was reported over a year ago. I apologize for taking so long to
respond, but would it be possible for you to determine if this bug still
exists in the latest version of Ubuntu?
** Changed in: libpcap (Ubuntu)
Status: New = Incomplete
--
libpcap0.8-dev package should not contain
