And when you look in those logs what do you see? Scott On 2021-09-27 10:59 a.m., Embedded Devel wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
it did continue, until the the end but did provide and error message about failed and missing rpms
[dingo@ffdf31df919a centos-mirror-tools]$ ls -al logs/*missing* -rw-r--r-- 1 dingo cgts 0 Sep 24 02:23 logs/K1_rpms_missing_centos.log -rw-r--r-- 1 dingo cgts 0 Sep 24 02:23 logs/K1_srpms_missing_centos.log -rw-r--r-- 1 dingo cgts 0 Sep 24 01:07 logs/L1_rpms_missing_3rdparties.log -rw-r--r-- 1 dingo cgts 0 Sep 24 01:18 logs/L1_rpms_missing_centos3rdparties.log -rw-r--r-- 1 dingo cgts 0 Sep 24 02:36 logs/L1_rpms_missing_centos.log -rw-r--r-- 1 dingo cgts 0 Sep 24 01:07 logs/L1_srpms_missing_3rdparties.log -rw-r--r-- 1 dingo cgts 5804 Sep 24 01:33 logs/L1_srpms_missing_centos3rdparties.log -rw-r--r-- 1 dingo cgts 83317 Sep 24 02:23 logs/L1_srpms_missing_centos.log -rw-r--r-- 1 dingo cgts 0 Sep 24 02:36 logs/log_download_tarball_missing.txt -rw-r--r-- 1 dingo cgts 270 Sep 24 02:36 logs/rpm-gpg-key-missing.txt
On Monday 27 September 2021 21:02:50 PM (+07:00), Scott Little wrote:
I don't think the entitlement server message is a fatal one.
Did download_mirror.sh actually fail on that message, Or did it keep going? What was the return code? did you look in logs/*missing* for a list of failed packages.
On 2021-09-27 6:24 a.m., Embedded Devel wrote:
[Please note: This e-mail is from an EXTERNAL e-mail address]
Hey can i ask, how you got past the cd $MY_REPO_ROOT_DIR/stx-tools/centos-mirror-tools && bash download_mirror.sh my errors below...
According to https://docs.starlingx.io/developer_resources/build_guide.html#run-building-...
Download packages¶ Inside the Docker container, enter the following commands to download the required packages to populate the CentOS mirror repository: cd $MY_REPO_ROOT_DIR/stx-tools/centos-mirror-tools && bash download_mirror.sh
ended up with
This system is registered with an entitlement server, but is not receiving updates. You can use subscription-manager to assign subscriptions.
so i register after hunting around google....
sudo subscription-manager register --username xxxxxxxx --password xxxxxxxx --auto-attach
and re-run cd $MY_REPO_ROOT_DIR/stx-tools/centos-mirror-tools && bash download_mirror.sh
now its saying
This system is registered with an entitlement server, but is not receiving updates. You can use subscription-manager to assign subscriptions.
so... how do i resolve this, i cant fix things and help if i cant build and test :) On Monday 27 September 2021 08:21:17 AM (+07:00), Shigeru Yoshida wrote:
Hi,
I'm trying to build StarlingX ISO following the Layered Build Guide.
When I run build-pkgs to build the compiler layer, building golang 1.13.15 failed with the following error:
# go tool dist test -run=^test:0_1$ BUILDSTDERR: run: go list -gcflags=all= -ldflags=all= -f={{if .Stale}} STALE {{.ImportPath}}: {{.StaleReason}}{{end}} std DONE BUILDSTDERR: /builddir/build/BUILD/go-13.15/test/runtest.exe --shard=0 --shards=1 BUILDSTDERR: run: go list -gcflags=all= -ldflags=all= -f={{if .Stale}} STALE {{.ImportPath}}: {{.StaleReason}}{{end}} std BUILDSTDERR: run: go list -gcflags=all= -ldflags=all= -f={{if .Stale}} STALE {{.ImportPath}}: {{.StaleReason}}{{end}} std DONE BUILDSTDERR: go run /builddir/build/BUILD/go-13.15/src/cmd/api/run.go BUILDSTDERR: run: go list -gcflags=all= -ldflags=all= -f={{if .Stale}} STALE {{.ImportPath}}: {{.StaleReason}}{{end}} std ##### API check # go tool dist test -run=^api$ Go version is "go1.13.15", ignoring -next /builddir/build/BUILD/go-13.15/api/next.txt BUILDSTDERR: run: go list -gcflags=all= -ldflags=all= -f={{if .Stale}} STALE {{.ImportPath}}: {{.StaleReason}}{{end}} std DONE FAILED RPM build errors: BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.7ZZ7V8 (%check) BUILDSTDERR: Macro expanded in comment on line 148: %{version}-%{release} BUILDSTDERR: Macro expanded in comment on line 149: %{version} BUILDSTDERR: Macro expanded in comment on line 150: %{version} BUILDSTDERR: Macro expanded in comment on line 151: %{version} BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.7ZZ7V8 (%check) Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", line 96, in trace result = func(*args, **kw) File "/usr/lib/python3.6/site-packages/mockbuild/util.py", line 736, in do_with_status raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode) mockbuild.exception.Error: Command failed: # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/golang.spec
It seems that other golang versions, e.g. 1.13.9, 1.15.14, and 1.16.6, are built successfully.
How can I fix this? Can anybody give me some comments to fix this?
Thanks, Shigeru
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
-- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com