Bug#606262: [pkg-bacula-devel] Bug#606262: bacula-director-mysql lenny to squeeze database upgrade fail
On Thu, Apr 14, 2011 at 05:18:05PM +0200, Jan Hauke Rahm wrote: > Actually, our debian package already handles such upgrades. It simply > started off of a false premise, that is having db version 11 in lenny. > I'm still thinking about this but, if I'm not mistaken, the lenny > version just needs to run the upgrade script for 10->11 additionally to > the already set script for 11->12. And if that's so, it's basicall > uncommenting a line in debian/rules. That's nonsense. bacula-director-* ship sql upgrade files for 3.0.0 and 5.0.0 (which combined are the script Julien provided). Either dbconfig-common didn't catch up on both or something entirely different went wrong. Hauke -- .''`. Jan Hauke Rahmwww.jhr-online.de : :' : Debian Developer www.debian.org `. `'` Member of the Linux Foundationwww.linux.com `- Fellow of the Free Software Foundation Europe www.fsfe.org signature.asc Description: Digital signature
Bug#620963: backup catalog scripts are not created when using an existing mysql database
tags 620963 + moreinfo Hi Guillaume, On Tue, Apr 05, 2011 at 02:45:31PM +0200, Guillaume Voyau wrote: > backup catalog failed because of missing scripts that should be created > during > installation. > occur (only ?) when using an existing mysql database. > this files have not been created : > - /etc/bacula/scripts/make_catalog_backup.pl > - /etc/bacula/scripts/delete_catalog_backup I'm not sure how that happened. Can you give me the output of the following command, please? dpkg -L bacula-director-mysql | fgrep catalog_backup Hauke -- .''`. Jan Hauke Rahmwww.jhr-online.de : :' : Debian Developer www.debian.org `. `'` Member of the Linux Foundationwww.linux.com `- Fellow of the Free Software Foundation Europe www.fsfe.org signature.asc Description: Digital signature
Processed (with 5 errors): Re: Bug#620963: backup catalog scripts are not created when using an existing mysql database
Processing commands for cont...@bugs.debian.org: > tags 620963 + moreinfo Bug #620963 [bacula] backup catalog scripts are not created when using an existing mysql database Added tag(s) moreinfo. > Hi Guillaume, Unknown command or malformed arguments to command. > On Tue, Apr 05, 2011 at 02:45:31PM +0200, Guillaume Voyau wrote: Unknown command or malformed arguments to command. > > backup catalog failed because of missing scripts that should be created > > during Unknown command or malformed arguments to command. > > installation. Unknown command or malformed arguments to command. > > occur (only ?) when using an existing mysql database. Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 620963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130331029823761.transcr...@bugs.debian.org
Bug#612717: marked as done (bacula-server: broken dependencies, cannot install)
Your message dated Wed, 20 Apr 2011 16:50:17 +0200 with message-id <20110420145017.ga16...@ca.home.jhr-online.de> and subject line Re: Bug#612717: bacula-server: broken dependencies, cannot install has caused the Debian Bug report #612717, regarding bacula-server: broken dependencies, cannot install 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 ow...@bugs.debian.org immediately.) -- 612717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bacula-server Version: 5.0.2-2.2 Severity: important -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bacula-server depends on: pn bacula-director-sqlite3 | bac (no description available) pn bacula-sd (no description available) pn bacula-sd-sqlite3 | bacula-sd (no description available) Versions of packages bacula-server recommends: ii bacula-fd 2.4.4-1network backup, recovery and verif bacula-server suggests no packages. --- End Message --- --- Begin Message --- We cannot deal with empty reports. Specify what's actually broken with actual sentences, please. Hauke -- .''`. Jan Hauke Rahmwww.jhr-online.de : :' : Debian Developer www.debian.org `. `'` Member of the Linux Foundationwww.linux.com `- Fellow of the Free Software Foundation Europe www.fsfe.org signature.asc Description: Digital signature --- End Message ---
Bug#606262: [pkg-bacula-devel] Bug#606262: bacula-director-mysql lenny to squeeze database upgrade fail
This is how I created the script, by merging the /usr/share/dbconfig-common/data/bacula-director-mysq/upgrade/mysql/3.0.0 and 5.0.0 scripts. I'm afraid I can see where this is probably my fault. Under /etc/dbconfig-common/bacula-director-mysql.conf I do not have the dbc_dbuser and dbc_dbpass properly populated. This is because we setup bacula's database access without first going through the dpkg-reconfigure bacula-director-mysql. I apologize, and I would like to close the ticket. This was an issue on our end. On 04/20/2011 07:34 AM, Jan Hauke Rahm wrote: > On Thu, Apr 14, 2011 at 05:18:05PM +0200, Jan Hauke Rahm wrote: > >> Actually, our debian package already handles such upgrades. It simply >> started off of a false premise, that is having db version 11 in lenny. >> I'm still thinking about this but, if I'm not mistaken, the lenny >> version just needs to run the upgrade script for 10->11 additionally to >> the already set script for 11->12. And if that's so, it's basicall >> uncommenting a line in debian/rules. >> > That's nonsense. bacula-director-* ship sql upgrade files for 3.0.0 and > 5.0.0 (which combined are the script Julien provided). Either > dbconfig-common didn't catch up on both or something entirely different > went wrong. > > Hauke > > -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4daf6176.5020...@usainteanne.ca
Bug#606262: [pkg-bacula-devel] Bug#606262: bacula-director-mysql lenny to squeeze database upgrade fail
All that said, it maybe better 'fall mode' behavior, or at least present us with a better error message. Especially since dbc_dbadmin and dbc_dbname were set properly. The upgrade runs as dbc_dbuser as I understand though. It's an entirely moot point though, but in theory it could have run the upgrade as dbc_dbadmin rather than dbc_dbuser. Anyways, this is a separate issue and my bug that the upgrade script doesn't work was in error. On 04/20/2011 07:43 PM, Julien Savoie wrote: > This is how I created the script, by merging the > > /usr/share/dbconfig-common/data/bacula-director-mysq/upgrade/mysql/3.0.0 > and 5.0.0 scripts. > > I'm afraid I can see where this is probably my fault. Under > /etc/dbconfig-common/bacula-director-mysql.conf > I do not have the dbc_dbuser and dbc_dbpass properly populated. This is > because we setup bacula's database access without first going through > the dpkg-reconfigure bacula-director-mysql. > > I apologize, and I would like to close the ticket. This was an issue on > our end. > > On 04/20/2011 07:34 AM, Jan Hauke Rahm wrote: > >> On Thu, Apr 14, 2011 at 05:18:05PM +0200, Jan Hauke Rahm wrote: >> >> >>> Actually, our debian package already handles such upgrades. It simply >>> started off of a false premise, that is having db version 11 in lenny. >>> I'm still thinking about this but, if I'm not mistaken, the lenny >>> version just needs to run the upgrade script for 10->11 additionally to >>> the already set script for 11->12. And if that's so, it's basicall >>> uncommenting a line in debian/rules. >>> >>> >> That's nonsense. bacula-director-* ship sql upgrade files for 3.0.0 and >> 5.0.0 (which combined are the script Julien provided). Either >> dbconfig-common didn't catch up on both or something entirely different >> went wrong. >> >> Hauke >> >> >> -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4daf635f.5070...@usainteanne.ca
