Your message dated Fri, 01 Feb 2008 03:02:01 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#463352: fixed in pristine-tar 0.5
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: pristine-tar
Version: 0.4
Severity: wishlist
Hi,
as you probably know, git is a content tracker, and (at the moment at
least) it completely ignores empty directories. Unfortunately, some
upstream tend to ship tarballs containing empty directories, which lead
to such problems while trying to re-use the delta generated using a git
working copy:
| tar: graphviz-2.16.1/windows/cmd/bin: Cannot stat: No such file or directory
| tar: graphviz-2.16.1/windows/lib/lib: Cannot stat: No such file or directory
| tar: graphviz-2.16.1/windows/lib/lib/Debug: Cannot stat: No such file or
directory
| tar: graphviz-2.16.1/windows/lib/lib/Release: Cannot stat: No such file or
directory
| tar: graphviz-2.16.1/windows/plugin/lib: Cannot stat: No such file or
directory
| tar: graphviz-2.16.1/windows/plugin/lib/Debug: Cannot stat: No such file or
directory
| tar: graphviz-2.16.1/windows/plugin/lib/Release: Cannot stat: No such file or
directory
| tar: Error exit delayed from previous errors
| command failed: tar cf /tmp/pristine-tar.vF1dw8NFlR/gentarball --owner 0
--group 0 --numeric-owner -C /tmp/pristine-tar.vF1dw8NFlR/workdir
--no-recursion --mode 0644 --files-from /tmp/pristine-tar.vF1dw8NFlR/manifest
Would you need an example of such a tarball, just apt-get source
graphviz, or help yourself in http://graphviz.org/pub/graphviz/ARCHIVE/,
2.8 is also affected, for example.
Note that I got rid of the empty directories when I generated the
deltas, using a really clean working directory (git-checkout -f,
git-clean -x -d), so the problem isn't that the empty directories were
present in the working directory during gendelta, and then absent during
gentar.
Solutions I can see right now (disclaimer: I'm really new to
pristine-tar):
- modify the handling of upstream sources, adding an empty .gitignore
files so that the empty directories can be tracked in git.
git-import-orig from git-buildpackage could be added a warning
message and a flag to create such empty .gitignore files.
I've tested adding such .gitignore files, and pristine-tar just does
the right thing and generate the expected tarballs.
Problem: While it's not really a problem for people starting using
pristine-tar, it requires modifications to the existing trees for
people already having stored upstream branches, and that might mean a
mess if tags are already being used.
- modify the format of deltas so as to support empty directories there.
Already-existing trees (upstream branches, and their tags) wouldn't
have to be modified, it would just be needed (if there are some
directories in the original tarball) to update the deltas so that
these empty directories get represented and then later added back to
the generated tarballs.
I don't think adding some strings representing empty directories
should bloat the deltas.
Cheers,
--
Cyril Brulebois
--- End Message ---
--- Begin Message ---
Source: pristine-tar
Source-Version: 0.5
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:
pristine-tar_0.5.dsc
to pool/main/p/pristine-tar/pristine-tar_0.5.dsc
pristine-tar_0.5.tar.gz
to pool/main/p/pristine-tar/pristine-tar_0.5.tar.gz
pristine-tar_0.5_i386.deb
to pool/main/p/pristine-tar/pristine-tar_0.5_i386.deb
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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Joey Hess <[EMAIL PROTECTED]> (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 [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 31 Jan 2008 21:52:45 -0500
Source: pristine-tar
Binary: pristine-tar
Architecture: source i386
Version: 0.5
Distribution: unstable
Urgency: low
Maintainer: Joey Hess <[EMAIL PROTECTED]>
Changed-By: Joey Hess <[EMAIL PROTECTED]>
Description:
pristine-tar - regenerate pristine tarballs
Closes: 463352
Changes:
pristine-tar (0.5) unstable; urgency=low
.
* Moved to git, and added a Vcs-Browser field.
* pristine-tar can now "commit" deltas for a tarball directly to a git
branch, and then "checkout" the original tarball again. Git users
are recommended to use these new subcommands because they're easier,
store the deltas in a consistent location, and avoid problems with
recreating things like empty directories that git doesn't track.
Closes: #463352
* Thanks to madcoder for help with manipulating git branches without
touching the working copy.
* Fix paranoia check in pristine-gz to correctly handle parameters
that take an option.
Files:
072b74c9dcf034fa75583bb0f8427f98 676 utils optional pristine-tar_0.5.dsc
7c75224fe62c287d471b6cbf1b9835a5 20896 utils optional pristine-tar_0.5.tar.gz
40db4f430e47fe66134f2ba3ee43a0af 28590 utils optional pristine-tar_0.5_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHoooN2tp5zXiKP0wRAqx4AKCKzv66CK5qzaILxueDYypYuQJ8DACglmfC
ISPvuwtSiN0EeEF+jI5bTPk=
=ifYp
-----END PGP SIGNATURE-----
--- End Message ---
