Sähkökaapin ovi auki tuolla radan vieressä.

I build on release tags, and it looks like building 2.28.0 now succeeds with node 22 as well (whereas 2.27.0 still failed). So I think this is fixed now!

Löysin herkullisen Kaurajemmarin jokin aika sitten. Lyhyen kokeilun perusteella se ei kuitenkaan harmi kyllä tunnu soveltuvan IBS:n takia FODMAP-rajoitteiseen ruokavaliooni.

Pienet jäämät muista viljoista (kuin kaurasta) eivät tavallisesti ole minulla aiheuttaneet ongelmia, eikä periaatteessa mikään muukaan ainesosaluettelossa mainitusta pitäisi olla sopimatonta, jollei sitten kyse ole siirapista. Kysyisinkin, että onkohan tuon valmistukseen käytettävä siirappi kenties fruktoosi- tai inverttisokerisiirappia? Nämä eivät FODMAP-rajoitteiselle sovi, toisin kuin glukoosisiirappi.

No problem; like I said, using node 20 works fine. I only noticed this issue recently, when I rebuilt my build environment, and tried doing so by the book (i.e. according to the docs).

If there’s something I can do to try to further narrow this down, let me know. I’m doing the build in an Ubuntu 24.04 VM, which I can restore to a working snapshot if testing causes it to break.

Tämä sotilasalueesta varoittava kyltti joutanee kai jo museoon, kun se aiheuttaa hämmennystä uusissa kävijöissä tuolla kuntoradan varrella.

Jollei siis tuota metsänplänttiä vielä oikeasti pv valvo.

Is it safe to update mongod* packages outside the script (directly with apt)? I prefer to leave security updates (and only those) to unattended upgrades, but it doesn’t cover these since they’re from the mongodb repository. AFAICT, the script would only allow me to update all packages (with ”Update the Operating System”), but I don’t want non-security updates.

mongod-amd64/noble 8.0.8 amd64 [upgradable from: 8.0.4]
mongodb-database-tools/noble/mongodb-org/8.0 100.12.0 amd64 [upgradable from: 100.10.0]
mongodb-mongosh-shared-openssl3/noble/mongodb-org/8.0 2.5.0 amd64 [upgradable from: 2.4.2]
mongodb-org-database-tools-extra/noble/mongodb-org/8.0 8.0.8 amd64 [upgradable from: 8.0.5]
mongodb-org-shell/noble/mongodb-org/8.0 8.0.8 amd64 [upgradable from: 8.0.5]
mongodb-org-tools/noble/mongodb-org/8.0 8.0.8 amd64 [upgradable from: 8.0.5]

Checks

• I have read the FAQ section, searched the open issues, and still think this is a new bug.

Describe the bug you encountered:

After the app has been updated, the next time it’s opened it shows the changelog (version history).

(See #2852)

Describe what you expected to happen:

I expect opening the app to have it authenticate me to give me access to my passwords. The changelog is a needless detour.

I appreciate the work that goes into developing the app without seeing the changelog. I can find the changelog myself, should I feel the need to read it.

What version of Keepass2Android are you using?

1.12-r5

Which version of Android are you on?

15

The Developer setup documentation says ”We recommend using NodeJS v22”, but trying to build the app (release 2.27.0) with node 22 fails (after nvm install 22.14.0):

npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: mattermost-mobile@2.27.0
npm error notsup Not compatible with your version of node/npm: mattermost-mobile@2.27.0
npm error notsup Required: {"node":"^18.18.0 || ^20.0.0","npm":"^9 || ^10"}
npm error notsup Actual:   {"npm":"10.9.2","node":"v22.14.0"}
npm error A complete log of this run can be found in: /home/jani/.npm/_logs/2025-04-20T11_20_48_320Z-debug-0.log

The build works if I install node 20.19.0 instead.

Lasinsirua ja muuta jätettä valunut pyörätielle tuosta viereiseltä rakennustyömaalta.

I was initially going to report this as a bug, but then I realized I’m in the beta program, so the issue could be specific to that. The unprompted version history at startup is an irritating interruption to using the app, and I could leave the beta program, if I knew that doing so gets rid of the interruption. (I’ve had no other issues with the beta AFAICR.)

What version of Keepass2Android are you using?
1.12-r5