public inbox for gentoo-binhost-autobuilds@lists.gentoo.org
 help / color / mirror / Atom feed
From: binhost@demeter.amd64.dev.gentoo.org
To: gentoo-binhost-autobuilds@lists.gentoo.org
Subject: [gentoo-binhost-autobuilds] [binhost amd64/17.1/x86-64] Update possibly failed
Date: Thu, 26 Oct 2023 10:24:46 +0000 (UTC)	[thread overview]
Message-ID: <20231026102446.28E3F268042@demeter.amd64.dev.gentoo.org> (raw)

Binhost amd64/17.1/x86-64 update produced long output


Starting run at Thu Oct 26 10:17:01 UTC 2023
Machine binhost-amd64-x86-64

Spawning container binhost-amd64-x86-64 on /var/lib/machines/binhost-amd64-x86-64.
Press Ctrl-] three times within 1s to kill container.

 * IMPORTANT: 27 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


 * IMPORTANT: 27 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

>>> Verifying ebuild manifests
>>> Running pre-merge checks for dev-java/openjdk-bin-17.0.8.1_p1
>>> Running pre-merge checks for dev-java/bcprov-1.74
>>> Emerging (1 of 4) dev-java/openjdk-bin-17.0.8.1_p1::gentoo
>>> Installing (1 of 4) dev-java/openjdk-bin-17.0.8.1_p1::gentoo
>>> Completed (1 of 4) dev-java/openjdk-bin-17.0.8.1_p1::gentoo
>>> Emerging (2 of 4) dev-java/bcprov-1.74::gentoo
>>> Emerging (3 of 4) dev-java/commons-lang-3.13.0::gentoo
>>> Installing (3 of 4) dev-java/commons-lang-3.13.0::gentoo
>>> Completed (3 of 4) dev-java/commons-lang-3.13.0::gentoo
>>> Installing (2 of 4) dev-java/bcprov-1.74::gentoo
>>> Completed (2 of 4) dev-java/bcprov-1.74::gentoo
>>> Emerging (4 of 4) app-text/pdftk-3.3.3-r2::gentoo
>>> Installing (4 of 4) app-text/pdftk-3.3.3-r2::gentoo
>>> Completed (4 of 4) app-text/pdftk-3.3.3-r2::gentoo

 * IMPORTANT: 27 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 * 
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence of this, it often becomes necessary to run 
 * `emerge --update --newuse --deep @world` prior to depclean.

Calculating dependencies  ..\b\b... done!
>>> Calculating removal order...

 dev-cpp/abseil-cpp
    selected: 20230125.2 
   protected: none 
     omitted: none 

All selected packages: =dev-cpp/abseil-cpp-20230125.2

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1
>>> Unmerging (1 of 1) dev-cpp/abseil-cpp-20230125.2...
Packages installed:   1730
Packages in world:    48
Packages in system:   49
Required packages:    1730
Number removed:       1

 * GNU info directory index is up-to-date.

 * IMPORTANT: 27 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

>>> Building file list for packages cleaning...
>>> Cleaning binary packages...
 [  125.1 M ] dev-java/openjdk-bin-17.0.6_p10
 [    1.6 M ] dev-python/lxml-4.9.2
 [    1.1 M ] dev-python/pillow-10.0.0
 [  220.0 K ] dev-util/spirv-headers-1.3.250
 [    2.3 M ] dev-util/spirv-tools-1.3.250
 [    1.2 M ] dev-util/vulkan-headers-1.3.250
 [   80.0 K ] media-fonts/font-util-1.4.0
 [  180.0 K ] media-libs/vulkan-loader-1.3.250
 [  170.0 K ] x11-base/xcb-proto-1.15.2
 [  170.0 K ] x11-base/xcb-proto-1.15.2
 [   80.0 K ] x11-drivers/xf86-input-libinput-1.3.0
 [  330.0 K ] x11-libs/libdrm-2.4.115
 [  330.0 K ] x11-libs/libdrm-2.4.115
 [  480.0 K ] x11-libs/libxcb-1.15-r1

