Hi all, First off, sorry for the large CC list, but it seems in order to try to collect all the efforts here into one and put this into shape. This ITP is blocking the entry of toxcore in Debian, and I think that's a shame... We should already have this in Debian now! Here are the different efforts that has been reported here: On Sun, Feb 23, 2014 at 12:19:24PM +0100, Bartosz Feński wrote: > Package: wnpp Bartosz, do you have anything published here? On Fri, Jul 04, 2014 at 05:28:11PM -0500, Mike Dupont wrote: > I started on packaging today > https://github.com/h4ck3rm1k3/toxcore Mike, did you look at the work Gaffa did? On Mon, Oct 20, 2014 at 11:19:31AM -0400, Alexandre Viau wrote: > I intend to create a repository on collab-maint. It will be using the > gbp recommended layout. Was that repository created? On Tue, Nov 25, 2014 at 03:56:21PM +0100, gaffa wrote: > The packages are available on mentors.debian.net[1]. > > https://mentors.debian.net/packages/uploader/gaffa%40folkemagt.dk That package is gone (understandably), is there another copy somewhere? It seems to me, at this point, that someone should take the work Mike did, merge this with gaffa's, and push this on collab-maint, or *somewhere*! Also you should consider examining the work that was done upstream already; a Debian package archive is available here: https://pkg.tox.chat once that is all merged, then gaffa or anyone can find a mentor to upload this, i'm happy to volunteer for that part. On Thu, Jun 11, 2015 at 05:27:36PM +0200, Tzafrir Cohen wrote: > Right now it seems that the software is changing too fast and should not > go to Unstable (though may go into Experimental). > > However Upstream's policy regarding ABI/API stability (or lack thereof) > is not promising: > > https://github.com/irungentoo/toxcore/issues/1353#issuecomment-104950787 as for this well, we'll just have to deal with this if we want it in debian. i'd suggest a version number like "0~YYYMMDD.gitXXXXXXX" for now, until upstream figures out that release engineering thing (which, yes, is scary). but that shouldn't keep this from hitting unstable. at worse, file an RC bug to keep it from migrating to testing, with the reasons (e.g. "upstream doesn't want to", "changes to fast", or whatever). that way it's clear why it's not in a stable release, yet people can try it out. thanks! a.
Attachment:
signature.asc
Description: Digital signature