Date: Mon, 5 Sep 2011 20:19:22 +0100 From: Chris Rees <crees@freebsd.org> To: Matthias Andree <mandree@freebsd.org> Cc: cvs-ports@freebsd.org, cvs-all@freebsd.org, ports-committers@freebsd.org Subject: Re: cvs commit: ports/security/vuxml vuln.xml Message-ID: <CADLo839d5WnpRHb8yt=X=ZruF_Mf_zVL9SF4Z5XO%2BxsWSJo6RQ@mail.gmail.com> In-Reply-To: <4E6410D0.1070100@FreeBSD.org> References: <201109042015.p84KFqOR005039@repoman.freebsd.org> <4E6410D0.1070100@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 September 2011 00:59, Matthias Andree <mandree@freebsd.org> wrote: > Am 04.09.2011 22:15, schrieb Chris Rees: >> crees 2011-09-04 20:15:52 UTC >> >> FreeBSD ports repository >> >> Modified files: >> security/vuxml vuln.xml >> Log: >> - Document cfs buffer overflow vulnerability. >> - While here, unbreak packaudit -- it doesn't like newlines in the >> middle of tags. Perhaps a comment should say something? > > Chris, > > Are you use that your XML and/or SGML toolchains and document type > definitions and catalogs are properly installed? I have seen cases > where the catalogs were broken, and nothing short of deinstalling > xmlcatmgr (and all ports that need it), removing leftover catalogs, and > reinstalling all ports that got deinstalled helped. > > Are you sure that you aren't by accident tripped up by CR characters > somewhere? > > I've reverted vuln.xml to 1.2434 and don't see how it breaks the parser > (xsltproc), and packaudit generates a file that seems to be in proper > working order for me. Would certainly make sense. If you can't reproduce it, we'll assume it's my out of date xml ports, which I thought I'd updated and obviously failed to. Sorry for the noise. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo839d5WnpRHb8yt=X=ZruF_Mf_zVL9SF4Z5XO%2BxsWSJo6RQ>