On 2013-03-03 21:28, Marc Haber wrote: > In squeeze, pdns's database backends do not immediately work after > package installation. It is necessary to manually create the database > after installing the package. Wheezy's pdns, on the other hand, uses > dbconfig-common to automatically create the databases.
Thanks for clarifying this. > piuparts does not bother to create a database before trying the > upgrade, installs a broken pdns which never worked on squeeze, and > only notices this after trying to upgrade to wheezy. If database creation is trivially scriptable, I could add a pre_install/post_install hook script to piuparts to do this (if someone supplies such a script). > It would of course be possible to catch this situation during the > upgrade to wheezy and to assume a fresh install. Otoh, this is a > pathological case. Noone would install a DNS server and have it run > in a broken, non functional state. Please comment whether it would be > acceptable to flag this as a bug in squeeze's pdns and downgrade it to > normal or even wishlist. Since installation in squeeze succeeded I assumed the package was actually functional. Feel free to downgrade the severity, but keep the bug found in the wheezy version s.t. piuparts-analyze can classify this as a known and bugged failure. > I would accept a patch that would make wheezy's PowerDNS fail more > gracefully on an unconfigured squeeze database on update, but at the > moment I have to say that I am not going to spend my time on > developing a work-around for a pathological synthetic test case and do > sincerely apologize for that. That's OK. This "pathological synthetic test case" works fine for most packages, and will work for pdns/wheezy. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
