On Sun, Jan 11, 2015 at 10:12 PM, Paul Gevers <elb...@debian.org> wrote: > On Mon, 10 Mar 2014 21:47:20 +0200 Andrey Utkin > <andrey.ut...@corp.bluecherry.net> wrote: >> The concern is that user is asked whether they want to perform DB >> upgrade, and default answer is "no". For us, ideally it should perform >> it without asking. > > Are you talking from a system administrator perspective, or from a > package maintainer perspective? If the later, which package? > >> dbconfig-common does not document any parameter to override its >> behavior regarding this, and this is likely still actual for latest >> version, too. > > All the default answers that are used during package > config/postinst/postrm/preinst/prerm are stored in > /etc/dbconfig-common/<package>.conf and can be changed there before > taking action. I assume this is not what you mean. > >> We appreciate >> - addition of such parameter, > > Please elaborate what you want to achieve exactly. > >> - documentation on achieving the behavior descibed above, >> - workaround suggestions. > > If you are concerned about package maintainership, I think you can do > this for new installs by doing "db_set <package>/dbconfig-upgrade true" > before calling dbconfig-common in the maintainer scripts.
Still thank you for your reply, after 10 months delay :) Sorry, not going to answer your questions or continue this discussion, because dbconfig-common got replaced with our own scripts in our project. Just FYI, besides the inconvenience described in the starting letter (sorry again, not going to check whether your advice is going to work), AFAIR dbconfig-common also failed with MySQL passwords containing spaces. -- Bluecherry developer. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
