I bought new ThinkPads in 2012 (well 2013), 2018, and 2023 (could have been 2021). 2012 to 2018 (i5-320M to 8250U) doubled performance, and 2018 to 2023 (to Ryzen 7650U Pro) doubled performance again.
That is, 2012 to 2021 quadrupled performance, and it about halved the power consumption, at light use anyway. Batteries can now last more than 3 hours, it's amazing.
but postfix is manually installed, postfix Conflicts mail-transport-agent, exim4 Provides mail-transport-agent.
Instead of
Error: Conflict: postfix:amd64 -> postfix:amd64=3.8.6-1build2 -> not exim4-daemon-heavy:amd64=4.97-4ubuntu4 -> not exim4:amd64=4.97-4ubuntu4 but exim4:amd64=4.97-4ubuntu4
The next step is to actually make this work correctly - right now the API isn't actually exposed from libapt-private.
And then rewrite the reporting. For each step of the implication graph, we need to look back up the original Dependency in the cache and then render one per line.
And this will become the error reporting format too so you get error messages like
As for the direction of the trixie transitional package, maybe that is the best. We'll certainly kill it after Trixie, then apt install keepassxc tells you the two choices and you can decide for yourself.
@debacle@nekohayo@keepassxc People are free to run upstream provided packages whether it be flatpak, snaps, or appimages to get the upstream experience.
It's not the Debian maintainer's job to implement the wishes of the upstream authors but to ensure that the software as delivered by Debian is not in conflict with Debian's values.
This includes patching out online functionality, dangerous IPC, pregenerated code, even the JavaScript shipped or referenced from external servers in html pages.
@nekohayo The whole "unilaterally" thing strikes me as an odd description. Which and how software is shipped is the decision of the distribution and its developers, and while they can seek input from upstream ultimately upstreams wishes are secondary. The packager needs to maintain the values of the distro, and is held to it by the other developers if necessary by ways enshrined in the constitution.
In this case communication with upstream broke down years ago anyway
@Suiseiseki There might be, but the point is that forcing the team building the installers to build two (and people to test two installers) would be unfair to them.