RUN: /usr/share/launchpad-buildd/slavebin/slave-prep ['slave-prep']
Forking launchpad-buildd slave process...
Kernel version: Linux bos01-ppc64el-009 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:57:08 UTC 2016 ppc64le
Buildd toolchain package versions: launchpad-buildd_138 python-lpbuildd_138 sbuild_0.65.2-1ubuntu2+ubuntu15.10.3 bzr-builder_0.7.3-0ubuntu1 bzr_2.6.0+bzr6602-2ubuntu4 git_1:2.5.0-1ubuntu0.1 dpkg-dev_1.18.2ubuntu5.1 python-debian_0.1.27ubuntu1 qemu-user-static_1:2.3+dfsg-5ubuntu9.2.
Syncing the system clock with the buildd NTP service...
13 Mar 22:48:23 ntpdate[1590]: adjust time server 10.211.37.1 offset 0.000259 sec
RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', 'PACKAGEBUILD-9345466', '/home/buildd/filecache-default/64ba6963cee521707036a0c48846d736532c58ef']
Unpacking chroot for build PACKAGEBUILD-9345466
RUN: /usr/share/launchpad-buildd/slavebin/mount-chroot ['mount-chroot', 'PACKAGEBUILD-9345466']
Mounting chroot for build PACKAGEBUILD-9345466
RUN: /usr/share/launchpad-buildd/slavebin/override-sources-list ['override-sources-list', 'PACKAGEBUILD-9345466', 'deb http://ftpmaster.internal/ubuntu xenial main universe', 'deb http://ftpmaster.internal/ubuntu xenial-security main universe', 'deb http://ftpmaster.internal/ubuntu xenial-updates main universe', 'deb http://ftpmaster.internal/ubuntu xenial-proposed main universe']
Overriding sources.list in build-PACKAGEBUILD-9345466
RUN: /usr/share/launchpad-buildd/slavebin/update-debian-chroot ['update-debian-chroot', 'PACKAGEBUILD-9345466', 'ppc64el']
Updating debian chroot for build PACKAGEBUILD-9345466
Get:1 http://ftpmaster.internal xenial InRelease [95.8 kB]
Get:2 http://ftpmaster.internal xenial-security InRelease [82.2 kB]
Get:3 http://ftpmaster.internal xenial-updates InRelease [82.2 kB]
Get:4 http://ftpmaster.internal xenial-proposed InRelease [95.8 kB]
Get:5 http://ftpmaster.internal xenial/main ppc64el Packages [1401 kB]
Get:6 http://ftpmaster.internal xenial/universe ppc64el Packages [7076 kB]
Get:7 http://ftpmaster.internal xenial/main Translation-en [850 kB]
Get:8 http://ftpmaster.internal xenial/universe Translation-en [4874 kB]
Get:9 http://ftpmaster.internal xenial-security/main ppc64el Packages [28 B]
Get:10 http://ftpmaster.internal xenial-security/universe ppc64el Packages [28 B]
Get:11 http://ftpmaster.internal xenial-security/main Translation-en [28 B]
Get:12 http://ftpmaster.internal xenial-security/universe Translation-en [28 B]
Get:13 http://ftpmaster.internal xenial-updates/main ppc64el Packages [28 B]
Get:14 http://ftpmaster.internal xenial-updates/universe ppc64el Packages [28 B]
Get:15 http://ftpmaster.internal xenial-updates/main Translation-en [28 B]
Get:16 http://ftpmaster.internal xenial-updates/universe Translation-en [28 B]
Get:17 http://ftpmaster.internal xenial-proposed/main ppc64el Packages [53.3 kB]
Get:18 http://ftpmaster.internal xenial-proposed/universe ppc64el Packages [190 kB]
Get:19 http://ftpmaster.internal xenial-proposed/main Translation-en [61.0 kB]
Get:20 http://ftpmaster.internal xenial-proposed/universe Translation-en [131 kB]
Fetched 15.0 MB in 5s (2939 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  libapt-pkg4.16 libgnutls-deb0-28 libisl13 libprocps3 udev
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  perl-modules*
The following NEW packages will be installed:
  gcc-6-base init-system-helpers libapt-pkg5.0 libgnutls30 libisl15 liblz4-1
  libperl5.22 libprocps4 perl-modules-5.22
The following packages will be upgraded:
  advancecomp apt apt-transport-https base-files base-passwd binutils bsdutils
  ca-certificates coreutils cpp cpp-5 dash debconf debianutils diffutils
  dmsetup dpkg dpkg-dev e2fslibs e2fsprogs findutils g++ g++-5 gcc gcc-5
  gcc-5-base gnupg gpgv grep hostname init initscripts libacl1 libapparmor1
  libasan2 libasn1-8-heimdal libatomic1 libaudit-common libaudit1 libblkid1
  libc-bin libc-dev-bin libc6 libc6-dev libcap2 libcap2-bin libcc1-0
  libcomerr2 libcurl3-gnutls libdbus-1-3 libdebconfclient0 libdevmapper1.02.1
  libdpkg-perl libfdisk1 libffi6 libgcc-5-dev libgcc1 libgcrypt20 libgmp10
  libgomp1 libgpg-error0 libgssapi-krb5-2 libgssapi3-heimdal
  libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhogweed4
  libhx509-5-heimdal libidn11 libitm1 libk5crypto3 libkeyutils1 libkmod2
  libkrb5-26-heimdal libkrb5-3 libkrb5support0 libldap-2.4-2 libmount1
  libmpfr4 libncurses5 libncursesw5 libnettle6 libnih-dbus1 libnih1
  libp11-kit0 libpcre3 libpng12-0 libreadline6 libroken18-heimdal librtmp1
  libseccomp2 libselinux1 libsemanage-common libsemanage1 libsepol1
  libsmartcols1 libsqlite3-0 libss2 libssl1.0.0 libstdc++-5-dev libstdc++6
  libsystemd0 libtasn1-6 libtinfo5 libubsan0 libudev1 libusb-0.1-4 libuuid1
  libwind0-heimdal linux-libc-dev login lsb-base make mount multiarch-support
  ncurses-base ncurses-bin openssl passwd perl perl-base pkg-create-dbgsym
  pkgbinarymangler procps readline-common sed systemd systemd-sysv sysv-rc
  sysvinit-utils tar tzdata udev util-linux
134 upgraded, 9 newly installed, 1 to remove and 0 not upgraded.
Need to get 133 MB of archives.
After this operation, 336 MB of additional disk space will be used.
Get:1 http://ftpmaster.internal/ubuntu/ xenial/main base-files ppc64el 9.4ubuntu3 [67.8 kB]
Get:2 http://ftpmaster.internal/ubuntu/ xenial/main bsdutils ppc64el 1:2.27.1-4ubuntu1 [49.5 kB]
Get:3 http://ftpmaster.internal/ubuntu/ xenial/main coreutils ppc64el 8.25-2ubuntu2 [1171 kB]
Get:4 http://ftpmaster.internal/ubuntu/ xenial/main debianutils ppc64el 4.7 [85.1 kB]
Get:5 http://ftpmaster.internal/ubuntu/ xenial/main dpkg ppc64el 1.18.4ubuntu1 [2099 kB]
Get:6 http://ftpmaster.internal/ubuntu/ xenial/main dash ppc64el 0.5.8-2.1ubuntu2 [111 kB]
Get:7 http://ftpmaster.internal/ubuntu/ xenial/main diffutils ppc64el 1:3.3-3 [158 kB]
Get:8 http://ftpmaster.internal/ubuntu/ xenial/main libc6-dev ppc64el 2.21-0ubuntu6 [1991 kB]
Get:9 http://ftpmaster.internal/ubuntu/ xenial/main libc-dev-bin ppc64el 2.21-0ubuntu6 [64.8 kB]
Get:10 http://ftpmaster.internal/ubuntu/ xenial-proposed/main linux-libc-dev ppc64el 4.4.0-13.29 [829 kB]
Get:11 http://ftpmaster.internal/ubuntu/ xenial/main libcap2 ppc64el 1:2.24-12 [13.3 kB]
Get:12 http://ftpmaster.internal/ubuntu/ xenial/main libc-bin ppc64el 2.21-0ubuntu6 [1170 kB]
Get:13 http://ftpmaster.internal/ubuntu/ xenial-proposed/main gcc-6-base ppc64el 6-20160313-0ubuntu1 [14.7 kB]
Get:14 http://ftpmaster.internal/ubuntu/ xenial-proposed/main libgcc1 ppc64el 1:6-20160313-0ubuntu1 [27.3 kB]
Get:15 http://ftpmaster.internal/ubuntu/ xenial/main libc6 ppc64el 2.21-0ubuntu6 [5185 kB]
Get:16 http://ftpmaster.internal/ubuntu/ xenial/main e2fslibs ppc64el 1.42.13-1ubuntu1 [192 kB]
Get:17 http://ftpmaster.internal/ubuntu/ xenial/main e2fsprogs ppc64el 1.42.13-1ubuntu1 [763 kB]
Get:18 http://ftpmaster.internal/ubuntu/ xenial/main findutils ppc64el 4.6.0+git+20160126-2 [288 kB]
Get:19 http://ftpmaster.internal/ubuntu/ xenial/main grep ppc64el 2.23-1 [143 kB]
Get:20 http://ftpmaster.internal/ubuntu/ xenial/main hostname ppc64el 3.16ubuntu2 [11.4 kB]
Get:21 http://ftpmaster.internal/ubuntu/ xenial/main init-system-helpers all 1.29ubuntu1 [32.1 kB]
Get:22 http://ftpmaster.internal/ubuntu/ xenial/main sysvinit-utils ppc64el 2.88dsf-59.3ubuntu2 [21.6 kB]
Get:23 http://ftpmaster.internal/ubuntu/ xenial/main perl-modules-5.22 all 5.22.1-8 [2641 kB]
Get:24 http://ftpmaster.internal/ubuntu/ xenial/main libperl5.22 ppc64el 5.22.1-8 [3239 kB]
Get:25 http://ftpmaster.internal/ubuntu/ xenial/main perl ppc64el 5.22.1-8 [237 kB]
Get:26 http://ftpmaster.internal/ubuntu/ xenial/main perl-base ppc64el 5.22.1-8 [1185 kB]
Get:27 http://ftpmaster.internal/ubuntu/ xenial/main init ppc64el 1.29ubuntu1 [4548 B]
Get:28 http://ftpmaster.internal/ubuntu/ xenial/main login ppc64el 1:4.2-3.1ubuntu4 [303 kB]
Get:29 http://ftpmaster.internal/ubuntu/ xenial/main libsmartcols1 ppc64el 2.27.1-4ubuntu1 [58.7 kB]
Get:30 http://ftpmaster.internal/ubuntu/ xenial/main libaudit-common all 1:2.4.5-1ubuntu2 [3884 B]
Get:31 http://ftpmaster.internal/ubuntu/ xenial/main libaudit1 ppc64el 1:2.4.5-1ubuntu2 [38.9 kB]
Get:32 http://ftpmaster.internal/ubuntu/ xenial/main libpcre3 ppc64el 2:8.38-3 [220 kB]
Get:33 http://ftpmaster.internal/ubuntu/ xenial/main libselinux1 ppc64el 2.4-3build1 [54.6 kB]
Get:34 http://ftpmaster.internal/ubuntu/ xenial/main libsepol1 ppc64el 2.4-2 [172 kB]
Get:35 http://ftpmaster.internal/ubuntu/ xenial-proposed/main libsemanage-common all 2.4-3build1 [6594 B]
Get:36 http://ftpmaster.internal/ubuntu/ xenial-proposed/main libsemanage1 ppc64el 2.4-3build1 [72.9 kB]
Get:37 http://ftpmaster.internal/ubuntu/ xenial/main libfdisk1 ppc64el 2.27.1-4ubuntu1 [129 kB]
Get:38 http://ftpmaster.internal/ubuntu/ xenial/main libtinfo5 ppc64el 6.0+20160213-1ubuntu1 [79.2 kB]
Get:39 http://ftpmaster.internal/ubuntu/ xenial/main libncurses5 ppc64el 6.0+20160213-1ubuntu1 [96.9 kB]
Get:40 http://ftpmaster.internal/ubuntu/ xenial/main libncursesw5 ppc64el 6.0+20160213-1ubuntu1 [110 kB]
Get:41 http://ftpmaster.internal/ubuntu/ xenial/main sysv-rc all 2.88dsf-59.3ubuntu2 [18.2 kB]
Get:42 http://ftpmaster.internal/ubuntu/ xenial/main libsystemd0 ppc64el 229-2ubuntu1 [205 kB]
Get:43 http://ftpmaster.internal/ubuntu/ xenial/main util-linux ppc64el 2.27.1-4ubuntu1 [803 kB]
Get:44 http://ftpmaster.internal/ubuntu/ xenial/main libudev1 ppc64el 229-2ubuntu1 [58.4 kB]
Get:45 http://ftpmaster.internal/ubuntu/ xenial/main udev ppc64el 229-2ubuntu1 [986 kB]
Get:46 http://ftpmaster.internal/ubuntu/ xenial/main systemd ppc64el 229-2ubuntu1 [3513 kB]
Get:47 http://ftpmaster.internal/ubuntu/ xenial/main initscripts ppc64el 2.88dsf-59.3ubuntu2 [24.5 kB]
Get:48 http://ftpmaster.internal/ubuntu/ xenial/main libacl1 ppc64el 2.2.52-3 [15.7 kB]
Get:49 http://ftpmaster.internal/ubuntu/ xenial/main libkmod2 ppc64el 22-1ubuntu4 [36.4 kB]
Get:50 http://ftpmaster.internal/ubuntu/ xenial/main libprocps4 ppc64el 2:3.3.10-4ubuntu2 [32.2 kB]
Get:51 http://ftpmaster.internal/ubuntu/ xenial/main debconf all 1.5.58ubuntu1 [136 kB]
Get:52 http://ftpmaster.internal/ubuntu/ xenial/main procps ppc64el 2:3.3.10-4ubuntu2 [221 kB]
Get:53 http://ftpmaster.internal/ubuntu/ xenial/main libapparmor1 ppc64el 2.10-3ubuntu2 [29.0 kB]
Get:54 http://ftpmaster.internal/ubuntu/ xenial/main libgpg-error0 ppc64el 1.21-2ubuntu1 [37.0 kB]
Get:55 http://ftpmaster.internal/ubuntu/ xenial/main libmount1 ppc64el 2.27.1-4ubuntu1 [104 kB]
Get:56 http://ftpmaster.internal/ubuntu/ xenial/main libseccomp2 ppc64el 2.2.3-3ubuntu1 [41.3 kB]
Get:57 http://ftpmaster.internal/ubuntu/ xenial/main libcap2-bin ppc64el 1:2.24-12 [20.1 kB]
Get:58 http://ftpmaster.internal/ubuntu/ xenial/main lsb-base all 9.20160110 [13.5 kB]
Get:59 http://ftpmaster.internal/ubuntu/ xenial/main passwd ppc64el 1:4.2-3.1ubuntu4 [753 kB]
Get:60 http://ftpmaster.internal/ubuntu/ xenial/main libuuid1 ppc64el 2.27.1-4ubuntu1 [15.6 kB]
Get:61 http://ftpmaster.internal/ubuntu/ xenial/main libblkid1 ppc64el 2.27.1-4ubuntu1 [99.2 kB]
Get:62 http://ftpmaster.internal/ubuntu/ xenial/main tzdata all 2016a-1 [168 kB]
Get:63 http://ftpmaster.internal/ubuntu/ xenial/main systemd-sysv ppc64el 229-2ubuntu1 [18.1 kB]
Get:64 http://ftpmaster.internal/ubuntu/ xenial/main mount ppc64el 2.27.1-4ubuntu1 [116 kB]
Get:65 http://ftpmaster.internal/ubuntu/ xenial/main ncurses-bin ppc64el 6.0+20160213-1ubuntu1 [137 kB]
Get:66 http://ftpmaster.internal/ubuntu/ xenial/main sed ppc64el 4.2.2-7 [145 kB]
Get:67 http://ftpmaster.internal/ubuntu/ xenial/main tar ppc64el 1.28-2.1 [222 kB]
Get:68 http://ftpmaster.internal/ubuntu/ xenial/main liblz4-1 ppc64el 0.0~r131-2 [45.5 kB]
Get:69 http://ftpmaster.internal/ubuntu/ xenial/main libgomp1 ppc64el 5.3.1-11ubuntu1 [50.3 kB]
Get:70 http://ftpmaster.internal/ubuntu/ xenial/main libitm1 ppc64el 5.3.1-11ubuntu1 [27.3 kB]
Get:71 http://ftpmaster.internal/ubuntu/ xenial/main libatomic1 ppc64el 5.3.1-11ubuntu1 [7948 B]
Get:72 http://ftpmaster.internal/ubuntu/ xenial/main libasan2 ppc64el 5.3.1-11ubuntu1 [237 kB]
Get:73 http://ftpmaster.internal/ubuntu/ xenial/main libubsan0 ppc64el 5.3.1-11ubuntu1 [96.0 kB]
Get:74 http://ftpmaster.internal/ubuntu/ xenial/main libgmp10 ppc64el 2:6.1.0+dfsg-2 [226 kB]
Get:75 http://ftpmaster.internal/ubuntu/ xenial/main libisl15 ppc64el 0.16.1-1 [507 kB]
Get:76 http://ftpmaster.internal/ubuntu/ xenial/main libmpfr4 ppc64el 3.1.4-1 [185 kB]
Get:77 http://ftpmaster.internal/ubuntu/ xenial/main g++-5 ppc64el 5.3.1-11ubuntu1 [30.2 MB]
Get:78 http://ftpmaster.internal/ubuntu/ xenial/main gcc-5 ppc64el 5.3.1-11ubuntu1 [28.4 MB]
Get:79 http://ftpmaster.internal/ubuntu/ xenial/main cpp-5 ppc64el 5.3.1-11ubuntu1 [28.1 MB]
Get:80 http://ftpmaster.internal/ubuntu/ xenial/main libcc1-0 ppc64el 5.3.1-11ubuntu1 [43.6 kB]
Get:81 http://ftpmaster.internal/ubuntu/ xenial/main binutils ppc64el 2.26-6ubuntu1 [2198 kB]
Get:82 http://ftpmaster.internal/ubuntu/ xenial/main libstdc++-5-dev ppc64el 5.3.1-11ubuntu1 [1418 kB]
Get:83 http://ftpmaster.internal/ubuntu/ xenial/main libgcc-5-dev ppc64el 5.3.1-11ubuntu1 [594 kB]
Get:84 http://ftpmaster.internal/ubuntu/ xenial/main gcc-5-base ppc64el 5.3.1-11ubuntu1 [16.6 kB]
Get:85 http://ftpmaster.internal/ubuntu/ xenial/main libstdc++6 ppc64el 5.3.1-11ubuntu1 [409 kB]
Get:86 http://ftpmaster.internal/ubuntu/ xenial-proposed/main libapt-pkg5.0 ppc64el 1.2.6 [736 kB]
Get:87 http://ftpmaster.internal/ubuntu/ xenial-proposed/main apt ppc64el 1.2.6 [1023 kB]
Get:88 http://ftpmaster.internal/ubuntu/ xenial/main gpgv ppc64el 1.4.20-1ubuntu3 [177 kB]
Get:89 http://ftpmaster.internal/ubuntu/ xenial/main readline-common all 6.3-8ubuntu2 [51.4 kB]
Get:90 http://ftpmaster.internal/ubuntu/ xenial/main libreadline6 ppc64el 6.3-8ubuntu2 [112 kB]
Get:91 http://ftpmaster.internal/ubuntu/ xenial/main libusb-0.1-4 ppc64el 2:0.1.12-28 [15.9 kB]
Get:92 http://ftpmaster.internal/ubuntu/ xenial/main gnupg ppc64el 1.4.20-1ubuntu3 [661 kB]
Get:93 http://ftpmaster.internal/ubuntu/ xenial/main libdebconfclient0 ppc64el 0.198ubuntu1 [6282 B]
Get:94 http://ftpmaster.internal/ubuntu/ xenial/main base-passwd ppc64el 3.5.39 [53.8 kB]
Get:95 http://ftpmaster.internal/ubuntu/ xenial/main ncurses-base all 6.0+20160213-1ubuntu1 [16.7 kB]
Get:96 http://ftpmaster.internal/ubuntu/ xenial/main libdbus-1-3 ppc64el 1.10.6-1ubuntu2 [157 kB]
Get:97 http://ftpmaster.internal/ubuntu/ xenial/main libnih-dbus1 ppc64el 1.0.3-4.3ubuntu1 [13.2 kB]
Get:98 http://ftpmaster.internal/ubuntu/ xenial/main libnih1 ppc64el 1.0.3-4.3ubuntu1 [44.9 kB]
Get:99 http://ftpmaster.internal/ubuntu/ xenial/main libcomerr2 ppc64el 1.42.13-1ubuntu1 [65.6 kB]
Get:100 http://ftpmaster.internal/ubuntu/ xenial/main libdevmapper1.02.1 ppc64el 2:1.02.110-1ubuntu7 [134 kB]
Get:101 http://ftpmaster.internal/ubuntu/ xenial/main libgcrypt20 ppc64el 1.6.5-2 [356 kB]
Get:102 http://ftpmaster.internal/ubuntu/ xenial/main libss2 ppc64el 1.42.13-1ubuntu1 [69.6 kB]
Get:103 http://ftpmaster.internal/ubuntu/ xenial/main multiarch-support ppc64el 2.21-0ubuntu6 [7186 B]
Get:104 http://ftpmaster.internal/ubuntu/ xenial/main libffi6 ppc64el 3.2.1-4 [19.8 kB]
Get:105 http://ftpmaster.internal/ubuntu/ xenial/main libhogweed4 ppc64el 3.2-1 [133 kB]
Get:106 http://ftpmaster.internal/ubuntu/ xenial/main libnettle6 ppc64el 3.2-1 [123 kB]
Get:107 http://ftpmaster.internal/ubuntu/ xenial/main libp11-kit0 ppc64el 0.23.2-3 [105 kB]
Get:108 http://ftpmaster.internal/ubuntu/ xenial/main libpng12-0 ppc64el 1.2.54-1ubuntu1 [120 kB]
Get:109 http://ftpmaster.internal/ubuntu/ xenial/main libsqlite3-0 ppc64el 3.11.0-1ubuntu1 [361 kB]
Get:110 http://ftpmaster.internal/ubuntu/ xenial/main libssl1.0.0 ppc64el 1.0.2g-1ubuntu2 [830 kB]
Get:111 http://ftpmaster.internal/ubuntu/ xenial/main libtasn1-6 ppc64el 4.7-3 [42.9 kB]
Get:112 http://ftpmaster.internal/ubuntu/ xenial/main libidn11 ppc64el 1.32-3ubuntu1 [45.6 kB]
Get:113 http://ftpmaster.internal/ubuntu/ xenial/main libgnutls30 ppc64el 3.4.9-2ubuntu1 [465 kB]
Get:114 http://ftpmaster.internal/ubuntu/ xenial/main libgssapi-krb5-2 ppc64el 1.13.2+dfsg-5 [109 kB]
Get:115 http://ftpmaster.internal/ubuntu/ xenial/main libkrb5-3 ppc64el 1.13.2+dfsg-5 [269 kB]
Get:116 http://ftpmaster.internal/ubuntu/ xenial/main libkrb5support0 ppc64el 1.13.2+dfsg-5 [30.1 kB]
Get:117 http://ftpmaster.internal/ubuntu/ xenial/main libk5crypto3 ppc64el 1.13.2+dfsg-5 [98.3 kB]
Get:118 http://ftpmaster.internal/ubuntu/ xenial/main libkeyutils1 ppc64el 1.5.9-8ubuntu1 [9812 B]
Get:119 http://ftpmaster.internal/ubuntu/ xenial/main libroken18-heimdal ppc64el 1.7~git20150920+dfsg-4ubuntu1 [40.0 kB]
Get:120 http://ftpmaster.internal/ubuntu/ xenial/main libasn1-8-heimdal ppc64el 1.7~git20150920+dfsg-4ubuntu1 [138 kB]
Get:121 http://ftpmaster.internal/ubuntu/ xenial/main libhcrypto4-heimdal ppc64el 1.7~git20150920+dfsg-4ubuntu1 [93.9 kB]
Get:122 http://ftpmaster.internal/ubuntu/ xenial/main libheimbase1-heimdal ppc64el 1.7~git20150920+dfsg-4ubuntu1 [28.6 kB]
Get:123 http://ftpmaster.internal/ubuntu/ xenial/main libwind0-heimdal ppc64el 1.7~git20150920+dfsg-4ubuntu1 [47.9 kB]
Get:124 http://ftpmaster.internal/ubuntu/ xenial/main libhx509-5-heimdal ppc64el 1.7~git20150920+dfsg-4ubuntu1 [102 kB]
Get:125 http://ftpmaster.internal/ubuntu/ xenial/main libkrb5-26-heimdal ppc64el 1.7~git20150920+dfsg-4ubuntu1 [189 kB]
Get:126 http://ftpmaster.internal/ubuntu/ xenial/main libheimntlm0-heimdal ppc64el 1.7~git20150920+dfsg-4ubuntu1 [15.7 kB]
Get:127 http://ftpmaster.internal/ubuntu/ xenial/main libgssapi3-heimdal ppc64el 1.7~git20150920+dfsg-4ubuntu1 [86.4 kB]
Get:128 http://ftpmaster.internal/ubuntu/ xenial/main libldap-2.4-2 ppc64el 2.4.42+dfsg-2ubuntu3 [151 kB]
Get:129 http://ftpmaster.internal/ubuntu/ xenial/main librtmp1 ppc64el 2.4+20151223.gitfa8646d-1build1 [50.8 kB]
Get:130 http://ftpmaster.internal/ubuntu/ xenial/main libcurl3-gnutls ppc64el 7.47.0-1ubuntu2 [176 kB]
Get:131 http://ftpmaster.internal/ubuntu/ xenial-proposed/main apt-transport-https ppc64el 1.2.6 [30.1 kB]
Get:132 http://ftpmaster.internal/ubuntu/ xenial/main openssl ppc64el 1.0.2g-1ubuntu2 [482 kB]
Get:133 http://ftpmaster.internal/ubuntu/ xenial/main ca-certificates all 20160104ubuntu1 [191 kB]
Get:134 http://ftpmaster.internal/ubuntu/ xenial/main advancecomp ppc64el 1.20-1 [201 kB]
Get:135 http://ftpmaster.internal/ubuntu/ xenial/main cpp ppc64el 4:5.3.1-1ubuntu1 [27.6 kB]
Get:136 http://ftpmaster.internal/ubuntu/ xenial/main dmsetup ppc64el 2:1.02.110-1ubuntu7 [57.0 kB]
Get:137 http://ftpmaster.internal/ubuntu/ xenial/main dpkg-dev all 1.18.4ubuntu1 [584 kB]
Get:138 http://ftpmaster.internal/ubuntu/ xenial/main libdpkg-perl all 1.18.4ubuntu1 [195 kB]
Get:139 http://ftpmaster.internal/ubuntu/ xenial/main make ppc64el 4.1-6 [150 kB]
Get:140 http://ftpmaster.internal/ubuntu/ xenial/main gcc ppc64el 4:5.3.1-1ubuntu1 [5240 B]
Get:141 http://ftpmaster.internal/ubuntu/ xenial/main g++ ppc64el 4:5.3.1-1ubuntu1 [1498 B]
Get:142 http://ftpmaster.internal/ubuntu/ xenial/main pkg-create-dbgsym all 0.70 [9046 B]
Get:143 http://ftpmaster.internal/ubuntu/ xenial/main pkgbinarymangler all 129 [43.0 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 133 MB in 4s (31.0 MB/s)
(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 ... 11573 files and directories currently installed.)
Preparing to unpack .../base-files_9.4ubuntu3_ppc64el.deb ...
Unpacking base-files (9.4ubuntu3) over (7.2ubuntu11) ...
Setting up base-files (9.4ubuntu3) ...
Installing new version of config file /etc/debian_version ...
Installing new version of config file /etc/issue ...
Installing new version of config file /etc/issue.net ...
Installing new version of config file /etc/lsb-release ...
Updating /etc/profile to current default.
Updating /etc/nsswitch.conf to current default.
Updating /root/.profile to current default.
(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 ... 11575 files and directories currently installed.)
Preparing to unpack .../bsdutils_1%3a2.27.1-4ubuntu1_ppc64el.deb ...
Unpacking bsdutils (1:2.27.1-4ubuntu1) over (1:2.26.2-6ubuntu3) ...
Setting up bsdutils (1:2.27.1-4ubuntu1) ...
(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 ... 11574 files and directories currently installed.)
Preparing to unpack .../coreutils_8.25-2ubuntu2_ppc64el.deb ...
Unpacking coreutils (8.25-2ubuntu2) over (8.23-4ubuntu2) ...
Setting up coreutils (8.25-2ubuntu2) ...
(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 ... 11575 files and directories currently installed.)
Preparing to unpack .../debianutils_4.7_ppc64el.deb ...
Unpacking debianutils (4.7) over (4.5.1) ...
Setting up debianutils (4.7) ...
(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 ... 11575 files and directories currently installed.)
Preparing to unpack .../dpkg_1.18.4ubuntu1_ppc64el.deb ...
Unpacking dpkg (1.18.4ubuntu1) over (1.18.2ubuntu5) ...
Setting up dpkg (1.18.4ubuntu1) ...
(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 ... 11575 files and directories currently installed.)
Preparing to unpack .../dash_0.5.8-2.1ubuntu2_ppc64el.deb ...
Unpacking dash (0.5.8-2.1ubuntu2) over (0.5.7-4ubuntu2) ...
Setting up dash (0.5.8-2.1ubuntu2) ...
(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 ... 11575 files and directories currently installed.)
Preparing to unpack .../diffutils_1%3a3.3-3_ppc64el.deb ...
Unpacking diffutils (1:3.3-3) over (1:3.3-1) ...
Setting up diffutils (1:3.3-3) ...
(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 ... 11575 files and directories currently installed.)
Preparing to unpack .../libc6-dev_2.21-0ubuntu6_ppc64el.deb ...
Unpacking libc6-dev:ppc64el (2.21-0ubuntu6) over (2.21-0ubuntu4) ...
Preparing to unpack .../libc-dev-bin_2.21-0ubuntu6_ppc64el.deb ...
Unpacking libc-dev-bin (2.21-0ubuntu6) over (2.21-0ubuntu4) ...
Preparing to unpack .../linux-libc-dev_4.4.0-13.29_ppc64el.deb ...
Unpacking linux-libc-dev:ppc64el (4.4.0-13.29) over (4.2.0-16.19) ...
Preparing to unpack .../libcap2_1%3a2.24-12_ppc64el.deb ...
Unpacking libcap2:ppc64el (1:2.24-12) over (1:2.24-9) ...
Setting up libcap2:ppc64el (1:2.24-12) ...
Processing triggers for libc-bin (2.21-0ubuntu4) ...
(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 ... 11585 files and directories currently installed.)
Preparing to unpack .../libc-bin_2.21-0ubuntu6_ppc64el.deb ...
Unpacking libc-bin (2.21-0ubuntu6) over (2.21-0ubuntu4) ...
Setting up libc-bin (2.21-0ubuntu6) ...
Selecting previously unselected package gcc-6-base:ppc64el.
(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 ... 11585 files and directories currently installed.)
Preparing to unpack .../gcc-6-base_6-20160313-0ubuntu1_ppc64el.deb ...
Unpacking gcc-6-base:ppc64el (6-20160313-0ubuntu1) ...
Setting up gcc-6-base:ppc64el (6-20160313-0ubuntu1) ...
(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 ... 11592 files and directories currently installed.)
Preparing to unpack .../libgcc1_1%3a6-20160313-0ubuntu1_ppc64el.deb ...
Unpacking libgcc1:ppc64el (1:6-20160313-0ubuntu1) over (1:5.2.1-22ubuntu2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libgcc1:ppc64el (1:6-20160313-0ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 11592 files and directories currently installed.)
Preparing to unpack .../libc6_2.21-0ubuntu6_ppc64el.deb ...
Unpacking libc6:ppc64el (2.21-0ubuntu6) over (2.21-0ubuntu4) ...
Setting up libc6:ppc64el (2.21-0ubuntu6) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 11592 files and directories currently installed.)
Preparing to unpack .../e2fslibs_1.42.13-1ubuntu1_ppc64el.deb ...
Unpacking e2fslibs:ppc64el (1.42.13-1ubuntu1) over (1.42.12-1ubuntu2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up e2fslibs:ppc64el (1.42.13-1ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 11592 files and directories currently installed.)
Preparing to unpack .../e2fsprogs_1.42.13-1ubuntu1_ppc64el.deb ...
Unpacking e2fsprogs (1.42.13-1ubuntu1) over (1.42.12-1ubuntu2) ...
Setting up e2fsprogs (1.42.13-1ubuntu1) ...
Installing new version of config file /etc/mke2fs.conf ...
(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 ... 11593 files and directories currently installed.)
Preparing to unpack .../findutils_4.6.0+git+20160126-2_ppc64el.deb ...
Unpacking findutils (4.6.0+git+20160126-2) over (4.4.2-9build1) ...
Setting up findutils (4.6.0+git+20160126-2) ...
(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 ... 11592 files and directories currently installed.)
Preparing to unpack .../grep_2.23-1_ppc64el.deb ...
Unpacking grep (2.23-1) over (2.21-2) ...
Setting up grep (2.23-1) ...
(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 ... 11592 files and directories currently installed.)
Preparing to unpack .../hostname_3.16ubuntu2_ppc64el.deb ...
Unpacking hostname (3.16ubuntu2) over (3.15ubuntu2) ...
Setting up hostname (3.16ubuntu2) ...
(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 ... 11592 files and directories currently installed.)
Preparing to unpack .../sysvinit-utils_2.88dsf-59.3ubuntu2_ppc64el.deb ...
Unpacking sysvinit-utils (2.88dsf-59.3ubuntu2) over (2.88dsf-59.2ubuntu2) ...
Selecting previously unselected package init-system-helpers.
Preparing to unpack .../init-system-helpers_1.29ubuntu1_all.deb ...
Unpacking init-system-helpers (1.29ubuntu1) ...
Replacing files in old package sysv-rc (2.88dsf-59.2ubuntu2) ...
Setting up init-system-helpers (1.29ubuntu1) ...
dpkg: perl-modules: dependency problems, but removing anyway as you requested:
 perl depends on perl-modules (>= 5.20.2-6).

(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 ... 11600 files and directories currently installed.)
Removing perl-modules (5.20.2-6) ...
Purging configuration files for perl-modules (5.20.2-6) ...
(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 ... 10872 files and directories currently installed.)
Preparing to unpack .../perl_5.22.1-8_ppc64el.deb ...
Unpacking perl (5.22.1-8) over (5.20.2-6) ...
Selecting previously unselected package perl-modules-5.22.
Preparing to unpack .../perl-modules-5.22_5.22.1-8_all.deb ...
Unpacking perl-modules-5.22 (5.22.1-8) ...
Selecting previously unselected package libperl5.22:ppc64el.
Preparing to unpack .../libperl5.22_5.22.1-8_ppc64el.deb ...
Unpacking libperl5.22:ppc64el (5.22.1-8) ...
Preparing to unpack .../perl-base_5.22.1-8_ppc64el.deb ...
Unpacking perl-base (5.22.1-8) over (5.20.2-6) ...
Setting up perl-base (5.22.1-8) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../init_1.29ubuntu1_ppc64el.deb ...
Unpacking init (1.29ubuntu1) over (1.23ubuntu3) ...
Setting up init (1.29ubuntu1) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../login_1%3a4.2-3.1ubuntu4_ppc64el.deb ...
Unpacking login (1:4.2-3.1ubuntu4) over (1:4.1.5.1-1.1ubuntu7) ...
Setting up login (1:4.2-3.1ubuntu4) ...
Installing new version of config file /etc/pam.d/login ...
Installing new version of config file /etc/pam.d/su ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libsmartcols1_2.27.1-4ubuntu1_ppc64el.deb ...
Unpacking libsmartcols1:ppc64el (2.27.1-4ubuntu1) over (2.26.2-6ubuntu3) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libsmartcols1:ppc64el (2.27.1-4ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libaudit-common_1%3a2.4.5-1ubuntu2_all.deb ...
Unpacking libaudit-common (1:2.4.5-1ubuntu2) over (1:2.4.2-1ubuntu1) ...
Setting up libaudit-common (1:2.4.5-1ubuntu2) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libaudit1_1%3a2.4.5-1ubuntu2_ppc64el.deb ...
Unpacking libaudit1:ppc64el (1:2.4.5-1ubuntu2) over (1:2.4.2-1ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libaudit1:ppc64el (1:2.4.5-1ubuntu2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libpcre3_2%3a8.38-3_ppc64el.deb ...
Unpacking libpcre3:ppc64el (2:8.38-3) over (2:8.35-7.1ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libpcre3:ppc64el (2:8.38-3) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libselinux1_2.4-3build1_ppc64el.deb ...
Unpacking libselinux1:ppc64el (2.4-3build1) over (2.3-2build1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libselinux1:ppc64el (2.4-3build1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libsepol1_2.4-2_ppc64el.deb ...
Unpacking libsepol1:ppc64el (2.4-2) over (2.3-2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libsepol1:ppc64el (2.4-2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libsemanage-common_2.4-3build1_all.deb ...
Unpacking libsemanage-common (2.4-3build1) over (2.3-1build2) ...
Setting up libsemanage-common (2.4-3build1) ...
Installing new version of config file /etc/selinux/semanage.conf ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libsemanage1_2.4-3build1_ppc64el.deb ...
Unpacking libsemanage1:ppc64el (2.4-3build1) over (2.3-1build2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libsemanage1:ppc64el (2.4-3build1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libfdisk1_2.27.1-4ubuntu1_ppc64el.deb ...
Unpacking libfdisk1:ppc64el (2.27.1-4ubuntu1) over (2.26.2-6ubuntu3) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libfdisk1:ppc64el (2.27.1-4ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libtinfo5_6.0+20160213-1ubuntu1_ppc64el.deb ...
Unpacking libtinfo5:ppc64el (6.0+20160213-1ubuntu1) over (5.9+20150516-2ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libtinfo5:ppc64el (6.0+20160213-1ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libncurses5_6.0+20160213-1ubuntu1_ppc64el.deb ...
Unpacking libncurses5:ppc64el (6.0+20160213-1ubuntu1) over (5.9+20150516-2ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libncurses5:ppc64el (6.0+20160213-1ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../libncursesw5_6.0+20160213-1ubuntu1_ppc64el.deb ...
Unpacking libncursesw5:ppc64el (6.0+20160213-1ubuntu1) over (5.9+20150516-2ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libncursesw5:ppc64el (6.0+20160213-1ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12183 files and directories currently installed.)
Preparing to unpack .../sysv-rc_2.88dsf-59.3ubuntu2_all.deb ...
Unpacking sysv-rc (2.88dsf-59.3ubuntu2) over (2.88dsf-59.2ubuntu2) ...
Setting up sysvinit-utils (2.88dsf-59.3ubuntu2) ...
Setting up sysv-rc (2.88dsf-59.3ubuntu2) ...
Processing triggers for systemd (225-1ubuntu9) ...
(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 ... 12181 files and directories currently installed.)
Preparing to unpack .../libsystemd0_229-2ubuntu1_ppc64el.deb ...
Unpacking libsystemd0:ppc64el (229-2ubuntu1) over (225-1ubuntu9) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libsystemd0:ppc64el (229-2ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12181 files and directories currently installed.)
Preparing to unpack .../util-linux_2.27.1-4ubuntu1_ppc64el.deb ...
Unpacking util-linux (2.27.1-4ubuntu1) over (2.26.2-6ubuntu3) ...
Setting up util-linux (2.27.1-4ubuntu1) ...
Installing new version of config file /etc/init.d/hwclock.sh ...
Installing new version of config file /etc/init/hwclock-save.conf ...
Installing new version of config file /etc/init/hwclock.conf ...
(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 ... 12189 files and directories currently installed.)
Preparing to unpack .../libudev1_229-2ubuntu1_ppc64el.deb ...
Unpacking libudev1:ppc64el (229-2ubuntu1) over (225-1ubuntu9) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libudev1:ppc64el (229-2ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12189 files and directories currently installed.)
Preparing to unpack .../udev_229-2ubuntu1_ppc64el.deb ...
Unpacking udev (229-2ubuntu1) over (225-1ubuntu9) ...
Preparing to unpack .../systemd_229-2ubuntu1_ppc64el.deb ...
Unpacking systemd (229-2ubuntu1) over (225-1ubuntu9) ...
Setting up systemd (229-2ubuntu1) ...
Installing new version of config file /etc/pam.d/systemd-user ...
Installing new version of config file /etc/systemd/journald.conf ...
Installing new version of config file /etc/systemd/logind.conf ...
Installing new version of config file /etc/systemd/resolved.conf ...
Installing new version of config file /etc/systemd/system.conf ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
Removing obsolete conffile /etc/X11/xinit/xinitrc.d/50-systemd-user.sh ...
(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 ... 12189 files and directories currently installed.)
Preparing to unpack .../initscripts_2.88dsf-59.3ubuntu2_ppc64el.deb ...
Unpacking initscripts (2.88dsf-59.3ubuntu2) over (2.88dsf-59.2ubuntu2) ...
Processing triggers for systemd (229-2ubuntu1) ...
Setting up initscripts (2.88dsf-59.3ubuntu2) ...
Installing new version of config file /etc/init.d/checkfs.sh ...
Installing new version of config file /etc/init.d/checkroot.sh ...
Installing new version of config file /etc/init.d/mountall.sh ...
Installing new version of config file /etc/default/rcS ...
Processing triggers for systemd (229-2ubuntu1) ...
(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 ... 12189 files and directories currently installed.)
Preparing to unpack .../libacl1_2.2.52-3_ppc64el.deb ...
Unpacking libacl1:ppc64el (2.2.52-3) over (2.2.52-2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libacl1:ppc64el (2.2.52-3) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12189 files and directories currently installed.)
Preparing to unpack .../libkmod2_22-1ubuntu4_ppc64el.deb ...
Unpacking libkmod2:ppc64el (22-1ubuntu4) over (21-1ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libkmod2:ppc64el (22-1ubuntu4) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Selecting previously unselected package libprocps4:ppc64el.
(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 ... 12189 files and directories currently installed.)
Preparing to unpack .../libprocps4_2%3a3.3.10-4ubuntu2_ppc64el.deb ...
Unpacking libprocps4:ppc64el (2:3.3.10-4ubuntu2) ...
Preparing to unpack .../debconf_1.5.58ubuntu1_all.deb ...
Unpacking debconf (1.5.58ubuntu1) over (1.5.57ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up debconf (1.5.58ubuntu1) ...
Removing obsolete conffile /etc/bash_completion.d/debconf ...
(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 ... 12196 files and directories currently installed.)
Preparing to unpack .../procps_2%3a3.3.10-4ubuntu2_ppc64el.deb ...
Running in chroot, ignoring request.
invoke-rc.d: policy-rc.d denied execution of stop.
Unpacking procps (2:3.3.10-4ubuntu2) over (1:3.3.9-1ubuntu8) ...
Preparing to unpack .../libapparmor1_2.10-3ubuntu2_ppc64el.deb ...
Unpacking libapparmor1:ppc64el (2.10-3ubuntu2) over (2.10-0ubuntu6) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libapparmor1:ppc64el (2.10-3ubuntu2) ...
Processing triggers for systemd (229-2ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12199 files and directories currently installed.)
Preparing to unpack .../libgpg-error0_1.21-2ubuntu1_ppc64el.deb ...
Unpacking libgpg-error0:ppc64el (1.21-2ubuntu1) over (1.19-2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libgpg-error0:ppc64el (1.21-2ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12199 files and directories currently installed.)
Preparing to unpack .../libmount1_2.27.1-4ubuntu1_ppc64el.deb ...
Unpacking libmount1:ppc64el (2.27.1-4ubuntu1) over (2.26.2-6ubuntu3) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libmount1:ppc64el (2.27.1-4ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12199 files and directories currently installed.)
Preparing to unpack .../libseccomp2_2.2.3-3ubuntu1_ppc64el.deb ...
Unpacking libseccomp2:ppc64el (2.2.3-3ubuntu1) over (2.2.3-2ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libseccomp2:ppc64el (2.2.3-3ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12199 files and directories currently installed.)
Preparing to unpack .../libcap2-bin_1%3a2.24-12_ppc64el.deb ...
Unpacking libcap2-bin (1:2.24-12) over (1:2.24-9) ...
Setting up libcap2-bin (1:2.24-12) ...
(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 ... 12199 files and directories currently installed.)
Preparing to unpack .../lsb-base_9.20160110_all.deb ...
Unpacking lsb-base (9.20160110) over (4.1+Debian11ubuntu8) ...
Setting up lsb-base (9.20160110) ...
(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 ... 12199 files and directories currently installed.)
Preparing to unpack .../passwd_1%3a4.2-3.1ubuntu4_ppc64el.deb ...
Unpacking passwd (1:4.2-3.1ubuntu4) over (1:4.1.5.1-1.1ubuntu7) ...
Setting up passwd (1:4.2-3.1ubuntu4) ...
Installing new version of config file /etc/init/passwd.conf ...
(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 ... 12201 files and directories currently installed.)
Preparing to unpack .../libuuid1_2.27.1-4ubuntu1_ppc64el.deb ...
Unpacking libuuid1:ppc64el (2.27.1-4ubuntu1) over (2.26.2-6ubuntu3) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libuuid1:ppc64el (2.27.1-4ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12201 files and directories currently installed.)
Preparing to unpack .../libblkid1_2.27.1-4ubuntu1_ppc64el.deb ...
Unpacking libblkid1:ppc64el (2.27.1-4ubuntu1) over (2.26.2-6ubuntu3) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libblkid1:ppc64el (2.27.1-4ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12201 files and directories currently installed.)
Preparing to unpack .../tzdata_2016a-1_all.deb ...
Unpacking tzdata (2016a-1) over (2015g-1) ...
Setting up tzdata (2016a-1) ...

Current default time zone: 'Etc/UTC'
Local time is now:      Sun Mar 13 22:48:50 UTC 2016.
Universal Time is now:  Sun Mar 13 22:48:50 UTC 2016.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

(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 ... 12201 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_229-2ubuntu1_ppc64el.deb ...
Unpacking systemd-sysv (229-2ubuntu1) over (225-1ubuntu9) ...
Setting up systemd-sysv (229-2ubuntu1) ...
(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 ... 12201 files and directories currently installed.)
Preparing to unpack .../mount_2.27.1-4ubuntu1_ppc64el.deb ...
Unpacking mount (2.27.1-4ubuntu1) over (2.26.2-6ubuntu3) ...
Setting up mount (2.27.1-4ubuntu1) ...
(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 ... 12201 files and directories currently installed.)
Preparing to unpack .../ncurses-bin_6.0+20160213-1ubuntu1_ppc64el.deb ...
Unpacking ncurses-bin (6.0+20160213-1ubuntu1) over (5.9+20150516-2ubuntu1) ...
Setting up ncurses-bin (6.0+20160213-1ubuntu1) ...
(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 ... 12197 files and directories currently installed.)
Preparing to unpack .../sed_4.2.2-7_ppc64el.deb ...
Unpacking sed (4.2.2-7) over (4.2.2-6.1) ...
Setting up sed (4.2.2-7) ...
(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 ... 12197 files and directories currently installed.)
Preparing to unpack .../tar_1.28-2.1_ppc64el.deb ...
Unpacking tar (1.28-2.1) over (1.27.1-2) ...
Setting up tar (1.28-2.1) ...
Selecting previously unselected package liblz4-1:ppc64el.
(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 ... 12197 files and directories currently installed.)
Preparing to unpack .../liblz4-1_0.0~r131-2_ppc64el.deb ...
Unpacking liblz4-1:ppc64el (0.0~r131-2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up liblz4-1:ppc64el (0.0~r131-2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12202 files and directories currently installed.)
Preparing to unpack .../libgomp1_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking libgomp1:ppc64el (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Preparing to unpack .../libitm1_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking libitm1:ppc64el (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Preparing to unpack .../libatomic1_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking libatomic1:ppc64el (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Preparing to unpack .../libasan2_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking libasan2:ppc64el (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Preparing to unpack .../libubsan0_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking libubsan0:ppc64el (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Preparing to unpack .../libgmp10_2%3a6.1.0+dfsg-2_ppc64el.deb ...
Unpacking libgmp10:ppc64el (2:6.1.0+dfsg-2) over (2:6.0.0+dfsg-7) ...
Selecting previously unselected package libisl15:ppc64el.
Preparing to unpack .../libisl15_0.16.1-1_ppc64el.deb ...
Unpacking libisl15:ppc64el (0.16.1-1) ...
Preparing to unpack .../libmpfr4_3.1.4-1_ppc64el.deb ...
Unpacking libmpfr4:ppc64el (3.1.4-1) over (3.1.3-1) ...
Preparing to unpack .../g++-5_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking g++-5 (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Preparing to unpack .../gcc-5_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking gcc-5 (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Preparing to unpack .../cpp-5_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking cpp-5 (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Preparing to unpack .../libcc1-0_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking libcc1-0:ppc64el (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Preparing to unpack .../binutils_2.26-6ubuntu1_ppc64el.deb ...
Unpacking binutils (2.26-6ubuntu1) over (2.25.1-6ubuntu1) ...
Preparing to unpack .../libstdc++-5-dev_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking libstdc++-5-dev:ppc64el (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Preparing to unpack .../libgcc-5-dev_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking libgcc-5-dev:ppc64el (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Preparing to unpack .../gcc-5-base_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking gcc-5-base:ppc64el (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up gcc-5-base:ppc64el (5.3.1-11ubuntu1) ...
(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 ... 12172 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.3.1-11ubuntu1_ppc64el.deb ...
Unpacking libstdc++6:ppc64el (5.3.1-11ubuntu1) over (5.2.1-22ubuntu2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libstdc++6:ppc64el (5.3.1-11ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12172 files and directories currently installed.)
Preparing to unpack .../archives/apt_1.2.6_ppc64el.deb ...
Unpacking apt (1.2.6) over (1.0.10.2ubuntu1) ...
Selecting previously unselected package libapt-pkg5.0:ppc64el.
Preparing to unpack .../libapt-pkg5.0_1.2.6_ppc64el.deb ...
Unpacking libapt-pkg5.0:ppc64el (1.2.6) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libapt-pkg5.0:ppc64el (1.2.6) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12205 files and directories currently installed.)
Preparing to unpack .../gpgv_1.4.20-1ubuntu3_ppc64el.deb ...
Unpacking gpgv (1.4.20-1ubuntu3) over (1.4.18-7ubuntu1) ...
Setting up gpgv (1.4.20-1ubuntu3) ...
(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 ... 12205 files and directories currently installed.)
Preparing to unpack .../readline-common_6.3-8ubuntu2_all.deb ...
Unpacking readline-common (6.3-8ubuntu2) over (6.3-8ubuntu1) ...
Setting up readline-common (6.3-8ubuntu2) ...
(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 ... 12205 files and directories currently installed.)
Preparing to unpack .../libreadline6_6.3-8ubuntu2_ppc64el.deb ...
Unpacking libreadline6:ppc64el (6.3-8ubuntu2) over (6.3-8ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libreadline6:ppc64el (6.3-8ubuntu2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12205 files and directories currently installed.)
Preparing to unpack .../libusb-0.1-4_2%3a0.1.12-28_ppc64el.deb ...
Unpacking libusb-0.1-4:ppc64el (2:0.1.12-28) over (2:0.1.12-27) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libusb-0.1-4:ppc64el (2:0.1.12-28) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12204 files and directories currently installed.)
Preparing to unpack .../gnupg_1.4.20-1ubuntu3_ppc64el.deb ...
Unpacking gnupg (1.4.20-1ubuntu3) over (1.4.18-7ubuntu1) ...
Setting up gnupg (1.4.20-1ubuntu3) ...
(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 ... 12203 files and directories currently installed.)
Preparing to unpack .../libdebconfclient0_0.198ubuntu1_ppc64el.deb ...
Unpacking libdebconfclient0:ppc64el (0.198ubuntu1) over (0.192ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libdebconfclient0:ppc64el (0.198ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12203 files and directories currently installed.)
Preparing to unpack .../base-passwd_3.5.39_ppc64el.deb ...
Unpacking base-passwd (3.5.39) over (3.5.38) ...
Setting up base-passwd (3.5.39) ...
(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 ... 12203 files and directories currently installed.)
Preparing to unpack .../ncurses-base_6.0+20160213-1ubuntu1_all.deb ...
Unpacking ncurses-base (6.0+20160213-1ubuntu1) over (5.9+20150516-2ubuntu1) ...
Setting up ncurses-base (6.0+20160213-1ubuntu1) ...
(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 ... 12204 files and directories currently installed.)
Preparing to unpack .../libdbus-1-3_1.10.6-1ubuntu2_ppc64el.deb ...
Unpacking libdbus-1-3:ppc64el (1.10.6-1ubuntu2) over (1.10.0-1ubuntu1) ...
Preparing to unpack .../libnih-dbus1_1.0.3-4.3ubuntu1_ppc64el.deb ...
Unpacking libnih-dbus1:ppc64el (1.0.3-4.3ubuntu1) over (1.0.3-4ubuntu27) ...
Preparing to unpack .../libnih1_1.0.3-4.3ubuntu1_ppc64el.deb ...
Unpacking libnih1:ppc64el (1.0.3-4.3ubuntu1) over (1.0.3-4ubuntu27) ...
Preparing to unpack .../libcomerr2_1.42.13-1ubuntu1_ppc64el.deb ...
Unpacking libcomerr2:ppc64el (1.42.13-1ubuntu1) over (1.42.12-1ubuntu2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libcomerr2:ppc64el (1.42.13-1ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12204 files and directories currently installed.)
Preparing to unpack .../libdevmapper1.02.1_2%3a1.02.110-1ubuntu7_ppc64el.deb ...
Unpacking libdevmapper1.02.1:ppc64el (2:1.02.110-1ubuntu7) over (2:1.02.99-1ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libdevmapper1.02.1:ppc64el (2:1.02.110-1ubuntu7) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12204 files and directories currently installed.)
Preparing to unpack .../libgcrypt20_1.6.5-2_ppc64el.deb ...
Unpacking libgcrypt20:ppc64el (1.6.5-2) over (1.6.3-2ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libgcrypt20:ppc64el (1.6.5-2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12204 files and directories currently installed.)
Preparing to unpack .../libss2_1.42.13-1ubuntu1_ppc64el.deb ...
Unpacking libss2:ppc64el (1.42.13-1ubuntu1) over (1.42.12-1ubuntu2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libss2:ppc64el (1.42.13-1ubuntu1) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
(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 ... 12204 files and directories currently installed.)
Preparing to unpack .../multiarch-support_2.21-0ubuntu6_ppc64el.deb ...
Unpacking multiarch-support (2.21-0ubuntu6) over (2.21-0ubuntu4) ...
Setting up multiarch-support (2.21-0ubuntu6) ...
(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 ... 12204 files and directories currently installed.)
Preparing to unpack .../libffi6_3.2.1-4_ppc64el.deb ...
Unpacking libffi6:ppc64el (3.2.1-4) over (3.2.1-3) ...
Preparing to unpack .../libhogweed4_3.2-1_ppc64el.deb ...
Unpacking libhogweed4:ppc64el (3.2-1) over (3.1.1-4) ...
Preparing to unpack .../libnettle6_3.2-1_ppc64el.deb ...
Unpacking libnettle6:ppc64el (3.2-1) over (3.1.1-4) ...
Preparing to unpack .../libp11-kit0_0.23.2-3_ppc64el.deb ...
Unpacking libp11-kit0:ppc64el (0.23.2-3) over (0.23.1-3) ...
Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1_ppc64el.deb ...
Unpacking libpng12-0:ppc64el (1.2.54-1ubuntu1) over (1.2.51-0ubuntu3) ...
Preparing to unpack .../libsqlite3-0_3.11.0-1ubuntu1_ppc64el.deb ...
Unpacking libsqlite3-0:ppc64el (3.11.0-1ubuntu1) over (3.8.11.1-1) ...
Preparing to unpack .../libssl1.0.0_1.0.2g-1ubuntu2_ppc64el.deb ...
Unpacking libssl1.0.0:ppc64el (1.0.2g-1ubuntu2) over (1.0.2d-0ubuntu1) ...
Preparing to unpack .../libtasn1-6_4.7-3_ppc64el.deb ...
Unpacking libtasn1-6:ppc64el (4.7-3) over (4.5-2) ...
Preparing to unpack .../libidn11_1.32-3ubuntu1_ppc64el.deb ...
Unpacking libidn11:ppc64el (1.32-3ubuntu1) over (1.28-1ubuntu2) ...
Selecting previously unselected package libgnutls30:ppc64el.
Preparing to unpack .../libgnutls30_3.4.9-2ubuntu1_ppc64el.deb ...
Unpacking libgnutls30:ppc64el (3.4.9-2ubuntu1) ...
Preparing to unpack .../libgssapi-krb5-2_1.13.2+dfsg-5_ppc64el.deb ...
Unpacking libgssapi-krb5-2:ppc64el (1.13.2+dfsg-5) over (1.13.2+dfsg-2) ...
Preparing to unpack .../libkrb5-3_1.13.2+dfsg-5_ppc64el.deb ...
Unpacking libkrb5-3:ppc64el (1.13.2+dfsg-5) over (1.13.2+dfsg-2) ...
Preparing to unpack .../libkrb5support0_1.13.2+dfsg-5_ppc64el.deb ...
Unpacking libkrb5support0:ppc64el (1.13.2+dfsg-5) over (1.13.2+dfsg-2) ...
Preparing to unpack .../libk5crypto3_1.13.2+dfsg-5_ppc64el.deb ...
Unpacking libk5crypto3:ppc64el (1.13.2+dfsg-5) over (1.13.2+dfsg-2) ...
Preparing to unpack .../libkeyutils1_1.5.9-8ubuntu1_ppc64el.deb ...
Unpacking libkeyutils1:ppc64el (1.5.9-8ubuntu1) over (1.5.9-5ubuntu1) ...
Preparing to unpack .../libroken18-heimdal_1.7~git20150920+dfsg-4ubuntu1_ppc64el.deb ...
Unpacking libroken18-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) over (1.6~rc2+dfsg-10ubuntu1) ...
Preparing to unpack .../libasn1-8-heimdal_1.7~git20150920+dfsg-4ubuntu1_ppc64el.deb ...
Unpacking libasn1-8-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) over (1.6~rc2+dfsg-10ubuntu1) ...
Preparing to unpack .../libhcrypto4-heimdal_1.7~git20150920+dfsg-4ubuntu1_ppc64el.deb ...
Unpacking libhcrypto4-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) over (1.6~rc2+dfsg-10ubuntu1) ...
Preparing to unpack .../libheimbase1-heimdal_1.7~git20150920+dfsg-4ubuntu1_ppc64el.deb ...
Unpacking libheimbase1-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) over (1.6~rc2+dfsg-10ubuntu1) ...
Preparing to unpack .../libwind0-heimdal_1.7~git20150920+dfsg-4ubuntu1_ppc64el.deb ...
Unpacking libwind0-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) over (1.6~rc2+dfsg-10ubuntu1) ...
Preparing to unpack .../libhx509-5-heimdal_1.7~git20150920+dfsg-4ubuntu1_ppc64el.deb ...
Unpacking libhx509-5-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) over (1.6~rc2+dfsg-10ubuntu1) ...
Preparing to unpack .../libkrb5-26-heimdal_1.7~git20150920+dfsg-4ubuntu1_ppc64el.deb ...
Unpacking libkrb5-26-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) over (1.6~rc2+dfsg-10ubuntu1) ...
Preparing to unpack .../libheimntlm0-heimdal_1.7~git20150920+dfsg-4ubuntu1_ppc64el.deb ...
Unpacking libheimntlm0-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) over (1.6~rc2+dfsg-10ubuntu1) ...
Preparing to unpack .../libgssapi3-heimdal_1.7~git20150920+dfsg-4ubuntu1_ppc64el.deb ...
Unpacking libgssapi3-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) over (1.6~rc2+dfsg-10ubuntu1) ...
Preparing to unpack .../libldap-2.4-2_2.4.42+dfsg-2ubuntu3_ppc64el.deb ...
Unpacking libldap-2.4-2:ppc64el (2.4.42+dfsg-2ubuntu3) over (2.4.41+dfsg-1ubuntu2) ...
Preparing to unpack .../librtmp1_2.4+20151223.gitfa8646d-1build1_ppc64el.deb ...
Unpacking librtmp1:ppc64el (2.4+20151223.gitfa8646d-1build1) over (2.4+20150115.gita107cef-1build1) ...
Preparing to unpack .../libcurl3-gnutls_7.47.0-1ubuntu2_ppc64el.deb ...
Unpacking libcurl3-gnutls:ppc64el (7.47.0-1ubuntu2) over (7.43.0-1ubuntu2) ...
Preparing to unpack .../apt-transport-https_1.2.6_ppc64el.deb ...
Unpacking apt-transport-https (1.2.6) over (1.0.10.2ubuntu1) ...
Preparing to unpack .../openssl_1.0.2g-1ubuntu2_ppc64el.deb ...
Unpacking openssl (1.0.2g-1ubuntu2) over (1.0.2d-0ubuntu1) ...
Preparing to unpack .../ca-certificates_20160104ubuntu1_all.deb ...
Unpacking ca-certificates (20160104ubuntu1) over (20150426ubuntu1) ...
Preparing to unpack .../advancecomp_1.20-1_ppc64el.deb ...
Unpacking advancecomp (1.20-1) over (1.19-1) ...
Preparing to unpack .../cpp_4%3a5.3.1-1ubuntu1_ppc64el.deb ...
Unpacking cpp (4:5.3.1-1ubuntu1) over (4:5.2.1-3ubuntu1) ...
Preparing to unpack .../dmsetup_2%3a1.02.110-1ubuntu7_ppc64el.deb ...
Unpacking dmsetup (2:1.02.110-1ubuntu7) over (2:1.02.99-1ubuntu1) ...
Preparing to unpack .../dpkg-dev_1.18.4ubuntu1_all.deb ...
Unpacking dpkg-dev (1.18.4ubuntu1) over (1.18.2ubuntu5) ...
Preparing to unpack .../libdpkg-perl_1.18.4ubuntu1_all.deb ...
Unpacking libdpkg-perl (1.18.4ubuntu1) over (1.18.2ubuntu5) ...
Preparing to unpack .../make_4.1-6_ppc64el.deb ...
Unpacking make (4.1-6) over (4.0-8.2) ...
Preparing to unpack .../gcc_4%3a5.3.1-1ubuntu1_ppc64el.deb ...
Removing old gcc doc directory.
Unpacking gcc (4:5.3.1-1ubuntu1) over (4:5.2.1-3ubuntu1) ...
Preparing to unpack .../g++_4%3a5.3.1-1ubuntu1_ppc64el.deb ...
Unpacking g++ (4:5.3.1-1ubuntu1) over (4:5.2.1-3ubuntu1) ...
Preparing to unpack .../pkg-create-dbgsym_0.70_all.deb ...
Unpacking pkg-create-dbgsym (0.70) over (0.69) ...
Preparing to unpack .../pkgbinarymangler_129_all.deb ...
Unpacking pkgbinarymangler (129) over (122) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libc-dev-bin (2.21-0ubuntu6) ...
Setting up linux-libc-dev:ppc64el (4.4.0-13.29) ...
Setting up libc6-dev:ppc64el (2.21-0ubuntu6) ...
Setting up perl-modules-5.22 (5.22.1-8) ...
Setting up libperl5.22:ppc64el (5.22.1-8) ...
Setting up perl (5.22.1-8) ...
Setting up libprocps4:ppc64el (2:3.3.10-4ubuntu2) ...
Setting up procps (2:3.3.10-4ubuntu2) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Running in chroot, ignoring request.
invoke-rc.d: policy-rc.d denied execution of start.
Setting up udev (229-2ubuntu1) ...
Installing new version of config file /etc/init.d/udev ...
addgroup: The group `input' already exists as a system group. Exiting.
virtio network devices detected, disabling predictable interface names in /etc/systemd/network/50-virtio-kernel-names.link
A chroot environment has been detected, udev not started.
Removing obsolete conffile /etc/init.d/lvm2 ...
Setting up libgomp1:ppc64el (5.3.1-11ubuntu1) ...
Setting up libitm1:ppc64el (5.3.1-11ubuntu1) ...
Setting up libatomic1:ppc64el (5.3.1-11ubuntu1) ...
Setting up libasan2:ppc64el (5.3.1-11ubuntu1) ...
Setting up libubsan0:ppc64el (5.3.1-11ubuntu1) ...
Setting up libgmp10:ppc64el (2:6.1.0+dfsg-2) ...
Setting up libisl15:ppc64el (0.16.1-1) ...
Setting up libmpfr4:ppc64el (3.1.4-1) ...
Setting up cpp-5 (5.3.1-11ubuntu1) ...
Setting up libcc1-0:ppc64el (5.3.1-11ubuntu1) ...
Setting up binutils (2.26-6ubuntu1) ...
Setting up libgcc-5-dev:ppc64el (5.3.1-11ubuntu1) ...
Setting up gcc-5 (5.3.1-11ubuntu1) ...
Setting up libstdc++-5-dev:ppc64el (5.3.1-11ubuntu1) ...
Setting up g++-5 (5.3.1-11ubuntu1) ...
Setting up apt (1.2.6) ...
Installing new version of config file /etc/apt/apt.conf.d/01-vendor-ubuntu ...
Installing new version of config file /etc/apt/apt.conf.d/01autoremove ...
Installing new version of config file /etc/cron.daily/apt ...
Installing new version of config file /etc/kernel/postinst.d/apt-auto-removal ...
usermod: no changes
Removing obsolete conffile /etc/apt/apt.conf.d/20changelog ...
Setting up libdbus-1-3:ppc64el (1.10.6-1ubuntu2) ...
Setting up libnih1:ppc64el (1.0.3-4.3ubuntu1) ...
Setting up libnih-dbus1:ppc64el (1.0.3-4.3ubuntu1) ...
Setting up libffi6:ppc64el (3.2.1-4) ...
Setting up libnettle6:ppc64el (3.2-1) ...
Setting up libhogweed4:ppc64el (3.2-1) ...
Setting up libp11-kit0:ppc64el (0.23.2-3) ...
Setting up libpng12-0:ppc64el (1.2.54-1ubuntu1) ...
Setting up libsqlite3-0:ppc64el (3.11.0-1ubuntu1) ...
Setting up libssl1.0.0:ppc64el (1.0.2g-1ubuntu2) ...
Setting up libtasn1-6:ppc64el (4.7-3) ...
Setting up libidn11:ppc64el (1.32-3ubuntu1) ...
Setting up libgnutls30:ppc64el (3.4.9-2ubuntu1) ...
Setting up libkrb5support0:ppc64el (1.13.2+dfsg-5) ...
Setting up libk5crypto3:ppc64el (1.13.2+dfsg-5) ...
Setting up libkeyutils1:ppc64el (1.5.9-8ubuntu1) ...
Setting up libkrb5-3:ppc64el (1.13.2+dfsg-5) ...
Setting up libgssapi-krb5-2:ppc64el (1.13.2+dfsg-5) ...
Setting up libroken18-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) ...
Setting up libasn1-8-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) ...
Setting up libhcrypto4-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) ...
Setting up libheimbase1-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) ...
Setting up libwind0-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) ...
Setting up libhx509-5-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) ...
Setting up libkrb5-26-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) ...
Setting up libheimntlm0-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) ...
Setting up libgssapi3-heimdal:ppc64el (1.7~git20150920+dfsg-4ubuntu1) ...
Setting up libldap-2.4-2:ppc64el (2.4.42+dfsg-2ubuntu3) ...
Setting up librtmp1:ppc64el (2.4+20151223.gitfa8646d-1build1) ...
Setting up libcurl3-gnutls:ppc64el (7.47.0-1ubuntu2) ...
Setting up apt-transport-https (1.2.6) ...
Setting up openssl (1.0.2g-1ubuntu2) ...
Setting up ca-certificates (20160104ubuntu1) ...
Setting up advancecomp (1.20-1) ...
Setting up cpp (4:5.3.1-1ubuntu1) ...
Setting up dmsetup (2:1.02.110-1ubuntu7) ...
Setting up libdpkg-perl (1.18.4ubuntu1) ...
Setting up make (4.1-6) ...
Setting up dpkg-dev (1.18.4ubuntu1) ...
Setting up gcc (4:5.3.1-1ubuntu1) ...
Setting up g++ (4:5.3.1-1ubuntu1) ...
Setting up pkg-create-dbgsym (0.70) ...
Setting up pkgbinarymangler (129) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Processing triggers for systemd (229-2ubuntu1) ...
Processing triggers for ca-certificates (20160104ubuntu1) ...
Updating certificates in /etc/ssl/certs...
6 added, 20 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
RUN: /usr/share/launchpad-buildd/slavebin/sbuild-package ['sbuild-package', 'PACKAGEBUILD-9345466', 'ppc64el', 'xenial-proposed', '-c', 'chroot:autobuild', '--arch=ppc64el', '--dist=xenial-proposed', '--purge=never', '--nolog', 'ruby-yajl_1.2.0-3build4.dsc']
Initiating build PACKAGEBUILD-9345466 with 4 jobs across 4 processor cores.
Kernel reported to sbuild: 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:57:08 UTC 2016 ppc64le
sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bos01-ppc64el-009.buildd

╔══════════════════════════════════════════════════════════════════════════════╗
║ ruby-yajl 1.2.0-3build4 (ppc64el)                          13 Mar 2016 22:49 ║
╚══════════════════════════════════════════════════════════════════════════════╝

Package: ruby-yajl
Version: 1.2.0-3build4
Source Version: 1.2.0-3build4
Distribution: xenial-proposed
Machine Architecture: ppc64el
Host Architecture: ppc64el
Build Architecture: ppc64el

I: NOTICE: Log filtering will replace 'build/ruby-yajl-u2GGIQ/ruby-yajl-1.2.0' with '«PKGBUILDDIR»'
I: NOTICE: Log filtering will replace 'build/ruby-yajl-u2GGIQ' with '«BUILDDIR»'
I: NOTICE: Log filtering will replace 'home/buildd/build-PACKAGEBUILD-9345466/chroot-autobuild' with '«CHROOT»'

┌──────────────────────────────────────────────────────────────────────────────┐
│ Fetch source files                                                           │
└──────────────────────────────────────────────────────────────────────────────┘


Local sources
─────────────

ruby-yajl_1.2.0-3build4.dsc exists in .; copying to chroot

Check architectures
───────────────────


Check dependencies
──────────────────

Merged Build-Depends: build-essential, fakeroot
Filtered Build-Depends: build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/«BUILDDIR»/resolver-LYGO9y/apt_archive/sbuild-build-depends-core-dummy.deb'.
Ign:1 copy:/«BUILDDIR»/resolver-LYGO9y/apt_archive ./ InRelease
Get:2 copy:/«BUILDDIR»/resolver-LYGO9y/apt_archive ./ Release [2119 B]
Ign:3 copy:/«BUILDDIR»/resolver-LYGO9y/apt_archive ./ Release.gpg
Get:4 copy:/«BUILDDIR»/resolver-LYGO9y/apt_archive ./ Sources [208 B]
Get:5 copy:/«BUILDDIR»/resolver-LYGO9y/apt_archive ./ Packages [527 B]
Fetched 2854 B in 0s (0 B/s)
Reading package lists...
W: The repository 'copy:/«BUILDDIR»/resolver-LYGO9y/apt_archive ./ Release' is not signed.
Reading package lists...

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install core build dependencies (apt-based resolver)                         │
└──────────────────────────────────────────────────────────────────────────────┘

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  libapt-pkg4.16 libgnutls-deb0-28 libisl13 libprocps3 udev
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 772 B of archives.
After this operation, 0 B of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  sbuild-build-depends-core-dummy
Authentication warning overridden.
Get:1 copy:/«BUILDDIR»/resolver-LYGO9y/apt_archive ./ sbuild-build-depends-core-dummy 0.invalid.0 [772 B]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 772 B in 0s (0 B/s)
Selecting previously unselected package sbuild-build-depends-core-dummy.
(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 ... 12194 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy_0.invalid.0_ppc64el.deb ...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...
Merged Build-Depends: base-files, base-passwd, bash, bsdutils, coreutils, dash, debianutils, diffutils, dpkg, e2fsprogs, findutils, grep, gzip, hostname, init, libc-bin, login, mount, ncurses-base, ncurses-bin, perl-base, sed, tar, util-linux, libc6-dev | libc-dev, gcc (>= 4:5.2), g++ (>= 4:5.2), make, dpkg-dev (>= 1.17.11), debhelper (>= 7.0.50~), gem2deb (>= 0.7.5~), ruby-rspec
Filtered Build-Depends: base-files, base-passwd, bash, bsdutils, coreutils, dash, debianutils, diffutils, dpkg, e2fsprogs, findutils, grep, gzip, hostname, init, libc-bin, login, mount, ncurses-base, ncurses-bin, perl-base, sed, tar, util-linux, libc6-dev | libc-dev, gcc (>= 4:5.2), g++ (>= 4:5.2), make, dpkg-dev (>= 1.17.11), debhelper (>= 7.0.50~), gem2deb (>= 0.7.5~), ruby-rspec
dpkg-deb: building package 'sbuild-build-depends-ruby-yajl-dummy' in '/«BUILDDIR»/resolver-qRRHMh/apt_archive/sbuild-build-depends-ruby-yajl-dummy.deb'.
Ign:1 copy:/«BUILDDIR»/resolver-qRRHMh/apt_archive ./ InRelease
Get:2 copy:/«BUILDDIR»/resolver-qRRHMh/apt_archive ./ Release [2119 B]
Ign:3 copy:/«BUILDDIR»/resolver-qRRHMh/apt_archive ./ Release.gpg
Get:4 copy:/«BUILDDIR»/resolver-qRRHMh/apt_archive ./ Sources [446 B]
Get:5 copy:/«BUILDDIR»/resolver-qRRHMh/apt_archive ./ Packages [713 B]
Fetched 3278 B in 0s (298 kB/s)
Reading package lists...
W: The repository 'copy:/«BUILDDIR»/resolver-qRRHMh/apt_archive ./ Release' is not signed.
Reading package lists...

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install ruby-yajl build dependencies (apt-based resolver)                    │
└──────────────────────────────────────────────────────────────────────────────┘

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  libapt-pkg4.16 libgnutls-deb0-28 libisl13 libprocps3 udev
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  autotools-dev bsdmainutils debhelper devscripts dh-python
  dh-strip-nondeterminism file gem2deb gem2deb-test-runner gettext
  gettext-base groff-base intltool-debian libarchive-zip-perl libasprintf0v5
  libcroco3 libexpat1 libfile-stripnondeterminism-perl libglib2.0-0 libgmp-dev
  libgmpxx4ldbl libicu55 libmagic1 libmpdec2 libpipeline1 libpython3-stdlib
  libpython3.5-minimal libpython3.5-stdlib libruby2.3 libtimedate-perl
  libunistring0 libxml2 libyaml-0-2 man-db mime-support po-debconf python3
  python3-chardet python3-debian python3-minimal python3-pkg-resources
  python3-six python3.5 python3.5-minimal rake ruby ruby-all-dev
  ruby-did-you-mean ruby-diff-lcs ruby-minitest ruby-net-telnet
  ruby-power-assert ruby-rspec ruby-rspec-core ruby-rspec-expectations
  ruby-rspec-mocks ruby-rspec-support ruby-setup ruby-test-unit
  ruby-thread-order ruby2.3 ruby2.3-dev rubygems-integration
Suggested packages:
  wamerican | wordlist whois vacation dh-make bsd-mailx | mailx
  cvs-buildpackage debbindiff devscripts-el gnuplot libauthen-sasl-perl
  libfile-desktopentry-perl libnet-smtp-ssl-perl libterm-size-perl
  libyaml-syck-perl mutt ssh-client svn-buildpackage w3m debian-keyring equivs
  liblwp-protocol-https-perl libsoap-lite-perl gettext-doc autopoint groff
  gmp-doc libgmp10-doc libmpfr-dev less www-browser libmail-box-perl
  python3-doc python3-tk python3-venv python3-setuptools python3.5-venv
  python3.5-doc binfmt-support ri ruby-dev bundler
Recommended packages:
  at dctrl-tools dput | dupload libdistro-info-perl libencode-locale-perl
  libjson-perl liburi-perl libwww-perl lintian patchutils python3-magic strace
  unzip wdiff wget | curl apt-file curl | wget | lynx-cur libasprintf-dev
  libgettextpo-dev libglib2.0-data shared-mime-info xdg-user-dirs xml-core
  libmail-sendmail-perl python3-apt zip fonts-lato libjs-jquery
The following NEW packages will be installed:
  autotools-dev bsdmainutils debhelper devscripts dh-python
  dh-strip-nondeterminism file gem2deb gem2deb-test-runner gettext
  gettext-base groff-base intltool-debian libarchive-zip-perl libasprintf0v5
  libcroco3 libexpat1 libfile-stripnondeterminism-perl libglib2.0-0 libgmp-dev
  libgmpxx4ldbl libicu55 libmagic1 libmpdec2 libpipeline1 libpython3-stdlib
  libpython3.5-minimal libpython3.5-stdlib libruby2.3 libtimedate-perl
  libunistring0 libxml2 libyaml-0-2 man-db mime-support po-debconf python3
  python3-chardet python3-debian python3-minimal python3-pkg-resources
  python3-six python3.5 python3.5-minimal rake ruby ruby-all-dev
  ruby-did-you-mean ruby-diff-lcs ruby-minitest ruby-net-telnet
  ruby-power-assert ruby-rspec ruby-rspec-core ruby-rspec-expectations
  ruby-rspec-mocks ruby-rspec-support ruby-setup ruby-test-unit
  ruby-thread-order ruby2.3 ruby2.3-dev rubygems-integration
  sbuild-build-depends-ruby-yajl-dummy
0 upgraded, 64 newly installed, 0 to remove and 0 not upgraded.
Need to get 25.6 MB of archives.
After this operation, 124 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  sbuild-build-depends-ruby-yajl-dummy
Authentication warning overridden.
Get:1 copy:/«BUILDDIR»/resolver-qRRHMh/apt_archive ./ sbuild-build-depends-ruby-yajl-dummy 0.invalid.0 [954 B]
Get:2 http://ftpmaster.internal/ubuntu xenial/main ppc64el libmpdec2 ppc64el 2.4.1-1 [84.7 kB]
Get:3 http://ftpmaster.internal/ubuntu xenial/main ppc64el libpython3.5-minimal ppc64el 3.5.1-6ubuntu2 [523 kB]
Get:4 http://ftpmaster.internal/ubuntu xenial/main ppc64el libexpat1 ppc64el 2.1.0-7 [76.5 kB]
Get:5 http://ftpmaster.internal/ubuntu xenial/main ppc64el python3.5-minimal ppc64el 3.5.1-6ubuntu2 [1593 kB]
Get:6 http://ftpmaster.internal/ubuntu xenial/main ppc64el python3-minimal ppc64el 3.5.1-1ubuntu2 [23.4 kB]
Get:7 http://ftpmaster.internal/ubuntu xenial/main ppc64el mime-support all 3.59ubuntu1 [31.0 kB]
Get:8 http://ftpmaster.internal/ubuntu xenial/main ppc64el libpython3.5-stdlib ppc64el 3.5.1-6ubuntu2 [2136 kB]
Get:9 http://ftpmaster.internal/ubuntu xenial/main ppc64el python3.5 ppc64el 3.5.1-6ubuntu2 [156 kB]
Get:10 http://ftpmaster.internal/ubuntu xenial/main ppc64el libpython3-stdlib ppc64el 3.5.1-1ubuntu2 [6850 B]
Get:11 http://ftpmaster.internal/ubuntu xenial/main ppc64el dh-python all 2.20151103ubuntu1 [74.4 kB]
Get:12 http://ftpmaster.internal/ubuntu xenial/main ppc64el python3 ppc64el 3.5.1-1ubuntu2 [8720 B]
Get:13 http://ftpmaster.internal/ubuntu xenial/main ppc64el groff-base ppc64el 1.22.3-7 [1370 kB]
Get:14 http://ftpmaster.internal/ubuntu xenial/main ppc64el bsdmainutils ppc64el 9.0.6ubuntu3 [176 kB]
Get:15 http://ftpmaster.internal/ubuntu xenial/main ppc64el libpipeline1 ppc64el 1.4.1-2 [24.1 kB]
Get:16 http://ftpmaster.internal/ubuntu xenial/main ppc64el man-db ppc64el 2.7.5-1 [850 kB]
Get:17 http://ftpmaster.internal/ubuntu xenial/main ppc64el libunistring0 ppc64el 0.9.3-5.2ubuntu1 [269 kB]
Get:18 http://ftpmaster.internal/ubuntu xenial/main ppc64el libyaml-0-2 ppc64el 0.1.6-3 [46.8 kB]
Get:19 http://ftpmaster.internal/ubuntu xenial/main ppc64el libmagic1 ppc64el 1:5.25-2ubuntu1 [220 kB]
Get:20 http://ftpmaster.internal/ubuntu xenial/main ppc64el file ppc64el 1:5.25-2ubuntu1 [21.7 kB]
Get:21 http://ftpmaster.internal/ubuntu xenial/main ppc64el libasprintf0v5 ppc64el 0.19.7-2ubuntu3 [6604 B]
Get:22 http://ftpmaster.internal/ubuntu xenial/main ppc64el gettext-base ppc64el 0.19.7-2ubuntu3 [46.8 kB]
Get:23 http://ftpmaster.internal/ubuntu xenial/main ppc64el libglib2.0-0 ppc64el 2.47.6-1 [1041 kB]
Get:24 http://ftpmaster.internal/ubuntu xenial/main ppc64el libicu55 ppc64el 55.1-7 [7758 kB]
Get:25 http://ftpmaster.internal/ubuntu xenial/main ppc64el libxml2 ppc64el 2.9.3+dfsg1-1 [611 kB]
Get:26 http://ftpmaster.internal/ubuntu xenial/main ppc64el autotools-dev all 20150820.1 [39.8 kB]
Get:27 http://ftpmaster.internal/ubuntu xenial/main ppc64el libcroco3 ppc64el 0.6.11-1 [75.6 kB]
Get:28 http://ftpmaster.internal/ubuntu xenial/main ppc64el gettext ppc64el 0.19.7-2ubuntu3 [1100 kB]
Get:29 http://ftpmaster.internal/ubuntu xenial/main ppc64el intltool-debian all 0.35.0+20060710.4 [24.9 kB]
Get:30 http://ftpmaster.internal/ubuntu xenial/main ppc64el po-debconf all 1.0.19 [234 kB]
Get:31 http://ftpmaster.internal/ubuntu xenial/main ppc64el libarchive-zip-perl all 1.56-2 [84.1 kB]
Get:32 http://ftpmaster.internal/ubuntu xenial/main ppc64el libfile-stripnondeterminism-perl all 0.015-1 [10.3 kB]
Get:33 http://ftpmaster.internal/ubuntu xenial/main ppc64el libtimedate-perl all 2.3000-2 [37.5 kB]
Get:34 http://ftpmaster.internal/ubuntu xenial/main ppc64el dh-strip-nondeterminism all 0.015-1 [4864 B]
Get:35 http://ftpmaster.internal/ubuntu xenial/main ppc64el debhelper all 9.20160115ubuntu2 [740 kB]
Get:36 http://ftpmaster.internal/ubuntu xenial/main ppc64el devscripts ppc64el 2.15.9ubuntu3 [827 kB]
Get:37 http://ftpmaster.internal/ubuntu xenial/main ppc64el rubygems-integration all 1.10 [4966 B]
Get:38 http://ftpmaster.internal/ubuntu xenial/main ppc64el ruby-did-you-mean all 1.0.0-2 [8390 B]
Get:39 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby-minitest all 5.8.4-2 [36.6 kB]
Get:40 http://ftpmaster.internal/ubuntu xenial/main ppc64el ruby-net-telnet all 0.1.1-2 [12.6 kB]
Get:41 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby-power-assert all 0.2.7-1 [7668 B]
Get:42 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby-test-unit all 3.1.7-2 [60.3 kB]
Get:43 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el libruby2.3 ppc64el 2.3.0-4 [2988 kB]
Get:44 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby2.3 ppc64el 2.3.0-4 [41.0 kB]
Get:45 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby all 1:2.3.0+1 [5530 B]
Get:46 http://ftpmaster.internal/ubuntu xenial/main ppc64el rake all 10.5.0-2 [48.2 kB]
Get:47 http://ftpmaster.internal/ubuntu xenial/main ppc64el gem2deb-test-runner all 0.29 [10.2 kB]
Get:48 http://ftpmaster.internal/ubuntu xenial/main ppc64el python3-pkg-resources all 20.1.1-1 [47.9 kB]
Get:49 http://ftpmaster.internal/ubuntu xenial/main ppc64el python3-chardet all 2.3.0-2 [96.2 kB]
Get:50 http://ftpmaster.internal/ubuntu xenial/main ppc64el python3-six all 1.10.0-3 [11.0 kB]
Get:51 http://ftpmaster.internal/ubuntu xenial/main ppc64el python3-debian all 0.1.27ubuntu1 [43.8 kB]
Get:52 http://ftpmaster.internal/ubuntu xenial/main ppc64el libgmpxx4ldbl ppc64el 2:6.1.0+dfsg-2 [9218 B]
Get:53 http://ftpmaster.internal/ubuntu xenial/main ppc64el libgmp-dev ppc64el 2:6.1.0+dfsg-2 [305 kB]
Get:54 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby2.3-dev ppc64el 2.3.0-4 [1098 kB]
Get:55 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby-all-dev all 1:2.3.0+1 [5014 B]
Get:56 http://ftpmaster.internal/ubuntu xenial/main ppc64el ruby-setup all 3.4.1-9 [32.2 kB]
Get:57 http://ftpmaster.internal/ubuntu xenial/main ppc64el gem2deb all 0.29 [44.8 kB]
Get:58 http://ftpmaster.internal/ubuntu xenial/main ppc64el ruby-diff-lcs all 1.2.5-2build1 [23.8 kB]
Get:59 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby-rspec-support all 3.4.0c3e0m1s1-1ubuntu1 [23.0 kB]
Get:60 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby-rspec-expectations all 3.4.0c3e0m1s1-1ubuntu1 [77.1 kB]
Get:61 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby-rspec-mocks all 3.4.0c3e0m1s1-1ubuntu1 [73.5 kB]
Get:62 http://ftpmaster.internal/ubuntu xenial/main ppc64el ruby-thread-order all 1.1.0-1 [5232 B]
Get:63 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby-rspec-core all 3.4.0c3e0m1s1-1ubuntu1 [149 kB]
Get:64 http://ftpmaster.internal/ubuntu xenial-proposed/main ppc64el ruby-rspec all 3.4.0c3e0m1s1-1ubuntu1 [3386 B]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 25.6 MB in 0s (41.6 MB/s)
Selecting previously unselected package libmpdec2:ppc64el.
(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 ... 12194 files and directories currently installed.)
Preparing to unpack .../libmpdec2_2.4.1-1_ppc64el.deb ...
Unpacking libmpdec2:ppc64el (2.4.1-1) ...
Selecting previously unselected package libpython3.5-minimal:ppc64el.
Preparing to unpack .../libpython3.5-minimal_3.5.1-6ubuntu2_ppc64el.deb ...
Unpacking libpython3.5-minimal:ppc64el (3.5.1-6ubuntu2) ...
Selecting previously unselected package libexpat1:ppc64el.
Preparing to unpack .../libexpat1_2.1.0-7_ppc64el.deb ...
Unpacking libexpat1:ppc64el (2.1.0-7) ...
Selecting previously unselected package python3.5-minimal.
Preparing to unpack .../python3.5-minimal_3.5.1-6ubuntu2_ppc64el.deb ...
Unpacking python3.5-minimal (3.5.1-6ubuntu2) ...
Selecting previously unselected package python3-minimal.
Preparing to unpack .../python3-minimal_3.5.1-1ubuntu2_ppc64el.deb ...
Unpacking python3-minimal (3.5.1-1ubuntu2) ...
Selecting previously unselected package mime-support.
Preparing to unpack .../mime-support_3.59ubuntu1_all.deb ...
Unpacking mime-support (3.59ubuntu1) ...
Selecting previously unselected package libpython3.5-stdlib:ppc64el.
Preparing to unpack .../libpython3.5-stdlib_3.5.1-6ubuntu2_ppc64el.deb ...
Unpacking libpython3.5-stdlib:ppc64el (3.5.1-6ubuntu2) ...
Selecting previously unselected package python3.5.
Preparing to unpack .../python3.5_3.5.1-6ubuntu2_ppc64el.deb ...
Unpacking python3.5 (3.5.1-6ubuntu2) ...
Selecting previously unselected package libpython3-stdlib:ppc64el.
Preparing to unpack .../libpython3-stdlib_3.5.1-1ubuntu2_ppc64el.deb ...
Unpacking libpython3-stdlib:ppc64el (3.5.1-1ubuntu2) ...
Selecting previously unselected package dh-python.
Preparing to unpack .../dh-python_2.20151103ubuntu1_all.deb ...
Unpacking dh-python (2.20151103ubuntu1) ...
Setting up libpython3.5-minimal:ppc64el (3.5.1-6ubuntu2) ...
Setting up libexpat1:ppc64el (2.1.0-7) ...
Setting up python3.5-minimal (3.5.1-6ubuntu2) ...
Setting up python3-minimal (3.5.1-1ubuntu2) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
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 ... 13145 files and directories currently installed.)
Preparing to unpack .../python3_3.5.1-1ubuntu2_ppc64el.deb ...
Unpacking python3 (3.5.1-1ubuntu2) ...
Selecting previously unselected package groff-base.
Preparing to unpack .../groff-base_1.22.3-7_ppc64el.deb ...
Unpacking groff-base (1.22.3-7) ...
Selecting previously unselected package bsdmainutils.
Preparing to unpack .../bsdmainutils_9.0.6ubuntu3_ppc64el.deb ...
Unpacking bsdmainutils (9.0.6ubuntu3) ...
Selecting previously unselected package libpipeline1:ppc64el.
Preparing to unpack .../libpipeline1_1.4.1-2_ppc64el.deb ...
Unpacking libpipeline1:ppc64el (1.4.1-2) ...
Selecting previously unselected package man-db.
Preparing to unpack .../man-db_2.7.5-1_ppc64el.deb ...
Unpacking man-db (2.7.5-1) ...
Selecting previously unselected package libunistring0:ppc64el.
Preparing to unpack .../libunistring0_0.9.3-5.2ubuntu1_ppc64el.deb ...
Unpacking libunistring0:ppc64el (0.9.3-5.2ubuntu1) ...
Selecting previously unselected package libyaml-0-2:ppc64el.
Preparing to unpack .../libyaml-0-2_0.1.6-3_ppc64el.deb ...
Unpacking libyaml-0-2:ppc64el (0.1.6-3) ...
Selecting previously unselected package libmagic1:ppc64el.
Preparing to unpack .../libmagic1_1%3a5.25-2ubuntu1_ppc64el.deb ...
Unpacking libmagic1:ppc64el (1:5.25-2ubuntu1) ...
Selecting previously unselected package file.
Preparing to unpack .../file_1%3a5.25-2ubuntu1_ppc64el.deb ...
Unpacking file (1:5.25-2ubuntu1) ...
Selecting previously unselected package libasprintf0v5:ppc64el.
Preparing to unpack .../libasprintf0v5_0.19.7-2ubuntu3_ppc64el.deb ...
Unpacking libasprintf0v5:ppc64el (0.19.7-2ubuntu3) ...
Selecting previously unselected package gettext-base.
Preparing to unpack .../gettext-base_0.19.7-2ubuntu3_ppc64el.deb ...
Unpacking gettext-base (0.19.7-2ubuntu3) ...
Selecting previously unselected package libglib2.0-0:ppc64el.
Preparing to unpack .../libglib2.0-0_2.47.6-1_ppc64el.deb ...
Unpacking libglib2.0-0:ppc64el (2.47.6-1) ...
Selecting previously unselected package libicu55:ppc64el.
Preparing to unpack .../libicu55_55.1-7_ppc64el.deb ...
Unpacking libicu55:ppc64el (55.1-7) ...
Selecting previously unselected package libxml2:ppc64el.
Preparing to unpack .../libxml2_2.9.3+dfsg1-1_ppc64el.deb ...
Unpacking libxml2:ppc64el (2.9.3+dfsg1-1) ...
Selecting previously unselected package autotools-dev.
Preparing to unpack .../autotools-dev_20150820.1_all.deb ...
Unpacking autotools-dev (20150820.1) ...
Selecting previously unselected package libcroco3:ppc64el.
Preparing to unpack .../libcroco3_0.6.11-1_ppc64el.deb ...
Unpacking libcroco3:ppc64el (0.6.11-1) ...
Selecting previously unselected package gettext.
Preparing to unpack .../gettext_0.19.7-2ubuntu3_ppc64el.deb ...
Unpacking gettext (0.19.7-2ubuntu3) ...
Selecting previously unselected package intltool-debian.
Preparing to unpack .../intltool-debian_0.35.0+20060710.4_all.deb ...
Unpacking intltool-debian (0.35.0+20060710.4) ...
Selecting previously unselected package po-debconf.
Preparing to unpack .../po-debconf_1.0.19_all.deb ...
Unpacking po-debconf (1.0.19) ...
Selecting previously unselected package libarchive-zip-perl.
Preparing to unpack .../libarchive-zip-perl_1.56-2_all.deb ...
Unpacking libarchive-zip-perl (1.56-2) ...
Selecting previously unselected package libfile-stripnondeterminism-perl.
Preparing to unpack .../libfile-stripnondeterminism-perl_0.015-1_all.deb ...
Unpacking libfile-stripnondeterminism-perl (0.015-1) ...
Selecting previously unselected package libtimedate-perl.
Preparing to unpack .../libtimedate-perl_2.3000-2_all.deb ...
Unpacking libtimedate-perl (2.3000-2) ...
Selecting previously unselected package dh-strip-nondeterminism.
Preparing to unpack .../dh-strip-nondeterminism_0.015-1_all.deb ...
Unpacking dh-strip-nondeterminism (0.015-1) ...
Selecting previously unselected package debhelper.
Preparing to unpack .../debhelper_9.20160115ubuntu2_all.deb ...
Unpacking debhelper (9.20160115ubuntu2) ...
Selecting previously unselected package devscripts.
Preparing to unpack .../devscripts_2.15.9ubuntu3_ppc64el.deb ...
Unpacking devscripts (2.15.9ubuntu3) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../rubygems-integration_1.10_all.deb ...
Unpacking rubygems-integration (1.10) ...
Selecting previously unselected package ruby-did-you-mean.
Preparing to unpack .../ruby-did-you-mean_1.0.0-2_all.deb ...
Unpacking ruby-did-you-mean (1.0.0-2) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../ruby-minitest_5.8.4-2_all.deb ...
Unpacking ruby-minitest (5.8.4-2) ...
Selecting previously unselected package ruby-net-telnet.
Preparing to unpack .../ruby-net-telnet_0.1.1-2_all.deb ...
Unpacking ruby-net-telnet (0.1.1-2) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../ruby-power-assert_0.2.7-1_all.deb ...
Unpacking ruby-power-assert (0.2.7-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../ruby-test-unit_3.1.7-2_all.deb ...
Unpacking ruby-test-unit (3.1.7-2) ...
Selecting previously unselected package libruby2.3:ppc64el.
Preparing to unpack .../libruby2.3_2.3.0-4_ppc64el.deb ...
Unpacking libruby2.3:ppc64el (2.3.0-4) ...
Selecting previously unselected package ruby2.3.
Preparing to unpack .../ruby2.3_2.3.0-4_ppc64el.deb ...
Unpacking ruby2.3 (2.3.0-4) ...
Selecting previously unselected package ruby.
Preparing to unpack .../ruby_1%3a2.3.0+1_all.deb ...
Unpacking ruby (1:2.3.0+1) ...
Selecting previously unselected package rake.
Preparing to unpack .../archives/rake_10.5.0-2_all.deb ...
Unpacking rake (10.5.0-2) ...
Selecting previously unselected package gem2deb-test-runner.
Preparing to unpack .../gem2deb-test-runner_0.29_all.deb ...
Unpacking gem2deb-test-runner (0.29) ...
Selecting previously unselected package python3-pkg-resources.
Preparing to unpack .../python3-pkg-resources_20.1.1-1_all.deb ...
Unpacking python3-pkg-resources (20.1.1-1) ...
Selecting previously unselected package python3-chardet.
Preparing to unpack .../python3-chardet_2.3.0-2_all.deb ...
Unpacking python3-chardet (2.3.0-2) ...
Selecting previously unselected package python3-six.
Preparing to unpack .../python3-six_1.10.0-3_all.deb ...
Unpacking python3-six (1.10.0-3) ...
Selecting previously unselected package python3-debian.
Preparing to unpack .../python3-debian_0.1.27ubuntu1_all.deb ...
Unpacking python3-debian (0.1.27ubuntu1) ...
Selecting previously unselected package libgmpxx4ldbl:ppc64el.
Preparing to unpack .../libgmpxx4ldbl_2%3a6.1.0+dfsg-2_ppc64el.deb ...
Unpacking libgmpxx4ldbl:ppc64el (2:6.1.0+dfsg-2) ...
Selecting previously unselected package libgmp-dev:ppc64el.
Preparing to unpack .../libgmp-dev_2%3a6.1.0+dfsg-2_ppc64el.deb ...
Unpacking libgmp-dev:ppc64el (2:6.1.0+dfsg-2) ...
Selecting previously unselected package ruby2.3-dev:ppc64el.
Preparing to unpack .../ruby2.3-dev_2.3.0-4_ppc64el.deb ...
Unpacking ruby2.3-dev:ppc64el (2.3.0-4) ...
Selecting previously unselected package ruby-all-dev.
Preparing to unpack .../ruby-all-dev_1%3a2.3.0+1_all.deb ...
Unpacking ruby-all-dev (1:2.3.0+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 .../archives/gem2deb_0.29_all.deb ...
Unpacking gem2deb (0.29) ...
Selecting previously unselected package ruby-diff-lcs.
Preparing to unpack .../ruby-diff-lcs_1.2.5-2build1_all.deb ...
Unpacking ruby-diff-lcs (1.2.5-2build1) ...
Selecting previously unselected package ruby-rspec-support.
Preparing to unpack .../ruby-rspec-support_3.4.0c3e0m1s1-1ubuntu1_all.deb ...
Unpacking ruby-rspec-support (3.4.0c3e0m1s1-1ubuntu1) ...
Selecting previously unselected package ruby-rspec-expectations.
Preparing to unpack .../ruby-rspec-expectations_3.4.0c3e0m1s1-1ubuntu1_all.deb ...
Unpacking ruby-rspec-expectations (3.4.0c3e0m1s1-1ubuntu1) ...
Selecting previously unselected package ruby-rspec-mocks.
Preparing to unpack .../ruby-rspec-mocks_3.4.0c3e0m1s1-1ubuntu1_all.deb ...
Unpacking ruby-rspec-mocks (3.4.0c3e0m1s1-1ubuntu1) ...
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.4.0c3e0m1s1-1ubuntu1_all.deb ...
Unpacking ruby-rspec-core (3.4.0c3e0m1s1-1ubuntu1) ...
Selecting previously unselected package ruby-rspec.
Preparing to unpack .../ruby-rspec_3.4.0c3e0m1s1-1ubuntu1_all.deb ...
Unpacking ruby-rspec (3.4.0c3e0m1s1-1ubuntu1) ...
Selecting previously unselected package sbuild-build-depends-ruby-yajl-dummy.
Preparing to unpack .../sbuild-build-depends-ruby-yajl-dummy_0.invalid.0_ppc64el.deb ...
Unpacking sbuild-build-depends-ruby-yajl-dummy (0.invalid.0) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...
Setting up libmpdec2:ppc64el (2.4.1-1) ...
Setting up mime-support (3.59ubuntu1) ...
Setting up libpython3.5-stdlib:ppc64el (3.5.1-6ubuntu2) ...
Setting up python3.5 (3.5.1-6ubuntu2) ...
Setting up libpython3-stdlib:ppc64el (3.5.1-1ubuntu2) ...
Setting up groff-base (1.22.3-7) ...
Setting up bsdmainutils (9.0.6ubuntu3) ...
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:ppc64el (1.4.1-2) ...
Setting up man-db (2.7.5-1) ...
Not building database; man-db/auto-update is not 'true'.
Setting up libunistring0:ppc64el (0.9.3-5.2ubuntu1) ...
Setting up libyaml-0-2:ppc64el (0.1.6-3) ...
Setting up libmagic1:ppc64el (1:5.25-2ubuntu1) ...
Setting up file (1:5.25-2ubuntu1) ...
Setting up libasprintf0v5:ppc64el (0.19.7-2ubuntu3) ...
Setting up gettext-base (0.19.7-2ubuntu3) ...
Setting up libglib2.0-0:ppc64el (2.47.6-1) ...
No schema files found: doing nothing.
Setting up libicu55:ppc64el (55.1-7) ...
Setting up libxml2:ppc64el (2.9.3+dfsg1-1) ...
Setting up autotools-dev (20150820.1) ...
Setting up libcroco3:ppc64el (0.6.11-1) ...
Setting up gettext (0.19.7-2ubuntu3) ...
Setting up intltool-debian (0.35.0+20060710.4) ...
Setting up po-debconf (1.0.19) ...
Setting up libarchive-zip-perl (1.56-2) ...
Setting up libfile-stripnondeterminism-perl (0.015-1) ...
Setting up libtimedate-perl (2.3000-2) ...
Setting up rubygems-integration (1.10) ...
Setting up ruby-did-you-mean (1.0.0-2) ...
Setting up ruby-minitest (5.8.4-2) ...
Setting up ruby-net-telnet (0.1.1-2) ...
Setting up ruby-power-assert (0.2.7-1) ...
Setting up ruby-test-unit (3.1.7-2) ...
Setting up libgmpxx4ldbl:ppc64el (2:6.1.0+dfsg-2) ...
Setting up libgmp-dev:ppc64el (2:6.1.0+dfsg-2) ...
Setting up dh-python (2.20151103ubuntu1) ...
Setting up python3 (3.5.1-1ubuntu2) ...
Setting up dh-strip-nondeterminism (0.015-1) ...
Setting up debhelper (9.20160115ubuntu2) ...
Setting up devscripts (2.15.9ubuntu3) ...
Setting up rake (10.5.0-2) ...
Setting up libruby2.3:ppc64el (2.3.0-4) ...
Setting up ruby2.3 (2.3.0-4) ...
Setting up gem2deb-test-runner (0.29) ...
Setting up python3-pkg-resources (20.1.1-1) ...
Setting up python3-chardet (2.3.0-2) ...
Setting up python3-six (1.10.0-3) ...
Setting up python3-debian (0.1.27ubuntu1) ...
Setting up ruby2.3-dev:ppc64el (2.3.0-4) ...
Setting up ruby-all-dev (1:2.3.0+1) ...
Setting up ruby-setup (3.4.1-9) ...
Setting up ruby-diff-lcs (1.2.5-2build1) ...
Setting up ruby-rspec-support (3.4.0c3e0m1s1-1ubuntu1) ...
Setting up ruby-rspec-expectations (3.4.0c3e0m1s1-1ubuntu1) ...
Setting up ruby-rspec-mocks (3.4.0c3e0m1s1-1ubuntu1) ...
Setting up ruby-thread-order (1.1.0-1) ...
Setting up ruby-rspec-core (3.4.0c3e0m1s1-1ubuntu1) ...
Setting up ruby-rspec (3.4.0c3e0m1s1-1ubuntu1) ...
Setting up ruby (1:2.3.0+1) ...
Setting up gem2deb (0.29) ...
Setting up sbuild-build-depends-ruby-yajl-dummy (0.invalid.0) ...
Processing triggers for libc-bin (2.21-0ubuntu6) ...

┌──────────────────────────────────────────────────────────────────────────────┐
│ Build environment                                                            │
└──────────────────────────────────────────────────────────────────────────────┘

Kernel: Linux 4.2.0-30-generic ppc64el (ppc64le)
Toolchain package versions: binutils_2.26-6ubuntu1 dpkg-dev_1.18.4ubuntu1 g++-5_5.3.1-11ubuntu1 gcc-5_5.3.1-11ubuntu1 libc6-dev_2.21-0ubuntu6 libstdc++-5-dev_5.3.1-11ubuntu1 libstdc++6_5.3.1-11ubuntu1 linux-libc-dev_4.4.0-13.29
Package versions: adduser_3.113+nmu3ubuntu4 advancecomp_1.20-1 apt_1.2.6 apt-transport-https_1.2.6 autotools-dev_20150820.1 base-files_9.4ubuntu3 base-passwd_3.5.39 bash_4.3-14ubuntu1 binutils_2.26-6ubuntu1 bsdmainutils_9.0.6ubuntu3 bsdutils_1:2.27.1-4ubuntu1 build-essential_12.1ubuntu2 bzip2_1.0.6-8 ca-certificates_20160104ubuntu1 coreutils_8.25-2ubuntu2 cpp_4:5.3.1-1ubuntu1 cpp-5_5.3.1-11ubuntu1 dash_0.5.8-2.1ubuntu2 debconf_1.5.58ubuntu1 debhelper_9.20160115ubuntu2 debianutils_4.7 devscripts_2.15.9ubuntu3 dh-python_2.20151103ubuntu1 dh-strip-nondeterminism_0.015-1 diffutils_1:3.3-3 dmsetup_2:1.02.110-1ubuntu7 dpkg_1.18.4ubuntu1 dpkg-dev_1.18.4ubuntu1 e2fslibs_1.42.13-1ubuntu1 e2fsprogs_1.42.13-1ubuntu1 fakeroot_1.20.2-1ubuntu1 file_1:5.25-2ubuntu1 findutils_4.6.0+git+20160126-2 g++_4:5.3.1-1ubuntu1 g++-5_5.3.1-11ubuntu1 gcc_4:5.3.1-1ubuntu1 gcc-5_5.3.1-11ubuntu1 gcc-5-base_5.3.1-11ubuntu1 gcc-6-base_6-20160313-0ubuntu1 gem2deb_0.29 gem2deb-test-runner_0.29 gettext_0.19.7-2ubuntu3 gettext-base_0.19.7-2ubuntu3 gnupg_1.4.20-1ubuntu3 gpgv_1.4.20-1ubuntu3 grep_2.23-1 groff-base_1.22.3-7 gzip_1.6-4ubuntu1 hostname_3.16ubuntu2 init_1.29ubuntu1 init-system-helpers_1.29ubuntu1 initscripts_2.88dsf-59.3ubuntu2 insserv_1.14.0-5ubuntu3 intltool-debian_0.35.0+20060710.4 libacl1_2.2.52-3 libapparmor1_2.10-3ubuntu2 libapt-pkg4.16_1.0.10.2ubuntu1 libapt-pkg5.0_1.2.6 libarchive-zip-perl_1.56-2 libasan2_5.3.1-11ubuntu1 libasn1-8-heimdal_1.7~git20150920+dfsg-4ubuntu1 libasprintf0v5_0.19.7-2ubuntu3 libatomic1_5.3.1-11ubuntu1 libattr1_1:2.4.47-2 libaudit-common_1:2.4.5-1ubuntu2 libaudit1_1:2.4.5-1ubuntu2 libblkid1_2.27.1-4ubuntu1 libbz2-1.0_1.0.6-8 libc-bin_2.21-0ubuntu6 libc-dev-bin_2.21-0ubuntu6 libc6_2.21-0ubuntu6 libc6-dev_2.21-0ubuntu6 libcap2_1:2.24-12 libcap2-bin_1:2.24-12 libcc1-0_5.3.1-11ubuntu1 libcomerr2_1.42.13-1ubuntu1 libcroco3_0.6.11-1 libcryptsetup4_2:1.6.6-5ubuntu2 libcurl3-gnutls_7.47.0-1ubuntu2 libdb5.3_5.3.28-11 libdbus-1-3_1.10.6-1ubuntu2 libdebconfclient0_0.198ubuntu1 libdevmapper1.02.1_2:1.02.110-1ubuntu7 libdpkg-perl_1.18.4ubuntu1 libexpat1_2.1.0-7 libfakeroot_1.20.2-1ubuntu1 libfdisk1_2.27.1-4ubuntu1 libffi6_3.2.1-4 libfile-stripnondeterminism-perl_0.015-1 libgcc-5-dev_5.3.1-11ubuntu1 libgcc1_1:6-20160313-0ubuntu1 libgcrypt20_1.6.5-2 libgdbm3_1.8.3-13.1 libglib2.0-0_2.47.6-1 libgmp-dev_2:6.1.0+dfsg-2 libgmp10_2:6.1.0+dfsg-2 libgmpxx4ldbl_2:6.1.0+dfsg-2 libgnutls-deb0-28_3.3.15-5ubuntu2 libgnutls30_3.4.9-2ubuntu1 libgomp1_5.3.1-11ubuntu1 libgpg-error0_1.21-2ubuntu1 libgssapi-krb5-2_1.13.2+dfsg-5 libgssapi3-heimdal_1.7~git20150920+dfsg-4ubuntu1 libhcrypto4-heimdal_1.7~git20150920+dfsg-4ubuntu1 libheimbase1-heimdal_1.7~git20150920+dfsg-4ubuntu1 libheimntlm0-heimdal_1.7~git20150920+dfsg-4ubuntu1 libhogweed4_3.2-1 libhx509-5-heimdal_1.7~git20150920+dfsg-4ubuntu1 libicu55_55.1-7 libidn11_1.32-3ubuntu1 libisl13_0.14-2 libisl15_0.16.1-1 libitm1_5.3.1-11ubuntu1 libk5crypto3_1.13.2+dfsg-5 libkeyutils1_1.5.9-8ubuntu1 libkmod2_22-1ubuntu4 libkrb5-26-heimdal_1.7~git20150920+dfsg-4ubuntu1 libkrb5-3_1.13.2+dfsg-5 libkrb5support0_1.13.2+dfsg-5 libldap-2.4-2_2.4.42+dfsg-2ubuntu3 liblockfile-bin_1.09-6ubuntu1 liblockfile1_1.09-6ubuntu1 liblz4-1_0.0~r131-2 liblzma5_5.1.1alpha+20120614-2ubuntu2 libmagic1_1:5.25-2ubuntu1 libmount1_2.27.1-4ubuntu1 libmpc3_1.0.3-1 libmpdec2_2.4.1-1 libmpfr4_3.1.4-1 libncurses5_6.0+20160213-1ubuntu1 libncursesw5_6.0+20160213-1ubuntu1 libnettle6_3.2-1 libnih-dbus1_1.0.3-4.3ubuntu1 libnih1_1.0.3-4.3ubuntu1 libp11-kit0_0.23.2-3 libpam-modules_1.1.8-3.1ubuntu3 libpam-modules-bin_1.1.8-3.1ubuntu3 libpam-runtime_1.1.8-3.1ubuntu3 libpam0g_1.1.8-3.1ubuntu3 libpcre3_2:8.38-3 libperl5.22_5.22.1-8 libpipeline1_1.4.1-2 libpng12-0_1.2.54-1ubuntu1 libprocps3_1:3.3.9-1ubuntu8 libprocps4_2:3.3.10-4ubuntu2 libpython3-stdlib_3.5.1-1ubuntu2 libpython3.5-minimal_3.5.1-6ubuntu2 libpython3.5-stdlib_3.5.1-6ubuntu2 libreadline6_6.3-8ubuntu2 libroken18-heimdal_1.7~git20150920+dfsg-4ubuntu1 librtmp1_2.4+20151223.gitfa8646d-1build1 libruby2.3_2.3.0-4 libsasl2-2_2.1.26.dfsg1-14 libsasl2-modules-db_2.1.26.dfsg1-14 libseccomp2_2.2.3-3ubuntu1 libselinux1_2.4-3build1 libsemanage-common_2.4-3build1 libsemanage1_2.4-3build1 libsepol1_2.4-2 libslang2_2.3.0-2ubuntu1 libsmartcols1_2.27.1-4ubuntu1 libsqlite3-0_3.11.0-1ubuntu1 libss2_1.42.13-1ubuntu1 libssl1.0.0_1.0.2g-1ubuntu2 libstdc++-5-dev_5.3.1-11ubuntu1 libstdc++6_5.3.1-11ubuntu1 libsystemd0_229-2ubuntu1 libtasn1-6_4.7-3 libtimedate-perl_2.3000-2 libtinfo5_6.0+20160213-1ubuntu1 libubsan0_5.3.1-11ubuntu1 libudev1_229-2ubuntu1 libunistring0_0.9.3-5.2ubuntu1 libusb-0.1-4_2:0.1.12-28 libustr-1.0-1_1.0.4-5 libuuid1_2.27.1-4ubuntu1 libwind0-heimdal_1.7~git20150920+dfsg-4ubuntu1 libxml2_2.9.3+dfsg1-1 libyaml-0-2_0.1.6-3 linux-libc-dev_4.4.0-13.29 lockfile-progs_0.1.17 login_1:4.2-3.1ubuntu4 lsb-base_9.20160110 make_4.1-6 man-db_2.7.5-1 mawk_1.3.3-17ubuntu2 mime-support_3.59ubuntu1 mount_2.27.1-4ubuntu1 multiarch-support_2.21-0ubuntu6 ncurses-base_6.0+20160213-1ubuntu1 ncurses-bin_6.0+20160213-1ubuntu1 openssl_1.0.2g-1ubuntu2 optipng_0.7.5-1 passwd_1:4.2-3.1ubuntu4 patch_2.7.5-1 perl_5.22.1-8 perl-base_5.22.1-8 perl-modules-5.22_5.22.1-8 pkg-create-dbgsym_0.70 pkgbinarymangler_129 po-debconf_1.0.19 policyrcd-script-zg2_0.1-2 procps_2:3.3.10-4ubuntu2 python3_3.5.1-1ubuntu2 python3-chardet_2.3.0-2 python3-debian_0.1.27ubuntu1 python3-minimal_3.5.1-1ubuntu2 python3-pkg-resources_20.1.1-1 python3-six_1.10.0-3 python3.5_3.5.1-6ubuntu2 python3.5-minimal_3.5.1-6ubuntu2 rake_10.5.0-2 readline-common_6.3-8ubuntu2 ruby_1:2.3.0+1 ruby-all-dev_1:2.3.0+1 ruby-did-you-mean_1.0.0-2 ruby-diff-lcs_1.2.5-2build1 ruby-minitest_5.8.4-2 ruby-net-telnet_0.1.1-2 ruby-power-assert_0.2.7-1 ruby-rspec_3.4.0c3e0m1s1-1ubuntu1 ruby-rspec-core_3.4.0c3e0m1s1-1ubuntu1 ruby-rspec-expectations_3.4.0c3e0m1s1-1ubuntu1 ruby-rspec-mocks_3.4.0c3e0m1s1-1ubuntu1 ruby-rspec-support_3.4.0c3e0m1s1-1ubuntu1 ruby-setup_3.4.1-9 ruby-test-unit_3.1.7-2 ruby-thread-order_1.1.0-1 ruby2.3_2.3.0-4 ruby2.3-dev_2.3.0-4 rubygems-integration_1.10 sbuild-build-depends-core-dummy_0.invalid.0 sbuild-build-depends-ruby-yajl-dummy_0.invalid.0 sed_4.2.2-7 sensible-utils_0.0.9 systemd_229-2ubuntu1 systemd-sysv_229-2ubuntu1 sysv-rc_2.88dsf-59.3ubuntu2 sysvinit-utils_2.88dsf-59.3ubuntu2 tar_1.28-2.1 tzdata_2016a-1 ubuntu-keyring_2012.05.19 udev_229-2ubuntu1 util-linux_2.27.1-4ubuntu1 xz-utils_5.1.1alpha+20120614-2ubuntu2 zlib1g_1:1.2.8.dfsg-2ubuntu4

┌──────────────────────────────────────────────────────────────────────────────┐
│ Build                                                                        │
└──────────────────────────────────────────────────────────────────────────────┘


Unpack source
─────────────

gpgv: Signature made Sun 13 Mar 2016 09:21:36 PM UTC using RSA key ID 778FA6F5
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./ruby-yajl_1.2.0-3build4.dsc
dpkg-source: info: extracting ruby-yajl in ruby-yajl-1.2.0
dpkg-source: info: unpacking ruby-yajl_1.2.0.orig.tar.gz
dpkg-source: info: unpacking ruby-yajl_1.2.0-3build4.debian.tar.xz
dpkg-source: info: applying mocks-test-fix
dpkg-source: info: applying RSpec3-test-fix

Check disc space
────────────────

Sufficient free space for build

User Environment
────────────────

DEB_BUILD_OPTIONS=parallel=4
HOME=/home/buildd
LANG=C.UTF-8
LOGNAME=buildd
MAIL=/var/mail/buildd
OLDPWD=/
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
PWD=/«PKGBUILDDIR»
SHELL=/bin/sh
SUDO_COMMAND=/usr/sbin/chroot /«CHROOT» su buildd -s /bin/sh -c cd '/«PKGBUILDDIR»' && 'env'
SUDO_GID=2501
SUDO_UID=2001
SUDO_USER=buildd
TERM=unknown
USER=buildd
USERNAME=root

dpkg-buildpackage
─────────────────

dpkg-buildpackage: source package ruby-yajl
dpkg-buildpackage: source version 1.2.0-3build4
dpkg-buildpackage: source distribution xenial
 dpkg-source --before-build ruby-yajl-1.2.0
dpkg-buildpackage: host architecture ppc64el
 fakeroot 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
 debian/rules build-arch
dh build-arch --buildsystem=ruby --with ruby
   dh_testdir -a -O--buildsystem=ruby
   dh_update_autotools_config -a -O--buildsystem=ruby
   dh_auto_configure -a -O--buildsystem=ruby
	dh_ruby --configure
   dh_auto_build -a -O--buildsystem=ruby
	dh_ruby --build
   dh_ruby --build
   dh_auto_test -a -O--buildsystem=ruby
	dh_ruby --test
 fakeroot debian/rules binary-arch
dh binary-arch --buildsystem=ruby --with ruby
   dh_testroot -a -O--buildsystem=ruby
   dh_prep -a -O--buildsystem=ruby
   dh_auto_install -a -O--buildsystem=ruby
	dh_ruby --install /«PKGBUILDDIR»/debian/ruby-yajl
   dh_ruby --install

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install files                                                                │
└──────────────────────────────────────────────────────────────────────────────┘

install -d /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby
install -D -m644 /«PKGBUILDDIR»/lib/yajl/http_stream.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/http_stream.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/deflate/stream_writer.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/deflate/stream_writer.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/deflate/stream_reader.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/deflate/stream_reader.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/deflate.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/deflate.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/json_gem/encoding.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/json_gem/encoding.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/json_gem/parsing.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/json_gem/parsing.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/json_gem.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/json_gem.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/version.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/version.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/bzip2.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/bzip2.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/gzip/stream_writer.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/gzip/stream_writer.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/gzip/stream_reader.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/gzip/stream_reader.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/bzip2/stream_writer.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/bzip2/stream_writer.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/bzip2/stream_reader.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/bzip2/stream_reader.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/gzip.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/gzip.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl.rb

┌──────────────────────────────────────────────────────────────────────────────┐
│ Build native extensions for ruby2.3                                          │
└──────────────────────────────────────────────────────────────────────────────┘

/usr/bin/ruby2.3 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb /«PKGBUILDDIR» debian/ruby-yajl
current directory: /«PKGBUILDDIR»/ext/yajl
/usr/bin/ruby2.3 -r ./siteconf20160313-11036-15j4dfi.rb extconf.rb
creating Makefile
current directory: /«PKGBUILDDIR»/ext/yajl
make V=1 "DESTDIR=" clean
make[1]: Entering directory '/«PKGBUILDDIR»/ext/yajl'
rm -f 
rm -f yajl.so  *.o  *.bak mkmf.log .*.time
make[1]: Leaving directory '/«PKGBUILDDIR»/ext/yajl'
current directory: /«PKGBUILDDIR»/ext/yajl
make V=1 "DESTDIR="
make[1]: Entering directory '/«PKGBUILDDIR»/ext/yajl'
gcc -I. -I/usr/include/powerpc64le-linux-gnu/ruby-2.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops  -o yajl_version.o -c yajl_version.c
gcc -I. -I/usr/include/powerpc64le-linux-gnu/ruby-2.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops  -o yajl_buf.o -c yajl_buf.c
gcc -I. -I/usr/include/powerpc64le-linux-gnu/ruby-2.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops  -o yajl_encode.o -c yajl_encode.c
gcc -I. -I/usr/include/powerpc64le-linux-gnu/ruby-2.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops  -o yajl_alloc.o -c yajl_alloc.c
gcc -I. -I/usr/include/powerpc64le-linux-gnu/ruby-2.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops  -o yajl.o -c yajl.c
gcc -I. -I/usr/include/powerpc64le-linux-gnu/ruby-2.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops  -o yajl_ext.o -c yajl_ext.c
yajl_ext.c: In function ‘rb_yajl_parser_parse’:
yajl_ext.c:472:17: warning: variable ‘stat’ set but not used [-Wunused-but-set-variable]
     yajl_status stat;
                 ^
gcc -I. -I/usr/include/powerpc64le-linux-gnu/ruby-2.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops  -o yajl_lex.o -c yajl_lex.c
gcc -I. -I/usr/include/powerpc64le-linux-gnu/ruby-2.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops  -o yajl_gen.o -c yajl_gen.c
gcc -I. -I/usr/include/powerpc64le-linux-gnu/ruby-2.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O3 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops  -o yajl_parser.o -c yajl_parser.c
rm -f yajl.so
gcc -shared -o yajl.so yajl_version.o yajl_buf.o yajl_encode.o yajl_alloc.o yajl.o yajl_ext.o yajl_lex.o yajl_gen.o yajl_parser.o -L. -L/usr/lib/powerpc64le-linux-gnu -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -L/build/ruby2.3-gmdiU5/ruby2.3-2.3.0/debian/lib -fstack-protector -rdynamic -Wl,-export-dynamic    -lruby-2.3  -lpthread -lgmp -ldl -lcrypt -lm   -lc
make[1]: Leaving directory '/«PKGBUILDDIR»/ext/yajl'
current directory: /«PKGBUILDDIR»/ext/yajl
make V=1 "DESTDIR=" install
make[1]: Entering directory '/«PKGBUILDDIR»/ext/yajl'
/bin/mkdir -p . ./.gem.20160313-11036-7r3mmg/yajl
exit > .RUBYARCHDIR.-.yajl.time
/usr/bin/install -c -m 0755 yajl.so ./.gem.20160313-11036-7r3mmg/yajl
make[1]: Leaving directory '/«PKGBUILDDIR»/ext/yajl'
dh_installchangelogs -pruby-yajl /«PKGBUILDDIR»/CHANGELOG.md upstream

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install Rubygems integration metadata                                        │
└──────────────────────────────────────────────────────────────────────────────┘

generating gemspec at /«PKGBUILDDIR»/debian/ruby-yajl/usr/share/rubygems-integration/2.3.0/specifications/yajl-ruby-1.2.0.gemspec
/usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner

┌──────────────────────────────────────────────────────────────────────────────┐
│ Run tests for ruby2.3 from debian/ruby-tests.rb                              │
└──────────────────────────────────────────────────────────────────────────────┘

RUBYLIB=/«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/powerpc64le-linux-gnu/ruby/vendor_ruby/2.3.0:/«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby:. GEM_PATH=debian/ruby-yajl/usr/share/rubygems-integration/2.3.0:/home/buildd/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/powerpc64le-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all ruby2.3 debian/ruby-tests.rb
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Gzip support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Deflate support is going to be removed in 2.0
DEPRECATION WARNING: Yajl::HttpStream is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0

Yajl
  dump
    should exist as a class-method
    should be able to encode to a string
    should be able to encode to an IO
    should be able to encode with a block supplied
  load
    should exist as a class-method
    should be able to parse from a string
    should be able to parse from an IO
    should be able to parse from a string with a block supplied
    should be able to parse from an IO with a block supplied

Yajl HTTP DELETE request
  should parse a raw response
  should parse a raw response using instance method
  should parse a raw response and symbolize keys
  should parse a deflate compressed response
  should parse a deflate compressed response and symbolize keys
  should parse a gzip compressed response
  should parse a gzip compressed response and symbolize keys
  should raise when an HTTP code that isn't 200 is returned

Yajl HTTP GET request
  should parse a raw response
  should parse a raw response and symbolize keys
  should parse a raw response using instance method
  should parse a chunked response using instance method
  should parse a deflate compressed response
  should parse a deflate compressed response and symbolize keys
  should parse a gzip compressed response
  should parse a gzip compressed response and symbolize keys
  should raise when an HTTP code that isn't 200 is returned

Yajl HTTP error
  should contain the error code in the message
  should provide the HTTP response headers

Yajl HTTP PUT request
  should parse a raw response
  should parse a raw response using instance method
  should parse a raw response with hashed body
  should parse a raw response and symbolize keys
  should parse a deflate compressed response
  should parse a deflate compressed response and symbolize keys
  should parse a gzip compressed response
  should parse a gzip compressed response and symbolize keys
  should raise when an HTTP code that isn't 200 is returned

Yajl HTTP POST request
  should parse a raw response
  should parse a raw response using instance method
  should parse a raw response with hashed body
  should parse a raw response and symbolize keys
  should parse a deflate compressed response
  should parse a deflate compressed response and symbolize keys
  should parse a gzip compressed response
  should parse a gzip compressed response and symbolize keys
  should parse a chunked raw response
  should throw Exception if chunked response and no block given
  should throw InvalidContentType if unable to handle the MIME type
  should raise when an HTTP code that isn't 200 is returned

Passing options to HttpStream instance methods
  should not create a new socket it one is provided
  should create a new socket if one is not provided

Yajl JSON encoder
  should encode unicode.json to an StringIO
  should encode ohai.json to an StringIO
  should encode twitter_stream.json to an StringIO
  should encode item.json to an StringIO
  should encode twitter_search.json to an StringIO
  should encode unicode.json to a Zlib::GzipWriter
  should encode ohai.json to a Zlib::GzipWriter
  should encode twitter_stream.json to a Zlib::GzipWriter
  should encode item.json to a Zlib::GzipWriter
  should encode twitter_search.json to a Zlib::GzipWriter
  should encode unicode.json and return a String
  should encode ohai.json and return a String
  should encode twitter_stream.json and return a String
  should encode item.json and return a String
  should encode twitter_search.json and return a String
  should encode unicode.json call the passed block, passing it a String
  should encode ohai.json call the passed block, passing it a String
  should encode twitter_stream.json call the passed block, passing it a String
  should encode item.json call the passed block, passing it a String
  should encode twitter_search.json call the passed block, passing it a String
  should encode with :pretty turned on and a single space indent, to an IO
  should encode with :pretty turned on and a single space indent, and return a String
  should encode with :pretty turned on and a tab character indent, to an IO
  should encode with :pretty turned on and a tab character indent, and return a String
  should encode with it's class method with :pretty and a tab character indent options set, to an IO
  should encode with it's class method with :pretty and a tab character indent options set, and return a String
  should encode with it's class method with :pretty and a tab character indent options set, to a block
  should encode multiple objects into a single stream, to an IO
  should encode multiple objects into a single stream, and return a String
  should encode all map keys as strings
  should check for and call #to_json if it exists on custom objects
  should encode a hash where the key and value can be symbols
  should encode using a newline or nil terminator
  should encode using a newline or nil terminator, to an IO
  should encode using a newline or nil terminator, using a block
  should not encode NaN
  should not encode Infinity or -Infinity
  should encode with unicode chars in the key
  should be able to escape / characters if html_safe is enabled
  should default to *not* escaping / characters
  return value of #to_json must be a string
  return value of #to_s must be a string
  should raise an exception for deeply nested arrays
  should raise an exception for deeply nested hashes

JSON Gem compatability API
  shoud not mixin #to_json on base objects until compatability has been enabled
  should mixin #to_json on base objects after compatability has been enabled
  should require yajl/json_gem to enable the compatability API
  should allow default parsing options be set with JSON.default_options
  should also allow the json gem's symbolize_names key
  should encode arbitrary classes via their default to_json method
  should have the standard parsing and encoding exceptions mapped
  ported tests for Unicode
    should be able to encode and parse unicode
  ported tests for generation
    should be able to unparse
    should be able to unparse pretty
  ported fixture tests
    should not be able to parse fail.15.json as an IO
    should not be able to parse fail.16.json as an IO
    should not be able to parse fail.17.json as an IO
    should not be able to parse fail.26.json as an IO
    should not be able to parse fail11.json as an IO
    should not be able to parse fail12.json as an IO
    should not be able to parse fail13.json as an IO
    should not be able to parse fail14.json as an IO
    should not be able to parse fail19.json as an IO
    should not be able to parse fail20.json as an IO
    should not be able to parse fail21.json as an IO
    should not be able to parse fail22.json as an IO
    should not be able to parse fail23.json as an IO
    should not be able to parse fail24.json as an IO
    should not be able to parse fail25.json as an IO
    should not be able to parse fail27.json as an IO
    should not be able to parse fail28.json as an IO
    should not be able to parse fail3.json as an IO
    should not be able to parse fail4.json as an IO
    should not be able to parse fail5.json as an IO
    should not be able to parse fail6.json as an IO
    should not be able to parse fail9.json as an IO
    should not be able to parse fail.15.json as a string
    should not be able to parse fail.16.json as a string
    should not be able to parse fail.17.json as a string
    should not be able to parse fail.26.json as a string
    should not be able to parse fail11.json as a string
    should not be able to parse fail12.json as a string
    should not be able to parse fail13.json as a string
    should not be able to parse fail14.json as a string
    should not be able to parse fail19.json as a string
    should not be able to parse fail20.json as a string
    should not be able to parse fail21.json as a string
    should not be able to parse fail22.json as a string
    should not be able to parse fail23.json as a string
    should not be able to parse fail24.json as a string
    should not be able to parse fail25.json as a string
    should not be able to parse fail27.json as a string
    should not be able to parse fail28.json as a string
    should not be able to parse fail3.json as a string
    should not be able to parse fail4.json as a string
    should not be able to parse fail5.json as a string
    should not be able to parse fail6.json as a string
    should not be able to parse fail9.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.codepoints_from_unicode_org.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.contacts.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.db100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.db1000.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.dc_simple_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.deep_arrays.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.difficult_json_c_test_case.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.difficult_json_c_test_case_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.doubles.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.empty_array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.empty_string.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.escaped_bulgarian.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.escaped_foobar.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.item.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample4-nows.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample4.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample5.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.map-spain.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.ns-invoice100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.ns-soap.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.numbers-fp-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.numbers-fp-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.numbers-int-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.numbers-int-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.twitter-search.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.twitter-search2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.unicode.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.yelp.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
    should be able to parse pass3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.codepoints_from_unicode_org.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.contacts.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.db100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.db1000.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.dc_simple_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.deep_arrays.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.difficult_json_c_test_case.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.difficult_json_c_test_case_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.doubles.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.empty_array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.empty_string.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.escaped_bulgarian.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.escaped_foobar.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.item.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample3.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample4-nows.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample4.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.json-org-sample5.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.map-spain.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.ns-invoice100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.ns-soap.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.numbers-fp-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.numbers-fp-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.numbers-int-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.numbers-int-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.twitter-search.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.twitter-search2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.unicode.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass.yelp.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
    should be able to parse pass3.json as a string

ActiveSupport test cases
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"returnTo":{"\/categories":"\/"}} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"return\"To\":":{"\/categories":"\/"}} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"returnTo":{"\/categories":1}} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"returnTo":[1,"a"]} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"returnTo":[1,"\"a\",", "b"]} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "'", "b": "5,000"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "a's, b's and c's", "b": "5,000"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"matzue": "松江", "asakusa": "浅草"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "2007-01-01"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "2007-01-01 01:12:34 Z"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "2007-01-01 01:12:34"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": " 2007-01-01 01:12:34 Z "} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "2007-01-01 : it's your birthday"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse [] as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a":1} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": ""} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a":"\""} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": null} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": true} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": false} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "http:\/\/test.host\/posts\/1"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "\u003cunicode\u0020escape\u003e"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "\\u0020skip double backslashes"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "\u003cbr /\u003e"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
  should be able to parse {"b":["\u003ci\u003e","\u003cb\u003e","\u003cu\u003e"]} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"returnTo":{"\/categories":"\/"}} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"return\"To\":":{"\/categories":"\/"}} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"returnTo":{"\/categories":1}} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"returnTo":[1,"a"]} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"returnTo":[1,"\"a\",", "b"]} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "'", "b": "5,000"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "a's, b's and c's", "b": "5,000"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"matzue": "松江", "asakusa": "浅草"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "2007-01-01"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "2007-01-01 01:12:34 Z"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "2007-01-01 01:12:34"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": " 2007-01-01 01:12:34 Z "} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "2007-01-01 : it's your birthday"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse [] as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a":1} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": ""} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a":"\""} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": null} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": true} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": false} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "http:\/\/test.host\/posts\/1"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "\u003cunicode\u0020escape\u003e"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "\\u0020skip double backslashes"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"a": "\u003cbr /\u003e"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
  should be able to parse {"b":["\u003ci\u003e","\u003cb\u003e","\u003cu\u003e"]} as a string
  should fail parsing {: 1} as an IO
  should fail parsing {: 1} as a string

Chunked parser
  should parse a single chunk
  should parse a single chunk, 3 times
  should parse in two chunks
  should parse in 2 chunks, twice
  should parse 2 JSON strings, in 3 chunks
  should parse 2 JSON strings in 1 chunk
  should parse 2 JSON strings from an IO
  should parse a JSON string an IO and fire callback once
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/chunked_spec.rb:68:in `block (2 levels) in <top (required)>'.
  should parse twitter_stream.json and fire callback 430 times
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/chunked_spec.rb:78:in `block (2 levels) in <top (required)>'.
  should parse twitter_stream.json and fire callback 430 times, with a block as the callback
  should raise a Yajl::ParseError error if multiple JSON strings were found when no on_parse_complete callback assigned

One-off JSON examples
  should parse 23456789012E666 and return Infinity
  should not parse JSON with a comment, with :allow_comments set to false
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/one_off_spec.rb:21:in `block (2 levels) in <top (required)>'.
  should parse JSON with a comment, with :allow_comments set to true
  should not parse invalid UTF8 with :check_utf8 set to true
  should parse invalid UTF8 with :check_utf8 set to false
  should parse using it's class method, from an IO
  should parse using it's class method, from a string with symbolized keys
  should parse using it's class method, from a utf-8 string with multibyte characters, with symbolized keys
  should parse using it's class method, from a string
  should parse using it's class method, from a string with a block
  should parse numbers greater than 2,147,483,648

Parsing JSON Fixtures
  should not be able to parse fail.15.json as an IO
  should not be able to parse fail.16.json as an IO
  should not be able to parse fail.17.json as an IO
  should not be able to parse fail.26.json as an IO
  should not be able to parse fail11.json as an IO
  should not be able to parse fail12.json as an IO
  should not be able to parse fail13.json as an IO
  should not be able to parse fail14.json as an IO
  should not be able to parse fail19.json as an IO
  should not be able to parse fail20.json as an IO
  should not be able to parse fail21.json as an IO
  should not be able to parse fail22.json as an IO
  should not be able to parse fail23.json as an IO
  should not be able to parse fail24.json as an IO
  should not be able to parse fail25.json as an IO
  should not be able to parse fail27.json as an IO
  should not be able to parse fail28.json as an IO
  should not be able to parse fail3.json as an IO
  should not be able to parse fail4.json as an IO
  should not be able to parse fail5.json as an IO
  should not be able to parse fail6.json as an IO
  should not be able to parse fail9.json as an IO
  should not be able to parse fail.15.json as a string
  should not be able to parse fail.16.json as a string
  should not be able to parse fail.17.json as a string
  should not be able to parse fail.26.json as a string
  should not be able to parse fail11.json as a string
  should not be able to parse fail12.json as a string
  should not be able to parse fail13.json as a string
  should not be able to parse fail14.json as a string
  should not be able to parse fail19.json as a string
  should not be able to parse fail20.json as a string
  should not be able to parse fail21.json as a string
  should not be able to parse fail22.json as a string
  should not be able to parse fail23.json as a string
  should not be able to parse fail24.json as a string
  should not be able to parse fail25.json as a string
  should not be able to parse fail27.json as a string
  should not be able to parse fail28.json as a string
  should not be able to parse fail3.json as a string
  should not be able to parse fail4.json as a string
  should not be able to parse fail5.json as a string
  should not be able to parse fail6.json as a string
  should not be able to parse fail9.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.codepoints_from_unicode_org.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.contacts.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.db100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.db1000.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.dc_simple_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.deep_arrays.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.difficult_json_c_test_case.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.difficult_json_c_test_case_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.doubles.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.empty_array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.empty_string.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.escaped_bulgarian.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.escaped_foobar.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.item.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample4-nows.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample4.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample5.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.map-spain.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.ns-invoice100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.ns-soap.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.numbers-fp-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.numbers-fp-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.numbers-int-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.numbers-int-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.twitter-search.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.twitter-search2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.unicode.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.yelp.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
  should be able to parse pass3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.codepoints_from_unicode_org.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.contacts.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.db100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.db1000.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.dc_simple_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.deep_arrays.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.difficult_json_c_test_case.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.difficult_json_c_test_case_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.doubles.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.empty_array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.empty_string.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.escaped_bulgarian.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.escaped_foobar.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.item.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample3.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample4-nows.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample4.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.json-org-sample5.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.map-spain.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.ns-invoice100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.ns-soap.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.numbers-fp-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.numbers-fp-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.numbers-int-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.numbers-int-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.twitter-search.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.twitter-search2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.unicode.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass.yelp.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
  should be able to parse pass3.json as a string

Deprecation Warnings:

Using `should_receive` from rspec-mocks' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /«PKGBUILDDIR»/spec/http/http_delete_spec.rb:40:in `prepare_mock_request_dump'.

Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` instead. Called from /«PKGBUILDDIR»/spec/global/global_spec.rb:6:in `block (3 levels) in <top (required)>'.


If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.

2 deprecation warnings total

Finished in 0.67173 seconds (files took 0.25273 seconds to load)
409 examples, 0 failures


┌──────────────────────────────────────────────────────────────────────────────┐
│ dh_ruby --install finished                                                   │
└──────────────────────────────────────────────────────────────────────────────┘

   dh_installdocs -a -O--buildsystem=ruby
   dh_ruby_fixdocs -a -O--buildsystem=ruby
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/«PKGBUILDDIR»'
dh_installchangelogs CHANGELOG.md
make[1]: Leaving directory '/«PKGBUILDDIR»'
   dh_installexamples -a -O--buildsystem=ruby
   dh_perl -a -O--buildsystem=ruby
   dh_link -a -O--buildsystem=ruby
   dh_strip_nondeterminism -a -O--buildsystem=ruby
   dh_compress -X.rb -a -O--buildsystem=ruby
   dh_fixperms -a -O--buildsystem=ruby
   dh_strip -a -O--buildsystem=ruby
dh_strip debug symbol extraction: enabling -a due to Build-Debug-Symbols: yes in /CurrentlyBuilding
dh_strip debug symbol extraction: all non-arch-all packages for this build platform ppc64el: ruby-yajl 
dh_strip debug symbol extraction: packages to act on: ruby-yajl 
dh_strip debug symbol extraction: ignored packages: 
dpkg-gencontrol: warning: -is is deprecated; it is without effect
dpkg-gencontrol: warning: -ip is deprecated; it is without effect
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe
/usr/bin/pkg_create_dbgsym: deferring build of .ddeb to dh_gencontrol
   dh_makeshlibs -a -O--buildsystem=ruby
   dh_shlibdeps -a -O--buildsystem=ruby
   dh_ruby_fixdepends -a -O--buildsystem=ruby
   dh_installdeb -a -O--buildsystem=ruby
   dh_gencontrol -a -O--buildsystem=ruby
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe
dh_gencontrol debug symbol wrapper: all non-arch-all packages for this build platform ppc64el: ruby-yajl 
dh_gencontrol debug symbol wrapper: packages to act on: ruby-yajl 
dh_gencontrol debug symbol wrapper: ignored packages: 
dh_gencontrol debug symbol wrapper: processing package ruby-yajl (pkgdir debian/ruby-yajl, ddeb package dir debian/ruby-yajl-dbgsym)
dh_gencontrol debug symbol wrapper: building ruby-yajl-dbgsym_1.2.0-3build4_ppc64el.ddeb
dpkg-deb: building package 'ruby-yajl-dbgsym' in '../ruby-yajl-dbgsym_1.2.0-3build4_ppc64el.ddeb'.
dh_gencontrol debug symbol wrapper: dpkg-distaddfile ruby-yajl-dbgsym_1.2.0-3build4_ppc64el.ddeb ruby extra
dpkg-distaddfile: warning: File::FcntlLock not available; using flock which is not NFS-safe
   dh_md5sums -a -O--buildsystem=ruby
   dh_builddeb -a -O--buildsystem=ruby
INFO: pkgstriptranslations version 129
pkgstriptranslations: processing ruby-yajl (in debian/ruby-yajl); do_strip: , oemstrip: 
pkgmaintainermangler: Maintainer field overridden to "Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>"
pkgstripfiles: processing control file: debian/ruby-yajl/DEBIAN/control, package ruby-yajl, directory debian/ruby-yajl
.. removing usr/share/doc/ruby-yajl/changelog.gz
pkgstripfiles: Truncating usr/share/doc/ruby-yajl/changelog.Debian.gz to topmost ten records
pkgstripfiles: Running PNG optimization (using 4 cpus) for package ruby-yajl ...
pkgstripfiles: No PNG files.
dpkg-deb: building package 'ruby-yajl' in '../ruby-yajl_1.2.0-3build4_ppc64el.deb'.
 dpkg-genchanges -B -mLaunchpad Build Daemon <buildd@bos01-ppc64el-009.buildd> >../ruby-yajl_1.2.0-3build4_ppc64el.changes
dpkg-genchanges: binary-only arch-specific upload (source code and arch-indep packages not included)
 dpkg-source --after-build ruby-yajl-1.2.0
dpkg-buildpackage: binary-only upload (no source included)
────────────────────────────────────────────────────────────────────────────────
Build finished at 20160313-2249

Finished
────────

I: Built successfully

┌──────────────────────────────────────────────────────────────────────────────┐
│ Post Build Chroot                                                            │
└──────────────────────────────────────────────────────────────────────────────┘


┌──────────────────────────────────────────────────────────────────────────────┐
│ Changes                                                                      │
└──────────────────────────────────────────────────────────────────────────────┘


ruby-yajl_1.2.0-3build4_ppc64el.changes:
────────────────────────────────────────

Format: 1.8
Date: Sun, 13 Mar 2016 21:17:39 +0000
Source: ruby-yajl
Binary: ruby-yajl
Architecture: ppc64el
Version: 1.2.0-3build4
Distribution: xenial-proposed
Urgency: medium
Maintainer: Launchpad Build Daemon <buildd@bos01-ppc64el-009.buildd>
Changed-By: Matthias Klose <doko@ubuntu.com>
Description:
 ruby-yajl  - Ruby interface to Yajl, a JSON stream-based parser library
Changes:
 ruby-yajl (1.2.0-3build4) xenial; urgency=medium
 .
   * No-change rebuild for ruby2.3-only support.
Checksums-Sha1:
 fa91c6b7d81c9300d4652c231b235b2e2bec1702 39878 ruby-yajl-dbgsym_1.2.0-3build4_ppc64el.ddeb
 61df27d92fb70e34d28c305562fb1f0db33578fa 37118 ruby-yajl_1.2.0-3build4_ppc64el.deb
Checksums-Sha256:
 4d76494af13a5a54cf2c353fae20d08de69f77d95c074d33a753a516c2e710b8 39878 ruby-yajl-dbgsym_1.2.0-3build4_ppc64el.ddeb
 4d210f3a826272cd8eedd070e7d79a2b3ea324bd51c8b0132dcfef9a7a108a0e 37118 ruby-yajl_1.2.0-3build4_ppc64el.deb
Files:
 e33829785424a600daf5320ede6fda8a 39878 ruby extra ruby-yajl-dbgsym_1.2.0-3build4_ppc64el.ddeb
 fea7be2f9ae9dbb1c943c7adf7d25b59 37118 ruby optional ruby-yajl_1.2.0-3build4_ppc64el.deb

┌──────────────────────────────────────────────────────────────────────────────┐
│ Package contents                                                             │
└──────────────────────────────────────────────────────────────────────────────┘


ruby-yajl_1.2.0-3build4_ppc64el.deb
───────────────────────────────────

 new debian package, version 2.0.
 size 37118 bytes: control archive=1737 bytes.
    1094 bytes,    28 lines      control              
    2364 bytes,    28 lines      md5sums              
 Package: ruby-yajl
 Version: 1.2.0-3build4
 Architecture: ppc64el
 Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
 Original-Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
 Installed-Size: 155
 Depends: ruby (>= 1:2.3~0), libc6 (>= 2.17), libruby2.3 (>= 2.3.0~preview2)
 Conflicts: libyajl-ruby
 Replaces: libyajl-ruby
 Section: ruby
 Priority: optional
 Homepage: http://github.com/brianmario/yajl-ruby
 Description: Ruby interface to Yajl, a JSON stream-based parser library
  Supported features include,
  .
  JSON parsing and encoding directly to and from an IO stream
  (file, socket, etc) or String. Compressed stream parsing and
  encoding supported for Bzip2, Gzip and Deflate.
  .
  Parse and encode *multiple* JSON objects to and from streams or strings
  continuously.
  .
  JSON gem compatibility API - allows yajl-ruby to be used as a drop-in
  replacement for the JSON gem
  .
  Basic HTTP client (only GET requests supported for now) which parses JSON
  directly off the response body *as it's being received*
 Ruby-Versions: ruby2.3

drwxr-xr-x root/root         0 2016-03-13 22:49 ./
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/powerpc64le-linux-gnu/
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/powerpc64le-linux-gnu/ruby/
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/powerpc64le-linux-gnu/ruby/vendor_ruby/
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/powerpc64le-linux-gnu/ruby/vendor_ruby/2.3.0/
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/powerpc64le-linux-gnu/ruby/vendor_ruby/2.3.0/yajl/
-rw-r--r-- root/root     67880 2016-03-13 22:49 ./usr/lib/powerpc64le-linux-gnu/ruby/vendor_ruby/2.3.0/yajl/yajl.so
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/ruby/
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/
-rw-r--r-- root/root      2654 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl.rb
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/
-rw-r--r-- root/root       355 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/bzip2.rb
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/bzip2/
-rw-r--r-- root/root       899 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/bzip2/stream_reader.rb
-rw-r--r-- root/root       392 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/bzip2/stream_writer.rb
-rw-r--r-- root/root       243 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/deflate.rb
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/deflate/
-rw-r--r-- root/root      1334 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/deflate/stream_reader.rb
-rw-r--r-- root/root       546 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/deflate/stream_writer.rb
-rw-r--r-- root/root       234 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/gzip.rb
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/gzip/
-rw-r--r-- root/root       903 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/gzip/stream_reader.rb
-rw-r--r-- root/root       368 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/gzip/stream_writer.rb
-rw-r--r-- root/root      7376 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/http_stream.rb
-rw-r--r-- root/root       314 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/json_gem.rb
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/json_gem/
-rw-r--r-- root/root      1354 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/json_gem/encoding.rb
-rw-r--r-- root/root       653 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/json_gem/parsing.rb
-rw-r--r-- root/root        36 2016-03-13 22:49 ./usr/lib/ruby/vendor_ruby/yajl/version.rb
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/share/
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/share/doc/
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/share/doc/ruby-yajl/
-rw-r--r-- root/root      4990 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/README.md.gz
-rw-r--r-- root/root      1237 2016-03-13 22:49 ./usr/share/doc/ruby-yajl/changelog.Debian.gz
-rw-r--r-- root/root      3063 2015-07-08 14:47 ./usr/share/doc/ruby-yajl/copyright
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/share/doc/ruby-yajl/examples/
drwxr-xr-x root/root         0 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/encoding/
-rw-r--r-- root/root       842 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/encoding/chunked_encoding.rb
-rw-r--r-- root/root       332 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/encoding/one_shot.rb
-rw-r--r-- root/root       338 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/encoding/to_an_io.rb
drwxr-xr-x root/root         0 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/http/
-rw-r--r-- root/root       389 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/http/twitter_search_api.rb
-rw-r--r-- root/root       714 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/http/twitter_stream_api.rb
drwxr-xr-x root/root         0 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/parsing/
-rw-r--r-- root/root       355 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/parsing/from_file.rb
-rw-r--r-- root/root       286 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/parsing/from_stdin.rb
-rw-r--r-- root/root       341 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/parsing/from_string.rb
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/share/rubygems-integration/
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/share/rubygems-integration/2.3.0/
drwxr-xr-x root/root         0 2016-03-13 22:49 ./usr/share/rubygems-integration/2.3.0/specifications/
-rw-r--r-- root/root     10345 2016-03-13 22:49 ./usr/share/rubygems-integration/2.3.0/specifications/yajl-ruby-1.2.0.gemspec


┌──────────────────────────────────────────────────────────────────────────────┐
│ Post Build                                                                   │
└──────────────────────────────────────────────────────────────────────────────┘


┌──────────────────────────────────────────────────────────────────────────────┐
│ Cleanup                                                                      │
└──────────────────────────────────────────────────────────────────────────────┘

Not removing build depends: as requested
Keeping session: 

┌──────────────────────────────────────────────────────────────────────────────┐
│ Summary                                                                      │
└──────────────────────────────────────────────────────────────────────────────┘

Build Architecture: ppc64el
Build-Space: 5152
Build-Time: 11
Distribution: xenial-proposed
Host Architecture: ppc64el
Install-Time: 16
Job: ruby-yajl_1.2.0-3build4.dsc
Machine Architecture: ppc64el
Package: ruby-yajl
Package-Time: 29
Source-Version: 1.2.0-3build4
Space: 5152
Status: successful
Version: 1.2.0-3build4
────────────────────────────────────────────────────────────────────────────────
Finished at 20160313-2249
Build needed 00:00:29, 5152k disc space
RUN: /usr/share/launchpad-buildd/slavebin/scan-for-processes ['scan-for-processes', 'PACKAGEBUILD-9345466']
Scanning for processes to kill in build /home/buildd/build-PACKAGEBUILD-9345466/chroot-autobuild...
RUN: /usr/share/launchpad-buildd/slavebin/umount-chroot ['umount-chroot', 'PACKAGEBUILD-9345466']
Unmounting chroot for build PACKAGEBUILD-9345466...
RUN: /usr/share/launchpad-buildd/slavebin/remove-build ['remove-build', 'PACKAGEBUILD-9345466']
Removing build PACKAGEBUILD-9345466