[Bug 394784] Re: TCP header fields not correct on 64 bit machines

2010-03-31 Thread Bug Watch Updater
** Changed in: libnet (Debian) Status: New = Fix Released -- TCP header fields not correct on 64 bit machines https://bugs.launchpad.net/bugs/394784 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 394784] Re: TCP header fields not correct on 64 bit machines

2009-10-07 Thread Bug Watch Updater
** Changed in: libnet (Debian) Status: Unknown = New -- TCP header fields not correct on 64 bit machines https://bugs.launchpad.net/bugs/394784 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 394784] Re: TCP header fields not correct on 64 bit machines

2009-07-15 Thread David Stansby
Since libnet1 is currently being used in Karmic, I presume this can be set a fix released? -- TCP header fields not correct on 64 bit machines https://bugs.launchpad.net/bugs/394784 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 394784] Re: TCP header fields not correct on 64 bit machines

2009-07-15 Thread jsteel
I think that is reasonable. We required libnet0 for a source installation of another program, but since the the actual libnet0 would never have worked, whats the point in fixing the libnet0 deb that is available. Will libnet0 eventually be removed from the repository? -- TCP header fields not

[Bug 394784] Re: TCP header fields not correct on 64 bit machines

2009-07-15 Thread David Stansby
The main reason that I put the previous comment was that I searched for libnet0 in the karmic repos. In fact, looking here: http://packages.ubuntu.com/jaunty/libnet0 it seems that libnet0 is only in Jaunty, and is obsolete. As such, I'll change the status of this bug to fix released. ** Changed

[Bug 394784] Re: TCP header fields not correct on 64 bit machines

2009-07-08 Thread fabrice_sp
** Bug watch added: Debian Bug tracker #536202 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536202 ** Changed in: libnet (Debian) Importance: Undecided = Unknown ** Changed in: libnet (Debian) Status: New = Unknown ** Changed in: libnet (Debian) Remote watch: None = Debian Bug

[Bug 394784] Re: TCP header fields not correct on 64 bit machines

2009-07-08 Thread jsteel
There has been a confusion between the libnet0 and libnet1 packages on Ubuntu. I have personally investigated this bug now and found that there is no problem with libnet-1.1.x, but rather the libnet0 package, which is libnet-1.0.2a. It looks like libnet1 has fixed this exact problem. The patch

[Bug 394784] Re: TCP header fields not correct on 64 bit machines

2009-07-07 Thread Brian Murray
** Also affects: libnet (Debian) Importance: Undecided Status: New ** Tags added: bitesize ** Changed in: libnet (Ubuntu) Importance: Undecided = Medium ** Changed in: libnet (Ubuntu) Status: New = Triaged -- TCP header fields not correct on 64 bit machines

[Bug 394784] Re: TCP header fields not correct on 64 bit machines

2009-07-02 Thread J. Collins
** Attachment added: A patch to fix the above bug. http://launchpadlibrarian.net/28635232/libnet_64.diff -- TCP header fields not correct on 64 bit machines https://bugs.launchpad.net/bugs/394784 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed