Hi Mike,
On Thu, Dec 13, 2018 at 04:37:53PM -0500, Mike Dalessio wrote:
> Hi Daniel,
>
> I'm curious if you have an updated release schedule for 2.9.9 final?
>
> Thanks much for coordinating this release.
>
> -m
Sorry it's out now, between work, Xmas with familly haeading to my place
and
Nikolai Weibull schrieb am 24.12.18 um 12:00:
> Stefan Behnel, 2018-12-24 11:43:
>> Nick Wellnhofer schrieb am 19.12.18 um 17:02:
>>> On 30/11/2018 11:41, Nikolai Weibull via xml wrote:
OK, now I understand why it was working in my copy of the repository and
not yours. Something went
Hi!
Stefan Behnel, 2018-12-24 11:43:
Nick Wellnhofer schrieb am 19.12.18 um 17:02:
On 30/11/2018 11:41, Nikolai Weibull via xml wrote:
OK, now I understand why it was working in my copy of the
repository and
not yours. Something went wrong when you applied the patch,
Daniel, as a
line was
Nick Wellnhofer schrieb am 19.12.18 um 17:02:
> On 30/11/2018 11:41, Nikolai Weibull via xml wrote:
>> OK, now I understand why it was working in my copy of the repository and
>> not yours. Something went wrong when you applied the patch, Daniel, as a
>> line was elided. Here’s a fix. We want
On 30/11/2018 11:41, Nikolai Weibull via xml wrote:
OK, now I understand why it was working in my copy of the repository and not
yours. Something went wrong when you applied the patch, Daniel, as a line was
elided. Here’s a fix. We want to include XML_RELAXNG_TEXT here as well,
otherwise it
Hi Daniel,
I'm curious if you have an updated release schedule for 2.9.9 final?
Thanks much for coordinating this release.
-m
On Thu, Nov 29, 2018 at 4:58 PM Daniel Veillard via xml
wrote:
> I pushed RC2 in git and pushed signed tarball and rpms to the usual
> place:
>
>
Nokogiri (a Ruby wrapper around libxml2) went green with RC2. I'll keep
this github PR up to date as more RCs or the Final get released:
https://github.com/sparklemotion/nokogiri/pull/1824
On Thu, Nov 29, 2018 at 4:58 PM Daniel Veillard via xml
wrote:
> I pushed RC2 in git and pushed signed
On 29/11/2018 22:50, Daniel Veillard wrote:
On Fri, Nov 23, 2018 at 11:12:13PM +0100, Nick Wellnhofer wrote:
The function now claims to work without preparsed documents, so the
workaround isn't used. But apparently there's problem with the commit. I'm
CC'ing the author. If we can't get this
Hi!
OK, now I understand why it was working in my copy of the
repository and not yours. Something went wrong when you applied
the patch, Daniel, as a line was elided. Here’s a fix. We want
to include XML_RELAXNG_TEXT here as well, otherwise it won’t work.
The second part of the patch
Daniel Veillard schrieb am 29.11.18 um 21:20:
> On Mon, Nov 26, 2018 at 11:48:37AM +0100, Nikolai Weibull via xml wrote:
>> Stefan Behnel, 2018-11-25 15:37:
>>> Nikolai Weibull schrieb am 24.11.18 um 00:12:
Yes, it seems that my patch for data in interleaves was added and
this may be the
I pushed RC2 in git and pushed signed tarball and rpms to the usual
place:
ftp://xmlsoft.org/libxml2
we have a couple of issues which were raised against rc1 and not completely
solved, depending on how we resolve those and if no new ones pop-up I
will either push an rc3 around Monday or
On Fri, Nov 23, 2018 at 11:12:13PM +0100, Nick Wellnhofer wrote:
> On 23/11/2018 22:38, Nick Wellnhofer wrote:
> > On 23/11/2018 20:51, Shlomi Fish wrote:
> > > I am getting a failure in one of the tests of
> > > https://github.com/shlomif/perl-XML-LibXML - it works fine with 2.9.8:
> >
> > Can
On Mon, Nov 26, 2018 at 11:48:37AM +0100, Nikolai Weibull via xml wrote:
> Hi!
>
> Stefan Behnel, 2018-11-25 15:37:
>
> > Nikolai Weibull schrieb am 24.11.18 um 00:12:
>
> > > Yes, it seems that my patch for data in interleaves was added and
> > > this may be the cause of these issues. The
Hi!
Stefan Behnel, 2018-11-25 15:37:
Nikolai Weibull schrieb am 24.11.18 um 00:12:
Yes, it seems that my patch for data in interleaves was added
and this may be the cause of these issues. The regression tests
didn’t display them, so this is something different. Could we
perhaps get a
Nikolai Weibull schrieb am 24.11.18 um 00:12:
> Yes, it seems that my patch for data in interleaves was added and this may
> be the cause of these issues. The regression tests didn’t display them, so
> this is something different. Could we perhaps get a minimal test that breaks?
Here is what I
Nikolai Weibull schrieb am 24.11.18 um 00:12:
> Yes, it seems that my patch for data in interleaves was added and this may
> be the cause of these issues. The regression tests didn’t display them, so
> this is something different. Could we perhaps get a minimal test that breaks?
It's a bit
On Fri, 23 Nov 2018 23:12:13 +0100
Nick Wellnhofer wrote:
> On 23/11/2018 22:38, Nick Wellnhofer wrote:
> > On 23/11/2018 20:51, Shlomi Fish wrote:
> >> I am getting a failure in one of the tests of
> >> https://github.com/shlomif/perl-XML-LibXML - it works fine with 2.9.8:
> >
> > Can you
On 24/11/2018 14:01, Daniel Veillard via xml wrote:
Nick there seems to be 7 merge requests, maybe we need to go though those
before I push an RC2,
https://gitlab.gnome.org/GNOME/libxml2/merge_requests/5
This should be kept externally, IMO.
Hi!
Daniel Veillard, 2018-11-24 14:01:
On Sat, Nov 24, 2018 at 12:14:06AM +0100, Nikolai Weibull wrote:
Daniel Veillard via xml, 2018-11-22 18:32:
> I have just tagged the Release Candidate 1 in git and
> pushed a
> signed
> tarball and signed rpms to the usual place:
Could we
On Sat, Nov 24, 2018 at 12:14:06AM +0100, Nikolai Weibull wrote:
> Hi!
>
> Daniel Veillard via xml, 2018-11-22 18:32:
>
> > I have just tagged the Release Candidate 1 in git and pushed a
> > signed
> > tarball and signed rpms to the usual place:
>
> Could we please get merge request 10 into
>
Hi!
Daniel Veillard via xml, 2018-11-22 18:32:
I have just tagged the Release Candidate 1 in git and pushed a
signed
tarball and signed rpms to the usual place:
Could we please get merge request 10 into
https://gitlab.gnome.org/GNOME/libxml2/merge_requests/10
this release? It fixes
Hi!
Stefan Behnel, 2018-11-23 21:54:
I think something changed in the RelaxNG code.
Yes, it seems that my patch for data in interleaves was added and
this may be the cause of these issues. The regression tests
didn’t display them, so this is something different. Could we
perhaps get a
On 11/23/2018 1:11 PM, Nick Wellnhofer wrote:
On 22/11/2018 18:32, Daniel Veillard via xml wrote:
Please give it some testing, if we need to make changes I will likely
push
an RC2 mid next week, and if everything goes well I will push 2.9.9 final
end of next week.
Built and tested (with
On 23/11/2018 22:38, Nick Wellnhofer wrote:
On 23/11/2018 20:51, Shlomi Fish wrote:
I am getting a failure in one of the tests of
https://github.com/shlomif/perl-XML-LibXML - it works fine with 2.9.8:
Can you check if it's caused by one of the following commits?
Nevermind, it's this commit:
On 23/11/2018 20:51, Shlomi Fish wrote:
I am getting a failure in one of the tests of
https://github.com/shlomif/perl-XML-LibXML - it works fine with 2.9.8:
Can you check if it's caused by one of the following commits?
Salut Daniel!
Daniel Veillard via xml schrieb am 22.11.18 um 18:32:
> I have just tagged the Release Candidate 1 in git and pushed a signed
> tarball and signed rpms to the usual place:
>
> ftp://xmlsoft.org/libxml2/
I think something changed in the RelaxNG code. When I try to validate a
Hi,
On Thu, 22 Nov 2018 18:32:59 +0100
Daniel Veillard via xml wrote:
> I have just tagged the Release Candidate 1 in git and pushed a signed
> tarball and signed rpms to the usual place:
>
> ftp://xmlsoft.org/libxml2/
>
> (also available as http://xmlsoft.org/download/)
>
I am getting
On 22/11/2018 18:32, Daniel Veillard via xml wrote:
Please give it some testing, if we need to make changes I will likely push
an RC2 mid next week, and if everything goes well I will push 2.9.9 final
end of next week.
Built and tested (with `make check`) succesfully on:
- Windows 10
-
I have just tagged the Release Candidate 1 in git and pushed a signed
tarball and signed rpms to the usual place:
ftp://xmlsoft.org/libxml2/
(also available as http://xmlsoft.org/download/)
Please give it some testing, if we need to make changes I will likely push
an RC2 mid next week, and
29 matches
Mail list logo
