In all my copies of the darcs darcs repository, I have lately been getting
complaints like

darcs:
/foo/bar/myDarcsRepo/_darcs/inventories/20030921155726-53a90-7d65b741dd9d81ff290ee5423046dd53f783a180.gz:
openBinaryFile: does not exist (No such file or directory)

Is anybody else getting something like this?  It might be something silly I did,
but I can't figure out what.  The commands affected so far are unrecord and check.

% darcs --exact-version | head -n 30
darcs compiled on Jun 18 2006, at 09:34:41
# configured Sun Jun 18 09:29:14 CEST 2006
./configure --no-create --no-recursion

Context:

[Added up links in web interface.
Peter Stuifzand <peter@stuifzand.com>**20060610082238
 Added a link to the 'projects' part of the cgi repository interface, so that
 you go back to the project list.
] 

[Merge makefile targets test_perl and test_shell into test_scripts.
Juliusz Chroboczek <jch@pps.jussieu.fr>**20060607223134
 This should keep parallel make from breaking.
] 

[bump version to 1.0.8pre1
Tommy Pettersson <ptp@lysator.liu.se>**20060522122655] 

[Assume local timezone, not UTC, when parsing iso8601 dates.
Eric Kow <eric.kow@gmail.com>**20060610194409
 
 UTC or any other timezone, can still be specified with an offset, for
 example, 14:00Z for UTC, or 14:00+02 for 2 hours after UTC.
 
] 

[Account for timezone offset in cleanDate  (Fixes issue173).
Eric Kow <eric.kow@gmail.com>**20060610193049

darcs failed:  resource vanished

> /foo/bar/myDarcsRepo/_darcs/inventories/20030921155726-53a90-7d65b741dd9d81ff290ee5423046dd53f783a180.gz:
> openBinaryFile: does not exist (No such file or directory)

Aye, same thing here.  I don't get the issue with a version from 15 May,
I do get it with the current unstable.

I'll try to work it out...

                                        Juliusz

Marking it as resolved, since the culprit was never pushed to a public
repo.

^
>
> but with your recent changes, it's trying to open
>
>   20030921155726-53a90-7d65b741dd9d81ff290ee5423046dd53f783a180.gz
             ^
>
> Obviously, your cleanDate changes are the culprit.

Sorry for the cryptical message, I was concentrating on the code and
forgot to switch to human-to-human I/O mode.  The problem is the digit
``1'' underlined above, which has become a ``5''.  If you look at
showIsoDateTime in IsoDate, you'll notice that this is the last digit
of the hour, which means that the new Darcs is formatting dates with a
four hour offset with respect to the old Darcs.

Eric, I think you're going to have to implement two versions of
cleanDate: one that uses GMT (UTC, whatever) for on-disk structures,
and one that uses local time for human interaction.  But I don't
understand why the offset is four hours (I'm at GMT+2).

                                        Juliusz

This is just a bug-tracker admin advisory.  I have removed msg816 from this bug
because it was confusing the roundup web interface (see issue1528 for details).

The contents were (with some noise inserted to prevent the error)

-----8<-----------------

You're guilty, Eric.

I've got the file [EYK: the word 'file' followed by this filename confused
roundup; so I'm putting this comment in between them so we can view this message]

  20030921115726-53a90-7d65b741dd9d81ff290ee5423046dd53f783a180.gz

but with your recent changes, it's trying to open

  20030921155726-53a90-7d65b741dd9d81ff290ee5423046dd53f783a180.gz

Obviously, your cleanDate changes are the culprit.  I'm reverting them
for now, let me know what you want me to do.

                                        Juliusz