-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
Am So den 21. Feb 2010 um 23:26 schrieb sean finney:
> The question is definitely confusing, and i believe it's even been
> reported before. I think asking the upgrade question instead of
> the install question would make it less ambiguous. For reference:
[...]
> Technically, it might still be a bit misleading as upgrades might not
> actually need to be performed, but it at least doesn't mislead the user
> to select the opposite of what they probably want to select. do you agree
> that this question is better or should we draft a new question entirely?
I'm not sure too. How is the case of a complete new installation
diverted from the update procedure? I think that should at least be
addressed by proper questions. Maybe that needs the second suggestion
with a new debconf-template.
> > However, later on I tried to say yes here (with having a backup of the
> > database) and I also didn't get asked to update the existing database.
>
> this may be because you already upgraded, and were instead reconfiguring
> at the new version level? dbconfig-common itself doesn't keep much state
> and instead relies on what it's given via the maintainer scripts.
Odd. I did not dive in to dbconfig-common until yet. But as I believe
this should be possible to do with dpkg-reconfigure.
> > However, also if I say not to manage the database with dbconfig-common,
> > there should be the update scripts anywhere around so I can use it
> > myself. Maybe put it to /usr/share/doc/bacula/... Not wanting dbconfig
> > to manage the database doesn't mean that the database do not have to be
> > converted.
>
> take a look under /usr/share/dbconfig-common/{data,scripts}/<pkg>, which
> should have all of the sql and/or scripts provided by the package. you
> might not be able to execute it directly depending on whether they're using
> some of the advanced features (scripts or template substitutions), but
> it should at least get you started in the right direction. that said the
> aim of dbconfig-common is to make this as transparent as possible.
[...]
> suggestions, feedback(, and ideally patches) are always welcome.
Yes, as I told before. The files under /usr/share/dbconfig-common are a
help. But I think, it is easy to also copy the update scripts from the
distribution to /usr/share/doc/<pkg> as that is the place where it is
expected (at least by me). This should not be that much work to do.
Maybe I'll find a minute the next days to file a patch.
Regards
Klaus
- --
Klaus Ethgen http://www.ethgen.de/
pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <kl...@ethgen.de>
Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQEVAwUBS4JK15+OKpjRpO3lAQop1gf/QgD1MMlYNPjkkMZa9x3pywiDBm4hNk/a
vHft913M6jiS9jsyWgDgtmZH9R14IRjgqQjN/lPn9DYekzYZuxxycohQS7FZgWFU
RE2/aZH66C/9kVJ7EOnIFg96zEEbc6yJwtNEmnRkmA45gfFdFkD2KxisAwV+wvZk
MwhYEuPV10Jw20YqcNkz9Bgfne8YHK+H7bTRea3TiAbtRllW+OUO949dZDKD7OqC
cHwpHk8C9hRU7imVfYfdIkIhVN9d1OxZrCITEQPT9LQsNwwHPxb2kT1PTf0zFe3m
KhlFK+47SxXNNWycqTeZCH8SJ/NKNakRlfQSA3kFLaZb2gVTdJAFKQ==
=XL8A
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
