Re: [Tails-dev] How to build tails for testing purposes?
Sorry, it is me again. There is so much to learn. I am now able· to get clear
with these
vagrant, rake and virsh stuff. That is a great step and I am happy, I can help
myself now.
But I believe, I now stumbled over a new issue with broken package. For me it
looks like
some settings are wrong in the pre-image file. As far as I understood, the
crash is in the
step, where the basic image is build, or say, filled with the packages.
This is the output, just at the basic installation step:
- snip --
I: Configuring gnupg...
I: Configuring tasksel-data...
I: Configuring tasksel...
I: Configuring libc-bin...
I: Configuring systemd...
I: Base system installed successfully.
P: Begin caching bootstrap stage...
P: Begin unmounting filesystems...
P: Setting up cleanup function
P: Begin caching chroot stage...
P: Begin mounting /dev/pts...
P: Begin mounting /proc...
P: Begin mounting /sys...
P: Configuring file /etc/debian_chroot
P: Configuring file /sbin/start-stop-daemon
P: Configuring file /usr/sbin/policy-rc.d
P: Configuring file /usr/sbin/initctl
P: Configuring file /etc/hosts
P: Configuring file /etc/resolv.conf
P: Configuring file /etc/hostname
P: Configuring file /bin/hostname
P: Configuring file /etc/apt/apt.conf
P: Configuring file /etc/apt/sources.list
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...
real4m14.338s
user1m14.028s
sys 0m19.934s
+ kill -9 10276
+ cleanup
+ [ -n /tmp/tails-build.Tj3YvUfU ]
+ cd /
+ remove_build_dirs
+ + tac
old_build_dirs
+ mount
+ perl -ni -E say $mountpoint if (($mountpoint) = ($_ =~
m{^(?:tmpfs|devpts-live|proc-
live|sysfs-live) on (/tmp/tai
ls-build(?:-tmpfs)?\.[/[:alnum:]]+)}))
-i used with no filenames on the command line, reading from STDIN.
+ sudo rm -rf /tmp/tails-build.Tj3YvUfU
No build artifacts were found!
- snap --
Ok, the directory here called /root is not the /root of my system, so it must
be in the
imagefile, that is mounted /dev/loop (I suppose so, am I wrong?).
What I do not understand, is that ioctl, but everything is looking for me as a
problem with
rights. However, I am building as root, so I should have all the rights, I
need.
I am sure, I have missed something.
For the explanation, I am building on an extra ssd, which is mounted
to /space, but this worked on building kali-linux. So this should work here,
too. Especially
at this step of building.
Any idea, what I am doing wrong? Or is this just a bug???
Thanks for being so patient.
Best
Hans
signature.asc
Description: This is a digitally signed message part.
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] How to build tails for testing purposes?
Hans: Yeah, yeah, sigh, it's me again Now I am running into a new issue, but I believe, something external happened. For learning I removed all the downloaded things completely. Then I deleted also ~/.vagrant.d/ in my home and started from the beginning with a new git clone and a new, but unchanged build. The proper way to reset and start over is to run: rake clean_all But now there is a new issue, related to vagrant. Please take a look at the last output. snip - /tmp.debootstrap-gnupg-i9oekjha *==> box: Box file was not detected as metadata. Adding it directly...* *==> box: Adding box 'tails-builder-amd64-buster-20210710-de2318f3ae' (v0) for provider: * box: Unpacking necessary files from: file:///space/tails-linux/tails-amd64/tails/tails-builder-amd64-buster-202 10710-de2318f3ae.box *==> box: Successfully added box 'tails-builder-amd64-buster-20210710-de2318f3ae' (v0) for 'libvirt'!* Bringing machine 'default' up with 'libvirt' provider... *==> default: Creating image (snapshot of base box volume).* Volume for domain is already created. Please run 'vagrant destroy' first. The basebox in ~/.vagrant.d are unpacked and the virtual machine images imported by libvirt and stored somewhere else, hence the "already created" above. List images with: virsh -c qemu:///system vol-list default Detele with: virsh -c qemu:///system vol-delete --pool default VOLUME_NAME So I suspect you will fix your issue with: virsh -c qemu:///system vol-delete --pool default tails-builder-amd64-buster-20210710-de2318f3ae_vagrant_box_image_0.img I wasa not lazy, and searched the web. vagrant destroy does not work, and vagrant global-status is telling me, there is no session running. I believe you! Our documentation about this is a bit lacking, and naturally we'd be thrilled to receive your patches improving them! :) OTOH, I don't think there was any good reason for you to start over like you did. Good luck! ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] How to build tails for testing purposes?
Yeah, yeah, sigh, it's me again
Now I am running into a new issue, but I believe, something external happened.
For learning I removed all the downloaded things completely. Then I deleted
also
~/.vagrant.d/ in my home and started from the beginning with a new git clone
and a new,
but unchanged build.
But now there is a new issue, related to vagrant. Please take a look at the
last output.
snip -
/tmp.debootstrap-gnupg-i9oekjha
*==> box: Box file was not detected as metadata. Adding it directly...*
*==> box: Adding box 'tails-builder-amd64-buster-20210710-de2318f3ae' (v0) for
provider: *
box: Unpacking necessary files from:
file:///space/tails-linux/tails-amd64/tails/tails-
builder-amd64-buster-202
10710-de2318f3ae.box *==> box: Successfully added box 'tails-builder-amd64-
buster-20210710-de2318f3ae' (v0) for 'libvirt'!*
Bringing machine 'default' up with 'libvirt' provider... *==> default: Creating
image
(snapshot of base box volume).*
Volume for domain is already created. Please run 'vagrant destroy' first.
rake aborted!
VagrantCommandError: 'vagrant ["up", "--provision"]' command failed with exit
status 1
/space/tails-linux/tails-amd64/tails/Rakefile:113:in `rescue in run_vagrant'
/space/tails-linux/tails-amd64/tails/Rakefile:110:in `run_vagrant'
/space/tails-linux/tails-amd64/tails/Rakefile:703:in `block (2 levels) in '
/usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in `'
Caused by:
CommandError: command ["vagrant", "up", "--provision", {:chdir=>"./vagrant"}]
failed
with exit status 1
/space/tails-linux/tails-amd64/tails/Rakefile:78:in `run_command'
/space/tails-linux/tails-amd64/tails/Rakefile:111:in `run_vagrant'
/space/tails-linux/tails-amd64/tails/Rakefile:703:in `block (2 levels) in '
/usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in `'
Tasks: TOP => build => vm:up
(See full trace by running task with --trace) *==> default: Domain is not
created. Please
run `vagrant up` first.*
snap
I wasa not lazy, and searched the web. vagrant destroy does not work, and
vagrant
global-status is telling me, there is no session running.
And I repeat: I did everything from scratch, reinstalling vagrant and its
dependencies,
reinstalling the git-tree and so on.
As everything worked before, and I made no changes, the only conclusion is,
that
something external must have changed. Something, I have no influence on.
If I am wrong, please apologize, any help is appreceated.
Best regards and happy hacking.
Hans
signature.asc
Description: This is a digitally signed message part.
___
Tails-dev mailing list
Tails-dev@boum.org
https://www.autistici.org/mailman/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] How to build tails for testing purposes?
Hans: Am Dienstag, 20. Juli 2021, 13:49:47 CEST schrieb anonym: In your previous email I see that you did some changes inside the tails folder without committing them to Git. Tails will only include changes that are in Git, and will refuse to build when you have uncommitted changes -- the ignorechanges option is just for disabling that check (only recommended if you know what you are doing), and proceeds to build without those uncommitted changes. If you are not too familiar with Git, you can try this (at the root of your tails folder) to add all files to Git: git add . git commit -m "Did some stuff" And then just `rake build` as usual. Cheers! Ok, I could do this. But does this not kill the original stuff? Nothing is ever lost when using Git. :) It keeps the history of how files have changed. My purpose is, to build my own tails version with XFCE and kali-undercover and without gnome. Just to make it as small as possible. Understood. That is compatible with the instructions I gave you above. However, removing Gnome is likely very hard. I suggest you install XFCE in addition to Gnome to save you tons of work (potentially weeks, I'd guess). Are saving ~100 megabytes really worth it? :) If I commit my personal changes to git, as you requesting, then (please correct me, if I am wrong) my changes will change the sources in github, what is the last thing I want to do. Don't worry, your local changes are not published anywhere by default (that requires the `git push` command). And you do not have permission to publish changed on Tails' GitLab any way. :) I still do not even know, if this, what I want to do, is really working. At the moment I am trying things, step by step. And I want to be sure, these things are only done on my own systems. This must be confirmed. That's awesome! "Try, fail, repeat" is a surefire recipe for learning! :) If you didn't already, have a look at HACKING.mdwn for some quick explanations of how to modify Tails! Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] How to build tails for testing purposes?
Hans: If I commit my personal changes to git, as you requesting, then (please correct me, if I am wrong) my changes will change the sources in github, what is the last thing I want to do. I still do not even know, if this, what I want to do, is really working. At the moment I am trying things, step by step. And I want to be sure, these things are only done on my own systems. This must be confirmed. sure! there is no way you can accidentally change Tails' sources like this. so feel free to experiment and don't worry about it :) -- boyska ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] How to build tails for testing purposes?
Am Dienstag, 20. Juli 2021, 13:49:47 CEST schrieb anonym: > In your previous email I see that you did some changes inside the tails > folder without committing them to Git. Tails will only include changes that > are in Git, and will refuse to build when you have uncommitted changes -- > the ignorechanges option is just for disabling that check (only recommended > if you know what you are doing), and proceeds to build without those > uncommitted changes. > > If you are not too familiar with Git, you can try this (at the root of your > tails folder) to add all files to Git: > > git add . > git commit -m "Did some stuff" > > And then just `rake build` as usual. > > Cheers! Ok, I could do this. But does this not kill the original stuff? My purpose is, to build my own tails version with XFCE and kali-undercover and without gnome. Just to make it as small as possible. If I commit my personal changes to git, as you requesting, then (please correct me, if I am wrong) my changes will change the sources in github, what is the last thing I want to do. I still do not even know, if this, what I want to do, is really working. At the moment I am trying things, step by step. And I want to be sure, these things are only done on my own systems. This must be confirmed. Best Hans signature.asc Description: This is a digitally signed message part. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] How to build tails for testing purposes?
Hans: Additionally the deb-package, I put below ~/chroot_local-packages/ is not going to be installed (maybe, because XFCE is not installed, as kali-undercover.deb needs got XFCE dependencies). The chroot_local-packages feature has frequently been broken, but I suspect there is another problem... Before build, I started export TAILS_BUILD_OPTIONS="ignorechanges" but got no success. My changes are ignored. I also tried In your previous email I see that you did some changes inside the tails folder without committing them to Git. Tails will only include changes that are in Git, and will refuse to build when you have uncommitted changes -- the ignorechanges option is just for disabling that check (only recommended if you know what you are doing), and proceeds to build without those uncommitted changes. If you are not too familiar with Git, you can try this (at the root of your tails folder) to add all files to Git: git add . git commit -m "Did some stuff" And then just `rake build` as usual. Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] How to build tails for testing purposes?
Sadly this does not work. Although it is now building, my changes are ignored. So it does install gnome again although it is commented out in tails-common-list, and it did not install XFCE, which I put into this file. Additionally the deb-package, I put below ~/chroot_local-packages/ is not going to be installed (maybe, because XFCE is not installed, as kali-undercover.deb needs got XFCE dependencies). Before build, I started export TAILS_BUILD_OPTIONS="ignorechanges" but got no success. My changes are ignored. I also tried export TAILS_BUILD_OPTIONS="ignorechanges nomergebasebranch rescue keeprunning" but again got no success. Same result as before. What do I do wrong? Is there anything I have to do, so that my downloaded gittree accepts and recognizes my changes? I do not understand, how the build is working. The doc says, it is using live-build from debian, so it should work similar to it and look into the configuration files (also those, I changed), but obviously, it is looking somewhere else. Thanks for any help. Best reagrds Hans > > > As the output tells you, you need to set TAILS_BUILD_OPTIONS: > > > > signature.asc Description: This is a digitally signed message part. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] How to build tails for testing purposes?
Ah, ok, this seem to work. I read this message, but understoood it in that way, that this command would ignore my changes. Building a tails live system is made in another way, like I know, so I am not very experienced with it. In the past I built my life-systems mostly with live-build (or ./build.sh when building my own optimized kali-linux livesystem). Thanks for the hint. Best Hans > As the output tells you, you need to set TAILS_BUILD_OPTIONS: > > export TAILS_BUILD_OPTIONS="ignorechanges" signature.asc Description: This is a digitally signed message part. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] How to build tails for testing purposes?
On Mon, Jul 19, 2021 at 10:04 AM Hans wrote: > > Hi folks, > > > I am experiencing with building my own version of tails, but got stuck. > > > I downloaded the git, installed all needed packages on my debian system, made > my changes in ~/tails/config/ and then started > > > rake build && rake vm:halt > > > But this did not work. I got the message: > > > snip > > > You have uncommitted changes in the Git repository. Due to limitations > of the build system, you need to commit them before building Tails: > M config/chroot_local-packageslists/tails-common.list > ?? config/chroot_local-packages/kali-undercover_2021.1.2_all.deb > ?? vmdb2.log > > > If you don't care about those changes and want to build Tails nonetheless, > please add `ignorechanges` to the TAILS_BUILD_OPTIONS environment > variable. > > Uncommitted changes. Aborting. > > --- snap - > > > However, I do not want to commit anything yet, because I do not want to mess > up with your git-sources! > > > How can I build just for me, without interfering your tails-git? > > > Changes I made: > > > 1. edited ~/tails/config/chroot_local-packageslists/tails-common.list > > > 2. added kali-undercover*.deb into ~/tails/config/chroot_local-packages/ > > > If this is working, I will try to optimize things (maybe also build for > 32-Bit). Maybe I will then ask for more help, but first let me try, if I can > get it managed to build tails running with XFCE instead of Gnome and the > possibility, to look XFCE like Windows10. As the output tells you, you need to set TAILS_BUILD_OPTIONS: export TAILS_BUILD_OPTIONS="ignorechanges" -- -Austin GPG: 267B CC1F 053F 0749 (expires 2024/02/17) ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] How to build tails for testing purposes?
Hi folks, I am experiencing with building my own version of tails, but got stuck. I downloaded the git, installed all needed packages on my debian system, made my changes in ~/tails/config/ and then started rake build && rake vm:halt But this did not work. I got the message: snip You have uncommitted changes in the Git repository. Due to limitations of the build system, you need to commit them before building Tails: M config/chroot_local-packageslists/tails-common.list ?? config/chroot_local-packages/kali-undercover_2021.1.2_all.deb ?? vmdb2.log If you don't care about those changes and want to build Tails nonetheless, please add `ignorechanges` to the TAILS_BUILD_OPTIONS environment variable. Uncommitted changes. Aborting. --- snap - However, I do not want to commit anything yet, because I do not want to mess up with your git-sources! How can I build just for me, without interfering your tails-git? Changes I made: 1. edited ~/tails/config/chroot_local-packageslists/tails-common.list 2. added kali-undercover*.deb into ~/tails/config/chroot_local-packages/ If this is working, I will try to optimize things (maybe also build for 32-Bit). Maybe I will then ask for more help, but first let me try, if I can get it managed to build tails running with XFCE instead of Gnome and the possibility, to look XFCE like Windows10. Thanks for any hints. Best regards Hans signature.asc Description: This is a digitally signed message part. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
