On Sat, 2 Nov 2024 14:21:58 +0100 =?utf-8?B?0L3QsNCx?= <[email protected]> wrote: > On Tue, Sep 10, 2024 at 01:15:14AM +0200, Andreas Rönnquist wrote: > > On Mon, 9 Sep 2024 22:00:07 +0200 Andreas =?UTF-8?B?UsO2bm5xdWlzdA==?= > > <[email protected]> wrote: > > > I'm working on importing the changes of the latest uploads into a git > > > repository with proper author information - is this anything that would > > > be welcome? Then we can set the Vcs- fields to git and use git for the > > > packaging fully and not the (which looks like it is abandoned) bazaar > > > repository. > The upstream is already in git. The bazaar says > 492. By Michael Vogt on 2015-07-08: releasing package gdebi version > 0.9.5.7 > 493. By Benjamin Drung on 2022-11-02: Move to > https://code.launchpad.net/~gdebi-developers/gdebi/+git/main > and https://code.launchpad.net/~gdebi-developers/gdebi/+git/main > has an accurate history of everything imported from bazaar. > > > "Proof of concept" available at > > https://salsa.debian.org/gusnan/gdebi > This appears to actually /be/ a fork (continuation) > of the repository above (SHAs match). > > Given that the old upstream is all but dead with open applications to > the gdebi-developers launchpad team since at least 2020, > and that development continues under collab-maint > (spelled as an NMU, but same difference), > we're just an ITS and updating Vcs-* fields away from making this official. > > gdebi came up on BOTD today and I fixed a few bugs. > I'll open an ITS and rebase my bugs on top of the new git repository. > The issue of the nominal maintainer post-salvage remains. >
Hi! Yeah, I have done some work on it and closed some bugs - and the migration to the git repository - I wouldn't mind at all if that work was being used in any way, but since I did that I discovered that Mint (which I believe was driving the work behind gdebi at least to some extent) will go another way. (see "Maintaining better APT libraries and utilities" on https://blog.linuxmint.com/?p=4740 So, I doubt that they will use gdebi, and then I guess that Debian will follow that. But I don't know for sure of course, but one thing is clear to me at least - Mint will use other tools than gdebi. So before doing more work on this I would like to see which way those groups go, and don't waste more of my time on tools that won't get any usage anyway. More info in the two RFS's for the Mint tools Captain and aptkit which seems to be straight replacements of gdebi: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081743 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081742 /Andreas [email protected] [email protected]
