https://bugs.kde.org/show_bug.cgi?id=508845
--- Comment #6 from Andrius Štikonas <[email protected]> --- (In reply to stellarpower from comment #5) > So even for e.g. security patches, are you saying it's up to the package > maintainers to cherry-pick lines and merge those in? There aren't occasions > where something is severe enough to go back to previous branches and cut a > new release for downstream to take up? Just wanting to understand if that is > the case as this would differ from some other projects. Right now Partition Manager is part of automated KDE Gear yy.mm.patch release schedule, so you only have the standard monthly or so releases. Once yy.mm.3 release is out, there wouldn't be any releases of that branch. I think it's technically not even possible because we wouldn't even have a corresponding translation branch (at the moment translations are in SVN and there are master and stable branches there). Anyway, even before that, when KDE Partition Manager had standalone releases, I once created a bugfix release of current stable branch that fixed security bug with an assigned CVE. Luckily that bug didn't affect any of the earlier versions. All the distros either took a patch that fixed CVE or a new release except for Ubuntu. Still not fixed there https://bugs.launchpad.net/ubuntu/+source/kpmcore/+bug/1903774. Ubuntu 20.04 still has that local root privilege escalation. So given that you are on Ubuntu derivative, new releases won't help you, I don't think they care. fsck for 24 hours seem excessive... But again, it's unlikely that --repair causes it. If it's stuck, most likely just simple btrfs filesystem check would also get stuck. But unless your disk was already corrupted, I don't think killing btrfsck process would do any harm. -- You are receiving this mail because: You are watching all bug changes.
