Arch Linux User Repository

@cyrozap That worked. Thank you.

@rscotthathcock I can't reproduce the issue you're seeing. Upon performing a fresh clone and running makepkg the file digilent.adept.runtime_2.27.9-amd64.deb downloads successfully and verifies against the hash without any problems. Try deleting your local copy of digilent.adept.runtime_2.27.9-amd64.deb and build the package again.

Failing the validity check.

==> Validating source_x86_64 files with sha256sums...
 digilent.adept.runtime_2.27.9-amd64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
 -> error downloading sources: /home/scottha/.cache/yay/digilent.adept.runtime 
 context: exit status 1 

Working now, thanks!

@malsyned I've updated the hashes. It seems a "_gpgbuild" file was added in each of the .deb files, changing the hashes without changing the filesystem contents of the packages. Since this was only a build issue and the change doesn't affect the resulting Arch package, I've left the pkgrel the same to avoid forcing everyone to rebuild.

This is failing sha256 validation for me on amd64 today.

==> Validating source_x86_64 files with sha256sums...
 digilent.adept.runtime_2.27.9-amd64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!

The sh256sum I'm getting is c8a2ccf2d9ea1ffa0f3a4ae4ed2ff690a0687ff83382b62dae30fa13198bbf53

In case anyone else has problems with missing symbols. There is a new version (that is not on https://reference.digilentinc.com/reference/software/adept/start) 2.27.7 that fixes that. See: https://forum.digilent.com/topic/20571-using-the-sdk-with-ad2-on-ubuntu/#comment-73608 You can just change pkgver to pgkver=2.27.7 and get new checksums or --skipchecksums, until package updates to that version.

Posting this here as a note for future users: iMPACT segfaults when using this version (2.26.1), but downgrading it to 2.21.3 fixes it.

@okasha: I think I'm going to leave the udev rules as they are, rather than move them under /usr/lib/udev/rules.d. My reason for this is that the rules file from the original package sets the permissions for Digilent devices to 666, and a user might want to change that to be more restrictive or use TAG+="uaccess". Also, changing this now might be an annoying surprise to users that have done this.

That said, if we're going to put rules in the system udev rules directory, we should probably just not bother with the package udev rules file and replace it with our own.

consider this patch for updating https://github.com/okasha55/digilent.adept.runtime-aur