retitle 694542 unblock: opendnssec/1.3.9-4 thank you Debdiff against -2 attached, diffstat:
README.Debian | 16 ++++++ changelog | 17 +++++++ patches/011-return_if_open_parse_of_zonelist.xml_fails.patch | 26 +++++++++++ patches/012-fix_RRSIGs_with_glue.patch | 18 +++++++ patches/013-fix_zone_delete_with_MySQL.patch | 23 +++++++++ patches/series | 3 + 6 files changed, 102 insertions(+), 1 deletion(-) Ondrej On Tue, Jan 15, 2013 at 10:28 AM, Ondřej Surý <ond...@debian.org> wrote: > Hi Adam, > > On Sat, Dec 29, 2012 at 12:47 AM, Adam D. Barratt > <a...@adam-barratt.org.uk> wrote: >> Hi, >> >> Apologies for the delay in getting back to you about this. > > same here. > >> On Wed, 2012-11-28 at 08:33 +0100, Ondřej Surý wrote: >>> On Tue, Nov 27, 2012 at 9:37 PM, Adam D. Barratt >>> <a...@adam-barratt.org.uk> wrote: >>> > On Tue, 2012-11-27 at 14:55 +0100, Ondřej Surý wrote: >>> >> + OPENDNSSEC-338: ods-ksmutil zone delete --all does not work >>> > [...] >>> > + If you have created your database in version 1.3.9, you should run >>> > + following statement in your OpenDNSSEC MySQL database: >>> > + >>> > + alter table dnsseckeys drop foreign key dnsseckeys_ibfk_1; >>> > >>> > Apologies for a possibly stupid question, but is there any way that >>> > could be automated rather than users having to make manual changes? >>> >>> Not stupid question at all. I thought about automating the process >>> myself, but then I realized that I have no way of knowing if the >>> database was created with version 1.3.9. >> >> Would something along the lines of "if key exists alter table" be >> feasible? Presumably if the key exists then the likelihood is that the >> package created it. > > > Well, I tried and I have ended with a scary patch which I am attaching > for a reference. I don't think it's good idea to go this way at this > moment. > >>> E.g. this is triggered (and the alter table should be run) only in >>> rare circumstances when the user has installed opendnssec 1.3.9-X from >>> wheezy for a first time. People upgrading from squeeze or people >>> upgrading from older releases should not be affected by this bug. >> >> This also means that all opendnssec users upgrading from squeeze will >> potentially be presented with the prompt, which isn't an ideal upgrade >> experience. > > True. I have decided to remove the NEWS file, since the conditions of > triggering this bug are rare (deleting all keys), and number people > using MySQL with OpenDNSSEC is low. I just put the text to > README.Debian, where it could happily live. > > I will be uploading new version with those changes today. > > O. > -- > Ondřej Surý <ond...@sury.org> -- Ondřej Surý <ond...@sury.org>
opendnssec_1.3.9-4.debdiff
Description: Binary data
