From: binhost@milou.amd64.dev.gentoo.org
To: gentoo-binhost-autobuilds@lists.gentoo.org
Subject: [gentoo-binhost-autobuilds] [binhost amd64/xx.x/x86-64] Update failed
Date: Thu, 23 May 2024 12:48:33 +0000 (UTC) [thread overview]
Message-ID: <20240523124833.4EAD574853B@milou.amd64.dev.gentoo.org> (raw)
Binhost amd64/xx.x/x86-64 update failed in at least one nspawn
* 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: 447
Packages in world: 50
Packages in system: 49
Required packages: 447
Number removed: 0
^[[32;01m*^[[39;49;00m Building file list for packages cleaning...
^[[32;01m*^[[39;49;00m Your packages directory was already clean.
Container binhost-amd64-x86-64-v3-server exited successfully.
Machine binhost-amd64-x86-64-kde-23
HEAD is now at 7d7bf19 Blender can't be built with baseline x86-64 anymore
Already up to date.
Spawning container binhost-amd64-x86-64-kde-23 on /var/lib/machines/binhost-amd64-x86-64-kde-23.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 35 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Verifying ebuild manifests
>>> Running pre-merge checks for dev-qt/qtwebengine-5.15.13_p20240510
^[[32m*^[[0m Checking for at least 64 GiB RAM ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
^[[32m*^[[0m Checking for at least 7 GiB disk space at "/var/tmp/portage/dev-qt/qtwebengine-5.15.13_p20240510/temp" ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
^[[32m*^[[0m Checking for at least 150 MiB disk space at "/usr" ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
>>> Emerging (1 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Installing (1 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Completed (1 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Emerging (2 of 3) app-text/libmspub-0.1.4::gentoo
>>> Emerging (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
>>> Installing (2 of 3) app-text/libmspub-0.1.4::gentoo
>>> Completed (2 of 3) app-text/libmspub-0.1.4::gentoo
>>> Installing (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
>>> Completed (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
* Messages for package dev-qt/qtwebengine-5.15.13_p20240510:
* This version of Qt WebEngine is based on Chromium version 87.0.4280.144,
* with additional security fixes from newer versions. Extensive as it is, the
* list of backports is impossible to evaluate, but always bound to be behind
* Chromium's release schedule.
* In addition, various online services may deny service based on an outdated
* user agent version (and/or other checks). Google is already known to do so.
*
* tldr: Your web browsing experience will be compromised.
* IMPORTANT: 35 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: 1752
Packages in world: 50
Packages in system: 49
Required packages: 1752
Number removed: 0
Container binhost-amd64-x86-64-kde-23 exited successfully.
Machine binhost-amd64-x86-64-gnome-23
HEAD is now at 7d7bf19 Blender can't be built with baseline x86-64 anymore
Already up to date.
Spawning container binhost-amd64-x86-64-gnome-23 on /var/lib/machines/binhost-amd64-x86-64-gnome-23.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 34 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
!!! The ebuild selected to satisfy "media-libs/openpgl:0/0.5" has unmet requirements.
- media-libs/openpgl-0.5.0-r1::gentoo USE="-debug" ABI_X86="(64)" CPU_FLAGS_X86="-avx2 -avx512dq -sse4_2"
The following REQUIRED_USE flag constraints are unsatisfied:
amd64? ( any-of ( cpu_flags_x86_sse4_2 cpu_flags_x86_avx2 cpu_flags_x86_avx512dq ) )
The above constraints are a subset of the following complete expression:
amd64? ( any-of ( cpu_flags_x86_sse4_2 cpu_flags_x86_avx2 cpu_flags_x86_avx512dq ) ) arm64? ( cpu_flags_arm_neon )
(dependency required by "media-gfx/blender-3.6.8::gentoo[openpgl]" [ebuild])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])
Container binhost-amd64-x86-64-gnome-23 failed with error code 1.
Machine binhost-amd64-x86-64-openrc-23
HEAD is now at 7d7bf19 Blender can't be built with baseline x86-64 anymore
Already up to date.
Spawning container binhost-amd64-x86-64-openrc-23 on /var/lib/machines/binhost-amd64-x86-64-openrc-23.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 25 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Verifying ebuild manifests
>>> Running pre-merge checks for dev-qt/qtwebengine-5.15.13_p20240510
^[[32m*^[[0m Checking for at least 64 GiB RAM ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
^[[32m*^[[0m Checking for at least 7 GiB disk space at "/var/tmp/portage/dev-qt/qtwebengine-5.15.13_p20240510/temp" ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
^[[32m*^[[0m Checking for at least 150 MiB disk space at "/usr" ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
>>> Emerging binary (1 of 3) app-text/libmspub-0.1.4::gentoo
>>> Installing (1 of 3) app-text/libmspub-0.1.4::gentoo
>>> Completed (1 of 3) app-text/libmspub-0.1.4::gentoo
>>> Emerging binary (2 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Installing (2 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Completed (2 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Emerging (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
>>> Installing (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
>>> Completed (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
* Messages for package dev-qt/qtwebengine-5.15.13_p20240510:
* This version of Qt WebEngine is based on Chromium version 87.0.4280.144,
* with additional security fixes from newer versions. Extensive as it is, the
* list of backports is impossible to evaluate, but always bound to be behind
* Chromium's release schedule.
* In addition, various online services may deny service based on an outdated
* user agent version (and/or other checks). Google is already known to do so.
*
* tldr: Your web browsing experience will be compromised.
* IMPORTANT: 25 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: 1835
Packages in world: 44
Packages in system: 49
Required packages: 1835
Number removed: 0
Container binhost-amd64-x86-64-openrc-23 exited successfully.
Machine binhost-amd64-x86-64-server-23
HEAD is now at 7d7bf19 Blender can't be built with baseline x86-64 anymore
Already up to date.
Spawning container binhost-amd64-x86-64-server-23 on /var/lib/machines/binhost-amd64-x86-64-server-23.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 19 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Emerging binary (1 of 1) app-arch/libarchive-3.7.4::gentoo
>>> Installing (1 of 1) app-arch/libarchive-3.7.4::gentoo
>>> Completed (1 of 1) app-arch/libarchive-3.7.4::gentoo
* IMPORTANT: 19 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: 447
Packages in world: 50
Packages in system: 49
Required packages: 447
Number removed: 0
^[[32;01m*^[[39;49;00m Building file list for packages cleaning...
^[[32;01m*^[[39;49;00m Your packages directory was already clean.
Container binhost-amd64-x86-64-server-23 exited successfully.
Machine binhost-amd64-x86-64-v3-kde-23
HEAD is now at 7d7bf19 Blender can't be built with baseline x86-64 anymore
Already up to date.
Spawning container binhost-amd64-x86-64-v3-kde-23 on /var/lib/machines/binhost-amd64-x86-64-v3-kde-23.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 35 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Verifying ebuild manifests
>>> Running pre-merge checks for dev-qt/qtwebengine-5.15.13_p20240510
^[[32m*^[[0m Checking for at least 64 GiB RAM ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
^[[32m*^[[0m Checking for at least 7 GiB disk space at "/var/tmp/portage/dev-qt/qtwebengine-5.15.13_p20240510/temp" ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
^[[32m*^[[0m Checking for at least 150 MiB disk space at "/usr" ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
>>> Emerging (1 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Installing (1 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Completed (1 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Emerging (2 of 3) app-text/libmspub-0.1.4::gentoo
>>> Emerging (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
>>> Installing (2 of 3) app-text/libmspub-0.1.4::gentoo
>>> Completed (2 of 3) app-text/libmspub-0.1.4::gentoo
>>> Installing (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
>>> Completed (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
* Messages for package dev-qt/qtwebengine-5.15.13_p20240510:
* This version of Qt WebEngine is based on Chromium version 87.0.4280.144,
* with additional security fixes from newer versions. Extensive as it is, the
* list of backports is impossible to evaluate, but always bound to be behind
* Chromium's release schedule.
* In addition, various online services may deny service based on an outdated
* user agent version (and/or other checks). Google is already known to do so.
*
* tldr: Your web browsing experience will be compromised.
* IMPORTANT: 35 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: 1752
Packages in world: 50
Packages in system: 49
Required packages: 1752
Number removed: 0
Container binhost-amd64-x86-64-v3-kde-23 exited successfully.
Machine binhost-amd64-x86-64-v3-gnome-23
HEAD is now at 7d7bf19 Blender can't be built with baseline x86-64 anymore
Already up to date.
Spawning container binhost-amd64-x86-64-v3-gnome-23 on /var/lib/machines/binhost-amd64-x86-64-v3-gnome-23.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 34 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Emerging binary (1 of 2) app-text/libmspub-0.1.4::gentoo
>>> Installing (1 of 2) app-text/libmspub-0.1.4::gentoo
>>> Completed (1 of 2) app-text/libmspub-0.1.4::gentoo
>>> Emerging binary (2 of 2) app-arch/libarchive-3.7.4::gentoo
>>> Installing (2 of 2) app-arch/libarchive-3.7.4::gentoo
>>> Completed (2 of 2) app-arch/libarchive-3.7.4::gentoo
* IMPORTANT: 34 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: 1402
Packages in world: 44
Packages in system: 49
Required packages: 1402
Number removed: 0
Container binhost-amd64-x86-64-v3-gnome-23 exited successfully.
Machine binhost-amd64-x86-64-v3-openrc-23
HEAD is now at 7d7bf19 Blender can't be built with baseline x86-64 anymore
Already up to date.
Spawning container binhost-amd64-x86-64-v3-openrc-23 on /var/lib/machines/binhost-amd64-x86-64-v3-openrc-23.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 25 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Verifying ebuild manifests
>>> Running pre-merge checks for dev-qt/qtwebengine-5.15.13_p20240510
^[[32m*^[[0m Checking for at least 64 GiB RAM ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
^[[32m*^[[0m Checking for at least 7 GiB disk space at "/var/tmp/portage/dev-qt/qtwebengine-5.15.13_p20240510/temp" ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
^[[32m*^[[0m Checking for at least 150 MiB disk space at "/usr" ...
^[[A^[[72C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
>>> Emerging binary (1 of 3) app-text/libmspub-0.1.4::gentoo
>>> Installing (1 of 3) app-text/libmspub-0.1.4::gentoo
>>> Completed (1 of 3) app-text/libmspub-0.1.4::gentoo
>>> Emerging binary (2 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Installing (2 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Completed (2 of 3) app-arch/libarchive-3.7.4::gentoo
>>> Emerging (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
>>> Installing (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
>>> Completed (3 of 3) dev-qt/qtwebengine-5.15.13_p20240510::gentoo
* Messages for package dev-qt/qtwebengine-5.15.13_p20240510:
* This version of Qt WebEngine is based on Chromium version 87.0.4280.144,
* with additional security fixes from newer versions. Extensive as it is, the
* list of backports is impossible to evaluate, but always bound to be behind
* Chromium's release schedule.
* In addition, various online services may deny service based on an outdated
* user agent version (and/or other checks). Google is already known to do so.
*
* tldr: Your web browsing experience will be compromised.
* IMPORTANT: 25 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: 1865
Packages in world: 45
Packages in system: 49
Required packages: 1865
Number removed: 0
Container binhost-amd64-x86-64-v3-openrc-23 exited successfully.
Machine binhost-amd64-x86-64-v3-server-23
HEAD is now at 7d7bf19 Blender can't be built with baseline x86-64 anymore
Already up to date.
Spawning container binhost-amd64-x86-64-v3-server-23 on /var/lib/machines/binhost-amd64-x86-64-v3-server-23.
Press Ctrl-] three times within 1s to kill container.
* IMPORTANT: 19 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
>>> Emerging binary (1 of 1) app-arch/libarchive-3.7.4::gentoo
>>> Installing (1 of 1) app-arch/libarchive-3.7.4::gentoo
>>> Completed (1 of 1) app-arch/libarchive-3.7.4::gentoo
* IMPORTANT: 19 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: 447
Packages in world: 50
Packages in system: 49
Required packages: 447
Number removed: 0
^[[32;01m*^[[39;49;00m Building file list for packages cleaning...
^[[32;01m*^[[39;49;00m Your packages directory was already clean.
Container binhost-amd64-x86-64-v3-server-23 exited successfully.
Upsyncing binpackages from /var/lib/machines/binhost-amd64-x86-64-kde/var/cache/binpkgs to amd64/17.1/x86-64
Number of files: 10,115 (reg: 7,939, dir: 2,176)
Number of created files: 3 (reg: 3)
Number of deleted files: 0
Number of regular files transferred: 5
Total file size: 28,928,383,016 bytes
Total transferred file size: 60,489,256 bytes
Literal data: 49,230,984 bytes
Matched data: 11,258,272 bytes
File list size: 262,117
File list generation time: 0.057 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 49,566,007
Total bytes received: 26,194
sent 49,566,007 bytes received 26,194 bytes 4,312,365.30 bytes/sec
total size is 28,928,383,016 speedup is 583.33
Upsyncing binpackages from /var/lib/machines/binhost-amd64-x86-64-v3-kde/var/cache/binpkgs to amd64/17.1/x86-64-v3
Number of files: 5,716 (reg: 3,557, dir: 2,159)
Number of created files: 4 (reg: 4)
Number of deleted files: 0
Number of regular files transferred: 6
Total file size: 10,288,679,526 bytes
Total transferred file size: 101,558,886 bytes
Literal data: 96,365,490 bytes
Matched data: 5,193,396 bytes
File list size: 196,598
File list generation time: 0.015 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 96,599,236
Total bytes received: 18,383
sent 96,599,236 bytes received 18,383 bytes 4,294,116.40 bytes/sec
total size is 10,288,679,526 speedup is 106.49
Upsyncing binpackages from /var/lib/machines/binhost-amd64-x86-64-kde-23/var/cache/binpkgs to amd64/23.0/x86-64
Number of files: 5,715 (reg: 3,558, dir: 2,157)
Number of created files: 4 (reg: 4)
Number of deleted files: 0
Number of regular files transferred: 6
Total file size: 10,259,288,473 bytes
Total transferred file size: 99,938,713 bytes
Literal data: 94,768,342 bytes
Matched data: 5,170,371 bytes
File list size: 196,600
File list generation time: 0.014 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 95,000,853
Total bytes received: 18,407
sent 95,000,853 bytes received 18,407 bytes 5,136,176.22 bytes/sec
total size is 10,259,288,473 speedup is 107.97
Upsyncing binpackages from /var/lib/machines/binhost-amd64-x86-64-v3-kde-23/var/cache/binpkgs to amd64/23.0/x86-64-v3
Number of files: 5,749 (reg: 3,588, dir: 2,161)
Number of created files: 4 (reg: 4)
Number of deleted files: 0
Number of regular files transferred: 6
Total file size: 10,512,060,792 bytes
Total transferred file size: 100,028,792 bytes
Literal data: 94,773,090 bytes
Matched data: 5,255,702 bytes
File list size: 196,575
File list generation time: 0.014 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 95,007,432
Total bytes received: 18,527
sent 95,007,432 bytes received 18,527 bytes 3,878,610.57 bytes/sec
total size is 10,512,060,792 speedup is 110.62
Full build log at /root/.tmp-binhost-amd64_xx.x_x86-64-update-1716455460
next reply other threads:[~2024-05-23 12:48 UTC|newest]
Thread overview: 293+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 12:48 binhost [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-23 15:12 [gentoo-binhost-autobuilds] [binhost amd64/xx.x/x86-64] Update failed binhost
2025-04-22 13:29 binhost
2025-04-21 10:55 binhost
2025-04-20 16:01 binhost
2025-04-19 12:04 binhost
2025-04-18 16:13 binhost
2025-04-18 12:40 binhost
2025-04-17 18:03 binhost
2025-04-16 11:37 binhost
2025-04-15 11:31 binhost
2025-04-14 18:11 binhost
2025-04-13 11:54 binhost
2025-04-11 13:13 binhost
2025-04-10 13:05 binhost
2025-04-09 11:42 binhost
2025-04-08 11:29 binhost
2025-04-06 11:54 binhost
2025-04-05 18:20 binhost
2025-04-03 13:24 binhost
2025-04-02 15:12 binhost
2025-03-30 19:26 binhost
2025-03-30 15:32 binhost
2025-03-28 10:04 binhost
2025-03-28 8:57 binhost
2025-03-27 15:25 binhost
2025-03-24 13:03 binhost
2025-03-23 10:59 binhost
2025-03-22 12:19 binhost
2025-03-21 11:27 binhost
2025-03-20 19:05 binhost
2025-03-19 11:39 binhost
2025-03-18 11:33 binhost
2025-03-17 13:44 binhost
2025-03-16 12:41 binhost
2025-03-14 12:48 binhost
2025-03-13 11:55 binhost
2025-03-12 11:42 binhost
2025-03-11 11:03 binhost
2025-03-09 14:45 binhost
2025-03-08 12:48 binhost
2025-03-08 9:09 binhost
2025-03-06 13:52 binhost
2025-03-04 13:40 binhost
2025-03-03 14:11 binhost
2025-03-02 13:37 binhost
2025-03-01 13:00 binhost
2025-03-01 7:54 binhost
2025-02-27 11:17 binhost
2025-02-26 15:41 binhost
2025-02-25 11:22 binhost
2025-02-24 19:37 binhost
2025-02-21 10:55 binhost
2025-02-20 10:46 binhost
2025-02-19 10:44 binhost
2025-02-19 1:06 binhost
2025-02-17 12:37 binhost
2025-02-16 12:56 binhost
2025-02-15 11:02 binhost
2025-02-14 15:17 binhost
2025-02-13 12:08 binhost
2025-02-12 10:43 binhost
2025-02-11 15:32 binhost
2025-02-10 11:24 binhost
2025-02-09 12:13 binhost
2025-02-08 15:14 binhost
2025-02-07 12:01 binhost
2025-02-06 16:39 binhost
2025-02-05 11:14 binhost
2025-02-04 10:55 binhost
2025-02-03 12:44 binhost
2025-02-01 11:55 binhost
2025-01-31 12:07 binhost
2025-01-30 10:57 binhost
2025-01-29 11:14 binhost
2025-01-28 11:22 binhost
2025-01-27 15:22 binhost
2025-01-26 12:35 binhost
2025-01-25 10:48 binhost
2025-01-24 11:21 binhost
2025-01-23 11:15 binhost
2025-01-20 16:45 binhost
2025-01-18 13:21 binhost
2025-01-17 12:39 binhost
2025-01-16 11:34 binhost
2025-01-15 12:21 binhost
2025-01-14 10:56 binhost
2025-01-14 6:51 binhost
2025-01-12 10:56 binhost
2025-01-11 16:40 binhost
2025-01-10 22:52 binhost
2025-01-10 11:12 binhost
2025-01-09 10:31 binhost
2025-01-08 10:43 binhost
2025-01-07 10:43 binhost
2025-01-06 13:11 binhost
2025-01-05 12:27 binhost
2025-01-04 10:54 binhost
2025-01-03 15:29 binhost
2025-01-02 10:37 binhost
2025-01-01 10:56 binhost
2024-12-31 13:30 binhost
2024-12-30 12:55 binhost
2024-12-30 2:02 binhost
2024-12-28 13:42 binhost
2024-12-27 10:13 binhost
2024-12-26 10:16 binhost
2024-12-25 10:34 binhost
2024-12-24 10:22 binhost
2024-12-23 18:24 binhost
2024-12-22 10:11 binhost
2024-12-21 16:17 binhost
2024-12-20 10:10 binhost
2024-12-19 10:08 binhost
2024-12-18 14:00 binhost
2024-12-17 12:02 binhost
2024-12-16 13:13 binhost
2024-12-16 6:34 binhost
2024-12-14 12:34 binhost
2024-12-13 16:05 binhost
2024-12-12 11:05 binhost
2024-12-11 17:00 binhost
2024-12-10 11:26 binhost
2024-12-09 14:44 binhost
2024-12-08 10:57 binhost
2024-12-07 23:48 binhost
2024-12-06 10:52 binhost
2024-12-05 15:01 binhost
2024-12-04 10:19 binhost
2024-12-03 10:22 binhost
2024-12-02 12:16 binhost
2024-12-01 11:03 binhost
2024-11-30 10:53 binhost
2024-11-29 16:58 binhost
2024-11-28 10:55 binhost
2024-11-26 12:35 binhost
2024-11-25 11:35 binhost
2024-11-24 10:39 binhost
2024-11-23 10:54 binhost
2024-11-21 14:12 binhost
2024-11-20 11:48 binhost
2024-11-19 12:06 binhost
2024-11-17 10:21 binhost
2024-11-16 10:30 binhost
2024-11-15 12:23 binhost
2024-11-14 11:05 binhost
2024-11-13 10:11 binhost
2024-11-12 12:43 binhost
2024-11-11 18:52 binhost
2024-11-10 14:01 binhost
2024-11-09 20:02 binhost
2024-11-08 11:32 binhost
2024-11-07 11:32 binhost
2024-11-06 11:18 binhost
2024-11-04 13:18 binhost
2024-11-03 18:46 binhost
2024-11-02 16:10 binhost
2024-11-01 18:51 binhost
2024-10-31 13:07 binhost
2024-10-30 10:10 binhost
2024-10-29 13:03 binhost
2024-10-28 11:30 binhost
2024-10-27 12:57 binhost
2024-10-26 9:58 binhost
2024-10-25 9:49 binhost
2024-10-24 9:59 binhost
2024-10-23 10:09 binhost
2024-10-22 11:34 binhost
2024-10-21 11:29 binhost
2024-10-20 9:59 binhost
2024-10-19 10:17 binhost
2024-10-18 9:53 binhost
2024-10-17 11:00 binhost
2024-10-16 9:59 binhost
2024-10-15 10:06 binhost
2024-10-14 11:57 binhost
2024-10-13 12:13 binhost
2024-10-12 16:14 binhost
2024-10-10 10:52 binhost
2024-10-09 10:17 binhost
2024-10-08 10:32 binhost
2024-10-08 4:52 binhost
2024-10-06 9:33 binhost
2024-10-05 13:35 binhost
2024-10-04 18:31 binhost
2024-10-03 10:44 binhost
2024-10-02 12:09 binhost
2024-10-01 11:16 binhost
2024-09-30 14:54 binhost
2024-09-29 11:41 binhost
2024-09-26 9:39 binhost
2024-09-24 12:25 binhost
2024-09-23 11:57 binhost
2024-09-22 10:13 binhost
2024-09-18 12:07 binhost
2024-09-13 13:58 binhost
2024-09-05 9:22 binhost
2024-09-04 9:23 binhost
2024-09-03 12:47 binhost
2024-09-02 14:32 binhost
2024-09-01 9:29 binhost
2024-08-29 11:06 binhost
2024-08-27 12:43 binhost
2024-07-19 9:15 binhost
2024-07-18 9:25 binhost
2024-07-17 10:26 binhost
2024-07-15 3:57 binhost
2024-07-14 9:38 binhost
2024-07-13 9:20 binhost
2024-07-12 13:31 binhost
2024-07-11 9:14 binhost
2024-07-10 9:15 binhost
2024-07-09 9:21 binhost
2024-07-08 9:17 binhost
2024-07-07 9:16 binhost
2024-07-06 9:39 binhost
2024-07-05 9:17 binhost
2024-07-04 9:51 binhost
2024-07-03 10:17 binhost
2024-07-02 9:31 binhost
2024-07-01 9:22 binhost
2024-06-30 10:15 binhost
2024-06-29 9:25 binhost
2024-06-28 9:16 binhost
2024-06-27 9:14 binhost
2024-06-26 9:19 binhost
2024-06-25 9:34 binhost
2024-06-24 9:24 binhost
2024-06-23 10:08 binhost
2024-06-22 9:18 binhost
2024-06-21 9:16 binhost
2024-06-20 9:13 binhost
2024-06-19 10:12 binhost
2024-06-18 9:56 binhost
2024-06-02 20:15 binhost
2024-06-02 18:22 binhost
2024-06-01 9:58 binhost
2024-05-31 12:00 binhost
2024-05-30 9:57 binhost
2024-05-29 10:19 binhost
2024-05-28 11:31 binhost
2024-05-27 9:38 binhost
2024-05-26 9:42 binhost
2024-05-25 9:29 binhost
2024-05-24 9:32 binhost
2024-05-22 9:58 binhost
2024-05-21 10:51 binhost
2024-05-20 9:35 binhost
2024-05-19 9:19 binhost
2024-05-18 9:57 binhost
2024-05-17 9:19 binhost
2024-05-16 10:35 binhost
2024-05-15 9:17 binhost
2024-05-14 9:51 binhost
2024-05-13 13:27 binhost
2024-05-12 9:40 binhost
2024-05-11 9:30 binhost
2024-05-10 9:59 binhost
2024-05-09 9:35 binhost
2024-05-08 9:46 binhost
2024-05-07 12:15 binhost
2024-05-06 9:19 binhost
2024-05-05 9:25 binhost
2024-05-04 19:53 binhost
2024-05-03 10:48 binhost
2024-05-02 9:21 binhost
2024-05-01 9:20 binhost
2024-04-30 10:21 binhost
2024-04-29 11:04 binhost
2024-04-28 9:58 binhost
2024-04-27 10:09 binhost
2024-04-26 9:31 binhost
2024-04-25 9:27 binhost
2024-04-24 10:27 binhost
2024-04-23 10:10 binhost
2024-04-22 10:03 binhost
2024-04-21 10:49 binhost
2024-04-20 9:46 binhost
2024-04-19 10:15 binhost
2024-04-18 13:01 binhost
2024-04-17 9:19 binhost
2024-04-16 12:59 binhost
2024-04-15 12:06 binhost
2024-04-14 13:07 binhost
2024-04-13 9:28 binhost
2024-03-28 9:25 binhost
2024-03-27 9:37 binhost
2024-03-26 9:45 binhost
2024-03-25 10:38 binhost
2024-03-18 10:48 binhost
2024-03-17 11:38 binhost
2024-03-16 12:21 binhost
2024-03-15 12:42 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=20240523124833.4EAD574853B@milou.amd64.dev.gentoo.org \
--to=binhost@milou.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