From owner-freebsd-python@FreeBSD.ORG Thu Apr 9 15:28:06 2015 Return-Path: Delivered-To: python@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C735714A for ; Thu, 9 Apr 2015 15:28:06 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A98319E9 for ; Thu, 9 Apr 2015 15:28:06 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t39FS60S064957 for ; Thu, 9 Apr 2015 15:28:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 199162] [MAINTAINER] devel/dulwich: Update to 0.10.1a (Security Update) Date: Thu, 09 Apr 2015 15:28:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: easy, needs-qa, patch, security X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: marco.broeder@posteo.eu X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback+ merge-quarterly+ X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2015 15:28:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199162 --- Comment #3 from Marco Br=C3=B6der --- Created attachment 155369 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D155369&action= =3Dedit py27-dulwich-0.10a.log The changes to SOURCES.txt, MANIFEST.in and setup.py are there to disable building and installing all the tests. They are pointless to the user and several tests are broken even in upstream's environments. It does not make sense to install / run them at the moment. For the other things, see the attached log and posted output. # portlint -AC WARN: Makefile: for new port, make $FreeBSD$ tag in comment section empty, = to make SVN happy. 0 fatal errors and 1 warning found. This is bogus. It is not a new port! portlint -C is more reasonable. # portlint -C looks fine. The poudriere testport log file is attached. I know the Porter's Handbook section about VuXML. There are already new ent= ries for other ports. So I guess the patch will not apply anymore. Btw, this whole VuXML procedure is a pain in the ass. Do not get me wrong b= ut I unless something changes there I do not care about it in the future. The make validate output is not attached (~ 14 MiB output), because it does= not validate and never has for me with or without my patch. I do not exactly kn= ow what is wrong with it. It fails to load the external schemes and cannot validate anything. But I guess my changes are fine. Some example output: =3D=3D=3D=3D http://www.vuxml.org/dtd/vuxml-1/vuxml-11.dtd:41: warning: failed to load external entity "http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-datatypes-1.mod" [...] http://www.vuxml.org/dtd/vuxml-1/vuxml-11.dtd:82: warning: failed to load external entity "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd" [...] vuln.xml:59: element vuxml: validity error : No declaration for attribute x= mlns of element vuxml ^ vuln.xml:60: element vuln: validity error : No declaration for attribute vi= d of element vuln [...] =3D=3D=3D=3D and so on for all lines of vuln.xml. Just wondering if it is a new requirement for a submission to post all the logs? A committer has to test it anyway and I never had to post logs / outp= ut before. ;-) Thank you and regards! --=20 You are receiving this mail because: You are on the CC list for the bug.=