Re: [Tails-dev] [review'n'merge:1.5] feature/9381-ship-amd64-syslinux
So, to clarify: now that u. has validated that this branch reaches its goal, it still needs to be reviewed and merged for 1.5. Any taker? 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] [review'n'merge:1.4.1] feature/5623-Installer-should-refuse-empty-device
u: sajolida: kurono: Hi guys, Could you please review the new iteration? Ticket: https://labs.riseup.net/code/issues/5623 Branch: https://git-tails.immerda.ch/kurono/liveusb-creator/commit/?h=feature/5623-Installer-should-refuse-empty-deviceid=ce0f3ac974a7b9f6e18071f01731e1d7edab0678 Thanks a lot! Instead of: 'The destination device was not created using Tails Installer. You can only upgrade a device created by Tails Installer. You need to install it a new to start with, e.g. by choosing the \Clone Install\ action instead.' What about: 'It is impossible to upgrade the destination device because it was not created using Tails Installer. You should instead reinstall Tails on this device using the \Clone Install\ action.' Which is shorted and avoids saying Tails Installer twice. I am currently implementing the Install from ISO option. Maybe we can make this sentence future compatible somehow? : Right :) If there is a simple way of detecting whether the code is running from inside Tails or from outside Tails, then we could have: inside Tails: 'It is impossible to upgrade the destination device because it was not created using Tails Installer. You should instead reinstall Tails on this device using the \Clone Install\ action.' outside Tails: 'It is impossible to upgrade the destination device because it was not created using Tails Installer. You should instead reinstall Tails on this device using the \Install from ISO\ action.' Otherwise maybe mentioning both (or none) would do: both: 'It is impossible to upgrade the destination device because it was not created using Tails Installer. You should instead reinstall Tails on this device using either the \Clone Install\ or the \Install from ISO\ action.' none: 'It is impossible to upgrade the destination device because it was not created using Tails Installer. You should instead reinstall Tails on this device.' I anyway think that the future is to get rid of this screen and this error message: https://tails.boum.org/blueprint/bootstrapping/installer#index2h2 But yes, what u mentions will arrive earlier. -- 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.
Re: [Tails-dev] [review'n'merge:1.4.1] feature/5623-Installer-should-refuse-empty-device
sajolida wrote (18 Jun 2015 13:32:18 GMT) : If there is a simple way of detecting whether the code is running from inside Tails or from outside Tails, [...] There is :) ___ 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_experimental #2336
See https://jenkins.tails.boum.org/job/build_Tails_ISO_experimental/2336/ -- [...truncated 4761 lines...] I: Unpacking wget... I: Unpacking libxapian22... I: Configuring the base system... I: Configuring gpgv... I: Configuring libssl1.0.0:i386... I: Configuring libgdbm3:i386... I: Configuring isc-dhcp-common... I: Configuring libtasn1-3:i386... I: Configuring libpopt0:i386... I: Configuring libusb-0.1-4:i386... I: Configuring libgpg-error0:i386... I: Configuring install-info... I: Configuring vim-common... I: Configuring libprocps0:i386... I: Configuring netbase... I: Configuring dmidecode... I: Configuring libudev0:i386... I: Configuring libkmod2:i386... I: Configuring adduser... I: Configuring traceroute... I: Configuring manpages... I: Configuring libsqlite3-0:i386... I: Configuring iproute... I: Configuring libidn11:i386... I: Configuring libnewt0.52... I: Configuring net-tools... I: Configuring libpipeline1:i386... I: Configuring bsdmainutils... I: Configuring netcat-traditional... I: Configuring debian-archive-keyring... I: Configuring libncursesw5:i386... I: Configuring info... I: Configuring iputils-ping... I: Configuring aptitude-common... I: Configuring cron... I: Configuring nano... I: Configuring libp11-kit0:i386... I: Configuring eatmydata... I: Configuring rsyslog... I: Configuring cpio... I: Configuring libstdc++6:i386... I: Configuring isc-dhcp-client... I: Configuring vim-tiny... I: Configuring readline-common... I: Configuring libnfnetlink0... I: Configuring libgcrypt11:i386... I: Configuring procps... I: Configuring libxapian22... I: Configuring whiptail... I: Configuring ifupdown... I: Configuring kmod... I: Configuring libapt-pkg4.12:i386... I: Configuring libept1.4.12... I: Configuring libapt-inst1.5:i386... I: Configuring libreadline6:i386... I: Configuring logrotate... I: Configuring libboost-iostreams1.49.0... I: Configuring groff-base... I: Configuring gnupg... I: Configuring libsigc++-2.0-0c2a:i386... I: Configuring libgnutls26:i386... I: Configuring apt-utils... I: Configuring udev... I: Configuring iptables... I: Configuring man-db... I: Configuring apt... I: Configuring wget... I: Configuring libcwidget3... I: Configuring aptitude... I: Configuring tasksel... I: Configuring tasksel-data... 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 ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. OK ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. OK ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded:
Re: [Tails-dev] [review'n'merge:1.5] feature/9381-ship-amd64-syslinux
u wrote (16 Jun 2015 12:28:36 GMT) : I simply modified line 1008 in /usr/lib/python2.7/dist-packages/liveusb/creator.py (derived from the feature_jessie branch) using syslinux-amd64 and the latest experimental ISO and it works! Yay \o/ Cool, thanks! In what environment, exactly? (Jessie? sid? both?) ___ 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] [review'n'merge:1.5] feature/9381-ship-amd64-syslinux
intrigeri: u wrote (16 Jun 2015 12:28:36 GMT) : I simply modified line 1008 in /usr/lib/python2.7/dist-packages/liveusb/creator.py (derived from the feature_jessie branch) using syslinux-amd64 and the latest experimental ISO and it works! Yay \o/ Cool, thanks! In what environment, exactly? (Jessie? sid? both?) Sorry for not providing this information. I tested this on Jessie only. Cheers u. ___ 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.
