[prev in list] [next in list] [prev in thread] [next in thread]
List: tails-dev
Subject: Re: [Tails-dev] Maintaining I2P
From: Alexandre Trottier <alextrottier2014 () gmail ! com>
Date: 2017-03-21 19:03:34
Message-ID: CAGp2nH2gNrG4m=0az0xUcwrA1TWbvL31C+bAVD7Tv9N+grQ30Q () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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" <anonym@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-unsubscribe@boum.org.
[Attachment #5 (text/html)]
<div dir="auto">I'll spend the next 1-2 weeks getting familiar with the package \
maintenance process.<div dir="auto"><br></div><div dir="auto">Any and all \
information/documentation would be great.</div><div \
dir="auto">Thanks!</div></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Mar 21, 2017 11:57 AM, "anonym" <<a \
href="mailto:anonym@riseup.net">anonym@riseup.net</a>> wrote:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">u:<br> > Hi,<br>
><br>
> anonym:<br>
>> Alexandre Trottier:<br>
>>> Sounds good I'll start reading<br>
>><br>
>> I have written the specific requirements here: <a \
href="https://labs.riseup.net/code/issues/12264" rel="noreferrer" \
target="_blank">https://labs.riseup.net/code/<wbr>issues/12264</a><br> >><br>
>> 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!<br> ><br>
> Does that mean that there is a package already somewhere?<br>
<br>
Yes, see: <a href="https://geti2p.net/en/download/debian#debian" rel="noreferrer" \
target="_blank">https://geti2p.net/en/<wbr>download/debian#debian</a><br> <br>
> And thus, that the code used to generate that package is available?<br>
<br>
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:<br> <br>
<a href="https://github.com/i2p/i2p.i2p/blob/master/debian/changelog" \
rel="noreferrer" target="_blank">https://github.com/i2p/i2p.<wbr>i2p/blob/master/debian/<wbr>changelog</a><br>
<br>
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:<br> <br>
<a href="https://twitter.com/echeloni2p/status/842030392525914117" \
rel="noreferrer" target="_blank">https://twitter.com/<wbr>echeloni2p/status/<wbr>842030392525914117</a><br>
<a href="https://twitter.com/echeloni2p/status/842012052260589568" rel="noreferrer" \
target="_blank">https://twitter.com/<wbr>echeloni2p/status/<wbr>842012052260589568</a><br>
<br>
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.<br> <br>
Cheers!<br>
<br>
______________________________<wbr>_________________<br>
Tails-dev mailing list<br>
<a href="mailto:Tails-dev@boum.org">Tails-dev@boum.org</a><br>
<a href="https://mailman.boum.org/listinfo/tails-dev" rel="noreferrer" \
target="_blank">https://mailman.boum.org/<wbr>listinfo/tails-dev</a><br> To \
unsubscribe from this list, send an empty email to <a \
href="mailto:Tails-dev-unsubscribe@boum.org">Tails-dev-unsubscribe@boum.org</a><wbr>.</blockquote></div></div>
[Attachment #6 (text/plain)]
_______________________________________________
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-unsubscribe@boum.org.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic