Hi there, When performing some testing on the Darcs 2.8 upload, I noticed that some of our repositories seem to be served up incorrectly over HTTP, for example: ,---- | laney@raleigh> debcheckout haskell-language-javascript | declared darcs repository at http://darcs.debian.org/pkg-haskell/haskell-language-javascript | darcs get http://darcs.debian.org/pkg-haskell/haskell-language-javascript haskell-language-javascript ... | Hash failure in /home/laney/.darcs/cache/pristine.hashed/0000001541-e6351b388ee23616eedf037f3d640a0e75bbedb7f145f9b7f25ba719345bceac | Hash failure in /home/laney/.darcs/cache/pristine.hashed/0000000002-10159baf262b43a92d95db59dae1f72c645127301661e0a3ce4e38b295a97c58 | Hash failure in /home/laney/.darcs/cache/pristine.hashed/0000002244-9f916c300ff6ee072f3330d0657552bbf3de1c39a42e7b0acac5879204171c9d | Hash failure in /home/laney/.darcs/cache/pristine.hashed/0000000294-841ee6b1812318415c890f3a4710751f191c77d5152b2e8afe3a0ecdc03b0c0a | Hash failure in /home/laney/.darcs/cache/pristine.hashed/0000000109-0b31a65727965878807a9006213151208d10dc1173738055701233e3188d8b59 | Hash failure in /home/laney/.darcs/cache/pristine.hashed/0000000089-2f6b009e8e7ed6c4aec6cce888d8b2a6a7855e6163bd7d85abec759277788363 | Hash failure in /home/laney/.darcs/cache/pristine.hashed/0000000242-0cdba734c96fd0d0f7b8a1152a3bc8c2c87662845ecf0cdf192863a20e928ead | Copying patches, to get lazy repository hit ctrl-C... | Hash failure in /home/laney/.darcs/cache/patches/0000000373-e121daf41f3f20e1ba5ab65a5d050563712a11e3b722c3cf108c89a7ee736fde | Hash failure in /home/laney/.darcs/cache/patches/0000000352-89a6f3c74ec4252e54fed5406818be3659945cae25830c0a0e55b0a4fec62ab8 | Hash failure in http://darcs.debian.org/pkg-haskell/haskell-language-javascript/_darcs/patches/0000000352-89a6f3c74ec4252e54fed5406818be3659945cae25830c0a0e55b0a4fec62ab8 | | darcs failed: Couldn't fetch `0000000352-89a6f3c74ec4252e54fed5406818be3659945cae25830c0a0e55b0a4fec62ab8' | in subdir patches from sources: `---- (I tried cleaning the cache and also in a fresh chroot with unstable's darcs. No change.) Does anyone know what the problem is here? darcs repair when run in the repository on vasks claims to see no problem and checking out over SSH is fine so it seems something is going wrong on the HTTP side. Cheers, -- Iain Lane [ iain@orangesquash.org.uk ] Debian Developer [ laney@debian.org ] Ubuntu Developer [ laney@ubuntu.com ] PhD student [ ial@cs.nott.ac.uk ]
Attachment:
signature.asc
Description: Digital signature