API tools faq
paste
Advertisement
Guest User

cantupdate

a guest
Jan 9th, 2015
307
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.14 KB | None | 0 0
raw download clone embed print report
  1. These are the packages that would be merged, in order:
  2.  
  3. Calculating dependencies... done!
  4. [ebuild N ] sys-kernel/linux-headers-3.16 0 KiB
  5. [ebuild N ] virtual/os-headers-0 0 KiB
  6. [ebuild R ] net-firewall/iptables-1.4.21-r1 USE="-ipv6* -netlink -static-libs" 0 KiB
  7. [ebuild R ] sys-apps/iproute2-3.8.0 USE="berkdb iptables -atm -ipv6* -minimal" 0 KiB
  8. [ebuild U ] dev-libs/openssl-1.0.1k [1.0.1j] USE="gmp (sse2) tls-heartbeat zlib -bindist -kerberos -rfc3779 -static-libs {-test} -vanilla" 0 KiB
  9. [ebuild U ] dev-libs/libevent-2.0.22 [2.0.21-r1] USE="ssl threads -debug% -static-libs {-test}" 0 KiB
  10. [ebuild U ] app-admin/perl-cleaner-2.19 [2.16] 0 KiB
  11. [ebuild U ] sys-devel/gettext-0.19.3 [0.18.3.2] USE="cxx ncurses nls openmp -acl -cvs -doc -emacs -git -java -static-libs" 0 KiB
  12. [ebuild N ] media-libs/gstreamer-1.2.4-r2:1.0 USE="introspection nls orc {-test}" 0 KiB
  13. [ebuild NS ] sys-kernel/gentoo-sources-3.14.27:3.14.27 [3.14.21:3.14.21] USE="-build -deblob -experimental -symlink" 23,624 KiB
  14. [ebuild R ] www-client/firefox-31.3.0 USE="gstreamer* jit minimal -bindist* -custom-cflags -custom-optimization -dbus -debug -hardened (-pgo) -pulseaudio (-selinux) -startup-notification -system-cairo -system-icu -system-jpeg -system-libvpx -system-sqlite {-test} -wifi" LINGUAS="-af -ar -as -ast -be -bg -bn_BD -bn_IN -br -bs -ca -cs -csb -cy -da -de -el -en_GB -en_ZA -eo -es_AR -es_CL -es_ES -es_MX -et -eu -fa -fi -fr -fy_NL -ga_IE -gd -gl -gu_IN -he -hi_IN -hr -hu -hy_AM -id -is -it -ja -kk -km -kn -ko -ku -lt -lv -mai -mk -ml -mr -nb_NO -nl -nn_NO -or -pa_IN -pl -pt_BR -pt_PT -rm -ro -ru -si -sk -sl -son -sq -sr -sv_SE -ta -te -th -tr -uk -vi -xh -zh_CN -zh_TW -zu" 144,558 KiB
  15.  
  16. Total: 11 packages (4 upgrades, 3 new, 1 in new slot, 3 reinstalls), Size of downloads: 168,182 KiB
  17.  
  18. Would you like to merge these packages? [Yes/No] yes
  19.  
  20. >>> Verifying ebuild manifests
  21. >>> Running pre-merge checks for www-client/firefox-31.3.0
  22. [www-client/firefox-31.3.0] bash: /usr/lib/portage/python2.7/ebuild.sh: No such file or directory
  23. /bin/bash: /usr/lib/portage/python2.7/misc-functions.sh: No such file or directory
  24. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  25. * behavior is known to be triggered by things such as failed variable
  26. * assignments (bug #190128) or bad substitution errors (bug #200313).
  27. * Normally, before exiting, bash should have displayed an error message
  28. * above. If bash did not produce an error message above, it's possible
  29. * that the ebuild has called `exit` when it should have called `die`
  30. * instead. This behavior may also be triggered by a corrupt bash binary or
  31. * a hardware problem such as memory or cpu malfunction. If the problem is
  32. * not reproducible or it appears to occur randomly, then it is likely to
  33. * be triggered by a hardware problem. If you suspect a hardware problem
  34. * then you should try some basic hardware diagnostics such as memtest.
  35. * Please do not report this as a bug unless it is consistently
  36. * reproducible and you are sure that your bash binary and hardware are
  37. * functioning properly.
  38. [www-client/firefox-31.3.0] bash: /usr/lib/portage/python2.7/ebuild.sh: No such file or directory
  39. * The ebuild phase 'pretend' has exited unexpectedly. This type of
  40. * behavior is known to be triggered by things such as failed variable
  41. * assignments (bug #190128) or bad substitution errors (bug #200313).
  42. * Normally, before exiting, bash should have displayed an error message
  43. * above. If bash did not produce an error message above, it's possible
  44. * that the ebuild has called `exit` when it should have called `die`
  45. * instead. This behavior may also be triggered by a corrupt bash binary or
  46. * a hardware problem such as memory or cpu malfunction. If the problem is
  47. * not reproducible or it appears to occur randomly, then it is likely to
  48. * be triggered by a hardware problem. If you suspect a hardware problem
  49. * then you should try some basic hardware diagnostics such as memtest.
  50. * Please do not report this as a bug unless it is consistently
  51. * reproducible and you are sure that your bash binary and hardware are
  52. * functioning properly.
  53. /bin/bash: /usr/lib/portage/python2.7/misc-functions.sh: No such file or directory
  54. * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
  55. * behavior is known to be triggered by things such as failed variable
  56. * assignments (bug #190128) or bad substitution errors (bug #200313).
  57. * Normally, before exiting, bash should have displayed an error message
  58. * above. If bash did not produce an error message above, it's possible
  59. * that the ebuild has called `exit` when it should have called `die`
  60. * instead. This behavior may also be triggered by a corrupt bash binary or
  61. * a hardware problem such as memory or cpu malfunction. If the problem is
  62. * not reproducible or it appears to occur randomly, then it is likely to
  63. * be triggered by a hardware problem. If you suspect a hardware problem
  64. * then you should try some basic hardware diagnostics such as memtest.
  65. * Please do not report this as a bug unless it is consistently
  66. * reproducible and you are sure that your bash binary and hardware are
  67. * functioning properly.
  68.  
  69. * Messages for package www-client/firefox-31.3.0:
  70.  
  71. * The ebuild phase 'pretend' has exited unexpectedly. This type of
  72. * behavior is known to be triggered by things such as failed variable
  73. * assignments (bug #190128) or bad substitution errors (bug #200313).
  74. * Normally, before exiting, bash should have displayed an error message
  75. * above. If bash did not produce an error message above, it's possible
  76. * that the ebuild has called `exit` when it should have called `die`
  77. * instead. This behavior may also be triggered by a corrupt bash binary or
  78. * a hardware problem such as memory or cpu malfunction. If the problem is
  79. * not reproducible or it appears to occur randomly, then it is likely to
  80. * be triggered by a hardware problem. If you suspect a hardware problem
  81. * then you should try some basic hardware diagnostics such as memtest.
  82. * Please do not report this as a bug unless it is consistently
  83. * reproducible and you are sure that your bash binary and hardware are
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!