Sorry I ddin't watch my xml folder for a while ... a bit busy
On Sat, Oct 06, 2018 at 07:32:00PM +0300, Roumen Petrov wrote:
> Hi Nick,
>
> Nick Wellnhofer wrote:
> > On 25/09/2018 14:36, Nick Wellnhofer wrote:
> > > The whole situation is a mess. I'd love to change the code so that
> > > non-A
On Tue, Sep 25, 2018 at 01:19:51PM +0200, Nick Wellnhofer wrote:
> libxml2 serializes documents without an encoding declaration differently
> than documents with an explicit UTF-8 encoding:
>
> $ echo 'Käse' |xmllint -
>
> Käse
>
> $ echo 'Käse' |xmllint -
>
> Käse
>
> Since the encoding shoul
On Thu, Sep 27, 2018 at 02:22:55PM +0200, Nick Wellnhofer wrote:
> On 27/09/2018 10:59, Roumen Petrov wrote:
> > Let consider case as "file" mode.
>
> > Let consider case as "stream" code.
>
> I'm not only talking about xmllint but the serialization API (xmlSave*,
> xmlNodeDump*) in general.
>
>
On Sat, Oct 13, 2018 at 12:23:09AM +0200, Nikolai Weibull via xml wrote:
> Hi!
>
> This remains unfixed. I have absolutely no idea what’s going on in the
> interleave validation code. Daniel, could you please put together some
> minor documentation on how the interleave validation code works? I
On Sun, Oct 14, 2018 at 09:02:29PM +0200, Nikolai Weibull via xml wrote:
> Hi!
>
> OK, I managed to decode it somewhat. The issue seems to be that we build
> groups of what can be matched by the interleave, but that these groups don’t
> include data, list, and value elements, only element and tex
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 i
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
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 regre
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 yo
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 proc
Happy New Year,
the release is finally out, I just tagged it in git and pushed signed
tarball and rpms to the usual place:
ftp://xmlsoft.org/libxml2/
this is a mixed release, it includes security fixes, bug fixes as well
as improvement and portability fixes for cygwin:
Security:
- CVE-201
amilly haeading to my place
and a short trip, it got delayed,
Daniel
>
> 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:
> >
> >ftp://xmlsoft.org/libxm
On Wed, Mar 13, 2019 at 06:17:18PM +0100, Roberto Bizzozero via xml wrote:
> Hello, I tried to install the LIBXML2 and service program on a V7R3M0 IBMi
> machine, but it failed to compile it, basically for the 100 char limit of
> the source file but also for other problems concerning the OS400 vers
On Wed, Jul 31, 2019 at 10:00:22PM +0530, Akash Opensource wrote:
> Can you please help on this. ??
> My guess is encoding in UTF-8
>
Can't remember, depending on which buffer it is encoding of byte flow may
not be UTF-8 there.
All this is relatively tricky code, written 15-20 years ago, I
On Mon, Jul 22, 2019 at 11:59:42AM +0200, Jan Pokorný via xml wrote:
> On 27/06/19 14:15 +0200, Nikolai Weibull via xml wrote:
> > The following RELAX NG schema requires exponential running time when
> > matching attributes (15 attributes is where my computer begins to
> > show the symptoms, this m
ACK :-)
Daniel
On Thu, Jul 11, 2019 at 08:00:39PM +0200, Jan Pokorný via xml wrote:
> At least when merely public API is to be leveraged, one cannot use
> xmlBufCreate function that would otherwise be a clear fit, and relying
> on some invariants wrt. how some other struct fields will get
> in
Took a while but it's time to assemble a new release,
I tagged it in git and pushed signed tarball and rpms to the
usual place:
ftp://xmlsoft.org/libxml2/
I will try to make an rc2 during the week-end, and then we can
roll up the release by mid next week.
In the meantime please give it som
On Wed, Oct 23, 2019 at 06:53:07PM +0200, Daniel Veillard via xml wrote:
> Took a while but it's time to assemble a new release,
> I tagged it in git and pushed signed tarball and rpms to the
> usual place:
>
>ftp://xmlsoft.org/libxml2/
>
> I will try to make
On Mon, Oct 28, 2019 at 02:35:06PM +0100, Christoph M. Becker wrote:
> Hi,
>
> On 28.10.2019 at 10:06, Daniel Veillard via xml wrote:
>
> > In the absence of feedback or changes since RC1, I am not pushing
> > an RC2 for libxml2-2.9.10, assume a final release for Wed o
> details, but RC1 looks good from here.
Another good news, thanks Mike !
Daniel
> -m
>
>
> On Mon, Oct 28, 2019 at 10:12 AM Daniel Veillard via xml
> wrote:
>
> > On Mon, Oct 28, 2019 at 02:35:06PM +0100, Christoph M. Becker wrote:
> > > Hi,
>
way to validate
that one and the libxslt 1.1.34 rc2 too, Stefan or Martijn are you around ?
Daniel
> - David
>
> On Thu, Oct 24, 2019 at 5:53 AM Daniel Veillard via xml
> wrote:
>
> > Took a while but it's time to assemble a new release,
> > I tagged it in git and
It's out ! Tagged in git and with signed tarball and rpms
at the usual place:
ftp://xmlsoft.org/libxml2/
This is a relatively large release, Nick fixed a number of bugs and improved
the code in many areas, among other things removing some recursive behaviour
of the code in various places.
and the libxslt 1.1.34 rc2 too, Stefan or Martijn are you around ?
> >
> > Daniel
> >
> >> - David
> >>
> >> On Thu, Oct 24, 2019 at 5:53 AM Daniel Veillard via xml
> >> wrote:
> >>
> >>> Took a while but it's time to asse
Hi Eric,
sorry, I'm very late to the thread, but in case you still have issues:
1/ yes xmlFreeDoc is the right way to free the whole memory of the
document, you may be missing freeing other bits left and right if you
don't use it
2/ you can debug memory allocation by running valgrind
On Fri, Dec 20, 2019 at 12:46:23PM +0100, Gökçe Aydos wrote:
> I use xmllint in my command-line scripts. The default mode of xmllint
> does not support namespaces, so when I must deal with XML files with
> namespaces I use the --shell mode of xmllint.
That sounds ... wrong
> I noticed that the
On Wed, Apr 14, 2021 at 11:35:58AM +0200, Stefan Behnel wrote:
> Hi,
>
> libxml2 2.9.10 has been around for almost 18 months now. There have been
> lots of fixes during that time, so, may I kindly ask what's hindering a new
> release?
Maybe that I'm just too busy with "work", plus teh fact that
P, I am way way behind, but now that CVE-2021-3541 is out I just pushed
that long awaited release. libxml2 2.9.11 is tagged in git and a signed
tarball is available at the usual place:
ftp://xmlsoft.org/libxml2/
This release incoporate the various security and quadatic patches that
N
include "fuzz.h"
> | ^~~~
> compilation terminated.
>
> It appears to be available in the git repo, so perhaps it just needs to be
> added to EXTRA_DIST or something?
Arghhh, indeed :-(
Daniel
> On Thu, May 13 2021 at 15:54:55 +0200, Daniel Veillard via xml
> wr
Oh well, a little bit of shame is better than a long lasting pain,
so 2.9.12 is out and it now includes everything to build outside of
a git checkout tree !
Sorry about that, and thanks for reporting it !
Daniel
On Thu, May 13, 2021 at 08:14:04PM +0200, Daniel Veillard via xml wrote:
>
On Thu, Jul 22, 2021 at 01:23:27PM +0200, Nick Wellnhofer via xml wrote:
> I never really asked for it but in the last years I became de-facto
> maintainer of both libxml2 and libxslt. Luckily, I was able to fund my
> involvement through Chrome VRP bug bounties and OSS-Fuzz integration
> rewards. B
On Mon, Jan 10, 2022 at 03:20:09PM +0100, Nick Wellnhofer via xml wrote:
> Hello,
>
> Thanks to a donation from Google, I'm able to resume maintenance of libxml2
> (and libxslt) for the remainder of 2022.
Yay ! :-)
> My immediate plans are:
>
> - Make a bug fix release fixing many regression
31 matches
Mail list logo
