Package Details: ib-tws 1:10.28.1e-1

Git Clone URL: https://aur.archlinux.org/ib-tws.git (read-only, click to copy)
Package Base: ib-tws
Description: Electronic trading platform from discount brokerage firm Interactive Brokers
Upstream URL: http://interactivebrokers.com/
Licenses: custom
Submitter: benalexau
Maintainer: benalexau
Last Packager: benalexau
Votes: 39
Popularity: 0.42
First Submitted: 2013-01-30 06:21 (UTC)
Last Updated: 2024-03-27 22:23 (UTC)

Latest Comments

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 Next › Last »

goodboy commented on 2017-01-12 02:13 (UTC) (edited on 2017-01-12 02:14 (UTC) by goodboy)

Thanks for the explanation benalexau. I've tried starting ib-tws in demo mode and it keeps hanging after the splash screen displays "Processing startup parameters...". Any ideas?

benalexau commented on 2017-01-11 22:29 (UTC)

All AUR packages are hosted in an AUR-specific Git repository. Details are at https://wiki.archlinux.org/index.php/Arch_User_Repository. You can access any AUR's repository via clicking the "View Changes" link at the top of the package's AUR page. Thanks for reporting the checksum issue. Our friends at Interactive Brokers released 962.2c at least twice, each with different hash codes. My scripts (themselves in the aforementioned AUR repository) run daily and only update the AUR package if both the "latest" tarball and the version number extracted from the associated execution log differ from the existing PKGBUILD. Given IB failed to increment the version number despite releasing a tarball with different contents, this explains why the package was not updated to reflect the new hash code. I wish IB would follow best practice and include a version number in the HTTP path, and treat file releases as immutable (ie have a staging environment to test and promote releases, incrementing the version number if a release was promoted in error). Until then we have to struggle with these hacky workarounds...

goodboy commented on 2017-01-11 21:48 (UTC) (edited on 2017-01-11 21:48 (UTC) by goodboy)

benalexau I needed 'c4fb512c612bfddf45f0324ce63a4bc6' to make it work. Is there somewhere that changes can be pushed (i.e. is the PKGBUILD hosted on github)?

benalexau commented on 2017-01-11 04:32 (UTC)

@goodboy, all fixed.

goodboy commented on 2017-01-11 04:08 (UTC)

Hey benalexau, Seems like the checksum is failing again... >>> sudo aura -A ib-tws -x [sudo] password for tyler: aura >>= Determining dependencies... aura >>= AUR Packages: ib-tws aura >>= Continue? [Y/n] aura >>= Building `ib-tws`... ==> Making package: ib-tws 962.2b-1 (Tue Jan 10 19:10:26 EST 2017) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found LICENSE -> Found ib-tws -> Found ib-tws.desktop -> Found ib-gw -> Found ib-gw.desktop -> Downloading tws-latest-standalone-linux-x64.sh... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 89.5M 100 89.5M 0 0 2813k 0 0:00:32 0:00:32 --:--:-- 3078k ==> Validating source files with md5sums... LICENSE ... Passed ib-tws ... Passed ib-tws.desktop ... Passed ib-gw ... Passed ib-gw.desktop ... Passed tws-latest-standalone-linux-x64.sh ... FAILED ==> ERROR: One or more files did not pass the validity check! aura >>= Well, building `ib-tws` failed. aura >>= Would you like to continue anyway? [Y/n] n aura >>= Building failed.

benalexau commented on 2016-06-27 23:15 (UTC)

As per https://en.wikipedia.org/wiki/Java_class_file internal version 52 means Java 8. See https://wiki.archlinux.org/index.php/Java for info on the various Java packages available for Arch (I use package jdk8-openjdk).

NyanCat commented on 2016-06-27 22:58 (UTC) (edited on 2016-06-27 22:59 (UTC) by NyanCat)

Thank you very much. I still had problems with the installation because the jar command was missing. It was necessary to switch from "java-8-openjdk/jre" to "java-7-openjdk" using the archlinux-java command. But now starting ib-tws fails with an exception: Exception in thread "main" java.lang.UnsupportedClassVersionError: jclient/LoginFrame : Unsupported major.minor version 52.0 I will do some research later. I guess it's because I'm using awesome as window manager.

benalexau commented on 2016-06-22 02:16 (UTC)

Hi NyanCat. IB made three changes to the installer and launch model, so the automatic sync scripts required more TLC (click "View Changes" if you're curious). The scripts have now been amended and as such auto-sync should work again. 956.2n is now available from AUR.

NyanCat commented on 2016-06-21 22:44 (UTC)

Hi benalexau, the md5sum of tws-latest-standalone-linux-x64.sh seems to be out of date again. Maybe you can fix it?