Arch Linux User Repository

80.4-2 adds OAuth authorization and thus the possibility to create a portfolio account for obtaining historic data.

Bevan implemented this crucial feature in the current PKGBUILD – and I'm very happy to welcome him as co-maintainer. :)

Thanks to Bevan, we now have a simple and elegant (compared to my attempt) workaround that lets the PKGBUILD download and use the most recent version of maven (currently 3.9.4). Should not need any intervention from you. :)

After having another thought on this, there is a much better solution for XDG Base Directory support, since you provide /usr/bin/portfolio yourself. In there, you can just start it via /usr/share/portfolio/PortfolioPerformance -data "${XDG_CONFIG_HOME:-$HOME/.config}/PortfolioPerformance/workspace" "$@" (config dir is probably most appropriate, though there are different kinds of files in there).

You could even move the directory beforehand if existent to not require any user interaction (except if they stored their portfolio in there).

Hey, could you do something like this in line 53, to make this package adhere to the XDG Base Directory specification, please?

sed -i 's|@user.home/.PortfolioPerformance|@user.home/.local/state/PortfolioPerformance|' */portfolio/configuration/config.ini

There's currently no other viable way to achieve this. It would be so great to have our home directories less cluttered.

You could print a huge information during package upgrade so users take note that they likely have to act on this improvement.

using --mflags "--skipinteg" seems to be working for now

Now the download succeeds, however the checksum for maven 3.9.14 has not been updated yet.

Looks like maven needs to be bumped to 3.9.14, the previous version is no longer available for download.

80.4-2 adds OAuth authorization and thus the possibility to create a portfolio account for obtaining historic data.

Bevan implemented this crucial feature in the current PKGBUILD – and I'm very happy to welcome him as co-maintainer. :)

Hi @MajorMayer,

80.4-2 fixes this issue by downloading the new version of maven (3.9.12).

The maven file is not found anymore:

Erstelle portfolio... ==> Erstelle Paket: portfolio 0.80.4-1 (Do 18 Dez 2025 12:24:51 CET) ==> Prüfe Laufzeit-Abhängigkeiten... ==> Prüfe Buildtime-Abhängigkeiten... ==> Empfange Quellen... -> 0.80.4.tar.gz gefunden -> Lade apache-maven-3.9.11-bin.tar.gz herunter... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 ==> FEHLER: Fehler beim Download von https://dlcdn.apache.org/maven/maven-3/3.9.11/binaries/apache-maven-3.9.11-bin.tar.gz Breche ab...

Hi @poetter,

we need help from upstream to get this feature working. Bevan wanted to contact the developer to agree on how to include OAUth authorization, but I haven't heard back from him yet. I hope that we will be able to support this feature soon.

Hi @Cobra,

I got a problem with portfolios new historic data feature, that requires to open your browser and login to the website. Instead of the browser opening, I get this error message:

Wed Nov 19 21:05:20 CET 2025 Unable to authenticate (application is not configured correctly).

name.abuchen.portfolio.oauth.AuthenticationException: Unable to authenticate (application is not configured correctly). at name.abuchen.portfolio.oauth.OAuthClient.getAPIAccessToken(OAuthClient.java:94) at name.abuchen.portfolio.ui.jobs.priceupdate.UpdatePricesJob.run(UpdatePricesJob.java:103) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Running portfolio from the x86 package, the website provides, the error does not happen. Any idea how to fix this?