Reading package lists... Building dependency tree... Reading state information... NOTICE: 'ruby-serverspec' packaging is maintained in the 'Git' version control system at: git://anonscm.debian.org/pkg-ruby-extras/ruby-serverspec.git Need to get 37.5 kB of source archives. Get:1 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-serverspec 2.18.0-1 (dsc) [2,189 B] Get:2 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-serverspec 2.18.0-1 (tar) [31.8 kB] Get:3 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-serverspec 2.18.0-1 (diff) [3,496 B] gpgv: keyblock resource `/tmp/.gnupg/trustedkeys.gpg': file open error gpgv: Signature made Thu 18 Jun 2015 04:55:51 PM UTC using RSA key ID CD460BDE gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./ruby-serverspec_2.18.0-1.dsc dpkg-source: info: extracting ruby-serverspec in ruby-serverspec-2.18.0 dpkg-source: info: unpacking ruby-serverspec_2.18.0.orig.tar.gz dpkg-source: info: unpacking ruby-serverspec_2.18.0-1.debian.tar.xz Fetched 37.5 kB in 0s (2,800 kB/s) Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: bsdmainutils ca-certificates debhelper devscripts dh-python file gem2deb gem2deb-test-runner gettext gettext-base groff-base intltool-debian libasprintf0v5 libcroco3 libexpat1 libffi6 libglib2.0-0 libgmp-dev libgmpxx4ldbl libicu52 libmagic1 libmpdec2 libpipeline1 libpython3-stdlib libpython3.4-minimal libpython3.4-stdlib libruby2.1 libruby2.2 libsqlite3-0 libunistring0 libxml2 libyaml-0-2 man-db mime-support openssl po-debconf python3 python3-chardet python3-debian python3-minimal python3-pkg-resources python3-six python3.4 python3.4-minimal rake ruby ruby-all-dev ruby-diff-lcs ruby-minitest ruby-multi-json ruby-net-scp ruby-net-ssh ruby-power-assert ruby-rspec ruby-rspec-core ruby-rspec-expectations ruby-rspec-its ruby-rspec-mocks ruby-rspec-support ruby-setup ruby-specinfra ruby-test-unit ruby-thread-order ruby2.1 ruby2.1-dev ruby2.2 ruby2.2-dev rubygems-integration 0 upgraded, 68 newly installed, 0 to remove and 0 not upgraded. Need to get 33.7 MB of archives. After this operation, 130 MB of additional disk space will be used. Get:1 http://urika:3142/ftp.debian.org/debian/ sid/main libasprintf0v5 amd64 0.19.5.1-1 [32.2 kB] Get:2 http://urika:3142/ftp.debian.org/debian/ sid/main libmagic1 amd64 1:5.22+15-2 [249 kB] Get:3 http://urika:3142/ftp.debian.org/debian/ sid/main libicu52 amd64 52.1-10 [6,786 kB] Get:4 http://urika:3142/ftp.debian.org/debian/ sid/main libxml2 amd64 2.9.2+dfsg1-3 [934 kB] Get:5 http://urika:3142/ftp.debian.org/debian/ sid/main groff-base amd64 1.22.3-1 [1,205 kB] Get:6 http://urika:3142/ftp.debian.org/debian/ sid/main bsdmainutils amd64 9.0.6 [183 kB] Get:7 http://urika:3142/ftp.debian.org/debian/ sid/main libpipeline1 amd64 1.4.1-1 [27.8 kB] Get:8 http://urika:3142/ftp.debian.org/debian/ sid/main man-db amd64 2.7.2-1 [1,000 kB] Get:9 http://urika:3142/ftp.debian.org/debian/ sid/main libffi6 amd64 3.2.1-3 [20.1 kB] Get:10 http://urika:3142/ftp.debian.org/debian/ sid/main libglib2.0-0 amd64 2.44.1-1.1 [2,461 kB] Get:11 http://urika:3142/ftp.debian.org/debian/ sid/main libcroco3 amd64 0.6.8-3+b1 [135 kB] Get:12 http://urika:3142/ftp.debian.org/debian/ sid/main libmpdec2 amd64 2.4.1-1 [85.7 kB] Get:13 http://urika:3142/ftp.debian.org/debian/ sid/main libpython3.4-minimal amd64 3.4.3-8 [495 kB] Get:14 http://urika:3142/ftp.debian.org/debian/ sid/main mime-support all 3.59 [36.4 kB] Get:15 http://urika:3142/ftp.debian.org/debian/ sid/main libsqlite3-0 amd64 3.8.11.1-1 [454 kB] Get:16 http://urika:3142/ftp.debian.org/debian/ sid/main libpython3.4-stdlib amd64 3.4.3-8 [2,057 kB] Get:17 http://urika:3142/ftp.debian.org/debian/ sid/main libunistring0 amd64 0.9.3-5.2+b1 [288 kB] Get:18 http://urika:3142/ftp.debian.org/debian/ sid/main libyaml-0-2 amd64 0.1.6-3 [50.4 kB] Get:19 http://urika:3142/ftp.debian.org/debian/ sid/main libexpat1 amd64 2.1.0-7 [80.0 kB] Get:20 http://urika:3142/ftp.debian.org/debian/ sid/main python3.4-minimal amd64 3.4.3-8 [1,401 kB] Get:21 http://urika:3142/ftp.debian.org/debian/ sid/main python3-minimal amd64 3.4.3-4 [34.7 kB] Get:22 http://urika:3142/ftp.debian.org/debian/ sid/main python3.4 amd64 3.4.3-8 [219 kB] Get:23 http://urika:3142/ftp.debian.org/debian/ sid/main libpython3-stdlib amd64 3.4.3-4 [18.1 kB] Get:24 http://urika:3142/ftp.debian.org/debian/ sid/main dh-python all 2.20150728 [71.3 kB] Get:25 http://urika:3142/ftp.debian.org/debian/ sid/main python3 amd64 3.4.3-4 [21.1 kB] Get:26 http://urika:3142/ftp.debian.org/debian/ sid/main file amd64 1:5.22+15-2 [60.1 kB] Get:27 http://urika:3142/ftp.debian.org/debian/ sid/main gettext-base amd64 0.19.5.1-1 [122 kB] Get:28 http://urika:3142/ftp.debian.org/debian/ sid/main openssl amd64 1.0.2d-1 [695 kB] Get:29 http://urika:3142/ftp.debian.org/debian/ sid/main ca-certificates all 20150426 [208 kB] Get:30 http://urika:3142/ftp.debian.org/debian/ sid/main gettext amd64 0.19.5.1-1 [1,459 kB] Get:31 http://urika:3142/ftp.debian.org/debian/ sid/main intltool-debian all 0.35.0+20060710.2 [25.9 kB] Get:32 http://urika:3142/ftp.debian.org/debian/ sid/main po-debconf all 1.0.18 [248 kB] Get:33 http://urika:3142/ftp.debian.org/debian/ sid/main debhelper all 9.20150811 [817 kB] Get:34 http://urika:3142/ftp.debian.org/debian/ sid/main devscripts amd64 2.15.8 [908 kB] Get:35 http://urika:3142/ftp.debian.org/debian/ sid/main rubygems-integration all 1.9 [4,754 B] Get:36 http://urika:3142/ftp.debian.org/debian/ sid/main libruby2.1 amd64 2.1.5-4 [3,280 kB] Get:37 http://urika:3142/ftp.debian.org/debian/ sid/main ruby2.1 amd64 2.1.5-4 [276 kB] Get:38 http://urika:3142/ftp.debian.org/debian/ sid/main ruby all 1:2.1.5.1 [9,756 B] Get:39 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-power-assert all 0.2.3-1 [7,236 B] Get:40 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-test-unit all 3.1.2-1 [60.0 kB] Get:41 http://urika:3142/ftp.debian.org/debian/ sid/main libruby2.2 amd64 2.2.2-3 [3,098 kB] Get:42 http://urika:3142/ftp.debian.org/debian/ sid/main ruby2.2 amd64 2.2.2-3 [213 kB] Get:43 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-minitest all 5.8.0-1 [49.7 kB] Get:44 http://urika:3142/ftp.debian.org/debian/ sid/main gem2deb-test-runner all 0.20.2 [16.8 kB] Get:45 http://urika:3142/ftp.debian.org/debian/ sid/main python3-pkg-resources all 18.0.1-2 [44.2 kB] Get:46 http://urika:3142/ftp.debian.org/debian/ sid/main python3-chardet all 2.3.0-1 [96.1 kB] Get:47 http://urika:3142/ftp.debian.org/debian/ sid/main python3-six all 1.9.0-3 [13.7 kB] Get:48 http://urika:3142/ftp.debian.org/debian/ sid/main python3-debian all 0.1.27 [50.9 kB] Get:49 http://urika:3142/ftp.debian.org/debian/ sid/main libgmpxx4ldbl amd64 2:6.0.0+dfsg-7 [22.2 kB] Get:50 http://urika:3142/ftp.debian.org/debian/ sid/main libgmp-dev amd64 2:6.0.0+dfsg-7 [621 kB] Get:51 http://urika:3142/ftp.debian.org/debian/ sid/main ruby2.1-dev amd64 2.1.5-4 [1,103 kB] Get:52 http://urika:3142/ftp.debian.org/debian/ sid/main ruby2.2-dev amd64 2.2.2-3 [1,142 kB] Get:53 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-all-dev all 1:2.1.5.1 [9,188 B] Get:54 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-setup all 3.4.1-9 [34.2 kB] Get:55 http://urika:3142/ftp.debian.org/debian/ sid/main gem2deb all 0.20.2 [52.1 kB] Get:56 http://urika:3142/ftp.debian.org/debian/ sid/main rake all 10.4.2-1 [49.0 kB] Get:57 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-diff-lcs all 1.2.5-2 [26.7 kB] Get:58 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-multi-json all 1.11.2-1 [18.9 kB] Get:59 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-net-ssh all 1:2.9.2-2 [90.1 kB] Get:60 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-net-scp all 1.2.1-2 [16.9 kB] Get:61 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-rspec-support all 3.3.0c0e0m0s0-1 [24.3 kB] Get:62 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-rspec-expectations all 3.3.0c0e0m0s0-1 [90.1 kB] Get:63 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-rspec-mocks all 3.3.0c0e0m0s0-1 [87.0 kB] Get:64 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-thread-order all 1.1.0-1 [5,096 B] Get:65 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-rspec-core all 3.3.0c0e0m0s0-1 [174 kB] Get:66 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-rspec all 3.3.0c0e0m0s0-1 [6,544 B] Get:67 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-rspec-its all 1.2.0-2 [6,054 B] Get:68 http://urika:3142/ftp.debian.org/debian/ sid/main ruby-specinfra all 2.35.1-1 [44.9 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 33.7 MB in 0s (52.3 MB/s) Selecting previously unselected package libasprintf0v5:amd64. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 15408 files and directories currently installed.) Preparing to unpack .../libasprintf0v5_0.19.5.1-1_amd64.deb ... Unpacking libasprintf0v5:amd64 (0.19.5.1-1) ... Selecting previously unselected package libmagic1:amd64. Preparing to unpack .../libmagic1_1%3a5.22+15-2_amd64.deb ... Unpacking libmagic1:amd64 (1:5.22+15-2) ... Selecting previously unselected package libicu52:amd64. Preparing to unpack .../libicu52_52.1-10_amd64.deb ... Unpacking libicu52:amd64 (52.1-10) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.2+dfsg1-3_amd64.deb ... Unpacking libxml2:amd64 (2.9.2+dfsg1-3) ... Selecting previously unselected package groff-base. Preparing to unpack .../groff-base_1.22.3-1_amd64.deb ... Unpacking groff-base (1.22.3-1) ... Selecting previously unselected package bsdmainutils. Preparing to unpack .../bsdmainutils_9.0.6_amd64.deb ... Unpacking bsdmainutils (9.0.6) ... Selecting previously unselected package libpipeline1:amd64. Preparing to unpack .../libpipeline1_1.4.1-1_amd64.deb ... Unpacking libpipeline1:amd64 (1.4.1-1) ... Selecting previously unselected package man-db. Preparing to unpack .../man-db_2.7.2-1_amd64.deb ... Unpacking man-db (2.7.2-1) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.2.1-3_amd64.deb ... Unpacking libffi6:amd64 (3.2.1-3) ... Selecting previously unselected package libglib2.0-0:amd64. Preparing to unpack .../libglib2.0-0_2.44.1-1.1_amd64.deb ... Unpacking libglib2.0-0:amd64 (2.44.1-1.1) ... Selecting previously unselected package libcroco3:amd64. Preparing to unpack .../libcroco3_0.6.8-3+b1_amd64.deb ... Unpacking libcroco3:amd64 (0.6.8-3+b1) ... Selecting previously unselected package libmpdec2:amd64. Preparing to unpack .../libmpdec2_2.4.1-1_amd64.deb ... Unpacking libmpdec2:amd64 (2.4.1-1) ... Selecting previously unselected package libpython3.4-minimal:amd64. Preparing to unpack .../libpython3.4-minimal_3.4.3-8_amd64.deb ... Unpacking libpython3.4-minimal:amd64 (3.4.3-8) ... Selecting previously unselected package mime-support. Preparing to unpack .../mime-support_3.59_all.deb ... Unpacking mime-support (3.59) ... Selecting previously unselected package libsqlite3-0:amd64. Preparing to unpack .../libsqlite3-0_3.8.11.1-1_amd64.deb ... Unpacking libsqlite3-0:amd64 (3.8.11.1-1) ... Selecting previously unselected package libpython3.4-stdlib:amd64. Preparing to unpack .../libpython3.4-stdlib_3.4.3-8_amd64.deb ... Unpacking libpython3.4-stdlib:amd64 (3.4.3-8) ... Selecting previously unselected package libunistring0:amd64. Preparing to unpack .../libunistring0_0.9.3-5.2+b1_amd64.deb ... Unpacking libunistring0:amd64 (0.9.3-5.2+b1) ... Selecting previously unselected package libyaml-0-2:amd64. Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ... Unpacking libyaml-0-2:amd64 (0.1.6-3) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-7) ... Selecting previously unselected package python3.4-minimal. Preparing to unpack .../python3.4-minimal_3.4.3-8_amd64.deb ... Unpacking python3.4-minimal (3.4.3-8) ... Selecting previously unselected package python3-minimal. Preparing to unpack .../python3-minimal_3.4.3-4_amd64.deb ... Unpacking python3-minimal (3.4.3-4) ... Selecting previously unselected package python3.4. Preparing to unpack .../python3.4_3.4.3-8_amd64.deb ... Unpacking python3.4 (3.4.3-8) ... Selecting previously unselected package libpython3-stdlib:amd64. Preparing to unpack .../libpython3-stdlib_3.4.3-4_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.4.3-4) ... Selecting previously unselected package dh-python. Preparing to unpack .../dh-python_2.20150728_all.deb ... Unpacking dh-python (2.20150728) ... Setting up libpython3.4-minimal:amd64 (3.4.3-8) ... Setting up libexpat1:amd64 (2.1.0-7) ... Setting up python3.4-minimal (3.4.3-8) ... Setting up python3-minimal (3.4.3-4) ... Processing triggers for libc-bin (2.19-19) ... Selecting previously unselected package python3. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 17026 files and directories currently installed.) Preparing to unpack .../python3_3.4.3-4_amd64.deb ... Unpacking python3 (3.4.3-4) ... Selecting previously unselected package file. Preparing to unpack .../file_1%3a5.22+15-2_amd64.deb ... Unpacking file (1:5.22+15-2) ... Selecting previously unselected package gettext-base. Preparing to unpack .../gettext-base_0.19.5.1-1_amd64.deb ... Unpacking gettext-base (0.19.5.1-1) ... Selecting previously unselected package openssl. Preparing to unpack .../openssl_1.0.2d-1_amd64.deb ... Unpacking openssl (1.0.2d-1) ... Selecting previously unselected package ca-certificates. Preparing to unpack .../ca-certificates_20150426_all.deb ... Unpacking ca-certificates (20150426) ... Selecting previously unselected package gettext. Preparing to unpack .../gettext_0.19.5.1-1_amd64.deb ... Unpacking gettext (0.19.5.1-1) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../intltool-debian_0.35.0+20060710.2_all.deb ... Unpacking intltool-debian (0.35.0+20060710.2) ... Selecting previously unselected package po-debconf. Preparing to unpack .../po-debconf_1.0.18_all.deb ... Unpacking po-debconf (1.0.18) ... Selecting previously unselected package debhelper. Preparing to unpack .../debhelper_9.20150811_all.deb ... Unpacking debhelper (9.20150811) ... Selecting previously unselected package devscripts. Preparing to unpack .../devscripts_2.15.8_amd64.deb ... Unpacking devscripts (2.15.8) ... Selecting previously unselected package rubygems-integration. Preparing to unpack .../rubygems-integration_1.9_all.deb ... Unpacking rubygems-integration (1.9) ... Selecting previously unselected package libruby2.1:amd64. Preparing to unpack .../libruby2.1_2.1.5-4_amd64.deb ... Unpacking libruby2.1:amd64 (2.1.5-4) ... Selecting previously unselected package ruby2.1. Preparing to unpack .../ruby2.1_2.1.5-4_amd64.deb ... Unpacking ruby2.1 (2.1.5-4) ... Selecting previously unselected package ruby. Preparing to unpack .../ruby_1%3a2.1.5.1_all.deb ... Unpacking ruby (1:2.1.5.1) ... Selecting previously unselected package ruby-power-assert. Preparing to unpack .../ruby-power-assert_0.2.3-1_all.deb ... Unpacking ruby-power-assert (0.2.3-1) ... Selecting previously unselected package ruby-test-unit. Preparing to unpack .../ruby-test-unit_3.1.2-1_all.deb ... Unpacking ruby-test-unit (3.1.2-1) ... Selecting previously unselected package libruby2.2:amd64. Preparing to unpack .../libruby2.2_2.2.2-3_amd64.deb ... Unpacking libruby2.2:amd64 (2.2.2-3) ... Selecting previously unselected package ruby2.2. Preparing to unpack .../ruby2.2_2.2.2-3_amd64.deb ... Unpacking ruby2.2 (2.2.2-3) ... Selecting previously unselected package ruby-minitest. Preparing to unpack .../ruby-minitest_5.8.0-1_all.deb ... Unpacking ruby-minitest (5.8.0-1) ... Selecting previously unselected package gem2deb-test-runner. Preparing to unpack .../gem2deb-test-runner_0.20.2_all.deb ... Unpacking gem2deb-test-runner (0.20.2) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../python3-pkg-resources_18.0.1-2_all.deb ... Unpacking python3-pkg-resources (18.0.1-2) ... Selecting previously unselected package python3-chardet. Preparing to unpack .../python3-chardet_2.3.0-1_all.deb ... Unpacking python3-chardet (2.3.0-1) ... Selecting previously unselected package python3-six. Preparing to unpack .../python3-six_1.9.0-3_all.deb ... Unpacking python3-six (1.9.0-3) ... Selecting previously unselected package python3-debian. Preparing to unpack .../python3-debian_0.1.27_all.deb ... Unpacking python3-debian (0.1.27) ... Selecting previously unselected package libgmpxx4ldbl:amd64. Preparing to unpack .../libgmpxx4ldbl_2%3a6.0.0+dfsg-7_amd64.deb ... Unpacking libgmpxx4ldbl:amd64 (2:6.0.0+dfsg-7) ... Selecting previously unselected package libgmp-dev:amd64. Preparing to unpack .../libgmp-dev_2%3a6.0.0+dfsg-7_amd64.deb ... Unpacking libgmp-dev:amd64 (2:6.0.0+dfsg-7) ... Selecting previously unselected package ruby2.1-dev:amd64. Preparing to unpack .../ruby2.1-dev_2.1.5-4_amd64.deb ... Unpacking ruby2.1-dev:amd64 (2.1.5-4) ... Selecting previously unselected package ruby2.2-dev:amd64. Preparing to unpack .../ruby2.2-dev_2.2.2-3_amd64.deb ... Unpacking ruby2.2-dev:amd64 (2.2.2-3) ... Selecting previously unselected package ruby-all-dev. Preparing to unpack .../ruby-all-dev_1%3a2.1.5.1_all.deb ... Unpacking ruby-all-dev (1:2.1.5.1) ... Selecting previously unselected package ruby-setup. Preparing to unpack .../ruby-setup_3.4.1-9_all.deb ... Unpacking ruby-setup (3.4.1-9) ... Selecting previously unselected package gem2deb. Preparing to unpack .../gem2deb_0.20.2_all.deb ... Unpacking gem2deb (0.20.2) ... Selecting previously unselected package rake. Preparing to unpack .../archives/rake_10.4.2-1_all.deb ... Unpacking rake (10.4.2-1) ... Selecting previously unselected package ruby-diff-lcs. Preparing to unpack .../ruby-diff-lcs_1.2.5-2_all.deb ... Unpacking ruby-diff-lcs (1.2.5-2) ... Selecting previously unselected package ruby-multi-json. Preparing to unpack .../ruby-multi-json_1.11.2-1_all.deb ... Unpacking ruby-multi-json (1.11.2-1) ... Selecting previously unselected package ruby-net-ssh. Preparing to unpack .../ruby-net-ssh_1%3a2.9.2-2_all.deb ... Unpacking ruby-net-ssh (1:2.9.2-2) ... Selecting previously unselected package ruby-net-scp. Preparing to unpack .../ruby-net-scp_1.2.1-2_all.deb ... Unpacking ruby-net-scp (1.2.1-2) ... Selecting previously unselected package ruby-rspec-support. Preparing to unpack .../ruby-rspec-support_3.3.0c0e0m0s0-1_all.deb ... Unpacking ruby-rspec-support (3.3.0c0e0m0s0-1) ... Selecting previously unselected package ruby-rspec-expectations. Preparing to unpack .../ruby-rspec-expectations_3.3.0c0e0m0s0-1_all.deb ... Unpacking ruby-rspec-expectations (3.3.0c0e0m0s0-1) ... Selecting previously unselected package ruby-rspec-mocks. Preparing to unpack .../ruby-rspec-mocks_3.3.0c0e0m0s0-1_all.deb ... Unpacking ruby-rspec-mocks (3.3.0c0e0m0s0-1) ... Selecting previously unselected package ruby-thread-order. Preparing to unpack .../ruby-thread-order_1.1.0-1_all.deb ... Unpacking ruby-thread-order (1.1.0-1) ... Selecting previously unselected package ruby-rspec-core. Preparing to unpack .../ruby-rspec-core_3.3.0c0e0m0s0-1_all.deb ... Unpacking ruby-rspec-core (3.3.0c0e0m0s0-1) ... Selecting previously unselected package ruby-rspec. Preparing to unpack .../ruby-rspec_3.3.0c0e0m0s0-1_all.deb ... Unpacking ruby-rspec (3.3.0c0e0m0s0-1) ... Selecting previously unselected package ruby-rspec-its. Preparing to unpack .../ruby-rspec-its_1.2.0-2_all.deb ... Unpacking ruby-rspec-its (1.2.0-2) ... Selecting previously unselected package ruby-specinfra. Preparing to unpack .../ruby-specinfra_2.35.1-1_all.deb ... Unpacking ruby-specinfra (2.35.1-1) ... Setting up libasprintf0v5:amd64 (0.19.5.1-1) ... Setting up libmagic1:amd64 (1:5.22+15-2) ... Setting up libicu52:amd64 (52.1-10) ... Setting up libxml2:amd64 (2.9.2+dfsg1-3) ... Setting up groff-base (1.22.3-1) ... Setting up bsdmainutils (9.0.6) ... update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode Setting up libpipeline1:amd64 (1.4.1-1) ... Setting up man-db (2.7.2-1) ... Building database of manual pages ... Setting up libffi6:amd64 (3.2.1-3) ... Setting up libglib2.0-0:amd64 (2.44.1-1.1) ... No schema files found: doing nothing. Setting up libcroco3:amd64 (0.6.8-3+b1) ... Setting up libmpdec2:amd64 (2.4.1-1) ... Setting up mime-support (3.59) ... Setting up libsqlite3-0:amd64 (3.8.11.1-1) ... Setting up libpython3.4-stdlib:amd64 (3.4.3-8) ... Setting up libunistring0:amd64 (0.9.3-5.2+b1) ... Setting up libyaml-0-2:amd64 (0.1.6-3) ... Setting up python3.4 (3.4.3-8) ... Setting up libpython3-stdlib:amd64 (3.4.3-4) ... Setting up file (1:5.22+15-2) ... Setting up gettext-base (0.19.5.1-1) ... Setting up openssl (1.0.2d-1) ... Setting up ca-certificates (20150426) ... Setting up gettext (0.19.5.1-1) ... Setting up intltool-debian (0.35.0+20060710.2) ... Setting up po-debconf (1.0.18) ... Setting up debhelper (9.20150811) ... Setting up rubygems-integration (1.9) ... Setting up libruby2.1:amd64 (2.1.5-4) ... Setting up ruby2.1 (2.1.5-4) ... Setting up ruby (1:2.1.5.1) ... Setting up ruby-power-assert (0.2.3-1) ... Setting up ruby-test-unit (3.1.2-1) ... Setting up libruby2.2:amd64 (2.2.2-3) ... Setting up ruby2.2 (2.2.2-3) ... Setting up ruby-minitest (5.8.0-1) ... Setting up gem2deb-test-runner (0.20.2) ... Setting up libgmpxx4ldbl:amd64 (2:6.0.0+dfsg-7) ... Setting up libgmp-dev:amd64 (2:6.0.0+dfsg-7) ... Setting up ruby2.1-dev:amd64 (2.1.5-4) ... Setting up ruby2.2-dev:amd64 (2.2.2-3) ... Setting up ruby-all-dev (1:2.1.5.1) ... Setting up ruby-setup (3.4.1-9) ... Setting up rake (10.4.2-1) ... Setting up ruby-diff-lcs (1.2.5-2) ... Setting up ruby-multi-json (1.11.2-1) ... Setting up ruby-net-ssh (1:2.9.2-2) ... Setting up ruby-net-scp (1.2.1-2) ... Setting up ruby-rspec-support (3.3.0c0e0m0s0-1) ... Setting up ruby-rspec-expectations (3.3.0c0e0m0s0-1) ... Setting up ruby-rspec-mocks (3.3.0c0e0m0s0-1) ... Setting up ruby-thread-order (1.1.0-1) ... Setting up ruby-rspec-core (3.3.0c0e0m0s0-1) ... Setting up ruby-rspec (3.3.0c0e0m0s0-1) ... Setting up ruby-rspec-its (1.2.0-2) ... Setting up ruby-specinfra (2.35.1-1) ... Setting up python3 (3.4.3-4) ... Setting up devscripts (2.15.8) ... Setting up python3-pkg-resources (18.0.1-2) ... Setting up python3-chardet (2.3.0-1) ... Setting up python3-six (1.9.0-3) ... Setting up python3-debian (0.1.27) ... Setting up gem2deb (0.20.2) ... Setting up dh-python (2.20150728) ... Processing triggers for libc-bin (2.19-19) ... Processing triggers for ca-certificates (20150426) ... Updating certificates in /etc/ssl/certs... 180 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Killed old client process Internet Systems Consortium DHCP Client 4.3.2 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/32:67:6c:0d:5d:4d Sending on LPF/eth0/32:67:6c:0d:5d:4d Sending on Socket/fallback DHCPRELEASE on eth0 to 10.0.3.1 port 67 dpkg-buildpackage: source package ruby-serverspec dpkg-buildpackage: source version 2.18.0-1 dpkg-buildpackage: source distribution unstable dpkg-buildpackage: source changed by Antonio Terceiro dpkg-source --before-build ruby-serverspec-2.18.0 dpkg-buildpackage: host architecture amd64 debian/rules clean dh clean --buildsystem=ruby --with ruby dh_testdir -O--buildsystem=ruby dh_auto_clean -O--buildsystem=ruby dh_ruby --clean dh_ruby --clean dh_clean -O--buildsystem=ruby dpkg-source -b ruby-serverspec-2.18.0 dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building ruby-serverspec using existing ./ruby-serverspec_2.18.0.orig.tar.gz dpkg-source: info: building ruby-serverspec in ruby-serverspec_2.18.0-1.debian.tar.xz dpkg-source: info: building ruby-serverspec in ruby-serverspec_2.18.0-1.dsc debian/rules build dh build --buildsystem=ruby --with ruby dh_testdir -O--buildsystem=ruby dh_auto_configure -O--buildsystem=ruby dh_ruby --configure dh_auto_build -O--buildsystem=ruby dh_ruby --build dh_ruby --build dh_auto_test -O--buildsystem=ruby dh_ruby --test debian/rules binary dh binary --buildsystem=ruby --with ruby dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby dh_ruby --install /ruby-serverspec-2.18.0/debian/ruby-serverspec dh_ruby --install ┌──────────────────────────────────────────────────────────────────────────────┐ │ Install files │ └──────────────────────────────────────────────────────────────────────────────┘ install -d /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/bin install -D -m755 /ruby-serverspec-2.18.0/bin/serverspec-init /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/bin/serverspec-init install -d /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/helper.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/helper.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/subject.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/subject.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/yumrepo.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/yumrepo.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/docker_image.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/docker_image.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/interface.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/interface.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/ppa.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/ppa.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/selinux.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/selinux.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/routing_table.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/routing_table.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/x509_private_key.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/x509_private_key.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/bond.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/bond.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/iis_app_pool.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/iis_app_pool.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/selinux_module.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/selinux_module.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/process.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/process.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/windows_hot_fix.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/windows_hot_fix.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/x509_certificate.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/x509_certificate.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/command.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/command.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/bridge.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/bridge.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/iptables.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/iptables.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/lxc.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/lxc.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/user.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/user.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/file.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/file.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/fstab.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/fstab.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/php_config.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/php_config.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/cron.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/cron.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/cgroup.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/cgroup.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/host.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/host.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/kernel_module.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/kernel_module.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/package.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/package.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/group.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/group.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/mail_alias.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/mail_alias.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/windows_scheduled_task.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/windows_scheduled_task.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/ipfilter.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/ipfilter.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/iis_website.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/iis_website.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/port.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/port.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/ipnat.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/ipnat.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/windows_registry_key.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/windows_registry_key.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/windows_feature.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/windows_feature.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/docker_container.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/docker_container.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/default_gateway.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/default_gateway.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/linux_kernel_parameter.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/linux_kernel_parameter.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/base.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/base.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/zfs.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/zfs.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/ip6tables.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/ip6tables.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/docker_base.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/docker_base.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/type/service.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/type/service.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/commands/base.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/commands/base.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/version.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/version.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/have_site_application.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/have_site_application.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/be_installed.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/be_installed.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/have_site_bindings.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/have_site_bindings.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/be_listening.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/be_listening.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/be_writable.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/be_writable.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/be_executable.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/be_executable.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/be_mounted.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/be_mounted.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/contain.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/contain.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/have_virtual_dir.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/have_virtual_dir.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/be_running.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/be_running.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/have_rule.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/have_rule.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/have_entry.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/have_entry.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/be_resolvable.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/be_resolvable.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/belong_to_primary_group.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/belong_to_primary_group.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/be_enabled.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/be_enabled.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/belong_to_group.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/belong_to_group.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/be_readable.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/be_readable.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher/be_reachable.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher/be_reachable.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/power_assert.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/power_assert.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/matcher.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/matcher.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/helper/type.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/helper/type.rb install -D -m644 /ruby-serverspec-2.18.0/lib/serverspec/setup.rb /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby/serverspec/setup.rb Rewriting shebang line of /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/bin/serverspec-init ┌──────────────────────────────────────────────────────────────────────────────┐ │ Install Rubygems integration metadata │ └──────────────────────────────────────────────────────────────────────────────┘ generating gemspec at /ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/share/rubygems-integration/all/specifications/serverspec-2.18.0.gemspec /usr/bin/ruby2.1 /usr/bin/gem2deb-test-runner ┌──────────────────────────────────────────────────────────────────────────────┐ │ Checking Rubygems dependency resolution on ruby2.1 │ └──────────────────────────────────────────────────────────────────────────────┘ GEM_PATH=/tmp/.gem/ruby/2.1.0:/var/lib/gems/2.1.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.1.0:/usr/share/rubygems-integration/2.1.0:/usr/share/rubygems-integration/2.1:/usr/share/rubygems-integration/all:debian/ruby-serverspec/usr/share/rubygems-integration/all ruby2.1 -e gem\ \"serverspec\" ┌──────────────────────────────────────────────────────────────────────────────┐ │ Run tests for ruby2.1 from debian/ruby-tests.rake │ └──────────────────────────────────────────────────────────────────────────────┘ RUBYLIB=/ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby:. rake2.1 -f debian/ruby-tests.rake /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/base/\*_spec.rb ...................................................................................WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/base/file_spec.rb:352:in `block (2 levels) in '. ........................................................WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/base/service_spec.rb:28:in `block (2 levels) in '. ...WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/base/service_spec.rb:45:in `block (2 levels) in '. .......... Finished in 0.15375 seconds (files took 0.39665 seconds to load) 152 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/fedora/\*_spec.rb ... Finished in 0.01028 seconds (files took 0.26099 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/windows/\*_spec.rb ....................WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:42:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:42:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:42:in `block (3 levels) in '. ....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:62:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:62:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:62:in `block (3 levels) in '. ....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:82:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:82:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:82:in `block (3 levels) in '. ....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. ...WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/group_spec.rb:20:in `block (3 levels) in '. ....................................................WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/service_spec.rb:25:in `block (2 levels) in '. .WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/service_spec.rb:28:in `block (2 levels) in '. .....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/user_spec.rb:30:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/user_spec.rb:30:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/user_spec.rb:30:in `block (3 levels) in '. . Finished in 0.1016 seconds (files took 0.32024 seconds to load) 94 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/smartos/\*_spec.rb ......... Finished in 0.02039 seconds (files took 0.31799 seconds to load) 9 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/solaris10/\*_spec.rb .....................................................WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/solaris10/file_spec.rb:309:in `block (2 levels) in '. ....... Finished in 0.08254 seconds (files took 0.35847 seconds to load) 60 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/nixos/\*_spec.rb ..... Finished in 0.01533 seconds (files took 0.28037 seconds to load) 5 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/fedora15/\*_spec.rb ... Finished in 0.00673 seconds (files took 0.24689 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/plamo/\*_spec.rb .. Finished in 0.01123 seconds (files took 0.25197 seconds to load) 2 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/freebsd/\*_spec.rb .................. Finished in 0.02643 seconds (files took 0.25429 seconds to load) 18 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/suse/\*_spec.rb ......... Finished in 0.01274 seconds (files took 0.25181 seconds to load) 9 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/fedora20/\*_spec.rb ... Finished in 0.00643 seconds (files took 0.23208 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/solaris/\*_spec.rb ............................ Finished in 0.02832 seconds (files took 0.3273 seconds to load) 28 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/redhat5/\*_spec.rb .. Finished in 0.01172 seconds (files took 0.28275 seconds to load) 2 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/opensuse/\*_spec.rb ... Finished in 0.00824 seconds (files took 0.3053 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/freebsd10/\*_spec.rb ...... Finished in 0.0119 seconds (files took 0.2692 seconds to load) 6 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/aix/\*_spec.rb ...WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/aix/file_spec.rb:19:in `block (2 levels) in '. .............. Finished in 0.02605 seconds (files took 0.23137 seconds to load) 17 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/redhat7/\*_spec.rb .. Finished in 0.00835 seconds (files took 0.22657 seconds to load) 2 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/openbsd/\*_spec.rb ................................ Finished in 0.03565 seconds (files took 0.23659 seconds to load) 32 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/arch/\*_spec.rb ........... Finished in 0.02377 seconds (files took 0.29581 seconds to load) 11 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/debian/\*_spec.rb ......... Finished in 0.01603 seconds (files took 0.24594 seconds to load) 9 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/linux/\*_spec.rb .............................................................. Finished in 0.05997 seconds (files took 0.26258 seconds to load) 62 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/darwin/\*_spec.rb ..................... Finished in 0.02363 seconds (files took 0.23447 seconds to load) 21 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/gentoo/\*_spec.rb ... Finished in 0.01012 seconds (files took 0.22486 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/ubuntu/\*_spec.rb ... Finished in 0.01047 seconds (files took 0.23352 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/type/redhat/\*_spec.rb ............... Finished in 0.02397 seconds (files took 0.22622 seconds to load) 15 examples, 0 failures /usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/helper/\*_spec.rb . Finished in 0.00113 seconds (files took 0.23038 seconds to load) 1 example, 0 failures /usr/bin/ruby2.2 /usr/bin/gem2deb-test-runner ┌──────────────────────────────────────────────────────────────────────────────┐ │ Checking Rubygems dependency resolution on ruby2.2 │ └──────────────────────────────────────────────────────────────────────────────┘ GEM_PATH=/tmp/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-serverspec/usr/share/rubygems-integration/all ruby2.2 -e gem\ \"serverspec\" ┌──────────────────────────────────────────────────────────────────────────────┐ │ Run tests for ruby2.2 from debian/ruby-tests.rake │ └──────────────────────────────────────────────────────────────────────────────┘ RUBYLIB=/ruby-serverspec-2.18.0/debian/ruby-serverspec/usr/lib/ruby/vendor_ruby:. rake2.2 -f debian/ruby-tests.rake /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/base/\*_spec.rb ...................................................................................WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/base/file_spec.rb:352:in `block (2 levels) in '. ........................................................WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/base/service_spec.rb:28:in `block (2 levels) in '. ...WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/base/service_spec.rb:45:in `block (2 levels) in '. .......... Finished in 0.14477 seconds (files took 0.28495 seconds to load) 152 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/fedora/\*_spec.rb ... Finished in 0.00724 seconds (files took 0.23965 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/windows/\*_spec.rb ....................WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:42:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:42:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:42:in `block (3 levels) in '. ....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:62:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:62:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:62:in `block (3 levels) in '. ....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:82:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:82:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:82:in `block (3 levels) in '. ....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/file_spec.rb:110:in `block (3 levels) in '. ...WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/group_spec.rb:20:in `block (3 levels) in '. ....................................................WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/service_spec.rb:25:in `block (2 levels) in '. .WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/service_spec.rb:28:in `block (2 levels) in '. .....WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/user_spec.rb:30:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/user_spec.rb:30:in `block (3 levels) in '. WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/windows/user_spec.rb:30:in `block (3 levels) in '. . Finished in 0.10454 seconds (files took 0.26674 seconds to load) 94 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/smartos/\*_spec.rb ......... Finished in 0.01595 seconds (files took 0.24349 seconds to load) 9 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/solaris10/\*_spec.rb .....................................................WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/solaris10/file_spec.rb:309:in `block (2 levels) in '. ....... Finished in 0.09644 seconds (files took 0.27285 seconds to load) 60 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/nixos/\*_spec.rb ..... Finished in 0.01091 seconds (files took 0.24006 seconds to load) 5 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/fedora15/\*_spec.rb ... Finished in 0.00766 seconds (files took 0.24522 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/plamo/\*_spec.rb .. Finished in 0.00634 seconds (files took 0.24067 seconds to load) 2 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/freebsd/\*_spec.rb .................. Finished in 0.02372 seconds (files took 0.23832 seconds to load) 18 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/suse/\*_spec.rb ......... Finished in 0.01754 seconds (files took 0.24605 seconds to load) 9 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/fedora20/\*_spec.rb ... Finished in 0.0077 seconds (files took 0.24057 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/solaris/\*_spec.rb ............................ Finished in 0.03167 seconds (files took 0.25125 seconds to load) 28 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/redhat5/\*_spec.rb .. Finished in 0.00597 seconds (files took 0.22847 seconds to load) 2 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/opensuse/\*_spec.rb ... Finished in 0.007 seconds (files took 0.24629 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/freebsd10/\*_spec.rb ...... Finished in 0.01332 seconds (files took 0.23482 seconds to load) 6 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/aix/\*_spec.rb ...WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /ruby-serverspec-2.18.0/spec/type/aix/file_spec.rb:19:in `block (2 levels) in '. .............. Finished in 0.02394 seconds (files took 0.25111 seconds to load) 17 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/redhat7/\*_spec.rb .. Finished in 0.00851 seconds (files took 0.25054 seconds to load) 2 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/openbsd/\*_spec.rb ................................ Finished in 0.03395 seconds (files took 0.24933 seconds to load) 32 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/arch/\*_spec.rb ........... Finished in 0.01901 seconds (files took 0.23519 seconds to load) 11 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/debian/\*_spec.rb ......... Finished in 0.01477 seconds (files took 0.24115 seconds to load) 9 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/linux/\*_spec.rb .............................................................. Finished in 0.06793 seconds (files took 0.26082 seconds to load) 62 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/darwin/\*_spec.rb ..................... Finished in 0.02635 seconds (files took 0.25146 seconds to load) 21 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/gentoo/\*_spec.rb ... Finished in 0.00664 seconds (files took 0.23685 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/ubuntu/\*_spec.rb ... Finished in 0.00707 seconds (files took 0.23103 seconds to load) 3 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/type/redhat/\*_spec.rb ............... Finished in 0.02011 seconds (files took 0.25455 seconds to load) 15 examples, 0 failures /usr/bin/ruby2.2 /usr/bin/rspec --pattern spec/helper/\*_spec.rb . Finished in 0.00093 seconds (files took 0.23727 seconds to load) 1 example, 0 failures ┌──────────────────────────────────────────────────────────────────────────────┐ │ dh_ruby --install finished │ └──────────────────────────────────────────────────────────────────────────────┘ dh_installdocs -O--buildsystem=ruby dh_ruby_fixdocs -O--buildsystem=ruby dh_installchangelogs -O--buildsystem=ruby dh_installman -O--buildsystem=ruby dh_perl -O--buildsystem=ruby dh_link -O--buildsystem=ruby dh_compress -X.rb -O--buildsystem=ruby dh_fixperms -O--buildsystem=ruby dh_installdeb -O--buildsystem=ruby dh_gencontrol -O--buildsystem=ruby dpkg-gencontrol: warning: Depends field of package ruby-serverspec: unknown substitution variable ${shlibs:Depends} dh_md5sums -O--buildsystem=ruby dh_builddeb -O--buildsystem=ruby dpkg-deb: building package 'ruby-serverspec' in '../ruby-serverspec_2.18.0-1_all.deb'. dpkg-genchanges >../ruby-serverspec_2.18.0-1_amd64.changes dpkg-genchanges: including full source code in upload dpkg-source --after-build ruby-serverspec-2.18.0 dpkg-buildpackage: full upload (original source is included)