spacepaste

Paste details

reply | raw

  1.  
  2. Failed to import the site module
  3. Traceback (most recent call last):
  4. File "/usr/lib/python3.4/site.py", line 74, in <module>
  5. import _sitebuiltins
  6. SystemError: Negative size passed to PyUnicode_New
  7. * ERROR: sys-libs/glibc-2.24-r3::gentoo failed (prerm phase):
  8. * filter-bash-environment.py failed
  9. *
  10. * Call stack:
  11. * ebuild.sh, line 538: Called __preprocess_ebuild_env
  12. * phase-functions.sh, line 156: Called __filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
  13. * phase-functions.sh, line 137: Called die
  14. * The specific snippet of code:
  15. * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
  16. *
  17. * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.24-r3::gentoo'`,
  18. * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.24-r3::gentoo'`.
  19. * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/build.log'.
  20. * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/environment'.
  21. * Working directory: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/homedir'
  22. * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/work/glibc-2.24'
  23. Traceback (most recent call last):
  24. File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 9, in <module>
  25. import logging
  26. File "/usr/lib/python3.4/logging/__init__.py", line 26, in <module>
  27. import sys, os, time, io, traceback, warnings, weakref, collections
  28. File "/usr/lib/python3.4/traceback.py", line 3, in <module>
  29. import linecache
  30. File "/usr/lib/python3.4/linecache.py", line 10, in <module>
  31. import tokenize
  32. File "/usr/lib/python3.4/tokenize.py", line 32, in <module>
  33. import re
  34. File "/usr/lib/python3.4/re.py", line 123, in <module>
  35. import sre_compile
  36. SystemError: Negative size passed to PyUnicode_New
  37. * The ebuild phase 'prerm' has exited unexpectedly. This type of behavior
  38. * is known to be triggered by things such as failed variable assignments
  39. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  40. * exiting, bash should have displayed an error message above. If bash did
  41. * not produce an error message above, it's possible that the ebuild has
  42. * called `exit` when it should have called `die` instead. This behavior
  43. * may also be triggered by a corrupt bash binary or a hardware problem
  44. * such as memory or cpu malfunction. If the problem is not reproducible or
  45. * it appears to occur randomly, then it is likely to be triggered by a
  46. * hardware problem. If you suspect a hardware problem then you should try
  47. * some basic hardware diagnostics such as memtest. Please do not report
  48. * this as a bug unless it is consistently reproducible and you are sure
  49. * that your bash binary and hardware are functioning properly.
  50. Failed to import the site module
  51. Traceback (most recent call last):
  52. File "/usr/lib/python3.4/site.py", line 72, in <module>
  53. import os
  54. File "/usr/lib/python3.4/os.py", line 57, in <module>
  55. import posixpath as path
  56. File "/usr/lib/python3.4/posixpath.py", line 16, in <module>
  57. import genericpath
  58. SystemError: Negative size passed to PyUnicode_New
  59. * ERROR: sys-libs/glibc-2.24-r3::gentoo failed:
  60. * filter-bash-environment.py failed
  61. *
  62. * Call stack:
  63. * misc-functions.sh, line 17: Called source '/usr/lib/portage/python3.4/ebuild.sh'
  64. * ebuild.sh, line 538: Called __preprocess_ebuild_env
  65. * phase-functions.sh, line 156: Called __filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
  66. * phase-functions.sh, line 137: Called die
  67. * The specific snippet of code:
  68. * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
  69. *
  70. * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.24-r3::gentoo'`,
  71. * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.24-r3::gentoo'`.
  72. * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/build.log'.
  73. * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/environment'.
  74. * Working directory: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/homedir'
  75. * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/work/glibc-2.24'
  76. Traceback (most recent call last):
  77. File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 11, in <module>
  78. import pickle
  79. File "/usr/lib/python3.4/pickle.py", line 1560, in <module>
  80. from _pickle import (
  81. SystemError: Negative size passed to PyUnicode_New
  82. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  83. * behavior is known to be triggered by things such as failed variable
  84. * assignments (bug #190128) or bad substitution errors (bug #200313).
  85. * Normally, before exiting, bash should have displayed an error message
  86. * above. If bash did not produce an error message above, it's possible
  87. * that the ebuild has called `exit` when it should have called `die`
  88. * instead. This behavior may also be triggered by a corrupt bash binary or
  89. * a hardware problem such as memory or cpu malfunction. If the problem is
  90. * not reproducible or it appears to occur randomly, then it is likely to
  91. * be triggered by a hardware problem. If you suspect a hardware problem
  92. * then you should try some basic hardware diagnostics such as memtest.
  93. * Please do not report this as a bug unless it is consistently
  94. * reproducible and you are sure that your bash binary and hardware are
  95. * functioning properly.
  96. !!! FAILED prerm: 1
  97. Failed to import the site module
  98. Traceback (most recent call last):
  99. File "/usr/lib/python3.4/site.py", line 74, in <module>
  100. import _sitebuiltins
  101. SystemError: Negative size passed to PyUnicode_New
  102. * ERROR: sys-libs/glibc-2.24-r3::gentoo failed (postrm phase):
  103. * filter-bash-environment.py failed
  104. *
  105. * Call stack:
  106. * ebuild.sh, line 538: Called __preprocess_ebuild_env
  107. * phase-functions.sh, line 156: Called __filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
  108. * phase-functions.sh, line 137: Called die
  109. * The specific snippet of code:
  110. * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
  111. *
  112. * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.24-r3::gentoo'`,
  113. * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.24-r3::gentoo'`.
  114. * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/build.log'.
  115. * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/environment'.
  116. * Working directory: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/homedir'
  117. * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/work/glibc-2.24'
  118. Traceback (most recent call last):
  119. File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 9, in <module>
  120. import logging
  121. File "/usr/lib/python3.4/logging/__init__.py", line 26, in <module>
  122. import sys, os, time, io, traceback, warnings, weakref, collections
  123. File "/usr/lib/python3.4/traceback.py", line 3, in <module>
  124. import linecache
  125. File "/usr/lib/python3.4/linecache.py", line 10, in <module>
  126. import tokenize
  127. File "/usr/lib/python3.4/tokenize.py", line 32, in <module>
  128. import re
  129. File "/usr/lib/python3.4/re.py", line 123, in <module>
  130. import sre_compile
  131. SystemError: Negative size passed to PyUnicode_New
  132. * The ebuild phase 'postrm' has exited unexpectedly. This type of behavior
  133. * is known to be triggered by things such as failed variable assignments
  134. * (bug #190128) or bad substitution errors (bug #200313). Normally, before
  135. * exiting, bash should have displayed an error message above. If bash did
  136. * not produce an error message above, it's possible that the ebuild has
  137. * called `exit` when it should have called `die` instead. This behavior
  138. * may also be triggered by a corrupt bash binary or a hardware problem
  139. * such as memory or cpu malfunction. If the problem is not reproducible or
  140. * it appears to occur randomly, then it is likely to be triggered by a
  141. * hardware problem. If you suspect a hardware problem then you should try
  142. * some basic hardware diagnostics such as memtest. Please do not report
  143. * this as a bug unless it is consistently reproducible and you are sure
  144. * that your bash binary and hardware are functioning properly.
  145. Failed to import the site module
  146. Traceback (most recent call last):
  147. File "/usr/lib/python3.4/site.py", line 72, in <module>
  148. import os
  149. File "/usr/lib/python3.4/os.py", line 57, in <module>
  150. import posixpath as path
  151. File "/usr/lib/python3.4/posixpath.py", line 16, in <module>
  152. import genericpath
  153. SystemError: Negative size passed to PyUnicode_New
  154. * ERROR: sys-libs/glibc-2.24-r3::gentoo failed:
  155. * filter-bash-environment.py failed
  156. *
  157. * Call stack:
  158. * misc-functions.sh, line 17: Called source '/usr/lib/portage/python3.4/ebuild.sh'
  159. * ebuild.sh, line 538: Called __preprocess_ebuild_env
  160. * phase-functions.sh, line 156: Called __filter_readonly_variables '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox'
  161. * phase-functions.sh, line 137: Called die
  162. * The specific snippet of code:
  163. * "${PORTAGE_PYTHON:-/usr/bin/python}" "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || die "filter-bash-environment.py failed"
  164. *
  165. * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.24-r3::gentoo'`,
  166. * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.24-r3::gentoo'`.
  167. * The complete build log is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/build.log'.
  168. * The ebuild environment file is located at '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/temp/environment'.
  169. * Working directory: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/homedir'
  170. * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.24-r3/work/glibc-2.24'
  171. Traceback (most recent call last):
  172. File "/usr/lib/portage/python3.4/ebuild-ipc.py", line 11, in <module>
  173. import pickle
  174. File "/usr/lib/python3.4/pickle.py", line 1560, in <module>
  175. from _pickle import (
  176. SystemError: Negative size passed to PyUnicode_New
  177. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  178. * behavior is known to be triggered by things such as failed variable
  179. * assignments (bug #190128) or bad substitution errors (bug #200313).
  180. * Normally, before exiting, bash should have displayed an error message
  181. * above. If bash did not produce an error message above, it's possible
  182. * that the ebuild has called `exit` when it should have called `die`
  183. * instead. This behavior may also be triggered by a corrupt bash binary or
  184. * a hardware problem such as memory or cpu malfunction. If the problem is
  185. * not reproducible or it appears to occur randomly, then it is likely to
  186. * be triggered by a hardware problem. If you suspect a hardware problem
  187. * then you should try some basic hardware diagnostics such as memtest.
  188. * Please do not report this as a bug unless it is consistently
  189. * reproducible and you are sure that your bash binary and hardware are
  190. * functioning properly.
  191. !!! FAILED postrm: 1
  192. * The 'postrm' phase of the 'sys-libs/glibc-2.24-r3' package has failed
  193. * with exit value 1.
  194. *
  195. * The problem occurred while executing the ebuild file named
  196. * 'glibc-2.24-r3.ebuild' located in the '/var/db/pkg/sys-
  197. * libs/glibc-2.24-r3' directory. If necessary, manually remove the
  198. * environment.bz2 file and/or the ebuild file located in that directory.
  199. *
  200. * Removal of the environment.bz2 file is preferred since it may allow the
  201. * removal phases to execute successfully. The ebuild will be sourced and
  202. * the eclasses from the current portage tree will be used when necessary.
  203. * Removal of the ebuild file will cause the pkg_prerm() and pkg_postrm()
  204. * removal phases to be skipped entirely.
  205.  
Powered by spacepaste. Paste removal.