https://bugs.kde.org/show_bug.cgi?id=523900
--- Comment #3 from John <[email protected]> --- (In reply to Nate Graham from comment #2) > Discover respects locks that you can set using your command-line package > manager. > > However Discover won't add this feature itself in the GUI because it can > cause the very thing you're complaining about: breaking the system. When you > have a "made of packages" distro, and you start selectively holding back > certain versions, you need to be a technical expert who knows exactly what > you're doing in every way, or else you're asking for trouble in the future. > > In general the right thing to do here is to talk to the people who made your > distro and tell them that specific package updates are causing problems. > Otherwise they may never know. It great that Discover respects the locks that I can set with the command-line package manager, in this case Apt, as it should. But that doesn't mean that is should be just a one way door, just read and and respect the lock, but never help in creating any lock. Yes, I know what selectively holding back certain versions mean, but what would you do when these packages regressed so much that they make the whole system unbootable? Or what would you do when a package like the one with UEFI certificates constantly fails to install and your are left with the same error to read that you already did a couple of time and you have to close it manually? What's the point of having a graphical package manager when some things, like holding back some packages for a while is not allowed, but it's respected if you do it from the terminal commands? This doesn't make too much sense! It just forces users to waste even more time after they have a problem! Have you at least looked at how many packages I have to find and then apply the hold command? Do you think that's easy to find and apply a command for all of them? Or that it's easy to find how, for each type of package manager or are we forgetting that Linux unfortunately has at least 3? As for informing the distro developers / maintainers, sure, but I don't always have the time to report all the problems I find. I do what I can with the time I have, like everybody else. But that doesn't mean that I should be forced to just report and then wait for months until stuff is fixed and in the meantime just choose how I waste more time: Learning command-line package manager commands for each package manager to hold back problematic packages and then search and apply those commands or do it like until now, graphically searching and unchecking them so my system doesn't break. And this is not the first time it happens as it happened also last year with Qbittorrent receiving an update that made it not starting at all so I had to track down its .deb package for the 'stable' repository, install that own and the fight with every update for it. It got fixed eventually, even though I didn't reported and other people did it. Thanks for nothing and letting me waste my time in one way or another as whatever I can do from here is only time wasting! I know wonder how much time it will take until you will make Plasma similar in attitude to Windows 10 and 11 with forced updates by removing the ability to untick some of them, all in the name of make it more secure for the user as maybe someone breaks the system by not installing all of them always. Or until you remove the ability to open the administrator mode in Dolphin or to add some global environment variables with Kate as someone might break their system. I see that the fact that updates breaking even the booting of the system, which probably affects dual-boot too, is accepted. Disappointing! No wonder that in the past a request to display the updates by danger level (firmware, bootloader, kernel, graphics, etc.) was also dismissed. -- You are receiving this mail because: You are watching all bug changes.
