Hi! Until recently, some other commitments prevented me from working on Tails (sorry for 8 months delay since 34C3!), but now I'd like to resume my effort to re-integrate I2P into Tails.
I got two questions -- both must be quite basic and stupid, but I appreciate if you could tell me or point me to the relevant references. Thanks! 1. Git(Lab) work flow I made a GitLab account, forked Tails/tails repo. Now I made Tails/tails as upstream and sync'd them well. $ git clone [email protected]:masayukihatta/tails.git $ git remote add upstream [email protected]:Tails/tails.git $ git fetch upstream; git merge upstream/master Then, I think I should work on devel branch. The question is, how to do? I know there are tons of documents about it, but I'm not sure what to do (I'm using Git/GitHub regularly, but still I should say quite a newbie...) I do $ git checkout --track upstream/devel But git fetch or such doesn't really follow the upstream changes. 2. Testing environment I could build the current Tails and produce ISO image. I can run it on USB sticks. It's okay, but a bit tiresome. Is there an established good practice to run/test Tails on VM or such? Best regards, MH 2017年11月28日(火) 0:47 intrigeri <[email protected]>: > > Hi, > > Masayuki Hatta: > > I am a Debian Developer. > > Another Debian (+ Tails) developer speaking. Small world, uh :) > > > Recently I uploaded I2P for Debian, […] > > I've noticed this and I'm very grateful someone eventually tackled > this. > > > I understand the previous (unofficial) Debian maintainer suddenly > > disappeared last year, and as a result I2P had been removed, not a > > part of Tails anymore. But I'd like to see I2P in Tails again since > > Tails is an important and major platform for privacy-savvy users. > > > I think I2P itself has been steadily improved, and I have a good > > relationship with the I2P upstream. Also my packages are in a > > reasonably good quality (well, at least lintian-free). I'll take care > > of those packages as much as I'm involved with Debian. > > By the way, what's your plan regarding stable releases, starting with > Buster? (Last time I checked, I2P had no maintenance/LTS release > branch so I don't know how severe bugs, network compatibility updates, > and security issues can easily be fixed in a frozen Debian stable.) > > > So what can I do to make I2P a part of Tails again? I know Debian > > things quite well, but I should say I don't know at all about Tails. > > But I can learn ;-) I appreciate if you would kindly tell me the next > > step. > > When we've removed I2P we've tried to document this on > https://labs.riseup.net/code/issues/12264. > > Regarding how to contribute to Tails, see > https://tails.boum.org/contribute/how/code/ > > Cheers, > -- > intrigeri -- Masayuki Hatta Associate Professor, Faculty of Economics and Management, Surugadai University, Japan http://about.me/mhatta [email protected] / [email protected] / [email protected] / [email protected] _______________________________________________ Tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
