Try to fix updating write-only files

[alexcrichton]

No description provided.

[xtqqczze]

It works, but it's a little annoying the standard library requires this workaround.

[alexcrichton]

Once std::fs::set_times is stable I plan on updating to that, and the stabilization may not be far out

[xtqqczze]

Thanks, will you yank 0.2.28?

[alexcrichton]

I wasn't planning on it, no, since it's pretty easy to update

[xtqqczze]

I thought best practice was to yank for semver breakage, especially in a patch release?

[xtqqczze]

I guess if you don't want to yank it, we can always work around the issue:

# filetime 0.2.28 is broken, so we need to exclude it from the allowed versions.
filetime = ">=0.2.23, <0.2.28, >=0.2.29"

[alexcrichton]

Can you do filetime = "0.2.29"?

[xtqqczze]

In my view, yanking the release is the most appropriate course of action. However, as the maintainer, the decision on how strictly to adhere to semantic versioning rests with you.

[xtqqczze]

filetime = ">=0.2.23, <0.2.28, >=0.2.29"

Unfortunately cargo doesn't support that syntax: rust-lang/cargo#5286

@alexcrichton Could you help me understand why you can't yank the semver-violating version?

[alexcrichton]

I can, but I won't. It's not something I consider semver-violating, it's just a bug.