Package: git-annex
Version: 3.20120629
Severity: normal
I might have misunderstood the meaning of 'preserve' here but if it supposed to
maintain the same extension in the key file as in the original -- then it
doesn't happen:
$> git init
Initialized empty Git repository in /tmp/repo1/.git/
$> git annex init --backend=SHA1E
init ok
(Recording state in git...)
$> cp
/home/yoh/deb/perspect/cmtk/cmtk.gitsvn/data/testing/inputs/jacobian-03.nii.gz .
$> touch test.nii test2.gz
$> git annex add *
add jacobian-03.nii.gz (checksum...) ok
add test2.gz (checksum...) ok
add test.nii (checksum...) ok
(Recording state in git...)
cached/staged changes:
jacobian-03.nii.gz | 1 +
test.nii | 1 +
test2.gz | 1 +
$> git commit -m 'added files with different extensions' -a
[master (root-commit) 456d4f3] added files with different extensions
3 files changed, 3 insertions(+)
create mode 120000 jacobian-03.nii.gz
create mode 120000 test.nii
create mode 120000 test2.gz
$> ls -l
total 12
lrwxrwxrwx 1 yoh yoh 182 Jul 5 17:09 jacobian-03.nii.gz ->
.git/annex/objects/Qz/qP/SHA256-s4690--a2083e82976b8016350752f063b6ce33f3744dc0facc2e8ece9b86eacf728267/SHA256-s4690--a2083e82976b8016350752f063b6ce33f3744dc0facc2e8ece9b86eacf728267
lrwxrwxrwx 1 yoh yoh 176 Jul 5 17:09 test.nii ->
.git/annex/objects/2K/49/SHA256-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
lrwxrwxrwx 1 yoh yoh 176 Jul 5 17:09 test2.gz ->
.git/annex/objects/2K/49/SHA256-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
as you can see -- all keys lack any extension and moreover two empty files just
point to the same "key"
I was interested to see how git annex would handle 'composite' extensions, e.g.
like in this case .nii.gz, where both present "meta-information". May be it
could become aware of most common compression schemes (.gz, .bz2, etc) thus
maintaining both preceeding and compression parts of the extension? i.e.
.nii.gz in the example above.
or may be more generally for anything which looks like a composite 2 level
extension ;)
-- System Information:
Debian Release: wheezy/sid
APT prefers stable
APT policy: (100, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages git-annex depends on:
ii curl 7.21.7-1
ii git 1:1.7.10-1
ii libc6 2.13-33
ii libffi5 3.0.10-3
ii libgmp10 2:5.0.2+dfsg-1
ii libpcre3 8.12-4
ii openssh-client 1:5.8p1-7
ii rsync 3.0.9-1
ii uuid 1.6.2-1.3
ii wget 1.13-1
Versions of packages git-annex recommends:
ii lsof 4.81.dfsg.1-1
Versions of packages git-annex suggests:
pn bup <none>
ii gnupg 1.4.12-4
ii graphviz 2.26.3-7
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
