Good Morning, I agree that this is a reasonable course of action. To make sure I understand: should I change this bug to packaging upstream mmsd, or should I close this bug and open a new bug to package upstream mmsd?
I am fine doing either one, but I want to make sure I do the correct one. -- Respectfully, Chris Talbot On Mon, 2021-03-22 at 08:40 +0100, Guido Günther wrote: > Hi Chris, > On Tue, Mar 16, 2021 at 10:01:14AM -0400, Chris Talbot wrote: > > Hello, > > > > I attempted again to contact the upstream developers and did not > > recieve a response. Please see my message from Feb 24, 2021: > > > > https://lists.ofono.org/hyperkitty/list/of...@ofono.org/thread/HFGZCER3I6G52SPSG44OC4KTHDO2ZEC6/ > > > > As such, does it make the most sense to keep this as a fork? As far > > as > > I can tell, the original mmsd has been abandoned. > > > > As another note, I reformatted the repository a bit. "Master" has > > the > > most up to date version of mmsd: > > https://source.puri.sm/kop316/mmsd/ > > > > And the Debian packaging is here: > > https://source.puri.sm/kop316/mmsd/-/tree/debian/modemmanager/latest > > > > I am still keeping the upstream patches seperate, but I am > > wondering > > what the best course of action is at this point. > > I'd go about it like this: > > - package 'upstream' mmsd for Debian and make it go into Debian. This > usually takes some time due to NEW processing > - Once that passed depending on upstream feedback it would be either > the > point in time to take over upsream maintenance of mmsd *or* add > your > patches in `debian/patches`. > > Does that make sense? > Cheers, > -- Guido > > > > > > Thank you! > > > > -- > > Respectfully, > > Chris Talbot > > > > > > _______________________________________________ > > Debian-on-mobile-maintainers mailing list > > debian-on-mobile-maintain...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers > >
