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 unstabl
Hi Yuri,
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. Are there any binary packages available for running the 2.1.x
On 20-04-17 17:53, Eliot Lear wrote:
> Given this, can those of us on 1.4 expect a 2.1.1 release?
As of today we made a release of 2.1.1.
For those who are still living in the past, when there was only one true
way of rolling your keys, and changing polices would botch your
database, we also made
Le 21/04/2017 à 10:05, Yuri Schaeffer a écrit :
>> So noone really tested migrating a MySQL backed OpenDNSSEC
>> installation from 1.4 to 2.x? I'm a bit concerned about this, as there
>> are a lot of TLDs using OpenDNSSEC. Do they all still use 1.4? Do they
>> not use MySQL? Didn't anyone test this
> Given this, can those of us on 1.4 expect a 2.1.1 release?
Yes. A patch release next week seems reasonable after we discuss it in
our team.
//Yuri
signature.asc
Description: OpenPGP digital signature
___
Opendnssec-user mailing list
Opendnssec-user
> I can confirm that your patch does indeed fix it for me,
Thank you.
//Yuri
signature.asc
Description: OpenPGP digital signature
___
Opendnssec-user mailing list
Opendnssec-user@lists.opendnssec.org
https://lists.opendnssec.org/mailman/listinfo/ope
Op 21-04-17 om 09:33 schreef Sebastian Wiesinger:
> * Yuri Schaeffer [2017-04-20 16:08]:
>>> And on to the next error:
>>> So... yeah
>>
>> Ah! I was wondering why it felt like I fixed those issues already. Here
>> they are:
>> https://github.com/opendnssec/opendnssec/pull/661
>>
>> They're still
* Yuri Schaeffer [2017-04-21 10:05]:
> > So noone really tested migrating a MySQL backed OpenDNSSEC
> > installation from 1.4 to 2.x? I'm a bit concerned about this, as there
> > are a lot of TLDs using OpenDNSSEC. Do they all still use 1.4? Do they
> > not use MySQL? Didn't anyone test this in de
> So noone really tested migrating a MySQL backed OpenDNSSEC
> installation from 1.4 to 2.x? I'm a bit concerned about this, as there
> are a lot of TLDs using OpenDNSSEC. Do they all still use 1.4? Do they
> not use MySQL? Didn't anyone test this in development?
Well, I did test it. But it is a c
* Yuri Schaeffer [2017-04-20 16:08]:
> > And on to the next error:
> > So... yeah
>
> Ah! I was wondering why it felt like I fixed those issues already. Here
> they are:
> https://github.com/opendnssec/opendnssec/pull/661
>
> They're still in a pull request and not released yet.
Thank you for t
Hi Juri,
Given this, can those of us on 1.4 expect a 2.1.1 release?
Eliot
On 4/20/17 4:08 PM, Yuri Schaeffer wrote:
>> And on to the next error:
>> So... yeah
> Ah! I was wondering why it felt like I fixed those issues already. Here
> they are:
> https://github.com/opendnssec/opendnssec/pull/66
> And on to the next error:
> So... yeah
Ah! I was wondering why it felt like I fixed those issues already. Here
they are:
https://github.com/opendnssec/opendnssec/pull/661
They're still in a pull request and not released yet.
//Yuri
signature.asc
Description: OpenPGP digital signature
__
* Yuri Schaeffer [2017-04-20 14:37]:
> Hi Sebastian,
>
> > Converting database
> > ERROR 1064 (42000) at line 663: You have an error in your SQL syntax;
> > check the manual that corresponds to your MySQL server version for the
> > right syntax to use near '--Set to OMN if Tactive + Dttl < Tnow
>
Hi Sebastian,
> Converting database
> ERROR 1064 (42000) at line 663: You have an error in your SQL syntax;
> check the manual that corresponds to your MySQL server version for the
> right syntax to use near '--Set to OMN if Tactive + Dttl < Tnow
> UPDATE keyState
> SET state = 2
> WHERE keySta' a
* Yuri Schaeffer [2017-02-22 10:54]:
> Dear Community,
>
> No issues with the RC1 have come up in the last 1.5 weeks so hereby we
> announce the OpenDNSSEC 2.1.0 release.
>
> OpenDNSSEC 2.1 development was focused on improving the daemon code for
> the Signer and Enforcer. As such it is much mor
On 03/02/17 11:04, Yuri Schaeffer wrote:
> Hmm strange, not having libunwind should be caught by configure.
configure.ac is only checking for the lib, not the headers.
line 222:
> AC_CHECK_LIB(unwind, unw_backtrace, [AC_DEFINE([HAVE_LIBUNWIND],
> [1], [Define if libunwind supported]) LIBS="$LIBS
"Wytze van der Raay" schreef in bericht
news:aed42a16-7350-722a-eb6c-94656cc3c...@deboca.net...
Hi Fred,
On 03/02/2017 11:27 AM, Fred.Zwarts wrote:
...
Then there was a fatal error:
janitor.c:54:23: fatal error: libunwind.h: No such file or directory
#include
^
compilat
On 03/02/2017 12:09 PM, Wytze van der Raay wrote:
> Hi Fred,
>
> On 03/02/2017 11:27 AM, Fred.Zwarts wrote:
>> ...
>> Then there was a fatal error:
>> janitor.c:54:23: fatal error: libunwind.h: No such file or directory
>> #include
Thanks for reporting it. Unwind is not necessary, for some reas
Hi Fred,
On 03/02/2017 11:27 AM, Fred.Zwarts wrote:
> ...
> Then there was a fatal error:
> janitor.c:54:23: fatal error: libunwind.h: No such file or directory
> #include
> ^
> compilation terminated.
>
> Does it mean that we have to install additional packages? If yes, wh
Hi Fred,
> Then the make failed.
> First there was a warning:
> scheduler/task.c: In function ‘task_perform’:
> scheduler/task.c:136:9: warning: implicit declaration of function
> ‘clamp’ [-Wimplicit-function-declaration]
> task->backoff = clamp(task->backoff * 2, 60, ODS_SE_MAX_BACKOFF);
"Yuri Schaeffer" schreef in bericht
news:d59b046a-420e-9108-6191-112a28c33...@nlnetlabs.nl...
Dear Community,
No issues with the RC1 have come up in the last 1.5 weeks so hereby we
announce the OpenDNSSEC 2.1.0 release.
...
Due to holidays I could not try this new version earlier on our tes
Dear Community,
No issues with the RC1 have come up in the last 1.5 weeks so hereby we
announce the OpenDNSSEC 2.1.0 release.
OpenDNSSEC 2.1 development was focused on improving the daemon code for
the Signer and Enforcer. As such it is much more a steady incremental
improvement rather than revol
22 matches
Mail list logo
