Arch Linux User Repository

(follow-up) - yeah, currently it's a bit of a mess :

• I found permalinks, like https://ltspice.analog.com/download/24.1.0/LTspice64.msi
• the above is the same file as what you currently (2025/01/25) get from https://ltspice.analog.com/software/LTspice64.msi
• the version string in the .json file is not 24.1.0 as expected, but '24.0.12' ....
• if you download https://ltspice.analog.com/download/24.0.12/LTspice64.msi, the .json says 24.0.11...

I'm going to try using a permalink, just so the build doesn't break on their next update, but I may not notice for a while to update the PKGBUILD. We can revisit this if analog gets their versioning straightened out.

@cartogan I didn't get any issues.

For me building fails with multiple errors like this one:

** (msiextract:1116): CRITICAL **: 05:12:34.500: gsf_input_name: assertion 'GSF_IS_INPUT (input)' failed

Does anyone else face the same issue?

EDIT: For whatever reason, I no longer have this issue. It builds fine now.

@anemona_anonima thanks, I don't think I was aware of that.

I can at least now make a maintainer script that updates PKGBUILD contents, to be invoked manually; or make this package instead just get the Latest version. I do like having permalinks and the ability to rollback to previous versions however.

Just in case it is useful (didn't see this mentioned in previous posts), Analog provides a link with the latest LTspice installer, version and also the checksum.

https://ltspice.analog.com/download/updates.txt

Tracking the changes in that page could help with the correct checksum for each new release. Hope that helps.

@Mighty_Pig

Make sure your PKGBUILD is up to date (and matches https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ltspice ), it should be fixed since jan 23

It is still failing to download the file.

 -> Downloading LTspice64.msi...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://ltspice.analog.com/download//LTspice64.msi
    Aborting...
 -> error making: ltspice-exit status 1
 -> Failed to install the following packages. Manual intervention is required:
ltspice - exit status 1

Seems like the version is not added correctly to the url?

Edit: For some reason the source inside the PKGBUILD is as following:

source=("${pkgname}.sh"
        "${pkgname}-help.sh"
    "conv.sh"
    "https://ltspice.analog.com/download/${_filever}/LTspice64.msi"
    )

It seems to be using the _filever variable instead of the pkgver it should be using? Even removing cache and redownloading everything still results into having the _filever variable inside the PKGBUILD?

It looks like _filever=24.1.0 is missing?

oops, leftover from a test, and when I re-tried 'makepkg', of course I already had the .msi file downloaded and didn't notice. Should work now.

I'll pin my other comment just to draw attention to the versioning situation.

@fenugrec It looks like _filever=24.1.0 is missing? That aside, thank you for taking over this package and providing such prompt maintenance.

P.S. By 'adding a note,' I actually meant a pinned comment, but your solution is even better!

(follow-up) - yeah, currently it's a bit of a mess :

• I found permalinks, like https://ltspice.analog.com/download/24.1.0/LTspice64.msi
• the above is the same file as what you currently (2025/01/25) get from https://ltspice.analog.com/software/LTspice64.msi
• the version string in the .json file is not 24.1.0 as expected, but '24.0.12' ....
• if you download https://ltspice.analog.com/download/24.0.12/LTspice64.msi, the .json says 24.0.11...

I'm going to try using a permalink, just so the build doesn't break on their next update, but I may not notice for a while to update the PKGBUILD. We can revisit this if analog gets their versioning straightened out.

@yaoyun thanks. Yes, I thought of this when I adopted the package; I'm not sure if analog has permalinks to previous versions. In this case I think it takes a manual intervention anyway; IIRC they changed some of the help hierarchy and some scripts need tweaking. Agreed some form of warning would be nice. I don't think it's possible to output anything before makepkg validates the sums however...