Please describe the problem.
If I do git annex init, I consistently get the same UUID's which messes up lots of remote transfers
What steps will reproduce the problem?
If I do git annex init on my system and then git annex info, it always shows
trusted repositories: 0
semitrusted repositories: 3
00000000-0000-0000-0000-000000000001 -- web
00000000-0000-0000-0000-000000000002 -- bittorrent
5df76b66-a137-4b11-bc65-316ee27d52b7 -- :CURRENTPATH [here]
(where currentpath is the path of the git annex repo). It's always 5df
What version of git-annex are you using? On what operating system?
I used the downloaded version, as well as recompiled this morning
git-annex version: 10.20230322-ga91f8070e7
build flags: Assistant Webapp Pairing Inotify TorrentParser Benchmark Feeds Testsuite S3 WebDAV
dependency versions: aws-0.22 bloomfilter-2.0.1.0 cryptonite-0.29 DAV-1.3.4 feed-1.3.2.0 ghc-8.10.7 http-client-0.7.9 persistent-sqlite-2.13.0.3 torrent-10000.1.1 uuid-1.3.15 yesod-1.6.1.2
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 BLAKE2B256E BLAKE2B256 BLAKE2B512E BLAKE2B512 BLAKE2B160E BLAKE2B160 BLAKE2B224E BLAKE2B224 BLAKE2B384E BLAKE2B384 BLAKE2BP512E BLAKE2BP512 BLAKE2S256E BLAKE2S256 BLAKE2S160E BLAKE2S160 BLAKE2S224E BLAKE2S224 BLAKE2SP256E BLAKE2SP256 BLAKE2SP224E BLAKE2SP224 SHA1E SHA1 MD5E MD5 WORM URL X*
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav adb tahoe glacier ddar git-lfs httpalso borg hook external
operating system: linux x86_64
supported repository versions: 8 9 10
upgrade supported from repository versions: 0 1 2 3 4 5 6 7 8 9 10
local repository version: 9
Please provide any additional information below.
I also don't get anything from
git config --local annex.uuid so tried to add a manual UUID, but it starts to feel overly hacky when dealing with critical data
# If you can, paste a complete transcript of the problem occurring here.
# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
# End of transcript or log.
Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Git annex is great, I use it to manage 3TB+ of research data, and it's useful for manually keeping data in track and versioned
Please describe the problem.
If I do git annex init, I consistently get the same UUID's which messes up lots of remote transfers
What steps will reproduce the problem?
If I do git annex init on my system and then git annex info, it always shows
trusted repositories: 0
semitrusted repositories: 3
00000000-0000-0000-0000-000000000001 -- web
00000000-0000-0000-0000-000000000002 -- bittorrent
5df76b66-a137-4b11-bc65-316ee27d52b7 -- :CURRENTPATH [here]
(where currentpath is the path of the git annex repo). It's always 5df
What version of git-annex are you using? On what operating system?
I used the downloaded version, as well as recompiled this morning
git-annex version: 10.20230322-ga91f8070e7
build flags: Assistant Webapp Pairing Inotify TorrentParser Benchmark Feeds Testsuite S3 WebDAV
dependency versions: aws-0.22 bloomfilter-2.0.1.0 cryptonite-0.29 DAV-1.3.4 feed-1.3.2.0 ghc-8.10.7 http-client-0.7.9 persistent-sqlite-2.13.0.3 torrent-10000.1.1 uuid-1.3.15 yesod-1.6.1.2
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 BLAKE2B256E BLAKE2B256 BLAKE2B512E BLAKE2B512 BLAKE2B160E BLAKE2B160 BLAKE2B224E BLAKE2B224 BLAKE2B384E BLAKE2B384 BLAKE2BP512E BLAKE2BP512 BLAKE2S256E BLAKE2S256 BLAKE2S160E BLAKE2S160 BLAKE2S224E BLAKE2S224 BLAKE2SP256E BLAKE2SP256 BLAKE2SP224E BLAKE2SP224 SHA1E SHA1 MD5E MD5 WORM URL X*
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav adb tahoe glacier ddar git-lfs httpalso borg hook external
operating system: linux x86_64
supported repository versions: 8 9 10
upgrade supported from repository versions: 0 1 2 3 4 5 6 7 8 9 10
local repository version: 9
Please provide any additional information below.
I also don't get anything from
git config --local annex.uuid so tried to add a manual UUID, but it starts to feel overly hacky when dealing with critical data
# If you can, paste a complete transcript of the problem occurring here.
# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
# End of transcript or log.
Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Git annex is great, I use it to manage 3TB+ of research data, and it's useful for manually keeping data in track and versioned
What CPU is this happening with?
git-annex generates uuids using https://hackage.haskell.org/package/uuid and the V4 uuid uses https://hackage.haskell.org/package/entropy, which in turn uses RDRAND when available.
So if your CPU supports RDRAND, it seems the CPU must have a broken random number generator! Or there's a bug in that software stack somewhere.
Do you mean you don't get anything different? Surely that outputs something. Or exits with a nonzero exit code.
If you're able to run ghci, here's how to generate a UUID the same way git-annex does:
ghci -e 'import Data.UUID.V4' -e nextRandom
And here's how to get entropy the same way that does:
ghci -e 'System.Entropy.getEntropy 16'