In at least the past couple of updates of Mattermost, the .deb package has changed contents of /opt/mattermost/client/root.html sometime after installing the update, which changes the file’s checksum. This is an issue for people like me, who run debsums --changed daily as part of monitoring the integrity of my server.

I’m not intimately familiar with Debian packaging, but I don’t think those (checksummed) installation files should change post-install. Maybe an unchanging template file should be installed instead, and the final file generated from that?

(I’ve inspected the file, and the only change from the package-provided one is an addition of ”js.stripe.com/v3” to aheader tag, so I’m pretty sure this is a packaging issue and not filesystem corruption or a malicious attacker.)

As a workaround, I can of course recalculate the new checksum, and update the .md5sums file where it’s listed accordingly, but… eww.

(Somewhat related: #26769)

Tuulenkaato Pookipolulla vähän ennen lintutornia.

Updated the Device information section above accordingly.

I just updated to 22.1 and can confirm that the issue is indeed still unfixed.

I blocked the account all those posts listed were from, then unblocked the domain (after which the posts were still there on the home feed), then blocked it again, and now those posts appear to have vanished. I don’t know which of the steps were crucial, but I’m open to experimenting further if it can help.

I added pubeurope.com to my blocked domains, and now my home feed consists of nothing but posts from that domain.

I’ve apparently blocked Threads previously (although I don’t remember it, so it may just be a default), but I don’t recall seeing posts from Threads in my timeline. Certainly not completely filling it like this.

I’m on Pixelfed.social.

With a 2D toy model and using flow of water to visualize the physics, this world should obviously have something named after Steve Mould.

Switched to 11.1 and tried updating those components again. No change unfortunately.

home-assistant_2024-11-14T09-59-20.244Z.log

After last night’s refresh I’m now running 2024.10.4. Attempting to update Nordpool, fmi-hass-custom and pytapo fail with:

Unable to install package nordpool==0.4.2: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)
Unable to install package fmi-weather-client==0.4.0: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)
Unable to install package pytapo==3.3.32: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)

It’s apparently due some changes in core, as some people running HA inside a customized Docker have also suffered this.

In the previous latest/stable, updating Nordpool and FMI weather client failed with errors about pip’s version, so I had reverted those back to their earlier versions and put off retrying the updates until now. Pytapo could be a dependency of Tapo Camera Control, which also updated recently.

Yes, the qemu solution seems simpler and more future-proof than the custom Unifi repository.

Also, my guess would be that few people running Wekan on hardware old enough not to have AVX will have a massively large user base on their installation; most are probably small-time hobbyists like myself, so any negligible slowdowns being exacerbated by scale won’t be much of an issue.