[Tails-dev] Build failed in Jenkins: build_Tails_ISO_experimental #1505
See https://jenkins.tails.boum.org/job/build_Tails_ISO_experimental/1505/changes Changes: [amnesia] Remove build timestamp files after computing what we need from them. -- [...truncated 14613 lines...] 59.15% done, estimate finish Sat Jan 3 10:42:14 2015 60.23% done, estimate finish Sat Jan 3 10:42:14 2015 61.31% done, estimate finish Sat Jan 3 10:42:14 2015 62.38% done, estimate finish Sat Jan 3 10:42:14 2015 63.46% done, estimate finish Sat Jan 3 10:42:14 2015 64.53% done, estimate finish Sat Jan 3 10:42:14 2015 65.61% done, estimate finish Sat Jan 3 10:42:14 2015 66.68% done, estimate finish Sat Jan 3 10:42:14 2015 67.76% done, estimate finish Sat Jan 3 10:42:14 2015 68.84% done, estimate finish Sat Jan 3 10:42:14 2015 69.91% done, estimate finish Sat Jan 3 10:42:14 2015 70.99% done, estimate finish Sat Jan 3 10:42:14 2015 72.06% done, estimate finish Sat Jan 3 10:42:14 2015 73.14% done, estimate finish Sat Jan 3 10:42:14 2015 74.21% done, estimate finish Sat Jan 3 10:42:14 2015 75.29% done, estimate finish Sat Jan 3 10:42:14 2015 76.36% done, estimate finish Sat Jan 3 10:42:14 2015 77.44% done, estimate finish Sat Jan 3 10:42:14 2015 78.51% done, estimate finish Sat Jan 3 10:42:14 2015 79.59% done, estimate finish Sat Jan 3 10:42:14 2015 80.66% done, estimate finish Sat Jan 3 10:42:14 2015 81.74% done, estimate finish Sat Jan 3 10:42:14 2015 82.82% done, estimate finish Sat Jan 3 10:42:14 2015 83.89% done, estimate finish Sat Jan 3 10:42:14 2015 84.97% done, estimate finish Sat Jan 3 10:42:14 2015 86.04% done, estimate finish Sat Jan 3 10:42:14 2015 87.12% done, estimate finish Sat Jan 3 10:42:14 2015 88.20% done, estimate finish Sat Jan 3 10:42:14 2015 89.27% done, estimate finish Sat Jan 3 10:42:14 2015 90.35% done, estimate finish Sat Jan 3 10:42:14 2015 91.42% done, estimate finish Sat Jan 3 10:42:14 2015 92.50% done, estimate finish Sat Jan 3 10:42:14 2015 93.57% done, estimate finish Sat Jan 3 10:42:14 2015 94.65% done, estimate finish Sat Jan 3 10:42:14 2015 95.72% done, estimate finish Sat Jan 3 10:42:14 2015 96.80% done, estimate finish Sat Jan 3 10:42:14 2015 97.87% done, estimate finish Sat Jan 3 10:42:14 2015 98.95% done, estimate finish Sat Jan 3 10:42:14 2015 Total translation table size: 2048 Total rockridge attributes bytes: 11670 Total directory bytes: 30720 Path table size(bytes): 130 Max brk space used 21000 464892 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://deb.tails.boum.org experimental Release.gpg Hit http://deb.torproject.org wheezy Release.gpg Hit http://security.debian.org wheezy/updates Release.gpg Hit http://deb.tails.boum.org experimental Release Hit http://ftp.us.debian.org wheezy Release.gpg Hit http://deb.torproject.org sid Release.gpg Hit http://deb.tails.boum.org experimental/main i386 Packages Hit http://security.debian.org wheezy/updates Release Hit http://ftp.us.debian.org experimental Release.gpg Hit http://deb.torproject.org wheezy Release Hit http://security.debian.org wheezy/updates/main i386 Packages Hit http://ftp.us.debian.org unstable Release.gpg Hit http://deb.torproject.org sid 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 wheezy/main i386 Packages Hit http://ftp.us.debian.org wheezy-backports Release.gpg Hit http://security.debian.org wheezy/updates/non-free i386 Packages Ign http://deb.tails.boum.org experimental/main Translation-en Hit http://ftp.us.debian.org wheezy Release Hit http://security.debian.org wheezy/updates/contrib Translation-en Hit http://deb.torproject.org sid/main i386 Packages Hit http://ftp.us.debian.org experimental Release Hit http://security.debian.org wheezy/updates/main Translation-en 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 Ign http://deb.torproject.org wheezy/main Translation-en Hit
[Tails-dev] [review'n'merge:1.2.3] feature/8518-save-packages-list
Hi, this is a very simple first step towards implementing #6297. The infrastructure (Puppet) bits have already been merged. The short-term goal is to have reproducible.debian.net track the status of the Debian packages we use (#8512) using current data, instead of a one-shot imported list as now: https://reproducible.debian.net/userContent/reproducible.html = I've merged this branch in feature/jessie already. For consistency, it would be nice to have it merged into stable and devel too. Should be safe for stable, given how minimal the changes that affect non-Jenkins-builds are. 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.
[Tails-dev] Build failed in Jenkins: build_Tails_ISO_feature-jessie #263
See https://jenkins.tails.boum.org/job/build_Tails_ISO_feature-jessie/263/changes Changes: [amnesia] Save build start and end timestamps. [amnesia] Add a script that extracts the list of binary and source packages used during a build, from apt-cacher-ng logs. [amnesia] Generate the list of packages used during build, after building with Jenkins. [amnesia] Remove build timestamp files after computing what we need from them. -- [...truncated 20781 lines...] 33.23% done, estimate finish Sat Jan 3 10:56:15 2015 34.15% done, estimate finish Sat Jan 3 10:56:15 2015 35.08% done, estimate finish Sat Jan 3 10:56:15 2015 36.00% done, estimate finish Sat Jan 3 10:56:15 2015 36.92% done, estimate finish Sat Jan 3 10:56:15 2015 37.85% done, estimate finish Sat Jan 3 10:56:15 2015 38.77% done, estimate finish Sat Jan 3 10:56:15 2015 39.69% done, estimate finish Sat Jan 3 10:56:15 2015 40.62% done, estimate finish Sat Jan 3 10:56:15 2015 41.54% done, estimate finish Sat Jan 3 10:56:15 2015 42.46% done, estimate finish Sat Jan 3 10:56:15 2015 43.38% done, estimate finish Sat Jan 3 10:56:15 2015 44.31% done, estimate finish Sat Jan 3 10:56:15 2015 45.23% done, estimate finish Sat Jan 3 10:56:15 2015 46.15% done, estimate finish Sat Jan 3 10:56:15 2015 47.08% done, estimate finish Sat Jan 3 10:56:15 2015 48.00% done, estimate finish Sat Jan 3 10:56:15 2015 48.92% done, estimate finish Sat Jan 3 10:56:15 2015 49.85% done, estimate finish Sat Jan 3 10:56:15 2015 50.77% done, estimate finish Sat Jan 3 10:56:15 2015 51.69% done, estimate finish Sat Jan 3 10:56:15 2015 52.61% done, estimate finish Sat Jan 3 10:56:15 2015 53.54% done, estimate finish Sat Jan 3 10:56:15 2015 54.46% done, estimate finish Sat Jan 3 10:56:15 2015 55.38% done, estimate finish Sat Jan 3 10:56:15 2015 56.31% done, estimate finish Sat Jan 3 10:56:15 2015 57.23% done, estimate finish Sat Jan 3 10:56:15 2015 58.15% done, estimate finish Sat Jan 3 10:56:15 2015 59.08% done, estimate finish Sat Jan 3 10:56:15 2015 60.00% done, estimate finish Sat Jan 3 10:56:15 2015 60.92% done, estimate finish Sat Jan 3 10:56:15 2015 61.84% done, estimate finish Sat Jan 3 10:56:15 2015 62.77% done, estimate finish Sat Jan 3 10:56:15 2015 63.69% done, estimate finish Sat Jan 3 10:56:15 2015 64.62% done, estimate finish Sat Jan 3 10:56:15 2015 65.54% done, estimate finish Sat Jan 3 10:56:15 2015 66.46% done, estimate finish Sat Jan 3 10:56:15 2015 67.38% done, estimate finish Sat Jan 3 10:56:15 2015 68.31% done, estimate finish Sat Jan 3 10:56:15 2015 69.23% done, estimate finish Sat Jan 3 10:56:15 2015 70.15% done, estimate finish Sat Jan 3 10:56:15 2015 71.07% done, estimate finish Sat Jan 3 10:56:15 2015 72.00% done, estimate finish Sat Jan 3 10:56:15 2015 72.92% done, estimate finish Sat Jan 3 10:56:15 2015 73.85% done, estimate finish Sat Jan 3 10:56:15 2015 74.77% done, estimate finish Sat Jan 3 10:56:15 2015 75.69% done, estimate finish Sat Jan 3 10:56:15 2015 76.61% done, estimate finish Sat Jan 3 10:56:15 2015 77.54% done, estimate finish Sat Jan 3 10:56:15 2015 78.46% done, estimate finish Sat Jan 3 10:56:15 2015 79.38% done, estimate finish Sat Jan 3 10:56:15 2015 80.31% done, estimate finish Sat Jan 3 10:56:15 2015 81.23% done, estimate finish Sat Jan 3 10:56:15 2015 82.15% done, estimate finish Sat Jan 3 10:56:15 2015 83.08% done, estimate finish Sat Jan 3 10:56:15 2015 84.00% done, estimate finish Sat Jan 3 10:56:16 2015 84.92% done, estimate finish Sat Jan 3 10:56:16 2015 85.84% done, estimate finish Sat Jan 3 10:56:16 2015 86.77% done, estimate finish Sat Jan 3 10:56:16 2015 87.69% done, estimate finish Sat Jan 3 10:56:16 2015 88.61% done, estimate finish Sat Jan 3 10:56:16 2015 89.54% done, estimate finish Sat Jan 3 10:56:16 2015 90.46% done, estimate finish Sat Jan 3 10:56:16 2015 91.38% done, estimate finish Sat Jan 3 10:56:16 2015 92.30% done, estimate finish Sat Jan 3 10:56:16 2015 93.23% done, estimate finish Sat Jan 3 10:56:16 2015 94.15% done, estimate finish Sat Jan 3 10:56:16 2015 95.08% done, estimate finish Sat Jan 3 10:56:16 2015 96.00% done, estimate finish Sat Jan 3 10:56:16 2015 96.92% done, estimate finish Sat Jan 3 10:56:16 2015 97.84% done, estimate finish Sat Jan 3 10:56:16 2015 98.77% done, estimate finish Sat Jan 3 10:56:16 2015 99.69% done, estimate finish Sat Jan 3 10:56:16 2015 Total translation table size: 2048 Total rockridge attributes bytes: 11880 Total directory bytes: 30720 Path table size(bytes): 130 Max brk space used 21000 541688 extents written (1057 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
Re: [Tails-dev] Windows camouflage for Jessie/GNOME shell
Alan: sajolida sajol...@pimienta.org wrote: 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? Done in 543f5a8. It fits on one line in a standalone page but it will probably wrap when inlined in the news feed. But let's not spend more time on this. # 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. Let's try this. Then I also think that it is important to request them to send regular updates on their progress. Because if we have 5-10 answers and they all start exploring the basics in parallel, then it's important to be able to identify quickly who is really capable and dedicated to do the work, so we can maybe assign them complementary tasks instead of having them duplicate the same work in parallel. In GSOC they ask for weekly reports, right? Maybe that's a bit too much but every two weeks sounds good, no? 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. That makes sense. 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. Good to know. 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. That makes perfect sense as well. I like your idea of not mentioning money at the beginning (unless they ask) and propose it to complete the last mile, shitty details, etc. once we found the good people to do it. So feel free to merge news/windows_camouflage_jessie into master whenever you want. Then I'll do a bit of Twitter. -- 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] [Grml-devel] Shared screen locking solution for live distributions in Debian
* Julien Jehannet [Fri Jan 02, 2015 at 04:19:10PM +0100]: 2015-01-02 13:41 GMT+01:00 Evgeni Golov evg...@grml.org: On Fri, Jan 02, 2015 at 11:20:35AM +, sajolida wrote: I've been investigating the screen locking mechanism of those various Debian based live distributions, and I found out that none of them had a real mechanism to do so. They either: - Do not provide any screen locking mechanism (Knoppix, Grml, Jondo Live). Grml has grml-lock[1], you should have set a proper password before using it, obviously ;) grml-lock actually checks if a password is set and if that's not the case then grml-lock prompts for setting one (to avoid locking yourself out). FYI, note that Debian disabled the --new switch in vlock which limit now the desktop locking capability. Here is what you can read in the NEWS file: vlock (2.2.2-4) unstable; urgency=medium This update disables the new.so plugin and thus the --new switch, because it proved too hard to fix it properly. See #702705. See also: Debian Bug report logs - #702705 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702705 Meh, how sad. Thanks for the pointer, Julien. regards, -mika- signature.asc Description: Digital signature ___ 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] [Grml-devel] Shared screen locking solution for live distributions in Debian
Axel Beckert: - Do not provide any screen locking mechanism (Knoppix, Grml, Jondo Live). At least for grml, that's wrong. grml-full ships vlock which can lock all consoles (and switching back to X) at once with the option -a. Right. I tried both grml-lock as advertised by Evgeni and vlock as advertised by you. Actually, grml-lock provides a similar user experience as the one that we imagined for Tails: if you didn't set a password it asks for one before locking the screen. On the other hand as Julien pointed out, the --new option of vlock is broken right now and as a consequence grml-lock doesn't work. Both in a console and in X it errors with vlock: loading plugin 'new' failed: No such file or directory. Shall I report a Grml bug about that? -- 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] Jenkins build is back to normal : build_Tails_ISO_feature-jessie #264
See https://jenkins.tails.boum.org/job/build_Tails_ISO_feature-jessie/264/changes ___ 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] Build failed in Jenkins: build_Tails_ISO_feature-jessie #263
[amnesia] Remove build timestamp files after computing what we need from them. That was buggy. Testing a fix. ___ 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_experimental #1507
See https://jenkins.tails.boum.org/job/build_Tails_ISO_experimental/1507/changes ___ 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] Please review bugfix/8087-gnome-screenshot-save-to-home-folder
Hi, please review the following branch, which aims to fix the bug #8087: matsa/bugfix/8087-gnome-screenshot-save-to-home-folder The ticket has been updated accordingly, except the target version. Thanks, and 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] Please review bugfix/8071-Do-not-suspend-to-RAM-when-closing-lid
Le Wed, 24 Dec 2014 13:18:21 +0100, intrigeri intrig...@boum.org a écrit : Hi, matsa wrote (24 Dec 2014 05:32:33 GMT) : please review the following branch, which aim to fix the bug #8071: matsa/bugfix/8071-Do-not-suspend-to-RAM-when-closing-lid Mangled the ticket as needed = candidate for 1.2.3. Next time, please read How to submit your changes on https://tails.boum.org/contribute/merge_policy/#index2h1, and follow its instructions :) Thanks for the pointer. I've tried again with the bug #8087, I hope everyhting will be allright this time. Thanks again, and 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] Windows camouflage for Jessie/GNOME shell
Hi! On Sat, 03 Jan 2015 17:17:08 + sajolida sajol...@pimienta.org wrote: [...] Then I also think that it is important to request them to send regular updates on their progress. Because if we have 5-10 answers and they all start exploring the basics in parallel, then it's important to be able to identify quickly who is really capable and dedicated to do the work, so we can maybe assign them complementary tasks instead of having them duplicate the same work in parallel. In GSOC they ask for weekly reports, right? Maybe that's a bit too much but every two weeks sounds good, no? Let's try that. So feel free to merge news/windows_camouflage_jessie into master whenever you want. Then I'll do a bit of Twitter. Done. Please proceed. ___ 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.
