Package: mysql-common-4.1
Version: 4.1.11a-4sarge2
Severity: important
Hopefully, I am not wasting your time...
I went to upgrade mysql today from 4.1.11a-4sarge1 to 4.1.14-6, and it is
trying to depend on mysql-common
5.0.13rc-1, as the latest 4.1 version that is available is 4.1.11a-4sarge2.
With all the warnings about "being brave" and "beta, be careful", it makes me
wary of upgrading mysql-common
to 5.0, plus it seems a little funny to have mysql-common at 5.0, and
mysql-{client,server} at 4.1.
Is this a bug, or should I just go ahead and leave server/client at 4.1, and
allow debian to upgrade
mysql-common to 5.0?
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11.7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ANSI_X3.4-1968) (ignored: LC_ALL
set to C)
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
