Hi Volker, > I followed the discussion on the upgrade path of some users. Today I had > a look at my OpenDNSSEC version. It's 1.4.6 because it's the Debian > jessie package. When I look at the upcoming stretch release, there will > be 2.0.4.
When I look at my package manager (apt, Debian unstable) both 1.4.6 and 2.0.4 are available. So likely you can continue to use 1.4.6. (though that doesn't reflect on the packages.debian.org website, I'm not sure how that works) > Are there any binary packages available for running the 2.1.x > versions on Debian/Ubuntu? We do not provide such a thing. Ondřej Surý [1] packages OpenDNSSEC for Debian, maybe he's able to help you there. [1] https://qa.debian.org/developer.php?login=ondrej%40debian.org > I now see an issue on the path how to update and maintain a current > OpenDNSSEC version. > > Any suggestions? Am I required to compile OpenDNSSEC myself? I made some > bad experiences with self-compiling when I started using OpenDNSSEC. Well, if you end up with a 2.X any other than 2.1.1 and find yourself required to go over the migration steps I strongly recommend you to use the migration scripts from 2.1.1. So use the files from this directory instead: https://github.com/opendnssec/opendnssec/tree/2.1/develop/enforcer/utils/1.4-2.0_db_convert //Yuri
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Opendnssec-user mailing list [email protected] https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
