[Tails-dev] Build failed in Jenkins: build_Tails_ISO_devel #763
See https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/763/ -- [...truncated 7054 lines...] Selecting previously unselected package libatk1.0-0:i386. Unpacking libatk1.0-0:i386 (from .../libatk1.0-0_2.4.0-2_i386.deb) ... Selecting previously unselected package libaudit0. Unpacking libaudit0 (from .../libaudit0_1%3a1.7.18-1.1_i386.deb) ... Selecting previously unselected package libcairo-gobject2:i386. Unpacking libcairo-gobject2:i386 (from .../libcairo-gobject2_1.12.2-3_i386.deb) ... Selecting previously unselected package libasound2:i386. Unpacking libasound2:i386 (from .../libasound2_1.0.25-4_i386.deb) ... Selecting previously unselected package libltdl7:i386. Unpacking libltdl7:i386 (from .../libltdl7_2.4.2-1.1_i386.deb) ... Selecting previously unselected package libogg0:i386. Unpacking libogg0:i386 (from .../libogg0_1.3.0-4_i386.deb) ... Selecting previously unselected package libtdb1:i386. Unpacking libtdb1:i386 (from .../libtdb1_1.2.10-2_i386.deb) ... Selecting previously unselected package libvorbis0a:i386. Unpacking libvorbis0a:i386 (from .../libvorbis0a_1.3.2-1.3_i386.deb) ... Selecting previously unselected package libvorbisfile3:i386. Unpacking libvorbisfile3:i386 (from .../libvorbisfile3_1.3.2-1.3_i386.deb) ... Selecting previously unselected package libcanberra0:i386. Unpacking libcanberra0:i386 (from .../libcanberra0_0.28-6_i386.deb) ... Selecting previously unselected package libdconf0:i386. Unpacking libdconf0:i386 (from .../libdconf0_0.12.1-3_i386.deb) ... Selecting previously unselected package dconf-service. Unpacking dconf-service (from .../dconf-service_0.12.1-3_i386.deb) ... Selecting previously unselected package dconf-gsettings-backend:i386. Unpacking dconf-gsettings-backend:i386 (from .../dconf-gsettings-backend_0.12.1-3_i386.deb) ... Selecting previously unselected package libgtk-3-common. Unpacking libgtk-3-common (from .../libgtk-3-common_3.4.2-7_all.deb) ... Selecting previously unselected package libcolord1:i386. Unpacking libcolord1:i386 (from .../libcolord1_0.1.21-1_i386.deb) ... Selecting previously unselected package libxcomposite1:i386. Unpacking libxcomposite1:i386 (from .../libxcomposite1_1%3a0.4.3-2_i386.deb) ... Selecting previously unselected package libxfixes3:i386. Unpacking libxfixes3:i386 (from .../libxfixes3_1%3a5.0-4+deb7u1_i386.deb) ... Selecting previously unselected package libxcursor1:i386. Unpacking libxcursor1:i386 (from .../libxcursor1_1%3a1.1.13-1+deb7u1_i386.deb) ... Selecting previously unselected package libxdamage1:i386. Unpacking libxdamage1:i386 (from .../libxdamage1_1%3a1.1.3-2_i386.deb) ... Selecting previously unselected package libxi6:i386. Unpacking libxi6:i386 (from .../libxi6_2%3a1.6.1-1+deb7u1_i386.deb) ... Selecting previously unselected package libxinerama1:i386. Unpacking libxinerama1:i386 (from .../libxinerama1_2%3a1.1.2-1+deb7u1_i386.deb) ... Selecting previously unselected package libxrandr2:i386. Unpacking libxrandr2:i386 (from .../libxrandr2_2%3a1.3.2-2+deb7u1_i386.deb) ... Selecting previously unselected package shared-mime-info. Unpacking shared-mime-info (from .../shared-mime-info_1.3-1~bpo70+1_i386.deb) ... Selecting previously unselected package libgtk-3-0:i386. Unpacking libgtk-3-0:i386 (from .../libgtk-3-0_3.4.2-7_i386.deb) ... Selecting previously unselected package libcanberra-gtk3-0:i386. Unpacking libcanberra-gtk3-0:i386 (from .../libcanberra-gtk3-0_0.28-6_i386.deb) ... Selecting previously unselected package libdbus-glib-1-2:i386. Unpacking libdbus-glib-1-2:i386 (from .../libdbus-glib-1-2_0.100.2-1_i386.deb) ... Selecting previously unselected package libupower-glib1. Unpacking libupower-glib1 (from .../libupower-glib1_0.9.17-1_i386.deb) ... Selecting previously unselected package libxkbfile1:i386. Unpacking libxkbfile1:i386 (from .../libxkbfile1_1%3a1.0.8-1_i386.deb) ... Selecting previously unselected package x11-common. Unpacking x11-common (from .../x11-common_1%3a7.7+3~deb7u1_all.deb) ... Selecting previously unselected package libice6:i386. Unpacking libice6:i386 (from .../libice6_2%3a1.0.8-2_i386.deb) ... Selecting previously unselected package libsm6:i386. Unpacking libsm6:i386 (from .../libsm6_2%3a1.2.1-2_i386.deb) ... Selecting previously unselected package libxt6:i386. Unpacking libxt6:i386 (from .../libxt6_1%3a1.1.3-1+deb7u1_i386.deb) ... Selecting previously unselected package libxmu6:i386. Unpacking libxmu6:i386 (from .../libxmu6_2%3a1.1.1-1_i386.deb) ... Selecting previously unselected package libxpm4:i386. Unpacking libxpm4:i386 (from .../libxpm4_1%3a3.5.10-1_i386.deb) ... Selecting previously unselected package libxaw7:i386. Unpacking libxaw7:i386 (from .../libxaw7_2%3a1.0.10-2_i386.deb) ... Selecting previously unselected package x11-xkb-utils. Unpacking x11-xkb-utils (from .../x11-xkb-utils_7.7~1_i386.deb) ... Selecting previously unselected package libxklavier16. Unpacking libxklavier16 (from .../libxklavier16_5.2.1-1_i386.deb) ... Selecting
[Tails-dev] Build failed in Jenkins: build_Tails_ISO_devel #762
See https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/762/ -- [...truncated 14575 lines...] 68.88% done, estimate finish Wed Dec 31 14:33:15 2014 69.95% done, estimate finish Wed Dec 31 14:33:15 2014 71.03% done, estimate finish Wed Dec 31 14:33:15 2014 72.10% done, estimate finish Wed Dec 31 14:33:15 2014 73.18% done, estimate finish Wed Dec 31 14:33:15 2014 74.26% done, estimate finish Wed Dec 31 14:33:15 2014 75.33% done, estimate finish Wed Dec 31 14:33:15 2014 76.41% done, estimate finish Wed Dec 31 14:33:15 2014 77.49% done, estimate finish Wed Dec 31 14:33:15 2014 78.56% done, estimate finish Wed Dec 31 14:33:15 2014 79.64% done, estimate finish Wed Dec 31 14:33:15 2014 80.71% done, estimate finish Wed Dec 31 14:33:15 2014 81.79% done, estimate finish Wed Dec 31 14:33:15 2014 82.87% done, estimate finish Wed Dec 31 14:33:15 2014 83.94% done, estimate finish Wed Dec 31 14:33:15 2014 85.02% done, estimate finish Wed Dec 31 14:33:15 2014 86.10% done, estimate finish Wed Dec 31 14:33:15 2014 87.17% done, estimate finish Wed Dec 31 14:33:15 2014 88.25% done, estimate finish Wed Dec 31 14:33:15 2014 89.32% done, estimate finish Wed Dec 31 14:33:15 2014 90.40% done, estimate finish Wed Dec 31 14:33:15 2014 91.48% done, estimate finish Wed Dec 31 14:33:15 2014 92.55% done, estimate finish Wed Dec 31 14:33:15 2014 93.63% done, estimate finish Wed Dec 31 14:33:15 2014 94.71% done, estimate finish Wed Dec 31 14:33:15 2014 95.78% done, estimate finish Wed Dec 31 14:33:15 2014 96.86% done, estimate finish Wed Dec 31 14:33:15 2014 97.93% done, estimate finish Wed Dec 31 14:33:15 2014 99.01% done, estimate finish Wed Dec 31 14:33:15 2014 Total translation table size: 2048 Total rockridge attributes bytes: 11670 Total directory bytes: 30720 Path table size(bytes): 130 Max brk space used 21000 464611 extents written (907 MB) P: Deconfiguring file /etc/hostname P: Deconfiguring file /bin/hostname P: Deconfiguring file /etc/resolv.conf P: Deconfiguring file /etc/hosts P: Deconfiguring file /etc/apt/apt.conf P: Deconfiguring file /usr/sbin/policy-rc.d P: Begin unmounting /sys... P: Deconfiguring file /usr/sbin/initctl P: Begin unmounting /selinux... P: Begin unmounting /proc... P: Begin unmounting /dev/pts... P: Begin unmounting filesystems... P: Setting up cleanup function 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/sources.list OK OK Hit http://ftp.us.debian.org wheezy Release.gpg Hit http://security.debian.org wheezy/updates Release.gpg Hit http://deb.tails.boum.org devel Release.gpg Hit http://deb.torproject.org wheezy Release.gpg Hit http://security.debian.org wheezy/updates Release Hit http://deb.tails.boum.org devel Release Hit http://ftp.us.debian.org experimental Release.gpg Hit http://deb.tails.boum.org devel/main i386 Packages Hit http://deb.torproject.org sid Release.gpg Hit http://security.debian.org wheezy/updates/main i386 Packages Hit http://ftp.us.debian.org unstable Release.gpg Hit http://deb.torproject.org wheezy Release Hit http://security.debian.org wheezy/updates/contrib i386 Packages Hit http://ftp.us.debian.org testing Release.gpg Hit http://deb.torproject.org sid Release Hit http://ftp.us.debian.org wheezy-backports Release.gpg Hit http://security.debian.org wheezy/updates/non-free i386 Packages Hit http://deb.torproject.org wheezy/main i386 Packages Hit http://ftp.us.debian.org wheezy Release Hit http://security.debian.org wheezy/updates/contrib Translation-en Ign http://deb.tails.boum.org devel/main Translation-en Hit http://ftp.us.debian.org experimental Release Hit http://security.debian.org wheezy/updates/main Translation-en Hit http://deb.torproject.org sid/main i386 Packages Hit http://ftp.us.debian.org unstable Release Hit http://security.debian.org wheezy/updates/non-free Translation-en Hit http://ftp.us.debian.org testing Release Hit http://ftp.us.debian.org wheezy-backports Release Hit http://ftp.us.debian.org wheezy/main i386 Packages Hit http://ftp.us.debian.org wheezy/contrib i386 Packages Hit http://ftp.us.debian.org wheezy/non-free i386 Packages Hit http://ftp.us.debian.org wheezy/contrib Translation-en Hit http://ftp.us.debian.org wheezy/main Translation-en Ign http://deb.torproject.org wheezy/main Translation-en Hit http://ftp.us.debian.org wheezy/non-free Translation-en Ign http://deb.torproject.org sid/main Translation-en Hit http://ftp.us.debian.org experimental/main i386 Packages/DiffIndex Hit http://ftp.us.debian.org experimental/main Translation-en/DiffIndex Hit http://ftp.us.debian.org unstable/main i386 Packages/DiffIndex Hit http://ftp.us.debian.org unstable/contrib i386 Packages/DiffIndex Hit http://ftp.us.debian.org unstable/non-free i386 Packages/DiffIndex Hit http://ftp.us.debian.org unstable/contrib Translation-en/DiffIndex Hit http://ftp.us.debian.org unstable/main
Re: [Tails-dev] Windows camouflage for Jessie/GNOME shell
Alan: % Call for participation : port windows camouflage to GNOME 3.14 I added this to a branch. See the current version of the call here: http://git.tails.boum.org/tails/tree/wiki/src/news/windows_camouflage_jessie.mdwn?h=news/windows_camouflage_jessie I was wondering whether we should use a shorter title. We use a big font for titles (that could be fixed) but I'd like to see if we can avoid wrapping titles. That's why I did a731b9f. Feel free to revert it if you don't like it as I'm not 100% convinced either. # Where should you start? Please read https://tails.boum.org/blueprint/update_camouflage_for_jessie/, then write to tails-dev@boum.org. This is a public mailing list: https://mailman.boum.org/listinfo/tails-dev/ Please subscribe! I'm a bit concerned about what will happen once we sent out the call. Hopefully we will have between 5 and 10 answers from random people who will write to the list saying hello, I'm interested in this. What are you going to answer them? Because if we're interested in their past experience on GNOME before we spend time mentoring them, then we might as well ask this upfront. You also silently ignored my concern about money. If giving out money can help us recruiting more qualified people and do less filtering and mentoring, them I'm all for it. But then I'm not sure whether you like the idea of being mentoring someone else who is being paid and I'm not sure how to put it in the announcement in the first place so I'm ok to try without mentioning money at all first. We might as well delay those questions for once the call is passed, but our past experience with the bounty program proved that getting external people to do work for us definitely doesn't come for free (as in free time)! -- sajolida ___ 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] Build failed in Jenkins: build_Tails_ISO_devel #764
See https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/764/
--
Started by timer
Building remotely on isobuilder2 in workspace
https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/ws/
Deleting project workspace... done
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository gitolite@puppet-git.lizard:tails
git init https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/ws/ #
timeout=10
Fetching upstream changes from gitolite@puppet-git.lizard:tails
git --version # timeout=10
git fetch --tags --progress gitolite@puppet-git.lizard:tails
+refs/heads/*:refs/remotes/origin/*
git config remote.origin.url gitolite@puppet-git.lizard:tails # timeout=10
git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* #
timeout=10
git config remote.origin.url gitolite@puppet-git.lizard:tails # timeout=10
Fetching upstream changes from gitolite@puppet-git.lizard:tails
git fetch --tags --progress gitolite@puppet-git.lizard:tails
+refs/heads/*:refs/remotes/origin/*
git rev-parse origin/devel^{commit} # timeout=10
Checking out Revision 090d360b4c46154da01f3286e28205fe63ba459e (origin/devel)
git config core.sparsecheckout # timeout=10
git checkout -f 090d360b4c46154da01f3286e28205fe63ba459e
git rev-list 090d360b4c46154da01f3286e28205fe63ba459e # timeout=10
git tag -a -f -m Jenkins Build #764 jenkins-build_Tails_ISO_devel-764 #
timeout=10
[build_Tails_ISO_devel] $ /bin/sh -xe /tmp/hudson6393819100470413145.sh
+ TAILS_RAM_BUILD=yes TAILS_CLEAN_BUILD=yes TAILS_BOOTSTRAP_CACHE=
http_proxy=http://apt-proxy.lizard:3142 sh -x
./vagrant/provision/assets/build-tails
+ set -e
+ trap cleanup EXIT
+ [ -n https://jenkins.tails.boum.org/ ]
+ ENV_FILE=/etc/jenkins/environment
+ [ -f /etc/jenkins/environment ]
+ [ -r /etc/jenkins/environment ]
+ . /etc/jenkins/environment
+ ARTIFACTS_ROOT_DIR=/srv/www
+ [ -z https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/ws/ ]
+ [ -z /srv/www ]
+ [ -z origin/devel ]
+ [ -z 090d360b4c46154da01f3286e28205fe63ba459e ]
+ REV=devel
+ COMMIT=090d360b4c46154da01f3286e28205fe63ba459e
+ ARTIFACTS_DIR=/srv/www/build_Tails_ISO_devel
+ cd https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/ws/
+ git checkout --force devel
Switched to a new branch 'devel'
Branch devel set up to track remote branch devel from origin.
+ git reset --hard 090d360b4c46154da01f3286e28205fe63ba459e
HEAD is now at 090d360 Merge remote-tracking branch
'origin/feature/6880-torsocks-2' into devel
+ install -m 0755 -d /srv/www/build_Tails_ISO_devel
install: cannot change permissions of `/srv/www/build_Tails_ISO_devel': No such
file or directory
+ cleanup
+ [ -n ]
+ return 0
Build step 'Execute shell' marked build as failure
___
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] Shared screen locking solution for live distributions in Debian
Ed Dixon: Hi, Hi, which project are you from? I have been using the xtrlock package which allows the screen to still be viewed while locked to good effect in classroom situations. It takes the current users password by default. I may be missing something here but as far as I am aware all current Debian screen locking mechanisms fill this need, if installed. I personally would not want a second set of credentials adding a potential vector attached to the user account just to have a separate password for the screen lock. Can you explain more the need for this? In the case of live distributions most of the time there is no user password by default. So if we want to use a password to lock the screen we need to ask for a password at some point. I'd like to avoid introducing yet another password if there is one already (like in the case of Jondo, and sometimes Tails) but otherwise we need at least one. Does that make sense? Note that in the case of Tails, you can configure an administration password at boot time: https://tails.boum.org/doc/first_steps/startup_options/administration_password. I'd like to consider reusing this for screen locking if it is set (and only ask for a screen locking password if there is none), unless someone has security concerns about this. -- sajolida ___ 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] Tails contributors meeting: Saturday January 03
The next Tails contributors meeting is scheduled for: Saturday 03 January #tails-dev on irc.oftc.net 9pm in Paris 8pm in London 3pm in New-York 12am in San Francisco Every one interested in contributing to Tails is welcome. Feel free to propose and prepare discussion topics. Either: - Raise them in this thread so that others can ask details and prepare the discussion too. - Update the blueprint of the agenda: https://tails.boum.org/blueprint/monthly_meeting/ - Make sure that the discussion tickets that you want to treat during the meeting are well detailed on Redmine. If you want to get involved but don't know yet how, please introduce yourself during the meeting, and be sure to tell us what you are interested in. The meeting might not be the most adequate time and place to properly introduce newcomers to the development process, but at least it should be a fine place to know each others, and schedule a better suited event. ___ 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] Lizard services outage
Hi, To prepare Lizard to host its new shiny hardware, it needs to get its kernel upgraded to the Wheezy-backports one to support such new bones. But the upgrade seems to raise troubles in the virtual network firewalling, so expect outages of Lizard's services today while I'm trying to debug it and get it back on the net. bert. ___ 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] Windows camouflage for Jessie/GNOME shell
Hi, On Thu, 01 Jan 2015 13:06:04 + sajolida sajol...@pimienta.org wrote: Alan: % Call for participation : port windows camouflage to GNOME 3.14 I added this to a branch. See the current version of the call here: http://git.tails.boum.org/tails/tree/wiki/src/news/windows_camouflage_jessie.mdwn?h=news/windows_camouflage_jessie Thanks! I was wondering whether we should use a shorter title. We use a big font for titles (that could be fixed) but I'd like to see if we can avoid wrapping titles. That's why I did a731b9f. Feel free to revert it if you don't like it as I'm not 100% convinced either. A shorter title looks fine indeed, but I'm a bit concerned about loosing the call or help idea. What about Help porting Windows camouflage to GNOME 3.14? # Where should you start? Please read https://tails.boum.org/blueprint/update_camouflage_for_jessie/, then write to tails-dev@boum.org. This is a public mailing list: https://mailman.boum.org/listinfo/tails-dev/ Please subscribe! I'm a bit concerned about what will happen once we sent out the call. Hopefully we will have between 5 and 10 answers from random people who will write to the list saying hello, I'm interested in this. What are you going to answer them? Thanks for pointing this out. My rought idea: if they have questions, answer them, else, tell them to DL and start tails/jessie and hack, and see what they produce. If there are several motivated answers then I think it's possible to split the work (e.g. icons/gtk/shell). I guess more than half of the people won't produce anything, but if someone has a convincing theme that would be a good start. I hope we would then do the integration and polishing together but I'm not that confident on that part. Because if we're interested in their past experience on GNOME before we spend time mentoring them, then we might as well ask this upfront. I thought that the first sentences made quite clear that we'd like some experience in theming of GTK/GNOME. But I'd rather not set some strict requirement as somebody motivated enough can do a good job even if they have no passed GNOME experience I think. e.g. perhaps experience in web development with JS and CSS forks perfectly. You also silently ignored my concern about money. If giving out money can help us recruiting more qualified people and do less filtering and mentoring, them I'm all for it. But then I'm not sure whether you like the idea of being mentoring someone else who is being paid and I'm not sure how to put it in the announcement in the first place so I'm ok to try without mentioning money at all first. I'm not interested in dealing with this money issue, but I'm not against it if you or someone else wants to take care of it. However, I think that we should not promise anything before being sure there is real good work behind. So if you think we could have money for this and want to take care of it, I'd propose not to mention it on the 1st place, but: - if someone asks, answer than that we can give them money; - additionally, if someone comes up with a convincing POC, propose them money to work on the shitty details fixing; - make very clear the requirements before money arrives: if we pay somebody who only does the funny parts and then let me do the shitty fixing, I'd feel tricked. What do you think? We might as well delay those questions for once the call is passed, but our past experience with the bounty program proved that getting external people to do work for us definitely doesn't come for free (as in free time)! Indeed thanks for sharing your experience. I'm a bit afraid of that too, but let's see what happens... 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] Shared screen locking solution for live distributions in Debian
Hi, I have a project called ediX which is just a minimized Debian for educational hosting. It is always under heavy redesign but especially so right now with all of the changes to the Debian Jessie. I recently took down the web site in order to move it the project to The Foundation for Learning Equality where I also help with educational projects such as Khan Academy Light etc. After reflecting on the question longer the thought finally occurred to me why others might want or need this second password feature. ediX is basically default Debian live with a few select packages for a minimum boot relying on the persistence feature to provide educational software for services and configuration. The users (teachers) are assumed to not have shell / linux knowledge and a minimal GUI is made available basically just for monitoring, changing configurations, and updates. However, tails users running directly from a live CD without using persistence do not benefit from having the users credentials saved and thus the need if I am understanding things correctly. What I would like to see is an easier method of changing the default password and other user settings in the Debian live configuration scripts. As a simple precaution I have been changing user name but allowing live as password for the image however this all gets changed once the persistence volume is loaded. As I understand it, Debian Live recommends and defaults to user / live for the user account credentials and recommends user-setup and sudo packages be installed in the packages-list providing those features. By adding those packages that account is created and there are supporting scripts for changing the default user name and password however I have not had a need to do so. Hope this helps! Thanks, On Thu Jan 01 2015 at 4:53:33 AM sajolida sajol...@pimienta.org wrote: Ed Dixon: Hi, Hi, which project are you from? I have been using the xtrlock package which allows the screen to still be viewed while locked to good effect in classroom situations. It takes the current users password by default. I may be missing something here but as far as I am aware all current Debian screen locking mechanisms fill this need, if installed. I personally would not want a second set of credentials adding a potential vector attached to the user account just to have a separate password for the screen lock. Can you explain more the need for this? In the case of live distributions most of the time there is no user password by default. So if we want to use a password to lock the screen we need to ask for a password at some point. I'd like to avoid introducing yet another password if there is one already (like in the case of Jondo, and sometimes Tails) but otherwise we need at least one. Does that make sense? Note that in the case of Tails, you can configure an administration password at boot time: https://tails.boum.org/doc/first_steps/startup_options/ administration_password. I'd like to consider reusing this for screen locking if it is set (and only ask for a screen locking password if there is none), unless someone has security concerns about this. -- sajolida ___ 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] building manually fail [for me]
Hello, I tried to build as described in the instructions: https://tails.boum.org/contribute/build/ Option Building manually. However, the build ends with the following errors: Get:1 http://ftp.de.debian.org/debian/ wheezy/main liblzo2-2 i386 2.06-1+deb7u1 [64.3 kB] Get:2 http://ftp.de.debian.org/debian/ wheezy/main squashfs-tools i386 1:4.2-5 [125 kB] Fetched 189 kB in 0s (482 kB/s) Selecting previously unselected package liblzo2-2:i386. (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ...$ Unpacking liblzo2-2:i386 (from .../liblzo2-2_2.06-1+deb7u1_i386.deb) ... Selecting previously unselected package squashfs-tools. Unpacking squashfs-tools (from .../squashfs- tools_1%3a4.2-5_i386.deb) ... Processing triggers for man-db ... Setting up liblzo2-2:i386 (2.06-1+deb7u1) ... Setting up squashfs-tools (1:4.2-5) ... P: Preparing squashfs image... P: This may take a while. ERROR: ld.so: object '/usr/lib/libeatmydata/libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. Cannot stat sortlist entry lib/modules/3.16-1-amd64/modules.dep.bin This is probably because you're using the wrong file path relative to the source directories Cannot stat sortlist entry lib/modules/3.16-1-amd64/modules.alias.bin This is probably because you're using the wrong file path relative to the source directories ... [same path relative to the source directories] Full log: https://filetea.me/t1sGZUHJxyYRL6TMYZNS2LTdA My developer OS: root@tails-dev:~/tails# df -h Filesystem Size Used Avail Use% Mounted on rootfs 24G 9.4G 14G 42% / udev 10M 0 10M 0% /dev tmpfs 397M 624K 397M 1% /run /dev/disk/by-uuid/a1c142af-2c54-4a6a-82fb-de5ad64fbf5d 24G 9.4G 14G 42% / tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 1011M 224K 1011M 1% /run/shm root@tails-dev:~/tails# cat /etc/issue Debian GNU/Linux 7 \n \l root@tails-dev:~/tails# uname -a Linux tails-dev 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/ Linux root@tails-dev:~/tails# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass # / was on /dev/sda1 during installation UUID=a1c142af-2c54-4a6a-82fb-de5ad64fbf5d / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=d5047e2b-8169-42fe-b2e2-ca77853088bc noneswap sw 0 0 /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 My command: git clone git://git.tails.boum.org/tails cd tails/ git checkout devel export TAILS_BUILD_OPTIONS=noproxy nano config/chroot_local-includes/usr/share/tails/tbb-dist-url.txt cat config/chroot_local-includes/usr/share/tails/tbb-dist-url.txt https://dist.torproject.org/torbrowser/ lb clean --all lb config lb build I would be very grateful for any ideas for troubleshooting. Thanks, And ___ 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] Build failed in Jenkins: build_Tails_ISO_devel #765
See https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/765/ -- Started by user anonymous Building remotely on isobuilder2 in workspace https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/ws/ Deleting project workspace... done Wiping out workspace first. Cloning the remote Git repository Cloning repository gitolite@puppet-git.lizard:tails git init https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/ws/ # timeout=10 Fetching upstream changes from gitolite@puppet-git.lizard:tails git --version # timeout=10 git fetch --tags --progress gitolite@puppet-git.lizard:tails +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command git fetch --tags --progress gitolite@puppet-git.lizard:tails +refs/heads/*:refs/remotes/origin/* returned status code 128: stdout: stderr: ssh: connect to host puppet-git.lizard port 22: No route to host fatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1437) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1225) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:87) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:282) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:438) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:701) ERROR: null ___ 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] building manually fail [for me]
admin itarragon wrote (01 Jan 2015 18:22:14 GMT) : I tried to build as described in the instructions: https://tails.boum.org/contribute/build/ Option Building manually. Great! However, the build ends with the following errors: [...] Cannot stat sortlist entry lib/modules/3.16-1-amd64/modules.alias.bin This is probably because you're using the wrong file path relative to the source directories ... [same path relative to the source directories] These are warnings, and fully expected. The full log ends with such messages, which indicates that mksquashfs has apparently not finished its job. Did the build really complete and give a shell prompt back to you? 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] building manually fail [for me]
No, I interrupted work through ^C. After the last line in the full log it just froze. No output to the stdout/stderr. I need to wait more time? P.S. If I do not correct answer to the mailing list, then I apologize in advance. I forgot how to use the mailing lists. ___ 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] Jenkins build is back to normal : build_Tails_ISO_devel #766
See https://jenkins.tails.boum.org/job/build_Tails_ISO_devel/766/ ___ 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.
