Your message dated Sat, 21 May 2016 22:33:57 +0000 with message-id <E1b4FT3-0002Lk-3V@franck.debian.org> and subject line Bug#737871: fixed in pristine-tar 1.34 has caused the Debian Bug report #737871, regarding O: pristine-tar -- regenerate pristine tarballs 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 owner@bugs.debian.org immediately.) -- 737871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737871 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: O: pristine-tar -- regenerate pristine tarballs
- From: Joey Hess <joeyh@debian.org>
- Date: Thu, 6 Feb 2014 11:41:42 -0400
- Message-id: <20140206154142.GA17206@kitenet.net>
Package: wnpp Severity: normal I am orphaning pristine-tar. Note that this is a native package, so it needs a new upstream maintainer in addition to Debian maintainer. I have no personal need to use pristine-tar now that dgit exists, and I would rather spend time on dgit. I should add a little bit about the reason I wrote pristine-tar in the first place. There were two reasons: 1. I was once in a talk where someone mentioned that Ubuntu had/was developing something that involved regenerating orig tarballs from version control. I asked the obvious question: How could that possibly be done technically? The (slightly hung over) presenter did not have a satesfactory response, so my curiosity was piqued to find a way to do it. (I later heard that Ubuntu has been using pristine-tar..) 2. Sometimes code can be subversive. It can change people's perspective on a topic, nudging discourse in a different direction. It can even point out absurdities in the way things are done. I may or may not have accomplished the subversive part of my goals with pristine-tar. Code can also escape its original intention. Many current uses of pristine-tar fall into that category. So it seems likely that some people will want it to continue to work even if it's met the two goals above already. My feeling is that pristine-tar will eventually need to embed a suite of historical versions of tar and gzip (and bzip2 etc), since upstream changes can break output stability. It already embeds several versions of the compressors. We've slightly been abusing the Debian patches of tar to put in pristine-tar compatability hacks there, and while I appreciate Bdale's willingness to do that, I don't think that's sustainable. Anyone who wants to maintain this is going to need to tackle that issue. It's also helpful if you enjoy the interesting puzzle of taking a file it fails to support currently, and finding the trick to make it work. Without Faidon Liambotis, much of the hardest parts of pristine-tar (particularly pristine-gz) would not have happened. If Faidon wants this package, he has it. -- see shy joAttachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: 737871-close@bugs.debian.org
- Subject: Bug#737871: fixed in pristine-tar 1.34
- From: Antonio Terceiro <terceiro@debian.org>
- Date: Sat, 21 May 2016 22:33:57 +0000
- Message-id: <E1b4FT3-0002Lk-3V@franck.debian.org>
Source: pristine-tar Source-Version: 1.34 We believe that the bug you reported is fixed in the latest version of pristine-tar, which is due to be installed in the Debian FTP archive. 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 737871@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro <terceiro@debian.org> (supplier of updated pristine-tar 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 ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sat, 21 May 2016 13:49:53 -0300 Source: pristine-tar Binary: pristine-tar Architecture: source Version: 1.34 Distribution: unstable Urgency: medium Maintainer: Antonio Terceiro <terceiro@debian.org> Changed-By: Antonio Terceiro <terceiro@debian.org> Description: pristine-tar - regenerate pristine tarballs Closes: 737871 Changes: pristine-tar (1.34) unstable; urgency=medium . * New maintainer (Closes: #737871) * pristine-tar.spec: bump version number * Add tests for very basic usage. These can be run during the build and under autopkgtest - Added build dependencies on shunit2, git, and xdelta * Makefile.PL: make build idempotent * debian/control: - Remove duplicated Section field in binary package - Switch Vcs-* fields to collab-maint repository - Bump Standard-Version to 3.9.8; no changes needed * Add missing debian/source/format * debian/copyright: fix wildcard for pit/suse-bzip2/ * Build with hardening flags * zgz/zgz.pod: fix typo Checksums-Sha1: 943d6180bc698b001035b6a209bfc9e822d975c8 1690 pristine-tar_1.34.dsc 30e6bd1a031af0aaa1f882820c989cc186d1e9e8 129948 pristine-tar_1.34.tar.xz Checksums-Sha256: 7be2141d570235f26584aa070a1536d8258e1d2e80815a09b46ac9aa40be52ff 1690 pristine-tar_1.34.dsc ee40ef7ba70be32b855a9fb4683ff5aa7e72266df0dc228aad92bc6e139c4c90 129948 pristine-tar_1.34.tar.xz Files: e66d2d59bcea51cdb0f8fd230eee6b1d 1690 utils optional pristine-tar_1.34.dsc 81372eb05778c7f980f077258bbaeb0a 129948 utils optional pristine-tar_1.34.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJXQM9QAAoJEPwNsbvNRgveJJMQAORFgczLSyE+ZMqi5j4oF6kt DRWDF3xC7YTD4abCjI4C6ohW/IorHIgzXOnd9vzamiiJY0CcEgWyp9kbEEto2O54 WEe2fq1Atu7iz58kWGAlLzttStmOuKys1pu8DAugtyJ1Qu/VotWqLHQVaPoEwwFy WUGngfmZGnDDaOel0Wtc+3b2AY+B67WHYKBjW/6rMWNkECJlRvhR2mWWeV4YOF9S MfMpLu6CNxU+iVnIcp/RiT4rrskfM5+YdoMK5xP5P/ccu6vULZXRAbFTdJGUcR1f 1Rj6enjfi5AQZyo94GBt1eOSBg6udQRido3LO/KIGKncfryA4XjjMOGIUHvIXsR2 LqvO8G19FDDBFyLuwiSclr6JBXEUM4jt4fJI5pVVCxN83o716Nvv9XL23ZUSdgkR UhenRcHROi49tcfTAgusutNp67At4Ej+fGwMHikp3bD1O53azOgBXVQ4SQmeMuv/ kE4L2xIWOsLQzLp9vmDHBQmsZjZm9NUfdMRYbAWTyAM5lRzC91AUMxOrUagYV2Fm lUEil83G1duqB00ABGcNAAStZGEtr6OoNH9CV2A719e8wFkl6JWCS0x7rNCbTWbA LwMsAANbMVR40FYrUSaFEBSS+O3DDrtgu7ft4COvSioZE1S/6wrowlMtWvzKjsCs CsTsKe95k6mZrQTi6AXa =Oea4 -----END PGP SIGNATURE-----
--- End Message ---