Search Criteria
Package Details: wd719x-firmware 1-7
Package Actions
Git Clone URL: | https://aur.archlinux.org/wd719x-firmware.git (read-only, click to copy) |
---|---|
Package Base: | wd719x-firmware |
Description: | Driver for Western Digital WD7193, WD7197 and WD7296 SCSI cards |
Upstream URL: | https://github.com/mijailr/wd719x-firmware |
Licenses: | unknown |
Submitter: | pedrogabriel |
Maintainer: | mijailr |
Last Packager: | mijailr |
Votes: | 288 |
Popularity: | 1.63 |
First Submitted: | 2015-03-02 23:50 (UTC) |
Last Updated: | 2020-08-05 01:10 (UTC) |
Latest Comments
1 2 3 4 Next › Last »
rbuchberger commented on 2021-04-04 09:37 (UTC)
Ok! thanks for explaining. I just asked because I didn't see it discussed anywhere.
mijailr commented on 2021-04-02 13:45 (UTC)
Indeed rbuchberger, but the original .exe file doesn't exist anymore and we was having issues with archive.org so we decided to store the exe in the repository and do not allow pull request changing the sha signature or the exe file. But if you have a proposal, please open a pull request.
rbuchberger commented on 2021-04-02 11:13 (UTC)
Sorry to be suspicious, but where did that .exe file come from? It's a little weird to pull a compiled binary from someone's github.
Eeems commented on 2020-10-28 17:29 (UTC)
I've noticed that this PKGBUILD will hang waiting for user input if the lha commands have already extracted their contents as part of a previous run. I'd recommend adding
f
to the options.ryshglene commented on 2020-04-07 18:22 (UTC) (edited on 2020-04-07 18:23 (UTC) by ryshglene)
Done ( :
Edit: sorry, it took a while. I'm not really familiar with how GitHub works
mijailr commented on 2020-04-07 17:18 (UTC)
@ryshglene can you please create a pull request to the aur branch on https://github.com/mijailr/wd719x-firmware
ryshglene commented on 2020-04-07 17:13 (UTC)
I've made these changes to the PKGBUILD:
And now it works for both
lha
andlhasa
. Please update it, if you get the same results.emceebois commented on 2020-04-06 15:50 (UTC) (edited on 2020-04-06 15:53 (UTC) by emceebois)
@mijailr @nightuser
I think I might know what's going on -- when I used lha from the AUR, the filenames were uppercase. When I replaced it with lhasa from Community, the filenames were lowercase.
If there is a flag recognized by both lha and lhasa that makes the command case-insensitive, adding that flag should fix this issue. If not then either some helper commands to do a case-insensitive grep of the output of
lha l
will need to be piped or parameterized to allow both to work, or lha will need to be removed as a dependency and entirely replaced with lhasa.1 2 3 4 Next › Last »