I'll spend the next 1-2 weeks getting familiar with the package maintenance
process.

Any and all information/documentation would be great.
Thanks!

On Mar 21, 2017 11:57 AM, "anonym" <ano...@riseup.net> wrote:

> u:
> > Hi,
> >
> > anonym:
> >> Alexandre Trottier:
> >>> Sounds good I'll start reading
> >>
> >> I have written the specific requirements here:
> https://labs.riseup.net/code/issues/12264
> >>
> >> Note that what we need in Tails doesn't include Debian packaging,
> although someone taking over that part from zzz (the I2P Project Manager,
> who is not so happy about having to do it at the moment) would be great!
> Let us know what you think!
> >
> > Does that mean that there is a package already somewhere?
>
> Yes, see: https://geti2p.net/en/download/debian#debian
>
> > And thus, that the code used to generate that package is available?
>
> I'm sure zzz would make this and any documentation available on request if
> it isn't already. The I2P sources has a `debian` directory:
>
>     https://github.com/i2p/i2p.i2p/blob/master/debian/changelog
>
> but the changelog hasn't been updated for 5 months, since version 0.9.27.
> I *just* stumbled upon zzz's twitter and found some tweets indicating that
> someone else already might have taken over the Debian packaging from zzz:
>
>     https://twitter.com/echeloni2p/status/842030392525914117
>     https://twitter.com/echeloni2p/status/842012052260589568
>
> Any way, I want to stress the fact that whoever works on integrating I2P
> into Tails does *not* have to be the I2P Debian package maintainer as well.
>
> Cheers!
>
> _______________________________________________
> Tails-dev mailing list
> Tails-dev@boum.org
> https://mailman.boum.org/listinfo/tails-dev
> To unsubscribe from this list, send an empty email to
> tails-dev-unsubscr...@boum.org.
_______________________________________________
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Reply via email to