Wireshark · Wireshark-dev: Re: [Wireshark-dev] Debian package on 1.8.0

[Benjamin Soriano <ben.the.rabbit@xxxxxxxxx>]

Hi,

Problem solved.

It's seems this bug is recurrent but doesn't produce same errors.
Indeed, I found an old bug on 1.6.2 with same result (can't build deb packages). (https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6049)

Problem show up when libraries versions in two following files doesn't match. These files are debian/wireshark-common.files and debian/wireshark-common.shlibs.

In 1.8.0 release content of the first one is : 

> ...
> /usr/lib/wireshark/libwireshark.so.2
> /usr/lib/wireshark/libwireshark.so.2.0.0
> /usr/lib/wireshark/libwiretap.so.2
> /usr/lib/wireshark/libwiretap.so.2.0.0
> /usr/lib/wireshark/libwsutil.so.2
> /usr/lib/wireshark/libwsutil.so.2.0.0
> ...

and second one :

> ...
> libwireshark 0 wireshark-common
> libwiretap 0 wireshark-common
> libwsutil 0 wireshark-common
> ...

So, I just replaced "0"s by "2"s in the second file, and it's now working properly.

I hope this will help someone !

Benjamin.

2012/9/20 Benjamin Soriano <ben.the.rabbit@xxxxxxxxx>

Hi,

Yeah, it seems if Wireshark packages are already installed it can lead to some problems. I obviously remove them from my system.

And as I say, this problem did not occur with a more recent version - on the same system.

Thanks you for your time!

Benjamin Soriano

On 19/09/2012 23:55, Jaap Keuter wrote:

Hi,

>From the bug comments this seems to depend more on what you have installed during the build, rather than a bugfix, which is not yet listed for this bug.

Thanks,
Jaap

On 09/19/2012 04:36 PM, Benjamin Soriano wrote:

Hi!

I have to generate debian package with some home-made plugins. Problem is I must
provide this packages in 1.8.0 version.

I notice two bugs. First one is noticed and fixed here :
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7406

Second one here :
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7408

is not fixed. But I succeed to generate packages on current version (svn). I
guess this bug has been fixed.

Is anyone can tell me where I can find a patch for this bug?

Thanks!

Benjamin.

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe