Re: [Tails-dev] On re-entry of I2P into Tails

Delete this message

Reply to this message
Author: Masayuki Hatta
To: tails-dev
Old-Topics: Re: [Tails-dev] On re-entry of I2P into Tails
Subject: Re: [Tails-dev] On re-entry of I2P into Tails

Finally, I began some work on reintroducing I2P into Tails. Sorry for

I could fork the Tails GitLab repo, checkout a new Git branch
build Tails ISO, and run it on VirtualBox. So far so good.

Because the official I2P repo only provides https transport (such as
"deb sid main") and Tails doesn't support it, I
simply put I2P *.deb files into config/chroot_local-packages for now.
With adding "i2p" to tails-common.list, I run "rake build", but it
stops with esoteric errors such as:

gpg: WARNING: unsafe permissions on homedir '/root/.gnupg'
gpg: keybox '/root/.gnupg/pubring.kbx' created
gpg: agent_genkey failed: Inappropriate ioctl for device
gpg: key generation failed: Inappropriate ioctl for device
cp: cannot create regular file 'cache/': Not a directory
P: Begin unmounting filesystems...

How can I use chroot_local-packages?

Best regards,

2018年8月15日(水) 14:55 intrigeri <intrigeri@???>:
> Masayuki Hatta:
> > I'm still a bit confused. The second command gives me something like:
> [...]
> > I guess "git push -u origin" might fix this, is this correct?
> Yes.
> > Also, I'm not sure how I can sync my local (topic) branch with the
> > upstream (the original Tails repo, not my forked one) devel branch.
> > Does "git fetch upstream" in the topic branch do the trick?
> After git fetch you'll need to merge recent changes from
> upstream/devel into your topic branch:
> git checkout $topic_branch && \
> git fetch upstream && \
> git merge upstream/devel
> :)
> Cheers,
> --
> intrigeri

Masayuki Hatta
Associate Professor, Faculty of Economics and Management, Surugadai
University, Japan

mhatta@??? / mhatta@??? / mhatta@??? /