From: binhost@jiji.arm.dev.gentoo.org
To: gentoo-binhost-autobuilds@lists.gentoo.org
Subject: [gentoo-binhost-autobuilds] [binhost arm64/23.0/arm64] Update failed
Date: Fri, 02 Aug 2024 03:30:20 +0000 [thread overview]
Message-ID: <d02d6df5bbf42c6d09288d9a419f540d@susuwatari.arm.dev.gentoo.org> (raw)
Binhost arm64/23.0/arm64 update failed in at least one nspawn
Starting run at Fri Aug 2 03:30:11 AM UTC 2024
Syncing host
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
Reading Portage settings...
Building database (/var/cache/eix/portage.eix)...
[0] "gentoo" /var/db/repos/gentoo/ (cache: metadata-md5-or-flat)
Reading up to 170 categories of packages...Finished
[1] "" /var/db/repos/crossdev (cache: parse|ebuild*3.0.24#metadata-md5#metadata-flat#assign)
Reading up to 170 categories of packages...EMPTY!
[2] "" /var/db/repos/local (cache: parse|ebuild*3.0.24#metadata-md5#metadata-flat#assign)
Reading up to 170 categories of packages...EMPTY!
Applying masks...
Calculating hash tables...
Writing database file /var/cache/eix/portage.eix...
Database contains 19023 packages in 170 categories
!!! Section 'local' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/local'
!!! Section 'crossdev' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/crossdev'
* IMPORTANT: 8 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
Machine binhost-arm64-kde-23
/root/bin/binhost-update: line 101: cd: /var/lib/machines/binhost-arm64-kde-23/etc/binhost: No such file or directory
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Directory /var/lib/machines/binhost-arm64-kde-23 doesn't look like it has an OS tree (/usr/ directory is missing). Refusing.
Machine binhost-arm64-gnome-23
/root/bin/binhost-update: line 101: cd: /var/lib/machines/binhost-arm64-gnome-23/etc/binhost: No such file or directory
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Directory /var/lib/machines/binhost-arm64-gnome-23 doesn't look like it has an OS tree (/usr/ directory is missing). Refusing.
Machine binhost-arm64-server-23
/root/bin/binhost-update: line 101: cd: /var/lib/machines/binhost-arm64-server-23/etc/binhost: No such file or directory
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Directory /var/lib/machines/binhost-arm64-server-23 doesn't look like it has an OS tree (/usr/ directory is missing). Refusing.
Upsyncing binpackages from /var/lib/machines/binhost-arm64-kde-23/var/cache/binpkgs to arm64/23.0/arm64
rsync: [sender] change_dir "/var/lib/machines/binhost-arm64-kde-23/var/cache/binpkgs" failed: No such file or directory (2)
Number of files: 0
Number of created files: 0
Number of deleted files: 0
Number of regular files transferred: 0
Total file size: 0 bytes
Total transferred file size: 0 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 0
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 51
Total bytes received: 15
sent 51 bytes received 15 bytes 18.86 bytes/sec
total size is 0 speedup is 0.00
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.3.0]
Full build log at /root/.tmp-binhost-arm64_23.0_arm64-update-1722569410
next reply other threads:[~2024-08-02 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 3:30 binhost [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-03 3:32 [gentoo-binhost-autobuilds] [binhost arm64/23.0/arm64] Update failed binhost
2024-08-04 3:33 binhost
2024-08-05 3:34 binhost
2024-08-06 7:24 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=d02d6df5bbf42c6d09288d9a419f540d@susuwatari.arm.dev.gentoo.org \
--to=binhost@jiji.arm.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