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
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" wrote:
> u:
> > Hi,
> >
> > anonym:
> >> Alexandre Trottier:
> >>> Sounds good I'll start
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
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
Austin English:
> Hi all,
>
> It's been a while since I've built tails, been busy with other
> projects.. Anyway, I've done a git pull, git clean -fxd (to clear out
> .vagrant), and removed ~/.vagrant.d. I then tried to build with noram,
> since my laptop is low on free memory, and I get:
>
>
Arnaud:
> anonym:
>> Let me add one, which is a special case of intrigeri's last point:
>>
>> * start Tails and "symlink" the relevant/changed files from your Tails
>> source tree into the correct places in the filesystem of a running Tails
>> session. So first you use sshfs or libvirt
Yphone:
> Is this nightly build reasonably secure?
Except "it's not been built in a trusted environment", it passes our
automated QA (in the very same untrusted environment).
Cheers,
--
intrigeri
___
Tails-dev mailing list
Tails-dev@boum.org
Hi,
I'll be the release manager for Tails 2.12, which is a major release scheduled
on 2017-04-18. The list of tickets targeting Tails 2.12 can be found here:
https://labs.riseup.net/code/projects/tails/issues?query_id=238
Below you'll find the preliminary release schedule for Tails 2.12:
On 21/03/17 20:15, anonym wrote:
> I just meant that detailed knowledge about aufs is not central to
> understanding Tails and being able to hack on it. :) I think it is enough to
> know the general idea, that we stack filesystems on top of each other. OTOH
> if this area excites you, by all
Thanks for getting back to me.
Looking forward to hearing back
On Mar 21, 2017 8:17 AM, "intrigeri" wrote:
> Hi,
>
> Alexandre Trottier:
> > In order to maintain I2P do all I need to do is build binaries from
> source
> > install onto a test distribution and make sure it
Hi,
Alexandre Trottier:
> In order to maintain I2P do all I need to do is build binaries from source
> install onto a test distribution and make sure it works.
Well, not exactly: there is also integration development + maintenance
work, to make I2P work fine in the context of Tails. So there's
Hi,
Alexandre Trottier:
> Hello,
> I'm interested in maintaining I2P for future releases of tails.
> I'm profficient at python and bash, and do Sys Admin work as a job so I
> feel like this is something that I could do.
Great!
> I have never had to maintain a package for a distribution before
Sounds good I'll start reading
On Mar 21, 2017 8:18 AM, "intrigeri" wrote:
> Hi,
>
> Alexandre Trottier:
> > Hello,
>
> > I'm interested in maintaining I2P for future releases of tails.
> > I'm profficient at python and bash, and do Sys Admin work as a job so I
> > feel like
13 matches
Mail list logo