Your message dated Thu, 18 Jun 2009 16:43:18 -0500
with message-id <[email protected]>
and subject line Re: Bug#533422: Upgrade from 2.4.4 to 3.0.1
has caused the Debian Bug report #533422,
regarding Upgrade from 2.4.4 to 3.0.1
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 reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
533422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533422
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bacula-director-mysql
Version: 3.0.1-2
Severity: important
Hi!
I updated to 3.0.1-2 from 2.4.4-1 on a Lenny box. At end of apt-get install
the database seems not updated (still version 10). As well bacula-dir do not
work and produce errors in logs.
Does this update need to be applied manually (nothing found in
README.Debian) or is it a bug in the package?
Sincerely,
Stéphane
--- End Message ---
--- Begin Message ---
Hi Stephane,
Thank you for sending that log. Unfortunately, it didn't contain
anything that can help me out.
Since you are running a custom-built package, in a Debian distribution
different from the one that bacula 3.0.1-2 is compiled against in the
archive, there are a tremendous number of variables, and it will be
almost impossible for me to track down why this is happening for you.
The Debian BTS is used only for packages that actually exist in Debian
as well.
Therefore, I must close the bug.
-- John
Stephane Leclerc wrote:
> Package: bacula-director-mysql
> Version: 3.0.1-2
> Severity: important
>
>
>> It should be done automatically, unless you said that you don't want it
>> to do so when you first installed it. Can you send me a script(1) log
>> of a session to upgrade? You may need to re-downgrade first.
>
> Hi!
>
> I've done a new upgrade installation. Below is the part who do not work.
> After upgrade, the database need to be upgraded manually.
>
>
> Paramétrage de bacula-director-mysql (3.0.1-2) ...
> Installation de la nouvelle version du fichier de configuration
> /etc/bacula/scripts/make_catalog_backup ...
> dbconfig-common: writing config to
> /etc/dbconfig-common/bacula-director-mysql.conf
> *** WARNING: ucf was run from a maintainer script that uses debconf, but
> the script did not pass --debconf-ok to ucf. The maintainer
> script should be fixed to not stop debconf before calling ucf,
> and pass it this parameter. For now, ucf will revert to using
> old-style, non-debconf prompting. Ugh!
>
> Please inform the package maintainer about this problem.
> Processing configuration ...Ok.
> Stopping Bacula Director: bacula-dir.
> Starting Bacula Director: bacula-dir.
>
>
>
>
>
>
>
>
>
--- End Message ---
