Package Details: chowtapemodel-lv2-git 2.11.0.r0.ge411646-1

Git Clone URL: (read-only, click to copy)
Package Base: chowtapemodel-git
Description: Physical modelling signal processing for analog tape recording
Upstream URL:
Licenses: GPL3
Provides: chowtapemodel-lv2, chowtapemodel.lv2, chowtapemodel.lv2-git
Submitter: robbert-vdh
Maintainer: robbert-vdh (SpotlightKid, milkii)
Last Packager: robbert-vdh
Votes: 0
Popularity: 0.000000
First Submitted: 2021-11-23 15:03 (UTC)
Last Updated: 2022-10-05 01:27 (UTC)

Latest Comments

1 2 3 Next › Last »

kflak commented on 2022-10-05 06:24 (UTC)

Still getting the validation error, unfortunately...

robbert-vdh commented on 2022-10-05 01:27 (UTC)

Oops yeah seems like I forgot to do that, thanks!

SpotlightKid commented on 2022-10-05 00:59 (UTC)

@robbert-vdh: I don't see an update. Last commit is still from July. git push?

robbert-vdh commented on 2022-10-05 00:10 (UTC)

The patch is also different for me. The commit hashes now contains an additional character. No idea if this is a recent global GitHub change or if they only do this if the hashes would otherwise collide. This is a diff of the patches:

--- fix-missing-utility-include.patch   2022-07-14 15:54:27.055325866 +0200
+++ fix-missing-utility-include.patch   2022-10-05 01:57:56.449785978 +0200
@@ -8,7 +8,7 @@
  1 file changed, 1 insertion(+)

 diff --git a/modules/juce_core/system/juce_StandardHeader.h b/modules/juce_core/system/juce_StandardHeader.h
-index fe164cdd315..cda6bbe8624 100644
+index fe164cdd3157..cda6bbe86248 100644
 --- a/modules/juce_core/system/juce_StandardHeader.h
 +++ b/modules/juce_core/system/juce_StandardHeader.h
 @@ -64,6 +64,7 @@

I've updated the hashes in the assumption that this is not just a fluke or something (and they better not be A/B testing this ha). If anyone gets checksum errors on the patch after this and the commit hashes changed back to fe164cdd315..cda6bbe8624, then please let me know!

kflak commented on 2022-10-04 17:19 (UTC) (edited on 2022-10-04 17:24 (UTC) by kflak)

I haven't touched makepkg.conf, but I am starting to wonder if something is wrong with my network... I'll try to reset everything.

EDIT: cleared out all caches, rebooted my system, reset all network things, but still getting the same response.

SpotlightKid commented on 2022-10-04 17:15 (UTC)

Did you configure a non.standard download agent (DLAGENTS setting) for makepkg? Try using the default one.

Also, make sue that you clear out any cached package repo / src / pkg dir you might have.

kflak commented on 2022-10-04 17:10 (UTC)

It opens a patch file. Looks all normal, afaict

SpotlightKid commented on 2022-10-04 17:08 (UTC)

What happens when you open the URL directly in your browser?

kflak commented on 2022-10-04 17:05 (UTC)

Weird... tried both the ssh and https versions as well, just in case, but in both cases the validity check fails on fix-missing-utility.patch

SpotlightKid commented on 2022-10-04 17:01 (UTC)

@kflak Sorry, I can't reproduce that. If I run updpkgsums and it downloads fix-missing-utility-include.patch anew, the SHA256 doesn't change.

Probably Github returned an (HTML/JSON) error page instead of the correct file in your case.