debian/0000755000000000000000000000000012245231721007165 5ustar debian/source/0000755000000000000000000000000011661547607010503 5ustar debian/source/format0000644000000000000000000000001411661547607011711 0ustar 3.0 (quilt) debian/gbp.conf0000644000000000000000000000015111661547607010617 0ustar [DEFAULT] pristine-tar = True upstream-tag = xml2rfc/%(version)s debian-tag = xml2rfc_debian/%(version)s debian/IETF-Trust-License-Policy.txt0000644000000000000000000005345711661547607014445 0ustar [ Original found on 2009-12-17 at http://trustee.ietf.org/docs/IETF-Trust-License-Policy.pdf, indexed from http://trustee.ietf.org/license-info/, translated to plain text by Daniel Kahn Gillmor ] IETF TRUST Legal Provisions Relating to IETF Documents Effective Date: September 12, 2009 1. Background The IETF Trust was formed on December 15, 2005, for, among other things, the purpose of acquiring, holding, maintaining and licensing certain existing and future intellectual property used in connection with the Internet standards process and its administration, for the advancement of science and technology associated with the Internet and related technology. Accordingly, pursuant to RFC 5378, Contributors to the IETF Standards Process grant the IETF Trust certain licenses with respect to their IETF Contributions. In RFC 5377, the IETF Community has provided the IETF Trust with guidance regarding licenses that the IETF Trust should grant to others with respect to such IETF Contributions and IETF Documents. These Legal Provisions describe the rights and licenses that the IETF Trust grants to others with respect to such IETF Contributions and IETF Documents; as well as certain restrictions, limitations and notices relating to IETF Documents. Capitalized terms used in these Legal Provisions that are not otherwise defined have the meanings set forth in RFC 5378. 2. Applicability of these Legal Provisions. a. These Legal Provisions are effective as of September 12, 2009 (the -Y´Effective Date¡). b. The licenses granted by the IETF Trust pursuant to these Legal Provisions apply only with respect to (i) IETF Contributions (including Internet-Drafts) that are submitted to the IETF following the Effective Date, and (ii) IETF RFCs and other IETF Documents that are published after the Effective Date. c. IETF Contributions made, and IETF Documents published, prior to the Effective Date (´Pre-Existing IETF Documents¡) remain subject to the licensing provisions of the IETF copyright policy document in effect at the time of their publication, including RFCs 1310, 1602, 2026, 3978 and 4748 and previous versions of these Legal Provisions. d. In most cases, rights to Pre-Existing IETF Documents that are not expressly granted under these RFCs can only be obtained by requesting such rights directly from the document authors. The IETF Trust and the Internet Society do not become involved in making such requests to document authors. e. These Legal Provisions may be amended from time to time by the IETF Trust in a manner consistent with the guidance provided by the IETF community and its own operating procedures. Any amendment to these Legal Provisions shall be posted for review at http://trustee.ietf.org/policyandprocedures.html and shall become effective on a date specified by the IETF Trust, but no earlier than thirty (30) days following its posting. Such amendment shall apply with respect to all IETF Contributions made and IETF Documents published following the effective date of such amendment. All prior versions of these Legal Provisions IETF Trust Legal Provisions Relating to IETF Documents Effective Date: September 12, 2009 shall continue to be posted at http://trustee.ietf.org/policyandprocedures.html for reference with respect to IETF Contributions and IETF Documents as to which they may apply. 3. Licenses to IETF Documents and IETF Contributions. a. License For Use Within the IETF Standards Process. The IETF Trust hereby grants to each participant in the IETF Standards Process, to the greatest extent that it is permitted to do so, a non-exclusive, royalty-free, worldwide right and license under all copyrights and rights of authors granted to the IETF Trust: i. to copy, publish, display and distribute IETF Contributions and IETF Documents, in whole or in part, as part of the IETF Standards Process, and ii. to translate IETF Contributions and IETF Documents, in whole or part, into languages other than English as part of the IETF Standards Process, and iii. unless explicitly disallowed in the notices contained in an IETF Contribution or IETF Document (as specified in Section 6.c below), to modify or prepare derivative works of such IETF Contributions or IETF Documents, in whole or in part, as part of the IETF Standards Process. b. IETF Standards Process. The term IETF Standards Process has the meaning assigned to it in RFC 5378. In addition, the IETF Trust interprets the IETF Standards Process to include the archiving of IETF Documents in perpetuity for reference in support of IETF activities and the implementation of IETF standards and specifications. c. Licenses For Use Outside the IETF Standards Process. In addition to the rights granted with respect to Code Components described in Section 4 below, the IETF Trust hereby grants to each person who wishes to exercise such rights, to the greatest extent that it is permitted to do so, a non-exclusive, royalty-free, worldwide right and license under all copyrights and rights of authors: i. to copy, publish, display and distribute IETF Contributions and IETF Documents in full and without modification, ii. to translate IETF Contributions and IETF Documents into languages other than English, and to copy, publish, display and distribute such translated IETF Contributions and IETF Documents in full and without modification, iii. to copy, publish, display and distribute unmodified portions of IETF Contributions and IETF Documents and translations thereof, provided that: (x) each such portion is clearly attributed to IETF and identifies the RFC or other IETF Document or IETF Contribution from which it is taken, (y) all IETF legends, legal notices and indications of authorship contained in the original IETF RFC must also be included where any substantial portion of the text of an IETF RFC, and in any event where more than one-fifth of such text, is reproduced in a 2 IETF Trust Legal Provisions Relating to IETF Documents Effective Date: September 12, 2009 single document or series of related documents. d. Licenses that are not Granted. The following licenses are not granted pursuant to these Legal Provisions: i. any license to modify IETF Contributions or IETF Documents, or portions thereof (other than to make translations or to extract, use and modify Code Components as permitted under the licenses granted under Section 4 of these Legal Provisions) in any context outside the IETF Standards Process, or ii. any license to publish, display or distribute IETF Contributions or IETF Documents, or portions thereof, without the required legends and notices described in these Legal Provisions. e. Requesting Additional Rights. Anyone who wishes to request license rights from the IETF Trust in addition to those granted under these Legal Provisions may submit such request to trustees@ietf.org. Such request will be considered by the IETF Trust, which will make a decision regarding the request in its sole discretion and inform the requester of its disposition. In addition, individual Contributors may be contacted regarding licenses to their IETF Contributions. The IETF Trust does not limit the ability of IETF Contributors to license their Contributions, so long as those licenses do not affect the rights granted to the IETF Trust under RFC 5378. 4. License to Code Components. a. Definition. IETF Contributions and IETF Documents often include components intended to be directly processed by a computer (´Code Components¡). A list of common Code Components can be found at http://trustee.ietf.org/license-info/. b. Identification. Text in IETF Contributions and IETF Documents of the types identified in Section 4.a above shall constitute ´Code Components¡. In addition, any text found between the markers and , or otherwise clearly labeled as a Code Component, shall be considered a ´Code Component¡. c. License. In addition to the licenses granted under Section 3, unless one of the legends contained in Section 6.c.i or 6.c.ii is included in an IETF Document containing Code Components, such Code Components are also licensed to each person who wishes to receive such a license on the terms of the ´Simplified BSD License", as described below. If a licensee elects to apply the BSD License to a Code Component, then the additional licenses and restrictions set forth in Section 3 and elsewhere in these Legal Provisions shall not apply thereto. BSD License: Copyright (c) IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 3 IETF Trust Legal Provisions Relating to IETF Documents Effective Date: September 12, 2009 • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. • Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The above BSD License is intended to be compatible with the Simplified BSD License template published at http://opensource.org/licenses/bsd-license.php . d. Attribution. Those who use Code Components under the license granted under Section 4.c above are requested to attribute each such Code Component to IETF and identify the RFC or other IETF Document or IETF Contribution from which it is taken. Such attribution may be placed in the code itself (e.g., ´This code was derived from IETF RFC [insert RFC number]. Please reproduce this note if possible.¡), or any other reasonable location. e. BSD License Text. For purposes of compliance with the redistribution clauses of the Simplified BSD License set forth in Section 4.c above, it is permissible, when using Code Components extracted from IETF Contributions and IETF Documents, either (1) to reproduce the entire text of the BSD License set forth in Section 4.c above as part of such Code Component, or (2) to include in such Code Component the legend set forth in Section 6.d below. 5. License Limitations. a. No Patent License. The licenses granted under these Legal Provisions shall not be deemed to grant any right under any patent, patent application or similar intellectual property right. b. Supersedure. The terms of any license granted under these Legal Provisions may be superseded by a written agreement between the IETF Trust and the licensee that specifically references and supersedes the relevant provisions of these Legal Provisions, except that (i) the IETF Trust shall in no event be authorized to grant rights with respect to any Contribution in excess of those which it has been granted by the Contributor, and (ii) the rights granted shall not be less than those otherwise granted under these Legal Provisions. 4 IETF Trust Legal Provisions Relating to IETF Documents Effective Date: September 12, 2009 c. Pre-5378 Material. In some cases, IETF Contributions or IETF Documents may contain material from IETF Contributions or IETF Documents published or made publicly available before November 10, 2008 as to which the persons controlling the copyright in such material have not granted rights to the IETF Trust under the terms of RFC 5378 (´Pre-5378 Material¡). If a Contributor includes the legend contained in Section 6.c.iii of these Legal Provisions on such IETF Contributions or IETF Documents containing Pre-5378 Materials, the IETF Trust agrees that it shall not grant any third party the right to use such Pre-5378 Material outside the IETF Standards Process unless and until it has obtained sufficient rights to do so from the persons controlling the copyright in such Pre-5378 Material. Where practical, Contributors are encouraged to identify which portions of such IETF Contributions and IETF Documents contain Pre-5378 Material, including the source (by RFC number or otherwise) of the Pre-5378 Material. 6. Text To Be Included in IETF Documents. The following text must be included in each IETF Document as specified below. The IESG shall specify the manner and location of such text for Internet-Drafts. The RFC Editor shall specify the manner and location of such text for RFCs. The copyright notice specified in 6.b below shall be placed so as to give reasonable notice of the claim of copyright. a. Submission Compliance for Internet-Drafts. In each Internet-Draft: This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. b. Copyright and License Notice. In each IETF Document (including RFCs and Internet-Drafts): Copyright (c) IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust’s Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the BSD License. c. Derivative Works and Publication Limitations. If a Contributor chooses to limit the right to make modifications and derivative works of an IETF Contribution, then one of the notices in clause (i) or (ii) below must be included. Note that an IETF Contribution with such a notice cannot become a Standards Track document or, in most cases, a working group document. If an IETF Contribution contains pre-5378 Material as to which the IETF Trust has not been granted, or may not have been granted, the necessary permissions to allow modification of such pre-5378 Material outside the IETF Standards Process, then the notice in clause (iii) may be included by the Contributor of such IETF Contribution to limit the right to make modifications to such pre-5378 Material outside the IETF Standards Process. i. If the Contributor does not wish to allow modifications, but does wish to 5 IETF Trust Legal Provisions Relating to IETF Documents Effective Date: September 12, 2009 allow publication as an RFC: This document may not be modified, and derivative works of it may not be created, except to format it for publication as an RFC or to translate it into languages other than English. ii. If the Contributor does not wish to allow modifications nor to allow publication as an RFC: This document may not be modified, and derivative works of it may not be created, and it may not be published except as an Internet-Draft. iii. If an IETF Contribution contains pre-5378 Material as to which the IETF Trust has not been granted, or may not have been granted, the necessary permissions to allow modification of such pre-5378 Material outside the IETF Standards Process: This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. d. BSD License Notification. In lieu of the complete text of the Simplified BSD License set forth in Section 4.c, a person who elects to license a Code Component under the BSD License as described in Section 4.c may use the following notification in the program or other file that includes the Code Component: Copyright (c) IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust’s Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). 7. Terms Applicable to All IETF Documents. The following legal terms apply to all IETF Documents: a. ALL DOCUMENTS AND THE INFORMATION CONTAINED THEREIN ARE PROVIDED ON AN "AS IS" BASIS AND THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. b. The IETF Trust takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation 6 IETF Trust Legal Provisions Relating to IETF Documents Effective Date: September 12, 2009 or use of the technology described in any IETF Document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. c. Copies of Intellectual Property disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. d. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement any standard or specification contained in an IETF Document. Please address the information to the IETF at ietf-ipr@ietf.org. e. The definitive version of an IETF Document is that published by, or under the auspices of, the IETF. Versions of IETF Documents that are published by third parties, including those that are translated into other languages, should not be considered to be definitive versions of IETF Documents. The definitive version of these Legal Provisions is that published by, or under the auspices of, the IETF. Versions of these Legal Provisions that are published by third parties, including those that are translated into other languages, should not be considered to be definitive versions of these Legal Provisions. f. For the avoidance of doubt, each Contributor to the IETF Standards Process licenses each Contribution that he or she makes as part of the IETF Standards Process to the IETF Trust pursuant to the provisions of RFC 5378. No language to the contrary, or terms, conditions or rights that differ from or are inconsistent with the rights and licenses granted under RFC 5378, shall have any effect and shall be null and void, whether published or posted by such Contributor, or included with or in such Contribution. 7 debian/xml2rfc.manpages0000644000000000000000000000002112245200361012244 0ustar debian/xml2rfc.1 debian/rules0000755000000000000000000000056512245231714010255 0ustar #!/usr/bin/make -f %: dh $@ --with=python2 debian/xml2rfc.1: PYTHONPATH=. help2man -n 'format RFCs using XML markup' -N ./scripts/xml2rfc -o $@ override_dh_installman: debian/xml2rfc.1 dh_installman # silly workaround for emacs turds left in upstream tarball override_dh_clean: dh_clean --exclude=nroff~ override_dh_auto_test: pyflakes xml2rfc ./test.py --verbose debian/compat0000644000000000000000000000000211771716753010403 0ustar 9 debian/control0000644000000000000000000000130512245231720010566 0ustar Source: xml2rfc Section: non-free/text Priority: optional Build-Depends: debhelper (>= 9), pyflakes, python-lxml, python, python-setuptools, dh-python, help2man Maintainer: Daniel Kahn Gillmor Standards-Version: 3.9.4 Homepage: https://pypi.python.org/pypi/xml2rfc/ Package: xml2rfc Architecture: all Depends: python-lxml, ${python:Depends}, ${misc:Depends} Description: XML-based formatting tool for RFCs This package provides xml2rfc, a tool which creates text, HTML and nroff output in the format required for Internet-Drafts and RFCs. The text and nroff output is suitable for input to the RFC editor. . The DTD used by the XML documents is described in RFC 2629. debian/patches/0000755000000000000000000000000012244770333010622 5ustar debian/patches/avoid-makefile.patch0000644000000000000000000001050012244770333014514 0ustar --- a/Makefile +++ /dev/null @@ -1,64 +0,0 @@ -# Simple makefile which mostly encapsulates setup.py invocations. Useful as -# much as documentation as it is for invocation. - -#svnrev := $(shell svn info | grep ^Revision | awk '{print $$2}' ) -datetime_regex = [0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9][T_ ][0-9][0-9]:[0-9][0-9]:[0-9][0-9] -version_regex = "[Vv]ersion.2\.[0-9]" - - -bin/python: - echo "Install virtualenv here ($$PWD) in order to run tests locally." - -install: - python --version - python setup.py --quiet install - -test: install - pyflakes xml2rfc - [ -d tests/failed/ ] && rm -f tests/failed/* - python test.py --verbose - -drafttest: install - [ -d tmp ] || mkdir -p tmp - [ -d tmp ] && rm -f tmp/* - @ PYTHONPATH=$$PWD python scripts/xml2rfc --cache tests/cache tests/input/draft-template.xml --base tmp/ --raw --text --nroff --html --exp - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/draft-template.raw.txt tmp/draft-template.raw.txt || { echo "Diff failed for .raw.txt output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/draft-template.txt tmp/draft-template.txt || { echo "Diff failed for .txt output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/draft-template.nroff tmp/draft-template.nroff || { echo "Diff failed for .nroff output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/draft-template.html tmp/draft-template.html || { echo "Diff failed for .html output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/draft-template.exp.xml tmp/draft-template.exp.xml || { echo "Diff failed for .exp.xml output"; exit 1; } - -miektest: install - [ -d tmp ] || mkdir -p tmp - [ -d tmp ] && rm -f tmp/* - @ PYTHONPATH=$$PWD python scripts/xml2rfc --cache tests/cache tests/input/draft-miek-test.xml --base tmp/ --raw --text --nroff --html --exp - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/draft-miek-test.raw.txt tmp/draft-miek-test.raw.txt || { echo "Diff failed for .raw.txt output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/draft-miek-test.txt tmp/draft-miek-test.txt || { echo "Diff failed for .txt output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/draft-miek-test.nroff tmp/draft-miek-test.nroff || { echo "Diff failed for .nroff output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/draft-miek-test.html tmp/draft-miek-test.html || { echo "Diff failed for .html output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/draft-miek-test.exp.xml tmp/draft-miek-test.exp.xml || { echo "Diff failed for .exp.xml output"; exit 1; } - -rfctest: bin/python install - [ -d tmp ] || mkdir -p tmp - [ -d tmp ] && rm -f tmp/* - @ PYTHONPATH=$$PWD python scripts/xml2rfc --cache tests/cache tests/input/rfc6787.xml --base tmp/ --raw --text --nroff --html --exp - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/rfc6787.raw.txt tmp/rfc6787.raw.txt || { echo "Diff failed for .raw.txt output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/rfc6787.txt tmp/rfc6787.txt || { echo "Diff failed for .txt output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/rfc6787.nroff tmp/rfc6787.nroff || { echo "Diff failed for .nroff output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/rfc6787.html tmp/rfc6787.html || { echo "Diff failed for .html output"; exit 1; } - @ diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/rfc6787.exp.xml tmp/rfc6787.exp.xml || { echo "Diff failed for .exp.xml output"; exit 1; } - - -tests: test drafttest miektest rfctest - -test2: test - @ PYTHONPATH=$$PWD python scripts/xml2rfc --cache tests/cache tests/input/rfc6635.xml --text --out tmp/rfc6635.txt && diff -I "$(datetime_regex)" -I "$(version_regex)" tests/valid/rfc6635.txt tmp/rfc6635.txt - -upload: - python setup.py sdist upload --sign - rsync dist/xml2rfc-$(shell PYTHONPATH=$$PWD python scripts/xml2rfc --version).tar.gz /www/tools.ietf.org/tools/xml2rfc2/cli/ - toolpush /www/tools.ietf.org/tools/xml2rfc2/cli/ - - -changes: - svn log -r HEAD:1 | sed -n -e 's/^/ * /' -e '1,400p' | egrep -v -- '^ \* (----------|r[0-9]+ |$$)' | head -n -1 | fold -sbw76 | sed -r 's/^([^ ].*)$$/ &/' debian/patches/series0000644000000000000000000000002512244765076012044 0ustar avoid-makefile.patch debian/changelog0000644000000000000000000001234012245231721011037 0ustar xml2rfc (2.4.3-1) unstable; urgency=low * new upstream release (major overhaul to python) (Closes: #727729, #556614) * Bump Standards-Version to 3.9.4 (no changes needed) * generate man pages from --help output -- Daniel Kahn Gillmor Fri, 22 Nov 2013 00:38:23 -0800 xml2rfc (1.36-5) unstable; urgency=low [ Helmut Grohne ] * Always remove /etc/sgml/xml2rfc.cat when it is not a conffile. (Closes: #680291) -- Daniel Kahn Gillmor Sun, 14 Oct 2012 19:30:24 -0400 xml2rfc (1.36-4) unstable; urgency=low * Bump Standards-Version to 3.9.3 (no changes needed) * increase build-dep on debhelper to >= 9.20120830, now that #681194 is closed (Closes: #680291) -- Daniel Kahn Gillmor Fri, 31 Aug 2012 14:15:56 -0400 xml2rfc (1.36-3) unstable; urgency=low [ Helmut Grohne ] * Convert to debhelper 9. * Especially use dh_installcatalogs. (Closes: #674911, #656170) -- Daniel Kahn Gillmor Sun, 24 Jun 2012 19:09:07 -0400 xml2rfc (1.36-2) unstable; urgency=low * added postrm script to purge /etc/sgml/xml2rfc.cat{,.old} (Closes: #656170) (thanks to Andreas Beckmann for the report, and dh_installcatalogs for the example fix). * debian/rules: updated to include build-{arch,indep} targets. -- Daniel Kahn Gillmor Tue, 17 Jan 2012 00:01:44 -0500 xml2rfc (1.36-1) unstable; urgency=low * New Upstream Release (Closes: #626929) * bumped Standards-Version to 3.9.2 (no changes needed) * updated debian/copyright to DEP5 rev 174 -- Daniel Kahn Gillmor Mon, 16 May 2011 11:38:49 -0400 xml2rfc (1.35-1) unstable; urgency=low * New Upstream Release. * switch to 3.0 (quilt) source format. * bump standards version to 3.8.4 (no changes needed) -- Daniel Kahn Gillmor Sun, 18 Apr 2010 18:07:48 -0400 xml2rfc (1.34-1) unstable; urgency=low * Taking over package (thanks for all your work, Florian!) * New Upstream version (Closes: #506652, #555288). * Move to non-free while waiting on resolution of IETF licensing for embedded blurbs. Add more info about the licensing situation, including text of IETF-Trust-License-Policy. * debian/copyright: made machine-readable. -- Daniel Kahn Gillmor Thu, 03 Dec 2009 16:26:19 -0500 xml2rfc (1.33.dfsg-1) unstable; urgency=low * New upstream version. * Compatible with tcl8.5. Closes: #466237. -- Florian Weimer Sun, 09 Mar 2008 09:13:27 +0100 xml2rfc (1.32.dfsg-1) unstable; urgency=low * New upstream version. Closes: #407591. -- Florian Weimer Sat, 20 Jan 2007 11:14:41 +0100 xml2rfc (1.31.dfsg-1) unstable; urgency=low * New upstream version. Closes: #380492. * Bump Standards-Version. No changes required. -- Florian Weimer Mon, 21 Aug 2006 07:43:55 +0200 xml2rfc (1.30.dfsg-1) unstable; urgency=low * Remove non-DFSG material from upstream tarball. -- Florian Weimer Sat, 21 Jan 2006 15:50:32 +0100 xml2rfc (1.30-1) unstable; urgency=low * New upstream release. * Install additional entity files. -- Florian Weimer Tue, 16 Aug 2005 09:47:49 +0200 xml2rfc (1.29-1) unstable; urgency=low * New upstream release. * Updates boilerplates, partially fixing Debian bug #303131. More IETF-conformance changes are expected. -- Florian Weimer Tue, 3 May 2005 13:24:18 +0200 xml2rfc (1.26-1) unstable; urgency=low * New upstream release. * Fix unwanted localization. Closes: 274191. -- Florian Weimer Thu, 30 Sep 2004 11:11:54 +0200 xml2rfc (1.25-1) unstable; urgency=low * New upstream release. * Add watch file. Closes: #258182. -- Florian Weimer Tue, 17 Aug 2004 10:25:18 +0200 xml2rfc (1.24-2) unstable; urgency=low * Repackage as a non-native package. -- Florian Weimer Sat, 10 Jul 2004 11:45:26 +0200 xml2rfc (1.24-1) unstable; urgency=low * New upstream release. Closes: #258182. -- Florian Weimer Sat, 10 Jul 2004 11:25:42 +0200 xml2rfc (1.23-1) unstable; urgency=low * New upstream release -- Florian Weimer Sun, 4 Apr 2004 12:20:35 +0200 xml2rfc (1.22-1) unstable; urgency=low * New upstream release -- Florian Weimer Fri, 27 Feb 2004 11:19:46 +0100 xml2rfc (1.21-1) unstable; urgency=low * New upstream release -- Florian Weimer Thu, 20 Nov 2003 15:08:34 +0100 xml2rfc (1.20-1) unstable; urgency=low * New upstream release * Upstream now incorporates the relevant parts of the "--"/"+" fix. * Fixed typo in manpage. * Updated copyright statement. -- Florian Weimer Sun, 14 Sep 2003 12:12:12 +0200 xml2rfc (1.15-2) unstable; urgency=low * Dont rely on "--" is "+". Closes: #185793. (Basic patch from Chris Waters, slightly extended.) * Remove debian/files in "clean" target. -- Florian Weimer Sat, 22 Mar 2003 18:23:45 +0100 xml2rfc (1.15-1) unstable; urgency=low * First version. Closes: #175412. -- Florian Weimer Sun, 5 Jan 2003 12:20:54 +0100 debian/watch0000644000000000000000000000012612142770077010225 0ustar version=3 https://pypi.python.org/packages/source/x/xml2rfc/xml2rfc-([0-9.]*)\.tar.gz debian/xml2rfc.docs0000644000000000000000000000004511771716753011433 0ustar debian/IETF-Trust-License-Policy.txt debian/xml2rfc.sgmlcatalogs0000644000000000000000000000005711771716753013166 0ustar debian/catalog /usr/share/sgml/xml2rfc/catalog debian/clean0000644000000000000000000000005112245200407010163 0ustar *.pyc */*.pyc */*/*.pyc debian/xml2rfc.1 debian/catalog0000644000000000000000000000034111661547607010536 0ustar SYSTEM "rfc2629.dtd" "dtd/rfc2629.dtd" DOCTYPE rfc "dtd/rfc2629.dtd" PUBLIC "-//IETF//ENTITIES XHTML subset for RFC 2629//EN" "dtd/rfc2629-xhtml.ent" PUBLIC "-//IETF//ENTITIES Other for RFC 2629//EN" "dtd/rfc2629-other.ent" debian/copyright0000644000000000000000000000562712143007354011132 0ustar Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: xml2rfc Upstream-Contact: Henrik Levkowetz Source: https://pypi.python.org/pypi/xml2rfc/ Disclaimer: This package is not in Debian's main archive because it contains sections of redistributable (but not modifiable) documents licensed by the IETF Trust. Discussions are underway to try to get rights to modify the sections to bring the package back into main. Note that the output produced by xml2rfc may also include more restrictive copyright statements, to conform with ISOC and IETF requirements. This should not affect the DFSG-freeness of the xml2rfc package itself. Files: * Copyright: Henrik Levkowetz License: BSD Files: debian/* Copyright: 2003-2013 Florian Weimer, Daniel Kahn Gillmor License: BSD License: BSD Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the author nor the names of the contributors may be used to endorse or promote products derived from this software without specific prior written permission. . THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUHTORS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. License: BSD+IETF-Trust Most data in this file is under a BSD license, but it incorporates portions of documents published by the IETF, under the IETF Trust's Legal Provisions Relating to IETF Documents, found at http://trustee.ietf.org/docs/IETF-Trust-License-Policy.pdf (see also /usr/share/doc/xml2rfc/IETF-Trust-License-Policy.txt.gz), which states (section 3.c.iii) that for use outside the IETF process, it is acceptable to copy, publish, display, and distribute unmodified portions of the IETF Contributions and IETF Documents provided that they are clearly attributed. . This software takes advantage of that license for free redistribution.