Package Details: ib-tws 985.1c-1

Git Clone URL: (read-only, click to copy)
Package Base: ib-tws
Description: Electronic trading platform from discount brokerage firm Interactive Brokers
Upstream URL:
Licenses: custom
Submitter: benalexau
Maintainer: benalexau
Last Packager: benalexau
Votes: 25
Popularity: 0.56
First Submitted: 2013-01-30 06:21
Last Updated: 2021-06-19 05:38

Latest Comments

1 2 3 4 5 6 ... Next › Last »

benalexau commented on 2021-05-21 23:36

IB updated to 984.1h. The daily script that detects this and maintains the PKGBUILD here had not as yet run. I ran it manually and PKGBUILD is now correct.

esemeniuc commented on 2021-05-21 18:26


I'm currently running into this:

➜  ~ yay -S ib-tws
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur: 1]  ib-tws-984.1f-1

  1 ib-tws                                   (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
:: PKGBUILD up to date, Skipping (1/1): ib-tws
  1 ib-tws                                   (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
:: Parsing SRCINFO (1/1): ib-tws
==> Making package: ib-tws 984.1f-1 (Fri 21 May 2021 11:25:55 AM PDT)
==> Retrieving sources...
  -> Found LICENSE
  -> Found ib-tws
  -> Found ib-tws.conf
  -> Found ib-tws.desktop
  -> Found ib-gw
  -> Found ib-gw.conf
  -> Found ib-gw.desktop
  -> Found
==> Validating source files with md5sums...
    LICENSE ... Passed
    ib-tws ... Passed
    ib-tws.conf ... Passed
    ib-tws.desktop ... Passed
    ib-gw ... Passed
    ib-gw.conf ... Passed
    ib-gw.desktop ... Passed ... FAILED
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: ib-tws

jose1711 commented on 2021-05-21 15:45

@esemeniuc is this still an issue? i haven't see a problem since the change.

esemeniuc commented on 2021-05-21 15:35

You can install without checking: yay -S ib-tws --mflags "--skipchecksums"

jose1711 commented on 2021-05-05 10:53

@benalexau Don't worry about it. Thank you for fixing and get well soon!

benalexau commented on 2021-05-05 01:54

My apologies, @jose1711. I am unwell at present and didn't look at your diff properly. I have now merged your changes. Thanks for your patience.

jose1711 commented on 2021-05-04 11:57

users to see the version number that has been installed.

Maybe I am missing a point but frankly I don't understand this sentence. There is no change to the way how the installed package looks - the only difference is that you'll get

instead of

in the build directory. This actually gives you the information about the version and also gives you a very simple way to switch between them (all you need to do is edit PKGBUILD) if there is a desire to.

I also don't see how this could affect your infrastructure around monitoring and updating the PKGBUILD in aur. Could you please elaborate?

benalexau commented on 2021-05-04 11:27

Thanks @jose1711 for the suggestion.

I prefer to keep it as-is because it allows users to see the version number that has been installed. This also allows automatic detection of when an older version is installed that requires updating.

While it is tedious maintaining symmetry between IB's latest TWS version, running it up to capture logs to extract the version number, and pushing up the new PKGBUILD as needed, I have scripts that do all of this (they're also in the AUR Git repo) and it's rarely more than 24 hours behind the latest TWS release.

I intend to transition these scripts to some other infrastructure in the medium term that will run more often and push up revised PKGBUILDs with fewer delays.

jose1711 commented on 2021-05-04 07:32


In order to fight the hash sum changes (often seen with package managers caching the old data), can you please make the following change?

--- PKGBUILD.orig   2021-05-04 09:30:30.913973088 +0200
+++ PKGBUILD    2021-05-04 09:29:08.783541113 +0200
@@ -20,7 +20,7 @@
-   '')
+   "tws-${pkgver}"::'')
@@ -32,11 +32,11 @@

 build() {
   cd ${srcdir}
-  chmod +x
+  chmod +x tws-${pkgver}
   # Assumes no other Install4J packages are in use by user; if so, makepkg from dedicated user account
   majorVer=$(echo "$pkgver" | sed "s/\([0-9]\+\)\..*/\1/")
   rm -rf $HOME/.install4j $HOME/.i4j_jres $HOME/tws $HOME/Desktop/Trader\ Workstation*.desktop $HOME/.local/share/applications/Trader\ Workstation*.desktop
-  ./ -q
+  ./tws-${pkgver} -q

   BUNDLED_JRE_VER=$(ls -1 ${HOME}/.i4j_jres)
   mv ${HOME}/.i4j_jres/${BUNDLED_JRE_VER} ${HOME}/.i4j_jres/jre

Thank you, jose

KerfuffleV2 commented on 2021-04-14 14:14

@benalexau The likely reason some people get the package integrity problem and you don't is because you're trying it right after you create the package so your hashes match the IB installer script. Later on, IB updates it and the hash no longer matches so people trying to install after that point get the issue.