Bug#766884: libxml2: lots of "validity error : ID ... already defined" errors with xmllint --valid

2014-11-12 Thread Vincent Lefevre
As said on https://bugzilla.gnome.org/show_bug.cgi?id=737840#c4 this
affects the building process of KDE documentation.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#766884: libxml2: lots of "validity error : ID ... already defined" errors with xmllint --valid

2014-10-30 Thread Vincent Lefevre
On 2014-10-30 09:19:30 +0100, intrigeri wrote:
> Vincent Lefevre wrote (30 Oct 2014 02:39:02 GMT) :
> > On 2014-10-29 23:34:37 +0100, intrigeri wrote:
> >> Does this bug really make libxml2 unusable for everybody?
> 
> > This is a major regression. Many users may be affected.
> 
> That's exactly what I was trying to evaluate :)

It's rather difficult to say about users. One can already look at
software using XML files that may be affected by the bug. I've done a
quick search on 'ENTITY.*SYSTEM' on the few sources that are present
on my machine (this concerns only some software I needed to build or
look at). I suppose that gdm documentation is affected: gdm/docs/C
has:

* index.docbook which contains:

http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"; [

 
 
 

]>

* legal.xml which contains:

  

so that I suppose that the bug would appear on it. The consequences
depend on what is done with this, but using the buggy libxml2 version
would make this DocBook file appear as invalid. Ideally validation
should really be done at build time and/or with "make check", so that
if everything is done correctly, you can consider this like a build
failure.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#766884: libxml2: lots of "validity error : ID ... already defined" errors with xmllint --valid

2014-10-30 Thread intrigeri
Vincent Lefevre wrote (30 Oct 2014 02:39:02 GMT) :
> On 2014-10-29 23:34:37 +0100, intrigeri wrote:
>> Does this bug really make libxml2 unusable for everybody?

> This is a major regression. Many users may be affected.

That's exactly what I was trying to evaluate :)

>> I can reproduce this failure in a clean sid chroot.
>> I can't in a clean Jessie chroot.

> The buggy version isn't in testing.

I was confirming your findings, not contradicting you.

Cheers,
-- 
intrigeri


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#766884: libxml2: lots of "validity error : ID ... already defined" errors with xmllint --valid

2014-10-29 Thread Vincent Lefevre
On 2014-10-29 23:34:37 +0100, intrigeri wrote:
> Vincent Lefevre wrote (26 Oct 2014 22:00:30 GMT) :
> > Severity: grave
> > Justification: renders package unusable
> 
> Does this bug really make libxml2 unusable for everybody?

This is a major regression. Many users may be affected.

> I see it has a lot of reverse-dependencies, so it should be easy to
> check.

This is meaningless. You need to check among users who use
libxml2 for their own applications.

> I can reproduce this failure in a clean sid chroot.
> I can't in a clean Jessie chroot.

The buggy version isn't in testing.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#766884: libxml2: lots of "validity error : ID ... already defined" errors with xmllint --valid

2014-10-29 Thread intrigeri
Hi Vincent,

Vincent Lefevre wrote (26 Oct 2014 22:00:30 GMT) :
> Severity: grave
> Justification: renders package unusable

Does this bug really make libxml2 unusable for everybody? I see it has
a lot of reverse-dependencies, so it should be easy to check.

If that were not the case, then I think this bug should have severity
important: "a bug which has a major effect on the usability of
a package, without rendering it completely unusable to everyone".

> Simple testcase:
[...]
> $ xmllint --noent --noout tst.xml
> tst.xml:2: element item: validity error : ID a already defined

I can reproduce this failure in a clean sid chroot.
I can't in a clean Jessie chroot.

Cheers,
--
intrigeri


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#766884: libxml2: lots of "validity error : ID ... already defined" errors with xmllint --valid

2014-10-26 Thread Vincent Lefevre
Control: tags -1 upstream
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=737840

except that contrary to what the title says, these are not warnings,
but errors.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#766884: libxml2: lots of "validity error : ID ... already defined" errors with xmllint --valid

2014-10-26 Thread Vincent Lefevre
Control: retitle -1 libxml2: "validity error : ID ... already defined" errors 
with xmllint --noent

Simple testcase:

tst.xml file:






]>
&ent;

ent.xml file:




$ xmllint --noent --noout tst.xml
tst.xml:2: element item: validity error : ID a already defined

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#766884: libxml2: lots of "validity error : ID ... already defined" errors with xmllint --valid

2014-10-26 Thread Vincent Lefevre
On 2014-10-26 16:36:17 +0100, Vincent Lefevre wrote:
> A major regression: when I use the --valid xmllint option, I get lots
> of "validity error : ID ... already defined" errors.

The problem seems to occur when both --noent (to include
other XML files) and --valid are used at the same time.
No errors when --noent is used first and --valid is used
on the result.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#766884: libxml2: lots of "validity error : ID ... already defined" errors with xmllint --valid

2014-10-26 Thread Vincent Lefevre
Package: libxml2
Version: 2.9.2+dfsg1-1
Severity: grave
Justification: renders package unusable

A major regression: when I use the --valid xmllint option, I get lots
of "validity error : ID ... already defined" errors.

If you can't reproduce the error, I'll try to provide a simple testcase
(my files are huge).

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libxml2 depends on:
ii  libc6  2.19-12
ii  liblzma5   5.1.1alpha+20120614-2
ii  multiarch-support  2.19-12
ii  zlib1g 1:1.2.8.dfsg-2

Versions of packages libxml2 recommends:
ii  xml-core  0.13+nmu2

libxml2 suggests no packages.

-- debconf-show failed


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org