Re: [Tails-dev] Maintaining I2P

[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? And thus, that
the code used to generate that package is available? That might be
helpful for Alexandre I guess.

Cheers!
u.
___
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.

Re: [Tails-dev] Maintaining I2P

[Alexandre Trottier]

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 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.

Re: [Tails-dev] Maintaining I2P

[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!

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.

Re: [Tails-dev] Maintaining I2P

[anonym]

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.

Re: [Tails-dev] Can't build tails, not enough ram?

[anonym]

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:
> 
> austin@debian-laptop:~/src/tails$ export TAILS_BUILD_OPTIONS=noram
> 
> austin@debian-laptop:~/src/tails$ rake build
> rake aborted!
> VagrantCommandError: 'vagrant ["status"]' command failed: 1
> /home/austin/src/tails/Rakefile:61:in `capture_vagrant'
> /home/austin/src/tails/Rakefile:84:in `vm_state'
> /home/austin/src/tails/Rakefile:117:in `enough_free_memory_for_ram_build?'
> /home/austin/src/tails/Rakefile:145:in `block in '
> Tasks: TOP => build => parse_build_options
> (See full trace by running task with --trace)

Weird! What happens if you run:

   (cd vagrant && vagrant status)

Also, have you made sure that up-to-date packages of vagrant and 
vagrant-libvirt are installed? (I know some people have had APT pinnings and 
stuff that has kept them on old, unsupported versions.)

I'd also be interested if one of our development branches, where we've reworked 
a lot how Vagrant works, improves the situation; can you please checkout the 
wip/11972-use-vagrant-in-jenkins Git branch and try to build? You might have to 
clear vagrant/.vagrant before you try starting this new VM.

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.

Re: [Tails-dev] Experimenting with Tails, preferred workflow ?

[anonym]

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 filesystem shares to make your 
>> Tails sources available inside the Tails guest, then you just symlink the 
>> source files to the correct places. This allows for rapidly testing your 
>> changes, but won't in all situations (e.g. stuff happening during early 
>> boot). YMMV.
> 
> Nice, thanks for sharing tips :)
> 
>>> Now I just read a bit about aufs and I understand better how it works
>> It's a cool technology, but I don't think it's really needed. :)
> 
> Not sure to follow you. It IS actually used, that's what `mount` and
> `/etc/fstab` show me. If I understand properly, it's thanks to aufs that
> the rootfs is writable (in RAM).

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 means, read up more, but probably about overlayfs instead, since 
that is what we are moving towards slowly (help needed!):

https://labs.riseup.net/code/issues/8415

> BTW I stumbled on quite a nice article about the different filesystem
> strategies used in different LiveCDs (Debian, Ubuntu, Fedora), here the
> link in case you're interested:
> 
> https://major.io/2014/07/29/adventures-in-live-booting-linux-distributions/

Cool! It's worth noting that overlayfs has been merged into the mainline Linux 
kernel since then, and this is a huge motivation for us to migrate from aufs to 
it instead.

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.

Re: [Tails-dev] Screen Reader issue tails 3.0 beta 2

[intrigeri]

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
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Release schedule for Tails 2.12

[anonym]

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:

* 2017-04-06:
   - Feature Freeze: All feature branches targeting Tails 2.12 should
 be merged into the `devel` branch by noon, CET. I'm open to make
 exceptions if you can be online and responsive during that
 afternoon, but ask me first!
   - Build and upload Tails 2.12~rc1.
   - Start testing Tails 2.12~rc1 during late CET if building the image
 went smoothly.

* 2017-04-07:
   - Finish testing Tails 2.12~rc1 by the afternoon, CET.
   - Release Tails 2.12~rc1.

* 2017-04-17:
  - All branches targeting Tails 2.12 *must* be merged into the
`testing` branch by noon, CET.
  - The upcoming Tor Browser is hopefully out so we can import it.
  - Build and upload Tails 2.12 ISO image and IUKs.
  - Hopefully start testing Tails 2.12.

* 2017-04-18:
  - Finish testing Tails 2.12 by the afternoon, CET.
  - Release Tails 2.12 during late CET.

Testers, please let me know:

* if you are available on 2017-04-06, late CET

* if you are available on 2017-04-07, morning to afternoon, CET.

* if you are available on 2017-04-17, late CET

* if you are available on 2017-04-18, morning to afternoon, CET.

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.

Re: [Tails-dev] Experimenting with Tails, preferred workflow ?

[Adam Burns]

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 means, read up more, but probably about 
> overlayfs instead, since that is what we are moving towards slowly (help 
> needed!):

Ping. I've been scripting Raspbian builds (albeit in hacky unorthodox
ways) to support overlayfs with overlayctl. Layers of RO and one or more
RW seem to work well (whether on RAM or overlay persistent partitions).






signature.asc
Description: OpenPGP digital signature
___
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.

Re: [Tails-dev] Maintaining I2P question

[Alexandre Trottier]

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 works.
>
> Well, not exactly: there is also integration development + maintenance
> work, to make I2P work fine in the context of Tails. So there's Debian
> packaging, system integration work, and (as usual in Tails)
> communication with our technical writers and UX team to ensure the
> integration is up to our standards :)
>
> I'll let anonym follow up, since I think he has the list of the
> top-priority issues we want to see fixed in I2P integration before
> it's reintroduced into Tails.
>
> Cheers,
> --
> intrigeri
> ___
> 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.

Re: [Tails-dev] Maintaining I2P question

[intrigeri]

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 Debian
packaging, system integration work, and (as usual in Tails)
communication with our technical writers and UX team to ensure the
integration is up to our standards :)

I'll let anonym follow up, since I think he has the list of the
top-priority issues we want to see fixed in I2P integration before
it's reintroduced into Tails.

Cheers,
-- 
intrigeri
___
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.

Re: [Tails-dev] Maintaining I2P

[intrigeri]

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 so I'm not
> sure where to start.

For the Debian packaging aspect, I recommend starting with:
https://www.debian.org/doc/manuals/packaging-tutorial/

For the Tails integration aspect, the best entry point we currently
have is: https://tails.boum.org/contribute/how/code/

Cheers,
-- 
intrigeri
___
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.

Re: [Tails-dev] Maintaining I2P

[Alexandre Trottier]

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 this is something that I could do.
>
> Great!
>
> > I have never had to maintain a package for a distribution before so I'm
> not
> > sure where to start.
>
> For the Debian packaging aspect, I recommend starting with:
> https://www.debian.org/doc/manuals/packaging-tutorial/
>
> For the Tails integration aspect, the best entry point we currently
> have is: https://tails.boum.org/contribute/how/code/
>
> Cheers,
> --
> intrigeri
> ___
> 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.