Your message dated Wed, 30 Dec 2009 12:47:06 +0000 with message-id <e1npxxc-00060w...@ries.debian.org> and subject line Bug#506652: fixed in xml2rfc 1.34-1 has caused the Debian Bug report #506652, regarding Yet another boilerplate change to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 506652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: xml2rfc Severity: grave Version: 1.33.dfsg-2 This means we shouldn't release the current xml2rfc version with lenny. From: "Ed Juskevicius" <e...@nortel.com> Subject: Announcement: New Boilerplate Text Required for all new Submissions to IETF To: "IETF Discussion" <i...@ietf.org>, <ietf-annou...@ietf.org>, <ipr...@ietf.org>, <i...@ietf.org>, <i...@iab.org>, "RFC Editor" <rfc-edi...@rfc-editor.org>, <wgcha...@ietf.org> Cc: trust...@ietf.org Date: Tue, 11 Nov 2008 18:03:36 -0500 Message-ID: <0bdfff51dc89434fa33f8b37fce363d511f95...@zcarhxm2.corp.nortel.com> Greetings. This message is to draw your attention to the significance of the publication of RFC5377 and RFC5378 earlier today. * RFC5377 is Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents * RFC5378 is Rights Contributors Provide to the IETF Trust Note that RFC5378 is also BCP0078. RFC5378 is an update to RFC2026, and RFC5378 obsoletes both RFC3978 and RFC4748. Coincident with the above, the IETF Trustees have posted a new policy document with guidance to the community on: * Legal Provisions Relating to IETF Documents at http://trustee.ietf.org/license-info/ Taken as a set, the documents listed above specify changes that are now required in all new submissions into the IETF. Henrik Levkowetz has updated the idnit tool and AMS have updated the Internet-Draft submission tool to reflect the new requirements. An update to the xml2rfc has been requested. Please review the "Legal Provisions Relating to IETF Documents" and RFC5378 to discover the new boilerplate text that is now required. Please also take action to update the tools you use for creating your documents. New submissions using either the old or the new boilerplate text will be accepted starting today, until 01h00 UTC on December 16th, 2008. After this cutoff date, all new submissions will be required to use ONLY the new boilerplate text. All submissions using old boilerplate text after the cutoff date will be rejected. Regards and FYI. Ed Juskevicius IETF Trust Chair e...@nortel.com p.s. - Don't be surprised if you see periodic reminders about this as we approach December 16th. _______________________________________________ Ipr-wg mailing list ipr...@ietf.org https://www.ietf.org/mailman/listinfo/ipr-wg
--- End Message ---
--- Begin Message ---Source: xml2rfc Source-Version: 1.34-1 We believe that the bug you reported is fixed in the latest version of xml2rfc, which is due to be installed in the Debian FTP archive: xml2rfc_1.34-1.diff.gz to non-free/x/xml2rfc/xml2rfc_1.34-1.diff.gz xml2rfc_1.34-1.dsc to non-free/x/xml2rfc/xml2rfc_1.34-1.dsc xml2rfc_1.34-1_all.deb to non-free/x/xml2rfc/xml2rfc_1.34-1_all.deb xml2rfc_1.34.orig.tar.gz to non-free/x/xml2rfc/xml2rfc_1.34.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 506...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor <d...@fifthhorseman.net> (supplier of updated xml2rfc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Thu, 03 Dec 2009 16:26:19 -0500 Source: xml2rfc Binary: xml2rfc Architecture: source all Version: 1.34-1 Distribution: unstable Urgency: low Maintainer: Daniel Kahn Gillmor <d...@fifthhorseman.net> Changed-By: Daniel Kahn Gillmor <d...@fifthhorseman.net> Description: xml2rfc - XML-based formatting tool for RFCs Closes: 506652 555288 Changes: 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. Checksums-Sha1: 8bc215fe2c279b7cd7bf4ce68b24698f025b34de 1548 xml2rfc_1.34-1.dsc 218ccae49901f075055989343d00c93e8e5ede69 901066 xml2rfc_1.34.orig.tar.gz 5fe476adb4076ebdf6b09d567fa6438c1755f972 10495 xml2rfc_1.34-1.diff.gz b1debbd14367f30dadbd4e04324b376520abf1eb 234986 xml2rfc_1.34-1_all.deb Checksums-Sha256: acde7eb3092822ff6df0f435ed28a8ed7b3cf7c1aa147b9f4fc2fa65d49b6fc4 1548 xml2rfc_1.34-1.dsc bb859d760fc90478e26bbef51261206470cd7407c9bd05d201c215311b43f549 901066 xml2rfc_1.34.orig.tar.gz 2d832d7bfb1f3e088742474095420b5180d6fcf07711afdb6d15d70b7ff66f7e 10495 xml2rfc_1.34-1.diff.gz 01ebd8dbe8f45eb23a5ab814ef471668486e8f73d0a8e3e39c5c989d4e5fbee9 234986 xml2rfc_1.34-1_all.deb Files: 6978b42ab7695243e870feb36dbe81c2 1548 non-free/text optional xml2rfc_1.34-1.dsc a6b10e039f850e5d4f6740b9e90e0797 901066 non-free/text optional xml2rfc_1.34.orig.tar.gz 52190918004a68adcd77b3d9125ab656 10495 non-free/text optional xml2rfc_1.34-1.diff.gz 23e1c51d458eeb24b1670cc80410de67 234986 non-free/text optional xml2rfc_1.34-1_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIVAwUBSzbw0szS7ZTSFznpAQqdAA/5AcpUsxtijyW2QDAC94tdzhGYuwoXAUh+ HsNgpVpMh475b33T934UlX4+9pTMAbajR93c15b22WCCxYayNJzmI9OpWuQfE8Uk 3kB1IhpyZrDU8bF9Dp0/LmI+ve48814O0WMzZLUUmQEqKfoDdgf90h6R82e2XrvI Sqvd8KBWtrlRsq0HK89v3fxFPfUZR7XHsYtRGcvtdFUtGaExmwZiVIvGXpjzv0gb 4tem4luYIDtgUTwHZTgMBck3ZgpRkib/v7nMYzDR6GzfXEvg5hmkpP6ysGQ64/Q4 HN4sofMWTIvRtz3LjsY8No9TEqyiwmtiXAdoToSmnggKDu7I9l8RNiiwG0DNgDq/ qd4kO16AqseYyqTQJBADQnmzrzqOeE4sH0W/p87gcPfU5AbuGEVGBf1gW8lU3Zyb HyFARccsdJYc5Ia+UYRGhbS4HRxNNBehvIPTNu6b5fIfV1xn83vb8YPcnkn77cbc nZ9WVxgKBbQHdlW4X8ecaZY+Ubz1chLgdIohEbKvZi3eqDj9CQnPAHm2DeQwJtMb PYUTyn1ni5me4i98WoJRewLZGQ1YhOGDe36Rz/IH2YErEfZ/ttRkV/fINPugGEbW K73nTg/tYnaAGTZi9o91SAjCcKHyb4koYH8hl9OnSnajGFzWFUm1r4Urtd2OcjZ6 RPSDiTQm2B4= =MhHu -----END PGP SIGNATURE-----
--- End Message ---
