Package Details: digilent.adept.runtime 2.27.9-1

Git Clone URL: https://aur.archlinux.org/digilent.adept.runtime.git (read-only, click to copy)
Package Base: digilent.adept.runtime
Description: The Adept Runtime consists of the shared libraries, firmware images, and configuration files necessary to communicate with Digilent's devices.
Upstream URL: https://reference.digilentinc.com/reference/software/adept/start
Keywords: Adept Digilent
Licenses: custom
Submitter: cyrozap
Maintainer: cyrozap
Last Packager: cyrozap
Votes: 14
Popularity: 0.000000
First Submitted: 2015-08-10 01:54 (UTC)
Last Updated: 2024-05-12 21:14 (UTC)

Latest Comments

1 2 Next › Last »

malsyned commented on 2024-05-12 21:47 (UTC)

Working now, thanks!

cyrozap commented on 2024-05-12 21:20 (UTC)

@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.

malsyned commented on 2024-05-12 20:12 (UTC)

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

sewimoser commented on 2023-01-26 08:47 (UTC)

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.

seeseemelk commented on 2022-12-26 21:51 (UTC)

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.

cyrozap commented on 2021-02-10 03:28 (UTC)

@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.

okasha commented on 2021-02-08 16:24 (UTC)

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

okasha commented on 2021-02-08 14:53 (UTC)

by @yjun : https://wiki.archlinux.org/index.php/Udev#Installation

udev rules written by the administrator go in /etc/udev/rules.d/, their file name has to end with .rules. The udev rules shipped with various packages are found in /usr/lib/udev/rules.d/.

maybe add udev rules to /usr/lib/udev/rules.d/ instead of /etc/udev/rules.d/ as package files

matteoipri commented on 2019-01-30 21:03 (UTC)

@cyrozap: Thank you!

cyrozap commented on 2019-01-30 07:20 (UTC)

@matteoipri, @Sc00tis_P00tis: Sorry for the delay on this--I had assumed Digilent would fix the cert in a timely manner, but I guess that didn't happen.

@matteoipri: HTTPS doesn't need a token--that link you posted actually just redirects to the HTTP version of the files.digilent.com link.

I'll push an update shortly.

1 2 Next › Last »