Note that Linux weekly news wrote about this bug in https://lwn.net/Articles/981565/
Was fixing this so tricky ultimately because the gdebi project is dead? If the project was alive, one could simply submit the fix upstream and it would flow out in next releases or be backported easily? Looking at https://tracker.debian.org/pkg/gdebi the source code hosting points to https://code.launchpad.net/~gdebi-developers/gdebi/trunk. Last version in this source code was 0.9.5.7 in 2015, followed by commit that source code moved to https://code.launchpad.net/~gdebi- developers/gdebi/+git/main in 2022, yet that location has zero new commits since the 0.9.5.7 in 2015. Note that this fix done in this bug report was made directly by uploading it to Ubuntu, and it was not committed to the version control of gdebi itself, so the issue is not fixed in Debian yet, and if Debian maintainer does some other fixes (and also he does not commit them to version control), the versions in Debian and Ubuntu will permanently diverge and neither is what is in the "upstream" version control. Is the last committer and original maitnainer Michael Vogt (@mvo) still around to comment? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: [SRU] gdebi-gtk calls pkexec inappropriately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
