Package Details: clonehero 0.23.2.2-2

Git Clone URL: https://aur.archlinux.org/clonehero.git (read-only, click to copy)
Package Base: clonehero
Description: Clone of Guitar Hero and Rockband-style games
Upstream URL: https://clonehero.net/
Keywords: clone game guitar hero rockband
Licenses: freeware-proprietary
Submitter: 0118999881999119
Maintainer: berocs
Last Packager: berocs
Votes: 2
Popularity: 0.000988
First Submitted: 2018-06-23 10:46
Last Updated: 2020-01-21 18:26

Latest Comments

1 2 Next › Last »

ccapitalK commented on 2020-01-19 04:29

@berocs, I'm experience something similar with pacaur. I believe the reason it failed is because I used it to install it last time as well, so it had a copy of "clonehero-linux.tar.gz" from the previous build stored locally in the cache and hence it didn't bother re-downloading it. I removed this file from the cache and then pacaur worked fine, I then replaced it with a different file and it stopped working again.

I think the canonical way to fix this in the package is to require different versions of the file to be named differently. This is a bit problematic since upstream decides the clonehero tarball name, but can be resolved by using an alias by making the source line in the PKGBUILD:

source=("${pkgname}-${pkgver}.tar.gz"::"http://dl.clonehero.net/clonehero-v.23.2.2/clonehero-linux.tar.gz"
        "$pkgname.install"
        "$pkgname.sh"
        "$pkgname.desktop")

And then referring to clonehero-linux.tar.gz as "$pkgname-$pkgver.tar.gz" in the scripts.

Hopes this helps.

berocs commented on 2019-12-15 18:49

Just FYI, I had to do a

sudo rm -rf /opt/clonehero/Custom/README.txt /opt/clonehero/README.txt

before installing.

berocs commented on 2019-11-12 19:47

I don't really know, maybe yay isn't downloading the new version correctly. Try cloning and building it by hand.

It actually happened the same to me with pamac; I thought it was something about my computer but maybe it's something about the AUR helpers. I suspect it has to do with the extra '.1' at the end of the version number, which maybe confuses them and makes it so they try the sha1sum of the older version without the '.1'. If somebody has any idea if I'm correct and how to fix it, you're welcome to help. Building with makepkg -sic installed fine.

code59656 commented on 2019-11-11 04:59

Hello Berocs, I am currently using yay to try to upgrade clonehero. Every time I try to install the 23.2.1 build, the tar.gz fails a "sha1sums" check. Can anyone please let me know what I need to fix? Thank You!

UnicornsOnLSD commented on 2019-09-29 13:24

Sorry for flagging this, didn't realise that Linux builds of 0.23 weren't out :p

dfanz0r commented on 2019-06-11 01:17

@berocs Clone Hero developer here, we will be releasing v.22.5 later this week which should resolve that issue with notes not rendering properly on some systems.

This was a bug with unity/graphics drivers reporting compute shaders being supported, but then failing to actually compile the shader. It now falls back to the cpu implementation in that case.

mefistofeles commented on 2019-04-27 22:50

Audio is not working at all for me, nothing sounds and nothing shown in terminal. Any ideas why?

berocs commented on 2019-04-04 03:17

I've reverted back to v0.21.7, the game can't be played in v0.22.* because the notes aren't shown.

berocs commented on 2019-04-03 18:08

There's a bug on 0.22.1 with score saving, it's fixed on 0.22.2, don't update yet. I'm working on updating the package.

berocs commented on 2019-04-01 18:41

The issue is with the megacmd-bin package, the SHA-256 isn't correct. I've made a comment on the package, but meanwhile you can edit the megacmd-bin PKGBUILD to use the actual SHA-256, or make it so the SHA-256 isn't checked.