On Thu, Mar 03, 2005 at 06:38:33AM +1100, Adam Conrad wrote:
> Theodore Ts'o said:
> > My system (currently running unstable, but it from the your description
> > it sounds like it may be happening on sarge as well) has an
> > apache2/mysql/php4 combination which blows up the moment you try to ope
Theodore Ts'o said:
>
> My system (currently running unstable, but it from the your description
> it sounds like it may be happening on sarge as well) has an
> apache2/mysql/php4 combination which blows up the moment you try to open
> a connection to a mysql database.
Are you sure you're note expe
On Fri, Jan 28, 2005 at 05:03:26AM -0800, Steve Langasek wrote:
> As a result, in spite of the timing wrt the release, I'm proposing a
> transition to libmysqlclient12 for a number of packages for sarge. The
> packages listed below are those packages currently in sarge which either are
> broken wi
On Sun, Feb 13, 2005 at 12:07:06PM +1100, Paul Hampson wrote:
> > So what if we had two editions of libmysqlclient, one of them
> > ssl-enabled and the other - as currently - not? That would allow
> > using ssl whenever possible. I think that could be done, without
> > breaking things.
>
> That's
On Sat, Feb 12, 2005 at 08:25:41PM +0100, Francesco Paolo Lovergine wrote:
> On Sat, Feb 12, 2005 at 09:17:44AM -0800, Steve Langasek wrote:
> > On Sat, Feb 12, 2005 at 09:53:34AM +0100, Francesco Paolo Lovergine wrote:
> > > > > Nice, so we should check that any linked GPL library directly
> > >
On Sat, Feb 12, 2005 at 09:17:44AM -0800, Steve Langasek wrote:
> On Sat, Feb 12, 2005 at 09:53:34AM +0100, Francesco Paolo Lovergine wrote:
> > > > Nice, so we should check that any linked GPL library directly
> > > > (obviuolsy) or
> > > > indirectly (with N=1,2,3... levels of indirection) linke
On Sat, Feb 12, 2005 at 09:53:34AM +0100, Francesco Paolo Lovergine wrote:
> > > Nice, so we should check that any linked GPL library directly (obviuolsy)
> > > or
> > > indirectly (with N=1,2,3... levels of indirection) linked against
> > > openssl adds the exception.
> > No, we should simply no
On Sat, Feb 12, 2005 at 12:39:58AM -0800, Steve Langasek wrote:
>
> > Nice, so we should check that any linked GPL library directly (obviuolsy) or
> > indirectly (with N=1,2,3... levels of indirection) linked against
> > openssl adds the exception.
>
> No, we should simply not be linking libmysql
On Sat, Feb 12, 2005 at 09:14:26AM +0100, Francesco Paolo Lovergine wrote:
> On Fri, Feb 11, 2005 at 03:30:59PM -0800, Steve Langasek wrote:
> > On Fri, Feb 11, 2005 at 03:31:44PM +0100, Christian Hammers wrote:
> > > On 2005-02-11 sean finney wrote:
> > > > On Fri, Feb 11, 2005 at 10:15:55AM +0100
On Fri, Feb 11, 2005 at 03:30:59PM -0800, Steve Langasek wrote:
> On Fri, Feb 11, 2005 at 03:31:44PM +0100, Christian Hammers wrote:
> > On 2005-02-11 sean finney wrote:
> > > On Fri, Feb 11, 2005 at 10:15:55AM +0100, Francesco P. Lovergine wrote:
> > > > FYI: new mysql FLOSS includes OpenSSL licen
On Fri, Feb 11, 2005 at 03:31:44PM +0100, Christian Hammers wrote:
> On 2005-02-11 sean finney wrote:
> > On Fri, Feb 11, 2005 at 10:15:55AM +0100, Francesco P. Lovergine wrote:
> > > FYI: new mysql FLOSS includes OpenSSL license, so many packages could
> > > migrate to current libmysqlclient start
Hello
On 2005-02-11 sean finney wrote:
> On Fri, Feb 11, 2005 at 10:15:55AM +0100, Francesco P. Lovergine wrote:
> > FYI: new mysql FLOSS includes OpenSSL license, so many packages could
> > migrate to current libmysqlclient starting from no starting from now..
>
> that's great to hear! i'm cc'i
On Fri, Feb 11, 2005 at 10:15:55AM +0100, Francesco P. Lovergine wrote:
> FYI: new mysql FLOSS includes OpenSSL license, so many packages could
> migrate to current libmysqlclient starting from no starting from now..
that's great to hear! i'm cc'ing the relevant wishlist bug i have open
against m
FYI: new mysql FLOSS includes OpenSSL license, so many packages could
migrate to current libmysqlclient starting from no starting from now..
--
Francesco P. Lovergine
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Wed, Feb 02, 2005 at 09:49:31PM +0100, Andreas Metzler wrote:
>
> > For what concern proftpd, it does not use libpam-mysql at all,
> > so I see no problem for that.
>
> Hello,
> Ehh. As maintainer of a PAM-using application you usually have no
> control which PAM modules are used. You just shi
[Cc ing Frankie as the [EMAIL PROTECTED] addresses appear to be non-functional]
On 2005-01-31 Francesco Paolo Lovergine <[EMAIL PROTECTED]> wrote:
> On Sat, Jan 29, 2005 at 02:34:07PM +0100, Andreas Metzler wrote:
> > These four packages also link against both libpam and libmysqlclient10
> > and mi
On Sat, Jan 29, 2005 at 02:34:07PM +0100, Andreas Metzler wrote:
> Hello,
> These four packages also link against both libpam and libmysqlclient10
> and might experience segfaults when accessing MYSQL over PAM with
> libpam-mysql if libpam-mysql switched to libmysqlclient12:
>
> linesrv-mysql, pur
On 2005-01-28 Steve Langasek <[EMAIL PROTECTED]> wrote:
[...]
> It would also probably be a good idea to transition these packages at the
> same time:
> dovecot-common
> exim4-daemon-heavy
> libnss-mysql
> libnss-mysql-bg
> libpam-mysql
> libsasl2-modules-sql
[...]
Hello,
These four p
On Fri, Jan 28, 2005 at 08:17:18PM +0100, Andreas Metzler wrote:
> On 2005-01-28 sean finney <[EMAIL PROTECTED]> wrote:
> > On Fri, Jan 28, 2005 at 04:36:05PM +0100, Andreas Metzler wrote:
> > > On Fri, Jan 28, 2005 at 05:03:26AM -0800, Steve Langasek wrote:
> > > [...]
> > > > Over the past six m
On 2005-01-28 sean finney <[EMAIL PROTECTED]> wrote:
> On Fri, Jan 28, 2005 at 04:36:05PM +0100, Andreas Metzler wrote:
> > On Fri, Jan 28, 2005 at 05:03:26AM -0800, Steve Langasek wrote:
> > [...]
> > > Over the past six months, the situation has changed
> > > significantly. The mysql maintainer
On Fri, Jan 28, 2005 at 04:36:05PM +0100, Andreas Metzler wrote:
> On Fri, Jan 28, 2005 at 05:03:26AM -0800, Steve Langasek wrote:
> [...]
> > Over the past six months, the situation has changed significantly. The
> > mysql maintainer, mysql upstream, and others have admirably worked through
> >
On Fri, Jan 28, 2005 at 05:03:26AM -0800, Steve Langasek wrote:
[...]
> Over the past six months, the situation has changed significantly. The
> mysql maintainer, mysql upstream, and others have admirably worked through
> the license issues to get a license exception that meets the needs of the
>
Previously, a number of packages have had to continue to link against
libmysqlclient10 in spite of the availability of libmysqlclient12 libraries
from upstream's MySQL 4.0 release. Some of these have been due to the lack
of a clear license exemption allowing libmyslqclient12 to be linked from
GPL-
23 matches
Mail list logo