\rEmaint: fix binhost             [<=>                                          ]\rEmaint: fix binhost        100% [============================================>]\rEmaint: fix binhost        100% [============================================>]
 [   16.2 K ] Packages Index
 ===========
 [  133.2 M ] Total space from 12 files were freed in the packages directory
Container binhost-amd64-x86-64 exited successfully.
Machine binhost-amd64-x86-64-gnome

Spawning container binhost-amd64-x86-64-gnome on /var/lib/machines/binhost-amd64-x86-64-gnome.
Press Ctrl-] three times within 1s to kill container.

 * IMPORTANT: 26 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


 * IMPORTANT: 26 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.

>>> Running pre-merge checks for dev-java/openjdk-bin-17.0.8.1_p1
>>> Emerging binary (1 of 1) dev-java/openjdk-bin-17.0.8.1_p1::gentoo
>>> Installing (1 of 1) dev-java/openjdk-bin-17.0.8.1_p1::gentoo
>>> Completed (1 of 1) dev-java/openjdk-bin-17.0.8.1_p1::gentoo

 * IMPORTANT: 26 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 * 
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence of this, it often becomes necessary to run 
 * `emerge --update --newuse --deep @world` prior to depclean.

Calculating dependencies  ...\b\b... done!
>>> No packages selected for removal by depclean
>>> To see reverse dependencies, use --verbose
Packages installed:   1311
Packages in world:    34
Packages in system:   49
Required packages:    1311
Number removed:       0
Container binhost-amd64-x86-64-gnome exited successfully.
Machine binhost-amd64-x86-64-server

Spawning container binhost-amd64-x86-64-server on /var/lib/machines/binhost-amd64-x86-64-server.
Press Ctrl-] three times within 1s to kill container.
rsync: [Receiver] safe_read failed to read 1 bytes: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(282) [Receiver=3.2.7]
>>> Retrying...


>>> Starting retry 1 of 3 with rsync://[2a01:90:200:10::1a]/gentoo-portage

 * IMPORTANT: 14 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


 * IMPORTANT: 14 news items need reading for repository 'gentoo'.
 * Use eselect news read to view new items.


 * Always study the list of packages to be cleaned for any obvious
 * mistakes. Packages that are part of the world set will always
 * be kept.  They can be manually added to this set with
 * `emerge --noreplace <atom>`.  Packages that are listed in
 * package.provided (see portage(5)) will be removed by
 * depclean, even if they are part of the world set.
 * 
 * As a safety measure, depclean will not remove any packages
 * unless *all* required dependencies have been resolved.  As a
 * consequence of this, it often becomes necessary to run 
 * `emerge --update --newuse --deep @world` prior to depclean.

Calculating dependencies  .\b\b... done!
>>> No packages selected for removal by depclean
>>> To see reverse dependencies, use --verbose
Packages installed:   326
Packages in world:    9
Packages in system:   49
Required packages:    326
Number removed:       0
Container binhost-amd64-x86-64-server exited successfully.
Upsyncing binpackages from /var/lib/machines/binhost-amd64-x86-64/var/cache/binpkgs to amd64/17.1/x86-64



