kasabali

19 ms·

331.
by kasabali 2y ago
> Stallman is definitely not someone I’d want in charge of the security of my system. ..but you'd be ok Microsoft being in charge of signing kernel images for secure boot, right?
332.
by kasabali 2y ago
Exactly.
333.
by kasabali 2y ago
Change for the changes sake, of course.
334.
by kasabali 2y ago
Oh, I've already did. You'll see that if you scroll up and read the last sentence in my comment above.
335.
by kasabali 2y ago
For a long time they didn't, and they'd worked better than ever.
336.
by kasabali 2y ago
Stay closer, now they're putting heatsinks on controller chips of SSDs :D
337.
by kasabali 2y ago
Even keeping the drive always 75% empty would be enough, but partitioning off is the easiest way to make sure it's never exceed 25-33% full (assuming the drive behaves like that in the first place). To verify the drive uses the all of
338.
by kasabali 2y ago
AFAIK Windows runs TRIM when you format a partition. So you can create a dummy partition and format it. Then you can either delete or simply not use it. On Linux, blkdiscard can be used in the same manner (create a dummy partition and run b
339.
by kasabali 2y ago
You don't need to go through all that trouble to use most cheap DRAMless SSDs in pSLC mode. You can simply under-provision them by using only 25-33% capacity. Most low end DRAMless controllers run in full disk caching mode. In other wo
340.
by kasabali 2y ago
It's in NEWS.debian file [0], so apt-listchanges (which is installed by default in standard installation) should've shown it. [0] https://salsa.debian.org/debian/keepassxc/-/blob/main/debia
341.
by kasabali 2y ago
> “it’s in the notes!” Your words, not mine. It isn't buried somewhere, it's in NEWS.Debian file, and it's shown to user during the package update by default.
342.
by kasabali 2y ago
It is marked as 'Priority: standard' thus installed as part of the standard Debian installation and shows only NEWS entries by default without needing further configuration.
343.
by kasabali 2y ago
That's a very misleading comparison. When Mozilla (upstream) axes a feature, it's gone permanently and you can't get it back. Which is not the case here at all, here downstream turns off a feature in the default build, while
344.
by kasabali 2y ago
Which more insecure ways? At worst they can install the keepassxc-full package and back to exactly where they were. This isn't tyranny, maintainer has provided a choice.
345.
by kasabali 2y ago
> Imagine if you wake up tomorrow, run a software update and then can't log in to your bank Oh, the horror of being in unstable/testing channel and ignoring the change notice which has been shown automatically during apt-get up
346.
by kasabali 2y ago
> people already have installed will no longer have functionality that many users depend on, breaking their configurations after an update. They'll have to type apt install keepassxc-full ENTER after reading about the packaging cha
347.
by kasabali 2y ago
What was your package named?
348.
by kasabali 2y ago
I can only talk for Debian, not derivatives. You definitely see it for several packages during dist-upgrades. Same in sid/testing except it can be any time though it's a rare event. In case apt/dpkg is configured to ignore th
349.
by kasabali 2y ago
How more clearly do you expect it to be communicated? apt shows the NEWS file during update when there's a change. If it doesn't (ie. user set it up to blindly do the upgrade), you can still check the news file or .debian.changelo
350.
by kasabali 2y ago
apt shows the NEWS file during update when there's a change. If it doesn't (ie. you set it up to blindly do the upgrade), you can still check the news file or .debian.changelog.gz file afterwards. Lastly, when it's shipped i
351.
by kasabali 2y ago
> all users should be keeping up to speed on NEWS They don't need to, it is shown to them during apt-get upgrade > especially in the stable channels This is in testing/unstable. Stable users aren't and won't be a
352.
by kasabali 2y ago
> user-hostile manner This isn't user hostile. You know what'd be user hostile? Removing the functionality and not providing the -full package alongside.
353.
by kasabali 2y ago
Yes, had he been a Fedora maintainer working at Red Hat everyone would be applauding him for his bold decision.
354.
by kasabali 2y ago
Not even comparable. Debian users can choose between the stripped and full version of Keepassxc, unlike the MESA example above.
355.
by kasabali 2y ago
You're talking as if it's a point release of Debian. It is not. It happened in sid/testing, that's what these releases are for. Whether it happened in a point or major release of Keepassxc is irrelevant, because ignorant
356.
by kasabali 2y ago
> that doesn't change the fact that a point release suddenly broke everyone's workflows BS. This change was in Debian sid/testing. That's what it's for. Debian stable users' workflow hasn't been broke
357.
by kasabali 2y ago
> make a very good point when they say that there's minimal testing of the stripped-down build in comparison with the full build, So they should be thankful their software will have better test coverage thanks to Debian users
358.
by kasabali 2y ago
Jeez, then you simply install the keepassxc-full package and move on. It's not like you store your sudo password in keepass database, too.
359.
by kasabali 2y ago
> If a user has an option enabled you don't like anymore, notify them, don't blindly remove functionality and say "your fault for not reading the changelogs". apt shows the NEWS file during update when there's a
360.
by kasabali 2y ago
> Why shouldn't users have been asked before changing the existing package? They were. apt shows the NEWS file during update when there's a change.

More ›