hrkfdn / ncspot

Cross-platform ncurses Spotify client written in Rust, inspired by ncmpc and the likes.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

wrong tag for 1.1.0 release

chenrui333 opened this issue Β· comments

πŸ‘‹ looks like the git tag is wrong for 1.1.0 release, can we re-tag it? Thanks! cc @hrkfdn

image

Thank you, good catch. Should be fixed!

commented

Hi,

Next time, could we please avoid re-taging?
This is not a solution, the correct way IMHO would be to release a new tag with a comment.
Re-taging just causes build failures due to mismatching.

/usr/pkgsrc/audio/ncspot> make checksum
=> Bootstrap dependency digest>=20211023: found digest-20220214
=> Fetching ncspot-1.1.0.tar.gz
=> Total size: 255205 bytes
Requesting https://github.com/hrkfdn/ncspot/archive/v.1.1.0.tar.gz
Redirected to https://codeload.github.com/hrkfdn/ncspot/tar.gz/v.1.1.0
Requesting https://codeload.github.com/hrkfdn/ncspot/tar.gz/v.1.1.0
ftp: Error retrieving file `404 Not Found'
fetch: Unable to fetch expected file ncspot-1.1.0.tar.gz
Trying [2a04:4e42:41::262]:443 ...
Requesting https://cdn.netbsd.org/pub/pkgsrc/distfiles/ncspot-1.1.0.tar.gz
ftp: Error retrieving file `404 Not Found'
fetch: Unable to fetch expected file ncspot-1.1.0.tar.gz
Trying [2001:660:3302:282a:204:75ff:fe9f:9e11]:80 ...
Requesting http://ftp.fr.netbsd.org/pub/pkgsrc/distfiles/ncspot-1.1.0.tar.gz
ftp: Error retrieving file `404 Not Found'
fetch: Unable to fetch expected file ncspot-1.1.0.tar.gz
Trying [2001:470:a085:999::21]:443 ...
Requesting https://ftp.netbsd.org/pub/pkgsrc/distfiles/ncspot-1.1.0.tar.gz
ftp: Error retrieving file `404 Not Found'
fetch: Unable to fetch expected file ncspot-1.1.0.tar.gz
*** Error code 1

Thanks!

EDIT: I'll commit a fix for this to the build environment in a few minutes.

@0323pin To be honest I assumed that no build infra would rely on this tag already as it's plain incorrect, but I'll keep it in mind for next time :)

commented

@0323pin To be honest I assumed that no build infra would rely on this tag already as it's plain incorrect, but I'll keep it in mind for next time :)

Agreed but, I was too quick pushing it yesterday and wasn't expecting the change πŸ˜‰