On Sun, 14 Jul 2024 10:16:37 -0700 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= <[email protected]> wrote: > The symptoms here sound very much like > https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588 which has > now been fixed in Ubuntu, but not submitted to Debian > > There was also a fix drafted in > https://salsa.debian.org/atzlinux-guest/gdebi/-/commit/1de6b00bef539de4458021dc02ed2110f76ab630 > but not record if it worked. It wasn't uploaded to Debian. > > I think the root cause why gdebi is broken is that it is unmaintained. > > 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. > > If it was maintained, and there was a git repository people could > contribute to, many of these bugs would have been fixed. Currently it > is just maintainers doing one-off emergency fixes without storing > anything in git in a way that would allow for contributions from users > like Doug Brown in LP#1854588. > >
Can anybody reproduce this in Debian with an up to date version? To me it looks like this was fixed by this commit https://salsa.debian.org/debian/gdebi/-/commit/467def1dc59d3e2427b7fa9788c8c3abf74506a0 which is present in gdebi 0.9.5.7+nmu8, which already is in trixie? Please inform me if I am mistaken. best /Andreas Rönnquist [email protected]
