Your message dated Sun, 13 Apr 2003 23:22:49 -0500
with message-id <[EMAIL PROTECTED]>
and subject line closing bug
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reop
Previously Marek Habersack wrote:
> What about a case as mine - Pike 7.4 is MPL/GPL/LGPL. How does that look in
> this situation?
You might get away with the MPL/LGPL options, but you should probably
ask for confirmation on debian-legal.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]>
On Sat, Apr 12, 2003 at 09:06:35PM +0200, Wichert Akkerman wrote:
> Previously Steve Langasek wrote:
> > The new libmysqlclient12 package comes from MySQL 4.0. It has been
> > known for some time that the libmysqclient library in MySQL 4.0 would
> > *not* be released under the LGPL: it is GPL only
Quoting Wichert Akkerman ([EMAIL PROTECTED]):
> Previously Marek Habersack wrote:
> > What about a case as mine - Pike 7.4 is MPL/GPL/LGPL. How does that look in
> > this situation?
> You might get away with the MPL/LGPL options, but you should probably
> ask for confirmation on debian-legal.
So,
Previously Sander Smeenk wrote:
> So, what *am* I supposed to do? Rebuild against libmysqlclient12
> and break licenses? Not rebuild and have an uninstallable snort-mysql?
The only viable approaches seem to be (in random order)
* fork libmysqlclient
* convince the MySQL folks to revert their li
On Mon, Apr 14, 2003 at 01:25:28PM +0200, Sander Smeenk wrote:
> Should we massively ask permission to explicitly link against OpenSSL
> from the OpenSSL upstream? It was something like that, right? You were
> supposed to ask permission to link against OpenSSL.
No, you need permission from the aut
On Mon, Apr 14, 2003 at 01:30:26PM +0200, Wichert Akkerman wrote:
> Previously Sander Smeenk wrote:
> > So, what *am* I supposed to do? Rebuild against libmysqlclient12
> > and break licenses? Not rebuild and have an uninstallable snort-mysql?
>
> The only viable approaches seem to be (in random
On Tue, Apr 15, 2003 at 12:05:49AM +1000, Hamish Moffatt wrote:
> On Mon, Apr 14, 2003 at 01:30:26PM +0200, Wichert Akkerman wrote:
> > Previously Sander Smeenk wrote:
> > > So, what *am* I supposed to do? Rebuild against libmysqlclient12
> > > and break licenses? Not rebuild and have an uninstalla
On Mon, Apr 14, 2003 at 04:10:11PM +0200, Francesco P. Lovergine wrote:
> > > > So, what *am* I supposed to do? Rebuild against libmysqlclient12
> > > > and break licenses? Not rebuild and have an uninstallable snort-mysql?
> > >
> > > The only viable approaches seem to be (in random order)
> > >
Processing commands for [EMAIL PROTECTED]:
> tag 175816 + fixed
Bug#175816: mpsql: conflicts with current postgresql
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debi
[Should this thread be carried over to debian-devel?]
On Mon, Apr 14, 2003 at 01:25:28PM +0200, Sander Smeenk wrote:
> Quoting Wichert Akkerman ([EMAIL PROTECTED]):
> > Previously Marek Habersack wrote:
> > > What about a case as mine - Pike 7.4 is MPL/GPL/LGPL. How does that look
> > > in
> > >
On Mon, Apr 14, 2003 at 04:10:11PM +0200, Francesco P. Lovergine wrote:
> On Tue, Apr 15, 2003 at 12:05:49AM +1000, Hamish Moffatt wrote:
> > On Mon, Apr 14, 2003 at 01:30:26PM +0200, Wichert Akkerman wrote:
> > > Previously Sander Smeenk wrote:
> > > > So, what *am* I supposed to do? Rebuild again
Steve Langasek, on 2003-04-14, 09:38, you wrote:
> There's also no wiggle room for "indirect linking" arguments, because
> Debian is distributed as a cohesive whole: if we distribute GPL app foo
> linked against LGPL library bar, and Debian's copy of libbar is linked
> against OpenSSL, you cannot a
On Mon, Apr 14, 2003 at 05:37:15PM +0200, Joerg Wendland wrote:
> Steve Langasek, on 2003-04-14, 09:38, you wrote:
> > There's also no wiggle room for "indirect linking" arguments, because
> > Debian is distributed as a cohesive whole: if we distribute GPL app foo
> > linked against LGPL library ba
On Mon, Apr 14, 2003 at 04:16:12PM +0200, Christian Hammers scribbled:
> On Mon, Apr 14, 2003 at 04:10:11PM +0200, Francesco P. Lovergine wrote:
> > > > > So, what *am* I supposed to do? Rebuild against libmysqlclient12
> > > > > and break licenses? Not rebuild and have an uninstallable
> > > > >
I think DSA-281 [1] addresses this buffer overflow in moxftp, but I
haven't looked to see if it is the same issue.
[1] http://www.debian.org/security/2003/dsa-281
Drew Daniels
On Mon, Apr 14, 2003 at 06:23:24PM +0200, Marek Habersack wrote:
> > > > > The only viable approaches seem to be (in random order)
> > > > >
> > > > > * fork libmysqlclient
> > > > > * convince the MySQL folks to revert their license change
> > > > > * switch to postgres
> > > > > * get upstream
On Mon, Apr 14, 2003 at 09:34:48PM +0200, Christian Hammers wrote:
> On Mon, Apr 14, 2003 at 06:23:24PM +0200, Marek Habersack wrote:
> > > > > > The only viable approaches seem to be (in random order)
> > > > > >
> > > > > > * fork libmysqlclient
> > > > > > * convince the MySQL folks to revert
18 matches
Mail list logo
