Hi Clement, > I'm working on wahay, a decentralized conference call solution using Tor > (see ITP #962953), as it'd be useful to have in Tails, and also in Debian. Nice, cool to see someone working on that :) > It happens one of the deps is already in Debian, but with a different > import path. Upstream has apparently moved: > > github.com/coyim/gotk3adapter (used to be github.com/twstrike/gotk3adapter). > > Apparently, upstream devs (twstrike) decided to move coyim and its deps > to a dedicated github organisation: https://github.com/coyim/. Yes, that has all been moved. I was considering migrating all of that earlier many months ago, but ran into various sorts of building issues with the GTK version in Debian, so I didn’t make much progress. Since I am no longer an active user of CoyIM, I must admit I lost interest there. > Since I need gotk3adapter, I propose we update coyim (which is an old > version) and its rdeps, instead of creating a new package (it's a move, > not a fork). I guess that makes sense. > Thoughts? Objections? Proposals for help? ;) Do you think that the new import paths (“twstrike” -> “coyim”) require that the new dependencies (which are more than before, IIRC, as I think more code was split out into separate GitHub projects) are also packaged as new Debian packages. AFAIK the package name should reflect the import path? Or do you think virtual packages with Provides relationships would suffice? I don’t remember if there were any API changes in the meantime... > Sascha, I CC-ed since you're uploader for coyim, would you take care of > this or do you need me to do it? TBH, I was seriously considering “orphaning” CoyIM (i.e. asking for any parties in the Go Packaging Team or Privacy Tools Team that might be interested in taking over) in the near future anyway as my priorities have moved quite a bit. I would be very happy for you to move in — thanks! Best regards Sascha
Attachment:
signature.asc
Description: Message signed with OpenPGP