[Tails-dev] firewall

[firewall]

Please add a firewall

___
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] firewall

[firewall]

Please add a firewall

___
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] Automated builds specification

[Jurre van Bergen]

Hi,

As some of you might know,  we'll spend quite some time this year seting
up automated builds and test using our Jenkins platform and make it
easier to extract information and data from it.

For the first iteration, which is automatically build of interesting
branches, we need to specify:

 * Which branches we want to build?
We already build the base branches (stables, testing, devel and
experimental + feature/jessie).
So the questions raised is mostly concern the feature/* and bugfix/*
branches (so topic branches)
The criterias to automatically select the branches to be build could be:
branches which are not merged to devel but has new commits since N weeks
time, 15 days or the previous release.

 * Which regularity if needed? (assuming it will be build when a push is
made on it)
 - Is a branch built everyday enough? Should it be built more often or
less often?
 * How should you be notified?
 - Direct e-mail?
 - IRC channel?

We're already drafted some scenario's on:
https://tails.boum.org/blueprint/automated_builds_and_tests/autobuild_specs/

Some of you might want to see other one's implemented , so please update
the blueprint accordingly.
Scenarios can range from release managers, developers, reviewers,
testers. Some of these suggestions might not make it this year but will
be looked at in the following year.

Need to keep in mind that the same question will be raised when we'll
design the automated tests.

All the best,
CI team

___
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_stable #166

[tails-sysadmins]

See 

___
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_stable #165

[tails-sysadmins]

See 

--
[...truncated 12567 lines...]
Package 'aptitude-doc-en' is not installed, so not removed
Package 'aptitude-doc-es' is not installed, so not removed
Package 'aptitude-doc-fi' is not installed, so not removed
Package 'aptitude-doc-fr' is not installed, so not removed
Package 'aptitude-doc-it' is not installed, so not removed
Package 'aptitude-doc-ja' is not installed, so not removed
Package 'aptitude-doc-ru' is not installed, so not removed
Package 'aptitude-robot' is not installed, so not removed
The following packages were automatically installed and are no longer required:
  debootstrap fakeroot html2text libc-dev-bin libgssglue1 libitm1 libnfsidmap2
  libtirpc1 lsb-release python-apt-common python-debian python-debianbts
  python-fpconst python-soappy
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  aptitude* aptitude-common* db5.1-util* krb5-locales* live-build* locales*
  openssh-blacklist* openssh-blacklist-extra* python2.6* python2.6-minimal*
  rpcbind* tasksel* tasksel-data*
0 upgraded, 0 newly installed, 13 to remove and 0 not upgraded.
After this operation, 55.1 MB disk space will be freed.
(Reading database ... 138349 files and directories currently installed.)
Removing aptitude ...
Purging configuration files for aptitude ...
Removing aptitude-common ...
Removing db5.1-util ...
Removing krb5-locales ...
Removing live-build ...
Removing locales ...
Purging configuration files for locales ...
Removing openssh-blacklist ...
Removing openssh-blacklist-extra ...
Removing python2.6 ...
Purging configuration files for python2.6 ...
Removing python2.6-minimal ...
pitivi: current (['install', 'ok', 'installed'])
python-socksipy: all (['install', 'ok', 'installed'])
Purging configuration files for python2.6-minimal ...
Removing rpcbind ...
All runlevel operations denied by policy
All runlevel operations denied by policy
invoke-rc.d: policy-rc.d denied execution of stop.
Purging configuration files for rpcbind ...
Removing tasksel-data ...
Removing tasksel ...
Purging configuration files for tasksel ...
Processing triggers for man-db ...
Processing triggers for menu ...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
  debootstrap* fakeroot* html2text* libc-dev-bin* libgssglue1* libitm1*
  libnfsidmap2* libtirpc1* lsb-release* python-apt-common* python-debian*
  python-debianbts* python-fpconst* python-soappy*
0 upgraded, 0 newly installed, 14 to remove and 0 not upgraded.
After this operation, 3487 kB disk space will be freed.
(Reading database ... 136428 files and directories currently installed.)
Removing debootstrap ...
Removing fakeroot ...
update-alternatives: using /usr/bin/fakeroot-tcp to provide /usr/bin/fakeroot 
(fakeroot) in auto mode
Purging configuration files for fakeroot ...
Removing html2text ...
Purging configuration files for html2text ...
Removing libc-dev-bin ...
Removing libtirpc1:i386 ...
Purging configuration files for libtirpc1:i386 ...
Removing libgssglue1:i386 ...
Purging configuration files for libgssglue1:i386 ...
Removing libitm1:i386 ...
Purging configuration files for libitm1:i386 ...
Removing libnfsidmap2:i386 ...
Purging configuration files for libnfsidmap2:i386 ...
Removing lsb-release ...
Purging configuration files for lsb-release ...
Removing python-apt-common ...
Removing python-debian ...
Removing python-debianbts ...
Removing python-soappy ...
Removing python-fpconst ...
Processing triggers for man-db ...
Processing triggers for mime-support ...
Processing triggers for python-support ...
Deduplicating files in /usr/share/doc
Mode: real
Files:7567
Linked:   1028 files
Compared: 4691 files
Saved:8.93 MiB
Duration: 0.26 seconds
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
  hardlink*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 58.4 kB disk space will be freed.
(Reading database ... 136074 files and directories currently installed.)
Removing hardlink ...
Processing triggers for man-db ...
Creating /etc/default/locale
Setting correct file permissions
Removing *.pyc
Setting mtime on large files whose content generally do not change
Removing resolv.conf symbolic link
Configuring the runtime APT proxy
Truncating log files
P: Begin executing hooks...
P: Begin executing hacks...
update-rc.d: warning:  stop runlevel arguments (6) do not match kexec-load 
Default-Stop values (0 6)
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
df: Warning: cannot read table of mounted file systems: No such file or 
directory
cryptsetup: WARNING: could not determine root device from /etc/fstab
live-boot: core filesystems devices utils memdisk u

Re: [Tails-dev] [review'n'merge:1.2.3] feature/8518-save-packages-list

[bertagaz]

On Sat, Jan 03, 2015 at 11:19:21AM +0100, intrigeri wrote:
> 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.

Works! Merged into stable and devel.

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] [review'n'merge: 1.2.3] bugfix/8571-fix-mac-spoof-panic-mode

[anonym]

On 06/01/15 18:41, anonym wrote:
> Hi,
> 
> Apparently our MAC spoofing feature's panic mode is quite broken. Please
> review and merge the bugfix/8571-fix-mac-spoof-panic-mode branch into
> stable and devel. Before that you may want to have a look at comment 1
> in the ticket and agree that commit 54a80db is a good idea.

I've also pushed commit 8156352. Without this, I can reproduce the error
(notification not shown) about half of the times.

1. Boot Tails (any build should do, I did it with 1.2.2) with some
   rootpw set.
2. Switch to some VT from Tails Greeter
3. Login as root
4. Run the following to simulate a MAC spoofing error:
   mv /usr/bin/macchanger /usr/bin/macchanger.real
   ln -s /bin/true /usr/bin/macchanger
5. Switch back to Tails Greeter and login
6. Look out for the "Network card $NIC disabled"

With commit 8156352 the notification was shown 10 out of 10 times, which
seems like an improvement. :)

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.