Work around: go to ~/.pub-cache/git and 'rm -rf ...' and re-run 'pub install'

Added Area-Pub, Triaged labels.

Added this to the Later milestone.

Removed Type-Defect label.
Added Type-Enhancement label.

Issue #5941 has been merged into this issue.

Deleting stuff out of your cache is always risky because you don't know which other apps on your machine are also depending on it.

But it would be useful to have a command that's basically "forcibly redownload this" for a package. That way it's still in your cache it's just back to the pristine version.

Exactly. If we want to get fancy, it'd be nice (at least w/ git) to have a pub status or similar to let me know if the associated tree is dirty

@bob,

Can we up the priority on this one? This would be a good one to surface in the editor, especially for Windows users, since the editor can mess up the pub cache sometimes.

We're very tight in M2 as it is right now, but if we can get uploading and the bug list into a happy place, we can try to squeeze this in.

Issue #7192 has been merged into this issue.

I'm going to add --force to pub cache add, which should cover this use case.

Set owner to @munificent.
Added Started label.

Great feature, but I'd still argue for --force (or similar) on get/upgrade

I'd take 'pub cache pristine' which would run through all installed packages, for instance.

Spent some time discussing this and instead of:

$ pub cache add <pkg> --force

we decided a better fit for what our users want is to forcibly redownload everything that was previously cached. So I'm going to add:

$ pub cache repair

which does just that.

Added Fixed label.

This issue has been moved to dart-lang/pub#149.