Hi, I still can't find out how to use chroot_local-packages, but anyway I can use the official I2P APT repo now. deb.i2p2.de only provides https (https:://deb.i2p2.de/), but deb.i2p2.no still provides http transport (both are the official repos).
Now in my repo (https://gitlab.com/masayukihatta/tails/commits/feature/12264-reintroduce-i2p), I added I2P tentatively. It seems that the build system can find, download and install I2P packages, but somehow it fails halfway (squashfs?). I tried to read the log from "rake --trace build", but can't find out the reason why it fails. I appreciate if you could give me any hints. Logs from the failed and successful build (without I2P) are available on Tails Issue Tracker (https://redmine.tails.boum.org/code/issues/12264#note-22). Best regards, MH 2018年12月22日(土) 13:51 Masayuki Hatta <[email protected]>: > > Hi, > > Finally, I began some work on reintroducing I2P into Tails. Sorry for > procrastination... > > I could fork the Tails GitLab repo, checkout a new Git branch > (https://gitlab.com/masayukihatta/tails/tree/feature/12264-reintroduce-i2p), > build Tails ISO, and run it on VirtualBox. So far so good. > > Because the official I2P repo only provides https transport (such as > "deb https://deb.i2p2.de/ 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: > > (snip) > 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... > (snip) > > How can I use chroot_local-packages? > > Best regards, > MH > > 2018年8月15日(水) 14:55 intrigeri <[email protected]>: > > > > 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 > > http://about.me/mhatta > > [email protected] / [email protected] / [email protected] / > [email protected] -- 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://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
