GitHub doesn't allow '~' in asset names

[lazka]

We currently have mintty in the queue which has an epoch set, so the version is 1~3.3.0-1. GitHub normalizes that to 1.3.3.0-1, so it is never considered done.

• We need some way to fix that.
• We need to make sure this doesn't happen for other cases and ideally check that the filename hasn't changed after the upload.

[lazka]

Maybe we can use the label to encode the real filename. I need to test that with the API.

[eine]

Maybe we can use the label to encode the real filename. I need to test that with the API.

Yes. E.g., in eine/tip, the label is not used when uploading the asset (https://github.com/eine/tip/blob/master/tip.py#L119). However, label is an optional argument. Then, the name and label are set to the same value (https://github.com/eine/tip/blob/master/tip.py#L123), but it is possible to rename the file and set a different label.

[jeremyd2019]

I hit that too. I just renamed such files before adding them to the pacman db.

# work around github issue with ~ in file name (turns into .)
for a in *~*; do
    mv "$a" "`tr '~' '.' <<<"$a"`"
done

That being said, I'd be interested to see a better solution.