clone 307473 -1
reassign 307473 mysql-server-4.1
close 307473
reassign -1 mysql-server
thanks
The fixed version of mysql-dfsg-4.1 has reached testing; we're just
waiting for the m68k build of mysql-dfsg to be available before it will be
fixed in 4.0 as well.
Cheers,
--
Steve Langasek
postmodern
On Fri, May 06, 2005 at 04:57:05PM +0200, Christian Hammers wrote:
> The first statement sounds better but I'm not sure if #DEBHELPER# gets
> replaced if it's not the very last statement. So if we include the
i'm pretty sure it does. from debhelper(7):
Some debhelper commands will automat
Hi Sean
On 2005-05-06 Sean Finney wrote:
> however, i did still notice one problem. when you purge mysql-server,
> it still does all the debhelper-added code, so it stops the mysql
> daemon and attempts (unsuccessfully, because it still exists) to
> call update-rc.d to remove the runlevel symlink
hey christian,
i've tested out the latest svn version, and it looks like the
rm -rf problem is fixed. to test, i did the following:
apt-get install the current unstable version of mysql-server and family
apt-get install msyql-server-4.1
dpkg -P mysql-server
say yes at debconf purge
*boom*, as a
Hi
On 2005-05-05 Sean Finney wrote:
> On Thu, May 05, 2005 at 07:01:45PM +0200, Christian Hammers wrote:
> > So it's: "if ( dh_answer==true and no_other_installed_server ) purge();"
>
> okay, that makes sense.
>
> the no_other_installed_server could probably be simplified, now that i'm
> think
On Thu, May 05, 2005 at 07:01:45PM +0200, Christian Hammers wrote:
> So it's: "if ( dh_answer==true and no_other_installed_server ) purge();"
okay, that makes sense.
the no_other_installed_server could probably be simplified, now that i'm
thinking of it. since this is in the postrm, the packag
Hello
On 2005-05-05 Sean Finney wrote:
> On Thu, May 05, 2005 at 04:34:47AM +0200, Christian Hammers wrote:
> > I think the following will work:
> > 1. Seting Woodies debconf answer to false once MySQL 4.0 or 4.1 gets
> > installed so that his danger is voided once for all.
>
> sounds like a
hey christian,
On Thu, May 05, 2005 at 04:34:47AM +0200, Christian Hammers wrote:
> I think the following will work:
> 1. Seting Woodies debconf answer to false once MySQL 4.0 or 4.1 gets
> installed so that his danger is voided once for all.
sounds like a good idea for woody.
> 2. To prev
Hello Sean
I think the following will work:
1. Seting Woodies debconf answer to false once MySQL 4.0 or 4.1 gets
installed so that his danger is voided once for all.
2. To prevent 4.0, 4.1 and soon 5.0, which asks the Debconf question
only immediately before purging in the postrm script,
tags 307473 + pending
thanks
Hello Adrian
On 2005-05-03 Adrian Bunk wrote:
> BTW2: This is a nice example for the class of data loss bugs
> testing cannot catch because it might take some time
> until the first usre falls into this trap.
Indeed. Thanks for spotting this.
I will try
Processing commands for [EMAIL PROTECTED]:
> tags 307473 + pending
Bug#307473: Purging mysql-server can kill mysql-server-4.1
There were no tags set.
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system adminis
Package: mysql-server, mysql-server-4.1
Version: 4.0.24-7
Severity: critical
apt-get install mysql-server
apt-get remove mysql-server
apt-get install mysql-server-4.1
dpkg --purge mysql-server
***boom***
Depending on your answer to "postrm_remove_databases", this
has deleted all your data or "o
12 matches
Mail list logo