Full build log at /root/.tmp-binhost-amd64_17.1_x86-64-update-1698315421


             reply	other threads:[~2023-10-26 10:24 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 10:24 binhost [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-10 13:19 [gentoo-binhost-autobuilds] [binhost amd64/17.1/x86-64] Update possibly failed binhost
2024-01-09  7:21 binhost
2024-01-07 19:09 binhost
2024-01-07  7:57 binhost
2024-01-06  6:24 binhost
2024-01-05  1:27 binhost
2024-01-03 19:39 binhost
2024-01-02 17:22 binhost
2023-12-31 11:02 binhost
2023-12-30 21:25 binhost
2023-12-29 13:30 binhost
2023-12-29  3:36 binhost
2023-12-27 17:52 binhost
2023-12-26 10:31 binhost
2023-12-25 10:22 binhost
2023-12-24 10:30 binhost
2023-12-24  3:15 binhost
2023-12-22 11:22 binhost
2023-12-21 17:02 binhost
2023-12-20 11:26 binhost
2023-12-19 10:23 binhost
2023-12-19  0:39 binhost
2023-12-17 11:47 binhost
2023-12-16 10:23 binhost
2023-12-14 12:31 binhost
2023-12-13 10:28 binhost
2023-12-10 10:41 binhost
2023-12-09 11:57 binhost
2023-12-06 10:36 binhost
2023-12-03 10:24 binhost
2023-12-02 16:51 binhost
2023-11-30 11:06 binhost
2023-11-29 10:18 binhost
2023-11-28 10:56 binhost
2023-11-26 10:38 binhost
2023-11-24 15:12 binhost
2023-11-23 10:34 binhost
2023-11-22 12:32 binhost
2023-11-21 10:22 binhost
2023-11-20 14:25 binhost
2023-11-19 10:20 binhost
2023-11-18 10:24 binhost
2023-11-17 11:18 binhost
2023-11-16 10:24 binhost
2023-11-15 10:23 binhost
2023-11-14 10:24 binhost
2023-11-13 10:25 binhost
2023-11-12 23:08 binhost
2023-11-11 14:20 binhost
2023-11-10 10:28 binhost
2023-11-09 10:25 binhost
2023-11-08 10:24 binhost
2023-11-07 10:27 binhost
2023-11-06 10:25 binhost
2023-11-05 10:29 binhost
2023-11-04 17:14 binhost
2023-11-03 11:19 binhost
2023-10-31 19:34 binhost
2023-10-30 10:22 binhost
2023-10-29 10:36 binhost
2023-10-28 14:00 binhost
2023-10-25 16:58 binhost
2023-10-24 10:26 binhost
2023-10-22 13:23 binhost
2023-10-20 10:21 binhost
2023-10-19 13:53 binhost
2023-10-18 10:28 binhost
2023-10-17 10:56 binhost
2023-10-15 22:58 binhost
2023-10-15 11:11 binhost
2023-10-14 11:08 binhost
2023-10-13 13:24 binhost
2023-10-12 10:40 binhost
2023-10-11 11:43 binhost
2023-10-11  6:14 binhost
2023-10-10 20:21 binhost
2023-10-10 12:06 binhost
2023-10-09 19:44 binhost
2023-10-09 10:41 binhost
2023-10-08 10:23 binhost
2023-10-07 10:21 binhost
2023-10-06 10:20 binhost
2023-10-05 10:21 binhost
2023-10-02 10:25 binhost
2023-10-01 10:22 binhost
2023-09-30 11:27 binhost
2023-09-29 11:16 binhost
2023-09-28 10:29 binhost
2023-09-27 11:45 binhost
2023-09-25 11:23 binhost
2023-09-23 11:59 binhost
2023-09-21 10:24 binhost
2023-09-19 11:22 binhost
2023-09-18 10:26 binhost
2023-09-17 10:21 binhost
2023-09-15 10:57 binhost
2023-09-14 11:13 binhost
2023-09-10 10:23 binhost
2023-09-08 12:50 binhost
2023-09-04 10:30 binhost
2023-09-02 15:14 binhost
2023-08-30 12:16 binhost
2023-08-25 10:32 binhost
2023-08-21 10:25 binhost
2023-08-20 12:13 binhost
2023-08-19 10:24 binhost
2023-08-17 10:53 binhost
2023-08-13 10:31 binhost
2023-08-11 11:08 binhost
2023-08-07 20:53 binhost

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231026102446.28E3F268042@demeter.amd64.dev.gentoo.org \
    --to=binhost@demeter.amd64.dev.gentoo.org \
    --cc=gentoo-binhost-autobuilds@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox